hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.1.2 Manual SNPN selection mode procedure
| The MS indicates to the user any available SNPNs which meet the criteria specified in bullets a) and b). If the MS does not support access to an SNPN using credentials from a credentials holder, this includes SNPNs in the list of "permanently forbidden SNPNs", and the list of "temporarily forbidden SNPNs". The MS may i... |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.1.3 Automatic SNPN selection mode procedure for onboarding services in SNPN
| When the MS needs to access an SNPN for onboarding services in SNPN, the MS shall select an SNPN indicating that onboarding is allowed and, if the onboarding SNPN selection information is pre-configured, also matching the onboarding SNPN selection information. If more than one such SNPNs are available, how the MS selec... |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.1.4 Manual SNPN selection mode procedure for onboarding services in SNPN
| The MS shall indicate to upper layers one or more SNPNs, which are available and indicate that onboarding is allowed.
These include SNPNs in the list of "permanently forbidden SNPNs for onboarding services in SNPN" and the list of "temporarily forbidden SNPNs for onboarding services in SNPN". The MS may indicate to th... |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.1.5 Void
| |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.2 User reselection
| |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.2.0 General
| At any time the user may request the MS to initiate reselection and registration onto an available SNPN, according to the following procedures, dependent upon the SNPN selection mode of the UE.
|
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.2.1 Automatic SNPN selection mode
| If:
- there is at least one entry in the "list of subscriber data"; or
- there is zero or more entries in the "list of subscriber data", the MS has a USIM with a PLMN subscription and the ME is provisioned with the SNPN selection parameters associated with the PLMN subscription,
the MS shall select one entry in the ... |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.2.2 Manual SNPN selection mode procedure
| The manual SNPN selection mode procedure of clause 4.9.3.1.2 is followed.
|
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.3.3 Additional conditions for SNPN selection for MS supports access to an SNPN providing access for localized services in SNPN
| If the MS supports access to an SNPN providing access for localized services in SNPN, the UE is in automatic SNPN selection mode and:
a) access for localized services in SNPN is changed between disabled and enabled; or
b) access for localized services in SNPN is enabled; and:
1) the selected SNPN is an SNPN selected... |
a21c68cd05f339296826517e9a705288 | 23.122 | 4.9.4 Abnormal cases
| If:
a) the MS does not support access to an SNPN using credentials from a credentials holder and:
1) the "list of subscriber data" is empty; or
2) for each entry of the "list of subscriber data", such that an SNPN with the SNPN identity of the entry or an equivalent SNPN, is available:
i) there has been an authenti... |
a21c68cd05f339296826517e9a705288 | 23.122 | 5 Tables and Figures
| Table 1: Effect of LR Outcomes on PLMN Registration
Location Registration Task State
Registration Status
Registered PLMN is
Updated
Successful
Indicated in the stored registration area identity
Idle, No IMSI
Unsuccessful
No registered PLMN (3) (4)
Roaming not allowed:
a) PLMN not allowed
Unsuccessful
N... |
a21c68cd05f339296826517e9a705288 | 23.122 | 6 MS supporting access technologies defined both by 3GPP and 3GPP2
| |
a21c68cd05f339296826517e9a705288 | 23.122 | 6.1 General
| An MS that supports access technologies defined both by 3GPP and 3GPP2 (see 3GPP TS 31.102 [40]) shall consider all supported access technologies in all supported bands when performing PLMN selection.
The goal of the PLMN selection process for such a multi mode MS is to find the highest priority PLMN and to attempt to... |
33899db2c6851096b26181357e548f46 | 23.167 | 1 Scope
| This document defines the stage 2 service description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services and IM emergency services for eCall. ITU‑T Recommendation I.130 [4] describes a three-stage method for charact... |
33899db2c6851096b26181357e548f46 | 23.167 | 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.
-... |
33899db2c6851096b26181357e548f46 | 23.167 | 3 Definitions, symbols and abbreviations
| |
33899db2c6851096b26181357e548f46 | 23.167 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [11] 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 [11].
Charging Data Record: Record generated by a network element for the purpose of bi... |
33899db2c6851096b26181357e548f46 | 23.167 | 3.2 Abbreviations
| For the purposes of the present document, the following abbreviations apply:
CDR Charging Data Record
CLF Connectivity session Location and repository Function
CS Circuit Switched
DRVCC Dual Radio Voice Call Continuity
E‑CSCF Emergency‑CSCF
EATF Emergency Access Transfer Function
ECS Emergency Call Server
ESQK ... |
33899db2c6851096b26181357e548f46 | 23.167 | 4 High level Principles
| |
33899db2c6851096b26181357e548f46 | 23.167 | 4.1 Architectural Principles
| The solution for emergency sessions in the IMS fulfils the emergency principles and requirements of TS 22.101 [8], TS 22.228 [27] and the following architectural requirements:
1. Void.
2. Emergency services are independent from the IP-CAN with respect to the detection and routing of emergency sessions. The emergency ... |
33899db2c6851096b26181357e548f46 | 23.167 | 20 A UE should support a capability to obtain local emergency numbers from the network once such a capability has been defined and agreed.
| 21. The network (e.g. in the E‑CSCF) shall prevent the sending of the information of the users, such as public user identifiers and the location information, to the PSAP if explicitly requested by the user (i.e. request on session by session basis) and local regulation requires the operator to provide privacy to the us... |
33899db2c6851096b26181357e548f46 | 23.167 | 25 Subject to local regulation, for non-roaming subscribers the network shall apply normal routing procedures for private network traffic even if that is marked as emergency session.
| 26. When a call is established with a PSAP that supports voice only, voice media is supported and GTT if required by local regulation or operator policy.
27. When a call is established with a PSAP that supports voice and other media, voice, GTT and other media according to TS 22.101 [8] (e.g. video, session mode text-... |
33899db2c6851096b26181357e548f46 | 23.167 | 4.2 Naming and Addressing
| When a UE performs an emergency registration, barring and roaming restrictions are ignored. The implicit registration set of the Public User Identifier used for emergency registrations shall contain an associated TEL‑URI.
NOTE: Annex G provides recommendations for the provisioning of TEL‑URI(s) in the IMS subscription... |
33899db2c6851096b26181357e548f46 | 23.167 | 4.3 Location information for Emergency Sessions
| Location information is needed for 2 main reasons in emergency services. The initial purpose of the location information is to enable the IMS network to determine which PSAP serves the area where the UE is currently located, so that the IMS network can route the emergency session to the correct PSAP. The second purpose... |
33899db2c6851096b26181357e548f46 | 23.167 | 4.3.1 General Location Information Principles
| The following general principles shall apply regarding the handling of location information:
- If the UE has location information available, the UE shall include the location information in the request to establish an emergency session. The location information may consist of network location information, that is the ... |
33899db2c6851096b26181357e548f46 | 23.167 | 4.3.2 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 4.4 IP-CAN
| The following are the expectations on the IP-CAN for IMS emergency services:
- Except for emergency services over WLAN access to EPC or non-3GPP access to 5GC, it shall be possible to access the IP-CAN without sufficient security credentials.
- It shall be possible to reject requests from UE without sufficient securi... |
33899db2c6851096b26181357e548f46 | 23.167 | 4.5 Media
| - When the call is established with a PSAP that supports voice only, voice and subject to local regulation, GTT media is allowed during the IMS emergency session.
- When the call is established with a PSAP that supports voice and other media, subject to UE and network support for the other media and local regulation, ... |
33899db2c6851096b26181357e548f46 | 23.167 | 5 Architecture model and reference points
| |
33899db2c6851096b26181357e548f46 | 23.167 | 5.1 Reference architecture
| This specification introduces an additional CSCF role to those defined in the IMS architecture TS 23.002 [12], called Emergency CSCF (E‑CSCF), see figure 5.1.
Legend:
Dashed lines: optional interfaces
Figure 5.1: E‑CSCF in reference architecture
NOTE 1: P‑CSCF, MSC Server enhanced for ICS, EATF and E-CSCF are a... |
33899db2c6851096b26181357e548f46 | 23.167 | 5.2 Reference points
| The E‑CSCF uses Mw, Mg, Mi, Ml, Mm, Mx and I4 reference points to connect to other IMS entities and other IP Networks.
I4 is a reference point between an E-CSCF and an EATF. See TS 23.237 [32].
I5 is a reference point between an I‑CSCF and an EATF. See TS 23.237 [32].
I6 is a reference point between an MSC Server en... |
33899db2c6851096b26181357e548f46 | 23.167 | 6 Functional description
| |
33899db2c6851096b26181357e548f46 | 23.167 | 6.1 UE
| - Should be able to detect an emergency session establishment request.
- In the case of NG-eCall, the IMS emergency session establishment request may be invoked either automatically without user input or manually via user input.
- Initiate an IMS emergency registration request.
- The UE may perform an IMS emergency ... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2 IMS Functional entities
| |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.1 Proxy‑CSCF
| - Handle registration requests with an emergency registration indication like any other registration request, except that it may reject an emergency registration request if the IM CN subsystem that the P‑CSCF belongs to can not support emergency sessions for the UE (e.g. due to operator policy or UE is not within IM CN... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.2 Emergency‑CSCF
| - Receive an emergency session establishment request from a P‑CSCF or an S-CSCF.
- If the UE does not have credentials, a non-dialable callback number shall be derived where required by local regulation (e.g. see Annex C of J‑STD‑036 [23]).
- If location information is not included in the emergency request or additio... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.3 Location Retrieval Function
| The Location Retrieval Function (LRF) is responsible for retrieving the location information of the UE that has initiated an IMS emergency session. It shall be possible to support configurations where the Location Retrieval Function (LRF) may consist of a Routing Determination Function (RDF) and a LS, the interface bet... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.4 Serving-CSCF
| When the S‑CSCF receives an Emergency Registration, the S‑CSCF determine the duration of the registration by checking the value of the Expires header in the received REGISTER request and based on local regulation or operator policy of the serving system.
NOTE 1: The value of the emergency registration time is subject ... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.5 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.6 Emergency Access Transfer Function (EATF)
| The EATF provides IMS emergency session continuity which is specified in TS 23.237 [32].
|
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.7 Interrogating-CSCF
| I-CSCF supports IMS emergency session continuity which is specified in TS 23.237 [32].
|
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.8 AS
| An AS can be involved in emergency session handling (e.g. for emergency sessions made via hosted enterprise services ETSI TS 182 024 [37], or for AS initiated session).
NOTE 1: The participation of an AS in emergency session handling is only expected over a non-emergency registration.
Dependent on the service provide... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.9 HSS
| In the course of an emergency registration, the HSS shall not apply any barring condition and/or roaming restriction associated with the Public User Identity received in the emergency registration request.
The emergency registration shall be handled with the considerations defined in clause 6.2.4.
|
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.10 Media Gateway Control Function (MGCF)
| For NG-eCall MGCF handles the emergency session as normal emergency call establishment.
NOTE: The MGCF does not forward the initial MSD, if received in the emergency session request.
|
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.11 MSC Server enhanced with ICS
| The MSC Server enhanced with ICS may provide interworking mechanisms to support emergency call using CS media bearer and using IMS for routing/handling the emergency call toward PSAP. From the view point of E-CSCF, MSC Server enhanced with ICS behaves like a P-CSCF. Further details on MSC Server procedure are defined i... |
33899db2c6851096b26181357e548f46 | 23.167 | 6.2.12 IBCF
| - Forward emergency session establishment requests.
- Prioritize the emergency session based on operator policy.
- For an emergency session leaving an IBCF, the IBCF, if configured through operator policies, invokes an AS for the signing of attested caller identity and asserted Resource-Priority information, if avail... |
33899db2c6851096b26181357e548f46 | 23.167 | 7 Procedures related to establishment of IMS emergency session
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.1 High Level Procedures for IMS Emergency Services
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.1.1 UE Detectable Emergency Session
| The following flow contains a high level description of the emergency service procedures performed when the UE can detect the emergency session is being requested.
Figure 7.1: Terminal Detected Emergency Calls
The following steps are performed:
1. The UE detects the request for the establishment of an emergency se... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.1.2 Non UE detectable Emergency Session
| As the UE could not detect the emergency session, the session establishment request will be sent to a P‑CSCF in the visited PLMN or a P‑CSCF in the home PLMN as per a normal session establishment procedure. The former is only applicable to a roaming situation whereas the latter can apply to both a roaming and non-roami... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.1.3 Emergency Session Establishment using LRF/RDF
| Figure 7.2 illustrates a high level call flow for the IMS emergency session establishment procedure using LRF/RDF to retrieve location and routing information.
Figure 7.2: Emergency Session Establishment procedure with using LRF/RDF
1. UE initiates an emergency session request by sending a SIP INVITE message with i... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.2 IMS Registration for Emergency Session
| The IMS emergency registration procedure shall follow the procedures as described in clause 5.2.2.3 of TS 23.228 [1] with the following modifications:
- The UE shall initiate an IMS emergency registration when all of the following conditions are met:
- either the UE is not already IMS registered or the UE is IMS regi... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.3 Emergency Session Establishment in the Serving IMS network
| If the UE is able to detect that the user is requesting an emergency session then it shall include an emergency service indication in the emergency session establishment request. In the case of NG-eCall, the UE shall include the eCall type of emergency service (automatic or manual) in the emergency session establishmen... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.4 IMS Emergency Session Establishment without Registration
| When the UE initiates an emergency session establishment without prior IMS registration, it shall include both the "anonymous user" and "emergency service" indications in the emergency session establishment request to the P‑CSCF.
Based on local regulation, the P‑CSCF may reject "anonymous user" emergency session estab... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.5 Interworking with PSAP
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.5.1 PSAP/Emergency centre located at the GSTN
| No special procedure is defined. PSAP uses the MSISDN (E.164) of the user for call back. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
33899db2c6851096b26181357e548f46 | 23.167 | 7.5.2 PSAP/Emergency centre connected via IP using SIP
| No special procedure is defined. PSAP uses any public user identity that it has received from the user for call back. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
33899db2c6851096b26181357e548f46 | 23.167 | 7.5.3 PSAP/Emergency centre connected via ECS
| No special procedures are identified in IMS Core, the routing determination will be performed by the ECS. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
33899db2c6851096b26181357e548f46 | 23.167 | 7.5.4 PSAP supporting NG-eCall
| It is assumed that the PSAP supporting the NG-eCall shall be able to receive and verify the consistency of the initial MSD within the initial SIP INVITE.
|
33899db2c6851096b26181357e548f46 | 23.167 | 7.6 Retrieving Location information for Emergency Session
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.6.1 Acquiring location information from the UE or the network
| When performing an emergency service, four scenarios for retrieving location information for routing purposes are considered:
- the UE knows its own location;
- the UE retrieves its location information from the network;
- the IMS core retrieves the location information. The related high level procedures are describ... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.6.2 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.6.3 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7 Transfer of MSD for eCall
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.1 MSD Transfer/Acknowledgement during Session Establishment with PSAP supporting NG-eCall
| Figure 7.7.1-1 illustrates a high level call flow for an interworking scenario between a UE and a PSAP supporting NG-eCall.
This scenario occurs, when the UE detects that the NG-eCall is supported by the IP-CAN.
Figure 7.7.1-1: NG-eCall Scenario with PSAP supporting NG-eCall
1. The UE performs steps 1 to 6 of the ... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.2 MSD Transfer/Acknowledgement during Session Establishment with a PSAP Not supporting NG-eCall (inband means)
| Figure 7.7.2-1 illustrates a high level call flow for an interworking scenario between a UE and a PSAP via the CS domain.
This scenario may occur in the case, when PS access is available, but the UE does not detect that the NG-eCall is supported by the IP-CAN and there is no CS access available. In this case, the UE s... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.3 Transfer of an updated MSD
| Figure 7.7.3-1 illustrates a high level call flow for transfer of an updated MSD in the case that the emergency centre or PSAP is accessed via the PS domain. The call flow is applicable following establishment of an emergency services session for eCall as described in clause 7.1.1 in which the initial MSD is transferre... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.4 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.5 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.6 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.7 Void
| |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.8 Callback from an NG capable PSAP with transfer of updated MSD
| Figure 7.7.8-1 illustrates a high level call flow for callback to a UE from an NG capable PSAP with transfer of updated MSD after the UE has established an eCall over IMS with the PSAP using the procedure in clause 7.7.1.
Figure 7.7.8-1: Callback from an NG capable PSAP with transfer of updated MSD
1. The UE and PS... |
33899db2c6851096b26181357e548f46 | 23.167 | 7.7.9 Callback from a PSAP in the CS domain with transfer of updated MSD
| Figure 7.7.9-1 illustrates a high level call flow for callback to a UE from a PSAP in the CS domain with transfer of updated MSD.
This scenario may occur following eCall session establishment and release with a PSAP not supporting NG-eCall as in clause 7.7.2 or may occur following eCall session establishment and relea... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 1 Scope
| This document specifies the functional architecture, procedures and information flows needed to support mission critical services in the IOPS mode of operation. IOPS mode of operation allows an isolated 3GPP network to maintain a level of MC services in case the backhaul connection is lost. For example, for EPS the IOP... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 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.
-... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 3 Definitions and abbreviations
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
IOPS MC system: The collection of application functions and enabling capa... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
APN Access Point Name
DNN Data Network Name
IOPS Isolated Oper... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 4 Introduction
| For the case of a backhaul failure, mission critical (MC) services (e.g. MCPTT defined in 3GPP TS 23.379 [5] and MCData defined in 3GPP TS 23.282 [6]) can also be supported based on the availability of an isolated operation for public safety (IOPS) MC system. The IOPS MC system provides MC services support to the MC se... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5 Architectural requirements
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.1 General requirements
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.1.1 Description
| This clause specifies the general requirements for the support of MC services in the IOPS mode of operation.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.1.2 Requirements
| [AR-5.1.2-a] For the case of a backhaul failure between the radio access network and the macro 3GPP core network, the IOPS MC system shall provide support for MC services in the IOPS mode of operation until the failure is recovered.
[AR-5.1.2-b] MC service UEs within the coverage of the local IOPS 3GPP systems shall b... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.2 MC service requirements
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.2.1 Description
| This clause specifies the MC service requirements in the IOPS mode of operation.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.2.2 Requirements
| [AR-5.2.2-a] The following MCPTT service features shall be supported in the IOPS mode of operation
- MCPTT group call
- MCPTT emergency group call
- MCPTT private call
- MCPTT emergency private call
[AR-5.2.2-b] The following MCData service features shall be supported in the IOPS mode of operation
- MCData short... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.3 Network broadcast/multicast session requirements
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.3.1 Description
| This clause specifies the network bearer requirements in the IOPS mode of operation.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.3.2 Requirements
| [AR-5.3.2-a] The IOPS MC system shall provide support for unicast session establishment and modification to support MC services via unicast transmissions in the IOPS mode of operation.
[AR-5.3.2-b] The IOPS MC system shall provide support for broadcast/multicast session establishment and modification to support MC ser... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.4 IP connectivity functionality
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.4.1 Description
| The support of MC services in the IOPS mode of operation can be based on the support of the IP connectivity functionality. The IP connectivity functionality enables that MC services are provided by the MC service clients via the IOPS MC connectivity function.
An IOPS MC connectivity function supporting the IP connect... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.4.2 General requirements
| [AR-5.4.2-a] The IOPS MC connectivity function supporting the IP connectivity functionality shall support discovering MC service users within the coverage of the local IOPS 3GPP system.
[AR-5.4.2-b] The IOPS MC connectivity function supporting the IP connectivity functionality shall support announcement, subscription ... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 5.4.3 Bearer management requirements
| [AR-5.4.3-a] The MC service UEs shall use specific APNs or DNNs for the support of the IP connectivity functionality, as follows:
- An APN/DNN for the IOPS related application signalling related to the IP connectivity functionality support, e.g. for IOPS discovery, subscription and notification.
- An MC service APN/D... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 6 Involved business relationships
| The description of the involved business relationships for the support of MC services in the IOPS mode of operation is contained in clause 6 of 3GPP TS 23.280 [3], and clause 6.4 of 3GPP TS 23.289 [12].
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7 Functional model
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.1 General
| The functional model to support MC services in the IOPS mode of operation in case of a backhaul failure consists of a set of functions and reference points.
NOTE: Terminology such as client and server are not meant to imply specific physical implementation of a functional entity.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.2 Description of the planes
| The functional model for the support of MC services in the IOPS mode of operation is defined as a series of planes to allow for the breakdown of the architectural description.
The application plane supports all the necessary functions to establish and provide MC services in the IOPS mode of operation. The application ... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.3 Functional model description
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.3.1 General
| The application plane and signalling plane supporting the functional model for the IOPS mode of operation are described in this clause.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.3.2 Functional model for the signalling control plane in the IOPS mode of operation
| Figure 7.3.2-1 shows the common functional model for the signalling control plane in the IOPS mode of operation.
Figure 7.3.2-1: Functional model for the signalling control plane in the IOPS mode of operation
NOTE: The functional model for the signalling plane in the IOPS mode of operation is described as a common ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.