Method and system for supporting passive internet of things service

Abstract

The invention discloses a method and a system for supporting a passive internet of things service. The method comprises the following steps: an AIoTAF sends an inspection / collection request to an AIoTMF; the AIoTMF determines a passive tag corresponding to the request and a service AMF and a service base station to which the passive tag belongs, and then forwards the checking / collecting request to the passive tag; the passive tag collects data, returns a normal or abnormal RRC message to the service base station, and sends the collected data to the service base station on the established data bearer; the service base station extracts label information from all normal RRC messages to form a normal label list, aggregates normal acquisition data into a normal data stream, returns the normal label list and the information of the service base station to the AIoTMF, sends the normal data stream to the AIoTMF, and sends the label information, the acquisition data and the information of the service base station in each abnormal RRC message to the AIoTMF; and the AIoTMF updates a label state according to the response message, aggregates all the abnormal acquisition data into an abnormal data stream, and sends the abnormal data stream to the AIoTMF. The invention relates to the technical field of Internet of Things, and can realize 5GC-based passive Internet of Things services.

Description

Technical Field

[0001] The present invention relates to a method and system for supporting passive Internet of Things (IoT) services, and relates to the technical field of IoT. Background Art

[0002] Passive IoT is one of the key directions for the evolution of future communication networks. Warehouse logistics, industrial parks, agriculture, animal husbandry, security, food and drug tracking, etc. are all key application scenarios of passive IoT in vertical industries. Internationally, the research work on the 5GC architecture supporting passive IoT is underway. 3GPP SA2 has carried out TR research, and it will be determined whether to do TS in Q4; 3GPP SA1 TR 22.840 SID has been completed, and the scenario and requirement research has been completed; 3GPP RAN R18 plenary session has released TR 38.848, and the RAN-related research has been completed. Domestically, CCSA TC10 WG2 has completed the project establishment of "Passive IoT Based on Cellular Communication - Part 1: Application Scenarios and Requirements" and "Passive IoT Services Based on Cellular Communication Technology - Part 2: General Technical Requirements", and studies the application scenarios and requirements of passive IoT.

[0003] The development of passive IoT technology has put forward new requirements for 5GC. The current network architecture, network element functions, interfaces, and protocols all need to be enhanced. On the one hand, passive IoT devices have the characteristics of low cost, low power, simple capabilities, and high density, and most devices have no batteries and do not have the ability to actively communicate with the network. Introducing passive IoT technology requires an innovation in the basic mechanisms of 5GC, involving basic capabilities such as mobility management and session management. On the other hand, the current core network does not support the identification and management of passive IoT devices, and new mechanisms such as network identity management need to be designed and tackled.

[0004] Therefore, how to provide support for passive IoT devices on the 5GC architecture to realize passive IoT services based on 5GC has become a key technical issue that technical personnel focus on. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a method and system for supporting passive IoT services, which can provide support for passive IoT devices on the 5GC architecture, so as to realize passive IoT services based on 5GC.

[0006] To achieve the above purpose, the present invention provides a method for supporting passive IoT services, including:

[0007] Step 1: The AIoTAF sends an inventory / collection request for passive tags to the AIoTMF;

[0008] Step 2: The AIoTMF receives the inventory / collection request, queries the local configuration to determine the passive tags corresponding to the inventory / collection request and the affiliated service AMF and service base station, and then forwards the inventory / collection request to the corresponding passive tags through the service AMF and the service base station;

[0009] Step 3: The passive tag receives the inventory / collection request, collects data, determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the service base station, and then sends the normal or abnormal collected data to the service base station on the subsequently established data bearer;

[0010] Step 4: The service base station extracts the tag information from all the returned normal RRC messages to form a normal tag list, aggregates the received normal collected data into a normal data stream, then returns the normal tag list and the service base station information to the AIoTMF through the service AMF. After requesting and establishing a PDU session, the normal data stream is sent to the AIoTAF through the UPF. At the same time, the tag information, abnormal collected data, and service base station information in each returned abnormal RRC message are sent to the AIoTMF via the service AMF;

[0011] Step 5: The AIoTMF updates the current status of the corresponding passive tag according to the response message returned by the service base station, and aggregates all the received abnormal collected data into an abnormal data stream and sends it to the AIoTAF.

[0012] To achieve the above object, the present invention also provides a system supporting passive Internet of Things services, including:

[0013] The AIoTAF sends an inventory / collection request for passive tags to the AIoTMF;

[0014] The AIoTMF receives the inventory / collection request sent by the AIoTAF, queries the local configuration to determine the passive tags corresponding to the inventory / collection request and the affiliated service AMF and service base station, then forwards the inventory / collection request to the corresponding passive tags through the service AMF and the service base station, and finally updates the current status of the passive tag according to the response message returned by the service base station, and aggregates all the received abnormal collected data into an abnormal data stream and sends it to the AIoTAF;

[0015] The passive tag receives the inventory / collection request, collects data, determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the service base station, and then sends the normal or abnormal collected data to the service base station on the subsequently established data bearer;

[0016] The serving base station receives normal or abnormal RRC messages returned by passive tags, extracts tag information from all normal RRC messages to form a normal tag list, aggregates the received normal collection data into a normal data stream, and then returns the normal tag list and serving base station information to the AIoTMF through the serving AMF. After requesting and establishing a PDU session, the normal data stream is sent to the AIoTAF through the UPF. Meanwhile, the tag information, abnormal collection data, and serving base station information in each abnormal RRC message are sent to the AIoTMF through the serving AMF.

[0017] To achieve the above object, the present invention also provides a computing device, including:

[0018] A memory and a processor;

[0019] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for supporting passive Internet of Things services are implemented.

[0020] To achieve the above object, the present invention also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, the steps of the method for supporting passive Internet of Things services are implemented.

[0021] Compared with the prior art, the beneficial effects of the present invention are as follows: By enhancing the current network architecture, network element functions, interfaces, and protocols of the 5GC, the present invention can provide support for passive IoT devices on the 5GC architecture, thereby realizing passive Internet of Things services based on the 5GC. In the case of large-scale signaling and data streams (i.e., when collecting data from all passive tags uniformly), the present invention merges the signaling and data streams fed back by each tag. Among them, the normal signaling is forwarded through the N1 control plane after merging, and the normal data is forwarded through the PDU session after merging, realizing a rapid reduction in the quantity of network signaling and data streams when the quantity surges, avoiding network congestion, and improving the forwarding efficiency. The abnormal signaling and abnormal data are forwarded through the N1 control plane after merging, realizing the rapid processing of abnormal tags. In the case of small-scale signaling and data streams (i.e., when collecting data from abnormal, power-limited, or missing passive tags), the present invention does not merge the signaling and data streams fed back by each tag, and directly forwards the signaling and data of each tag through the N1 control plane quickly, realizing the rapid processing of specific tags. The present invention also proposes various states of passive tags, as well as the conversion timing and conversion methods between each state, thereby realizing the full-life cycle management of passive tags. When the power of the passive tag is limited, the core network in the present invention will automatically back off for a certain period of time and then send a request message to the passive tag, thereby effectively saving power and signaling. Description of the Drawings

[0022] Figure 1 It is a flowchart of a method for supporting passive IoT services shown in an exemplary embodiment of the present invention.

[0023] Figure 2 It is a specific process flowchart of AIoTMF in an exemplary embodiment of the present invention for sending re-inventory / collection requests to each passive tag with an abnormal, power-limited, or missing current status locally.

[0024] Figure 3 It is a signaling interaction flowchart of AIoTAF sending an inventory / collection request for a passive tag to AIoTMF and the passive tag returning a normal RRC message shown in an exemplary embodiment of the present invention.

[0025] Figure 4 It is a signaling interaction flowchart of AIoTAF sending an inventory / collection request for a passive tag to AIoTMF and the passive tag returning an abnormal RRC message shown in an exemplary embodiment of the present invention.

[0026] Figure 5 It is a signaling interaction flowchart of AIoTAF sending an inventory / collection request for a passive tag to AIoTMF and not receiving a response message from the passive tag shown in an exemplary embodiment of the present invention.

[0027] Figure 6 It is a signaling interaction flowchart of a passive tag actively reporting an RRC message to a serving base station shown in an exemplary embodiment of the present invention.

[0028] Figure 7 It is a schematic structural diagram of a system for supporting passive IoT services shown in an exemplary embodiment of the present invention.

[0029] Figure 8 It is a schematic structural diagram of a computer device shown in an exemplary embodiment of the present invention. Detailed implementation manners

[0030] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings.

[0031] As Figure 1 shown, a method for supporting passive IoT services proposed by the present invention includes:

[0032] Step 1: AIoTAF (i.e., Ambient IoT Application Function, passive tag application function) sends an inventory / collection request for a passive tag to AIoTMF (i.e., Ambient IoT Management Function, passive tag management function);

[0033] Step 2: The AIoTMF receives the inventory / collection request, queries the local configuration, determines the passive tags corresponding to the inventory / collection request and the service AMF and service base station to which they belong, and then forwards the inventory / collection request to the corresponding passive tags through the service AMF and service base station;

[0034] Step 3: The passive tag receives the inventory / collection request, collects data, and determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the service base station, and then sends the normal or abnormal collected data to the service base station on the data bearer established later;

[0035] Step 4: The service base station extracts the tag information from all the returned normal RRC messages to form a normal tag list, aggregates the received normal collected data into a normal data stream, and then returns the normal tag list and service base station information to the AIoTMF through the service AMF. After requesting and establishing a PDU session, the normal data stream is sent to the AIoTAF through the UPF. At the same time, the tag information, abnormal collected data, and service base station information in each returned abnormal RRC message are sent to the AIoTMF through the service AMF;

[0036] Step 5: The AIoTMF updates the current status of the corresponding passive tags according to the response message returned by the service base station, and aggregates all the received abnormal collected data into an abnormal data stream and sends it to the AIoTAF.

[0037] In Step 1, the AIoTAF can directly or through the NEF send an inventory / collection request for all passive tags to the AIoTMF. The inventory / collection request is an HTTP message that contains the passive tag group ID.

[0038] In Step 2, the local configuration information of the AIoTMF comes from the passive tag ID, service base station information, power information, and service information reported by the OMC (i.e., Operations & Maintenance Center), and specifically includes the following content:

[0039] 1) Passive tag ID: including the passive tag's own ID, as well as the attached commodity ID or sensor ID.

[0040] 2) Service base station information: including (at the time of initial deployment / and after subsequent movement) the service base station ID (and the AMF ID to which the service base station belongs) serving the passive tag, as well as the relative position between the passive tag and the service base station (such as direction and angle), which is used to instruct the service base station to send an excitation signal to the power-constrained passive tag in a specific direction and angle when the passive tag is in a power-constrained state;

[0041] 3) Power information: including the power value at the deployment moment, the full power value, the functional relationship between the power value and the duration that can be sustained by sending and receiving inventory / collection requests according to a predetermined period, the functional relationship between the power value and the number of transmissions and receptions, the functional relationship between the power value and the protection interval for the next send command, the relationship between performing a certain action and the consumed power value, the energy types of energy harvesting (radio frequency, light, piezoelectric, vibration, electromagnetic, electrostatic, heat, wind, water, etc.), and other information that can assist the passive tag in maximizing power saving and charging during task execution and signal transmission and reception;

[0042] 4) Service information: including the service information subscribed by the passive tag, the capability information required to support the subscribed service, and the service-related status information such as switches or directions set at the deployment moment. For example, the passive tag on a commodity supports the inventory of the commodity when receiving an inventory command, the passive tag on a thermal sensor supports reading the temperature collected by the thermal sensor and sending a warning signal when the temperature exceeds the threshold, and the passive tag on a sprinkler supports opening the sprinkler switch and spraying in a specific direction after receiving a command. Storing the service information of the passive tag in the core network can, when receiving an abnormal signal from the passive tag, immediately send a command to the passive tag to perform a corresponding action according to the actual status and service capabilities of the passive tag, achieving the purpose of automatically controlling and eliminating abnormal situations in the first time.

[0043] Figure 1 Step 2 may further include:

[0044] Step 21: AIoTMF sends an inventory / collection request to the serving base station through the serving AMF and starts a data collection timer;

[0045] If multiple passive tags corresponding to the inventory / collection request involve multiple serving AMFs, AIoTMF sends an HTTP message to each relevant serving AMF. This message contains one or more relevant serving base stations and multiple passive tag IDs covered by each serving base station; the serving AMF sends an inventory / collection request to the serving base station according to the indication of AIoTMF. If multiple serving base stations are involved, an NGAP message is sent to each relevant serving base station. This message contains the passive tag IDs covered by the serving base station;

[0046] Step 22: The serving base station forwards the inventory / collection request to the corresponding passive tag and starts a data collection timer. The inventory / collection request forwarded by the serving base station to the passive tag is an RRC message.

[0047] Figure 1 Step 3 may further include:

[0048] The passive tag determines whether the collected data is within the normal range. If so, it returns a normal RRC message to the serving base station, sets DataStateFlag = 0, and sends the collected normal data to the serving base station on the subsequently established data bearer. If not, the collected data is abnormal data, and it returns an abnormal RRC message to the serving base station, sets DataStageFlag = 1, and sends the collected abnormal data to the serving base station on the subsequently established data bearer. At the same time, the passive tag also writes the tag information (i.e., the necessary information required for the core network to manage the passive tag) into the NAS layer of the RRC message. The tag information includes the tag ID, remaining power, etc. DataStateFlag is used to identify whether the RRC message is a normal or abnormal message.

[0049] Figure 1 Step 4 may further include:

[0050] Step 41: The serving base station receives the RRC message and the collected data returned by each passive tag, calculates the relative position between the passive tag and the serving base station, and determines whether the RRC message is a normal RRC message. If so, it writes the tag information and the relative position extracted from the normal RRC message into the normal tag list. If not, it returns an abnormal response message to the serving AMF. The abnormal response message is an NGAP message encapsulating the tag information, the collected data, the relative position, and the serving base station information extracted from the abnormal RRC message. At the same time, it monitors whether the data collection timer times out. After the data collection timer times out, it returns a normal response message and a PDU session establishment request to the serving AMF. The normal response message is an NGAP message encapsulating the normal tag list and the serving base station information.

[0051] Step 42: The serving AMF determines whether the response message returned by the serving base station is a normal response message. If so, it reads the normal tag list and the serving base station information from the normal response message, encapsulates them into an HTTP message and sends it to the AIoTMF, and then forwards the PDU session establishment request to the SMF to establish a session transmission tunnel between the serving base station and the UPF under the management of the SMF. Subsequently, the serving base station aggregates the collected data of all passive tags in the normal tag list into a normal data stream and transmits it to the AIoTAF through the established PDU session. If not, it reads the tag information, the collected data, and the serving base station information from the abnormal response message, and encapsulates them into an HTTP message and sends it to the AIoTMF.

[0052] Figure 1 In step 5, each passive tag maintained in the AIoTMF can have four states:

[0053] Normal state: The power is sufficient to support message sending and receiving, and the collected data is within the normal range.

[0054] Abnormal state: The power is sufficient to support message sending and receiving, and the collected data is out of the normal range;

[0055] Power-limited state: Due to power limitation, it takes a certain time to collect energy from the surrounding environment, and message sending and receiving are temporarily unavailable;

[0056] Missing state: After its serving base station sends an inventory / collection request, no response from this passive tag is received within a sufficiently long predetermined time.

[0057] In the normal state, if the collected data of the passive tag is abnormal, it enters the abnormal state; if it does not respond within the predetermined time, it enters the power-limited state; in the abnormal state, if the collected data is normal, it enters the normal state; if it does not respond within the predetermined time, it enters the power-limited state; in the power-limited state, if it still does not respond to the core network within the increased predetermined time, it enters the missing state; if the collected data is normal, it enters the normal state; if the collected data is abnormal, it enters the abnormal state; in the missing state, if the collected data is normal, it enters the normal state; if the collected data is abnormal, it enters the abnormal state.

[0058] Figure 1 Step 5 may further include:

[0059] AIoTMF determines whether the received response message is a normal response message. If so, it extracts the normal tag list from the normal response message, then updates the current local status of all passive tags in the normal tag list to the normal state, and records information such as the power and corresponding time of all passive tags, the serving base station ID of the passive tag, and the relative position between the passive tag and the serving base station. If not, it indicates that it is an abnormal response message. It extracts the tag information from the abnormal response message, then updates the current local status of the corresponding passive tag to the abnormal state, determines the corresponding actions that the abnormal passive tag needs to perform, and then sends a command indicating the abnormal passive tag to execute the actions to the serving AMF, records information such as the power and corresponding time of the passive tag, the serving base station ID of the passive tag, and the relative position between the passive tag and the serving base station. At the same time, it monitors whether the data collection timer times out. After the data collection timer times out, it aggregates all the received abnormal collected data into an abnormal data stream and forwards it to AIoTAF, and based on the local configuration and the received response message, updates the current local status of the passive tags that have not returned a response message to the power-limited state, and replies to AIoTAF with a list of power-limited passive tags, indicating the serving base station to send an excitation signal to the power-limited passive tags, or indicating the power-limited passive tags to modify the orientation of collecting power.

[0060] The AIoTMF updates the current local status of the corresponding passive tag to an abnormal status, determines the corresponding actions that the abnormal passive tag needs to perform, and then sends a command instructing the abnormal passive tag to perform the actions to the serving AMF. This may further include:

[0061] The AIoTMF determines the command for the passive tag to perform actions based on the collected data of the passive tag, as well as the service information and power information of the passive tag stored locally, and calculates the charging waiting time for the passive tag. The charging waiting time is used for the passive tag to charge to a sufficient power level to support message transmission and reception, and then waits until the charging waiting time of the passive tag expires. After that, it instructs the passive tag to perform the action command through the serving AMF. For example, if the smoke value collected by the smoke detector exceeds the threshold, by querying the local configuration, it is determined that the passive tag needs to be instructed to turn on the spraying switch. Also, based on the power information, it is determined that the current power value of the passive tag cannot support receiving commands and performing actions, calculates the waiting time, and finally, at an appropriate moment, instructs the passive tag to perform the command to turn on the spraying switch through the AMF.

[0062] Considering that the power conditions, actions to be performed, etc. of each abnormal, power - limited, or missing passive tag may be different, the AIoTMF also calculates a certain waiting time for each abnormal, power - limited, or missing passive tag, and after the waiting time expires, continues to send a re - inventory / collection request to the corresponding passive tag. In this way, each abnormal, power - limited, or missing passive tag will occupy a signaling channel alone. Since the number of these passive tags is usually small, it will not cause a sharp increase in the signaling load on the network. As Figure 2 shown, the AIoTMF sending a re - inventory / collection request to each passive tag with an abnormal, power - limited, or missing current local status may further include:

[0063] Step A1: The AIoTMF calculates the re - inventory waiting time for each passive tag with an abnormal, power - limited, or missing current local status, then waits until the re - inventory waiting time expires, and through the serving AMF and the serving base station, sends a re - inventory / collection request to the corresponding abnormal, power - limited, or missing passive tag, and starts a re - collection data timer;

[0064] Since the power conditions of each passive tag may be different, it is necessary to estimate the sending time of the corresponding re - inventory / collection request, that is, the re - inventory waiting time, based on the power model of each passive tag to ensure that the passive tag has sufficient power to receive the request and respond;

[0065] Step A2: After receiving the re-inventory / collection request, the passive tag collects data, determines whether the collected data is within the normal range, returns a normal or abnormal RRC message to the serving base station, and then sends the collected data to the serving base station on the data bearer established later;

[0066] Step A3: The serving base station receives the RRC message and the collected data returned by the passive tag in response to the re-inventory / collection request, calculates the relative position between the passive tag and the serving base station, and then encapsulates the tag information, the collected data, the relative position between the passive tag and the serving base station, and the serving base station information returned by the passive tag into an NGAP message and sends it to the serving AMF;

[0067] Step A4: The serving AMF encapsulates the tag information, the collected data, the relative position between the passive tag and the serving base station, and the serving base station information read from the received NGAP message into an HTTP message and sends it to the AIoTMF;

[0068] Step A5: The AIoTMF receives the HTTP message sent by the serving AMF, determines whether the collected data of the passive tag is within the normal range, and updates the current status of the corresponding passive tag locally accordingly. Then, the AIoTMF sends the received collected data to the AIoTAF. Herein, updating the current status of the passive tag locally includes: when a response message of the passive tag is received within the time of the re-collection data timer, if the response message is a normal response message, the current status of the passive tag is updated to the normal status locally; if the response message is an abnormal response message, the current status of the passive tag is updated to the abnormal status locally, and the corresponding actions that the abnormal passive tag needs to perform are determined, and a command indicating the abnormal passive tag to perform the actions is sent to the serving AMF; when no response message of the passive tag is received after the re-collection data timer times out, if the current status of the passive tag is the abnormal status locally, its current status is updated to the power-limited status, the local configuration is queried, and it is indicated that the serving base station to which the passive tag belongs sends an excitation signal to it, or it is indicated that the passive tag modifies the orientation for collecting power, and a power-limited passive tag is replied to the AIoTAF; if the current status of the passive tag is the power-limited status locally, its current status is updated to the missing status, and a re-inventory / collection request for the passive tag is continuously sent to one or more serving base stations centered on the serving base station stored in the local configuration, and a missing passive tag is replied to the AIoTAF.

[0069] It should be emphasized that in the present invention, the AIoTMF can also use the power information of the passive tag stored locally to calculate the above-mentioned charging waiting time and re-inventory waiting time, so as to reasonably schedule the timing of sending signaling to the passive tag. That is to say, if it is estimated according to the power model that the current power of the passive tag cannot ensure successful information transmission and reception, a suitable time is retreated, and then a request message is sent to the passive tag.

[0070] Specifically, if an inventory / collection request is sent to a passive tag but no response message from the passive tag is received after the collection data timer times out, the AIoTMF considers "the current time, the function relationship between the latest power value and the corresponding time, the function relationship between the power value and the duration that the inventory / collection signal can be sent and received according to a predetermined period, the function relationship between the power value and the number of transmissions and receptions, the function relationship between the power value and the protection interval for the next instruction to be sent, and the relationship between performing a certain action and the consumed power value", estimates the time required for the passive tag to collect the power (required to ensure message transmission and reception) according to the power model, automatically backs off the calculated re-inventory waiting time length, and then sends a re-inventory / collection request to the passive tag, thereby achieving the technical effects of power saving, signaling saving, communication guarantee, and timely detection of anomalies.

[0071] Specifically, if a re-inventory / collection request for a passive tag in a power-constrained state is received from the AIoTAF, the AIoTMF considers "the current time, the function relationship between the latest power value and the corresponding time, the function relationship between the power value and the duration that the inventory / collection signal can be sent and received according to a predetermined period, the function relationship between the power value and the number of transmissions and receptions, the function relationship between the power value and the protection interval for the next instruction to be sent, and the relationship between performing a certain action and the consumed power value", estimates the time required for the passive tag to collect the power (required to ensure message transmission and reception) according to the power model, automatically backs off the calculated re-inventory waiting time length, and then sends a re-inventory / collection request to the passive tag, thereby achieving the technical effects of power saving, signaling saving, communication guarantee, and timely detection of anomalies.

[0072] The AIoTMF can also send an action execution command to a passive tag in a power-constrained state according to surrounding environmental factors such as real-time sunlight, wind direction, water flow, and base station direction, instruct the serving base station of the passive tag to send an excitation signal to it, or instruct the passive tag to modify the orientation for collecting power, so as to facilitate power collection, and achieve the auxiliary charging of the passive tag from both the network and the passive tag aspects.

[0073] When the AIoTMF estimates according to the power model that the passive tag already has sufficient power at a certain moment but still does not receive a response message from the passive tag, it is determined that the passive tag is in a missing state to ensure the accuracy of the missing warning.

[0074] When the passive tag does not receive an inventory / collection request for a certain period of time or the collected data of the passive tag exceeds the normal range, the passive tag can also actively report a normal RRC message or an abnormal RRC message to the serving base station, and further includes:

[0075] Step B1: The passive tag reports normal or abnormal RRC messages to the serving base station, and sends the collected data to the serving base station on the data bearer established later.

[0076] Step B2: The serving base station calculates the relative position between the passive tag and the serving base station, encapsulates the tag information, collected data, relative position between the passive tag and the serving base station, and serving base station information extracted from the RRC message reported by the passive tag into an NGAP message, and sends it to the serving AMF.

[0077] Step B3: The serving AMF encapsulates the tag information, collected data, relative position between the passive tag and the serving base station, and serving base station information read from the NGAP message into an HTTP message, and sends it to the AIoTMF.

[0078] Step B4: The AIoTMF updates the current status of the passive tag locally according to the reported message of the passive tag, and sends the received collected data to the AIoTAF. Among them, updating the current status of the passive tag further includes: if the reported message is a normal response message, set the current status of the passive tag locally to the normal status; if the reported message is an abnormal response message, set the current status of the passive tag locally to the abnormal status, determine the corresponding actions that the abnormal passive tag needs to perform, and send a command indicating the actions of the abnormal passive tag to the serving AMF.

[0079] To more clearly explain the implementation process of the present invention, Figure 3 An embodiment of a signaling interaction flowchart is shown when the AIoTAF sends an inventory / collection request for a passive tag to the AIoTMF and the passive tag returns a normal RRC message. Figure 4 An embodiment of a signaling interaction flowchart is shown when the AIoTAF sends an inventory / collection request for a passive tag to the AIoTMF and the passive tag returns an abnormal RRC message. Figure 5 An embodiment of a signaling interaction flowchart is shown when the AIoTMF sends an inventory / collection request for a passive tag but does not receive a response message returned by the passive tag. Figure 6 An embodiment of a signaling interaction flowchart is shown when a passive tag actively reports an RRC message to the serving base station.

[0080] As Figure 3 shown, when the AIoTAF sends an inventory / collection request for a passive tag to the AIoTMF and the passive tag returns a normal RRC message, the signaling interaction process is as follows:

[0081] Step a1: The AIoTAF sends an inventory / collection request for all passive tags to the AIoTMF.

[0082] Step a2: The AIoTMF receives an inventory / collection request, determines the serving AMF and serving base station of the passive tag according to the passive tag, and forwards the above inventory / collection request to the serving AMF;

[0083] Step a3: The serving AMF sends an inventory / collection request to the corresponding serving base station according to the indication of the AIoTMF;

[0084] Step a4: The serving base station sends an inventory / collection request to the corresponding target passive tag according to the indication of the serving AMF, and starts a data collection timer;

[0085] Steps a5-6: After receiving the inventory / collection request, when the passive tag determines that the collected data is within the normal range, it feeds back a normal RRC message to the serving base station, and sends the collected normal data to the serving base station on the subsequently established data bearer;

[0086] Steps a7-19: After the data collection timer times out, the serving base station encapsulates the normal tag list and base station information into an NGAP message and sends it to the serving AMF. The serving AMF reads the normal tag list and the base station ID from the NGAP message, encapsulates them into an HTTP message, sends it to the AIoTMF, and sends a PDU session establishment request to the SMF. Under the management of the SMF, a session transmission tunnel is established with the UPF, and the normal collected data stream is transmitted to the AIoTAF via the UPF;

[0087] Step a20: The AIoTMF sets the status of the passive tags in the normal tag list to normal.

[0088] As Figure 4 shown, when the AIoTAF sends an inventory / collection request for passive tags to the AIoTMF and the passive tag returns an abnormal RRC message, the signaling interaction process is as follows:

[0089] Step b1: The AIoTAF sends an inventory / collection request for all passive tags to the AIoTMF;

[0090] Steps b2-4: The AIoTMF receives the inventory / collection request, and then sends the inventory / collection request to the corresponding target passive tag through the serving AMF and the serving base station;

[0091] Steps b5-6: After receiving the inventory / collection request, when the passive tag determines that the collected data is within the abnormal range, it feeds back an abnormal RRC message to the serving base station, and sends the collected abnormal data to the serving base station on the subsequently established data bearer;

[0092] Step b7: The serving base station returns an abnormal response message to the serving AMF;

[0093] Step b8: The serving AMF sends an exception response message to the AIoTMF;

[0094] Steps b9 - 12: The AIoTMF sets the status of the corresponding passive tag to abnormal, determines the actions that the abnormal passive tag needs to perform, and sends a command indicating the actions to be performed to the passive tag through the serving AMF and the serving base station;

[0095] Steps b13 - 14: After the data collection timer times out, the AIoTMF aggregates all the received abnormal collection data into an abnormal data stream and forwards it to the AIoTAF;

[0096] Steps b15 - 18: The AIoTMF calculates the re - inventory waiting time for the abnormal passive tag. After waiting until the re - inventory waiting time times out, it sends a re - inventory / collection request to the abnormal passive tag through the serving AMF and the serving base station;

[0097] Steps b19 - 20: After receiving the re - inventory / collection request, the abnormal passive tag collects data, returns an RRC message to the serving base station, and then sends the collected data to the serving base station on the data bearer established later;

[0098] Step b21: The serving base station sends a re - inventory / collection response message to the serving AMF without distinguishing between a normal RRC message and an abnormal RRC message;

[0099] Step b22: The serving AMF sends a re - inventory / collection response message to the AIoTMF;

[0100] Steps b23 - 27: When the AIoTMF determines that the collection data of the passive tag is abnormal, it updates the status of the corresponding passive tag to abnormal, then returns the received collection data to the AIoTAF, determines the actions that the abnormal passive tag needs to perform, and continues to send a command indicating the actions to be performed to the passive tag through the serving AMF and the serving base station.

[0101] As Figure 5 shown, the signaling interaction process when the AIoTMF sends a re - inventory / collection request for a passive tag but does not receive a response message returned by the passive tag is as follows:

[0102] Steps c1 - 6: The AIoTMF sends a re - inventory / collection request for a passive tag. After the data collection timer times out, it updates the status of the tags that have not returned a re - inventory / collection response message to power - constrained, then returns the power - constrained passive tags to the AIoTAF, and instructs a specific base station to send an excitation signal in a specific direction;

[0103] Steps c7 - 10: The AIoTMF estimates the time required for the power - limited passive tag to collect sufficient energy (i.e., the re - inventory waiting time) according to the power model. After waiting until the re - inventory waiting time times out, it sends a re - inventory / collection request to the power - limited passive tag through the serving AMF and the serving base station;

[0104] Steps c11 - 15: After the AIoTMF waits until the re - collection data timer times out, it updates the status of the power - limited tags that have not returned the re - inventory / collection response message to missing. Then it continues to send re - inventory / collection requests for the missing passive tags to one or more serving base stations centered on the serving base station stored in the local configuration, and replies to the AIoTAF with the missing passive tags.

[0105] As Figure 6 shown, the signaling interaction process when the passive tag actively reports the RRC message to the serving base station is as follows:

[0106] Steps d1 - 2: The passive tag actively sends an RRC message to the serving base station and transmits the collected data to the serving base station;

[0107] Steps d3 - 4: The serving base station sends the tag information, the collected data, and the base station information actively reported by the passive tag to the AIoTMF through the serving AMF;

[0108] Steps d5 - 9: When the AIoTMF determines that the reported message is an abnormal response message, it sets the status of the passive tag to abnormal. Then it determines the corresponding actions that the abnormal passive tag needs to perform, sends a command indicating the actions of the abnormal passive tag to the serving AMF, and returns the abnormal collected data to the AIoTAF.

[0109] As Figure 7 shown, a system for supporting passive Internet of Things services proposed by the present invention includes:

[0110] The AIoTAF sends an inventory / collection request for the passive tag to the AIoTMF;

[0111] The AIoTMF receives the inventory / collection request sent by the AIoTAF, queries the local configuration, determines the passive tag corresponding to the inventory / collection request and the affiliated serving AMF and serving base station, then forwards the inventory / collection request to the corresponding passive tag through the serving AMF and the serving base station. Finally, according to the response message returned by the serving base station, it updates the current status of the passive tag and aggregates all the abnormal collected data into an abnormal data stream and sends it to the AIoTAF;

[0112] The passive tag receives an inventory / collection request, collects data, determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the serving base station, and then sends the normal or abnormal collected data to the serving base station on the data bearer established later.

[0113] The serving base station receives the normal or abnormal RRC message returned by the passive tag, extracts the tag information from all normal RRC messages to form a normal tag list, aggregates the received normal collected data into a normal data stream, and then returns the normal tag list and serving base station information to the AIoTMF through the serving AMF. After requesting and establishing a PDU session, the normal data stream is sent to the AIoTAF through the UPF. At the same time, the tag information, abnormal collected data, and serving base station information in each abnormal RRC message are sent to the AIoTMF via the serving AMF.

[0114] See Figure 8 , Figure 8 FIG. is a block diagram of a computing device 800 shown in an exemplary embodiment of the present specification. The components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 through a bus 830, and a database 850 is used to store data.

[0115] The computing device 800 further includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interfaces (e.g., a Network Interface Card (NIC)), such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0116] In one embodiment of this specification, the above components of the computing device 800, as well as Figure 8 other components not shown in Figure 8 can also be connected to each other, for example, via a bus. It should be understood that

[0117] the block diagram of the computing device shown is for illustrative purposes only and is not a limitation on the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0118] The processor 820 is used to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the method for supporting passive Internet of Things services described above.

[0119] The above is a schematic solution of a computing device in this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the method for supporting passive Internet of Things services described above belong to the same concept. For the details not described in the technical solution of the computing device, reference can be made to the description of the technical solution of the method for supporting passive Internet of Things services.

[0120] This specification also provides a computer-readable storage medium in one embodiment, which stores computer-executable instructions that, when executed by a processor, implement the steps of the method for supporting passive Internet of Things services described above.

[0121] The above is a schematic solution of a computer-readable storage medium in this embodiment. It should be noted that the technical solution of this storage medium and the method for supporting passive Internet of Things services described above belong to the same concept. For the details not described in the technical solution of the storage medium, reference can be made to the description of the technical solution of the method or system for supporting passive Internet of Things services.

[0122] This specification also provides a computer program in one embodiment, wherein when the computer program is executed on a computer, the computer is made to execute the steps of the method for supporting passive Internet of Things services described above.

[0123] The above is a schematic solution of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the above method for supporting passive Internet of Things services belong to the same concept. For the details not described in detail in the technical solution of the computer program, reference can be made to the description of the technical solution of the above method or system for supporting passive Internet of Things services.

[0124] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0125] The computer instructions include computer program code, which may be in the form of source code, object code, executable files, or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, external hard drives, magnetic disks, optical discs, computer memories, read-only memories (ROMs), random access memories (RAMs), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0126] It should be noted that for the foregoing method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of this specification are not limited by the described order of actions, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments of this specification.

[0127] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A method for supporting passive Internet of Things services, characterized in that, It includes: Step 1: AIoTAF sends an inventory / collection request for passive tags to AIoTMF; Step 2: AIoTMF receives the inventory / collection request, queries the local configuration, determines the passive tags corresponding to the inventory / collection request and the affiliated service AMF and service base station, and then forwards the inventory / collection request to the corresponding passive tags through the service AMF and service base station; Step 3: The passive tag receives the inventory / collection request, collects data, determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the service base station, and then sends the normal or abnormal collected data to the service base station on the data bearer established later; Step 4: The service base station extracts the tag information from all the returned normal RRC messages to form a normal tag list, aggregates the received normal collected data into a normal data stream, then returns the normal tag list and service base station information to AIoTMF through the service AMF, and sends the normal data stream to AIoTAF through the UPF after requesting and establishing a PDU session. At the same time, the tag information, abnormal collected data, and service base station information in each returned abnormal RRC message are sent to AIoTMF through the service AMF; Step 5: AIoTMF updates the current status of the corresponding passive tags according to the response message returned by the service base station, and aggregates all the received abnormal collected data into an abnormal data stream and sends it to AIoTAF.

2. The method according to claim 1, wherein Step 3 includes: The passive tag determines whether the collected data is within the normal range. If so, it returns a normal RRC message to the service base station, where DataStateFlag = 0 is set, and sends the collected normal data to the service base station on the data bearer established later; if not, the collected data is abnormal data, and it returns an abnormal RRC message to the service base station, where DataStageFlag = 1 is set, and sends the collected abnormal data to the service base station on the data bearer established later. At the same time, the passive tag also writes the tag information into the NAS layer of the RRC message. The tag information includes the tag ID and remaining battery power. DataStateFlag is used to identify whether the RRC message is a normal or abnormal message.

3. The method according to claim 1, wherein Step 4 includes: Step 41: The service base station receives each RRC message and collected data returned by the passive tag, calculates the relative position between the passive tag and the service base station, and determines whether the RRC message is a normal RRC message. If so, it writes the tag information and relative position extracted from the normal RRC message into the normal tag list. If not, it returns an abnormal response message to the service AMF. The abnormal response message is an NGAP message encapsulating the tag information, collected data, relative position, and service base station information extracted from the abnormal RRC message. At the same time, it monitors whether the data collection timer times out. After the data collection timer times out, it returns a normal response message and a PDU session establishment request to the service AMF. The normal response message is an NGAP message encapsulating the normal tag list and service base station information; Step 42: The serving AMF determines whether the response message returned by the serving base station is a normal response message. If so, it reads the normal tag list and serving base station information from the normal response message, encapsulates them into an HTTP message and sends it to the AIoTMF, and then forwards the PDU session establishment request to the SMF to establish a session transmission tunnel between the serving base station and the UPF under the management of the SMF. Subsequently, the serving base station aggregates the acquisition data of all passive tags in the normal tag list into a normal data stream through the established PDU session and transmits it to the AIoTAF. If not, it reads the tag information, acquisition data, and serving base station information from the abnormal response message, encapsulates them into an HTTP message and sends it to the AIoTMF.

4. The method according to claim 1, wherein In step five, each passive tag maintained by the AIoTMF has four states: normal state, abnormal state, power-limited state, and missing state.

5. The method according to claim 4, wherein Step five further includes: The AIoTMF determines whether the received response message is a normal response message. If so, it extracts the normal tag list from the normal response message, then updates the current status of all passive tags in the normal tag list locally to the normal state, and records the power and corresponding time of all passive tags, the serving base station ID of the passive tags, and the relative position between the passive tags and the serving base station. If not, it indicates that it is an abnormal response message. It extracts the tag information from the abnormal response message, then updates the current status of the corresponding passive tags locally to the abnormal state, determines the corresponding actions that the abnormal passive tags need to perform, and then sends a command indicating the actions of the abnormal passive tags to the serving AMF, records the power and corresponding time of the passive tags, the serving base station ID of the passive tags, and the relative position between the passive tags and the serving base station. At the same time, it monitors whether the data collection timer times out. After the data collection timer times out, it aggregates all the received abnormal acquisition data into an abnormal data stream and forwards it to the AIoTAF, and based on the local configuration and the received response message, updates the current status of the passive tags that have not returned a response message locally to the power-limited state, and replies to the AIoTAF with a list of power-limited passive tags, indicating that the serving base station sends an excitation signal to the power-limited passive tags, or indicating that the power-limited passive tags modify the orientation of collecting power.

6. The method according to claim 5, wherein The AIoTMF updates the current status of the corresponding passive tags locally to the abnormal state, determines the corresponding actions that the abnormal passive tags need to perform, and then sends a command indicating the actions of the abnormal passive tags to the serving AMF, which further includes: The AIoTMF determines the command to be sent to the passive tags to perform actions according to the acquisition data of the passive tags, as well as the service information and power information of the passive tags stored locally, and calculates the charging waiting time of the passive tags. The charging waiting time is used for the passive tags to charge until the power is sufficient to support message sending and receiving. Then, after waiting until the charging waiting time of the passive tags times out, it indicates the command to perform actions to the passive tags through the serving AMF.

7. The method according to claim 1, wherein The AIoTMF issues re-inventory / collection requests to each passive tag that is locally in an abnormal, power-limited, or missing state, including: Step A1: The AIoTMF calculates the re-inventory waiting time for each passive tag that is locally in an abnormal, power-limited, or missing state, then waits until the re-inventory waiting time times out, and through the service AMF and the serving base station, issues a re-inventory / collection request to the corresponding abnormal, power-limited, or missing passive tag, and starts the re-collection data timer; Step A2: After receiving the re-inventory / collection request, the passive tag collects data, determines whether the collected data is within the normal range, returns a normal or abnormal RRC message to the serving base station, and then sends the collected data to the serving base station on the data bearer established later; Step A3: The serving base station receives the RRC message and the collected data returned by the passive tag for the re-inventory / collection request, calculates the relative position between the passive tag and the serving base station, and then encapsulates the tag information, the collected data, the relative position between the passive tag and the serving base station, and the serving base station information returned by the passive tag into an NGAP message and sends it to the serving AMF; Step A4: The serving AMF encapsulates the tag information, the collected data, the relative position between the passive tag and the serving base station, and the serving base station information read from the received NGAP message into an HTTP message and sends it to the AIoTMF; Step A5: The AIoTMF receives the HTTP message sent by the serving AMF, determines whether the collected data of the passive tag is within the normal range, and accordingly updates the current local state of the corresponding passive tag, and then sends the received collected data to the AIoTAF. Among them, updating the current local state of the passive tag includes: when a response message of the passive tag is received within the time of the re-collection data timer, if the response message is a normal response message, then update the current local state of the passive tag to the normal state, if the response message is an abnormal response message, then update the current local state of the passive tag to the abnormal state, and determine the corresponding actions that the abnormal passive tag needs to perform, and send a command indicating the actions of the abnormal passive tag to the serving AMF; when no response message of the passive tag is received after the re-collection data timer times out, if the current local state of the passive tag is the abnormal state, then update its current state to the power-limited state, query the local configuration, instruct the serving base station to which the passive tag belongs to send an excitation signal to it, or instruct the passive tag to modify the orientation of collecting power, and reply to the AIoTAF with the power-limited passive tag. If the current local state of the passive tag is the power-limited state, then update its current state to the missing state, continue to issue re-inventory / collection requests for the passive tag to one or more serving base stations centered on the serving base station stored in the local configuration, and reply to the AIoTAF with the missing passive tag.

8. The method according to claim 1, characterized in that, The passive tag actively reports a normal RRC message or an abnormal RRC message to the serving base station, including: Step B1: The passive tag reports normal or abnormal RRC messages to the serving base station, and then sends the collected data to the serving base station on the established data bearer. Step B2: The serving base station calculates the relative position between the passive tag and the serving base station, encapsulates the tag information, collected data, relative position between the passive tag and the serving base station, and serving base station information extracted from the RRC messages reported by the passive tag into an NGAP message, and sends it to the serving AMF. Step B3: The serving AMF encapsulates the tag information, collected data, relative position between the passive tag and the serving base station, and serving base station information read from the NGAP message into an HTTP message and sends it to the AIoTMF. Step B4: The AIoTMF updates the current status of the passive tag locally according to the reported message of the passive tag, and sends the received collected data to the AIoTAF. Among them, updating the current status of the passive tag further includes: if the reported message is a normal response message, setting the current status of the passive tag locally to the normal state; if the reported message is an abnormal response message, setting the current status of the passive tag locally to the abnormal state, determining the corresponding actions that the abnormal passive tag needs to perform, and sending a command indicating the actions of the abnormal passive tag to the serving AMF.

9. A system for supporting passive Internet of Things services, characterized in that, It includes: The AIoTAF sends an inventory / collection request for the passive tag to the AIoTMF. The AIoTMF receives the inventory / collection request sent by the AIoTAF, queries the local configuration, determines the passive tag corresponding to the inventory / collection request and the affiliated serving AMF and serving base station, then forwards the inventory / collection request to the corresponding passive tag through the serving AMF and serving base station, and finally updates the current status of the passive tag according to the response message returned by the serving base station, and aggregates all the received abnormal collected data into an abnormal data stream and sends it to the AIoTAF. The passive tag receives the inventory / collection request, collects data, determines whether the collected data is within the normal range, then returns a normal or abnormal RRC message to the serving base station, and then sends normal or abnormal collected data to the serving base station on the established data bearer. The serving base station receives the normal or abnormal RRC messages returned by the passive tag, extracts the tag information from all normal RRC messages to form a normal tag list, aggregates the received normal collected data into a normal data stream, then returns the normal tag list and serving base station information to the AIoTMF through the serving AMF, sends the normal data stream to the AIoTAF through the UPF after requesting and establishing a PDU session, and at the same time, sends the tag information, abnormal collected data, and serving base station information in each abnormal RRC message to the AIoTMF through the serving AMF.

10. A computing device, characterized in that, It includes: A memory and a processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the method for supporting passive Internet of Things services described in any one of claims 1-8 are implemented.

11. A computer-readable storage medium, characterized in that, It stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the method for supporting passive Internet of Things services described in any one of claims 1-8 are implemented.

Images