hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.21 Namf_Communication_RelocateUEContext service operation | Service operation name: Namf_Communication_RelocateUEContext
Description: This service operation is used by an initial AMF to relocate the UE context in a target AMF during EPS to 5GS handover (per N26) procedures.
Input, Required: UE context of the identified UE, Source to Target RAN Transparent Container and the identification of target RAN, PDU Session ID and its associated S-NSSAI of the VPLMN value for each PDU Session, the corresponding S-NSSAI of HPLMN value for home routed PDU Session(s), content for EPS to 5GS handover (information to reach the MME about this UE (MME Control Plane F-TEID, MME addressing information), PDU Session ID and the S-NSSAI associated with corresponding N2 SM Information received from SMF). As described in Table 5.2.2.2.2-1, the UE context may include the SUPI, DRX parameters, AM policy information, UE Radio Capability ID, PCF ID, UE network capability, used N1 security context information, event subscriptions by other consumer NF, Allowed NSSAI received from NSSF and the list of SM PDU Session IDs with the corresponding SMF handling the PDU Session, the S-NSSAI of the VPLMN and the S-NSSAI of HPLMN for home routed PDU Session(s).
Input, Optional: This may contain following optional information within the UE context: allocated EBI information, MS Classmark 2, STN-SR, C MSISDN and the Supported Codec IE.
Output, Required: Cause, handle for the UE context created.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.2.22 Namf_Communication_CancelRelocateUEContext service operation | Service operation name: Namf_Communication_CancelRelocateUEContext
Description: This service operation is used by an initial AMF to cancel the relocation of the UE context in a target AMF during EPS to 5GS handover (per N26) with AMF reallocation procedures.
Input, Required: Handle of the UE context.
Input, Optional: None.
Output, Required: Cause.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.3 Namf_EventExposure service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.3.1 General | Service description: This service enables an NF to subscribe and get notified about an Event ID.
Following UE access and mobility information event are considered (Event ID is defined in clause 4.15.1 and Table 4.15.3.1-1):
- Location Report (TAI, Cell ID, N3IWF/TNGF node, UE local IP address and optionally UDP source port number);
- UE moving in or out of a subscribed "Area Of Interest" as described in clauses 5.3.4.4 and 5.6.11 of TS 23.501 [2];
- Number of UEs served by the AMF and located in "Area Of Interest";
- Time zone changes (UE Time zone);
- Access Type changes (3GPP access or non-3GPP access);
- Registration state changes (Registered or Deregistered);
- Connectivity state changes (IDLE or CONNECTED);
- UE loss of communication;
- UE reachability status;
- UE indication of switching off SMS over NAS service;
- Subscription Correlation ID change (implicit subscription);
- UE Type Allocation code (TAC);
- Frequent mobility re-registration;
- Subscription Correlation ID addition (implicit subscription);
- User State Information in 5GS, as described in clause 5.4.4 of TS 23.632 [68];
- UE access behaviour trends (see clause 4.15.4.2);
- UE location trends (see clause 4.15.4.2);
- Assigned Trajectory (see clause 5.13 of TS 23.256 [80]); and
- Total number of Mobility Management transactions:
- The Total number of Mobility Management transactions is used to collect the number of MM transactions of a SUPI or Internal Group ID, for example Dispersion Analytics as specified in TS 23.288 [50]. The Total number of transactions is incremented when the NAS signalling transactions from Authentication, Registration, De-Registration, Service Request and UE Configuration Update procedures is completed. Only the periodic reporting mode applies.
For support signalling storm analytics, total signalling measures is considered:
- Total Signalling Measurements: The event is used to collect the Request type and the number of requests corresponding to the request type from UE/NG-RAN, Request type and number from NF, Public Warning information and Frequent Mobility Registration Update, State transition information, Timer information, etc. The detail of the total signalling measures refers to signalling storm analytics as specified in clause 6.22 of TS 23.288 [50].
In addition to UE access and mobility information event, AMF exposes the "S-NSSAIs per TAI mapping" event providing, per TAI, the related access type and list of supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF). The Event Consumer may use as target of event reporting a list of TAIs, or "any TAI" and may use event filter information including a list of "S-NSSAIs". Whenever there is a change in supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF) for a TAI, the event notification is generated with the updated information.
Event Filters are used to specify the conditions to match for notifying the event (i.e. "List of Parameter values to match"). If there are no conditions to match for a specific Event ID, then the Event Filter is not provided. The following table provides some examples on how the conditions to match for event reporting can be specified for various Event IDs for AMF exposure.
NOTE: The conditions to match can be set based on AMF-associated expected UE Behaviour parameter(s) to only notify the event when the UE's behaviour deviates from its expected UE behaviour as described in TS 23.288 [50].
Table 5.2.2.3.1-1: Example of Event Filters for AMF exposure events
Event ID
Event Filter (List of Parameter Values to Match)
Location Report
<Parameter Type = LocationFilter, Value = TA1>
UE moving in or out of Area of Interest
<Parameter Type = TAI, Value = TA1>
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
<Parameter Type = NSI ID, Value = NSI ID1>
<Parameter Type = PRA ID, Value = PRA ID value>
<Parameter Type = RAN Node ID, Value = RAN Node ID value>
<Parameter Type = Cell ID, Value = Cell ID value>
<Parameter Type = RAN timing synchronization status change event >
(NOTE 1) (NOTE 2)
<Parameter Type = Adjust AoI based on RA, Value = Yes or No> to indicate that AMF may adjust the received AoI depending on UE's current Registration Area. Absence of this parameter in the request is interpreted as "AoI remains unchanged".
<Parameter Type = Notify the consumer considering UE identity, Value = List of SUPIs or Internal Group ID > The parameter may be included when the request is targeted to Any UE. Absence of this parameter in the request is interpreted as "AMF reports an event regardless to UE's identity triggering the event".
(NOTE 2)
<Parameter Type = Notify the consumer considering DNN/S-NSSAI, Value = DNN and/or S-NSSAI> Absence of this parameter in the request is interpreted as "AMF reports the event without checking to which DNN/S-NSSAI the UE has PDU sessions established".
(NOTE 2)
Access Type
<Parameter Type=AN Type, Value=3GPP Access">
Location
<Parameter Type=TAI, Value=wildcard> (to report any TAI change)
Location
<Parameter Type=TAI Value=abnormal> (to report only when the TAI deviates from expected values based on Expected UE Moving Trajectory).
Assigned Trajectory
<Parameter Type = Notify when the UE deviates from the assigned trajectory, Value=TAI, Scheduled Time in a particular TA and/or Height> (to report only when the UE deviates from the assigned values of TAI, Scheduled Time in a particular TA and/or moves outside the altitude range based on the assigned flight plan).
The assigned trajectory may consist of multiple segments identified by geographical areas that, for instance, are served by different UAV Service Suppliers. In this case, the information of each segment shall be provided.
<Parameter Type = Notify when the altitude reporting conditions are met, Value=altitude thresholds, reporting periodicity>
(NOTE 4)
Reachability Filter
Applicable to the event UE reachability. Value = UE reachability status change or UE reachable for DL traffic. Absence of this parameter in UE reachability event request is interpreted as "UE reachability status change".
Total number of Transactions
<Parameter Type = TAI, Value = TA1>
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
Number of UEs present in a geographical area
<Parameter Type = UE Type, Value = Aerial UE>
<Parameter Type = PDU session status, Value = PDU session established for DNN subject to aerial services>
<Parameter Type = LCS broadcasting assistance data type, Value = A bitmap indicates broadcast location assistance data types for which the UE is subscribed to receive ciphering keys to decipher broadcast assistance data (see Table 7.1-3 in clause 7.1 of TS 23.273 [51] and clause 6.1.6.2.72 of TS 29.503 [52])>
(NOTE 3)
NOTE 1: The Parameter Type = RAN timing synchronization status change event can be present with Parameter Type defining a RAN Node ID.
NOTE 2: The use of event filter parameters is described in clause 5.3.4.4 of TS 23.501 [2].
NOTE 3: The mapping relationship between the LCS broadcasting assistance data element and corresponding positioning SIB type is described in clause 7.2 of TS 37.355 [56].
NOTE 4: Filter information for the events is provided as a set of TAI, Scheduled Time and/or Height values for each of the trajectory segments assigned to the UE/UAV, see clause 5.13 of TS 23.256 [80].
NOTE 5: Procedures related to reporting altitude information of aerial UEs are specified in clause 5.16 of TS 23.256 [80].
The following service operations are defined for the Namf_EventExposure service:
- Namf_EventExposure_Subscribe.
- Namf_EventExposure_UnSubscribe.
- Namf_EventExposure_Notify. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.3.2 Namf_EventExposure_Subscribe service operation | Service operation name: Namf_EventExposure_Subscribe.
Description: The consumer NF uses this service operation to subscribe to or modify event reporting for one UE, a group of UE(s) or any UE.
Input, Required: NF ID, Target of Event Reporting: UE(s) ID (SUPI or Internal Group Identifier or indication that any UE is targeted), ((set of) Event ID(s) defined in clause 5.2.2.3.1, Notification Target Address (+ Notification Correlation ID))s, Event Reporting Information defined in Table 4.15.1-1.
Input, Optional: (Event Filter (s) associated with each Event ID; Event Filter (s) are defined in clause 5.2.2.3.1, Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested).
Output, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy).
Output, Optional: First corresponding event report is included, if available (see clause 4.15.1).
The NF consumer subscribes to the event notification by invoking Namf_EventExposure to the AMF. The AMF allocates an Subscription Correlation ID for the subscription and responds to the consumer NF with the Subscription Correlation ID. UE ID identifies the UE, SUPI and/or GPSI. Event ID (see clause 4.15.1) identifies the events that the NF consumer is interested in. The Subscription Correlation ID is unique within the AMF Set.
The ((set of) Event ID(s), Notification Target Address (+ Notification Correlation ID)) helps the Event Receiving NF to co-relate a notification against a corresponding event subscription for the indicated Event ID.
In the case that the NF consumer subscribes to the AMF on behalf of other NF, the NF consumer include the Notification Target Address(+Notification Correlation ID) of other NF for the Event ID which is to be notified to other NF directly and the Notification Target Address(+Notification Correlation ID) of itself for the Subscription Correlation ID change event. Each Notification Target Address(+ Notification Correlation ID) is associated with the related (set of) Event ID(s).When the Subscription Correlation ID change due to the AMF reallocation, the notification is sent to NF consumer which triggers this subscription.
Event filter may include "AN type(s)" as part of the list of parameter values to match and it indicates to subscribe the event per Access Type.
Event receiving NF ID identifies the NF that shall receive the event reporting.
When the consumer NF needs to modify an existing subscription previously created by itself in the AMF, it invokes Namf_EventExposure_Subscribe service operation which contains the Subscription Correlation ID and the new Event Filters with Event ID to the AMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.3.3 Namf_EventExposure_UnSubscribe service operation | Service operation name: Namf_EventExposure_UnSubscribe.
Description: The NF consumer uses this service operation to unsubscribe for a specific event for one UE, group of UE(s), any UE.
Input, Required: Subscription Correlation ID.
Input, Optional: None.
Output, Required: Operation execution result indication.
Output, Optional: None.
The NF consumer unsubscribes the event notification by invoking Namf_EventExposure_Unsubscribe (Subscription Correlation ID) to the AMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.3.4 Namf_EventExposure_Notify service operation | Service operation name: Namf_EventExposure_Notify.
Service operation description: Provides the previously subscribed event information to the NF Consumer which has subscribed to that event before.
Input, Required: AMF ID (GUAMI), Notification Correlation Information, Event ID, corresponding UE(s) (SUPI(s) and if available GPSI(s)), time stamp.
Input, Optional: Event specific parameter list, Idle Status Indication (time when UE returned to Idle, Active Time, Periodic Update Timer, eDRX cycle, suggested number of DL packets).
Output, Required: None.
Output, Optional: None.
When the AMF detects a UE access and mobility event corresponding to a Subscription, it invokes Namf_EventExposure_Notify service operation to the NF consumer(s) which has subscribed to the UE mobility event before. The event is notified towards the consumers for which the Event filters (which may include "AN type(s)") match. The Notification Target Address (+ Notification Correlation ID) indicates to the Event Receiving NF the specific event notification subscription. The event specific parameter indicates the type of mobility event and related information, e.g. Registration Area Update/new Registration Area.
For Subscription Correlation ID changes due to the AMF reallocation, the AMF can send a list of additional subscriptions to UDM in order to trigger an event resynchronization.
The optional event specific parameter list provides the values that matched for generating the event notification. The parameter values to match are specified during the event subscription (see clause 5.2.2.3.2). For example, if the event type reported is "AN change", the event specific parameter list contains the value of the new AN. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4 Namf_MT service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4.1 General | Service description: It provides a NF the service to request information related to capabilities that make sure UE is reachable to send MT signalling or data to a target UE or toward UEs in a multicast session. The following are the key functionalities of this NF service
- paging UE if UE is in IDLE state and respond other NF after the UE enters CM-CONNECTED state.
- response to the requester NF if UE is in CONNECTED state.
- providing the terminating domain selection information for IMS voice to the consumer NF.
- requesting paging towards a group of UEs as defined in TS 23.247 [78]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4.2 Namf_MT_EnableUEReachability service operation | Service operation name: Namf_MT_EnableUEReachability.
Description: The consumer NF uses this service operation to request enabling UE reachability.
Inputs, Required: NF ID, UE ID.
Inputs, Optional: Extended Buffering Support, PPI, ARP, 5QI, QFI, DL data size, PDU Session ID.
Outputs, Required: Result indication.
Outputs, Optional: Redirection information, Estimated Maximum wait time.
See clause 4.13.3.6 and clause 4.24.2 for details on the usage of this service operation.
The consumer NF does not need to know UE state. The AMF accepts the request and respond the consumer NF immediately if UE is in CM-CONNECTED state. If the UE is in CM-IDLE state, the AMF may page the UE and respond to the consumer NF after the UE enters CM-CONNECTED state.
If the result of the service operation fails, the AMF shall set the corresponding cause value in the result indication which can be used by the NF consumer for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the NF consumer to resend UE related message to the AMF that serves the UE. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4.3 Namf_MT_ProvideDomainSelectionInfo | Service operation name: Namf_MT_ProvideDomainSelectionInfo.
Description: Provides the UE information for terminating domain selection of IMS voice to the consumer NF.
Input, Required: SUPI.
Input, Optional: None.
Output, Required: Success/Failure indication.
Output, Optional: Indication of supporting IMS voice over PS Session or not, Time stamp of the last radio contact with the UE, Current RAT type. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4.4 Namf_MT_EnableGroupReachability service operation | Service operation name: Namf_MT_EnableGroupReachability.
Description: NF Service Consumer uses this service operation to request paging towards a group of UEs.
Inputs, Required: Multicast Session ID, UE list.
Inputs, Optional: MBS service area, ARP, 5QI, Associated PDU Session ID list, UE reachability Notification Address.
Outputs, Required: None.
Outputs, Optional: List of UEs in connected state (out of the input list).
This service operation is used in 5G MBS as specified in TS 23.247 [78]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.4.5 Namf_MT_UEReachabilityInfoNotify | Service operation name: Namf_MT_UEReachabilityInfoNotify
Description: Provided the UE reachability information and user location information by the AMF to NF consumers.
Inputs, Required: Notification Correlation ID
Inputs, Optional: list of reachable UE (UE ID, User Location Information), list of unreachable UE (UE ID).
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5 Namf_Location service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5.1 General | Service description: This service enables an NF to request location information for a target UE. The following are the key functionalities of this NF service.
- Allow NFs to request the current or last known geodetic and optionally local and/or civic location of a target UE.
- Allow NFs to be notified of event information related to emergency sessions or deferred UE location.
- Allow NFs to request Network Provided Location Information (NPLI) and/or local time zone corresponding to the location of a target UE.
- Allow NFs to request a deferred geodetic and optionally local and/or civic location of a target UE for Periodic, Triggered and UE Available Location Events.
- Allow NFs to cancel an ongoing session for periodic or triggered location of a target UE. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5.2 Namf_Location_ProvidePositioningInfo service operation | Service operation name: Namf_Location_ProvidePositioningInfo
Description: Provides UE positioning information to the consumer NF.
Input, Required: UE Identification (SUPI or PEI or GPSI), Client Type.
Input, Optional: required Location QoS instance(s), Supported GAD shapes, UE Privacy Requirements, LCS Client Identification, Deferred location type, Deferred location parameters, Notification Target address, Notification Correlation ID, Scheduled Location Time, service type, LMF ID, UE unaware indication, request for user plane reporting to an LCS Client or AF, user plane address of an LCS Client or AF, user plane security information for an LCS Client or AF, cumulative event report timer, maximum number of user plane event reports to an LCS Client or AF, Application layer IDs of the UEs for Ranging/Sidelink positioning.
Output, Required: Success/Failure indication
Output, Optional: Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, Position Methods Used, Failure Cause, achieved Location QoS Accuracy.
See steps 4 and 10 of clause 6.1.1, steps 5, 14, 18 and 22 of clause 6.1.2, steps 5 and 6 of clause 6.3.1 and step 5 of clause 6.20.3 of TS 23.273 [51], for examples of usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5.3 Namf_Location_EventNotify service operation | Service operation name: Namf_Location_EventNotify
Description: Provides UE location related event information related to emergency sessions or deferred location to the consumer NF.
Input, Required: Type of location related event (e.g. emergency session initiation, deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location), UE Identification (SUPI or PEI).
Input, Optional: GPSI, Geodetic Location, Local Location including Coordinate ID, Civic Location, Indoor/Outdoor indication, Position methods used, Notification Target address, Notification Correlation ID, address of a new AMF or MME or MSC server Identity for 5G-SRVCC as specified in TS 23.216 [81], achieved Location QoS Accuracy.
Output, Required: None.
Output, Optional: None.
See steps 5 and 8 of clause 6.10.1 and step 19 of clause 6.3.1 of TS 23.273 [51] and clause 6.5.4 of TS 23.216 [81] for examples of usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5.4 Namf_Location_ProvideLocationInfo service operation | Service operation name: Namf_Location_ProvideLocationInfo
Description: Provides Network Provided Location Information (NPLI) of a target UE to the consumer NF.
Input, Required: UE Identification (SUPI).
Input, Optional: 5GS Location Information Request, Current Location Request, RAT type Requested, Local Time Zone Request.
Output, Required: Success/Failure indication.
Output, Optional: 5GS Location Information (Cell Identity, Tracking Area Identity, Geographical/Geodetic Information, Current Location Retrieved, Age of Location Information, Current RAT Type), Local Time Zone, Failure Cause. In the case of non-3GPP access: a UE local IP address (used to reach the N3IWF/TNGF) and optionally UDP source port number (if NAT is detected). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.2.5.5 Namf_Location_CancelLocation service operation | Service operation name: Namf_Location_CancelLocation
Description: Cancels an ongoing deferred location of a target UE to the consumer NF.
Input, Required: UE Identification (SUPI), Notification Target address, Notification Correlation ID.
Input, Optional: None.
Output, Required: Success/Failure indication.
Output, Optional: None.
See steps 4 and 10 of clause 6.3.3 of TS 23.273 [51] for examples of usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3 UDM Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.1 General | The following table illustrates the UDM Services and Service Operations.
Table 5.2.3.1-1: NF services provided by UDM
NF service
Service Operations
Operation Semantics
Example Consumer(s)
Subscriber Data
Get
Request/Response
AMF, SMF, SMSF, NEF, 5G DDNMF, TSCTSF, NWDAF, LMF
Management
Subscribe
Subscribe/Notify
AMF, SMF, SMSF, NEF, 5G DDNMF, NWDAF, LMF
(SDM)
Unsubscribe
Subscribe/Notify
AMF, SMF, SMSF, NEF, 5G DDNMF, NWDAF, LMF
Notification
Subscribe/Notify
AMF, SMF, SMSF, NEF, GMLC, 5G DDNMF, NWDAF, LMF
ModifySubscription
Subscribe/Notify
AMF, SMF, SMSF, NEF, 5G DDNMF, NWDAF, LMF
Info
Request/Response
AMF, NEF
UE Context
Registration
Request/Response
AMF, SMF, SMSF
Management
DeregistrationNotification
Subscribe/Notify
AMF
(UECM)
Deregistration
Request/Response
AMF, SMF, SMSF
Get
Request/Response
NEF, SMSF, GMLC, NWDAF, SMF, TSCTSF, EIF
Update
Request/Response
AMF, SMF, SMSF
PCscfRestoration
Subscribe/Notify
AMF, SMF
SendRoutingInfoForSM
Request/Response
SMS-GMSC
UE
Get
Request/Response
AUSF
Authentication
ResultConfirmation
Request/Response
AUSF
EventExposure
Subscribe
Subscribe/Notify
NEF (NOTE), NWDAF, SMS-GMSC
Unsubscribe
NEF (NOTE), NWDAF, SMS-GMSC
Notify
NEF (NOTE), NWDAF, SMS-GMSC
ModifySubscription
NEF (NOTE), NWDAF, SMS-GMSC
Parameter
Update
Request/Response
NEF, AMF
Provision
Create
Request/Response
NEF
Delete
Request/Response
NEF
Get
Request/Response
NEF
NIDDAuthorisation
Get
Request/Response
NEF
UpdateNotify
Subscribe/Notify
NEF
ServiceSpecificAuthorisation
Create
Request/Response
NEF
UpdateNotify
Subscribe/Notify
NEF
ReportSMDeliveryStatus
Request
Request/Response
SMS-GMSC
NOTE: Other NFs are allowed to consume the service based on roaming agreement or operator policy. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2 Nudm_UECM (UECM) service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.1 Nudm_UECM_Registration service operation | Service operation name: Nudm_UECM_Registration
Description: Register UE's serving NF (if NF Type is AMF, SMSF, or NWDAF) or Session's serving NF (if NF Type is SMF) on the UDM. This operation implies the following:
- The authorization, if applicable, to register the NF service consumer in UDM for the UE (e.g. based on UE roaming/RAT restrictions applicable when NF type is AMF). If this is successful, the NF service consumer is set as a serving NF for the corresponding UE/Session context.
- When the consumer is AMF or SMF, it is implicitly subscribed to be notified when it is deregistered in UDM. This notification is done by means of Nudm_UECM_DeregistrationNotification operation.
- When the consumer is AMF or SMF, it may optionally use this operation to subscribe to be notified of the need for P-CSCF Restoration. This notification is done by means of Nudm_UECM_PCscfRestoration operation. For more information regarding P-CSCF restoration procedures see TS 23.380 [38].
Inputs, Required: NF ID, SUPI, NF Type, Access Type (if NF Type is AMF, SMSF), RAT Type and GUAMI (if NF Type is AMF), PDU Session ID (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF). If NF Type is SMF: DNN or Indication of Emergency Services, S-NSSAI, SMF+PGW-C FQDN for S5/S8 if the PDU Session supports EPS interworking, Serving Node PLMN ID. If NF type is AMF and Access Type is 3GPP access: Registration type. If NF type is SMSF: SMSF MAP address and/or Diameter address, Serving PLMN ID.
NOTE: The GUAMI includes the MNC+MCC of the serving PLMN. In home routed roaming, the H-SMF provides the PLMN ID of the HPLMN as Serving Node PLMN ID. In LBO roaming, the SMF in the VPLMN provides the PLMN ID of the serving PLMN in the VPLMN as Serving Node PLMN ID.
Inputs, Optional: PEI (conditional, condition stated below), P-CSCF Restoration notification information, NID (e.g. if NF Type is AMF; see clause 5.18 of TS 23.501 [2]), backup AMF(s) (if NF Type is AMF), "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE SRVCC capability (if NF Type is AMF), indication that access is from ePDG (shall be sent if NF Type is SMF and PDU Session is setup via S2b), VGMLC ID (if NF type is AMF and information is available in AMF). Backup AMF(s) sent only once by the AMF to the UDM in its first interaction with the UDM, indication of no event exposure subscription information available (if NF Type is AMF). PCF ID selected for the PDN connection/PDU Session (If NF type is SMF), UE MINT support indicator, Disaster Roaming indicator indicating that Disaster Roaming service is applied.
Outputs, Required: Result indication.
Outputs, Optional: None.
If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm_UECM_Registration in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association.
See step 14a of clause 4.2.2.2.2 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.2 Nudm_UECM_DeregistrationNotification service operation | Service operation name: Nudm_UECM_DeregistrationNotification.
Description: UDM notifies the NF consumer which has previously registered (using Nudm_UECM_Registration operation) has been deregistered in the UDM. As a result, the consumer is no longer registered in UDM as a serving NF for that UE.
NOTE: This notification corresponds to an implicit subscription.
Inputs, Required: SUPI, Access Type, PDU Session ID, serving NF deregistration reason.
Inputs, Optional: NF ID in the case of SM Context Transfer.
Outputs, Required: None.
Outputs, Optional: None.
See step 14d of clauses 4.2.2.2.2 and 4.26.5.3 for an example usage of this service operation. The serving NF deregistration reason tells the reason for sending the deregistration notification to the consumer NF.
The reason for AMF deregistration can be one of the following:
- UE Initial Registration.
- UE Registration area change.
- Subscription Withdrawn.
- 5GS to EPS Mobility.
The reason for SMF deregistration can be one of the following:
- SMF Context Transfer.
- Removal of duplicated PDU Sessions in the old SMF.
- PDU session being released requested to be re-activated.
- Other UDM determined reason as specified in TS 29.503 [52]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.3 Nudm_UECM_Deregistration service operation | Service operation name: Nudm_UECM_Deregistration.
Description: The NF consumer requests the UDM to delete the information related to the NF in the UE context. When the consumer is AMF, this implies that the subscriptions to be notified when the NF is deregistered in UDM (i.e. Nudm_UECM_DeregistrationNotification) are also removed.
Inputs, Required: SUPI, NF type, Access Type, PDU Session ID (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF).
- Access Type is included only when the NF type indicates AMF or SMSF.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.4 Nudm_UECM_Get service operation | Service operation name: Nudm_UECM_Get.
Description: The NF consumer requests the UDM to get the NF ID or SMS address of the NF serving the UE.
Inputs, Required: UE ID, NF Type.
Inputs, Optional: Access Type, Analytics ID(s) (if NF Type is NWDAF), indication to retrieve PDU Session ID information.
- Access Type is included when the NF type indicates SMSF.
Outputs, Required: NF ID or SMS address of the NF corresponding to the NF type requested by NF consumer. If the NF Type requested by NF consumer is AMF, the Access Type corresponding to the AMF is also included. Analytics ID(s), if NF Type is NWDAF.
Outputs, Optional: SUPI or GPSI or both, PDU Session ID(s) already registered in the UDM for the UE.
For more information on retrieving PDU Session information, refer to clause 4.11.0a.5. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.5 Nudm_UECM_Update service operation | Service operation name: Nudm_UECM_Update.
Description: Consumer updates some UE related information (e.g. UE capabilities, Intersystem continuity context, SMF+PGW-C FQDN for S5/S8 interface, Analytics ID(s) in the case of NWDAF).
Inputs, Required: NF ID, SUPI, NF type, UE context information.
Inputs, Optional: "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE MINT support indicator (if NF Type is AMF), SMF+PGW-C FQDN for S5/S8 interface (if NF Type is SMF), UE memory available for SMS indication (if NF Type is SMSF).
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.6 Nudm_UECM_PCscfRestoration service operation | Service operation name: Nudm_UECM_PCscfRestoration.
Description: UDM notifies the AMF and/or SMF(s) which indicated during registration in UDM to be notified of the need for P-CSCF Restoration.
Inputs, Required: SUPI.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.2.7 Nudm_UECM_SendRoutingInfoForSM service operation | Service operation name: Nudm_UECM_SendRoutingInfoForSM.
Description: This service operation is used to get SMS Routing Info for MT SMS.
Inputs, Required: GPSI.
Inputs, Optional: None.
Outputs, Required: Result indication, SMS Routing Info.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3 Nudm_SubscriberDataManagement (SDM) Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.1 General | Subscription data types used in the Nudm_SubscriberDataManagement Service are defined in Table 5.2.3.3.1-1 below.
Table 5.2.3.3.1-1: UE Subscription data types
Subscription data type
Field
Description
Access and Mobility Subscription data (data needed for UE
GPSI List
List of the GPSI (Generic Public Subscription Identifier) used both inside and outside of the 3GPP system to address a 3GPP subscription (see NOTE 9).
Registration and Mobility Management)
Internal Group ID-list
List of the subscribed internal group(s) that the UE belongs to.
Subscribed UE-AMBR
The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR QoS Flows according to the subscription of the user.
Subscribed UE-Slice-MBR(s)
List of maximum aggregated uplink and downlink MBRs to be shared across all GBR and Non-GBR QoS Flows related to the same S-NSSAI according to the subscription of the user. There is a single uplink and a single downlink value per S-NSSAI.
Subscribed S-NSSAIs
The Network Slices that the UE subscribes to. In the roaming case, it indicates the subscribed Network Slices applicable to the Serving PLMN (NOTE 11, NOTE 24).
For a subscribed S-NSSAI subject to NSAC for the registered number of UE, the applicable NSAC admission mode is included as described in clause 4.2.11.5.2.
Default S-NSSAIs
The Subscribed S-NSSAIs marked as default S-NSSAI. In the roaming case, only those applicable to the Serving PLMN (NOTE 12).
Slice Usage Policy information
Includes:
- indication the S-NSSAI is on demand; and
- slice deregistration inactivity timer value.
The AMF uses this information as described in clause 5.15.15 of TS 23.501 [2].
(NOTE 22)
S-NSSAIs subject to Network Slice-Specific Authentication and Authorization
The Subscribed S-NSSAIs marked as subject to NSSAA. When present, the GPSI list shall include at least one GPSI.
Network Slice Simultaneous Registration Group Information
Optionally, for each S-NSSAI in the Subscribed S-NSSAIs, one or more value of Network Slice Simultaneous Registration Group(s) (NOTE 11) associated with the S-NSSAI.
Network Slice validity time information
Optionally, if the Subscribed S-NSSAI is temporarily available network slice, one validity time is associated with this S-NSSAI.
UE Usage Type
As defined in clause 5.15.7.2 of TS 23.501 [2].
RAT restriction
3GPP and non-3GPP Radio Access Technology(ies) not allowed the UE to access.
Forbidden area
Defines areas in which the UE is not permitted to initiate any communication with the network.
Service Area Restriction
Indicates Allowed Areas in which the UE is permitted to initiate communication with the network and Non-allowed areas in which the UE and the network are not allowed to initiate Service Request or SM signalling to obtain user services.
Core Network type restriction
Defines whether UE is allowed to connect to 5GC and/or EPC for this PLMN.
CAG information
The CAG information includes Allowed CAG list and optionally an indication whether the UE is only allowed to access 5GS via CAG cells and each entry in the Allowed CAG list may also be associated with time validity information as defined in clause 5.30.3 of TS 23.501 [2].
CAG information Subscription Change Indication
When present, indicates to the serving AMF that the CAG information in the subscription data changed and the UE must be updated.
RFSP Index
An index to specific RRM configuration in the NG-RAN.
Subscribed Periodic Registration Timer
Indicates a subscribed Periodic Registration Timer value, which may be influenced by e.g. network configuration parameter as specified in clause 4.15.6.3a.
Subscribed Active Time
Indicates a subscribed active time value, which may be influenced by e.g. network configuration parameter as specified in clause 4.15.6.3a.
MPS priority
Indicates the user is subscribed to MPS as indicated in clause 5.16.5 of TS 23.501 [2].
MPS for Messaging indication
Indicates whether the user has MPS for Messaging set (enabled)/cleared (disabled) as described in clause 5.16.5 of TS 23.501 [2]. This parameter is valid only when the MPS priority parameter is set and UE is allowed to use the SMS service.
MCX priority
Indicates the user is subscribed to MCX as indicated in clause 5.16.6 of TS 23.501 [2].
AMF-Associated Expected UE Behaviour parameters
Information on expected UE movement and communication characteristics. See clause 4.15.6.3
Steering of Roaming
List of preferred PLMN/access technology combinations and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services (see NOTE 21) or HPLMN/Credentials Holder indication that no change of the above list(s) stored in the UE is needed (see NOTE 3).
Optionally includes an indication that the UDM requests an acknowledgement of the reception of this information from the UE.
SoR Update Indicator for Initial Registration
An indication whether the UDM requests the AMF to retrieve SoR information when the UE performs Registration with NAS Registration Type "Initial Registration".
SoR Update Indicator for Emergency Registration
An indication whether the UDM requests the AMF to retrieve SoR information when the UE performs Registration with NAS Registration Type "Emergency Registration".
Network Slicing Subscription Change Indicator
When present, indicates to the serving AMF that the subscription data for network slicing changed and the UE configuration must be updated.
Provide the UE with the full set of subscribed S-NSSAIs
Indicates the AMF to provide the UE with the full set of subscribed S-NSSAIs even if they do not share a common NSSRG.
Tracing Requirements
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421 [39].
Inclusion of NSSAI in RRC Connection Establishment Allowed
When present, it is used to indicate that the UE is allowed to include NSSAI in the RRC connection Establishment in clear text for 3GPP access.
Service Gap Time
Used to set the Service Gap timer for Service Gap Control (see clause 5.31.16 of TS 23.501 [2]).
Subscribed DNN list
List of the subscribed DNNs for the UE (NOTE 1). Used to determine the list of LADN available to the UE as defined in clause 5.6.5 of TS 23.501 [2].
LADN Service Area
List of Tracking Areas configured per DNN and S-NSSAI within which UE is permitted to initiate Service Request or SM signalling.
UDM Update Data
Includes a set of parameters see clause 4.20.1 for parameters possible to deliver) to be delivered from UDM to the UE via NAS signalling as defined in clause 4.20 (NOTE 3).
Optionally includes an indication that the UDM requests an acknowledgement of the reception of this information from the UE and an indication for the UE to re-register.
NB-IoT UE priority
Numerical value used by the NG-RAN to prioritise between UEs accessing via NB-IoT.
Enhanced Coverage Restriction
Specifies whether CE mode B is restricted for the UE, or both CE mode A and CE mode B are restricted for the UE, or both CE mode A and CE mode B are not restricted for the UE.
NB-IoT Enhanced Coverage Restriction
Indicates whether Enhanced Coverage for NB-IoT UEs is restricted or not.
IAB-Operation allowed
Indicates that the subscriber is allowed for IAB-operation as specified in clause 5.35.2 of TS 23.501 [2].
MBSR Operation allowed
Indicates the subscriber is allowed for MBSR operation as specified in clause 5.35A.4 of TS 23.501 [2]. If present, additional location information (i.e. a list of TAIs or Area Codes that can be interpreted by AMF into TAIs ) and/or time information (including one or more time windows, and/or one or more recurring time periods) may also be present to restrict the MBSR operation to be within the location and time provided.
Charging Characteristics
It contains the Charging Characteristics as defined in Annex A of TS 32.256 [71].
This information, when provided, shall override any corresponding predefined information at the AMF.
Extended idle mode DRX cycle length
Indicates a subscribed extended idle mode DRX cycle length value.
PCF Selection Assistance info
list of combination of DNN and S-NSSAI that indicates that the same PCF needs to be selected for AM Policy Control and SM Policy Control (NOTE 10).
AerialUESubscriptionInfo
Aerial UE Subscription Information. It contains an Indication on whether Aerial service for the UE is allowed or not.
5G Access Stratum-based Time Synchronization Service Data
Includes the Access Stratum Time Synchronization Service Authorization to indicate whether the UE should be provisioned with 5G system internal clock timing information over access stratum.
Optionally includes an Uu time synchronization error budget.
Optionally includes one or more periods of start and stop times defining the times when the UE should be provisioned with 5G system internal clock timing information.
Optionally includes a Time Synchronization Coverage Area comprising a list of TAs where the UE shall be provisioned with 5G system internal clock timing information (NOTE 19).
Optionally includes a clock quality detail level to indicate whether and which clock quality information to provide to the UE. It comprises one of the following values: clock quality metrics or acceptable/not acceptable indication.
Optionally includes the clock quality acceptance criteria for the UE. It may be defined based on one or more of the following attributes: time source, traceability to UTC and to GNSS, synchronization state, clock accuracy, frequency stability.
Routing Indicator
Routing Indicator assigned to the SUPI.
ODB for Packet services
Operator Determined Barring for Packet Oriented Services. See TS 23.015 [90] and TS 29.503 [52] for the handling of ODB for Packet service parameter.
QMC Configuration information
The content of QMC Configuration information (e.g. QoE reference, QoE collection entity address, etc.) is defined in TS 28.405 [92].
NCR-Operation allowed
Indicates that the subscriber is allowed for NCR-operation as specified in clause 5.47 of TS 23.501 [2].
AM Policy Association indicator
Indicates whether the AM Policy Association is "enabled", "disabled".
UE Policy Association indicator
Indicates whether the UE Policy Association is "enabled" or "disabled".
Energy Saving Indicator
The Energy Saving indicator defined in clause 5.51.5 of TS 23.501 [2].
Slice Selection Subscription data (data needed for
Subscribed S-NSSAIs
The Network Slices that the UE subscribes to. In roaming case, it indicates the subscribed network slices applicable to the serving PLMN (NOTE 11, NOTE 24).
Slice Selection as described in clause 4.2.2.2.3 and
Default S-NSSAIs
The Subscribed S-NSSAIs marked as default S-NSSAI. In the roaming case, only those applicable to the Serving PLMN (NOTE 12).
in clause 4.11.0a.5)
S-NSSAIs subject to Network Slice-Specific Authentication and Authorization
The Subscribed S-NSSAIs marked as subject to NSSAA.
Network Slice Simultaneous Registration Group (NSSRG) Information
Optionally, for each S-NSSAI in the Subscribed S-NSSAIs, the one or more value of Network Slice Simultaneous Registration Group(s) (NOTE 11) associated with the S-NSSAI.
Network Slice validity time information
Optionally, if the Subscribed S-NSSAI is temporarily available network slice, one validity time is associated with this S-NSSAI.
SMF Selection
SUPI
Key
Subscription data (data needed for SMF
SMF Selection Subscription data contains one or more S-NSSAI level subscription data:
Selection as described
S-NSSAI
Indicates the value of the S-NSSAI.
in clause 6.3.2 of
Subscribed DNN list
List of the subscribed DNNs for the UE (NOTE 1, NOTE 24).
TS 23.501 [2])
Default DNN
The default DNN if the UE does not provide a DNN (NOTE 2).
DNN(s) subject to aerial services
List of DNNs that are used for aerial services (e.g. UAS operations or C2, etc.) as described in TS 23.256 [80]. (see NOTE 13).
LBO Roaming Information
Indicates whether LBO roaming is allowed per DNN, or per (S-NSSAI, subscribed DNN). (NOTE 16)
HR-SBO allowed indication
Indicates whether Session Breakout for HR Session in VPLMN is allowed per DNN, or per (S-NSSAI, subscribed DNN).
(NOTE 17)
Interworking with EPS indication list
Indicates whether EPS interworking is supported per (S-NSSAI, subscribed DNN).
Same SMF for Multiple PDU Sessions to the same DNN and S-NSSAI
Indication whether the same SMF for multiple PDU Sessions to the same DNN and S-NSSAI is required.
Invoke NEF indication
When present, indicates, per S-NSSAI and per DNN, that NEF based infrequent small data transfer shall be used for the PDU Session (see NOTE 8).
SMF information for static IP address/prefix
When static IP address/prefix is used, this may be used to indicate the associated SMF information per (S-NSSAI, DNN).
Additional parameters for SMF selection in target PLMN
Indicates the target PLMN identifier where SMF resource resides.
Local Offloading Management allowed indication
Indicates whether Local Offloading Management is allowed per DNN, or per (S-NSSAI, DNN).
UE context in SMF
SUPI
Key.
data
PDU Session ID(s)
List of PDU Session ID(s) for the UE.
For emergency PDU Session ID:
Emergency Information
The SMF+PGW-C FQDN for emergency session used for interworking with EPC.
For each non-emergency PDU Session ID:
DNN
DNN for the PDU Session.
SMF
Allocated SMF for the PDU Session. Includes SMF IP Address and SMF NF Id.
SMF+PGW-C FQDN
The S5/S8 SMF+PGW-C FQDN used for interworking with EPS (see NOTE 5).
PCF ID
The PCF ID serving the PDU Session/PDN Connection.
SMS Management Subscription data (data needed by
SMS parameters
Indicates SMS parameters subscribed for SMS service such as SMS teleservice, SMS barring list
SMSF for SMSF Registration)
Trace Requirements
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421 [39].
This information is only sent to a SMSF in HPLMN.
Charging Characteristics
It contains Charging Characteristics as defined in TS 32.274 [45]. This information, when provided, shall override any corresponding predefined information at the SMSF.
SMS Subscription data
SMS Subscription
Indicates subscription to any SMS delivery service over NAS irrespective of access type.
(data needed in AMF)
UE Context in SMSF data
SMSF Information
Indicates SMSF allocated for the UE, including SMSF address and SMSF NF ID.
Access Type
3GPP or non-3GPP access through this SMSF
Session Management Subscription data (data needed for PDU
GPSI List
List of the GPSI (Generic Public Subscription Identifier) used both inside and outside of the 3GPP system to address a 3GPP subscription.
Session Establishment)
Internal Group ID-list
List of the subscribed internal group(s) that the UE belongs to.
Trace Requirements
Trace requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc…) is defined in TS 32.421 [39].
This information is only sent to a SMF in the HPLMN or one of its equivalent PLMN(s).
Session Management Subscription data contains one or more S-NSSAI level subscription data:
S-NSSAI
Indicates the value of the S-NSSAI.
For a subscribed S-NSSAI subject to NSAC for the established PDU session number, the applicable NSAC admission mode is included as described in clause 4.2.11.5.2.
Subscribed DNN list
List of the subscribed DNNs for the S-NSSAI (NOTE 1, NOTE 24).
Slice Usage Policy information
Includes:
- PDU Session inactivity timer value.
The SMF uses this information as described in clause 5.15.15 of TS 23.501 [2].
(NOTE 22).
ODB for Packet services
Operator Determined Barring for Packet Oriented Services. See TS 23.015 [90] and TS 29.503 [52] for the handling of ODB for Packet service parameter.
For each DNN in S-NSSAI level subscription data:
DNN
DNN for the PDU Session.
Aerial service indication
Indicates whether the DNN is used for aerial services (e.g. UAS operations or C2, etc.) as described in TS 23.256 [80].
Framed Route information
Set of Framed Routes. A Framed Route refers to a range of IPv4 addresses / IPv6 Prefixes to associate with a PDU Session established on this (DNN, S-NSSAI).
See NOTE 4.
IP Index information
Information used for selecting how the UE IP address is to be allocated (see clause 5.8.2.2.1 of TS 23.501 [2]).
Allowed PDU Session Types
Indicates the allowed PDU Session Types (IPv4, IPv6, IPv4v6, Ethernet and Unstructured) for the DNN, S-NSSAI. See NOTE 6.
Default PDU Session Type
Indicates the default PDU Session Type for the DNN, S-NSSAI.
Allowed SSC modes
Indicates the allowed SSC modes for the DNN, S-NSSAI.
Default SSC mode
Indicate the default SSC mode for the DNN, S-NSSAI.
Interworking with EPS indication
Indicates whether interworking with EPS is supported for this DNN and S-NSSAI.
5GS Subscribed QoS profile
The QoS Flow level QoS parameter values (5QI and ARP) for the DNN, S-NSSAI (see clause 5.7.2.7 of TS 23.501 [2]).
Charging Characteristics
It contains Charging Characteristics as defined in Annex A clause A.1 of TS 32.255 [45]. This information, when provided, shall override any corresponding predefined information at the SMF.
Subscribed-Session-AMBR
The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR QoS Flows in each PDU Session, which are established for the DNN, S-NSSAI.
Static IP address/prefix
Indicate the static IP address/prefix for the DNN, S-NSSAI.
Allowed VLAN tags
A list of allowed VLAN tags for the PDU Session; this shall apply only for PDU Sessions of Ethernet PDU Session type and is further described in clause 5.6.10.2 of TS 23.501 [2].
VLAN handling information
Instructions for VLAN tag handling in UPF, e.g. the C-VLAN tag to be inserted or removed, S-TAG to be inserted or removed for Ethernet PDU Session type (see clause 5.6.10.2 of TS 23.501 [2]).
User Plane Security Policy
Indicates the security policy for integrity protection and encryption for the user plane.
PDU Session continuity at inter RAT mobility
Provides for this DDN, S-NSSAI how to handle a PDU Session when UE the moves to or from NB-IoT. Possible values are: maintain the PDU session; disconnect the PDU session with a reactivation request; disconnect PDU session without reactivation request; or to leave it to local VPLMN policy.
NEF Identity for NIDD
When present, indicates, per S-NSSAI and per DNN, the identity of the NEF to anchor Unstructured PDU Session. When not present for the S-NSSAI and DNN, the PDU session terminates in UPF (see NOTE 8).
NIDD information
Information such as External Group Identifier, External Identifier, MSISDN, or AF Identifier used for SMF-NEF Connection.
SMF-Associated Expected UE Behaviour parameters
Parameters on expected characteristics of a PDU Session their corresponding validity times as specified in clause 4.15.6.3.
SMF-Associated Application-Specific Expected UE Behaviours parameters
Parameters characterise the foreseen behaviour of a UE for a specific application as specified in clause 4.15.6.3f.
Suggested number of downlink packets
Parameters on expected PDU session characteristics as specified in clauses 4.15.3.2.3b and 4.15.6.3a.
ATSSS information
Indicates whether MA PDU session establishment is allowed.
Secondary authentication indication
Indicates that whether the Secondary authentication/authorization (as defined in clause 5.6 of TS 23.501 [2]) is required for PDU Session Establishment or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2. (see NOTE 14)
DN-AAA Server UE IP address allocation indication
Indicates that whether the SMF is required to request the UE IP address from the DN-AAA Server (as defined in clause 5.6 of TS 23.501 [2]) for PDU Session Establishment or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2.
DN-AAA Server addressing information
If at least one of secondary DN-AAA authentication, DN-AAA authorization or DN-AAA UE IP address allocation is required by subscription data, the subscription data may also contain DN-AAA Server addressing information.
Edge Configuration Server Address Configuration Information
Consists of one or more ECS Configuration Information as defined in clause 8.3.2.1 of TS 23.558 [83]. The ECS Configuration Information sent by UDM to SMF is associated with the PLMN ID where the UE is roaming on. (see NOTE 20)
API based secondary authentication indication
Indicates that whether the API based Secondary authentication/authorization (as defined in clause 5.2.3 of TS 23.256 [80]) is required for PDU Session Establishment or PDN Connection Establishment as specified in clause 4.3.2.3 and clause H.2 (see NOTE 14).
UE authorization for EAS discovery via EASDF
Indicates whether the UE is authorized to use 5GC assisted EAS discovery via EASDF (as defined in TS 23.548 [74]).
HR-SBO authorization indication
Indicates whether the VPLMN is authorized for Home Routed Session Breakout (HR-SBO) (see NOTE 17 and NOTE 18).
Local Offloading Management allowed indication
Indicates whether the Local Offloading Management is allowed.
Required UPF functionalities
Indicates the required UPF functionalities for the PDU Session (NOTE 23).
Preferred UPF functionalities
Indicates the preferred UPF functionalities for the PDU Session and optionally for each preferred UPF functionality its priority (NOTE 23).
Identifier translation
SUPI
Corresponding SUPI for input GPSI.
(Optional) MSISDN
Corresponding GPSI (MSISDN) for input GPSI (External Identifier). This is optionally provided for legacy SMS infrastructure not supporting MSISDN-less SMS. The presence of an MSISDN should be interpreted as an indication to the NEF that MSISDN shall be used to identify the UE when sending the SMS to the SMS-SC via T4.
GPSI
Corresponding GPSI for input SUPI and associated application information (e.g. Application Port ID) (NOTE 15).
Intersystem continuity Context
(DNN, PGW FQDN) list
For each DNN, indicates the SMF+PGW-C which support interworking with EPC.
LCS privacy
(data needed by GMLC)
LCS privacy profile data
Provides information for LCS privacy classes and Location Privacy Indication (LPI) as defined in clause 5.4.2 of TS 23.273 [51]
Ranging/Sidelink Positioning privacy (data needed by GMLC)
UE Ranging/SL Positioning privacy profile data
Provides information for Ranging/Sidelink Positioning privacy classes and Ranging/SL Positioning Privacy Indication (RSPI) as defined in Annex B of TS 33.533 [94].
LCS mobile origination
(data needed by AMF)
LCS Mobile Originated Data
When present, indicates to the serving AMF which LCS mobile originated services are subscribed as defined in clause 7.1 of TS 23.273 [51].
User consent (see TS 23.288 [50])
User consent for UE data collection
Indicates whether the user has given consent for collecting, distributing and analysing UE related data. User consent is provided per purpose (e.g. analytics, model training).
UE reachability
UE reachability information
Provides, per PLMN, the list of NF IDs or the list of NF sets or the list of NF types authorized to request notification for UE's reachability (NOTE 7).
V2X Subscription data (see TS 23.287 [73])
NR V2X Services Authorization
Indicates whether the UE is authorized to use the NR sidelink for V2X services as Vehicle UE, Pedestrian UE, or both.
LTE V2X Services Authorization
Indicates whether the UE is authorized to use the LTE sidelink for V2X services as Vehicle UE, Pedestrian UE, or both.
NR UE-PC5-AMBR
AMBR of UE's NR sidelink (i.e. PC5) communication for V2X services.
LTE UE-PC5-AMBR
AMBR of UE's LTE sidelink (i.e. PC5) communication for V2X services.
A2X Subscription data (see TS 23.256 [80])
NR A2X Services Authorization
Indicates whether the UE is authorized to use the NR sidelink for A2X services.
LTE A2X Services Authorization
Indicates whether the UE is authorized to use the LTE sidelink for A2X services.
NR UE-PC5-AMBR for A2X
AMBR of UE's NR sidelink (i.e. PC5) communication for A2X services.
LTE UE-PC5-AMBR for A2X
AMBR of UE's LTE sidelink (i.e. PC5) communication for A2X services.
ProSe Subscription data (see TS 23.304 [77])
ProSe Service Authorization
Indications for whether the UE is authorised to use the 5G ProSe service(s), including:
- use 5G ProSe Direct Discovery;
- use 5G ProSe Direct Communication;
- use 5G ProSe Layer-3 Multi-hop UE-to-Network Discovery;
- use 5G ProSe Layer-3 Multi-hop UE-to-Network Communication;
- use 5G ProSe Layer-3 Multi-hop UE-to-UE Discovery;
- use 5G ProSe Layer-3 Multi-hop UE-to-UE Communication;
- act as a 5G ProSe Remote UE;
- serve as a 5G ProSe UE-to-Network Relay;
- serve as a 5G ProSe Layer-3 Intermediate UE-to-Network Relay;
- use multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE;
- act as a 5G ProSe End UE; and
- serve as a 5G ProSe UE-to-UE Relay.
ProSe NR UE-PC5-AMBR
AMBR of UE's NR sidelink (i.e. PC5) communication for ProSe services.
MBS Subscription data (see TS 23.247 [78])
MBS Service Authorization
Indicates whether the UE is authorized to use Multicast MBS service. May also indicate the multicast MBS Session which the UE is allowed to join if the UE is authorized to use multicast MBS Service.
MBS Assistance Information
Include MBS assistance information for a UE that joins a multicast group.
Time Synchronization Subscription data (see clause 5.27.1.11 of TS 23.501 [2])
AF Request Authorization Information
Includes the AF Request Authorization to indicate whether the UE is authorized for an AF-requested 5G access stratum-based time distribution and (g)PTP-based time distribution services (per DNN/S-NSSAI). The indication is provided separately for each service.
Optionally includes a list of TA(s) which specifies the Authorized Time Synchronization Coverage Area in which an AF may request time synchronization services (NOTE 19).
Optionally, one or more periods of authorized start and stop times, which indicates the allowed time period during which an AF may request time synchronization services.
Optionally, authorized Uu time synchronization error budget, which indicates the limit the AF may request.
Optionally includes information to determine whether the AF may request
- to provide clock quality metric information to the UE;
- to provide an acceptable/not acceptable indication to the UE.
Optionally includes one or more sets of the clock quality acceptance criteria for the UE that the AF may request. Clock quality acceptance criteria may be defined using TSS attributes from Table 5.27.1.12-1 of TS 23.501 [2].
Subscribed Time Synchronization Service ID(s)
Each containing the DNN/S-NSSAI and a reference to a PTP instance configuration pre-configured at the TSCTSF.
Optionally, for each PTP instance configuration, one or more periods of start and stop times defining active times of time synchronization service for the PTP instance.
Optionally, for each PTP instance configuration, a Time Synchronization Coverage Area defining a list of TAs where the (g)PTP-based time synchronization is available for the UEs in the PTP instance (NOTE 19).
Optionally, for each PTP instance configuration, Uu time synchronization error budget.
Ranging/Sidelink Positioning Subscription data (see TS 23.586 [88])
Ranging/SL Positioning Service Authorization
Indicates whether the UE is authorized to use Ranging/SL Positioning Service.
NOTE 1: The Subscribed DNN list can include a wildcard DNN.
NOTE 2: The default DNN shall not be a wildcard DNN.
NOTE 3: The Steering of Roaming information and UDM Update Data are protected using the mechanisms defined in TS 33.501 [15].
NOTE 4: Framed Route information and Framed Route(s) are defined in TS 23.501 [2].
NOTE 5: Depending on the scenario PGW-C FQDN may be for S5/S8, or for S2b (ePDG case).
NOTE 6: The Allowed PDU Session Types configured for a DNN which supports interworking with EPC should contain only the PDU Session Type corresponding to the PDN Type configured in the APN that corresponds to the DNN.
NOTE 7: Providing a list of NF types or a list of NF sets may be more appropriate for some deployments, e.g. in highly dynamic NF lifecycle management deployments.
NOTE 8: For a S-NSSAI and a DNN, the "Invoke NEF Indication" shall be present in the SMF selection subscription data if and only if the "NEF Identity for NIDD" Session Management Subscription Data includes a NEF Identity. When the "NEF Identity for NIDD" Session Management Subscription Data includes a NEF Identity for a S-NSSAI and DNN, the "Control Plane Only Indicator" will always be set for PDU Sessions to this S-NSSAI and DNN (see clause 5.31.4.1 of TS 23.501 [2]).
NOTE 9: When multiple GPSIs are included in the GPSI list, any GPSI in the list can be used in NSSAA procedures.
NOTE 10: The same PCF can be selected to serve the UE and to serve one or multiple PDU sessions, each of them is indicated in the list of S-NSSAI, DNN combinations in the PCF Selection Assistance Info. Providing one combination of DNN and S-NSSAI in the PCF Selection Assistance Info is assumed if interworking with EPS is needed. In case multiple PDU sessions to one DNN, S-NSSAI are established in EPS, it is appropriate to select same PCF by configuration or by using existing method, e.g. same PCF selection in usage monitoring.
NOTE 11: If Network Slice Simultaneous Registration Group information is present and the VPLMN does not support the subscription-based restrictions to simultaneous registration of network slices, the subset of the Subscribed S-NSSAIs defined in clause 5.15.12 of TS 23.501 [2], are included, without providing the NSSRG information.
NOTE 12: The Default S-NSSAIs (if more than one is present) are associated with common NSSRG values if NSSRG information is present. At least one Default S-NSSAI shall be present in a subscription including NSSRG information.
NOTE 13: When UUAA is performed in the AMF (as in clause 5.2.2 of TS 23.256 [80]) and UUAA-MM status is FAILED or PENDING, the AMF shall reject PDU session establishment requests from the UE for a DNN that is subject to aerial services.
NOTE 14: For a DNN in S-NSSAI either a DN-AAA based secondary authentication, or an API based secondary authentication can be configured. When API based authentication of the PDU session is required, Secondary authentication indication shall not be present.
NOTE 15: A GPSI may be associated with Application Port ID, MTC Provider Information and/or AF Identifier.
NOTE 16: For non-roaming UE (e.g. accessing SNPN with CH credentials), LBO roaming information does not apply.
NOTE 17: This information applies only for HR PDU Session.
NOTE 18: This information is only valid for the current serving network. When Session Breakout for HR Session is authorized, usage of corresponding EAS Deployment Information and AF traffic influence in VPLMN is also authorized.
NOTE 19: The subscribed Time Synchronization Coverage Area shall be inside of the Allowed Areas as per UE's service area restriction.
NOTE 20: For roaming UE in a visited PLMN, the corresponding PLMN ID is provided with Edge Configuration Server (ECS) Address Configuration Information.
NOTE 21: The entries in the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services are associated with a time validity information and optionally a location validity information indicating the conditions allowing the UE to access to localized services in the SNPN or/and location assistance information used to aid the UE where to search for the SNPN as specified in clause 5.30.2.3 of TS 23.501 [2].
NOTE 22: Only for an S-NSSAI dedicated to a single AF is associated with Slice Usage Policy information. For roaming UE, refer to clause 5.15.15.1 of TS 23.501 [2] for the Slice Usage Policy.
NOTE 23: Packet inspection and operator configurable UPF capabilities as specified in clause 5.8.2.21 of TS 23.501 [2] can be indicated as required and/or preferred UPF functionalities for the PDU Session.
NOTE 24: Based on operator configuration, certain S-NSSAIs and DNNs can be dedicated to support the wireless backhaul links established by PDU sessions of the MWAB-UE as specified in clause 5.49 of TS 23.501 [2].
Table 5.2.3.3.1-2: Group Subscription data types
Subscription data type
Field
Description
Group Identifier translation
External Group Identifier
Identifies external group of UEs that the UE belongs to as defined in TS 23.682 [23].
Internal Group Identifier
Identifies internal group of UEs that the UE belongs to as defined in TS 23.501 [2].
SUPI list
Corresponding SUPI list for input External Group Identifier.
Group Data
(NOTE 1)
Internal Group Identifier
Internal identifiers of the group of UEs that the Group Data belongs to.
Group data
In the case of 5G VN related groups the content of this information contains parameters defined in clause 4.15.6.3b.
In the case of DNN and S-NSSAI specific parameters in the Groups, the content of this information contains parameters defined in clause 4.15.6.3e.
NOTE 1: Group Data within Group Subscription Data can be managed using the Shared Data feature defined in TS 29.503 [52]. In that case, Shared Data is identified using Shared Data identifier and can contain additional information than the one defined in this table.
At least a mandatory key is required for each Subscription Data Type to identify the corresponding data. Depending on the use case, for some Subscription Data Types it is possible to use one or multiple sub keys to further identify the corresponding data, as defined in Tables 5.2.3.3.1-3 and 5.2.3.3.1-4 below.
Table 5.2.3.3.1-3: UE Subscription data types keys
Subscription Data Types
Data Key
Data Sub Key
Access and Mobility Subscription data
SUPI
Serving PLMN ID and optionally NID
SMF Selection Subscription data
SUPI
Serving PLMN ID and optionally NID
UE context in SMF data
SUPI
S-NSSAI
SMS Management Subscription data
SUPI
Serving PLMN ID and optionally NID
SMS Subscription data
SUPI
Serving PLMN ID and optionally NID
UE Context in SMSF data
SUPI
-
Session Management Subscription data
SUPI
S-NSSAI
DNN
Serving PLMN ID and optionally NID
Identifier translation
GPSI
-
SUPI
Application Port ID, MTC Provider Information, AF Identifier
Slice Selection Subscription data
SUPI
Serving PLMN ID and optionally NID
Intersystem continuity Context
SUPI
DNN
LCS privacy
SUPI
-
Ranging/Sidelink Positioning privacy
SUPI
-
LCS mobile origination
SUPI
-
User consent
SUPI
Purpose
UE reachability
SUPI
-
V2X Subscription data
SUPI
-
ProSe Subscription data
SUPI
-
MBS Subscription data
SUPI
-
A2X Subscription data
SUPI
-
Ranging/Sidelink Positioning Subscription data
SUPI
-
Table 5.2.3.3.1-4: Group Subscription data types keys
Subscription Data Types
Data Key
Data Sub Key
Group Identifier translation
External Group Identifier
-
Internal Group Identifier
-
Group Data
Internal Group Identifier
-
Wireline access specific subscription data parameters are specified in TS 23.316 [53]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.2 Nudm_SDM_Get service operation | Service Operation name: Nudm_SDM_Get
Description: Consumer NF gets the subscription data indicated by the subscription data type input from UDM. The UDM shall check the requested consumer is authorized to get the specific subscription data requested. In the case of NF consumer is SMF, the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP, Subscribed S-NSSAI(s).
Inputs, Required: NF ID, Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: Data Sub Key(s), SoR Update Indicator, AF Identifier (for AF authorisation by the UDM), Disaster Roaming Indicator indicating that Disaster Roaming service is applied, Serving PLMN ID.
NOTE: Some subscription data subsets can be specific to the Serving PLMN where the UE is registered (e.g. access and mobility subscription data) as defined in clause 5.2.12.2.1. If the corresponding NF consumer does not include the Serving PLMN ID, the UDM provides the subscription data for the SUPI associated to the HPLMN.
If the AMF already has subscription data for the UE but the SoR Update Indicator in the UE context requires the AMF to retrieve SoR information depending on the NAS Registration Type ("Initial Registration" or "Emergency Registration"), the AMF shall include SoR update indicator in the Nudm_SDM_Get depending on the NAS Registration type.
Outputs, Required: The consumer NF gets the requested subscription data.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.3 Nudm_SDM_Notification service operation | Service or service operation name: Nudm_SDM_Notification
Description: The UDM notifies NF consumer of the updates of Subscription Data indicated by the "subscription data Type" input and additional UDM-related parameters.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: None.
Outputs, Required: Result Indication.
The UDM invokes this service operation under the following cases:
- When the subscription data is updated at the UDM, the updated subscription information is notified to the serving NF that has subscribed for the specific subscription data type to be notified.
- When the UDM needs to deliver Steering of Roaming information to a UE.
- When the UDM needs to deliver UDM Update Data to a UE (e.g. a new Routing Indicator or Default Configured NSSAI to the UE).
If the updated subscription information is related to session management the subscriber data may contain e.g. Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI/ARP.
Outputs, Optional: Redirection information.
If the NF consumer is AMF and if the result of the service operation fails, AMF shall set corresponding cause value in result indication which can be used by the UDM for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the UDM to resend UE related message to the AMF that serves the UE. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.4 Nudm_SDM_Subscribe service operation | Service operation name: Nudm_SDM_Subscribe
Description: The NF consumer subscribes for updates to Subscription Data indicated by the 'subscription data type' input. The UDM shall check the requested consumer is authorized to subscribe to requested updates.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: Data Sub Key(s), Immediate Report Indication, Disaster Roaming Indicator indicating that Disaster Roaming service is applied.
Outputs, Required: None.
Outputs, Optional: Subscription Data. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.5 Nudm_SDM_Unsubscribe service operation | Service operation name: Nudm_SDM_Unsubscribe
Description: The NF consumer unsubscribes from updates to Subscription Data indicated by the 'subscription data type input.
Inputs, Required: Subscription data type(s), Key for each Subscription data type(s).
Inputs, Optional: If the NF type is SMF: DNN, S-NSSAI.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.6 Nudm_SDM_Info service operation | Service Operation name: Nudm_SDM_Info
Description: Consumer NF provides UDM with information about the status of the subscription data management procedures. This service operation is used for:
- providing acknowledgement from the UE to UDM about successful delivery of Steering of Roaming information via the AMF as defined in TS 23.122 [22].
- providing acknowledgement from the UE to UDM about successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF.
- providing acknowledgement from the UE to UDM about successful delivery of UDM Update Data via the AMF as defined in clause 4.20.
- providing acknowledgement from the AMF to UDM that the delivery of the UDM Update Data has failed as defined in clause 4.20.
Inputs, Required: SUPI, Info (e.g. UE acknowledgment of SoR information from UDM via AMF, UE acknowledgement of successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF, UE acknowledgment of UDM Update Data from UDM via AMF, failed transmission of UDM Update Data from UDM via AMF, failed transmission of SoR information from UDM via AMF).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.7 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.3.8 Nudm_SDM_ModifySubscription service operation | Service operation name: Nudm_SDM_ModifySubscription
Description: The NF consumer requests to modify an existing subscription to notifications of data changes.
Inputs, Required: Subscription Correlation ID, SUPI.
Inputs, Optional: Expiry time, Monitored resource URIs.
Outputs, Required: None.
Outputs, Optional: Subscription Data. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.4 Nudm_UEAuthentication Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.4.1 General | This service is used by the requester NF to get authentication data and provide UDM with the result of the authentication procedure success. In the case of SNPN, this service may be used to instruct the AUSF to execute authentication towards AAA-S. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.4.2 Nudm_UEAuthentication_Get service operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.4.3 Nudm_UEAuthentication_ResultConfirmation service operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5 Nudm_EventExposure service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5.1 General | See clause 4.15.3.1. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5.2 Nudm_EventExposure_Subscribe service operation | Service operation name: Nudm_EventExposure_Subscribe
Description: The NF consumer subscribes to receive an event.
NF Consumers: NEF, SMS-GMSC.
Inputs, Required: Target of Event Reporting: UE(s) ID (SUPI or GPSI, Internal Group Identifier or External Group Identifier, or indication that any UE is targeted), Event filter containing the Event Id(s) (see clause 4.15.3.1) and Event Reporting Information defined in Table 4.15.1-1.
Inputs, Optional: Expiry time, DNN, S-NSSAI, traffic descriptor identifying the source of the downlink IP or Ethernet traffic (for Availability after DDN Failure and downlink data delivery status events), MTC Provider Information, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested).
For configuration of monitoring events applicable to both EPC and 5GC, a combined SCEF+NEF indicates that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC) and may include a SCEF address (i.e. if the event needs to be configured in a serving node in the EPC and the corresponding notification needs to be sent directly to the SCEF).
Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy).
Outputs, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1), Number of UE if the External Group Identifier and Maximum Number of Reports are included in the inputs.
Number of UEs indicates the number of UEs within the group identified by the External Group Identifier. The NEF uses this value to determine whether the monitoring event has been reported for all group member UEs. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5.3 Nudm_EventExposure_Unsubscribe service operation | Service operation name: Nudm_EventExposure_Unsubscribe
Description: the consumer deletes the subscription of an event if already defined in UDM.
Inputs, Required: Subscription Correlation ID.
Outputs, Required: Operation execution result indication. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5.4 Nudm_EventExposure_Notify service operation | Service operation name: Nudm_EventExposure_Notify
Description: UDM reports the event to the consumer that has previously subscribed.
Inputs, Required: Event ID, Notification Correlation Information, time stamp.
Inputs, Optional: Event specific parameters list, Event Removal Indication, list of group member UE(s) whose subscription to event notification(s) are removed from a group-based event notification subscription, UE(s) added/removed to/from the group.
Outputs, Required: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.5.5 Nudm_EventExposure_ModifySubscription service operation | Service operation name: Nudm_EventExposure_ModifySubscription
Description: The NF consumer requests to modify an existing subscription to event notifications.
NF Consumers: NEF, SMS-GMSC.
Inputs, Required: UE(s) ID (SUPI or GPSI, Internal Group Identifier or External Group Identifier, or any UE), Subscription Correlation ID, Modifications to the Event Subscription.
Inputs, Optional:
Outputs, Required: Operation execution result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6 Nudm_ParameterProvision service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6.1 General | This service is for allowing NEF to provision of information which can be used for the UE in 5GS.
Parameter Provision data types used in the Nudm_ParameterProvision Service are defined in Table 5.2.3.6.1-1 below.
Table 5.2.3.6.1-1: Parameter Provision data types
Parameter Provision data type
Description
Expected UE Behaviour parameters
See clause 4.15.6.3
Network Configuration parameters
See clause 4.15.6.3a
5G VN group configuration data
5G VN Group Data and 5G VN Group membership management parameters for the 5G VN Group. See clause 4.15.6.3b and clause 4.15.6.3c.
Location Privacy Indication parameters
Location Privacy Indication parameters of the "LCS privacy" Data Subset of the Subscription Data.
See clause 5.2.3.3.1 of the present document and clause 7.1 of TS 23.273 [51].
Ranging/Sidelink Positioning Privacy Indication parameters
Ranging/Sidelink Poistioning Privacy Indication parameters of the "Ranging/Sidelink Positioning privacy" Data Subset of the Subscription Data.
See clause 5.2.3.3.1 of the present document and Annex B of TS 33.533 [94].
Enhanced Coverage Restriction Information
See clause 4.27.1 and clause 5.31.12 of TS 23.501 [2].
ECS Address Configuration Information
See clause 4.15.6.3d.
Multicast MBS group membership management parameters
See clause 7.2.9 of TS 23.247 [78].
MBS Session Authorization information
See clause 7.2.9 of TS 23.247 [78].
MBS Session Assistance Information
See clause 7.2.9a of TS 23.247 [78].
DNN and S-NSSAI specific Group Parameters
See clause 4.15.6.3.e.
Application-Specific UE Behaviour parameters
See clause 4.15.6.3f.
CAG Information provisioning parameters
See clause 4.15.6.3h.
Static IP address assignment parameters
See clause 4.15.6.3i.
At least a mandatory key is required for each Parameter Provision Data Type to identify the corresponding data as defined in Table 5.2.3.6.1-2.
Table 5.2.3.6.1-2: Parameter Provision data types keys
Parameter Provision Data Types
Data Key
Data Sub Key
Expected UE Behaviour parameters
GPSI or External Group ID
-
Network Configuration parameters
GPSI
-
5G VN group data
External Group Identifier
-
5G VN group membership management parameters
External Group Identifier
-
Location Privacy Indication parameters.
GPSI
-
Ranging/Sidelink Positioning Privacy Indication parameters
GPSI
-
Enhanced Coverage Restriction Information
GPSI
-
ECS Address Configuration Information
GPSI or External Group ID or any UE
-
Multicast MBS group membership management parameters
External Group Identifier
-
MBS Session Authorization information
External Group ID
-
MBS Session Assistance Information
External Group ID (NOTE)
-
DNN and S-NSSAI specific Group Parameters
External Group ID
-
Application-Specific UE Behaviour parameters
GPSI or External Group ID
-
CAG Information provisioning parameters
GPSI
-
Static IP address assignment parameters
GPSI
-
NOTE: MBS Session Assistance Information can contain a subset list of UEs represented by GPSI associated with the External Group ID. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6.2 Nudm_ParameterProvision_Update service operation | Service operation name: Nudm_ParameterProvision_Update.
Description: The consumer updates the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters, Location Privacy Indication parameters, Ranging/Sidelink Positioning Privacy Indication parameters, Enhanced Coverage Restriction Information, ECS Address Configuration Information, CAG Information provisioning parameters), 5G VN group related information (5G VN group data, 5G VN membership management), Multicast MBS group related information, or Application-Specific UE Behaviour, or Static IP address assignment parameters.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI or SUPI, External Group ID, DNN, S-NSSAI, at least one of the Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Network Configuration parameters or 5G VN group related information, MTC Provider Information, Validity Time or Location Privacy Indication parameters or Ranging/Sidelink Positioning Privacy Indication parameters or Enhanced Coverage Restriction Information or ECS Address Configuration Information, Multicast MBS related information, Application-Specific UE Behaviour, Static IP address assignment parameters, or CAG Information provisioning parameters , or DNN and S-NSSAI specific Group Parameters.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: Transaction specific parameters, if available.
For Multicast MBS related information, refer to TS 23.247 [78]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6.3 Nudm_ParameterProvision_Create service operation | Service operation name: Nudm_ParameterProvision_Create
Description: The consumer creates a Network Configuration with one or more parameters, a 5G VN group related information (e.g. 5G VN group data, 5G VN membership management), or Multicast MBS related information, or Static IP address assignment parameters, or CAG Information.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI, External Group ID, DNN, S-NSSAI, one or multiple Network Configuration parameters, one or multiple Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or one or multiple Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or ECS Address Configuration Information, or for 5G VN group creation, External Group ID and 5G VN group related information, MTC Provider Information, for Multicast MBS related information, or DNN and S-NSSAI specific Group Parameters, or Static IP address assignment parameters, or CAG Information provisioning parameters.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: Transaction specific parameters, if available; Internal Group ID if the inputs include a new 5G VN configuration.
For Multicast MBS related information, refer to TS 23.247 [78]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6.4 Nudm_ParameterProvision_Delete service operation | Service operation name: Nudm_ParameterProvision_Delete
Description: The consumer deletes one or more previously created Network Configuration parameters, or a 5G VN group, or ECS Address Configuration Information, or Multicast MBS related information, or Static IP address assignment parameters, or CAG Information.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: GPSI, External Group ID, for 5G VN group deletion or for Multicast MBS deletion or Network Configuration of Parameters, Static IP address assignment parameters.
Outputs, Required: Transaction Reference ID(s), Operation execution result indication.
Outputs, Optional: None.
For Multicast MBS related information, refer to TS 23.247 [78]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.6.5 Nudm_ParameterProvision_Get service operation | Service operation name: Nudm_ParameterProvision_Get
Description: The consumer gets the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters).
Inputs, Required: GPSI, AF Identifier, requested information (e.g. Expected UE Behaviour, Network Configuration parameters).
Inputs, Optional: None.
Outputs, Required: Requested data, Operation execution result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7 Nudm_NIDDAuthorisation service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7.1 General | See clause 4.25.3. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7.2 Nudm_NIDDAuthorisation_Get service operation | Service operation name: Nudm_NIDDAuthorisation_Get
Description: The consumer requests authorisation for NIDD Configuration.
Inputs, Required: GPSI or External Group Identifier, DNN, S-NSSAI, MTC Provider Information, Update Notification Address.
Inputs, Optional: NIDD Duration.
Outputs, Required: Single value or list of (SUPI, GPSI), Result.
Outputs, Optional: NIDD Duration. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7.3 Nudm_NIDDAuthorisation_UpdateNotify service operation | Service operation name: Nudm_NIDDAuthorisation_UpdateNotify
Description: This service operation is used by the UDM to notify the NIDD Authorization Update to NF consumer.
Inputs, Required: SUPI, GPSI, DNN, S-NSSAI, Result.
Inputs, Optional: Cause (e.g. subscription withdrawal, DNN used for NIDD service is removed from the UE subscription), NIDD Duration.
Outputs, Required: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7.4 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.7.5 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.8 Nudm_ServiceSpecificAuthorisation service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.8.1 General | Service description: This service is for authorisation of a specific service configuration. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.8.2 Nudm_ServiceSpecificAuthorisation_Create service operation | Service operation name: Nudm_ServiceSpecificAuthorisation_Create
Description: The consumer requests authorisation for a specific service configuration.
Inputs, Required: GPSI or External Group Id, DNN, S-NSSAI, Service Type (e.g. AF guidance for URSP), Update Notification address.
Inputs, Optional: MTC Provider Information, AF ID.
Outputs, Required: Authorisation result indication, SUPI or Internal Group Id, Service Specific Authorization Id.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.8.3 Nudm_ServiceSpecificAuthorisation_UpdateNotify service operation | Service operation name: Nudm_ServiceSpecificAuthorisation_UpdateNotify
Description: This service operation is used by the UDM to notify a Service Specific Authorisation Update to NF consumer.
Inputs, Required: GPSI or External Group Id, SUPI or Internal Group Id, Status, Cause (e.g. subscription withdrawal, DNN associated to the authorization is removed from UE subscription).
Inputs, Optional: DNN, S-NSSAI, Service Type (e.g. AF guidance for URSP), MTC Provider Information, AF ID.
Outputs, Required: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.8.4 Nudm_ServiceSpecificAuthorisation_Remove service operation | Service operation name: Nudm_ServiceSpecificAuthorisation_Remove
Description: The consumer requests the removal of the authorisation for a specific service configuration.
Inputs, Required: Service Specific Authorisation Id.
Outputs, Required: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.9 Nudm_ReportSMDeliveryStatus service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.9.1 General | Service description: This service is to report the SM-Delivery Status to UDM. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.3.9.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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.4 5G-EIR Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.4.1 General | The following table illustrates the 5G-EIR Service.
Table 5.2.4-1: NF services provided by 5G-EIR
NF service
Service Operations
Operation Semantics
Example Consumer(s)
N5g-eir_Equipment Identity Check
Get
Request/Response
AMF |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.4.2 N5g-eir_EquipmentIdentityCheck service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.4.2.1 General | Service Description: This service is provided by the 5G-EIR to check the PEI and check whether the PEI is in the prohibited list or not. The service can be consumed by AMF. The service operations provided within this service are depicted as below. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.4.2.2 N5g-eir_EquipmentIdentityCheck_Get service operation | Service operation name: N5g-eir_EquipmentIdentityCheck_Get
Description: Check the PEI and determine whether the subscriber is allowed to use the equipment.
Inputs, Required: PEI, SUPI.
Inputs, Optional: none
Outputs, Required: PEI checking result
Outputs, Optional: none |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5 PCF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.1 General | The following table illustrates the PCF Services.
Table 5.2.5.1-1: NF services provided by PCF
Service Name
Service Operations
Operation
Semantics
Example Consumer (s)
Npcf_AMPolicyControl
Create
Request/Response
AMF
Update
Request/Response
AMF
UpdateNotify
Subscribe/Notify
AMF
Delete
Request/Response
AMF
Npcf_Policy Authorization
Create
Request/Response
AF, NEF, TSCTSF
(NOTE)
Update
Request/Response
AF, NEF, TSCTSF
Delete
Request/Response
AF, NEF, TSCTSF
Notify
Subscribe/Notify
AF, NEF, NWDAF, PCF, TSCTSF
Subscribe
AF, NEF, NWDAF, PCF, TSCTSF
Unsubscribe
AF, NEF, NWDAF, PCF, TSCTSF
Npcf_SMPolicyControl
Create
Request/Response
SMF
UpdateNotify
Subscribe/Notify
SMF
Update
Request/Response
SMF
Delete
Request/Response
SMF
Npcf_BDTPolicyControl
Create
Request/Response
NEF
Update
Request/Response
NEF
Notify
NEF
Npcf_UEPolicyControl
Create
Request/Response
AMF, PCF
Update
Request/Response
AMF, PCF
UpdateNotify
Subscribe/Notify
AMF, PCF
Delete
Request/Response
AMF, PCF
Npcf_EventExposure
Subscribe
Subscribe/Notify
AF, NEF, NWDAF
Unsubscribe
Notify
Npcf_AMPolicyAuthorization
Create
Request/Response
AF, NEF, TSCTSF
Update
Request/Response
AF, NEF, TSCTSF
Delete
Request/Response
AF, NEF, TSCTSF
Notify
Subscribe/Notify
AF, NEF, 5G DDNMF
Subscribe
AF, NEF, 5G DDNMF
Unsubscribe
AF, NEF, 5G DDNMF
Npcf_PDTQPolicyControl
Create
Request/Response
NEF
Update
Request/Response
NEF
Notify
NEF
NOTE: In the Npcf_PolicyAuthorization operations, PCF is a consumer when the PCF for the UE and the PCF for the PDU session are different. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2 Npcf_AMPolicyControl service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2.1 General | Service description: NF Service Consumer, e.g. AMF, can create and manage an AM Policy Association in the PCF through which the NF Service Consumer receives access and mobility related policy information for a UE identified by a SUPI.
As part of this service, the PCF may provide the NF Service Consumer, e.g. AMF, with AM policy information for a SUPI that may contain:
- Access and mobility related policy information as defined in clause 6.5 of TS 23.503 [20]. In the case of roaming, this information is provided by V-PCF;
- Policy Control Request Trigger of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503 [20]. In the case of roaming, the V-PCF may subscribe to AMF.
At Npcf_AMPolicyControl_Create, the NF Service Consumer, e.g. AMF requests the creation of a corresponding AM Policy Association with the PCF (Npcf_AMPolicyControl_Create) and provides relevant parameters about the UE context to the PCF. When the PCF has created the AM Policy Association, the PCF may provide access and mobility related policy information in the response.
When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. AMF requests the update (Npcf_AMPolicyControl_Update) of the AM Policy Association by providing information on the condition(s) that have been met as defined in clause 6.1.2.5 of TS 23.503 [20]. The PCF may provide updated access and mobility related policy information to the NF Service Consumer in the response.
The PCF may at any time provide updated access and mobility related policy information (Npcf_AMPolicyControl_UpdateNotify);
At UE deregistration the NF Service Consumer, e.g. AMF requests the deletion of the corresponding AM Policy Association (Npcf_AMPolicyControl_Delete). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2.2 Npcf_AMPolicyControl_Create service operation | Service operation name: Npcf_AMPolicyControl_Create
Description: NF Service Consumer can request the creation of an AM Policy Association and by providing relevant parameters about the UE context to the PCF.
Inputs, Required: SUPI.
Inputs, Optional: Information provided by the AMF, such as Access Type, Permanent Equipment Identifier, GPSI, User Location Information, UE Time Zone, Serving Network identifier (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), RAT type, List of subscribed Service Area Restrictions, subscribed RFSP Index, the Allowed NSSAI, Partially Allowed NSSAI, S-NSSAI(s) rejected partially in the RA, Rejected S-NSSAI(s) for the RA, Pending NSSAI, Target NSSAI, GUAMI, Subscribed UE-AMBR, Network Slice Replacement supported for the UE (see clause 5.15.19 of TS 23.501 [2]), Internal Group (see clause 5.9.7 of TS 23.501 [2]), subscription notification indication, Energy Saving indicator (see clause 5.51.6 of TS 23.501 [2]), backup AMF(s) (if NF Type is AMF). Backup AMF(s) are sent only once by the AMF to the PCF in its first interaction with the PCF, list of NWDAF instance Ids and corresponding Analytics ID(s).
Outputs, Required: AM Policy Association ID.
Outputs, Optional: The requested access and mobility related policy information as defined in clause 6.5 of TS 23.503 [20] and Policy Control Request Trigger(s) of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503 [20], Request for notification of SM Policy Association establishment and termination, PCF binding information.
See clause 4.2.2.2.2 (step 16) for the detail usage of this service operation for AMF. In step 16, the AMF requests the PCF to apply operator policies for the UE.
See clause 4.16.1.2 (steps 2 and 3) for the detail usage of this service operation for AMF. In step 2, the AMF requests the PCF to apply operator policies for the UE; in step 3, the PCF acknowledges AMF with requested policy.
Request for notification of SM Policy Association establishment and termination and the PCF binding information apply when the BSF is not deployed. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2.3 Npcf_AMPolicyControl_UpdateNotify service operation | Service operation name: Npcf_AMPolicyControl_UpdateNotify
Description: Provides to the NF Service Consumer, e.g. AMF, updated AM related Policy information for the AM Policy Association as defined in clause 6.5 of TS 23.503 [20].
NOTE: This notification corresponds to an implicit subscription.
Inputs, Required: AM Policy Association ID.
Inputs, Optional: Access and Mobility related information or indication of AM Policy Association termination.
Outputs, Required: Success or failure.
Outputs, Optional: None.
See clause 4.16.2.2 for the usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2.4 Npcf_AMPolicyControl_Delete service operation | Service operation name: Npcf_AMPolicyControl_Delete
Description: Provides means for the NF Consumer to delete the AM Policy Association.
Inputs, Required: AM Policy Association ID.
Inputs, Optional: None.
Outputs, Required: Success or Failure.
Outputs, Optional: None.
See clause 4.16.3.2 (step 2 and 3) for the detail usage of this service operation for AMF. In step 2, the AMF initiates the AM Policy Association Termination procedure; in step 3 the PCF deletes the AM Policy Association for this AM Policy Association ID. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.2.5 Npcf_AMPolicyControl_Update service operation | Service operation name: Npcf_AMPolicyControl_Update.
Description: NF Service Consumer, e.g. AMF can request the update of the AM Policy Association to receive updated access and mobility related policy information for the UE context when the Policy Control Request Trigger is met or the AMF is relocated due to the UE mobility and the old PCF is selected.
Inputs, Required: AM Policy Association ID.
Inputs, Optional: Information on the Policy Control Request Trigger condition that has been met as defined in clause 6.1.2.5 of TS 23.503 [20], GUAMI(s) (if NF Type is AMF), list of NWDAF instance Ids and corresponding Analytics ID(s), Target NSSAI.
Outputs, Required: Success or not.
Outputs, Optional: Access and mobility related policy information for the UE context as defined in clause 6.5 of TS 23.503 [20] and Policy Control Request Trigger(s) of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503 [20].
See clause 4.16.2.1 for the usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3 Npcf_PolicyAuthorization Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.1 General | Service description: This service is to authorise an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. Additionally, this service allows an AF or TSCTSF to exchange port management information with DS-TT and NW-TT. This service allows the NF consumer to subscribe/unsubscribe the notification of events, which are defined in clause 6.1.3.18 of TS 23.503 [20]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.2 Npcf_PolicyAuthorization_Create service operation | Service operation name: Npcf_PolicyAuthorization_Create
Description: Authorize the request and optionally determines and installs SM Policy Control Data according to the information provided by the NF Consumer or provides Port Management Information Container for ports on DS-TT or NW-TT, or User plane node Management Information Container.
Inputs, Required: UE (IP or MAC) address, identification of the application session context.
Inputs, Optional: GPSI(s) or SUPI(s) if available, Internal Group Identifier, DNN if available, S-NSSAI if available, Media type, Media format, bandwidth requirements, sponsored data connectivity information if applicable, flow description information as described in clause 6.1.3.6 of TS 23.503 [20], AF Application Identifier, AF Communication Service Identifier, AF Record Identifier, Flow status, Priority indicator, emergency indicator, ASP Identifier, resource allocation outcome, AF Application Event Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, AF Transaction Id, Early and/or late notifications about UP path management events, temporal validity condition, spatial validity condition, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation, AF indication for simultaneous connectivity over source and target PSA at edge relocation, EAS Correlation indication, Common EAS IP address, Traffic Correlation ID, FQDN(s), Indication of considering N6 delay as described in clause 5.6.7 in 23.501 [2], Background Data Transfer Reference ID, priority sharing indicator as described in clause 6.1.3.15 of TS 23.503 [20], pre-emption control information as described in clause 6.1.3.15 of TS 23.503 [20], Port Management Information Container and related port number, User plane node Management Information Container, TSN AF parameters provided by the TSN AF to the PCF as described in clause 6.1.3.23 of TS 23.503 [20], TSCTSF parameters provided by the TSCTSF to the PCF as described in clause 6.1.3.23a and clause 6.1.3.23b of TS 23.503 [20], QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501 [2], Reporting frequency, Target of reporting and optional an indication of direct event notification as described in clause 6.1.3.21 of TS 23.503 [20], QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503 [20], RT Latency Indication as described in clause 6.1.3.22 of TS 23.503 [20], Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), TSC Assistance Container, MPS for Data Transport Service indicator as described in clause 6.1.3.11 of TS 23.503 [20], Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503 [20], SFC Identifier(s), Metadata, Header Handling Control information as described in clause 5.6.17 of TS 23.501 [2], Periodicity as described clauses 6.1.3.22 and 6.3.1 of TS 23.503 [20], PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501 [2], Protocol Description (as described in clauses 5.37.5, 5.37.8.3, 5.37.9.2, 5.37.9.4 and other (sub)clauses in clause 5.37 of TS 23.501 [2]) and/or On-path N6 Signalling Information (see clause 5.37.9 of TS 23.501 [2]), Data Burst Handing Information as described in clause 6.3.1of TS 23.503 [20], Indication of ECN marking for L4S as described in clause 6.1.3.22 of TS 23.503 [20], Data Burst Size Marking Support Indication as described in clause 6.1.3.27.5 of TS 23.503 [20], Time to Next Burst Support Indication as described in clause 6.1.3.27.5 of TS 23.503 [20], Expedited Transfer Indication as described in clause 6.1.3.27.9 of TS 23.503 [20], Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event, Multi-Modal Service ID together with Multi-modal Service Requirements information for each data flow as described in clause 6.1.3.27.3 of TS 23.503 [20], QoS duration, QoS inactivity interval as described in clause 6.1.3.22 of TS 23.503 [20].
NOTE 1: When only one DNAI and corresponding routing profile ID(s) and the Indication for EAS Relocation are available, the presented DNAI is the target DNAI as defined in clause 6.3.7 of TS 23.548 [74].
NOTE 2: A dedicated Notification Target Address for PMIC/UMIC UPF event and Correlation ID for PMIC/UMIC UPF event are provided by the event consumer over Npcf_PolicyAuthorization as the corresponding events are reported by the UPF and not by the PCF. Providing such information indicates that the consumer of the Npcf_PolicyAuthorization (TSN AF, TSCTSF) supports PMIC/UMIC via Nupf event reporting.
Outputs, Required: Success or Failure (reason for failure, e.g. as defined in clauses 6.1.3.16 and clause 6.1.3.10 of TS 23.503 [20]).
Outputs, Optional: The service information that can be accepted by the PCF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.3 Npcf_PolicyAuthorization_Update service operation | Service operation name: Npcf_PolicyAuthorization_Update
Description: Provides updated information to the PCF.
Inputs, Required: Identification of the application session context.
Inputs, Optional: Media type, Media format, bandwidth requirements, sponsored data connectivity information if applicable, flow description information as described in clause 6.1.3.6 of TS 23.503 [20], AF Application Identifier, AF Communication Service Identifier, AF Record Identifier, Flow status, Priority indicator, resource allocation outcome, AF Application Event Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, AF Transaction Id, Early and/or late notifications about UP path management events, Acknowledgement of notifications about UP path management events, temporal validity condition, spatial validity condition, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation, AF indication for simultaneous connectivity over source and target PSA at edge relocation, Indication of considering N6 delay as described in clause 5.6.7 of TS 23.501 [2], Background Data Transfer Reference ID, priority sharing indicator as described in clause 6.1.3.15 of TS 23.503 [20], pre-emption control information as described in clause 6.1.3.15 of TS 23.503 [20], Port Management Information Container and related port number, User plane node Management Information Container, TSN AF parameters provided by the TSN AF to the PCF as described in clause 6.1.3.23 of TS 23.503 [20], TSCTSF parameters provided by the TSCTSF to the PCF as described in clause 6.1.3.23a and clause 6.1.3.23b of TS 23.503 [20], QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503 [20], Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), TSC Assistance Container, QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501 [2], Reporting frequency, Target of reporting and optional an indication of direct event notification as described in clause 6.1.3.21 of TS 23.503 [20], MPS for Data Transport Service indicator as described in clause 6.1.3.11 of TS 23.503 [20], Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503 [20], SFC Identifier(s), Metadata, Header Handling Control information as described in clause 5.6.17 of TS 23.501 [2], Periodicity as described clauses 6.1.3.22 and 6.3.1 of TS 23.503 [20], PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501 [2], Protocol Description (as described in clauses 5.37.5, 5.37.8.3, 5.37.9.2, 5.37.9.4 and other (sub)clauses in clause 5.37 of TS 23.501 [2]) and/or On-path N6 Signalling Information (see clause 5.37.9 of TS 23.501 [2]), Data Burst Handing Information as described in clause 6.3.1of TS 23.503 [20], Data Burst Size Marking Support Indication as described in clause 6.1.3.27.5 of TS 23.503 [20], Time to Next Burst Support Indication as described in clause 6.1.3.27.5 of TS 23.503 [20], Expedited Transfer Indication as described in clause 6.1.3.27.9 of TS 23.503 [20], Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event, updated information for Multi-modal Service Requirements as described in clause 6.1.3.27.3 of TS 23.503 [20].
NOTE: When only one DNAI and corresponding routing profile ID(s) and the Indication for EAS Relocation are available, the presented DNAI is the target DNAI as defined in clause 6.3.7 of TS 23.548 [74].
Outputs, Required: Success or Failure (reason for failure, e.g. as defined in clause 6.1.3.16 of TS 23.503 [20]).
Outputs, Optional: The service information that can be accepted by the PCF.
Provides updated application level information and communicates with Npcf_SMPolicyControl service to determine and install the policy according to the information provided by the NF Consumer. Updates an application context in the PCF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.4 Npcf_PolicyAuthorization_Delete service operation | Service operation name: Npcf_PolicyAuthorization_Delete
Description: Provides means for the NF Consumer to delete the context of application level session information.
Inputs, Required: Identification of the application session context.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.5 Npcf_PolicyAuthorization_Notify service operation | Service operation name: Npcf_PolicyAuthorization_Notify
Description: provided by the PCF to notify NF consumers of the subscribed events.
Inputs, Required: Event ID.
The events that can be subscribed are defined in clause 6.1.3.18 of TS 23.503 [20].
Inputs, Optional: Event information (defined on a per Event ID basis) are defined in clause 6.1.3.18 of TS 23.503 [20], Notification Correlation Information (information to identify the application session), DNN, S-NSSAI.
Notification Correlation Information is mandatory except in the case of the new 5GS Bridge/Router information detected event if no AF session exists between the PCF and the AF.
DNN and S-NSSAI are required in the case of private IPv4 address being used for the IP type PDU Session that are potentially impacted by time sensitive communication and time synchronization service.
The PCF forwards UP path change notification to the AF in the case that UP path change notification is received at the PCF from SMF.
To support UE-Satellite-UE (UE-SAT-UE) communication, the UP path change notification includes DNAI to represent the change of satellite identifier.
NOTE: DNAI value can be derived from the satellite identifier as per operator policy and implementation.
The event notification may contain the type of notification ("EARLY" or "LATE").
Outputs, Required: Operation execution result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.6 Npcf_PolicyAuthorization_Subscribe service operation | Service operation name: Npcf_PolicyAuthorization_Subscribe
Description: provided by the PCF for NF consumers to explicitly subscribe the notification of events.
Inputs, Required: (Set of) Event ID(s) as specified in Npcf_PolicyAuthorization_Notify service operation, target of PCF event reporting (defined below), NF ID, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address (+ Notification Correlation ID).
The target of PCF event reporting the subscription for an individual AF session: An UE IP address (IPv4 address or IPv6 prefix) optionally together with a (DNN, S-NSSAI) or with a UE ID (SUPI or GPSI).
Inputs, Optional: Event Filter, Subscription Correlation ID (in the case of modification of the event subscription), Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event.
Outputs, Required: When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional: URSP rule enforcement including Connection Capability. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.3.7 Npcf_PolicyAuthorization_Unsubscribe service operation | Service operation name: Npcf_PolicyAuthorization_Unsubscribe
Description: Enable NF consumers to explicitly unsubscribe the notification of PCF events related to Npcf_PolicyAuthorization_Subscribe operation.
Inputs, Required: Subscription Correlation.
Inputs, Optional: None.
Outputs, Required: Success or Failure.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4 Npcf_SMPolicyControl service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4.1 General | Service description: NF Service Consumer, e.g. SMF, can create and manage a SM Policy Association in the PCF through which the NF Service Consumer receives policy information for a PDU Session.
As part of this service, the PCF may provide the NF Service Consumer, e.g. SMF, with policy information for the PDU Session that may contain:
- PDU Session related policy information as defined in clause 6.4 of TS 23.503 [20].
- PCC rule information as defined in clause 6.3 of TS 23.503 [20].
- Policy Control Request Trigger information i.e. a set of Policy Control Request Trigger(s) as defined in clause 6.1.3.5 of TS 23.503 [20].
At PDU Session establishment the NF Service Consumer, e.g. SMF, requests the creation of a corresponding SM Policy Association with the PCF (Npcf_SMPolicyControl_Create) and provides relevant parameters about the PDU Session to the PCF.
When the PCF has created the SM Policy Association, the PCF may provide policy information for the PDU Session in the response.
When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. SMF requests the update(Npcf_SMPolicyControl_Update) of the SM Policy Association by providing information on the condition(s) that have been met as defined in clause 6.1.3.5 of TS 23.503 [20]. The PCF may provide updated policy information for the PDU Session to the NF Service Consumer in the response.
The PCF may at any time provide updated policy information for the (Npcf_SMPolicyControl_UpdateNotify).
At PDU Session Release the NF Service Consumer, e.g. SMF requests the deletion of the corresponding SM Policy Association (Npcf_SMPolicyControl_Delete). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4.2 Npcf_SMPolicyControl_Create service operation | Service operation name: Npcf_SMPolicyControl_Create.
Description: The NF Service Consumer can request the creation of a SM Policy Association and provides relevant parameters about the PDU Session to the PCF.
Inputs, Required: SUPI (or PEI in the case of emergency PDU Session without SUPI), PDU Session id, DNN, S-NSSAI and RAT Type.
Inputs, Optional: Information provided by the SMF, such as PDU Session Type, Request Type, Access Type, the IPv4 address and/or IPv6 prefix, PEI, GPSI, Non-3GPP Device Connection Information (as defined in clause 4.3.2), User Location Information, UE Time Zone, Serving Network identifier (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), Charging Characteristics information, Session-AMBR, subscribed default QoS information (5QI, 5QI Priority Level, ARP), UE support of reflective QoS (see TS 23.501 [2], clause 5.7.5.1), Number of supported packet filters for signalled QoS rules for the PDU Session (see TS 23.501 [2], clause 5.7.1.4), UE's capability to support (S)RTP Multiplexed Media Identification Information in IP Packet Filters (see clause 4.3.2.2.1), 3GPP PS Data Off status, Trace Requirements and Internal Group Identifier (see clause 5.9.7 of TS 23.501 [2]), DN Authorization Profile Index, DN authorized Session AMBR, Framed Route information (as defined in Table 5.2.3.3.1-1), MA PDU Request indication, MA PDU Network-Upgrade Allowed indication, ATSSS capabilities of the MA PDU Session, QoS constraints from the VPLMN (as defined in clause 5.7.1.11 of TS 23.501 [2]), Satellite backhaul category, list of NWDAF instance Ids (used by AMF, SMF, UPF) and corresponding Analytics ID(s), PVS IP address(es) and/or PVS FQDN(s) and Onboarding Indication in the case of ON-SNPN (see clause 5.30.2.10.4.2 of TS 23.501 [2]), URSP rule enforcement that including Connection Capability, PCF binding information (address(es) of PCF for UE, instance id of PCF for UE), HR-SBO support indication (see clause 6.2.1.2 of TS 23.503 [20]), Alternative S-NSSAI (see clause 5.15.19 of TS 23.501 [2]), URSP delivery in EPS support indication, Local Offloading Management indication.
NOTE 1: If SMF receives the DN authorized Session AMBR from the DN-AAA at PDU Session establishment, it includes the DN authorized Session AMBR within the Session-AMBR, instead of the subscribed Session-AMBR received from the UDM, in the request.
NOTE 2: It is up to stage 3 to determine whether the corresponding supportedFeature in Npcf_SMPolicyControl can be reused as URSP delivery in EPS support indication.
NOTE 3: When Local Offloading Management is allowed, SMF provides Local Offloading Management indication to PCF.
W-5GAN specific PDU Session information provided by the SMF is specified in TS 23.316 [53].
Outputs, Required: SM Policy Association ID defined in TS 29.512 [57]. Success or Failure.
Outputs, Optional: Policy information for the PDU Session as defined in TS 23.503 [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503 [20].
See clause 5.8.2.2 of TS 23.501 [2] for allocation of IPv4 address and IPv6 prefix. The IPv6 prefix length is /64, or is shorter than /64 when Prefix Delegation applies.
See clause 4.16.4 for the detail usage of this service operation.
See clauses 4.22.2.1 and 4.22.3 for detailed usage of this service operation for ATSSS. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4.3 Npcf_SMPolicyControl_UpdateNotify service operation | Service operation name: Npcf_SMPolicyControl_UpdateNotify
Description: Provides to the NF Service Consumer, e.g. SMF, updated Policy information for the PDU Session.
Inputs, Required: SM Policy Association ID.
Inputs, Optional: Policy information for the PDU Session as defined in TS 23.503 [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503 [20].
Outputs, Required: Success or Failure.
Outputs, Optional: None.
See clause 4.16.5.2 for the usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4.4 Npcf_SMPolicyControl_Delete service operation | Service operation name: Npcf_SMPolicyControl_Delete
Description: The NF Service Consumer can request the deletion of the SM Policy Association and of the associated resources.
Inputs, Required: SM Policy Association ID.
Inputs, Optional: 5G SRVCC indication.
Outputs, Required: Success or Failure.
Outputs, Optional: None.
See clause 4.16.6 for the usage of this service operation.
When the PDU session for IMS is released due to PS to CS handover for 5G SRVCC, SMF indicate the 5G SRVCC indication received from AMF to PCF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.4.5 Npcf_SMPolicyControl_Update service operation | Service operation name: Npcf_SMPolicyControl_Update.
Description: The NF Service Consumer can request the update of the SM Policy Association to receive updated Policy information for the PDU Session.
Inputs, Required: SM Policy Association ID.
Inputs, Optional: Information on the Policy Control Request Trigger condition that has been met, as defined in clause 6.1.3.5 of TS 23.503 [20].
W-5GAN specific PDU Session information provided by the SMF is specified in TS 23.316 [53].
Outputs, Required: Success or not.
Outputs, Optional: Policy information for the PDU Session as defined in TS 23.503 [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503 [20] and UE Policy Container.
See clause 4.16.5.1 for the usage of this service operation.
NOTE: When this service operation is invoked by SMF, race conditions apply, which are defined in TS 29.513 [47]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.5 Npcf_BDTPolicyControl Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.5.1 General | Service description: This service provides background data transfer policy, which includes the following functionalities:
- Get background data transfer policies based on the request via NEF from AF; and
- Update background data transfer based on the selection provided by AF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.5.2 Npcf_BDTPolicyControl_Create service operation | Service operation name: Npcf_BDTPolicyControl_Create
Description: This service is to create the background data transfer policy.
Inputs, Required: ASP identifier, Volume per UE, Number of UEs, Desired time window.
Inputs, Optional: S-NSSAI, DNN, Internal Group Identifier, Network Area Information, Request for notification, MAC address or IP 3-tuple of Application server.
Outputs, Required: one or more background data transfer policies, Background Data Transfer Reference ID.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.5.3 Npcf_BDTPolicyControl_Update service operation | Service operation name: Npcf_BDTPolicyControl_Update
Description: This service is to update the background data transfer policy to the PCF.
Inputs, Required: ASP identifier, background data transfer policy, Background Data Transfer Reference ID.
Inputs, Optional: Stop notification.
Outputs, Required: None
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.5.5.4 Npcf_BDTPolicyControl_Notify service operation | Service operation name: Npcf_BDTPolicyControl_Notify
Description: This service operation sends the BDT warning notification to the NF consumer.
Inputs, Required: Background data transfer reference ID.
Inputs, Optional: Network Area Information, Time window, list of candidate Background Data Transfer policies.
Outputs, Required: None.
Outputs, Optional: None. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.