hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.1 KI#1 solution evaluation
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.2 KI#2 solution evaluation
| The open issues of this KI are as follows:
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.3 KI#3 solution evaluation
| The open issues of this KI are as follows:
1. Whether and how the enabler layer can use sensing results for determining the presence of objects (e.g. humans, animals, and vehicles) within an area of interest in a spatial map.
2. Whether and how the enabler layer can associate a sensing result with an object within a... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.4 KI#4 solution evaluation
| The open issues of this KI are as follows:
1. How to enhance VAE layer to provide enhanced HD map including traditional vehicles information with considering sensing results.
2. How to enhance VAE layer to provide enhanced HD map including environment information (e.g. pedestrian/animal objects, etc) with considering... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10 Conclusions
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10.1 General conclusions
| This clause will provide general conclusions for the study.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10.3 Conclusions of key issue #2
| For KI#2 on "Enhance UAV service utilizing sensing results" the following conclusions are agreed:
a) The UAS application enabler needs to support enhanced trajectory tracking for UAV based on the combination of the 3GPP CN’s sensing capability and the SEAL services, e.g. LMS, as well as the capabilities provided by th... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10.4 Conclusions of key issue #3
| The following solutions will be considered for normative work for KI #3:
- Solutions #8, #9, and #10 address open issues 1 and 4 to support creating and updating spatial maps with environment information based on sensing results, including the presence of objects within an area of interest. With necessary updates, i.e... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10.5 Conclusions of key issue #4
| For KI#4 on "utilizing sensing results for HD map in V2X" the following conclusions are agreed:
a) The V2X Server needs to support the creation and updating of HD map based on the device-centric sensing results. The SEAL sensing server generates device-centric sensing results based on the processed/filtered sensing ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 work... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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.
-... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 3 Definitions of terms, symbols and abbreviations
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 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.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
927d329fbd1f6bc1dcb4978e40e976f4 | 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
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 4 Architectural Assumptions and Requirements
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 5GS architecture for AIoT service which is specified in the 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 ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 4.2 Architectural Requirements
| [AR-4.2-a] The AIoT enabler layer shall support the provisioning of AIoT related application information by AIoT service consumers.
[AR-4.2-b] The AIoT enabler layer shall support AIoT service event report from the AIoT enabler layer to the AIoT application layer.
[AR-4.2-c] The AIoT enabler layer shall support AIoT ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 6 Key issues
| 6.1 Key issue #1: Enhance Application enablement layer for Ambient IoT services
|
927d329fbd1f6bc1dcb4978e40e976f4 | 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 ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 servic... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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. ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7 Solutions
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.0 Mapping of solutions to key issues
| Table 7.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 #1... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.1 Solution #1: New architecture and functional model for AIoT services
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.1.1 Solution description
| This solution addresses the KI#1. The following procedures introduce the on-network functional model for AIoT services, also mention the functional entities and reference points in the new architecture. This solution aligns with the 5GS architecture for AIoT services which is specified in the clause 4.2 of 3GPP TS 23.3... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 cla... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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;
- En... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.1.2 Architecture Impacts
| This solution proposes a new architecture and functional mode for AIoT services.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.1.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.1.4 Solution evaluation
| This solution addresses the KI#1 to provide a new architecture and functional model in the application enablement layer to support the AIoT services. Specifically, this solution introduces the on-network functional model, the relevant functional entities and the reference points included in the new architecture for the... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.2 Solution #2: Enhance application enablement layer for Ambient IoT services
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 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.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 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 cli... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.2.2.1 Reference points
| AIoTApp-S
The functional interactions of the AIoT services between the AIoT application enabler and the VAL server(s) are supported by the AIoTApp-S reference point.
The AIoTApp-S reference point is used by the VAL server to request and receive the AIoT device related information from the AIoT App enabler.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 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.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.2.4 Solution evaluation
| This solution addresses the KI#1 for the architectural enhancement of the application enablement layer for the support of Ambient IoT service, specifically:
- Study whether and how to enhance the application enablement architecture /functional model or new application enabler to support the Ambient IoT services (i.e.,... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.3 Solution #3: AIoT application work flow using AIoT enabler layer
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 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,... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.3.2 Architecture Impacts
| This solution is based on the architecture defined in Sol#2.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.3.3 Corresponding APIs
| No service API is introduced.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.3.4 Solution evaluation
| This solution is based on the architecture described in solution 2.
This solution addresses key issues #1, #2, #3, and #4. It provides an overall description of how the enabler layer service is used. It helps the AIoT application layer understand what the enabler server provides, what they can achieve using those valu... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4 Solution #4: Support of AIoT device presence information subscription
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 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 p... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 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 or AIOTEC) sends an AIoT presence information subscription request to the AIOTES. The request includes the requestor identifier, information ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.2 Architecture Impacts
| This solution proposes that a new functional entity, as an AIoT Enablement Server (AIOTES), is supported in the application enablement layer as described in Solution #1 and Solution #2.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.3 Corresponding APIs
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.3.1 AIoT Presence Information Subscription 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 subs... |
927d329fbd1f6bc1dcb4978e40e976f4 | 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 response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for th... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.3.3 AIoT Presence Information notification
| Table 7.4.3.3-1 describes the AIoT Presence Information notification.
Table 7.4.3.3-1: AIoT Presence Information notification
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Presence report
M
The presence report information.
> AIoT device identifiers
M
... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.4.4 Solution evaluation
| This solution addresses Key Issue #3 on provisioning information in the application enablement layer and enables presence monitoring of AIoT devices. It provides procedures for enabling a consumer (e.g., VAL server or AIOTEC) of monitoring AIoT device presence via a subscription mechanism.
The solution uses the capabi... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5 Solution#5: Services on Application AIoT Discovery and Monitoring
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1 Solution Description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.1 General
| The existing services on AIoT inventory and AIoT command cannot satisfy the application requirements on the aspects listed in the above key issues. For example, based on current exposure results from 5G core network as specified in 3GPP TS 23.369 [3], only the AIoT devices ID will be provided for the inventory request,... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.2 Procedure for Application AIoT Discovery
|
Figure 7.5.1.2-1: Application AIoT Discovery
1. A consumer (e.g., VAL server) sends application AIoT discovery request to AIoT App server. The request information includes VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device i... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.3 Procedure for Application AIoT Monitoring
|
Figure 7.5.1.3-1: Application AIoT Monitoring
1. A consumer (e.g., VAL server) sends application AIoT monitoring request to AIoT App server. The request information include VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4 Information Flows
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4.1 Application AIoT Discovery request
| Table 7.5.1.4.1-1 describes the application AIoT discovery request.
Table 7.5.1.4.1-1: Application AIoT Discovery request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
VAL service ID
M
The identifier of the VAL service.
Area of interest
M
Indicates the inter... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4.2 Application AIoT Discovery response
| Table 7.5.1.4.2-1 describes the application AIoT discovery response.
Table 7.5.1.4.2-1: Application AIoT Discovery response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Discovery information
M
Indicates the discovery information, e.g. n... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4.3 Application AIoT Monitoring request
| Table 7.5.1.4.3-1 describes the application AIoT monitoring request.
Table 7.5.1.4.3-1: Application AIoT Monitoring request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
VAL service ID
M
The identifier of the VAL service.
Area of interest
M
Indicates the int... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4.4 Application AIoT Monitoring response
| Table 7.5.1.4.4-1 describes the application AIoT monitoring response.
Table 7.5.1.4.4-1: Application AIoT Monitoring response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the monitoring request was successful.
> Subscription identifier
M
The identifier for the subsc... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.1.4.5 Application AIoT Monitoring notify
| Table 7.5.1.4.5-1 describes the application AIoT monitoring notify.
Table 7.5.1.4.5-1: Application AIoT Monitoring notify
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Monitored information
M
The monitored information, e.g. the number of objects in speci... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.2 Architecture impacts
| This solution has no architecture impact.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.5.3 Solution evaluation
| This solution addresses the KI#2 on enrich processing AIoT service and provide value-added AIoT devices information to consumer, KI#3 on AIoT device monitoring, and KI#4 on manage and expose the conversion of inventory result data according to the vertical application requirements.
In this solution, the AIoT enableme... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6 Solution #6: Solution for AIoT service provision
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1.1 General
| 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 cons... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1.2 Procedures
| The figure 7.6.1.2-1 show the high-level procedures of AIoT service provisioning.
Figure 7.6.1.2-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 foll... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1.3 Information flows
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1.3.1 AIoT service data provisioning request
| Table 7.6.1.3.1 describes the AIoT service data provisioning request from the consumer (VAL server) and the AIoT enabler server.
Table 7.6.1.3.1-1: AIoT service data provisioning request
Information element
Status
Description
Requester identifier
M
The identifier of the requester
List of AIoT device mapping in... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.1.3.2 AIoT service data provisioning response
| Table 7.6.1.3.2-1 describes the AIoT service data provisioning response from the AIoT enabler server and the consumer (VAL server).
Table 7.6.1.3.2-1: AIoT service data provisioning response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
Fai... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.2 Architecture Impacts
| This solution introduces the AIoT service provisioning capability to the AIoT enabler layer.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.3 Corresponding APIs
| A new AIoT service provisioning service is introduced.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.6.4 Solution evaluation
| This solution is based on the new functional model with an AIoT enabler server function entity.
In this solution, a new value-added service, i.e., service data provisioning service is designed to address key issue #2 and key issue #4. This service enables the application layer to configure the association between AIo... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7 Solution #7: Application AIoT Task execution
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.1 Solution description
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.1.1 General
| 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.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.1.2 Procedures
| The figure 7.7.1.2-1 shows a high-level description of the AIoT task execution initiated by AIoT application layer entity (e.g., VAL server) towards the AIoT enabler server.
Pre-conditions:
- The VAL consumer (e.g., VAL server) has provisioned the application layer related information as described in sol#6.
Figure... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.1.3 Information flows
| 7.7.1.3.1 AIoT task initiate request
Table 7.7.3.1-1 describes the AIoT task initiate request from the AIoT application layer consumer (e.g., VAL server) towards the AIoT enabler server.
Table 7.7.1.3.1-1: AIoT task initiate request
Information element
Status
Description
Requester Identifier
M
The identifier ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.1.3.2 AIoT task initiate response
| Table 7.7.1.3.2-1 describes the AIoT task initiate response from the AIoT enabler server to the AIoT application layer consumer (e.g., VAL server).
Table 7.7.1.3.2-1: AIoT task initiate response
Information element
Status
Description
Success
M (NOTE)
Indicate the request is successfully processed.
> Correlatio... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.2 Architecture Impacts
| This solution introduces the AIoT task transformation capability to the AIoT enabler server.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.3 Corresponding APIs
| This solution introduces a new AIoT task execution service.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.7.4 Solution evaluation
| This solution is based on the new functional model with an AIoT enabler server function entity and with the pre-condition that the provisioned information in Sol#6 is available.
This solution addresses key issues #2, #3, and #4 by introducing AIoT task execution service. AIoT task execution translates AIoT tasks into... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8 Solution #8: Exposing the value-added information of AIoT devices to the consumer
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.1 Solution Architecture
| This solution is based on an independent architecture that is newly defined in the Sol#2. In the architecture, an AIoTApp application enabler is defined and acts as a SEAL layer function entity. This function entity can be deployed and implemented by integrating with other related service enabler functions (e.g., SEALD... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.2 Solution description
| For AIoT service operation requests, the collected AIoT Devices ID(s) could be huge, less categorized and may not fulfill the service requirements from the 3rd parties (e.g. AS/AF).
For example, a 3rd-party retail App-server (i.e., VAL server) may issue periodic inventory service requests to check the volume of some ... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3 Procedure
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3.1 Exposure of value-added information via AIoT application enabler
| Figure 7.8.3.1-1 illustrates the procedure for the AIoT application enabler to interact with the 5GS for the support of the Ambient IoT App service that leverages the corresponding 5GC NF services and APIs as specified in the TS 23.369 [3]. Upon receiving the requested AIoT device information, the AIoTApp enabler condu... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3.2 Information flows
| NOTE: The Information flows can be further updated during the normative phase.
|
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3.2.1 AIoT App Service request
| Table 7.8.3.2.1-1 describes the information flow from the VAL server to the AIoTApp enabler for the support of the AIoT App service.
Table 7.8.3.2.1-1: AIoT App service request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
AIoTA... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3.2.2 AIoT App service response
| Table 7.8.3.2.2-1 describes the information flow from the AIoTApp enabler to the VAL server to respond to the AIoT App service request.
Table 7.8.3.2.2-1: AIoT App service response
Information element
Status
Description
Result
M
Success or failure.
AIoTApp-S enpoint information
O
Address/port and/or URL of th... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.3.2.3 AIoT App service notification
| Table 7..8.3.2.3-1 describes the information flow from the AIoTApp enabler to the VAL server to notify the events related to the AIoT App service.
Table 7.8.3.2.3-1: AIoT App service notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event of the AIoTApp enabler interaction sta... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.8.4 Solution evaluation
| This solution addresses the KI#2 for exposing value-added information of AIoT devices to consumer(s). It covers both open issues:
- Enrich the processing (e.g. filtering, categorization, consolidation) of AIoT service requests and the collected Ambient IoT device data.
- Utilize the exposure from other working group... |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9 Solution #9: Support of periodical and event-triggered AIoT service operations
| |
927d329fbd1f6bc1dcb4978e40e976f4 | 23.700-26 | 7.9.1 Solution description
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.