hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.5.2 Nnef_IPTVconfiguration_Create operation
|
Service operation name: Nnef_IPTVconfiguration_Create
Description: Authorize the request and forward the request for IPTV configuration information.
Inputs (required): AF Transaction Id, GPSI or External-Group-ID, application identifier, Multicast Access Control List.
The AF Transaction Id refers to the request.
Inputs (optional): DNN, S-NSSAI.
Outputs (required): Operation execution result indication.
Outputs (optional): None.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.5.3 Nnef_IPTVconfiguration_Update operation
|
Service operation name: Nnef_IPTVconfiguration_Update
Description: Authorize the request and forward the request to update IPTV configuration information.
Inputs (required): AF Transaction Id.
The AF Transaction Id identifies the NF Service Consumer request to be updated.
Inputs (optional): Multicast Access Control List.
Outputs (required): Operation execution result indication.
Outputs (optional): None.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.5.4 Nnef_IPTVconfiguration_Delete operation
|
Service operation name: Nnef_IPTVconfiguration_Delete
Description: Authorize the request and forward the request to delete(s) request for IPTV configuration information.
Inputs (required): AF Transaction Id.
The AF Transaction Id identifies the NF Service Consumer request for IPTV configuration to be deleted.
Inputs (optional): None.
Outputs (required): Operation execution result indication.
Outputs (optional): None.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.6 UDR Services
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.6.1 Nudr_DataManagement (DM) Service
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
8.6.1.1 General
|
The UDM makes use of the Nudr_DM service to perform the mapping of the SUPI/IMSI associated with the Line ID or HFC-Identifier included in the SUCI.
In addition to the Subscription data types and corresponding Subscription Data keys used in the Nudr_DM_Service, as defined in TS 23.502 [3], the Subscription data types and corresponding Subscription data keys defined for the Nudr_DM Service in Table 8.6.1.1-1 and Table 8.6.1.1-2 are applicable for FN-RGs connected to 5GC.
Table 8.6.1.1-1: UE Subscription data types
Subscription data type
Field
Description
Subscription identifier translation
Other Identifier Of The Subscription (Global Line ID or Global Cable ID)
Global Line ID or Global Cable ID included in SUCI provided by the W-AGF to the 5GC for FN-RG support and used as pseudonym of the SUPI.
SUPI
Corresponding SUPI
Table 8.6.1.1-2: Data keys
Data Set
Data Subset
Data Key
Data Sub Key
Subscription Data
Subscription identifier translation
Global Line ID or Global Cable ID
-
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9 Policy and Charging Control Framework and Configuration by ACS
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.0 General
|
This clause specifies the delta related to Policy and charging control framework defined in TS 23.503 [4] and the configuration of the 5G-RG by the ACS.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.1 Session management related policy control
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.1.0 General
|
This clause specifies the delta related to UE policy distribution defined in TS 23.503 [4] clause 6.1.3 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.1.1 Session binding
|
The session binding mechanism defined in TS 23.503 [4] clause 6.1.3.2.2 applies. In addition, the PDU session parameters considered for session binding are:
- For IPv6 PDU session type, one or multiple UE IPv6 address or one or multiple IPv6 prefixes /64 or shorter prefixes.
- For IPv4v6 PDU session type, one UE IPv4 address and one or multiple IPv6 prefixes /64 or shorter prefixes.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.1.2 Policy Control Request Triggers relevant for SMF and wireline access type
|
The Policy Control Request Triggers relevant for SMF and wireline access define the conditions when the SMF shall interact again with PCF after a PDU Session established via W-5GAN. PCR triggers defined in Table 6.1.3.5 in TS 23.503 [4] are supported for W-5GAN scenario with the following not supporting ones:
- PLMN change.
- Location change (serving area).
- Location change (serving CN node in 5GS).
- Location change (serving CN node in EPC).
- Change of UE presence in Presence Reporting Area.
- 3GPP PS Data Off status change.
- GFBR of the QoS Flow can no longer (or can again) be guaranteed.
- UE resumed from suspend data.
- 5GS Bridge/Router information available.
- QoS Monitoring.
- QoS constraints change.
- Satellite backhaul category change.
- NWDAF info change.
- Notification on BAT offset.
- UE Policy Container received or delivery failure for UE Policy Container delivery via EPS.
- UE reporting Connection Capabilities from associated URSP rule.
- Change of HR-SBO support indication.
- QoS Monitoring can no longer (or can again) be performed.
Additionally, the new triggers defined in clause 9.7 for IPTV service are also applied for a 5G-RG connected via W-5GAN scenario.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2 Network Functions and entities
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2.1 General
|
This clause specifies the delta related to Network Function and entities defined in TS 23.503 [4] clause 6.2 for 5G-RG and FN-RG.
The functional description of the NEF, NWDAF, UDR and CHF applies as described in TS 23.503 [4].
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2.2 Policy Control Function (PCF)
|
The PCF provides session management policy control for single access PDU sessions over non 3GPP wireline and multiaccess PDU sessions over both 3GPP and non 3GPP wireline access.
The session management related functionality defined in clause 6.2.1 of TS 23.503 [4] applies for 5G-RG and FN-RG, with the following modifications for W-5GAN:
- Determination of Maximum Packet Loss Rate for UL/DL does not apply.
- QoS Notification Control does not apply.
NOTE: No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this Release.
The non-session management related functionality defined in clause 6.2.2 of TS 23.503 [4] applies for 5G-RG and FN-RG, with the following modifications for W-5GAN:
- the UE-AMBR control by the Visited Network does not apply.
- the Service Area Restrictions for a FN-BRG does not apply.
- the 5G-RG and FN-RG replaces the UE.
- the PCF provides Access and mobility related policy control as described in clause 9.5.1.
- the PCF provides UE access selection and PDU session selection
- the PCF provides the UE access selection and PDU Session selection related policy control as defined in clause 9.5.2.
The policy control subscription data defined in TS 23.503 [4] applies for 5G-RG and FN-RG connected via W-5GAN access, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release.
The policy control subscription data defined in TS 23.503 [4] applies for a 5G-RG and FN-RG connected via W-5GAN, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release.
The V-PCF and H-PCF functionality does not apply for session and non-session policy control for 5G-RG and FN-RG users in this Release.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2.3 Session Management Function (SMF)
|
The SMF enforces policy decisions related to service data flow detection, authorized QoS, charging, gating, traffic usage reporting, packet routing and forwarding and traffic steering for single access PDU session over W-5GAN and multiaccess PDU sessions over W-5GAN and 3GPP as defined in clause 6.2.2 of TS 23.503 [4] with the following modifications for W-5GAN:
- Reporting RAN/NAS Release Cause over wireline is not supported.
- The Maximum Packet Loss Rate for UL and DL is not forwarded to the wireline non-3GPP access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2.4 Application Function (AF)
|
The AF requests for policy control functionality described in clause 6.2.3 of TS 23.503 [4] applies with the following clarification for W-5GAN:
- Indication that the QoS targets can no longer (or can again) be fulfilled is not supported.
NOTE: No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this release.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.2.5 Access and Mobility Management Function (AMF)
|
The policy control related functionality defined in TS 23.503 [4] applies, with the clarification that the UE-AMBR control by the visited network is only applicable for a 5G-RG registered over 3GPP access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.3 Policy and charging control rule
|
Policy and charging control rule for 5G-RG PDU Session is described in TS 23.503 [4] clause 6.3 with the clarification and difference in this clause.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.3.1 PCC rule information to support IPTV service
|
- PCF shall take Multicast Access Control list described in clause 7.7.1.1.4 as input to policy decision in the case of PDU Session used for IPTV service. PCC rules sent to SMF may indicate allowed IP Multicast Addressing information as defined in Table 9.3.1-1.
- The "Gate status" is not applicable to IGMP transmitted over PDU Session used for IPTV service.
Comparing to Table 6.3.1 in TS 23.503 [4], additional PCC rule information for PDU Session used for IPTV service is described in Table 9.3.1-1.
Table 9.3.1-1: The additional PCC rule information for PDU Session used for IPTV service
Information name
Description
Category
PCF permitted to modify for a dynamic PCC rule in the SMF
Differences compared with table 6.3. in TS 23.203 [31]
IPTV
This part defines the additional PCC rule information for PDU Session used for IPTV service.
IP Multicast traffic control information
indicates whether the service data flow, corresponding to the service data flow template, may be allowed or not allowed (NOTE 1).
Optional
Yes
Added
NOTE 1: The corresponding IP Multicast Addressing information in provided in the SDF template. The SDF template may refer to "any" IP Multicast address (for example allowing the user to access to receive any IPTV channel).
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.4 PDU Session related policy information
|
This clause specifies the delta related to PDU session related policy information defined in TS 23.503 [4] clause 6.4 for 5G-RG and FN-RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5 Non-session management related policy information
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5.1 Access and mobility related policy information
|
This clause specifies the delta related to Access and Mobility related policy information defined in TS 23.503 [4] clause 6.1.2.1 for 5G-RG and FN-RG.
The access and mobility policy control encompass the management of service area restrictions for a 5G-BRG or a 5G-CRG connecting to 5GC via W-5GAN or simultaneously via NG-RAN and W-5GAN as well as AUN3 devices behind a 5G-RG.
The management of service area restrictions enables the PCF of the serving PLMN or SNPN to modify the service area restrictions based on operator defined policies at any time, either by expanding a list of allowed GLIs or HFC Node IDs or by reducing the list of non-allowed GLIs or HFC Node IDs. Operator defined policies in the PCF may depend on input data such as time of day, or UE context information provided by other NFs, etc.
The AMF reports the subscribed service area restrictions in NG-RAN received from UDM during 5G-RG Registration in NG-RAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to NG-RAN when the policy control request triggers listed in clause 6.1.2.5 in TS 23.503 [4], are met.
The AMF reports the subscribed service area restrictions in W-5GAN received from UDM during 5G-RG or AUN3 device Registration in W-5GAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to W-5GAN when the policy control request triggers listed in clause 9.5.3 are met.
The AMF receives the modified service area restrictions from the PCF and then use them as described in clause 4.3.3.3.
No mobility events, such a change of UE location or change of AMF applies when provisioning the service area restrictions for a 5G-BRG or a 5G-CRG or AUN3 device when connected via W-5GAN.
The PCF may provide the service area restrictions applicable to a 5G-RG connected to 5GC via W-5GAN or via NG-RAN or simultaneously connected to 5GC via W-5GAN and NG-RAN to AMF. The PCF may provide the service area restrictions applicable to a FN-CRG to the AMF. The PCF may provide the service area restrictions applicable to an AUN3 device behind 5G-RG connected to 5GC via W-5GAN to the AMF.
The Service Area Restrictions provided to AMF for a 5G-RG connected via NG-RAN is according to the information listed in listed in TS 23.503 [4] clause 6.5.
The Service Area Restrictions provided to AMF for a 5G-RG or AUN3 device connected via W-5GAN is according to the information listed in Table 9.5-1.
For a 5G-RG simultaneously connected to 5GC via W-5GAN and NG-RAN the PCF provides Service Area Restrictions for both W-5GAN and NG-RAN.
The Service Area Restrictions provided to AMF for a FN-CRG connected via W-5GAN is according to the information listed in Table 9.5-1.
Table 9.5-1: Access and mobility related policy control information for 5G-RG and FN-CRG accessing via W-5GAN
Information name
Description
Category
PCF permitted to modify in a AM context in the AMF
Scope
Service Area Restrictions for a 5G-BRG or AUN3 device behind 5G-BRG
This part defines the service area restrictions applicable for a 5G-BRG or AUN3 device behind 5G-BRG.
List of allowed GLIs
List of allowed GLIs
(NOTE 2).
Conditional
(NOTE 1)
Yes
AM context
List of non-allowed GLIs
List of non-allowed GLIs.
Conditional
(NOTE 1)
Yes
AM context
Service Area Restrictions for a 5G-CRG or for a FN-CRG
This part defines the service area restrictions applicable for a 5G-CRG or for a FN-CRG
List of allowed HFC Node IDs
List of allowed HFC Node IDs
(NOTE 2)
Conditional
(NOTE 1)
Yes
AM context
List of non-allowed HFC Node IDs
List of non-allowed HFC Node IDs (NOTE 2).
Conditional
(NOTE 1)
Yes
AM context
Service Area Restrictions for an AUN3 device behind 5G-CRG
This part defines the service area restrictions applicable for an AUN3 device behind 5G-CRG
Conditional
(NOTE 1)
Yes
AM context
List of allowed combinations of GCI and HFC Node IDs
List of allowed combinations of GCI and HFC Node ID
(NOTE 3)
Conditional
(NOTE 1)
Yes
AM context
NOTE 1: If service area restrictions is enable.
NOTE 2: Either the list of allowed (GLIs or HFC Node IDs) or the list of non-allowed (GLIs or HFC Node IDs) are provided by the PCF.
NOTE 3: Either the list of allowed (GCI and HFC Node ID combinations) or the list of non-allowed (GCI or HFC Node ID combinations) are provided by the PCF.
The list of allowed GLIs or the list of allowed HFC Node IDs indicates the locations where the 5G-RG is allowed to be registered, see clause 4.3.3.3 for the description on how AMF uses this information.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5.2 UE access selection and PDU Session selection related policy information
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5.2.1 5G-RG
|
This clause specifies the delta related to UE policy distribution defined in TS 23.503 [4] clause 6.1.2.2 and related to URSP defined in TS 23.503 [4] clause 6.6. for 5G-RG.
Only URSP policies are applicable for a 5G -RG.
NOTE: For example, ANDSP policies, ProSe Layer-3 UE-to-Network Relay Offload Policy are not applicable to 5G-RG,
If the PCF provides a URSP policy to the 5G-RG, the PCF should only provide the following URSP policy information:
- Rule Precedence.
- Traffic descriptor/Application descriptors, IP descriptors, Domain descriptors, Non-IP descriptors, DNN, Connection Capabilities.
- Route Selection Descriptor Precedence.
- Route selection components/ SSC Mode Selection, Network Slice Selection, DNN Selection, PDU Session Type Selection.
- Route Selection Validation Criteria/ Time Window.
The 5G-RG shall ignore any of the parameters and policies not listed above, if received from the 5GC.
The 5G-RG shall use the URSP policy as specified in TS 23.503 [4], for example for the association of application and PDU session, slices, etc.
The URSP indicates for the application of Auto-Configuration Server (ACS) which PDU session type, NSSAI and/or DNN is to be used. The 5G-RG establishes the connectivity to the management entity (e.g. ACS) via user plane connection on a PDU session according to the URSP.
UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 [4] are applicable as follows:
- Roaming is not applicable to W-5GAN access in this release of specification.
- USRP rule enforcement reporting is not defined for 5G-RG.
In the case of an Authenticable Non-3GPP (AUN3) device behind a 5G-RG only URSP policies are applicable. Each AUN3 device is managed in 5G-RG as a separate device with its own NAS and states, therefore from point of view of 5GC, the AUN3 device is seen as a single device and the URSP received in the NAS dedicated to an AUN3 device shall apply to this AUN3 device only the 5G-RG shall apply URSP received within NAS for AUN3 device acting on behalf of AUN3 device. Therefore to support the case when AUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF for the SUPI associated with the AUN3 device.
UE Route Selection Policy information targeting an AUN3 device (i.e. sent to a 5G-RG in the NAS connection corresponding to an AUN3 device) follows the structure defined in clause 6.2.2 of TS 23.503 [4] with the following difference:
- As an AUN3 can have only one PDU Session, its URSP shall contain a match all TD.
USRP rule enforcement reporting is not defined for AUN3 devices.
In order to support the case when NAUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF on 5G-RG.
URSP rules for NAUN3 devices connected to 5G-RG follow the structure defined in clause 6.6.2 of TS 23.503 [4] and may contain any combination of the following traffic descriptors:
- IP Descriptors: For IP traffic from NAUN3 devices connected to 5G-RG, IP descriptors are matched against header information contained in IP packets sent by NAUN3 devices; IP descriptors are only applicable for traffic from NAUN3 devices if network address translation (NAT) is performed for that traffic.
- Non-IP descriptors: For Ethernet traffic from NAUN3 devices connected to 5G-RG, Non-IP descriptors are matched against header information contained in Ethernet frames sent by NAUN3 devices.
- Connectivity Group ID: For traffic from a NAUN3 device connected to 5G-RG, Connectivity Group ID in the URSP rule is matched against the Connectivity Group ID that the NAUN3 device is associated with (see clause 4.10b).
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5.2.2 FN-RG
|
This clause specifies the delta for FN-RG related to UE policy distribution defined in clause 6.1.2.2 of TS 23.503 [4] and related to URSP defined in clause 6.6 of TS 23.503 [4].
Only URSP policies are applicable for a FN-RG
A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. Therefore the URSP is used by a W-AGF on behalf of a FN-RG to determine the association of traffic from FN-RG with a PDU session to use for this traffic.
USRP rule enforcement reporting is not defined for FN-RG.
URSP policy information applicable for 5G-RG (as defined in clause9.5.2.1) is also applicable for FN-RG devices except that for Traffic descriptor, only IP descriptors, and Non-IP descriptors are applicable.
The W-AGF shall ignore any of the information and policies not listed above if received from the 5GC.
NOTE 1: The FN-RG initiates the W-5GAN session with the W-AGF, for example PPPoE, and consequently the W-AGF does not receive any indication of the application used for that session (e.g. whether it used for web browsing or for any specific application) and any DNN indication from the application, hence the policy including the Application Descriptors and/or DNN will never match the traffic.
If the PCF sends UE policy (e.g. URSP), the W-AGF shall store it for the duration that FN-RG is registered. When the FN-RG is deregistered, the UE policy can be removed. Whether it is done immediately, or after a certain period (e.g. for quick recovery from disconnection or fault), or stored permanently it is left to implementation and is out of the scope of this TS.
If the URSP for the FN-RG are present in W-AGF (e.g. pre-configured or received from PCF) the W-AGF shall use them as defined for a UE with URSP.
If the URSP for the FN-RG are not present in W-AGF, the W-AGF acts based on local configuration, as defined for a UE without URSP.
The W-AGF requests PDU Sessions upon data trigger (e.g. PPPoE, DHCP, etc.) received over a data path identified by a VLAN and a GLI; this is defined in BBF specifications (BBF TR-456 [9] and BBF TR-470 [38]).
Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN(s) terminated at different FN RG(s).
NOTE 2: The VLAN configuration depends on the served FN RG as a W-AGF service area can serve different Wireline access networks with different VLAN configurations.
The corresponding W-AGF configuration about parameters of the PDU Sessions to request for a GLI corresponds to URSP that the W-AGF receives from the PCF for a SUPI corresponding to a GLI.
The URSP(s) may be used to map VLAN(s) at transport level (S-tags as defined in BBF TR-470 [38]) on the V interface of the W-AGF (identifying the target service of the corresponding data flows, e.g. internet / IMS Voice / IPTV) towards Route Selection components including PDU Session type, DNN, S-NSSAI, SSC mode, etc.
NOTE 3: UDR policy data related with a FN-RG subscription (UE Policy Section, see clause 5.4.2.3 of TS 29.519 [39]) can be configured accordingly.
It is assumed that the FN-RG configuration (provided via BBF TR-069 [18]/BBF TR-369 [19]), the URSP rules and the local configuration in the W-AGF are consistent with each other. If the W-AGF detects conflicting requirements based on URSP, local configuration, or requests from the FN-RG, then the URSP rules takes precedence since they are considered the most updated and aligned to the current 5G system conditions.
UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 [4] are applicable with the following modification:
- Roaming is not applicable to W-5GAN access in this release of specification.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.5.3 Policy Control Request Triggers relevant for AMF and wireline access type
|
The Policy Control Request Triggers relevant for AMF and wireline access type define the conditions when the AMF shall interact again with PCF after the AM Policy Association. PCR triggers defined in Table 6.1.2.5 in TS 23.503 [4] are supported for W-5GAN scenario with the following not supporting ones:
- Location change (tracking area).
- Change of UE presence in Presence Reporting Area.
- RFSP index change.
- UE-AMBR change.
- PLMN change.
Additionally, the following PCR triggers are added regarding the wireline access type:
Table 9.5.3-1: Policy Control Request Triggers relevant for AMF and wireline access type
Policy Control Request Trigger
Description
Condition for reporting
Access Type change
(NOTE 1)
The Access Type and the RAT Type has changed
PCF (AM Policy)
NOTE 1: The RAT type is reported for 3GPP access, or when the 5G-RG or FN-RG registers over wireline access (i.e. W-AGF).
The UE Policy related PCR triggers like location change, PRA change and PLMN change are not applicable for wireline access.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.6 Configuration and Management from ACS
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.6.1 General
|
Once the 5G-RG connects to 5GC, the 5G-RG shall establish a PDU session for interaction with the ACS to support the functionalities as described in BBF TR-069 [18] or in BBF TR-369 [19].
NOTE: Whether and how to use the objects received from the ACS by RG is out of 3GPP scope.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.6.2 ACS Discovery
|
The ACS information may be associated to the RG subscription in the UDM / UDR. In this case the ACS information may be provided to the RG with at least one of the following methods:
- via DHCP interaction if the RG sends DHCP signalling indicating a request for ACS information. The RG sends a DHCPv4 request including a request for ACS information and receives ACS information from the DHCP as specified in BBF TR-069 [18] clause 3.1 for ACS Discovery or in BBF TR-369 [19] R-DIS.1 and R-DIS.2.
- during the PDU session establishment procedure via PCO (protocol Configuration Option) sent in N1 SM message if the 5G-RG has asked to be provided with ACS information via PCO. This applies for 5G-RG only.
The ACS information (e.g. URL of the ACS) is defined in BBF TR-069 [18] or in BBF TR-369 [19].
If the RG performs ACS discovery via DHCP process and the SMF is not the DHCP server (e.g. in the case of Ethernet PDU session), the ACS URL is provided by the external DHCP server. In this case, the whole process is transparent to the 5GC and the 5GC is not aware of the ACS information. If the RG performs ACS discovery via DHCP process and the SMF is the DHCP server the ACS information is provided by SMF as part of DHCP process and the SMF shall support the DHCP procedure defined in BBF TR-069 [18] Amendment 6 clause 3.2 or in USP (BBF TR-369 [19]).
If the SMF is to provide ACS information to the RG (via PCO or DHCP), it gets this ACS information from SMF subscription data.
The request of ACS information via PCO or via DHCP are mutually exclusive.
The RG may be pre-configured with an ACS information.
The 5G-RG shall consider the ACS information received with the following descending priority order:
1) ACS information received during the DHCP process.
2) ACS information received during the PDU session establishment procedure from SMF PCO. This applies for 5G-RG only.
3) The pre-configured ACS information in the RG.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.6.3 ACS Information Configuration by the 3rd party
|
The ACS information may be configured by a 3rd party AF to the 5GC per subscriber when the SMF is to provide ACS information to the RG. Subsequently, the ACS discovery via PCO or via DHCP with the DHCP server in the SMF may apply as described in clause 9.6.2.
Figure 9.6.3-1: ACS information configuration procedure
The ACS information configuration procedure enables the 3rd party AF to configure the ACS information (e.g. URL or IP address) to the 5GC.
1. The 3rd party AF provides the ACS information, in the Nnef_ParameterProvision_Update Request to the NEF as in step 1 of TS 23.502 [3] figure 4.15.6.2-1.
2. As in step 2 of TS 23.502 [3] figure 4.15.6.2-1 where the provisioned data is the ACS information.
3. As in steps 3 and 4 of TS 23.502 [3] figure 4.15.6.2-1 where the provisioned data is the ACS information.
4. As in step 5 of TS 23.502 [3] figure 4.15.6.2-1.
5. As in step 6 of TS 23.502 [3] figure 4.15.6.2-1.
6. As in step 6 of TS 23.502 [3] figure 4.15.6.2-1 in order to update SMF with ACS information.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.6.4 URSP for FN RG
|
The URSP for FN-RG is defined in clause 9.5.2.2.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.7 new PCRT (Policy Control Request Trigger)
|
The Policy Control Request Triggers relevant for SMF are described in TS 23.503 [4] clause 6.1.3.5 with the clarification and difference shown in this clause.
Table 9.7-1
Policy Control Request Trigger
Description
Difference compared with table 6.2 and table A.4.3-2 in TS 23.203 [31]
Conditions for reporting
Motivation
5G-RG join to a multicast group
The 5G-RG has joined to an IP Multicast Group (NOTE 1).
New
PCF
To support IPTV as defined in clause 7.7.1
5G-RG Leave to a multicast group
The 5G-RG has left an IP Multicast Group (NOTE 1).
New
PCF
To support IPTV as defined in clause 7.7.1
NOTE 1: When the SMF reports this condition it indicates the corresponding IP multicast Addressing information.
NOTE: The corresponding notification can be used by the PCF to manage Preview Rights related with an IP multicast flow corresponding to an IPTV channel. In this case the PCF is responsible to remove the 5G RG authorization to receive an IP multicast flow when the preview duration has elapsed.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.8 AF-based service parameter provisioning for TNAP ID
|
To support location dependent policies when a UE connects using trusted non-3GPP access procedures via a TNAP collocated with a 5G-RG, as described in Figure 4.10-1, an AF may provide one or more TNAP IDs for a UE. A TNAP IDs provided by an AF refers to a TNAP that is collocated with a 5G-RG.
The guidance provided by the AF is sent to the HPLMN of the UE and may apply to a single UE identified by GPSI The request cannot be sent with Any UE or a group of UE as a target.
For TNAP service parameter provisioning (i.e., creating, updating and deleting), the Nnef_ServiceParameter service defined in clause 4.15.6.7 of TS 23.502 [3] is performed with the following modification:
- Service Description contains an AF service Identifier indicating that the request is for providing TNAP information.
- The GPSI of the target UE is provided.
- Service Parameters include TNAP ID(s).
The PCF may compare the TNAP ID provided by the AF with the TNAP ID received in the User Location Information when the UE connects via trusted non-3GPP access. The PCF may apply different policies depending on whether UE is at the TNAP/RG indicated by the AF or not. In case the PCF has both subscribed TNAP ID and AF-provided TNAP ID, the PCF decides based on configuration whether to apply both or one of them.
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
9.9 Policy control subscription information management
|
This clause specifies the delta related to policy control subscription information defined in clause 6.2.1.3 of TS 23.503 [4] for 5G-RG and FN-RG.
To support that the PCF of a PDU Session may, as described in clause 4.10, take the TNAP ID into account in policy decisions when the UE connects via trusted non-3GPP access over wireline access, following information may be supported in PDU Session policy control subscription information for the UE that is defined in Table 6.2-2 of TS 23.503 [4]:
Table 9.9-1: Extract of Table 6.2-2 of TS 23.503 [4]
Information name
Description
Category
List of TNAP ID(s)
The list of identifiers of TNAP collocated with 5G-RG associated with the subscriber
Optional
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
10 Support of additional functionalities
| |
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
10.0 General
|
This clause specifies the delta related to the Rel-16 additional specifications included in TS 23.273 [29] (LCS).
|
e69d1cd2dc70da9d9741385e6ce426a4
|
23.316
|
10.1 User Location Information
|
The User Location Information may correspond to: - In the case of W-5GCAN: TAI and HFC node ID. NOTE 1: HFC node ID identifies the point of attachment of the 5G-CRG. - In the case of W-5GBAN: TAI and GLI. The GLI contains an identifier of the Line ID source and the Line ID value. NOTE 2: A combination of Line ID and identifier of the Line ID source identifies the attachment point of the 5G-BRG. An indication of whether the ULI corresponds to a DSL or to a PON line may also be provided. - In the case of 5G-RG connected via 3GPP access: TAI and Cell Information (as described in TS 23.502 [3] clause 4.10 and TS 23.401 [24] clause 5.9.1). Annex A (informative): UE behind RG using untrusted Non-3GPP access procedures This Annex describes how untrusted Non-3GPP access to 5GC can be provided to a UE via a 5G-RG and FN-RG connected to 5GC. Figure A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via untrusted non-3GPP access (via 5G-RG), NG-RAN or via both accesses. NOTE 1: The reference architecture in figure A-1 only shows the architecture and the network functions directly connected to W-5GAN or N3IWF, and other parts of the architecture are the same as defined in TS 23.501 [2] clause 4.2. NOTE 2: The reference architecture in figure A-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. NOTE 3: The two N2 instances in Figure A-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network. NOTE 4: The UE can as well be registered and connected via 3GPP access. Figure A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access The FN-RG can be connected to 5GC via W-5GAN The UE can be connected to 5GC via untrusted non-3GPP access (via FN-RG), NG-RAN or via both accesses. NOTE 5: The reference architecture in figure A-2 only shows the architecture and the network functions directly connected to Wireline 5G Access Network or N3IWF, and other parts of the architecture are the same as defined in clause 4.2 of TS 23.501 [2]. NOTE 6: The reference architecture in figure A-2 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. NOTE 7: For untrusted non-3GPP access, UE connects to the overlay 5G network using the untrusted non-3GPP access approach as illustrated above. Annex B (informative): Support for differentiated charging and QoS for UEs behind RG For the traffic of UEs behind a RG, QoS differentiation in the RG's PDU Session can be provided on a per UE's IPsec Child Security Association basis. The UE's N3IWF/TNGF determines the IPsec child SAs as defined in clauses 4.12 and 4.12a of TS 23.502 [3] as well as the DSCP value used in the outer IP header of that IPsec child SA. It is assumed that the same set of DSCP values and corresponding QoS are applicable independent of whether UE-requested or network-initiated QoS is used. To support QoS differentiation for the UE's traffic, QoS mapping rules between the RG's 5GC and the UE's 5GC are governed by an SLA (or network configuration in case of single operator), which includes the mapping between the DSCP marking for the IPsec child SAs and the corresponding QoS parameters and also the N3IWF/TNGF IP address(es). The non-alteration of the DSCP field on NWu/NWt is also governed by the SLA and by transport-level arrangements that are outside of 3GPP scope. The SLA also governs the RG PDU session IP addresses. The RG's PCF and SMF may provide PCC rules and QoS rules for the available mappings as determined by the SLA. The packet detection filters in the RG's UPF can be based on the N3IWF/TNGF IP address and the DSCP markings on NWu/NWt. UE's SMF/PCF may use the UE's local IP address, which is the N6 address of the RG's PDU session, to enable differentiated QoS and charging when the UE is accessing N3IWF/TNGF via a W-5GAN. Differentiated charging is enabled by the awareness of N3IWG/TNGF and RG PDU Session IP addresses and also the mapping between DSCP marking and QoS parameters included in the SLA. Annex C (informative): QoS differentiation of traffic of individual non-3GPP devices behind 5G-RG This Annex describes how the traffic of individual non-3GPP devices behind a 5G-RG can be identified and provided with differentiated QoS. Figure C-1: Example scenario for mapping traffic of individual non-3GPP devices to a PDU Session As in this example, two non-3GPP devices mapped to PDU Session A initially used the default QoS Flow (QFI 1); when differentiated QoS is requested for one device, the 5G-RG binds its traffic to a Non-3GPP Device Identifier, and its traffic is mapped to a separate QoS Flow (QFI 2). Four non-3GPP devices mapped to PDU Session B based on their Connectivity Group ID X initially used the default QoS Flow (QFI 3); when differentiated QoS is requested for two of those four devices, the 5G-RG binds their traffic to Non-3GPP Device Identifiers, and their traffic is mapped to separate QoS Flows (QFI 4 and QFI 5). Similarly, three non-3GPP devices mapped to PDU Session C based on their Connectivity Group ID Y initially used the default QoS Flow (QFI 6); when differentiated, but the same, QoS is requested for two of those three devices, the 5G-RG binds their traffic to Non-3GPP Device Identifiers, and their traffic is mapped to a separate QoS Flow (QFI 7). Figure C-2 illustrates a procedure which enables the 5GS to identify the traffic of individual non-3GPP devices initially using the same PDU Session behind a 5G-RG and provide differentiated QoS. Figure C-2: Example procedure for enabling QoS differentiation for individual non-3GPP devices behind 5G-RG 0a. Non-3GPP device 1 is connected to the 5G-RG. 0b. To provide connectivity to the non-3GPP device 1, the 5G-RG implements the existing behaviour of either using the URSP rule (optionally containing the Connectivity Group ID as described in clause 4.10b), or using UE Local Configuration, to map the traffic of the non-3GPP device 1 to a PDU Session. 0c. Non-3GPP device 2 is connected to the 5G-RG. 0d. To provide connectivity to the non-3GPP device 2, the 5G-RG implements the existing behaviour of either using the URSP rule (optionally containing the Connectivity Group ID as described in clause 4.10b), or using UE Local Configuration, to map the traffic of the non-3GPP device 2 to the same PDU Session as non-3GPP device 1. 1. The 5G-RG subscription owner or an authorized user, using mechanisms out of scope of 3GPP, requests differentiated QoS for the non-3GPP device 2 through the AF. NOTE 1: The request for differentiated service can be made through an operator portal hosted either in the 5G-RG or in the AF. 2. AF provisions the Non-3GPP Device Identifier Information for the non-3GPP device 2 into the UDR, as defined in clause 4.15.6.15 of TS 23.502 [3]. NOTE 2: Provisioning of the Non-3GPP Device Identifier Information into the UDR is done only for the non-3GPP devices that require differentiated QoS. This provisioning could be done before a device is connected to the 5G-RG. 3. 5G-RG requested PDU Session Modification procedure is triggered, as defined in clause 7.3.2. NOTE 3: For already existing QoS Flows of a Non-3GPP Device Identifier for whom there is a subsequent update of Non-3GPP Device Identifier Information, PCF may initiate SM Policy Association Modification procedure, as defined in clause 4.16.5.2 of TS 23.502 [3]. 4. In response to step 1, using mechanisms out of scope of 3GPP, the operator portal returns a response to the 5G-RG subscription owner or the authorized user about the completion of the differentiated QoS request for non-3GPP device 2. Annex D (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2019-05 SP#84 SP-190458 - - - MCC Editorial update for presentation to TSG SA#84 for approval 1.0.0 2019-06 SP#84 - - - - MCC editorial update for publication after approval 16.0.0 2019-09 SP#85 SP-190609 0001 4 F Alignment of user location reporting for 5G-RG FWA to TS 23.273 16.1.0 2019-09 SP#85 SP-190609 0003 - B Deregistration procedure for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0004 1 B Service request procedure for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0005 2 B Other procedures for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0006 1 B User profile management and handover clarifications for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0007 1 B PDU Session Modification and Release procedures for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0008 1 F PEI for 5G-RG and FN-RG 16.1.0 2019-09 SP#85 SP-190609 0009 2 B Features for W-AGF to act on behalf of FN-RG 16.1.0 2019-09 SP#85 SP-190609 0011 2 C Network Functions and entities - PCC clause 16.1.0 2019-09 SP#85 SP-190609 0015 3 B Applicability of URSP policy 16.1.0 2019-09 SP#85 SP-190609 0018 2 B Clarification of Network Access Control for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0020 3 B Clarification of N2 procedures for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0025 1 B FN-RG Configuration Update 16.1.0 2019-09 SP#85 SP-190609 0026 1 F Update to FN-RG Registration via W-5GAN 16.1.0 2019-09 SP#85 SP-190609 0027 2 F Update to PDU Session handling for FN-RG 16.1.0 2019-09 SP#85 SP-190609 0028 2 F Update to Session Management procedures for RG 16.1.0 2019-09 SP#85 SP-190609 0030 4 F Support of IPTV 16.1.0 2019-09 SP#85 SP-190609 0032 1 F CableLabs, Charter Communications 16.1.0 2019-09 SP#85 SP-190609 0034 2 C Coordination between PCF and ACS (for FN RG) 16.1.0 2019-12 SP#86 SP-191076 0055 1 F Clean up of services Description 16.2.0 2019-12 SP#86 SP-191076 0010 3 F Reporting wireline non-3GPP access in the AM Policy Association 16.2.0 2019-12 SP#86 SP-191076 0012 1 F Scope of clause 9 16.2.0 2019-12 SP#86 SP-191076 0029 3 F Defining support of slicing for Wireline access 16.2.0 2019-12 SP#86 SP-191076 0036 3 F Addition of support of IPv6 IPTV 16.2.0 2019-12 SP#86 SP-191076 0038 6 F Line ID uniqueness 16.2.0 2019-12 SP#86 SP-191076 0039 3 F UDM/UDR subscription data support for a mapping from Line ID to the the SUPI 16.2.0 2019-12 SP#86 SP-191076 0040 4 F PEI for FN RG (BBF LIAISE-337 / 3GPP S2-1908758) 16.2.0 2019-12 SP#86 SP-191076 0041 3 F Addition of support of IPTV Leave procedure 16.2.0 2019-12 SP#86 SP-191076 0044 1 F Resolving open issue on IPv6 multi-homing 16.2.0 2019-12 SP#86 SP-191076 0045 1 F Correction to the support of RG-LWAC and UDM procedures 16.2.0 2019-12 SP#86 SP-191076 0046 2 F Correction on FN-RG procedure 16.2.0 2019-12 SP#86 SP-191076 0048 3 F Clarification of UE behind 5G-RG through trusted Non-3GPP access 16.2.0 2019-12 SP#86 SP-191076 0049 1 F Clarification of IP address allocation for FN-RG 16.2.0 2019-12 SP#86 SP-191076 0050 3 F Clarification on 5G-RG with Hybrid access 16.2.0 2019-12 SP#86 SP-191076 0051 1 F Triggers for procedures initiated by W-AGF 16.2.0 2019-12 SP#86 SP-191076 0052 3 F Clarification of Session-TMBR 16.2.0 2019-12 SP#86 SP-191076 0053 2 F QFI and RQI support in BBF W-5GBAN 16.2.0 2019-12 SP#86 SP-191076 0054 2 F Update to Protocol Stacks for W-5GAN 16.2.0 2019-12 SP#86 SP-191076 0056 - F Service Area Restrictions applicability for FN-CRG, and not FN-BRG 16.2.0 2019-12 SP#86 SP-191076 0057 F Correction to Clause 7.2.1.1 5G-RG Registration via W-5GAN 16.2.0 2019-12 SP#86 SP-191076 0058 2 F Separate Multicast access control for multiple STBs behind 5G-RG 16.2.0 2019-12 SP#86 SP-191076 0059 2 F Addition of Policy Control Request Triggers for wireline access 16.2.0 2019-12 SP#86 SP-191076 0060 1 F Clarification of IPTV configuration create service operation 16.2.0 2019-12 SP#86 SP-191076 0061 1 F Non-5G Capable (N5GC) devices alignment with SA3 16.2.0 2020-03 SP#87E SP-200068 0063 2 F Corrections to 5G-RG and FN-RG procedures 16.3.0 2020-03 SP#87E SP-200068 0064 - F Resolving Editor's notes for Hybrid Access / ATSSS 16.3.0 2020-03 SP#87E SP-200068 0065 1 F Remove a batch of ENs for WWC 16.3.0 2020-03 SP#87E SP-200068 1829 5 F Configuration of URSP for FN RG 16.3.0 2020-03 SP#87E SP-200068 1831 1 F Reference Alignment with BBF 16.3.0 2020-03 SP#87E SP-200068 1832 3 F TS23.316 - Correction on User Location Information 16.3.0 2020-03 SP#87E SP-200068 1833 2 F Access type and RAT type per Non-3GPP accesses 16.3.0 2020-03 SP#87E SP-200068 1834 - F Clarification related with the (non) support of PWS and LADN on Wireline access 16.3.0 2020-03 SP#87E SP-200068 1835 1 F Cable access related corrections 16.3.0 2020-03 SP#87E SP-200068 1837 1 F AS level parameters to W-5GAN 16.3.0 2020-03 SP#87E SP-200068 1838 - F Corrections to Hybrid Access 16.3.0 2020-03 SP#87E SP-200068 2034 - F Mega CR on editorial corrections for 5WWC 16.3.0 2020-03 SP#87E SP-200068 2035 1 F Remove the Editor's note for 5WWC 16.3.0 2020-03 SP#87E SP-200068 2036 1 F Correction to IPTV 16.3.0 2020-03 SP#87E SP-200068 2037 1 F Correction of EAP support in Registration procedure for 5G-RG 16.3.0 2020-07 SP#88E SP-200427 2038 1 F Removing explicit signalling of RG-TMBR 16.4.0 2020-07 SP#88E SP-200427 2039 1 F Corrections of RG procedures 16.4.0 2020-07 SP#88E SP-200427 2040 1 F Correction on RAT types of wireline access 16.4.0 2020-07 SP#88E SP-200427 2041 1 F Correction on wireline access 16.4.0 2020-07 SP#88E SP-200427 2042 1 F Adding SUPI and SUCI for N5GC device support 16.4.0 2020-07 SP#88E SP-200427 2044 1 F Correction of references causing wrong specification 16.4.0 2020-07 SP#88E SP-200427 2045 - F Corrections to description of lawful intercept 16.4.0 2020-09 SP#89E SP-200676 2046 1 F Handling of IPv6 addresses for FN-RG 16.5.0 2020-09 SP#89E SP-200676 2048 - F Correction to the description of FN-RG Session Modification Procedure 16.5.0 2020-09 SP#89E SP-200676 2049 1 F Correction on figure in 5WWC 16.5.0 2020-12 SP#90E SP-200954 2050 - F Alignment of 23.316 with TR-456 / TR-470 i.e. the BBF technical specifications 16.6.0 2020-12 SP#90E SP-200954 2051 1 F Update RG-LWAC via UE context modification procedure 16.6.0 2020-12 SP#90E SP-200954 2053 1 F Clarification on UDM and UDR services in 5WWC 16.6.0 2020-12 SP#90E SP-200954 2054 - F Correction on 5WWC 16.6.0 2020-12 SP#90E SP-200954 2055 1 F 5GC Support of DHCP signalling for RG 16.6.0 2021-06 SP#92E SP-210345 2056 1 B MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC 17.0.0 2021-09 SP#93E SP-210912 2058 - A SSC modes for FN-RG 17.1.0 2021-12 SP#94E SP-211304 2061 1 F MTU value for wireline access 17.2.0 2021-12 SP#94E SP-211288 2062 1 F Applicability of ATSSS to 5G-RG in Rel-17 17.2.0 2022-06 SP#96 SP-220391 2063 2 A Generalizing NAS transport between 5G and W-AGF to accommodate latest BBF developments 17.3.0 2022-06 SP#96 SP-220411 2064 1 F Alignment to BBF LS 512 (Frame route, BBF references) 17.3.0 2022-06 SP#96 SP-220411 2065 1 F Additional support for selecting UPF collocated with W-AGF 17.3.0 2022-06 SP#96 SP-220391 2070 1 A Correction about 23.316 reference to UE Security Capabilities 17.3.0 2022-12 SP#98E SP-221062 2072 1 F Change the direction of the arrow in figure 17.4.0 2022-12 SP#98E SP-221080 2073 - F ULI with TAI for wireline access 17.4.0 2022-12 SP#98E SP-221087 2074 2 B Support of Non-3GPP access for SNPN 18.0.0 2023-03 SP#99 SP-230081 2075 1 B IPv6 prefix delegation in 5GS 18.1.0 2023-03 SP#99 SP-230063 2076 6 B Support of wireline access as access to SNPN 18.1.0 2023-03 SP#99 SP-230063 2078 2 B Support for SNPN via wireline access 18.1.0 2023-06 SP#100 SP-230456 2082 1 B Introducing non-3GPP QoS assistance information 18.2.0 2023-06 SP#100 SP-230471 2083 1 F Content of home network domain when SUPI is IMSI 18.2.0 2023-06 SP#100 SP-230456 2085 1 B Differentiation for UEs behind 5G-RG 18.2.0 2023-06 SP#100 SP-230456 2086 1 B Support for AF influence on TNAP ID 18.2.0 2023-06 SP#100 SP-230456 2087 7 B New feature for 5G-RG to support NSWO procedure to authorize UE behind RG 18.2.0 2023-06 SP#100 SP-230456 2091 8 B Support of AUN3 device 18.2.0 2023-06 SP#100 SP-230471 2095 4 B Support of wireline access as access to NPI-NPN and to SNPN 18.2.0 2023-06 SP#100 SP-230456 2097 1 B 5G-RG ID provided in Trusted Non-3GPP access procedure 18.2.0 2023-06 SP#100 SP-230456 2098 6 B Non-3GPP Device Category Definitions 18.2.0 2023-06 SP#100 SP-230456 2099 5 B Differentiated service for NAUN3 devices connected behind a 5G-RG 18.2.0 2023-09 SP#101 SP-230838 2107 - A RFCs related to DHCPv6 are obsoleted by RFC 8415 18.3.0 2023-09 SP#101 SP-230830 2109 1 A Correction of PDU Session Release for 5G-RG 18.3.0 2023-12 SP#102 SP-231252 2113 2 F Corrections Not related with AUN3 devices 18.4.0 2023-12 SP#102 SP-231252 2114 1 F Update on deregistration procedure of 5G-RG serving AUN3 devices 18.4.0 2023-12 SP#102 SP-231252 2115 2 F Clarification on MBR determination for AUN3 device 18.4.0 2023-12 SP#102 SP-231252 2116 1 F Clarification on UE behind 5G-RG and FN-RG 18.4.0 2023-12 SP#102 SP-231252 2117 4 F Clarification on handling devices behind 5G-RG 18.4.0 2023-12 SP#102 SP-231252 2119 2 F Corrections related with AUN3 devices 18.4.0 2023-12 SP#102 SP-231252 2122 2 F Access restriction for AUN3 devices 18.4.0 2023-12 SP#102 SP-231259 2123 3 F SUPI for 5G-CRG support 18.4.0 2023-12 SP#102 SP-231259 2124 3 F SUPI for 5G-BRG support 18.4.0 2024-03 SP#103 SP-240093 2125 - F AUN3 device de-registration 18.5.0 2024-03 SP#103 SP-240093 2126 1 F Registration Management of AUN3 devices to follow TS 23.501 clause 5.5.1 18.5.0 2024-03 SP#103 SP-240093 2127 1 F Clarification on NAS security for AUN3 devices 18.5.0 2024-03 SP#103 SP-240093 2128 1 F URSP for 5G-RG and FN-RG 18.5.0 2024-09 SP#105 SP-241258 2134 1 F Corrections to AUN3 handling in AMF 18.6.0 2024-12 SP#106 SP-241497 2129 10 B XRM_Ph2 KI#6 L4S support in wireline access 19.0.0 2024-12 SP#106 SP-241497 2135 4 B PDU Set handling in wireline access 19.0.0 2024-12 SP#106 SP-241494 2136 10 B Identifying non-3GPP devices behind 5G-RG 19.0.0 2025-03 SP#107 SP-250061 2140 1 F Resolving EN related to PCF initiated Policy Updates 19.1.0 2025-03 SP#107 SP-250061 2141 1 F QoS differentiation of non-3GPP devices behind 5G-RG 19.1.0 2025-03 SP#107 SP-250064 2143 1 F L4S support in wireline access 19.1.0 2025-03 SP#107 SP-250034 2148 1 F R19 Correction on PCRT applicable for 5WWC 19.1.0
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
1 Scope
|
The present document specifies architectural enhancements to the 5G system to support Ambient power-enabled Internet of Things, complying to the requirements in TS 22.369 [2] applicable to the AIoT Device types, traffic types, use cases and connectivity topologies defined in TS 38.300 [5].
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.369: "Service requirements for Ambient power-enabled IoT".
[3] 3GPP TS 23.501: "System Architecture for the 5G System (5GS); Stage 2".
[4] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[5] 3GPP TS 38.300: "NR; Overall description; Stage-2".
[6] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[7] GS1 TDS Release 2.1: "EPC Tag Data Standard".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] 3GPP TS 33.369: "Security aspects of ambient IoT services in 5G".
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
3 Definitions of terms and abbreviations
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
3.1 Terms
|
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
AIoT Device: An Ambient IoT device is an IoT device powered by energy harvesting, with limited energy storage capability.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
ADM AIoT Data Management
AIoT Ambient IoT
AIOTF Ambient IoT Function
EPC Electronic Product Code
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4 Architecture model and concepts
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.1 General concept
|
AIoT is a service that can be provided by the 5GS system to support Ambient power-enabled IoT devices that are powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g. using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source.
The 5GS System architecture for AIoT include the following functions and procedures for:
- AIoT Device identification;
- AIoT Device inventory;
- Providing to, and obtaining from, an AIoT Device application data.
- Disabling AIoT Devices.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2 Architecture
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2.1 General
|
The 5GS System architecture for AIoT includes core network functions, different AIoT Reader architectures and AIoT Devices. The different AIoT Reader architectures allow for different deployment options. The following AIoT Reader architectures are defined:
- NG- RAN (which supports AIoT Reader), which includes either a direct connectivity between NG-RAN and the AIOTF or an indirect connectivity between NG-RAN and the AIOTF via an AMF.
The NG-RAN in this specification refers to the gNB which supports AIoT related functionalities, as specified in TS 38.300 [5]. The gNB may only support communication with AIoT Devices.
The architecture for Network Exposure Function, using reference point representation, defined in clause 4.2.3 of TS 23.501 [3] is applicable for AIoT, with a southbound interface from the NEF to AIOTF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2.2 Architecture for NG-RAN connectivity
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2.2.1 General
|
5GS system architecture for AIoT supports the following connectivity to access an NG-RAN:
- Direct Connectivity: AIOTF communicates with NG-RAN directly.
- Indirect Connectivity via AMF: NG-RAN and the AIOTF communicate indirectly via an AMF.
Figure 4.2.2.1-1 depicts the complete non-roaming architecture showing the overall 5GS architecture for support of AIoT, including both the Indirect Connectivity and Direct Connectivity.
Figure 4.2.2.1-1: Non-roaming AIoT System Architecture
NOTE 1: For the sake of clarity and to depict the complete reference point architecture, the AMF, AIOT2 and N2 as depicted using dashed lines, as all deployments might not use them.
Figure 4.2.2.1-2 depicts the complete non-roaming AIoT system architecture, using the reference point representation.
Figure 4.2.2.1-2: Non-roaming AIoT System Architecture (RAN Readers) in reference point representation
NOTE 2: For the sake of clarity of the point-to-point diagrams, the AF and NRF have not been depicted. However, all depicted Network Functions can interact with the NRF as necessary.
NOTE 3: For clarity, the UDR and its connections with ADM, are not depicted in the point-to-point and service-based architecture diagrams. For more information on the ADM data storage architectures refer to clause 4.5.8.
NOTE 4: For the sake of clarity and to depict the complete reference point architecture, the AMF, AIOT3, N2 and AIOT2 as depicted using dashed lines, as all deployments might not use them.
The architectures in the following clauses showing parts of the overall AIoT architecture specific to each connectivity option:
- Direct Connectivity: the AIOTF uses AIOT2 to access NG-RAN, and is described in clause 4.2.2.2.
- Indirect Connectivity via AMF: the AIOTF uses an AMF which uses N2 to access NG-RAN, and is described in clause 4.2.2.3.
NOTE 5: A deployment that only uses, e.g. the Direct Connectivity only does not need to deploy the NFs, reference points and service-based interfaces associated with the Indirect Connectivity, and vice-versa.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2.2.2 Direct connectivity between AIOTF and NG-RAN
|
In the Direct Connectivity architecture, the AIOTF uses AIOT2 to communicate directly with NG-RAN.
Figure 4.2.2.2-1 depicts the AIoT architecture, using the service-based interfaces, showing only the parts of the AIoT architecture for an AIOTF connecting to NG-RAN directly. The remaining parts of the AIoT architecture shown in Figure 4.2.2.1-1 remain unchanged.
Figure 4.2.2.2-1: NG- RAN - AIOT Direct connectivity Architecture
Figure 4.2.2.2-2 depicts the AIoT architecture, using the reference point representation, showing only the parts of the AIoT architecture for an AIOTF access NG-RAN. The remaining parts of the AIoT architecture shown in Figure 4.2.2.1-2 remain unchanged.
Figure 4.2.2.2-2: NG-RAN - AIOT Direct connectivity Architecture in reference point representation
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.2.2.3 Indirect connectivity between AIOTF and NG-RAN via an AMF
|
Figure 4.2.2.3-1 depicts the AIoT architecture, using the service-based interfaces showing only the parts of the AIoT architecture for an AIOTF connects indirectly to NG-RAN via an AMF. The remaining parts of the AIoT Architecture shown in Figure 4.2.2.1-1 remain unchanged.
Figure 4.2.2.3-1: NG-RAN - AIOT Indirect connectivity Architecture
Figure 4.2.2.3-2 depicts the AIoT architecture, using the reference point representation showing only the parts of the AIoT architecture for an AIOTF connects to NG-RAN via an AMF. The remaining parts of the AIoT architecture shown in Figure 4.2.2.1-2 remain unchanged.
Figure 4.2.2.3-2: NG-RAN - AIOT Indirect connectivity Architecture in reference point representation
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.3 Reference points
|
The AIoT Architecture contains the following reference points:
AIOT1: Reference point between the AIoT Device and the AIOTF.
AIOT2: Reference point between the NG-RAN and the AIOTF.
The following reference points show the interactions that exist between the NF services in the NFs. These reference points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure.
AIOT3: Reference point between the AIOTF and the AMF.
AIOT4: Reference point between the AIOTF and the NEF.
AIOT5: Reference point between the AIOTF and the NRF.
AIOT6: Reference point between the AIOTF and the ADM.
AIOT7: Reference point between the ADM and the UDR.
AIOT8: Reference point between the ADM and the NEF.
In addition to the relevant reference points defined in TS 23.501 [3], in the case of AIoT, these reference points are as follows:
N2: Reference point between the NG-RAN and the AMF.
N33: Reference point between NEF and AF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.4 Service-based interfaces
|
Naiotf: Service-based interface exhibited by the AIOTF.
Nadm: Service-based interface exhibited by the ADM.
In addition to the relevant services defined in TS 23.501 [3] the following service-based interfaces are enhanced for AIoT in this specification:
Namf: Service-based interface exhibited by AMF.
Nnef: Service-based interface exhibited by NEF.
Naf: Service-based interface exhibited by AF.
Nnrf: Service-based interface exhibited by NRF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5 Functional Entities
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.1 AIoT Device
|
Editor’s note: The definition of AIoT Device needs to align with the definition at RAN WGs.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.2 AIoT Readers
|
Editor’s note: NG-RAN and AIoT Reader will be aligned later with RAN WGs. It is FFS whether to specify the relationship between NG-RAN and AIoT Reader and which term to use in this TS.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.3 AIOTF
|
The AIOTF supports the following functions:
- Termination of AIoT NAS protocol with AIoT Device.
- Connectivity with an NG-RAN via a direct interface reference point or via an AMF.
- Support of AIoT service operations towards the AIoT Devices(s):
- Providing an interface to the AF (or via NEF) for AIoT services and authorizing the trusted AF's AIoT service operation request.
- Triggering the NG-RAN to perform AIoT service operations towards the AIoT Device(s), and optionally determining and providing assistance information to the NG-RAN .
- Report the service operation results to AF (or via NEF) based on the local configuration or the AF request.
- NG-RAN selection and optionally a list of RAN Reader selection for AIoT service operations.
- AMF selection based on target area information when AIOTF connects the NG-RAN indirectly via an AMF.
- Correlation ID allocation corresponding to the AF service operation request.
- Retrieving AIoT device profile data from ADM.
- Retrieving AF subscription data from ADM.
- Optionally AIoT Device context management.
- Perform aggregation of the AIoT service responses, determine and provide assistant for the AIoT aggregation in NG-RAN.
NOTE: Authentication of AIoT Devices related to AIOTF is defined in TS 33.369 [9].
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.4 NEF
|
In addition to the functions defined in TS 23.501 [3], the NEF performs the following functions:
- Providing a service exposure API to AFs of 3rd party for AIoT services.
- Interacting with AF of 3rd party and AIOTF.
- Selection of AIOTF for AIoT services.
- Authorization of the untrusted AF’s AIoT operation request.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.5 AF
|
The AF performs the following functions to support AIoT services:
- Interacting with NEF for AIoT related service exposure for 3rd party .
- Interacting with AIOTF for AIoT related service exposure for trusted AF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.6 NRF
|
In addition to the functions defined in TS 23.501 [3], the NRF performs the following functions:
- Support of new NF types AIOTF and their corresponding NF profiles. The NF profile includes the AIOTF ID or IP address, NF type and the serving area information of the AIOTF.
- Support of AIOTF discovery based on parameters such as target area information.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.7 AMF
|
The AMF performs the following functions when the NG-RAN and the AIOTF communicate indirectly via an AMF:
- Relaying signalling for AIoT service between AIoT-RAN and AIOTF.
- Providing transparent transport for AIoT NAS messages between AIoT Device and AIOTF.
- Providing transport for NG-RAN Node’s serving area information between NG-RAN and AIOTF.
Editor’s note: Further functions on AMF is FFS.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.8 UDR
|
In addition to the functions defined in TS 23.501 [3], the UDR may support the following functions:
- Storage of AIoT device profile data.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.5.9 ADM
|
The ADM supports the following functions:
- Management of AIoT device profile data.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6 Protocol Stacks
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6.1 General
|
This clause specifies the protocol stacks between entities used for AIoT. The protocol stacks include the following:
- Protocol stacks between AIoT Device and AFs, including the protocol stacks among AIoT Device, NG-RAN, AMF, AIOTF, NEF and AFs.
Editor's note: The protocol stacks between RAN and 5GC in the following clauses need to align with RAN specifications.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6.2 Protocol Stack between AIoT Device and AF
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6.2.1 General
|
The general protocol stack between an AIoT Device, NG-RAN, AIOTF and AF is shown in Figure 4.6.2.1-1.
Legend:
- AIoT NAS: The NAS protocol between AIoT Device and AIOTF.
- AIoT AS: It is between the AIoT Device and the NG-RAN is specified in TS 38.300 [5].
- AIoT Data: It is the application data exchanged between the AIoT Device and AF.
Figure 4.6.1-1: Protocol Stack Between AIoT Device and AF
The NG-RAN may communicate to AIOTF via different connectivities, see clause 4.2.2.1. The NG-RAN protocol stack remains the same and is transparent to the different connectivities. The protocol stacks and routing of information between an NG-RAN and the AIOTF is defined in other clauses depending upon the architecture used:
- Direct Connectivity: When the NG-RAN communicates with AIOTF directly, the protocol stack is specified in clause 4.6.2.2.
- Indirect Connectivity: When the NG-RAN communicates with AIOTF indirectly via an AMF, the protocol stack is specified in clause 4.6.2.3.
The AIoT NAS protocol supports the inventory response and command related signalling.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6.2.2 Protocol Stack between AF and AIoT Device for NG-RAN Direct Connectivity
|
Legend:
- AIoT Reader Control: It is between the AIOTF and NG-RAN.
Figure 4.6.2.2-1: Protocol Stack between AF and AIoT Device for Direct Connectivity option
The AIoT NAS messages between the AIoT device and the AIOTF are transferred via the NG-RAN transparently.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
4.6.2.3 Protocol Stack between AF and AIoT Device for NG-RAN Indirect Connectivity
|
Figure 4.6.3.1-2: Protocol Stack between AF and AIoT Device for Indirect Connectivity via AMF option
In this Protocol Stack, the AMF is additionally involved and its functionality is as defined in clause 4.5.7. The AIoT NAS messages between the AIoT device and the AIOTF are transferred via the NG-RAN and AMF transparently.
Editor's note: Whether AIoT Reader Control is transported by NGAP or is part of the NGAP protocol will be updated based on RAN WG3 decision.
Editor's note: The reference to AIoT AS Layer protocol will be updated based on RAN WG1 or RAN WG2 decision.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5 High level functionality and features
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.1 General
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.2 AIoT Services
|
The following AIoT Services are supported:
- Inventory service;
- Command service.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.2.1 AIoT Inventory service
|
AIoT Inventory service is used to discover the AIoT devices, i.e. to obtain the AIoT device identifiers.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.2.2 AIoT Command service
|
Three types of Command service operations are supported: Read, Write and Disable.
An AF uses the Command service Read operation to retrieve information from a specific AIoT device.
An AF uses the Command service Write operation to configure information into a specific AIoT device.
An AF uses the Command service Disable operation to permanently disable the capability of the AIoT device(s) to transmit RF signals
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.3 Discovery and Selection of AIoT node(s)
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.3.1 AIOTF Discovery and Selection
|
The AIOTF discovery and selection functionality is supported by the NEF and AF to determine an AIOTF to handle AIoT Services.
When the NEF or AF performs AIOTF discovery and selection for an AIoT service operation request, the following applies:
- The NEF or AF shall utilize the NRF to discover AIOTF instance(s) unless AIOTF information is available by other means, e.g. locally configured in the NEF or AF. The NEF or AF provides to the NRF the Target Area information, when trying to discover AIOTF instance(s). The NRF provides AIOTF instance(s) to the NEF or AF.
NOTE: The local configuration in the NEF can be used for example to select a specific AIOTF instance for the request from a given AF.
- The NEF or the AF selects the AIOTF instance(s) based on the available AIOTF instance(s) (obtained from the NRF or locally configured)
When AIoT Device ID information indicates individual AIoT device(s), the NEF may select AIOTF(s) by taking into account the last known AIOTF instance(s) for those device(s) from ADM.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.3.2 ADM Discovery and Selection
|
The ADM discovery and selection function is supported by the AIOTF to select an ADM instance to retrieve the device profile data or update the last known AIOTF for the AIoT device. The AIOTF may also discover and select an ADM to retrieve AF authorization data. Similarly, the NEF uses the ADM discovery and selection function to select an ADM to obtain the last known AIOTF for the AIoT device.
When the ADM discovery is performed, the AIOTF or the NEF utilizes the NRF to discover the ADM instance(s) unless the ADM information is available by other means, e.g., locally configured. The AIOTF or the NEF selects an ADM instance based on the available ADM instances (obtained from the NRF or locally configured).
One or more of the following factors may be considered for the ADM discovery and selection:
- The AIoT device permanent ID or domain information.
- The AF ID.
Editor's note: The further investigation of factors for the ADM selection will be needed and other factors are FFS.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.3.3 NG-RAN Node and RAN Reader Selection
|
The AIOTF selects NG-RAN node(s) and optionally RAN readers.
The AIOTF obtains the NG-RAN information (supported Area, RAN reader ID list, and, optionally, the location of each served RAN reader) via OAM. The AIOTF receives an AIoT service request including the Target Area information from the NEF or trusted AF. Based on the received Target Area information and the NG-RAN information configured by OAM, the AIOTF selects the NG-RAN node(s) and optionally RAN reader(s).
NOTE 1: The Target Area information can span the supported Area of multiple NG-RAN node(s) or can be a subset of the supported Area of a NG-RAN node.
The AIOTF sends the AIoT service request to the selected NG-RAN node(s), optionally including the RAN Area information derived from mapping the Target Area information to the supported Area and/or RAN reader ID list, if selected, to assist RAN reader selection by NG-RAN node, either directly or through the selected AMF. If multiple NG-RAN nodes are selected, the AIOTF sends the AIoT service request to each selected NG-RAN node along with its corresponding RAN Area information and/or the RAN reader ID list, if selected
If the AIOTF does not provide the RAN Area information or the RAN reader ID list in the AIoT service request to the NG-RAN node, then the NG-RAN node may use all available RAN readers.
Editor’s note: NG-RAN and RAN reader information needs to coordinate with the RAN WG(s). Details are pending RAN WG feedback.
Editor’s note: The AIOTF or AMF configuration of NG-RAN and RAN reader information over NGAP needs to coordinate with RAN WG(s).
Editor’s note: It is FFS how NG-RAN transfers and updates its information to the AIOTF in indirect connectivity.
NOTE 2: RAN reader ID is not exposed to the AF.
If an AIoT service request includes AIoT device Identifier(s), the AIOTF may consider the last known serving RAN reader(s) from the AIoT device context to determine targeted RAN reader(s) directly.
NOTE 3: From the selected NG-RAN node, the AIOTF receives the Inventory Report including the RAN reader ID that represents the AIoT device’s location at reader ID granularity. The AIOTF uses the RAN reader ID to update the last known serving RAN reader information in the local AIoT device context.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.3.4 AMF Discovery and Selection
|
For indirect Connectivity via AMF (see clause 4.2), AMF discovery and selection functionality is implemented in AIOTF.
When the AIOTF performs AMF discovery and selection in order to forward AIoT service operation messages the NG-RAN via AMF, the following applies:
- After the NG-RAN selection for the AIoT service operation (see clause 5.3.3), the AIOTF selects the AMF that has association with the selected NG-RAN nodes in order to forward the AIoT service operation messages.
Editor’s note: It is FFS whether and how the procedure is performed between AMF and AIOTF in order to provide the NG-RAN ID of NG-RAN from the AMF to the AIOTF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.4 Assistance information provided to NG-RAN node
|
The AIOTF provides the following assistance information to the NG-RAN together with the service operation requests:
a) AIoT service type (e.g. Inventory, Command).
b) Optionally, approximate number of AIoT devices based on AF request.
c) Optionally, approximate D2R message size based on AF request.
d) Optionally, time interval as AIoT aggregation assistance information.
Editor's note: Other assistance information may be added later if necessary.
Editor's note: It is FFS where detailed description on time interval as AIoT aggregation assistance information will be captured, i.e. in this clause or in another clause.
If not provided by the AF, bullets b) and c) in the above assistance information provided by the AIOTF may be based on local configuration based on SLA between the AIoT service provider represented by an AF and the operator.
If the AF has provided a time interval, then the AIOTF should set bullet d) to NG-RAN that is equal or shorter than the time interval received from the AF.
NOTE: Based on local configuration, the AIOTF can reject the AF request, e.g. if the AF provided time interval is shorter than a locally configured minimum interval.
The assistance information is used by the NG-RAN for performing service operations, e.g. radio resource allocation by using bullets b) and c), AIoT Device responses aggregation by using bullet d).
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.5 AIoT Device Profile Management
|
The ADM may hold operator’s subscription data for the AIoT Device used in the network. If the AIoT Device is managed by the network, then the profile data for an AIoT Device is required in the network, otherwise the corresponding profile data (e.g. AIoT Device Permanent ID or credentials) is stored external to the network.
The AIoT Device Permanent ID is used by the AIOTF together with local configuration, 3rd party related context to locate the entity which stores the profile data of an AIoT Device.
In case the AIoT Device is managed by the network, the AIOTF checks whether the AIoT Device Permanent ID from AIoT Device has the profile data in the network and retrieves the profile data. The profile data for AIoT Device is different with UE subscription data as defined in clause 5.2.3 of TS 23.502 [4], it is stored in the ADM network entity that exclusively supports management of AIoT Device’s profile data. The AIoT Device Permanent ID is the primary key for AIoT device profile data in the ADM.
The table 5.5-1 below describes information storage structures for AIoT device profile data.
Table 5.5-1: AIoT Device Profile Data
Field
Description
AIoT Device Permanent ID
Uniquely identifies the AIoT Device.
Last known AIOTF information
Indicate the last known AIOTF that serves the AIoT device, or unknown
NOTE: Security materials and security mechanism involving ADM are specified in TS 33.369 [9].
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.6 AF authorization for the AIoT Services
|
The information needed to support the authorization of the AF for performing the AIoT service is stored as the authorization data for 3rd party AF in the ADM, or locally configured in the AIOTF.
Table 5.6-1 below describes items stored as AF authorization data for the AIoT.
Table 5.6-1: AF Authorization Data for AIoT
AF Authorization Data
Description
AF ID
Identifier used to identify the AF.
Allowed area
Indicate the allowed area for the indicated AF to perform the AIoT services operations.
Allowed service operations
Indicate the allowed service operation (s) for the indicated AF, e.g. inventory, read, write, permanent disable.
Allowed target AIoT Devices
Indicate the allowed AIoT Device(s) for the indicated AF.
The information indicating the allowed target AIoT Devices is a list of the permanent AIoT Device ID (see clause 5.7) or the filtering information (see clause 5.8).
The authorization of the AF for the AIoT includes two parts:
- NEF performs AIoT AF request authorization based on the service level agreement (SLA) between the 3rd party AF and the 5GS of the mobile network operator, the operator policy and local configuration as in TS 33.501 [8].
- AIOTF may perform authorization of AIoT service requested by the AF, using the AF authorization data retrieved from n the ADM or configured locally as described in above Table 5.6-1. When ADM is used, the AIOTF also subscribes to changes of AF authorization data in the ADM for synchronization.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.7 Identifiers
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.7.1 General
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.7.2 AIoT Device Permanent Identifier
|
In order to support the AIoT feature in 5G System, a globally unique AIoT Device Permanent Identifier shall be allocated to each AIoT Device. An AIoT Device Permanent Identifier is assigned either by an operator or by a third party. The AIoT Device Permanent Identifier is used to identify an AIoT Device and locate the entity where the AIoT Device related information is stored.
NOTE 1: How to configure an AIoT Device with the AIoT Device Permanent Identifier is out of scope of this specification.
The AIoT Device Permanent Identifier includes the following components:
- The ID Type, including:
- Information indicating whether a PLMN ID is included.
- Information indicating whether a NID is included.
- Information indicating whether a third party identifier is included.
- Identification Information Type, indicating whether the Identification Information contains an EPC or unstructured information.
- The Domain Information includes none, one or more of the following:
- A PLMN Identifier (i.e., MCC and MNC) as specified in TS 23.003 [6] when the information in the ID type indicates it is included
- A Network Identifier (NID) as specified in TS 23.003 [6] when the information in the ID type indicates it is included.
- A third party identifier used to identify a third party when the information in the ID type indicates it is included.
- The Identification Information is used to distinguish different AIoT Devices within the scope identified by Domain Information (if available) and can contain either:
- An EPC, as defined in clause 14 of GS1 TDS Release 2.1 [7].
- Unstructured information, where the contents is defined by the allocator.
Figure 5.7.2-1: AIoT Device Permanent Identifier Structure
An operator allocated AIoT Device Permanent Identifier should include the identifier of the network for the operator. The identifier of the network is present as either a PLMN Identifier, NID or both in the AIoT Device Permanent Identifier.
A third party allocated AIoT Device Permanent Identifier may include none of the following information or include any combination of at least one kind of the following information: a PLMN Identifier, NID or the third party identifier.
NOTE 3: The length of ID Type, PLMN Identifier (if present), NID (if present) and the third party identifier (if present) components is fixed. The length of the Identification Information is variable. The details are specified in TS 23.003 [6] and TS 29.xxx [xx].
Editor's note: The reference in NOTE 3 needs to be updated, when the appropriate stage 3 document is identified.
Editor's note: Whether the Domain Information can be empty needs to be clarified.
The following lengths are supported for the Identification Information in an AIoT Device Permanent Identifier: 96 bits, and 128 bits.
NOTE 4: The encoding for the length of the Identification Information enables additional shorter or longer fixed lengths to be supported in the future.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
5.8 Filtering Information
|
The filtering information is used to identify or filter multiple AIoT Devices and is constructed by one or multiple components of the AIoT Device Permanent Identifier as defined in clause 5.7.
The filtering information includes a list of filtering element information. The filtering element information includes:
- Information indicating a which component of the AIoT Device Permanent Identifier that is used to match the bitstring.
- A bitstring which is used to compare with the component.
Each bitstring is corresponding to one component of the AIoT Device Permanent Identifier.
NOTE: The bitstring match can start at any position in the corresponding component.
Editor's note: Whether and how to secure the filtering information is up to SA WG3.
To determine whether an AIoT Device Permanent Identifier matches the filtering information, it is compared with every filtering element information within filtering information by comparing the bitstring in a filtering element information with the indicated component of its AIoT Device Permanent Identifier. If all the compared bitstrings match the AIoT Device Permanent Identifier then an AIoT Device Permanent Identifier matches the filtering information. If an AIoT Device Permanent Identifier does not contain an indicated component then it does not match the filtering information.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6 AIoT Procedures
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.1 General
|
Editor’s note: The contents of this general clause is FFS and is expected to describe there are service procedures which are reader type/routing agnostic and there are procedures which relate to the transports to the readers.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.2 AIoT Service Procedures
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.2.1 General
|
Clause 6.2.2 provides the procedure for AIoT Inventory. Clause 6.2.3 provides the procedure for AIoT Command.
Editor's note: Additional information in the steps, parameters, and their naming throughout the procedures requires additional details, alignment with other clauses and references adding as required.
Editor's note: Alignment is required for how to document and describe Direct Connectivity and Indirect Connectivity options in the procedures.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.2.2 Inventory Procedure
|
Figure 6.2.2-1 describes the inventory procedure.
The procedure focuses on the messages and parameters used for the communication between AIOTF and NG-RAN regardless of the path to access NG-RAN, see clause 4.2.2.1. The handling of the different communication paths is described in clause 6.2.4.
Figure 6.2.2-1: Inventory Procedure
1. The AF invokes Nnef_AIoT_Inventory(AF ID, [External Target Area information], information about the target AIoT Device(s), [Approximate number of AIoT Devices]) service operation request to the NEF.
The External Target Area information is specified in clause 5.3.
Information about the target AIoT Device(s) may include Filtering Information, as described in clause 5.8, or include complete AIoT Device Identifier(s).
The approximate number of AIoT Devices, if provided, is used to determine the number of AIoT Devices expected to respond to this inventory service operation, which is sent by AIOTF to the NG-RAN in the assistance information for NG-RAN in step 7 for proper radio resource allocation.
Editor's note: The parameters for the inventory service operation need further definition.
2. The NEF may further authorize the AF request as specified in clause 5.6.
The NEF determines the Target Area information, and selects one or multiple AIOTF(s) to handle the request as specified in clause 5.3.1.
3. The NEF invokes the Naiotf_AIoT_Inventory(AF ID, [Target Area information], [information about the target AIoT Device(s)], [Approximate number of AIoT Devices]) service operation towards to the selected AIOTF(s).
4. The AIOTF receives the AIoT service operation request and checks the parameters included in the request. The AIOTF may perform authorization as specified in clause 5.6. If the AIoT service operation request cannot be processed, the AIOTF rejects the AIoT service operation request with an appropriate cause code, and step 7 onwards are skipped.
The AIOTF generates a Correlation ID corresponding to this AF service operation request.
The AIoT Identification Information to be provided to NG-RAN can include Filtering Information, as defined in clause 5.8, or a single AIoT Device Identifier.
AIOTF performs Reader Selection, see clause 5.3.3.
The AIOTF may also use the last serving Reader to assist with determining which Readers to use for an AFs request targeting for a specific AIoT Device.
The AIOTF determines assistance information as described in clause 5.4.
5. AIOTF sends the AIoT Inventory Service Response to the NEF containing the accept or reject result for the AIoT Inventory service operation request based on step 4.
6. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT Inventory service operation request as specified in clause 8.3.
7. The AIOTF sends the Inventory Request message including the Correlation ID, the AIoT Identification Information to be included in the paging message, and assistance information to the selected NG-RAN.
Editor's note: Whether the Inventory Request sent to NG-RAN includes indication about whether there will be a follow up command or not needs to be determined.
8. The NG-RAN sends an Inventory Response to the AIOTF with the Correlation ID indicating that the Inventory Request is received successfully and will perform the service operation accordingly.
9. Upon reception of the Inventory Request message from the AIOTF, the RAN Reader(s) will execute the inventory operation. The RAN Reader(s) broadcast the paging message that includes the AIoT Identification Information.
The AIoT Device determines whether it matches the AIoT Identification Information, as described in clause 5.8.
If an AIoT device matches the AIoT Identification Information in the paging message, the AIoT Device responds to the paging message and sends an AIOT NAS message that includes its AIoT Device ID.
Editor's note: Whether and how the Device ID is concealed or encrypted will be determined and aligned with SA WG3.
10. NG-RAN sends one or more Inventory Report messages to the AIOTF including the Correlation ID, Reader ID and the AIOT NAS message(s) from the AIoT Device(s). The AIOTF stores the mapping between the Reader ID and AIoT Device ID(s).
NOTE: When to erase the stored mapping between the Reader ID and AIoT device ID(s) is up to implementation and local configuration.
11. The AIOTF validates the results, using local stored device information or device profile data retrieved from the ADM. The AIOTF may aggregate the results.
12. Optionally, if the NG-RAN detects that no more AIoT Devices will respond to the inventory procedure, the NG-RAN informs the AIOTF that the procedure is complete.
Editor's note: The details how interactions between NG-RAN and AIOTF to indicate no further Inventory Reports will be sent and completion of the procedure need to be aligned with RAN.
13. The AIOTF reports the progress of the AIoT inventory request to the NEF by sending the Naiotf_AIoT_Notify message including a list of AIoT Device Permanent Identifier (s). The AIOTF may send multiple reports. The AIOTF in the final Naiotf_AIoT_Notify message indicates it is the last report for this operation. If multiple AIOTFs are involved in the procedure, the NEF may receive the AIoT_Notify from multiple AIOTFs.
14. When receiving the Naiotf_AIoT_Notify message from AIOTF, the NEF informs the AF of the outcome of the AIoT_Inventory request by sending the Nnef_AIoT_Notify message(s) including the AIoT Device Permanent Identifier(s). The NEF in the final Nnef_AIoT_Notify message indicates that it is the last report for this operation.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.2.3 Command Procedure
|
Editor's note: Additional information in the steps, parameters, and their naming throughout the procedures requires alignment with other clauses and references adding as required.
Editor's note: Alignment is required for how to document and describe Direct Connectivity and Indirect Connectivity options in the procedures.
Figure 6.2.3-1 depicts the command procedure.
The procedure focuses on the messages and parameters used for the communication between AIOTF and NG-RAN regardless of the path to access NG-RAN, see clause 4.2.2.1. The handling of the different communication paths is described in clause 6.2.4.
Figure 6.2.3-1: Command Procedure
1. The AF sends the Nnef_AIoT_Command (in case of untrusted AF) Request (AF ID, Command Type, AIoT Device identification information, [External Target Area information], [Approximate number of AIoT Devices], [Approximate D2R message size], AIoT data) message to NEF.
Editor's note: It is FFS whether and how to structure the AIoT data if the Command Type is Read, Write or Disable.
The AIoT Device identification information may include one or more AIoT Device ID(s) or the filtering information which is used to associate with multiple AIoT devices.
2. The NEF selects the AIOTF(s) as described in clause 5.3.1. If no AIOTF can be selected, the NEF rejects the AIoT Command request with an appropriate cause code and step 6 is performed before ending the procedure.
3. The NEF sends Naiotf_AIoT_Command Request message (AF ID, Command Type, AIoT Device identification information, [Target area information], , [Approximate number of AIoT Devices], [Approximate D2R message size], AIoT data) message to the selected AIOTF.
4. The AIOTF receives the AIoT command operation request and checks the parameters included in the request. The AIOTF performs NG- RAN and optionally RAN Reader selection as specified in clause 5.3. If no NG-RAN or RAN Reader can be selected, the AIOTF rejects the AIoT Command request with an appropriate cause code.
The AIOTF generates a Correlation ID corresponding to this AF service operation request, and is used for the AIOTF to correlate the service operation responses to the request.
The AIOTF determines assistance information as described in clause 5.4.
The AIOTF performs AF authorization for AIoT command operation as described in clause 5.6.
The AIOTF performs AMF selection as described in clause 5.3.4.
5. AIOTF sends the Naiotf_AIoT_Command Response message (accept or reject, [cause code]) to the NEF.
6. NEF sends the Nnef_AIoT_Command Response message (accept or reject, [cause code]) to the AF. If the response was a reject the procedure stops here.
7. Step 7 to step11 of procedure for Inventory specified in clause 6.2.2 are performed with the following clarifications:
- In step 11, the AIOTF validates the results as specified in TS 33.369 [9], and determines whether the command should be sent to an AIoT Device, e.g., by checking the Target AIoT device information.
If none of successful Inventory response is received, Step 8 -11 is not performed and the AIOTF sends a failure report to the NEF in Step 12.
8. For each successful Inventory response received, the AIOTF sends Command Request message (Correlation ID, [Reader ID], NAS Command Request, [Approximate D2R message size]) to the NG-RAN directly or as an AIoT Transfer Container via an AMF as specified in clause 6.2.4. The NAS Command Request message includes the AIoT data.
Editor's note: What parameter(s) are used in the Command Request to enable NG-RAN node to target a specific AIoT Device requires coordination with RAN3.
Editor's note: Additional information included in the NAS Command Request for security will be determined and aligned with SA WG3.
9. The NG-RAN sends the AS R2D message (NAS Command Request) to the AIoT Device.
10. The AIoT Device sends the AS D2R message (NAS Command Response) to the NG-RAN. The NAS Command Response message may include the AIoT data.
Editor's note: The AS R2D message and AS D2R message will be aligned with RAN WG's specification.
Editor's note: Additional information included in the NAS Command Response for security will be determined and aligned with SA WG3.
11. The NG-RAN responds with a Command Response message (Correlation ID, Reader ID, NAS Command Response) to the AIOTF directly or as an AIoT Transfer Container via an AMF as specified in clause 6.2.4.
12. The AIOTF reports the result of the AIoT Command request to the NEF by sending the Naiotf_AIoT_Command Notify message (AIoT Device ID(s), AF ID, AIoT data).
13. The NEF informs the AF of the result of the AIoT_Command request by sending the Nnef_AIoT_Command Notify message (AIoT Device ID(s), AF ID, AIoT data).
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
6.2.4 Procedures between AIOTF and NG-RAN for Indirect Connectivity
|
An AIOTF and NG-RAN can use an indirect interface via an AMF as described in clause 4.2.2.4. The additional steps used for indirect interface between AIOTF and NG-RAN are shown in Figure 6.2.4-1.
Figure 6.2.4-1: Procedure for AIOTF and NG-RAN for indirect connectivity via an AMF
1. The AIOTF sends Namf_AIoT_MessageDelivery message (AIoT Transfer Container, NG-RAN ID, AIOTF ID, Message Type for AIoT Transfer Container) to the AMF. The AIoT Transfer Container may be Inventory Request Transfer or Command Request Transfer.
2. The AMF sends an NGAP message (AIOTF ID, AIoT Transfer Container) to the target NG-RAN.
3. The NG-RAN sends an NGAP message (AIOTF ID, AIoT Transfer Container) to an AMF. AIoT Transfer Container may be Inventory Response Transfer, Inventory Report Transfer, Inventory Failure Transfer, Command Response Transfer or Command Failure Transfer.
4. AMF sends the Namf_AIoT_Notify message (AIoT Transfer Container) to the AIOTF.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7 Network Functions Services
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.1 General
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.2 AIOTF services
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.2.1 General
|
The AIOTF supports to expose AIoT services towards the AF or the NEF as described in Table 7.2.1-1.
Table 7.2.1-1: NF services provided by the AIOTF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Naiotf_AIoT
Inventory
Request/Response
NEF, AF
Command
Request/Response
NEF, AF
Notify
Subscribe/Notify
NEF, AF
Editor's note: It is FFS how to support the service between AMF and AIOTF in order to report and update the information provided by the RAN for indirect connectivity.
Editor's note: It is FFS whether to use separate service operation to respectively support read, write or disable command procedure.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.2.2 Naiotf_AIoT_Inventory service operation
|
Service operation name: Naiotf_AIoT_Inventory.
Description: The NF consumer requests an inventory operation for one or multiple AIoT Device(s).
Inputs, Required:
1) AF ID.
2) At least one of the following parameters are included:
- Target area information for the inventory operation.
- Information about the target AIoT Device(s):
- either the AIoT Device ID(s) or the filtering information for multiple AIoT Devices.
Inputs, Optional:
1) Information to be used for resource allocation:
- Approximate number of AIoT Devices.
Outputs, Required: Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional: None.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.2.3 Naiotf_AIoT_Command service operation
|
Service operation name: Naiotf_AIoT_Command.
Description: The NF consumer requests a command operation for one or multiple AIoT Device(s).
Inputs, Required:
1) AF ID.
2) At least one of the following parameters are included:
- Target area information for the command operation.
- Information about the target AIoT Device(s):
- either the AIoT Device ID(s) or the filtering information for multiple AIoT Devices.
4) Command Type: Read, Write or Permenant Disable.
5) Command specific parameters:
Editor’s note: The AIoT Data specific for the Read/Write/Disable command is FFS.
Editor’s note: The Command specific parameters for Read/Write/Disable command is FFS.
Inputs, Optional:
1) Information to be used for resource allocation:
- Approximate number of AIoT Devices.
- Approximate message size from the AIoT Device for Read Operation.
Editor’s note: It is FFS whether the Approximate message size from the AIoT Device can also be provided by the AF for the other command operations.
Outputs, Required: Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional: None.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.2.4 Naiotf_AIoT_Notify service operation
|
Service operation name: Naiotf_AIoT_Notify
Description: The AIOTF uses this service operation to notify the results or status of the service operation towards the NF consumers. If the NF consumer invokes the Naiotf_AIoT_Inventory, or Naiotf_AIoT_Command service operation, the NF consumer implicitly subscribes to the results of the requested service operation.
Inputs, Required:
1) Common report information: Transaction ID, List of AIoT Device ID or Failure Cause in case of Failure).
2) Read command specific report information: Information obtained from each target AIoT Device.
Editor’s note: It is FFS whether that fail to discovery any AIoT device is normal operation result or failure case.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
Editor’s note: It is FFS how to make AF be aware of the report is finished in case there are multiple notify for the same AIoT operation.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.