hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.3.3 AIoT Presence Information notification
| Table 7.4.3.3-1 describes the AIoT Presence Information notification.
Table 7.4.3.3-1: AIoT Presence Information notification
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Presence report
M
The presence report information.
> AIoT device identifiers
M
The list of device identifiers for which presence is reported
> Presence status
M
The status of presence which is one of present or absent or unknown.
> Location information
O
The location information of the AIoT device.
> Presence status duration
O
The duration since the last presence status change.
> Presence reporting status
O
The status of presence reporting which may be an indication that presence reporting has started or stopped.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5 Solution#5: Services on Application AIoT Discovery and Monitoring
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1 Solution Description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.1 General
| The existing services on AIoT inventory and AIoT command cannot satisfy the application requirements on the aspects listed in the above key issues. For example, based on current exposure results from 5G core network as specified in 3GPP TS 23.369 [3], only the AIoT devices ID will be provided for the inventory request, and cannot identify the AIoT devices in service granularity and indicate when one type of device will reach the pre-defined threshold to perform the increase or decrease.
The following clauses specify AIoT discovery and monitoring services for supporting AIoT applications.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.2 Procedure for Application AIoT Discovery
|
Figure 7.5.1.2-1: Application AIoT Discovery
1. A consumer (e.g., VAL server) sends application AIoT discovery request to AIoT App server. The request information includes VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device information (e.g., list of application layer objects (e.g., goods in a warehouse) which correspond to a list of application AIoT devices, type(s) of the objects), Number of AIoT devices, Requirements on categorization (e.g., location-based, object type-based), Requirements on discovery (e.g., count number of objects in specific location, count number of specific objects), and Time interval.
2. The AIoT App server authenticates and authorizes the request.
3. If authorized, the AIoT App server performs categorization of the AIoT devices in the list provided in step 1 according to the requirements on categorization and determines the AIoT inventory request to 5GC NF (i.e. NEF/AIOTF) for each of the categories. Based on the list of AIoT devices in a category, the AIoT App determines the Filtering Information to be used in the inventory request.
4. The AIoT App server sends the AIoT inventory requests according to the determination in step 3 to the 5GC NF (NEF or AIOTF), for obtaining the AIoT device IDs and location of each AIoT device for each of the category.
5. The AIoT App server maps the received AIoT device IDs into objects for each category and processes the received information according to the requirements on discovery, e.g., count the number of objects in specific location, count the number of specific object type.
6. The AIoT App server sends application AIoT discovery response to the consumer, with the required discovery information.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.3 Procedure for Application AIoT Monitoring
|
Figure 7.5.1.3-1: Application AIoT Monitoring
1. A consumer (e.g., VAL server) sends application AIoT monitoring request to AIoT App server. The request information include VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device information (e.g., list of application layer objects (e.g., goods in a warehouse) which correspond to a list of application AIoT devices), Number of AIoT devices, Requirements on categorization (e.g., location-based), Requirements on monitoring (e.g., monitor the number of objects in specific location (e.g., number of goods in a warehouse), the expired time of the objects (e.g., the expired time of the goods in a supermarket)), Time interval for monitored data processing, and Reporting requirements.
Reporting requirements could be Periodic reporting (frequency of the reporting), or Event-triggered reporting (report when a threshold is exceeded or change occur).
For threshold-based report, Threshold(s) (e.g., number(s) of objects in specific locations, time threshold(s) for specific objects) is included in the request.
For flexible report (i.e., change occur and report), the event could be, for example, number of specific type object change compared with previous check (e.g., increase or decrease in given location (e.g., Goods with the given category are in or out the given location)) or status of object change (e.g., expired time is approached/reached (e.g., Goods are close to be expired with given time range per goods category)). Frequency for check the changes of object (e.g., number, status (may align with the time interval for monitored data processing)) are included in the request.
2. The AIoT App server authenticates and authorizes the request.
3. The AIoT App server responds to the application AIoT monitoring request, with subscription ID.
4. If authorized, the AIoT App server performs categorization of the AIoT devices in the list provided in step 1 according to the requirements on categorization, determines the operations according to the requirements on monitoring in step 1 (e.g., AIoT inventory for monitoring the number changes of objects, AIoT command-read for monitoring the status of object), and schedules periodic AIoT inventory and/or command-read.
5. Based on the determinations in step 4, the AIoT App server performs corresponding operations for monitoring.
5a. The AIoT App server may send AIoT inventory request(s) to 5GC NF (NEF/AIoTF) to obtain the AIoT device IDs in given location.
5b. The AIoT App server may send AIoT command request(s) to 5GC NF (NEF/AIoTF) to read the AIoT data and location information.
6. Based on the received information in step 5 and requirements in step 1, the AIoT App server processes the data, and determines whether need to send notification to the consumer after each round of monitored data processing, e.g., report periodically, report the changes of object number, report the changes of object status (e.g., expired time approached/reached).
7. The AIoT App server sends application AIoT monitoring notification to the consumer, with the required monitoring information.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.4 Information Flows
| Editor’s Note: The information flows of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6 Solution #6: Solution for AIoT service provision
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.1 Solution description
| This solution address key issue#2, and #4 to introduce a solution for AIoT service provision.
AIoT network service can provide the information of what (AIoT device IDs) and where (AF ID and the external Target Area information), as shown in the TS 23.369[7]. However, these network exposured data can’t be directly consumed by the 3rd party appication layer and needs to be correlated with application information. The core idea is to establish a mapping relationship for network layer information and the application data.
The figure 7.6.1-1 show the high-level procedures of AIoT service provisioning.
Figure 7.6.1-1: Service data provisioning
1. The AIoT application layer consumer invokes the service provisioning service of AIoT enabler server by sending the AIoT service data provisioning request. The request contains the following information:
- a. Mapping of AIoT devece IDs and specific application objects (such as a product, a pallet, a tool, or a person) ID. This is the premise of all associations. When attaching AIoT devices to objects of the ASP, it is necessary to create a "AIoT devece ID and application object" association in theAIoT enabler server to record this binding relationship.
b. The application object information including the object ID, name, type, other attributes, etc.
c. AIoT application service regions and its associated target area information, the associated AIoT service scenarios.
d. AIoT service scenario and its cooresponding service requriements and interested AIoT service events
The AIoT service scenario is tightly correlated with the application service meanings. The cooresponding service requirements and the interested AIoT service event will be used be later inforced during the invocation of AIoT network services and the processing of network exposured AIoT data before providing enriched information to the AIoT application layer.
The AIoT service scenario categoried based on the application requirements, such as inbound/outbound, inventory, monitor and tag command, and each type may need different kinds of 3GPP AIoT network service. For different scenarios, the interested AIoT service events may be different, which should be set according to the requirements of the application layer. For example, the warehouse storage inventory scenario may need the inventory result about what objects are exist or what objects are missing or the counting of the objects.
An example of those information is listed as table 7.6..1-1.
Table 7.6.1.1: an example of scenario type, service requirement, interested service event
AIoT service scenario Type
AIoT network services requements
interested AIoT service events
Inbond/Outbound
Rapid inventory and report with time interval X for result aggregation
Inbond/Outbound event/ Alarm Event
Storage Inventory
non-rapid inventory and report time interval Y for result aggregation
Inventory/Alarm/ Counting Event
Monitor
periodic inventory
Moving/Alarm Event
Tag command
Read/Write/Disable service
Read/Write/Disable result event
2. The AIoT enabler layer performs the authorization check. If authorized, it stores the information received in the request for futher usage.
3. The AIoT enabler layer returns a AIoT service data provisioning response indicating the success of service provisioning.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.2 Architecture Impacts
| This solution introduces the AIoT service provisioning capability to the AIoT enabler layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.3 Corresponding APIs
| A new AIoT service provisioning service is introduced.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7 Solution #7: Application AIoT Task execution
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.1 Solution description
| This solution address key issue#2, 3 and 4 to introduce a solution for application AIoT task execution. The AIoT tasks from the application layer cannot be directly aligned with the AIoT NEF interface. It is necessary to translate AIoT tasks into AIoT inventory and/or command towards the 3GPP core network.
Figure 7.7.1-1: AIoT Task initiation
1. AIoT task is generated in the AIoT application layer according to the service requirements. Usually, the AIoT task is described with AIoT service scenario with the information of application object and AIoT application service region as described in table 7.7.1-1. The AIoT task is initiated and sent to AIoT enabler server with AIoT task information.
Table 7.7.1-1: Example of Application AIoT task description
Application AIoT Tasks information
Application Object ID(s)/application object type(s)
AIoT application service area
AIoT service scenario Type
-Inbound/outbound
-inventory
-monitor
-read/write/disable command
2. The AIoT enabler server determines to invoke the network Inventory and/or Command service API towards the 3GPP core network. The value of input parameters of the Inventory and/or Command service API is determined based on the received AIoT task information and the provisioned service data.
For example, for the inbound task in warehouse A at check point X, the AIoT enable layer needs to determine a specific AF id and the target area information, which is associated to “warehouse A check point X”. Due to the AIoT service scenario is “inbound”, a rapid periodic AIoT inventory service should be performed with a time interval of result aggregation being set Xms.
3. The final AIoT service API invocation(s) is initiated towards the 3GPP core network.
4. The 3GPP core network starts the AIoT services operations
5. The AIoT enabler server sends a AIoT task initiate response information to the application layer to notify whether the AIoT task is initiate successfully or not, then the application layer decides whether to wait for the result or republish the AIoT task.
NOTE 1: The step 5 can be performed before step 4.
NOTE 2: The step 1 and step 5 can use the subscribe/notification model.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.2 Architecture Impacts
| This solution introduces the AIoT task transformation capability to the AIoT enabler server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.3 Corresponding APIs
| This solution introduces a new AIoT task execution service.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8 Solution #8: Exposing the value-added information of AIoT devices to the consumer
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.1 Solution Architecture
| This solution is based on an independent architecture that is newly defined in the Sol#2. In the architecture, an AIoTApp application enabler is defined and acts as a SEAL layer function entity. This function entity can be deployed and implemented by integrating with other related service enabler functions (e.g., SEALDD server, NSCE server) for the support of the Ambient IoT application services.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.2 Solution description
| For AIoT service operation requests, the collected AIoT Devices ID(s) could be huge, less categorized and may not fulfill the service requirements from the 3rd parties (e.g. AS/AF).
For example, a 3rd-party retail App-server (i.e., VAL server) may issue periodic inventory service requests to check the volume of some specific types of AIoT devices in a (large) area. When the number of the available AIoT devices of a type drops below a certain threshold, the retail store might run into service interruption of not having sufficient goods for customers. In this scenario, the corresponding retailer is better off replenishing the stock in advance by adding more devices of the type. The current exposure information from the 5G core network as specified in 3GPP TS 23.369[3] lacks the categorization for the AIoT devices.
In another scenario, if a VAL server (AF) sends an 'inventory service’ request covering a large area, or send continuously a batch of 'inventory service’ requests covering different (small) areas, though belonging to the same (large) targeted area whose identity could be a geographical civic address, then, the AIoT application enabler may aggregate these requests to optimize the efficiency by sending only one combined 'inventory service’ request, or sending multiple requests to multiple AIOTF in 5GC.
Besides, some VAL servers may need to regularly track the location of the AIoT devices (e.g. the goods in the truck) and identify the trajectory or the direction for the AIoT devices depending on their locations. Alert messages may be sent to certain AIoT devices in case they deviate from the right trajectory/direction. How to leverage the 5GC exposure capability of mapping the RAN ID to the location information (e.g. civic address) and accordingly tracking the devices’ location continually as requested should be studied further in application enablement layer.
In a word, it would be of great advantage to AIoT services consumers, i.e., the VAL server, if they can receive enriched results from the Ambient IoT App enabler.
Based on the functional model for AIoTApp service as in the Sol#2, the application enablement architecture layer is proposed to enhance at the server side. The VAL server communicates with the AIoTApp enabler via the AIoTApp-S reference point, which further communicates with the underlying 3GPP network systems. For any additional processing of value-add services, e.g., more effective batched processing of service requests, aggregation of captured AIoT device information, exposure of location info. of AIoT devices, etc., the application enabler AIoTApp can provide the enriched services.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3 Procedure
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.1 Exposure of value-added information via AIoT application enabler
| Figure 7.8.3.1-1 illustrates the procedure for the AIoT application enabler to interact with the 5GS for the support of the Ambient IoT App service that leverages the corresponding 5GC NF services and APIs as specified in the TS 23.369 [3]. Upon receiving the requested AIoT device information, the AIoTApp enabler conducts the value-added information processing before exposing the information to the VAL server (i.e., AIoT service consumer).
Pre-condition:
- The VAL server discovers and selects the AIoTApp enabler by CAPIF functions.
- Multiple AIOTFs may be discovered and selected in the 5GS.
Figure 7.8.3.1-1: Exposure of value-added info via AIoT App enabler
1. The VAL server decides to use the AIoT application enabler (AIoTApp) to collect the AIoT device information and allocates address/port as AIoTApp-S Data transmission connection information for receiving the AIoT data packets from the AIoTApp enabler. The VAL server sends the AIoT_app_service request to the AIoTApp enabler. The type of AIoT service is Inventory request. The service request includes VAL server ID, VAL service ID, AIoTApp-S Data transmission connection information of the VAL server side, and the AIoT service related parameters (e.g., AF ID, [External Target Area information], [information about the target AIoT Device(s)], [Approximate number of AIoT Devices], [time interval], etc.). The details of these service parameters are described in 3GPP TS 23.369 [3].
As specified in the clause 5.8 of TS 23.369 [3], Information about the target AIoT Device(s) may include Filtering Information that might be constructed by one or multiple components (i.e. ID Type, PLMN Identifier, NID, third party identifier and Identification Information). These components can be used by the AIoTApp enabler to enrich the processing.
2. Upon receiving the request, the AIoTApp enabler performs an authorization check. If authorization is successful, the AIoTApp enabler allocates the AIoTApp-S data transmission connection information (e.g., address/port) of AIoTApp enabler side to receive the AIoT data packets from the VAL server to be delivered to the 5GC. The AIoTApp enabler responds with the AIoT_app_service response.
NOTE 1: The AIoTApp-S data transmission connection information of the AIoTApp enabler side is optional, if the AIoTApp enabler uses the downlink pull mode to fetch the AIoT data from the address provided by the VAL server in step 1, and uses the uplink push mode to send the AIoT data to the address provided by VAL server.
3. After the AIoTApp enabler receives from the VAL server the AIoT service related parameters, depending on the local configuration, the AIoTApp enabler may apply enriched and optimized processing, e.g.:
- If the received request covers a large area, the AIoTApp may send multiple requests to multiple discovered and selected AIOTF NFs in 5GC. This is applicable to the trusted AF case.
- If the AIoTApp receives batched requests continuously with each one spanning a small area, the AIoTApp may either aggregate the batched requests and send only one combined service request or send multiple requests concurrently to multiple AIOTF NFs in 5GC.
4. The AIoTApp sends service operation requests towards the (selected) AIOTF(s), as in 3GPP TS 23.369 [3] clause 6.2. There could be multiple AIOTF NFs selected from the step-3.
NOTE 2: All the invoked service operations, together with the service parameters, conform to what have been specified in TS 23.369 [3]. E.g., depending on the trustiness of the AF (i.e., AIoTApp), AIoTApp sends either External Target Area information (to NEF as an untrusted AF) or Target Area information (to AIOTF as a trusted AF).
The 5GS processes the AIoT service request(s) and collects the AIoT device information based on the provided service parameters, or local configuration. There could be multiple AIoTF(s) sending collected AIoT device information to AIoTApp (or via NEF). Details are in TS 23.369 [3].
5. The AIoTApp enabler apply value-added processing to the received AIoT device information, e.g.
- If AIoTApp receives AIoT device information for a large target area from multiple AIOTF NFs, then it can consolidate the information before send to the VAL server.
- Based on the components in the Filtering Information received in the step-1, e.g., ID Type, the AIoTApp enabler may consolidate and categorize AIoT devices and derive the number of the available AIoT devices of a type in a target area. The AIoTApp then exposes the value-added information to the VAL server for further processing.
6. The AIoTApp enabler sends the processed AIoT device information via the AIoT_app_service notification to the VAL server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2 Information flows
| Editor’s Note: The details of Information Flows are FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.1 AIoT App Service request
| Table 7.8.3.2.1-1 describes the information flow from the VAL server to the AIoTApp enabler for the support of the AIoT App service.
Table 7.8.3.2.1-1: AIoT App service request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
AIoTApp-S endpoint information
M
Address/port and/or URL of the VAL server to receive the AIoT data packets from the AIoTApp.
AIoT service parameters
M
(Note 1)
AIoT service parameters (e.g., AF ID, (external) target area info, etc.).
DL AIoT data delivery status subscription indication
O
Indicates the VAL server expected to receive the DL AIoT delivery status notification
NOTE: The AIoT service parameters are specified in the 3GPP TS 23.369 [3].
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.2 AIoT App service response
| Table 7.8.3.2.2-1 describes the information flow from the AIoTApp enabler to the VAL server to respond to the AIoT App service request.
Table 7.8.3.2.2-1: AIoT App service response
Information element
Status
Description
Result
M
Success or failure.
AIoTApp-S enpoint information
O
Address/port and/or URL of the AIoTApp enabler to receive the AIoT data packets from the VAL server to be delivered to 5GC.
Cause
O
(see NOTE)
Indicates the reason for the failure, e.g., AF ID not supported, Target Area not allowed.
NOTE: The IE is only present if the Result is failure.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.3 AIoT App service notification
| Table 7..8.3.2.3-1 describes the information flow from the AIoTApp enabler to the VAL server to notify the events related to the AIoT App service.
Table 7.8.3.2.3-1: AIoT App service notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event of the AIoTApp enabler interaction status with 5GC for AIoT App services, e.g., enriched processing results, no collected AIoT device info., etc.
VAL service ID
O
Identity of the VAL service.
DL AIoT data delivery instructions
O
(see NOTE)
Indicates the instructions to the VAL server regarding the DL AIoT App service
> Collected AIoT device info.
O
Indicates the collected raw AIoT device information.
> Enrich-processed AIoT info.
O
Indicates enriched processing results of AIoT info (e.g., categorization, consolidation, filtering, etc.)
NOTE: Either Event ID IE or the DL AIoT data delivery instruction ID is present.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9 Solution #9: Support of periodical and event-triggered AIoT service operations
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.1 General
| This solution addresses the KI#2. Just as the example described in the KI#2, a 3rd-party retail App-server (i.e., VAL server) may issue periodic or event-triggered inventory service requests to check the changed volume of some specific types of AIoT devices in a certain area. When the number of the available AIoT devices of a type drops below a certain threshold, the retail store might run into service interruption of not having sufficient goods for customers. In this scenario, the corresponding retailer is better off replenishing the stock in advance by adding more devices of the type. If the retail store asks for periodic inventory service, it’s expected to be informed when and which type of devices will be increased or decreased.
This solution is proposed to fulfil the above scenario and mainly support the following service requests:
- Periodic inventory service request;
- Event-triggered inventory service request;
- Report changed volume of some specific types of AIoT devices in a certain area;
- Report when and which type of devices will be increased or decreased.
Clause 7.9.1.2 illustrates the high-level procedure of periodic AIoT inventory service operations.
Clause 7.9.1.3 illustrates the high-level procedure of event-triggered inventory service operations.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.2 Procedure of periodic AIoT inventory service operations
| Figure 7.9.1.2-1 illustrates the high-level procedure of periodic inventory service request triggered by the VAL server(s).
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services. For the functionalities of new AIoT enabler, please check the Sol#1 for KI#1 for more details.
Figure 7.9.1.2-1: Procedure of periodic AIoT inventory service operations
1. The VAL server sends an AIoT Inventory subscription request to the AIoT enabler, including the service type indication (e.g., inventory), service ID, target area information, target AIoT device information , triggering conditions (e.g., periodic reporting), time interval for periodic reporting, only reporting the changed volume indicator for AIoT devices, etc.
The information about the target AIoT device(s) may include the Filtering Information as described in clause 5.8 of 3GPP TS 23.369[3].
The indication of only reporting the changed volume for AIoT devices means only the changed volume compared to last report for the specific AIoT device will be reported instead of all of AIoT device IDs.
2. The AIoT enabler checks whether the VAL server is authorized to request the Inventory subscription request, may be based on e.g., the pre-configurations or the operator policies.
3. If the request is authorized, the AIoT enabler sends an AIoT Inventory subscription response to the VAL server.
4. The AIoT enabler invokes Nnef_AIoT_Inventory request periodically to the 3GPP CN to obtain the AIoT device data as specified in clause 6.2.2 of 3GPP TS 23.369 [3]. And the AIoT enabler will set the time interval for the periodical Nnef_AIoT_Inventory request less than or equals to the time interval received in Step 1.
5. The AIoT enabler stores the received AIoT device information and analyse them based on the AIoT Inventory subscription service request. The AIoT enabler may classify the AIoT devices based on the requested AIoT Device(s) filtered information (e.g., EPC ID), count the number for each type of AIoT devices (including maximum, minimum and average granularity), compare the number for two sequential times for the same target AIoT device in the same target area, and then calculate the corresponding changed information including e.g., the change is increase/decrease, the changed number/volume, the specific AIoT device type corresponding to the changes, etc.
6. The AIoT enabler will periodically report the AIoT device information to the VAL server based on the time interval received in Step 1. The report may include the AIoT device ID, the number of AIoT devices which may be all devices or the devices filtered based on different criteria (e.g., PLMN, third-party ID, EPC ID, etc.), the changed information compared to the previous report (e.g., the change is increase/decrease, the number/volume of change, etc.), the time point of the report, the last report indication, etc.
NOTE 1: Whether the AIoT enabler reports the changed information depends on the indication of only reporting the changed volume for AIoT devices in Step 1 is included or not.
NOTE 2: Reporting of changed information is only applicable to the second and subsequent notification messages.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.3 Procedure of event triggered AIoT inventory operations
| Figure 7.9.1.3-1 illustrates the high-level procedure of event triggered AIoT inventory operations which is based on the periodic AIoT inventory operations described in clause 7.9.1.2.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services. For the functionalities of new AIoT enabler, please check the Sol#1 for KI#1 for more details.
Figure 7.9.1.3-1: Procedure of event triggered AIoT inventory operations
1. Similar with Step 1 in clause 7.9.1.2. The difference is the triggering condition is not the periodic reporting but the event-triggered reporting, and the event is e.g. when the number of one type of AIoT devices is going to reach the pre-defined threshold.
2. Similar with Step 2 in clause 7.9.1.2.
3. Similar with Step 3 in clause 7.9.1.2.
4. The AIoT enabler may set the time interval to trigger the periodic AIoT inventory operations described in clause 7.9.1.2 to obtain the target AIoT devices information.
5. The AIoT enabler stores the obtained AIoT devices information and classifies the AIoT devices based on the requested filtered information (e.g., EPC ID), count the number for requested type of AIoT devices, and then compare the number with pre-defined threshold received in Step 1. If the number of certain AIoT devices are going to reach the pre-defined threshold, the AIoT enabler may immediately notify the VAL server to indicate the number of specific AIoT devices will reach the pre-defined threshold, with the AIoT device ID, the total number, the trigger events, the suggested actions (e.g., increase/decrease the number of specific AIoT devices), etc.
If the event trigger condition is met, the AIoT enabler will no longer trigger the periodic AIoT inventory request to the 3GPP CN.
6. Similar with Step 7 in clause 7.9.1.2. The AIoT enabler notifies the VAL server of the AIoT device information. The notification may include the target AIoT device ID, the number of target AIoT devices, the trigger events, and the suggested actions (e.g., increase/decrease the number of specific AIoT devices), the time point of the report, etc.
Editor’s note: Whether and how the procedures 7.9.1.2 and 7.9.1.3 can be combined or not is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10 Solution #10: Support of querying history data for AIoT devices
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1.1 General
| This solution addresses the KI#2. Some application servers (e.g., a super market) may need to check the history data for some specific type of AIoT devices (e.g., check the sales volume of umbrellas from last year) to predict the trends for this year and beyond. So it’s necessary for application servers to query the history data for the AIoT devices in the application enabled layer.
This solution is proposed to fulfil the above scenario and mainly support the following service requests:
- Query the history data (e.g., device number, device location info, etc.) for AIoT devices;
- Report the history data to the application server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1.2 Procedure of querying history data for AIoT devices
| Figure 7.10.1.2-1 illustrates the high-level procedure of querying history data for AIoT devices.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services.
- The AIoT enabler support to store the history data for requested AIoT devices.
- The VAL server doesn’t have the requested AIoT history data.
Figure 7.10.1.2-1: Procedure of querying history data for AIoT devices
1. The AIoT enabler may interact with 3GPP CN to query the AIoT devices data periodically as described in solution Sol#9 and store the obtained AIoT device data.
2. The VAL server sends an AIoT history data request to the AIoT enabler, including the query service type (e.g., device location, device number), service ID, target area information, target AIoT device information, and target time point/period, etc.
Information about the target AIoT Device(s) may include Filtering Information as described in clause 5.8 of 3GPP TS 23.369 [3].
3. The AIoT enabler checks whether the VAL server is authorized to request the AIoT history data request may be based on e.g. the pre-configurations or operator policies.
4. If the request is authorized, the AIoT enabler checks if the stored sensing data in the local storage could meet the service requirements received in step 1. If yes, the AIoT enabler may report the requested history data and perform the statistical analysis for the retrieved information. E.g., if the query type is device number, the report may include the total number for the specific AIoT devices as well as the maximum/minimum/average number. If there is no local storage or the local storage cannot fulfil the service requirements, the AIoT enabler may response with the failure cause.
5. The AIoT enabler reports the history data for the requested AIoT device to the VAL server via sending AIoT history data response message. The report may include the AIoT device ID, the retrieved history data for the AIoT device, and related statistical analysis for the retrieved data, etc.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11 Solution #11: Provision and monitor AIoT device presence
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.1 Solution Architecture
| This solution is based on an independent architecture that is newly defined in the Sol#2. In the architecture, an AIoTApp application enabler is defined and acts as a SEAL layer function entity. This function entity can be deployed and implemented by integrating with other related service enabler functions for the support of the Ambient IoT application services.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.2 Solution description
| For the AIoT service operation requests defined in 3GPP TS 23.369 [3], i.e., Inventory and Command, there exist certain scenarios for which the AIoT application enabler can enhance the operations.
For example, a 3rd-party application server (e.g., VAL server) may collect the AIoT device information (e.g., location information) via inventory service request for an AIoT device originally located in a first target area. This AIoT device may be moved to a second target area for any reason. When the 3rd-party application server issues inventory service request for the same AIoT device to the first target area, the failure to retrieve the AIoT device information will be generated. For this scenario, the AIoTApp application enabler may provide a remediation mechanism by searching within alternate targeted area(s) so as to pinpoint the up-to-date information of the AIoT device. The 5GC does not provide such remediation mechanisms.
In another scenario, some application servers (e.g. a logistics company) may need to regularly track the locations of AIoT devices (e.g. the goods in the truck) and identify the (moving) path of the AIoT devices, based on which warnings could be sent to the AIoT devices in case they deviate the right/expected track. Recently, the SA2 WG has reached agreement to support the exposure of AIoT device location information to AF as in 3GPP TS 23.369 [3].
In a 3rd scenario, when concurrent monitoring operations need to be performed on multiple AIoT devices, repeatedly issuing the same commands can significantly reduce system scheduling efficiency. Since base stations typically only support serial operations, meaning they can handle only one task at a time, the application enablement layer must coordinate and aggregate concurrent requests from multiple applications. For instance, if multiple operations target different AIoT devices within the same area, they can be consolidated into a single command and uniformly dispatched to the 5GC, thereby avoiding redundant scheduling and enhancing processing efficiency. Also, the application enablement layer can intelligently filter based on device identifiers, for instance, selecting devices that match specific code segments. Drawing from the masking mechanism of RFID, these devices can be abstracted into a logical group and described through a unified masking rule. This involves filtering target devices according to identifier rules (such as those with similar ID segments) and then configuring them into a mask group. Subsequently, the application enablement layer only needs to issue a single monitoring command to the 5GC and specify this mask to achieve batch operations on all devices within the group.
Therefore, it would be of great advantage if the Ambient IoT App enabler could help monitor the presence as well as track the path of AIoT devices in more efficient schemes.
Based on the functional model for AIoTApp service as in the Sol#2, the application enablement architecture layer is proposed to enhance at the server side. The VAL server communicates with the AIoTApp enabler via the AIoTApp-S reference point, which further communicates with the underlying 3GPP network systems via either the N33 (via NEF for an untrusted AF), or the interface off the 5GC AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF. The enhanced provisioning and monitoring operations will be handled by the AIoTApp enabler.
A VAL server provides to the App enabler AIoTApp the parameter ‘location information requested’, along with other parameters. Then, AIoTApp interacts with the 5GS NF AIOTF to retrieve the location information of an AIoT device. Accordingly, AIoTApp can track the presence of the device as well as its trajectory. AIoTApp enabler may also request location information based on its local configuration.
AIoTApp can send concurrent service requests to multiple AIOTFs in 5GC to optimize the operations.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3 Procedure
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.1 Provision and monitor AIoT device presence
| Figure 7.11.3.1-1 illustrates the procedure for the AIoT application enabler to interact with the 5GS for the support of the Ambient IoT App service that leverages the corresponding 5GC NF services and APIs as specified in the TS 23.369 [3]. The VAL server sends the ‘location information request’ indication to AIoTApp, along with the potential monitoring schedule. The AIoTApp sends the received request, or based on local configuration, to the 5GC. Once the requested AIoT device information (e.g., location information) is received from the 5GC, the AIoTApp enabler can do more enhanced information processing (e.g., presence verification, location tracking) before sending the information to the VAL server (i.e., AIoT service consumer).
Pre-condition:
- The VAL server discovers and selects the AIoTApp enabler by CAPIF functions.
- Multiple AIOTFs may be discovered and selected in the 5GS.
- AIOTFs have determined to provide the AIoT device location information to AF based on operator policy.
Figure 7.11.3.1-1: Provision and monitor AIoT device presence
1. The VAL server decides to use the AIoT application enabler (AIoTApp) to collect the AIoT device information and allocates address/port as AIoTApp-S Data transmission connection information for receiving the AIoT data packets from the AIoTApp enabler. The VAL server sends the AIoT_app_service request to the AIoTApp enabler. The type of AIoT service request is Inventory. The service request includes VAL server ID, VAL service ID, and the AIoT service related parameters (e.g., AF ID, [External Target Area information], [information about the target AIoT Device(s)], [Approximate number of AIoT Devices], [time interval], location information requested). The VAL server may also send AIoT device provisioning and monitoring parameters (e.g., device location tracking request, monitoring schedule (e.g., every hour for 24 hours), device-id/a group of device-IDs). The details of AIoT service related parameters are described in 3GPP TS 23.369 [3].
As specified in the clause 5.8 of 3GPP TS 23.369 [3], Information about the target AIoT Device(s) may include Filtering Information that might be constructed by one or multiple components (i.e. ID Type, PLMN Identifier, NID, third party identifier and Identification Information). These components can be used by the AIoTApp enabler to identify a particular AIoT device or a group of devices.
2. Upon receiving the request, the AIoTApp enabler performs an authorization check. If authorization is successful, the AIoTApp enabler responds with the AIoT_app_service response.
3. After the AIoTApp enabler receives from the VAL server both the AIoT service related parameters and AIoT device provisioning and monitoring parameters, depending on the local configuration, the AIoTApp enabler sends AIoT service requests to 5GC, with the indication ‘location information requested’.
The AIoTApp may send concurrently the requests for a group of AIoT device-IDs to multiple discovered and selected AIOTF NFs in 5GC.
4. The AIoTApp sends Inventory service operations towards the (selected) AIOTF(s), as in 3GPP TS 23.369 clause 6.2.
There could be multiple AIOTF NFs selected from the step-3. for concurrent AIoT device monitoring operations.
NOTE 2: All the invoked service operations, together with the service parameters, conform to what have been specified in TS 23.369. E.g., depending on the trustiness of the AF (i.e., AIoTApp), AIoTApp sends either External Target Area information (to NEF as an untrusted AF) or Target Area information (to AIOTF as a trusted AF).
NOTE 3: The AF (i.e., AIoTApp) can send the parameter ‘location information requested’ to AIOTF in 5GC to request the AIOTF to report the location information of AIoT devices.
The 5GS processes the AIoT service request(s) and collects the AIoT device information based on the provisioned service parameters, or local configuration. The AIoT device location information can be reported to the AF (i.e., AIoTApp) as described in the TS 23.369 [3]. (Multiple) AIOTF(s) send collected AIoT device information to AIoTApp (or via NEF). This information may include the location information of an AIoT device, depending on operator policy and the requested parameter from the AIoTApp.
5. The AIoTApp enabler processes the received AIoT device information, e.g.
- If the VAL server has requested the AIoTApp to monitor the presence of an AIoT device and the AIoTApp receives the device information for the AIoT device, then AIoTApp reports the presence to the VAL server.
- If the VAL server has requested the AIoTApp to monitor the presence of an AIoT device and the AIoTApp does not receive the device information for the AIoT device from 5GC, then AIoTApp may expand the service request in more Target Areas that have been received in step-1 from the VAL server. The step 4 of the procedure will be repeated to monitor the presence of the AIoT device.
- If the VAL server has requested the AIoTApp to track the historical location information of an AIoT device, then AIoTApp will record the received location information of the AIoT device. Based on the monitoring schedule received in step-1, the AIoTApp enabler may repeat the step 4 of the procedure to continue tracking the location of the device. When the monitoring schedule is fulfilled, the AIoTApp can send the tracked historical location information of the AIoT device to the VAL server.
6. The AIoTApp enabler sends the processed AIoT device information via the AIoT_app_service notification to the VAL server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.2 Information flows
| Editor’s Note: The details of Information flows are FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.2.1 AIoT App Service request
| Table 7.11.3.2.1-1 describes the information flow from the VAL server to the AIoTApp enabler for the support of the AIoT App service.
Table 7.11.3.2.1-1: AIoT App service request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
AIoT service parameters
M
(Note 1)
AIoT service parameters (e.g., AF ID, (external) target area info, location information requested, AIoT device filtering info., etc.).
AIoT monitoring schedule
O
AIoT service request schedule based on which AIoT service requests are sent to 5GC.
DL AIoT service request delivery status subscription indication
O
Indicates the VAL server expected to receive the DL AIoT service request delivery status notification
NOTE 1: The AIoT service parameters are specified in the 3GPP TS 23.369 [3].
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.2.2 AIoT App service response
| Table 7.11.3.2.2-1 describes the information flow from the AIoTApp enabler to the VAL server to respond to the AIoT App service request.
Table 7.11.3.2.2-1: AIoT App service response
Information element
Status
Description
Result
M
Success or failure.
Cause
O
(see NOTE)
Indicates the reason for the failure, e.g., AF ID not supported.
NOTE: The IE is only present if the Result is failure.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.3.2.3 AIoT App service notification
| Table 7.11.3.2.3-1 describes the information flow from the AIoTApp enabler to the VAL server to notify the events related to the AIoT App service.
Table 7.11.3.2.3-1: AIoT App service notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event of the AIoTApp enabler interaction status with 5GC for AIoT App services, e.g., device present, location & trajectory tracking, no collected AIoT device info., etc.
VAL service ID
O
Identity of the VAL service.
DL AIoT service request delivery instructions
O
(see NOTE)
Indicates the instructions to the VAL server regarding the DL AIoT App service request
> Collected AIoT device info.
O
Indicates the collected AIoT device information (raw, location, etc.)
> AIoT device tracking info.
O
Indicates tracked trajectory, presence monitoring results of AIoT device info
NOTE: Either Event ID IE or the DL AIoT service request delivery instruction ID is present.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.4 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.11.5 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12 Solution #12: Support of monitoring requests for AIoT devices
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.1.1 General
| This solution addresses the KI#2 and KI#3. Some application servers (e.g. a logistics company) may need to regularly track the location of the AIoT devices (e.g. the goods in the truck) and identify the trajectory or the direction for the AIoT devices depending on their locations, and then send warnings to the AIoT devices in case they deviate the right trajectory/direction.
This solution is proposed to fulfil the above scenario and mainly support the following service requests:
- Monitoring the status (e.g. enable, disable) of requested AIoT devices;
- Monitoring the location of requested AIoT devices;
- Report the location trajectory for the target AIoT devices;
- Report to indicate the target AIoT device is deviating or will deviate the right location trajectory.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.1.2 Procedure of Monitoring requests for AIoT devices
| Figure 7.12.1.2-1 illustrates the high-level procedure of monitoring requests for AIoT devices.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services.
Figure 7.12.1.2-1: Procedure of Monitoring requests for AIoT devices
1. The VAL server sends an AIoT monitoring subscription request to the AIoT enabler, including the monitoring service type (e.g., location), service ID, target area information, target AIoT device information, triggering conditions (e.g., periodic or event triggered reporting), time intervals for periodic reporting, monitoring time duration, AIoT device group member deviation indicator, the group ID for a group of AIoT devices if the AIoT device group member deviation indicator is included, etc.
The AIoT device group member deviation indicator indicates whether and which AIoT device (or type of AIoT devices) is deviating (or will deviate) from other similar devices in a group.
The information about the target AIoT Device(s) may include Filtering Information as described in clause 5.8 of 3GPP TS 23.369[3].
2. The AIoT enabler checks whether the VAL server is authorized to request the AIoT monitoring subscription request, may be based on e.g. the pre-configurations or operator policies.
3. If the request is authorized, the AIoT enabler sends an AIoT monitoring subscription response to the VAL server.
4. The AIoT enabler invokes Nnef_AIoT_Command request to the 3GPP CN periodically as specified in clause 6.2.3 of 3GPP TS 23.369 [3] to obtain the requested AIoT device data including the location information of AIoT devices. The Command type is Read.
5. Upon received the AIoT device data and related location information, the AIoT enabler stores and analyses them based on the AIoT monitoring subscription request. If the subscription request includes the location-related UE group analytics indication, the AIoT enabler may interact with ADAES to obtain the predicated location trajectory and the deviation analytics for the requested AIoT devices as specified in clause 8.15 of 3GPP TS 23.436 [7]. The AIoT enabler will send the obtained AIoT device data to the ADAES and ADAES doesn’t need to sends a data collection subscription request to the Data Producer. Based on the received AIoT device data, the ADAE server sends location-related UE group analytics notifications to the AIoT enabler which may include the predicated location trajectory and the deviation analytics for the group of AIoT devices. The deviation analytics mainly indicate which AIoT device (or type of AIoT devices) is deviating (or will deviate) from other similar devices or the target devices in a group.
6. The AIoT enabler checks if the received location-related analytics in step 5 could meet the service requirements or not. And if not, the step 4 and step 5 may need to be operated repeatedly.
7. The AIoT enabler reports the monitoring results for the requested AIoT device to the VAL server via sending AIoT monitoring notification message. The report may include the AIoT device ID, the location information for the AIoT device, the location trajectory, the predicted location trajectory for the AIoT device, the deviation analytics, the device availability status, etc.
Editor’s note: Whether and how the procedures of AIoT Inventory subscription and AIoT monitoring subscription can be combined or not is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1 for KI#1 for more details.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.12.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13 Solution #13: AIoT Data Processing management
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.1 Solution description
| This solution address key issue#2, and #4 to introduce a solution for AIoT data processing of the network exposured AIoT inventory/command result.
The inventory results in the notification from 3GPP network is further processed and transformed into the application layer interested service events using the provisioned service data.
The figure 7.13.1-1 shows the high-level procedure of AIoT data processing management and event notification.
Pre-conditions:
1. The AIoT task initiate service has been invoked by the AIoT application layer consumer, and the AIoT enabler has initiated the AIoT service request to the 3GPP core network.
Figure 7.13.1-1: AIoT Data Processing management
1. The AIoT enabler server receives the notification(s) with inventory/command result from the 3GPP core network as described in 3GPP TS 23.369 [3].
2. The AIoT enabler processes the network expoured data from step 1 and transforms them into service event based on the provisioned service data and the AIoT taks initiate request previously received. The AIoT service event contains the information of “what AIoT device ID(s)”, “in which area,” and “what happened”. For “what happened”, there are some examples (not limited to) as below:
Type1: AIoT device appearance, the AIoT device is being reported at the service region for the first time;
Type2: AIoT device disappearance, the AIoT device is not being reported during the limited time;
Type3: AIoT device stay, the AIoT device is continuously reported at the same service region;
Type4: AIoT device moving, the AIoT device is reported from different regions.
The reported AIoT device ID is transformed back to the application layer object ID.
Further the AIoT enabler server processes the network expoured data per AIoT service scenario type indicated in the AIoT task initiate service request.
- Inbound or Outbound type: for all the AIoT devices appearance events during the task execution period, compare the objects ID(s) reported from 3GPP network and the objects ID lists from the AIoT tasks. If the ID(s) can match, then, the application objects can be successfully inbound or outbound; otherwise, it is considered an illegal operation and an alert information is triggered.
- Inventory type: for all the AIoT devices appearance and stay events, the corresponding objects can be seen as the normal inventory information. However, for the AIoT devices disappearance event, an alert or other method such as specific AIoT device ID inventory should be initiated.
- Monitor type: for all the AIoT devices appearance, disappearance, moving events, the AIoT device state changed, the AIoT enable layer should record and report.
Editor’s note: The potential overapping between inbound/outbound type and inventory type and how to resolve it is FFS.
3. Report the interested application events to the application layer and the AIoT task is completed.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.2 Architecture Impacts
| This solution introduces AIoT service event notification capability to the AIoT enabler server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.3 Corresponding APIs
| The AIoT service event notification service is introduced.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.13.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 8 Overall evaluation
| This clause will provide evaluation of different solutions.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9 Conclusions
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9.1 General conclusions
| This clause will provide general conclusions for the study.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 9.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA6#68
Skeleton
0.0.0
2025-08
SA6#68
Implementation of the following pCRs approved by SA6:
S6-253714，S6-253636，S6-253751，S6-253638，S6-253639，S6-253752.
0.1.0
2025-10
SA6#69
Implementation of the following pCRs approved by SA6:
S6-254523，S6-254525，S6-254526，S6-254527，S6-254664，S6-254667, S6-254669, S6-254670, S6-254725, S6-254747, S6-254748, S6-254749, S6-254750, S6-254751, S6-254770.
0.2.0
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 1 Scope
| The present document is a technical report which analyses and proposes solutions for the application user (app-user) consent.
The study work is performed in a phased approach. In the first phase, the study identifies and analyse the use cases, it clarifies the related terminology, analyses related industry solutions (e.g., GSMA OPG, CAMARA), it explores the relevant business relationships with a potential impact on the app-user consent end to end solutions.
In the second phase, the technical report provides an analysis of the app-user consent use cases, identifies the key issues, gaps and overlaps for an end-to-end app-user consent 3GPP solution. It covers different possible scenarios with user service experience impacts (up-front, in-flow, etc.), it provides solutions to the identified key issues, evaluates them and concludes on recommended solutions, as well as proposing requirements.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 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] GSMA PRD OPG.02, "Operator Platform: Requirements and Architecture".
[3] CAMARA API "Access and Consent Management", IdentityAndConsentManagement/documentation/CAMARA-API-access-and-user-consent.md at r3.3 · camaraproject/IdentityAndConsentManagement · GitHub.
[4] 3GPP TS 23.501: "System architecture for the 5G System (5GS)"
[5] 3GPP TS 23.502: "Procedures for the 5G System (5GS)"
[6] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS)"
[7] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)"
[8] 3GPP TS 23.288: " Architecture enhancements for 5G System (5GS) to support network data analytics services"
[9] 3GPP TS 33.501: " Security architecture and procedures for 5G system "
[10] 3GPP TS 33.558: "Security aspects of enhancement of support for enabling edge applications"
[11] 3GPP TS 29.503: "5G System; Unified Data Management Services"
[12] 3GPP TS 23.558: "Architecture for enabling Edge Applications"
[13] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs"
[14] 3GPP TS 33.122: " Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs"
…
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 3 Definitions of terms, symbols and abbreviations
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 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].
Application user consent: The agreement of a user/subscriber provided to the API Provider, to allow the API Provider to expose the user’s personal data (subjected to regulations) to the application.
NOTE: The subscriber can be the end-user.
Editor Note: The terms used in the definition user/subscriber, personal data need further clarification.
Exposure platform: implementation consisting of a set of functions supporting a controlled exposure to API consumers of certain underlying capabilities offered by API Provider(s).
NOTE: An exposure platform can be developed leveraging a standardized exposure framework (e.g., CAPIF CCF).
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 3.3 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].
AEF API Exposing Function
ASP Application Service Provider
CSP Communications Service Provider
E-W East West
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4 Use Cases
| 4.1 General
This clause describes relevant use cases where different aspects of app-user consent need to be considered.
It is assumed in all cases that an exposure platform provider is aware of the regulation, and therefore it has internal knowledge (via internal policies, provisioning, etc) which applications and possibly also purposes, require checks on app-user consent data, as part of the overall application authorization process.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.2 Use Case #1: End-to-end basic scenario
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.2.1 Use Case Description
| Preconditions:
• The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
• Alice is an app-user (e.g., for Netflix).
• The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
• Netflix application has an agreement with the Exposure Platform provider B,
• Provider A has an app-user consent management solution for the users that have a subscription with the API Provider, including Alice.
Summary:
An application (e.g., Netflix) requests to access some of the app-user data such as for example location, to determine if the app-user Alice, who is accessing the Netflix application, is allowed to use the Netflix service at her current location.
Description:
• The use case implies an app-user consent check for this specific application context: Application: e.g., Netflix, stated purpose(s): e.g., confirm conditions for providing the service, and the app-user data requested: e.g., app-user’s location data from API Provider domain.
• Assuming the basic scenario, i.e., the app-user consent was already provided by Alice for the above application context, then the response from the Consent Manager of API Provider of Alice (PLMN A) to the Exposure Platform is positive.
• The Exposure Platform provides authorization to Netflix application request, which the application uses further in its service request to the API Provider (PLMN A) to obtain app-user’s location data.
• Once the API Provider (PLMN A) receives the Service Request for Alice’s location data, it can validate with the Exposure Platform of provider B the received authorization data from the Netflix application
• The API Provider (PLMN A) processes the request, but as internal requests in PLMN A’s Core Network get performed in view of obtaining the app-user’s location data, it can be determined (via mechanisms outside the scope of this specification) if a check on the PLMN A’s user consent is required in order to provide the location data between NFs of the Core Network.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.2.2 Use Case Analysis
| As the Exposure platform and the Consent management entity belong to different domains, the interactions for the app-user consent check between the Exposure platform and the Consent management entity require an interoperable, standard interaction.
The app-user consent enabler needs to expose the capability to perform consent check for a given application, stated purpose and the indicated user data.
There can be different scopes for the user consent: the app-user consent for specific user data exposure to applications, and the user consent intended for internal consumption of data by Core Network NFs.
The application user consent capture is defined under the "Consent Capture" term in GSMA PRD OPG.02 [2] and is not the subject of this study.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.3 Use Case #2: Add app-user consent
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.3.1 Use Case Description
| Preconditions:
• The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
• Alice is an app-user for several applications.
• The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
• The ASPs for the applications used by Alice have an agreement with the Exposure Platform provider B.
• API Provider (PLMN A) has an app-user Consent management solution for the users that have a subscription with the API Provider, including Alice. The Consent management solution can be inside or outside the API Provider (PLMN A) domain.
• There is no app-user consent data for Alice in the Consent management of API Provider (PLMN A) for an application that Alice wants to use.
Summary:
Alice was prompted to provide her app-user consent to the API Provider (PLMN A) and she has provided the data.
The Consent Management entity receives the app-user consent data for Alice and for the specific application and persists it for further use.
Description:
• The Consent Capture methods are out of scope.
• The app-user consent data can vary depending on the regional regulations which govern the API Provider (PLMN A) and Alice’s subscription.
• Once Alice has provided her app-user consent data, the Consent Management entity receives the request to add the app-user consent data for the specific app.
• The app-user consent is provided by Alice per application, and optionally subject to API Provider’s policies, also some context for the app-user consent, such as purpose of use by the application and per Alice’s user data to be exposed from API Provider (PLMN A) domain.
• Once the Consent Management entity receives the app-user consent data for Alice, it persists it for further use and until Alice decides to change her app-user consent for that application.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.3.2 Use Case Analysis
| The Consent Management entity has to have the capability to receive for each app-user, their app-user consent data per application, and additional app-user consent context data such as purpose and the user data that is allowed to be exposed to the application.
Consent Management entity has the capability to persist each user’s app-user consent data, until such time when app-user decides to change their current consent data for an application (update of app-user consent data is handled in clause 4.4).
The application user consent capture is defined under the "Consent Capture" term in GSMA PRD OPG.02 [2] and is not the subject of this study.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.4 Use Case #3: Update app-user consent (includes revoke)
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.4.1 Use Case Description
| Preconditions:
• The API provider (PLMN A) is the owner and manager of Alice’s subscription in the API Provider (PLMN A) domain.
• Alice is an app-user for several applications.
• The API provider (PLMN A) has a service agreement with the provider B of the Exposure Platform.
• The ASP for the applications used by Alice have an agreement with the Exposure Platform provider B.
• API Provider (PLMN A) has an app-user consent management solution for the users that have a subscription with the API Provider, including Alice.
• The app-user consent data for Alice was provisioned in the Consent management entity of API Provider (PLMN A) for an application X that Alice wants to use.
Summary:
Alice decided to change her app-user consent for application X.
The Consent Management entity receives the updates to the app-user consent data for Alice and for the specific application X and persists it.
Description:
• The Consent Capture methods are out of scope.
The app-user consent data can vary depending on the regional regulations which govern the API Provider (PLMN A) and Alice’s subscription.
• Once Alice has provided the updates to her app-user consent data for application X, the Consent Management entity receives the updated data and performs the updates of the app-user consent data for the specific app X accordingly. The updates to Alice’s app-user consent data for application X can change the existing data to either provide access, or to revoke it.
• Once the Consent Management entity receives the updated app-user consent data for Alice, it persists it for further use and until Alice decides to change her app-user consent for that application.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.4.2 Use Case Analysis
| The Consent Management enabler has to be able to receive updates of the app-user consent data at any time, whenever the app-user decides to change their current consent data for an application.
The application user consent capture is defined under the “Consent Capture” term in GSMA PRD OPG.02 [2] and is not the subject of this study.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.5 Use Case #4: App-user consent handled by exposure platform
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.5.1 General
| This section describes use case where the applications require app-user consent and the app-user consent is handled by exposure platform.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.5.1 Use Case Description
| This use case illustrates the case of app-user consent data delegated to service providers like exposure platforms. When the API provider is responsible for the user data shared via the exposed APIs, the API provider can delegate the app-user consent capture and management to trusted exposure platforms. The exposure platform provider that exposes the services of the API provider will determine the authorization of the service API invocation based on the app-user consent information available at exposure platform.
An example can be, exposure platforms leveraging CAPIF, can capture and maintain for their API invokers, the app-user consent data for access to specific user data from the API provider, including MSISDN, location data and history, etc.
Certain API providers also expose service APIs where there is dependency on other consents (e.g., from Core network). So, for a given service API exposure, app-user consent and consent from core network might need to be considered for fulfilment of the service API request.
The use case needs to be studied further:
• The flows for the app-user consent checks integrated with exposure platform need to be further clarified, for the different consent scopes and purposes to analyse if any gaps exist as part of the application enablement and exposure platform leveraging flows.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 4.5.2 Use Case Analysis
| This section contains an analysis of the use case and identifies topics for key issues
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 5 Business Relationships
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 5.1 General
| The business relationships between main exposure actors impact on the approach and solutions for handling the application user consent (app-user consent) is not determined. Typical business relationships models used by service and capabilities providers that are considered in the app-user consent analysis are:
• Federation model,
• Aggregator model.
Some common aspects of the federation and aggregator models are:
• allowing an Application Service Provider to use one common interface to access capabilities exposed by multiple service and capabilities providers, subject to an agreement between the ASP and the service and capabilities providers involved,
• providing continuation of use, for application purposes, of the services enabled by the service and capabilities providers, when UEs are moving between mobile networks.
The general assumption is that the ownership and management responsibility for the app-user consent data belongs to the API Provider that owns the subscription under which the user consumes services in the API provider domain.
The business relationships between different exposure partners and the open issues related to their implications on app-user consent are described in the next clauses.
While the exposure platforms and the API Provider can belong to the same or different PLMN domains, the exposure platforms can leverage standardized exposure frameworks (e.g., CAPIF).
Editor’s note: The business models may be updated based on use cases and their main actors.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 5.2 Business relationship: Federation model
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 5.2.1 Description
| The federation business model enables different service and capabilities providers to efficiently leverage exposure platforms from other service and capabilities providers (API providers), establishing an exposure ecosystem partnership.
In the federated model described in GSMA PRD OPG.02 [2], an exposure platform (such as the Operator Platform (OP)):
• facilitates access to the edge networks and other capabilities of an API Provider (PLMN operator), or federation of PLMN operators and exposure partners (per clause 1.1.3 in GSMA PRD OPG.02 [2]),
• allows one exposure partner to access services offered by another exposure partner (subject to a federation agreement between the exposure partners), on behalf of the Application Service Providers that it serves (per clause 2.2.5 in GSMA PRD OPG.02 [2]).
• enables continuation of a UE’s use of the services and capabilities exposed via the exposure platform, such as when moving into a visited PLMN (per clause 2.2.5 in GSMA PRD OPG.02 [2]).
There are different cases of federation, such as:
• federated platforms interworking in an East-West approach (CAPIF interconnect is an example). This case is depicted in figure 4.2-2 below.
Figure 5.2-1: Business relationships in Federation model B (interconnect)
Editor’s Note: Additional federation business relationships to be considered.
5.3 Business relationship: Aggregator model
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 5.3.1 Description
| ASPs target simplification not only at API level, but also in eliminating the need to implement variations and customizations to multiple exposure platform (e.g., Operator Platform (OP)) providers and to API providers, as well as to establishing many individual business relationships.
To simplify their business relationships model, the ASPs establish a business relationship with an aggregator, and in turn the aggregator sets up all the necessary individual business relationships with multiple exposure platform providers and API providers (e.g., PLMN operators).
In this model, the ASP reaches applications users across many API providers and countries, transparently, via the aggregator. The exposure platform providers need to provide enough information to the aggregator, so that the aggregator can identify the right home PLMN for a user, as well as a target network e.g., when roaming.
Figure 5.3-1: Business relationships in Aggregator model
An exposure platform provider, same as the API provider, can establish business relationships with multiple aggregators to widen their exposure and reach to more ASPs.
|
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 6 Terminology
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 6.1 Background
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 6.2 Related industry specifications
| |
3cbb5d7131c3fdded478ddbec9c7a872 | 23.700-42 | 6.2.1 General
| Various specifications tackling the consent obtained or provided by a subscriber have used specific terminology to refer to the subscriber consent, provided to a network service provider. This clause collects the different terms used and studies the differences in meaning, with the goal to clarify what the terms refer to in their industry documentation contexts.
6.2.2 Industry group #1: GSMA OPG
The GSMA PRD OPG.02 [2] defines the term "Consent" as "The agreement of a Subscriber to allow the usage of their personal data. This agreement can be revoked at any time", with the clarification in Annex F "Privacy Management considerations" that the terms "Consent" and "Application-related Consent" are interchangeable in the PRD.
• In clause 4.3.6.1.3 "Managing Consent" of GSMA PRD OPG.02 [2] the Operator Platform (OP) shall be able to "receive notifications when a Subscriber revokes Consent via NBI". This implies that some capabilities are expected, such as providing subscription and notification mechanisms for app-user consent data changes.
• The process of Consent Capture is also described in GSMA PRD OPG.02 [2], which specifies that the mechanism for interacting with the end-user for consent capture are left to the CSP.
6.2.3 Industry group #2: CAMARA
The CAMARA API Access and User Consent Management have been published with following terms in the API documentation:
• "Consent: an explicit opt-in action that the User takes to allow processing of personal data. Consent grants a Legal Entity (e.g. the Operator or ASP) access to a set of Scopes related to the Resource Owner, for a specific Purpose. "
• "Purpose: The reason for which Personal Data will be processed by an Application. For example, an Application might want to create a movie recommendation for an End-User using their Personal Data, such as age or gender. CAMARA defines a standard set of Purposes which can be used by Applications to specify the reason for their intended Personal Data processing. "
• "Scope: the OpenID Connect scope which maps one or more protected resources, some scopes may require processing of Personal Data."
There are several distinct procedure flows for the consent management interactions in CAMARA API "Access and User Consent Management" [3], all describing interface interactions between two entities called "API Explosure Platform" and the "Consent Master" to allow the "API Explosure Platform" to perform a "check consent" with the "Consent Master".
While the term definition for Consent is generically worded and it does not explicitly state its focus on applications, the flows depict always an Application making the authentication and authorization requests. Based on this, it can be inferred that the scope of the CAMARA API "Access and User Consent Management” apply to the user consent provided for applications.
Based on the flow interactions, the "check consent" is a required operation to be supported.
6.2.4 Industry group #3: 3GPP
No term definition for user consent, or for consent, was found in the 3GPP specifications studied.
In SA3, there are two related terms that are used for different purposes:
• User consent:
◦ covers Core Network data shared to NFs or to the Edge applications.
◦ Requirements and procedures are defined in Annex V of 3GPP TS 33.501 [9]. User consent data is managed and stored in UDM.
◦ Requirements are defined on the NFs that are an enforcement point for the user consent in Annex V.3 of [9], as well as additional requirements on NWDAF in Annex X.7 of [9].
◦ For edge applications, 3GPP TS 33.558 [10] reuses the same procedures by referencing 3GPP TS 33.501 [9] (Annex V). Either EES or the NEF act as the consent enforcing entity of the user consent for the edge applications.
• RO authorization:
◦ has a definition in 3GPP TS 33.122 [14] in context of RNAA:
"Resource owner authorization: The permission provided by the resource owner to allow the API invoker to access the resource owner’s resource via the northbound API."
◦ It covers the resource owner (subscriber) agreement, to expose over northbound APIs, specific user data from API Provider domain to applications.
Several SA2 specifications mention user consent, but no definition of the term is provided. In the procedures, the user consent data is in UDM/UDR and is accessed and enforced by Core Network NFs: EIF in 3GPP TS 23.501 [4], NEF in 3GPP TS 23.502 [5], LMF, NWDAF in 3GPP TS 23.288 [8], and Location functions in 3GPP TS 23.273 [6] and 3GPP TS 23.271 [7].
The CT4 specification 3GPP TS 29.503 [11] defined in clause 6.1.6.3.20 “Enumeration: UcPurpose” the user consent ennumeration values that are stored in UDM, which can be consumed by e.g., NFs and trusted AF:
• "ANALYTICS": User consent for analytics
• "MODEL_TRAINING": User consent for model training
• "NW_CAP_EXPOSURE": User consent for network capability exposure.
• "EDGEAPP_UE_LOCATION": User consent for the manipulation of UE information for the purpose of UE Location retrieval by the EDGEAPP EAS entity.
SA6 specifications have introduced user consent aspects in:
• CAPIF 3GPP TS 23.222 [13] under RNAA, which includes the user consent for applications under the term RO authorization defined in 3GPP TS 33.122 [14].
Also in CAPIF 3GPP TS 23.222 [13] it is stated in clause 6.2.3. in NOTE 4:
"The authorization information from the resource owner used by CCF (described in 3GPP TS 33.122 "[14] ") is independent from the user consent information used from user subscription data at UDM/UDR (described in Annex V of 3GPP TS 33.501"[9] "). In the current release of 3GPP specifications, no synergy between CCF and UDM is specified."
• EDGEAPP 3GPP TS 23.558 [12] has user consent for edge applications, referencing 3GPP TS 33.558 [10] and 3GPP TS 33.501 [9] (Annex V). A summary of the user consent for edge applications is provided in Table 6.2-2 below.
For reference, a summary of the user consent purpose and specifications indicating consent handling in the above 3GPP SA6 EDGEAPP specification is in Table 6.2-1 below.
Table 6.2-1: SA6 EDGEAPP user consent summary
User Consent purpose
(per 3GPP TS 23.558 [12])
User Data
(subjected to consent)
Enforcer
User Consent management
Generally per each AF/ app
UE Location
- clause 8.14.2.3
LMF, NEF (via enforcing the OAuth token scope)
UDM
(referred in SA3 3GPP TS 33.558 [10] and 3GPP TS 33.501 [9])
EDGEAPP (per app/AF)
GPSI (MSISDN)
- clause 7.2.6
EES
(clauses 6.3.2; 8.5.2.2)
UDM
EDGEAPP (per app/AF)
UE tunnel e2e info (security) – clause 8.3.3.2.2
EES
(clauses 6.3.2; 8.5.2.2)
UDM
EDGEAPP (per app/AF)
AF specific UE identifier (MSISDN) – clause 8.6.5.2
EES
(clauses 6.3.2; 8.5.2.2)
UDM
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.