hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0265427df956e32eb1f8284408761815 | 101 177 | 4.7 Service support | |
0265427df956e32eb1f8284408761815 | 101 177 | 4.7.1 Service transparency and service independence | An operator using HIPERACCESS should be able to provide a similar set of bearer services and a similar grade of service to his competitor using VDSL or cable modems, though there may be limitations on the penetration of the potential user base which can be served. HIPERACCESS will provide service transparency and be service independent. To ensure service transparency, the performance of the system should be such that the application behaviour will be the same as on a wired system of equivalent bandwidth. To be service independent, the system behaviour should be independent of the information types being transported. The system will be capable of providing high bit-rate services with variable symmetry and transfer rates, as needed to support ATM and future applications of IP. It will also be capable of efficiently providing "toll quality" POTS and ISDN. |
0265427df956e32eb1f8284408761815 | 101 177 | 4.7.2 Typical customer applications | Broadband fixed radio access networks have to be flexible enough to support a wide range of applications in use today and to support future services. The main user applications that can be foreseen today are as follows: - internet access; - home working; - Local Area Network (LAN) emulation (i.e. connecting remote workstations to LANs via routers and PP links); - video-telephony and video conferencing; - real time video (the degree to which it is economical to offer video distribution services will depend on the required video quality, spectrum availability, the economics of the HIPERACCESS system and subscriber densities); - real-time audio; and - computer gaming. In addition to the above broadband applications, HIPERACCESS will include support for existing narrowband applications: - voice (using 64 kbit/s and lower rate code(s); - legacy voice-band modems (including fax); and - narrowband ISDN. TR 101 177 V1.1.1 (1998-05) 22 |
0265427df956e32eb1f8284408761815 | 101 177 | 4.7.3 Bandwidth | Table 4.2 lists the bandwidth requirements for applications of broadband access by market sector, distilled from the general requirements illustrated above. Table 4.2: Requirements for access bandwidth by market sector Market sector and applications Peak data rate (bit/s) Residential narrowband service (POTS and ISDN Basic Rate Access (BRA)) 32k to 144k SME service (POTS, ISDN Primary Rate Access (to ISDN) (PRA), LAN interconnect) 2M to 25M Large enterprise service (ISDN PRA, LAN interconnection, Leased lines, etc.) 25M to 155M (see note) Public safety/utility (Network disaster recovery, multimedia kiosks, wideband telemetry, etc.) 2M Consumer electronic commerce (Transaction processing, home banking, targeted marketing, interactive advertising, etc.) 2M to 8M Residential entertainment (Internet, digital audio/video programming, Video on Demand (VoD), HDTV, etc.) 2M to 25M Educational/medical (Corporate training, distance education, telemedicine, etc.) 2M to 25M Telecommuting support (LAN interconnect, multipoint video teleconferencing, etc.) 2M to 25M NOTE: Large enterprises may have high bandwidth requirements for corporate telephony and corporate data network interconnection. The bandwidth is also in use for long periods because the organizations have internal network equipment such as PABXs and routers which "concentrate" traffic. The "large enterprise" market sector is therefore regarded generally as outside HIPERACCESS' scope, because the bandwidth required may be too large and the efficiencies of statistically multiplexing traffic on a shared air interface are small. The table states the overall peak bandwidth required. However, this bandwidth may be required in both directions (for example for telephone or videophone/videoconference calls); to the customer's premises (for example for viewing video, or downloading large files from a corporate LAN server); or from the customer's premises (for example web server access or file transfer from a corporate LAN server. In general there may be data flows to and from customers' premises with different bandwidths in both directions. In addition within the premises several users sharing the same subscription (e.g. the members of a family or the employees of a company) may be running several applications (e.g. in a family, using the 'phone, watching television, accessing the internet) and each application may have different data flow characteristics. The data rates shown above are those for the total of all the applications from the premises. |
0265427df956e32eb1f8284408761815 | 101 177 | 4.8 HIPERACCESS deployment | This subclause describes examples of how HIPERACCESS may be deployed to serve various users and areas. The deployment configurations outlined below are for-example only and should not be regarded as exclusive. It is tempting to consider HIPERACCESS systems in similar configurations to mobile cellular systems, however this may not be the case and it is important not to think in this constrained way. Specific "non-cellular" deployments shown below include the use of repeaters to fill-in coverage in hard-to-get-to locations where it is cheaper to provide a repeater site that has only a power feed and no network connection; and the concept of being able to take service from multiple base stations, to account for varying propagation conditions. These features may not be needed at the lower radio frequencies, say around 3 GHz, but at higher frequencies, say 40 GHz, may be essential to obtaining a high percentage of reliable coverage over a service area. TR 101 177 V1.1.1 (1998-05) 23 |
0265427df956e32eb1f8284408761815 | 101 177 | 4.8.1 General | A HIPERACCESS system will be capable of deployment over an area that is in principle unlimited (such as a large city). It will only provide fixed services; that is, the AT to which users' terminals are connected are permanently fixed to the structures of buildings. The system will be economically viable in low to medium penetrations (1% to 20%) of households and SMEs in typical semi-rural, suburban, urban and dense urban environments in most of the world, taking account not only of the costs of AP and ATs but any necessary links connecting the APs to (e.g.) switches. In practice this means that a high proportion of the network investment should be in the customer termination equipment. The system should be flexible and efficient so that it can support several configurations, for example: - one AT supporting several applications in several attached terminals; - one AT supporting one customer; or several customers in the same premises who would have separate subscriptions (for the purposes of billing, service management, and fault management for example). The system will also meet the needs of small and medium size enterprises who usually require communications bandwidth at a different time of the day from residential users and can therefore efficiently share network infrastructure. This may be aided by incorporating means to re-configure the network to "move" capacity to different areas depending on traffic load distribution. |
0265427df956e32eb1f8284408761815 | 101 177 | 4.8.2 Example deployment configurations | Figure 4.3 shows an example deployment configuration of HIPERACCESS. The AP (the base station) can serve individual buildings, multiple subscribers in multiple buildings (using multiple radio links), or multiple subscribers in a single building by use of a single radio link and further in-building distribution systems. NOTE: It should not be assumed that all the interfaces shown in figures 4.3 and 4.4 will be subject to HIPERACCESS standardization. TR 101 177 V1.1.1 (1998-05) 24 Core network APC AT AT AT feeding multiple residentialcustomers APT APT AT feeding SME customer AT AT Repeater site AT feeding single residential customer Diverse routing Figure 4.3: A typical deployment configuration Figure 4.3 above shows the use of a repeater and route diversity in order to fill-in coverage in difficult areas. This does not imply the use of these features in all types of HIPERACCESS system. However it does require the capability to implement them if required, and leave them out if not. The use of sectorisation at an AP is not shown here, but may be expected in many cases. Sectorisation is used for several reasons. First, at microwave frequencies it becomes impossible to make a practical omni-directional antenna, and in any case its omni-directional pattern would be destroyed when mounted on a mast. Second, sectorisation may be used to improve frequency re-use and hence system capacity. Third, sectored antennas have higher gain and may improve range. One sector would be fed from at least one Access Point Transceiver (APT). In rare cases an APT may illuminate more than one sector through a passive splitter (for example when only limited sectors of the field of view are inhabited and likely user density is low). The core network in figure 4.3 could be ATM, IP, PSTN/ISDN, or a combination (with suitable interworking units). |
0265427df956e32eb1f8284408761815 | 101 177 | 4.8.3 Interfaces at the customer premises | At the user or customer end, the interface to the customer's equipment will not be explicitly specified by HIPERACCESS. It could be any one (or more) of the many existing and future (perhaps standardized) interfaces. The air interface protocol is interworked to the interface(s) in use. This approach allows the implementation of a wide range of options to fit specific customer needs. A few examples are described here (with reference to figure 4.4), but clearly they do not represent the full set of possibilities. TR 101 177 V1.1.1 (1998-05) 25 Within individual dwelling units: - simple connection to a Personal Computer (PC), Network Computer (NC) or peripheral via standardized interfaces (e.g. Ethernet, USB, IEEE 1394, ATM etc.); - connection to common residential entertainment equipment such as a STB, digital TV, HiFi or games console. This may be through one of the interfaces above, or otherwise; - analogue telephone or ISDN terminal through suitable terminal adapter; - further short range wireless network within the unit (for example HIgh PErformance Radio Local Area Network (HIPERLAN)); and - a combination of the above. Serving Multiple Dwelling Units (MDUs): - distribution to each individual residence, via a per-residence antenna; or a single AT and an in-building distribution network; - use one radio link to a large building and then further wired distribution to individual residences within the building; - further short range wireless network within the building (for example HIPERLAN); and - connection to narrowband mux. or concentrator within building. Business customers: - connection to router and LAN; - connection to PABX; and - further short range wireless network within the building (for example HIPERLAN). It is not required that the HIPERACCESS standards will define how all these interfaces will be supported. Rather, interworking definitions should be developed for a limited set of standard network layer protocols (e.g. ATM, IP), so that standardized methods of supporting other interfaces can be called on. TR 101 177 V1.1.1 (1998-05) 26 V5 Multiplexer PC ISDN PBX Voice over IP Voice Facsimile LAN Router Set-top box Video conference Access Termination Figure 4.4: Customer interface functionality (examples) |
0265427df956e32eb1f8284408761815 | 101 177 | 4.9 Miscellaneous issues | The HIPERACCESS system design should also consider the following issues: - it should support standard user-network interfaces; - while network management should follow standard TMN principles, the specific needs of access and radio systems should be taken into consideration; - customer equipment especially should be cheap to implement; - efficient use of appropriate frequency bands to enable operators to meet availability, QoS and Grade of Service (GoS) requirements economically; - it should be transparent to billing (or at least make no limitation of billing options); - equipment should be easy to install, in particular the ATs in customer premises; - requirements for frequency planning should be minimized, though it should be possible for an operator to manually intervene to optimize frequency re-use; - smooth upgrade of network capacity from initial "coverage-dominated" to eventual "capacity dominated" roll-out; and - the difficulty of obtaining LOS for propagation at microwave frequencies and the desirability of standardized functions such as repeaters to enable more economical coverage and the high availability required for fixed services. TR 101 177 V1.1.1 (1998-05) 27 The needs of established public telecommunications operators, new public telecommunications operators and private network operators should be considered. |
0265427df956e32eb1f8284408761815 | 101 177 | 5 Requirements | Requirements may be of three types: - end-to-end (i.e. UNI to UNI) requirements for networks including a HIPERACCESS system; - requirements to be met by the complete HIPERACCESS system at or between its external interfaces; and - requirements to be met by sub-systems within a HIPERACCESS network. These requirements do not explicitly address any end-to-end requirements except in the context of setting the requirements for complete HIPERACCESS systems. These requirements are generally set within specifications that are outside the scope of the BRAN Project. The requirements are generally defined using the terminology introduced informally in figure 4.1. There are some general requirements for complete HIPERACCESS systems. - Logically at least, a HIPERACCESS system should be capable of replacing an ITU-T Recommendation G.902 [24] - compliant wired access network. Therefore it should comply with ITU-T Recommendation G.902 [24] wherever appropriate. This may not need to be strictly enforced, and some requirements of ITU-T Recommendation G.902 [24] may be inappropriate for certain types of broadband access network and service type. - HIPERACCESS information transport shall be service independent. That is, the HIPERACCESS system shall not (need to) know about the precise nature of the traffic it carries. - Where appropriate, HIPERACCESS shall conform to a service contract on a connection-by-connection basis (e.g. for ATM connections). The available service contracts, their data rates and the QoS parameters to be supported shall be specified. - It is not envisaged that an AT shall be moved once it has been affixed to subscribers' premises. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.1 External interfaces, and network management | A HIPERACCESS network has three external interfaces (see figure 5.1), the SNI, the user-network interface (UNI) and the management interface. It may actually be connected to multiple service nodes and/or to multiple user-network interfaces. HIPERACCESS Network Management Interface Service Node Interface User-Network Interfaces Service Node Management Interface Telecommunications Management Network Figure 5.1 HIPERACCESS interfaces TR 101 177 V1.1.1 (1998-05) 28 In HIPERACCESS the UNI will be supported at an AT, (see figure 4.1). A single AT should be able to support several UNIs, for example a 100BaseTX Ethernet PC interface; a POTS or ISDN interface for telephony; and a DAVIC [37] interface to a video set-top box. The HIPERACCESS standard will define how a range of standardized interfaces are supported for interoperation with other networks (see table 5.1). Table 5.1 Standardized HIPERACCESS interfaces Supported Service Service Node Interface User Network Interface Comments PSTN - ETS 300 347/A1 [42] - EN 301 005-1 [43] POTS (national standards) N-ISDN - ETS 300 347/A1 [42] - EN 301 005-1 [43] - ISDN BRA (ITU-T Recommendation I.430 [27]) - ISDN PRA/2 048 kbit/s (ITU-T Recommendation I.431 [28]) B-ISDN ATM - EN 301 005-1 [43] - ATM Forum (ATMF) NNI (ITU-T Recommendation Q.2140 [31] /ITU-T Recommendation Q 2144 [32]) - FDDI (ISO 8802.5 [14]) - ATMF ATM Inter Network Interface - B-ISDN/2 048 kbit/s (ITU-T Recommendation I.432 [29]) - ATM UNI 4.0 [45], UNI 3.1 [44] - Ethernet (ISO 8802.3 [13]) on 10baseT and 100baseTX - DAVIC [37] ATM as an end-to-end transport mechanism carrying an unspecified service IP - ETS 300 347/A1 [42] - EN 301 005-1 [43] - ATMF NNI (Q.2140/4 [30], [31]) - FDDI (ISO 8802.5 [14]) - UMTS - Ethernet (ISO 8802.3 [13]) on 10baseT and 100baseTX - IEEE 1394 [46] and USB [47] - ATM UNI 4.0 (AAL5 UBR) [45] - DAVIC [37] UMTS - UMTS As above As defined by the ETSI GSM/UMTS Project. SMG3 An open standard protocol should be used by the management entity of the HIPERACCESS system to interface to the external network manager of the operator. Generally, the network management interface requirements should follow the guidelines of ITU-T Recommendations G.902 [24], M.3010 [30], and the ETSI V5 and VB5 series of recommendations where applicable [42] and [43]. For HIPERACCESS systems conforming to interoperability standards the following network management guidelines should be followed: - as an over-riding requirement, it should be possible to provision and operate an AT provided by one supplier on an AP provided by another; - remote and local test, configuration, and software download should be supported; - a standardized interface should be defined for local management (i.e. not over the air) at the AT; - a standardized set of MIB information elements should be defined to permit at least a basic level of interoperation of ATs with APs; - any radio relay or repeater function should be a managed element; and - specific needs of radio network management should be considered and defined as appropriate. TR 101 177 V1.1.1 (1998-05) 29 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2 HIPERACCESS transport requirements | Within a HIPERACCESS network, requirements may be put on all of its sub-systems. Furthermore, complete end-to-end network requirements must be met for acceptable levels of user service. Here we derive the HIPERACCESS network's transport requirements, that is between the service node interface and the user-network interface. In order to identify those requirements, we consider a top down approach from the application characteristics down to the access network transport requirements. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.1 Transparency | The behaviour of a user's application connected through HIPERACCESS shall be indistinguishable from that of the same application connected through a wired broadband access network. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.2 Service independence | A HIPERACCESS system must not need to have information on the type of application information being carried to transport it correctly. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.3 Throughput requirements | Table 5.2 lists the desired characteristics for some specific applications that are to be transported. Although HIPERACCESS must be service-independent they are listed to allow the transport requirements of the network to be derived. TR 101 177 V1.1.1 (1998-05) 30 Table 5.2: Characteristics for broadband access by application Application Downstream data rate (bit/s) Upstream data rate (bit/s) Transfer Mode (note 6) Mean transit delay (ms) (note 7) Maximum transit delay variation Telephony (PSTN) 64 k max. (note 9) 64 k max. (note 9) Circuit Oriented 10 (note 1) ≈0 (note 1) N-ISDN 64 k to 1 920 k 64 k to 1 920 k Circuit Oriented 10 (note 1) ≈0 (note 1) High quality video conference (note 2) 1,5 M to 6 M 1,5 M to 6 M Circuit Oriented tbd (note 2) ≈0 (note 2) VoD 1,5 M to 6 M (HDTV: 25M) Packet mode (note 3) Circuit Oriented 300 ≈0 (note 4) Near VoD (NVoD) 1,5 M to 6 M (HDTV: 25 M) Packet mode (note 3) Circuit Oriented 300 ≈0 (note 4) WWW browsing 10 M 1 M (note 8) Connection- less 10 approx. 100 WWW serving (note 5) (note 5) Connection- less 10 approx. 100 Remote access to corporate data network 25,6 M (note 5) 25,6 M (note 5) Connection- less 10 approx. 100 LAN Interconnect 25,6 M (note 5) 25,6 M (note 5) Connection- less 10 approx. 100 NOTE 1: For telephony service echo cancellers are needed if the round-trip delay exceeds critical values (which are generally functions of the national network). Beyond a round-trip delay of 100 ms to 200 ms natural conversation becomes very difficult. NOTE 2: High-quality video conferencing is an assumed service which uses (e.g.) MPEG to transport video to overcome the main objection to the quality of existing video- conferences. NOTE 3: For VoD and NVoD the upstream channel used for programme selection should be carried on a packet-mode (e.g. IP) bearer and "bandwidth" is an inappropriate term. Only infrequent, short messages are carried to select programme material. NOTE 4: VoD and NVoD services need relatively short one-way end-to-end delay if the user interaction is to be acceptable. The end-to-end delay variance for these applications must also be essentially zero but this may be achieved by application buffering. NOTE 5: IP datagrams should be transferred at the maximum possible burst rate the system is capable of. Services such as LAN interconnection which apparently do need the maximum possible rate in each direction are delay-insensitive, so that the full bandwidth is not needed in both directions simultaneously. NOTE 6: "Transfer Mode" refers to the switching paradigm of the complete network. "Circuit Oriented" is the classic PSTN/ISDN model of a deterministic isochronous switched circuit. "Connection Oriented" is the concept introduced in X.25 and continued in ATM for a packet-mode, possibly non-deterministic, information transfer based on the "virtual" call. "Connectionless" is the IP model where information is transferred in autonomous independently addressed packets and there is no concept of a "call". NOTE 7: Mean transit delay and transit delay variation are measured as in ITU-T Recommendation E.800 [18] between W.3 and W.2. NOTE 8: Whilst the main data flow for WWW browsing is in the "down" direction, a substantial upstream bandwidth is also required for TCP acknowledgements, estimated to be 10 % of the downstream requirement. NOTE 9: Most applications (for example POTS) which need a symmetrical "duplex" service are quite low bit-rate. Even the "hypothetical" high-quality videoconference service only needs a maximum of 6 Mbit/s in each direction. Based on this the following bandwidth specification may be derived for HIPERACCESS. The HIPERACCESS standard shall support a peak aggregate information rate of at least 25 Mbit/s at the UNI of a single AT. This aggregate rate will be shared between the incoming and outgoing streams associated with all the active applications supported through the UNI. Methods shall be defined for an APT to communicate with ATs which support lower peak information rates. This may for example be to allow lower cost implementation, or to operate with longer range. TR 101 177 V1.1.1 (1998-05) 31 The HIPERACCESS standard will specify methods to allow conformant equipment to manage (for example through radio channel numbering) a radio spectrum allocation of a minimum of 2 GHz. The HIPERACCESS standard shall allow for implementation of systems providing efficient transport of ATM, IP, MPEG streams, POTS, and narrowband ISDN. Multicast is an important capability to support future IP and ATM applications efficiently. Radio access systems in particular can be made more efficient by using multicast for data intended for multiple users. HIPERACCESS must therefore support multicast. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.4 Signalling | HIPERACCESS shall not terminate the UNI signalling. It shall only interpret the UNI signalling to the extent necessary to allow efficient multiple access. In general billing is done through the switching function in the network and the HIPERACCESS system shall neither include any specific, nor imply any limitation on, billing functionality. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.5 Performance | It shall be possible for a HIPERACCESS system to achieve the following objectives when deployed under limiting conditions (in respect of range, capacity, etc.). Table 5.3: Performance objectives POTS ISDN ATM IP Access network delay (mean) ms (notes 1and 2) 10 10 5 10 Access network delay variation µs 12,5 12,5 1 000 100 000 Bit error ratio 10-3 10-6 N/A N/A Cell/packet error ratio N/A N/A [10-10] [10-10] Cell/packet loss ratio N/A N/A [10-8] [10-8] Cell/packet mis-routing ratio (note 5) N/A N/A [10-12] [10-12] Route set-up time (note 3) ms 50 50 50 N/A Availability note 4 note 4 note 4 note 4 NOTE 1: If the round trip delay exceeds a value which depends on the national network echo cancellers may be needed. If the access network delay exceeds certain values special steps may need to be taken with ISDN to ensure that certain layer 3 timers operate correctly. NOTE 2: For ATM the delay and delay variation is for constant bit-rate services. NOTE 3: Route set-up time is the time from submitting an DLC_CONN_req to the Data Link Control (DLC) layer to the DLC layer returning a positive DLC_CONN_conf, or the equivalent, assuming that the service node response time is zero. NOTE 4: Availability objectives are tbd. Sources of information for guidance can be found in ITU-T Recommendations. G.827 [23], I.355 [25]and I.357 [26], ETSI standards I-ETS 300 416 [11] and I-ETS 300 465 [12], and ITU-R Recommendations. F.557 [15], F.695 [19], F.696 [20] and F.697 [21]. NOTE 5: Cell and packet mis-routing occurs when Virtual Channel Indicator (VCI)/Virtual Path Indicator (VPI) information or IP source/destination addresses become corrupted, the errors are not identified by the error control mechanisms, and the corrupted routing information is valid for the access system so that the information ends up with the wrong user. TR 101 177 V1.1.1 (1998-05) 32 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.2.6 Radio specific security requirements | Because a radio access system may be subject to attempted interception of the "on-air" signals, a complete HIPERACCESS network may incorporate security systems designed to prevent fraud and protect the privacy of the customers', service providers' and operators' traffic. The following security features will be needed in the end to end network and the HIPERACCESS standard should be consistent with them: - the network management system should be able to manage all aspects of system security; - the security system should prevent unauthorized eavesdropping on customer communications and network management traffic; - systems should support the applicable requirements for legal interception [40]; - the HIPERACCESS standards shall not prevent security features from being removed from a system or set at a level appropriate to meet the requirements of any export regulations; - it shall be impossible to use a stolen or cloned network component in order to eavesdrop on network traffic or obtain service illegally from the network; - the AT installation process shall include a check that a "legal" AT is being attached to the network; and - it shall be possible for a security check to be performed periodically to check the validity of all ATs subscribed to the network. The need for HIPERACCESS systems to include any specific security features is for further study. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3 Operational requirements | This subclause presents requirements on HIPERACCESS systems based on broadband operators' likely service objectives and an analysis of critical factors affecting radio access network commercial viability, including the following: - subscriber-dependent factors such as population densities, principal applications required, user-traffic models and network penetration and growth; - environmental factors such as prevailing weather conditions, constraints on geographical coverage etc.; and - cost minimization/resource utilization factors such as installation and maintenance of equipment, frequency planning and management and bandwidth utilization. This is not intended to be a rigorous market analysis; for example we only divide users into residential and small business segments. The aim is rather to extract basic operational requirements on HIPERACCESS systems, for example, on system range, capacity, and coverage, to allow candidate technologies to be selected for HIPERACCESS. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.1 User density and market penetration | |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.1.1 Residential market | We can assume that the household is the unit that buys residential services (in other words there is one subscriber at most per household, though there may be more than one user in the household). We can derive the residential user density from the household density of the targeted deployment areas, given the targeted service penetration. Caution must be taken with figures for "average" household density, as local peaks may be much larger than the average for a large area. Table 5.4 gives figures for typical household densities in a square kilometre in Europe and the likely range of variations on a smaller scale. TR 101 177 V1.1.1 (1998-05) 33 Table 5.4: Typical household densities in Europe (Households per square km) Environment: Rural Suburban Urban City centre Average household density 1 000 3 000 Household density range 5 to 500 500 to 3 000 1 000 to 8 000 8 000 to 30 000 In rural areas HIPERACCESS may be rolled out by a single operator to provide full service to all customers, since the areas may not be attractive enough for competitive operators. Therefore HIPERACCESS should permit 100% penetration in these areas. In suburban areas HIPERACCESS should be able to support at least 50% penetration of the market, and in urban areas at least 30%. In dense city centre areas HIPERACCESS need only to be able to support at least 10% penetration. HIPERACCESS systems may be installed both in regions of relatively low household densities (rural areas) and regions with very high household densities (urban areas including city centres). At least in the early roll-out stages of a network, only a small fraction of the potential user base within the coverage area may subscribe, which will results in a low-to-medium user density in densely populated areas. HIPERACCESS systems must therefore allow economic deployment in areas with fairly low user density, but have adequate growth potential to maintain a good grade of service as the user density increases. In rural areas HIPERACCESS systems should target clustered households, such as villages, and not isolated houses. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.1.2 Business market | In a business a number of employees may use broadband services simultaneously through a single company subscription (probably sharing the access transceiver through an internal network). Little data seems to be available on the actual density of businesses. However data is available on the proportions of businesses across economies. Table 5.5 gives data for five EU countries. From the table it is clear that in each market: - approximately 2/3 to 3/4 of all telephone connections are to residences; and - 99% of all businesses employ less than 250 employees. Table 5.5: Market statistics for Europe Enterprises - % - with # of employees: Number of Country Households 000s Res. lines 000s Total lines 000s 1 to 9 10 to 49 50 to 249 250 + enterprises France 22 540 20 737 32 900 83,00 14,00 2,50 0,50 821 900 Germany 35 250 32 136 42 000 80,60 16,40 2,30 0,70 1 430 300 Italy 19 700 17 694 24 542 93,70 5,60 0,60 0,10 2 913 200 Spain 12 000 11 262 15 413 84,50 13,60 1,60 0,30 724 300 UK 22 300 20 739 30 678 79,70 16,60 3,00 0,70 826 600 These figures show that the predominant potential market for access will be for residential and small business premises, with the majority of business premises (at least 97% in fact) housing less than 50 employees. It is assumed that all businesses will also have telecommunications service. HIPERACCESS should be designed on the assumption that, in each type of region (rural, suburban, urban, city centre) it should support the same penetration of the SME customer base as the residential customer base. The density of SMEs is assumed to be in proportion to the household density as indicated by table 5.5. The number of users per subscription (i.e. per customer) will be distributed according to the distribution of enterprise size. However it is assumed that only half the employees in each enterprise will have access to broadband services (i.e. on average this is the proportion of employees who use communications in their daily work). TR 101 177 V1.1.1 (1998-05) 34 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.2 User reference traffic models | These traffic models are presented for the purposes of understanding the traffic mix and estimating spectrum requirement. They are thought to be reasonable projections or current trends but are not based on specific market research. NOTE: A subscriber means one connected via a HIPERACCESS network. Only households which require broadband services such as VoD and internet access will subscribe to such networks. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.2.1 Residential users | Each user may access a set of services through a HIPERACCESS system. A single household may have several people who may use the services simultaneously. Voice Telephony: Most subscriber households will use voice telephony. The working assumption for residential traffic intensity is 70 mE in the busy hour at 64 kbit/s duplex. ISDN: Most subscriber households will have ISDN access and these will also generate 70 mE in the busy hour at 128 kbit/s duplex (assuming that the D channel is interworked at layer 2 rather than layer 1). Video conferencing: It is assumed that 10% of HIPERACCESS households will use video conferencing (or similar residential services) also at 70 mE in the busy hour at 384 kbit/s duplex. Video on Demand: In UK the average household watches TV between 20 hours and 25 hours per week. Many households have more than one TV. At peak viewing time one third of the population is watching TV. It is assumed that 50% of subscriber households will use video on demand services. and of these on average each household will watch six hours of video per month. The downstream bit rates required for a VoD channel are between 1,5 Mbit/s and 6 Mbit/s depending on content - 3 Mbit/s average is assumed. Upstream traffic is assumed to be very low. Near VoD and Pay Per View: No additional allowance has been made for these services on the assumption that they will substitute for VoD. Internet Access: It is assumed that 80% of subscriber households will use internet access. From statistics gathered within a business environment an average internet user may download at an average rate of about 12 kbit/s in the busy hour, i.e. a total of about 5 Mbytes. This represents a low average utilization of a packet system at 25 Mbit/s. It is assumed that for future applications the utilization will be much higher: 1% in the busy hour. The upstream data would be smaller, typically "mouse-clicks", email and TCP acknowledgements, at 20% of the downstream rate. LAN access and interconnect: Presumably this will only be used by "homeworkers" and the small office home office (SoHo) market. It is assumed that 10% of subscriber customers fall in this category and that they utilize LANs for only 0,25% of the busy hour but while accessing they use high data rates. These figures are summarized in table 5.6. Table 5.6: Traffic model summary - residential (busy - hour) Services % HH Utilization Down (kbit/s) Up (kbit/s) Down tot (kbit/s) Up tot (kbit/s) Voice 80% 7% 64 64 0,4 0,4 ISDN 10% 7% 128 128 0,1 0,1 V.conf 10% 7% 384 384 0,3 0,3 VoD 50% 3,3% 3 000 0 50 0 Internet 80% 1% 25 000 5 000 200 40 Rem. LAN 10% 0,25% 25 000 25 000 6 6 Total 264 54 The "total" columns give an estimate of the mean upstream and downstream bandwidth per residential user (in kbit/s). These are the best estimates that could be made without formal market research. It is possible that traffic levels could be much higher in the longer term. The residential figures and business figures should not simply be added together as it is expected that busy hours do not correspond for the two categories. The data is intended to give guidance on the average values for channel bandwidth, not the maximum which a user may require. TR 101 177 V1.1.1 (1998-05) 35 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.2.2 Business users | In a small business the figures in the table 5.7 apply to the usage by each employee of the businesses of subclause 5.3.1.2 using telecommunications in their daily work. Voice Telephony: It is assumed that every business user of a HIPERACCESS network will use voice telephony. The working assumption for business user traffic intensity is 100 mE of external traffic in the busy hour at 64 kbit/s duplex. ISDN: It is assumed that 10% of business users of a HIPERACCESS network will have ISDN access and these will also generate 100 mE in the busy hour at 128 kbit/s duplex (assuming that the D channel is interworked at layer 2 rather than layer 1). Video conferencing: It is assumed that 10% of business users of a HIPERACCESS network will use video conferencing also at 100 mE in the busy hour at 384 kbit/s duplex. Video on Demand: VoD is not seen as an important application for business users. Internet Access: It is assumed that 100% of businesses will have Internet access. The utilization per employee is assumed to be the same inbound as in the residential case, and outbound rates more equal, as a significant number of businesses will have web servers on their premises. LAN access and interconnect: In the small business market, it is paradoxical that the proportion of remote LAN access will probably be about the same as the residential market. Businesses of the size which will be served by HIPERACCESS will not have too many remote workers since they are very small anyway. These figures are summarized in table 5.7. Table 5.7: Traffic model summary - business Service % employees Utilization Down kbit/s Up kbit/s Down tot. kbit/s Up tot. kbit/s Voice 50% 10% 64 64 3 3 ISDN 5% 10% 128 128 1 1 V.conf 5% 10% 384 384 2 2 VoD 0% 0% 3 000 0 0 0 Internet 50% 1% 25 000 5 000 125 250 Rem. LAN 5% 0,5% 25 000 25 000 6 6 Total 1 260 262 Service % businesses Utilization Down kbit/s Up kbit/s Down tot. kbit/s Up tot. kbit/s Web serving 25 80 5 000 25 000 1 000 5000 The "total" columns give an estimate of the mean upstream and downstream bandwidth per business user (in kbit/s). Again it should be emphasized that a number of users in a business may operate through one HIPERACCESS connection. The % employees column takes into account the factor of 50% of employees in each enterprise estimated to have access to broadband services . The separate summary for web serving uses percent of businesses with a web server, rather than percent of employees, since small and medium sized businesses tend to have one server, irrespective of the number of employees. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.3 Installation issues | Environmental concerns mean that HIPERACCESS antennas on customer premises must be small. As a target, the maximum size of the AT or repeater antenna should not exceed 0,45 m in any dimension irrespective of frequency; and the system design should assume that a pointing tolerance of no better than ± 2° may be achieved but desirable to be looser tolerance for ease of installation. System designs with electronically steerable antennas are interesting. Account should also be taken of the antenna deflection caused by wind. TR 101 177 V1.1.1 (1998-05) 36 Installation of customer premises equipment is not a negligible cost. The HIPERACCESS standards should allow a design to include any functionality necessary to enable the economical installation of subscriber equipment. For example, it should make available Received Signal Strength Indicator (RSSI)/Bit Error Ratio (BER) indications for optimum antenna alignment. Easy installation with a minimum of manual configuration should be the goal. Flexibility and an installation that is as automated as possible are highly desirable. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.4 Capacity | In an initial low-density deployment a single HIPERACCESS APT may serve an area of radius 5 km with a low user density. In this situation it is desirable for the single APT to support a reasonable number of users without artificial limits being imposed by, for example, AT addressing. Therefore the HIPERACCESS standard must allow one APT to support a logical minimum of 2 000 AT. One APT should be able to support a group of customers and ideally fully utilize at least one Synchronous Transmission Multiplex-1 (STM-1) connection to the core network (via the Access Point Controller (APC)) provided that this rate is feasible over a practical air interface. However it shall not be mandatory to connect through an STM-1 interface, and lower capacity interfaces are allowable where appropriate. To optimize functions such as handover and provide enough AP capacity a single APC must be able to manage a minimum of eight APTs. This would mean that the APC connection to the SNI would fill the capacity of two STM4 links. The HIPERACCESS system should support efficient frequency re-use and the protocol design should incorporate appropriate features to do this. Some fixed access systems today claim a re-use factor of one in a cellular deployment and HIPERACCESS should be at least as good. HIPERACCESS should be designed for maximum spectral efficiency, taking into account the trade-off between modulation efficiency and good frequency re-use. HIPERACCESS should support features to maximize the scalability of an installed system (i.e. the growth from coverage-limited to capacity-limited). The statistical multiplexing efficiency of the multiple-access scheme should be as high as possible. Features should be incorporated to allow system control parameters to be optimized for the traffic mix being encountered on individual APTs. For example, on a given site one sector may cover residential premises with a high usage of video on demand while another sector covers largely business premises with mainly LAN interconnection. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.5 Radio range and coverage | At frequencies above 10 GHz, heavy rain or snow may cause strong attenuation and unavailability events. Additional attenuation will be caused by atmospheric absorption by oxygen, hydroxyl ions, and fog. Additional margin should be allowed in the link budget in order to protect radio links from these events. A range requirement is stated here for the purposes of providing a reference point for link budget and should not be taken to prescribe the implementation. The HIPERACCESS PHY layer specification shall allow enough system gain to achieve a range of at least 5 km at 99,99% availability in LOS propagation conditions at the relevant frequency in ITU-R Recommendation PS 837-1 [17] climate zone E, with directional antennas meeting the requirements of subclause 5.3.3 above at the subscribers' premises and four sectored antennas at the base site. For the purposes of this specification availability is as defined in ITU-T Recommendation G.821 [22] (or its ITU-R Recommendation equivalent: ITU-R Recommendation F.697-2 for ISDN [16]). Network operators deploying HIPERACCESS in other environments should note that more or less planning margin may be needed to obtain the required availability. It should be possible to trade-off service bandwidth against range when deploying a HIPERACCESS system. At the microwave frequencies at which HIPERLAN will be deployed a line of sight is needed between network nodes. This is difficult to obtain in all circumstances especially in urban areas and a standardized repeater function is needed to optimize coverage at low cost. A HIPERACCESS system must be technically able, by using coverage overlap, repeaters or other techniques, to reach at least 95% of potential users in a coverage area, taking account of atmospheric attenuation. Table 5.8 shows the coverage improvement possible through the use of coverage overlap based on analysis of one area in the USA. TR 101 177 V1.1.1 (1998-05) 37 Table 5.8: Coverage achieved as a function of coverage area overlap Situation Probability of LOS Coverage No Overlap between coverage areas 0,50 to 0,60 Single Overlap 0,75 to 0,84 Double Overlap 0,875 to 0,936 NOTE: Assumptions are: coverage area radius = 5 km; APTs and ATs placed on building tops; probability of LOS = 0,60 for range < 2 km, 0,50 for range > 2 km. HIPERACCESS should incorporate features to cope with and exploit overlapping coverage. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.6 LOS deployment; Channel models | At low microwave frequencies, for example up to 4 GHz, there may be enough signal diffraction around obstacles to allow a significant number of customer locations to be served even though they do not have a LOS to the APT. At higher frequencies LOS is generally needed, but at short ranges an AT may still be able to operate even though the LOS is obstructed by quasi-opaque objects such as trees. In either case, if the LOS path is obstructed the relative amplitude of reflected paths will increase, and the system shall cope with multipath-induced effects including amplitude fading, intersymbol interference and "click" phenomena. Suitable channel models should be used in the design of the HIPERACCESS radio system. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.7 Maintaining QoS | The QoS objectives for fixed services are generally very stringent (for example availability of 99,99 %). A number of problems may arise during the operation of a network which effect the quality of the service delivered to an AT. - Load balancing between APTs may be needed. - The radio path between HIPERACCESS nodes may become obstructed, either temporarily or permanently. - Sporadic co-channel interference may arise from within the system or from another system. - Network equipment may fail. - As the network grows new APTs may be built to increase capacity or extend or "fill-in" coverage. HIPERACCESS shall incorporate system features to maintain the QoS in the face of these effects. Possible features include changing the connectivity of the radio segment ("handover") and dynamic channel allocation. These features may need to be applied on a short (e.g. within a call); medium (e.g. between calls); or long (e.g. from season to season) term basis. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.8 Frequency planning and management | Whilst coverage and capacity planning are expected to be essential for an operator to be able to manage QoS, frequency planning may not be essential if the system design can incorporate some features to self-manage frequencies (known generically as Dynamic Channel Assignment (DCA)). Also, the effectiveness of such features may depend on the type of service and the QoS targets of the operator. The range of possibilities for frequency planning in a HIPERACCESS system can be illustrated by the following simple scenarios. Operator A may provide broad-band services, in the form of permanent virtual circuits, to SMEs only and therefore does not require DCA; indeed DCA may not optimize the service quality for this type of link. Therefore operator A prefers to undertake such planning in a manner completely under his control. Operator B, however, provides a complex mix of broad-band services to mainly residential customers and therefore welcomes automatic DCA facilities. HIPERACCESS shall incorporate DCA but should also permit external optimization of frequency usage as appropriate. TR 101 177 V1.1.1 (1998-05) 38 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.9 General economic requirements | To optimize the economics of deploying a HIPERACCESS system the following requirements should be considered: - the cost of base station equipment should obviously be as low as possible; but in particular the cost of customer radio terminations should be minimized since a high proportion of mature system cost is likely to lie in these; - the AT should ideally be customer installable; - the system should, as far as possible, allow for graceful upgrade of capacity as customer numbers grow, without manual adjustment of the AT; - the system should incorporate features to minimize the need for any maintenance visits to the customer premises. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.10 Environmental conditions | HIPERACCESS networks are primarily intended to operate outdoors. The equipment must meet ETS 300 019 [7] class 4.1, and may have to meet other regional standards. Examples of the operating conditions include salt spray, humidity, temperature and wind loading. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.11 ElectroMagnetic Compatibility (EMC) | HIPERACCESS systems will conform to all applicable EMC standards. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.3.12 Standardization requirements | The HIPERACCESS standard shall include PHY and DLC layer specifications, and interworking functions to the UNIs and SNIs to be supported. Not all manufacturers may wish to manufacture interoperable equipment; and operators may not wish to procure interoperable equipment from different manufacturers. The PHY layer specification should therefore be produced in two parts. The "coexistence" specification will define, as a minimum, the spectrum mask, transmit power, receive sensitivity, and spurious emissions and responses. It may also include other aspects such as frequency sharing etiquette. The other part will include all other aspects of the PHY layer. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.4 Spectrum and regulatory issues | |
0265427df956e32eb1f8284408761815 | 101 177 | 5.4.1 Spectrum requirements | The potential market for HIPERACCESS equipment is very large - a significant proportion of households and small business premises in most countries. To achieve this market potential the production volumes must be very high, which can best be achieved by deployment of similar equipment operating at the same frequency in every country. It is therefore desirable that HIPERACCESS systems should be allocated at least one international dedicated band, sufficiently large and at an appropriate frequency, for mass deployment. However, it may take some time to obtain such a band, and therefore HIPERACCESS systems should be able to operate in other suitable fixed service bands. The coexistence part of the PHY layer specification should take this into account. Very high microwave frequencies are prone to severe atmospheric attenuation and the necessary device technology is also immature. The choice of frequency band should enable operators to meet availability, QoS and GoS requirements economically. |
0265427df956e32eb1f8284408761815 | 101 177 | 5.4.2 Operation in licence exempt bands | The HIPERACCESS standard, though intended primarily for use in licensed bands, may also be applied in licence-exempt bands which are shared with other services on an ad-hoc basis, provided that HIPERACCESS conforms to the sharing etiquettes for these bands. However, HIPERACCESS systems will not be deployed in the 5,15 GHz to 5,25 GHz band, in which HIPERLAN systems operate. TR 101 177 V1.1.1 (1998-05) 39 |
0265427df956e32eb1f8284408761815 | 101 177 | 5.4.3 Co-ordination | Whilst HIPERACCESS systems provide fixed access they have some operating and commercial characteristics in common with cellular mobile systems: - mass market; - high volume; - premium on capacity; - possibly rapid expansion of capacity to meet market demand. For these reasons the operator of a HIPERACCESS network will need the ability to deploy very rapidly, to vary capacity, and change the frequency plan (as far as applicable). Therefore it is important that a similar radio regulatory regime to mobile services is used - there should not be a need to involve the local administration in site co-ordination. This differs from common practice with fixed links. |
0265427df956e32eb1f8284408761815 | 101 177 | 6 Architecture | |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1 Reference models | There are two specific reference models applicable to HIPERACCESS members of the BRAN family: the General Reference Model (GRM) and the General Protocol Model (GPM). NOTE: Although the present document applies to HIPERACCESS systems, whatever core network they are connected to, it is intended that both of these reference models should align with the common reference model DTR/BRAN 040001 (see annex A) used to co-ordinate and align the work of the ATM Forum, and the ETSI BRAN Project, primarily addressing HIPERLAN systems. A common reference model may also be developed for IP systems. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1.1 GRM as applied to HIPERACCESS | Before we specify the GRM itself, (see subclause 6.1.2) , the model given here (figure 6.1) is of the GRM as might be applied to a general HIPERACCESS scenario. It is an example and does not constrain the actual implementation of any real system. TR 101 177 V1.1.1 (1998-05) 40 B.3 W.1 EMS RT B.1 TERMINALs W.1 W.1 W.1 W.1 W.1 W.1 W.1 W.1 W.3 W.2 W.2 W.2 W.2 W.2 ELEMENT MANAGEMENT SYSTEM IWF APT B.1 W.3 IWF RT/ RR APC RT/ RR W.3 IWF B.1 APT RR RT B.1 W.3 IWF RT B.1 W.3 IWF LOCAL NETWORKS ISDN ATM PSTN IP etc. IWF IWF IWF IWF IWF B.2 W.3 HIPERACCESS NETWORK IWF AT AP TE TE TE TE TE TE Figure 6.1: BRAN GRM as might be applied to HIPERACCESS The HIPERACCESS network, depicted in the enclosed part of the figure, provides a means of communication between a terminal (or terminals), typically on customers premises, and a switch or router, typically operated by a telecommunications operator and connected to one or more core networks. The HIPERACCESS network is a network element from an Operation Administration and Management(OA&M) viewpoint and should provide appropriate communication via interface B.3, to an external EMS which will be part of the operator's umbrella network management system. The telecommunications networks which may be accessed in this way include: - PSTN; - ATM networks; - ISDN; and - IP networks. In practice, some of these networks may be carried in others (such as IP over ATM) and further types of network may also be supported by adaptation over one of these. The BRAN comprises the following: - AP, which are the interface points to core networks. - APC which present network-specific interfaces to the core network via an InterWorking Functions (IWFs) which comply with a appropriate standards (e.g. V5 for PSTN, VB5 for ATM etc.). The APC also presents OA&M information from the entire radio access network to an external EMS. The APC may be physically distributed and the HIPERACCESS network may include more than one APC associated with a local network to provide a degree of fault tolerance and redundancy. The APC's principal function is to control the routing of traffic through the HIPERACCESS network, including optionally the provision of diverse routing between ATs and the core network to avoid congestion, faults, or (temporary) obstruction of LOS radio paths. Such alternative paths are indicated by broken lines in figure 6.1. The APC communicates with a number of APT via PP links (fibre, copper, microwave, etc.) which are not explicitly specified. - IWFs, which translate the internal (B.2) interface of the HIPERACCESS network into network specific interfaces of the external core network and translate the internal (B.1) interface of the HIPERACCESS network into external interfaces with terminal equipment. TR 101 177 V1.1.1 (1998-05) 41 - APT, distributed so as to be able to provide coverage throughout the service area of the BRAN. These communicate via the air interfaces (W.1) with Radio Terminations (RTs) and Radio Relays (RRs) or units which combine the functions of both RT and RR. - ATs. An AT comprises an RT and an IWF. It is normally located on or near customers premises, which communicate with the APT (possibly via one or more RR) and present fixed connections for customers' terminals. This connection (W.3) represents the network termination point: the demarcation between the operator's and the customers' responsibility. Multiple terminals may be connected to, and supported simultaneously by, one RT. The network may be designed so that each RT communicates via interface W.1 to a unique APT either directly or through a RR. - RTs are the radio parts of the ATs. - RR emulate one or more RTs as seen by the APT and emulate an APT as seen by a RT. The network may possibly allow RRs and if so may or may not allow cascading of RRs. RRs may support the direct connection of terminals - through interface W.3 - subject to the same considerations as for ATs. In this case they are denoted as RT/RR. A HIPERACCESS network may possibly allow communication between RTs of different customers without passing via an external switch. Should routing within the HIPERACCESS network be allowed, it would not then be handled by the switch but instead by the radio resource control and association control systems (see figure 6.4). This would allow some spectrum saving since an internal call would otherwise potentially occupy twice the bandwidth. However it represents a major change in access network functionality, conflicting with ITU-T Recommendation G.902 [24] and requires further study before such a feature could be supported. Radio paths implying routing within the HIPERACCESS network are shown dotted in figure 6.1. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1.2 HIPERACCESS GRM | The BRAN GRM for HIPERACCESS systems is shown in figure 6.2A. IWF AP Con- troller AP Trans- ceiver Core Network Radio Termi- nation IWF User Applic- ation W.1 B.2 B.1 W.3 W.3 Access Termination HIPERACCESS System Access Point B.3 User Terminal Figure 6.2A: BRAN GRM Figure 6.2B indicates that the HIPERACCESS specification is intended to be applied to equipment using any of several different radio frequency bands, and that it is advantageous to ensure that the frequency-dependent parts of the radio access subsystem should be confined as far as possible to parts of the system "close" to the air interface, W.1. AP Con- troller RT Radio Access Subystem Freq-dep. front-end Back- end Freq-dep. front-end Back- end B.1 B.2 APT W.1 Figure 6.2B: Optional mult-band split within RT TR 101 177 V1.1.1 (1998-05) 42 An optional interface may be defined between W.1 (the air interface) and W.3 (the user-network interface) which physically splits an installation between outdoor and indoor units. The presence of this physical split is useful in some circumstances. However such an interface is not specified at present. The model is intended to align with the ITU IMT2000 and ETSI UMTS models of the radio access network and identifies the following reference points: Reference point B.1: a service interface which is defined in terms of abstract services and parameters for the user, control and management planes of the HIPERACCESS air interface protocol stack. This interface is expected to be a common definition for HIPERACCESS systems which define interoperation via a common air interface and HIPERLAN/2. It may not actually exist, and is therefore not required to be present in any real implementation, but forms the basis for specification and testing. Reference point W.1: defines the radio interface between the APT and the radio termination. It is either a radio coexistence interface for all of the radio bands in which the HIPERACCESS network may operate or an interoperability interface that includes a radio coexistence interface and a standardized air interface. A radio relay may be supported at this interface (figure 6.3). AP Trans- ceiver Radio Termi- nation W.1 B.1 AP Con- troller B.2 Radio Relay W.1 Radio Access Subystem Figure 6.3 Radio relay at interface W.1 Reference point B.2: a service interface which is defined in terms of abstract services and parameters for the user, control and management planes of the HIPERACCESS air interface protocol stack. This interface is expected to be a common definition for HIPERACCESS systems which define interoperation via a common air interface and HIPERLAN/2. It may not actually exist, and is therefore not required to be present in any real implementation, but forms the basis for specification and testing. NOTE: The AP may be considered to comprise one or more APTs connected to a single APC. The interface between these two elements is not necessarily visible and is not specified. Reference points W.3 and W.2: the interfaces at W.3 and W.2 (W.2 on the network side and W.3 on the user side) are the supported standard interfaces to the relevant core networks and their related user interfaces. For any given core network, it is in principle possible to specify all of the relevant (W.3, W.2) pairs that BRAN systems support (see table 5.1). Non-standard W.3 and W.2 interfaces may be supported, but the BRAN family of interworking standards should not specify an interworking function for these cases. Reference point B.3: an interface over which are specified the mechanisms for communicating with the EMS, specific to the management of the radio access network. The BRAN protocol standards describe the mechanisms of the service interface at the B.1/B.2 reference point and the air interface at the W.1 reference point. Specifications of all other interfaces are outside the scope of the BRAN project. TR 101 177 V1.1.1 (1998-05) 43 |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1.3 GPM | The GPM for all HIPERACCESS systems is shown figure 6.4. Core Network Access Point Access Termination Radio Resource Control Association Control User Application User traffic Call Control Peer-to-peer communication Network stack R-PHY R-DLC IWF R-PHY R-DLC IWF Core network stack W.1 B.2 B.1 W.3 W.2 L M E L M E Radio Resource Control Association Control Access Point Control Access Point Control * Off-stack control * May be null if the network is not mobility-enhanced Application Figure 6.4: HIPERACCESS GPM The dark lines indicate call control flows, the dashed lines special protocols between the system elements, the grey band indicates user data flow. The thin arrowed black lines show the "off stack" control interfaces. The radio DLC layer contains two sublayers: a MAC sublayer and a Logical Link Control (LLC) sublayer. The MAC sublayer implements a service policy that takes into account such factors as channel quality, number of terminal devices and medium sharing with other access sub-networks. The LLC sublayer maintains the QoS on a virtual circuit basis. Depending on the type of service provided and channel quality, capacity and utilization, the LLC layer will implement a variety of means including Forward Error Correction (FEC), Automatic Repeat reQuest (ARQ) and flow pacing to optimize the service provided to the DLC user. NOTE 1: Within the ATM community, generic flow control is being discussed - this may impact the functionality of the DLC layer and its service definition. NOTE 2: Usage parameter control is an optional capability of ATM systems that may have impact on the specification of the radio DLC layer and on the AP behaviour. NOTE 3: The wireless DLC and PHY layers are intended to be generic enough to support the services of at least those networks listed in table 5.1 by providing appropriate connection types and service qualities. NOTE 4: The figure above (and figures 6.6 and 6.7) show an "Access Point Control" function in the core network. This may be provided in certain future core networks (e.g. UMTS) or may not be. When HIPERACCESS is behaving as a G.902 compliant network, the core network will not provide any radio resource management. TR 101 177 V1.1.1 (1998-05) 44 Radio relay support is shown in figure 6.5. Access Point Access Termination R-PHY R-DLC IWF R-PHY R-DLC IWF W.1 B.2 B.1 W.3 W.2 L M E L M E W.1 R-PHY L M E R-PHY R-DLC Radio Relay IWF User traffic Call Control Peer-to-peer communication Off-stack control Radio Resource Control Association Control Radio Resource Control Association Control Radio Resource Control Association Control R-DLC Figure 6.5: RR support NOTE: Figure 6.5 illustrates a RR router. Other types of RR are possible. A bridge differs only in that the call control and user traffic are connected between radio DLC blocks. A repeater differs only in that the call control and user traffic are connected between R-PHY blocks. An RR/RT configuration is also possible. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1.3.1 The GPM in an ATM environment | Applying the GPM in an ATM environment would result in figure 6.6. ATM Switch Wireless ATM Access Point Wireless ATM Access Termination Fixed ATM Terminal PHY ATM SAAL AAL-X Q.2931+M R-PHY R-DLC PHY ATM IWF R-PHY R-DLC PHY ATM IWF PHY ATM SAAL * May be null if the ATM switch is not mobility-enhanced R-CS R-CS L M E L M E W.1 B.2 B.1 W.3 W.2 Q.2931+M Access Point Control * Radio Resource Control Association Control Radio Resource Control Association Control Access Point Control User traffic Call Control Peer-to-peer communication Off-stack control Application Figure 6.6: HIPERACCESS GPM in an ATM environment TR 101 177 V1.1.1 (1998-05) 45 This model is equivalent to models used by the wireless group of the ATMF. Comparing this model to one of a wired ATM connection, the architecture presented above replaces the ATM PHY and part of the ATM layer with the two wireless layers that describe the wireless protocols: the radio DLC layer and the radio PHY layer. The radio DLC layer conserves the QoS of the each VPI/VCI "connection". In order to do this, it needs to know the VPI/VCI and other ATM cell header information. The ATM PHY does not need this information and therefore the standard ATM PHY SAP definition can not be used in this architecture to communicate with the radio DLC. On the other hand, the standard ATM PHY SAP must be included in the architecture to assure compatibility with existing systems. This modelling conundrum is solved by requiring the ATM interworking function to store this information on connection set-up and re-insert it at the radio DLC SAP (B.1 and B.2). The layer management entity of the radio DLC layer is used to convey QoS contract information and performance requirements between the radio DLC layer and the higher, connection control functions. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.1.3.2 The GPM in an IP environment | Applying the GPM in an IP environment would result in figure 6.7. Access Point Control * IP Network Wireless IP Access Point Wireless IP Access Termination Radio Resource Control Association Control Fixed IP Terminal PHY IP TCP, UDP ... R-PHY R-DLC PHY IP IWF R-PHY R-DLC PHY IP IWF PHY IP R-CS R-CS L M E L M E W.1 B.2 B.1 W.3 W.2 Radio Resource Control Association Control Access Point Control * May be null if the IP network is not mobility-enhanced User traffic Call Control Peer-to-peer communication Off-stack control Application Figure 6.7: HIPERACCESS GPM in an IP environment At the DLC SAP, one of the supported Service Data Units (SDUs) may be for an ATM cell, since IP packets will almost certainly need to be fragmented to a manageable size for the air interface. Support for alternative SDUs is not specified here, but may possibly also be included within the HIPERACCESS specifications. The support of a connectionless protocol such as IP over a DLC/PHY stack that also supports connection-oriented transport such as ATM creates several options on how this is to be done. The resolution of this issue is also left to the HIPERACCESS specifications. NOTE: The radio DLC shall support bandwidth reservation protocols in an IP environment (e.g. RSVP). |
0265427df956e32eb1f8284408761815 | 101 177 | 6.2 Interoperation | The HIPERACCESS family may contain members that support full interoperation at the air interface and those that do not. It is not a property of the HIPERACCESS family but of individual types of HIPERACCESS. TR 101 177 V1.1.1 (1998-05) 46 |
0265427df956e32eb1f8284408761815 | 101 177 | 6.2.1 General | Interoperation means the ability of any access termination built according to the standards to interoperate with any AP designed independently to the same standards, and provide defined services according to an "interoperation profile" specification. The interoperation profile defines the specific services and may possibly define the specific W.3 and W.2 interfaces essential to ensure interoperation. Not all permutations of W.2, W.3 and services will be standardized, or even be practical. Not all possible permutations of W.2 and W.3 will be provided on any specific HIPERACCESS equipment. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.2.2 Coexistence | If air interface interoperation is not supported, the only specification for that HIPERACCESS family member is the coexistence air interface specification. There is no need to specify any network interface support if the HIPERACCESS system only has to coexist at the radio interface with other HIPERACCESS systems of the same type. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.2.3 Air interface interoperation | When air interface interoperation is supported, then interface W.1 shall be fully specified. Support for interoperation of specified network interfaces (W.3 and W.2) may also be specified. Some services may be defined to work over all W.3 and B3 interfaces (e.g. POTS service should work with interoperating equipment however the AP controller and its IWF are connected to a core network). Support for air interface interoperation also implies that the service interfaces B.1 and B.2 are specified. B.1 and B.2 are specified at a logical level only, and specific implementations are a private matter for the manufacturer of the HIPERACCESS radio access system. This means that no interoperation is possible at the B.1 or B.2 interfaces. The manufacturer of a RT must therefore be entirely responsible for the interworking unit that connects any accessible, specified customer interface W.3 to the logical interface B.1. A similar case applies in the case of the IWF between B.2 and W.2. The specifications for B.1 and B.2 must be flexible to account for future developments in network architecture and interfacing. |
0265427df956e32eb1f8284408761815 | 101 177 | 6.2.4 Network and user interfaces | If a network or interface is listed in table 5.1, then an interworking function will be defined and a procurement specification may call for interworking at this interface. Table 5.1 does not constrain the implementation of HIPERACCESS systems, a manufacturer may choose to supply other interfaces (proprietary or standard) either for legacy interconnect or to support future developments. In this case the necessary standards will not exist to ensure interworking. NOTE: It is possible (and entirely permissible) that the W.3 interface could completely disappear in cases of access networks that communicate with, for example, integrated mobile terminals that contain a radio termination and a user application. The standard will not forbid such applications. This applies to the W.2 interface as well. In this case, the protocol models specified later may be collapsed to provide a single integrated protocol stack without a physically-accessible W.3 interface. The interfaces at W.2 and W.3 are themselves not explicitly specified by HIPERACCESS - they are the responsibility of other standardization bodies. Although the details of the HIPERACCESS W.2 and W.3 interfaces are not specified by the BRAN project, some new features of the interfaces and of the systems to which they connect may be required. For example, the AP Control function, if present in an ATM switch, may have to communicate with its counterpart in a HIPERACCESS system's AP, in order to support certain forms of mobility. It is up to the BRAN project to identify what additions are needed to support radio access, but the BRAN project must then persuade the appropriate body to create this support within its own specifications. The method by which this is done is to create agreed common reference models (e.g. the ATMF common reference model DTR/BRAN 040001 (see annex A). TR 101 177 V1.1.1 (1998-05) 47 Bibliography DTR/BRAN-040001: "Broadband Radio Access Networks (BRAN); Common ETSI - ATM Forum Reference Model for Wireless ATM Access systems". TR 101 177 V1.1.1 (1998-05) 48 History Document history V1.1.1 May 1998 Publication ISBN 2-7437-2199-5 Dépôt légal : May 1998 |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 1 Scope | To investigate radio and network aspects and clarifying the possibilities, problems and needs for new standardization related to advanced dual-mode terminals for DECT and GSM. The present document will identify the needed contents of the necessary standards that will form the basis for the second edition of Harmonized Standard EN 301 439 [18], i.e. dual-mode terminals that cannot be type approved according to existing TBRs and Harmonized Standards and that may operate in both modes at the same time or using only a single subscription. Basic dual-mode terminals, i.e. terminals consisting of one DECT part and one GSM part and that can be type approved according to existing TBRs and Harmonized Standards, were considered in another ETR (TR 101 072 [16]). The same consideration should be made for dual-mode terminals and infrastructure for DECT/DCS1800 as well as dual-mode/dual-band terminals DECT/GSM/DCS1800. The term GSM is considered to cover all the frequency bands, and combinations of frequency bands, allowed for GSM type equipments, i.e. P-GSM, E-GSM, R-GSM, DCS1800 or dual-band GSM/DCS. NOTE: A terminal comprising multiple GSM parts operating on different frequency bands is considered as a dual- band terminal. A terminal comprising both DECT and GSM parts is referred to as a dual-mode terminal. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 2 References | References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] EN 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 1: Overview". [2] EN 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 2: Physical layer (PHL)". [3] EN 300 175-3: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 3: Medium Access Control (MAC) layer". [4] EN 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer". [5] EN 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK) layer". [6] EN 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 6: Identities and addressing". [7] EN 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security features". [8] EN 300 175-8: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 8: Speech coding and transmission". TR 101 176 V1.1.1 (1998-04) 7 [9] ETS 300 370: "Digital Enhanced Cordless Telecommunications / Global System for Mobile communications (DECT/GSM) inter-working profile; Access and mapping (Protocol/procedure description for 3,1 kHz speech service)". [10] ETR 341: "Digital Enhanced Cordless Telecommunications / Global System for Mobile communications (DECT/GSM) Interworking Profile (IWP); Profile overview". [11] ETS 300 787: "Digital Enhanced Cordless Telecommunications / Global System for Mobile communications (DECT/GSM); Integrated Services Digital Network; DECT access to GSM via ISDN; General description of service requirements". [12] EN 300 444: "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)". [13] ETS 300 824: "Digital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)". [14] ETS 300 434-2: "Digital Enhanced Cordless Telecommunications (DECT); Integrated Services Digital Network (ISDN); DECT/ISDN interworking for end system configuration; Part 2: Access profile". [15] ETR 185: "Digital European Cordless Telecommunications (DECT); Data Services Profile (DSP); Profile overview". [16] TR 101 072: "Digital Enhanced Cordless Telecommunications/Global System for Mobile Communications (DECT/GSM); Integration based on dual-mode terminals". [17] EN 301 242: "Digital Enhanced Cordless Telecommunication (DECT); Global System for Mobile communications (GSM); DECT/GSM integration based on dual-mode terminals". [18] EN 301 439: "Digital European Cordless Telecommunications (DECT); Global System for Mobile communications (GSM); Attachment requirements for DECT/GSM Dual-Mode Terminal (DMT) equipment". [19] ETR 350: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms (GSM 01.04 version 5.0.1)". [20] GTS GSM 03.09: "Digital cellular telecommunications system (Phase 2+); Handover procedures (GSM 03.09 version 5.1.0)". [21] ETS 300 930: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode (GSM 03.22 version 5.2.1)". [22] ETR 366: "Digital cellular telecommunications system (Phase 2+); Multiband operation of GSM/DCS 1800 by a single operator (GSM 03.26 version 5.1.0)". [23] ETS 300 940: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface; Layer 3 specification (GSM 04.08 version 5.6.3)". [24] ETS 300 921: "Digital cellular telecommunications system; Service accessibility (GSM 02.11 version 5.0.1)". [25] TBR 6: "Digital Enhanced Cordless Telecommunications (DECT); General terminal attachment requirements". [26] TBR 10: "Digital Enhanced Cordless Telecommunications (DECT); General terminal attachment requirements; Telephony applications". [27] TBR 19: "European digital cellular telecommunications system (Phase 2); Attachment requirements for Global System for Mobile communications (GSM) mobile stations; Access". [28] TBR 20: "European digital cellular telecommunications system (Phase 2); Attachment requirements for Global System for Mobile communications (GSM) mobile stations; Telephony". TR 101 176 V1.1.1 (1998-04) 8 [29] TBR 22: "Digital Enhanced Cordless Telecommunications (DECT); Attachment requirements for terminal equipment for DECT; Generic Access Profile (GAP) applications". [30] TBR 31: "Digital cellular telecommunications system (Phase 2); Attachment requirements for mobile stations in the DCS 1 800 band and additional GSM 900 band; Access". [31] TBR 32: "Digital cellular telecommunications system (Phase 2); Attachment requirements for mobile stations in the DCS 1 800 band and additional GSM 900 band; Telephony". [32] TBR 36: "Digital Enhanced Cordless Telecommunications (DECT); Global System for Mobile communications (GSM); DECT access to GSM Public Land Mobile Network (PLMNs) for 3.1 kHz speech applications". [33] EN 301 440: "Digital Enhanced Cordless Telecommunications (DECT); Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment for DECT/ISDN interworking profile applications". |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 3 Definitions, symbols and abbreviations | |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 3.1 Definitions | For the purposes of the present document, the following definitions apply: active communication: A state, where a communication link has been established between the DMT and a fixed part in either GSM or DECT mode. NOTE 1: When the DMT is in active communication in a mode, it has left the idle state of that mode. active mode: GSM or DECT mode after being selected and switch on procedures for that mode being performed. NOTE 2: For GIP/GSM DMTs, registration is not performed in both modes. background scanning: The process whereby a basic DMT attempts to identify the existence of stable networks in the mode other than the one it is in to which the terminal has access rights. basic dual-mode terminal: A DMT that can only be in one mode at the time and that can be switched either manually or automatically between modes. The basic DMT is always in one mode. cell (DECT): The domain served by a single antenna(e) system (including a leaky feeder) of one fixed part. NOTE 3: A cell may include more than one source of radiated Radio Frequency (RF) energy (i.e. more than one radio end point). call (DECT): All of the layer 3 processes involved in one layer 3 peer-to-peer association. dual-band terminal: A terminal comprising multiple GSM parts operating on different frequency bands. For example a terminal comprising of GSM and DCS1800 parts. Dual-Mode Mobile Station (DMS): A GIP/GSM DMT that operates using only a GSM subscription. Dual-Mode Terminal (DMT): A terminal comprising both DECT and GSM parts. Fixed Part (DECT Fixed Part) (FP): A physical grouping that contains all of the elements in the DECT network between the local network and the DECT air interface. GAP/GSM DMT: A dual-mode terminal where the DECT part is compliant with any DECT profile(s) except the DECT/GSM InterWorking Profile. GIP/GSM DMT: A dual-mode terminal where the DECT part is at least compliant with the DECT/GSM InterWorking Profile. TR 101 176 V1.1.1 (1998-04) 9 GSM: In the present document, the GSM part of a DMT can be GSM 900, Digital Cellular System 1800 (DCS 1800) or GSM/DCS dual-band. GSM coverage: The sum of all GSM Public Land Mobile Network (PLMN) coverages where the DMT has at least limited service. mode selection: A DMT based procedure, whereby operating mode, GSM or DECT, is chosen. NOTE 4: Mode selection only applies for type 2 DMTs, type 3, 4, and 5 DMTs operate in both modes. mode: A basic DMT is in either of the two modes GSM and DECT. In GSM mode the DMT behaves as a GSM Mobile Station (MS) and in DECT mode the DMT behaves as a DECT Portable Part (PP). NOTE 5: More advanced DMTs can be active in both modes. The grade of service available in the two modes depend on the terminal type. Portable Part (PP) (DECT Portable Part): A physical grouping that contains all elements between the user and the DECT air interface. PP is a generic term that may describe one or several physical pieces. PLMN selection: A GSM procedure defined in [21] where the DMT identifies and selects the PLMN to which it may register. NOTE 6: For GIP/GSM DMTs, both radio interfaces may be involved in the PLMN selection. Radio Fixed Part (RFP): One physical sub-group of a fixed part that contains all the radio end points (one or more) that are connected to a single system of antennas. NOTE 7: Specific GSM abbreviations may be found in ETR 350 [19]. Specific DECT definitions and abbreviations are found in EN 300 175-1 [1]. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARI Access Rights Identifier CAP CTM Access Profile CTM Cordless Terminal Mobility DAM DECT Authentication Module DECT Digital Enhanced Cordless Telecommunications DMS Dual-Mode Mobile Station DMT Dual-Mode Terminal ETR ETSI Technical Report ETS European Telecommunication Standard ETSI European Telecommunications Standards Institute FP Fixed Part FT Fixed Termination GAP Generic Access Profile GIP DECT/GSM Interworking Profile IMEI International Mobile Equipment Identity IPEI International Portable Equipment Identity IPUI International Portable User Identity ISDN Integrated Services Digital Network LAI Local Area Identifier LE Local Exchange MMI Man Machine Interface MSC Mobile Switching Centre PABX Private Automatic Bransch Exchange PBX Private Bransch Exchange PLMN Public Land Mobile Network PP Portable Part PSTN Public Switched Telephone Network PT Portable Termination TR 101 176 V1.1.1 (1998-04) 10 RES Radio Equipment and Systems RFP Radio Fixed Part SIM Subscriber Identity Module SMS Short Message Service TBR Technical Basis for Regulation |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4 Reference configurations and scenarios | |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.1 Terminal Configurations | A Dual-Mode Terminal (DMT) for DECT and GSM is considered to be a terminal with one GSM part and one DECT part that is controlled by a common Interworking Unit which also controls one common MMI (keypad, display and menu functions). A reference configuration for dual-mode terminals is shown in figure 1. Interworking MMI D E C T G S M Figure 1: Reference configuration for DMT Some parts in the terminal, such as microphone and loudspeaker, could be reused by both the GSM and DECT parts or could be implemented in two ways. Integration of the RF parts is also foreseen. The exact functionality of the interworking function will depend on the terminal configuration. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.1.1 Terminal states | A DMT can operate in two modes: DECT and/or GSM. In each mode the terminal can be in different states of operations at a lower layer (MAC layer for DECT and RR layer for GSM). |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.1.1.1 DECT Terminal states | The DECT mode of a DMT behaves as a DECT Portable Part (PP). A PP can exist in one of the following MAC layer states (see EN 300 175-3 [3], subclause 4.3.1). 1) Active_Locked: where the PP is synchronized to at least one RFP transmission and has one or more connections in progress. 2) Idle_Locked: where the PP is synchronized to at least one RFP transmission. It is able to make or receive connections, but has no connections in progress. 3) Active_Unlocked: where the PP is not synchronized to any RFP transmissions, and is unable to make or receive connections. The PP makes occasional attempts to detect a suitable RFP and enter the Idle_Locked state. 4) Idle_Unlocked: the PP is not synchronized to any RFP and does not attempt to detect RFPs. TR 101 176 V1.1.1 (1998-04) 11 Idle Locked Active Unlocked Idle Unlocked Active Locked "sw itch off" "sw itch on" no suitable R FP found suitable R FP first bearer established last bearer released Figure 2: DECT mode state diagram (see EN 300 175-3 [3]) The DECT idle unlocked state corresponds to the GSM idle state. NOTE: Compared to the GSM case, a DECT PP can go to the switched off state via the active state (e.g. in the GIP and CAP cases) but also directly from the idle state (as e.g. in the GAP case). TR 101 176 V1.1.1 (1998-04) 12 |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.1.1.2 GSM Terminal states | A switched on DMT in GSM mode can be in either idle state or active state at the RR layer [23]: Switched off Sw itched off Switched on Idle Active RR release R R im m ediate assignm ent 1) Idle state: where the MS is switched on and is in GSM idle mode but is not in active communication. 2) Active state: where the MS has initiated an RR immediate assignment and left the idle state. NOTE: The idle state here should not be mixed with the idle mode. In GSM idle mode, the following steps are covered that corresponds to the DECT finding of suitable RFP: PLMN selection , Cell selection/re- selection (identification of suitable, or any, cell), Camping (tuning to the BCCH of the selected cell) and Location registration (for those services that requests registration). Figure 3: GSM mode state diagram (based on the description in ETS 300 940 [23]) |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.2 Specific terminal configurations | Five general terminal configurations have been identified in TR 101 072 [16]. These are denoted types 1-5. The type 3 terminal where subdivided into type 3a and type 3b. The different terminal types are described in the following subclauses. Table 1: Summary of terminal types Number Description type 1 single active mode - manual switch type 2 single active mode - automatic scan (manual or automatic switch) type 3 dual idle mode (double registration, listen in both modes) type 3a simultaneous receive (two transceivers) type 3b time multiplexed receive (one transceiver) type 4 single transmit - dual receive (listen to one radio interface even when active on the other) type 5 dual active mode (simultaneous transmit/receive in both modes) Terminal types 1 and 2 where analysed in TR 101 072 [16] and the basis for automatic background scanning and automatic switching between modes (type 2 DMTs) where given in EN 301 242 [17]. The present document covers the terminal types 3-5 and develops further on single-subscription type 2 DMTs. TR 101 176 V1.1.1 (1998-04) 13 |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.3 Subscription configurations | A dual-mode terminal may contain different subscriptions related to each radio interface or could have a single subscription which could be used in both the DECT and the GSM air interface. The same subscription configurations as for basic DMTs applies here. Two different types must be distinguished in the context of advanced dual-mode terminals: - single subscription operation where the GSM identity is used to access GSM service also in DECT mode (i.e. the DECT part is GIP compliant); - multiple subscription operation where the DECT part uses other DECT profile(s) than GIP and at least one DECT subscription in addition to the GSM subscription. (This type of operation also covers the theoretical possibility to use the IPUI-R, containing the IMSI, to connect to other telephony networks than GSM PLMN using another DECT profile than GIP. It also covers the case were both GIP and other DECT profiles are used in the DECT part). NOTE: Since the GIP is GAP compatible, a GIP portable (and a GIP/GSM DMT) may use both a DECT and a GSM identity depending on which it operates according to (i.e. depending in which environment it is active). A DMT where the DECT part is compliant with at least the DECT/GSM Interworking Profile is sometimes called a GIP/GSM DMT while DMTs based on other DECT profiles than GIP sometimes are generically called GAP/GSM DMTs. A GIP/GSM DMT that operates only on a single subscription (the GSM subscription), i.e. the DECT part is based only on GIP, will be called a Dual-Mode Mobile Station (DMS). Basic dual-mode terminals were considered in EN 301 242 [17] for the cases where the DECT part is compliant with the Generic Access Profile, EN 300 444 [12], the CTM Access Profile, ETS 300 824 [13] or the ISDN Access Profile, ETS 300 434-2 [14]. The present document elaborates further on the single subscription operation of types 2-5 DMTs where the DECT part is compliant with the DECT/GSM Interworking Profile, ETR 341 [10] and on multiple subscription operation of DMTs based on types 3-5 DMTs where the DECT part is compliant with other DECT profiles than GIP (possibly in addition to GIP in which case also type 2 DMTs are covered). |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.4 Network configurations | |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.4.1 GIP/GSM | For the first phase of dual-mode standardization (see TR 101 072 [16]), it was assumed that the portable supports at least basic speech services. For the GIP/GSM case, the connection between DECT access network and PLMN network could be either via an A interface, ETS 300 370 [9] or via an ISDN interface, ETS 300 787 [11]. Support of other (non basic-speech) GSM services is considered in this report. Clearly when additional services are added they must be supported within the networks. Currently support for SMS and other GSM services is only defined for the A interface. Plans exist for implementing support for all GSM services also on the ISDN interface. Plans for enhancements of the DECT/GSM Interworking Profile with respects to enhanced bearer services and interworking to GSM phase 2+ services HSCSD and GPRS exists. TR 101 176 V1.1.1 (1998-04) 14 GPRS GSM A DSS1+ Gb GSM BSS G IP FP D ECT FP D ECT FP GSM BSS G SM M SC GPRS SG SN D M T D M T GSM ph 2 basic speech G SM ph 2+ Figure 4: Some examples of network configurations related to GIP/GSM dual-mode terminals |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.4.2 GAP/GSM | For the cases where the DECT part of the DMT is not using GIP, several network configurations can be identified, e.g.: - a DECT FP in a private system can be connected to both the PABX and data network, e.g. a LAN; - a residential DECT FP can be connected to a local exchange in the public network; - a DECT FP can be connected to both private and public CTM networks. LE D M T speech D M T PABX LAN LE PINX D M T G SM M SC C AP FP C TM ph 2 G SM BSS G AP/IAP FP G AP/D SP FP speech & data G SM ph 2+ Figure 5: Some examples of network configurations related to GAP/GSM dual-mode terminals TR 101 176 V1.1.1 (1998-04) 15 |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.5 Service scenarios | In addition to the service scenarios identified for basic dual-mode terminals (see TR 101 072 [16]), i.e. speech service on both GSM and DECT radio interfaces, the examples in this subclause are relevant for advanced GAP/GSM DMTs. NOTE: The service scenario for GIP/GSM DMTs is covered mainly in clause 6. Two main applications are identified for double location registered terminals: - to be reachable on both fixed and mobile telephone numbers at the same time; - multiple service execution (e.g. simultaneous speech and data). |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.5.1 Simultaneous speech calls | For example, while in the office, the DMT is simultaneously registered via a GSM radio interface to a GSM PLMN and via a DECT radio interface to an Access Rights Identifier (ARI) B network. In the home environment the scenario is the same and DMT is registered in both a GSM PLMN and an ARI A RFP. The DMT is simultaneously reachable on both the PSTN and the GSM numbers. A type 3 or 4 DMT will be active in a call only on one radio interface at the time. It listens for incoming calls on both radio interfaces but can only answer one at the time. A type 5 DMT can be active in calls on both radio interfaces at the same time. Support of a conference call involving both modes may not be possible but a terminal based call completion (call waiting/call hold) feature would be possible and could have the same user interface as the corresponding network based services. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.5.2 speech + data | When active in data call in one mode, a double location registered DMT of type 4 or 5 could be reachable also for incoming speech calls in the other mode. A type 5 DMT could be considered to operate a data call on one radio interface and one speech call on the other radio interface. It is believed that the data call would then most likely be on the DECT link. The DECT part of the DMT would then have to support one DECT data profile [15] in addition to GAP. In the future there may even be multi mode terminals optimized for data services that only supports a data profile on the DECT part. DECT data profiles and DECT/GSM specific enhanced bearer services may also be considered to be implemented in type 1-3 DMTs but for these type there are no aspects of simultaneous service execution to consider. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.5.3 speech/data + SMS | Double location registered DMTs (i.e type 3-5) are able to send and receive SMS over both radio interfaces in the same way as they are able to initiate and receive speech and data calls over both radio interfaces. (For the DECT part the SMS capability depends on which profile the DECT part is based on.) Only a DMT type 5 is able to handle SMS PTP in one mode while being in active communication in the other mode. The delivery of an SMS to type 3 and 4 DMTs would be delayed in one mode until the communication in the other mode is completed. A type 4 DMT can receive SMS CB in one mode even when it is in active communication in the other mode. Table 2: SMS capability in one mode of a double location registered DMT depending on activity in the other mode Activity in the other mode DMT type idle active type 3 yes no type 4 yes CB only type 5 yes yes For GAP/GSM DMTs used for single number applications there is a need for the user to always receive GSM short messages. Since DECT access networks cannot necessarily deliver SMSs, the only way to guarantee that SMSs are TR 101 176 V1.1.1 (1998-04) 16 delivered to the DMT is that the DMT can receive a SMS over the GSM radio interface even when the DMTs is locked to a DECT system. A DMT type 5 meets this requirement. A type 3 or 4 DMT is probably sufficient from the users point of view since it would receive an incoming SMS rather soon after a DECT call is completed. NOTE: Repetition of paging for SMS is network dependent. In case the continuous SMS reception is to implemented without having the missed pagings problem of type 3 and 4 DMT, a few options exist: 1) a type 2 DMT could be set to change mode regularly to check for eventual incoming SMS. E.g. the DMT could leave DECT mode once every 15 minutes and go into GSM mode for a minute or so and then go back into DECT mode. This behaviour would not make more harm to networks than what is already allowed for type 2 DMTs (see EN 301 242 [17]); 2) a type 3 DMT could be set to be reachable only for GSM SMS when in DECT coverage. It would then be reachable for incoming telephone calls only from one system at the time in the same way as a type 2 DMT. When in GSM mode and a DECT scanning has identified a suitable DECT network, the DMT would activate the Call Forwarding Unconditional SS (for all services but SMS) and lock to the DECT system. When leaving the DECT coverage the DMT would just deactivate the CFU service. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 4.5.4 speech/data + supplementary service transaction | DMTs that are registered in two networks simultaneously (i.e. types 3-5), could be expected to perform a supplementary service transaction, or other signalling, in one mode even when being active in a call (speech or data) in the other mode. Only a type 5 DMT can meet this requirement. Type 3 and 4 DMTs would fail to do this in the same way as they would fail to receive a second incoming call. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5 Double location registered terminals | Type 3, 4 and 5 DMTs are here analysed in the same way as type 1 and 2 DMTs were in TR 101 072 [16]. As a terminal of type 3, 4 and 5 can be simultaneously registered in both systems, the GSM and DECT specifications should be simultaneously met to an extent that needs to be defined. Due to the different capabilities of the three terminals types, there have to be different requirements for each type of terminal. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.1 General on testing issues | The basic principle for type testing of advanced dual-mode terminals should be that all relevant TBRs and Harmonized Standards apply simultaneously, and that the terminals need to comply to all those TBR and Harmonized Standard requirements. It is, however, obvious that it may be physically impossible to fulfil them all. If, for instance, the transmitters in both modes are transmitting at the same time, the DECT uplink signal would have to be regarded as an unwanted radiation (not fulfilling the requirements) in the GSM specification, and vice versa. There need therefore to be exceptions or replacements to the existing requirements. If not all requirements can be fulfilled, at least the general principle must be that all the primary requirements (meaning the requirements which directly degrade/influence the effectivity of the networks or/and the effective use of the RF spectrum and the requirements which have direct influence on the terminal behaviour as seen from the user) shall be fulfilled. The secondary requirements (meaning requirements which only in very special scenarios, and only with small probabilities degrade the network, the use of the spectrum, or the terminal behaviour) must be fulfilled to a reasonable extent. In this case the principle must be that the most relaxed of the specifications applied simultaneously applies. Therefore the primary and secondary requirements must be identified: TR 101 176 V1.1.1 (1998-04) 17 Primary requirements: - sensitivity; - pageability; - unwanted radiation in the GSM/DCS 1800 receive band; - immunity to in band interference; - transmit power; - transmitter modulation parameters; - timing parameters; - spurious response rejection/blocking including 3rd order (out of band) intermodulation phenomina. Secondary requirements: - unwanted radiations (out of band); - transmitter intermodulation products. The requirements regarding unwanted transmitter emissions in the GSM/DCS 1800 receive bands are very severe. There is no reason that a DECT transmitter should not fulfil the GSM requirements, but there may be problems about the DCS 1800 requirements because the DECT band is very close to the DCS 1800 receive band. All such cases must be described in a separate standard, which must then serve as the basis for a TBR or Harmonized Standard together with the relevant standards for DECT and GSM family terminals. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2 DMT of type 3 and 4 | DMTs of type 3 and 4 can be simultaneously location registered via different radio interfaces but cannot be in active communication in both modes at the same time. When registered in two networks simultaneously (one PLMN and one ARI A, B or C network) the terminal is listening on both radio interfaces at the same time. Location registration procedures work independently and are controlled by the handset. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.1 Idle mode issues | For a type 3 (particularly type 3b) there is a potential loss of idle mode performance compared with single mode terminals, e.g. due to parallel reception or processing in the two modes, which may result in: - loss of paging messages; - reduced update rate of broadcast information; - delayed cell re-selection; - delayed cell selection; - delayed location update. It is desirable that idle mode performance is not degraded. However this may not be practical. If so, the maximum acceptable level of degradation of each of the parameters given needs to be defined. This is an area where new requirements need to be set. A type 4 DMT will likely not have these idle mode problems. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.1.1 Missed pagings | Pagings being missed by the DMT will force networks to take actions as if the terminal is not reachable even if it is generally present. Pagings on one radio interface may be missed in certain situations: TR 101 176 V1.1.1 (1998-04) 18 a) when scanning the other radio interface. This situation is relevant for type 3b DMTs. This could be reduced by intelligent scanning i. e. not scanning when expecting a paging on the other interface; b) when expecting paging at the same time on both radio interfaces. It could be decided that systematic priority is given to one air interface in this case, e.g. GSM, or to rely on repeated pagings to reach the terminal (this will be the case on the second interface, when the first has priority). The probability of such collisions is expected to be very low; c) when in active communication on the other interface. When the terminal is in active communication on one radio interface, the other radio interface is blocked. Attach/detach procedures could be used for long periods of active communications such as calls but probably not for short periods of active communications such as location updating or supplementary services. The impact of the time taken to perform detach and attach procedures needs to be considered. If the signalling load is considered too high it could be decided to forbid the use of attach/detach procedures in such cases. The consequence of the above considerations, is that for type 3 and 4 DMTs, the pageability is degraded. This degradation ought to be limited: - in case a) and b), an upper limit for the pagings allowed to get lost should be set. This upper limit has to take into account operators needs as well as manufacturers possibilities; - for b) and c), extra specification of the DMT is necessary if some behaviour is unwanted or if another is preferred. NOTE: In GAP there is no detach procedure. GSM networks indicate if attach/detach procedures are allowed or not by a broadcast parameter. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.1.2 Automatic network selection | A type 3 and 4 DMT that is double location registered does not switch between the modes, both are active at the same time. It may, though, still be advantageous to say that one of the two active modes is the preferred mode. This would mean the mode in which network selection is performed first and where outgoing calls are set up. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.1.3 Location registration | Considerations of how many subscriptions that are simultaneously active in a DMT are made in TR 101 072 [16]. For DMT type 3 and 4 normally 2 subscriptions, one DECT and one PLMN, will be active at the same time. This could cause problems to the networks as they have no information on whether a DMT is simultaneously registered in another network. These problems are expected to be solved by the operators, e.g. by some intelligent network architecture. A special situation is a GIP/GSM DMT where a single subscription is used to access a PLMN both via DECT and GSM air interfaces. Simultaneous location registration attempts via both radio interfaces must here be avoided, as each location registration on one air interface overrules the previous registration on the other radio interface. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.2 Active mode issues | When a DMT type 3 and 4 is in active communication in one mode, there is the same loss of idle mode performance in the other mode as described in subclause 5.2.1. When the type 3 DMT is in active communication (e.g. channel request, call, mobility management operation) on one radio interface, it is not able to receive on the second radio interface. This means e.g. that when the DMT is active in one mode, pagings will be missed in the other mode and the DMT will appear as if it was out of coverage (not reachable) in the other mode. During a call, the synchronization or coverage of the network in the other mode may be lost and a new network may be found after the call is completed. When the type 4 DMT is in active communication on one radio interface, it is able to receive on the second radio interface. This means e.g. that when the DMT is active in one mode, pagings will be received in the other mode but the DMT may not be able to take any action and may thus also appear to be out of coverage in the other mode. During a call, the synchronization of the network in the other mode is kept and broadcasted information and SMS CB is received. It could be possible for a type 4 DMT to suspend the active service while answering the paging in the other mode and then try to resume the first connection after the call in the second mode is completed (e.g. reception of a SMS). It is TR 101 176 V1.1.1 (1998-04) 19 probably not possible for the DMT to switch the transmitter between the modes and thus achieve a terminal based call waiting/hold feature. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.3 Call forwarding for a one number service | Type 3 and 4 DMTs have no major advantage or drawbacks compared to type 2 DMTs for access to one number services. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.2.4 Principles for type approval of type 3 and 4 DMTs | The new requirements for type 3 and 4 DMTs are different from those for type 2 DMTs (see EN 301 242 [17]). Special concern has to be put on finding the acceptable levels of degradation related to idle mode issues and non reachability in one mode when active in the other. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3 DMT of type 5 | A type 5 DMT is able to be in active communication in both modes at the same time. The advantages of this type of terminal are: - implementation of a terminal based call hold/waiting feature is possible; - reception of GSM SMS while the DMT is in active communication in DECT mode is possible; - running a data call in one mode and a speech call in the other mode at the same time is possible. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.1 Spectrum protection | |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.1.1 Intermodulation interference | Calculations indicate that there are no 1st - 3rd order intermodulation interference between GSM+DCS and the basic DECT band. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.1.2 Adjacent channel interference | The radio problem for dual active mode terminals is about the adjacent channel interference from DECT to DCS - the DCS receiver may be blocked due to a DECT transmission. (Since the upper DCS band is downlink, there is no interference from DCS to DECT.) To overcome this problem, two solutions were identified: 1) no degradation is accepted - good enough attenuation by, e.g. additional isolators and filters, has to be built (may take considerable time to realize and certainly costs). The guard band between the 1 880,928 MHz (lower DECT) and 1 879,9 MHz (upper DCS 1800) does not give sufficient attenuation. The minimum attenuation from DECT Tx to DCS 1 800 Rx is 64 dB, see figure 6; 2) some kind of degradation is accepted: the DCS sensitivity level can be decreased or, preferably, reduced DECT output power can be used in the lowest DECT frequency channel. A reduction of the power from 24 dBm to 10 dBm in the lowest channel, correspondingly reduce the minimum attenuation from 64 to 50 dB. TR 101 176 V1.1.1 (1998-04) 20 1880 MH z 1882 MH z Figure 6: Transmitted DECT spectrum for channel 9 (power 24 dBm) and the three upper DSC1800 receive channels (sensitivity level -100 dBm). NOTE The maximum interference power for the highest DCS1800 channels is indicated by a dashed line. The minimum additional attenuation is given by the difference between this level and the DECT output power spectrum |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.1.3 Blocking requirements | An interesting idea that would enable an early software radio realization of dual-mode terminals is to harmonize the blocking levels requirements so that the DCS value (-25 dBm) applies also for the GSM part (otherwise -13 dBm). Hence, the 12 dB dynamic range reduction, corresponding to 2 bits in a software dual-band/dual-mode ADC, is promising for this implementation. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.2 Protection of network | |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.2.1 Sensitivity | Most of the issues in subclause 5.2 applies to the protection of network. Two of the main parameters is probably the sensitivity and blocking. When the advanced dual-mode terminal is in active communication in both modes, the two transmitters are active at the same time, and both receivers must fulfil the sensitivity requirements at the same time. As the operators are depending on the sensitivity in their cell planning and link budgets, it seems reasonable to maintain the receiver sensitivity requirements also for an advanced dual-mode terminal. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.2.2 Network selection | A major subject relevant for the protection of the networks is the network selection behaviour of the terminal - an issue similar to the type 2 and 3 or 4 terminal. Even if a type 5 DMT is registered in two networks simultaneously, and thus does not need to switch mode, it is important that correct networks are selected so that there is no excessive switching between available networks. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.2.3 Missed pagings | For DMT type 5 will not miss pagings. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.3.3 Principles for type approval of type 5 DMTs | The simplest approach for type 5 DMTs is to say that they should comply with both GSM and DECT specifications even when they are in active communication in both modes. Some concern is needed for the formulation of test cases. A level with weaker requirements would be to say that both GSM and DECT specifications should be met when both modes are in idle mode but that some decreased sensitivity is accepted in one mode when the DMT is in active TR 101 176 V1.1.1 (1998-04) 21 communication in the other mode. From a network operators cell planing point of view, it is though reasonable to maintain the receiver sensitivity requirements. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.4 Telephony requirements | There are no other issues related to speech requirements for advanced DMTs than already handled for basic DMTs [18]. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 5.5 Handover between DECT and GSM | This subclause covers aspects of handover between DECT and GSM systems for DECT systems that are not directly connected to GSM networks. (i.e. the DECT systems are not GIP systems. GIP/GSM handover is covered in clause 6.) The DECT FP is considered to be connected to an exchange, a public Local Exchange (LE) or a private PABX, as illustrated in figure 7. LE PABX FP MSC BSS 1 1 2 2 D M T Figure 7: Reference configuration for DECT/GSM handover. The DECT FP is connected to a public LE or to a private PABX which in turn can be connected to an LE or to an MSC Handover between DECT and GSM in this case requires procedures for handing over calls between two networks. A fully efficient automatic procedure requires that a common control node for the two networks is defined and that procedures are specified for handing over of the connection between exchanges. No standard for inter-network handover is available at the moment. The generic handover mechanism intended for UMTS could be used for the DECT/GSM handover when available. For early implementations, a simple procedure based on third party connections could be possible. For DMT types 1-3, this procedure will lead to interruptions in the communications when the terminals switches mode and registers in the new network. For type 4 DMTs, only the transmission from the terminal is interrupted if the DMT is already registered in the new network. The DMT would, when it identifies that a change of mode is necessary or preferred, first initiate the setup of a third party connection between the fixed exchange and the MSC. Then the DMT registers in the second network using the other mode (if necessary) and a mobile terminated call set-up is initiated before the first link is released. TR 101 176 V1.1.1 (1998-04) 22 For DMT type 5, the handover may be seamless since both terminal and networks can handle simultaneous connections. 6 GIP/GSM dual-mode operation based on a single subscription The purpose of this clause is to describe the functionality of a GIP/GSM dual-mode network operated by a single operator and the DMS, a GIP/GSM DMT with a single subscription). The DMS uses a single GSM subscription to access a single PLMN both via the GSM and the DECT radio interfaces in a way similar to how a GSM/DCS multiband MS accesses a single PLMN both via GSM 900 and DCS 1800 frequency bands, see ETR 366 [22]. As before, the GSM part of a DMT is considered to have GSM/DCS multiband functionality, i.e. in GSM mode the DMT can operate as a GSM/DCS multiband MS as well as a single band GSM 900 and DCS 1800 MS. The DECT/GSM Interworking Profile (GIP), ETR 341 [10] defines how GSM services can be supported on the DECT radio interface and how DECT and GSM can be interworked at layer 3 so that a DECT access network can be connected to a GSM PLMN via the A-interface and a user can access GSM phase 2 services using a DECT portable. GSM macro cell GSM micro cell or DCS cell DECT pico cells MB MS & DMS DMS DMS MS & MB MS Figure 8: Illustration of a possible dual-mode network with GSM macro cells, GSM micro cells, DCS cells and DECT (GIP) pico cells - the types of terminals that can move between the different cell layers are also indicated. MB MS: GSM/DCS multi band mobile station; - DMS: GIP/GSM dual-mode terminal. Two different approaches can be taken for the integration of the GIP access network with the GSM PLMN in order to support GIP/GSM dual-mode operation: - approach 1: enables optimum combined usage of the two technologies that benefits from their specific features. E.g. the DMS would choose to work in DECT or GSM mode based on that a prefered mode is defined, either by the user or the network. Idle mode procedures could be based on that a prefered mode is defined. System information would need to be collected over both radio interfaces. This approach leads to a minimum of additional specifications and amendments. This approach is analogue to the one used for basic dual-mode terminals (see EN 301 242 [17]). TR 101 176 V1.1.1 (1998-04) 23 - approach 2: efforts are made to make the DECT access to behave as if it was a GSM access. E.g. the PLMN must be able to tune cell re-selections and handovers and a DECT cell must mimic a GSM cell. Idle mode procedures would be based on information from both types of cells. The DMT would chose to work in DECT or GSM mode based mainly on radio parameters that has to be made comparable. System information would be broadcasted over both radio interfaces. This approach would likely imply considerable amendments to both GSM and DECT standards. The purpose of DECT/GSM interworking is to complement GSM systems with the DECT access and not to introduce a competing application. In this clause only approach 1 in considered since it enables an optimum combined usage of the two technologies that benefits from their specific features which approach 2 does not. The primary use of GIP/GSM dual-mode operation is likely to increase capacity in hot-spots (e.g. city centres), extend coverage for GSM services to indoor environments and enhance the service level with higher data rates. To achieve these benefits, DECT should be set as the preferred mode of the DMS. The use of GIP does not imply changes of the pricing of the GSM service even when accessed through DECT. The call pricing for the DECT access could, though, be set higher than for GSM calls in case of an increased service level (e.g. higher data rate services) but also lower than GSM in order to attract new types of users. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1 General | GIP/GSM dual-mode operation by a single operator enables an operator, with license(s) to frequencies specified in the GSM specifications, to support the use of three types of terminals (MSs, PPs and DMSs) and to extend the PLMN with respect to capacity, quality, services (higher data rates) and coverage (e.g. indoor environments). A DMS is a GIP/GSM DMT operating with a single subscription, the GSM subscription. It has the functionality to access a single PLMN, and get GSM services delivered, via both GSM and DECT radio interfaces and may be able to perform handover, channel assignment, cell selection and cell re-selection between DECT and GSM modes of operation within one PLMN, i.e. when one PLMN code is used in both modes. NOTE: The functionality to perform handover between modes depend on which type of DMT is used, type 5 is required for a "seamless" handover. Basic DECT/GSM DMTs, as defined in EN 301 242 [17], can use both the GSM and the DECT frequency bands but can not access GSM services in DECT mode. The DMS has the functionality to make PLMN selection in either mode of operation. The DMS shall meet all requirements for each individual-mode and the extra functional requirements for the DMS to handle the priorities related to selection of HPLMN and use of preferred mode. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.1 Frequency bands of operation | GIP/GSM dual-mode operation shall be possible with any combination of the DECT frequency band and the frequency bands specified in the GSM specifications. No frequency band needs to be treated as a primary band. The user or the operator may, however, use control mechanisms to make the DMSs treat one of the modes (DECT or GSM) as the preferred mode. As a first implementation of GIP/GSM dual-mode operation only operation with GSM 900, DCS 1800 and DECT frequency bands is included. The proposed procedures should, however, make it possible for operation between other bands if such are included in the core specifications in the future. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.2 Backwards compatibility | GIP/GSM dual-mode operation should be specified to be backwards compatible so that no harm is made to existing networks and so that GSM phase 2 single mode mobiles, GSM/DCS multi band mobiles and DECT GIP portables will work in a GIP/GSM dual-mode network. DECT GIP PPs and DMSs are based on GSM phase 2 and backward compatibility with GSM phase 1 and 2 single band mobiles and GSM/DCS multi band mobiles are ensured by the GSM specifications. A GIP/GSM dual-mode PLMN shall therefore, in addition to support of DMSs, be able to support the use of single mode terminals for each of the modes of operation. Single mode signalling will be present as well as dual-mode signalling. TR 101 176 V1.1.1 (1998-04) 24 Backward compatibility by the DMSs must also be ensured. The DMSs shall therefore be able to, functionally, work as single mode terminals in single mode networks (DECT or GSM). |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.3 PLMN codes | Dual-mode operation of GIP/GSM by a single operator, with handover and assignment between the bands, implies that only one PLMN code is used in all bands of operation. Handover and assignment between PLMNs is not considered. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.4 Other systems | GIP/GSM dual-mode operation by a single operator does not include multi mode operation, i.e. handover assignment or roaming between DECT or GSM and systems covered by other specifications or standards. The amendments of the DECT and the GSM specifications for GIP/GSM dual-mode and GSM/DCS multiband operation may however be done in a flexible way so that future multi mode operation can make use of the same procedures. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.5 Multiple service execution | The possibility to run several services simultaneously, e.g. GSM speech at the same time as a DECT/GSM enhanced bearer service over DECT, exists for a DMT type 5 based DMS. This may require modifications in the network to allow multiple services but may become possible if e.g. the DECT part of the DMS can interwork to GPRS. |
e02eba098cd1221ec7283147ddcee9f5 | 101 176 | 6.1.6 DMT type considerations | The consequence for service and network performance of GIP/GSM dual-mode operation depends on which DMT type the DMS is based on. This subclause describes the main differences between the service levels offered by the different DMS types. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.