hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3.1.3 Disabling EAS IP Replacement Procedure
|
Figure 6.3.3.1.3-1: Disabling EAS IP replacement procedure
1. Local PSA performs FARs as instructed by SMF, which results in EAS IP address replacement:
- For UL traffic, the destination IP address and port number are replaced with the old Target EAS IP address and port number;
- For DL traffic, the source IP addr... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3.2 Enhancement to AF Influence
| The AF may additionally include Source and Target EAS IP address(es) and Port number(s) in the Nnef_TrafficInfluence_Create/Update or Nnef_TrafficInfluence_AppRelocationInfo or Nsmf_EventExposure_AppRelocationInfo request. Based on the Source EAS IP address(es) and Port number(s), the SMF knows which service flow(s) is... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.4 AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation
| EAS relocation can make use of network capabilities that, at PSA change, provide simultaneous connectivity over the source and the target PSA during a transient period. This is described in Annex F.
AF may issue a request to the network on whether to provide simultaneous connectivity over the source and the target PSA... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.5 Packet Buffering for Low Packet Loss
| This procedure aims at synchronizing between EAS relocation and UL traffic from the UE, ensuring that UL traffic from the UE is sent to the new EAS only when EAS context transfer has been carried out.
This procedure may be applied at change of local PSA. It consists of buffering uplink packets in the target PSA in ord... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.6 Edge Relocation Considering User Plane Latency Requirement
| Edge relocation may be performed considering user plane latency requirements provided by the AF.
In a network deployment where the estimated user plane latency between the UE and the potential PSA-UPF is known to the SMF, the 5GC provides the enhancement of AF influence to consider the user plane latency requirements ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.7 Edge Relocation Triggered by AF
| The AF may invoke the AF request targeting an individual UE address procedure as described in clause 4.3.6.4 of TS 23.502 [3], due to EAS relocation. The EAS relocation may be due to AF internal triggers e.g. EAS load balance or maintenance, etc. or due to UP path change notification from SMF. The EAS relocation may in... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.4 Network Exposure to Edge Application Server
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.4.1 General
| Some real time network information, e.g. user path latency, are useful for application layer. In this release, in order to expose network information timely to local AF, the L-PSA UPF may expose i.e. QoS monitoring results as defined in clause 5.33.3 of TS 23.501 [2], to the local AF.
NOTE 1: Local PSA UPF can expose ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.4.2 Network Exposure to Edge Application Server
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.4.2.1 Usage of Nupf_EventExposure to Report QoS Monitoring results
| The UPF may be instructed to report information about a PDU Session directly i.e. bypassing the SMF and the PCF. This reporting may target an Edge Application Server (EAS) or a local AF that itself interfaces the EAS.
Local NEF deployed at the edge may be used to support network exposure with low latency to local AF. ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.4.2.2 Local NEF Discovery
| As specified in clause 6.2.5.0 of TS 23.501 [2], the NRF may be used by the AF to discover the L-NEF. To become discoverable, the L-NEF registers with an NRF deployed within the operator's domain where the AF resides.
The AF uses existing procedures as described in clause 4.17.4 of TS 23.502 [3] to discover the L-NEF.... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5 Support of 3GPP Application Layer Architecture for Enabling Edge Computing
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.1 General
| The 3GPP application layer architecture for Enabling Edge Computing that is specified in TS 23.558 [5] includes the following functional entities:
- Edge Enabler Client (EEC).
- Edge Configuration Server (ECS).
- Edge Enabler Server (EES).
A UE may host EEC(s) as defined in TS 23.558 [5] and support the ability to ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2 ECS Address Provisioning
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.1 ECS Address Configuration Information
| The ECS Address Configuration Information consists of one or more ECS Configuration Information as defined in clause 8.3.2.1 of TS 23.558 [5]. The ECS Configuration Information may contain Spatial Validity Conditions, which includes one of the following alternatives:
- a Geographical Service Area (see TS 23.558 [5]);
... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.2 ECS Address Configuration Information Provisioning to the UE
| If the UE hosts an EEC and supports transferring the ECS address received from the 5GC to the EEC, the UE indicates in the PCO at PDU Session establishment that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s) (see TS 23.502 [3]). As described in TS 23.502 [3]... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.3 ECS Address Provisioning by a 3rd Party AF
| As described in TS 23.558 [5], the Edge Configuration Server can be deployed in a 3rd party domain by a service provider. An AF in the MNO domain or, if the Edge Configuration Server is deployed in a 3rd party domain by a service provider, a 3rd party AF can use Nnef_ParameterProvision to provide, update, or delete AF ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.4 ECS Address Provisioning by MNO
| The ECS Address Configuration Information can be provisioned by the MNO subscription provisioning in UDM.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.5 Interworking with EPC
| In interworking scenarios, if the UE hosts an EEC and supports transferring the ECS address received from the 5GC to the EEC, the UE indicates in the PCO at PDN Connection establishment that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s) (see TS 23.502 [3]) ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.6 ECS Address Provisioning in Roaming
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.6.1 General
| For both LBO and HR case, the subscription data of the ECS Address Configuration Information in UDM or UDR is stored per PLMN ID.
For the LBO case, an AF in the visited PLMN may provide the EACI via External Parameter Provisioning procedure as described in clause 4.15.6.3d in TS 23.502 [3] to UDM via H-NEF. This ECS A... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.6.2 ECS Address Configuration Information Provision from AF via NEF in VPLMN
| The AF provides non-PDU Session specific ECS Address Configuration Information via NEF in VPLMN to 5GC is defined in this clause.
Figure 6.5.2.6.2-1 ECS Address Configuration Information provisioning to UDR via NEF in VPLMN
1. The AF invokes the Nnef_ECSAddress_Create /Update/Delete service operation to provide ECS... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.5.2.6.3 ECS Address Configuration Information Provision to the SMF in VPLMN
| V-SMF supporting HR-SBO may receive the ECS Address Configuration Information from NEF in VPLMN via Subscribe/Notify procedure is defined in this clause.
Figure 6.5.2.6.3-1: ECS Address Configuration Information provisioning to SMF in VPLMN
1-2. As pre-requisite condition, the SMF subscribes to ECS Address Configur... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.6 Support of AF Guidance to PCF Determination of Proper URSP Rules
| This clause describes how an Edge Computing related AF may send guidance to PCF determination of proper URSP rules to send to the UE.
NOTE 1: This clause can apply in all deployment models.
An AF related with Edge computing may need to guide PCF determination of proper URSP rules. The guidance sent by the AF may appl... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7 Support of the local traffic routing in VPLMN for Home Routed PDU Session for roaming (HR-SBO)
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.1 General
| When roaming, the UE establishes a Home Routed Session that is capable of supporting session breakout in V-PLMN based on the subscription. In this scenario, the Home PLMN and Visited PLMN have an agreement on the support of the local traffic routing (i.e. session breakout performed by V-SMF also called HR-SBO) in VPLMN... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2 Procedure
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.1 General
| This clause describes the authorization procedure of the local traffic offloading using HR PDU Session and EAS discovery procedure supporting HR-SBO.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.2 PDU Session establishment for supporting HR-SBO in VPLMN
|
Figure 6.7.2.2-1: Procedure for PDU Session establishment supporting HR-SBO in VPLMN
1. During the Registration procedure, the AMF receives the HR-SBO allowed indication per DNN/S-NSNAI from the UDM in the step 14b of the procedure in the clause 4.2.2.2.2 of TS 23.502 [3].
2. During the PDU Session Establishment pr... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.3 EAS Discovery Procedure with V-EASDF for HR-SBO
|
Figure 6.7.2.3-1: Procedure for EAS Discovery with V-EASDF for HR-SBO roaming scenario
1. The DNS query sent by the UE reaches the UL CL UPF in VPLMN selected in step 2 of clause 6.7.2.2. The UL CL UPF forwards it to Local PSA UPF then to V-EASDF, or to H-UPF as described below.
If the target FQDN of the DNS query... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.4 EAS Discovery Procedure with Local DNS for HR-SBO
|
Figure 6.7.2.4-1: Procedure for EAS Discovery with local DNS for HR-SBO roaming scenario
The procedure in this clause assumes that the UL CL is able to detect FQDN(s) in traffic sent to the IP address of the local DNS Server. It is thus incompatible with usage of DoT (DNS over TLS) or DoH to protect the DNS traffic ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.5 EAS discovery procedure with V-EASDF/Local DNS Server using IP replacement mechanism for supporting HR-SBO
| Based on the operator's configuration and local regulations, the IP replacement mechanism may be used for EAS discovery supporting HR-SBO:
- The H-SMF sends DNS server address provided by the HPLMN included in PCO to UE via V-SMF during PDU Session Establishment/Modification procedure. The DNS query related to the edg... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.6 N2 Handover with V-SMF insertion/change/removal in HR-SBO case
| This clause defines the procedure for intra-VPLMN and inter-PLMN N2-based handover for HR-SBO PDU Sessions with V-SMF insertion/change/removal. This procedure is based on Inter NG-RAN node N2-based handover with I-SMF insertion/change/removal defined in TS 23.502 [3] clause 4.23.7.3 by replacing the I-SMF as V-SMF and ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.7 Inter V-SMF mobility registration update procedure in HR-SBO case
| This clause defines the procedure for inter V-SMF intra-VPLMN and inter-PLMN mobility registration update procedure for HR-SBO PDU Sessions. This procedure is based on I-SMF insertion/change/removal defined in clauses 4.23.3 and 4.23.4.3 of TS 23.502 [3] by replacing the I-SMF as V-SMF and replacing the SMF as H-SMF.
... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.8 N2 Handover without V-SMF change in HR-SBO case
| This clause defines the procedure for intra-VPLMN N2-based handover without V-SMF change for HR-SBO PDU Session. This procedure is based on Inter NG-RAN node N2-based handover without I-SMF change defined in TS 23.502 [3] clause 4.23.7.2.
The procedure described in clauses 4.23.17, 4.23.7.2, 4.9.1.3.2 and 4.9.1.3.3 of... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.9 Xn Handover with V-SMF change in HR-SBO case
| This clause defines the procedure for Xn handover with intra-PLMN V-SMF change for HR-SBO PDU Session. This procedure is based on Xn based handover with re-allocation of I-SMF defined in TS 23.502 [3] clause 4.23.11.3.
The procedure described in clauses 4.23.17 and 4.23.11.3 of TS 23.502 [3] is performed by replacing ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.2.10 Xn Handover without V-SMF change in HR-SBO case
| This clause defines the procedure for Xn handover without V-SMF change for HR-SBO PDU Session. This procedure is based on Xn based handover without change of I-SMF defined in TS 23.502 [3] clause 4.23.11.5.
The procedure described in clauses 4.23.17 and 4.23.11.5 of TS 23.502 [3] is performed by replacing I-SMF with V... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.3 EAS Re-discovery and Edge Relocation Procedure
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.3.1 General
| The EAS re-discovery and edge relocation in VPLMN can be triggered due to UE mobility, AF interacting with HPLMN, or AF interacting with VPLMN.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.3.2 Network triggered EAS change in HR-SBO context
| Figure 6.7.3.2-1 shows the procedure of EAS re-discovery and edge relocation when HR-SBO is supported and allowed in the target serving PLMN (i.e. V-SMF change or insertion).
NOTE 1: For the V-SMF removal case, the AF triggers EAS relocation refer to clause 6.2.3.3.
Figure 6.7.3.2-1: Network triggered EAS rediscove... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5 The V-SMF may configure the V-UPF (UL CL and L-PSA) with EAS IP replacement information.
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.7.4 AF request on PDU Sessions supporting HR-SBO
| For HR-SBO PDU Sessions, the AF may interact with VPLMN or HPLMN in order to send an AF request to influence traffic routing. The AF is assumed to check whether it has an SLA with the serving PLMN. If the AF has no SLA with the serving VPLMN, the AF interacts with HPLMN (H-NEF or H-PCF) to issue traffic influence reque... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.8 Support for mapping between EAS address Information and DNAI
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.8.1 General
| In order to make sure the AF can query for DNAIs, the 5GS may help determine proper DNAI(s) and notify the information to AF based on AF request providing EAS address information (i.e. IP address(es), EAS IP range(s) or FQDN(s)).
NEF/UDR is configured by OAM with the mapping information between EAS IP address informat... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.8.2 AF request for DNAI Procedures
|
Figure 6.8.2-1: AF request for DNAI based on AF request
1. AF invokes Nnef_DNAIMapping_Subscribe service to request the DNAI information. The request includes EAS address information and optionally: DNN, S-NSSAI and AF Identifier.
If mapping information is stored in NEF, skip step 2-3.
2. If the mapping informati... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.9 Use of N6 Delay Measurement
| To enhance EAS and local UPF (re)selection by considering N6 delay measurements per pair of 5GC N6 termination point (i.e. UPF/L-PSA) and the measurement endpoint at application side, as described in clause 4.3.3 of TS 23.502 [3].
The N6 delay measurement results received from the UPF may be used by the SMF in the fol... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10 Support of the Local Offloading Management
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.1 General
| In edge computing deployment, to reduce the impact on a centrally deployed SMF on management of the edge computing related information, 5GS may support the Local Offloading Management.
In Distributed Anchor Point and Multiple PDU Sessions connectivity models (see clause 4.3), the existing means such as URSP and SSC mo... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.2 Procedure
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.2.1 General
| This clause describes the procedures related to Local Offloading Management.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.2.2 I-SMF insertion during the PDU Session establishment
|
Figure 6.10.2.2-1: Procedure for PDU Session establishment supporting Local Offloading Management
1. During the Registration procedure, the AMF receives the Local Offloading Management allowed indication per DNN/S-NSSAI as part of SMF selection subscription data from the UDM in the step 14b of the procedure in the c... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.2.3 EAS Discovery Procedure with EASDF for Local Offloading Management
| The EAS Discovery Procedure with EASDF for Local Offloading Management follows the same procedure as defined in clause 6.7.2.3, with the following differences:
- General:
- VPLMN is replaced by HPLMN;
- V-EASDF is replaced by EASDF;
- H-UPF is replaced by UPF;
- H-SMF is replaced by SMF;
- V-SMF is replaced by I-... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.2.4 UE mobility for PDU session supporting Local Offloading Management
| For a PDU session supporting Local Offloading Management, during mobility events, e.g. Hand-Over or AMF change, the mobility handling is executed same as the respective mobility handling defined in clause 4.23 of TS 23.502 [3] and clause 6.7.2 with the following difference:
- The retrieval of the Local Offloading Mana... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.3 Policy provisioning for Local Offloading Management
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.3.1 General
| For Local Offloading Management, traffic routing related policy (e.g. Local Offloading Management Information) need be provided to the I-SMF. AF provides traffic influence request as defined in clause 4.3.6 of TS 23.502 [3], and procedure as defined in clause 4.23.6 of TS 23.502 [3] is performed to provision the relate... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.10.3.2 Local offloading management policy handling
| The Local Offloading Management Policy may be dynamically generated by PCF and retrieved by SMF for Local Offloading Management as described in clause 6.10.2. The Local offloading Management Policy may be provided with a Offload Identifier. The Offload Identifier is assigned by PCF.
The SMF (including SMF which may ac... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7 Network Function Services and Descriptions
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1 EASDF Services
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.1 General
| The following table illustrates the EASDF Services and Service Operations.
Table 7.1.1-1: NF services provided by the EASDF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Neasdf_DNSContext
Create
Request/Response
SMF/I-SMF
Update
Request/Response
SMF/I-SMF
Delete
Request/Respo... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2 Neasdf_DNSContext Service
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2.1 General
| Service description: This service enables the consumer to create, update, or delete DNS context in EASDF and to Subscribe to DNS message related reporting from EASDF.
DNS contexts in EASDF include rules on how EASDF is to handle DNS messages.
This service also can be supported by V-EASDF in VPLMN for HR scenario supp... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2.2 Neasdf_DNSContext_Create Service Operation
| Service operation name: Neasdf_DNSContext_Create
Description: Create a DNS context in EASDF.
Input, Required: UE IP address, DNN, S-NSSAI, Notification Endpoint.
Input, Optional: HPLMN ID, DNS message handling rules, N6 traffic routing information (towards the Local PSA-UPF).
NOTE 1: In HR-SBO scenario, the V-SMF c... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2.3 Neasdf_DNSContext_Update Service Operation
| Service operation name: Neasdf_DNSContext_Update
Description: Update the DNS context in EASDF, or indicate EASDF to forward the DNS Response to UE.
Input, Required: EASDF Context ID, updated DNS message handling rules.
Input, Optional: UE IP address, N6 traffic routing information (towards the Local PSA-UPF).
NOTE:... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2.4 Neasdf_DNSContext_Delete Service Operation
| Service operation name: Neasdf_DNSContext_Delete
Description: Delete the DNS context in EASDF.
Input, Required: EASDF Context ID.
Input, Optional: None.
Output, Required: Result Indication.
Output, Optional: None.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.2.5 Neasdf_DNSContext_Notify Service Operation
| Service operation name: Neasdf_DNSContext_Notify
Description: EASDF reports DNS message related information to the consumer when receiving DNS Query or DNS Response.
Input, Required: DNS message reporting information (DNS message content specified in clause 6.2.3.2.2 and corresponding DNS message type), Notification ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.3 Neasdf_BaselineDNSPattern Service
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.3.1 General
| This service provides the capability to create, update or remove BaselineDNSPattern in EASDF. See clause 6.2.3.4.4 for detailed procedure.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.3.2 Neasdf_BaselineDNSPattern_Create Service Operation
| Service operation name: Neasdf_BaselineDNSPattern_Create
Description: Create the BaselineDNSPattern in EASDF.
Input, Required: BaselineDNSPattern.
Input, Optional: None.
Output, Required: Success or Failure.
Output, Optional:
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.3.3 Neasdf_BaselineDNSPattern_Update Service Operation
| Service operation name: Neasdf_BaselineDNSPattern_Update
Description: Update the BaselineDNSPattern in EASDF.
Input, Required: Updated BaselineDNSPattern.
Input, Optional: None.
Output, Required: Success or Failure.
Output, Optional: None.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 7.1.3.4 Neasdf_BaselineDNSPattern_Delete Service Operation
| Service operation name: Neasdf_BaselineDNSPattern_Delete
Description: Delete the BaselineDNSPattern in EASDF.
Input, Required: Baseline DNS message detection template ID and/or Baseline DNS handling actions ID.
Input, Optional: None.
Output, Required: Result.
Output, Optional: None.
Annex A (Informative):
EAS ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 1 Scope
| The present document specifies the functional architecture, procedures, information flows and APIs for MSGin5G Service. MSGin5G Service provides messaging communication capability in 5GS especially for Massive Internet of Things (MIoT).
MSGin5G Service includes the following message communication models:
- Point-to... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 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.
-... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3 Definitions, symbols and abbreviations
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 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].
AS-to-Point messaging: an MSGin5G message delivery that is originated at ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3.3 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].
5GS 5G System
AOMT AS-Originated Mobile-Terminated
AS Applicat... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4 Architectural requirements
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.1 General
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.1.1 Description
| This subclause specifies the general architecture requirements for MSGin5G Service.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.1.2 Requirements
| [AR-4.1.2-a] The MSGin5G Client shall support one or more applications which need to use the MSGin5G message exchanging capabilities.
[AR-4.1.2-b] The MSGin5G Server shall support one or more Applications Servers which support the MSGin5G message exchanging capabilities.
[AR-4.1.2-c] The MSGin5G messaging related cap... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.2 UE types
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.2.1 Description
| This subclause specifies the requirements for UE types supported by MSGin5G Service.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.2.2 Requirements
| [AR-4.2.2-a] The application architecture shall support the message exchanging between the following UE types:
1. MSGin5G UE:
1) constrained devices (e.g. sensors, actuators) and
2) unconstrained devices with advanced capabilities (e.g. washing machine, micro-ovens)
2. Legacy 3GPP UE
3. Non-3GPP UE
[AR-4.2.2-... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.3 Communication models
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.3.1 Description
| This subclause specifies the requirements for MSGin5G communication models.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.3.2 Requirements
| [AR-4.3.2-a] The application architecture shall support the following message communication models:
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 1 Point-to-Point message;
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 2 Application-to-Point message/ Point-to-Application message;
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3 Group message;
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4 Broadcast message.
| [AR-4.3.2-b] The application architecture shall support interconnecting between the MSGin5G Service and other different messaging delivery mechanisms, (e.g. SMS as specified in 3GPP TS23.040 [15], or RCS message as specified in GSMA PRD RCC.07 [3]).
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.4 Charging
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.4.1 Introduction
| This subclause specifies the charging related requirements for the MSGin5G Service.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4.4.2 Requirements
| [AR-4.4.2] The MSGin5G Server shall support collecting charging information from MSGin5G message according to the operator's charging policy including charge per message, charge by amount of data, and flat rate (e.g., per month or per year).
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5 Application layer architecture
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.1 General
| The following aspects of MSGin5G Service are described in this clause:
- application architecture;
- functional entities;
- reference points;
- capability exposure for enabling MSGin5G Service; and
- service-based interface representation for MSGin5G Service.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.2 Application Architecture
| Figure 5.2-1 shows the application architecture of the MSGin5G service. The MSGin5G service shall fulfil the service requirements which are enumerated in 3GPP TS 22.262 [2] and the architecture requirements enumerated in clause 4.
Figure 5.2-1: Application Architecture of the MSGin5G Service
The Application Client ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3 Functional entities
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.1 General
| The functional entities of the application architecture for the MSGin5G Service are described in this clause.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.2 MSGin5G Server
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.2.1 General functionalities
| An MSGin5G Server provides server-side functionality to assist MSGin5G Clients with the sending and receiving of messages via the MSGin5G Service to/from Application Servers and/or other MSGin5G Service endpoints on other UEs, and collect charging information from MSGin5G message.
Functionalities of MSGin5G Server:
-... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.