Ambient internet of things (AIOT) device information transmission methods, network device and reading device

Abstract

The present disclosure relates to ambient Internet of things (AIoT) device information transmission methods, a network device and a reading device. In at least one embodiment of the present disclosure, a method comprises: a network device sending an AIoT service request to at least one first network element capable of acquiring AIoT device information, such as a reading device, a 3GPP core network device and / or a third-party device, so as to obtain AIoT device information and / or AIoT service status indications which are sent by different first network elements; then performing statistical processing on the AIoT device information to obtain an AIoT device analysis result; and sending the AIoT device analysis result to an AIoT application device, so as to meet service requirements of the AIoT application device in different application scenarios.

Description

Passive Internet of Things (AIoT) device information transmission methods, network devices and reading devices

[0001] Cross-references to related applications

[0002] This disclosure claims priority to Chinese Patent Application No. 202510071901.8, filed on January 16, 2025, entitled “Passive Internet of Things (AIoT) Device Information Transmission Method, Network Device and Reading Device”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, specifically to a passive Internet of Things (AIoT) device information transmission method, network device, and reading device. Background Technology

[0004] Passive Internet of Things (AIoT) utilizes environmental energy harvesting technology to convert available signals and energy from the surrounding environment into electrical energy that can drive terminal circuits. It also employs a communication mode based on backscattering to transmit information to target nodes. AIoT devices do not rely on traditional battery power, such as Radio Frequency Identification (RFID) devices, thus reducing the size and cost of user equipment (UE).

[0005] Because AIoT devices have no or limited energy, they can only obtain energy from the external environment. The amount of data transmitted is very small (e.g., only reporting tag information) and the frequency is very low (e.g., perhaps only a single data transmission). Therefore, AIoT devices cannot directly interact with the communication network, nor do they obtain data from third parties. How the communication network can support the business needs of AIoT devices in different application scenarios (e.g., inventory, positioning, and reporting sensing data) is a problem that urgently needs to be solved. Summary of the Invention

[0006] At least one embodiment of this disclosure provides a passive Internet of Things (AIoT) device information transmission method, network device, and reading device, supporting the business needs of different application scenarios of AIoT devices.

[0007] In a first aspect, embodiments of this disclosure propose a passive Internet of Things (AIoT) device information transmission method, applied to network devices, the method comprising:

[0008] Send an AIoT service request to at least one first network element capable of obtaining AIoT device information;

[0009] Receive a first AIoT service response corresponding to an AIoT service request sent by at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication;

[0010] Based on the first AIoT service response, a second AIoT service response is sent to the AIoT application device; wherein, the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

[0011] Secondly, this disclosure also proposes a passive Internet of Things (AIoT) device information transmission method, applied to a reading device, the method comprising:

[0012] Send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0013] Receive response information sent by network devices.

[0014] Thirdly, this disclosure also discloses a passive Internet of Things (AIoT) device information transmission apparatus, applied to network equipment, the apparatus comprising:

[0015] The first sending unit is used to send an AIoT service request to at least one first network element that is capable of obtaining AIoT device information;

[0016] The receiving unit is configured to receive a first AIoT service response corresponding to an AIoT service request sent by at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information and AIoT service status indication;

[0017] The second sending unit is used to send a second AIoT service response to the AIoT application device based on the first AIoT service response; wherein the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

[0018] Fourthly, this disclosure also discloses a passive Internet of Things (AIoT) device information transmission apparatus for use in a reading device, the apparatus comprising:

[0019] The sending unit is used to send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0020] The receiving unit is used to receive response information sent by network devices.

[0021] Fifthly, this disclosure also discloses a network device, wherein the network device includes a memory, a transceiver, and a processor;

[0022] Memory is used to store computer programs; transceiver is used to send and receive data under the control of the processor; processor is used to read the computer program from memory and execute it.

[0023] Send an AIoT service request to at least one first network element capable of obtaining AIoT device information;

[0024] Receive a first AIoT service response corresponding to an AIoT service request sent by at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication;

[0025] Based on the first AIoT service response, a second AIoT service response is sent to the AIoT application device; wherein, the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

[0026] Sixthly, embodiments of this disclosure also provide a reading device, wherein the reading device includes a memory, a transceiver, and a processor;

[0027] Memory is used to store computer programs; transceiver is used to send and receive data under the control of the processor; processor is used to read the computer program from memory and execute it.

[0028] Send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0029] Receive response information sent by network devices.

[0030] In a seventh aspect, embodiments of this disclosure also provide a processor-readable storage medium, wherein the processor-readable storage medium stores a program for causing the processor to execute the passive Internet of Things (AIoT) device information transmission method of any embodiment of the first aspect or to execute the passive Internet of Things (AIoT) device information transmission method of any embodiment of the second aspect.

[0031] In at least one embodiment of this disclosure, an AIoT service request is sent by a network device to at least one first network element capable of obtaining AIoT device information, such as a reading device, a 3GPP core network device, and / or a third-party device. This allows the network device to obtain AIoT device information and / or AIoT service status indications sent by different first network elements. Statistical processing of the AIoT device information yields analysis results for the AIoT devices. These analysis results are then sent to AIoT application devices to meet the service needs of different application scenarios of the AIoT application devices. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0033] Figure 1 is a topology diagram of communication between AIoT devices and base stations;

[0034] Figure 2 is a topology diagram of AIoT devices connecting to the network through intermediate nodes;

[0035] Figure 3 is a schematic diagram of architecture 1 that supports the topologies shown in Figures 1 and 2;

[0036] Figure 4 is a schematic diagram of architecture two that supports the topologies shown in Figures 1 and 2;

[0037] Figure 5 is a flowchart illustrating a passive Internet of Things (AIoT) device information transmission method provided in an embodiment of this disclosure;

[0038] Figure 6 is a flowchart illustrating another passive Internet of Things (AIoT) device information transmission method provided in this embodiment of the present disclosure;

[0039] Figure 7 is a schematic diagram of the AIoT device information transmission process when the UE acts as the Reader in the AIoT inventory scenario.

[0040] Figure 8 is a schematic diagram of the AIoT device information transmission process in the AIoT inventory scenario, where the RAN acts as the Reader.

[0041] Figure 9 is a schematic diagram of the AIoT device information transmission process where the UE acts as the Reader in the scenario of AIoT positioning or sensing data reporting.

[0042] Figure 10 is a schematic diagram of an AIoT service subscription process provided in an embodiment of this disclosure;

[0043] Figure 11 is a schematic diagram of a UE Reader reporting AIoT capability information according to an embodiment of this disclosure;

[0044] Figure 12 is a schematic diagram of a passive Internet of Things (AIoT) device information transmission device provided in an embodiment of this disclosure;

[0045] Figure 13 is a schematic diagram of another passive Internet of Things (AIoT) device information transmission device provided in an embodiment of this disclosure;

[0046] Figure 14 is a schematic diagram of a network device provided in an embodiment of this disclosure;

[0047] Figure 15 is a schematic diagram of a reading device provided in an embodiment of this disclosure. Detailed Implementation

[0048] To better understand the above-described objectives, features, and advantages of this disclosure, the present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It is to be understood that the described embodiments are only some, not all, of the embodiments of this disclosure. The specific embodiments described herein are merely for explaining this disclosure and are not intended to limit it. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure are within the scope of protection of this disclosure.

[0049] It should be noted that in this article, relational terms such as “first” and “second” are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0050] Figure 1 is a topology diagram of communication between AIoT devices and base stations. In Figure 1, the base station (BS) communicates directly with the AIoT devices as a reader.

[0051] Figure 2 is a topology diagram of AIoT devices connecting to the network through an intermediate node. The intermediate node is a UE (UE Reader) that supports the reader function. The interface between the UE and the AIoT device is the same as the interface between the AIoT device and the base station acting as the reader.

[0052] There are several alternative architectures that support the topologies shown in Figures 1 and 2, such as Architecture 1 shown in Figure 3 and Architecture 2 shown in Figure 4.

[0053] As shown in Figure 3, in Architecture 1, the protocol between the User Equipment Reader (UE Reader) and the Passive IoT Function (AIoTF) is the AIoT Application Protocol (AIoT-AP), and they transmit signaling through Protocol Data Unit (PDU) sessions. The AIoT device and AIoTF support the AIoT Non-Access Stratum (NAS) protocol.

[0054] As shown in Figure 4, in Architecture 2, the message transmission path between the UE Reader and the AIoTF can be a Radio Resource Control (RRC) message between the UE and the Radio Access Network (RAN), a transmission path between the 5G base station (gNB) / AIoT RAN and the AIoTF, or an AIoT NAS message. Specifically, the transmission path between the gNB / AIoT RAN and the AIoTF can be from the gNB / AIoT RAN to the AMF and from the AMF to the AIoTF, or it can be from the gNB / AIoT RAN to the AIoTF.

[0055] In Figures 3 and 4, the functions of the Passive Internet of Things Function (AIoTF) are as follows:

[0056] 1. AIoTF manages information related to AIoT devices.

[0057] 2. AIoTF registers network function (NF) attribute information within the network storage function (NRF).

[0058] 3. The AIoTF receives an AIoT service request from the Application Function (AF) and triggers the BS Reader or UE Reader to perform AIoT service operations on the AIoT device.

[0059] 4. AIoTF obtains the results from BS Reader and UE Reader and sends them to AF.

[0060] In Figures 3 and 4, the Network Exposure Function (NEF) supports exposing network capabilities to external third parties (such as the Application Firewall). These exposed network capabilities are categorized into monitoring capabilities, provisioning capabilities, policy / charging capabilities, network status reporting capabilities, and analytics reporting capabilities. Monitoring capabilities monitor specific events of the terminal in the 5G network and expose these monitored events to external third parties via the NEF. Provisioning capabilities allow external third parties to provide information available to the UE in the 5G network, i.e., the UE's configuration information. Policy / charging capabilities provide QoS and charging policies to the UE based on requests from external third parties. Analytics capabilities allow external third parties to request analytical data from the 5G system.

[0061] At least one embodiment of this disclosure provides a passive Internet of Things (AIoT) device information transmission method, apparatus, network device, reading device, or storage medium. After receiving an AIoT service request, the network device can obtain AIoT device information and / or AIoT service status indication by sending the AIoT service request to a reading device, a 3GPP core network device, and / or a third-party device. Then, it can perform statistical processing on the AIoT device information according to preset dimensions to obtain AIoT device statistical information. The AIoT device information, AIoT device statistical information, and / or AIoT device incremental information are then sent to AIoT application devices to meet the service needs of different application scenarios of AIoT application devices.

[0062] Figure 5 is a flowchart illustrating a passive Internet of Things (AIoT) device information transmission method according to an embodiment of this disclosure. This method is applied to network devices. Network devices may be, for example, AIoT servers, AIoT enablers, or other application enablement layer devices serving AIoT devices. The network device can be an independent network element / function or co-located with existing application enablement layer network elements / functions. This method is applicable to 5G and 6G networks. As shown in Figure 5, the method may include, but is not limited to, steps 501 to 503:

[0063] In step 501, an AIoT service request is sent to at least one first network element capable of obtaining AIoT device information.

[0064] Optionally, in this embodiment of the application, the network device sends an AIoT service request to at least one first network element.

[0065] In this embodiment, the network device receives AIoT service requests sent by AIoT application devices (e.g., Vertical Application Layer (VAL Server)).

[0066] The AIoT service request must include at least one of the following:

[0067] AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier (which can be a User Equipment Reader (UE Reader) identifier or a Radio Access Network Reader (RAN Reader) identifier), number of AIoT devices, and Device to Reader (D2R) data volume.

[0068] The AIoT business types include any of the following:

[0069] Inventory, location, sensor data reporting, read, write, enable, disable.

[0070] - Inventory information includes AIoT device identifiers. In automated warehousing scenarios, inventory refers to requesting AIoT devices within a certain area to report their identifiers, thereby enabling the counting of goods within that area.

[0071] - The location information for AIoT devices includes the AIoT device identifier and the AIoT device location.

[0072] - The AIoT device information corresponding to sensor data reporting includes the AIoT device identifier and the sensor data information of the AIoT device.

[0073] - The AIoT device information read includes the AIoT device identifier.

[0074] The information for the AIoT device to be written includes the AIoT device identifier.

[0075] - The information for activating (enable) the corresponding AIoT device includes the AIoT device identifier.

[0076] - The information for the AIoT device that is disabled includes the AIoT device identifier.

[0077] In this embodiment, after receiving an AIoT service request, the network device sends the AIoT service request to at least one first network element capable of obtaining AIoT device information. The at least one first network element capable of obtaining AIoT device information includes: a reading device, a 3GPP core network device, and / or a third-party device.

[0078] The reading device can be the reading device corresponding to the reading device identifier carried in the AIoT service request. The reading device can be a User Equipment Reader (UE Reader), an AIoT Client inside the terminal, or a Radio Access Network Reader (RAN Reader). It can also be a 3GPP core network device, such as a Network Development Function (NEF). Third-party devices are independent of the 3GPP network and can acquire or store information from AIoT devices.

[0079] In step 502, a first AIoT service response corresponding to an AIoT service request sent by at least one first network element is received; wherein the first AIoT service response includes at least one of the following: AIoT device information and AIoT service status indication.

[0080] Optionally, the network device receives a first AIoT service response sent by at least one first network element. The first AIoT service response corresponds to a received AIoT service request.

[0081] The AIoT device information includes at least one of the following:

[0082] Tag information of AIoT devices, location information of AIoT devices, location information of reading devices, and AIoT sensing data information of AIoT devices and / or reading devices.

[0083] In AIoT devices, the tag information is an identifier attached to the device, used to provide basic information, identification, tracking, and management functions. The tag information may include basic information such as the device's name, model, serial number, manufacturer, and production date, as well as a unique identifier for the AIoT device (such as IP address or MAC address). The tag information is considered the device's identification information. Therefore, the tag information can be understood as the device's identification information.

[0084] Among them, AIoT sensing data information refers to business data from sensing services. AIoT device information may also include data information from other business types, such as the location of AIoT devices in the positioning service.

[0085] In step 503, a second AIoT service response is sent to the AIoT application device based on the first AIoT service response; wherein the second AIoT service response includes at least one of the following: AIoT device information, AIoT device statistical information, and AIoT device incremental information.

[0086] Optionally, the second AIoT service response includes a first analysis result, which includes at least one of the following: AIoT device information, AIoT device statistics, and AIoT device incremental information.

[0087] The AIoT device statistics information is the information of AIoT devices obtained by statistical processing according to preset dimensions; the statistical processing includes at least one of the following: unified format, deduplication, classification, and aggregation; the preset dimensions include at least one of the following: time, location, space, and quantity.

[0088] The incremental information for AIoT devices refers to information about AIoT devices that have not been inventoried.

[0089] As can be seen, in this embodiment, after receiving an AIoT service request, the network device can obtain AIoT device information and / or AIoT service status indication by sending the AIoT service request to the reading device, 3GPP core network device, and / or third-party device; then, it can perform statistical processing on the AIoT device information according to preset dimensions to obtain AIoT device statistical information; and then send the AIoT device information, AIoT device statistical information, and / or AIoT device incremental information to the AIoT application device to meet the service needs of different application scenarios of the AIoT application device.

[0090] In some embodiments, when the network device receives a first AIoT service response corresponding to an AIoT service request sent by at least one first network element, the method further includes the following (1) and (2):

[0091] (1) Send AIoT device information to the second network element with artificial intelligence (AI) function.

[0092] Optionally, A-IoT device information can be sent to the second network element.

[0093] The second network element includes at least one of the following:

[0094] Network Data Analytics Function (NWDAF), Application Data Analytics Enablement Service (ADAES), and Artificial Intelligence / Machine Learning Enablement (AIMLE).

[0095] (3) Receive the AI ​​analysis results of the AIoT device information sent by the second network element. The AI ​​analysis results here can be understood as the second analysis results.

[0096] The AI ​​analysis results include at least one of the following:

[0097] AIoT device information analysis includes the actual number of AIoT devices, the duration of AIoT devices in the AIoT business area, the time of humidity or temperature changes, and predictive data.

[0098] The prediction data includes at least one of the following: predicted AIoT device information, and predicted AIoT device location information.

[0099] Accordingly, in step 503, the second AIoT service response sent to the AIoT application device also includes AI analysis results.

[0100] In some embodiments, after receiving an AIoT service request from an AIoT application device (e.g., a Vertical Application Layer Server (VAL Server)), the network device may also perform an authorization check on the AIoT service request.

[0101] For example, network devices check whether the VAL Server can initiate AIoT service requests. Network devices can determine whether to allow or authorize the VAL Server to initiate AIoT service requests based on pre-configuration or operator policies.

[0102] In this embodiment, when the network device performs an authorization check on the AIoT service request and the authorization is successful, that is, the VAL Server can initiate the AIoT service request, or the AIoT service request is valid, the network device sends the AIoT service request to at least one first network element that can obtain AIoT device information.

[0103] When a network device sends an AIoT service request, it can determine the recipient of the AIoT service request based on at least one of the following:

[0104] AIoT service requests, reading device AIoT capability information, pre-configuration, operator policies;

[0105] The objects include reading devices, 3GPP core network devices, and / or third-party devices.

[0106] For example, the network device determines to send the AIoT service request to the UE Reader based on the UE Reader's identifier and AIoT capability information carried in the AIoT service request. Or,

[0107] The network device determines to send an AIoT service request to the RAN Reader based on the fact that the AIoT service request does not carry the UE Reader identifier and / or the UE Reader has not reported AIoT capability information.

[0108] As can be seen, in this embodiment, the objects of AIoT service requests are increased (such as 3GPP core network equipment and third-party equipment), thereby increasing the sources from which network devices obtain AIoT device information, improving the reliability of obtaining AIoT device information, and meeting the diversified and personalized needs of AIoT services.

[0109] In some embodiments, when the network device receives a first AIoT service response corresponding to an AIoT service request sent by at least one first network element, the method further includes:

[0110] Perform authentication, authorization, and / or privacy checks on AIoT device information.

[0111] In this embodiment, in order to prevent errors in the AIoT device information reported by the reading device, 3GPP core network device and / or third-party device, or based on the request of the AIoT application device (e.g., VAL Server), the network device can perform authentication, authorization and / or privacy checks on the AIoT device identifier in the first AIoT service response.

[0112] For example, network devices can interact with AIoT application devices (such as VAL Servers) or third-party devices in advance to obtain AIoT device identifiers and privacy information within the AIoT service area. Then, based on the AIoT device identifiers and privacy information obtained in advance, the network devices can perform authentication, authorization, and / or privacy checks on the AIoT device identifiers in the first AIoT service response.

[0113] It should be noted that since AIoT devices do not rely on traditional batteries for power, they cannot perform authentication or authorization checks like traditional UEs. Therefore, network devices can only perform authentication or authorization checks on the AIoT device identifier after receiving the first AIoT service response, that is, after obtaining the AIoT device information.

[0114] In this embodiment, the network device performs authentication, authorization, and / or privacy checks on the AIoT device information. If the authentication, authorization, and / or privacy checks pass, the network device performs statistical processing on the AIoT device information according to preset dimensions (such as time, location, space, and / or quantity) (such as unified format, deduplication, classification, and / or aggregation) to obtain AIoT device statistical information.

[0115] In this embodiment, the network device carries AIoT device information, AIoT device statistics, and / or AIoT device incremental information that meet the AIoT service requirements in a second AIoT service response and sends it to the AIoT application device (e.g., VAL Server). If there is no AIoT device information, AIoT device statistics, and / or AIoT device incremental information that meet the AIoT service requirements, the network device sends a second AIoT service response carrying the reason for the error to the AIoT application device (e.g., VAL Server).

[0116] It should be noted that for periodically reported AIoT service requests, each time the network device reports, it only needs to report the incremental information of the AIoT device to the AIoT application device (such as the VAL Server).

[0117] In some embodiments, the network device may also receive AIoT service subscription requests sent by AIoT application devices.

[0118] Among them, the AIoT application device is, for example, an AIoT application server. An AIoT service subscription request includes at least one of the following:

[0119] The AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reader device identifier, number of AIoT devices, device-to-reader (D2R) data volume, and an indication to report all data or updated data. Updated data can also be understood as changed data.

[0120] After receiving an AIoT service subscription request, if the network device performs an authorization check on the AIoT service subscription request and the authorization is successful, the network device sends the AIoT service subscription request to the 3GPP core network equipment (such as the Network Development Function (NEF)) and may also send the first AIoT service subscription request response to the AIoT application server.

[0121] In some embodiments, after a network device sends an AIoT service subscription request to the Network Development Function (NEF), it may receive a second AIoT service subscription request response sent by the Network Development Function (NEF); and / or receive a first AIoT service subscription notification sent by the Network Development Function (NEF); wherein the first AIoT service subscription notification includes AIoT device information.

[0122] If a network device receives the first AIoT service subscription notification, the network device will perform statistical processing on the AIoT device information according to preset dimensions (such as time, location, space and / or quantity) (such as unified format, deduplication, classification and / or aggregation) to obtain AIoT device statistical information.

[0123] In this embodiment, the network device carries AIoT device statistics and / or AIoT device incremental information in the second AIoT service subscription notification and sends it to the AIoT application server. The AIoT device incremental information refers to information about AIoT devices that have not yet been stored in the database.

[0124] In some embodiments, the network device may also receive AIoT capability information.

[0125] The AIoT capability information is sent to the network device by a reading device (which can be a User Equipment Reader, an AIoT Client inside the terminal, or a Radio Access Network Reader). The AIoT capability information includes at least one of the following:

[0126] Read the device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier.

[0127] The reader identifier may be the same as or different from the reading device identifier.

[0128] After receiving AIoT capability information, the network device performs an authorization check on the AIoT capability information and, if the authorization is successful, sends a response message to the reading device and stores the AIoT capability information.

[0129] Figure 6 is a flowchart illustrating another passive Internet of Things (AIoT) device information transmission method provided in this embodiment of the present disclosure. This method is applied to a reading device. The reading device can be a User Equipment Reader (UE Reader) or a Radio Access Network Reader (RAN Reader). As shown in Figure 6, the method may include, but is not limited to, steps 601 and 602:

[0130] In step 601, AIoT capability information is sent to the network device; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier.

[0131] In step 602, the response information sent by the network device is received.

[0132] For example, the reading device sends a request to the network device to report and / or update AIoT capability information. If the network device performs an authorization check on the request and the authorization check passes, the network device sends a response message to the reading device.

[0133] In some embodiments, the reading device may also receive AIoT service requests sent by the network device.

[0134] The AIoT service request must include at least one of the following:

[0135] AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader (D2R) data volume;

[0136] After receiving an AIoT service request, the reading device initiates an AIoT service request to the AIoT device when the AIoT service triggering conditions are met, in order to obtain the AIoT device information corresponding to the AIoT service and the status indication of whether the AIoT device has been stored.

[0137] After acquiring information about at least one AIoT device, the reading device sends a first AIoT service response to the network device. The first AIoT service response includes at least one of the following:

[0138] AIoT device information and AIoT service status indication.

[0139] The AIoT device information includes at least one of the following:

[0140] Tag information of AIoT devices, location information of AIoT devices, location information of reading devices, and AIoT sensing data information of AIoT devices and / or reading devices.

[0141] Example 1: AIoT inventory scenario, UE as Reader

[0142] Figure 7 illustrates the AIoT device information transmission process where the UE acts as a Reader in an AIoT inventory scenario. This embodiment is applicable to the network architecture for transmitting AIoT data in the user plane topology shown in Figure 2 (i.e., architecture one shown in Figure 3).

[0143] In this embodiment, the reading device is either a UE Read or an internal passive IoT client (AIoT client). The AIoT client is a client within the terminal that serves AIoT devices in the application enablement layer. The network device is an AIoT application enabler, which is an enabler server added by the application enablement layer to serve AIoT devices. The AIoT application device is a VAL Server.

[0144] This embodiment applies to a topology architecture where the UE acts as the Reader. The AIoT enabler can determine whether to send a request to the UE reader based on whether the AIoT service request carries the UE reader identifier and the AIoT capability information reported by the UE.

[0145] In this embodiment, the AIoT enabler supports AIoT inventory requests, that is, obtaining AIoT device information from the 3GPP core network (3GPP CN), UE Reader or passive IoT client inside the terminal (AIoT client), and third-party devices (3rd Party).

[0146] As shown in Figure 7, the AIoT device information transmission process includes the following steps 1 to 7:

[0147] 1. The AIoT application device (VAL server) sends an AIoT service request to the AIoT enabler. The AIoT service request includes at least one of the following:

[0148] Service type indication (inventory), AIoT service area, AIoT device identifier, UEreader identifier, AIoT service triggering conditions (such as goods entering and leaving), AIoT service reporting frequency (such as periodicity), number of AIoT devices (optional), D2R data volume (optional), etc.

[0149] An AIoT device can be a single device or a group of devices. If an AIoT service request does not contain an AIoT device identifier, it means that all AIoT devices need to be monitored. An AIoT service area refers to the area where inventory operations are performed. The VAL server can include multiple AIoT service areas in an AIoT service request.

[0150] 2. The AIoT enabler performs authorization checks on AIoT service requests from the VAL server. For example, it checks whether the VAL server can initiate AIoT service requests. The AIoT enabler can determine whether to allow or authorize the VAL server to initiate AIoT service requests based on pre-configuration or operator policies.

[0151] 3a. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the UE Reader. The AIoT enabler can select a suitable UE Reader based on the AIoT capabilities reported by the UE (as shown in Implementation 6) and the AIoT service area carried in the AIoT service request.

[0152] 3b. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the 3GPP CN (e.g., NEF). The AIoT enabler can select the appropriate NEF based on the AIoT service area carried in the AIoT service request and request the 3GPP CN to perform the Inventory operation.

[0153] 3c. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the third-party device (3rd Party), requesting the third party to send AIoT device information (such as device tags, number of devices, etc.).

[0154] Note: The AIoT enabler can decide whether to send AIoT service requests to the UE Reader, 3GPP CN and / or third-party devices based on AIoT service requests (such as the UE reader identifier carried), the UE's reporting capabilities (as shown in Example 6), pre-configuration, operator policies, etc.

[0155] 4. When the triggering conditions for an AIoT service request are met, the UE Reader triggers the corresponding Inventory operation process to obtain information about one or more AIoT devices (such as AIoT device identifiers) and a status indication of whether the AIoT device has been inventoried.

[0156] 5a. The UE Reader sends the acquired AIoT device information to the AIoT enabler.

[0157] 5b. NEF provides the corresponding AIoT device information to the AIoT enabler according to the AIoT service request (as shown in Implementation 5).

[0158] 5c. The third-party device returns the corresponding AIoT device information to the AIoT enabler according to the AIoT service request.

[0159] 6. The AIoT enabler authenticates, authorizes, and performs privacy checks on the AIoT device identifiers reported by the UE Reader, 3GPP CN, ​​and / or third-party devices. The AIoT enabler may interact with the VAL server or third-party devices in advance to obtain the AIoT device identifiers and privacy information within the AIoT service area, and perform authentication, authorization, and privacy checks on the received AIoT device identifiers based on this information.

[0160] If authentication is successful, the AIoT enabler performs statistical processing on the received AIoT device information (such as unifying the format, deduplication, classification, aggregation, etc.) and outputs AIoT device statistics according to preset dimensions (such as time, location, space, quantity, etc.), such as the number of AIoT devices in the AIoT business area, the duration of AIoT devices entering and leaving the AIoT business area, and historical data of AIoT devices.

[0161] 7. The AIoT enabler reports AIoT device information, AIoT device statistics, and / or incremental AIoT device information that meet the AIoT business requirements to the VAL server. If there are no results for the AIoT business requirements, it reports the reason for the error.

[0162] Note: For periodically reported AIoT service requests, the AIoT enabler will not report all AIoT device information each time, but only the incremental information of AIoT devices (the incremental information of AIoT devices is the information of AIoT devices that have not been stored in inventory).

[0163] Example 2: AIoT inventory scenario, RAN acts as Reader

[0164] Figure 8 illustrates the AIoT device information transmission process when the RAN acts as the Reader in an AIoT inventory scenario. The difference between this embodiment and Implementation 1 is that this embodiment applies to a topology where the RAN acts as the Reader (i.e., the topology shown in Figure 1), allowing the RAN to interact directly with the AIoT enabler. If the AIoT service request does not carry the UE reader identifier, and / or the UE does not report its AIoT support capability, the AIoT enabler initiates an AIoT service request to the RAN reader.

[0165] As shown in Figure 8, the AIoT device information transmission process includes the following steps 1 to 7:

[0166] 1-2, same as in Example 1.

[0167] 3a. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the RAN reader. The AIoT enabler can select the appropriate RAN reader based on the AIoT service area carried in the AIoT service request.

[0168] Note: The AIoT enabler may decide whether to send an AIoT service request to the RAN Reader, 3GPP CN, ​​and / or third-party devices based on the AIoT service request, UE capabilities, pre-configuration, and / or operator policies. If the AIoT service request does not carry the UE reader identifier, and / or the UE has not reported its AIoT support capability, the AIoT enabler will send the AIoT service request to the RAN reader.

[0169] 3b to 3c are the same as in Example 1.

[0170] 4. When the triggering conditions for an AIoT service request are met, the RAN reader triggers the corresponding Inventory operation process and reports the AIoT device information under its jurisdiction (such as the AIoT device identifier).

[0171] 5a. The RAN reader reports AIoT device information to the AIoT enabler.

[0172] 5b to 5c are the same as in Example 1.

[0173] 6. Similar to Example 1, the AIoT enabler will authenticate, authorize, and perform privacy checks on the AIoT device identifiers reported by the RAN reader, 3GPP CN, ​​and / or third-party devices.

[0174] 7. Same as Example 1.

[0175] Example 3: AIoT positioning or sensing data reporting scenario, UE as Reader

[0176] Figure 9 illustrates the AIoT device information transmission process where the UE acts as a Reader in an AIoT positioning or sensing data reporting scenario. The difference between this embodiment and Implementation 1 is that this embodiment is applicable to AIoT positioning or sensing data reporting scenarios. Positioning scenarios refer to AIoT devices reporting their location information, while sensing data reporting scenarios refer to AIoT devices reporting various sensing data information. This embodiment is applicable to the network architecture for transmitting AIoT data in the user plane topology shown in Figure 2 (i.e., Architecture 1 shown in Figure 3).

[0177] As shown in Figure 9, the AIoT device information transmission process includes the following steps 1 to 7:

[0178] 1. Similar to Example 1, the difference is that the service type indicator carried in the AIoT service request is either location or sensor data reporting, the operation command is Read, and the triggering conditions may be different (such as humidity threshold).

[0179] 2. Same as Example 1.

[0180] 3a. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the UE Reader, requesting the UE Reader to report AIoT device information, including AIoT device identifier, AIoT device location information, or AIoT device sensing data information (such as humidity, temperature).

[0181] 3b. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the 3GPP CN (such as NEF), requesting the 3GPP CN to report AIoT device information, including AIoT device identifier, AIoT device location information, or AIoT device sensing data information (such as humidity, temperature).

[0182] 3c. (Optional) After authorization, the AIoT enabler sends the AIoT service request to the third-party device, requesting the third-party device to report AIoT device information, including AIoT device identifier, AIoT device location information, or AIoT device sensing data information (such as humidity, temperature).

[0183] 4. The UE Reader initiates the corresponding positioning process or sensing data acquisition process to the AIoT device.

[0184] 5a-5c. Same as Example 1. The difference is that the UE Reader will simultaneously report its own location information and / or sensing data information.

[0185] 6. Similar to Example 1, the difference lies in that the AIoT enabler performs statistical processing on the received AIoT device information (such as format unification, deduplication, classification, aggregation, etc.), and may interact with network elements with AI capabilities such as Network Data Analytics Function (NWDAF), Application Data Analytics Enablement Service (ADAES), and Artificial Intelligence / Machine Learning Enablement (AIMLE) to obtain AI analysis results of the AIoT device information (such as actual quantity, duration of presence in the AIoT business area, time of humidity or temperature changes, and predicted data). The predicted data includes at least one of the following: predicted AIoT device information and predicted AIoT device location information.

[0186] 7. Same as Example 1.

[0187] Example 4: AIoT positioning or sensing data reporting scenario, RAN acts as Reader

[0188] Similar to Embodiment 2, this embodiment is applicable to topologies where the RAN acts as the Reader.

[0189] This embodiment is mainly used for AIoT positioning or sensing data reporting scenarios. The main difference from Embodiment 2 is that the service type indicator is different. This embodiment is for positioning or sensing data reporting, and the operation command is Read. The triggering conditions may be different.

[0190] Furthermore, the process between the RAN and AIoT devices involves acquiring location or sensing data. The RAN Reader will simultaneously report its own location information and / or sensing data information to the AIoT enabler.

[0191] Example 5: NEF supports open AIoT device information

[0192] Figure 10 is a schematic diagram of an AIoT service subscription process provided in an embodiment of this disclosure. In this embodiment, the AIoT enabler, acting as an Application Function (AF), subscribes to AIoT services from the 3GPP core network (such as NEF). After receiving the relevant AIoT device information, the 3GPP core network (such as NEF) releases the relevant AIoT device information to the AIoT enabler. The process shown in Figure 10 is also applicable to the subscription process for AIoT service updates / releases.

[0193] As shown in Figure 10, the AIoT service subscription process includes the following steps 1 to 7:

[0194] 1. The AIoT application server sends an AIoT service subscription request to the AIoT enabler, carrying service type indications (such as inventory, read, write, disable, enable, location, sensor data reporting), AIoT device identifiers (such as tag, group identifier, type), AIoT service area, UE reader identifier, number of AIoT devices, D2R data volume, AIoT service reporting frequency, AIoT service triggering conditions, and instructions to report all data or report updated data. If location information needs to be reported, it may also carry location services (LCS) quality of service (QoS).

[0195] 2. The AIoT enabler performs authorization checks on requests to the AIoT application server.

[0196] 3. Once authorization is granted, the AIoT enabler sends an AIoT service subscription request response to the AIoT application server.

[0197] 4. The AIoT enabler sends an AIoT service subscription request to the NEF. If the request information in step 1 does not carry the Reader identifier associated with the AIoT device, the NEF will distribute it to other core network elements based on its own stored information or the Reader identifier obtained from the Unified Data Repository (UDR).

[0198] After the NEF passes the authorization check of the AIoT service subscription request initiated by the AIoT enabler, it sends the corresponding subscription response to the AIoT enabler.

[0199] 5. NEF forwards the AIoT service subscription request received in step 4 to the corresponding Reader. After the set trigger conditions are met, NEF sends the AIoT device information reported by the Reader (such as tag information, AIoT device location information, Reader location information, AIoT device and / or Reader sensing data information, etc.) to the AIoT enabler.

[0200] 6. The AIoT enabler will uniformly format the AIoT device information received from different sources, and perform operations such as aggregation, filtering, deduplication, and fusion on a large amount of AIoT device information, and output AIoT device statistical information according to certain dimensions (such as time, location, space, quantity).

[0201] 7. The AIoT enabler provides the AIoT application server with AIoT device information, AIoT device statistics, and / or incremental AIoT device information that meet the needs of AIoT business.

[0202] Example 6: UE Reader Reports AIoT Capability Information

[0203] Figure 11 is a schematic diagram illustrating the process of a UE Reader reporting AIoT capability information according to an embodiment of this disclosure. In this embodiment, the UE, acting as a Reader, proactively reports its supported AIoT capabilities before the network initiates an AIoT service request to an AIoT device, assisting the network in discovering the corresponding Readers and AIoT devices. The process shown in Figure 11 is also applicable to the UE Reader updating AIoT capability information.

[0204] As shown in Figure 11, the process of UE Reader reporting AIoT capability information includes the following steps 1 to 3:

[0205] 1. The AIoT Client / UE Reader sends an AIoT capability reporting request to the AIoT enabler, carrying the UE identifier, Reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier, etc.

[0206] 2. The AIoT enabler performs authorization checks on the AIoT capability requests reported by the UE Reader.

[0207] 3. After authorization is granted, the AIoT enabler sends an AIoT capability reporting response to the UE Reader and stores the reported AIoT capability information.

[0208] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art will understand that the embodiments of this disclosure are not limited to the described order of actions, because according to the embodiments of this disclosure, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art will understand that the embodiments described in the specification are all optional embodiments.

[0209] Figure 12 is a schematic diagram of a passive Internet of Things (AIoT) device information transmission device provided in an embodiment of this disclosure. This device is applied to a network device, such as an AIoT server, an AIoT application enabler, or other application enablement layer devices serving AIoT devices. As shown in Figure 12, the device includes, but is not limited to, a first transmitting unit 1201, a receiving unit 1202, and a second transmitting unit 1203, as detailed below:

[0210] The first sending unit 1201 is used to send an AIoT service request to at least one first network element that is capable of obtaining AIoT device information;

[0211] The receiving unit 1202 is configured to receive a first AIoT service response corresponding to an AIoT service request sent by at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information and AIoT service status indication;

[0212] The second sending unit 1203 is used to send a second AIoT service response to the AIoT application device according to the first AIoT service response; wherein the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

[0213] In some embodiments, the second AIoT service response also includes AI analysis results;

[0214] The second sending unit 1203 is further configured to: send AIoT device information to the second network element with artificial intelligence (AI) function when the receiving unit 1202 receives a first AIoT service response corresponding to an AIoT service request sent by at least one first network element;

[0215] The receiving unit 1202 is also used to receive the AI ​​analysis results of the AIoT device information sent by the second network element.

[0216] In some embodiments, the receiving unit 1202 is further configured to: receive an AIoT service request sent by an AIoT application device before the first sending unit 1201 sends an AIoT service request to at least one first network element capable of obtaining AIoT device information;

[0217] The first sending unit 1201 is configured to: send an AIoT service request to at least one first network element capable of obtaining AIoT device information when the authorization check of the AIoT service request is performed and the authorization is passed.

[0218] In some embodiments, the first transmitting unit 1201 is configured to:

[0219] The object receiving the AIoT service request is determined based on at least one of the following:

[0220] AIoT service requests, reading device AIoT capability information, pre-configuration, operator policies;

[0221] The objects include reading devices, 3GPP core network devices, and / or third-party devices.

[0222] In some embodiments, the first sending unit 1201 determines the object receiving the AIoT service request based on at least one of the following:

[0223] Based on the user equipment reader identifier and the user equipment reader's AIoT capability information carried in the AIoT service request, determine whether to send the AIoT service request to the user equipment reader; or...

[0224] Based on the fact that the AIoT service request does not carry the user equipment reader identifier and / or the user equipment reader does not report AIoT capability information, it is determined to send an AIoT service request to the radio access network reader.

[0225] In some embodiments, the analysis results include at least one of the following:

[0226] AIoT device information, AIoT device statistics, and AIoT device incremental information.

[0227] In some embodiments, AIoT device information includes at least one of the following:

[0228] Tag information of AIoT devices, location information of AIoT devices, location information of reading devices, and AIoT sensing data information of AIoT devices and / or reading devices.

[0229] In some embodiments, an AIoT service request includes at least one of the following:

[0230] AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader (D2R) data volume.

[0231] In some embodiments, the AIoT device statistics information is the AIoT device information obtained by statistical processing; wherein, the statistical processing includes at least one of the following: unified format, deduplication, classification, and aggregation.

[0232] In some embodiments, the incremental information of AIoT devices is information about AIoT devices that have not been inventoried.

[0233] In some embodiments, the AIoT device statistics information is the information of AIoT devices obtained by statistical processing according to preset dimensions, and the preset dimensions include at least one of the following: time, location, space, and quantity.

[0234] In some embodiments, AIoT service types include any of the following: inventory, positioning, sensing data reporting, reading, writing, activation, and disabling;

[0235] The inventory includes the corresponding AIoT device information, including the AIoT device identifier;

[0236] The location information for the corresponding AIoT device includes the AIoT device identifier and the AIoT device location;

[0237] The AIoT device information corresponding to the reported sensing data includes the AIoT device identifier and the sensing data information of the AIoT device.

[0238] Read the corresponding AIoT device information, including the AIoT device identifier;

[0239] Write the corresponding AIoT device information, including the AIoT device identifier;

[0240] The activation of the corresponding AIoT device information includes the AIoT device identifier;

[0241] The corresponding AIoT device information, including the AIoT device identifier, is disabled.

[0242] In some embodiments, the receiving unit 1202 is further configured to:

[0243] Receive AIoT service subscription requests sent by AIoT application devices; wherein the AIoT service subscription request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, device-to-reader D2R data volume, and an indication to report all data or report updated data;

[0244] The second sending unit 1203 is also used to send an AIoT service subscription request to the 3GPP core network equipment.

[0245] In some embodiments, the receiving unit 1202 is further configured to:

[0246] After the second sending unit 1203 sends an AIoT service subscription request to the 3GPP core network equipment, it receives a second AIoT service subscription request response from the 3GPP core network equipment.

[0247] And / or, receive a first AIoT service subscription notification sent by a 3GPP core network device; wherein the first AIoT service subscription notification includes AIoT device information.

[0248] In some embodiments, the second transmitting unit 1203 is further configured to:

[0249] After receiving the first AIoT service subscription notification sent by the 3GPP core network equipment, the receiving unit 1202 sends a second AIoT service subscription notification to the AIoT application device; wherein the second AIoT service subscription notification includes at least one of the following: AIoT device statistical information and AIoT device incremental information.

[0250] In some embodiments, the receiving unit 1202 is further configured to:

[0251] Receive AIoT capability information sent by the reading device; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0252] The second sending unit 1203 is also used to send response information to the reading device.

[0253] For details of the various embodiments of the passive IoT AIoT device information transmission device shown in Figure 12, please refer to the various embodiments of the passive IoT AIoT device information transmission method shown in Figure 5. To avoid repetition, they will not be described again.

[0254] Figure 13 is a schematic diagram of another passive Internet of Things (AIoT) device information transmission device provided in an embodiment of this disclosure. This device is applied to a reading device, which can be a User Equipment Reader (UE Reader) or a Radio Access Network Reader (RAN Reader). As shown in Figure 13, the device includes, but is not limited to, a transmitting unit 1301 and a receiving unit 1302, as detailed below:

[0255] The sending unit 1301 is used to send AIoT capability information to the network device; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0256] The receiving unit 1302 is used to receive response information sent by the network device.

[0257] In some embodiments, the receiving unit 1302 is further configured to:

[0258] Receive AIoT service requests sent by network devices; wherein the AIoT service request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader D2R data volume;

[0259] The transmitting unit 1301 is also used for:

[0260] Send a first AIoT service response to the network device; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication.

[0261] In some embodiments, the sending unit 1301 is further configured to: after receiving the AIoT service request, the receiving unit 1302 initiates an AIoT service request to the AIoT device;

[0262] The device also includes an acquisition unit for acquiring AIoT device information corresponding to AIoT services.

[0263] For details of the various embodiments of the passive IoT AIoT device information transmission device shown in Figure 13, please refer to the various embodiments of the passive IoT AIoT device information transmission method shown in Figure 6. To avoid repetition, they will not be described again.

[0264] This disclosure also provides a processor-readable storage medium storing a program for causing a processor to execute the steps of various embodiments of the passive Internet of Things (AIoT) device information transmission method. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0265] Figure 14 is a schematic diagram of a network device provided in an embodiment of this disclosure. The network device may be, for example, an AIoT server, an AIoT enabler, or other network devices serving AIoT devices. As shown in Figure 14, the network device provided in this embodiment includes a memory 1401, a transceiver 1402, and a processor 1403.

[0266] Memory 1401 is used to store computer programs; transceiver 1402 is used to send and receive data under the control of the processor; processor 1403 is used to read the computer program from the memory and execute it.

[0267] Send an AIoT service request to at least one first network element capable of obtaining AIoT device information;

[0268] Receive a first AIoT service response corresponding to an AIoT service request sent by at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication;

[0269] Based on the first AIoT service response, a second AIoT service response is sent to the AIoT application device; wherein, the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

[0270] In some embodiments, the second AIoT service response also includes AI analysis results;

[0271] In the case of receiving a first AIoT service response corresponding to an AIoT service request sent by at least one first network element, the processor 1403 is further configured to:

[0272] Send AIoT device information to a second network element with artificial intelligence (AI) capabilities;

[0273] AI analysis results of receiving AIoT device information sent by the second network element.

[0274] In some embodiments, before sending an AIoT service request to at least one first network element capable of obtaining AIoT device information, the processor 1403 is further configured to:

[0275] Receive AIoT service requests sent by AIoT application devices;

[0276] If the authorization check of the AIoT service request is performed and the authorization is passed, the AIoT service request is sent to at least one first network element that can obtain AIoT device information.

[0277] In some embodiments, sending an AIoT service request to at least one first network element capable of obtaining AIoT device information includes:

[0278] The object receiving the AIoT service request is determined based on at least one of the following:

[0279] AIoT service requests, reading device AIoT capability information, pre-configuration, operator policies;

[0280] The objects include reading devices, 3GPP core network devices, and / or third-party devices.

[0281] In some embodiments, the object receiving the AIoT service request is determined based on at least one of the following:

[0282] Based on the user equipment reader identifier and the user equipment reader's AIoT capability information carried in the AIoT service request, determine whether to send the AIoT service request to the user equipment reader; or...

[0283] Based on the fact that the AIoT service request does not carry the user equipment reader identifier and / or the user equipment reader does not report AIoT capability information, it is determined to send an AIoT service request to the radio access network reader.

[0284] In some embodiments, the analysis results include at least one of the following:

[0285] AIoT device information, AIoT device statistics, and AIoT device incremental information.

[0286] In some embodiments, AIoT device information includes at least one of the following:

[0287] Tag information of AIoT devices, location information of AIoT devices, location information of reading devices, and AIoT sensing data information of AIoT devices and / or reading devices.

[0288] In some embodiments, an AIoT service request includes at least one of the following:

[0289] AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader (D2R) data volume.

[0290] In some embodiments, the AIoT device statistics information is the AIoT device information obtained by statistical processing; wherein, the statistical processing includes at least one of the following: unified format, deduplication, classification, and aggregation.

[0291] In some embodiments, the incremental information of AIoT devices is information about AIoT devices that have not been inventoried.

[0292] In some embodiments, the AIoT device statistics information is the information of AIoT devices obtained by statistical processing according to preset dimensions, and the preset dimensions include at least one of the following: time, location, space, and quantity.

[0293] In some embodiments, AIoT service types include any of the following: inventory, positioning, sensing data reporting, reading, writing, activation, and disabling;

[0294] The inventory includes the corresponding AIoT device information, including the AIoT device identifier;

[0295] The location information for the corresponding AIoT device includes the AIoT device identifier and the AIoT device location;

[0296] The AIoT device information corresponding to the reported sensing data includes the AIoT device identifier and the sensing data information of the AIoT device.

[0297] Read the corresponding AIoT device information, including the AIoT device identifier;

[0298] Write the corresponding AIoT device information, including the AIoT device identifier;

[0299] The activation of the corresponding AIoT device information includes the AIoT device identifier;

[0300] The corresponding AIoT device information, including the AIoT device identifier, is disabled.

[0301] In some embodiments, the processor 1403 is further configured to:

[0302] Receive AIoT service subscription requests sent by AIoT application devices; wherein the AIoT service subscription request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, device-to-reader D2R data volume, and an indication to report all data or report updated data;

[0303] Send an AIoT service subscription request to the 3GPP core network equipment.

[0304] In some embodiments, the processor 1403 is further configured to:

[0305] Receive AIoT service subscription requests sent by AIoT application devices; wherein the AIoT service subscription request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, device-to-reader D2R data volume, and an indication to report all data or report updated data;

[0306] Send an AIoT service subscription request to the 3GPP core network equipment.

[0307] In some embodiments, after receiving an AIoT service subscription request sent by an AIoT application device, the processor 1403 is further configured to:

[0308] If the authorization check of the AIoT service subscription request is performed and the authorization is successful, the first AIoT service subscription request response is sent to the AIoT application device.

[0309] In some embodiments, after sending an AIoT service subscription request to the 3GPP core network equipment, the processor 1403 is further configured to:

[0310] Receive the second AIoT service subscription request response sent by the 3GPP core network equipment;

[0311] And / or, receive a first AIoT service subscription notification sent by a 3GPP core network device; wherein the first AIoT service subscription notification includes AIoT device information.

[0312] In some embodiments, after receiving the first AIoT service subscription notification sent by the 3GPP core network device, the processor 1403 is further configured to:

[0313] Send a second AIoT service subscription notification to AIoT application devices; wherein the second AIoT service subscription notification includes at least one of the following: AIoT device statistics information, AIoT device incremental information.

[0314] In some embodiments, the processor 1403 is further configured to:

[0315] Receive AIoT capability information sent by the reading device; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0316] Response information sent to the reading device to transmit AIoT capability information.

[0317] In some embodiments, after receiving the AIoT capability information sent by the reading device, the processor 1403 is further configured to:

[0318] If the authorization check of the AIoT capability information is successful and the authorization is approved, a response message is sent to the reading device, and the AIoT capability information is stored.

[0319] For details of the network device embodiments shown in Figure 14, please refer to the embodiments of the passive IoT AIoT device information transmission method shown in Figure 5. To avoid repetition, they will not be described again.

[0320] Figure 15 is a schematic diagram of a reading device provided in an embodiment of this disclosure. The reading device can be a User Equipment Reader (UE Reader) or a Radio Access Network Reader (RAN Reader). As shown in Figure 15, the reading device provided in this embodiment of the disclosure includes a memory 1501, a transceiver 1502, and a processor 1503.

[0321] Memory 1501 is used to store computer programs; transceiver 1502 is used to send and receive data under the control of the processor; processor 1503 is used to read the computer program from the memory and execute it.

[0322] Send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier;

[0323] Receive response information sent by network devices.

[0324] In some embodiments, the processor 1503 is further configured to:

[0325] Receive AIoT service requests sent by network devices; wherein the AIoT service request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader D2R data volume;

[0326] Send a first AIoT service response to the network device; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication.

[0327] In some embodiments, after receiving an AIoT service request sent by a network device, the processor 1503 is further configured to:

[0328] Initiate an AIoT service request to the AIoT device;

[0329] Obtain AIoT device information corresponding to AIoT service requests.

[0330] For details of the various embodiments of the reading device shown in Figure 15, please refer to the various embodiments of the passive Internet of Things (AIoT) device information transmission method shown in Figure 6. To avoid repetition, they will not be described again.

[0331] In the above embodiments, the transceiver is used to receive and transmit data under the control of the processor. The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by the processor) and memory (represented by the memory). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver can be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. The processor is responsible for managing the bus architecture and general processing, and the memory can store data used by the processor during operation.

[0332] A processor can be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above methods can be completed through integrated logic circuits in the processor's hardware or through software instructions. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor.

[0333] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0334] Those skilled in the art will understand that although some embodiments described herein include certain features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of this disclosure and form different embodiments.

[0335] Those skilled in the art will understand that the descriptions of the various embodiments have different focuses, and for parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0336] Although embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A passive Internet of Things (AIoT) device information transmission method, applied to network devices, the method comprising: Send an AIoT service request to at least one first network element capable of obtaining AIoT device information; Receive a first AIoT service response corresponding to the AIoT service request sent by the at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication; Based on the first AIoT service response, a second AIoT service response is sent to the AIoT application device; wherein, the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

2. The method according to claim 1, wherein, The second AIoT service response also includes AI analysis results; When receiving a first AIoT service response corresponding to the AIoT service request sent by at least one first network element, the method further includes: Send the AIoT device information to a second network element with artificial intelligence (AI) capabilities; Receive the AI ​​analysis results of the AIoT device information sent by the second network element.

3. The method according to claim 1, wherein, Before sending the AIoT service request to at least one first network element capable of obtaining AIoT device information, the method further includes: Receive AIoT service requests sent by AIoT application devices; If the authorization check of the AIoT service request is performed and the authorization is successful, the AIoT service request is sent to at least one first network element that can obtain AIoT device information.

4. The method according to claim 1, wherein, Sending an AIoT service request to at least one first network element capable of obtaining AIoT device information includes: The object receiving the AIoT service request is determined based on at least one of the following: The AIoT service request, reading the device's AIoT capability information, pre-configuration, and operator policies; The objects referred to here are reading devices, 3GPP core network devices, and / or third-party devices.

5. The method according to claim 4, wherein, The determination of the object receiving the AIoT service request based on at least one of the following includes: Based on the user equipment reader identifier and the user equipment reader's AIoT capability information carried in the AIoT service request, it is determined whether to send the AIoT service request to the user equipment reader; or... Based on the fact that the AIoT service request does not carry the user equipment reader identifier and / or the user equipment reader does not report AIoT capability information, it is determined that the AIoT service request will be sent to the wireless access network reader.

6. The method according to claim 1, wherein, The analysis results include at least one of the following: The AIoT device information, AIoT device statistics, and AIoT device incremental information.

7. The method according to claim 1, wherein, The AIoT device information includes at least one of the following: Tag information of AIoT devices, location information of AIoT devices, location information of reading devices, and AIoT sensing data information of AIoT devices and / or reading devices.

8. The method according to claim 1, wherein, The AIoT service request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering conditions, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader (D2R) data volume.

9. The method according to claim 6, wherein, The AIoT device statistics information is the information of AIoT devices obtained through statistical processing; wherein, the statistical processing includes at least one of the following: unified format, deduplication, classification, and aggregation.

10. The method according to claim 6, wherein, The incremental information of AIoT devices refers to the information of AIoT devices that have not been stored in inventory.

11. The method according to claim 6, wherein, The AIoT device statistics information is obtained by statistical processing of AIoT devices according to preset dimensions. The preset dimensions include at least one of the following: time, location, space, and quantity.

12. The method according to claim 8, wherein, The AIoT service types include any of the following: inventory, positioning, sensing data reporting, reading, writing, activation, and disabling; The AIoT device information corresponding to the inventory includes the AIoT device identifier; The AIoT device information corresponding to the location includes the AIoT device identifier and the AIoT device location; The AIoT device information corresponding to the reported sensing data includes the AIoT device identifier and the sensing data information of the AIoT device. The information read from the corresponding AIoT device includes the AIoT device identifier; The corresponding AIoT device information to be written includes the AIoT device identifier; The activated AIoT device information includes the AIoT device identifier; The information for the disabled AIoT device includes the AIoT device identifier.

13. The method according to claim 1, wherein, The method further includes: Receive an AIoT service subscription request sent by an AIoT application device; wherein the AIoT service subscription request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering condition, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, device-to-reader D2R data volume, and an indication to report all data or report updated data; Send the AIoT service subscription request to the 3GPP core network equipment.

14. A passive Internet of Things (AIoT) device information transmission method, applied to a reading device, the method comprising: Send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier; Receive response information sent by the network device.

15. The method according to claim 14, wherein, The method further includes: Receive the AIoT service request sent by the network device; wherein the AIoT service request includes at least one of the following: AIoT service type, AIoT service area, AIoT service triggering condition, AIoT service reporting frequency, AIoT device identifier, reading device identifier, number of AIoT devices, and device-to-reader D2R data volume; Send a first AIoT service response to the network device; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication.

16. A passive Internet of Things (AIoT) device information transmission apparatus, applied to network equipment, the apparatus comprising: The first sending unit is used to send an AIoT service request to at least one first network element that is capable of obtaining AIoT device information; The receiving unit is configured to receive a first AIoT service response corresponding to the AIoT service request sent by the at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information and AIoT service status indication; The second sending unit is configured to send a second AIoT service response to the AIoT application device based on the first AIoT service response; wherein the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

17. A passive Internet of Things (AIoT) device information transmission apparatus, applied to a reading device, the apparatus comprising: A sending unit is used to send AIoT capability information to network devices; wherein the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier; The receiving unit is used to receive response information sent by the network device.

18. A network device, wherein, The network device includes a memory, a transceiver, and a processor; The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and execute them. Send an AIoT service request to at least one first network element capable of obtaining AIoT device information; Receive a first AIoT service response corresponding to the AIoT service request sent by the at least one first network element; wherein the first AIoT service response includes at least one of the following: AIoT device information, AIoT service status indication; Based on the first AIoT service response, a second AIoT service response is sent to the AIoT application device; wherein, the second AIoT service response includes the analysis results of the AIoT device corresponding to the AIoT service request.

19. A reading device, wherein, The reading device includes a memory, a transceiver, and a processor; The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and execute them. Send AIoT capability information to network devices; wherein, the AIoT capability information includes at least one of the following: reading device identifier, reader identifier, AIoT capability indication, coverage area, location information, and associated AIoT device identifier; Receive response information sent by the network device.

20. A processor-readable storage medium, wherein, The processor-readable storage medium stores a program for causing the processor to execute the passive Internet of Things (AIoT) device information transmission method as described in any one of claims 1 to 13, or to execute the passive Internet of Things (AIoT) device information transmission method as described in claim 14 or 15.

Images