hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.5 Unsuccessful Mobile Terminated short message transfer without SMS Router/IP-SM-GW | Figure 5.1.5-1: Unsuccessful MT SMS over NAS without SMS Router/ IP-SM-GW
1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
2a. SMS-GMSC invokes the Nnrf_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the use... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.6 Unsuccessful Mobile Terminated short message transfer via IP-SM-GW | Figure 5.1.6-1: Unsuccessful MT SMS over NAS via IP-SM-GW
1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
2a. SMS-GMSC invokes the Nnrf_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7 GPSI-to-Subscription-Network resolution procedure | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.1 General | MT SMS delivery procedure requires routing based on the GPSI of the SMS recipient for interactions between the SMS-GMSC and the UDM, e.g., to retrieve the SMS routing information (e.g., the SMSF address) or report delivery status. In case that the SMS recipient belongs to a PLMN different from the PLMN of the SMS sende... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.2.1 General | Figure 5.1.7.2-1: GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC
1a-1b. The MNPF registers in the NRF with a new NF Type (e.g. MNPF).
2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
3a-3b. The SMS-GMSC should query the NRF to find the MNPF ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.2.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Direct routing | When MNP is implemented in a country or number portability domain with direct routing mechanism, the originating network first does the number portability query to identify the recipient GPSI's subscription PLMN before routing any messages based on GPSI.
Figure 5.1.7.2.2-1 GPSI-to-Subscription-Network resolution trigge... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.2.3 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Indirect routing | When MNP is implemented in a country or number portability domain with indirect routing mechanism, the signalling messages are always routed to the number range holder network, the number range holder then performs a number portability check and forwards the request to the subscription network if the number is ported o... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3 SCP supports GPSI-to-Subscription-Network resolution procedure | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3.1 General | This procedure is used to retrieve the PLMN ID of the recipients GPSI for further discovery of UDM NF profiles for invoking UDM service operation for routing information retrieval. In indirect Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3.2 SCP supports GPSI-to-Subscription-Network resolution with MNPF | Figure 5.1.7.3.2-1: SCP supports GPSI-to-Subscription-Network resolution with MNPF
1a-1b. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF).
2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
3. The SMS-GMSC sends Nudm_UECM_Se... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3.3 SCP supports GPSI-to-Subscription-Network resolution with NRF | Figure 5.1.7.3.3-1: SCP supports GPSI-to-Subscription-Network resolution with NRF
1a-1b. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF).
2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
3. The SMS-GMSC sends Nudm_UECM_Sen... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3.4 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Direct routing | Figure 5.1.7.3.4-1 shows the procedure for Direct Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service in MNPF and routes an SBI message based on GPSI when direct routing of MNPF is implemented.
Figure 5.1.7.3.4-1 SCP supports the GPSI-to-Subscri... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.3.5 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing | Figure 5.1.7.3.5-1 shows the procedure for Indirect Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service in MNPF NF and routes an SBI message based on GPSI when indirect routing of MNPF is implemented.
Figure 5.1.7.3.5-1 SCP supports GPSI-to-Subs... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.7.4 GPSI-to-Subscription-Network resolution using NRF | Figure 5.1.7.4-1 shows the procedure to determine the target PLMN based on the GPSI using the discovery and selection framework via the NRF as defined in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4].
Figure 5.1.7.4-1: Determination of target PLMN based on GPSI using NRF
1. The SMS-GMSC located in the PLMN of the SMS sende... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.8 Alert | Figure 5.1.8-1 depicts procedure for alert.
Figure 5.1.8-1: Procedure for alert
1 Unsuccessful Mobile Terminated short message transfer (without IP-SM-GW/SMS Router) procedure, as defined in steps 1-10 in Figure 5.1.5-1.
2 UDM receives Namf_EventExposure_Notify or Nudm_UECM_Registration operation from AMF or SMSF indic... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.1.9 Unsuccessful Mobile Terminated short message transfer via SMS Router | Figure 5.1.9-1: Unsuccessful MT SMS over NAS via SMS Router
1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2].
2a. SMS-GMSC invokes the Nnrf_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscription... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.2 Procedure for SBI-based MO SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.2.1 General | The procedure for SBI-based MO SMS is showed in Figure 5.2.2-1, which is based on MO SMS procedures in 3GPP TS 23.040 [2] clause 10.2. Compared to procedures in 3GPP TS 23.040 [2], new services are introduced in, including:
- Niwmsc_SMService service provided by SMS-IWMSC.
This new service is registered in NRF, and can... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.2.2 Procedure for Successful Mobile Originated short message transfer | Figure 5.2.2-1: Procedures for successful SBI-based SM MO message transfer
0 The SMS-IWMSC registers with the Niwmsc_SMService service in the NRF, during the NF registration procedure.
1 The MO SM message transfer from the UE to the SMSF through the AMF follows the current procedure as defined in 3GPP TS 23.040 [2]
2a ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.2.3 Unsuccessful Mobile Originated short message transfer | Figure 5.2.3-1 depicts procedure for unsuccessful SBI-based SM MO message transfer
Figure 5.2.3-1: Procedures for unsuccessful SBI-based SM MO message transfer
0-3 The same as the procedures in step 0-3 of Figure 5.2.2-1 in clause 5.2.2
4 SMS-IWMSC sends Niwmsc_SMService_MoForwardSm response with HTTP status code for a... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 5.2.4 MSISDN-less MO SMS message transfer | The procedure for SBI-based MSISDN-less MO SMS message transfer is depicted in Figure 5.2.4-1,
Figure 5.2.4-1: Procedures for MSISDN-less MO SMS message transfer
0 NEF registers Nnef_SMService_MoForwardSm service and supporting long/short code ranges in NRF, during the NF registration procedure.
1 MO SMS transmit from ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6 Services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.1 General | This clause introduces the services for SBI-based SMS. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2 UDM services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.1 General | The following table illustrates the UDM services for SBI-based SMS.
Table 6.2.1-1: UDM Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
UE Context Management (UECM)
SendRoutingInfoForSM
request / response
UDM
SMS-GMSC
ReportSMDeliveryStatus
Request
r... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.2 Nudm_ReportSMDeliveryStatus service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.2.1 General | For the Nudm_ReportSMDeliveryStatus service the following service operations are defined:
- Request |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.2.2 Nudm_ReportSMDeliveryStatus_Request service operation | Service operation name: Nudm_ReportSMDeliveryStatus_Request
Description: reports the SM-Delivery Status to UDM.
Inputs, Required: GPSI, SM-Delivery status
Inputs, Optional: None.
Outputs, Required: report SM-Delivery status result.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.3 Nudm_EventExposure service | Service Description: This service is defined in clause 5.2.3.5 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm_EventExposure for alert sc.
Except the existing events that are exposed by UDM, events "UE_MEMORY_AVAILABLE_FOR_SMS" and "UE_REACHABILITY_FOR_SMS" should be supported. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.2.4 Nudm_UECM service | Service Description: This service is defined in clause 5.2.3.2 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm_UECM service.
The new service operation SendRoutingInfoForSM shall be supported to get the target valid node(s) serving the UE from the UDM, which will be used by the SMS-GMSC t... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.3 SMS-IWMSC services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.3.1 General | The following table illustrates the SMS-IWMSC services for SBI-based SMS.
Table 6.3.1-1: SMS-IWMSC Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
SMService
MoForwardSm
request / response
SMS-IWMSC
SMSF, IP-SM-GW |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.3.2 Niwmsc_SMService service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.3.2.1 General | Service Description: This service can be used for SBI-based MO SM transfer and Delivery Report through SMS-IWMSC. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.3.2.2 Niwmsc_SMService_MoForwardSm service operation | Service operation name: Niwmsc_SMService_MoForwardSm.
Description: Service request from consumer to SMS-IWMSC for MO SM transmit.
Inputs, Required: the SM record to be sent, the Service Centre address, the callbackURI for MO SMS Delivery Report, the timer for waiting MO SMS Delivery Report.
Inputs, Optional: Access Typ... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.4 SMSF services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.4.1 General | The following table illustrates the SMSF services for SBI-based SMS.
Table 6.4.1-1: SMSF Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
SMService
MtForwardSm
request / response
SMSF
SMS-GMSC, IP-SM-GW, SMS Router |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.4.2 Nsmsf_SMService service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.4.2.1 General | Service Description: This service can be used for SBI-based MT SM transfer through SMSF. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.4.2.2 Nsmsf_SMService_MtForwardSm service operation | Service operation name: Nsmsf_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to SMSF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: SMS message transmission result.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5 IP-SM-GW services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5.1 General | The following table illustrates the IP-SM-GW services for SBI-based SMS.
Table 6.5.1-1: IP-SM-GW Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
SMService
RoutingInfo
request / response
IP-SM-GW
UDM
MtForwardSm
request / response
IP-SM-GW
SMS-GMSC |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5.2 Nipsmgw_SMService service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5.2.1 General | Service Description: This service can be used for SBI-based MT SM transfer through IP-SM-GW. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5.2.2 Nipsmgw_SMService_RoutingInfo service operation | Service operation name: Nipsmgw_SMService_RoutingInfo
Description: provides the SMSF Instance Id to the IP-SM-GW.
Inputs, Required: GPSI, SMSF Instance Id.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.5.2.3 Nipsmgw_SMService_MtForwardSm service operation | Service operation name: Nipsmgw_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to IP-SM-GW and return the MT SMS Delivery Report to the consumer NF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: MT SMS Delivery Report.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6 SMS Router services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6.1 General | The following table illustrates the SMS Router services for SBI-based SMS.
Table 6.6.1-1: SMS Router Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
SMService
RoutingInfo
request / response
SMS Router
UDM
MtForwardSm
request / response
SMS Router
SM... |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6.2 Nrouter_SMService service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6.2.1 General | Service Description: This service can be used for SBI-based MT SM transfer through SMS Router. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6.2.2 Nrouter_SMService_RoutingInfo service operation | Service operation name: Nrouter_SMService_RoutingInfo
Description: provides the SMSF Instance Id to the SMS Router.
Inputs, Required: GPSI, SMSF Instance Id.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.6.2.3 Nrouter_SMService_MtForwardSm service operation | Service operation name: Nrouter_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to SMS Router and return the MT SMS Delivery Report to the consumer NF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: MT SMS Delivery Report.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.7 MNPF services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.7.1 General | The following table illustrates the MNPF services for SBI-based SMS.
Table 6.7.1-1: MNPF Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
NPStatus
Get
request / response
MNPF
SMS-GMSC, SCP |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.7.2 Nmnpf_NPStatus service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.7.2.1 General | Service Description: This service can be used to retrieve the PLMN ID of the Subscription Network of a GPSI. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.7.2.2 Nmnpf_NPStatus_Get service operation | Service operation name: Nmnpf_NPStatus_Get
Description: retrieve the PLMN ID of the Subscription Network of a GPSI.
Inputs, Required: GPSI.
Inputs, Optional: None.
Outputs, Required: PLMN Id.
Outputs, Optional: None. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.8 NEF services for SBI-based SMS | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.8.1 General | The following table illustrates the NEF services for SBI-based SMS.
Table 6.8.1-1: NEF Services for SBI-based SMS
Service Name
Service Operations
Operation
Semantics
Service Provider(s)
Service Consumer(s)
SMService
MoForwardSm
request / response
NEF
SMS-SC |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.8.2 Nnef_SMService service | |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.8.2.1 General | This service can be used for SBI-based MO SM transfer through NEF for MSISDN-less MO SMS. |
18a39873ce7be4b55c8d872eda4ea87c | 23.540 | 6.8.2.2 Nnef_SMService_MoForwardSm service operation | Service operation name: Nnef_SMService_MoForwardSm Description: transmit MO SMS message from consumer NF to NEF. Inputs, Required: SMS payload, Application port ID, SUPI, destination SME address (long/short code of the AF). Inputs, Optional: None. Outputs, Required: SMS message transmission result. Outputs, Optional: N... |
06253d02247591cc2149faea837cc737 | 23.542 | 1 Scope
| The present document specifies the application enabler layer architecture, procedures and information flows necessary for enabling PIN applications over 3GPP networks. The specification includes the capabilities (e.g. PIN management, discovery of elements, capabilities and services related to PIN) at the application en... |
06253d02247591cc2149faea837cc737 | 23.542 | 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.
-... |
06253d02247591cc2149faea837cc737 | 23.542 | 3 Definitions of terms, symbols and abbreviations
| |
06253d02247591cc2149faea837cc737 | 23.542 | 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].
Access Control Information: A set of information that assists the authorized PINE in a PIN to acces... |
06253d02247591cc2149faea837cc737 | 23.542 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
06253d02247591cc2149faea837cc737 | 23.542 | 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].
PIN Personal IoT Network
PINAPP Personal IoT Network Application
PEMC P... |
06253d02247591cc2149faea837cc737 | 23.542 | 4 Overview
| |
06253d02247591cc2149faea837cc737 | 23.542 | 4.1 General
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5 Architectural requirements
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.1 General
| This clause specifies architectural requirements for enabling Personal IoT Networks in different functional aspects.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2 Architectural requirements
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.1 General requirements
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.1.1 General
| This clause specifies general requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.1.2 Requirements
| [AR-5.2.1.2-a] The application enablement layer architecture shall support deployment of personal IoT network.
[AR-5.2.1.2-b] The application enablement layer architecture shall support different deployment models in conjunction with an operator's 3GPP network.
[AR-5.2.1.2-c] The application enablement layer architec... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.2 PIN Management
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.2.1 General
| This clause specifies PIN management requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.2.2 Requirements
| [AR-5.2.2.2-a] The application enablement layer architecture shall provide mechanisms to create PIN for UE or PIN elements.
[AR-5.2.2.2-b] The application enablement layer architecture shall provide mechanisms to delete PIN, either triggered by PINEs or by PIN server.
[AR-5.2.2.2-c] The application enablement layer a... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.3 PIN enable 5GS communication
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.3.1 General
| This clause specifies PIN communication requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.3.2 Requirements
| [AR-5.2.3.2-a] The application enablement layer architecture shall provide mechanisms to configure routing information in PEGC to enable the PINE to access the network provided by PEGC.
[AR-5.2.3.2-b] The application enablement layer architecture shall provide mechanisms to support the PIN and the PINEs in PIN to cons... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.4 Service Switch
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.4.1 General
| This clause specifies service switch requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.4.2 Requirements
| [AR-5.2.4.2-a] The application enablement layer architecture shall provide mechanisms to support the service switching in a PIN between different PINE for achieving better service experience.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.5 Application server discovery
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.5.1 General
| This clause specifies application server discovery requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.5.2 Requirements
| [AR-5.2.5.2-a] The application enablement layer architecture shall provide mechanisms to support the application server discovery for PIN.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.6 Service continuity
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.6.1 General
| This clause specifies service continuity requirements for the architecture.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.6.2 Requirements
| [AR-5.2.6.2-a] The application enablement layer architecture shall provide mechanisms to support the PEGC relocation procedure to enable service continuity.
[AR-5.2.6.2-b] The application enablement layer architecture shall provide mechanisms to change the communication from via PEGC to via 5GS, and enable the service... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.7 Security
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.7.1 General
| This clause specifies PIN security requirements.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.7.2 Requirements
| [AR-5.2.7.2-a] Communication between the functional entities of the application enablement layer architecture shall be protected.
[AR-5.2.7.2-b] Access control mechanisms for authenticating functional entities of the application enablement layer architecture shall be provided.
[AR-5.2.7.2-c] Access control mechanisms... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.8 Subscription service
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.8.1 General
| This clause specifies the requirements for PIN subscription service.
|
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.8.2 Requirements
| [AR-5.2.8.2-a] The application enablement layer architecture shall provide subscription and notification mechanisms enabling to receive PIN modification information changes.
[AR-5.2.8.2-b] The application enablement layer architecture shall provide subscription and notification mechanisms enabling to receive PIN manag... |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.9 PIN application KPIs
| |
06253d02247591cc2149faea837cc737 | 23.542 | 5.2.9.1 General
| This clause specifies the requirements for PIN application KPIs.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.