Internet of things data sending method, internet of things data receiving method, identifier allocation method, and device

Abstract

Embodiments of the present disclosure provide an Internet of Things data sending method, an Internet of Things data receiving method, an identifier allocation method, and a device. The sending method comprises: receiving or acquiring first information from a tag, wherein the first information carries at least one of the following pieces of information: a tag identifier, a tag group identifier, and a transaction identifier; determining or obtaining second information, wherein the second information comprises at least one of the following pieces of first information: the carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, the carried tag identifier belongs to a first tag group or a first tag identifier group, and the carried transaction identifier is a first transaction identifier; and aggregating the at least one piece of second information and sending same to a first AF.

Description

Method for sending, receiving, and serial number allocation of IoT data, and device thereof

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese Patent Application No. 202410163129.8 filed in China on February 5, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the field of mobile communication technology, and in particular to a method for sending and receiving Internet of Things data, a device, an application function (AF), and a storage medium. Background Art

[0004] Passive IoT generally refers to a technical architecture that implements IoT applications through wireless communication technology. It does not rely on traditional power or battery power and has the advantages of low power consumption, low cost, small size, light weight, and long life. It can adapt to various harsh environments and application scenarios. Therefore, it is widely used in scenarios such as industrial automation, smart cities, smart homes, and medical health.

[0005] In some local scenarios, there may be a large or even massive number of passive IoT devices, also known as tags or devices. These devices consume a significant amount of network resources when responding to messages simultaneously, potentially triggering events such as signaling storms in the 5th Generation mobile communication technology (5G) Core Network (5GC), leading to network paralysis or service unavailability, severely impacting network reliability and security. Summary of the Invention

[0006] At least one embodiment of the present disclosure provides a method for sending, receiving, and serial number allocation methods and devices for IoT data, which are used to solve the problems of related technologies such as tag information transmission occupying too many network resources and affecting network security and reliability.

[0007] In order to solve the above technical problems, the present disclosure is implemented as follows:

[0008] In a first aspect, an embodiment of the present disclosure provides a method for transmitting IoT data, which is applied to a first device and includes:

[0009] Receive or obtain first information from a tag, where the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number;

[0010] Determine or obtain second information, where the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number;

[0011] Aggregate at least one of the second information and send it to the first AF.

[0012] In some embodiments, when at least one second information is aggregated and sent to the first AF, the first transaction sequence number is also carried.

[0013] In some embodiments, aggregating at least one of the second information and sending it to the first AF includes:

[0014] The first device sends the aggregated at least one second information to the first AF through a radio access network and / or a core network function.

[0015] In some embodiments, it further includes:

[0016] The first device performs the step of aggregating at least one second information and sending the aggregating information to the first AF when at least one of the following conditions is met:

[0017] The duration of the business operation reaches the timeout period;

[0018] Receiving or acquiring the second information reported by the first number of tags;

[0019] The amount of the second information reaches the maximum aggregation amount.

[0020] In some embodiments, it further includes:

[0021] The first device obtains third information, and the third information includes at least one of the following: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first tag identification group, the first transaction sequence number, the timeout duration of the business operation, the first quantity, and the maximum aggregation quantity.

[0022] In some embodiments, obtaining the third information includes at least one of the following:

[0023] The first device receives or obtains a service operation message sent by the first AF, where the service operation message includes the third information;

[0024] The first device assigns the first transaction sequence number to the business operation;

[0025] The first device locally configures or sets a timeout period for the service operation;

[0026] The first device locally configures or sets the first quantity;

[0027] The first device locally configures or sets the maximum aggregation quantity;

[0028] The first device receives or obtains the first transaction sequence number sent by the second device.

[0029] In some embodiments, the method further comprises:

[0030] When the first device is a tag reader, the first device directly forwards the service operation message to the corresponding tag;

[0031] When the first device is not a tag reader, the first device forwards the service operation message to the corresponding tag through the tag reader.

[0032] In some embodiments, after the first device assigns the first transaction sequence number to the service operation, the first device further forwards the service operation message carrying the first transaction sequence number to the corresponding tag.

[0033] In some embodiments, receiving or obtaining the first information from the tag includes at least one of the following:

[0034] When the first device is a tag reader, the first device directly receives or obtains the first information sent by the tag;

[0035] When the first device is not a tag reader, the first device receives or obtains the first information from the tag forwarded by the tag reader.

[0036] In some embodiments, when the first device is a tag reader, the first device is a terminal or a RAN;

[0037] When the first device is not a tag reader, the first device is a terminal, a RAN or a core network function.

[0038] In a second aspect, an embodiment of the present disclosure provides a method for receiving IoT data, which is applied to a first AF, including:

[0039] Receiving or obtaining aggregate information sent by the first device, the aggregate information including at least one second information, the second information including at least one of the following first information: a carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, a carried tag identifier belongs to a first tag group or a first tag identifier group, and a carried transaction sequence number is a first transaction sequence number;

[0040] At least one second information is obtained according to the aggregated information.

[0041] In some embodiments, the aggregate information also carries the first transaction sequence number.

[0042] In some embodiments, receiving or obtaining the aggregated information sent by the first device includes:

[0043] The first AF receives or obtains the aggregated information sent by the first device and forwarded via a radio access network RAN ​​and / or a core network function.

[0044] In some embodiments, it further includes:

[0045] The first AF sends a business operation message to the tag reader, and the business operation message includes at least one of the following information: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first transaction sequence number, the timeout duration of the business operation, the first number used to indicate the maximum number of tags, and the maximum aggregation number, where the maximum aggregation number is the maximum number of second information that can be aggregated by the aggregated information.

[0046] In some embodiments, when the tag reader is a terminal, the device further includes:

[0047] The first AF sends the service operation message to the core network function, and the core network function encapsulates the service operation message into a NAS message and sends the message to the tag reader.

[0048] In some embodiments, when the first device is a terminal, it also includes: the first AF carries its own IP address in the service operation message and sends it to the tag reader; wherein, the aggregate information is sent by the first device to the first AF through the user plane based on the IP address of the first AF.

[0049] In some embodiments, it further includes:

[0050] The first AF allocates the first transaction sequence number to the business operation.

[0051] In a third aspect, an embodiment of the present disclosure provides a sequence number allocation method, applied to a second device, including:

[0052] Receive or obtain a service operation message sent by the first AF;

[0053] Assigning a first transaction sequence number to the business operation;

[0054] Forward the service operation message carrying the first transaction sequence number to the tag.

[0055] In some embodiments, forwarding the service operation message carrying the first transaction sequence number to the tag includes:

[0056] When the second device is a tag reader, directly forwarding the service operation message carrying the first transaction sequence number to the tag;

[0057] When the second device is not a tag reader, the service operation message carrying the first transaction sequence number is forwarded to the tag through the tag reader.

[0058] In some embodiments, the second device is a terminal, a RAN, or a core network function.

[0059] In a fourth aspect, an embodiment of the present disclosure provides a first device, comprising a transceiver and a processor, wherein:

[0060] The transceiver is configured to receive or obtain first information from a tag, wherein the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number;

[0061] The processor is configured to determine or obtain second information, where the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number;

[0062] The transceiver is further configured to aggregate at least one piece of the second information and send the aggregated information to the first AF.

[0063] In a fifth aspect, an embodiment of the present disclosure provides a first device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in any one of the first aspects.

[0064] In a sixth aspect, an embodiment of the present disclosure provides a first AF, comprising a transceiver and a processor, wherein:

[0065] The transceiver is configured to receive or obtain aggregate information sent by the first device, the aggregate information including at least one second information, the second information including at least one of the following first information: a carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, a carried tag identifier belongs to a first tag group or a first tag identifier group, and a carried transaction sequence number is a first transaction sequence number;

[0066] The processor is configured to obtain at least one second information according to the aggregated information.

[0067] In the seventh aspect, an embodiment of the present disclosure provides a first AF, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method described in any one of the second aspects are implemented.

[0068] In an eighth aspect, an embodiment of the present disclosure provides a second device, including a transceiver and a processor, wherein:

[0069] The transceiver is configured to receive or obtain a service operation message sent by the first AF;

[0070] The processor is further configured to assign a first transaction sequence number to the business operation;

[0071] The transceiver is further configured to forward the service operation message carrying the first transaction sequence number to the tag.

[0072] In the ninth aspect, an embodiment of the present disclosure provides a second device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in any one of the third aspects.

[0073] In the tenth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described in any one of the first aspect, or the steps of the method described in any one of the second aspect, or the steps of the method described in any one of the third aspect are implemented.

[0074] In the eleventh aspect, an embodiment of the present disclosure provides a computer program product, comprising computer instructions, which, when executed by a processor, implement the steps of the method described in any one of the first aspect, or implement the steps of the method described in any one of the second aspect, or implement the steps of the method described in any one of the third aspect.

[0075] Compared with related technologies, the method for sending, receiving, serial number allocation and device of IoT data provided by the embodiments of the present disclosure can improve network resource utilization, reduce the risk of signaling storms, and improve network security and reliability by aggregating and sending information reported by tags. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present disclosure. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0077] FIG1 is a flow chart of a method for transmitting IoT data according to an embodiment of the present disclosure;

[0078] FIG2 is a flow chart of a method for receiving IoT data according to an embodiment of the present disclosure;

[0079] FIG3 is a flow chart of a method for receiving IoT data according to an embodiment of the present disclosure;

[0080] FIG4 is an interaction flow chart of Example 1 of an embodiment of the present disclosure;

[0081] FIG5 is an interaction flow chart of Example 1 of an embodiment of the present disclosure;

[0082] FIG6 is an interaction flow chart of Example 1 of an embodiment of the present disclosure;

[0083] FIG7 is a schematic structural diagram of a first device according to an embodiment of the present disclosure;

[0084] FIG8 is a schematic structural diagram of a first AF according to an embodiment of the present disclosure;

[0085] FIG9 is a schematic structural diagram of a second device according to an embodiment of the present disclosure;

[0086] FIG10 is a schematic structural diagram of a first device according to another embodiment of the present disclosure;

[0087] FIG11 is a schematic structural diagram of a first AF according to another embodiment of the present disclosure.

[0088] FIG12 is a schematic structural diagram of a second device according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0089] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0090] The terms "first", "second", etc. in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products or devices. "And / or" in the specification and claims represents at least one of the connected objects.

[0091] The technology described herein is not limited to New Radio (NR) systems and Long Time Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.21 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-Advanced (LTE-A) are new versions of UMTS that use E-UTRA.UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. However, the following description describes an NR system for example purposes, and NR terminology is used in much of the following description, although the techniques may also be applicable to applications other than NR system applications.

[0092] The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of this disclosure. The various examples may appropriately omit, substitute, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0093] In order to solve a series of problems such as the waste of network resources and the impact on network security and reliability caused by managing the access and data transmission of massive passive IoT devices in local scenarios, such as events such as 5GC signaling storms caused by a large number of tags responding to messages at the same time, the embodiments of the present disclosure propose a method for sending and receiving IoT data, which can reduce the consumption of network resources for information transmission by aggregating information, improve network resource utilization, and reduce the adverse effects of concentrated transmission of large amounts of information on network reliability and network security.

[0094] The solution of the embodiment of the present disclosure, when applied to a 5G network, can realize data aggregation and data transmission solutions and related processes based on the control plane and user plane by enhancing the existing 5G core network architecture.

[0095] In the various embodiments of the claims and the specification of the present disclosure, the label can be an independent label (tag) or a device (device), such as a device with a label function or a device provided with a label. The transaction number is usually used to uniquely identify a certain or a certain type of label business operation, and can be in the form of a number (number), an identity (ID), a transaction identifier (Transaction ID), a sequence number (SN), a session number (session ID), a task number (task ID), etc. The embodiments in the specification are mainly described using Transaction ID as an example. It can be understood that Transaction ID can also be replaced by a number, SN or other ID.

[0096] In addition, to facilitate understanding of the embodiments of the present disclosure, related issues and solutions are first described below.

[0097] 1. Aggregation of reporting information from a large number of passive IoT devices:

[0098] As an embodiment, a transaction number (such as a Transaction ID) can be assigned by a tag reader (which can be a Radio Access Network (RAN) or a User Equipment (UE)), 5GC, or AF. When a service is triggered, it is sent to the tag. After the tag is activated, it needs to report information to the tag reader. Within a certain time limit, the reader performs data aggregation based on the Transaction ID carried in the tag report information and reports it to the passive IoT AF through the 5G core network.

[0099] In other embodiments of the present disclosure, information aggregation can also be performed based on other factors or information, for example, based on whether the tag identifier carried by the tag reporting information (i.e., the tag message) belongs to a specific tag list (such as the first tag list below) or a specific tag (such as the first tag in the embodiment below), or whether the carried tag identifier belongs to a specific tag group (such as the first tag group in the embodiment below).

[0100] 2. Downlink service trigger mechanism:

[0101] Taking the 5G core network as an example, when the RAN acts as a tag reader, the trigger path for the tag service has the following options:

[0102] (1)AF->NEF->AMF->RAN->Tag;

[0103] (2) AF->NEF->other 5GC network functions (NF)->RAN->label;

[0104] (3) AF->NEF->AMF->other 5GC NF->RAN->label;

[0105] (4)AF->NEF->other 5GC NF->AMF->RAN->label.

[0106] Here, NEF refers to Network Exposure Function, and AMF refers to Access and Mobility Management Function.

[0107] When the UE acts as a tag reader, the service trigger path has the following options:

[0108] (1)AF->NEF->AMF->RAN->UE->Tag;

[0109] (2) AF->NEF->other 5GC NF->RAN->UE->label;

[0110] (3) AF->NEF->AMF->other 5GC NF->RAN->UE->label;

[0111] (4)AF->NEF->other 5GC NF->AMF->RAN->UE->label.

[0112] In some embodiments, the transaction ID may be allocated and carried by the AF, or may be allocated by a tag reader (RAN or UE), NEF, AMF, or one of the other 5GC NFs. Of course, some embodiments of the present disclosure may not allocate a transaction ID.

[0113] 3. The reporting path of aggregated information is explained here by taking the aggregation based on the transaction ID as an example. It is understandable that in the implementation method of aggregating based on other information, the transaction ID may not be carried:

[0114] Taking the 5G core network as an example, when the RAN acts as a tag reader, the reporting path for aggregated information has the following options:

[0115] (1) Tag (carrying Transaction ID) -> RAN performs Non-Access Stratum (NAS) aggregation based on Transaction ID -> AMF -> NEF -> AF;

[0116] (2) Tag (carrying Transaction ID) -> RAN performs NAS aggregation based on Transaction ID -> other 5GC NFs -> NEF -> AF;

[0117] (3) Tag (carrying Transaction ID) -> RAN performs NAS aggregation based on Transaction ID -> other 5GC NFs -> AMF -> NEF -> AF;

[0118] (4) Tag (carrying Transaction ID) -> RAN performs NAS aggregation based on Transaction ID -> AMF -> other 5GC NFs -> NEF -> AF.

[0119] When the UE acts as a tag reader, the reporting path for aggregated information has the following options:

[0120] (1) Tag (carrying Transaction ID) -> UE performs NAS aggregation based on Transaction ID -> RAN -> AMF -> NEF -> AF;

[0121] (2) Tag (carrying Transaction ID) -> UE performs NAS aggregation based on Transaction ID -> RAN -> other 5GC NFs -> NEF -> AF;

[0122] (3) Tag (carrying Transaction ID) -> UE performs NAS aggregation based on Transaction ID -> RAN -> other 5GC NFs -> AMF -> NEF -> AF;

[0123] (4) Tag (carrying Transaction ID) -> UE performs NAS aggregation based on Transaction ID -> RAN -> AMF -> other 5GC NFs -> NEF -> AF.

[0124] In addition, a tag message encapsulation mechanism may specifically be based on an early data transmission (EDT) and sent through a message established by a radio resource control (RRC) connection, in which a NAS message carrying data is encapsulated.

[0125] Figure 1 is a flow chart of the method for sending IoT data according to an embodiment of the present disclosure when it is applied to the first device side. The first device is a device that aggregates and transmits information reported by multiple tags. Specifically, the first device may be a device or network function other than the tag and AF in the tag service triggering path or the aggregated information reporting path mentioned above. For example, the first device may be a terminal (UE), RAN, or a core network function. Taking the 5G core network as an example, the core network function may be an AMF or other 5GC NF, etc. In addition, the first device may also be a tag reader (Reader), but of course, it may not be a tag reader (Reader). As shown in Figure 1, the sending method includes:

[0126] Step 11: Receive or obtain first information from a tag, where the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number.

[0127] In some embodiments of the present disclosure, the first device may be a tag reader, in which case the first device may be a terminal (UE) or a RAN. In other embodiments of the present disclosure, the first device may not be a tag reader, in which case the first device may be a terminal, a RAN, or a core network function (such as an AMF or other 5GC NF).

[0128] Here, the tag reports the first information to the tag reader. If the first device is a tag reader, the first device can directly receive or obtain the first information sent by the tag. If the first device is not a tag reader, the tag reader receives the first information reported by the tag and forwards it to the first device. In this case, the first device can receive or obtain the first information forwarded from the tag by the tag reader.

[0129] Step 12, determine or obtain second information, the second information including at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number.

[0130] Here, the first device determines whether the first information received or acquired from each tag meets a predetermined condition. If so, the first information is used as the second information.

[0131] Here, that the carried tag identifier belongs to the first tag list may also mean that: the carried tag identifier is in the first tag list.

[0132] The carried tag identifier belongs to the first tag identifier list or the carried tag identifier is in the first tag identifier list.

[0133] The carried tag identifier belonging to the first tag may also mean: the carried tag identifier is the identifier of the first tag.

[0134] The carried tag identifier belongs to the first tag identifier and may also mean: the carried tag identifier is the first tag identifier.

[0135] The carried tag identifier belongs to the first tag group or may also mean that the carried tag identifier is in the first tag group.

[0136] The carried tag identifier belongs to the first tag identifier group or may also mean that the carried tag identifier is in the first tag identifier group.

[0137] Step 13: Aggregate at least one of the second information and send it to the first AF.

[0138] Here, the first device may send the aggregated at least one second information to the first AF via a radio access network (RAN) and / or core network function. For example, the first device may aggregate the at least one second information to obtain aggregated information, and then send the aggregated information to the first AF. In this case, the first AF may receive or obtain the aggregated information sent by the first device via the RAN and / or core network function.

[0139] For example, in some embodiments of the present disclosure, the first device is a RAN. In this case, the RAN may send the aggregated information to the first AF through a core network function (including but not limited to an AMF, NEF, or other 5GC NF). In this case, the first AF receives or obtains the aggregated information sent by the first device through the core network function.

[0140] For another example, in some other embodiments of the present disclosure, the first device is a terminal. In this case, the terminal may send the aggregate information to the first AF through the user plane. In this case, the first AF receives or obtains the aggregate information sent by the terminal through the user plane.

[0141] In addition, in the embodiment of the present disclosure, when the first device aggregates at least one second information and sends it to the first AF, it also carries the first transaction sequence number.

[0142] Through the above steps, the embodiment of the present disclosure aggregates the information reported by the tag by the first device and then sends it to the first AF. Compared with the implementation method of sending the reporting information of each tag to the first AF separately, the embodiment of the present disclosure can reduce the consumption of network resources and reduce the possibility of signaling storms, thereby improving network security and reliability.

[0143] In some embodiments of the present disclosure, the first device may perform the action of aggregating at least one second information and sending it to the first AF in step 13 above when at least one of the following conditions is met:

[0144] (1) The duration of the business operation reaches the timeout period of the business operation.

[0145] Here, after a service operation triggering a tag, the first device may time the service operation duration. When the service operation timeout period is reached, the first device may aggregate the second information received or acquired and send it to the first AF. The service operation timeout period may be locally set or configured by the first device, or may be sent to the first device by the first AF.

[0146] (2) Receive or obtain the second information reported by the first number of tags.

[0147] Here, the first device may count the number of tags reporting the second information, and when the number reaches the first number, aggregate the received second information and send it to the first AF. Similarly, the first number may be locally set or configured by the first device, or sent by the first AF to the first device.

[0148] (3) The number of the second information reaches the maximum aggregation number.

[0149] Here, the first device may count the amount of second information received or acquired, and when the amount reaches the maximum aggregation amount, aggregate the received or acquired second information and send it to the first AF. Similarly, the maximum aggregation amount may be locally set or configured by the first device, or may be sent to the first device by the first AF.

[0150] Prior to step 11 above, the first device may obtain the third information, wherein the third information includes at least one of the following: the first tag list, the first tag identifier list, the first tag, the first tag identifier, the first tag group, the first tag identifier group, the first transaction sequence number, the timeout period of the business operation, the first quantity, and the maximum aggregate quantity. In this way, the first device may determine the second information based on the first tag, the first tag list, the first tag group, the first transaction sequence number, and other information indicated in the third information; and determine whether to aggregate at least one of the second information and send it to the first AF based on the timeout period of the business operation, the first quantity, the maximum aggregate quantity, and other information indicated in the third information.

[0151] There are many ways to obtain the third information, for example, including at least one of the following ways:

[0152] (1) The first device receives or obtains a service operation message sent by the first AF, where the service operation message includes the third information. In this way, the first device can obtain the third information from the service operation message.

[0153] (2) The first device assigns the first transaction sequence number to the business operation.

[0154] (3) The first device locally configures or sets the timeout period of the service operation.

[0155] (4) The first device locally configures or sets the first quantity.

[0156] (5) The first device locally configures or sets the maximum aggregation number.

[0157] (6) The first device receives or obtains the first transaction sequence number sent by the second device.

[0158] In the above method 2, after the first device assigns the first transaction sequence number to the business operation, the first device may also forward the business operation message carrying the first transaction sequence number to the corresponding tag, thereby notifying the tag of the first transaction sequence number. When the tag subsequently reports the first information, the first information may include the first transaction sequence number. In this way, the first information received or obtained by the first device can carry the transaction sequence number of the business operation, and the second information can be determined from the first information based on the transaction sequence number.

[0159] In the above methods 3 to 5, when the first device locally configures or sets the timeout duration, the first quantity, and the maximum aggregation quantity of the service operation, it can directly obtain the relevant third information based on the result of the local configuration or setting. The first device can also receive or obtain the first transaction sequence number sent by the second device. In this case, the first transaction sequence number can be the transaction sequence number assigned by the second device to the service operation. The second device can specifically be a terminal, RAN, or core network function (such as AMF, NEF or other 5GC NF).

[0160] In some embodiments of the present disclosure, the first AF sends a service operation message to the first device, where the service operation message includes the third information. The first device can obtain the third information from the service operation message. In addition, if the first device is a tag reader, the service operation message can be directly forwarded to the corresponding tag (e.g., the tag on which the service operation is to be performed); if the first device is not a tag reader, the first device forwards the service operation message to the corresponding tag via the tag reader.

[0161] For example, when the first device is a RAN or a terminal and the first device is a tag reader, the first device receives or obtains a service operation message sent by the first AF, where the service operation message is used to trigger a related tag to perform a corresponding service operation and carries the third information. In this case, the first device directly sends the service operation message to the corresponding tag to trigger the tag to perform the service operation.

[0162] For another example, when the first device is a RAN and is not a tag reader, but a terminal is a tag reader, the first device receives or obtains a service operation message sent by the first AF. The service operation message is used to trigger the relevant tag to perform the corresponding service operation and carries the third information. In this case, the first device sends the service operation message to the terminal, which then forwards it to the corresponding tag to trigger the tag to perform the service operation.

[0163] In some embodiments of the present disclosure, the first device is a terminal. In this case, the first device also receives or obtains the service operation message sent by the first AF and carrying the IP address of the first AF. In this way, the first device can obtain the IP address of the first AF. In this way, in step 13 above, the first device can aggregate at least one piece of the second information into aggregated information, and then send the aggregated information to the first AF via the user plane based on the IP address of the first AF.

[0164] Referring to FIG. 2 , the method for receiving data provided by an embodiment of the present disclosure, when applied to a first AF side, includes the following steps:

[0165] Step 21, receive or obtain aggregate information sent by the first device, the aggregate information includes at least one second information, the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number.

[0166] As described above, the first device aggregates at least one second information into aggregated information and sends it to the first AF. The first AF receives or obtains the aggregated information. The second information is at least one of the following first information, for example, first information carrying a tag identifier belonging to a first tag or a first tag list, first information carrying a tag identifier belonging to a first tag group, and first information carrying a transaction sequence number that is a first transaction sequence number. The first information is the reported information reported by the tag to the first device.

[0167] Here, the first AF may be receiving or obtaining the aggregate information sent by the first device and forwarded via the RAN and / or core network function. For example, when the first device is the RAN, the first device forwards the aggregate information to the first AF via the core network function (including but not limited to AMF, NEF or other 5GC NF). At this time, the first AF receives or obtains the aggregate information forwarded by the first device via the core network function. For another example, when the first device is a terminal, the first device forwards the aggregate information to the first AF via the RAN and core network function (including but not limited to AMF, NEF or other 5GC NF). At this time, the first AF receives or obtains the aggregate information forwarded by the first device via the RAN and core network function.

[0168] Step 22: Obtain at least one first information according to the aggregated information.

[0169] Here, the first AF may parse the aggregate information to obtain the at least one second information.

[0170] Through the above steps, the embodiment of the present disclosure realizes the reception of aggregated tag reporting information, reduces the consumption of network resources for the transmission of tag reporting information, reduces the possibility of signaling storms, and thus improves network security and reliability.

[0171] In some embodiments, the aggregate information may further carry the first transaction sequence number, so that the first AF can determine the service operation corresponding to the second information based on the first transaction sequence number.

[0172] Before the above step 21, the first AF may also send a service operation message to the tag reader, and the service operation message includes at least one of the following information: the first tag list, the first tag identifier list, the first tag, the first tag identifier, the first tag group, the first transaction sequence number, the timeout duration of the service operation, the first number used to indicate the maximum number of tags, the maximum aggregation number, and the maximum aggregation number is the maximum number of second information that can be aggregated by the aggregation information. The tag reader may be the first device or may not be the first device. In addition, when the tag reader is a terminal, the first AF may send the service operation message to the core network function (such as 5GC NF), and encapsulate it into a NAS message via the core network function and send it to the tag reader.

[0173] In the embodiment of the present disclosure, the first AF may also assign a first transaction sequence number to the service operation before sending the service operation message. Of course, the first transaction sequence number may also be assigned by other devices or network functions in the tag service triggering path.

[0174] In addition, when the first device is a terminal, the first AF may also include its own IP address in the service operation message and send it to the tag reader. Thus, in step 21 above, the first device may send the aggregated information to the first AF via the user plane based on the IP address of the first AF. The first AF then receives or obtains the aggregated information sent by the first device via the user plane. In other words, the aggregated information is sent from the first device to the first AF via the user plane. More specifically, the aggregated information is sent from the first device to the first AF via the user plane based on the IP address of the first AF.

[0175] Figure 3 is a flow chart of the method for receiving linked data provided by an embodiment of the present disclosure when it is applied to the second device side. The second device is a device that assigns transaction numbers to service operations, and specifically may be a device or network function other than the tag and AF in the tag service triggering path or the aggregate information reporting path mentioned above. The second device and the first device mentioned above may also be the same device or network function, or different devices or different network functions. For example, the second device may be a terminal (UE), RAN, a core network function, such as NEF, AMF or other 5GC NF. In addition, the second device may also be a tag reader (Reader), but of course, it may not be a tag reader (Reader). As shown in Figure 3, the method includes:

[0176] Step 31: Receive or obtain a service operation message sent by the first AF.

[0177] Here, the business operation message is a message that triggers a related tag to perform a business operation.

[0178] Step 32, assigning a first transaction sequence number to the business operation;

[0179] Here, the second device allocates a first transaction sequence number for the business operation, where the first transaction sequence number is used to uniquely identify the business operation, and may be in the form of a number, an ID (such as a Transaction ID), a sequence number (SN), or the like.

[0180] Step 33: Forward the service operation message carrying the first transaction sequence number to the tag.

[0181] Here, the second device forwards the service operation message carrying the first transaction sequence number to the tag, thereby notifying the tag of the first transaction sequence number.

[0182] Through the above steps, the embodiment of the present disclosure implements the allocation of transaction sequence numbers. In this way, the first transaction sequence number can be carried when the subsequent tag reports information, so that the relevant reporting information can be aggregated according to the first transaction sequence number and then sent to the first AF, thereby reducing the transmission resources required for tag information reporting.

[0183] The above describes the relevant methods of the embodiments of the present disclosure from the perspectives of the first device, the first AF, and the second device. The following further describes the interaction process between devices and functions using several examples from the 5G core network. The following examples enhance the existing 5GC architecture to implement data aggregation and data transmission solutions based on the control plane and user plane, as well as the related processes. Specifically, on the reader side, transaction IDs are allocated, and data is aggregated and sent.

[0184] Example 1: RAN acts as both a tag reader and a data aggregation point

[0185] Example 1 is shown in Figure 4 , where the RAN acts as a tag reader, the AF or RAN assigns transaction numbers (e.g., Transaction IDs), and three paths are described: AMF / other 5GC NF / AMF+other 5GC NF. The RAN is the data aggregation point, corresponding to the first device in the previous embodiment. Figure 4 includes two processes, Process A and Process B.

[0186] In process A, the AF assigns the Transaction ID, and the RAN acts as both a tag reader and a data aggregation point. Process A shown in Figure 4 specifically includes:

[0187] Step 41. The AF assigns a transaction ID, assuming it is the first transaction ID, and triggers a business operation process, such as inventory / Read Data / Write Data / Disable Device operations. This operation may carry at least one of the following information: the first transaction ID, the first tag ID, the first tag group ID, the timeout period for the business operation, the first quantity (maximum number of tags), and the maximum number of aggregates (the maximum number of second information that can be aggregated). The meanings of the above operations are explained as follows:

[0188] -Inventory: to discover the AIoT device(s) in a specific area.

[0189] -Read Data: Read application data from the memory of an AIoT Device.

[0190] -Write Data: Write application data to the memory of the AIoT Device.

[0191] -Disable Device: Disable the capability of an AIoT Device to transmit RF signals.

[0192] Step 42. The service operation message is delivered to the RAN through the NEF, other 5GC NFs, AMF, and other 5GC NFs, carrying the first transaction ID, the first tag ID, the first tag group ID, the timeout period of the service operation, the first quantity, and the maximum aggregation quantity; the RAN initiates a service operation on the tag, carrying one or more of the first transaction ID, the first tag ID, and the first tag group ID.

[0193] Step 43. The tag determines whether to return service operation information based on the first tag ID or the first tag group ID; if the conditions are met, the tag returns the service operation information to the RAN, carrying the first Transaction ID and / or the first tag ID.

[0194] Step 44. The RAN waits for the tag to return information based on the service operation timeout (which can be locally configured by the RAN or issued by the AF in step 41), the first number (which can be locally configured by the RAN or issued by the AF in step 41), and the maximum aggregation number. If the service operation duration reaches the service operation timeout, or if the first number of second information reported by the tags is received / obtained, or if the number of second information reaches the maximum aggregation number, the RAN aggregates the second information into a service operation response message containing multiple tags based on at least one of the first transaction ID, the first tag ID, and the first tag group ID.

[0195] Step 45. RAN returns the service operation response message carrying the first Transaction ID to AF through NEF, other 5GC NFs, AMF and other 5GC NFs.

[0196] In process B shown in Figure 4, the Transaction ID is assigned by the RAN, which acts as both a tag reader and a data aggregation point. Process B specifically includes:

[0197] Step 51. AF triggers the business operation process, such as

[0198] Operations such as inventory / Read Data / Write Data / Disable Device can carry at least one of the following information: first tag ID, first tag group ID, timeout period of the service operation, first quantity (maximum number of tags), maximum number of aggregates (the maximum number of second information that can be aggregated). Through 5GC NFs such as NEF, other 5GCNFs, and AMF, the service operation message is delivered to RAN, carrying the first tag ID, first tag group ID, timeout period of the service operation, first quantity, and maximum number of aggregates. The meanings of the above operations are explained as follows:

[0199] -Inventory: to discover the AIoT device(s) in a specific area.

[0200] -Read Data: Read application data from the memory of an AIoT Device.

[0201] -Write Data: Write application data to the memory of the AIoT Device.

[0202] -Disable Device: Disable the capability of an AIoT Device to transmit RF signals.

[0203] Step 52: RAN allocates a Transaction ID based on the service operation message, assuming it is the first Transaction ID.

[0204] Step 53: The RAN initiates a service operation on the tag, carrying at least one of the first transaction ID, the first tag ID, and the first tag group ID.

[0205] Step 54. The tag determines whether it needs to return business operation information based on the first tag ID or the first tag group ID; if the conditions are met, the tag returns the business operation information, carrying the first Transaction ID and / or the first tag ID.

[0206] Step 55. The RAN waits for the tag to return information based on the service operation timeout (which can be locally configured by the RAN or issued by the AF in step 51), the first quantity (which can be locally configured by the RAN or issued by the AF in step 51), and the maximum aggregation quantity. If the service operation duration reaches the service operation timeout, or if the first quantity of second information reported by the tags is received / acquired, or if the quantity of the second information reaches the maximum aggregation quantity, the RAN aggregates the second information into a service operation response message containing multiple tags based on at least one of the first transaction ID, the first tag ID, and the first tag group ID.

[0207] Step 56. RAN returns the service operation response message to AF through NEF, other 5GC NFs, AMF and other 5GC NFs.

[0208] Example 2:

[0209] Example 2 is shown in Figure 5, in which the UE is used as a tag reader and data aggregation point, and the AF or UE allocates transaction numbers (such as Transaction IDs) through three paths: AMF / other 5GC NF / AMF+other 5GC NF. In this example, the UE is a data aggregation point, corresponding to the first device in the above embodiment, and the UE also serves as a tag reader. Figure 5 includes two processes, namely process C and process D. Among them, process C includes steps 61 to 65a, and process D includes steps 71 to 76a.

[0210] Compared to the case where the RAN is a tag reader as shown in FIG4 , the process where the UE is a reader mainly includes the following relevant steps (refer to the underlined steps in FIG5 ):

[0211] In step 72, the UE allocates a first Transaction ID;

[0212] In step 64 or step 75, the UE aggregates the data reported by the tag;

[0213] Step 62a: The AF encapsulates the first Transaction ID and other information in a downlink NAS message and sends it to the UE through the AMF or other 5GC NF.

[0214] In step 65a or step 76a, when the UE reports data, it can be through the control plane or the user plane. If it is through the user plane, the AF needs to notify the UE of the AF's IP address in step 62 or step 71.

[0215] Example 3: AMF as a data aggregation point and RAN as a tag reader

[0216] Example 2 is shown in Figure 6 , where the RAN serves as the tag reader and the AMF serves as the data aggregation point, with the AF or RAN allocating transaction numbers (e.g., Transaction IDs) for illustration. In this example, the AMF serves as the data aggregation point, corresponding to the first device in the above embodiment. Figure 6 includes two processes, Process E and Process F. Process E includes steps 81-85, and Process F includes steps 91-96. In Process E, the RAN is the device that allocates the Transaction ID, corresponding to the second device in the above embodiment.

[0217] Compared to the case where the RAN is the aggregation point as shown in Figure 4, the process in Figure 6 with the AMF as the aggregation point has the following differences (refer to the relevant steps marked with underlines in Figure 6):

[0218] In step 82, the AMF needs to store information such as the first tag ID and the first tag group ID.

[0219] In step 84 or step 95, when AMF aggregates data, it can further parse the tag ID and tag group ID to perform further screening and select the tag data that meets the conditions for reporting.

[0220] As can be seen from the above examples, the data aggregation point (i.e., the first device in the above embodiments) in the embodiments of the present disclosure can be the RAN, AMF, or other 5GC NF. NEF, AMF, and other 5GC NFs can all allocate transaction IDs; in addition, the transaction ID is optional in messages such as service operations.

[0221] Through the above examples, this disclosure enhances the existing 5GC architecture, implementing data aggregation and data transmission solutions based on the control and user planes and related processes. This disclosure is conducive to guiding technological innovations such as passive IoT, and avoiding events such as signaling storms caused by a large number of tag response messages.

[0222] The above describes various methods of the embodiments of the present disclosure. The following further provides apparatuses for implementing the above methods.

[0223] Please refer to Figure 7. The embodiment of the present disclosure further provides a first device 700, which is a device that aggregates and transmits information reported by multiple tags. Specifically, the first device can be a device or network function other than the tag and AF in the above-mentioned tag service trigger path or aggregate information reporting path. For example, the first device can be a terminal (UE), RAN, or core network function. As shown in Figure 7, the first device 700 includes: a transceiver 701 and a processor 702;

[0224] The transceiver 701 is configured to receive or obtain first information from a tag, where the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number;

[0225] The processor 702 is configured to determine or obtain second information, where the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number;

[0226] The transceiver 701 is further configured to aggregate at least one piece of the second information and send the aggregated information to the first AF.

[0227] In some embodiments, the transceiver is further configured to carry the first transaction sequence number when aggregating and sending at least one second information to the first AF.

[0228] In some embodiments, the transceiver is further configured to send the aggregated at least one second information to the first AF via a radio access network and / or core network function.

[0229] In some embodiments, the transceiver is further configured to perform the step of aggregating and sending the at least one second information to the first AF when at least one of the following conditions is met:

[0230] The duration of the business operation reaches the timeout period;

[0231] Receiving or acquiring the second information reported by the first number of tags;

[0232] The amount of the second information reaches the maximum aggregation amount.

[0233] In some embodiments, the processor is further used to obtain third information, and the third information includes at least one of the following: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first tag identification group, the first transaction sequence number, the timeout duration of the business operation, the first quantity, and the maximum aggregation quantity.

[0234] In some embodiments, obtaining the third information includes at least one of the following:

[0235] The first device receives or obtains a service operation message sent by the first AF, where the service operation message includes the third information;

[0236] The first device assigns the first transaction sequence number to the business operation;

[0237] The first device locally configures or sets a timeout period for the service operation;

[0238] The first device locally configures or sets the first quantity;

[0239] The first device locally configures or sets the maximum aggregation quantity;

[0240] The first device receives or obtains the first transaction sequence number sent by the second device.

[0241] In some embodiments, the transceiver is further used to directly forward the service operation message to the corresponding tag when the first device is a tag reader; when the first device is not a tag reader, forward the service operation message to the corresponding tag through the tag reader.

[0242] In some embodiments, the transceiver is further configured to, after the first device assigns the first transaction sequence number to the service operation, forward the service operation message carrying the first transaction sequence number to the corresponding tag.

[0243] In some embodiments, the receiving or obtaining the first information from the tag includes at least one of the following:

[0244] When the first device is a tag reader, the first device directly receives or obtains the first information sent by the tag;

[0245] When the first device is not a tag reader, the first device receives or obtains the first information from the tag forwarded by the tag reader.

[0246] In some embodiments, when the first device is a tag reader, the first device is a terminal or a RAN; when the first device is not a tag reader, the first device is a terminal, a RAN, or a core network function.

[0247] It should be noted that the device in this embodiment corresponds to the method applied to the first device described above, and the implementation methods in the above embodiments are all applicable to the embodiments of this device and can achieve the same technical effects. The above-mentioned device provided in the embodiments of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiments and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those in the method embodiments will not be described in detail here.

[0248] Referring to FIG8 , an embodiment of the present disclosure further provides a first AF 800 , comprising: a transceiver 801 and a processor 802 ;

[0249] The transceiver 801 is configured to receive or obtain aggregate information sent by the first device, where the aggregate information includes at least one second information, where the second information includes at least one of the following first information: a carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, a carried tag identifier belongs to a first tag group or a first tag identifier group, and a carried transaction sequence number is a first transaction sequence number;

[0250] The processor 802 is configured to obtain at least one second information according to the aggregated information.

[0251] In some embodiments, the aggregate information also carries the first transaction sequence number.

[0252] In some embodiments, the transceiver is further configured to receive or obtain the aggregated information sent by the first device and forwarded via a radio access network RAN ​​and / or a core network function.

[0253] In some embodiments, the transceiver is also used to send a business operation message to the tag reader, and the business operation message includes at least one of the following information: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first transaction sequence number, the timeout period of the business operation, the first number used to indicate the maximum number of tags, and the maximum aggregation number, where the maximum aggregation number is the maximum number of second information that can be aggregated by the aggregated information.

[0254] In some embodiments, the transceiver is further configured to, when the tag reader is a terminal, send the service operation message to a core network function, and encapsulate the service operation message into a NAS message via the core network function and send the message to the tag reader.

[0255] In some embodiments, the transceiver is further used to carry its own IP address in the service operation message and send it to the tag reader when the first device is a terminal; wherein the aggregate information is sent by the first device to the first AF through the user plane based on the IP address of the first AF.

[0256] In some embodiments, the processor is further configured to assign the first transaction sequence number to the business operation.

[0257] It should be noted that the device in this embodiment corresponds to the method applied to the first AF described above. The implementation methods in the above embodiments are all applicable to the embodiments of this device and can achieve the same technical effects. The above-mentioned device provided in the embodiments of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiments and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those in the method embodiments will not be detailed here.

[0258] Referring to FIG9 , an embodiment of the present disclosure further provides a second device 900 , including: a transceiver 901 and a processor 902 ;

[0259] The transceiver 901 is configured to receive or obtain a service operation message sent by the first AF;

[0260] The processor 902 is further configured to assign a first transaction sequence number to the business operation;

[0261] The transceiver 901 is further configured to forward the service operation message carrying the first transaction sequence number to the tag.

[0262] In some embodiments, the transceiver is further configured to:

[0263] When the second device is a tag reader, directly forwarding the service operation message carrying the first transaction sequence number to the tag;

[0264] When the second device is not a tag reader, the service operation message carrying the first transaction sequence number is forwarded to the tag through the tag reader.

[0265] In some embodiments, the second device is a terminal, a RAN, or a core network function.

[0266] It should be noted that the device in this embodiment corresponds to the method applied to the second device, and the implementation methods in the above embodiments are all applicable to the embodiments of this device and can achieve the same technical effects. The above-mentioned device provided in the embodiment of the present disclosure can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0267] Please refer to Figure 10. The embodiment of the present disclosure also provides a first device 1000, including a processor 1001, a memory 1002, and a computer program stored in the memory 1002 and executable on the processor 1001. When the computer program is executed by the processor 1001, the various processes of the embodiment of the method for sending IoT data executed by the first device are implemented, and the same technical effects can be achieved. To avoid repetition, they will not be described here.

[0268] Please refer to Figure 11. The embodiment of the present disclosure also provides a first AF 1100, including a processor 1101, a memory 1102, and a computer program stored in the memory 1102 and executable on the processor 1101. When the computer program is executed by the processor 1101, the various processes of the embodiment of the method for receiving IoT data executed by the first device are implemented, and the same technical effect can be achieved. To avoid repetition, they will not be described here.

[0269] Please refer to Figure 12. The embodiment of the present disclosure also provides a second device 1200, including a processor 1201, a memory 1202, and a computer program stored in the memory 1202 and executable on the processor 1201. When the computer program is executed by the processor 1201, the various processes of the above-mentioned serial number allocation method embodiment executed by the second device are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0270] The present disclosure also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process of each embodiment of the above-mentioned method for sending, receiving, and serial number allocation methods of IoT data is implemented, and the same technical effect is achieved. To avoid repetition, the details are not described here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0271] The embodiments of the present disclosure also provide a computer program product, including computer instructions. When the computer instructions are executed by a processor, the various processes of the above-mentioned embodiments of the method for sending IoT data, the method for receiving IoT data, and the method for allocating serial numbers are implemented, and the same technical effects can be achieved. To avoid repetition, they will not be described here.

[0272] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0273] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the relevant technology, can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0274] The embodiments of the present disclosure are described above in conjunction with the accompanying drawings, but the present disclosure is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present disclosure, ordinary technicians in this field can also make many forms without departing from the scope of protection of the purpose of the present disclosure and the claims, all of which are protected by the present disclosure.

Claims

1. A method for transmitting IoT data, applied to a first device, the method comprising: Receive or obtain first information from a tag, where the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number; Determine or obtain second information, where the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number; Aggregate at least one of the second information and send it to the first application function AF.

2. The method according to claim 1, wherein When at least one second information is aggregated and sent to the first AF, the first transaction sequence number is also carried.

3. The method according to claim 1, wherein Aggregating at least one piece of the second information and sending the aggregating piece of information to the first AF includes: The first device sends the aggregated at least one second information to the first AF through a radio access network and / or a core network function.

4. The method according to claim 1, further comprising: The first device performs the step of aggregating at least one second information and sending the aggregating information to the first AF when at least one of the following conditions is met: The duration of the business operation reaches the timeout period; Receiving or acquiring the second information reported by the first number of tags; The amount of the second information reaches the maximum aggregation amount.

5. The method according to claim 4, further comprising: The first device obtains third information, and the third information includes at least one of the following: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first tag identification group, the first transaction sequence number, the timeout duration of the business operation, the first quantity, and the maximum aggregation quantity.

6. The method according to claim 5, wherein: Obtaining third information, including at least one of the following: The first device receives or obtains a service operation message sent by the first AF, where the service operation message includes the third information; The first device assigns the first transaction sequence number to the business operation; The first device locally configures or sets a timeout period for the service operation; The first device locally configures or sets the first quantity; The first device locally configures or sets the maximum aggregation quantity; The first device receives or obtains the first transaction sequence number sent by the second device.

7. The method according to claim 6, further comprising: When the first device is a tag reader, the first device directly forwards the service operation message to the corresponding tag; When the first device is not a tag reader, the first device forwards the service operation message to the corresponding tag through the tag reader.

8. The method according to claim 7, wherein: After the first device allocates the first transaction sequence number to the service operation, the first device further forwards the service operation message carrying the first transaction sequence number to the corresponding label.

9. The method according to any one of claims 1 to 8, wherein: Receiving or obtaining first information from a tag, including at least one of the following: When the first device is a tag reader, the first device directly receives or obtains the first information sent by the tag; When the first device is not a tag reader, the first device receives or obtains the first information from the tag forwarded by the tag reader.

10. The method according to claim 9, wherein: When the first device is a tag reader, the first device is a terminal or a radio access network RAN; When the first device is not a tag reader, the first device is a terminal, a RAN or a core network function.

11. A method for receiving IoT data, applied to a first AF, the method comprising: Receiving or obtaining aggregate information sent by the first device, the aggregate information including at least one second information, the second information including at least one of the following first information: a carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, a carried tag identifier belongs to a first tag group or a first tag identifier group, and a carried transaction sequence number is a first transaction sequence number; At least one second information is obtained according to the aggregated information.

12. The method according to claim 11, wherein The aggregation information also carries the first transaction sequence number.

13. The method according to claim 11, wherein Receiving or obtaining aggregated information sent by the first device includes: The first AF receives or obtains the aggregated information sent by the first device and forwarded via a radio access network RAN and / or a core network function.

14. The method according to claim 11, further comprising: The first AF sends a business operation message to the tag reader, and the business operation message includes at least one of the following information: the first tag list, the first tag identification list, the first tag, the first tag identification, the first tag group, the first transaction sequence number, the timeout duration of the business operation, the first number used to indicate the maximum number of tags, and the maximum aggregation number, where the maximum aggregation number is the maximum number of second information that can be aggregated by the aggregated information.

15. The method according to claim 14, wherein When the tag reader is a terminal, it further includes: The first AF sends the service operation message to the core network function, and the core network function encapsulates the service operation message into a NAS message and sends the message to the tag reader.

16. The method according to claim 14, wherein When the first device is a terminal, it also includes: the first AF carries its own IP address in the service operation message and sends it to the tag reader; wherein the aggregation information is sent to the first AF by the first device through the user plane according to the IP address of the first AF.

17. The method according to claim 14, further comprising: The first AF allocates the first transaction sequence number to the business operation.

18. A method for allocating a sequence number, applied to a second device, the method comprising: Receive or obtain a service operation message sent by the first AF; Assigning a first transaction sequence number to the business operation; Forward the service operation message carrying the first transaction sequence number to the tag.

19. The method according to claim 18, wherein Forwarding the service operation message carrying the first transaction sequence number to the label includes: When the second device is a tag reader, directly forwarding the service operation message carrying the first transaction sequence number to the tag; When the second device is not a tag reader, the service operation message carrying the first transaction sequence number is forwarded to the tag through the tag reader.

20. The method according to claim 18, wherein The second device is a terminal, a RAN, or a core network function.

21. A first device comprising a transceiver and a processor, wherein: The transceiver is configured to receive or obtain first information from a tag, wherein the first information carries at least one of the following information: a tag identifier, a tag group identifier, and a transaction sequence number; The processor is configured to determine or obtain second information, where the second information includes at least one of the following first information: the carried tag identifier belongs to the first tag list or the first tag identifier list or the first tag or the first tag identifier, the carried tag identifier belongs to the first tag group or the first tag identifier group, and the carried transaction sequence number is the first transaction sequence number; The transceiver is further configured to aggregate at least one piece of the second information and send the aggregated information to the first AF.

22. A first device, comprising: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 1 to 10 are implemented.

23. A first AF comprising a transceiver and a processor, wherein: The transceiver is configured to receive or obtain aggregate information sent by the first device, the aggregate information including at least one second information, the second information including at least one of the following first information: a carried tag identifier belongs to a first tag list or a first tag identifier list or a first tag or a first tag identifier, a carried tag identifier belongs to a first tag group or a first tag identifier group, and a carried transaction sequence number is a first transaction sequence number; The processor is configured to obtain at least one second information according to the aggregated information.

24. A first AF, comprising: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 11 to 17 are implemented.

25. A second device comprising a transceiver and a processor, wherein: The transceiver is configured to receive or obtain a service operation message sent by the first AF; The processor is further configured to assign a first transaction sequence number to the business operation; The transceiver is further configured to forward the service operation message carrying the first transaction sequence number to the tag.

26. A second device comprising: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the method according to any one of claims 18 to 20 are implemented.

27. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 6, or implements the steps of the method according to any one of claims 7 to 12.

28. A computer program product comprising computer instructions, wherein when the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented, or the steps of the method according to any one of claims 11 to 17 are implemented, or the steps of the method according to any one of claims 18 to 20 are implemented.

Images