hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.3 Radio Interface | Service capabilities shall be provided in a wide range of radio operating environments (where a radio environment is characterised in terms of propagation environment, mobile equipment relative speeds and traffic characteristics). Although 3GPP aims to minimise the number of radio interfaces and to maximise commonality... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.4 Real-time Resource Usage | To enable network operators to render services efficiently, dimension their networks and set tariffs that more accurately reflect radio resource usage, real time information on resource usage is needed. When requested, it shall be possible for the serving cell type (e.g. RAT), cell ID / UTRAN Service Area Identity and ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5 Selected IP Traffic Offload (SIPTO) for PS Domain only | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5.1 Common Requirements for SIPTO in the Mobile Operator Network and SIPTO at the Local Network | The 3GPP system shall be able to offload selected traffic (e.g. internet) towards a defined IP network close to the UE's point of attachment to the access network.
The following requirements apply to Selected IP Traffic Offload:
- The mobile operator may enable/disable Selected IP Traffic Offload on a per UE per define... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.5.2 Requirements for SIPTO in the Mobile Operator Network | The following requirements apply to Selected IP Traffic Offload in the mobile operator network:
- The mobile operator shall be able to enable/disable Selected IP Traffic Offload for certain parts of the network.
- Selected IP Traffic Offload shall not compromise integrity and confidentiality of offloaded traffic.
- The... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.3.6 Paging policy selection for LTE | The 3GPP core network shall be able to use these additional criteria for selecting a paging policy:
- mobility information on the UE (e.g. the UE is stationary, or moving only in a specified area)
- application characteristics that are known and trusted at the serving network (e.g. communication pattern, expected QoS (... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.4 Compatibility with Global Standards | 3GPP specifications aim to be compatible with IMT-2000 and to provide global terminal mobility (roaming), enabling the user to take his/her terminal to different regions of the world and to be provided with services. It is probable that different regions of the world will adopt different radio interface technologies. I... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.6 Functionality of Serving Network and Home Environment | The following functionality shall be the responsibility of the home environment:
- User Authentication.
- SIM/USIM Issue.
- Billing.
- User Profile/VHE Management.
The following functionality shall be the responsibility of the serving network:
- Radio or other means of access.
- Transport and signalling.
The following ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.7 PLMN Architecture | The network is logically divided into a radio access network and a core network, connected via an open interface. From a functional point of view the core network is divided into a Packet Switched CN Domain, IP Multimedia (IM) CN subsystem [27] and a Circuit Switched CN Domain. IM CN subsystem utilises PS CN domain bea... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.8 Interworking Between PLMN and Wireless LANs | Aspects related to interworking between PLMN and WLAN are captured in TS 22.234 [35]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.9 Network Sharing | Network sharing shall be transparent to the user.
The specifications shall support both the sharing of:
(i) radio access network only;
(ii) radio access network and core network entities connected to radio access network
NOTE: In a normal deployment scenario only one or the other option will be implemented.
It shall be... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.10 The Evolved Packet System | Evolved Packet System is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and E-UTRAN).The service requirements for the Evo... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11 User Data Convergence | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.1 Introduction | The UDC concept [45] supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends. And such unique repository shall be possible to be sha... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.2 Management of user data | Due to the logical centralization of user data, it is necessary for UDC to support the provisioning of the user data, that is, user data manipulation like creation, deletion, reading, modification and other operations. Provisioning shall be possible via an external system, self-care or dynamically via applications offe... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.3 User Data Modelling | User Data Modelling refers to the different models that apply to user data convergence: Information Models and Data Models.
An Information Model denotes an abstract, formal representation of entity types, including their properties and relationships, the operations (e.g. read, write…) that can be performed on them, and... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5 Evolution | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5.1 Support of 2G services | The 3GPP specifications shall be capable of supporting existing 2G services in a manner which is transparent to the users of these services. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5.2 Provision and evolution of services | Since a phased approach has been adopted, the same general service principles shall apply to each phase. Support of services from an end user perspective is understood to be an important driver for established mobile users to stay with their existing operator while taking the new services into use. It is therefore impo... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 6 Classification of services | In the CS CN domain, the basic services are divided into circuit teleservices (3GPP TS 22.003 [14]) and bearer services (3GPP TS 22.002 [21]) and they can utilise standardised supplementary services (3GPP TS 22.004 [5]).
The PS CN Domain provides IP bearer services. SMS, USSD and UUS can also be considered as bearer se... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7 Principles for new service capabilities | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.1 General | 3GPP specifications shall enable the user of a single terminal to establish and maintain several connections simultaneously. It shall efficiently cater for applications which have variable requirements relating to specific QoS parameters (e.g. throughput) whilst meeting other QoS targets. It shall also cater for applic... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2 Multimedia | 3GPP specifications shall support development of multimedia services and provide the necessary capabilities.
Multimedia services combine two or more media components (e.g. voice, audio, data, video, pictures, text) within one call. A multimedia service may involve several parties and connections (different parties may ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.1 Circuit Switched (CS) multimedia calls | CS multimedia call is a Bearer Service which utilises Synchronous Transparent Data service. The following basic requirements shall be supported for CS multimedia calls [24]:
- CS multimedia call shall be based on a 3GPP specific subset of H.324M.
- All call scenarios shall be supported, i.e. Mobile Originating and Mobi... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.2 IP multimedia (IM) sessions | IP multimedia services are not the evolution of the circuit switched services but represent a new category of services, mobile terminals, services capabilities, and user expectations. Any new multimedia service, which may have a similar name or functionality to a comparable standardised service, does not necessarily ha... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.4 Real-Time Text Conversation | Real-Time Text (RTT) conversation is a service enabled in 3GPP networks by the Global Text Telephony ( GTT ) [26].
- GTT enables real time, character by character, text conversation to be included in any conversational service, Circuit Switched as well as IP based.
- It is possible to use the text component in a sessio... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.5 Packet Switched Streaming Service | The following basic requirements are to be supported for streaming:
- The streaming service uses a client / server model which is transparent to the PLMN. The client controls the initiation and execution of the service.
- The streaming service [30] shall use existing standards (codecs and protocols [31]) where these ar... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.3 Service Management Requirements | 3GPP specifications shall include standardised protocols enabling service management. It shall enable control, creation and subscription of service capabilities and services, and the management of user profiles. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.4 Automatic Device Detection | The home environment should be automatically notified when a user, identified by a SIM/USIM, has changed ME and should be informed of the identity of the new ME. This should be applicable to any ME. It should also be possible to achieve Automatic Device Detection for users using any SIM/USIM.
NOTE: The purpose of this ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 8 Service architecture | In order to provide standardisation of service capabilities a service architecture shown by Figure 2 is envisaged
Figure 2: Service Architecture
A number of bearers shall be provided that can differ in flexibility and offer different capabilities. Bearers may be characterised by parameters such as "throughput", "delay ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 9 Quality of Service (QoS) | The Quality of Service (QoS) parameters should be identified together with appropriate parameter values which set targets to be reached when designing 3GPP specifications, and which also will serve as guidelines for network design and service provision.
The QoS for call set-up time, as an example, can be defined in ter... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10 Emergency Calls | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1 General requirements | 10.1.0 Introduction
It shall be possible to establish an emergency speech call or GTT [26] call (subject to national requirements). The term 'Emergency call' henceforth refers to speech calls, and GTT Emergency calls if applicable. The term "other media" henceforth refers to media other than speech and GTT. Support of ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2 Domains priority and selection for UE attempts to emergency call | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2.1 Voice and GTT only | A UE that is connected to a domain in which it is possible for the UE to make non emergency calls using the particular media requested by the user, shall use that domain to attempt an emergency call unless serving network policy (based on regulatory requirements and operator needs) requires the UE, including an unauthe... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2.2 Other media | The following applies in addition to 10.1.2.1.
If an emergency call attempt that includes a request for both (i) voice and/or GTT and (ii) other media cannot be supported or fails in all connected access types in the PS CN domain, the UE shall attempt the emergency call in the CS domain if available and shall only incl... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.3 Call-Back Requirements | Subject to local/regional regulations the network shall support a call-back from a PSAP.
It shall be possible to supply the user's Directory Number/MSISDN/SIP URI as the CLI to the PSAP to facilitate call-back. The CLI used on call-back shall allow the PSAP to contact the same terminal that originated the emergency cal... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.2 Emergency calls in the CS CN Domain | A CS CN Domain shall support the emergency call teleservice as defined in 3GPP TS 22.003 [14] (TS12).
If a UE supports TS11(Telephony)[14], then it shall also support TS12(Emergency Calls)[14]. It shall be possible to set up emergency calls initiated by an emergency call number. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.3 Emergency Calls in the PS CN Domain | Without the IM CN subsystem, emergency calls are not supported in the PS CN domain. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4 Emergency calls in the IM CN subsystem | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.1 General | The IM CN subsystem shall support IMS emergency calls. It shall be possible to set up emergency calls initiated by an emergency call number.
If a UE supports IMS Multimedia Telephony service with speech media as specified in TS 22.173 [40] via an access network, then it shall also support IMS emergency calls via that a... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2 IMS Multimedia Emergency Sessions | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.1 General | For IMS emergency calls towards IP PSAPs, other media types may be supported by the UE and the IMS, subject to regulatory requirements.
The media types that may be supported during an IMS MES include:
- Real time video (simplex, full duplex), synchronized with speech if present;
- Session mode text-based instant messag... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.2 UE Requirements | When IMS MES are supported by the UE, the following apply:
- An IMS UE that supports IMS MES shall also support IMS emergency voice calls.
- Once a UE is aware that an IMS MES has been initiated, the UE shall be able to (subject to user configuration) avoid drawing unnecessary attention to the user (e.g., playing audib... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.3 Originating Network Requirements | When an IMS MES is enabled by the originating network, the following apply:
- Other media shall only be supported in packet-based networks that support IMS emergency voice calls.
- The originating network shall deliver all media to the same IP PSAP throughout the duration of the IMS MES.
- The network shall indicate to... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.6 Location Availability for Emergency Calls | National regulations may require wireless networks to provide the emergency caller's location. This requirement typically overrides the caller's right to privacy with respect to their location being revealed, but remains in effect only as long as the authorities need to determine the caller's location. The interpretati... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.7 Transfer of data during emergency calls | Emergency calls may be supplemented with emergency related data [1]. Typically this data enables the accurate geographic location of a manually or automatically activated emergency calling device e.g. an in vehicle system (IVS), to be provided to the Public Safety Answering Point (PSAP).
The following requirements appl... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.8 Supplementary service interaction during emergency calls | Supplementary services that interrupt or divert the media path between a PSAP and the end device shall be handled as specified in TS 22.173 [40] (e.g. Communication Hold) for Multimedia Telephony. No such Supplementary Services are applicable to CS Emergency Calls (TS12) according to TS 22.004 [5].
10.9 Emergency Calls... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.10 Emergency Services over Non-public networks | Subject to local/regional regulations, the 5G system shall support IMS Multimedia Emergency services (see clause10.4) over non-public network (NPN) [59] for NPNs using IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.11 Short Message Service over IMS to emergency centre | EPS and 5GS shall route a Short Message over IMS using the emergency numbers to a local emergency response centre (i.e. PSAP), according to the local regulations.
The Short Message shall be routed to the emergency response centre serving the location where the subscriber is located and replies routed back to the subscr... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.12 Emergency Sessions over Relay UEs | Where the 5G system supports remote UE access to emergency sessions via relay UEs, the following requirements apply:
- Subject to local regulatory requirements, the UE shall first attempt to make an emergency session via any available network. If the UE fails to find a network that allows emergency sessions, the UE sha... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11 Numbering principles | The following network addressing schemes listed below shall be supported at the relevant domains:
- E.164,
- E.168,
- E.212,
- X.121
- Internet (including e.g. IP address, SIP URI). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1 Number portability | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.1 Requirements for CS CN domain | Some numbering schemes shall be fully independent of the supporting serving network and the home environment, allowing users to transfer this number to another home environment. For further information see 3GPP TS 22.066 [7].
An MSISDN shall be allocated to each new user at the start of a subscription. This number may ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.2 Requirements for PS CN domain | None identified. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.3 Requirements for IM CN subsystem | It shall be possible to offer number portability for E.164 numbers within IM CN subsystem. For further information see 3GPP TS 22.066 [7]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.2 Evolution path | Since 3GPP specifications aim to be aligned with IMT-2000, a primary goal in numbering is the provision of global user numbering in line with steps taken by the ITU - SG2.
The numbering scheme and network implementation chosen shall allow for international/global evolution. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.3 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.4 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.6 Private numbering | A user may wish to use private numbers for the purposes of calling frequent numbers. Therefore there is a requirement for the use, by the user, of Private Numbering Plans (PNPs). These schemes may belong to the user himself, to a home environment or a third-party. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7 Numbering schemes | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.1 Multiple numbering scheme | The standards shall support the possibility of allowing the bearer service associated with an MT call to be implicitly defined by the destination MSISDN, for example to use a different MSISDN to establish voice, fax or data. It will be possible for multiple MSISDNs to be associated with a single subscription. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.2 Single numbering scheme | The standards shall support the possibility of allowing MT calls of different bearer types (e.g. voice, fax, data) to be routed to a single MSISDN. It is recognised that the implementation of this may depend on the availability of bearer information associated with an incoming call from the adjoining transit network. I... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.3 Additional numbers | The 3GPP system shall support the possibility to assign an additional MSISDN, in addition to the original MSISDN, to a user with a connection to the PS CN domain. If this additional MSISDN is available, it shall be used for correlation of CS and IMS in voice call and service continuity as well as IMS Centralized Servic... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.8 Optimal routing | The implementation of the numbering scheme used shall allow for optimal routing; i.e. routing shall not take place simply on the number dialled.
See 3GPP TS 22.079 [8] for some scenarios for the CS CN domain. Optimal routing for IP services is supported by the All-IP Network [42].
11a Identification Requirements
11a.1 ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 12 Human Factors and user procedures | The User Interface (MMI) from the end-user's point of view should be as flexible as possible while still meeting the general service requirements. In addition, it should be capable of being updated so as to meet new services which are still to be envisaged.
In general, the following principles should be encompassed:
- ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13 UICC, USIM and Terminal | This clause defines the functional characteristics and requirements of the User Service Identity Module (USIM) and ISIM (IM Services Identity Module). The USIM/ISIM are applications residing on a UICC. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1 The USIM/ISIM and User Profiles | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.1 The USIM | Every USIM shall have a unique identity and shall be associated with one and only one home environment.
It shall be possible for a home environment to uniquely identify a user by the USIM.
The USIM shall be used to provide security features.
For access to services, provided by PS or CS CN domains, a valid USIM shall be... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.2 User Profiles | It shall be possible for a user to be associated with one or a number of user profiles, which the user can select and activate on a per call basis. The user profile contains information which may be used to personalise services for the user.
It shall be possible for one or more user profiles associated with the same us... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.3 UICC usage in GERAN only Terminals | In Release 5 and later, terminals supporting only GERAN shall support USIM.
NOTE: It is strongly recommended that manufacturers implement SIM support on GERAN only terminals until the population of SIMs in the market is reduced to a low level. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.4 Multiple USIMs per UICC | The standard shall support more than one USIM per UICC even when those USIMs are associated with different home environments. Only one of the USIMs or the SIM shall be active at a given time. While the UE is in idle mode, it shall be possible for the user to select/reselect one USIM application amongst those available ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2 The UICC | Characteristics including physical formats of a UICC are defined in TS 31.101[36].
Access to services via 3GPP system with a single UICC shall be possible.
NOTE 1: The UICC refers to either a physically distinct module, or to an embedded eUICC (e..g as defined in [62], [63]). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2.1 The UICC and Applications other than the USIM or ISIM | It shall be possible for the UICC to host other applications in addition to the USIM or ISIM, see figure 3. Service providers, subscribers or users may need to establish additional data or processes on the UICC. Each application on an UICC shall reside in its own domain (physical or logical). It shall be possible to ma... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2.2 Fast Access and Retrieval of Data from UICC | An optional "high speed" interface may be provided between the UICC and the ME.
If provided, this interface shall allow fast access and retrieval of data to support functionalities requiring large amounts of data to be transferred to and from the UICC. Examples include:
- on-card web servers
- rapid access to data stor... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.3 Terminals and Multiple UICCs | A single terminal may support the use of multiple UICC (e.g. with applications like USIM and/or banking, credit card,...). Only one UICC shall be active at a time to access a PLMN. In case the active UICC contains more than one USIM, the requirements of 13.1.4 shall apply.
If the UICC with the active USIM is removed fr... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.4 Multiple USIMs | With the growing demand in the consumer market, some commercially deployed UEs support more than one USIM (typically two). With support of MUSIM UEs in the 3GPP system, the system performance and user experiences are expected to be improved.
The 3GPP system shall support ME with multiple USIMs (on the same UICC or on d... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 14 Types of features of UEs | 3GPP specifications should support a wide variety of user equipment, i.e. setting any limitations on terminals should be avoided as much as possible. For example user equipment like hand-portable phones, personal digital assistants and laptop computers can clearly be seen as likely terminals.
In order not to limit the ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15 Relationship between subscription and service delivery | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.1 Subscription | A subscription describes the commercial relationship between the subscriber and the service provider.
Figure 4: Subscriber, subscription and services relationship
A subscription to a network operator may provide the user with access to one or more domains. A Subscription shall identify the set of services, within parti... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.2 Other concepts associated with services | Provision of services:
An action to make a service available to a subscriber. The provision may be:
• general: where the service is made available to all subscribers (subject to compatibility restrictions enforced) without prior arrangements being made with the service provider;
• pre‑arranged: where the service is mad... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3 Requirements concerning service delivery | In general, it is a requirement to allow the use of independent services simultaneously (i.e. Basic, PS, IP multimedia and operator specific).
1) The network usage shall be based on the services identified within the subscription, the terminal capabilities and, where applicable, roaming agreements between operators.
2)... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3.1 Mobile Originated Voice calls | When a ME capable of offering voice service both on CS and IMS is CS attached and IMS registered MO CS Voice calls (TS11) and MO IMS voice services shall be originated on the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3.2 Mobile Terminated Voice calls | When a ME capable of offering voice service both on CS and IMS, MT CS Voice calls (TS11) and MT IMS voice services shall be delivered over the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences. If the call delivery attempt fails in one ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 16 Charging principles | The cost of the call may cover the cost of sending, transporting, delivery and storage. The cost of call related signalling may also be included. Provision shall be made for charging based on time, destination, location, volume, bandwidth, access technology and quality. Charges may also be levied as a result of the use... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17 Roaming | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17.1 Assumptions | In order to roam, the following applies:
- Mobile terminal can connect to the radio access network.
- Authentication (charging/billing network) must occur in order to get access to services (except for emergency calls).
- The services offered to a roaming subscriber may be restricted by the capabilities of the visited ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17.3 Requirements | Figure 5: Roaming requirements
- The personalised services & capabilities available in a visited network are dependent upon the subscription options in the home environment. This does not preclude the visited network offering additional services, or access to content providers.
- Roaming from this release's home enviro... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 18 Handover Requirements | Any handover required to maintain an active service while a user is mobile within the coverage area of a given network, shall be seamless from the user's perspective. However handovers that occur between different radio environments may result in a change of the quality of service experienced by the user.
It shall be p... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 19 Network Selection | Network selection procedures are defined in 3GPP TS 22.011 [11].
Other procedures may be offered by the UE. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 20 Security | Security matters are considered in 3GPP TS 21.133 [15] and 3GPP TS 33.120 [16]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21 Voice Call Continuity | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.1 General | The 3GPP system shall be able to provide continuity between CS voice services (Teleservice 11[14]) and the full duplex speech component of IMS multimedia telephony service [40] with no negative impact upon the user's experience of the voice service. This functionality is known as voice call continuity. Voice call conti... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2 Support of Supplementary Services | The voice call continuity user's experience shall be such that, to the greatest degree possible, a consistency of service is provided regardless of the underlying communication infrastructure and technology. With regard to supplementary services, the general principle is that CS-based supplementary services only apply ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.1 Line Identification Services | A user who has subscribed to the CLIP Supplementary Service and receives a call shall also receive the line identity or appropriate IMS information of the calling party.
The identity presentation is not changed for the duration of the call regardless of whether the call undergoes VCC.
If the CLIR Supplementary Service ... |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.2 All Call Forwardings | It shall be possible to perform VCC on a call which was forwarded due to call forwarding supplementary services in the CS or redirecting services in the IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.3 Call Waiting | The functionality of call waiting supplementary service in the CS domain shall not be affected by the user's ability to undergo VCC.
NOTE: Whether the user will continue to receive call waiting notifications in the case their call is continued in the IMS will depend on whether a call waiting service is available in the... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.