Environmental internet of things system

Abstract

An Ambient Internet of Things (AIoT) system includes an AIoT service function (ASF) configured to facilitate delivery of AIoT services through non-access stratum (NAS) signaling. The ASF is responsible for AIoT service activation and / or deactivation, AIoT device state management, AIoT tag management, AIoT service management, relaying one or more information elements or data, handling AIoT service charging, AIoT service charging, and / or interacting with an access and mobility management function (AMF), a unified data management (UDM), and one or more AIoT service providers.

Description

Technical Field

[0001] This disclosure relates to the field of communication systems, and more specifically, to environmental Internet of Things (AIoT) systems. Background Technology

[0002] Ambient Internet of Things (AIoT) devices are IoT devices powered by ambient energy, primarily through energy harvesting. AIoT devices can operate without batteries or have limited energy storage capabilities, such as using capacitors. Unlike other devices like Narrowband Internet of Things (NB-IoT), mobile phones, and 5G residential gateways (RGs), AIoT devices have unique characteristics. One of the defining features of AIoT devices is their reliance on energy harvesting. AIoT devices have no batteries and limited energy storage capabilities. In other words, their online time is very limited, relying either on harvested energy for power or on the limited energy storage on the device to extend communication or runtime. This energy constraint limits AIoT devices to communicating with fifth-generation (5G) systems only within a narrow time window. Based on these limitations, a communication protocol stack must be designed that is not only lightweight but also ensures rapid communication establishment, minimizes the number of interactions, optimizes energy efficiency, and accelerates communication initiation. However, current technological solutions do not provide this specific AIoT service functionality tailored to the unique needs of AIoT devices. Furthermore, current 5G systems lack the architecture and protocol stack to support such communication by AIoT devices.

[0003] Therefore, there is a need for an AIoT system that can solve the problems in existing technologies and other issues. Summary of the Invention

[0004] The purpose of this disclosure is to propose an Environmental Internet of Things (AIoT) system that addresses problems in the prior art and other issues, providing an efficient and lightweight architecture and communication that ensures rapid communication establishment, reduces the number of interactions, improves energy efficiency, and / or accelerates communication initiation.

[0005] In one aspect of this disclosure, an Ambient Internet of Things (AIoT) system includes an AIoT Service Function (ASF) configured to facilitate the delivery of AIoT services via Non-Access Stratum (NAS) signaling.

[0006] Optionally, in some embodiments, the ASF is responsible for at least one of the following duties: AIoT service activation and / or deactivation, AIoT device status management, AIoT tag management, AIoT service management, forwarding one or more information elements or data from one or more AIoT tags and / or AIoT readers to one or more AIoT service providers, application servers, or application functions (AFs), processing AIoT service billing, relaying one or more information elements or data from one or more AIoT service providers, application servers, or AFs to AIoT readers and / or one or more AIoT tags, AIoT service billing, and interacting with the Access and Mobility Management Function (AMF), Unified Data Management (UDM), and one or more AIoT service providers to perform one or more notification processes when AIoT tags are unable to transmit information.

[0007] Optionally, in some embodiments, the AIoT system includes an AMF, and the AMF is responsible for at least one of the following duties: ASF selection, AIoT tag registration, accessibility management and / or mobility management, access authentication and / or authorization, providing the transmission of one or more AIoT service information elements between the AIoT reader and the ASF, and relaying one or more information elements or data to and / or from the ASF.

[0008] Optionally, in some embodiments, the AIoT system further includes an AIoT AF and / or an AIoT AS, wherein the ASF allows the AIoT AF and / or the AIoT AS to issue one or more commands to an AIoT reader and / or one or more AIoT tags to support one or more AIoT services.

[0009] Optionally, in some embodiments, the AIoT system also includes a UDM, which is responsible for AIoT service subscription data.

[0010] Optionally, in some embodiments, the ASF supports at least one of the following service operations: activation operation, deactivation operation, AIoT uplink data operation, and / or AIoT command operation.

[0011] Optionally, in some embodiments, the AIoT system also includes one or more AIoT tags having one or more NAS capabilities.

[0012] Optionally, in some embodiments, the one or more AIoT tags having one or more NAS capabilities are configured to perform at least one of the following signaling procedures: registration request procedure, service request procedure, message transmission service procedure, and paging procedure.

[0013] Optionally, in some embodiments, the AIoT system further includes a protocol stack for the one or more AIoT tags having one or more NAS capabilities.

[0014] Optionally, in some embodiments, the AIoT system further includes one or more AIoT tags that do not have NAS capabilities.

[0015] Optionally, in some embodiments, the one or more AIoT tags that do not have NAS capability are configured to perform at least one of the following signaling procedures: registration request procedure, service request procedure, message transmission service procedure, and paging procedure.

[0016] Optionally, in some embodiments, the AIoT system further includes a protocol stack for one or more AIoT tags that do not have NAS capabilities.

[0017] Optionally, in some embodiments, the AIoT system further includes a Tag Service Layer (TSL), and when one or more AIoT tags are requested to provide information to the AIoT reader, the TSL issues one or more commands to retrieve information from one or more AIoT tags.

[0018] Optionally, in some embodiments, the AIoT service subscription data in the UDM is configured to select a service ASF for one or more AIoT tags. Attached Figure Description

[0019] To more clearly illustrate the embodiments of this disclosure or related technologies, the following drawings will be described in the brief introduction of the embodiments. Obviously, the drawings are only some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings with creative effort. Figure 1A This is a block diagram of an Ambient Internet of Things (AIoT) system configured to implement AIoT service functions (ASF) employing reference point notation, as presented in some embodiments herein.

[0020] Figure 1B This is a block diagram of an AIoT system that includes an ASF configured to implement some of the embodiments presented herein, using a service-based interface.

[0021] Figure 2 This is a block diagram illustrating an AIoT system that includes an architecture for one or more AIoT tags / devices having one or more non-access stratum (NAS) capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein.

[0022] Figure 3 This is a block diagram illustrating an AIoT system that includes a protocol stack for one or more AIoT tags / devices having one or more NAS capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein.

[0023] Figure 4 This is a block diagram illustrating an AIoT system that includes an architecture for one or more AIoT tags / devices that do not have NAS capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein.

[0024] Figure 5 This is a block diagram illustrating an AIoT system that includes a protocol stack for one or more AIoT tags / devices that do not have NAS capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein.

[0025] Figure 6 This is a block diagram of an AIoT system that includes a publish / subscribe architecture deployment for an ASF configured to implement some of the embodiments presented herein.

[0026] Figure 7 This is a block diagram of an example computing device according to embodiments of the present disclosure.

[0027] Figure 8 This is a block diagram of a communication system according to an embodiment of the present disclosure. Detailed Implementation

[0028] The technical features, structural characteristics, objectives, and effects of embodiments of this disclosure are described in detail below with reference to the accompanying drawings. Specifically, the terminology used in the embodiments of this disclosure is only used to describe the purpose of a particular embodiment and is not intended to limit this disclosure.

[0029] For clarity, throughout this disclosure, the terms "AIoT tag" and "AIoT device," as well as other similar terms, are interchangeable and do not differ in meaning. The terms "environmental IoT node," "environmental IoT reader," "AIoT node," "AIoT reader," simply "reader," and other similar terms are interchangeable and do not differ in meaning. The terms "AIoT base station," "base station with AIoT capability," "environmental IoT base station," and other similar terms are interchangeable and do not differ in meaning throughout this disclosure. The terms "network element" and "network node," as well as other similar terms, are interchangeable and do not differ in meaning. The terms "standalone" and "independent," as well as other similar terms, are interchangeable and do not differ in meaning.

[0030] In some implementations, the term " / " can be interpreted as indicating "and / or". The term "configuration" can refer to "pre-configuration" and "network configuration". The terms "predefined" or "predefined rules" in this disclosure can be implemented by pre-storing corresponding codes, tables, or other means in devices (e.g., including AIoT tags / tags and network devices) to indicate relevant information. Specific implementations are not limited in this disclosure. For example, "predefined" can refer to those defined in a protocol. It should also be understood that in this disclosure, "protocol" can refer to standard protocols in the communications field, which may include, for example, the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied to future communication systems, which are not limited in this disclosure.

[0031] Some embodiments of this disclosure provide an Environmental Internet of Things (AIoT) system including an AIoT Service Function (ASF) configured to facilitate the delivery of AIoT services via Non-Access Stratum (NAS) signaling. This addresses problems in the prior art and other issues, providing an efficient and lightweight architecture and communication, ensuring rapid communication establishment, reducing the number of interactions, improving energy efficiency, and / or accelerating communication initiation.

[0032] In some embodiments, AIoT services based on a NAS architecture, protocol stack, and publish / subscribe architecture are disclosed for deployment scenarios. When communication originates from an AIoT tag (e.g., in some cases where the AIoT tag has NAS capabilities) or from an AIoT reader (e.g., in RICO mode, i.e., reactive interactive connections only or reader-initiated connections only), data or information elements are transmitted via uplink NAS transmission. Conversely, for communication terminated at the AIoT tag (e.g., in some cases where the AIoT tag has NAS capabilities) or at the AIoT reader, delivery of data or information elements is performed via N1 / N2 messages. This process eliminates the need to establish a PDU session and does not require the involvement of Session Management Function (SMF) and User Plane Function (UPF). This approach significantly reduces the complexity of the protocol stack.

[0033] It's worth noting that a Non-Access Stratum Session Management (NAS-SM) layer is not required in this configuration. Instead, the simplified AIoT service is effectively positioned to run directly on top of the Non-Access Stratum Mobility Management (NAS-MM) layer. NAS-SM: It supports session management between the UE and the SMF. It supports user plane PDU session establishment, modification, and release. It is transmitted through the AMF and is transparent to the AMF. NAS-MM: It supports registration management functions, connection management functions, and user plane connection activation and deactivation. It is also responsible for the encryption and integrity protection of NAS signaling.

[0034] Figure 1A An Ambient Internet of Things (AIoT) system is shown, which includes AIoT service functions (ASF) configured to implement some embodiments presented herein using reference point notation. Figure 1B An AIoT system is illustrated, which includes an ASF configured to implement some embodiments presented herein, using a service-based interface. Figure 1A and Figure 1B In the exemplary architecture shown, the traditional SMF and UPF are replaced by simplified network functions such as AIoT Service Functions (ASF). The ASF facilitates the delivery of AIoT services through NAS signaling without establishing a Protocol Data Unit (PDU) session.

[0035] In some embodiments, the ASF is responsible for at least one of the following duties: AIoT service activation and / or deactivation, AIoT device status management, AIoT tag management, AIoT service management, relaying one or more information elements or data from one or more AIoT tags and / or AIoT readers to one or more AIoT service providers, application servers, or application functions (AFs), processing AIoT service billing (such as related AIoT service billing aspects), and relaying one or more information elements or data from one or more AIoT service providers, application servers, or AFs to an AIoT reader and / or a... This involves interaction with multiple AIoT tags (oriented towards the AIoT reader and ultimately to the AIoT tag), AIoT service billing, and, when the AIoT tag is unable to transmit information, interaction with the Access and Mobility Management Function (AMF) via an interface in Reference Point Notation (tentatively N11x) or a service-based interface (tentatively Nasf); interaction with the Unified Data Management (UDM) via an interface in Reference Point Notation (tentatively N8a) or a service-based interface Nudm and a service-based interface (tentatively Nasf); or interaction with one or more AIoT service providers to execute one or more notification processes. In some examples, AIoT device state management includes temporary disable / enable, permanent disable, power off, hibernate, sleep, activate, and / or charging / energy harvesting / energy collection, etc. In some examples, the AS or AF can be a third-party AS or a third-party AF.

[0036] It should be noted that the reference point notation or service-based notation for interfaces N8a, N11x, and Nasf are placeholders and their final names will be adopted after standardization.

[0037] In some embodiments, the AIoT system includes an AMF. Furthermore, in addition to the existing functions currently defined in the relevant 3GPP specifications, the AMF is also responsible for at least one of the following new functions: ASF selection, AIoT tag registration, accessibility management and / or mobility management, access authentication and / or authorization, providing the transmission of one or more AIoT service information elements between the AIoT reader and the ASF, and relaying one or more information elements or data to and / or from the ASF.

[0038] In some examples, the AIoT Service Function (ASF) interacts with the AMF to support bidirectional environmental IoT communication via NAS signaling in 5G systems. When the AIoT Service Function triggers a service request, it allows the AMF to forward uplink data originating from an AIoT tag or AIoT reader, and further forward it to the AIoT Application Function (AF) and the AIoT Application Server (AS).

[0039] In some embodiments, the AIoT system also includes an AIoT AF and / or an AIoT AS, which enables the AIoT AF and / or AIoT AS to issue one or more commands to an AIoT reader and / or one or more AIoT tags to support one or more AIoT services. For example, AIoT service functions enable the AIoT AF and AS to issue commands to the AIoT reader or AIoT tag to support AIoT tag disabling, shutting down, pausing, energy harvesting, energy indication, and various AIoT services such as inventory, sensor, positioning, command / actuator, etc.

[0040] In some embodiments, the AIoT system also includes a UDM, which is responsible for AIoT service subscription data. Specifically, in some examples, the ASF connects to the UDM via a service-based interface to provide 5G AIoT services to 5G subscribers. Table 1 shows a list of environmental IoT service subscription data in the UDM.

[0041] Table 1: Environmental IoT Service Subscription Data

[0042] ASF supports at least one of the following service operations: activation, deactivation, AIoT uplink data operation, and / or AIoT command operation. In some examples, ASF supports one or more service operations as shown in Table 2.

[0043] Table 2: ASF Service Operations

[0044] Figure 2 An AIoT system is illustrated, comprising an architecture for one or more AIoT tags / devices having one or more Non-Access Stratum (NAS) capabilities, said one or more AIoT tags / devices being configured to implement some embodiments presented herein. In some embodiments, the AIoT system also includes one or more AIoT tags having one or more NAS capabilities. In some examples, Figure 2An exemplary architecture for an AIoT device with NAS capability in the presence of an ASF is shown.

[0045] Figure 2 As illustrated in some examples, an AIoT base station / gNB may include a module (e.g., an AIoT reader) designed to transmit radio waves to activate AIoT tags, supporting communication protocols that ensure interaction between the AIoT base station / gNB and the AIoT tags, and handling related 5G environmental IoT processes via N1 and N2 interfaces. The radio waves may take the form of a carrier wave to provide a carrier frequency for backscatter communication between environmental IoT devices and the AIoT reader. The radio waves may also take the form of a continuous wave to provide an energy harvesting source for surrounding IoT devices. Alternatively, the radio waves may be a combination of carrier and continuous waves to provide both a carrier frequency and an energy harvesting source.

[0046] Alternatively, an external radio wave generator can be located outside the AIoT base station / gNB. The radio wave generator can operate independently by transmitting a carrier wave or continuous wave for the tag to perform backscatter communication / energy harvesting, or it can transmit a carrier wave or continuous wave via a defined communication interface under the control of the AIoT base station / gNB to allow the AIoT device to perform backscatter communication / energy harvesting.

[0047] In some embodiments, one or more AIoT tags with one or more NAS capabilities are configured to perform at least one of the following signaling flows: registration request flow, service request flow, message transmission service flow, and paging flow.

[0048] Specifically, in some examples, the AIoT tag becomes active when it accumulates sufficient energy from the reader's radio waves or periodic power transfer. For AIoT tags with NAS signaling capabilities, the AIoT tag can initiate registration requests, service requests, and other signaling processes. These messages are transmitted to the AMF via the AIoT base station / gNB or simply by the AIoT reader using UL NAS transmission. The AMF then forwards these messages and the Ambient IoT identifier to the AIoT Service Function (ASF) via the N11x / NASF interface.

[0049] Specifically, in some examples, the ASF can invoke the Namf_Communication_N1N2 MessageTransfer service to send an acknowledgment message to the AMF.

[0050] Specifically, in some examples, a specific environmental IoT paging procedure is required for communication termination by environmental IoT devices. Once the AIoT tag is located, the Namf_communicaiton_N1N2 message uses NAS signaling to deliver AIoT service data to the AIoT tag.

[0051] Figure 3 An AIoT system is illustrated, comprising a protocol stack for one or more AIoT tags / devices having one or more NAS capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein. In some embodiments, the AIoT system further includes a protocol stack for the one or more AIoT tags having one or more NAS capabilities. Figure 3 The protocol stack for AIoT devices with NAS capabilities is shown in the presence of ASF.

[0052] Figure 4 An AIoT system is illustrated, comprising an architecture for one or more AIoT tags / devices without NAS capabilities, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein. In some embodiments, the AIoT system also includes one or more AIoT tags without NAS capabilities. Figure 4 An architecture for AIoT devices without NAS capabilities is shown in the presence of an ASF. Specifically, Figure 4 The diagram shows that in some examples, the AIoT tag does not have NAS signaling capabilities. An AIoT reader residing on the AIoT base station / gNB performs the NAS signaling function on behalf of the AIoT tag. In some examples, the AIoT tag becomes activated when it accumulates sufficient energy from the reader's radio waves or through periodic power transfer.

[0053] In some embodiments, one or more AIoT tags that do not have NAS capability are configured to perform at least one of the following signaling procedures: registration request procedure, service request procedure, message transmission service procedure, and paging procedure.

[0054] In some examples, procedures for AIoT devices without NAS capabilities are disclosed in the presence of an ASF. In some examples, for AIoT tags without NAS signaling capabilities, for communications initiated by the AIoT tag / device, upon request from the AIoT tag / device, the AIoT reader or AIoT base station / gNB initiates registration, service requests, and other signaling procedures on behalf of the tag. The AIoT reader or AIoT base station / gNB utilizes uplink (UL) NAS transmission to transmit data collected from individual or grouped tags to the AMF. Subsequently, the AMF forwards the messages and AIoT tag identifiers to the AIoT Service Function (ASF) via the N11x / NASF interface. In some examples, the ASF may use the Namf_Communication_N1N2 Message Transfer service to send acknowledgment messages back to the AMF.

[0055] Figure 5 An AIoT system is illustrated, comprising a protocol stack for one or more AIoT tags / devices that do not have NAS capability, the one or more AIoT tags / devices being configured to implement some of the embodiments presented herein. In some embodiments, the AIoT system further includes a protocol stack for one or more AIoT tags that do not have NAS capability. In other words, a protocol stack for AIoT devices that do not have NAS capability is disclosed in the presence of ASF.

[0056] In some examples, within the protocol stack, the Tag Service Layer (or other similar names / terms, such as Data Service Layer, AIoT Tag Service Layer, AIoT Service Layer, or simply AIoT Layer) is responsible for processing information defined by the environmental IoT service provider, environmental IoT network operator, environmental IoT device manufacturer, or end user. In some examples, when a reader requests to perform such an operation, the Tag Service Layer (TSL) may simply provide a response reporting its EPC (Electronic Product Code) code, and once activated, the reader can further extract relevant information from the tagged object. In some examples, the TSL layer may be responsible for interpreting commands issued by the reader or by the AIoT application server.

[0057] In some embodiments, the AIoT system also includes a Tag Service Layer (TSL), which issues one or more commands to retrieve information from one or more AIoT tags when one or more AIoT tags are requested to provide information to the AIoT reader.

[0058] In some examples, when an AIoT tag is queried to provide information to a requested AIoT reader, the Tag Service Layer (TSL) can issue commands to retrieve the requested information from the AIoT tag's memory, to request the lower layer to encode the information using an appropriate encoding format, and to request the lower layer to transmit the requested information in an appropriate radio frequency (RF) signal format.

[0059] exist Figure 5 In some examples, simplified protocol stacks can also help establish connections and exchange data quickly and efficiently. Because AIoT tags have limited power, such protocol stacks can quickly establish connections and exchange data rapidly and efficiently.

[0060] Figure 6 An AIoT system is illustrated, comprising a publish / subscribe architecture deployment for an ASF configured to implement some of the embodiments presented herein. In some embodiments, AIoT service subscription data in a UDM is configured as one or more AIoT tag selection service ASFs.

[0061] In some examples, considering the potential for millions of AIoT tags in real-world deployments, a flexible publisher / subscriber (Pub / Sub) system can be implemented as a possible embodiment to support scalability. Figure 6 In this context, AIoT tags T2 and T6 act as publishers and send messages related to both topic 1 and topic 2. According to the configuration in the tag subscription profile within the UDM, AIoT service subscription data is used to select a Service ASF for the AIoT tag or a group of AIoT tags.

[0062] In some examples, messages published by T2 are directed to ASF1. In some examples, messages published by T6 are directed to ASF2. In some examples, AIoT AS / AF1 subscribes to both topic 1 and topic 2, specifically from ASF1. Therefore, AIoT service AS / AF1 receives messages: M1, M2, M3, M4, and M5. On the other hand, AIoT service AS / AF2 subscribes to topic 2 from ASF1 and to topic 1 from ASF2. Therefore, it receives messages: M3, M4, M5, M6, and M7.

[0063] In some of the embodiments described above, an AIoT service based on a NAS architecture and protocol stack is proposed. When communication originates from an AIoT tag, AIoT reader, or AIoT base station / gNB (e.g., in RICO mode), data or information elements are transmitted via uplink NAS transmission. Conversely, for communication terminated at an AIoT tag, AIoT reader, or AIoT base station / gNB, delivery of data or information elements is performed via NAS N1N2 messages. This process eliminates the need to establish a PDU session and does not require the involvement of SMF and UPF. This approach significantly reduces the complexity of the protocol stack. Notably, a NAS-SM layer is not required in this configuration. Instead, the simplified AIoT service is effectively positioned to run directly on top of the NAS-MM layer.

[0064] In summary, in some embodiments, the exemplary lightweight architecture and protocol stack for environmental IoT services may include at least one of the following benefits.

[0065] Scalability: The architecture and protocol stack are scalable and can efficiently manage a large number of AIoT devices in the network without straining system resources.

[0066] Reduced latency: Simplified protocols and architectures enable faster data transmission and processing, minimizing latency so that AIoT tags can complete information exchange and transactions within limited energy storage time.

[0067] Greater reliability: Fewer components and complexity mean fewer points of failure, resulting in a more reliable system.

[0068] Cost efficiency: The lightweight architecture requires less processing power and storage, which also saves on the cost of AIoT tags.

[0069] Easier integration: Integrating AIoT devices into other systems or applications is simpler.

[0070] Adaptability: The introduction of dedicated AIoT service functionality (NF) means there is ample room to support further evolution of the server to accommodate evolving needs or emerging standards.

[0071] Lower maintenance: Easier and less frequent maintenance, resulting in longer service life and reduced downtime.

[0072] Some implementation schemes offer the following commercial benefits: 1. Solving problems and other issues in the prior art. 2. Providing an efficient and lightweight architecture and communication, ensuring rapid communication establishment, reducing the number of interactions, improving energy efficiency, and / or accelerating communication initiation. 3. Some embodiments of this disclosure can be used in many applications. Some embodiments of this disclosure are used by chipset suppliers, video system development suppliers, automobile manufacturers including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drones (unmanned aerial vehicles), smartphone manufacturers, communication equipment for public safety purposes, and AR / VR / MR device manufacturers (e.g., for gaming, conferences / seminars, educational purposes). Some embodiments of this disclosure are combinations of "technologies / processes" that can be adopted in video standards to create end products. Some embodiments of this disclosure propose technical mechanisms. At least one of the proposed solutions, methods, systems, and apparatuses of some embodiments of this disclosure can be used with respect to current and / or new / future standards related to communication systems. Compatible products follow at least one of the proposed solutions, methods, systems, and apparatuses of some embodiments of this disclosure. The proposed solutions, methods, systems, and apparatuses are widely used in communication systems. At least one modification / improvement of the energy-related routing method and apparatus proposed by implementing at least one of the embodiments of this disclosure is being considered for standardization.

[0073] Figure 7 This is an example of a computing device 1100 according to embodiments of the present disclosure. Any suitable computing device can be used to perform the operations described herein. For example, Figure 7 An example of a computing device 1100 is shown, which can use any appropriately configured hardware and / or software to implement Figures 1 to 1100. Figure 6 The apparatus and / or methods illustrated herein. In some embodiments, computing device 1100 may include processor 1112, which is communicatively coupled to memory 1114 and executes computer-executable program code and / or accesses information stored in memory 1114. Processor 1112 may include a microprocessor, application-specific integrated circuit (“ASIC”), state machine, or other processing device. Processor 1112 may include any of a plurality of processing devices, including one processing device. Such a processor may include, or be communicative to, a computer-readable medium storing instructions that, when executed by processor 1112, cause the processor to perform the operations described herein.

[0074] Memory 1114 may include any suitable non-transitory computer-readable medium. Computer-readable media may include any electronic, optical, magnetic, or other storage device capable of providing computer-readable instructions or other program code to a processor. Non-limiting examples of computer-readable media include disks, memory chips, read-only memory (ROM), random access memory (RAM), application-specific integrated circuits (ASICs), configured processors, optical storage devices, magnetic tape or other magnetic storage devices, or any other medium from which a computer processor may read instructions. Instructions may include processor-specific instructions generated by code written by a compiler and / or interpreter in any suitable computer programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript.

[0075] The computing device 1100 may also include a bus 1116. The bus 1116 may communicatively couple one or more components of the computing device 1100. The computing device 1100 may also include multiple external or internal devices, such as input devices or output devices. For example, the computing device 1100 is shown having an input / output (“I / O”) interface 1118 that can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. One or more input devices 1120 and one or more output devices 1122 may be communicatively coupled to the I / O interface 1118. The communication coupling may be implemented via any suitable means (e.g., via printed circuit board connection, via cable connection, via wireless transmission, etc.). Non-limiting examples of the input device 1120 include a touchscreen (e.g., one or more cameras for imaging a touch area or a pressure sensor for detecting pressure changes caused by a touch), a mouse, a keyboard, or any other device that can be used to generate input events in response to physical actions of a user of the computing device. Non-limiting examples of output device 1122 include liquid crystal display (LCD) screens, external monitors, speakers, or any other device that can be used to display or otherwise present output generated by a computing device.

[0076] The computing device 1100 can execute program code that configures the processor 1112 to perform the above-described description of Figures 1 to 1. Figure 6 One or more of the operations described in some of the embodiments shown. The program code may reside in memory 1114 or any suitable computer-readable medium and may be executed by processor 1112 or any other suitable processor.

[0077] The computing device 1100 may also include at least one network interface device 1124. The network interface device 1124 may include any device or group of devices adapted to establish wired or wireless data connections to one or more data networks 1128. Non-limiting examples of the network interface device 1124 include Ethernet network adapters, modems, etc. The computing device 1100 may transmit messages as electronic or optical signals via the network interface device 1124.

[0078] Figure 8 This is a block diagram of an example communication system 1200 according to an embodiment of the present disclosure. The embodiments described herein can be implemented in the communication system 1200 using any appropriately configured hardware and / or software. Figure 8 The communication system 1200 shown includes at least radio frequency (RF) circuitry 1210, baseband circuitry 1220, application circuitry 1230, memory / storage unit 1240, display 1250, camera 1260, sensor 1270, and input / output (I / O) interface 1280, which are coupled to each other as shown.

[0079] Application circuitry 1230 may include circuitry such as (but not limited to) one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (such as graphics processors, application processors). The processor may be coupled to memory / storage units and configured to execute instructions stored in the memory / storage units to enable various applications and / or operating systems running on the system. Communication system 1200 can execute program code that configures application circuitry 1230 to perform the above-described instructions regarding Figures 1 to 1230. Figure 6 One or more of the operations described. The program code may reside in application circuit 1230 or any suitable computer-readable medium and may be executed by application circuit 1230 or any other suitable processor.

[0080] The baseband circuit 1220 may include circuitry such as (but not limited to) one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various radio control functions that enable communication with one or more radio networks via RF circuitry. Radio control functions may include (but are not limited to) signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments of the baseband circuitry configured to support radio communication with more than one radio protocol may be referred to as a multi-mode baseband circuitry.

[0081] In various embodiments, the baseband circuit 1220 may include circuitry to operate using signals not strictly considered to be at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry that operates using signals having an intermediate frequency (IF), which is between the baseband frequency and the radio frequency (RF). The RF circuitry 1210 may use electromagnetic radiation modulated by a non-solid-state medium to enable communication with a wireless network. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with a wireless network. In various embodiments, the RF circuitry 1210 may include circuitry that operates using signals not strictly considered to be at the radio frequency. For example, in some embodiments, the RF circuitry may include circuitry that operates using signals having an intermediate frequency (IF), which is between the baseband frequency and the radio frequency.

[0082] In various embodiments, the above description regarding Figures 1 to 1... Figure 6 The transmitter circuitry, control circuitry, or receiver circuitry discussed in the illustrated apparatus and / or methods may be wholly or partially embodied in one or more of the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, “circuit” may refer to, be part of, or include: an application-specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), combinational logic circuitry, and / or other suitable hardware components that provide the described functionality, executing one or more software or firmware programs. In some embodiments, electronic device circuitry may be implemented in one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / storage cell may be implemented together on a system-on-a-chip (SOC). Memory / storage cell 1240 may be used to load and store, for example, data and / or instructions for the system. Memory / storage cell for one embodiment may include any combination of suitable volatile memory (such as dynamic random access memory (DRAM)) and / or non-volatile memory (such as flash memory).

[0083] In various embodiments, I / O interface 1280 may include one or more user interfaces and / or peripheral component interfaces, the user interfaces being designed to enable users to interact with the system, and the peripheral component interfaces being designed to enable peripheral components to interact with the system. The user interface may include (but is not limited to) a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. The peripheral component interfaces may include (but are not limited to) a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power interface. In various embodiments, sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information relevant to the system. In some embodiments, the sensor may include (but is not limited to) a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, baseband and / or RF circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0084] In various embodiments, display 1250 may include displays such as liquid crystal displays and touchscreen displays. In various embodiments, communication system 1200 may be a mobile computing device, such as (but not limited to) laptops, tablets, netbooks, ultrabooks, smartphones, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as computer programs. Computer programs may be stored on storage media, such as non-transitory storage media.

[0085] Those skilled in the art will understand that each unit, algorithm, and step described and disclosed in the embodiments of this disclosure is implemented using electronic hardware or a combination of computer software and electronic hardware. Whether a function operates in hardware or software depends on the application conditions and the design requirements of the technical solution. Those skilled in the art can use different methods to implement the functions for each specific application, and such implementations should not exceed the scope of this disclosure. Those skilled in the art will understand that since the workflows of the above-described systems, devices, and units are substantially the same, they can refer to the workflows of the systems, devices, and units in the above embodiments. For ease of description and simplification, these workflows will not be described in detail again.

[0086] It should be understood that the systems, devices, and methods disclosed in the embodiments of this disclosure can be implemented in other ways. The above embodiments are merely exemplary. The division of units is based solely on logical function, and other division methods may exist in actual implementation. Multiple units or components may be combined or integrated into another system. It is also possible to omit or skip some features. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed, whether in electrical, mechanical, or other forms, can be operated indirectly or communicatively through some ports, devices, or units.

[0087] The units used as illustrative components may or may not be physically separate. The units used for display may or may not be physical units; that is, they may be located in one location or distributed across multiple network units. Some or all of these units may be used depending on the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated into a processing unit, may be physically independent, or two or more units may be integrated into a single processing unit.

[0088] If a software functional unit is implemented and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solutions proposed in this disclosure can be implemented substantially or partially in the form of a software product. Alternatively, a portion of the technical solution that is beneficial to conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium, which includes multiple commands for a computing device (such as a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this disclosure. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other types of media capable of storing program code.

[0089] While this disclosure has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims

1. An environmental Internet of Things (AIoT) system, comprising: The AIoT Service Function (ASF) is configured to facilitate the delivery of AIoT services via Non-Access Stratum (NAS) signaling.

2. The AIoT system according to claim 1, wherein, The ASF is responsible for at least one of the following duties: AIoT service activation and / or deactivation; AIoT device status management; AIoT tag management; AIoT service management; Relay one or more information elements or data from one or more AIoT tags and / or AIoT readers to one or more AIoT service providers, application servers or application functions (AFs); Handling AIoT service billing; Relay one or more information elements or data from one or more AIoT service providers, application servers or AFs to AIoT readers and / or one or more AIoT tags; AIoT service billing; as well as When the AIoT tag is unable to transmit information, it interacts with the Access and Mobility Management Function (AMF), Unified Data Management (UDM), and one or more AIoT service providers to execute one or more notification processes.

3. The AIoT system according to claim 2, wherein, The AIoT system includes the AMF, and the AMF is responsible for at least one of the following duties: ASF selection; AIoT tag registration, accessibility management and / or mobility management; Access authentication and / or authorization; The transmission of one or more AIoT service information elements is provided between the AIoT reader and the ASF; and Relay the one or more information elements or the data to and / or from the ASF.

4. The AIoT system according to claim 2 or 3, wherein, The AIoT system further includes an AIoT AF and / or an AIoT AS, wherein the ASF allows the AIoT AF and / or the AIoT AS to issue one or more commands to the AIoT reader and / or the one or more AIoT tags to support one or more AIoT services.

5. The AIoT system according to any one of claims 2 to 4, wherein, The AIoT system also includes the UDM, and the UDM is responsible for AIoT service subscription data.

6. The AIoT system according to any one of claims 1 to 5, wherein, The ASF supports at least one of the following service operations: Activation operation; Deactivate the operation; AIoT uplink data operations; and / or AIoT command operations.

7. The AIoT system according to any one of claims 2 to 6, wherein, The AIoT system further includes one or more AIoT tags with one or more NAS capabilities.

8. The AIoT system according to claim 7, wherein, The one or more AIoT tags with one or more NAS capabilities are configured to perform at least one of the following signaling procedures: The registration request process, service request process, message transmission service process, and paging process.

9. The AIoT system according to claim 7 or 8, wherein, The AIoT system further includes a protocol stack for the one or more AIoT tags having one or more NAS capabilities.

10. The AIoT system according to any one of claims 2 to 6, wherein, The AIoT system further includes one or more AIoT tags that do not have NAS capabilities.

11. The AIoT system according to claim 10, wherein, One or more AIoT tags that do not have NAS capability are configured to perform at least one of the following signaling procedures: The registration request process, service request process, message transmission service process, and paging process.

12. The AIoT system according to claim 9 or 10, wherein, The AIoT system further includes a protocol stack for one or more AIoT tags that do not have NAS capabilities.

13. The AIoT system according to claim 12, wherein, The AIoT system further includes a Tag Service Layer (TSL), and when one or more AIoT tags are requested to provide information to the AIoT reader, the TSL issues one or more commands to retrieve the information from the one or more AIoT tags.

14. The AIoT system according to any one of claims 5 to 13, wherein, The AIoT service subscription data in the UDM is configured to select a service ASF for the one or more AIoT tags.

Images