FUTURE RESEARCH DIRECTIONS

The following directions are envisaged for future research. There is much research potential in the new fields of (i) third-party authentication, authorization, and accounting (3P-AAA) and third-party charging and billing (3P-C&B) and (ii) WBCs and ADA. Some ideas and directions are listed in the following. Included also is a suggestion to develop a cross-layer reference communications model to aid in design and analysis of open cross-layer functionalities.

3P-AAA and 3P-C&B

• Extending 3P-AAA into the area of wireless Ad Hoc networks. This can yield significant 3P-AAA use cases influencing the 3P-C&B requirements. Typical Ad Hoc domain scenarios involving hot-zone wireless heterogeneous architectures are envisaged where mobile terminals use multi-hop techniques to get to a hot zone using intermediate mobile terminals (the latter should benefit from their role in such scenarios, i.e., be paid properly).
• Research to date has identified and established the basic charging scenarios in CBM-based UCWW by employing inter-3P-AAA-SP signalling. However, when the inter-3P-AAA-SP signalling involves Internet usage, then charging interactions can experience high network latency. To eliminate this problem either further optimization is needed in the 3P-AAA-SP signalling (i.e., compressing the messages where possible) or a new ‘charging agent’ concept should be developed. This new concept would result in the following: (1) the charging occurs in the metering domain (TSP/ANP), (2) the charging agent is downloaded from the 3P-AAA-SP to provide the charging function in the TSP/ANP domain, (3) the charging agent imports the charging rule set from the 3P-AAA-SP, (4) the charging agent imports segments of the consumer account into the metering domain.
• Elaboration of the C&B framework to support dynamic reconfiguration of applicable metering and pricing policies for specific service, specific user or combination of both, and to support various pricing models according to the service profile, user profile and location, and one-stop billing schemes.
• Implementation of a C&B system prototype as a discrete service that can be provided by a trusted third-party authentication, authorization and accounting service providers (3P-AAA-SPs).
• Running trial experiments with the designed prototype in a 4G testbed environment showing good interfacing with the 3P-AAA service, WBC&ADA services, and other (new) types of 4G services (e.g., consumer-oriented ICC service).

WBC and ADA

• At the WBC Service Layer - Besides the intelligent software architecture already mentioned, other issues for future investigation include:
• Agent environment: JADE has been used to date to act as an agent environment in the heterogeneous WBC software architecture. However, JADE is a heavy agent platform with a big footprint for executing both the SD collecting, clustering, scheduling, indexing, broadcasting on the server side, and the SD discovery and association on the mobile terminal side. In addition, it does not fully support the BDI agent. Therefore, investigation into lightweight BDI-based Java agent platforms (WBC-BDI) is recommended. Formatting the communication language's messages with WBC-ASN is also recommended, as well as ensuring that the agent platform functions correctly in the following environments: J2SE (Sun Java 2 platform, standard edition 2003), J2ME (Sun J2ME Specification 2009), Android (Google Android Software Development Kit 2008), WinCE (Windows Embedded CE Overview 2008), etc.
• SD formatting: In order to encode SDs in a more compact way, an efficient abstract syntax notation language based on ASN.1 (WBC-ASN) is suggested. Any design should take into account the requirement for minimizing decoder's power consumption.
• Rule engine: Resolution of the need to improve the flexibility and scalability could be approached by designing an intelligent SD self-organization lightweight Java rule engine. In suggesting this, we also recommend that the rules configuration file here could be defined with WBC-ASN.
• ADP: Designing with system scalability in mind, the route of developing the ADP protocol in Java, together with a Java-based Reed-Solomon algorithm being fully implemented is suggested as worthy of investigation.
• Profile design: To increase security and privacy for WBC-SPs, and mobility and personalization for mobile users, investigation of the benefits from this perspective of a well-structured rule-based profile developed and formatted with WBC-ASN is suggested.
• At the WBC Link Layer and Physical Layer - Potential broadcast platform solutions include WBC over DVB-H, over DRM, over DAB, etc. Investigations in the technical realization configurations for each have yet to be undertaken. There is little doubt about the potential consumer base into which WBC advertisement may be pushed. Today, for instance, there is an expectation of 300 million DVB-H capable handsets operational by 2009/10.

Cross-Layer Reference Communication Model

Some activities within UCWW, such as end-to-end (E2E) hot access network change (HAC) based on user-driven ABS&S policies, require cross-layer protocol functionality. Other examples include E2E reconfigurability (Z. Boufidis et. al., 2004, Sept), service adaptability (Houssos, N., et. al. 2003), E2E QoS support (Politis, C. al., 2004), ABC&S (O'Droma, M., Ganchev, I, et. al., 2006), user/network/service/terminal profile management, 3P-AAA and related 3P-C&B, and WBC & ADA operation. While this seems to contradict the layering architecture model for designing, planning, implementing and analysing communication protocols, nonetheless, it is the reality and it is worthwhile to structurally allow for it with suitable modifications of the reference models. Such a suitably modified reference communication model is presented in Figure 1. 

It has similarities with the B-ISDN/ATM reference communication model in that it is a 3D model consisting of three planes: user plane, control plane, and management plane. The new central element, which intersects all three planes, is added to allow for structured cross-layer functionality. This cross-layer core cylinder is a modification ofthat proposed in (Ganchev, I., O'Droma, M., et. al., 2006) and may be visualized as consisting of several parallel mini cylinders each with its own dedicated functionality, e.g., corresponding to the activities already listed above with cross-layer protocol functionality. Formal reflecting of these activities and their cross-layer functionalities into this model will assist their formal design and analysis, and facilitate development of formal and open primitives and APIs.

Figure 1: The proposed cross-layer reference communication model