hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.4 Call Hold | It shall be possible to re-establish a call which has been put on hold before undergoing VCC, after the VCC has been performed. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.5 Multiparty | It shall be possible for any party in a multiparty call to undergo VCC and to stay in the call. It shall be possible to terminate the entire multiparty call when the served mobile subscriber releases even if she is connected via the IMS after undergoing VCC. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.6 All Call Barrings | If a call were to undergo VCC and that would result in the call being barred in the target domain/system, it shall be up to the home operator policy whether the call continues in the target domain/system, the call terminates, or VCC is not executed for the call. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.7 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.8 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.9 All other Supplementary Services | Other supplementary services are not discussed in this section as they do not apply to calls in progress (i.e. they apply to call set up only) or their support and/or the need for standardised implementation has not been identified as critical for VCC in this Release. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.3 Quality of Service | Voice call continuity shall not adversely impact the quality of the voice service experienced by the user. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.4 Security | Voice call continuity shall not adversely impact the security of the 3GPP system.
Security mechanisms of the 3GPP system shall be reused for voice call continuity. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.5 Emergency calls | Voice call continuity for emergency calls shall be applicable to dual radio and single radio UEs.
Voice call continuity of emergency calls shall only be performed when all the following conditions are met:
- the source network is IMS;
- the target network supports emergency calls;
- the user is moving out of coverage;
... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.6 Charging | It shall be possible to indicate in the charging information that a VCC event has occurred (e.g., so that appropriate ratings can be applied for the CS and IMS parts of the continued voice call). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.7 VCC Activation | It shall be possible to activate VCC based on operator policies, taking into account any of the following:
- Radio conditions e.g. radio quality thresholds and related hysteresis
- Coverage availability e.g.: Always prefer I-WLAN, if certain SSID are available |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22 IMS Centralized Services | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.1 General | The ICS user shall receive both registered and unregistered services in a consistent manner when the user accesses IMS either via the CS or the PS domain (both of which can be supported by 3GPP access networks or non‑3GPP access networks). Support of UEs enhanced with ICS capability as well as UEs without ICS capabilit... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.2 Service Consistency | Subscribers shall have a consistent user experience regardless of the domain used, subject to the constraints of the UE and access network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.3 Service Continuity | ICS shall support service continuity between CS and PS domains (both of which can be supported by 3GPP access networks or non‑3GPP access networks), subject to the constraints of the UE and access networks.
Note : The impacts to support non 3GPP CS domains are outside the scope of 3GPP.
The service continuity shall inc... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.4 IMS Services | The set of IMS services supported by ICS shall include at least the following, subject to the constraints of the UE and access networks:
- IMS Multimedia Telephony services, including:
- speech,
- video,
- fax,
- data (CS),
- Supplementary services defined within [40]; and
- Multimedia priority service.
- IMS emergency... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.5 Roaming Support | An ICS user shall be able to receive full ICS support from the HPLMN while roaming in the VPLMN, subject to the constraints of the VPLMN (e.g. roaming agreements, operator policies).
The Home operator shall be able to control if the UE enhanced with ICS capability shall act without ICS capability while roaming. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23 CS IP interconnection requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.1 Introduction | CS IP interconnect represents the interconnection of MSC Server functionality between 2 CS networks over an underlying IP infrastructure. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.2 IP interconnect | The IP connection used for CS IP interconnect shall be generic such that it can support all combinations of core network interconnection. E.g. the IP interconnection shall be shared between the IMS interconnection and the CS IP interconnection.
It shall be possible to handle the inter-connection of all services over th... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.3 MSC server interconnect | The following requirements apply at the interconnection point when two PLMNs are interconnected by means of IP transport technology for 2G and 3G CS services.
The system shall support the capability for CS service interoperability and interworking.
It shall be possible to apply operator defined policy at the interconne... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24 Service Alignment & Migration | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24.1 Introduction | Services can be offered to the users via different service domains, e.g. certain teleservices and supplementary services via CS or Multimedia Telephony and supplementary services via IMS. Especially for the supplementary services given below a strong relationship exists from the user's point of view. Therefore means sh... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24.2 Alignment of supplementary services settings | Based on user preferences and if provisioned by the home operator the network shall automatically synchronise the parameter settings of the supplementary services listed in the following table:
Table 24.2-1: Alignment of supplementary services settings
CS Voice (TS11) Supplementary Services
Equivalent Multimedia Teleph... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25 System optimisation for communication with specific characteristics | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.1 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.2 Numbering Resource Efficiency | The following optional requirement is intended to provide better numbering resource efficiency for UEs that only require packet switched services.
- A network operator shall be able to provide PS only subscriptions with or without assigning an MSISDN.
- Remote triggering shall be supported with or without assigning an ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.3 Network provided destination for uplink data | The Network Provided Destination for Uplink Data feature is intended for use when all data from a UE is to be directed to a network provided destination address.
- For uplink data communication, the network shall be able to direct all uplink PS data traffic to a network provided destination address.
NOTE: This feature ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.4 PS only subscriptions | The system shall support subscriptions that only allow packet-based services and SMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26 Single Sign-On (SSO) Service | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1.1 Requirements for the UE | An SSO-capable UE shall support 3GPP SSO Authentication, without user intervention, based on Operator-controlled credentials.
An SSO-capable UE shall be able to initiate the SSO Service regardless of the access network technologies supported by the UE.
An SSO-capable UE that supports 3GPP access and non-3GPP access sha... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1.2 Requirements for a 3GPP SSO Service | The 3GPP SSO Service shall provide secure, seamless and transparent access to data applications for users of the SSO Service independent of the access network technology.
The 3GPP SSO Service shall be able to interwork with Identity Management (IdM) specifications (e.g., OpenID [51]).
The 3GPP SSO Service shall support... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27 User plane congestion management | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.1 Introduction | RAN user plane congestion, in the context of this clause, is considered to be downlink congestion that affects the user plane, which may last for a few seconds, a few minutes, or a few hours due to arrival of new active users, increase of communication intensity of existing users, the radio environment changing, the mo... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.2 General | a) The network shall be able to detect RAN user plane congestion onset and abatement. Mechanisms to cope with RAN user plane congestions should be resilient to rapid changes in the level of congestion.
b) The network shall be able to identify whether or not an active UE is in a RAN user plane congested cell.
c) The net... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.3 Prioritizing traffic | a) According to operator policy, during RAN user plane congestion the operator shall be able to select the communications which require preferential treatment and allocate sufficient resources for such communications in order to provide these services with appropriate service quality.
b) According to operator policy, t... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.4 Reducing traffic | a) Based on RAN congestion status and according to operator policy, the network shall be able to reduce the user plane traffic load (e.g. by compressing images or by adaptation for streaming applications) taking into account UE related information (e.g. UE capabilities, subscription).
b) The system shall be able to adj... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28 RAN Sharing Enhancements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.1 General | RAN Sharing Enhancements allow multiple Participating Operators to share the resources of a single RAN according to agreed allocation schemes. The Shared RAN is provided by a Hosting RAN Operator which can be one of the Participating Operators.
The Shared RAN can be GERAN, UTRAN, E-UTRAN or NG-RAN as described below.
A... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2 Specific E-UTRAN and NG-RAN Sharing requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.1 Allocation of Shared E-UTRAN and NG-RAN resources | When E-UTRAN and NG-RAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting E-UTRAN/NG-RAN Operator.
The following requirements apply:
The Hosting E-UTRAN/NG-RAN Operator shall ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.2 OA&M Access to the Shared E-UTRAN/NG-RAN | Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a shared E-UTRAN/NG-RAN. Information exchange involved in those operations need to be controlled by the Hosting E-UTRAN/NG-RAN Operator as to prevent disclosing them to other Participating Oper... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.3 Generation and retrieval of usage and accounting information | To facilitate interoperator accounting between Hosting E-UTRAN/NG-RAN Operator and Participating Operator the Hosting E-UTRAN/NG-RAN Operator needs to record E-UTRAN/NG-RAN resource usage by UEs of the Participating Operator.
The following requirements apply:
A Hosting E-UTRAN/NG-RAN Operator shall be able to collect e... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.4 MDT Collection | MDT data from a Participating Operator's customer UEs allow the Hosting E-UTRAN/NG-RAN Operator to be provided with performance measurements on his Shared E-UTRAN/NG-RAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
The following requirements apply:... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.5 PWS support of Shared E-UTRAN/NG-RAN | A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of E-UTRAN/NG-RAN Sharing.
The following requirements apply:
The Shared E-UTRAN/NG-RAN shall be able to broadcast PWS messages originated from the core networks of all Participating Operators.
NOTE: Rel-... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.6 Support for load balancing | Hosting E-UTRAN/NG-RAN Operators have the need to optimize E-UTRAN/NG-RAN resource usage within the shared E-UTRAN/NG-RAN for a particular coverage area. At the same time, the agreed shares of E-UTRAN/NG-RAN resources based on a single cell and sector for each Participating Operator need to be respected. Likewise, Part... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.7 Dynamic capacity negotiation | In situations where a need for additional, unplanned, E-UTRAN/NG-RAN capacity by a Participating Operator arises (e.g. in the case of big mass-events) the Shared E-UTRAN/NG-RAN can provide means to allocate available spare capacity to the Participating Operator. Based on service level agreement between the Hosting and ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3 Specific GERAN & UTRAN Sharing Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.1 Allocation of Shared GERAN or UTRAN Resources | When GERAN or UTRAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting RAN Operator.
The following requirements apply:
The Hosting RAN Operator shall be able to specify the all... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.2 OA&M Access to the Shared GERAN or UTRAN | Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a Shared GERAN or UTRAN. Information exchange involved in those operations need to be controlled by the Hosting RAN Operator so as to prevent disclosing them to other Participating Operators, b... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.3 Generation and retrieval of usage and accounting information | To facilitate inter-operator accounting between the Hosting RAN Operator and the Participating Operator, the Hosting RAN Operator needs to record GERAN or UTRAN resource usage by UEs of the Participating Operator.
The following requirements apply:
A Hosting RAN Operator shall be able to collect events supporting the ac... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.4 MDT Collection | MDT data from a Participating Operator's customer UEs allow the Hosting RAN Operator to be provided with performance measurements on his Shared GERAN or UTRAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
The following requirements apply:
When autho... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.5 PWS support of Shared GERAN or UTRAN | A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of GERAN or UTRAN Sharing.
The following requirements apply:
The Shared GERAN or UTRAN shall be able to broadcast PWS.
NOTE: The Hosting RAN Operator is responsible for the delivery of PWS messages to th... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.6 Support for load balancing | Hosting RAN Operators need to optimise GERAN or UTRAN resource usage within the Shared GERAN or UTRAN for a particular coverage area while respecting the agreed resource shares for each Participating Operator. Similarly, Participating Operators need to optimise their GERAN or UTRAN resource usage between Shared and uns... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.7 Dynamic capacity negotiation | The Participating Operator shall be able to request on-demand spare capacity of the Shared GERAN or UTRAN based on policies and without human intervention.
The Hosting RAN Operator shall be able to allocate spare on-demand capacity on the Shared GERAN or UTRAN to a Participating Operator, based on policies and without ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29 Service exposure with 3rd party service providers | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29.1 General | The intention of service exposure is that, under the assumption of a service agreement between MNO and a 3rd party, the 3GPP Network allows a 3rd party service provider to benefit from network provided services and capabilities that are exposed by the PLMN. For example the 3GPP Core Network can exchange information wit... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29.2 Exposed Services and capabilities | The 3GPP Core Network shall be able provide a standardized interface to enable exposure of the following services and capabilities to 3rd party service providers:
Support of 3rd party requested MTC Device triggering
- The 3GPP Core Network shall support a 3rd party service provider request to trigger a UE that is serve... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30 Flexible Mobile Service Steering | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30.1 Introduction | In order to realize efficient and flexible mobile service steering in (S)Gi-LAN, the network operator uses information (e.g. user profile, network operator’s policies, RAT type, application characteristics) to define traffic steering policies. These policies are used to steer the subscriber’s traffic to appropriate ena... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30.2 General Requirements | The following requirements apply:
- The 3GPP Core Network shall be able to define and modify traffic steering policies that are used to steer traffic in (S)Gi-LAN containing operator or 3rd party service functions e.g. to improve e.g. the user’s QoE, apply the bandwidth limitation and provide valued added services.
- T... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.1 Description | This feature is a set of service features that allows operators to control traffic from UEs to an application on a third-party server or the third-party server itself. When an application on a third-party server or the third-party server itself becomes congested or fails the traffic towards that server need to be contr... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2.1 Control requirements | The 3GPP network shall be able to control (i.e. block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.
For this purpose, the 3GPP network shall be able... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2.2 Requirements on awareness of third-party server issue | The 3GPP network shall be able to receive a status indication from the third-party server when an application on it is experiencing congestion or failure, and when normal operation resumes. Such a status indication may be sent periodically, and/or when the status of the application changes.
The 3GPP network shall be ab... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.1 Feature description | 3GPP enhancement for TV service support is a feature whereby 3GPP networks can provide unicast and broadcast transport, referred to as “TV transport services”, to support distribution of TV programs. TV transport services can support the three types of TV services – Free-to-air (FTA), Free-to-view (FTV), and Subscribed... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.1 General requirements | The 3GPP network shall be able to support on-demand network capacity assignment for TV services.
The 3GPP system shall allow the MNO to implement a network supporting downlink only broadcasting based on a set of EPS functionalities and entities which are required to offer linear TV services.
The 3GPP network shall be a... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.2 Requirement for transmission performance enhancement | The 3GPP system shall be able to support 20Mbps over one logical broadcast channel.
The mechanisms in the 3GPP network shall be designed to support at least 10 high quality video channels of 12Mbps each simultaneously via broadcast.
The 3GPP network shall support flexible change between broadcast and unicast per traffi... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.3 Requirement for network flexibility | The 3GPP network shall be able to support network broadcast capacity assignment according to operator policies to consider the following criteria:
• OTT provider request (including TV service information (e.g., codec information, media type information, etc))
• available network unicast/broadcast capacity of 3GPP netwo... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.4 Requirement for TV application support | The eMBMS service layer should support audio and video formats typically supported by TV Content Providers for SD and HD TV transport services and UHD TV transport services.
The eMBMS service layer should support codecs typically supported by TV Content Providers for HD TV services and UHD TV services. The eMBMS servic... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.5 Requirement for RAN sharing | A participating eMBMS-enabled RAN shall be capable of distributing the content including both free-to-air content and subscribed content in conjunction with other participating eMBMS-enabled RANs.
The hosting eMBMS-enabled RAN network provider shall be able to manage the shared eMBMS network to each of the participatin... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.6 Requirement for wide area support | The eMBMS network shall be able to support designated coverage area, for example national, regional and local coverage areas. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.7 Requirement for capability exposure | The 3GPP system shall be able to support an MNO offering on-demand broadcast availability to TV services.
Subject to MNO and 3rd OTT party agreement, to enable the MNO to evaluate the impact on distribution of data transfer in the network, the 3rd OTT party shall be able to indicate to the MNO the desired media format ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.8 Fixed reception for TV services | The 3GPP network shall allow a UE to receive a broadcast TV content using existing TV antenna equipment.
NOTE 1: “existing TV antenna equipment” means rooftop or indoor antennas directly connected to a TV or set-top box typically used to receive DTT signals
The 3GPP network shall allow a UE to receive unicast TV conten... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 33.1 Description | It is important to document usage over unlicensed access such that an operator has the facility to determine which type of access the traffic was transported over.
For example, LTE-WiFi Aggregation (LWA) and License Assisted Access (LAA) are two features whereby a UE is connected to two access technologies at the same ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 33.2 Requirements | The 3GPP network shall be able to identify traffic which was transported over unlicensed access. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34.1 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34.2 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35 Restricted local operator services | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35.1 Description | Access to restricted local operator services by unauthenticated UEs is based on FCC regulations in the U.S. related to manual roaming as noted in the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 Section 20.3 and the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 S... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35.2 Requirements | Based on operator policy and national regulations, the 3GPP system shall support a mechanism to indicate to UEs that restricted local operator services are available. A UE shall be able to explicitly request access to a network offering restricted local operator services in order to access restricted local operator ser... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 1 Scope
| The purpose of this TS is to describe the service access procedures as presented to the user.
Definitions and procedures are provided in this TS for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station (UE).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 1.1 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 a... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 1.2 Definitions and abbreviations
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 1.2.1 Definitions
| In addition to those below, the definitions and abbreviations listed in 3GPP TR 21.905 [2] are applicable.
3GPP PS Data Off: A feature which when configured by the HPLMN and activated by the user prevents transport via PDN connections or PDU sessions in 3GPP access of all IP packets except IP packets required by 3GPP ... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 1.2.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [2].
ACDC Application specific Congestion control for Data Communicat... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 2 Roaming
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 2.1 General requirements
| A UE with a valid IMSI may roam and access service in the area authorized by the entitlement of the subscription.
If a communication has been established, the UE will in principle not suffer an interruption within the PLMN area (provided the entitlement of the subscription allows it). Exceptions are possible if no net... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 2.2 International roaming
| International roaming is a service whereby a UE of a given PLMN is able to obtain service from a PLMN of another country.
The availability of International Roaming is subject to inter-PLMN agreements.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 2.3 National roaming
| National Roaming is a service whereby a UE of a given PLMN is able to obtain service from another PLMN of the same country, anywhere, or on a regional basis.
The availability of National Roaming depends on the home PLMN of the requesting UE and the visited PLMN; it does not depend on subscription arrangements.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 2.4 Roaming in shared networks
| The following requirements are applicable to GERAN, UTRAN, E-UTRAN and NG-RAN sharing scenarios:
- Mechanisms shall be specified to enable flexible allocation of visiting roamers among core network operators that have roaming agreements with the same roaming partners. The core network operators shall be able to pre-d... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3 Provisions for providing continuity of service
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.1 Location registration
| PLMNs shall provide a location registration function with the main purpose of providing continuity of service to UEs over the whole system area. The location registration function shall be such as to allow:
- Fixed subscribers to call a UE by only using the directory number of the UE irrespective of where the UE is l... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2 Network selection
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.1 General
| The UE shall support both manual and automatic network selection mechanisms (modes). The UE shall select the last mode used, as the default mode, at every switch-on.
As an optional feature of the ME, the user shall be able to set a preference in the ME for the mode that shall be used at switch on. If set, then the ME ... |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2 Procedures
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.