hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.2.3 PDP Context Deactivation Procedure | At PDP context deactivation, the PDP context in the PS-MGW is deleted.
The MS initiated PDP context deactivation procedure with the required changes is presented in the figure below. The required changes are the same in case of the SGSN or GGSN initiated PDP context deactivation procedure.
Figure 25: PDP Context Deacti... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.2.4 RAB Release Procedure | With the RAB release procedure, the UTRAN initiates the release of one or more RABs. The SGSN Server has to inform the PS-MGW about the RAB release. The RAB release procedure with the required changes is presented in the figure below.
Figure 26: RAB Release Procedure
1-4) The RAB release procedure is performed as descr... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.2.5 Service Request Initiated by MS Procedure | After releasing RABs for active PDP contexts (see chapter ‘RAB release’), it may be necessary to establish the RABs again, e.g., due to packets to be transferred on the PDP contexts. This is done with the service request procedure initiated either by the MS or by the network. The SGSN Server has to inform the PS-MGW ab... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.2.6 Service Request Initiated by Network Procedure | The network initiated service request procedure with the required changes is presented in the figure below.
Figure 28: Service Request Initiated by Network Procedure
1) A downlink PDU is received in the PS-MGW.
2) The PS-MGW sends the Update PDP Context Request message to the SGSN Server to request the initiation of pa... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.3 Charging (GTP-C option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.4 CAMEL Considerations (GTP-C option) | The communication towards the SCP is triggered by signalling events as well as by events related to the transfer of user data. The communication towards the SCP may be provided either by 1) preserving only one interface towards the SCP (i.e. SGSN Server – SCP) and sending the necessary information between the SGSN Serv... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.5 Lawful Interception (GTP-C option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.5.1 Lawful Interception of Content of Communications | To enable the PS-MGW to intercept Content of Communication (CC), or in other words user plane packets, and forward these to Delivery Function 3 (DF3), the SGSN server must order the PS-MGW to set up a connection towards DF3 for every applicable PDP Context. The SGSN server must give the PS-MGW the parameters that are n... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.5.2 Lawful Interception of Intercept Related Information | The IRI (Intercept Related Information) signalling is handled by the SGSN server. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.6 QoS Considerations (GTP-C option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.7 Information storage in PS-MGW (GTP-C option) | The PS-MGW has to store information on active PDP contexts in order to relay packets between the RNC and the GGSN. For uplink packets, the PS-MGW needs the GGSN Address for User Plane and the GGSN TEID for User Plane. For downlink packets, the PS-MGW needs the RNC Address for User Plane and the RNC TEID for User Plane.... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.4.8 Abnormal Cases (GTP-C option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.5 General Lawful Interception Considerations | As the protocol interfaces and data formats between the ADMF/DF and GSN entities were omitted from the scope of standardisation, constraints on the interoperability of the split SGSN exist, if the entities are to be supplied from different vendors. The ADMF and DF entities in this case would have to inter-operate with ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.6 Security | The security mechanisms Ipsec/IKE can be used on the Mp interface. Ipsec/IKE are recommended for the H.248 protocol and are parts of the security architecture that is under design in S3 for the UMTS R4/R5 network. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.7 O&M | The split SGSN solution will add a new network element to manage but only minor changes to the 3GPP O&M standards. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.8 RAN Considerations (e.g. GERAN) | No impacts are foreseen between the split of the SGSN and the RAN functionality since:
- The Iu-PS interface is already split into a control plane and a user plane, and the existing protocols can be used as is.
- The Gb interface will be terminated in the 2G-SGSN for both the control plane and the user plane.
- GERAN u... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.9 Compatibility | The compatibility issue between 2G and 3G is already handled in the sections on Mobility Management.
As there is no impact on the existing PS protocols when introducing the split architecture, the SGSN server and the PS-MGW can have an interface towards R’97 (and later releases) nodes, both towards SGSN and GGSN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.10 Dynamic Allocation of PS-MGW Resources | A simple way of achieving resource sharing is that each SGSN server uses a primary PS-MGW and a secondary PS-MGW. Say SGSN server A uses PS-MGW A as its primary and PS-MGW B as its secondary, and SGSN server B uses PS-MGW B as its primary and PS-MGW A as its secondary. SGSN server A will therefore use PS-MGW A, and SGS... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.11 Benefits and Drawbacks | The benefits and drawbacks are compared to the R’99 architecture, unless otherwise specified.
Benefits:
- Flexibility to allocate processing capacity for traffic and for control in different locations
- Flexibility to independently scale the control plane and the user plane by increasing/decreasing the number of nodes ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.12 Open Issues | - Investigation into redundancy schemes are to be addressed in stage 3 work
- Comparison analysis of H.248 and GTP-C protocols is to be addressed in stage 3 work
- Migration to MIP Step 3, as proposed by TR 23.923, would negate the need for the split architecture.
- Ongoing 3GPP work on Iu flexibility will allow load s... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7 Alternative 2: One Tunnel Approach | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.1 Introduction | The One Tunnel Approach separates transport and control functionality of the SGSN in applicable scenarios. The result of this separation are an SGSN controller (cSGSN) performing all control functions of an SGSN and an enhanced GGSN (xGGSN) which performs SGSN and GGSN transport functionality. This enables a direct GTP... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.1.1 Applicability | The benefits of the approaches depend on the extent of their applicability. An anticipation of future IP bearer service usage is therefore important to identify the gain of the approaches.
The trends for the usage of IP bearer services anticipated here are:
- IP based VPN solutions provide access to Intranets in an acc... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2 Logical Architecture | The logical architecture for this approach, as an evolution of the reference logical architecture, is depicted in Figure 33.
Figure 33: Evolved logical architecture for the One Tunnel Approach |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.1 Functional Nodes | Only functional nodes relevant for the One Tunnel Approach are described, i.e. which are changed compared with R99 or used differently. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.1.1 2G-SGSN | This evolved architecture has no impact on the 2G-SGSN or its interfaces. A 2G-SGSN is necessary to support the Gb interface which does not support a separation of transport and control. The Gn interface of a 2G-SGSN supports both user and control data. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.1.2 3G-SGSN / cSGSN | This evolved architecture has no impact on the 3G-SGSN and its interfaces and is compatible with it. A 3G-SGSN is necessary to support packet bearer services using GGSN external to the visited PLMN and packet bearer services using a R97-R99 GGSN.
The 3G-SGSN can be upgraded to become an SGSN without data transport func... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.1.3 GGSN / xGGSN | The R99 GGSN can be upgraded to become a GGSN required for the one tunnel approach by adding new functionality and modifying its interface towards the cSGSN. In order to have a differentiation the following notion is introduced.
The notion of an (x)GGSN shall maintain a clear figure of the architecture. The (x)GGSN is ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.2 Interfaces | Only interfaces relevant for the One Tunnel Approach are described, i.e. interfaces which are changed compared with 3GPP R99. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.2.1 Gn (cSGSN – xGGSN) | This interface evolves to control the direct GTP tunnel between RAN and xGGSN and to deliver information for SGSN specific transport functions to the xGGSN (location information and prepaid budget).
The modifications compared with the R99 GTP version are:
- One Tunnel information field is introduced as optional informa... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.2.3 User Plane | The protocol stack for the user plane is shown in Figure 34. The protocol stacks in the UE, in the 3G-RAN and the 3G-GGSN are the same as specified in the 3GPP R99 architecture. The user plane protocols specified for the SGSN are not needed in the One Tunnel Approach. Instead the IP transport network adapts different p... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3 Mobility Management | The procedures are for packet bearer services using a GGSN in the visited network with a 3G RAN, i.e. for the cSGSN / xGGSN architecture of the One Tunnel Approach. For all other bearer services or 2G RAN the R99 procedures and the SGSN / GGSN as specified in TS 23.060 apply. Modifications compared with 3GPP R99 are in... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.1 Inter ISGSN Routeing Area Update | The Inter ISGSN Routeing Area Update procedure is illustrated in Figure 35. The difference compared with 3GPP R99 is in step 5) when the change is from a cSGSN or an SGSN to a cSGSN. In this case the Tunnel Endpoint Identifier delivered to the xGGSN indicates the reserved “not allocated” value for the traffic path as t... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.2 Location Report Procedure | This procedure is necessary in order to inform the xGGSN about the location of a subscriber. This is needed e.g. for location dependent interception or location dependent charging.
Figure 36: Location Report Procedure
1) The cSGSN sends a Location Report message to the xGGSN. This could contain the SAI or a geographica... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.3 Serving SRNS Relocation Procedure | The Serving SRNS Relocation procedure is illustrated in figure 37. The sequence is valid for both intra cSGSN SRNS relocation and inter cSGSN SRNS relocation. The differences to 3GPP R99 are: in step 4) the RAN is provided with the user data TEID and user data Address of the xGGSN instead that of the SGSN and in step 1... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.4 Combined Hard Handover and SRNS Relocation Procedure | With the same modifications as for the SRNS Relocation Procedure above compared to 3GPP R99 this procedure relocates the direct GTP tunnel between RAN and xGGSN from one RNC to the other. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.5 UMTS to GSM Change | In this case the procedure is the same as specified in 23.060 for the R99 UMTS to GSM change. The SRNS Data Forward Command delivers from cSGSN to the SRNC tunnel endpoints for the packets to be forwarded. These tunnels terminate in the cSGSN as in R99. The downlink data flow is then GGSN – SRNC – cSGSN – 2G-SGSN until... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.6 GSM to UMTS SGSN Change | The intersystem change from GSM to UMTS takes place when a GPRS-attached UE changes from GSM radio access to UTRAN and the UTRAN node serving the UE is served by a different SGSN. In this case the RA changes. Therefore, the UE shall initiate a UMTS RA update procedure by establishing a RRC connection and initiating the... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.6.1 Intra SGSN Change | The difference compared with 3GPP R99 is, that an additional Update PDP Context in step 4) is needed. This message indicates to the xGGSN the reserved “not allocated” value for the traffic path as the Iu bearer is not yet allocated at the RAN. In step 12) the xGGSN tunnel endpoints are indicated to the RNC instead of t... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.3.6.2 Inter SGSN Change | The difference compared with 3GPP R99 is, that the Update PDP Context in step 8) indicates to the xGGSN the reserved “not allocated” value for the traffic path as the Iu bearer is not yet allocated at the RAN. In step 20) the xGGSN tunnel endpoints are indicated to the RNC instead of the SGSN tunnel endpoints. Furtherm... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4 Session Management | The procedures are for packet bearer using a GGSN in the visited network with a 3G RAN, i.e. for the cSGSN / xGGSN architecture of the One Tunnel Approach. For all other bearer services or 2G RAN the R99 procedures and the SGSN / GGSN as specified in TS 23.060 apply. Modifications compared with 3GPP R99 are in italic. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4.1 PDP Context Activation Procedure | For better comparison with the 3GPP R99 PDP context activation procedure all PDP parameter checks and descriptions are included in the description, although the procedure applies only for bearer services using a GGSN in the visited network. The difference compared with 3GPP R99 is the creation of the PDP context on the... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4.2 Secondary PDP Context Activation Procedure | The Secondary PDP Context Activation procedure may only be initiated after a PDP context is already activated for the same PDP address and APN. The procedure is illustrated in figure 41. The difference compared with 3GPP R99 is the creation of the PDP context on the xGGSN before the RAB setup. And this PDP context crea... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4.3 Iu Release Procedure | The RAN initiates an Iu release procedure to release all RABs of an UE and the Iu connection. The Iu Release procedure is illustrated in figure 42. The difference compared with 3GPP R99 is the additional step 2) informing the xGGSN, that the transport tunnel endpoint at the RAN is no more allocated.
Figure 42: Iu Relea... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4.4 Service Request Initiated by UE Procedure | The UE in PMM‑IDLE state sends the Service Request message to the cSGSN in order to establish the PS signalling connection for the upper layer signalling or for the resource reservation for active PDP context(s). This procedure is also used by an UE in PMM‑CONNECTED state to request the resource reservation for the act... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.4.5 Service Request Initiated by Network Procedure | When the xGGSN receives a downlink packet for a PDP context with a not allocated GTP tunnel (UE in PMM‑IDLE state), the xGGSN notifies the cSGSN. This initiates a paging request to trigger the Service Request procedure in the UE. Compared with 3GPP R99 the GTP tunnel at the xGGSN is not established after Iu release. Th... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.5 Charging | There are three different types of charging information which are collected by the SGSN and/or the GGSN: Mobility Management information, SMS information and PDP context information. In the One Tunnel Approach the cSGSN doesn’t collect the data volume for charging purposes. The charging functionality for Mobility Manag... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.6 CAMEL Considerations | In the One Tunnel Approach the data traffic passes only the xGGSN. Therefore volume dependent CAMEL functionality is performed by the xGGSN. All other CAMEL functionality remains in the cSGSN.
In the following, two aspects are described where the xGGSN is involved. The first one is the subscription change during establ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.6.1 Subscription Change during Established PDP Context | If due to subscription change, the SCP needs to get control on PDP contexts that were established using the One Tunnel approach, then the cSGSN activates all required functionality when the subscription change is signalled by the HLR. If CAMEL prepaid applies the cSGSN sends an Update PDP Context to the xGGSN including... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.6.2 CAMEL Prepaid | In the One Tunnel Approach the data traffic passes only the xGGSN. Therefore volume dependent CAMEL prepaid is performed by the xGGSN. The cSGSN sends by means of the Create PDP Context Request message the prepaid budget for the required context to the xGGSN. Also during an inter cSGSN change the prepaid budget will be... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.7 Lawful Interception | 3G TS 33.107 describes the architecture and functional requirements for interception for a 3rd generation mobile communication system. The specification applies to both SGSN and GGSN. There is only one difference interception at the GGSN is a national option which means in fact a GGSN is enabled for interception if an ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.8 QoS Considerations | The removal of one GPRS specific node from the data path by the One Tunnel Approach improves the packet bearer QoS by reducing the packet transfer delay.
If two tunnels are established then the SGSN has to perform the following functions:
- IP/UDP termination
- GTP termination,
- look up for the corresponding PDP conte... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.9 Security | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.10 O&M | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.11 RAN Considerations (e.g. GERAN) | The One Tunnel Approach is applicable for any RAN with separated transport and control at the interface to the core network, i.e. for UTRAN and the Iu enabled part of the GERAN. The One Tunnel Approach has no impact on the RAN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.12 Abnormal Cases | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.13 Compatibility | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.14 Benefits and Drawbacks | The benefits and drawbacks are compared to the R’99 architecture, unless otherwise specified.
Benefits:
- Removes the SGSN from the user data path when this is possible (NB, it is expected to apply for most of the cases). The delay that the packets experience in the UMTS network is then decreased by bypassing the SGSN ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 7.15 Open Issues | - The actual reduction in delay by bypassing the SGSN in the transport plane is strongly dependent on implementation and can therefore not be exactly estimated here. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8 Summary | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1 Selection Criteria | This subsection contains an unordered list of selection criteria which will be used as a guideline when the feasibility study makes its recommendation.
The selection criterion is divided into two parts. The first refers to specific aims of the Feasibility Study and is included to give a clear indication of the advantag... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1.1 Aims | - Available in a timely manner (e.g., R4/R5). However, the interactions with a split of call control and user planes, also in UTRAN, need to be taken into consideration to allow comprehensive operator reasoning behind the viability of the split functionality
- The chosen approach should make efficient use of the networ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.1.2 Compatibility criteria | - Can be introduced into an existing network in a phased manner, i.e. can co-exist and inter-operate with non-split elements of the same type.
- Applicable for both pre-pay and subscription subscribers
- Applicable for both roaming and non-roaming subscribers
- Should not preclude the use of Mobile IP, both v4 and v6, ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2 Assignment of Functions to the Logical Architecture | The following table provides an overview of the functions performed by the different nodes of each alternative. SGSN and GGSN refer to R99 nodes and also to the case where it is not possible to establish one tunnel in alternative 2.
NOTE 1: For alternative 2, the SGSN and cSGSN functions on one hand, and the GGSN and x... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1 High-Level Functions Description | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.1 Network Control Functions | Authentication and Authorisation Function: This function performs the identification and authentication of the service requester, and the validation of the service request type to ensure that the user is authorised to use the particular network services. The authentication function is performed in association with the ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.2 Packet Routeing and Transfer Functions | Relay Function: The relay function is the means by which a node forwards data received from one node to the next node in the route.
Routeing Function: The routeing function determines the network node to which a message should be forwarded and the underlying service(s) used to reach that GPRS Support Node (GSN), using ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.2.1.3 Mobility Management Functions | The mobility management functions are used to keep track of the current location of an MS within the PLMN or within another PLMN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 8.3 Comparison of the Overall Functionality | The table below addresses the cases where the respective evolved architectures are applicable.
NOTE 1: The split SGSN approach is not applicable when 2G radio is used.
NOTE 2: The one tunnel approach is not applicable when 2G radio is used, at inter PLMN scenarios, and when R97-R99 SGSN and/or GGSN is used.
Table 3: Co... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 9 Work Plan | SA2#13
May 22-26, 2000
Proposal for a new Work Item.
CN/SA2 workshop
June 14-15, 2000
Discussion of Work Item responsibilities.
SA#8
June 26-28, 2000
Work Item and distribution of responsibilities approved.
Drafting session
August 22-24
Discussion and selection of alternative architectures to be studied. Start work on ... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 1 Scope | The purpose of the present document is to help the TSG RAN WGs to understand the proposed method and to specify the impacts to existing specifications, which is needed for the introduction of the “Enhancement on the DSCH hard split mode” for Release 5.
“Enhancement on the DSCH hard split mode” is proposed to specify th... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 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.
For a no... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3 Definitions, symbols and abbreviations | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.2 Symbols | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
TFCI Transport Format Combination Indicator
DSCH Downlink Shared Channel |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4 TFCI coding in DSCH hard split mode | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.1 Introduction | In the current Rel99 & Rel’4 specification, as identified by RAN WG’s (WG1, WG2 and WG3), when DSCH scheduling be done in DRNC, logical split cannot be supported over Iur during the DSCH soft handover. Furthermore, hard split has advantage over logical split in the sense that it can be supported over Iur. However, it w... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.3.4 Operation of TFCI in Hard Split Mode | If one of the DCH is associated with a DSCH, the TFCI code word may be split in such a way that the code word relevant for TFCI activity indication is not transmitted from every cell. The use of such a functionality shall be indicated by higher layer signalling.
The TFCI is encoded by using punctured code of (32,10) su... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.1 Study Areas | 4.4.3.1.1 Impact on NBAP messages
Currently, on Iub interface, it is assumed that the TFCI bit for DCH and DSCH in hard split mode have 5 bit/5 bit length. TFCI signalling mode that contains TFCI split information is included in following NBAP messages for DSCH split mode setting.
• RADIO LINK SETUP REQUEST
• RADIO LI... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.2.2.50 TFCI signalling mode | This parameter indicates if the normal or split mode is used for the TFCI. In the event that the split mode is to be used then the IE indicates whether the split is 'Hard' or 'Logical', and in the event that the split is 'Logical' the IE indicates the number of bits in TFCI (field 2).
IE/Group Name
Presence
Range
IE ty... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 9.2.2.46 TFCI Signalling Mode | This parameter indicates if the normal or split mode is used for the TFCI.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
TFCI Signalling Mode
ENUMERATED (Normal, Split)
===========================================================================
In the above message, if the TFCI Signalling Mod... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2 Agreements and associated contributions | 4.4.3.2.1 Impact on TS 25.423
4.4.3.2.1.1 RADIO LINK SETUP REQUEST
FDD Message
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
reject
Transaction ID
M
9.2.1.59
–
SRNC-Id
M
RNC-Id
9.2.1.50
YES
reject
S-RNTI
M
9.2.1.53
YES
reject
D-RNT... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2.1.3 UPLINK SIGNALLING TRANSFER INDICATION | FDD Message
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Criticality
Assigned Criticality
Message Type
M
9.2.1.40
YES
ignore
Transaction ID
M
9.2.1.59
–
UC-Id
M
9.2.1.71
YES
ignore
SAI
M
9.2.1.52
YES
ignore
Cell GAI
O
9.2.1.5A
YES
ignore
C-RNTI
M
9.2.1.14
YES
ignore
S-RNTI
M
9.2.1.54
YES
ign... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.2.1.5.2 Flexible Hard Split Support Indicator | The Flexible Hard Split Support Indicator indicates whether the particular cell is capable to support Flexible Hard Split or not.
IE/Group Name
Presence
Range
IE type and reference
Semantics description
Flexible Hard Split Support Indicator
ENUMERATED (Flexible Hard Split Supported,).
4.4.3.2.2 Impact on TS 25.433
Fo... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.3 Specification Impact and associated Change Request | Table 1: Place where Change request is given in order to refer the new procedure
3G TS
CR
Title
Remarks
25.433
583
NBAP signalling support for DSCH hard split mode
25.423
543
RNSAP signalling support for DSCH hard split mode |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 4.4.3.4 Backward Compatibility | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5 TFCI power control in DSCH hard split mode | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.1 Introduction | According to Release99 and Rel’4 specification, there is split mode of operation where TFCI2 (TFCI for DSCH) is not necessarily transmitted from every cell in the active set when UE is in soft handover region. Thus, the combined TFCI power in UE may not be enough to detect it reliably. As well, the power offset for TFC... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.3 Proposed TFCI power control scheme | In this section, some details on the proposed TFCI power control scheme are described, in which new parameters such as TFCI PO or TFCI PO_primary are introduced in Frame Protocol specification and how to allocate flexible power offset for TFCI is explained. As well, simulation results are shown to indicate the required... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4 Specification Impact and associated Change Request | The expected specification impacts are small.
25.214: Time-varying TFCI power by method 1 or method 2 should be explained.
• For method 1, no impact is expected.
• For method 2, SSDT uplink signalling usage for TFCI power control is to be described.
25.427: The changed power offset should be signalled via Iur/Iub signa... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1 DPCCH/DPDCH | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.1 General | The downlink transmit power control procedure controls simultaneously the power of a DPCCH and its corresponding DPDCHs. The power control loop adjusts the power of the DPCCH and DPDCHs with the same amount, i.e. the relative power difference between the DPCCH and DPDCHs is not changed.
The relative transmit power offs... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.4 Site selection diversity transmit power control | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.2.1.4.1 General | Site selection diversity transmit power control (SSDT) is another macro diversity method in soft handover mode. This method is optional in UTRAN.
Operation is summarised as follows. The UE selects one of the cells from its active set to be ‘primary’, all other cells are classed as ‘non primary’. The main objective is t... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4.2 Agreements and associated contributions | It is agreed that the Method2 described in the study area is accepted as the Enhanced TFCI Power Control procedure and this solution will be adopted and specified in RAN3 TSs.
1. It is agreed to use the User plane to signal TFCI power offsets.
2. It is agreed that TFCI PO and TFCI PO_primary parameters are introduced i... |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 5.4.3 Specification Impact and associated Change Request | 5.4.3.1 Impacts on RNSAP (TS 25.423)
=========================== TS 25.423 ============================== |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1 Radio Link Setup | |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1.1 General | This procedure is used for establishing the necessary resources in the DRNS for one or more radio links.
The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure. |
83726f0f79dd0b5bad7d922a555d137b | 25.870 | 8.3.1.2 Successful Operation | Figure 5: Radio Link Setup procedure: Successful Operation
When the SRNC makes an algorithmic decision to add the first cell or set of cells from a DRNS to the active set of a specific UE-UTRAN connection, the RADIO LINK SETUP REQUEST message is sent to the corresponding DRNC to request establishment of the radio link(... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.