hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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,S... |
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 wo... |
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.
-... |
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 ... |
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 ... |
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... |
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 servic... |
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. ... |
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
... |
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... |
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 cla... |
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;
- En... |
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 ... |
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 cli... |
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,... |
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 subsc... |
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 subs... |
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... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.4.3.3 AIoT Presence Information notification
| Table 7.4.3.3-1 describes the AIoT Presence Information notification.
Table 7.4.3.3-1: AIoT Presence Information notification
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Presence report
M
The presence report information.
> AIoT device identifiers
M
... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5 Solution#5: Services on Application AIoT Discovery and Monitoring
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1 Solution Description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.1 General
| The existing services on AIoT inventory and AIoT command cannot satisfy the application requirements on the aspects listed in the above key issues. For example, based on current exposure results from 5G core network as specified in 3GPP TS 23.369 [3], only the AIoT devices ID will be provided for the inventory request,... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.2 Procedure for Application AIoT Discovery
|
Figure 7.5.1.2-1: Application AIoT Discovery
1. A consumer (e.g., VAL server) sends application AIoT discovery request to AIoT App server. The request information includes VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device i... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.3 Procedure for Application AIoT Monitoring
|
Figure 7.5.1.3-1: Application AIoT Monitoring
1. A consumer (e.g., VAL server) sends application AIoT monitoring request to AIoT App server. The request information include VAL service ID, Area of interest (e.g., physical location, logical location (e.g., warehouse, factory, supper market)), Application AIoT device ... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.1.4 Information Flows
| Editor’s Note: The information flows of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.2 Architecture impacts
| Editor’s Note: The architecture impacts of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.5.3 Solution evaluation
| Editor’s Note: The evaluation of the solution is FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6 Solution #6: Solution for AIoT service provision
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.1 Solution description
| This solution address key issue#2, and #4 to introduce a solution for AIoT service provision.
AIoT network service can provide the information of what (AIoT device IDs) and where (AF ID and the external Target Area information), as shown in the TS 23.369[7]. However, these network exposured data can’t be directly cons... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.2 Architecture Impacts
| This solution introduces the AIoT service provisioning capability to the AIoT enabler layer.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.3 Corresponding APIs
| A new AIoT service provisioning service is introduced.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.6.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7 Solution #7: Application AIoT Task execution
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.1 Solution description
| This solution address key issue#2, 3 and 4 to introduce a solution for application AIoT task execution. The AIoT tasks from the application layer cannot be directly aligned with the AIoT NEF interface. It is necessary to translate AIoT tasks into AIoT inventory and/or command towards the 3GPP core network.
Figure 7... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.2 Architecture Impacts
| This solution introduces the AIoT task transformation capability to the AIoT enabler server.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.3 Corresponding APIs
| This solution introduces a new AIoT task execution service.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.7.4 Solution evaluation
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8 Solution #8: Exposing the value-added information of AIoT devices to the consumer
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.1 Solution Architecture
| This solution is based on an independent architecture that is newly defined in the Sol#2. In the architecture, an AIoTApp application enabler is defined and acts as a SEAL layer function entity. This function entity can be deployed and implemented by integrating with other related service enabler functions (e.g., SEALD... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.2 Solution description
| For AIoT service operation requests, the collected AIoT Devices ID(s) could be huge, less categorized and may not fulfill the service requirements from the 3rd parties (e.g. AS/AF).
For example, a 3rd-party retail App-server (i.e., VAL server) may issue periodic inventory service requests to check the volume of some ... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3 Procedure
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.1 Exposure of value-added information via AIoT application enabler
| Figure 7.8.3.1-1 illustrates the procedure for the AIoT application enabler to interact with the 5GS for the support of the Ambient IoT App service that leverages the corresponding 5GC NF services and APIs as specified in the TS 23.369 [3]. Upon receiving the requested AIoT device information, the AIoTApp enabler condu... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2 Information flows
| Editor’s Note: The details of Information Flows are FFS.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.1 AIoT App Service request
| Table 7.8.3.2.1-1 describes the information flow from the VAL server to the AIoTApp enabler for the support of the AIoT App service.
Table 7.8.3.2.1-1: AIoT App service request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL service
AIoTA... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.2 AIoT App service response
| Table 7.8.3.2.2-1 describes the information flow from the AIoTApp enabler to the VAL server to respond to the AIoT App service request.
Table 7.8.3.2.2-1: AIoT App service response
Information element
Status
Description
Result
M
Success or failure.
AIoTApp-S enpoint information
O
Address/port and/or URL of th... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.3.2.3 AIoT App service notification
| Table 7..8.3.2.3-1 describes the information flow from the AIoTApp enabler to the VAL server to notify the events related to the AIoT App service.
Table 7.8.3.2.3-1: AIoT App service notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event of the AIoTApp enabler interaction sta... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.8.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9 Solution #9: Support of periodical and event-triggered AIoT service operations
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.1 General
| This solution addresses the KI#2. Just as the example described in the KI#2, a 3rd-party retail App-server (i.e., VAL server) may issue periodic or event-triggered inventory service requests to check the changed volume of some specific types of AIoT devices in a certain area. When the number of the available AIoT devic... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.2 Procedure of periodic AIoT inventory service operations
| Figure 7.9.1.2-1 illustrates the high-level procedure of periodic inventory service request triggered by the VAL server(s).
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services. For the functionalities of new AIoT ... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.1.3 Procedure of event triggered AIoT inventory operations
| Figure 7.9.1.3-1 illustrates the high-level procedure of event triggered AIoT inventory operations which is based on the periodic AIoT inventory operations described in clause 7.9.1.2.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related ... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.9.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10 Solution #10: Support of querying history data for AIoT devices
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1 Solution description
| |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1.1 General
| This solution addresses the KI#2. Some application servers (e.g., a super market) may need to check the history data for some specific type of AIoT devices (e.g., check the sales volume of umbrellas from last year) to predict the trends for this year and beyond. So it’s necessary for application servers to query the hi... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.1.2 Procedure of querying history data for AIoT devices
| Figure 7.10.1.2-1 illustrates the high-level procedure of querying history data for AIoT devices.
Pre-condition:
- The AIoT enabler is the new application enabler in the application enablement layer which supports the AIoT related operations and services.
- The AIoT enabler support to store the history data for req... |
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.2 Architecture Impacts
| This solution proposes a new architecture (i.e., new AIoT enabler) to support AIoT services.
For the new architecture, please check the Sol#1for KI#1 for more details.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a4787e77ad46014e6b67fb22e3452dda | 23.700-26 | 7.10.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.