hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.6.2.4 Notification of host UAV dynamic information
| Pre-conditions:
- UAS Application Specific Server has performed subscription as per procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] with UAE server 1.
- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3 in 3GPP TS 23.255 [4].
Figure 6.6.2.4: Notification for host UAV dynamic information
1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UAS Application Specific Server and/or to the subscribed UAE client of the host UAV). The UAE server can aggregate the dynamic information obtained by sensing and other methods. The notification includes the aggregated information of all the objects in the application defined proximity range of the host UAV and the location of the host UAV.
2. The UAS Application Specific Server or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client.
Editor's note: How to define objects in the notification message is FFS. It may be associated to an UAV identity or not.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7 Solution #6: Sensing based DAA service
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.1 Solution description
| This solution intends to solve the second open issue of key issue #2, i.e. enhance DAA service by utilizing sensing results. This solution is based on the procedures in clause 7.7.2 of 3GPP TS 23.255 [4].
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.2 Procedures
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.2.1 Configuration of sensing based DAA policies to the UAE layer
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.2.1.1 Management of DAA support configuration
| Figure 6.7.2.1.1-1 illustrates the DAA support management procedure where the UAE server receives an application request for managing the DAA application policy from the UAS application specific server.
Pre-conditions:
1. The UAV has received its UAS ID from the UAS application specific server.
2. The UAV has performed the UAS UE registration procedure.
Figure 6.7.2.1.1-1: DAA support management procedure
1. The UAS application specific server sends to the UAE server a DAA support management request. The request includes the UAV (UAE client) identifier and the DAA application policy. If the procedure is for LDGS assisted DAA, then the request may include a list of UAE client identifiers (LDGS IDs) and/or geographical area so UAE server may select the relevant UAE client(s). The DAA application policy includes parameters for the control of LDGS assisted DAA. DAA application policy could includes parameters for the control of sensing assisted DAA.
2. The UAE server shall send to the UAS application specific server a DAA support management response with a positive or negative acknowledgement of the request.
3. The UAE server shall timestamp and store the DAA application policy and execute the DAA configuration according to clause 7.7.2.1.2 and sensing based DAA support configuration procedure according to clause 6.7.2.1.2 if DAA application policy include parameter for the control of sensing assisted DAA.
4. After execution of DAA configuration, the UAE server shall send a DAA support management complete to the UAS application specific server.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.2.1.2 Sensing based DAA support configuration procedure
| Figure 6.7.2.1.2-1 illustrates the sensing based DAA support configuration procedure. This procedure enables the configuration of the UAE server, based on a request from UAS application specific server to configure the sensing based DAA application policy.
Pre-conditions:
1. UAE server has performed the DAA support management procedure according to clause 6.7.2.1.1.
Figure 6.7.2.1.2-1: Sensing based DAA support configuration procedure
1. The UAE server obtains and initiates tracking the UAV location from the location management server as speicified in 3GPP TS 23.434.
2. The UAE server determines the dynamic area for sensing based on the location of the UAV and the sensing based DAA application policy.
3. The UAE server sends request and obtain sensing results of the area determined in Step 2.
4. The UAE detects UAVs in approaching based on the obtained sensing results and sensing based DAA application policy.
Editor’s Note: how to request and obtain sensing results depends on SA2.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.7.2.2 Sensing based DAA event reporting
| Figure 6.7.2.2-1 illustrates the procedure of sensing based DAA event reporting.
Pre-conditions:
1. UAE server has detected UAVs in approaching as specified in 6.7.2.1.2.
Figure 6.7.2.2-1: Sensing based DAA event reporting
1. The UAE server shall send a sensing based DAA event information to the UAS application specific server with information about one or more UAVs in approaching as detected and the corresponding timestamp.
2. The UAS application specific server provides a sensing based DAA event information acknowledge to the UAE server.
Editor’s Note 1: UAE server how to consider sensing based detection result and other detection methods jointly to determine DAA event is FFS
Editor’s Note 2: The message name of sensing based DAA event information report depends on what information is used to trigger the report and it is FFS
6.8 Solution #7: Sensing Coverage Information Exposure for Supporting UAV Services
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.1 Solution Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.1.0 General
| The Spatial Map Server can benefit from sensing (including 3rd Party sensing services) data or results to build high-quality Spatial Map.
As sensing capabilities rely on the CSP’s infrastructure, which may provide full coverage. And the rollout of the CSP’s sensing service takes time, coverage remains incomplete during the deployment phase. Given that sensing capabilities are critical for the safety of UAVs and automotive systems, comprehensive sensing coverage information is essential for these sectors to develop robust services and ensure operational safety. Currently, there is no mechanism for CSP to expose the sensing coverage information.
The following clauses specify sensing coverage information exposure for supporting UAV services.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.1.1 Procedure
|
Figure 6.8.1.1-1: Sensing coverage information exposure
1. The Consumer (VAL Server, SEAL Server) sends check sensing coverage information request to the SEAL Sensing Server.
2. The SEAL Sensing Server authenticates the request, checks the stored sensing coverage information, and determines the next actions (e.g., to collect sensing coverage information from sensing entities).
3. The SEAL Sensing Server responds to the VAL server for the check sensing coverage information request.
Editor’s Note: Whether the SEAL sensing server gets initial sensing coverage information from CN between 3 and 4, will be decided based on the stable conclusion of SA2.
4. The SEAL Sensing Server interacts with the 3rd party sensing server(s) to collect the sensing coverage information of the 3rd party sensing data.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
5. The SEAL Sensing Server aggregates the sensing coverage information from different sensing entities received in step 4.
6. The SEAL Sensing Server sends check sensing coverage information response to the VAL server with the aggregated sensing coverage information.
Editor’s Note: Further changes to this procedure are FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.1.2 Information Flows
| Editor’s Note: The information flows of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.8.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
6.9 Solution #8: Use Sensing Results for Creating Spatial Map
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.1 Solution Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.1.0 General
| The Spatial Map Server can benefit from sensing (including 3rd Party sensing services) data or results to build high-quality Spatial Map.
The following clauses specify use combination of sensing results for creating spatial map.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.1.1 Procedure
|
Figure 6.9.1.1-1: Sensing results for creating spatial map
1. The Spatial Map Server sends sensing result request for consolidated sensing results from the SEAL Sensing Server.
2. The SEAL Sensing Server authenticates the request, and determines the sensing entities (e.g., 5GC NFs, 3rd party sensing server) for collection of sensing data.
3. The SEAL Sensing Server responds to the SM server for the sensing result request.
4. The SEAL Sensing Server interacts with the NEF to collect the sensing result measured by the 3GPP network. The SEAL Sensing Server determines whether the sensing result fulfils the request from the consumer provided in step 1, and determines whether additional sensing data is needed to enhance the sensing result.
5. The SEAL Sensing Server interacts with the 3rd party sensing server to collect third party sensing data measured.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
6. The SEAL Sensing Server consolidates the sensing data/results from different sources in steps 4-5 to generate sensing result (e.g. draft spatial map).
7. The SEAL Sensing Server sends sensing result response to the SM server with the consolidated sensing results.
8. The Spatial Map Server creates spatial map based on the consolidated sensing result.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.1.2 Information Flows
| Editor’s Note: The information flows of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.9.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.10 Solution #9: high level architecture and procedures for use of sensing results for spatial map
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.10.1 Description
| This solution resolves solution of KI#3 on use of sensing results for spatial maps.
This solution is based on following principles:
1. No significant changes are made to the spatial map management procedures defined in 3GPP TS 23.437 [8];
2. A separated SEAL Sensing service server is provided by Enabler layer and interacts with Spatial Map server via a new SEAL-X interference.
The functional model for the SEAL Sensing server is based on the generic functional model specified in clause 6 of 3GPP TS 23.434 [4] and the generic architecture of sensing service concluded in this study. The functional model enhanced to Spatial map for this solution is illustrated in Figure 6.10.1-1.
Figure 6.10.1-1: On-network spatial map functional model for use of sensing
NOTE: In this solution, SEAL SM client/server in the architecture and procedures refer to SEAL Spatial Map client/server specified in 3GPP TS 23.437 [8].
This solution contains two basic procedures:
1. Create spatial map with sensing capabilities.
2. Spatial map subscription and notification with sensing capabilities.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.10.2 Procedures
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.10.2.1 Create spatial map with sensing capabilities
| Figure 6.10.2.1-1 below illustrates the procedure for creating a spatial map when sensing capabilities are introduced. For the request from VAL server or SEAL SM client, as a spatial map consumer. SEAL SM server creates a spatial map by utilizing sensing capabilities provided by SEAL Sensing server.
Pre-conditions:
1. The VAL Server or SEAL SM client is authorized to use APIs provided by the SEAL SM server.
2. The SEAL SM server can interact with SEAL Sensing server via SEAL-X interface.
3. The SEAL Sensing server is authorized to use Sense ing related capability APIs provided by sensing related function in the 3GPP core network or authorized to use the NEF exposed Sense ing related capability.
NOTE: In this solution, it is assumed that neither the VAL Server nor the SEAL SM Server has sufficient knowledge to understand the detailed use of sensing-related capabilities/parameters provided by the 3GPP core network, whether directly or via the NEF. Alternatively, If the VAL Server/SEAL SM Server knows that sensing service can be provided by SEAL sensing server, the VAL Server/SEAL SM Server may include a sensing indicator in the request. If so, the SEAL SM server will use the sensing indicator to decide whether to utilize sensing capabilities.
.
Figure 6.10.2.1-1: Create spatial map procedure
1. The requester (e.g., VAL server or SEAL SM client) sends a Create Spatial Map Request message to the SEAL SM server to create a spatial map. The request includes the same IEs as specified in clause 9.3.1.3.1 of 3GPP TS 23.437 [8].
2. The SEAL SM server decides to utilize sensing capabilities to assist the creation of the spatial map based on local policy. If SEAL SM server decides to utilize sensing capabilities, it sends a Get Sensing Results Request to SEAL Sensing server. The request includes requester ID, security credentials and three-dimensional area of interest.
Editor’s note: the detailed IEs included in the Get Sensing Result Request is FFS.
3. The SEAL Sensing server sends a Sensing Service Request either directly to a sensing-related function in the 3GPP core network or to this function via the NEF (e.g., using the Nnef_Sensing_Subscribe service operation). The request includes the Target Sensing Area information. This information is derived from a three-dimensional area of interest and can be handled by 3GPP core network.
Editor’s note: the Sensing Service Request may be used to trigger the sensing service provided by 3GPP core network, or used to request the sensing result. How the SEAL sensing server utilizes the sensing service will be based on SA2 progress and is FFS.
4. The sensing-related function in the 3GPP core network sends the Sensing Service Response either directly to the SEAL Sensing server or via the NEF. The response includes the sensing result (with or without the sensing contextual information).
Editor’s note: the detailed IEs included in the step 3 and step 4 are based on the output of SA2 and are FFS.
5. The SEAL Sensing server sends the Get Sensing Result Response to the SEAL SM server. The response includes the List of objects information in the Area of interest obtained from the sensing service.
6. The SEAL SM server creates the spatial map as per step 2 in clause 9.3.1.2 of 3GPP TS 23.437 [8]. In this step, the processed sensor data may be sourced from step 5 instead of the VAL layer.
7. The SEAL SM server sends response message to the requester as per step 3 in clause 9.3.1.2 of 3GPP TS 23.437 [8].
8. If the response in step 7 indicates "in-progress", the SEAL SM server notifies the requester with the spatial map ready notification message as per step 4 in clause 9.3.1.2 of 3GPP TS 23.437 [8].
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.10.2.2 Spatial map subscription and notification with sensing capabilities
| Figure 6.10.2.2-1 below illustrates the procedure for Spatial map subscription and notification with sensing capabilities. It is based on the Subscribe spatial map event specified in clause 9.3.6.2.1 of 3GPP TS 23.437 [8] and Notify spatial map event specified in clause 9.3.6.2.2 of 3GPP TS 23.437 [8].
Pre-conditions:
1. The VAL Server or SEAL SM client is authorized to use APIs provided by the SEAL SM server.
2. The SEAL SM server can interact with SEAL Sensing server via SEAL-Xsensing interface.
3. The SEAL Sensing server is authorized to use Sense ing related capability APIs provided by sensing related function in the 3GPP core network or authorized to use the NEF exposed Sense ing related capability.
Figure 6.10.2.2-1: Create spatial map with periodic update notification procedure
The following step 1 to step 8 are Spatial map subscription procedure.
1. The VAL server (or SEAL SM client) sends a Subscribe Spatial Map Event Request to the SEAL SM server to subscribe spatial map event.. The request includes the same IEs as specified in clause 9.3.6.2.1 of 3GPP TS 23.437 [8].
2. The SEAL SM server processes the Subscribe Spatial Map Event Request as per step 2 in clause 9.3.6.2.1 of 3GPP TS 23.437 [8]. If the "Change of objects event" is subscribed by requester (VAL server or SEAL SM client), the SEAL SM server may subscribe the Sensing Results from SEAL Sensing server.
3. The SEAL SM server sends a Get Sensing Results Subscription Request to SEAL Sensing server. The request includes requester ID, security credentials, and may include one or more IEs in the Target spatial map(s) and/or List of events.
Editor’s note 1: the detailed IEs included in the Get Sensing Result Request is FFS.
4. The SEAL Sensing server processes the Sensing subscription for this Get Sensing Results Subscription Request.
5. The SEAL Sensing server sends a Sensing Service Request either directly to a sensing-related function in the 3GPP core network or to this function via the NEF (e.g. Nnef_Sensing_Subscribe service). The request may includes:
a. the Target Sensing Area information. This information is derived from the Target spatial map(s) (e.g. Area of interest) and can be handled by 3GPP core network.
b. If periodic or event triggered sensing result notification is supported by the 3GPP core network, the SEAL Sensing server may also utilize them based on the Notification intervals included in the List of events.
c. If Detection or Tracking specific object is supported by the 3GPP core network, the SEAL Sensing server may also translates the information included in the specified objects IE in the List of events to a list of IDs that can be handled by the 3GPP core network and includes them in this Sensing Service Request.
Editor’s note 2: the Sensing Service Request may be used to trigger the sensing service provided by 3GPP core network, or used to request the sensing result. How the SEAL sensing server utilizes the sensing service will be based on SA2 progress and is FFS.
6. The sensing-related function in the 3GPP core network sends the Sensing Service Response either directly to the SEAL Sensing server or via the NEF.The response indicates the result of Sensing Service subscription.
Editor’s note 3: the detailed IEs included in the step 5 and step 6 are based on the output of SA2 and are FFS.
7. The SEAL Sensing server sends a Get Sensing Results Subscription response to the SEAL SM server to indicate the result of Sensing Results Subscription.
8. The SEAL SM server sends a Subscribe Spatial Map Event Response to the VAL server (or SEAL SM client) as per step 3 in clause 9.3.6.2.1 of 3GPP TS 23.437 [8].
The following step 9 to step 12 are Spatial map notification procedure.
9. The SEAL Sensing server detects a sensing event that requires the use of sensing capabilities, e.g. a specific time, then the SEAL Sensing server interacts with 3GPP core network to get the sensing result. The interaction may be also based on the information included in the Get Sensing Results Subscription Request, e.g. if periodic notification is required, the 3GPP core network may notify the sensing result to the SEAL Sensing server periodically.
10. The SEAL Sensing server sends a Sensing Event Notification to the SEAL SM server. This notification includes the information obtained from step 9.
11. The SEAL SM server sends a Spatial Map Event Notification to the requester as per step 2 in clause 9.3.6.2.2 of 3GPP TS 23.437 [8].
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.11 Solution #10: Sensing results for spatial maps
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.11.1 Solution description
| This solution addresses Key Issue #3, open issues #2 and #4 on how the sensing enabler layer can support SM server with creating a spatial map and to associate a sensing result with an object in a spatial map. The solution proposes enhancements to Create spatial map and Update spatial map procedures in 3GPP TS 23.437 [8].
The enhancements enable a VAL server or SM client to specify a sensing service policy when requesting to create or update a spatial map. The SM server uses the information in the sensing service policy to send requests to a sensing service to obtain objects for the area of interest. Within the sensing service policy, there are sensing configuration parameters the SM server can use for sending the requests to the sensing service. An Object label classification policy is provided to enable the SM server to label sensing results received from the sensing service with object IDs.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.11.2 Procedures
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.11.2.1 Impact to Create spatial map procedure
| The Create spatial map procedure and information flows in 3GPP TS 23.437 [8] are enhanced (highlighted in bold italics) as follows.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.1.2 Procedure
| Figure 9.3.1.2-1 depicts the procedure for creating a spatial map. For the request from VAL server or SEAL SM client, as a spatial map consumer, SEAL SM server creates a spatial map. A spatial map can be structured in layers where each layer signifies a specific aspect of the spatial information (e.g. three dimensional space of area of interest, objects).
Figure 9.3.1.2-1: Create spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to create a spatial map. The request includes requestor ID, security credentials, three-dimensional area of interest, information to be included in the spatial map such as allowed entities list defining which entities are permitted to discover and access the spatial map. The request may include spatial map layering information parameters and may also include augmented layer information that can be requested with the spatial map. The request may include a required media format for the spatial map. A sensing service policy may be provided to configure the SM server to use a sensing service to obtain object information for the spatial map.
NOTE: SEAL SM server can obtain augmented layer information and can provide the obtained augmented layer information to the requestor in the response message.
2) The SEAL SM server authorizes the requestor, and validates the request. The SEAL SM server produces a requested spatial map using layering information and processed sensor data, according to the requested spatial map media format. The SEAL SM server does not create a spatial map if the requested spatial map media format is not supported and can create a spatial map based on local configuration if no spatial map media format is included in the request.
a) If the augmented layer information indicates to include VAL UE information, the SEAL SM server fetches the list of VAL UEs in the area of interest from LM server using clause 9.3.10 of 3GPP TS 23.434 [4] and/or from NEF as specified in 3GPP TS 23.502 [5].
b) If the augmented layer information indicates to include spatial anchors information within area of interest, the SEAL SM server fetches the list of spatial anchors in the area of interest as specified in clause 8.3.4.
c) If a sensing service policy is provided, the SM server triggers a sensing service to obtain object information using information in the sensing service policy.
NOTE: Processed sensor data is stored at the VAL layer (e.g., in database at VAL layer) or within the SM server (e.g., when sensing service policy is provided). When processed sensor data is stored at the VAL layer, the SEAL SM server gets access to such database to create a spatial map via application specific way which is out of scope. When processed sensor data is stored within the SM server, the SM server will use the sensing service policy to configure and manage sensing service(s) to obtain object information for the spatial map. ML models are used to derive object information from sensing results and the object information is saved within the SM server.
Editor’s Note: The procedure of triggering of sensing service by the SM server is FFS.
3) The SEAL SM server sends response message to the requestor with a indication of success, in-progress or fail. If the requested spatial map has been created sussesfully, the response message includes assigned spatial map ID and information which includes three-dimensional space defined by the spatial map and can include a list of spatial map layers with their corresponding layer ID, objects belong to the layer, etc.. If the response indicates "in-progress", an assigned spatial map ID is included in the message. Further, if the response indicates "in-progress" and the requestor has not provided a notification target address, then the requestor subscribes for spatial map event to receive notification when the spatial map is created. Otherwise, the response includes an indication of failure and may include a reason for the failure and indication of supported spatial map media formats if the failure is related to an unsupported spatial map media format.
4) If the response indicates "in-progress", the SM server detects when the SEAL SM server has sufficient information to map all the objects related to area of interest and the spatial map is ready to provide service (e.g. employed for localization). If the requestor has provided a notification target address in the request or has subscribed for spatial map events, the SEAL SM server notifies the requestor with the spatial map ready notification message. The notification includes parameters as specifed in Table 9.3.6.3.3-1.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.1.3 Information flows
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.1.3.1 Create spatial map request
| Table 9.3.1.3.1-1 descibes the information elements from VAL server (or SEAL SM client) to SM server for create spatial map request.
Table 9.3.1.3.1-1: Create spatial map request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Area of interest
M
Three-dimensional area information to produce the spatial map
Notification Target Address
O
Notification target address (e.g. URL, URI, IP) where the notifications should be sent.
Spatial map media format
O
The media format requested for the spatial map.
Information to include
O
Information to be included in the spatial map
> Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover and access the spatial map
> List of spatial map layers
O
List of spatial map layer information. Each element includes the information described below.
>> Spatial map layer information
O
Information to specify the corresponding spatial map layer specific information
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_USERS;
- SPATIAL_ANCHORS.
Sensing service policy
O
A policy to provide configuration parameters for the SM server to trigger sensing service to obtain object information for the spatial map. The contents of the policy is described in Table 9.3.1.3.1-y.
NOTE 1: For the current release, the spatial map layer information is implementation specific and out of scope.
Table 9.3.1.3.1-y: Sensing service policy
Information element
Status
Description
Sensing service policy ID
M
The identifier of the sensing service policy.
Sensing service provider IDs
O
The identifier of the sensing service providers the SM server should use to trigger sensing service.
Sensing area
O
Three-dimensional area information of the sensing area.
Sensing resolution
O
A resolution to provide to the sensing service.
Sensing schedule
O
A schedule to trigger sensing service.
Sensing refresh interval
O
An interval to refresh SM object information provided by a sensing service.
Sensing output requirements
M
A listing of object characteristics required from the sensing service. Object characteristics describes the size, shape, orientation, speed, and absolute and relative location of an object obtained from sensing service.
Object label classification policy
O
A policy to assist with the labeling of sensing results obtained from the sensing service. The policy provides e.g. a list of ML models that derives object information from sensing results received by the SM server.
NOTE 2: Sensing service policy values are within the range defined in Table 9.3.1.3.1-1.
Editor's Note: Whether the Object label classification policy IE is included in the sensing service policy is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.11.2.2 Impact to Update spatial map procedure
| The Update spatial map procedure and information flows in 3GPP TS 23.437 [8] are enhanced (highlighted in bold italics) as follows.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.4 Update spatial map
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.4.1 General
| The update spatial map procedure enables the consumers to request the SEAL SM Server to update a spatial map.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.4.2 Procedure
| Figure 9.3.4.2-1 depicts the procedure to update the spatial map. For the request from the spatial map consumer (VAL server or SEAL SM client), SEAL SM server updates the spatial map as requested.
Figure 9.3.4.2-1: Update spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to update a spatial map. The request includes requestor ID, security credentials, spatial map ID, information on what to update such as updated spatial map layering information and updated spatial map coverage area. As a part of update, the request may include augmented layer information (e.g., VAL users, spatial anchors). The request may include a list of UE-object association information for the SEAL SM server to identify associations between UEs and objects in a spatial map. A sensing service policy may be provided to configure the SM server to use a sensing service to obtain object information for the spatial map.
2) The SEAL SM server authorizes the requestor and validates the request. The SEAL SM server updates the spatial map as requested. If a sensing service policy is provided, the SM server triggers a sensing service to obtain object information with the information in the sensing service policy.
Editor’s Note: The procedure of triggering of sensing service by the SM server is FFS.
3) The SEAL SM server sends response message to the requestor with result of the request and updated spatial map information with the spatial map ID. SEAL SM server may include the requested augmented layer information in the response message.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.4.3 Information flows
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9.3.4.3.1 Update spatial map request
| Table 9.3.4.3.1-1 descibes the information elements for update spatial map request from VAL server or SEAL SM client to SEAL SM server.
Table 9.3.4.3.1-1: Update spatial map request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Spatial map ID
M
ID of the spatial map to update
Spatial map update information
M
The spatial map Information to update as described in described in Table 7.3.3.1-1. Only IEs which need to be updated are included.
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_UE;
- SPATIAL_ANCHORS.
List of UE-object association information
O
List of UE-object association information to identify associations between UEs and objects in a spatial map as described in Table 7.3.3.x-1.
Sensing service policy
O
A policy to provide configuration parameters for the SM server to trigger sensing service to obtain object information for the spatial map. The contents of the policy is described in Table 9.3.1.3.1-y.
NOTE: At least one of the information elements shall be provided.
6.12 Solution #11: Use Sensing Results to Enhance HD Map for V2X Services
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.1 Solution Description
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.1.0 General
| Sensing plays an important role in smart transportation. Most modern cars are equipped with onboard sensors – radar, lidar, and cameras just to mention a few – which help the car to get an overview of its immediate surroundings. However, onboard systems fail to provide information further away and cannot “see around the corner”. An sensing system can complement onboard sensory data with more “global” data that cannot be obtained by sensors mounted on the vehicle. Another automotive-related example is the detection of pedestrians or animals on highways.
Application enablement layer can aggregate the sensing demands of a large number of vehicles, enabling unified subscription to sensing data from different sensing entities. By tracking or predicting vehicle locations in real time, this layer transforms the geographically scoped sensing data into a vehicle-centric dynamic view, and simplifies the vehicle's data consumption process and significantly enhances processing efficiency and system responsiveness.
The following clauses specify use sensing results to enhance HD map for supporting V2X services.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.1.1 Procedure
|
Figure 6.12.1.1-1: Sensing result subscription for enhance HD map
1. The Consumer (e.g., VAL server/client, VAE server/client) sends sensing result subscription request to the SEAL Sensing Server for device-centric sensing result. The request contains the context information, e.g. planned route of the vehicle.
2. The SEAL Sensing Server authenticates the request, checks the stored sensing data, and determines the next actions (e.g., to collect sensing data from sensing entities, to collect device location information/analytics, to generate device-centric sensing result).
3. The SEAL Sensing Server responds to the VAL server for the sensing result subscription request.
4. The SEAL Sensing Server interacts with the 5GC NF (e.g. NEF) for receiving notifications with the sensing data from the 3GPP network. The SEAL sensing server determines whether the sensing result fulfils the request from the consumer provided in step 1, and determines whether additional sensing data is needed to enhance the sensing result.
5. The SAE Server interacts with the 3rd party sensing server for receiving the sensing data from the 3rd party sensing data.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
6. After receiving the sensing data from the sensing entities in steps 4-5, the SEAL Sensing Server interacts with the other SEAL servers for collection of location information/analytics (e.g., LMS for device location information, ADAES for device location analytics).
7. The SEAL Sensing Server filters the sensing data and location information/analytics, to generate device-centric sensing results.
8. The SEAL Sensing Server sends sensing result subscription notifications the Consumer with the generated device-centric sensing results.
9. The Consumer may use the sensing result for e.g., create/update HD map.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.1.2 Information Flows
| Editor’s Note: The information flows of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 6.12.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 7 Deployment scenarios
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 7.1 General
| This clause will provide a general description of the deployment scenarios.
7.x Deployment model #x: <Title>
Provide a description of the deployment scenarios.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 8 Business Relationships
| Provide a description of the involved business relationships.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9 Overall evaluation
| This clause will provide evaluation of different solutions.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10 Conclusions
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10.1 General conclusions
| This clause will provide general conclusions for the study.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10.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
S6-253520
Skeleton
0.0.0
2025-09
SA6#68
Implemented the following pCRs, S6-253521,S6-253522,S6-253723,S6-253759,S6-253760,S6-253776
0.1.0
2025-10
SA6#69
Implemented the following pCRs,S6-254617, S6-254779, S6-254736, S6-254623, S6-254737, S6-254679, S6-254756, S6-254681, S6-254682, S6-254790, S6-254781, S6-254739, S6-254686
0.2.0
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 1 Scope
|
The present document is a technical report which identifies the architecture requirements and related functionalities to support the Ambient IoT services in the application enabled layer.
The aspects of the study mainly include enriching the processing of the collected Ambient IoT devices data exposed from other working group (e.g. SA2), providing the value-added Ambient IoT device information to the consumers and monitoring the Ambient IoT devices to minimize the service interruption (e.g. inform the application server the AIoT device has been disabled in time).
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.369: "Service requirements for ambient power-enabled IoT, Stage 1".
[3] 3GPP TS 23.369: "Architecture support for Ambient power-enabled Internet of Things, Stage 2".
[4] 3GPP TR 23.700-30: "Study on Architecture support of Ambient power-enabled Internet of Things (AIoT); Phase 2”.
[5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[6] 3GPP TS 23.542: "Application layer support for Personal IoT Network".
[7] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service".
[8] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 3 Definitions of terms, symbols and abbreviations
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP 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 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
<ABBREVIATION> <Expansion>
AIoT Ambient IoT
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4 Architectural Assumptions and Principles
| This clause will document any architectural assumptions and principles.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.1 Architectural Assumption
| [AA-4.1-a] The architecture for the AIoT services in the application enablement layer should align with the network architecture for the AIoT services which specified in clause 4 of 3GPP TS 23.369 [3].
[AA-4.1-b] The architecture for the AIoT services in the application enablement layer should take the API framework as specified in 3GPP TS 23.222 [823222] as a baseline.
4.2a Provisioning management requirement
4.2a.1 Description
This clause specifies the requirements of AIoT service provisioning management from AIoT application layers to the AIoT enabler layers.
4.2a.2 Requirements
[AR-4.2a.2-a] The AIoT enabler layer shall support the provisioning of application object data, application service region, service scenario, interested service events to the AIoT enabler layer.
4.3b Event report requirement
4.3b.1 Description
This clause specifies the requirements of service event report from the AIoT enabler layer to the AIoT application layers.
4.3b.2 Requirements
[AR-4.3b.2-a] The AIoT enabler layer shall support service event report from the AIoT enaber layer to the AIoT application layer.
[AR-4.3b.2-b] The AIoT enabler layer shall support trigger based or periodic event report.
4.4d Security
4.4d.1 Description
This subclause specifies the security requirements regarding the AIoT enabler layer.
4.4d.2 Requirements
[AR-4.4d.2-a] The AIoT enabler layer shall support authentication of the AIoT application layer consumer.
[AR-4.4d.2-b] The AIoT enabler layer shall support authorization of access and operation requst from AIoT application layer consumer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.2 Provisioning management requirement
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.2.1 Description
| This clause specifies the requirements of AIoT service provisioning management from AIoT application layers to the AIoT enabler layers.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.2.2 Requirements
| [AR-4.2.2-a] The AIoT enabler layer shall support the provisioning of application object data, application service region, service scenario, interested service events to the AIoT enabler layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.3 Event report requirement
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.3.1 Description
| This clause specifies the requirements of service event report from the AIoT enabler layer to the AIoT application layers.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.3.2 Requirements
| [AR-4.3.2-a] The AIoT enabler layer shall support service event report from the AIoT enaber layer to the AIoT application layer.
[AR-4.3.2-b] The AIoT enabler layer shall support trigger based or periodic event report.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.4 Security
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.4.1 Description
| This subclause specifies the security requirements regarding the AIoT enabler layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 4.4.2 Requirements
| [AR-4.4.2-a] The AIoT enabler layer shall support authentication of the AIoT application layer consumer.
[AR-4.4.2-b] The AIoT enabler layer shall support authorization of access and operation requst from AIoT application layer consumer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 5 Architecture for Ambient IoT service enablement
| This clause will document any new architecture or the architectural enhancement for the existing application enablers.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 6 Key issues
| 6.1 Key issue #1: Enhance Application enablement layer for Ambient IoT services
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 6.1.1 Description
| Ambient power-enabled IoT devices or AIoT devices are of low complexity, small size, lower power consumption, having limited memory capacity, less compute power, and lacking advanced capabilities, which make AIoT devices different from previously defined 3GPP IoT devices. Therefore, AIoT devices cannot accommodate and run directly the VAL functionality component (i.e., VAL client) to support AIoT services, nor can they support the application enablement layer client entity (e.g., SEAL client).
As shown in the TS 23.434[5], clauses 6.1 & 6.2, for the generic on-network functional model for SEAL, while there is neither VAL client nor SEAL client providing the service enabler layer support functions from the client side, there should necessarily exist the VAL server (i.e., AIoT application server or the 3rd-party AS/AF) and the SEAL server. The SEAL server communicates with the VAL server. As explained above, due to the lack of the corresponding client-side functionality components (e.g., VAL client, SEAL-client), a SEAL server may only communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system, i.e., either the N33 via NEF (for an untrusted AF), or the new interface off the SA2-defined AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF (please reference the SA2 TS 23.369[3]).
There are already some IoT services/devices that have been studied in FS_ACE_IOT and PINAPP which the related normative work has been specified in 3GPP TS 23.434[5] and 3GPP TS 23.542[6]. Especially for PINAPP, a new application enabler (i.e. PIN enabler) has been developed to support the PIN service and personal IoT devices. As the AIoT devices are the new type of IoT devices, whether a new architecture/functional model or the existing IoT related application enablers could support the AIoT devices should be studied further.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 6.1.2 Open Issues
| This key issue is proposed to study the enhancement of the application enablement architecture for AIoT service in application enabler layer:
- Study whether and how to enhance the application enablement architecture /functional model or new application enabler to support the Ambient IoT services (i.e., AIoT inventory and command services).
6.2 Key issue #2: Exposing the value-added information of AIoT devices to the consumer
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 6.2.1 Description
| At present, 5G core network in Rel-19 could provide the requested AIoT Devices ID(s) to the AF as specified in 3GPP TS 23.369[3]. However, these AIoT Devices ID(s) are huge and may not fulfill the service requirements from the 3rd parties (e.g. AS/AF). The following are some examples to show the gaps between the service requirements and the current exposure capabilities.
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 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. However, 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, how to identify the AIoT devices in service granularity and how to indicate when one type of device will reach the pre-defined threshold to perform the increase or decrease actions should be studied further in application enablement layer.
In another scenario, if AF sends continuously a batch of 'inventory service’ requests covering different areas (with different area-IDs), though these areas belonging to a same (large) targeted area whose identity could be a geographical civic address. Then, the AIoT application enabler may aggregate these requests and send only one combined 'inventory service’ request to the 5G core network instead of sending several 'inventory service’ requests continuously.
Besides, 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. However, based on current exposure results from 5G core network, only the device ID with RAN reader ID may be exposed, but how to map the RAN ID to the location information (e.g. civic address) and track 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, if they received enriched results from the enabler layer. Hence, how to provide value-added services to the consumers based on the AIoT devices information retrieved from the core network should be studied at the application enablement layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 6.2.2 Open Issues
| Based on the above analysis, the following open issues need to be studied in the application enabled layer:
1. How to enrich the processing (e.g. filtering, categorization, consolidation) of AIoT service requests and the collected Ambient IoT device data;
2. How to utilize the exposure from other working group (e.g. SA2) and provide the value-added AIoT devices information to the consumer (e.g. VAL server) based on open issue #1.
6.3 Key issue #3: Key issue on provisioning and monitoring AIoT device presence
6.3.1 Description
The 5G core network (5GC) defines the “inventory” and the “command” AIoT service operations in 3GPP TS 23.369 [3]. While architecture and framework for supporting AIoT services in the 5GC have been defined, there exist unique scenarios for which the application enablement layer can enhance the AIoT service operations.
For example, a 3rd-party retail application server (i.e., VAL server) may issue periodic inventory service requests to check the volume of some specific types of AIoT devices in a certain area. When the number of available AIoT devices of a type drops below a certain threshold, product shortage may happen. In this scenario, a retailer may desire to replenish product stock in advance to avoid shortage. An AIoT application enabler may provide a service enabling threshold-driven inventory checks for monitoring the changing volume of AIoT devices. An AIoT application enabler can provide unform and efficient monitoring for different 3rd party retail application servers (i.e., VAL servers).
In another example scenario, a 3rd-party application server (e.g., VAL server) may collect AIoT device information via inventory service command for an AIoT device originally located in a first target area. This AIoT device may be moved to a second target area. The 3rd-party application server may issue inventory service command to the AIoT device for the first target area, thus generating a failure to retrieve the AIoT device information. For this scenario, an AIoT 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.
Further, 3GPP TS 22.369 [2] mentions that “Subject to user consent, operator’s policy and 3rd party request, the 5G system shall provide information about an Ambient IoT device or a group of Ambient IoT devices (e.g. position) to the trusted 3rd party via the 5G network.”. The 5GC support for AIoT service operations does not meet that requirement.
KI #3 focuses on providing enhanced means and information realted to monitoring the presence of provisioned AIoT devices by the application enablement layer. Monitoring of AIoT device presence may need to be performed according to different schedules and according to different presence monitoring criteria, for example for a group of AIoT devies associated with a product or with an object.
The exposure of AIoT devices by the core network (e.g., via the inventory or command service operations) offers limited reporting options; thus, it may be beneficial for an AIoT information consumer (e.g., VAL server) to have access to enhanced capabilities offered by the application enablement layer for configuring and monitoring the presence of AIoT devices.
6.3.2 Open Issues
This key issue will study the following aspects
1. How to provision information about AIoT devices requiring monitoring in the application enablement layer.
2. How concurrent AIoT device monitoring operations can be managed in the application enablement layer considering existing CN AIoT exposure capabilities.
3. Whether and how enhanced AIoT device monitoring information, such as status, location or trajectory of Ambient IoT devices, can be provided by the application enablement layer.
6.4 Key issue #4: AIoT Data Management
6.4.1 Description
AIoT inventory service provides the inventory resultdata only including device ID. However, the upper-layer applications require high-level, semantic-rich information such as "which application layer object, at what time, in which logical location, experienced what meaningful application layer event, and associated with which application layer attributes". For example, typical AIoT inventory result data is about "Device ID list: ID1, ID2, ID3…… ", while application requirement is about "the Product SKU123 has just been received through the Gate 1 at Warehouse 1".
So, the AIoT data and application requement has significant gaps in semantics, granularity and application layer context:
1) Physical location vs logical location: Currently the external target area for inventory is normally e.g., a civic address or shapes, but the application needs a logically significant application layer position, such as warehouse zone A, workstation 3, entry checkpoint1.
2) Device id vs application layer object: AIoT inventory service provided by SA2 only identifies the tag(EPC) attached to the item, but the application needs to get the information of the item(product, asset, pallet).
3) Network inventory event vs application layer event: The 5GS AIoT inventory services provide inventory result only with Device ID list, but the application usually needs to aggregate device ID and other information like target service area, timestamp, and even aggreate the inventory result from multiple times inventory to generate a meaningful event, for example:
- application layer event: A packet containing 5 items has been shipped. (Confirm that all five product tags are read at a specific location and time and are associated with the same shipping order.)
- Counting: There are 25 items on the shelf. (Summarize the number of unique tags which is associated to some item, read within a specific target area.)
- State: Pallet a is moved to production line. (Check the tag’s physical location is accurately changed from target area A to target area B)
For the downlink datastream, the 5G core network provides inventory service API. It requires the upper layer to specify the network resources (service area) for executing inventory instructions. However, the application layer is only interested in the applicatoin layer items and application layer area information. There is a semantic gap between the application layer area information and the physical area information on the network side. Direct integration and use the network reported data require a significant amount of adaptation development work for the AIoT application, which is not conducive to promoting the 3GPP AIoT marketing adoptation.
6.4.2 Open Issues
Open issues:
1. How to align the inventory result data acording to the desired application semantics and formats.
2. How to configure, manage and expose the conversion of inventory result data according to the vertical application requirements, such as ERP(enterprise resource planning system), MES(Management Execution System) or WMS(warehousing management system).
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7 Solutions
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.0 Mapping of solutions to key issues
| Table 6.0-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
Sol #1
x
Sol #2
x
Sol #3
x
x
x
x
Sol #4
x
Sol #5
x
x
x
Sol #6
x
x
Sol #7
x
x
x
Sol #8
x
Sol #9
x
Sol #10
x
Sol #11
x
Sol #12
x
x
Sol #13
x
x
Sol #x
7.1x Solution #1x: New architecture and functional model for AIoT services <title>
Provide a suitable title for the solution.
7.1x.1 Solution description
This clause will describe the solution. Each solution should clearly describe which of the key issues it covers and how.
This solution addresses the KI#1. The following procedures introduce the on-network and off-network functional model for AIoT services, also mention the functional entities and reference points in the new architecture. This solution aligns with the network architecture for AIoT services which specified in clause 4.2 of 3GPP TS 23.369 [3].
7.1x.1.1 On-network Functional model for AIoT services
Figure 7.1x.1.1-1 illustrates the generic on-network functional model for AIoT service.
Figure 7.1x.1.1-1: On-network functional model for AIoT services
The AIoT management server, acting as an AF, could obtain AIoT data information from the 3GPP core network via NEF (over N33 reference point) which is defined in clause 4.5.4 of 3GPP TS 23.369 [3]. If the AIoT management server is a trusted AF, it may interact with AIOTF directly for AIoT related service as defined in clause 4.5.5 of 3GPP TS 23.369 [3]. The AIoT management server may communicate with other SEAL server(s) over AM-X reference point.
Editor’s note: Whether and how the AIoT management server communicates with other SEAL servers is FFS.
The VAL server(s) could communicate with the AIoT management server over AM-S reference point for requesting the AIoT services and receiving the AIoT data information.
The AIoT management client, acting as a consumer, could also request the AIoT services to the AIoT management server over AM-UU reference point, and provide the support for AIoT related functions to the VAL client(s) over AM‑C reference point.
NOTE: In this release, the AIoT management client is not an UE reader, but only acts as an AIoT service consumer.
The VAL client communicates with the VAL server over the VAL-UU reference point which is outside the scope of this document.
7.1x.1.23 Functional entities description
AMS (AIoT Management Server):
The AMS performs the following functionalities to support AIoT services:
- Interact with 3GPP core network via NEF to obtain the AIoT device data, acting as an untrusted AF;
- Interact with AIOTF in 3GPP core network directly to obtain the AIoT device data, acting as a trusted AF;
- Enrich the processing of AIoT service requests and the collected Ambient IoT related data;
- Provide the value-added information of AIoT devices to the VAL servers or 3rd parties;
- Provision the AIoT devices monitoring information;
- Expose the AIoT device monitoring information to the the VAL servers or 3rd parties;
- Acting as CAPIF's API exposing function as specified in 3GPP TS 23.222 [823222].
NOTE: The functionalities for the AMS may update according to the approved solution and final conclusions.
AMC (AIoT Management Client):
The AMC performs the following functionalities to support AIoT services:
- Acting as the application client for consuming the AIoT services;
NOTE: The specific functionalities for the AMC may update according to the approved solutions and final conclusions.
7.1x.1.34 Reference points description
AM-S
The interactions related to AIoT functions between the VAL server(s) and the AIoT management servers are supported by AM-S reference point.
AM-S reference point is used by the VAL server to request and receive the AIoT device related information from AIoT management server.
AM-S reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [823222].
AM-X
The interactions related to AIoT functions between the AIoT management servers and the other SEAL servers (e.g., LMS, ADAES) are supported by AM-E reference point.
AM-X reference point is used by the AIoT management server to request and receive the AIoT device related information.
AM-C:
The interactions related to AIoT functions between the VAL client(s) and the AIoT management clients within a VAL UE are supported by AM-C reference point.
AM-UU:
The interactions related to AIoT functions between the AIoT management clients and the AIoT management servers are supported by AM-UU reference point.
7.1x.2 Architecture Impacts
This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
This solution proposes a new architecture and functional mode for AIoT services.
7.1x.3 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
7.1x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.2x Solution #2x: Enhance application enablement layer for Ambient IoT services
7.2x.1 Solution Architecture
This solution proposes to define an independent architecture, based on which a new application enabler AIoTApp is defined and acts as a SEAL layer function entity.
7.2x.2 On-network functional model for AIoTApp Service with/ new application enabler
Ambient power-enabled IoT devices or AIoT devices are of low complexity, small size, lower power consumption, having limited memory capacity, less compute power, and lacking advanced capabilities, which results in AIoT devices not being able to accommodate and run directly the VAL functionality component (i.e., VAL client) to support AIoT services, nor can they support the application enablement layer client entity (e.g., SEAL client).
For AmbientIoT_App service, upon viewing the generic on-network functional model for SEAL as in the 3GPP TS 23.434[5] clauses 6.2, while there is neither VAL client nor SEAL client providing the service enabler layer support functions from the client side, there should necessarily exist the VAL server, i.e., AIoT application server or the 3rd-party AS/AF, and the SEAL layer enabler (or server). The SEAL server communicates with the VAL server via the SEAL-S reference point. However, due to the lack of the corresponding client-side service enabler layer functional entities (e.g., VAL client, SEAL-client), a SEAL server may only communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system, i.e., either the N33 via NEF (for an untrusted AF), or the interface off the SA2-defined AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF (as in the 3GPP TS 23.369[3]).
Figure 7.2x.2-1: On-network functional model for AIoTApp service
As shown in the Fig. 7.2x.2-1, for the unique (one-side) on-network functional model, the application enablement architecture layer can only be enhanced at the server side (i.e., the right-hand side of the picture) of the application enabler for Ambient IoT service. A new application enabler, i.e., AIoTApp, is introduced to act as a SEAL layer function entity. The AIoTApp enabler function provides services to VAL server over the AIoTApp-S reference point. The detailed 5GC architecture to support the AIoT service is shown in the TS 23.369 [3].
NOTE 1: The AIoTApp-N interface is either the N33 via NEF (for an untrusted AF), or the interface off the SA2-defined AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF as defined in the 3GPP TS 23.369 [3].
7.2x.3 Off-network functional model for AIoTApp Service
The off-network functional model for AmbientIoT application enablement architecture is not supported in this release.
7.2x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.3x Solution #3x: AIoT application work flow using AIoT enabler layer
7.3x.1 Solution description
This solution addresses key issue#1, 2, 3 and 4 to introduce a AIoT application work flow using AIoT enabler layer based on the AIoT enabler functional model defined in Sol#2.
The AIoT network provides fundamental tag inventory service with typical output AIoT data is about "Device ID list: ID1, ID2, ID3…… ". However, the upper-layer applications require high-level, semantic-rich information such as "which business object, at what time, in which logical location, experienced what meaningful business event, and associated with which business attributes". To ensure better adaptation and integration between the AIoT network and the application layer, it is necessary to build AIoT-enabled service capabilities to bridge the gap between AIoT inventory data obtained from the 3GPP network and AIoT application layer data, as well as the AIoT task and the 3GPP network service APIs.
In addition to the function model defined in Sol#2, this solution assmuption the enabler layer has the following
The functional model introduce a new functionality AIoT enabler server. It supports the following functionalities:
• AIoT service provisioning: it supports the AIoT application layer to provision its AIoT application tag data, application object data, AIoT application service region, and AIoT service scenario associated with each region, interested AIoT service events. Via this service provisioning, the AIoT enabler server allows each AIoT service provider to customize their own AIoT task, region, event.
• AIoT task control: It supports the dynamic conversion between the AIoT application layer data and the AIoT service API or data reported from 3GPP system, including:
- translate the AIoT task (i.e., inventory check of all goods in warehouse A) to the network AIoT services (i.e., Inventory and command service). A AIoT task is AIoT service oriented and normally contains several key information, e.g., service region(s), service objects, scenario.
- collects the network reported AIoT result data, derives the corresponding AIoT service events and AIoT service layer data, and notifies the AIoT application server.
The end-to-end data processing workflow is illustrated in the following figure 7.3.1x-1:
Figure 7.3.1x-1: Overview of AIoT enabler workflow
1. Perform the initial and basic AIoT service provisioning including the batch registration of AIoT tags, AIoT regions, AIoT application objects, and AIoT application service regions, the association between AIoT tags and business objects, the association between AIoT application service region and target service area, and also the AIoT service scenario as well as the interested AIoT service events. After the basic configuration phase, the application layer can invoke AIoT services using its configued task, scenario, region.
2. AIoT Inventory Task Generation and Distribution. The AIoT enabler server receives the request with AIoT task from the application layer. The AIoT enabler server transforms these AIoT tasks into AIoT inventory/command towards the 3GPP system. For example, the application layer AIoT task "Inventory check of all goods in warehouse A", whose application objects are goods, application service region is warehouse A, service scenario is stock-taking, is translated into the AIoT inventory API invocation " inventory command with service area 1 and AIoT device ID filter information for goods."
3. The 3GPP network begins inventorying and reports the results to the AIoT Enabled Server.
4. The AIoT-enabler server receives the AIoT inventory results and, based on the AIoT service configuration informations set in step 1 and scenario-processing models specified in step 2, applies the scenario-based processing on the AIoT inventory results to form AIoT service events.
For example, the AIoT inventory result "Tag x, y and zwere seen at AIoT service area a (specified in the inventory service requests)" is translated into "Goods X, Y and Z have completed inventory at warehouse A." Depend on the different requirements at the application layer, the AIoT enabler server can directly report the AIoT service event to the AIoT application server or further process it in conjunction with AIoT service logic to form another AIoT service event, such as "The receipt task at Checkpoint 1 has been successfully completed," and then report it.
7.3x.2 Architecture Impacts
This solution has no architecture impact.
7.3x.3 Corresponding APIs
No service API isare introduced.
7.3x.4 Solution evaluation
7.4x Solution #4x: Support of AIoT device presence information subscription
7.4x.1 Solution description
7.4x.1.1 Introduction
This solution addresses Key Issue #3 on provisioning information in the application enablement layer and enables presence monitoring of AIoT devices.
This solution proposes that an AIoT Enablement Server (AIOTES) offers a service to authorized consumers (e.g., VAL Servers, VAL clients) for subscribing to AIoT device presence information.
This solution proposes to:
• define a new procedure and information flows to enable provisioning of AIoT presence information subscription in the AIOTES for presence reporting;
• define a new procedure and information flow for detecting events and reporting presence of AIoT devices.
7.4x.1.2 AIoT presence information subscription
Figure 7.4x.1.2-1 describes a procedure for AIoT presence information subscription.
Figure 7.4x.1.2-1: AIoT Presence Information Subscription
1. The requestor (e.g., VAL server) sends an AIoT presence information subscription request to the AIOTES. The request includes the requestor identifier, information about AIoT device(s) [device identifier, area information] and information about the presence reporting configuration [notification endpoint, frequency, schedule, location indication, change only indication].
2. Upon receiving the request from the requestor, the AIOTES validates if the requestor is authorized for the request. If the requestor is authorized, the AIOTES allocates a presence reporting subscription identifier, and stores the associated AIoT device information and presence reporting configuration.
The AIOTES initiates the presence monitoring by sending the Nnef_AIoT_Inventory Request as described in 3GPP TS 23.369 [3]. Based on the AIoT devices information and reporting configuration, the AIOTES includes the AIOTES identifier, the AIOTES notification endpoint, the AIoT device identifiers and may include Area Information, Location information indication and number of AIoT devices as input parameters for Nnef_AIoT_Inventory Request. If the reporting configuration includes schedule, the AIOTES sends the Nnef_AIoT_Inventory Request according to the time schedule (e.g., delays the request based on reporting time schedule).
The AIOTES configures the reporting based on the presence reporting configuration. If the reporting configuration includes frequency, the AIOTES schedules periodic reporting of the monitored presence to the notification endpoint according to frequency. If the reporting configuration includes change only indication, the AIOTES sends the notification only if a change in the presence information has happened since the previous notification.
If the AIOTES sends the Nnef_AIoT_Inventory Request and the request is successful, the AIOTES stores the returned transaction identifier.
3. The AIOTES sends an AIoT Information Provisioning response to the VAL server. If the request was authorized, the response includes an indication of success for the request, the presence reporting session identifier and an indication that the presence monitoring has started. Otherwise, the response includes an indication of failure and may include a failure cause.
7.4x.1.3 AIoT presence information notification
Figure 7.4x.1.3-1 describes a procedure for AIoT presence information notification.
Figure 7.4x.1.3-1: AIoT Presence Information Notification
1. The AIOTES detects a presence reporting event. The presence reporting event may be one of receiving a Nnef_AIoT_Notify message or detecting a reporting event based on the reporting configuration.
If the AIOTES receives a Nnef_AIoT_Notify message as described in 3GPP TS 23.369 [3], the AIOTES identifies retrieves the subscription information using the AF transaction identifier. The AIOTES stores or updates the received AIoT device presence information locally and prepares the information to be included in the AIoT Presence Information notification. If the change only indication is present in the reporting configuration, the AIOTES determines, for each device, if the received presence information has changed and the AIoT Presence Information notification is sent only if the AIOTES has determined a change. If the Nnef_AIoT_Notify message includes a last report indication, the AIOTES may send a Nnef_AIoT_Inventory Request as described in step 2 of clause 7.4x.1.2 to continue receiving inventory notifications.
If the AIOTES detects a reporting event which is the periodic reporting frequency timer expiration,. tThe AIOTES prepares the information to be included in the AIoT Presence Information notification based on the AIoT device presence information locally available.
If the AIOTES detects a reporting event which is a scheduled reporting time event,. iIf the reporting event is to start reporting, the AIOTES starts inventory command by sending the Nnef_AIoT_Inventory Request as described in step 2 of clause 7.x.1.2. If the detected reporting event is to stop reporting, the AIOTES sends a last notification to the requestor to indicate that reporting is stopped and stops sending notifications to the requestor.
2. The AIOTES sends an AIoT presence information notification to the endpoint configured in the presence reporting configuration.
The notification includes a presence report including the AIoT device identifiers, the presence status of the AIoT devices and may include the location information (e.g., as indicated in Nnef_AIoT_Notify), a duration since the last presence status change. The presence report includes a presence reporting status (e.g., started or stopped) if the detected event scheduled reporting time event.
7.4x.2 Architecture Impacts
This solution proposes that a new functional entity, as an AIoT Enablement Server (AIOTES) which is a SEAL Server, is supported in the application enablement layer.
7.4x.3 Corresponding APIs
7.4x.3.1 AIoT Presence Information Provisioning request
Table 7.4x.3.1-1 describes the AIoT Presence Information Subscription request.
Table 7.4x.3.1-1: AIoT Presence Information Subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
AIoT device information
M
The information about AIoT devices for the subscription.
> AIoT device identifiers
M
The list of device identifiers for which the presence is monitored.
> Area information
O
The area information where the presence is monitored.
Reporting configuration
M
The configuration for presence reporting.
> Notification endpoint
M
The endpoint information (e.g., URL, URI, IP address) where presence reports should be sent.
> Frequency
O
The frequency at which the presence is reported to the requestor.
> Schedule
O
The time schedule (e.g., duration, time of day, period) at which presence reporting is required.
> Location information indication
O
The indication that location information is requested in the presence report.
> Change only indication
O
The indication that reporting only includes device for which the presence status has changed.
7.4x.3.2 AIoT Presence Information Subscription response
Table 7.4x.3.2-1 describes the AIoT Presence Information Subscription response.
Table 7.4x.3.2-1: AIoT Presence Information Subscription request
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for the subscription.
Failure response
O
(NOTE)
The indication that the request failed.
> Cause
O
The failure cause
NOTE: Only one of these information elements shall be provided.
7.4x.3.3 AIoT Presence Information notification
Table 7.4x.3.35-1 describes the AIoT Presence Information notification.
Table 7.4x.3.35-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.
7.5Y Solution#5: Services on Application AIoT Discovery and Monitoring
7.5Y.1 Solution Description
7.5Y.1.10 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.
7.5Y.1.21 Procedure for Application AIoT Discovery
Figure 7.5Y.1.21-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.
7.5Y.1.32 Procedure for Application AIoT Monitoring
Figure 7.5Y.1.32-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.
1. The AIoT App server authenticates and authorizes the request.
2. The AIoT App server responds to the application AIoT monitoring request, with subscription ID.
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, 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.
4. 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.
5. 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).
6. The AIoT App server sends application AIoT monitoring notification to the consumer, with the required monitoring information.
7.5Y.1.43 Information Flows
Editor’s Note: The information flows of the solution is FFS.
7.5Y.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
7.5Y.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.
7.6x Solution #6x: Solution for AIoT service provision
7.6x.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.1x-1 show the high-level procedures of AIoT service provisioning.
Figure 7.6.1x-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.x.1-1.
Table 7.6.1x.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.
7.6x.2 Architecture Impacts
This solution introduces the AIoT service provisioning capability to the AIoT enabler layer.
7.6x.3 Corresponding APIs
A new AIoT service provisioning service is introduced.
7.6x.4 Solution evaluation
7.7x Solution #7X: Application AIoT Task execution
7.7x.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.7x.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.7x.1-1. The AIoT task is initiated and sent to AIoT enabler server with AIoT task information.
Table 7.7x.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.
7.7x.2 Architecture Impacts
This solution introduces the AIoT task transformation capability to the AIoT enabler server.
7.7x.3 Corresponding APIs
This solution introduces a new AIoT task execution service.
7.7x.4 Solution evaluation
7.8x Solution #8x: Exposing the value-added information of AIoT devices to the consumer
7.8x.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.
7.8x.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.
7.8x.3 Procedure
7.8x.3.1 Exposure of value-added information via AIoT application enabler
Figure 7.8x.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.8x.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.
7.8x.3.2 Information flows
Editor’s Note: The details of Information Flows are FFS.
7.8x.3.2.1 AIoT App Service request
Table 7.8x.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.8x.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 1: The AIoT service parameters are specified in the 3GPP TS 23.369 [3].
7.8x.3.2.2 AIoT App service response
Table 75.8x.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.8x.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.
7.8x.3.2.3 AIoT App service notification
Table 7.5.8x.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.8x.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.
7.8x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.9x Solution #9x: Support of periodical and event-triggered AIoT service operations
7.9x.1 Solution description
7.9x.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.9x.1.2 illustrates the high-level procedure of periodic AIoT inventory service operations.
Clause 7.9x.1.3 illustrates the high-level procedure of event-triggered inventory service operations.
7.9x.1.2 Procedure of periodic AIoT inventory service operations
Figure 7.9x.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.9x.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.
7.9x.1.3 Procedure of event triggered AIoT inventory operations
Figure 7.9x.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.9x.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.9x.1.3-1: Procedure of event triggered AIoT inventory operations
1. Similar with Step 1 in clause 7.9x.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.9x.1.2.
3. Similar with Step 3 in clause 7.9x.1.2.
4. The AIoT enabler may set the time interval to trigger the periodic AIoT inventory operations described in clause 7.9x.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.9x.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.9x.1.2 and 7.9x.1.3 can be combined or not is FFS.
7.9x.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.
7.9x.3 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
7.9x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.10x Solution #10x: Support of querying history data for AIoT devices
7.10x.1 Solution description
7.10x.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.
7.10x.1.2 Procedure of querying history data for AIoT devices
Figure 7.10x.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.10x.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.
7.10x.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.
7.10x.3 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
7.10x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.11x Solution #11x: Provision and monitor AIoT device presence
7.11x.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.
7.11x.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.
7.11x.3 Procedure
7.11x.3.1 Provision and monitor AIoT device presence
Figure 7.11x.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.11x.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.
7.11x.3.2 Information flows
Editor’s Note: The details of Information flows are FFS.
7.11x.3.2.1 AIoT App Service request
Table 7.11x.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.11x.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].
7.11x.3.2.2 AIoT App service response
Table 7.11x.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.11x.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.
7.11x.3.2.3 AIoT App service notification
Table 7.11x.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.11x.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.
7.11x.43 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
7.11x.54 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.12x Solution #12x: Support of monitoring requests for AIoT devices
7.12x.1 Solution description
7.12x.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.
7.12x.1.2 Procedure of Monitoring requests for AIoT devices
Figure 7.12x.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.12x.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 [723436]. 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.
7.12x.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.
7.12x.3 Corresponding APIs
This clause provides the corresponding APIs for supporting the solution.
7.12x.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
7.13x Solution #13X: AIoT Data Processing management
7.13x.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.13x.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.13X.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 [323.369].
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.
34. Report the interested application events to the application layer and the AIoT task is completed.
7.13x.2 Architecture Impacts
This solution introduces AIoT service event notification capability to the AIoT enabler server.
7.13x.3 Corresponding APIs
The AIoT service event notification service is introduced.
7.13x.4 Solution evaluation
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1 Solution #1: New architecture and functional model for AIoT services
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.1 Solution description
| This solution addresses the KI#1. The following procedures introduce the on-network and off-network functional model for AIoT services, also mention the functional entities and reference points in the new architecture. This solution aligns with the network architecture for AIoT services which specified in clause 4.2 of 3GPP TS 23.369 [3].
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.1.1 On-network Functional model for AIoT services
| Figure 7.1.1.1-1 illustrates the generic on-network functional model for AIoT service.
Figure 7.1.1.1-1: On-network functional model for AIoT services
The AIoT management server, acting as an AF, could obtain AIoT data information from the 3GPP core network via NEF (over N33 reference point) which is defined in clause 4.5.4 of 3GPP TS 23.369 [3]. If the AIoT management server is a trusted AF, it may interact with AIOTF directly for AIoT related service as defined in clause 4.5.5 of 3GPP TS 23.369 [3]. The AIoT management server may communicate with other SEAL server(s) over AM-X reference point.
Editor’s note: Whether and how the AIoT management server communicates with other SEAL servers is FFS.
The VAL server(s) could communicate with the AIoT management server over AM-S reference point for requesting the AIoT services and receiving the AIoT data information.
The AIoT management client, acting as a consumer, could also request the AIoT services to the AIoT management server over AM-UU reference point, and provide the support for AIoT related functions to the VAL client(s) over AM‑C reference point.
NOTE: In this release, the AIoT management client is not an UE reader, but only acts as an AIoT service consumer.
The VAL client communicates with the VAL server over the VAL-UU reference point which is outside the scope of this document.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.1.2 Functional entities description
| AMS (AIoT Management Server):
The AMS performs the following functionalities to support AIoT services:
- Interact with 3GPP core network via NEF to obtain the AIoT device data, acting as an untrusted AF;
- Interact with AIOTF in 3GPP core network directly to obtain the AIoT device data, acting as a trusted AF;
- Enrich the processing of AIoT service requests and the collected Ambient IoT related data;
- Provide the value-added information of AIoT devices to the VAL servers or 3rd parties;
- Provision the AIoT devices monitoring information;
- Expose the AIoT device monitoring information to the the VAL servers or 3rd parties;
- Acting as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8].
NOTE: The functionalities for the AMS may update according to the approved solution and final conclusions.
AMC (AIoT Management Client):
The AMC performs the following functionalities to support AIoT services:
- Acting as the application client for consuming the AIoT services;
NOTE: The specific functionalities for the AMC may update according to the approved solutions and final conclusions.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.1.3 Reference points description
| AM-S
The interactions related to AIoT functions between the VAL server(s) and the AIoT management servers are supported by AM-S reference point.
AM-S reference point is used by the VAL server to request and receive the AIoT device related information from AIoT management server.
AM-S reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
AM-X
The interactions related to AIoT functions between the AIoT management servers and the other SEAL servers (e.g., LMS, ADAES) are supported by AM-E reference point.
AM-X reference point is used by the AIoT management server to request and receive the AIoT device related information.
AM-C:
The interactions related to AIoT functions between the VAL client(s) and the AIoT management clients within a VAL UE are supported by AM-C reference point.
AM-UU:
The interactions related to AIoT functions between the AIoT management clients and the AIoT management servers are supported by AM-UU reference point.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.2 Architecture Impacts
| This solution proposes a new architecture and functional mode for AIoT services.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.1.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.2 Solution #2: Enhance application enablement layer for Ambient IoT services
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.2.1 Solution Architecture
| This solution proposes to define an independent architecture, based on which a new application enabler AIoTApp is defined and acts as a SEAL layer function entity.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.2.2 On-network functional model for AIoTApp Service with new application enabler
| Ambient power-enabled IoT devices or AIoT devices are of low complexity, small size, lower power consumption, having limited memory capacity, less compute power, and lacking advanced capabilities, which results in AIoT devices not being able to accommodate and run directly the VAL functionality component (i.e., VAL client) to support AIoT services, nor can they support the application enablement layer client entity (e.g., SEAL client).
For AmbientIoT_App service, upon viewing the generic on-network functional model for SEAL as in the 3GPP TS 23.434[5] clauses 6.2, while there is neither VAL client nor SEAL client providing the service enabler layer support functions from the client side, there should necessarily exist the VAL server, i.e., AIoT application server or the 3rd-party AS/AF, and the SEAL layer enabler (or server). The SEAL server communicates with the VAL server via the SEAL-S reference point. However, due to the lack of the corresponding client-side service enabler layer functional entities (e.g., VAL client, SEAL-client), a SEAL server may only communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system, i.e., either the N33 via NEF (for an untrusted AF), or the interface off the SA2-defined AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF (as in the 3GPP TS 23.369[3]).
Figure 7.2.2-1: On-network functional model for AIoTApp service
As shown in the Fig. 7.2.2-1, for the unique (one-side) on-network functional model, the application enablement architecture layer can only be enhanced at the server side (i.e., the right-hand side of the picture) of the application enabler for Ambient IoT service. A new application enabler, i.e., AIoTApp, is introduced to act as a SEAL layer function entity. The AIoTApp enabler function provides services to VAL server over the AIoTApp-S reference point. The detailed 5GC architecture to support the AIoT service is shown in the TS 23.369 [3].
NOTE 1: The AIoTApp-N interface is either the N33 via NEF (for an untrusted AF), or the interface off the SA2-defined AIOT NF (i.e., AIOTF) directly providing the AIoT service operations to a trusted AF as defined in the 3GPP TS 23.369 [3].
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.2.3 Off-network functional model for AIoTApp Service
| The off-network functional model for AmbientIoT application enablement architecture is not supported in this release.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.2.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.3 Solution #3: AIoT application work flow using AIoT enabler layer
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.3.1 Solution description
| This solution addresses key issue#1, 2, 3 and 4 to introduce a AIoT application work flow using AIoT enabler layer based on the AIoT enabler functional model defined in Sol#2.
The AIoT network provides fundamental tag inventory service with typical output AIoT data is about "Device ID list: ID1, ID2, ID3…… ". However, the upper-layer applications require high-level, semantic-rich information such as "which business object, at what time, in which logical location, experienced what meaningful business event, and associated with which business attributes". To ensure better adaptation and integration between the AIoT network and the application layer, it is necessary to build AIoT-enabled service capabilities to bridge the gap between AIoT inventory data obtained from the 3GPP network and AIoT application layer data, as well as the AIoT task and the 3GPP network service APIs.
In addition to the function model defined in Sol#2, this solution assmuption the enabler layer has the following
The functional model introduce a new functionality AIoT enabler server. It supports the following functionalities:
- AIoT service provisioning: it supports the AIoT application layer to provision its AIoT application tag data, application object data, AIoT application service region, and AIoT service scenario associated with each region, interested AIoT service events. Via this service provisioning, the AIoT enabler server allows each AIoT service provider to customize their own AIoT task, region, event.
- AIoT task control: It supports the dynamic conversion between the AIoT application layer data and the AIoT service API or data reported from 3GPP system, including:
- translate the AIoT task (i.e., inventory check of all goods in warehouse A) to the network AIoT services (i.e., Inventory and command service). A AIoT task is AIoT service oriented and normally contains several key information, e.g., service region(s), service objects, scenario.
- collects the network reported AIoT result data, derives the corresponding AIoT service events and AIoT service layer data, and notifies the AIoT application server.
The end-to-end data processing workflow is illustrated in the following figure 7.3.1-1:
Figure 7.3.1-1: Overview of AIoT enabler workflow
1. Perform the initial and basic AIoT service provisioning including the batch registration of AIoT tags, AIoT regions, AIoT application objects, and AIoT application service regions, the association between AIoT tags and business objects, the association between AIoT application service region and target service area, and also the AIoT service scenario as well as the interested AIoT service events. After the basic configuration phase, the application layer can invoke AIoT services using its configued task, scenario, region.
2. AIoT Inventory Task Generation and Distribution. The AIoT enabler server receives the request with AIoT task from the application layer. The AIoT enabler server transforms these AIoT tasks into AIoT inventory/command towards the 3GPP system. For example, the application layer AIoT task "Inventory check of all goods in warehouse A", whose application objects are goods, application service region is warehouse A, service scenario is stock-taking, is translated into the AIoT inventory API invocation " inventory command with service area 1 and AIoT device ID filter information for goods."
3. The 3GPP network begins inventorying and reports the results to the AIoT Enabled Server.
4. The AIoT-enabler server receives the AIoT inventory results and, based on the AIoT service configuration informations set in step 1 and scenario-processing models specified in step 2, applies the scenario-based processing on the AIoT inventory results to form AIoT service events.
For example, the AIoT inventory result "Tag x, y and zwere seen at AIoT service area a (specified in the inventory service requests)" is translated into "Goods X, Y and Z have completed inventory at warehouse A." Depend on the different requirements at the application layer, the AIoT enabler server can directly report the AIoT service event to the AIoT application server or further process it in conjunction with AIoT service logic to form another AIoT service event, such as "The receipt task at Checkpoint 1 has been successfully completed," and then report it.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.3.2 Architecture Impacts
| This solution has no architecture impact.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.3.3 Corresponding APIs
| No service API is introduced.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.3.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4 Solution #4: Support of AIoT device presence information subscription
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.1 Solution description
| 7.4.1.1 Introduction
This solution addresses Key Issue #3 on provisioning information in the application enablement layer and enables presence monitoring of AIoT devices.
This solution proposes that an AIoT Enablement Server (AIOTES) offers a service to authorized consumers (e.g., VAL Servers, VAL clients) for subscribing to AIoT device presence information.
This solution proposes to:
- define a new procedure and information flows to enable provisioning of AIoT presence information subscription in the AIOTES for presence reporting;
- define a new procedure and information flow for detecting events and reporting presence of AIoT devices.
7.4.1.2 AIoT presence information subscription
Figure 7.4.1.2-1 describes a procedure for AIoT presence information subscription.
Figure 7.4.1.2-1: AIoT Presence Information Subscription
1. The requestor (e.g., VAL server) sends an AIoT presence information subscription request to the AIOTES. The request includes the requestor identifier, information about AIoT device(s) [device identifier, area information] and information about the presence reporting configuration [notification endpoint, frequency, schedule, location indication, change only indication].
2. Upon receiving the request from the requestor, the AIOTES validates if the requestor is authorized for the request. If the requestor is authorized, the AIOTES allocates a presence reporting subscription identifier, and stores the associated AIoT device information and presence reporting configuration.
The AIOTES initiates the presence monitoring by sending the Nnef_AIoT_Inventory Request as described in 3GPP TS 23.369 [3]. Based on the AIoT devices information and reporting configuration, the AIOTES includes the AIOTES identifier, the AIOTES notification endpoint, the AIoT device identifiers and may include Area Information, Location information indication and number of AIoT devices as input parameters for Nnef_AIoT_Inventory Request. If the reporting configuration includes schedule, the AIOTES sends the Nnef_AIoT_Inventory Request according to the time schedule (e.g., delays the request based on reporting time schedule).
The AIOTES configures the reporting based on the presence reporting configuration. If the reporting configuration includes frequency, the AIOTES schedules periodic reporting of the monitored presence to the notification endpoint according to frequency. If the reporting configuration includes change only indication, the AIOTES sends the notification only if a change in the presence information has happened since the previous notification.
If the AIOTES sends the Nnef_AIoT_Inventory Request and the request is successful, the AIOTES stores the returned transaction identifier.
3. The AIOTES sends an AIoT Information Provisioning response to the VAL server. If the request was authorized, the response includes an indication of success for the request, the presence reporting session identifier and an indication that the presence monitoring has started. Otherwise, the response includes an indication of failure and may include a failure cause.
7.4.1.3 AIoT presence information notification
Figure 7.4.1.3-1 describes a procedure for AIoT presence information notification.
Figure 7.4.1.3-1: AIoT Presence Information Notification
1. The AIOTES detects a presence reporting event. The presence reporting event may be one of receiving a Nnef_AIoT_Notify message or detecting a reporting event based on the reporting configuration.
If the AIOTES receives a Nnef_AIoT_Notify message as described in 3GPP TS 23.369 [3], the AIOTES identifies retrieves the subscription information using the AF transaction identifier. The AIOTES stores or updates the received AIoT device presence information locally and prepares the information to be included in the AIoT Presence Information notification. If the change only indication is present in the reporting configuration, the AIOTES determines, for each device, if the received presence information has changed and the AIoT Presence Information notification is sent only if the AIOTES has determined a change. If the Nnef_AIoT_Notify message includes a last report indication, the AIOTES may send a Nnef_AIoT_Inventory Request as described in step 2 of clause 7.4.1.2 to continue receiving inventory notifications.
If the AIOTES detects a reporting event which is the periodic reporting frequency timer expiration, the AIOTES prepares the information to be included in the AIoT Presence Information notification based on the AIoT device presence information locally available.
If the AIOTES detects a reporting event which is a scheduled reporting time event, if the reporting event is to start reporting, the AIOTES starts inventory command by sending the Nnef_AIoT_Inventory Request as described in step 2 of clause 7.x.1.2. If the detected reporting event is to stop reporting, the AIOTES sends a last notification to the requestor to indicate that reporting is stopped and stops sending notifications to the requestor.
2. The AIOTES sends an AIoT presence information notification to the endpoint configured in the presence reporting configuration.
The notification includes a presence report including the AIoT device identifiers, the presence status of the AIoT devices and may include the location information (e.g., as indicated in Nnef_AIoT_Notify), a duration since the last presence status change. The presence report includes a presence reporting status (e.g., started or stopped) if the detected event scheduled reporting time event.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.2 Architecture Impacts
| This solution proposes that a new functional entity, as an AIoT Enablement Server (AIOTES) which is a SEAL Server, is supported in the application enablement layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.3 Corresponding APIs
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.3.1 AIoT Presence Information Provisioning request
| Table 7.4.3.1-1 describes the AIoT Presence Information Subscription request.
Table 7.4.3.1-1: AIoT Presence Information Subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
AIoT device information
M
The information about AIoT devices for the subscription.
> AIoT device identifiers
M
The list of device identifiers for which the presence is monitored.
> Area information
O
The area information where the presence is monitored.
Reporting configuration
M
The configuration for presence reporting.
> Notification endpoint
M
The endpoint information (e.g., URL, URI, IP address) where presence reports should be sent.
> Frequency
O
The frequency at which the presence is reported to the requestor.
> Schedule
O
The time schedule (e.g., duration, time of day, period) at which presence reporting is required.
> Location information indication
O
The indication that location information is requested in the presence report.
> Change only indication
O
The indication that reporting only includes device for which the presence status has changed.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.3.2 AIoT Presence Information Subscription response
| Table 7.4.3.2-1 describes the AIoT Presence Information Subscription response.
Table 7.4.3.2-1: AIoT Presence Information Subscription request
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for the subscription.
Failure response
O
(NOTE)
The indication that the request failed.
> Cause
O
The failure cause
NOTE: Only one of these information elements shall be provided.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.