hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.9.5.5 Mobility Management
|
For MM point of view, interworking with 2G-SGSN has to be considered. A non-anchor SGSN architecture makes it easy since the GGSN is the anchor point in both 2G-GPRS and UMTS networks. The concepts chosen for UMTS and GSM/GPRS for R99 need to be compatible.
In the case SGSN anchor concept is introduced in R99 GPRS, several issues have to be considered:
• A new relaying protocol has to be introduced since BSSGP does not fulfil this requirement,
• The MS behaviour has to be modified: in standby state, it has to initiate a cell update instead of a RA update,
• The drift SGSN has to route the cell update to the anchor SGSN it does not already knows,
• When receiving a downstream PDU, the anchor SGSN has to page the MS under another SGSN. The use of P-TMSI may lead to conflicts since the same P-TMSI value may be already used for another MS.
• Interception and charging aspects, since the GGSN and the MS could be in different regions.
The current mechanism with UMM uses different mechanisms for PS and CS MM. The impacts of both mechanisms on GPRS MM/UMM and security/ciphering need to be addressed.
Within the anchor concept there are no RA updates as long as the MS has an active PDP context via anchor SGSN.
The non-anchor concept leads to RA updates with every change of SGSN; however, there is no RA update as long as the SRNS is not changed since the SRNS acts as an anchor point in the UTRAN.
The impacts of inter SGSN RA update for both anchor and non anchor solution in conjunction with location based services (such as SoLSA) needs to be addressed.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.9.5.6 Comparison of developments needed within the standards for GSM/GPRS/UMTS R99
|
• R99 will include the support of QoS within GSM/GPRS and UMTS.
• Class A operation and UMTS simultaneous mode will be required for R99.
• The anchor SGSN concept would include the specification of drift SGSN and packet forwarding mechanisms.
• The non-anchor concept may need enhancement to satisfy the QoS concepts and will need development to ensure the interruption for inter SGSN RA update can be achieved within the QoS requirements.
• The changes and developments needed to GPRS R97 to satisfy these requirements as well as inter-working to pre R99 networks needs to be addressed.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.10 Quality of service
|
• Application/End to end QoS
• QoS Segments (e.g. Radio, UTRAN, CN, Internet)
• QoS Mapping (between different segments/layers)
• Radio Access Bearers
• Resource management
• Interfaces/APIs between Application, TE, MT
• Charging of QoS aware applications
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.11 Others
| |
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.11.1 GPRS/IP support for Multi-media service
|
The following developments are needed within IP/GPRS to support the expected multi-media requirements of UMTS (note this list is not exhaustive):
QoS for GPRS: To enable real-time ‘streaming’ developments.
Adoption of IP Telephony, H.323 and equivalent PSTN/Internet technologies: To support the control and interworking of multi-media and telephony applications with non-UMTS networks.
Interrogation of the HLR with the Gateway functionality: To enable terminated communications to be delivered to the mobile terminal. This can include the PIG and H323 functionality.
Figure Z 17 illustrates a potential architecture which could be used to deliver telephony and multi-media features.
Figure 173: Evolved GPRS/IP support for Multi-media services
Telephony and multi-media requirements for UMTS may be supported via the evolved IP/GPRS network of Figure Z17. This architecture does not need a separate non-IP based circuit switched (MSC) platform.
• Multimedia service control
• Phasing. What is for release -99, -00, etc. ?
• Network migration
• Handling and type of coded speech over Iu
• Location of ciphering functionality
• Link access control for user data (LAC-U)
• Data compression
• Allocation of resources of Iu
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.11.2 Separation of switching and control
|
Proposed Architecture
In this section the concept of a logically Separated Call Control (SCC) server is introduced. Currently CC is integrated with each of the MSCs in a network. Here it is suggested (and shown in figure 18) that a single CC function is implemented which is logically separated from the switch. The physical location of the SCC server is an implementation issue. Examples of implementation include:
• SCC integrated with IWU.
• SCC integrated with one or more switches. In this case a IWU may not be required between the SCC and the switch(s) with which it is implemented. IWUs would be used to connect to other switches.
• Standalone SCC.
Data required by the SCC could be held locally so as to reduce signalling load. This is likely to include data currently held in the HLR and VLR and a network resource database which allows the SCC to determine what network resources are available and record the state of resources e.g. used, reserved or free. Figures 2 19 and 3 20 show the signalling flows in the network for mobile originated and mobile terminated calls respectively.
In figure 1 MM is shown as being integrated with the SCC. It could equally well be separated from the SCC.
Figure 184 Network Architecture
Notes:
1. DBs represents all databases necessary for SCC operation, e.g. HLR, VLR, Network Resource database.
2. MAP (with some new operations) could be used here which would probably represent minimum change. Alternatively a more general protocol such as MGCP could be used which would represent more change but have the advantage that the switch would be made more generic.
3. ISUP (with some modified messages) could be used to communicate between the SCC and the transit switch of a neighbouring network.
4. This signalling is shown to pass through the transit switch as this is a likely (but not mandatory) route for it to take. The logical connection is between the SCC and the neighbour network.
5. MAP (with some new operations) could be used here which would probably represent minimum change. Alternatively a more general protocol could be used which would represent more change but have the advantage that the databases would become more generic. If an IN implementation is adopted the SSF could form part of the SCC which could communicate with an SCF via MAP or INAP which in turn could communicate with the DB via DAP.
6. This interface could be the same vendor specific propriety interface that is implemented today internally to the MSC.
Mobile Originated Call
Figure 1519. Signalling Flow for MO call.
Notes:
1. A modified SRI operation could be used by the SCC to request routing information from the databases. The response contains all the information required to route the call from the serving switch to the point of interconnect.
2. A modified IAM and ACM could be used to communicate between the SCC and the transit switch. Because the SCC serves multiple switches a switch ID (in addition to a route ID and circuit ID) is required.
3. EST (establish) and EST ACK could be a new MAP) or could be provided by a new protocol such as MGCP. Here EST is used to instruct the switch to establish the backward connection. EST ACK confirms that the required connection has been established. Note that the SCC executes the EST operation to all involved switches simultaneously. In the event of a handover the SCC would execute EST operations only to those switches involved in the handover. In the event that the neighbour network is not controlled by an SCC the transit switch is unlikely to be involved.
4. Here EST is used to instruct the switch to establish the forward connection.
Mobile Terminated Call
Figure 1620. Signalling Flow for MT Call.
Notes:
1. A modified IAM and ACM could be used to communicate between the SCC and the transit switch. Because the SCC serves multiple switches a switch ID (in addition to a route ID and circuit ID) is required.
2. A modified SRI operation is used by the SCC to request routing information from the databases. The response contains all the information required to route the call from the serving switch to the point of interconnect.
3. For clarity MM is considered as part of SCC here.
4. EST (establish) and EST ACK could be a new MAP) or could be provided by a new protocol such as MGCP. Here EST is used to instruct the switch to establish the backward connection. EST ACK confirms that the required connection has been established.
5. Here EST is used to instruct the switch to establish the forward connection.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.11.2.1 Benefits
|
The separation of switching and control functions offers the following benefits:
Architectural Flexibility: The separation of bearer from the control allows flexibility in locating the desired functions.(functions could either be centralised or distributed). For instance, the switching and call control functions performed by a circuit or packet switch can now be separated and located in physically distinct locations. The control functions (all or a part thereof) could be located in a “call control server”, which can provide the information necessary to appropriately route the bearer. Further, this allows the use of platforms designed specifically for the task being performed to be used. Dedicated platforms will allow easier and faster software development and less work will be involved in rolling out new software versions.
Efficient Utilisation of Network Resources Given that most of the traffic associated with a call is bearer traffic, optimal routing of bearers (facilitated by separating control from the bearer) allows efficient utilisation of network resources. For instance, call control may be routed to a “ Call Control server” for purposes of address resolution, billing, enabling of services, and others, but the bearer does not have to traverse through the call control server. Further, optimal routing can be maintained during mobility (the concept of an anchor MSC can be removed)since the bearers can be re-routed after a change in location. Optimising the routing in this way will have greater significance for UMTS calls which are likely to be high bandwidth and may also consist of multiple streams.
• Further optimal routing can be achieved in the case of call divert.
Bearer Flexibility and Robustness: The separation of bearer and control allows the communicating parties to negotiate the resources required (even possibly re-route the bearers) even after call setup has been completed. Bearers could be re-routed during a call due to a change in the performance required or to work around failure of network elements.
Future-Proof: The separation of bearers from control makes the protocols used more modular (than before). For instance, the same control protocols can be used over multiple transport technologies. Further, the same control protocol can be used for establishing multiple bearer types. This facilitates improvements in technologies being used with minimal impact.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.11.2.2 Drawbacks
|
Separation of switching and control means defining the interfaces between the various control functions (such as cal control, mobility management, session control, etc.) and the switching functions (i.e., switching matrix). For example in the case of a GSM MSC, this would mean defining an open interface between the MSC service switching functionality and the TDM switching matrix.
For packet data nodes, the separation might be more realistic as a client-server type of architecture is more natural in that domain. However, this is a deviation from the current GPRS and therefore may require additional standardisation effort.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.12 New Handover functionalities
|
The radio access network has to be capable of connecting to a variety of existing core networks. This leads to a requirement that the UTRAN will be allowed to connect with evolved forms of existing CNs. There will be the need to support new Handover functionalities between UMTS and 2G systems.
The support of multimedia services and the separation of Call Control and Connection Control (many connections: telephony, video, data could be associated with one single call and handed over separately), together with a micro or pico-cellular environment will cause increased complexity of Handovers compared with GSM.
Developments will be needed of the contemporary GSM/GPRS platforms to enable handover/cell reselection of communications between GSM/GPRS and UMTS. To enable this specific developments are needed for:
• Handover/cell reselection of communications which have inherent delay and error requirements (e.g. speech as for contemporary GSM circuit switched and speech/ video).
(This may be viewed as an equivalent of GSM circuit switched handover).
• Handover/cell reselection of communications which may not have inherent delay requirements but do have error requirements (e.g. packet data communications such as IP/GPRS, file transfer, SMS).
(This may be viewed as an equivalent of GPRS cell-reselection).
This also requires the ability to potentially ‘negotiate’ and modify communications parameters when handing over between GSM/GPRS and UMTS.
• It would be useful to provide new procedures in UMTS in order to make handover a totally Radio Resource Management procedure fulfilled as far as possible by the BSS without the intervention of the NSS part. The proposed interconnection of BSSs to allow for handover streamlining could be a step in this direction. (This may be difficult when performing hand-over between different environments, and a traditional GSM-like handover procedure is likely to be used in this case).
• It is likely that the network performance during handovers will be increased by restricting handover to the access network, leaving the core Network to deal with the Streamlining procedure without any real-time constraints. (In the case of a successful GSM inter-BSC handover, eight messages are exchanged real time on the A interface between the MSC and the two BSC; if Streamlining is used, this could be potentially reduced to two messages (Streamlining Request - Streamlining Acknowledge) with a significant saving in the signalling overhead.
As part of the overall QOS negotiation between user and network, mechanisms will be needed to enable parameters such as handover delay, jitter, packet/information loss/acceptable error etc. to be applied as part of the communications path requirements utilised during the communications ’session’.
A number of options are available to support handover within the UMTS Core Network; real time support within the core network, real time handover within the UTRAN with subsequent ‘streamlining’. Irrespective of the final mechanism developed within the UMTS Core Network for UMTS handover, functional developments are needed within the Core Networks (both GSM/GPRS and UMTS) to support handover between UMTS Core Networks and evolved GSM/GPRS core networks.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.13 Reduction of UMTS signalling
| |
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.13.1 Turbo Charger
|
The signalling load associated with subscriber roaming can be high when either the location areas are small or the subscriber travels significantly. The Turbo-Charger concept aims to optimise signalling associated with subscriber data management by assigning one MSC/VLR to perform the Call Control and Mobility Management functions while the subscriber remain attached or until signalling routes require further optimisation.
The benefits of the Turbo-Charger concept are:
• the substantial reduction in signalling traffic for subscribers located in the home PLMN,
• the substantial reduction in signalling traffic between the visited PLMN and the home PLMN,
• no new network nodes are required,
• applicable to a wide range of protocol used for the transfer of data.
The disadvantages of the turbo-charger concept are:
• Connections are required from the access network to be fully meshed to all MSCs in the turbo-charger area.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.13.1.1 Overview of the Turbo-Charger Concept
|
A Turbo-Charged network constitutes a network architecture designed to reduce mobility management costs and provide automatic load-sharing between MSC/VLRs.
The architectural philosophy is to equally divide the subscribers between the available MSC/VLRs, irrespective of their location. In the context of GSM, this could be achieved by placing a routing function (e.g. evolved STP) between the BSC and the pool of MSC/VLRs. The purpose of the routing function is to route A-interface messages to the MSC/VLR that is serving the mobile station. The solution requires the MS to store a discriminate that can be used to identify the serving MSC/VLR and for routing to be applied on this discriminate on the connection between the MSC/VLR and access network. A TMSI partitioning scheme could be utilised. This scheme allocates a sub-set of the TMSI range to each MSC/VLR, Figure X. The A-interface messages are then routed to the right MSC based on the TMSI. This could be done by a routing function external to the access network implying no access network modification (see figure x). If a TMSI partitioning scheme is used then new SIM cards are not required.
The temporary identity used for paging (TMSI) must be unique within all the MSCs in the turbocharger area. This implies that there must be a mechanism to ensure that this requirement is met for turbocharged MSCs (e.g. TMSI partitioning).
Two mechanism to provide load-sharing are envisaged, random load-sharing and dynamic load-sharing.
Random load-sharing requires the routing function to randomly assign a MSC/VLR to serve a particular mobile station when it first comes in to the network. Regardless of where the mobile is the same MSC/VLR will always serve it provided the mobile remains in the area served by all the turbocharged MSC/VLRs linked by the routing function.
In large metropolitan areas where subscribers are served by multiple MSC/VLRs, some MSC/VLRs may be very busy while others are not fully utilised. Dynamic load-sharing requires the implementation of an intelligent router. Since the routing function routes all A-interface traffic, it can participate in load-sharing and balancing based on the current loading of each MSC however linkage between MSC load and the routing algorithm would be required.
In the case of a Turbo-Charged network where the network is sub-divided into large regions, further optimisation can be achieved by adding the Super-Charger functionality.
Figure 17: Example of GSM Turbo-Charger Network Architecture
In the context of UMTS, the routing function becomes a feature of the RNC, see Error! Reference source not found..
Figure 18: Example of UMTS Turbo-Charger Network Architecture
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.13.2 Relationship between GLR and TurboCharger
|
The GLR and TurboCharger are two independent schemes for reducing the amount of MAP traffic generated in UMTS networks.
The GLR works by reducing traffic between PLMNs associated with Location Updates. This is achieved by "caching" the roaming subscriber's data in the visited network
The TurboCharger works by eliminating the need to perform location updates. The same VLR can hold a subscriber's data for the duration of his attachment to the network.
A TurboCharged network requires that each MSC/VLR can physically connect to all RNCs. Therefore TurboCharging may be best suited to areas of the network characterised by dense geographic coverage. On the other hand, the GLR function is independent of the network density.
The network structure illustrated in Error! Reference source not found. shows that the GLR and a TurboCharged area within the same PLMN are independent. In fact, it shows benefits from using the two techniques in the same network. The Turbo-Charger reduces the location registration signals between the MSC/VLR and GLR:
There is no new update location signal between MSC/VLR and GLR if roamer moves inside of the Region A.
There is no new update location signal between GLR and HLR if roamer moves between regions.
Figure 19.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.14 Transcoder Control
|
In order to improve voice quality for mobile-to-mobile calls (MS-MS calls) in GSM Phase 2+ networks, Tandem Free Operation (TFO) using in-band signalling has been specified. The equivalent function in Japan's PDC (Personal Digital Cellular) network is known as Transcoder Bypass, which has been specified to make use of out-of-band signalling control (i.e. by the PDC-MAP protocol).
It is likely that UMTS terminals will support a wider range of codecs than is currently the case for GSM terminals. In the case of calls between UMTS terminals, codec negotiation will be needed to:
• match terminal capabilities during call establishment
• support supplementary services interactions such as with conference/Multi-party calling, ECT, CFNRy
• support changes in radio interface conditions.
This requires control of the transcoder unit in the UMTS Core Network during (and after) call establishment and handover. However, the inband signalling technique currently specified for GSM-TFO has limitations in this area. For example:
• UMTS call setup; the GSM-TFO mechanism is designed to support a limited set of codecs. Each time a new codec is introduced into UMTS the transcoder would need to be upgraded.
• UMTS call in progress; codec negotiation using the GSM-TFO mechanism would need complex in band signalling.
The different solutions to support the required functionality for transcoder control in UMTS need to be studied in detail. Signalling for codec negotiation and control may be achieved by:
• New control mechanisms between the mobile terminal and the network based transcoder (out of band and in-band solutions need to be studied).
• Revisions to ISUP signalling.
• Revisions to MAP signalling.
• Inband signalling mechanism developed for AMR
It is for further study what impact transcoder control has upon networks external to the PLMN.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.15 Support of multimedia services
|
One of the most important requirements for UMTS is the capability of supporting multimedia services.
The following principles should guide and apply to the support of multimedia services in UMTS:
• Multimedia services in relation to UMTS should be standardised and handled according to emerging multimedia standards. SMG should not standardise multimedia services solely for UMTS networks. SMG should take advantage of existing and emerging main stream standards for multimedia, in reality defined outside of the UMTS.
• Multimedia applications according to such main stream standards should be supported (transported and handled) efficiently in the UMTS.
• Multimedia requirements on the UMTS should, as far as possible, explicitly be related to such multimedia application standards to be supported – rather than to generic statements or assumptions related to the architecture.
• The multimedia bearer capability requirements, incl. QoS, are expected to effect the core as well as the radio network.
Among others, two requirements for an efficient support for multimedia applications, which currently can not be achieved by GSM, are sufficient bandwidth allocation and flexibility of bearers.
• The bandwidth requirement relates to the transport technology used on (both the radio and network sides). In particular switching and transport capabilities within the network must be able to support, in an efficient and flexible way, air interface rates of at least up to 2 Mbit/s. It is unlikely that a 64 kbit/s based switching system will be able to do this in the most efficient manner.
• Separation of call control from connection and bearer control. This is an important requirement to satisfy the concept of Quality of Service for media components: a call/session may use various connections at any one particular instant (making use of one or several bearers). It should then be possible to add or remove bearers during such a call in order to cope with user needs or problems on the radio path. (Ref. ETS 22.01 Service Principles)
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.16 Support of services requiring variable bit rate
|
• If a number of applications use VBR data flows then packet transfer mode on the radio and network side has to be considered in order to make efficient use of resources.
• If packet transfer is allowed on the radio side, a finer degree of location management is/may be needed for radio resource optimisation (if only the LAI is used as in GSM, packets addressed to one single mobile terminal would need to be broadcasted over its entire Location Area; a new routing concept playing a similar role to the GPRS routing area is then needed).These additional Radio Resource/Mobility Management functions could be located in the Radio Access Domain, containing data strictly related to the access techniques that could be hidden from the serving network.
5.17 UMTS Simultaneous Mode.
Within GSM/GPRS Class A mobiles have been defined which support ‘simultaneous operation of both GPRS and other GSM services’. UMTS is intended to enable users to access a variety of communications features including access to PSTN/ISDN services/features as well as IP capability. The UTRAN developments have a mechanism to support common ‘pipe’ over the radio interface (the RRC Connection). It is expected that multi-media and mixed media (PSTN/ISDN/IP communications) will play a large part of UMTS communications.
From this perspective it is essential for UMTS that from day 1 of network launch that mobile terminals can support both PSTN/ISDN services and features as well as IP simultaneously. Based upon this aspect ‘Simultaneous mode’ has been defined for UMTS communications. This definition can be applied to both network and mobile terminals.
Simultaneous mode is defined as the support of active parallel CS and PS communications.
The UE has simultaneous PS MM Connected and CS MM Connected states when in UE simultaneous mode.
Note: The support of ‘Simultaneous mode’ should not prevent the operation of mobile terminals in solely CS MM or PS MM connected mode. Simultaneous mode capable terminals should be supported in CS service and PS service only capable networks. Operators may wish to just use 3G_MSC and/or 3G_GSNs if required.
The impact of supporting ‘Simultaneous mode’ operation of the UE needs to be addressed within the UMTS System as a whole. In particular, the impacts upon the UE, radio, UTRAN and Core Network nodes need to be assessed.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.18 GSM and UMTS cells in the same registration area
|
The concept of GSM and UMTS cells in the same registration area was introduced in order to minimize location update signaling when changing between GSM and UMTS systems. Especially, the lack of UMTS coverage, e.g. in-building coverage in urban or suburban areas, can lead mobiles frequently changing between GSM and UMTS systems. In such case, the common registration area concept is anticipated to reduce the signaling compared to GSM and UMTS cells in different registration areas.
Currently GPRS routing area updates cause serious disruption to the user plane traffic. This was acceptable in GPRS only because routing area updates would be rare events which should only occur at the borders of large, well planned geographic areas.
If GSM and UMTS routing areas are overlaid, it can be expected that many mobiles will change routing areas at rates greater than in GPRS. In such cases the (negative) impact on the quality and throughput of the data will be very significant. Placing UMTS and GSM cells in the same RA greatly alleviates this effect.
If the core network does not use the Gs interface then, while the mobile is performing a routing update in the GSM cell the mobile will not be pageable from the MSC. Frequent routing area updates will have a serious effect on mobile terminating call success rates. Note that implementing the Gs interface only really helps in the case that the GSM and UMTS cells use the same SGSN. Therefore, this pageability problem disappears when the UMTS and GSM cells are in the same RA.
Third generation needs to offer higher quality (eg higher MT call success rate) than second generation. Hence the capability to have GSM and UMTS cells in the same Registration Area is needed for at least CS traffic.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.18.1 Open issues
|
The following open issues, opportunities and challenges have been identified concerning this concept:
a) Security.
In UMTS both MS authentication and network authentication is planned to be implemented. Some solutions have been proposed for MS authentication, ciphering and integrity check during change from GSM to UMTS but not any for network authentication. However, all these issues need to be resolved in order to perform handover between UMTS and GSM (either on the MSC, or, on the SGSN side, or both) so it is a requirement that the issue is solved.
b) Network service capabilities.
The availability of network service capabilities should be indicated to the end user somehow in order to offer confidence in the cellular service. However, any communication that starts in GSM cells needs to be easily transferable to UMTS cells, and vice versa. Usage of a UMTS cell does not guarantee any particular data rate: the data rate will vary with, at least, range, load on the cell and interference levels. Thus merely being camped on a GSM or a UMTS cell will give no real indication of the services available from that PLMN - this is irrespective of whether or not the cells are in the same or different registration areas.
The most likely source of ‘network service capability’ information will come from the core network. As the mobile contacts the core network whenever it does a registration update, it seems sensible that we allow network operators the option to send “network service capability” information in MM (and GMM) messages sent to the mobile.
c) Terminal capabilities
Terminal capabilities have some affect on the service availability e.g. in a situation where a dualmode terminal makes an attach in UMTS and later on moves into GSM cell. If mobile is PS and CS attached in UMTS, it may need to detach either CS or PS in GSM (e.g. class C mobile).
d) Idle mode control
Within a particular visited network it can be expected that the Core Network will restrict some subscribers to only UMTS cells, restrict others to only GSM cells, and permit some to use both types of cell.
Mobility Management signalling (MM and GMM) needs to be developed so that the (dual mode) mobiles in idle mode adapt their cell reselection procedures according to the Core Network’s instructions.
e) Paging channels
When GSM and UMTS cells are in the same common registration area, the overall paging channel capacity is given by the minimum of the GSM paging channel capacity and the UMTS paging channel capacity. If the capacity of the two channels cannot be configured so that the UMTS paging capacity is larger or equal to that of the GSM channel, then paging capacity will be wasted. Note that UMTS paging channels with larger capacity than GSM paging channels probably do not cause any inefficiency (because under occupancy of the UMTS paging channel probably only leads to less radio energy being transmitted). Hence it is expected that UMTS paging channel capacity need to exceed or equal that offered by the GSM radio interface (in the cases of a GSM combined control channel and the case of a single GSM non-combined control channel). Note that this is relevant for both CS and PS domains.
In any case, in a common registration area GPRS pages are always sent also via UMTS paging channel, due to the nature of GPRS paging (CN paging). This may have some impact on paging channel capacity needed in UMTS.
5.19 Short Message Service Cell Broadcast in UMTS
The Short Message Service Cell Broadcast (SMS.CB) was defined as a UMTS Phase 1 requirement to guarantee the continuity of the corresponding GSM services. It shall be provided seamlessly (as far as the user or the users terminal equipment is concerned) across the UMTS and GSM network.
5.19.1 Network Architecture
Figure 22 proposes a straight forward adoption of the GSM cell broadcast architecture in UMTS.
The basic network structure replaces the GSM BSS with the UTRAN containing the RNC and the Node B. The cell broadcast center (CBC) is part of the core network and connected to a routing node e.g. a 3G SGSN via the Bc reference point. Thus the CBC can reach every RNC via the user plane of the Iu interface by using the newly introduced common communication channel. On the logical interface between the CBC and the RNC a mandatory protocol shall be defined. which should mainly be adopted from the corresponding GSM specification (see GSM 03.41). The other UTRAN related interfaces are described in the according UTRAN specifications based on the RAN 2 TR 25.925. Based on this architecture and the current requirements for cell broadcast the core network elements like MSC, VLR, HLR etc are not involved for the service delivery.
Figure 21: Architecture for SMS Cell Broadcast in UMTS
The protocol stack between the CBC and the RNC is given in figure 22. Protocol primitives for the cell broadcast application defined by GSM 03.41 are used for the Cell Broadcast application.
Figure 22: Common Communication Channel used by the Cell Broadcast Application
5.19.2 Interface Responsibilities
Interface 1 was not in the scope of GSM (see also GSM 03.41). At the moment it is ffs. if it should be standardized.
The interface between the CBC and the RNC is in the scope of T2 SWG3 (Messaging) as this group is continuing the work of the SMG4 Drafting Group Message Handling. Work has not yet started.
The needed changes to the Iu and Iub Interfaces is in the scope of RAN WG3 mainly.
The Uu Interface is fully under scope of RAN WG2 for layer 2 and 3 and RAN WG1 for layer 1 questions.
5.19 Use of Single MSISDN for CS and PS Voice Services
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
5.19.1 Introduction
|
Within release 99 it is a working assumption that existing and future multimedia protocols can be supported by the UMTS CC/SM as application layer protocols. Where terminals support voice over both CS and PS domains, MT calls currently would require separate MSISDNs. It is desirable to allow the use of a single MSISDN and allow the network to determine how to route the calls. The mechanisms described below allows the use of a single MSISDN. The mechanism shall not restrict the network to only supporting a single MSISDN.
5.19.2 Option 1
In overview, when an incoming call arrives from the PSTN, GMSC (gateway MSC) sends an enquiry, via HLR, to the VLR for the MSRN in order to route the call request to the serving MSC. Upon receiving this enquiry from HLR (containing the MSISDN of the called UE), VLR should be able to assign a MSRN based on the decision on how to terminate the call, i.e., either via CS or PS domain. The MSRN assigned will be different (in prefix, for example) so that the ISUP message can be sent to the serving MSC or the serving GK correspondingly.
In order to provide the capability for a user to be contactable for voice services via CS or PS domain using the same MSISDN, two enhancements are for-seen to the VLR.
• VLR needs to be able to store the UE’s capability as a VoIP terminal, and user’s preference of accepting a call via VoIP or CS call.
• VLR should be able to assign a MSRN based on the decision on how to terminate the call, i.e., either via CS or PS domain. The MSRN assigned will be different (in prefix, for example) so that the ISUP message can be sent to the serving MSC or the serving GK correspondingly.
Furthermore, each GK shall be associated with a single VLR, and shall be required to support a MAP-B (VLR-MSC) like interface. A VLR may however be associated with multiple GK.
Figure X illustrates in greater detail how the single number and path selection can be supported. It shows a scenario of incoming call from PSTN/ISDN domain to a roaming UE. The message flow is as follows:
1. Call request from ISDN in ISUP message, which contains MSISDN of the called party.
2. GMSC gets the request and issues a enquiry to HLR.
3. HLR, knowing the called UE is roaming, issue a enquiry to the VLR in the visiting network.
4. The VLR replies with a MSRN, which is associated with GK/Signalling-Gateway interface or MSC interface, depending on the path selected.
5. HLR relays the MSRN back to GMSC.
6. GMSC continues to route the call to the MSC or GK/SG in the visiting network:
6a: if the CS path is selected (reflected by the MSRN returned), the call is routed to the MSC. The message flows after that is not shown.
6b: if the PS path is selected, the call is routed to the GK/SG via PSTN/ISDN. The GK will then setup a call to the UE over PS domain via a PSTN/IP gateway. The message flow between GK and UE is not shown.
7. If the PS path is selected, the GK shall contact the VLR in order to provide the mobile identity (IMSI) for the MSRN.
Figure 23
Step 7 could further be enhanced to provide subscriber information pertaining to supplementary services, hence allowing common services to be provided to the user, regardless of the path (CS or PS) used to route the call.
5.19.3 Option 2
When an incoming call arrives from the PSTN, GMSC (gateway MSC) sends an enquiry to get a MSRN in order to route the call request to the servingnode. Upon receiving this enquiry from GMSC (containing the MSISDN of the called UE), HLR should be able to determine VLR that will assign a MSRN. This HLR determination of the VLR is based on the decision on how to terminate the call, i.e., either via CS or PS domain. The MSRN assigned will be different (in prefix, for example) so that the ISUP message can be sent to the serving MSC or the serving GK correspondingly.
In order to provide the capability for a user to be contactable for voice services via CS or PS domain using the same MSISDN, two enhancements are for-seen to the HLR.
• HLR needs to be able to store
• the user’s rights to use speech services using CS and / or PS domain
• user’s preference of accepting a call via VoIP or CS call.
• Upon user’s subscription and preference and upon the registration status of the UE (either registered on a MSC, on a GK or on both), the HLR chooses a VLR (either VLR of the MSC or VLR of the GK) whom to request a roaming number from. If due to user detach or due to internal load, the first chosen VLR does not allocate a roaming number, then the HLR requests (if allowed by user’s subscription) a roaming number from the VLR of the other domain (if the address or the VLR of the other domain is known to the HLR)
Figure X illustrates in greater detail how the single number and path selection can be supported. It shows a scenario of incoming call from PSTN/ISDN domain to a roaming UE. The message flow is as follows:
1. Call request from ISDN in ISUP message, which contains MSISDN of the called party.
2. GMSC gets the request and issues an enquiry to HLR.
3. HLR, knowing where the called UE is roaming as well as the user’s subscription and preferences, determines the VLR associated with GK/Signalling-Gateway interface (3b) or MSC (3a) in the visiting network and issues an enquiry for a roaming number.
4. The VLR replies with a MSRN. (4a if the VLR is the VLR of the MSC, 4b if it is the VLR of the GK)
5. HLR relays the MSRN back to GMSC.
6. GMSC continues to route the call to the MSC or GK/SG in the visiting network:
6a: if the CS path is selected (reflected by the MSRN returned), the call is routed to the MSC. The message flows after that is not shown.
6b: if the PS path is selected, the call is routed to the GK/SG via PSTN/ISDN. The GK will then setup a call to the UE over PS domain via a PSTN/IP gateway. The message flow between GK and UE is not shown.
Figure 24
The VLR of the GK had previously updated its location to get subscriber information pertaining to supplementary services, hence allowing common services to be provided to the user, regardless of the path (CS or PS) used to route the call and to give its address to the HLR.
5.19.4 Option 3
This chapter describes an architecture and exemplifying call flows for inter-service roaming for Telephony as classical TeleService Speech in GSM/UMTS networks and Telephony as the voice component of a MultiMedia service. The chapter is intended to show the reasons and principles of the proposed architecture.
Terminology
• Personal Number Domain. An optional architecture that is overlaid over the GSMisdn Domain and the IP MultiMedia Domain to support user reachability according various criteria such as Network domain attachment(s), user preferences, incoming traffic characteristics etc.
• Personal Number Service. The service supporting reachability across Network Domains.
• Personal Number Function (PNF). The function performing the routing control.
• InterroGation Function (IGF). A call processing function that routes call to the appropriate Network Domain based on interrogation of the Personal Number Function.
Architectural overview:
Figure 25: The Personal Number Domain architecture
Here it is proposed to provide this functionality overlaid as a Personal Number service, typically occurring in the home environment. The reason for this is to keep as loose as possible coupling between the GSMisdn Domain and the IP MultiMedia domain. The aim is to avoid disturbing the user experience in the tremendous growth in GSMisdn Domain deployment and to avoid restrictions and delays for the development of the IP MultiMedia domain. The need for the functionality may vary as coverage for the IP MultiMedia service becomes more complete- looking to a distant future, this overlaid routing function may not be needed at all. Seen from the all IP network, the GSM Speech fall-back could be seen as an architectural exception, however for years to come commercially very important.
Based on these extensive flexibility requirements we propose the overlaid approach rather than to implement the functionality into the core of both Network Domains. Thus we have rejected any solution where the IP MultiMedia Domain regards the GSMisdn network as a visited network due to associated complex mappings user profiles. The reason is the necessary freedom for new innovative add-on services within the IP MultiMedia Domain which would become impossible to map transparent enough into GSMisdn services.
In line with the VHE/OSA approach, we propose to implement capabilities in both domains to report routing impacting events to the Personal Number Domain. This may also be complemented by direct (network transparent) interaction from the mobile or the user.
This approach allows for maximum control power to the home environment on the design of the routing algorithms, to make them customised per user, to change them by time etc. Even if use of a single reachable number creates the need, nothing restricts using the concept for other cases as well and even expand it to a full fledged add-on services/applications concept, as desired by each operator
It is also assumed that the Personal Number Domain is regarded optional in the architecture. e.g. for a situation where there is not need for a fall-back from the IP MultiMedia service to the GSMisdn Domain Teleservice Speech, the discrimination of users to various IP accesses shall also be possible within the IP Multimedia domain.
The Personal Number Domain is suggested as a call processing Personal Interrogation Function linked into the call chain (thus not excluding sequential or parallel hunting algorithms) and a Personal Number Function hosting the user preferences, visited network domain(s) etc. as well as the algorithms for routing decisions. Thus, the service can be introduced with minimal coupling to the Network Domains. The needed adaptation of the served underlying networks is the capabilities to report routing impacting events to the Personal Number Function. This approach is aligned with the VHE/OSA concept of UMTS and allows for re-using these capabilities for any kind of services/applications.
The Personal Interrogation Function may not be identical when interfacing the GSMisdn Domain and the IP MultiMedia domain due to the very different environment, these details are for further study.
Call handling
In the next following sections a few principle call scenarios are shown to highlight how packet and circuit calls interact with respect to the one MSISDN concept. In the examples that follow, H.323 is named just as an IP multimedia example.
It is here assumed that the home PLMN makes the interrogation towards the Personal Number service, which determines the called user’s call reception point preference based on a one MSISDN scheme. The split of CSCF into a visiting and home CSCF has not been considered herein. Optimal routing is not considered either, but remains for further study.
Registration of a CS/PS Mobile Terminal in an R00 Network
Above is shown how a CS/PS mobile terminal e.g. at power on makes three types of registrations. One is a circuit registration, one is a GPRS registration, and one is an IP multimedia e.g. H.323 registration. The latter is done within the GPRS user plane. The HLR indicates to the Personal Number Function that the user is available for CS speech calls. The CSCF indicates to the Personal Number Function that the user is available for IP multimedia voice calls.
PSTN -> Mobile Subscriber IP Multimedia Voice Call
Above figure shows an incoming call from PSTN to a mobile subscriber who wants telephony calls as IP multimedia voice calls. The SSP together with the CSE/SCE functions makes up the IGF as described above in chapter 1. Of course the SSP can be realised as an SSF within some other network element.
1) Incoming call from PSTN is received in the SSP
2) SSP informs CSE/SCF
3) CSE/SCF interrogates the personal number server for routing instructions based on incomming MSISDN.
4) A routing number is returned (MSISDN with IP multimedia prefix) in SSP which forwards the call to the SGW
5) SGW translates ISUP/STM to ISUP/IP towards MGCF
6) MGCF allocates resources from the MGW
7) MGCF translates the ISUP signalling to H.323 towards CSCF/GK
8) CSCF/GK checks the user’s service profile and thereafter routes the IP MM call over GPRS onto the terminal.
PSTN -> Mobile Subscriber Roaming in a GSM Only Network
Above figure shows an incoming speech call from PSTN to a mobile subscriber who is registered under a GSM only PLMN.
1) Incoming call from PSTN is received in the SSP
2) SSP informs CSE/SCF
3) CSE/SCF interrogates the personal number server for routing instructions based on MSISDN
4) A routing number (MSISDN with CS prefix) is returned in SSP which forwards the call to the GMSC
5) GMSC requests routing information from HLR
6) HLR requests roaming number from VLR
7) HLR returns a roaming number to GMSC
8) GMSC forwards the call via PSTN to the destination NW
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
6 Interoperability between GSM and UMTS
|
• Transparency [from a users perspective] of roaming and handover
• Re-use of existing subscription profiles
Note: This list is not exhaustive and is FFS.
This allows easier management and deployment of a new UMTS network.
UMTS is a system supporting handovers between GSM and UMTS in both directions. To support these handovers effectively, the following is required from a dual mode MS/UE supporting simultaneous ISDN/PSTN and packet service in GSM/UMTS:
Depending upon the solution adopted for GSM-UMTS handover, the MS/UE supporting simultaneous ISDN/PSTN and packet service may be required to perform appropriate update into CN depending on the activity of the UE once the handover between GSM and UMTS is completed. This update is needed to avoid any severe interruptions on the accessibility of packet services after the handover.
The nature of the update to be made after the handover in both direction, i.e., from GSM to UMTS and from UMTS to GSM, from MS/UE depends on the activity of the UE in the following way:
ISDN/PSTN connection: RA update only (if RA is changed)
Packet connection: LA and RA update (if RA and LA are changed)
Both ISDN/PSTN and packet connection: RA update only (if RA is changed)
If the RA, LA or both LA and RA are not changed the MS/UE behaviour is for further study
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
6.1 Circuit Switched Handover and Roaming Principles
|
Introduction of a UMTS Core Network necessitates the inter-connection with legacy systems to allow inter-PLMN roaming and handover.
For ease of convergence with the existing networks and the introduction of dual mode handsets, roaming and handover to/from UMTS should be performed in the simplest manner that requires as little change as possible to the legacy networks and standards, i.e. inter-MSC handover functionality.
These principles provide - from a user perspective - transparency of handover and roaming. In addition, operators providing UMTS services should also allow access to legacy networks using existing subscriber profiles and network interfaces.
Illustrated in Figure 17 shows the introduction of a UMTS Core Network for UMTS phase 1 network configuration. Notice that it leaves the current GSM specifications mainly untouched whereupon the UMTS core network acts towards the GSM MSC like a GSM MSC by providing for example MAP/E for handover purposes. Further, it should be observed that GSM subscriptions belong to the HLR whilst UMTS subscriptions exist in the HLR release 99..
Figure 20 Inter-Operability between GSM and UMTS
Note: No physical implementation should be taken from the figure. As a further note, no interworking functions are shown to ease clarity, but however should not be precluded.
From Figure 17 it can be seen that the information exchanged over the Iu must provide the necessary parameters to enable the core networks to communicate via for example the MAP interface for handover purposes.
Also note that from the above diagram, existing interfaces are used towards the HLR to allow for subscription management based on today's principles using the already defined user profile, providing seamless roaming between the 2nd generation system and UMTS.
The existing GSM handover procedures should be re-used to minimise the effects on existing GSM equipment (figure 1).
The anchor concept in GSM for inter-MSC handover should be used for inter-system handover between UMTS and GSM.
The signalling over the A-interface and over the MAP/E-interface should be the same as in GSM
phase 2+ with possibly addition of some new or updated information elements in some messages.
For the set up of the handover leg (user plane) standard ISUP/POTS should be used in line with the principles used in GSM.
The control signalling over the Iu-interface at handover between UMTS and GSM should be based on the A-interface signalling at inter-MSC handover in GSM.
The signalling over the Iu-interface at call set up to/from a dual mode UMTS/GSM mobile station, shall include GSM information elements needed for handover from UMTS to GSM.
In the corresponding way the signalling over the A-interface at call set up to/from a dual mode UMTS/GSM mobile shall include UMTS elements needed for handover from GSM to UMTS.
The data are needed to initiate the handover towards the new BSS/RNC.
• A target cell based on CGI is sent to the MSC from UTRAN at handover from UMTS to GSM. The CGI points out the target MSC and target BSC.
The target "cell" identifier for UMTS at handover in the direction GSM to UMTS is for further study.
• 6.1.1 UMTS to GSM handover for circuit switched services
• The signalling sequence in figure 1 shows the case when the UMTS MSC (UMSC) and the GSM MSC are located in separate "physical" nodes.
• If the UMSC and MSC are located within the same "physical" node, no MAP signalling and no ISUP signalling are needed between UMSC and MSC.
• For release 99 it is expected that the codec is placed in the anchor or non-anchor UMSC (for the UE in UMTS mode), which will have no impact on the signalling.
• Note: Handling of the user plane is FFS.
•
Figure 21. UMTS to GSM handover for circuit switched services e.g. voice
SRNS initiates the preparation of UMTS to GSM Handover by sending the RANAP message Handover Required to UMSC. This message includes parameters such as Target cell identification and Serving cell identification, both in the form of CGI according to GSM.
UMSC requests MSC to prepare for UMTS to GSM Handover, by sending the MAP message PREPARE HANDOVER request. The message contains a BSSMAP message Handover Request, to be sent from MSC to BSS. It includes data such as Target and Serving CGI received from the Handover Required message, and data stored in UMSC indicating type of radio resources required.
MSC sends the BSSMAP message Handover Request to BSS which then allocates necessary radio resources in BSS.
When BSS has allocated necessary radio resources it sends the BSSMAP message Handover Request Acknowledge. This message contains all radio-related information that the UE needs for handover, i.e. a complete GSM Handover Command message to be sent transparently via MSC, UMSC, and SRNS to UE.
MSC acknowledges handover preparation by sending the MAP message Prepare Handover Respons to UMSC, including a complete GSM Handover Command message.
UMSC sends the ISUP message IAM to MSC to establish a circuit ISUP connection between UMSC and MSC.
As acknowledgement to IAM, MSC sends the ISUP message ACM back to UMSC.
UMSC sends the RANAP message Handover Command to SRNS, including a complete GSM Handover Command message to be sent to UE.
SRNS sends the RRC message Inter-System Handover Command to UE, including a complete GSM handover Command message, to order the UE to start the execution of handover.
Upon detection of UE in BSS, (by reception of the Layer1 GSM message Handover Access from the UE), which indicates that the correct UE has successful accessed the radio resource in the target GSM cell, the BSSMAP message Handover Detect is sent from BSS to MSC. MSC may use this condition to switch the connection to the BSS.
MSC sends the MAP message PROCESS-ACCESS-SIGNALLING request to UMSC, including the BSSMAP message Handover Detect. UMSC may use this message as trigger point for switch of the connection to the MSC.
To complete the ISUP signalling the ISUP message ANM is sent from MSC to UMSC.
After Layer 1 and 2 connections are successfully established, the UE sends the GSM message Handover Complete to BSS.
After completed handover, BSS sends the BSSMAP message Handover Complete to MSC.
MSC sends the MAP message SEND-END-SIGNAL request to UMSC, including the BSSMAP message Handover Complete.
UMSC initiates release of resources allocated by the former SRNS.
SRNS acknowledges release of resources.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
6.2 Packet Switched Handover and Roaming Principles
|
The introduction of a UMTS core Network as described in section 11.1 illustrates the requirement for inter-connection with the legacy GSM system to allow inter-PLMN roaming and handover.
Even though there is no current GPRS deployment, the operator may decide to deploy a GPRS network prior to the deployment of a UMTS network. Therefore, the introduction of a UMTS Core Network may require to be inter-connected to the legacy packet network.
As in the circuit switched case, roaming and handover to/from UMTS should be performed in the simplest manner that requires as little change as possible to the GPRS network and standards, i.e. inter-GSN handover functionality. In addition, access is provided to the GPRS network using the existing subscriber profiles and current network interfaces.
A similar figure to Figure 17 is illustrated in Figure 19. Notice that it also leaves the current GPRS specifications mainly untouched whereupon the UMTS core network acts towards the GSN like a GSN by providing for example Gn. Further, it should be observed that GPRS subscriptions belong to the HLR whilst UMTS subscriptions exist in the HLR release 99.
Figure 22 Inter-Operability between GSNs and UMTS
Note: No physical implementation should be taken from Figure 19. As a further note, no interworking functions are shown to ease clarity, but however should not be precluded.
From Figure 19 it can be seen that to provide inter-working between legacy packet switched and UMTS packet switched services, the information exchanged over the Iu must provide the necessary parameters to enable the core networks to communicate via for example the Gn interface for handover purposes.
Also note that from the above diagram, the same principles are used as in the circuit switched services to provide seamless roaming.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
6.2.1 Implications
|
The active PDP context resides in the same GGSN even after a handover between GSM and UMTS (both directions). This corresponds in principle to the anchor concept on the circuit switched side, but note that whereas packet sessions are long lived, the anchor MSC remains only for the duration of a CS call (typically much shorter than a packet session).
Assuming an internal structure in UMTS CN that contains logical GGSN and SGSN nodes, the signalling over the inter-system GGSN-SGSN interface should be a joint evolution of Gn for the GSM system and UMTS. I.e., when Gn evolves in the sequence of GSM releases, Gn should include any new or updated information necessary for interoperation.
The corresponding SGSN-SGSN inter-system interface (also Gn) should also be evolved together. However, in this case the changes relative to the current GPRS release may possibly be more profound.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
6.2.2 Signalling procedures
|
The signalling procedures shows how handover UMTS <-> GSM GPRS can be done. The parameters carried by each message is not complete and shall be seen as examples of important information carried be the messages.
The signalling sequences shows the case when the UMTS 3G_SGSN and the GPRS 2G_SGSN are located in separate “physical” nodes.
If the 3G_SGSN and 2G_SGSN are located within the same "physical" node, no signalling are needed between 3G_SGSN and 2G_SGSN.
For handover in the UMTS to GSM GPRS direction the intention is to re-use the handover principles of GSM GPRS today in order to limit the changes in GSM GPRS and to take the changes if any on the UMTS side. The below specified messages is standard GSM 2+ messages (when applicable)
Handover from UMTS to GSM GPRS
Figure 23: UMTS to GSM GPRS, Inter SGSN Routing Area Update Procedure
The UE [2] or UTRAN [2] decides to perform handover which leads to that the UE switch to the new cell under the new system.
The UE sends a Routing Area Update Request (old RAI, old P-TMSI) to the new 2G_SGSN. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the 2G_SGSN.
The new 2G_SGSN sends SGSN Context Request (old RAI, old P-TMSI, New SGSN Address) to the old 3G_SGSN to get the MM and PDP contexts for the UE (The old RAI received from the UE is used to derive the old 3G_SGSN address). The old 3G_SGSN responds with SGSN Context Response (MM Context, e.g. IMSI, PDP Contexts, e.g. APN).
Security functions may be executed.
The new 2G_SGSN sends an SGSN Context Acknowledge message to the old 3G_SGSN. This informs the old 3G_SGSN that the new 2G_SGSN is ready to receive data packets belonging to the activated PDP contexts.
The new 2G_SGSN sends Update PDP Context Request (new SGSN Address) to the GGSN concerned. The GGSN update their PDP context fields and return Update PDP Context Response.
The new 2G_SGSN informs the HLR of the change of SGSN by sending Update GPRS Location (SGSN Number, SGSN Address, IMSI) to the HLR.
The HLR sends Cancel Location (IMSI) to the old 3G_SGSN. The old 3G_SGSN removes the MM and PDP contexts.
The old 3G_SGSN acknowledges with Cancel Location Ack (IMSI).
The old 3G_SGSN request the SRNS to release the radio resources by sending Bearer Release. The SRNS responds with Bearer Release Response.
The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new 2G_SGSN. The 2G_SGSN constructs an MM context for the UE and returns an Insert Subscriber Data Ack (IMSI) message to the HLR.
The HLR acknowledges the Update Location by sending Update GPRS Location Ack (IMSI) to the new 2G_SGSN.
The new 2G_SGSN validates the UE's presence in the new RA. The new 2G_SGSN constructs MM and PDP contexts for the UE. A logical link is established between the new 2G_SGSN and the UE. The new 2G_SGSN responds to the UE with Routeing Area Update Accept (P‑TMSI).
The UE acknowledges the new P‑TMSI with a Routing Area Update Complete (P‑TMSI).
Note 1: The functionality for forward of packets and handling of GTP sequence numbers is a subject fore more investigation, i.e. FFS.
Handover from GSM GPRS to UMTS
Figure 24: GSM GPRS to UMTS, Inter SGSN Routing Area Update Procedure
The UE/network decides to perform handover which leads to that the UE switch to the new cell, details for this is FFS.
The UE sends a x_Routing Area Update Request (old RAI, old P-TMSI) to the new 3G_SGSN. The SRNS shall add an identifier of the area where the message was received before passing the message to the 3G_SGSN.
The new 3G_SGSN sends SGSN Context Request (old RAI, old P-TMSI, New SGSN Address) to the old 2G_SGSN to get the MM and PDP contexts for the UE (The old RAI received from the UE is used to derive the old 2G_SGSN address). The old 2G_SGSN responds with SGSN Context Response (MM Context, e.g. IMSI, PDP Contexts, e.g. APN).
Security functions may be executed.
The new 3G_SGSN request the SRNS to establish of a radio access bearer by sending Bearer Setup to the SRNS. The SRNS responds with Bearer Setup Response.
The new 3G_SGSN sends an SGSN Context Acknowledge message to the old 2G_SGSN. This informs the old 2G_SGSN that the new 3G_SGSN is ready to receive data packets belonging to the activated PDP contexts.
The new 3G_SGSN sends Update PDP Context Request (new SGSN Address) to the GGSN concerned. The GGSN update their PDP context fields and return Update PDP Context Response.
The new 3G_SGSN informs the HLR of the change of SGSN by sending Update GPRS Location (SGSN Number, SGSN Address, IMSI) to the HLR.
The HLR sends Cancel Location (IMSI) to the old 2G_SGSN. The old 2G_SGSN removes the MM and PDP contexts.
The old 2G_SGSN acknowledges with Cancel Location Ack (IMSI).
The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new 3G_SGSN. The 3G_SGSN constructs an MM context for the UE and returns an Insert Subscriber Data Ack (IMSI) message to the HLR.
The HLR acknowledges the Update GPRS Location by sending Update Location Ack (IMSI) to the new 3G_SGSN.
The new 3G_SGSN validates the UE's presence in the new RA. The new 3G_SGSN constructs MM and PDP contexts for the UE. A logical link is established between the new SGSN and the UE. The new 3G_SGSN responds to the UE with x_Routing Area Update Accept (P‑TMSI).
The UE acknowledges the new P‑TMSI with a x_Routing Area Update Complete (P‑TMSI).
Note 1: The functionality for forward of packets and handling of GTP sequence numbers (within the box) is a subject fore more investigation, i.e. FFS.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
7 Network Migration And Evolution
|
The installed base of GSM networks will be very comprehensive at the time of the UMTS roll out. These GSM networks will co-operate very closely with and in many cases be partly integrated into the overall UMTS network. Thus network migration and evolution is a very fundamental aspect to consider when standardising UMTS.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
7.1 Network Migration Scenarios
|
A number of principally different network migration scenarios can be envisioned, e.g.:
• GSM to GSM release 99 (GSM operator with no UMTS licence and no UMTS roaming/handover agreements).
• GSM to GSM release 99 with support for dual mode ‘UMTS visitors’ (GSM operator with no UMTS licence but with UMTS roaming/handover agreements).
• GSM to GSM/UMTS (GSM operator with a UMTS licence).
• UMTS only PLMN (new UMTS operator with GSM roaming/handover agreements). This scenario is more a matter of network ‘compatibility’ rather than network migration.
A basic assumption is that the provision of UMTS services in most cases will start, from a radio coverage point of view, within ‘islands in a sea of GSM BSS’.
7.2 network migration and evolution requirements
1) The UMTS standard shall consider all aspects of network migration and shall describe the migration process from GSM release 98 to UMTS/GSM release 99, including the aspect of partly updated networks and its consequences on end-user services etc.
2) While fulfilling the SMG1 requirements the UMTS standard shall aim at minimising the impact on the existing GSM networks delivering only GSM. It is recognised that GSM/GPRS standards will need developments for UMTS however these should not adversely impact the networks that offer GSM only.
3) It shall be possible to perform the network migration process of a PLMN independently of co-operating PLMNs.
4) It shall be possible to gradually migrate a PLMN, i.e. the UMTS standard shall allow network elements compliant with different GSM releases to co-exist within a PLMN.
5) The impact on end-user service level for partly updated PLMN(s) is FFS.
6) Internetworking within a PLMN as well as between different PLMNs shall allow operators to utilise current backbone networks (dedicated for GSM traffic only or carrying non-mobile traffic as well according to non-PLMN specific standards).
7) A GSM/UMTS mobile terminal shall be reachable from an external network (PSTN/ISDN, IP, X.25) regardless of the mobile terminal being served by BSS or UTRAN.
8) A terminal in an external network, as well as the external networks themselves, shall not need to know if the GSM/UMTS mobile terminal is served by BSS or UTRAN.
9) The user equipment shall not need to change the E.164 or IP address at handover between UTRAN and BSS.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8 Protocol Architecture
| |
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1 IU Signalling Bearer Requirements for IP Domain
| |
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.1 Connectionless and Connection Oriented Services
|
Connection-oriented and connection-less IU Signalling Bearers are required.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.2 Dynamic Bandwidth Allocation
|
The IU Signalling Bearer shall support rapid and flexible allocation and de-allocation of IU transport resources.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.3 Reliable Transfer
|
The IU Signalling Bearer shall provide reliable delivery of signalling data.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.4 Flow Control
|
The IU Signalling Bearer shall provide throttling mechanisms to adapt to intermittent congestion in the UTRAN or Core Network.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.5 Redundancy and Load Sharing
|
To handle detected failures and signalling data congestion, the IU Signalling Bearer shall be capable of dynamically routing over alternate routes that minimise delay. If the delay metrics over alternative routes are identical, the IU Signalling Bearer shall be capable of spreading traffic over the identical paths, thus performing load sharing.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.6 Large Pdu Size
|
To support large transactions, it is important for the IU Signalling Bearer to provide a Signalling Data Unit size, large enough to allow for all signalling messages to be transferred without fragmentation.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.7 Signalling Bearer Management
|
To support supervision of IU Signalling Bearers, mechanisms for managing IU Signalling Bearers shall be used to provide status information to the RANAP for individual UE(s). The signalling bearer shall also maintain a consistent UE Activation State in the access and the core network.
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
8.1.8 Transport Media Independence
|
The IU Signalling Bearer shall be independent of the underlying transport media (e.g. ATM).
|
6e5fdf15efa25f132d2e779f583f3558
|
23.920
|
9 History
|
Document history
V1.0.0
June 1999
Creation of document from 23.20, all sections except 7
V2.0.0
June 1999
Some editorial changes in order to prepare the document for the approval by the TSG SA, June 1999 meeting
V3.0.0
July 1999
Template changed, clauses and sub-clauses numbering corrected, administrative clauses added.
v.3.1.0
October 1999
Incorporation of all the Change Requests approved at TSG SA#5
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
1 Scope
|
The present document identifies the parameters of the access stratum part of the UE radio access capabilities. Furthermore, some reference configurations of these values are defined. The intention is that these configurations will be used for test specifications.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
2 References
|
[1] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) protocol".
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply:
UE User Equipment
UMTS Universal Mobile Telecommunication System
UTRAN UMTS Terrestrial Radio Access Network
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4 UE radio access capability parameters
|
In the following the UE radio capability parameters are defined. In addition the relevant RRC configuration parameters are shown when applicable. When using the RRC configuration parameters, UTRAN needs to respect the UE capabilities. Only parameters for which there is a need to set different values for different UEs are considered as UE capability parameters. Therefore, the capabilities that are the same for all UEs, including baseline capabilities, are not listed here.
UTRAN is responsible for the respect of the UE capabilities when configuring the RBs. Actions in the UE when capabilities are in conflict with a UTRAN request are specified in RRC.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.1 PDCP parameters
|
Header compression algorithm supported
Defines whether header compression algorithms will be supported by the UE. If it will be supported it will be the RFC 2507 as specified in 3GPP TS 25.323.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.2 BMC parameters
|
No UE radio access capability parameters identified.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.3 RLC parameters
|
NOTE: It is FFS whether some of the RLC functions should be considered as UE capabilities.
Total RLC AM buffer size
The total buffer size across all RLC AM entities puts requirements on memory.
UTRAN controls that the UE capability can be fulfilled through the following parameters:
1. The number of RLC AM entities configured (no explicit RRC parameter);
2. UL PU size;
3. Transmission window size (#PUs);
4. Receiving window size (FFS whether this is configurable).
The following criterion must be fulfilled in the configuration:
where i is the RLC "entity number"
Maximum number of AM entities
The number of AM entities affect the main part of the total processing and memory capacity to be shared between different RLC machines.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.4 MAC parameters
|
No capability parameters identified.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5 PHY parameters
| |
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.1 Transport channel parameters in downlink
|
Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant
NOTE: "Being received" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels received by the UE. "Arbitrary time instant" means that the time instant corresponding to the highest sum of number of bits is relevant. This note also applies to similar parameter definitions below
This parameter is defined as:
i(Ni)
where Ni is defined as the number of bits in transport block #i, and the sum is over all transport blocks being received at an arbitrary time instant. All transport blocks that are to be simultaneously received by the UE on DCH, FACH, PCH and DSCH transport channels are included in the parameter.
A UE does not need to support a TFC within the TFCS for which the sum of Number of Transport Blocks * Transport Block size over all simultaneous transport channels is larger than what the UE capability indicates.
Maximum sum of number of bits of all convolutionally coded transport blocks being received at an arbitrary time instant.
This parameter is defined similar to the parameter above, but the sum includes only convolutionally coded transport blocks.
Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant.
This parameter is defined similar to the parameter above, but the sum includes only turbo coded transport blocks.
Maximum number of simultaneous transport channels
This is defined as the maximum number of Transport Channels that should be possible to process simultaneously, not taking into account the rate of each Transport Channel.
The number of simultaneous transport channels affects how the total memory space and processing capacity can be shared among the transport channels.
A UE does not need to support more simultaneous transport channels than the UE capability allows for.
Maximum number of simultaneous CCTrCH
CCTrCH should be interpreted as CCTrCH of any type, i.e. consisting of DCH, FACH or DSCH.
Maximum total number of transport blocks received within TTIs that end within the same 10 ms interval
All transport blocks that are to be simultaneously received by the UE on DCH, FACH, PCH and DSCH transport channels are included in the parameter.
Relates to processing requirements for CRC in downlink.
A UE does not need to support a TFC within the TFCS for which the sum of Number of Transport Blocks is larger than what the UE capability indicates.
Maximum number of TFC in the TFCS
The maximum number of TFC in a TFCS sets the size of the TFCI to TFCS mapping table to be handled by the UE.
Maximum number of TF
The maximum total number of downlink transport formats the UE can store.
Support for turbo decoding
Defines whether turbo decoding is supported or not.
The UTRAN configuration parameter is Type of channel coding which is part of the Transport format set (TFS) of each transport channel.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.2 Transport channel parameters in uplink
|
Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant
NOTE: "Being transmitted" refers to all bits in the active TFC within the TFCS over all simultaneous transport channels transmitted by the UE. "Arbitrary time instant" means that the time instant corresponding to the highest sum of number of bits is relevant. This note also applies to similar parameter definitions below.
This parameter is defined as:
i(Ni)
where Ni is defined as the number of bits in transport block #i, and the sum is over all transport blocks being transmitted at an arbitrary time instant.
This parameter is related to memory requirements for uplink data received from MAC before it can be transmitted over the radio interface. As shown in Figure 4.1 the worst case occurs for the maximum TTI.
A UE does not need to support a TFC within the TFCS for which the sum of Number of Transport Blocks * Transport Block size over all simultaneous transport channels is larger than what the UE capability indicates.
Maximum sum of number of bits of all convolutionally coded transport blocks being transmitted at an arbitrary time instantThis parameter is defined similar to the parameter above, but the sum includes only convolutionally coded transport blocks.
Maximum sum of number of bits of all turbo coded transport blocks being transmitted at an arbitrary time instant
This parameter is defined similar to the parameter above, but the sum includes only turbo coded transport blocks.
Maximum number of simultaneous transport channels
The number of simultaneous transport channels affects how the total memory space and processing capacity can be shared among the transport channels.
UTRAN shall not set up more simultaneous transport channels than the UE capability allows for.
Maximum number of simultaneous CCTrCH
TDD only. For FDD there is always only one CCTrCH at a time.
Maximum total number of transport blocks transmitted within TTIs that start at the same time
Relates to processing requirements for CRC in uplink.
A UE does not need to support the TFC within the TFCS for which the sum of Number of Transport Blocks is larger than what the UE capability allows for.
Maximum number of TFC in the TFCS
The maximum number of TFC in a TFCS sets the size of the TFCI to TFCS mapping table to be handled by the UE.
Maximum number of TF
The maximum total number of uplink transport formats the UE can store.
Support for turbo encoding
Defines whether turbo encoding is supported or not.
The UTRAN configuration parameter is Type of channel coding which is part of the Transport format set (TFS) of each transport channel.
Figure 4.1: UE transport channel processing limitations in uplink
NOTE: When CPCH is supported, then simultaneous DPCCH & SCCPCH reception is needed.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.3 FDD Physical channel parameters in downlink
|
Maximum number of DPCH/PDSCH codes to be simultaneously received
Defines the number of codes the UE is capable of receiving in parallel. For DPCH in soft/softer handover, each DPCH is only calculated once in this capability. The capability does not include codes used for S-CCPCH.
Maximum number of physical channel bits received in any 10 ms interval (DPCH, PDSCH, S-CCPCH)
Defines the number of physical channel bits the UE is capable of receiving. For DPCH in soft/softer handover, each DPCH is only calculated once in this capability.
The number of DPCH channel bits indicates the capability for normal, un-compressed mode.
The parameter also indicates the capability of the UE to support compressed mode by spreading factor reduction. For parameter values up to and including 9600 bits, the UE shall also be able to support compressed mode by SF reduction when operating in normal mode, at any value up to the reported capability. For parameter values greater than 9600 bits, the UE shall be able to support compressed mode by spreading factor reduction when operating, in normal mode, at any value up to half the reported capability or 9600bits, whichever is greater.
Support for SF 512
Spreading factor 512 should not be mandatory for all UEs.
The corresponding configuration parameter is Spreading factor which is part of Downlink DPCH info.
Support of PDSCH
Support of PDSCH is only required for some RAB realizations, and is therefore a UE capability.
The corresponding configuration parameter is Downlink transport channel type, which is part of RB mapping info.
Simultaneous reception of SCCPCH and DPCH
Simultaneous reception of SCCPCH and DPCH, i.e. simultaneous reception of FACH and DCH is required for e.g. DRAC procedure, but it should not be mandatory for all UEs (e.g. speech only UEs).
There is no specific configuration parameter.
Simultaneous reception of SCCPCH, DPCH and PDSCH
Simultaneous reception of SCCPCH, DPCH and PDSCH, i.e. simultaneous reception of FACH, DCH and DSCH is required for e.g. simultaneous use of DSCH and the DRAC procedure, but it should not be mandatory for all UEs (e.g. speech only UEs). The PDSCH part of this capability is only relevant if the UE supports PDSCH, as covered by the capability "Support of PDSCH".
There is no specific configuration parameter.
Maximum number of simultaneous S-CCPCH radio links
Defines the maximum number of radio links on which the UE is capable of receiving S-CCPCH simultaneously.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.4 FDD physical channel parameters in uplink
|
Maximum number of DPDCH bits per 10 ms
This capability combines the 'Max number of DPDCH' and 'Minimum SF' capabilities into one capability. Note that no flexibility is lost due to this, as multiple DPDCH is only used for SF=4, i.e. when the number of DPDCH bits exceed a certain value.
The number of DPDCH channel bits indicates the capability for normal, un-compressed mode. The UE shall also be able to support compressed mode by SF reduction when operating at this value.
Support of PCPCH
Support of PCPCH is only required for some RAB realizations, and is therefore a UE capability.
There is no specific configuration parameter.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.5 TDD physical channel parameters in downlink
|
Maximum number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can receive.
Maximum number of physical channels per frame
This parameter defines how many physical channels can be received during one frame. The distribution of the received physical channels on the received timeslots can be arbitrary.
Minimum SF
Defines the minimum SF supported by the UE.
Support of PDSCH
Defines whether PDSCH is supported or not.
Maximum number of physical channels per timeslot
This parameter defines how many physical channels can be received within one timeslot.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.6 TDD physical channel parameters in uplink
|
Maximum Number of timeslots per frame
Defines the maximum number of timeslots per frame that the UE can transmit.
Maximum number of physical channels per timeslot
Defines the maximum number physical channels transmitted in parallel during one timeslot.
Minimum SF
Defines the minimum SF supported by the UE.
Support of PUSCH
Defines whether PUSCH is supported or not.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.5.7 RF parameters
|
UE power class
The value is fixed per UE and is not related to any configuration parameter.
Radio frequency bands
Defines the uplink and downlink frequency bands supported by the UE.
Configuration parameters are UTRA RF Channel numbers for uplink and downlink, which are part of Frequency info.
Tx/Rx frequency separation
Defines the uplink/downlink frequency separations supported by the UE.
Configuration parameters are UTRA RF Channel numbers for uplink and downlink, which are part of Frequency info.
Chip rate capability
Chip rates supported by the UE.
Corresponding configuration parameter is chip rate, which is part of Frequency info.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.6 Multi-mode related parameters
|
Support of UTRA FDD/TDD
Defines whether UTRA FDD and/or TDD are supported.
There is no explicit configuration parameter.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.7 Multi-RAT related parameters
|
Support of GSM
Defines whether GSM is supported or not.
There is no explicit configuration parameter.
Support of multi-carrier
Defines whether multi-carrier is supported or not.
There is no explicit configuration parameter.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.8 LCS related parameters
|
Standalone location method(s) supported
Defines if a UE can measure its location by some means unrelated to UTRAN (e.g. if the UE has access to a standalone GPS receiver).
OTDOA UE based method supported
Defines if a UE supports the OTDOA UE based schemes.
Network Assisted GPS support
Defines if a UE supports either of the two types of assisted GPS schemes, namely "Network based", "UE based", "Both", or "none".
GPS reference time capable
Defines if a UE has the capability to measure GPS reference time as defined in 25.215.
Support for IPDL
Defines if a UE has the capability to use IPDL to enhance its "SFN-SFN observed time difference –type 2" measurement.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
4.9 Measurement related capabilities
|
Need for downlink compressed mode
Defines whether the UE needs compressed mode in the downlink in order to perform inter-frequency or inter-RAT measurements. There are separate parameters for measurements on each UTRA mode, on each RAT, and in each frequency band.
Need for uplink compressed mode
Defines whether the UE needs compressed mode in the uplink in order to perform inter-frequency or inter-RAT measurements. There are separate parameters for measurements on each UTRA mode, on each RAT, and in each frequency band.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
5 Possible UE radio access capability parameter settings
| |
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
5.1 Value ranges
|
Table 5.1: UE radio access capability parameter value ranges
UE radio access capability parameter
Value range
PDCP parameters
Header compression algorithm supported
Yes/No
RLC parameters
Total RLC AM buffer size
2,10,50,100,150,500,1000 kBytes
Maximum number of AM entities
3,4,5,6,8,16,32
PHY parameters
Transport channel parameters in downlink
Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum sum of number of bits of all convolutionally coded transport blocks being received at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum number of simultaneous transport channels
4, 8, 16, 32
Maximum number of simultaneous CCTrCH
1, 2, 3, 4, 5, 6, 7, 8
Maximum total number of transport blocks received within TTIs that end within the same 10 ms interval
4, 8, 16, 32, 48, 64, 96, 128, 256, 512
Maximum number of TFC in the TFCS
16, 32, 48, 64, 96, 128, 256, 512, 1024
Maximum number of TF
32, 64, 128, 256, 512, 1024
Support for turbo decoding
Yes/No
Transport channel parameters in uplink
Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum sum of number of bits of all convolutionally coded transport blocks being transmitted at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum sum of number of bits of all turbo coded transport blocks being transmitted at an arbitrary time instant
640, 1280, 2560, 3840, 5120, 6400, 7680, 8960, 10240, 20480, 40960, 81920, 163840
Maximum number of simultaneous transport channels
2, 4, 8, 16, 32
Maximum number of simultaneous CCTrCH of DCH type (TDD only)
1, 2, 3, 4, 5, 6, 7, 8
Maximum total number of transport blocks transmitted within TTIs that start at the same time
2, 4, 8, 16, 32, 48, 64, 96, 128, 256, 512
Maximum number of TFC in the TFCS
4, 8, 16, 32, 48, 64, 96, 128, 256, 512, 1024
Maximum number of TF
32, 64, 128, 256, 512, 1024
Support for turbo encoding
Yes/No
FDD Physical channel parameters in downlink
Maximum number of DPCH/PDSCH codes to be simultaneously received
1, 2, 3, 4, 5, 6, 7, 8
Maximum number of physical channel bits received in any 10 ms interval (DPCH, PDSCH, S-CCPCH)
600, 1200, 2400, 3600, 4800, 7200, 9600, 14400, 19200, 28800, 38400, 48000, 57600, 67200, 76800
Support for SF 512
Yes/No
Support of PDSCH
Yes/No
Simultaneous reception of SCCPCH and DPCH
Yes/No
Simultaneous reception of SCCPCH, DPCH and PDSCH
Yes/No
Maximum number of simultaneous S-CCPCH radio links
1
NOTE: Only the value 1 is part of R99
FDD Physical channel parameters in uplink
Maximum number of DPDCH bits transmitted per 10 ms
600, 1200, 2400, 4800, 960, 19200, 28800, 38400, 48000, 57600
Support of PCPCH
Yes/No
TDD physical channel parameters in downlink
Maximum number of timeslots per frame
1..14
Maximum number of physical channels per frame
1,2,3..,224
Minimum SF
16, 1
Support of PDSCH
Yes/No
Maximum number of physical channels per timeslot
1..16
TDD physical channel parameters in uplink
Maximum Number of timeslots per frame
1..14
Maximum number of physical channels per timeslot
1, 2
Minimum SF
16,8,4,2,1
Support of PUSCH
Yes/No
RF parameters
FDD RF parameters
UE power class
(25.101 subclause 6.2.1)
3, 4
NOTE: Only power classes 3 and 4 are part of R99
Tx/Rx frequency separation
(25.101 subclause 5.3) .
NOTE: Not applicable if UE is not operating in frequency band a
190 MHz
174.8-205.2 MHz
134.8-245.2 MHz
RF parameters
TDD RF parameters
UE power class
(25.102)
2,3
NOTE: Only power classes 2 and 3 are part of R99
Radio frequency bands
(25.102)
a), b), c), a+b), a+c), a+b+c)
Chip rate capability
(25.102)
3.84,1.28
Multi-mode related parameters
Support of UTRA FDD/TDD
FDD, TDD, FDD+TDD
Multi-RAT related parameters
Support of GSM
Yes/No
Support of multi-carrier
Yes/No
LCS related parameters
Standalone location method(s) supported
Yes/No
Network assisted GPS support
Network based / UE based / Both/ None
GPS reference time capable
Yes/No
Support for IPDL
Yes/No
Support for OTDOA UE based method
Yes/No
Measurement related capabilities
Need for downlink compressed mode
Yes/No (per frequency band, UTRA mode and RAT)
Need for uplink compressed mode
Yes/No (per frequency band, UTRA mode and RAT)
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
5.2 Reference UE radio access capability combinations
|
Based on required UE radio access capabilities to support reference RABs as defined in clause 6, this clause lists reference UE Radio Access capability combinations. Subclause 5.2.1 defines reference combinations of UE radio access capability parameters common for UL and DL. Subclause 5.2.2 and 5.2.3 define reference combinations of UE radio access capability parameters that are separate for DL and UL respectively. A reference combination for common UL and DL parameters, one combination for UL parameters and one combination for DL parameters together relate to a UE with a certain implementation complexity, that allows support for one or several combined reference RABs. Combinations for UL and DL can be chosen independently. The bit rate supported by the selected combination of common UL and DL parameters needs to be at least as high as the maximum out of the supported bit rates of the selected combination of DL parameters and the selected combination of UL parameters. Different combinations have different levels of implementation complexity.
For defined reference RABs, it is possible to require a UE to meet a certain reference UE radio access capability combination. Each UE needs to have capabilities complying with a given reference radio access capability combination. Each individual radio access capability parameter as defined in Subclause 5.1 shall be signalled.
The reference combination numbers shall not be used in the signalling of UE radio access capabilities between the UE and UTRAN. Reference UE radio access capability combinations provide default configurations that should be used as a basis for conformance testing against reference RABs.
Allowed values of UE capability parameters are limited by the defined range and granularity of values in Subclause 5.1. Values might change depending on further definition of reference RABs for testing.
5.2.1 Combinations of common UE Radio Access Parameters
for UL and DL
NOTE: It is FFS whether measurement-related capabilities need to be included in the combinations. These capabilities are independent from the supported RABs.
Table 5.2.1.1: UE radio access capability parameter combinations, parameters common for UL and DL
Reference combination of UE Radio Access capability parameters common for UL and DL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
2048kbps class
PDCP parameters
Header compression algorithm supported
No
No/Yes NOTE 1
No/Yes
NOTE 1
No/Yes
NOTE 1
No/Yes
NOTE 1
No/Yes
NOTE 1
RLC parameters
Total RLC AM buffer size (kbytes)
10
10
50
50
100
500
Maximum number of AM entities
4
4
5
6
8
8
Multi-mode related parameters
Support of UTRA FDD/TDD
FDD / FDD+TDD / TDD
NOTE 1
Multi-RAT related parameters
Support of GSM
Yes/No
NOTE 1
Support of multi-carrier
Yes/No
NOTE 1
LCS related parameters
Standalone location method(s) supported
Yes/No
NOTE 1
Network assisted GPS support
Network based / UE based / Both/ None
NOTE 1
GPS reference time capable
Yes/No
NOTE 1
Support for IPDL
Yes/No
NOTE 1
Support for OTDOA UE based method
Yes/No
NOTE 1
RF parameters for FDD
UE power class
3 / 4
NOTE 1
Tx/Rx frequency separation
190 MHz
RF parameters for TDD
Radio frequency bands
A / b / c / a+b / a+c / b+c / a+b+c
NOTE 1
Chip rate capability
1.28 / 3.84 Mchip/sec
NOTE 1
UE power class
2 / 3
NOTE 1
NOTE 1: Options represent different combinations that should be supported with Conformance Tests.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
5.2.2 Combinations of UE Radio Access Parameters for DL
|
Table 5.2.2.1: UE radio access capability parameter combinations, DL parameters
Reference combination of UE Radio Access capability parameters in DL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
2048kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being received at an arbitrary time instant
640
3840
3840
6400
10240
20480
Maximum sum of number of bits of all convolutionally coded transport blocks being received at an arbitrary time instant
640
640
640
640
640
640
Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant
NA
3840
3840
6400
10240
20480
Maximum number of simultaneous transport channels
8
8
8
8
8
16
Maximum number of simultaneous CCTrCH (FDD)
1
2/1
NOTE 2
2/1
NOTE 2
2/1
NOTE 2
2
2
Maximum number of simultaneous CCTrCH (TDD)
2
3
3
3
4
4
Maximum total number of transport blocks received within TTIs that end at the same time
8
8
16
32
64
96
Maximum number of TFC in the TFCS
32
48
96
128
256
1024
Maximum number of TF
32
64
64
64
128
256
Support for turbo decoding
No
Yes
Yes
Yes
Yes
Yes
Physical channel parameters (FDD)
Maximum number of DPCH/PDSCH codes to be simultaneously received
1
2/1
NOTE 2
2/1
NOTE 2
3
3
3
Maximum number of physical channel bits received in any 10 ms interval (DPCH, PDSCH, S-CCPCH).
1200
3600/2400
NOTE2
7200/4800
NOTE2
19200
28800
57600
Support for SF 512
No
No
No
No
No
No
Support of PDSCH
No
Yes/No
NOTE 1
Yes/No
NOTE 1
No/Yes
NOTE 1
Yes
Yes
Maximum number of simultaneous S-CCPCH radio links
1
1
1
1
1
1
Physical channel parameters (TDD)
Maximum number of timeslots per frame
1
2
4
5
10
12
Maximum number of physical channels per frame
8
9
14
28
64
136
Minimum SF
16
16
16
1/16
NOTE 1
1/16
NOTE 1
1/16
NOTE 1
Support of PDSCH
Yes/No
NOTE 1
Yes
Yes
Yes
Yes
Yes
Maximum number of physical channels per timeslot
8
9
9
9
9
13
NOTE 1: Options represent different combinations that should be supported with conformance tests.
NOTE 2: Options depend on the support of PDSCH. The highest value is required if PDSCH is supported.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
5.2.3 Combinations of UE Radio Access Parameters for UL
|
Table 5.2.3.1: UE radio access capability parameter combinations, UL parameters
Reference combination of UE Radio Access capability parameters in UL
32kbps class
64kbps class
128kbps class
384kbps class
768kbps class
Transport channel parameters
Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant
640
3840
3840
6400
10240
Maximum sum of number of bits of all convolutionally coded transport blocks being transmitted at an arbitrary time instant
640
640
640
640
640
Maximum sum of number of bits of all turbo coded transport blocks being transmitted at an arbitrary time instant
NA
3840
3840
6400
10240
Maximum number of simultaneous transport channels
4
8
8
8
8
Maximum number of simultaneous CCTrCH(TDD only)
1
2
2
2
2
Maximum total number of transport blocks transmitted within TTIs that start at the same time
4
8
8
16
32
Maximum number of TFC in the TFCS
16
32
48
64
128
Maximum number of TF
32
32
32
32
64
Support for turbo encoding
No
Yes
Yes
Yes
Yes
Physical channel parameters (FDD)
Maximum number of DPDCH bits transmitted per 10 ms
1200
2400
4800
9600
19200
Simultaneous reception of SCCPCH and DPCH
NOTE 2
No
No
Yes/No
NOTE 1
Yes/No
NOTE 1
Yes/No
NOTE 1
Simultaneous reception of SCCPCH, DPCH and PDSCH
NOTE 2
No
No
No
No
No
Support of PCPCH
No
No
No
No
No
Physical channel parameters (TDD)
Maximum Number of timeslots per frame
1
2
3
7
9
Maximum number of physical channels per timeslot
1
1
1
1
2
Minimum SF
8
2
2
2
2
Support of PUSCH
Yes/No
NOTE 1
Yes
Yes
Yes
Yes
NOTE 1: Options represent different combinations that should be supported with conformance tests.
NOTE 2: The downlink parameters 'Simultaneous reception of SCCPCH and DPCH' and 'Simultaneous reception of SCCPCH, DPCH and PDSCH' are included in the combinations for uplink as their requirements relate to the uplink data rate. Simultaneous reception of SCCPCH and DPCH is required for the DRAC procedure that is intended for controlling uplink transmissions. In release 99, this is limited to 1 SCCPCH.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
6 Usage of UE radio access capabilities
|
NOTE: The rationale for the parameter combination settings will be explained here.
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
6.1 Examples of reference radio access bearers
|
In Table 6.1 reference RAB A-G are defined with some characteristics that impact the required UE Radio Access capabilities. These reference RABs shall be seen as example RABs covered by the reference UE radio access capability combinations defined in Subclause 5.2. Reference RABs for conformance testing are specified in TS 34.108.
Table 6.1: Reference RABs
Reference RAB
A
B
C
D
E
F
G
RAB characteristics and mapping to DCH
Coding (CC/TC)
Conversational speech 4.75-12.2 kbps (20 ms TTI)
CC, Only one rate per RAB
Conversational 64 kbps
(40 ms TTI)
TC
Streaming
max. 57.6 kbps
(40 ms TTI)
TC
Interactive/
Background max. 32 kbps
(10 ms TTI)
CC
Interactive/
Background max. 64 kbps
(20 ms TTI)
TC
Interactive/
Background max. 384 kbps
(10/20 ms TTI)
TC
Interactive/
Background max. 2048 kbps
(10 ms TTI)
TC
DCH carrying DCCH
(rate, TTI)
3.4kpbs, 40ms
3.4kbps, 40ms/
6.4kbps, 20ms
3.4kbps, 40ms/
6.4kbps, 20ms
3.4kbps, 40ms/
12.8kbps, 10ms
3.4kbps, 40ms/
12.8kbps, 10ms
3.4kbps, 40ms/
12.8kpbs, 10ms
3.4kbps, 40ms/
12.8kpbs, 10ms
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
6.2 Example mappings between reference RABs and capability combinations
|
The following examples show how the reference RABs of Table 6.1 can be mapped to the reference UE radio access capability combinations that are listed in Clause 5.
Table 6.2: Example mappings between capability combinations and RAB combinations
Reference UE radio access capability combinations
Examples of supported reference RAB combination
32kbps class
One at the time of the following:
- A
- D
64kbps class
One at the time of the following:
- B
- C
- E
- A and D simultaneously
- A and E simultaneously
- A and B simultaneously
- A and C simultaneously
- The RAB combination supported by 32kbps class
128kbps class
One at the time of the following:
- 2 times E
- The RAB combination supported by 64kbps class
384kbps class
One at the time of the following:
- E + B
- 2 times B
- F (TTI 10 ms)
- A and F (TTI 10 ms) simultaneously
- The RAB combination supported by 128kbps class
768kbps class
One at the time of the following:
- F (TTI 20 ms)
- A and F (TTI 20 ms) simultaneously
- 2 times F (TTI 10 ms) in DL.
- The RAB combination supported by 384kbps class
2048kbps class
One at the time of the following:
- G in DL only
- A and G simultaneously
- The RAB combination supported by 768kbps class
|
a81d9bd99016b59710681951aa0bdd87
|
25.926
|
7 Mandatory UE radio access capabilities
|
NOTE: In this section features and requirements that are mandatory for UEs (capabilities that do not need to be signalled) will be listed for information. The normative descriptions are part of the respective specifications.
Annex A (informative):
Change history
Change history
TSG-RAN#
Version
CR
Tdoc RAN
New Version
Subject/Comment
RAN_07
-
-
RP-000052
3.0.0
(03/00)
Approved at TSG-RAN #7 and placed under Change Control
RAN_08
3.0.0
003
RP-000229
3.1.0
(06/00)
Updated Ad Hoc changes
RAN_08
3.0.0
008
RP-000229
3.1.0
CPCH note to the the parameter definitions
RAN_09
3.1.0
010
RP-000368
3.2.0
(09/00)
TDD DL Physical Channel Capability per Timeslot
RAN_09
3.1.0
012
RP-000368
3.2.0
Change to UE Capability definition
RAN_09
3.1.0
013
RP-000368
3.2.0
Physical parameter changes
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
1 Scope
|
The present document …
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
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 non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
3 Definitions of terms, symbols and abbreviations
| |
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4 Assessment of existing specification formats and working methods, and requirements for any improvements
|
Editor's note: corresponds to objective 1.
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4.1 Advantages of current tools
|
<< Examples:
WYSIWYG editing
Change tracking >>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4.2 Shortcomings, pain-points and potential benefits
|
Editor’s note: corresponds to objectives 1a/b
#
Shortcoming / pain-point / potential benefit
Possible improvement approaches with current tools
Pros of possible improvement approaches
Cons of possible improvement approaches
Summary of feasibility of addressing the shortcoming / pain-point / potential benefit with current tools
Applicable WGs and users of the specification
x
<< Example: Large docx files are slow to open >>
<< Example:
x.1 Split into multiple smaller docx files >>
<< Example:
Faster opening >>
<< Example:
Hyperlinking not possible across spec, e.g. from contents page.
Searching across whole spec is difficult. >>
<< Example:
Partial solution but drawbacks remain with existing tools. >>
<<Example: all WGs, users (e.g., delegates, rapporteurs, MCC)>>
<< Example:
x.2 Move content into separate database, e.g. as with CA band combinations >>
<< Example:
Faster opening of residual spec >>
<< Example:
Does not help with large specs that do not include database-appropriate content >>
<< Example:
Potential solution for some specs but not others >>
<<Example: all WGs, users (e.g., delegates, rapporteurs, MCC)>>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4.3 Requirements Identification
|
Editor's note: corresponds to Objective 1c
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4.3.1 General requirements
|
#
Requirement
Description
Applicable to objective 2
Applicable to objective 3
x
<< Example: International availability >>
<< Example: There shall be no geographic limitations on availability and usability of tools >>
<<Example: Y>>
<<Example:: Y>>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
4.3.2 Requirements related to specific identified shortcomings/pain-points in clause 4.2
|
#
Requirement
Description
Applicable to objective 2
Applicable to objective 3
x
<< Example: Fast file opening >>
<< Example: Any new format shall open significantly more quickly than docx for a given amount of content >>
<<Example: Y>>
<<Example:: N>>
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
5 Proposals for new formats for 3GPP specifications
|
Editor's note: corresponds to objective 2.
5.X Proposal #X
5.X.1 Description
5.X.2 Evaluation against requirements of section 4.3
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
6 Proposals for Tools and Ways of Working
|
Editor's note: corresponds to objective 3.
6.X Proposal #X
6.X.1 Description
6.X.1.1 Description of tools
6.X.1.2 Description of procedures
6.X.2 Evaluation against requirements of section 4.3
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
7 Overall evaluation
|
Editor's note: Overall evaluation of combined proposals from sections 5 and 6, including trials.
|
d380c78f5f9bacabc1ad685b66c3dde8
|
21.802
|
8 Recommendations
|
Editor's note: Final recommendations
Annex <A>:
Annex Placeholder
Editor's note: To be used if there is a need for an annex.
Annex X:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
|
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
1 Scope
|
The present document …
|
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
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 non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
3 Definitions of terms, symbols and abbreviations
| |
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
db6b1a7d49922ff5a0278da106d353b2
|
28.887
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
Annex <A> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
V0.0.0
|
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
1 Scope
|
The present document …
|
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
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 non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
3 Definitions of terms, symbols and abbreviations
| |
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
47da2fe28f0cbe4d80d26f47a0ffb712
|
28.882
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
Annex <X> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
0.0.0
|
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
1 Scope
|
The present document …
|
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
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 non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
3 Definitions of terms, symbols and abbreviations
| |
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
1a6efd3c40ff1e749ca1d3ee92720834
|
28.883
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
Annex <X> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
V0.0.0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.