hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.18.3 APIs
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.18.3.1 General
| The APIs as defined in clause 8.5.4 are used to perform EAS discovery in partner ECSP.
See clause 8.18.2.3.2, clause 8.18.2.3.3 and clause 8.18.2.3.4 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19 Common EAS announcement
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.1 General
| Common EAS announcement procedure enables an EES to exchange selected common EAS information with other EES(s).
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.2 Procedure
| Pre-conditions:
1. The announcing EES may be pre-configured with the EES information of other receiving EES(s), which belongs to the same EDN; or
2. The announcing EES may receive the list of receiving EES(s) information (e.g. address information) from the EEC during the EAS information provisioning procedure.
Fig... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.3 Information flows
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.3.1 General
| The information flows are specified for Announce common EAS request and response.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.3.2 Announce common EAS request
| Table 8.19.3.2-1 describes the information elements for Announce common EAS request from the announcing EES to the receiving EES.
Table 8.19.3.2-1: Announce common EAS request
Information element
Status
Description
Requestor identifier
M
The identifier of the announcing EES.
Security credentials
M
Security cr... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.3.3 Announce common EAS response
| Table 8.19.3.2-1 describes the information elements for Announce common EAS response from the receiving EES to the announcing EES.
Table 8.19.3.3-1: Announce common EAS response
Information element
Status
Description
Successful response
O
Indicates that the request was successful.
UE ID
O
The identifier of t... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.4 APIs
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.4.1 General
| Table 8.19.4.1-1 illustrates the API for common EAS announcement.
Table 8.19.4.1-1: Eees_CommonEASAnnouncement API
API Name
API Operations
Operation
Semantics
Consumer(s)
Eees_CommonEasAnnouncement
Declare
Request/Response
EES
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.19.4.2 Eees_CommonEasAnnouncement_Declare operation
| API operation name: Eees_CommonEasAnnouncement_Declare
Description: The consumer declares common EAS information to the EES.
Inputs: See clause 8.19.3.2.
Outputs: See clause 8.19.3.3.
See clause 8.19.2 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20 Interaction with ECS with Repository function
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.1 General
| This clause describes procedures and services provided by the ECS with Repository function (ECS-ER), which is applicable when the ECS-ER is available.
NOTE: ECS can support repository function as ECS-ER.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2 Procedure
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2.1 General
| Clause 8.20.2.2, clause 8.20.2.3, clause 8.20.2.4, and clause 8.20.2.5 illustrate the application group specific EAS information retrieval procedures.
The procedures for Common EAS information store/removal/update in clause 8.20.2.2, clause 8.20.2.3, clause 8.20.2.4, and clause 8.20.2.5 enable an EES to exchange selec... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2.2 Obtain EAS information
|
Figure 8.20.2.2-1: Obtain EAS information
1. The EES sends EAS information get request message to the ECS-ER. The request message includes EAS ID and Application Group ID, and may include bundled EAS ID list and main EAS ID or EAS bundle ID.
2. Upon receiving the request, the ECS-ER checks if there are any stored E... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2.3 Common EAS information storage
| Pre-condition:
1. The EES is registered in the ECS supporting repository function.
Figure 8.20.2.3-1: Common EAS information storage
1. The EES sends Common EAS information store request message to the ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint and Application Group ID, and ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2.4 Common EAS information removal
| Pre-condition:
1. Common EAS is deregistered from the common EES.
Editor's note: It is FFS about other triggers for common EES to use this procedure.
Figure 8.20.2.4-1: Common EAS information removal
1. The common EES sends Common EAS information remove request message to the ECS-ER. The request message includes... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.2.5 Common EAS information update
|
Figure 8.20.2.5-1: Common EAS information update
1. The EES sends Common EAS information update request message to the ECS-ER. The request message includes EDN information, EES ID, EAS ID, EAS endpoint and Application Group ID.
2. Upon receiving the request, the ECS-ER checks if there is any stored EAS serving the ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3 Information flows
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.1 General
| The information flows are specified for EAS information service.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.2 EAS information get request
| Table 8.20.3.2-1 describes the information elements for EAS information get request from the EES to the ECS-ER.
Table 8.20.3.2-1: EAS information get request
Information element
Status
Description
Requestor identifier
M
The identifier of the EES.
Security credentials
M
Security credentials resulting from a su... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.3 EAS information get response
| Table 8.20.3.3-1 describes the information elements for EAS information get response from the ECS-ER to the EES.
Table 8.20.3.3-1: EAS information get response
Information element
Status
Description
Successful response (NOTE 1)
O
Indicates that the request was successful.
> EAS information (NOTE 2)
M
This IE ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.4 Common EAS information store request
| Table 8.20.3.4-1 describes the information elements for common EAS information store request from the EES to the ECS-ER.
Table 8.20.3.4-1: Common EAS information store request
Information element
Status
Description
Requestor identifier
M
The identifier of the EES.
Security credentials
M
Security credentials r... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.5 Common EAS information store response
| Table 8.20.3.5-1 describes the information elements for common EAS information store response from the ECS-ER to the EES.
Table 8.20.3.5-1: Common EAS information store response
Information element
Status
Description
Successful response (NOTE)
O
Indicates that the request was successful.
Failure response (NOTE)... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.6 Common EAS information remove request
| Table 8.20.3.6-1 describes the information elements for common EAS information remove request from the EES to the ECS-ER.
Table 8.20.3.6-1: Common EAS information remove request
Information element
Status
Description
Requestor identifier
M
The identifier of the EES.
Security credentials
M
Security credentials... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.7 Common EAS information remove response
| Table 8.20.3.7-1 describes the information elements for common EAS information remove response from the ECS-ER to the EES.
Table 8.20.3.7-1: Common EAS information remove response
Information element
Status
Description
Successful response (NOTE)
O
Indicates that the request was successful.
Failure response (NOT... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.8 Common EAS information update request
| Table 8.20.3.8-1 describes the information elements for common EAS information update request from the EES to the ECS-ER.
Table 8.20.3.8-1: Common EAS information update request
Information element
Status
Description
Requestor identifier
M
The identifier of the EES.
Security credentials
M
Security credentials... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.3.9 Common EAS information update response
| Table 8.20.3.9-1 describes the information elements for common EAS information update response from the ECS-ER to the EES.
Table 8.20.3.9-1: Common EAS information update response
Information element
Status
Description
Successful response (NOTE)
O
Indicates that the request was successful.
Failure response (NOT... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4 APIs
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4.1 General
| Table 8.20.4.1-1 illustrates the API for EAS information management.
Table 8.20.4.1-1: EAS information management APIs
API Name
API Operations
Operation
Semantics
Consumer(s)
Eecs_EASInfoManagement
Store
Request/Response
EES
Update
Request/Response
EES
Remove
Request/Response
EES
Get
Request/Res... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4.2 Eecs_EASInfoManagement_Store operation
| API operation name: Eecs_EASInfoManagement_Store
Description: The consumer requests EAS information storage service from the ECS.
Inputs: See clause 8.20.3.4.
Outputs: See clause 8.20.3.5.
See clause 8.20.2.3 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4.3 Eecs_EASInfoManagement_Get operation
| API operation name: Eecs_EASInfoManagement_Get
Description: The consumer obtains EAS information from the ECS.
Inputs: See clause 8.20.3.2.
Outputs: See clause 8.20.3.3.
See clause 8.20.2.2 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4.4 Eecs_EASInfoManagement_Remove operation
| API operation name: Eecs_EASInfoManagement_Remove
Description: The consumer requests to remove EAS information from the ECS.
Inputs: See clause 8.20.3.6.
Outputs: See clause 8.20.3.7.
See clause 8.20.2.4 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 8.20.4.5 Eecs_EASInfoManagement_Update operation
| API operation name: Eecs_EASInfoManagement_Update
Description: The consumer requests EAS information update service from the ECS.
Inputs: See clause 8.20.3.8.
Outputs: See clause 8.20.3.9.
See clause 8.20.2.5 for details of usage of this operation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 9 Usage of SEAL services
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 9.1 Notification management service
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 9.1.1 General
| The notification management is a SEAL service that offers the notification functionality. This service enables EEC to subscribe and receive notifications from the EES and ECS, and thereby offloading the complexity of delivery and reception of notifications to the edge enabler layer.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 9.1.2 Information flows
| The following information flows of notification management service of SEAL as specified in 3GPP TS 23.434 [13] are applicable for the EEL:
- Create notification channel request specified in clause 17.3.2.1;
- Create notification channel response specified in clause 17.3.2.2;
- Open notification channel specified in ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 9.1.3 Procedures
| The following procedures of notification management service of SEAL as specified in 3GPP TS 23.434 [13] are applicable for the edge enabler layer:
- Procedure for creating notification channel to receive notifications, specified in clause 17.3.3.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 10 Edge service reliability support
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 10.1 General
| By adopting the NF set and NF service set approach, as specified in clause 5.21.3 of 3GPP TS 23.501 [2], edge server set enable edge service producers (e.g. EES/ECS) in the data network to provide reliable services to the edge service consumers (e.g. EAS, EEC).
Equivalent edge servers may be grouped into edge server s... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11 Edge Enabler Using Satellite Access
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1 General
| This clause provides clarifications on the procedures and information flows necessary for enabling edge application using satellite access.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1.1 EES determination based on UE serving satellite ID Procedure
| This procedure is applicable for EDN deployment with gNB on satellite.
A satellite EDN may be deployed as described in Annex A.2.5. The service provisioning procedure for satellite EDN is the same as clause 8.3.3.2.2 and clause 8.3.3.2.3 with the following clarifications.
When UE connects to the satellite, the servic... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1.2 EES determination based on UE location and route Procedure
| This procedure and the corresponding EES profile and Service provisioning request are applicable for EDN deployment with gNB on satellite.
A satellite EDN may be deployed as described in Annex A.2.5. The service provisioning procedure for satellite EDN is the same as clause 8.3.3.2.2 and clause 8.3.3.2.3 with the foll... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1.2.1 EES profile
| The EES profile is same as clause 8.2.6 with the following additions.
Table 11.1.2.1-1: EES Profile
Information element
Status
Description
IEs from Table 8.2.6-1
Dynamic service area indication
O
Indicates if the service area is mobile or not. The service area is dynamic in case of EES on board a MEO or LEO sa... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1.2.2 Service provisioning request
| Table 11.1.2.2-1 is same as clause 8.3.3.3.2 Table 8.3.3.3.2-1 with the following additions.
Table 11.1.2.2-1: Service provisioning request
Information element
Status
Description
IEs from Table 8.3.3.3.2-1
UE serving Satellite ID
(NOTE 1)
O
The identifier of the satellite which is serving UE in current locatio... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 11.1.2.3 Service provisioning response
| Table 11.1.2.3-1 is same as clause 8.3.3.3.3 Table 8.3.3.3.3-2 with the following additions.
Table 11.1.2.3-1: EDN configuration information
Information element
Status
Description
IEs from Table 8.3.3.3.2-1
List of EESs
M
List of EESs of the EDN.
> EESID
M
The identifier of the EES
> EES Endpoint
M
The ... |
b647d725f39317e667005befaa44b373 | 23.632 | 1 Scope
| The present document defines the Stage 2 architecture, procedures, flows and Network Function Services for User Data Interworking, Coexistence and Migration within the 5G System.
|
b647d725f39317e667005befaa44b373 | 23.632 | 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.
-... |
b647d725f39317e667005befaa44b373 | 23.632 | 3 Definitions of terms, symbols and abbreviations
| |
b647d725f39317e667005befaa44b373 | 23.632 | 3.1 Terms
| For the purposes of the present document, the terms 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].
|
b647d725f39317e667005befaa44b373 | 23.632 | 3.2 Symbols
| Void
|
b647d725f39317e667005befaa44b373 | 23.632 | 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 UDR 5G Unified Data Repository
EPS UDR EPS User Data Reposi... |
b647d725f39317e667005befaa44b373 | 23.632 | 4 System architecture
| |
b647d725f39317e667005befaa44b373 | 23.632 | 4.1 Architecture for direct UDM-HSS interworking
| Figure 4.1-1 shows the reference architecture for direct UDM-HSS interworking.
Figure 4.1-1: Architecture for Direct UDM-HSS interworking
Non-SBA interfaces between the HSS and non-SBA network nodes include interfaces to / from the SMS-GMSC/IWMSC and SMS Router. In the Architecture for direct UDM-HSS interworking ,... |
b647d725f39317e667005befaa44b373 | 23.632 | 4.2 Reference points for direct UDM-HSS interworking
| The following reference points are realized by service-based interfaces:
NU1: Reference point between the HSS and the UDM.
NU2: Reference point between the HSS and the 5GS-UDR.
For a list of other SBA reference points supported in 5GC see 3GPP TS 23.501 [2].
For a list of IMS reference points, including SBA IMS ref... |
b647d725f39317e667005befaa44b373 | 23.632 | 4.3 Service based interfaces for direct UDM-HSS interworking
| Nudm: Service-based interface exhibited by UDM.
Nhss: Service-based interface exhibited by HSS.
The HSS shall make use of Nudm services as described in clause 6.2 and may make use of Nudr services as described in clause 6.3.
The UDM shall make use of Nhss services and Nudr services as described in clauses 6.1 and 6.... |
b647d725f39317e667005befaa44b373 | 23.632 | 4.4 Subscription Identifiers
| As defined in 3GPP TS 23.501 [2], for interworking with the EPC, the SUPI allocated to the 3GPP UE shall always be based on an IMSI to enable the UE to present an IMSI to the EPC.
The subscription identifier used over NU1 reference point in Nhss services shall be an IMSI. The UDM extracts the IMSI from the user's SUPI... |
b647d725f39317e667005befaa44b373 | 23.632 | 4.5 HSS Discovery and Selection
| This clause defines the procedures for HSS discovery and selection by the UDM. The procedures for HSS discovery and selection by SBI capable IMS entities is defined in 3GPP TS 23.228 [7].
The UDM performs HSS discovery to discover an HSS that manages the user subscriptions in EPC.
The UDM shall utilize the NRF to dis... |
b647d725f39317e667005befaa44b373 | 23.632 | 4.6 UDM Discovery and Selection
| The HSS performs UDM discovery and selection as described in 3GPP TS 23.501 [2].
|
b647d725f39317e667005befaa44b373 | 23.632 | 4.7 Subscription Profiles
| In the context of Mobility, IMS and SMS use cases, the HSS initiates interworking with the UDM only for UEs which have a 5G subscription that is known to be active in 5GC.
NOTE: The HSS may be aware that a 5G subscription for the UE exists based on the Core Network Type restrictions defined for the UE (i.e. If restric... |
b647d725f39317e667005befaa44b373 | 23.632 | 5 System procedures
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.1 General
| Procedures involving communication between HSS and UDM comprise Authentication, Mobilty, IMS interworking, SMS support, common Network Exposure and Common External Parameter Provisioning.
|
b647d725f39317e667005befaa44b373 | 23.632 | 5.2 Authentication
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.2.1 General
| A subscriber's authentication subscription data, including the subscriber's long-term key(s) and sequence number, shall be stored in a single repository so that a single sequence number can be maintained for the subscriber.
The subscriber's long-term key(s) shall not be transferred over the NU1 reference point between... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.2.2 Vector Generation in HSS
| This clause specifies the procedures for authentication vector request when the subscriber's authentication subscription data is stored at the EPS-UDR. In this case, the UDM requests the generation of the Authentication Vector for 5GS to the HSS.
NOTE: The HSS acts as ARPF rather than as AuC and it is required to gene... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.2.3 Vector Generation in UDM/ARPF
| This clause specifies the procedures for authentication vector request when the subscriber's authentication subscription data is stored at the 5GS-UDR. In this case, the HSS requests the generation of the Authentication Vector for EPS and/or IMS to the UDM.
NOTE: The UDM acts as AuC rather than as ARPF and it is requi... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.2.4 HSS using the Nudr SBI
| When the HSS receives an S6a-AIR from the MME, it may check (by means of an EPC-UDR query) whether the subscriber has an 5G subscription. If so, the HSS can use of the Nudr_DM_Query Get service operation to retrieve the authentication subscription data from the 5GS UDR and generate the authentication vector.
Figure 5.... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.3 5GC-EPC Mobility Scenarios
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.3.1 General
| As defined in 3GPP TS 23.501 [2], when interworking procedures with N26 are used, the UE operates in single-registration mode. For the 3GPP access, either the AMF or the MME is registered in the HSS+UDM. This implies that:
- The registration of an MME in HSS for a UE that is capable to access the 5GC, triggers the can... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.3.2 Mobility from 5GC to EPC
| Figure 5.3.2-1 shows the interaction between the HSS and UDM in an interworking scenario when the UE attaches to the EPC.
Figure 5.3.2-1: Mobility from 5GC to EPC
1. The HSS receives an S6a ULR request containing the IMSI of the subscriber.
The HSS stores the new MME address. If the EPC UDR is used, the HSS updat... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.3.3 Mobility from EPC to 5GC
| Figure 5.3.3-1 shows the interaction between the UDM and the HSS in an interworking scenario when the UE attaches to the 5GC.
Figure 5.3.3-1: Mobility from EPC to 5GC
1. The UDM receives a Nudm_UECM_Registration request for 3GPP access containing the SUPI of the subscriber. In this case the SUPI shall be based on a... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.3.4 Support for PDU session continuity during intersystem mobility procedures
| When the UE is connected to 5GS or 5GC-N3IWF, the PGW-C+SMF may store in UDM the PGW-C+SMF FQDN for S5/S8/S2b interface, within the UE context in SMF data, when the PWG-C+SMF registers in UDM. The AMF serving 3GPP access may also notify the UDM to store the association between DNN or emergency session and PGW-C+SMF FQD... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4 Scenarios of Interworking with IMS
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.0 General
| The following clauses assume that the HSS (and EPS-UDR) supports IMS procedures and EPS procedures. However, in EPS-less deployments where the HSS supports only IMS procedures, the EPS-UDR may store only IMS profile information and IMPI-IMSI associations, but no EPS-Profile information. In such deployments the HSS can ... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.1 T-ADS
| Figure 5.4.1-1 shows the scenario where the HSS receives a T-ADS request from the AS for a subscriber who has a 5GC subscription.
Figure 5.4.1-1: T-ADS request for 5G subscriber
1. The HSS receives a T-ADS request from the AS. The request includes the user's IMPU or MSISDN and optionally the user's IMPI.
NOTE: An... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.2 P-CSCF Restoration
| Figure 5.4.2-1 shows the scenario where the HSS receives a P-CSCF restoration indication from the S-CSCF for a subscriber who has a 5GC subscription.
Figure 5.4.2-1: P-CSCF Restoration for 5G subscriber
1. The HSS receives a P-CSCF Restoration indication from the S-CSCF. The request includes the user's IMPU and IMP... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.3 Network Provided Location Information Request
| Figure 5.4.3-1 shows the scenario where the HSS receives a Location Information retrieval request from the IMS-AS for a subscriber who has a 5GC subscription.
Figure 5.4.3-1: Location Information retrieval request for 5G subscriber
1. The HSS receives a Location Information retrieval request (requested nodes includ... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.4 User State Retrieval
| Figure 5.4.4-1 shows the scenario where the HSS receives a PS User State retrieval request from the IMS-AS for a subscriber who has a 5GC subscription.
Figure 5.4.4-1: PS User State retrieval request for 5G subscriber
1. The HSS receives a PS User State retrieval request (requested nodes includes AMF) from the IMS-... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.5 UE Reachability
| Figure 5.4.5-1 shows the scenario where the HSS receives a Subscription to notification request for UE-reachability from the IMS-AS for a subscriber who has a 5GC subscription.
Figure 5.4.5-1: Subscription to UE reachability for 5G subscriber
1. The HSS receives a Subscribe request for UE reachability for IP from ... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.6 IMEI Retrieval
| A pre-requisite for the retrieval of the IMEI when requested by an IMS-AS is that the IMEI for a given UE stored in HSS and UDM is always synchronized. This is, when the HSS detects that the IMEI for a UE changes (e.g. during an Update Location in EPS), the HSS informs the UDM about the IMEI change which stores the new... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.7 SRVCC: IMS AS obtaining SRVCC data
| Figure 5.4.7-1 shows the scenario where the HSS communicates with the IMS-AS in support of (5G) SRVCC for a subscriber who has a 5GC subscription. An operator shall be able to control whether the interaction between HSS and UDM is performed based on local policy.
Figure 5.4.7-1: IMS AS obtaining data related to (5G)... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.8 SRVCC: IMS AS obtaining SRVCC data – HSS using Nudr
| When the HSS receives an S6a-AIR from the MME, it may check (by means of an EPC-UDR query) whether the subscriber has a 5G subscription. If so, the HSS can use of the Nudr_DM_Query Get service operation to retrieve the 5G SRVCC subscription data from the 5GS UDR.
Figure 5.4.8-1 shows the scenario where the HSS communi... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.4.9 SRVCC: IMS AS updating STN-SR
| Figure 5.4.9-1 shows the scenario where the IMS-AS updates the STN-SR at the HSS. An operator shall be able to control whether the interaction between HSS and UDM is performed based on local policy.
Figure 5.4.9-1: Updating STN-SR
1. As described in 3GPP TS 23.237 [13], the IMS-AS can use Sh-Update to provide the S... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5 SMS Support
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.1 General
| Potential MT-SMS target nodes in the EPS are the MME/MSC and the SGSN registered at the HSS, while in 5GS MT-SMS target nodes are the 3GPP-SMSF and the Non3GPP-SMSF registered at the UDM. For the role of SMS-Router and IP-SM-GW see 3GPP TS 23.040 [12].
|
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.2 MT-SMS Routing Information Retrieval
| Figure 5.5.2-1 shows the interaction when the SMS-GMSC retrieves routing information from the HSS for MT-SMS delivery.
Figure 5.5.2-1: SMS Routing Info Retrieval
1. The HSS receives a request for routing information from the SMS-GMSC via MAP or S6c.
2. The HSS queries the EPS-UDR via Ud to read the registered MME/... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.3 MT-SMS Delivery Failure
| Figure 5.5.3-1 shows the interaction when the SMS-GMSC sends Report-SM-Delivery-Status to the HSS.
Figure 5.5.3-1: MT-SMS Delivery Failure
1. The HSS receives a Report-SM-Delivery-Status from the SMS-GMSC indicating the MT-SMS target nodes at which MT-SMS delivery was unsuccessful.
2-3. The HSS reads and updates t... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.4 SMS Alerting
| Figure 5.5.4-1 shows the interaction when the UE becomes available.
Figure 5.5.4-1: SMS Alerting
1. The UDM receives a Notification from the AMF or an SMSF Registration.
2-3. The UDM queries the 5GS-UDR to see whether any NF (e.g. the HSS) has subscribed to notifications on UE-reachability for SMS events and/or "U... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.5 MT-SMS Routing Information Retrieval Over Nudr
| Figure 5.5.5-1 shows the interaction when the SMS-GMSC retrieves routing information from the HSS for MT-SMS delivery when the HSS uses the Nudr SBI.
Figure 5.5.5-1: SMS Routing Info Retrieval over Nudr
1. The HSS receives a request for routing information from the SMS-GMSC via MAP or S6c.
2. The HSS queries the E... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.6 Support for SMS over IP
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.6.1 General
| In deployment scenarios where 2G/3G/4G accesses are available, SMS over IP is supported as described in 3GPP TS 23.204 [18], and the interactions between HSS and UDM are those defined in clauses 5.5.2, 5.5.3 and 5.5.4.
For MT-SMS delivery over 5G NAS in deployment scenarios where support for SMS over IP is also requir... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.6.2 IP-SM-GW registration and SMS routing information retrieval in 5GC only deployments
| Figure 5.5.6.2-1 shows the interaction for the registration of the IP-SM-GW address in the UDM and subsequent SMS routing information retrieval.
Figure 5.5.6.2-1: IP-SM-GW registration in UDM and SMS routing info retrieval in 5GC only deployments
1. The IP-SM-GW registers its address in HSS (IMS) via Sh as define... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.6.3 MT SMS delivery failure in 5GC only deployments
| Figure 5.5.6.3-1 shows the interactions for the unsuccessful MT SMS delivery case in a 5GC only deployment requiring SMSoIP.
Figure 5.5.6.3-1: MT SMS delivery failure in 5GC only deployments supporting SMSoIP
1 - 7. The message delivery fails after the IP‑SM‑GW has tried all selectable domains, and the IP-SM-GW f... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.5.6.4 Alert Service Centre in 5GC only deployments
| Figure 5.5.6.4-1 shows the interactions when the UE becomes available in a 5GC only deployment requiring SMSoIP.
Figure 5.5.6.4-1: Alert Service Centre procedure in 5GC only deployments supporting SMSoIP
The steps described below are based on the procedure described in clause 6.5b of 3GPP TS 23.204 [18], consider... |
b647d725f39317e667005befaa44b373 | 23.632 | 5.6 Common Network Exposure Scenarios
| |
b647d725f39317e667005befaa44b373 | 23.632 | 5.6.1 General
| As specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [5], a combined SCEF+NEF can configure monitoring events applicable to both EPC and 5GC using only 5GC procedures towards UDM. In this case, the SCEF+NEF indicates that the monitoring event is also applicable to EPC together with the SCEF identity, i.e. the event mu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.