User Requirements (0) : The real user requirements that should be taken into account during the early phase of system design can be classified according to various perspectives and metrics, including durability, fault-tolerance and manageability. First, the user should be capable of maintaining a persistent connection to servers of interest. The model of peer-to-peer systems, although criticized for its business potential, has highly been adopted by the Internet community, due to the provision of a high degree of connectivity in a transparent fashion, even in the presence of failures. Users can always retrieve data regardless of the server location, whilst queries are optimized to fetch the nearest replica, exploiting locality and minimizing the necessary resources. Local loop unbundling aims at fast, always-on Internet access. These efforts have their counterparts in the mobile industry via the integration of Wireless LANs and 3G systems. The underlying objective is to combine a cheep, flexible, easily deployed but untrustworthy technology with a stable, resilient infrastructure. Users registered with a 4G provider would require that they be always connected enjoying an acceptable level of quality of service, while roaming among diverse systems including direct video. Thus, the issue have been split into: -Requirements on connectivity -Requirements on servive provision -Requirements on adaptibility and reconfigurability
Private list for “Requirements” Task force (0)
Final Draft D1.1.1: User Requirements for Next Generation Networks
This deliverable is an attempt to define the requirements that users impose in the evolving world of heterogeneous wireless networks. These requirements are grouped together in three main and distinguishable categories: Connectivity, Service Provision and Adaptability/Reconfigurability. For each category the requirements are given in a structural manner from content/application providers to network and terminal or from application/transport layers to network/physical. These user requirements work in ANWIRE is intended to provide a user focus on system concepts by disseminating user requirements to the technical Work Packages.
final draft D1.1.2 V1.0: Report on the coordination of integrated
This deliverable focuses on the identification of generic requirements forReconfigurability, Adaptability and always-on connectivity features that will enhance the services offered by the wireless networks. To provide an essential impact on existing and future systems, all aspects including user (covered in D1.1.1 to a large extent), network operator and service provider needs for always-on connectivity as well as adaptability and reconfigurability are to be discussed.
5th draft D1.1.3 v1.0: Report on the co-ordination of integrated
The main scope of this deliverable is to identify novel system concepts, which can be potentially standarised across the core and access network and terminals. The introduction of a generic architecture enabling always on connectivity as well as the distributed processing of reconfigurability management related features in various layers and an environment empowering adaptability in service creation, introduction, deployment and execution will be investigated based on integrated thematic efforts. Location and context awareness will be also investigated. The identification of methods for network and terminal capabilities negotiation, spectrum sharing, mode detection, policy provision and respective adaptability and reconfiguration actions triggering, seamless service provision by mode switching secure software download will be elaborated.