hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.1.2.2 HIPERLAN/2 specific user equipment requirements | • It shall be possible to control access to HIPERLAN/2 specific data (protocol intervention). • It shall not be possible to access HIPERLAN/2 specific data that is only intended to be used for security purposes, e.g. authentication keys and algorithms. • It shall be difficult to change the identifier. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.1.2.3 Comparison with HIPERLAN/2 capabilities | After looking at the current HIPERLAN/2 specification some issues have been identified as needing further attention in order to fulfil the requirements. These issues are: 1) There does not seem to be any replay protection. The challenge needs to be sequential to assure that the same challenge is not sent several times.... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.1.3 Quality of Service | Note that one of these requirements below, would also apply to a non-3G interworking HIPERLAN/2 networks. Later more detailed system requirements on the provisioning of IP QoS in HIPERLAN/2 networks are provided. In the loose coupling case it is not the intention to replicate/use the UMTS QoS mechanisms. Overall Requir... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2 System architecture | This clause introduces the system architecture that is required to support loose coupling. In order to provide HIPERLAN/2 access for this scenario the HIPERLAN/2 network as described for corporate access can be used [H2GF SFA]. However, it is useful to split up authentication into a server and a client part where the c... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.1 Protocol stacks | These protocol stacks have been created for the Ethernet CL as an example CL and reflect UMTS Release 3. Additionally it should be noted that TCP may also be used instead of SCTP to transport the Diameter [30] protocol. MT AP IWU Local AAA HLR Gr PHY LINK IP SCTP M3UA SCCP TCAP MAP PHY LINK IP SCTP M3UA SCCP TCAP MAP E... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.2 Interworking with UMTS Releases | The roaming, including charging and security issues, can be handled by the AAA (Authentication, Authorization and Accounting). For Release 4, the Home Subscriber Server (HSS) in the UMTS Core Network is the master database holding the subscriber data for e.g. charging and identity. In future Releases it may be possible... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.3 Interface definitions | Figure 9 presents the interfaces that are covered by the scope of the present document. Interfaces W.1 and W.2 were introduced in reference [15]. The present document defines the sub-parts of W.2. A.2 Diameter/RAD HIPERLAN2 NAI Diameter/RAD (U)SIM Quintets AP AAAL MT NAI Centric- IWU W.2a W.1 A.1 Figure 9: Loose Coupli... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.4 Subscriber data | There are three basic ways in which the subscriber management for HIPERLAN/2 and 3G users can be co-ordinated. 1) Have the interworking between the HIPERLAN/2 subscriber database and HLR/HSS. This is for the case where the interworking is managed through a partnership or roaming agreement. The administrative domains' A... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.4.1 NAI as the user authentication identifier | Internet AAA protocols identify users with the Network Access Identifier (NAI). The NAI that is the userID submitted by the client during authentication (PPP or AAA). The NAI format is: user@realm. In mobility between different administrative domains, the purpose of the NAI is to identify the user as well as to assist ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.4.2 IMSI as the user authentication identifier | The subscribers of the cellular systems GSM/GPRS and UMTS are identified by the International Mobile Subscriber Identity (IMSI), which is stored on a Subscriber Identity Module (U)SIM card, which is a smart card. The IMSI consists of three parts; the Mobile Country Code (3 digits), the Mobile Network Code (2 digits) an... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.4.3 IMSI in NAI as the user authentication identifier | The next feasible possibility is to use the IMSI in NAI [ref: MobileIP I-D]. This means that the IMSI is encoded as a NAI, where the username portion of the NAI contains the IMSI as a string of digits, and the realm portion identifies the AAA server. The IMSI itself contains enough information to identify the GSM opera... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.4.4 Pre paid SIM | As far as the HLR within the core network is concerned, it cannot distinguish the difference between a customer who is pre-paid or not. Hence, this prevents a non-subscriber to this specific 3G network from using the system, if the operator wishes to impose this restriction. As an example, pre-paid calls within a 2G ne... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5 Mobility and handover | In line with the requirements as stated for mobility and handover (see clause 7.1.1), the system architecture supporting this is divided up into two parts: mobility within and between HIPERLAN/2 networks, and mobility between HIPERLAN/2 networks and any other network. (The 'other' network could be a different HIPERLAN/... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.1 Mobility within and between HIPERLAN/2 Islands | In the loose coupling approach, the mobility within the HIPERLAN/2 network is provided by native HIPERLAN/2 (i.e. RLC layer) facilities, possibly extended by the convergence layer in use (e.g. the current Ethernet CL, or a future IP CL). This functionality should be taken unchanged in the loose coupling approach, i.e. ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.1.1 The MT registers to a foreign network | MT AP FA HA IWU/AAAL HLR AAAH Basic HL2 association signalling Encryption startup eapol-start eapol-request- identity eap-response- identity authentication-data request authentication-response (rand, autn,...) authentication- data request authentication-data- response (rand, autn, xres, Ik, Ck) eap-request-??? eap-resp... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.2 The MT moves to a new AP connected to a new foreign agent | MT APnew FAnew APold FAold HA HLR mip-agent-solicitation mip-agent-advertisement IWU/AAAL Basic hl2 association signalling See the message sequence chart "The MT registers at a foreign network" Old registration time expires NOTE: The black circles designate the nodes that are affected by the expiration. Figure 11: Sequ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.3 Mobility Between HIPERLAN/2 access networks and 3G access networks | For the case of mobility between HIPERLAN/2 and 3G access networks, recall that we have the following basic architecture: - An MT attaches to a HIPERLAN/2 network, authenticates and acquires an IP address. At that stage, it can access IP services using that address while it remains within that HIPERLAN/2 network. If th... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.3.1 The MT moves from UMTS/UTRAN to HIPERLAN/2 | It is assumed that the MT has both HIPERLAN/2 and UMTS/UTRAN coverage. It also assumed that the MT remains attached to the UMTS core network by sending routing area updates with a periodicity shorter than the mobile reachable timer in SGSN. The MT will then be in PMM-IDLE mode towards the core network. It also assumes ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.5.4 Handover Triggers | For handover, the terminal must have enough information to be able to make a handover decision for itself, or be able to react to a network decision to handover. Indeed these decision driven events are referred to as triggers, resulting in Network centric triggers or Terminal centric triggers. Simple triggers include t... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6 Security | For Loose Coupling it is possible to use the security features described in the current HIPERLAN/2 standard, with some additions. As mentioned in the introduction there are two variants of security that can be considered. ETSI ETSI TR 101 957 V1.1.1 (2001-08) 32 |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6.1 NAI centric | Within this approach HIPERLAN/2 users may be either existing 3G subscribers or just HIPERLAN/2 network subscribers. These users want to make use of their existing data devices (e.g. Laptop, Palmtop) without additional hardware/software requirements. For both users and mobile operators it is beneficial to be able to bas... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6.2 (U)SIM centric | The (U)SIM centric definitely requires that a user is a native cellular subscriber while - in addition and distinctly from the NAI centric approach - standard cellular procedures and parameters for authentication are used (e.g. (U)SIM quintets). In this way a mobile subscriber using a HIPERLAN/2 mobile access network f... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6.3 Key exchange | Key agreement for confidentiality and integrity protection is an integral part of the UMTS authentication procedure, and hence the UTRAN confidentiality and integrity mechanisms should be reused within the HIPERLAN/2 when interworking with a 3G core network. This will also increase the applied level of security. The Di... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6.4 (U)SIM vs no (U)SIM | Another issue under discussion is whether a (U)SIM shall be used or not. Given the assumption that a (U)SIM is a smart card that needs to be inserted into the terminal the following two paragraphs can be used as input to the discussion. It should be noted that the way (U)SIM is discussed here is independent of authenti... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.6.5 Authentication, Authorization and Accounting architecture | Authentication, Authorization and Accounting functionality needs to be handled by the HIPERLAN/2 network. To support both scenarios outlined above; the AAA server is split into a client (AAAL) and a server (AAAH) part. The AAAH is likely to, but does not have to, be part of a mobile network (e.g. UMTS) or interwork wit... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.7 Quality of Service | This clause discusses the mechanisims that could be used to meet the requirements isted in clause 7.1.3. In UMTS it will be mandatory to support DiffServ at transport level and at user level in Release 4. For HIPERLAN/2 DiffServ can probably be supported via the priorities in the Ethernet CL (TS 101 493-2 [28]). Intero... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.8 User Traffic Management | User traffic will be carried by the CL as defined within the stack as shown in figure 1. Hence the management of this traffic is beyond the scope of the present document. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 7.2.9 End user device (terminal) | For interworking with 3G, the terminal can be of different kinds, like: • a multimode terminal, i.e. one terminal or one module such as a PC card with many different radio interfaces; • separated modules with different radio interfaces. The modules are used in a single terminal. A driver selection function between acti... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8 Tight interworking HIPERLAN/2 and 3G | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.0 General | This clause only considers UMTS as a specific example of 3G technology. Its scope is to investigate some of the Control Plane issues. User plane issues are not considered. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.1 Requirements | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.1.1 Mobility and handover | Two main types of mobility and handover should be handled: between HIPERLAN/2 cells and between HIPERLAN/2 and UTRAN. The radio controller in UTRAN is called RNC and for HIRAN IWU, since the main function for HIRAN is interworking rather than controlling the radio network. Thus, an AP may be connected to an IWU while a... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.1.2 Security | The same security level as for other UMTS access network technologies should be required. The requirements on security of 3GPP services described in [10] are used as a basis for the security requirements in this case. The important access network related functions that should be supported are: 1) A valid (U)SIM shall b... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.1.3 Quality of Service | Reference [1] lists a number of high level requirements for the QoS; end user, general and technical. All of these high level requirements are applicable to HIPERLAN/2 as well. The UMTS bearer service is a part of the end-to-end service. The external bearer service cannot be controlled by UMTS, nor can the bearer servi... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2 System architecture | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.1 General | The discussions below have the following prerequisites: 1) Generally, the standard and design of a HIRAN should be independent of the standard and design of other UMTS access technologies like UTRAN. 2) The Iuhl2 interface (SGSN - IWU) should be used as it is specified by 3GPP, that is, Iu. Some small changes may be ne... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.2 Iu/Iuhl2 | See reference [5]. It is assumed that the Iuhl2 interface, RANAP included, will be used as it is specified by 3GPP, with a minimum amount of changes. SCCP M3UA SCTP RANAP IP AAL5 SDH ETSI/ SONET ATM NOTE: RANAP is placed in the radio network layer control plane. Figure 16: The control plane of Iu and Iuhl2 ETSI ETSI TR... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.3 Iur, Iurhl2, Iurhl2/utr. The use of RNSAP signalling for HIPERLAN/2 | See references [6] and [7]. ATM AAL5 IP SCTP M3UA SCCP RNSAP NOTE: This is not to imply that the solution should be used for HIRAN. Figure 18: The protocol stack of the control plane of Iur for UTRAN In order to offload the core network at handover between two IWU/RNCs, the Iur, Iurhl2, Iurhl2/utr interface can be used... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.4 Iub/Iubhl2 | Some reasoning about the functional distribution between the AP and an IWU can be made here. It could be assumed that the AP handles all functions that can be isolated to its own cell. The IWU handles functions for interworking with the UMTS core network and with other IWUs. The IWU consists of a control plane unit and... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5 Uu/Uuhl2 | See references [8] and [9]. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.1 General | It is assumed that the PHY (TS 101 475 [32]), DLC (TS 101 761-1 [29]) and RLC (TS 101 761-2 [29]) layers of HIPERLAN/2 make up the basis for an UMTS interworking. It is assumed that PHY will not be affected, DLC to a relatively low extent (if any) and RLC to a relatively large extent for a full standard. The RLC part c... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2 Uu/Uuhl2 signalling | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.1 General | Below, HIPERLAN/2 RLC is the same thing as Uuhl2 control plane. The important property is what information needs HIPERLAN/2 RLC signalling and what information can be carried transparently over the air. Transparent here means information that goes directly between the MT and the core network (SGSN) and is not processed... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.2 Existing HIPERLAN/2 RLC signals that can be used as they are | 1) RELEASE. RELEASE-ACK (RADIO BEARER handling). Iuhl2 related. 2) MAC-ID-ASSIGN. MAC-ID-ASSIGN-ACK. U-RNTI Iuhl2 related. 3) HANDOVER-REQUEST, HANDOVER-ASSOCIATION. See clause 8.2.5.2.4[], 3). 4) KEY-EXCHANGE-AP, KEY-EXCHANGE-MT. Probably not. If encryption and authentication are separated, there is a risk for a man-i... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.3 Existing HIPERLAN/2 signals that can be used after changes of the contents | 1) SETUP. CONNECT. CONNECT-ACK (RADIO BEARER handling). Iuhl2 related. 2) MODIFY-REQ. MODIFY. MODIFY-ACK (RADIO BEARER handling). Iuhl2 related. 3) RBCH-ASSOCIATION. Can be used for paging and system information. Iu related. 4) LINK-CAPABILITY, LINK-CAPABILITY-ACK 5) INFO, INFO-ACK. 6) DFS-MEASUREMENT-SHORT-REQUEST, DF... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.4 Possible new HIPERLAN/2 RLC signals | 1) PAGING type 1. See clause 8.2.5.2.3. Iuhl2 related. 2) PAGING type 2. See clause 8.2.5.2.3. Iuhl2 related. 3) CELL-UPDATE, CELL-UPDATE-CONFIRM. See clause 8.2.5.2.2, 2) and 3). New cell update signals are probably not needed. 4) MOBILITY-INFORMATION, MOBILITY-INFORMATION-CONFIRM. Probably needed. 5) REGISTRATION-ARE... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.5 UTRAN signals probably not needed for HIPERLAN/2 | Informational. 1) TRANSPORT-CHANNEL-RECONFIGURATION, TRANSPORT-CHANNEL-RECONFIGURATION- COMPLETE, TRANSPORT-CHANNEL-RECONFIGURATION-FAILURE. Probably not needed for HIPERLAN/2. 2) TRANSPORT-FORMAT-COMBINATION-CONTROL, TRANSPORT-FORMAT-COMBINATION- CONTROL-FAILURE. Probably not needed for HIPERLAN/2. 3) PHYSICAL-CHANNEL... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.6 Transparent signals (NAS) | See clause 8.2.7. It is not a complete list of transparent signals but only an example of those that are used for mobility functions. Over the air interface, transparent information is carried by the signals DOWNLINK-DIRECT-TRANSFER, UPLINK-DIRECT-TRANSFER and INITIAL-DIRECT-TRANSFER. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.5.2.7 Summary of Uuhl2 signals | • up to 37 signals are used as they are; • up to 16 signals are changed; • up to 40 signals are added. The figures are very uncertain and should be used for guidance only. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.6 Subscriber data | The node handling the subscriber data for UMTS is HSS. It is an umbrella concept containing such parts as the HLR and AAA. The development of HSS will be done in steps. HLR and AAA will continue to be separated with different protocols as seen by an authenticating user for quite some time. Eventually, they will merge (... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7 Mobility and handover | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.1 General | In UMTS, the tracking of the location of the MS occurs on three levels; cell, UTRAN/HIRAN registration area and routing area. Change of cell and UTRAN/HIRAN registration area is not visible outside UTRAN/HIRAN. Another way to classify the handover is intra-IWU/RNC, inter-IWU/RNC/intra-SGSN and inter SGSN. Mobility and ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.2 UMTS/UTRAN/HIPERLAN/2 Identifiers | See reference [2]. A number of identifiers are used in UMTS. Some of them are partly handled by HIPERLAN/2 at present. In HIPERLAN/2 there is an AP-Id corresponding to the local cell-id. There is also a NOP-Id that perhaps can be used for the PLMN-Id. The fact that there is an AP field that is split between APT and APC... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.3 Numbering, addressing and identification | See reference [3]. 1) International Mobile Subscriber Identity (IMSI). 2) Temporary Mobile Subscriber Identity (P-TMSI). The VLR and SGSN may allocate TMSI to visiting mobile subscribers in order to support subscriber identity confidentiality. It has only local significance. 3) International Mobile Station Equipment id... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4 Some mobility basic functions used to build mobile sequences | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.1 Basic function Attach | The following signals that are relevant for HIPERLAN/2 are exchanged: 1) Attach Request. From MT via IWU to SGSN. 2) Identity Request. From SGSN via IWU to MT. 3) Identity Response. From MT via IWU to SGSN. 4) Authentication. Between MT and SGSN via IWU. 5) IMEI check. Between MT and SGSN via IWU. ETSI ETSI TR 101 957 ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.2 Basic function Detach | There are two types of detach, MT initiated and network initiated. The following signals are relevant for HIPERLAN/2: 1) Detach Request. From/to MT via IWU to/from SGSN. 2) Detach Accept. To/from MT via IWU from/to SGSN. 3) PS signalling connection Release |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.3 Basic function Service Request, MS initiated | The service request is used by MT in PMM-IDLE state to establish the PS signalling connection for the upper layer signalling or for the resource reservation for active PDP contexts. The following signals are relevant for HIPERLAN/2: 1) Service Request. From MT via IWU to SGSN. 2) Security signalling. MT-IWU-SGSN-HLR. 3... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.4 Basic function Service Request, network initiated | When SGSN receives a downlink packet for an MT in PMM-IDLE mode, SGSN sends a paging request. The following signals are relevant for HIPERLAN/2: 1) Paging. From IWU to MT. 2) Service Request. From MT via IWU to SGSN. 3) Security signalling between MT, IWU, SGSN and HLR. 4) Radio bearer setup. From IWU to MT. 5) Radio b... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.5 Basic function PDP context activation, modification and deactivation | The following signals are relevant for HIPERLAN/2: 1) Activate PDP Context Request. From MT via IWU to SGSN. 2) Activate PDP Context Accept. From SGSN via IWU to MT. 3) Modify PDP Context Request. From/to MT via IWU to/from SGSN. 4) Radio Access Bearer Modification. MT - IWU - SGSN. 5) Modify PDP Context Accept. From/t... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.4.6 Basic function SRNS Relocation Procedure. MT in PMM-CONNECTED state | Radio Network Subsystem relocation is the process where the Iu, Iurhl2, Iurhl2/utr connection is moved from one IWU/RNC to another. It is one ingredient of mobility and handover for optimization of routes, when there is no Iur, Iurhl2, Iurhl2/utr and when there is an Iur, but it is only used for the control plane. For ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.5 Mobility within the same IWU/RNC | If the MT is in MM-IDLE state, Routing Area Update is performed. If the MT in PMM-CONNECTED and the PDP context is activated for user data, the mobility can be handled by the same type of mechanisms that exist for HIPERLAN/2 now, at least over the air. |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.6 Mobility within the same SGSN. Change of RNCs | |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.6.1 General | See reference [4]. The RNCs can be either HIPERLAN/2 IWUs or UTRAN RNCs. There are some main cases depending on the following factors: 1) MT in PMM-IDLE state or PMM-CONNECTED state. In PMM-IDLE state, the MT location is known in the SGSN with an accuracy of the routing area. In PMM-CONNECTED state the MT location is k... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.6.2 Routing Area Update. MT in PMM-IDLE state. Mobile initiated | For the routing area update procedure, the following four signals/signal types are relevant for HIPERLAN/2/UTRAN: 1) Routing Area Update Request. MT via SIWU to SSGN. 2) Security signals. Conditionally exchanged. MT to SIWU to SSGN. 3) Routing Area Update Accept. SGSN via SIWU to MT. 4) Routing Area Update Complete. MT... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.7.7 Mobility within the same GGSN. Change of RNC and SGSN | This is not covered in the present document. ETSI ETSI TR 101 957 V1.1.1 (2001-08) 49 8.2.8 Some simplified signalling diagrams for mobility/handover. Signals inside the core network not shown |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.8.1 General | The following cases should be considered. Handover/Mobility HIRAN-HIRAN HIRAN-UTRAN Mobile initiated Common channel Network initiated Dedicated channel Network initiated Dedicated channel Mobile initiated Common channel Iur used Iur not used Iur not used Iur used Iur not used Iur used Case not treated Iur not used Iur ... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.8.2 ATTACH. An MT attaches (associates) to an UMTS network | MT CORE HIRAN ATTACH-REQUEST IDENTITY-REQUEST IDENTITY-RESPONSE AUTHENTICATION IMEI-CHECK ATTACH-ACCEPT ATTACH-COMPLETE MAC-ID- ASSIGN MAC-ID-ASSIGN-ACK LINK-CAPABILITY LINK-CAPABILITY-ACK KEY.EXCHANGE-MT KEY.EXCHANGE-AP CL-INFO CL-INFO-ACK SETUP CONNECT CONNECT-ACK Signalling connection setup? Figure 20: An MT attache... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.8.4 Network initiated handover with Iurhl2. HIRAN-HIRAN | MT RNC/APold RNC/APnew Core RELOCATION-REQUIRED RELOCATION-REQEST RELOCATION-REQEST- ACKNOWLEDGE Decision to perform SRNS relocation. MT contributes with measurement reports RELOCATION-DETECT RELOCATION-COMPLETE Iu-RELEASE-COMMAND RELOCATION-COMMIT FORWARDING-OF-DATA RNTI-REALLOCATION RNTI-REALLOCATION COMPLETE FORWARD... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.8.5 Mobile initiated handover without Iur. HIRAN-HIRAN and HIRAN-UTRAN | It is not solved for UMTS yet. It will be done so in the near future. ETSI ETSI TR 101 957 V1.1.1 (2001-08) 53 8.2.8.6 Mobile initiated handover with Iur used. Combined cell/URA update and SRNS relocation. HIRAN-HIRAN MT RNC/APold RNC/APnew CORE CELL/URA-UPDATE. Instead, probably parts of the HL2 HO procedure can be us... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 8.2.9 Security | The security functions reside in the terminal, the access network and in the core network. The distribution of the functions differs and is described below. (U)SIM based mutual authentication is used between the MT and the serving network. This requires that a physical device, UICC(UMTS IC Card), is available in the te... |
0b93cc07d20d84eebf181c0e7cf1637f | 101 957 | 9 Conclusion | The present document shows that HIPERLAN/2 - 3G Interworking can be achieved by changes, discussed within the main body of the document, to existing HIPERLAN/2 standards. It is therefore recommended that the findings of the present document are acted on and taken further. ETSI ETSI TR 101 957 V1.1.1 (2001-08) 55 Annex ... |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 1 Scope | The present document addresses interoperability issues specific to ASI data transmission links, and explicitly is not concerned with general MPEG-2 interoperability issues. An example of an ASI interoperability problem is where equipment receiving an ASI data stream occasionally drops out of lock, or never achieves loc... |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASI Asynchronous Serial Interface tx-clk transmission clock rx-clk receiver clock ETSI ETSI TR 101 891 V1.1.1 (2001-02) 6 |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 4 ASI transmission links | The ASI is a uni-directional transmission link to transfer data between professional digital video equipment. Figure 1 presents an abstract model of an ASI transmission link. The model represents signals at the Layer 1/Layer0 interface of figure B.1 of EN 50083-9 [1]. rx-clk tx-clk Variable Delay ASI-link T R Figure 1:... |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 5 Recommendations | It is recommended that equipment manufacturers include the following information on their product data sheets: • For equipment with an ASI input, the size of the ASI receiver buffer in transport packets that is available to remove ASI transmission aperiodicity should be stated; • For equipment with an ASI output, the m... |
eadc1e2144db26ebd14fcb36554aba39 | 101 891 | 6 Clarifications | Note that if the equipment can accept 204-byte transport packets (optional) in addition to 188-byte packets (mandatory), then the size of the required buffer in bytes would have to be larger than if only 188-byte packets are supported. In some cases, an ASI output may work with an ASI input with a smaller buffer than i... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 1 Scope | The present document describes the requirements and definitions for the administrative and real-time aspects of the TIPHON Resolution Capability (TRC). TIPHON Resolution Capability (TRC) is a centralized resolution mechanism for inter-service provider call routing in TIPHON compliant networks. In terms of the general f... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [2] ITU-T Recommendation E.168: "Application of E.164 numbering plan for UPT". [3] ITU-T Recommendation Q.1290: "Glossary of terms used in the defi... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 3 Definitions and abbreviations | |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Administrative Reference DataBase (ARDB): centralized database used for storing the master copy of E.164 number to HNN mapping that will be periodically downloaded to RTDBs for real-time query NOTE: Service providers can create, update... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AD Administrative Domain AD-BES Administrative Domain Back-End Service ARDB Administrative Reference DataBase HNN Home Network Name IP Internet Protocol ITU-T International Telecommunication Union - Telecommunications standardization sector NA... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 4 Overview | The main purpose of the TIPHON Resolution Capability (TRC) is to provide a global, geographically independent service to telephony users in TIPHON compliant networks. Each user obtains a unique E.164 number during the provisioning process either from a Number Allocation Authority (NAA) or via the service provider where... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5 Functional requirements for the ARDB | This clause describes the requirements pertaining to the administrative aspects of ARDB. "SHALL" means mandatory, while "SHOULD" means recommendation, and "MAY" means optional. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.1 Service provider management | |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.1.1 Service provider profile | 1) The ARDB SHALL maintain a profile for each participating service provider. 2) The profile of a service provider SHALL be created by the TRC administrator when the service provider is first granted access to the TRC. 3) The profile of a service provider SHALL be deleted by the TRC administrator when the service provi... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.1.2 Access control | 1) The ARDB SHALL allow a service provider to query its own profile. 2) The ARDB MAY allow a service provider to provision certain parts of its profile. 3) The ARDB SHOULD accommodate multiple accounts for a service provider, which may access the RTDB simultaneously. 4) The ARDB SHALL disallow a service provider from a... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.1.3 Access methods | 1) The ARDB SHALL allow interactive access by a service provider to its own profile. 2) The ARDB SHOULD allow non-interactive means by a service provider to update its own profile. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.2 Subscriber record management | A subscriber record is associated with a specific service provider. If a subscriber has multiple numbers, each number constitutes a separate record. The TRC may consolidate common information among these numbers for a subscriber. If a subscriber has multiple numbers from different service providers, each number will ha... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.2.1 Subscriber record | 1) A subscriber record SHALL contain the number to HNN translation information for each number assigned to the subscriber. 2) A subscriber record MAY contain other subscriber information such as contact address and billing. 3) The ARDB SHALL provide capabilities for a service provider to create, query, update and delet... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.2.2 Access control | 1) A service provider SHALL be able to access all of its subscriber records. 2) A service provider SHALL be disallowed from accessing subscriber records of other service providers. 3) If an individual subscriber is allowed to access the ARDB, he/she SHALL be able to access only their record and nothing else. The operat... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.2.3 Access methods | 1) The ARDB SHALL provide both interactive and batch modes for a service provider. 2) If an individual subscriber is allowed to access their record(s), the ARDB SHALL provide interactive mode. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3 Number management | |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.1 Number assignment | 1) A number SHALL be assigned to no more than one subscriber. 2) A provider/subscriber SHALL be able to request for more than one number. 3) A provider/subscriber MAY be allowed to request for preferred (golden) number(s). 4) If a potential subscriber requests a specific number, the ARDB SHALL check for the availabilit... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.2 Number recall | 1) If a number is no longer associated with a subscriber, the number SHALL be marked as "hold" with a time stamp. 2) When the time expires, the number is marked as "free" and SHALL be returned to the available number pool for re-assignment. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.3 States of a number | The states of each number SHALL include the following: • Free – default entry state; • Reserved – wait for routing provisioning to become complete; • Assigned – finished registration and provisioning process; • Hold – wait for time expiration in order to become available for assignment; • Unusable; or • Spare – not ava... |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.4 Service disconnect | When a subscriber no longer wants to subscribe a number, he/she and the service provider will agree on a disconnect date/time. The service disconnect event SHOULD be logged. The ARDB SHALL remove the subscriber's record at the agreed upon disconnect date/time. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.5 Problem solving | The TRC SHOULD aid in isolating problems associated with numbers that are not reachable. If an inaccuracy is found, the TRC SHALL take appropriate actions to fix the problems and inform or update any appropriate entities/parties. |
8ea3a70ff1bf865c2806c00ec5f889fd | 101 886 | 5.3.6 Subscriber support | 7x24 business support SHALL be provided by the TRC. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.