hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.6.4 Handover procedures between 3GPPaccess / EPS and W-5GAN/5GC access
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.6.4.1 Handover from 3GPP access / EPS to W-5GAN / 5GC
|
Figure 7.6.4.1-1: Handover from EPS to W-5GAN/5GC
The procedure specified in clause 4.11.3.1 of TS 23.502 [3] (Handover from EPS to 5GC-N3IWF) applies with the following changes.
0. Initial status: one or more PDN connections have been established in EPC between the 5G-RG and the PGW-C+SMF via E-UTRAN.
1. The 5G-R... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.6.4.2 Handover from W-5GAN / 5GC access to 3GPP-access / EPS
|
Figure 7.6.4.2-1: Handover from W-5GAN/5GC to EPS
0. Initial status: one or more PDU Sessions have been established via W-5GAN / 5GC access. During PDU Session setup, and in addition to what is specified in clause 4.3.2.2.1 of TS 23.502 [3], the PGW-C+SMF sends the FQDN related to the S5/S8 interface to the HSS+UDM ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7 Support of specific services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.0 General
| This clause specifies the procedure for specific services for WWC scenario defined in clause 5.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1 IPTV
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1.1 Overview
| In this Release of the specification, in order to support IPTV services, following principles apply:
- the 5G-RG supports IP PDU Session Type;
- IP multicast traffic received from N6 interface is replicated by UPF and sent over PDU Sessions;
- IGMP or MLD messages from the STB or from the 5G-RG are terminated and ma... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1.1.1 Registration and PDU Session Establishment procedure for IPTV
| 5G-RG perform Registration procedure described in clause 4.2.2.2.2 of TS 23.502 [3] with the following differences:
- UE is replaced by 5G-RG.
5G-RG perform PDU Session establishment procedure described in clause 4.3.2.2.1 of TS 23.502 [3] applies with the following differences and clarifications:
- UE is replaced b... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1.1.2 IPTV Access procedure
| In the case of IPTV network access control based on the DHCP procedure, 5G-RG may be configured to retrieve via DHCP the IP address that it will use to access IPTV services. The DHCP procedure described in TS 23.501 [2] clause 5.8.2.2 is carried out with the difference shown below:
- When the SMF receives the Uplink D... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1.1.3 Unicast/Multicast Packets transmission procedure
| 5GS can support Unicast Service from IPTV network directly.
In order to obtain the multicast service from IPTV network, the Multicast Packets transmission procedure should be performed. The procedure in figure 7.7.1.1-3 describes how the 5G-RG joins an IP multicast group.
Figure 7.7.1.1-3: 5G-RG join IP Multicast P... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 7.7.1.1.4 AF request to provision Multicast Access Control List information into UDR
|
Figure 7.7.1.1.4: AF request to provision Multicast Access Control List information into UDR
NOTE 1: The 5GC NFs used in this scenario are assumed to all belong to the same PLMN (HPLMN).
1. To create a new request, the AF invokes an Nnef_IPTV_configuration service operation. The request contains the Multicast Acce... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8 Network Function services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.0 General
| This clause specifies the delta related to Network Function services description defined in TS 23.502 [3] clause 5.2. For 5G RG in FWA mode TS 23.502 [3] clause 5.2 applies.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.1 UDM Services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.1.1 Nudm_SubscriberDataManagement (SDM) Service
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.1.1.1 General
| In addition to the Subscription data types used in the Nudm_SubscriberDataManagement Service, as defined in Table 5.2.3.3.1-1 of TS 23.502 [3], the additional data types defined in Table 8.1.1.1-1 below are applicable for RGs connected to 5GC via W-5GAN and AUN3 devices .
Table 8.1.1.1-1: Wireline access specific UE S... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.2 Void
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.3 BSF Services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.3.1 General
| The Nbsf_Management_Register/Deregister and Discovery service operations defined in TS 23.502 [3] are extended to allow registration/deregistration and discovery of the binding information when one or multiple /128 IPv6 address or UE IPv6 prefix shorter than /64 is/are assigned to a PDU session.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4 PCF Services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4.1 General
| PCF services defined in TS 23.502 [3] apply with modifications described in this clause.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4.2 Npcf_SMPolicyControl
| The Npcf_SMPolicyControl_Create and Npcf_SMPolicyControl_Update, defined in TS 23.502 [3], are extended to be able to provide PCF with one or multiple allocated /128 IPv6 UE address or with UE IPv6 prefix shorter than /64.
The Npcf_SMPolicyControl_Update, defined in TS 23.502 [3], is extended to be able to provide PCF... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4.3 Npcf_AMPolicyControl
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4.3.1 Npcf_AMPolicyControl_Create service operation
| The input data listed in clause 5.2.5.2.2 in TS 23.502 [3] apply when an AM Policy Association is created for a 5G-RG, except for the handling of RFSP information that applies only if a 5G RG is registered over 3GPP access.
The input information when the UE registers via W-5GAN includes the Access type set to non-3GPP... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.4.3.2 Npcf_AMPolicyControl_Update service operation
| The input data listed in clause 5.2.5.2.5 in TS 23.502 [3] apply when an AM Policy Association is updated for a 5G-RG or for a FN-RG, except for the notification of UE location change (if an RG registers only on Wireline access), PRA changes or RFSP index change.
PCRT on UE location change apply when a 5G RG registers... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.5 Nnef_IPTVconfiguration service
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.5.1 General
| Service description: This service provides:
- Request authorization of NF Service Consumer requests.
- Request parameter mapping from NF Service Consumer requests to 5GC parameters and vice versa as described in clause 7.7.1.1.x
- NF Service Consumer request configuration of Multicast Access control list as describe... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
In... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
Input... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.6 UDR Services
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 8.6.1 Nudr_DataManagement (DM) Service
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9 Policy and Charging Control Framework and Configuration by ACS
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.1 Session management related policy control
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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 c... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.2 Network Functions and entities
| |
fb6d29e6a362615ca2c901270a8a42ba | 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].
|
fb6d29e6a362615ca2c901270a8a42ba | 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 modifi... |
fb6d29e6a362615ca2c901270a8a42ba | 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] ... |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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 transmitte... |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.5 Non-session management related policy information
| |
fb6d29e6a362615ca2c901270a8a42ba | 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... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.5.2 UE access selection and PDU Session selection related policy information
| |
fb6d29e6a362615ca2c901270a8a42ba | 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 appl... |
fb6d29e6a362615ca2c901270a8a42ba | 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 re... |
fb6d29e6a362615ca2c901270a8a42ba | 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 cha... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.6 Configuration and Management from ACS
| |
fb6d29e6a362615ca2c901270a8a42ba | 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.
|
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 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
... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 9.6.4 URSP for FN RG
| The URSP for FN-RG is defined in clause 9.5.2.2.
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
Diffe... |
fb6d29e6a362615ca2c901270a8a42ba | 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 ... |
fb6d29e6a362615ca2c901270a8a42ba | 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 acces... |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 10 Support of additional functionalities
| |
fb6d29e6a362615ca2c901270a8a42ba | 23.316 | 10.0 General
| This clause specifies the delta related to the Rel-16 additional specifications included in TS 23.273 [29] (LCS).
|
fb6d29e6a362615ca2c901270a8a42ba | 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 an... |
b2d353929edcfdfba7b1da5c3ee436ab | 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].
In this Release, the AIoT sy... |
b2d353929edcfdfba7b1da5c3ee436ab | 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.
-... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 3 Definitions of terms and abbreviations
| |
b2d353929edcfdfba7b1da5c3ee436ab | 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 ener... |
b2d353929edcfdfba7b1da5c3ee436ab | 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
EP... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4 Architecture model and concepts
| |
b2d353929edcfdfba7b1da5c3ee436ab | 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,... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.2 Architecture
| |
b2d353929edcfdfba7b1da5c3ee436ab | 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 ... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.2.2 Architecture for NG-RAN connectivity
| |
b2d353929edcfdfba7b1da5c3ee436ab | 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... |
b2d353929edcfdfba7b1da5c3ee436ab | 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... |
b2d353929edcfdfba7b1da5c3ee436ab | 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 c... |
b2d353929edcfdfba7b1da5c3ee436ab | 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... |
b2d353929edcfdfba7b1da5c3ee436ab | 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-... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.5 Functional Entities
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.5.1 AIoT Device
| The AIoT Device supports the following functionality:
- Support of AIoT NAS protocol with the AIOTF.
- Support of AIoT radio interface towards AIoT reader, as defined in TS 38.300 [5].
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.5.2 NG-RAN
| The NG-RAN in this specification refers to the gNB which supports AIoT related functionalities as specified in clause 4.2.1.
The NG-RAN supports the following functions:
- The NG-RAN communicates with the AIOTF either via a direct connectivity or indirectly connectivity.
- The NG-RAN serves one or more AIoT readers.... |
b2d353929edcfdfba7b1da5c3ee436ab | 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... |
b2d353929edcfdfba7b1da5c3ee436ab | 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 reques... |
b2d353929edcfdfba7b1da5c3ee436ab | 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.
|
b2d353929edcfdfba7b1da5c3ee436ab | 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 type AIOTF and its corresponding NF profile. The NF profile includes the AIOTF ID, FQDN or IP address, NF type and the serving area information of the AIOTF.
NOTE: The serving area information of the A... |
b2d353929edcfdfba7b1da5c3ee436ab | 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 (including e.g., inventory/command messages) between NG-RAN and AIOTF transparently.
- Providing transparent transport for AIoT NAS messages between AIoT Device and AIOTF.
|
b2d353929edcfdfba7b1da5c3ee436ab | 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 Ambient IoT data, including:
- AIoT device profile data.
- AF authorization data.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.5.9 ADM
| The ADM supports the following functions:
- Management of AIoT device profile data.
- Management of AIoT device security data including device credentials as defined in clause 4.2.3 of TS 33.369 [9].
- Management of AF authorization data.
The AIoT device profile data and AF authorization data used by the ADM may be... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6 Protocol Stacks
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6.1 General
| This clause specifies the protocol stacks among 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.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6.2 Protocol Stack between AIoT Device and AF
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6.2.1 General
| The NG-RAN communicates with AIOTF via one of the two connectivity options as following:
- 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 stac... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6.2.2 Protocol Stack between AF and AIoT Device for NG-RAN Direct Connectivity
|
Legend:
- AIoT Data: It is the application data exchanged between the AIoT Device and the AF.
- AIoT NAS: The NAS protocol between AIoT Device and the AIOTF.
- AIoT AS: It is between the AIoT Device and the NG-RAN as specified in TS 38.300 [5].
- NGAP: Application Layer Protocol between the AIOTF and the NG-RAN a... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 4.6.2.3 Protocol Stack between AF and AIoT Device for NG-RAN Indirect Connectivity
|
Legend:
- AIoT Data: It is the application data exchanged between the AIoT Device and the AF.
- AIoT NAS: The NAS protocol between AIoT Device and the AIOTF.
- AIoT AS: It is between the AIoT Device and the NG-RAN as specified in TS 38.300 [5].
- NGAP: Application Layer Protocol between the AMF and the NG-RAN as ... |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5 High level functionality and features
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.1 General
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.2 AIoT Services
| The following AIoT Services are supported:
- Inventory service;
- Command service.
|
b2d353929edcfdfba7b1da5c3ee436ab | 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.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.2.2 AIoT Command service
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.