Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.502  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H… 
5.2.12 UDR Services  5.2.12.1 General  5.2.12.2 Nudr_DataManagement (DM) service  5.2.12.3 Nudr_GroupIDmap service  5.2.13 BSF Services  5.2.13.1 General  5.2.13.2 Nbsf_Management service  5.2.14 UDSF Services  5.2.14.1 General  5.2.14.2 Nudsf_UnstructuredDataManagement service  5.2.14.3 Nudsf_Timer service  5.2.15 LMF Services  5.2.16 NSSF Services  5.2.16.1 General  5.2.16.2 Nnssf_NSSelection service  5.2.16.3 Nnssf_NSSAIAvailability service  5.2.17 CHF Spending Limit Control Service  5.2.17.1 General  5.2.17.2 Nchf_SpendingLimitControl service 
...

 

5.2.12  UDR Services  p. 821

5.2.12.1  General  p. 821

The following Data Set Identifiers shall be considered in this release: Subscription Data, Policy Data, Application data and Data for Exposure. The corresponding Data Subset Identifiers and Data (Sub)Key(s) are defined in Table 5.2.12.2.1-1.
The set of Data Set Identifiers shall be extensible to cater for new identifiers as well as for operator specific identifiers and related data to be consumed.
The following Table illustrates the UDR Services.
NF service Service Operations Operation Semantics Example Consumer(s)
Data Management (DM)QueryRequest/ResponseUDM, PCF, NEF
CreateRequest/ResponseNEF
DeleteRequest/ResponseNEF
UpdateRequest/ResponseUDM, PCF, NEF
SubscribeSubscribe/NotifyUDM, PCF, NEF
UnsubscribeSubscribe/NotifyUDM, PCF, NEF
NotifySubscribe/NotifyUDM, PCF, NEF
GroupIDmapQueryRequest/ResponseNRF, SCP
 
The following Table shows the Exposure data that may be stored in the UDR along with a time stamp using Data Management (DM) Service:
Category Information Description Data key Data Sub key
Access and mobility informationUE locationGives the Location or the last known location of a UE (e.g. Tai, Cell Id… both 3GPP and non-3GPP access location)SUPI or GPSI
UE time zoneCurrent time zone for the UESUPI or GPSI
UE Access type3GPP access or non-3GPP accessSUPI or GPSI
UE RAT typeDetermined as defined in clause 5.3.2.3 of TS 23.501.
The values are defined in TS 29.571		SUPI or GPSI
UE registration stateRegistered or DeregisteredSUPI or GPSI
UE connectivity stateIDLE or CONNECTEDSUPI or GPSI
UE reachability statusIt indicates if the UE is reachable for sending either SMS or downlink data to the UE, which is detected when the UE transitions to CM-CONNECTED state or when the UE will become reachable for paging, e.g. Periodic Registration Update timerSUPI or GPSI
UE SMS over NAS service statusSMS over NAS supported or not in the UESUPI or GPSI
UE Roaming statusIt indicates UE's current roaming status (the serving PLMN and/or whether the UE is in its HPLMN)SUPI or GPSI
UE Current PLMNCurrent PLMN for the UESUPI or GPSI
Session management informationUE IP addressUE IP addressSUPI or GPSIPDU session ID or DNN
PDU session statusActive / releasedSUPI or GPSIPDU session ID or DNN or UE IP address
DNAIDNAISUPI or GPSIPDU session ID or DNN or UE IP address
N6 traffic routing informationN6 traffic routing informationSUPI or GPSIPDU session ID or DNN or UE IP address
DNAI mapping informationDNAIDNAI mapping informationDNN and/or S-NSSAI
Up

5.2.12.2  Nudr_DataManagement (DM) service  p. 822

5.2.12.2.1  General  p. 822
The operations defined for Nudr_DM service use following set of parameters defined in this clause:
  • Data Set Identifier: uniquely identifies the requested set of data within the UDR (see clause 4.2.5).
  • Data Subset Identifier: it uniquely identifies the data subset within each Data Set Identifier. As specified in the procedures in clause 4, e.g. subscription data can consist of subsets particularised for specific procedures like mobility, session, etc.
  • Data Keys defined in Table 5.2.12.2.1-1
For Nudr_DM_Subscribe and Nudr_DM_Notify operations:
  • The Target of Event Reporting is made up of a Data Key and possibly a Data Sub Key both defined in Table 5.2.12.2.1-1. When a Data Sub Key is defined in the Table but not present in the Nudr_DM_Subscribe this means that all values of the Data Sub Key are targeted.
  • The Data Set Identifier plus (if present) the (set of) Data Subset Identifier(s) corresponds to a (set of) Event ID(s) as defined in clause 4.15.1
An NF Service Consumer may include an indicator when it invokes Nudr_DM Query/Create/Update service operation to subscribe the changes of the data, to avoid a separate Nudr_DM_Subscribe service operation.
Depending on the use case, it is possible to use a Data Key and/or one or multiple Data sub keys to further identify the corresponding data, as defined in Table 5.2.12.2.1-1 below.
Data Set Data Subset Data Key Data Sub Key
Subscription Data (see clause 5.2.3.3.1)Access and Mobility Subscription dataSUPIServing PLMN ID and optionally NID
SMF Selection Subscription dataSUPIServing PLMN ID and optionally NID
UE context in SMF dataSUPIPDU Session ID or DNN
SMS Management Subscription dataSUPIServing PLMN ID and optionally NID
SMS Subscription dataSUPIServing PLMN ID and optionally NID
Session Management Subscription dataSUPIS-NSSAI
DNN
Serving PLMN ID and optionally NID
Slice Selection Subscription dataSUPIServing PLMN ID and optionally NID
Group Data
(NOTE 5)		Internal Group Identifier or External Group Identifier-
Identifier translationGPSI
SUPIApplication Port ID, MTC Provider Information, AF Identifier
Intersystem continuity ContextSUPIDNN
LCS privacySUPI-
LCS mobile originationSUPI-
UE reachabilitySUPI-
Group Identifier TranslationInternal Group Identifier or External Group Identifier-
UE context in SMSF dataSUPI-
V2X Subscription dataSUPI-
A2X Subscription dataSUPI-
ProSe Subscription dataSUPI-
Ranging/SL Positioning subscription dataSUPI-
User consentSUPIPurpose
ECS Address Configuration Information (See Table 4.15.6.3d-1)SUPI, Internal group identifier or external group identifier or any UEDNN, S-NSSAI, (Serving) PLMN ID (NOTE 7)
MBS Subscription data (see clause 6.4.3 of TS 23.247)SUPI-
Ranging/Sidelink Positioning Subscription dataSUPI-
Ranging/Sidelink Positioning privacySUPI-
Operator Determined Barring data (see clause 2.3 of TS 23.015 and TS 29.505)SUPI-
Shared dataShared Data ID-
Application dataPacket Flow Descriptions (PFDs) (NOTE 11)Application Identifier-
AF traffic influence request information for traffic routing (See clause 5.6.7 and clause 6.3.7.2 of TS 23.501) AF transaction internal ID
For non-roaming and LBO:
S-NSSAI and DNN, accompanied with Internal Group Identifier(s) and/or Subscriber Category(s) or SUPI or "any UE" indication
For HR-SBO:
HPLMN S-NSSAI and DNN and either: HPLMN ID and IP address, or SUPI, or "any UE" indication and HPLMN ID.
(NOTE 4) (NOTE 6) (NOTE 12)
AF traffic influence request information for service function chaining (See clause 5.6.16 and clause 6.3.7.2 of TS 23.501) AF transaction internal ID
S-NSSAI and DNN and Internal Group Identifier or SUPI or "any UE" indication (NOTE 4)
Background Data Transfer (NOTE 3)Internal Group Identifier or SUPI
Service specific information (See clause 4.15.6.7) S-NSSAI and DNN or Internal Group Identifier or SUPI or "any UE" indication (NOTE 4) or "PLMN ID(s) of inbound roamer"
UE ID mapping information (See clause 4.3.5 of TS 23.586)GPSI or Application Layer ID
EAS Deployment Information (See clause 7.1 of TS 23.548)DNN and/or S-NSSAIApplication Identifier and/or Internal Group Identifier
ECS Address Configuration Information (See Table 4.15.6.3d-1)
(NOTE 13)		 DNN, S-NSSAI and "any UE" indication
AM influence information (See clause 4.15.6.9.3) AF transaction internal ID
S-NSSAI and DNN
and/or
Internal Group Identifier or SUPI or "any UE" indication or any inbound roaming UEs (NOTE 4, NOTE 8)
AF request for QoS information (See clause 4.15.6.14) AF transaction internal ID
S-NSSAI and DNN
and/or
Internal Group Identifier or SUPI or "any UE" indication (NOTE 4)
Policy DataUE context policy control data (See clause 6.2.1.3 of TS 23.503)SUPI
PDU Session policy control data (See clause 6.2.1.3 of TS 23.503)SUPIS-NSSAI
DNN
Policy Set Entry data (See clause 6.2.1.3 of TS 23.503)SUPI (for the UDR in HPLMN)
PLMN ID (for the UDR in VPLMN)
Remaining allowed Usage data (See clause 6.2.1.3 of TS 23.503)SUPIS-NSSAI
DNN
Sponsored data connectivity profiles (See clause 6.2.1.6 of TS 23.503)Sponsor Identity
Background Data Transfer data (See clause 6.2.1.6 of TS 23.503)Background Data Transfer Reference ID. (NOTE 2)
None. (NOTE 1)
Network Slice Specific Control Data (See clause 6.2.1.3 of TS 23.503)S-NSSAI
5G VN Group Specific Control Data (See clause 6.2.1.3 of TS 23.503)S-NSSAI and DNN and/or Internal Group Identifier
Operator Specific DataSUPI or GPSI
Planned Data Transfer with QoS requirements data (See clause 6.2.1.6 of TS 23.503)PDTQ Reference ID. (NOTE 10)
None. (NOTE 9)
Exposure Data (see clause 5.2.12.1)Access and Mobility InformationSUPI or GPSIPDU Session ID or UE IP address or DNN
Session Management informationSUPI or GPSI
DNAI mapping informationDNN and/or S-NSSAI
NOTE 1:
Retrieval of the stored Background Data Transfer data for all ASP identifiers in the UDR requires Data Subset but no Data Key or Data Subkey(s).
NOTE 2:
Update of a Background Data Transfer data in the UDR requires a Data key to refer to a Background Data Transfer data as input data.
NOTE 3:
The Background Data Transfer includes the Background Data Reference ID and the ASP Identifier that requests to apply the Background Data Reference ID to the UE(s). Furthermore, the Background Data Transfer includes the relevant information received from the AF as defined in clause 6.1.2.4 of TS 23.503.
NOTE 4:
When the Data Key targets "any UE", then the request to UDR applies on Application data that applies on all subscribers of the PLMN. For encoding, see TS 29.519.
NOTE 5:
Group Data includes 5G VN group configuration, DNN and S-NSSAI specific Group Parameters and any other data related to a group stored in the UDR.
NOTE 6:
If a list of Internal Group IDs is used, the AF traffic influence request information request applies to the UEs that belong to every one of these groups, i.e. a single UE needs to be a member of every group in the list of Internal Group IDs.
NOTE 7:
When the Data Key targets "PLMN ID", then the request to UDR applies on subscription data about subscribers roaming in this PLMN.
NOTE 8:
In LBO roaming scenarios, when the AF request targets "any inbound roaming UEs", the AM influence information applies to the roaming subscribers from a PLMN or from any PLMN.
NOTE 9:
Retrieval of the stored Planned Data Transfer with QoS requirements data for all ASP identifiers in the UDR requires Data Subset but no Data Key or Data Subkey(s).
NOTE 10:
Update of a Planned Data Transfer with QoS requirements data in the UDR requires a Data key to refer to a Planned Data Transfer with QoS requirements data as input data.
NOTE 11:
Each PFD (as defined in TS 23.503) may be complimented with a source NF type which indicates the type of NF that has generated the PFD (i.e. AF or NWDAF). Absence of a source NF type indicates that the AF is the source of the PFD.
NOTE 12:
Further information about HR-SBO case and how these keys are used, see clause 4.3.6.1.
NOTE 13:
The ECS Address Configuration Information as part of application data is used for HR roaming case as defined in clause 6.5.2.6 of TS 23.548.
 
The content of the UDR storage for (Data Set Id= Application Data, Data Subset Id = AF TrafficInfluence request information) is specified in clause 5.6.7 of TS 23.501, Table 5.6.7-1. This information is written by the NEF and read by the PCF(s). PCF(s) may also subscribe to changes onto this information.
Up
5.2.12.2.2  Nudr_DM_Query service operation  p. 828
Service operation name:
Nudr_DM_Query.
Description:
NF service consumer requests a set of data from UDR.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Requested data.
Outputs, Optional:
None.
5.2.12.2.3  Nudr_DM_Create service operation  p. 828
Service operation name:
Nudr_DM_Create.
Description:
NF service consumer intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.4  Nudr_DM_Delete service operation  p. 828
Service operation name:
Nudr_DM_Delete.
Description:
NF service consumer intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.5  Nudr_DM_Update service operation  p. 828
Service operation name:
Nudr_DM_Update.
Description:
NF service consumer intends to update stored data in the UDR.
Inputs, Required:
Data Set Identifier, Data Key(s), Data.
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.6  Nudr_DM_Subscribe service operation  p. 828
Service operation name:
Nudr_DM_Subscribe.
Description:
NF service consumer performs the subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required:
Data Set Identifier as defined in clause 5.2.12.2.1, Notification Target Address (+ Notification Correlation ID).
Inputs, Optional:
Target of Event Reporting as defined in clause 5.2.12.2.1, Data Subset Identifier(s) as defined in clause 5.2.12.2.1, Data Key(s), Subscription Correlation ID (in the case of modification of the event subscription).
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional:
None.
5.2.12.2.7  Nudr_DM_Unsubscribe service operation  p. 829
Service operation name:
Nudr_DM_Unsubscribe
Description:
NF service consumer performs the un-subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.8  Nudr_DM_Notify service operation  p. 829
Service operation name:
Nudr_DM_Notify.
Description:
UDR notifies NF service consumer(s) about modification of data, when data in the UDR is added, modified or deleted and an NF needs to be informed about this, due to a previous subscription to notifications procedure or due to a local configuration policy in the UDR.
Inputs, Required:
Notification Correlation Information, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, Updated Data.
Inputs, Optional:
Data Subset Identifier as defined in clause 5.2.12.2.1.
Outputs, Required:
Result.
Outputs, Optional:
None.

5.2.12.3  Nudr_GroupIDmap service |R16|  p. 829

5.2.12.3.1  General  p. 829
The Nudr_GroupIDmap service allows an NF consumer to retrieve a NF group ID corresponding to a subscriber identifier.
5.2.12.3.2  Nudr_GroupIDmap_query service operation  p. 829
Service operation name:
Nudr_GroupIDmap_query
Description:
Provides towards the invoking NF the NF Group ID corresponding to the supplied subscriber identifier.
Inputs, Required:
  • NF Type (e.g. HSS).
  • Subscriber Identifier.
  • Subscriber Identifier Type (at least one of {IMPI, IMPU, SUPI, GPSI}).
Inputs, Optional:
None.
Outputs, Required:
NF Group ID.
Outputs, Optional:
None.

5.2.13  BSF Services  p. 830

5.2.13.1  General  p. 830

The following Table shows the BSF Services and Service Operations:
NF service Service Operations Operation Semantics Example Consumer(s)
Nbsf_ManagementRegisterRequest/ResponsePCF
DeregisterRequest/ResponsePCF
DiscoveryRequest/ResponseNEF, AF, NWDAF, TSCTSF
UpdateRequest/ResponsePCF
SubscsribeSubscribe/NotifyNEF, PCF, AF, TSCTSF, 5G DDNMF
UnsubscribeSubscribe/NotifyNEF, PCF, AF, TSCTSF, 5G DDNMF
NotifySubscribe/NotifyNEF, PCF, AF, TSCTSF, 5G DDNMF
Up

5.2.13.2  Nbsf_Management service  p. 830

5.2.13.2.1  General  p. 830
The Nbsf provides the Nbsf_Management_Register, the Nbsf_Management_Deregister and the Nbsf_Management_Discovery services, the Nbsf_Management_Update, the Nbsf_Management_Subscribe, the Nbsf_Management_Unsubscribe and the Nbsf_Management_Notify operations.
5.2.13.2.2  Nbsf_Management_Register service operation  p. 830
Service operation name:
Nbsf_Management_Register
Description:
Registers the tuple (UE address(es), SUPI, GPSI, MBS session ID, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID, level of Binding) for a PDU Session or for a UE.
Inputs, Required:
[Required, if PCF registration is for a PDU Session], UE address(es), PCF address(es), DNN [Required, if PCF registration is for a PDU Session], S-NSSAI [Required, if PCF registration is for a PDU Session], MBS session ID as defined in TS 23.247 [Required, if PCF registration is for a MBS Session].
UE address can contain IP address/prefix or MAC address as defined in TS 23.501. It can optionally include Framed Route information. W-5GAN specific UE IP address information is specified in TS 23.316.
Framed Route information is defined in Table 5.2.3.3.1-1.
Inputs, Conditional:
SUPI [Required, if PCF registration is for a UE or required by the local policy in PCF if the registration is for a PDU session, otherwise it is optional].
Inputs, Optional:
GPSI, PCF instance ID and PCF Set ID, level of Binding (see clause 6.3.1.0 of TS 23.501).
Outputs, Required:
Result indication, Binding Identifier for a PDU Session, or for a UE, or for an MBS session.
Outputs, Optional:
None.
Up
5.2.13.2.3  Nbsf_Management_Deregister service operation  p. 831
Service operation name:
Nbsf_Management_Deregister
Description:
Removes the binding information for a PDU Session or for a UE.
Inputs, Required:
Binding Identifier for a PDU Session, or for a UE, or for an MBS session.
W-5GAN specific UE IP address information are specified in TS 23.316.
Inputs, Optional:
Outputs, Required:
Result indication.
Outputs, Optional:
None.
5.2.13.2.4  Nbsf_Management_Discovery service operation  p. 831
Service operation name:
Nbsf_Management discovery
Description:
Discovers the PCF and PCF set selected for a PDU Session identified by the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI), or discovers the PCF and PCF set selected for the UE identified by the tuple (SUPI, GPSI). This operation may also be used to determine the SUPI from the tuple (UE address, DNN, S-NSSAI).
Inputs, Required:
UE address (i.e. IP address or MAC address), [Required, for a PDU Session and for a UE], DNN [Conditional], S-NSSAI [Conditional], if the target PCF is for a PDU Session, MBS session ID as defined in TS 23.247, [Required, for an MBS Session].
SUPI and/or GPSI, if the target PCF is for a UE.
Inputs, Optional:
If the target PCF is for a PDU Session, SUPI, GPSI.
Outputs, Required:
PCF address(es), PCF instance ID [Conditional, if available] and PCF Set ID [Conditional, if available], level of Binding [Conditional, if available] (see clause 6.3.1.0 of TS 23.501).
Outputs, Optional:
SUPI, if available.
Up
5.2.13.2.5  Nbsf_Management_Update service operation |R16|  p. 831
Service operation name:
Nbsf_Management_Update
Description:
Replaces the list of UE address(es) for a PDU Session or replace PCF id or PCF address(es) for a PDU Session or for a UE.
Inputs, Required:
Binding Identifier for the PDU Session.
UE address can contain IP address/prefix or Ethernet address as defined in TS 23.501.
Inputs, Optional:
UE address(es), PCF id, PCF address(es).
Outputs, Required:
Result indication.
Outputs, Optional:
None.
Up
5.2.13.2.6  Nbsf_Management_Subscribe service operation |R17|  p. 832
Service Operation name:
Nbsf_Management_Subscribe
Description:
NEF, AF, TSCTSF or PCF for the UE can subscribe to be notified of newly registered or deregistered PCF for the PDU Session. In addition, NEF or AF can subscribe to be notified of newly registered or deregistered PCF for the UE.
Inputs, Required:
SUPI, DNN(s) [Required, if PCF subscription is for a PDU Session], S-NSSAI(s) [Required, if PCF subscription is for a PDU Session], callback URI.
Inputs, Optional:
GPSI, indication of registration/deregistration per (DNN, S-NSSAI).
Indication of registration/deregistration per (DNN, S-NSSAI) indicates to the BSF to report when the first SM policy association is established and when the last SM policy association is terminated to the same (DNN, S-NSSAI) combination.
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID.
Outputs, Conditional:
One or more instance per (DNN, S-NSSAI) of (UE address(es) [If available], PCF address(es) [If available], PCF instance ID [If available], PCF Set ID [If available], level of Binding [If available] (see clause 6.3.1.0 of TS 23.501)) or notification of registration/deregistration per (DNN, S-NSSAI).
Up
5.2.13.2.7  Nbsf_Management_Unsubscribe service operation |R17|  p. 832
Service Operation name:
Nbsf_Management_Unsubscribe
Description:
NEF, AF, TSCTSF or PCF for the UE can undo a previous subscription.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
result.
Outputs, Optional:
None.
5.2.13.2.8  Nbsf_Management_Notify service operation |R17|  p. 832
Service Operation name:
Nbsf_Management_Notify
Description:
BSF can notify NEF, AF, TSCTSF or PCF for the UE of newly registered PCF for the PDU Session or of deregistered PCF for the PDU Session.
Inputs, Required:
Notification Correlation Information, One or more instance per (DNN, S-NSSAI) of (UE address(es) [Required, if PCF notification is for a PDU Session], PCF address(es), PCF instance ID [Conditional, if available] and PCF Set ID [Conditional, if available]), level of Binding [Conditional, if available] (see clause 6.3.1.0 of TS 23.501) or notification of registration/deregistration per (DNN, S-NSSAI).
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.

5.2.14  UDSF Services  p. 833

5.2.14.1  General  p. 833

The following Table illustrates the UDSF Services.
NF service Service Operations Operation Semantics Example Consumer(s)
UnstructuredData ManagementQueryRequest/ResponseAny NF
CreateRequest/ResponseAny NF
DeleteRequest/ResponseAny NF
UpdateRequest/ResponseAny NF
SubscribeSubscribe/NotifyAny NF
UnsubscribeSubscribe/NotifyAny NF
NotifySubscribe/NotifyAny NF
Nudsf_TimerStartRequest/ResponseAny NF
StopRequest/ResponseAny NF
UpdateRequest/ResponseAny NF
SearchRequest/ResponseAny NF
NotifySubscribe/NotifyAny NF
Up

5.2.14.2  Nudsf_UnstructuredDataManagement service  p. 833

5.2.14.2.1  General  p. 833
5.2.14.2.2  Nudsf_UnstructuredDataManagement_Query service operation  p. 833
Service operation name:
Nudsf_UnstructuredDataManagement_Query.
Description:
NF service consumer intends to query data from UDSF.
Inputs, Required:
Data Identifier.
Data Identifier uniquely identifies the data to be retrieved from the UDSF
Inputs, Optional:
None.
Outputs, Required:
Requested data.
Outputs, Optional:
None.
5.2.14.2.3  Nudsf_UnstructuredDataManagement_Create service operation  p. 833
Service operation name:
Nudsf_UnstructuredDataManagement_Create.
Description:
NF service consumer intends to insert a new user data record into the UDSF, e.g. AMF stores the context for registered UE(s) in the UDSF.
Inputs, Required:
Data Identifier, Data.
Data Identifier uniquely identifies the data, which is created in the UDSF.
Inputs, Optional:
Validity time, Notification Endpoint.
Validity time tells for how long the created data is valid. When validity time has expired, NF service consumer is notified and data is removed.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.4  Nudsf_UnstructuredDataManagement_Delete service operation  p. 834
Service operation name:
Nudsf_UnstructuredDataManagement_Delete.
Description:
NF service consumer intends to delete user data stored in the UDSF, e.g. when AMF deletes the context for unregistered UE(s) in the UDSF.
Inputs, Required:
Data Identifier.
Inputs, Optional:
None.
Data Identifier uniquely identifies the data to be deleted within the UDSF.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.5  Nudsf_UnstructuredDataManagement_Update service operation  p. 834
Service operation name:
Nudsf_UnstructuredDataManagement_Update.
Description:
NF service consumer intends to update stored data in the UDSF.
Inputs, Required:
Data Identifier, Data.
Data Identifier uniquely identifies the data, which is updated in the UDSF.
Inputs, Optional:
Validity time.
Validity time tells for how long the created data is valid. When validity time has expired, NF service consumer is notified and data is removed.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.6  Nudsf_UnstructuredDataManagement_Subscribe |R17|  p. 834
Service operation name:
Nudsf_UnstructuredDataManagement_Subscribe
Description:
NF service consumer subscribes to notifications of data change in the UDSF.
Inputs, Required:
Identity of data to be monitored, Notification endpoint.
Inputs, Optional:
None.
Outputs, Required:
Subscription ID.
Outputs, Optional:
None.
5.2.14.2.7  Nudsf_UnstructuredDataManagement_Unsubscribe |R17|  p. 834
Service operation name:
Nudsf_UnstructuredDataManagement_Unsubscribe
Description:
NF service consumer un-subscribes to notifications of data change in the UDSF.
Inputs, Required:
Subscription ID.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.8  Nudsf_UnstructuredDataManagement_Notify |R17|  p. 835
Service operation name:
Nudsf_UnstructuredDataManagement_Notify
Description:
NF is notifications of data change or if validity time for created data has expired in the UDSF.
Inputs, Required:
Data Identifier, Data.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.

5.2.14.3  Nudsf_Timer service |R17|  p. 835

5.2.14.3.1  General  p. 835
Any NF may use the UDSF to run timer(s), search for timer(s) and get notifications on expiry.
5.2.14.3.2  Nudsf_Timer_Start service operation  p. 835
Service operation name:
Nudsf_Timer_Start
Description:
NF service consumer starts a timer in the UDSF.
Inputs, Required:
Timer ID, Time of expiry.
Inputs, Optional:
Notification Endpoint, Associated data.
Associated data is data that can be used by the consumer to identify for what purpose the timer is for, e.g. a subscription that has timed out.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.3.3  Nudsf_Timer_Update service operation  p. 835
Service operation name:
Nudsf_Timer_Update
Description:
NF service consumer updates a timer in the UDSF.
Inputs, Required:
Timer Identity.
Inputs, Optional:
Notification Endpoint, Associated data, Time of expiry.
Associated data is data that can be used by the consumer to identify for what purpose the timer is for, e.g. a subscription that has timed out.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.3.4  Nudsf_Timer_Notify service operation  p. 835
Service operation name:
Nudsf_Timer_Notify
Description:
The UDSF notifies the NF service consumer about a timer expiry.
Inputs, Required:
Timer Identity.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.3.5  Nudsf_Timer_Stop service operation  p. 836
Service operation name:
Nudsf_Timer_Stop
Description:
NF service consumer intends to stop timer(s) in the UDSF.
Inputs, Required:
Timer Identity/Identities.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.3.6  Nudsf_Timer_Search service operation  p. 836
Service operation name:
Nudsf_Timer_Search
Description:
NF service consumer intends to search and retrieve timers matching a filter in the UDSF.
Inputs, Required:
Search filter (see TS 29.598).
Inputs, Optional:
Filter.
Outputs, Required:
Result.
Outputs, Optional:
Timer Identity/Identities.

5.2.15  LMF Services  p. 836

LMF services are defined in clause 8.3 of TS 23.273.

5.2.16  NSSF Services  p. 836

5.2.16.1  General  p. 836

The following Table illustrates the NSSF Services.
NF service Service Operations Operation Semantics Example Consumer(s)
Nnssf_NSSelectionGetRequest/ResponseAMF, NSSF in a different PLMN, SMF, NWDAF
Nnssf_NSSAIAvailabilityUpdateRequest/ResponseAMF
SubscribeSubscribe/NotifyAMF, NSSF
UnsubscribeAMF, NSSF
NotifyAMF, NSSF
DeleteRequest/ResponseAMF
Up

5.2.16.2  Nnssf_NSSelection service  p. 837

5.2.16.2.1  Nnssf_NSSelection_Get service operation  p. 837
Service operation name:
Nnssf_NSSelection_Get
Description:
This service operation enables Network Slice selection in both the Serving PLMN and HPLMN. It also enables the NSSF to provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN. It allows also to provide the NSAG information which is applicable (clause 5.15.14 of TS 23.501).
It may be invoked during Registration procedure, during inter-PLMN mobility procedure, during PDU Session Establishment procedure or during UE Configuration Update procedure. When invoked during Registration procedure it may possibly trigger AMF re-allocation. When invoked during PDU Session Establishment procedure it may be invoked in the VPLMN or in the HPLMN; if invoked in the VPLMN it returns the hNRF selected by the hNSSF and if applicable, the value of the HPLMN NSI ID. When invoked during UE Configuration Update procedure or inter-PLMN mobility procedure it may be invoked in the Serving PLMN.
Inputs, Required:
None.
Inputs, Conditional Required:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are required:
  • Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked during Registration procedure to get the slice mapping information in the case of Indirect Network Sharing as specified in clause 5.18.5 of TS 23.501, then the following inputs are required:
  • HPLMN S-NSSAIs, PLMN ID of the SUPI.
If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following inputs are required:
  • S-NSSAIs for the HPLMN associated with established PDN connection, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked by target AMF during inter-PLMN mobility procedure, the following inputs are required:
  • S-NSSAIs for the HPLMN, PLMN ID of the SUPI, TAI.
If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following inputs are required:
  • Subscribed S-NSSAIs for the UE, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked during PDU Session Establishment procedure in the Serving PLMN then the following inputs are required:
  • S-NSSAI, non-roaming/LBO roaming/HR roaming indication, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
Inputs, Optional:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are provided if available:
  • Requested NSSAI, Mapping Of Requested NSSAI, Default Configured NSSAI Indication, NSSRG Information, UE support of subscription-based restrictions to simultaneous registration of network slice feature Indication, UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based restrictions to simultaneous registration of network slices, Allowed NSSAI for current Access Type, Allowed NSSAI for the other Access Type and the corresponding Mapping Of Allowed NSSAIs for current Access Type and other Access Type, Rejected S-NSSAI(s) for RA, UE support of NSAG Information.
If this service operation is invoked during PDU Session Establishment procedure, then the following input is optional:
  • HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI of the Serving PLMN.
Outputs, Conditional Required:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then one or more of the following outputs are required:
  • Allowed NSSAI, Configured NSSAI; Target AMF Set or, based on configuration, the list of candidate AMF(s).
If this service operation is invoked during Registration procedure to get the slice mapping information in the case of Indirect Network Sharing as specified in clause 5.18.5 of TS 23.501, then the following outputs are required:
  • HPLMN S-NSSAIs, Mapping of HPLMN S-NSSAIs in the hosting operator's network.
If this service operation is invoked during inter-PLMN mobility procedure, then one or more of the following outputs are required:
  • Allowed NSSAI.
If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following output is required:
  • S-NSSAIs for the HPLMN associated with established PDN connection, Mapping of S-NSSAIs associated with established PDN connection in the Serving PLMN.
If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a SMF+PGW-C, the following outputs are required:
  • Subscribed S-NSSAIs for the UE, Mapping of S-NSSAIs associated with the subscribed S-NSSAIs for the UE in the Serving PLMN.
If this service operation is invoked during PDU Session Establishment procedure, then the following outputs are required:
  • The NRF to be used to select NFs/services within the selected Network Slice instance.
Outputs, conditional Optional:
If this service operation is invoked during UE Registration procedure or UE Configuration Update procedure, then one or more of the following outputs are optional:
  • Mapping Of Allowed NSSAI, Mapping Of Configured NSSAI, NSI ID(s) associated with the Network Slice instances of the Allowed NSSAI, NRF(s) to be used to select NFs/services within the selected Network Slice instance(s) and NRF to be used to determine the list of candidate AMF(s) from the AMF Set, rejected S-NSSAI with cause of rejection, Target NSSAI, the NSAG information (defined in clause 5.15.14 of TS 23.501).
If this service operation is invoked during inter-PLMN mobility procedure, then the following output is optional:
  • Mapping Of Allowed NSSAI.
If this service operation is invoked during PDU Session Establishment procedure, then the following output is optional:
  • NSI ID associated with the S-NSSAI provided in the input.
Up

5.2.16.3  Nnssf_NSSAIAvailability service  p. 839

5.2.16.3.1  General  p. 839
Service description:
This service enables to update the AMFs and the NSSF on the availability of S-NSSAIs and NSAGs on a per TA basis. This service also enables updates for Network Slice Replacement and Network Slice Instance Replacement to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) when the NSSF determines that an S-NSSAI has to be replaced with an Alternative S-NSSAI or a Network Slice instance is replaced as described in clause 5.15.19 of TS 23.501.
When this service is used by the NSSF for Network Slice Replacement, i.e. to provide to the NF Service Consumer an Alternative S-NSSAI to the S-NSSAI to be replaced, the following cases are possible:
  • in non-roaming and in roaming case, NSSF in the Serving PLMN provides to the AMF the Alternative S-NSSAI of the Serving PLMN; or
  • in roaming case, the NSSF in the HPLMN provides to the NSSF in the VPLMN the Alternative HPLMN S-NSSAI; and the NSSF in the VPLMN provides to the AMF the Alternative HPLMN S-NSSAI.
Following NSSF event subscriptions are supported:
Up
5.2.16.3.2  Nnssf_NSSAIAvailability_Update service operation  p. 839
Service operation name:
Nnssf_NSSAIAvailability_Update
Description:
This service operation enables the AMF to update the NSSF with the S-NSSAIs the AMF supports per TA and get the availability of the S-NSSAIs and optionally NSI IDs per TA for the S-NSSAIs the AMF supports.
Inputs, Required:
Supported S-NSSAIs per TAI.
The supported S-NSSAIs per TAI is a list of TAIs and for each TAI the S-NSSAIs supported by the AMF.
Inputs, Optional:
Supported NSAGs per TAI.
The supported NSAGs per TAI is a list of TAIs and for each TAI the NSAGs and for each NSAG the associated S-NSSAIs supported by the AMF.
Outputs, Required:
A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI.
Outputs, Conditional Required:
A list of TAIs and for each TAI, the NSAGs authorized by the NSSF for the TAI.
If the NSSF has NSAG information, it should provide the authorized NSAGs per TAI. This is a list of TAIs and for each TAI the NSAGs and for each of the NSAGs the associated S-NSSAIs.
Up
5.2.16.3.3  Nnssf_NSSAIAvailability_Notify service operation  p. 839
Service operation name:
Nnssf_NSSAIAvailability_Notify
Description:
This service operation enables the NSSF to update a NF Service Consumer (e.g. AMF) with any S-NSSAIs restricted per validity time, or per TA and if needed subsequently lift any restriction per TA. This service operation also enables the NSSF to notify to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) that an S-NSSAI has to be replaced by an Alternative S-NSSAI or a Network Slice instance should be replaced.
Inputs, Required:
Subscription Correlation ID.
Inputs, Conditional Required:
If this service operation is invoked by subscription for changes in the status of the NSSAI availability information, then the following inputs are required:
  • a list of TAIs and the S-NSSAIs for which the status is changed (restricted/unrestricted) per each TAI.
If this service operation is invoked by subscription for event notification for Network Slice Replacement, then the following inputs are required:
  • For replacement of an S-NSSAI of the serving PLMN: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAI to be replaced.
  • For replacement of an HPLMN S-NSSAI: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAIs of the HPLMN, PLMN ID.
  • For termination of the Network Slice replacement:
    1. indication to stop the Network Slice replacement for new UEs; or
    2. indication to terminate the Network Slice replacement and move back the UEs and PDU Sessions from the Alternative S-NSSAI to the S-NSSAI.
If this service operation is invoked by subscription for event notification for Network Slice Instance Replacement, then the following inputs are required:
  • The S-NSSAI(s) and NSI ID(s) for which the status is changed (e.g. congested or no longer available).
If this service operation is invoked by subscription for event notification for update of slice validity time, then the following inputs are required:
  • The S-NSSAI(s) and associated validity time for each S-NSSAI.
Inputs, Optional:
  • NSI IDs in the S-NSSAI for which the status is changed (restricted/unrestricted) per each TAI.
If this service operation is invoked by subscription for event notification for Network Slice Replacement or Network Slice Instance Replacement, then the following inputs are optionally provided with the Alternative S-NSSAI:
  • For replacement due to congestion: congestion mitigation information which includes information that the Network Slice replacement applies 1) for a percentage and/or 2) for new UEs registering to the Network Slice.
Outputs, Required:
None.
Outputs, Optional:
None.
Up
5.2.16.3.4  Nnssf_NSSAIAvailability_Subscribe service operation  p. 840
Service operation name:
Nnssf_NSSAIAvailability_Subscribe
Description:
This service operation enables a NF Service Consumer (e.g. AMF) to subscribe to a notification of any changes in status of the NSSAI availability information (e.g. S-NSSAI validity time, S-NSSAIs and optionally NSI IDs available per TA and the restricted S-NSSAI(s) and optionally NSI IDs per PLMN in that TA in the serving PLMN of the UE) upon this is updated by another AMF. This service also enables the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) to subscribe to a notification of Network Slice Replacement and Network Slice Instance Replacement.
Inputs, Required:
Callback URI of the NF Service Consumer:
Inputs, Conditional Required:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following inputs are required:
  • list of TAIs supported by the NF service consumer, event to be subscribed.
If this service operation is invoked to subscribe for changes in status of the NSSAI validity time information, then the following inputs are required:
  • The S-NSSAIs, event to be subscribed.
If this service operation is invoked to subscribe to a notification for Network Slice Replacement, then the following inputs are required:
  • for the S-NSSAI of the serving PLMN: set of S-NSSAIs served by the NF Service Consumer that may be replaced, NF type of the NF Service Consumer (e.g. AMF), Requester ID, event to be subscribed.
  • for HPLMN S-NSSAI: S-NSSAIs for the HPLMN, NF type of the NF Service Consumer (e.g. AMF or NSSF), Requester ID and PLMN ID, event to be subscribed.
If this service operation is invoked to subscribe to a notification when the Network Slice instance is congested or no longer available, then the following inputs are required:
  • The S-NSSAIs, NSI IDs, event to be subscribed.
Inputs, Optional:
Expiry time.
Outputs, Required:
Subscription Correlation ID.
Outputs, Conditional Required:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are required:
  • Expiry time (if present in the request, may be included in the response based on operator's policy and taking into account the expiry time present in the request (i.e. should be less than or equal to that value); if not present in the request, may be included in the response based on operator's policy. Whatever the case, if not included in the response, this means that the subscription is valid without an expiry time).
Outputs, Optional:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are optional:
  • A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI and a list of S-NSSAIs and optionally NSI IDs restricted per PLMN for the TAI. The NSSS indicates to the AMF that the S-NSSAI(s) are not available in the corresponding TAIs.
Up
5.2.16.3.5  Nnssf_NSSAIAvailability_Unsubscribe service operation  p. 841
Service operation name:
Nnssf_NSSAIAvailability_Unsubscribe
Description:
This service operation enables a NF Service Consumer (e.g. AMF) to unsubscribe to a notification of any previously subscribed changes to the NSSAI availability information. This service operation also enables the NF Service Consumer (e.g. AMF, NSSF) to unsubscribe to a notification for Network Slice Replacement or for Network Slice Instance Replacement.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.16.3.6  Nnssf_NSSAIAvailability_Delete service operation  p. 842
Service operation name:
Nnssf_NSSAIAvailability_Delete
Description:
This service operation enables a NF service consumer (e.g. AMF) to delete the NSSAI availability information stored for the NF service consumer in the NSSF.
Inputs, Required:
NF ID.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.

5.2.16.4  Void

5.2.17  CHF Spending Limit Control Service  p. 842

5.2.17.1  General  p. 842

The following Table illustrates the CHF Services defined in this specification. The other services of CHF are defined in clause 6.2 of TS 32.290.
NF service Service Operations Operation Semantics Example Consumer(s)
Nchf_SpendingLimitControlSubscribeSubscribe/NotifyPCF
UnsubscribePCF
NotifyPCF
Up

5.2.17.2  Nchf_SpendingLimitControl service  p. 842

5.2.17.2.1  General  p. 842
Service description: This service enables transfer of policy counter status information relating to subscriber spending limits from CHF to the NF consumer.
5.2.17.2.2  Nchf_SpendingLimitControl Subscribe service operation  p. 842
Service operation name:
Nchf_SpendingLimitControl_Subscribe
Description:
Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval of the status of the policy counters for which subscription is accepted by CHF.
Inputs, Required:
SUPI (for the Initial Spending Limit request), SubscriptionCorrelationId (for the Intermediate Spending Limit report), Event Id "policy counter status change", Event Filter Information "List of policy counter identifier (s)".
Inputs, Optional:
Notification Correlation Target (required for the Initial Spending Limit request), Event Filter Information "List of policy counter identifier (s)", Event Reporting Information (continuous reporting).
Outputs, Required:
Status of the requested subscribed policy counters to the subscriber in the Event Information.
Outputs, Optional:
Pending policy counter statuses and their activation times, for all policy counter(s) available for this subscriber. If list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses and their activation times, per required policy counter identifier in the Event Information, SubscriptionCorrelationId.
Up
5.2.17.2.3  Nchf_SpendingLimitControl Unsubscribe service operation  p. 843
Service operation name:
Nchf_SpendingLimitControl_Unsubscribe
Description:
Cancel the subscription to status changes for all the policy counters available at the CHF.
Inputs, Required:
SubscriptionCorrelationId.
Inputs, Optional:
None.
Outputs, Required:
Success or Failure.
Outputs, Optional:
None.
5.2.17.2.4  Nchf_SpendingLimitControl Notify service operation  p. 843
Service operation name:
Nchf_SpendingLimitControl_Notify
Description:
Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber.
Inputs, Required:
Notification Target Address, SUPI.
Inputs, Optional:
policy counter status as Event Information, Pending policy counter statuses and their activation times as Event Information. Subscriber removal from the CHF system as Event Information.
Outputs, Required:
Success or Failure.
Outputs, Optional:
None.
Up

Up   Top   ToC