hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.2.2 Inheritance
|
Figure 4.1.2.2.2.1: Assurance management inheritance relationships
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3 Class definitions
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.1 AssuranceClosedControlLoop
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.1.1 Definition
| This class represents the information for controlling and monitoring an assurance closed control loop associated with a NetworkSlice or NetworkSliceSubnet. It can be name-contained by SubNetwork or ManagedElement.
To express the assurance closed control loop goals, the MnS consumer needs to request the MnS producer to... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.1.2 Attributes
| The AssuranceClosedControlLoop IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and the following attributes:
Attribute name
S
isReadable
isWritable
isInvariant
isNotifyable
operationalState
M
T
F
F
T
administrativeState
M
T
T
F
T
controlLoopLifeCyclePhase
M
T
T
F
T
aCCLDis... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.1.3 Constraints
| Name
Definition
networkSliceSubnetRef
Condition: if the use of an ACCL with a NetworkSliceSubnet is supported.
networkSliceRef
Condition: if the use of an ACCL with a NetworkSlice is supported.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.1.4 Notifications
| The common notifications defined in clause 4.1.2.5 are valid for this IOC, without exceptions or additions.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.2 AssuranceGoal
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.2.1 Definition
| This IOC represents assurance goal.
To express a new assurance goal for the assurance closed control loop, the MnS consumer needs to request the MnS producer to create an instance of AssuranceGoal. MnS producer can also trigger the creation of an instance of AssuranceGoal. For example, when a new instance NetworkSli... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.2.2 Attributes
| The AssuranceGoal IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and the following attributes:
Attribute name
S
isReadable
isWritable
isInvariant
isNotifyable
assuranceTargetList
M
T
F
F
T
sliceProfileId
CM
T
T
F
T
serviceProfileId
CM
T
T
F
T
observationTime
M
T
T
F
... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.2.3 Attribute constraints
| Name
Definition
sliceProfileId
Condition: if the use of sliceProfile parameters with an AssuranceGoal is supported.
serviceProfileId
Condition: if the use of serviceProfile parameters with an AssuranceGoal is supported.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.2.4 Notifications
| The common notifications defined in subclause 4.1.2.5 are valid for this IOC, without exceptions or additions.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.3 Void
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.4 Void
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.5 AssuranceTarget <<dataType>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.5.1 Definition
| This data type represents a single attribute name-value-pair of which one or more are included in an AssuranceGoal.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.5.2 Attributes
| Attribute name
S
isReadable
isWritable
isInvariant
isNotifyable
assuranceTargetName
M
T
T
F
T
assuranceTargetValue
M
T
F
F
T
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.5.3 Attribute constraints
| No constraints have been defined for this document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.5.4 Notifications
| The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.6 AssuranceGoalStatus <<dataType>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.6.1 Definition
| This data type represents the observed and/or predicted AssuranceGoal fulfilment status.
To obtain the observed predicted status of the the goal fulfilment information, the MnS consumer can query the attributes “AssuranceGoalStatusObserved” and “AssuranceGoalStatusPredicted”from MnS producer. The attributes “Assurance... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.6.2 Attributes
| Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
assuranceGoalStatusId
M
T
F
F
T
assuranceGoalId
O
T
F
F
T
assuranceGoalStatusObserved
O
T
F
F
T
assuranceGoalStatusPredicted
O
T
F
F
T
assuranceTargetStatusList
O
T
F
F
T
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.6.3 Attribute constraints
| No constraints have been defined for this document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.6.4 Notifications
| The common notifications defined in clause 4.1.2.5 are valid for this <<IOC>> , without exceptions or additions.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.7 AssuranceTargetStatus <<dataType>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.7.1 Definition
| This data type represents the observed and/or predicted target fulfilment status.
To obtain the observed predicted status of the the target fulfilment information, the MnS consumer can query the attributes “AssuranceTargetStatusObserved” and “AssuranceTargetPredicted” from MnS producer. The attributes“AssuranceTargetS... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.7.3 Attribute constraints
| No constraints have been defined for this document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.7.4 Notifications
| The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.8 AssuranceReport <<IOC>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.8.1 Definition
| This class represents the attributes of assurance report, e.g, the information about one or multiple AssuranceGoalStatus and one or multiple AssuranceTargetStatus.
The attribute “assuranceGoalStatusList” defines a list of AssuranceGoalStatus.
AssuranceReport represents the monitoring information of an assurance close... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.8.2 Attributes
| Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
assuranceGoalStatusList
O
T
F
F
T
Attributes related to role
assuranceGoalRef
O
T
F
F
T
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.8.3 Attribute constraints
| No constraints have been defined for this document
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.8.4 Notifications
| The common notifications defined in subclause 4.1.2.5 are valid for this IOC, without exceptions or additions.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.9 AssuranceScope <<dataType>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.9.1 Definition
| It indicates the target for assurance goal in terms of location. A particular ACCL can target for a particular location. The assurance goal status is ascertained based on the appropriately collected performance measurements as per the target location.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.9.2 Attributes
| Attribute name
S
isReadable
isWritable
isInvariant
isNotifyable
taiList
O
T
F
F
T
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.9.3 Attribute constraints
| No constraints have been defined for this document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.9.4 Notifications
| The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.10 ACCLDisallowedAttributes <<datatype>>
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.10.1 Definition
| This data type represents attributes which an ACCL is not allowed to change. The first attribute “managedEntityIdentifier” identifies the DN of the SubNetwork or ManagedElement, the second attribute is a list of attributeNames of the Subnetwork or ManagedElement.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.10.2 Attributes
| Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
managedEntityIdentifier
M
T
T
F
T
attributeNameList
M
T
T
F
T
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.3.10.3 Constraints
| No constraints have been defined for this document.
4.1.2.3.10 .4 Notifications
The common notifications defined in clause 4.1.2.5 are valid for this IOC, without exceptions or additions.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.4 Attribute definitions
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.4.1 Attribute properties
| The following table defines the properties of attributes that are specified in the present document.
Table 4.1.2.4.1.1
Attribute Name
Documentation and Allowed Values
Properties
controlLoopLifeCyclePhase
It indicates the lifecycle phase of the AssuranceClosedControlLoop instance.
AllowedValues: PREPARATION, C... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.4.2 Constraints
| No constraints have been identified for this document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.4.3 Notifications
| This subclause presents a list of notifications, defined in TS 28.532 [7], that provisioning management service consumer can receive. The notification parameter objectClass/objectInstance, defined in TS 32.160 [10], would capture the DN of an instance of an IOC defined in the present document.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.5 Common notifications
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.5.1 Alarm notifications
| This clause presents a list of notifications, defined in TS 28.111 [19], that an MnS consumer may receive. The notification header attribute objectClass/objectInstance, defined in TS 32.302 [8], shall capture the DN of an instance of a class defined in the present document.
Name
Qualifier
Notes
notifyNewAlarm
M
... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.5.2 Configuration notifications
| This clause presents a list of notifications, defined in TS 28.532 [7], that an MnS consumer may receive. The notification header attribute objectClass/objectInstance, defined in TS 32.302 [8], shall capture the DN of an instance of a class defined in the present document.
Name
Qualifier
Notes
notifyMOICreation
O
... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.3 Procedures
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.3.1 SLS Assurance Procedure
|
Figure 4.1.3.1.1 SLS assurance procedure
For the purpose of the procedure shown in Figure 4.1.3.1.1 "entities participating in the loop" refers to any entity in the 3GPP management system responsible for the functioning of an ACCL to ensure the AssuranceControlLoopGoal required by an AssuranceControlLoop_Consumer.
... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.2 Stage 3
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.2.1 Solution Set (SS) for JSON/YAML
| The OpenAPI/YAML definitions are specified in 3GPP Forge, refer to clause 4.3 of TS 28.623 [x] for the Forge location. An example of Forge location is: "https://forge.3gpp.org/rep/sa5/MnS/-/tree/Tag_Rel18_SA104/".
Directory: OpenAPI
File: TS28536_CoslaNrm.yaml
Annex A (informative):
Control loop deployed in differe... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 1 Scope | The present document studies the architecture support of Ambient IoT Devices, based on the services requirements defined in TS 22.369 [2] applicable to the Device types, traffic types, use cases and connectivity topologies defined in TR 38.769 [8]. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 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.
- Fo... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 3 Definitions of terms and abbreviations | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Ambient IoT Device: An Ambient IoT device is an IoT device powered by energy harvesting, with limite... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
AIoT Ambient IoT
DO-A Device-originated - autonomous
DO-DTT Device-originat... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 4 Architectural Assumptions and Requirements | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 4.1 Architectural Assumptions | - The following traffic types for Ambient IoT Device are to be studied:
- DT: Device-terminated; and
- DO-DTT: Device-originated - device-terminated triggered.
NOTE 1: The DO-DTT additionally includes traffic from AIoT Devices, which is triggered by RAN/UE as reader, without CN sending traffic towards the AIoT Devices.... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 4.2 Architectural Requirements | The following architectural requirements are applicable to this study:
- Support for AIoT Services needs to adhere to the nature of the AIoT Devices (e.g. ultra-low complexity, power, cost and resource-constrained).
- Support of the security aspects needs to consider the nature of the AIoT Devices (e.g. ultra-low compl... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5 Key Issues | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.1 Key Issue #1: Architecture support of Ambient IoT Devices | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.1.1 Description | This key issue will address the system architecture to support Ambient IoT Devices, especially on the following aspects:
- System architecture identified along with the solutions for KI#2 and KI#3.
- Authentication and authorization for the Ambient IoT Device;
- Validation of the Ambient IoT Device identifier;
NOTE 1: ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.2 Key Issue #2: Identification, Subscription, Registration and Connection management | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.2.1 Description | This Key Issue pertains to the authorization and management of Ambient IoT Devices to support Ambient IoT services.
Considering that Ambient IoT Devices are a new type of reduced capabilities devices, the existing subscription model may not be suitable. Specifically, there is the need to study the device identification... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.3 Key Issue #3: Support of Ambient IoT Services | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 5.3.1 Description | This Key Issue pertains to the AIoT services. Considering that AIoT Devices are a new type of devices with reduced capabilities, the following need to be supported:
- Inventory.
- Command.
NOTE 1: Further detailing of the inventory and commands will be addressed by solutions.
The key issue will study the following aspe... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6 Solutions | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
Key Issue #1
Key Issue #2
Key Issue #3
#1
X
#2
X
#3
X
X
X
#4
X
X
X
#5
X
X
X
#6
X
X
X
#7
X
X
#8
X
X
#9
X
X
X
#10
X
X
#11
X
#12
X
X
X
#13
X
#14
X
#15
X
X
#16
X
#17
X
X
X
#18
X
#19
X
X
#20
X
X
X
#21
X
X
X
#22
X
X
X
#23
X
#24
X
#25
X
#26
X
#27
X
#28
X
#29... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.1 Solution #1: AIoT Temporary Identifier Control | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.1.1 Description | This solution addresses KI#2. The basic principle in 5GS is that the permanent subscriber identifier shall never be sent in clear text over Uu interface and a UE temporary identifier shall only be sent over Uu interface in clear text once e.g. when the UE is paged. This solution propose that same principle shall apply ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.1.2 Procedures | As the available power in an AIoT device is very limited, the message exchange between the device and the network must be minimized. The solution is based on the following principle:
- The initial temporary identifier (TempID) is known by both the CN NF and the AIoT device. After the AIoT device has been onboarded to t... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.1.3 Impacts on services, entities and interfaces | Impacts on existing entities:
CN NF:
- Support the AIoT TempID handling including the generation of initial TempID, new TempID and re-synchronization between AIoT device and CN NF.
AIoT device:
- Recieving a initial TempID from the network.
- Generation of new TempID locally, when TempID used over Uu interface.
- re-sy... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.2 Solution #2: AIoT Device ID with home network, owner and instance identification | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.2.1 Description | This solution addresses the KI#2 and the aspect about how to identify and format the identifier of Ambient IoT Device in order to identify specific Ambient IoT Device or a group of Ambient IoT Devices.
In this solution, it is assumed that the Ambient IoT Device is configured with 3GPP-defined identifier and optionally ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.2.2 Procedures | How to utilize such format of Ambient IoT Device ID when network performs service operations will be specified in the call flows in other solutions. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.2.3 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing services, entities and interfaces. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3 Solution #3: Lightweight Ambient IoT system | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.1 Introduction | This solution proposes a lightweight Ambient IoT system. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.2 Definitions | - Command: Refers to an instruction sent by an AF to an AIoT Device. The following instructions may be supported:
- Read: Reading data from an AIoT Device;
- Write: Writing data to an AIoT Device;
- Disable: Disable an AIoT Device temporarily or permanently.
- Command Response: Refers to the message sent by an AIoT Dev... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.3 Assumptions | This solution makes the following assumptions:
- Commands and Command Responses are end-to-end protected between AF and AIoT Device.
NOTE 1: Details of the end-to-end protection of Commands and Command Results are assumed to be addressed by SA WG3.
- Commands and Command Responses are transparent to the AIoT Controller... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.4 Reference architecture | This solution proposes the reference architecture depicted in Figure 6.3.1.4-1 and Figure 6.3.1.4-2.
Figure 6.3.1.4-1: Ambient IoT system architecture for Topology 1
Figure 6.3.1.4-2: Ambient IoT system architecture for Topology 2
The Ambient IoT system can support different deployment options. For example, the Reader ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.5 Network function description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.5.1 Reader | The Reader supports the following functionality:
- Supports the A-Uu air interface towards Ambient IoT Devices.
- Registers with an AIoT Controller.
- Supports the following functionality based on requests from an AIoT Controller:
- Perform one-time or periodic Inventory, deliver Inventory result to AIoT Controller.
- ... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.5.2 AIoT Controller | The AIoT Controller supports the following functionality:
- Register Readers.
- Authenticate and authorize AFs.
- Based on requests from an AF:
- Verify whether an AF is entitled to issue a specific Inventory Request.
- Select Readers to fulfil Inventory or Command request by AFs.
- Forward Inventory request to Readers... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.5.3 AF | The AF is assumed to support the following functionality:
- Authenticate towards the AIoT Controller.
- Send Inventory and Command Requests.
- Receive Inventory Responses and Command Responses.
NOTE: The AF is assumed to be preconfigured with the IP address or FQDN of the AIoT Controller. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.6 Protocol Stacks | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.6.1 Protocol Stack between Reader and AIoT Controller | Legend:
- Reader Application Protocol (R-AP): Application Layer Protocol between the Reader and the AIoT Controller.
- Service-based Interface (SBI) Protocol Stack: The protocol stack for service-based interfaces as defined in TS 29.500 [9].
Figure 6.3.1.6.1-1: Control Plane between Reader and AIoT Controller for Topol... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.1.6.2 Protocol Stack between AIoT Device and Application Function | Legend:
- Reader Application Protocol (R-AP): Application Layer Protocol between the Reader and the AIoT Controller.
- Service-based Interface (SBI) Protocol Stack: The protocol for service-based interfaces as defined in TS 29.500 [9].
- AIoT API: The API between AIoT Controller and Application Function to support Inve... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.2 Procedures | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.2.1 Inventory procedure | Figure 6.3.2.1: Inventory procedure
1. The AF sends an Inventory Request to the AIoT controller. The AF may optionally include the following information:
- Filter Criteria to limit the inventory to AIoT Devices matching those criteria;
NOTE 1: If the AF does not provide Filter Criteria, then a full inventory of all AIo... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.2.2 Command procedure | Figure 6.3.2.2: Command procedure
1. The AF issues a Send Command request, which includes the Command to be sent and either:
- a list of Device IDs that the Command is destined to; or
- Filter Criteria that identify the AIoT Devices that are supposed to act upon the Command.
In addition, if the AF provides Filter Crite... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.3.3 Impacts on services, entities and interfaces | New network entities and interfaces are proposed. |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4 Solution #4: Simplified system for AIoT | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1 Description | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.1 General | The solution addresses KI#1, #2 and KI#3.
It provides an e2e solution to support AIoT services with regard to topology1 and 2.
Figure 6.4.1.1-1: Topology 1&2
The following assumptions are taken into account for the solutions
- No matter what Topologies are applied (including more topologies in future release), The Topo... |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.2 Abbreviations | |
ce341a3dae2443be0e0b63ccc8ca34c3 | 23.700-13 | 6.4.1.3 Terms | The following terms are used for the solution:
- AIoT operation: the operation with communicating to AIoT devices, e.g. inventory and command.
- Inventory: filter and/or discovery one or multiple Ambient IoT device(s).
- Command: e.g. read, write, control, enable or disable one or multiple Ambient IoT device(s).
- AIoT... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.