Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The method comprises the steps that first information is received, the first information comprises a first identifier, the first identifier corresponds to M tags, and the first information indicates that first operation is executed for the first identifier; m > = 2, and M is an integer. Second information is sent to M1 labels in the M labels, the second information indicates that the first operation is executed on the M1 labels, M1 is smaller than or equal to M, and M1 is an integer. Receiving third information from each label in the N labels, wherein the third information indicates that the first operation is successfully executed on the labels; the N tags belong to M1 tags, N is smaller than or equal to M1, and N is an integer. And sending fourth information, wherein the fourth information indicates that the first operation is successfully executed for the first identifier. In this way, the devices can be prevented from frequently interacting and indicating instructions for executing the first operation for each label in the M labels through the mode that the devices interact and indicate the instructions for executing the first operation for the first identification.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a communication method and a communication device. Background Art

[0002] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) has defined the ambient internet of things (AIoT) technology. In AIoT technology and other related technologies, the communication system can include readers and tags, and tags can be IoT terminals, such as passive / semi-passive / active tags. AIoT technology is mainly used to implement the following services: inventory, positioning, sensing, command, etc.; typical application scenarios of AIoT technology include logistics, warehousing, industrial manufacturing, identity recognition, environmental monitoring, etc.

[0003] With the development of technology and environmental protection requirements, the Internet of Things will have a larger scale of application deployment prospects, and it is predicted that it will cover hundreds of billions of devices in the future. Based on this, the number of tags in the network will increase. If the reader and each tag perform one or more of the processes of reading, writing, inventorying or disabling, and at the same time require the tag to respond to the reader's operation request immediately, it will lead to too much signaling interaction on the network side. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a communication method and a communication device, etc., which define identifiers corresponding to multiple tags, and when the read, write, inventory or disable process is triggered on the network side, multiple tags are indexed by the newly defined identifiers, thereby helping to reduce signaling interactions on the network side.

[0005] In a first aspect, a communication method is provided, which can be performed by a first device, and the first device can be replaced by a tag management function entity or a component of the tag management function entity (such as a chip or a chip system or a circuit or a communication module). For ease of understanding, the following description is taken as an example of the execution of the first device. At this time, the first device can also be called a communication device.

[0006] Exemplarily, the method comprises:

[0007] Receive first information, the first information includes a first identifier, the first identifier corresponds to M tags, and the first information indicates to perform a first operation on the first identifier; M≥2, M is an integer;

[0008] Sending second information to M1 tags among the M tags, where the second information indicates that the first operation is performed on the M1 tags, where M1≤M, and M1 is an integer;

[0009] Receiving third information from each of the N tags, the third information indicating that the first operation on the tag is successfully performed; the N tags belong to M1 tags, N≤M1, and N is an integer;

[0010] The fourth information is sent, where the fourth information indicates that the first operation is successfully performed on the first identifier.

[0011] Based on the above technical solution, by corresponding M tags to a first identifier, each device can interactively indicate instructions to perform the first operation on the M tags, thereby achieving the purpose of performing the first operation on the M tags, thereby avoiding frequent interactive instructions between each device to perform the first operation on each of the M tags.

[0012] Exemplarily, M tags correspond to a first terminal; or, M tags correspond to P terminals, and any two of the M tags are of the same type, and P is an integer greater than 1.

[0013] Herein, the first terminal refers to a terminal.

[0014] Exemplarily, the first identification is determined based on identification of one or more tags among the M tags, where the identification of the tag includes one or more of the following: a tag identification, an electronic product code, or a user identification.

[0015] Exemplarily, the first identifier corresponds to M tags which are predefined.

[0016] In combination with the first aspect, in some implementations of the first aspect, sending the fourth information includes:

[0017] If the quantity of the third information meets the first condition, the fourth information is sent.

[0018] Among them, the first condition includes one or more of the following: the amount of third information is not less than the first threshold; the ratio between the amount of third information and M is not less than the second threshold; the amount of third information is equal to M; the ratio between the number of third information received in the first time period and M is not less than the third threshold.

[0019] Based on the above technical solution, enterprises or operators can define different first conditions for different needs, and then reduce the signaling interaction process required to perform the first operation as much as possible while meeting the needs of performing the first operation. For example, in the scenario of warehouse inventory, if multiple tags on a terminal (or an object) are mapped to an identifier, it can be determined that the first condition includes the above first item, thereby reducing the signaling interaction required for inventory. For another example, in the positioning scenario, it can be determined that the first condition includes the above second item, thereby ensuring the accuracy of positioning.

[0020] In combination with the first aspect, in some implementations of the first aspect, the first information further indicates a first condition.

[0021] In combination with the first aspect, in some implementations of the first aspect, before sending the second information, the method further includes:

[0022] Sending fifth information, where the fifth information includes the first identifier, and the fifth information is used to request first tag information of M tags, where the first tag information of any one of the M tags is used to determine the tag;

[0023] Sixth information is received, where the sixth information includes first tag information of the M tags.

[0024] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, so that the M tags can be determined according to the first tag information of the M tags, which is beneficial for the first device to send instructions to perform the first operation to the M tags.

[0025] In combination with the first aspect, in some implementations of the first aspect, before sending the second information, the method further includes:

[0026] Sending fifth information, where the fifth information includes the first identifier, and the fifth information is used to request a correspondence between the first identifier and the M tags;

[0027] receiving sixth information, where the sixth information includes a correspondence between the M tags and the first identifier;

[0028] M labels are determined according to the corresponding relationships.

[0029] Based on the above technical solution, the first device can obtain the correspondence between the first identifier and the M tags, and thus can determine the M tags according to the correspondence, which is beneficial for the first device to send instructions to perform the first operation to the M tags.

[0030] In combination with the first aspect, in some implementations of the first aspect, before receiving the first information, the method further includes:

[0031] Receive the seventh message;

[0032] The seventh information includes the first identifier and first tag information of the M tags, and the first tag information of any one of the M tags is used to determine the tag; or,

[0033] The seventh information includes a correspondence between the first identifier and the M tags, and the correspondence is used to determine the M tags.

[0034] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, or obtain the correspondence between the first identifier and the M tags, which is conducive to the first device determining the M tags. Furthermore, after the first device receives the first information, it is conducive to the first device sending instructions to perform the first operation to the M tags.

[0035] In combination with the first aspect, in some implementations of the first aspect, the sixth information further includes a first flag, and the first flag indicates that the first identifier is not disabled.

[0036] In combination with the first aspect, in certain implementations of the first aspect, the first operation includes reading, and the first tag information of the first tag among the M tags includes a second flag whose value is the first value, and the second flag whose value is the first value indicates that the write operation is successfully performed on the first tag.

[0037] Based on the above technical solution, the first device can determine whether each of the M tags has successfully performed a write operation. In the case where the first operation includes reading, it is beneficial for the first device to send a read instruction only to the tag that has successfully performed the write operation, thereby avoiding the first device sending a read instruction to the tag that is in a write operation, resulting in read-write inconsistency or read failure.

[0038] In combination with the first aspect, in some implementations of the first aspect, the first operation includes reading, and the M1 tags are tags on which a write operation has been successfully performed among the M tags.

[0039] Based on the above technical solution, the first device only sends read instructions to tags that have successfully performed write operations, thereby avoiding the first device sending read instructions to tags that are in the process of writing operations, which may cause read-write inconsistency or read failure.

[0040] In combination with the first aspect, in some implementations of the first aspect, the first operation includes inventory, and if no legitimacy check is performed on any of the N tags, before sending the fourth information, the method further includes:

[0041] Perform a validity check on one of the N labels.

[0042] Optionally, if the legitimacy of one tag among the N tags has been verified, the first device will no longer verify the legitimacy of other tags.

[0043] Based on the above technical solution, it is helpful to ensure the security of the inventory process. In addition, when M tags correspond to the first identifier, if any one of the M tags passes the legitimacy check, it can be considered that all the M tags have passed the legitimacy check. Therefore, when the first device performs a legitimacy check on at least one of the M tags, it can achieve the purpose of performing a legitimacy check on the M tags, and can also avoid frequent signaling interactions caused by performing a legitimacy check on all the M tags.

[0044] In combination with the first aspect, in some implementations of the first aspect, the fourth information further indicates whether the first operation is successfully performed on each of the M tags.

[0045] Based on the above technical solution, it is helpful for other devices to determine whether each tag in the M tags performs the first operation successfully.

[0046] In combination with the first aspect, in certain implementations of the first aspect, the first operation includes disabling or writing; the fourth information includes second tag information of M tags, the second tag information of the fourth tag among the M tags includes a third flag having a second value, and the second tag information of the fifth tag among the M tags includes a third flag having a third value; wherein the third flag having the second value indicates that the first operation is to be performed on the fourth tag, and the third flag having the third value indicates that the first operation on the fifth tag is successfully performed.

[0047] In combination with the first aspect, in some implementations of the first aspect, the method further includes:

[0048] receiving eighth information, where the eighth information includes a fourth identifier, the fourth identifier corresponds to a tag, and the eighth information indicates to perform a second operation on the fourth identifier;

[0049] Sending ninth information to the tag corresponding to the fourth identifier, where the ninth information indicates to perform a second operation on the tag corresponding to the fourth identifier;

[0050] receiving tenth information from the tag corresponding to the fourth identifier, the tenth information indicating whether the second operation is successfully performed on the tag corresponding to the fourth identifier;

[0051] An eleventh message is sent, where the eleventh message indicates whether the second operation is successfully performed on the fourth identifier.

[0052] Exemplarily, the fourth identifier corresponds to a label that is predefined.

[0053] Based on the above technical solution, it is helpful for enterprises or operators to customize the number of labels corresponding to the identification according to different needs.

[0054] In a second aspect, a communication method is provided, which can be performed by a second device, and the second device can be replaced by a data management network element or a component of a data management network element (such as a chip or a chip system or a circuit or a communication module), or the second device can be replaced by an application function or a component of an application function (such as a chip or a chip system or a circuit or a communication module). For ease of understanding, the following description is taken as an example of the execution of the second device. At this time, the second device can also be referred to as a communication device.

[0055] Exemplarily, the method comprises:

[0056] Receive twelfth information, the twelfth information includes a first identifier, the first identifier corresponds to M tags, and the twelfth information indicates to perform a first operation on the first identifier; M≥2, M is an integer;

[0057] Sending first information, where the first information includes a first identifier, and the first information indicates that a first operation is to be performed for the first identifier;

[0058] Fourth information is received, where the fourth information indicates that the first operation is successfully performed on the first identifier.

[0059] Based on the above technical solution, by corresponding M tags to a first identifier, each device can interactively indicate instructions to perform the first operation on the M tags, thereby achieving the purpose of performing the first operation on the M tags, thereby avoiding frequent interactive instructions between each device to perform the first operation on each of the M tags.

[0060] Exemplarily, M tags correspond to a first terminal; or, M tags correspond to P terminals, and any two of the M tags are of the same type, and P is an integer greater than 1.

[0061] Herein, the first terminal refers to a terminal.

[0062] Exemplarily, the first identification is determined based on identification of one or more tags among the M tags, where the identification of the tag includes one or more of the following: a tag identification, an electronic product code, or a user identification.

[0063] In combination with the second aspect, in some implementations of the second aspect, the fourth information further indicates whether the first operation is successfully performed on each of the M tags.

[0064] Based on the above technical solution, it is helpful for the second device to determine whether each tag in the M tags performs the first operation successfully.

[0065] In combination with the second aspect, in certain implementations of the second aspect, the first operation includes disabling or writing, the fourth information includes second tag information of M tags, the second tag information of the fourth tag among the M tags includes a third flag having a second value, and the second tag information of the fifth tag among the M tags includes a third flag having a third value; wherein the third flag having the second value indicates that the first operation is to be performed on the fourth tag, and the third flag having the third value indicates that the first operation on the fifth tag is successfully performed.

[0066] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes:

[0067] The thirteenth message is sent, and the thirteenth message indicates that the first operation is successfully performed on the first identifier.

[0068] In combination with the second aspect, in some implementations of the second aspect, before receiving the fourth information, the method further includes:

[0069] Send the seventh message;

[0070] The seventh information includes the first identifier and first tag information of the M tags, and the first tag information of any one of the M tags is used to determine the tag; or,

[0071] The seventh information includes a correspondence between the M tags and the first identifier, and the correspondence is used to determine the M tags.

[0072] Based on the above technical solution, the first device can obtain the first tag information of the M tags corresponding to the first identifier, or obtain the correspondence between the first identifier and the M tags, which is beneficial for the first device to determine the M tags. Furthermore, after the first device receives the first information, it is beneficial for the first device to send instructions to perform the first operation to the M tags.

[0073] In conjunction with the second aspect, in some implementations of the second aspect, before receiving the twelfth information, the method further includes:

[0074] receiving fourteenth information, wherein the fourteenth information indicates determining the first identifier;

[0075] Based on the above technical solution, the second device can determine the first identifier based on the fourteenth information, and the first identifier corresponds to multiple tags. Then, different network elements can interact with each other to indicate instructions to perform the first operation on the first identifier, thereby achieving the purpose of performing the first operation on multiple tags corresponding to the first identifier, thereby avoiding frequent interactions between different network elements to indicate instructions to perform the first operation on each of the multiple tags.

[0076] Exemplarily, the fourteenth information further indicates a method of determining the first identifier based on identifiers of one or more tags among the M tags.

[0077] In conjunction with the second aspect, in some implementations of the second aspect, saving the first identifier includes:

[0078] Save the association relationship between the first identifier and the M tags; or,

[0079] The first identifier is saved in the signing information of each tag in the M tags.

[0080] In a third aspect, a communication device is provided. The communication device may include a functional module corresponding to the method / operation / step / action described in any possible implementation of the first aspect, or include a functional module corresponding to the method / operation / step / action described in any aspect of the second aspect. The module may be a hardware circuit, or software, or a combination of a hardware circuit and software.

[0081] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending action and the receiving action performed by the first device in the method described in the first aspect above, and the processing module is used to perform the action involving processing performed by the first device in the method described in the first aspect above.

[0082] In one design, the communication device may be a tag management functional entity, or may be a device, module, circuit or chip configured in the tag management functional entity, or may be a device that can be used in conjunction with the tag management functional entity, such as an intelligent network element, an over-the-top (OTT) server or a cloud server deployed with a radio access network (RAN) intelligent controller (RIC).

[0083] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending action and the receiving action performed by the second device in the method described in the second aspect above, and the processing module is used to perform the action involving processing performed by the second device in the method described in the second aspect above.

[0084] In one design, the communication device may be a data management network element or an application function, or may be a device, module, circuit or chip configured in the data management network element or application function, or may be a device that can be used in conjunction with the data management network element or application function, such as an intelligent network element, an OTT server or a cloud server.

[0085] In a fourth aspect, a communication device is provided, comprising a processor and a storage medium, wherein the storage medium stores instructions, which, when executed by the processor, enable a method as in the first aspect or any possible implementation of the first aspect to be implemented, or enable a method as in the second aspect or any possible implementation of the second aspect to be implemented.

[0086] In a fifth aspect, a communication device is provided, comprising a processing circuit, wherein the processing circuit is used to process data and / or information so that a method as in the first aspect or any possible implementation of the first aspect is implemented, or a method as in the second aspect or any possible implementation of the second aspect is implemented.

[0087] The processing circuit may include one or more processors, or all or part of the circuitry of one or more processors for controlling or processing functions.

[0088] Optionally, the communication device may also include a memory, the memory being used to store programs or instructions, and the processor being used to run the programs or instructions so that the method in the first aspect or any possible implementation of the first aspect is implemented, or the method in the second aspect or any possible implementation of the second aspect is implemented.

[0089] Optionally, the communication device may further include the transceiver circuit, or an input / output interface.

[0090] In a sixth aspect, a chip is provided, comprising a processing circuit, wherein the processing circuit is used to run a program or instruction so that a method as in the first aspect or any possible implementation of the first aspect is implemented, or a method as in the second aspect or any possible implementation of the second aspect is implemented.

[0091] Optionally, the chip may further include a memory, wherein the memory is used to store programs or instructions.

[0092] Optionally, the chip may further include a transceiver circuit, or an input / output interface.

[0093] In a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium is included in a communication device, and the computer-readable storage medium includes instructions, and when the instructions are executed by a processor, the method in the first aspect or any possible implementation of the first aspect is implemented, or the method in the second aspect or any possible implementation of the second aspect is implemented.

[0094] In an eighth aspect, a computer program product is provided. The computer program product includes computer program code or instructions, and when the computer program code or instructions are executed on a communication device, the method in the first aspect and any possible implementation of the first aspect is implemented, or the method in the second aspect or any possible implementation of the second aspect is implemented.

[0095] In a ninth aspect, a communication system is provided, which includes an apparatus for executing the first aspect and any possible implementation of the first aspect, or includes an apparatus for executing the second aspect and any possible implementation of the second aspect.

[0096] It should be understood that the third to ninth aspects of the present application correspond to the technical solutions of the first to second aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] Figure 1 is a schematic diagram of a communication system applicable to the communication method of an embodiment of the present application;

[0098] Figure 2 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0099] Figure 3 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0100] Figure 4 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0101] Figure 5 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0102] Figure 6 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0103] Figure 7 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0104] Figure 8 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0105] Fig. 9 It is another schematic block diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0106] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0107] The technical solution provided in the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, wireless local area network (wireless local area network, WLAN) system, satellite communication system, future communication system, etc., or a fusion system of multiple systems, etc. The technical solution provided in the present application can also be applied to device to device (device to device, D2D) communication, vehicle to everything (vehicle-to-everything, V2X) communication, machine to machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and Internet of things (Internet of things, IoT) communication system or other communication systems.

[0108] The technical solution provided in this application can also be applied to non-terrestrial communication network (NTN) systems such as intersatellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and a terminal device. The satellite base station provides communication services for the terminal device. The satellite base station can also communicate with the base station. The satellite can be used as a base station or as a terminal device. Among them, the satellite can refer to an unmanned aerial vehicle, a hot air balloon, a low-orbit satellite, a medium-orbit satellite, a high-orbit satellite, etc. A satellite can also refer to a non-ground base station or non-ground equipment, etc.

[0109] A device in a communication system can send a signal to another device or receive a signal from another device. The signal may include information, signaling or data, etc. The device may also be replaced by an entity, a network entity, a communication device, a mobile device, a network element, a communication module, a node, a communication node, a communication device, etc. The present disclosure is described by taking the device as an example. For example, a communication system may include at least one terminal device and at least one network device. The network device may send a downlink signal to the terminal device, and / or the terminal device may send an uplink signal to the network device. It is understandable that the terminal device in the present disclosure may be replaced by a first communication device, and the network device may be replaced by a second communication device, and the two perform the corresponding communication method in the present disclosure. Alternatively, the corresponding communication method in the present disclosure may be applied between network devices, or between terminal devices, which is not limited here.

[0110] The network device in the embodiment of the present application may be a device or module with corresponding communication functions. The network device may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network. Base station can broadly cover various names as follows, or replace with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point, master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center, a device that performs the base station function in D2D, V2X, and M2M communications, a device that performs the base station function in future communication systems, etc. The base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network device.

[0111] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0112] In some deployments, the network device mentioned in the embodiments of the present application may be a device including a CU, or a DU, or a device including a CU and a DU, or a control plane CU node (central unit control plane (central unit-control plane, CU-CP)) and a user plane CU node (central unit user plane (central unit-user plane, CU-UP)) and a DU node. For example, the network device may include a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU.

[0113] In some deployments, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes implement part of the functions of the base station. For example, the RAN node can be a CU, DU, CU-CP, CU-UP, or RU. The CU and DU can be set separately, or can also be included in the same network element, such as a BBU. The RU can be included in a radio frequency device or a radio frequency unit, such as an RRU, AAU, or RRH.

[0114] In some deployments, the CU is a logical node that carries the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer and other control functions of the access network equipment. The CU is connected to network nodes such as the core network through some interfaces, which may be E2 interfaces, etc. Optionally, the CU has some functions of the core network. The CU (such as the PDCP layer and higher layers) is connected to the DU (such as the radio link control (RLC) layer and lower layers) through some interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (such as the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (such as interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol of the F1 interface, and in some examples, the signaling process of F1 is defined. The F1 interface supports the control plane (F1 control plane, F1-C) and the user plane (F1 user plane, F1-U).

[0115] In some deployments, the CU can be split into CU-CP and CU-UP. Among them, CU-CP is a logical node that carries the RRC layer and the control plane (control plane part of PDCP, PDCP-C) layer of PDCP, and is used to implement the control plane function of CU. CU-CP can interact with the network elements in the core network for implementing the control plane function. The network element in the core network for implementing the control plane function may be an access and mobility function network element. CU-UP is a logical node that carries the SDAP layer and the user plane (user plane part of PDCP, PDCP-U) layer of PDCP, and is used to implement the user plane function of CU. CU-UP can interact with the network elements in the core network for implementing the user plane function. The network element in the core network for implementing the user plane function. The above configuration of CU and DU is only an example, and the functions of CU and DU can also be configured as needed. For example, CU or DU can be configured to have the functions of more protocol layers, or CU or DU can be configured to have partial processing functions of the protocol layer. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. For another example, the functions of the CU or DU can be divided according to the service type or other system requirements, such as by latency, and the functions whose processing time needs to meet the smaller latency requirement are set in the DU, and the functions that do not need to meet the latency requirement are set in the CU.

[0116] In some deployments, the DU is a logical node that carries the RLC layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU. The DU is connected to the RU through some interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes parts of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation and other processing functions.

[0117] In some deployments, the RU is a logical node that carries the lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP or RRH or other entity with similar functions. In some examples, Low-PHY includes part of the PHY processing, such as fast Fourier transform (FFT), inverse fast Fourier transformation (IFFT), digital beamforming and filtering. The RU communicates with one or more UEs via a wireless link.

[0118] The DU and RU may or may not be co-located. The DU and RU exchange control plane information and user plane information via the lower-layer split CUS-Plane (LLS-CUS) interface over the fronthaul link. The LLS-CUS may include interfaces and interfaces that provide the control plane and user plane, respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU have an interface for the fronthaul link (such as the so-called LLS-M interface) to exchange management information, and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0119] DU and RU can cooperate to jointly implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in a variety of ways according to the design. For example, DU is configured to implement baseband functions, and RU is configured to implement mid-RF functions. For another example, DU is configured to implement high-level functions in the PHY layer, and RU is configured to implement low-level functions in the PHY layer or to implement the low-level functions and RF functions. The high-level functions in the physical layer may include a part of the functions of the physical layer, which is closer to the MAC layer, and the low-level functions in the physical layer may include another part of the functions of the physical layer, which is closer to the mid-RF side.

[0120] In one possible design, the processing unit for implementing the baseband function in the BBU is called a baseband high layer (BBH) unit, and the processing unit for implementing the baseband function in the RRU / AAU / RRH is called a baseband low layer (BBL) unit.

[0121] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, the radio access network may also be an open radio access network (O-RAN) architecture. In the O-RAN system, CU may also be called an open CU (open CU, O-CU), DU may also be called an open DU (open DU, O-DU), CU-CP may also be called an open (open CU-CP, O-CU-CP), CU-UP may also be called an open (open CU-UP, O-CU-UP), and RU may also be called an open RU (open RU, O-RU). Any unit in the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0122] In the embodiment of the present application, the device for realizing the function of the network device may be a network device, or a device capable of supporting the network device to realize the function, such as a chip system or a chip or a circuit or a communication module (i.e., a communication module that performs a communication function), and the communication device may be installed in the network device. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In addition, program instructions for performing corresponding communication functions may also be configured in the communication device. In the embodiment of the present application, only the device for realizing the function of the network device is a network device as an example for explanation, and the scheme of the embodiment of the present application is not limited.

[0123] The network device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water; it can also be deployed on aircraft, balloons and satellites in the air. The scenario in which the network device is located is not limited in the embodiments of the present application. In addition, the network device can be a hardware device, or it can be a software function running on dedicated hardware, a software function running on general-purpose hardware, such as a virtualization function instantiated on a platform (e.g., a cloud platform), or an entity including dedicated or general-purpose hardware devices and software functions. The present application does not limit the specific form of the terminal device and the network device.

[0124] First, a communication system applicable to an embodiment of the present application is briefly introduced as follows.

[0125] Figure 1 1 is a schematic diagram of a communication system 100 applicable to the present application. Figure 1As shown, the communication system 100 includes one or more of the following: a tag, an access network device (RAN), a tag management function (TMF) entity, a unified data management (UDM) network element, an application function (AF), and an operator's business and operation support system (BOSS). Optionally, the communication system 100 also includes a network exposure function (NEF).

[0126] Below Figure 1 Describe each network element involved.

[0127] 1. Tag: A tag is also called a transponder, electronic tag, radio frequency identification (RFID) tag, radio frequency tag, transponder, data carrier, recording medium, radio frequency card, AIoT device, AIoT terminal, IoT device, IoT terminal, etc. For the convenience of description, this application uniformly refers to it as a tag. Each tag has a unique electronic code, such as a tag identifier (TID), and each tag also has an electronic product code (EPC). The tag can be attached to an object or device to identify the target object.

[0128] The storage area of ​​the tag can be divided into a reserved storage area, an EPC storage area, a TID storage area, and a user storage area. Among them, the reserved storage area is mainly used to store kill passwords, access passwords, etc. The EPC storage area is mainly used to store the EPC of the tag, etc. The TID storage area is mainly used to store the TID of the tag. The user storage area is mainly used to store user-defined data.

[0129] Tags may include: active tags (also called Class C tags), semi-passive tags (also called Class B tags) and passive tags (also called Class A tags).

[0130] Active tags, also known as active tags, are powered by a battery inside the tag. The battery energy can also be converted into the radio frequency energy required for the tag to communicate with the reader.

[0131] Semi-passive tags are tags that have batteries but do not actively transmit RF signals. They receive and respond to RF signals from readers.

[0132] Passive tags, also known as passive tags, do not have batteries inside. When the tag is outside the reading range of the reader, the tag is in a passive state. When the tag is within the reading range of the reader, the tag extracts the energy required for its operation from the radio frequency energy emitted by the reader.

[0133] 2. The access network equipment has the ability to count tags, and can use air interface wireless technology to stimulate and count tags in the passive Internet of Things. The access network equipment can be used to communicate with terminals (such as Figure 1 The device for communicating with a terminal through a wireless network (label shown in FIG. 1 ) may also be a device for connecting a terminal to a wireless network. For more description of the access network device, please refer to the description of the network device above.

[0134] The embodiments of the present application do not limit the specific technology, device form and name adopted by the access network device.

[0135] 3. TMF is responsible for managing labels. TMF can be an independent network element. TMF can also be co-located with other network elements, such as Figure 1 As shown, it is co-located with the access and mobility management function (AMF). TMF can also be a function of other network elements, or it can be understood that other network elements are improved so that the network elements have the functions that TMF is responsible for, such as improving AMF so that AMF has the functions of TMF, that is, AMF can have the functions of TMF while having the functions of managing user registration, reachability detection, session management function (SMF) node selection, mobile state transition management, etc.

[0136] Optionally, TMF can be replaced by one of the following: ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), ambient IoT aware core network (AIoT aware CN), or other core network elements / nodes / devices that support or enable AIoT.

[0137] 4. AF mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network. AF can be the AF deployed by the operator network itself or a third-party AF.

[0138] 5. NEF is mainly used to securely open the services and capabilities provided by 3GPP network functions and support secure interaction between 3GPP networks and third-party applications.

[0139] 6. UDM is used to generate 3GPP authentication and key agreement (AKA) authentication certificates, user identification (User ID) processing, access authorization based on contract information, service network function (NF) registration management, contract information management and other function-related data unified management.

[0140] 7. BOSS is an important supporting software platform for operators to realize network operation, management and maintenance. BOSS undertakes important functions such as billing, customer management, data collection and analysis, marketing decision-making, network operation and maintenance. BOSS provides comprehensive network operation and management support for operators through billing, authentication, customer relationship maintenance, marketing strategy mining for different services and customers, as well as monitoring and management of basic network operation quality.

[0141] It should be understood that Figure 1 In the network architecture shown, each network element can communicate with each other through an interface. The interface between each network element can be a point-to-point interface or a service-oriented interface, which is not limited in this application.

[0142] It should be understood that the network architecture shown above is only an exemplary description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0143] It should also be understood that Figure 1 The functions or network elements such as AMF, TMF, NEF, AF, etc. shown in the figure can be understood as network elements used to implement different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0144] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in other networks.

[0145] With the development of technology and environmental protection requirements, the Internet of Things will have a larger scale of application deployment prospects, and it is predicted that it will cover hundreds of billions of devices in the future. Based on this, the number of tags in the network will increase. If the reader and each tag perform one or more of the processes of reading, writing, inventorying or disabling, and at the same time require the tag to respond to the reader's operation request immediately, it will lead to too much signaling interaction on the network side.

[0146] In view of this, an embodiment of the present application provides a communication method and device, which defines identifiers corresponding to multiple tags, and when the read, write, inventory or disable process is triggered on the network side, indexes multiple tags through the newly defined identifier, thereby helping to reduce signaling interactions on the network side.

[0147] Before introducing the solution of this application, the following points are made.

[0148] (1) In this application, "indication" may include direct indication, indirect indication, explicit indication, and implicit indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0149] In the present application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, specified by the protocol), thereby reducing the indication overhead to a certain extent. In addition, the information to be indicated can be sent as a whole, or it can be divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different.

[0150] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information is XX, which can include direct sending through the air interface, and also include indirect sending through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information is YY, which can include direct receiving from YY through the air interface, and also include indirect receiving from YY through the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be performed between devices, for example, between network devices and terminal devices, or can be performed within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.

[0151] (3) In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the different embodiments are consistent and can be referenced to each other. The technical features in the different embodiments can be combined to form a new embodiment based on their internal logical relationships.

[0152] (4) In this application, "first" and "second" are only used for convenience of description and to distinguish objects, and are not used to limit the scope of the embodiments of this application. They are not used to describe the order or precedence of features. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of this application.

[0153] (5) In the present application, “predefined” may mean predefined by a standard protocol, or may mean pre-agreed or pre-negotiated between devices.

[0154] (6) In this application, words such as "exemplarily" and "such as" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as an "example" in this application should not be construed as being preferred or advantageous over other embodiments or designs. Specifically, the use of the word "example" is intended to present concepts in a concrete way. In the embodiments of this application, "of", "corresponding, relevant" and "corresponding" are sometimes used interchangeably. It should be noted that when the distinction is not emphasized, the meanings to be expressed are consistent.

[0155] (7) "At least one" in this document means one or more. "Multiple" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of this application, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

[0156] The method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings. The embodiment provided by the present application can be applied to the above Figure 2 The communication system shown is not limited.

[0157] It should be noted that the following is an illustrative description of the method provided in the embodiment of the present application by taking the interaction between the first device, the second device, and the third device as an example. Among them, the first device can be replaced by a tag management function entity or a component of a tag management function entity (such as a chip or a chip system or a circuit or a communication module). The tag management network element can be replaced by one of the following: AIoTMF, AIoTF, AIoT aware CN, or other core network elements / nodes / devices that support or enable AIoT. The second device can be replaced by a data management network element (such as the UDM described above) or a component of a data management network element (such as a chip or a chip system or a circuit or a communication module), or the second device can be replaced by an application function (such as the AF described above) or a component of an application function (such as a chip or a chip system or a circuit or a communication module). The third device can be replaced by a network development function (such as the NEF described above) or a component of the network development function (such as a chip or a chip system or a circuit or a communication module), or the third device can be replaced by an operator's business operation support system (such as the BOSS described above) or a component of an operator's business operation support system (such as a chip or a chip system or a circuit or a communication module).

[0158] Furthermore, the steps described below as being executed by a single execution entity may also be divided into steps executed by multiple execution entities, and these execution entities may be separated logically and / or physically.

[0159] Figure 2 2 is a schematic diagram of a communication method 200 provided in an embodiment of the present application. Figure 2 As shown, method 200 may include the following steps.

[0160] S201: A third device registers a first identifier in a second device.

[0161] A detailed description of how the third device registers the first identifier in the second device can be found in method 300 below, which is not described in detail here for the sake of brevity.

[0162] S202: The second device sends seventh information.

[0163] Correspondingly, the first device receives the seventh information.

[0164] In a possible implementation, the seventh information includes the first identifier and first tag information of M tags, and the first tag information of any one of the M tags is used to determine the tag. Wherein, M≥2, and M is a positive integer.

[0165] Exemplarily, the first identifier in the embodiment of the present application can be replaced by a logical label, and the M labels in the embodiment of the present application can be replaced by M physical labels.

[0166] The first tag information of the tag may include one or more of the following: an identifier of the tag or a second flag whose value is a first value. The identifier of the tag may include one or more of the following: TID, EPC, or User ID. The second flag whose value is the first value indicates that the tag successfully performs the overwrite operation. Exemplarily, if the first tag information of any tag #a among the M tags includes a second flag whose value is the first value, then tag #a can be called the first tag.

[0167] The first identifier corresponds to M tags. It should be understood that when the first device receives the first identifier and the first tag information of the M tags, the first device can determine the M tags based on the first tag information of the M tags, and determine that the first identifier corresponds to the M tags.

[0168] Exemplarily, M tags correspond to a first terminal. It should be understood that the first terminal refers to one terminal.

[0169] In another exemplary embodiment, there are M tags for P terminals, and any two of the M tags are of the same type. P is an integer greater than 1.

[0170] The embodiment of the present application does not limit the correspondence between the M tags and the first identifier. For example, the first identifier is determined based on the identifier of one or more tags in the M tags. For another example, the first identifier can be a randomly generated random number corresponding to the M tags.

[0171] Exemplarily, the correspondence between the M tags and the first identifier is predefined by the enterprise or operator. In other words, the correspondence between the first identifier and the M tags is defined by the enterprise or operator.

[0172] The embodiment of the present application does not limit the method for determining the first identifier based on the identifiers of one or more tags among the M tags.

[0173] For example, if the Xth to Yth bits of the EPC of any two of the M tags are the same, the first identifier can be determined based on the X1th to Y1th bits of the EPC of any one of the M tags, where X1≥X, Y1≤Y, and X, Y, X1, and Y1 are all integers greater than or equal to 0.

[0174] For another example, the first identifier may be composed of identifiers of M tags, or the first identifier may be composed of the Zth bit of the identifier of each tag in the M tags, where Z is an integer greater than or equal to zero.

[0175] In a possible implementation manner, the seventh information includes a correspondence between the first identifier and the M tags, and the correspondence between the first identifier and the M tags is used to determine the M tags.

[0176] It should be understood that when the first device receives the seventh information, if the first device stores the contract information of at least one tag, the first device can determine the M tags based on the contract information of at least one tag and the correspondence between the first identifier and the M tags. For example, if the correspondence between the first identifier and the M tags indicates that the X1th to Y1th bits of the EPC of each tag in the M tags can constitute the first identifier, the first device determines that the X1th to Y1th bits of the EPC of any two tags in the M tags are the same, and the first identifier is composed of the X1th to Y1th bits of the EPC of any one of the M tags. Furthermore, the first device can determine the tags with the same X1th to Y1th bits of the EPC of the tags in at least one tag as M tags based on the contract information of the stored at least one tag, and determine that the first identifier is the X1th to Y1th bits of the EPC of any one of the M tags.

[0177] Exemplarily, the tag's subscription information may include the tag's identifier, such as one or more of a TID, an EPC, or a User ID.

[0178] Exemplarily, the correspondence between the first identifier and M labels can be replaced by a method for determining the first identifier based on M labels, or can be replaced by a first identifier creation rule, or can be replaced by a logical label creation rule, or can be replaced by a mapping rule between a logical label and M physical labels.

[0179] Optionally, the seventh information also includes a second identifier, the second identifier corresponds to multiple third identifiers, each of the multiple third identifiers corresponds to at least one label, and the multiple third identifiers include the first identifier.

[0180] Optionally, if the multiple third identifiers corresponding to the second identifier include identifier #a in addition to the first identifier, and the second device is used to provide services for at least one tag corresponding to identifier #a, in other words, the second device can communicate with at least one tag corresponding to identifier #a, then the seventh information also includes identifier #a and first tag information of at least one tag corresponding to identifier #a, or includes the correspondence between identifier #a and at least one tag corresponding to identifier #a.

[0181] Optionally, if the multiple third identifiers corresponding to the second identifier also include the above identifier #a, the method 200 also includes: the second device sends information #a to the first device, the information #a includes the second identifier, the identifier #a and the first tag information of at least one tag corresponding to the identifier #a, or the information #a includes the second identifier and the corresponding relationship between the identifier #a and at least one tag corresponding to the identifier #a. The second device can send the seventh information and information #a to the first device at the same time, or send the seventh information to the first device first, and then send information #a to the first device, or send information #a to the first device first, and then send the seventh information to the first device.

[0182] It should be noted that S202 is an optional step. For example, after the third device registers the first identifier with the second device, if the second device determines that the M tags corresponding to the first identifier are not registered with the first device, then method 200 may not execute S202. For another example, if the first device has not subscribed to the change notification of the contract information of the M tags, then method 200 may not execute S202.

[0183] Further, the method 200 includes a step of the first device receiving the first information. Exemplarily, the first device receives the first information from the third device, and the method 200 continues to execute S203a. Exemplarily, the first device receives the first information from the second device, and the method 200 continues to execute S203b1 and S203b3.

[0184] S203a, the third device sends the first information.

[0185] Correspondingly, the first device receives the first information.

[0186] The first information includes a first identifier. For more description of the first identifier, please refer to S202 above.

[0187] The first information indicates that a first operation is performed on the first identifier. Exemplarily, the first operation is disabling, inventorying, reading or writing. For example, the first information may include a 2-bit field #1. If the value of field #1 is "00", it means that the first information indicates that an inventory is performed on the first identifier; if the value of field #1 is "01", it means that the first information indicates that an inventory is performed on the first identifier; if the value of field #1 is "10", it means that the first information indicates that a read is performed on the first identifier; if the value of field #1 is "11", it means that the first information indicates that a write is performed on the first identifier.

[0188] Optionally, the first information further indicates a first condition, and the first condition is used by the first device to determine whether the first operation is successfully performed for the first identifier.

[0189] Exemplarily, the first condition includes one or more of the following: the number of tags among M tags that successfully perform the first operation is not less than a first threshold value (hereinafter referred to as condition #1); the ratio between the number of tags among M tags that successfully perform the first operation and M is not less than a second threshold value; the number of tags among M tags that successfully perform the first operation is equal to M (hereinafter referred to as condition #2); the ratio between the number of tags among M tags that successfully perform the first operation in the first time period and M is not less than a third threshold value.

[0190] Among them, one or more of the first threshold, the second threshold, the third threshold, or the first time period is predefined or preconfigured, or is indicated by the third device to the first device, and this application does not limit this. For example, one or more of the first threshold, the second threshold, the third threshold, or the first time period is predefined or preconfigured by an enterprise or operator.

[0191] For example, if the first operation is an inventory, and M tags correspond to the first terminal, the first condition may include the above condition #1, and the first threshold is 1. For another example, if the first operation is an inventory for positioning, the first condition may include the above condition #2.

[0192] Optionally, if the third device has not registered the first identifier in the second device, the first information also includes information #1, where information #1 includes the first identifier and first tag information of the M tags, or information #1 includes a correspondence between the first identifier and the M tags. For more descriptions of information #1, refer to the description of the seventh information in S202 above.

[0193] Optionally, the first information also includes information for permission checking, and the information for permission checking is used by the first device to determine whether the third device has permission to instruct to perform the first operation on the first identifier. For example, the information for permission checking may include information of the third device. Accordingly, the first device may determine whether the third device has permission to instruct to perform the first operation on the first identifier based on the information of the third device.

[0194] In a possible implementation, the first identifier included in the first information may be replaced by the second identifier mentioned in S202 above.

[0195] It should be understood that if the first information includes the second identifier, the method 200 further includes: the first device determines at least one third identifier among a plurality of third identifiers corresponding to the second identifier.

[0196] For example, if method 200 executes S202, and the seventh information includes the second identifier and at least one of the multiple third identifiers corresponding to the second identifier, the first device can determine at least one of the multiple third identifiers corresponding to the second identifier based on the seventh information. It should be understood that the first device can provide services for the tags corresponding to each of the at least one third identifier. For example, at least one third identifier includes the first identifier and the identifier #a mentioned in S202 above, then the first device can provide services for M tags and at least one tag corresponding to the identifier #a.

[0197] For another example, if method 200 does not execute S202, the first device may obtain at least one third identifier among multiple third identifiers corresponding to the second identifier through S205 to S206 mentioned below.

[0198] Exemplarily, the first information sent by the third device is a message.

[0199] Optionally, after S203a1, the method 200 further includes: the first device sends response information #1 to the third device, wherein the response information #1 indicates that the first device has received the first information.

[0200] S203b1, the third device sends twelfth information.

[0201] Correspondingly, the second device receives the twelfth information.

[0202] The twelfth information includes the first identifier, and the twelfth information indicates that the first operation is performed on the first identifier. For example, the twelfth information may include a 2-bit field #2, and the value of field #2 is different, then the twelfth information indicates that the first operation performed on the first identifier is different, and more descriptions of field #2 can refer to the description of field #1 in S203a.

[0203] Optionally, the twelfth information further indicates the first condition. For more descriptions of the first condition, reference may be made to the description in S203a above.

[0204] Optionally, if the third device has not registered the first identifier in the second device, the twelfth information also includes information #1, where information #1 includes the first identifier and the first tag information of the M tags, or information #1 includes the correspondence between the first identifier and the M tags. For more description of information #1, refer to the description of the seventh information in S202 above.

[0205] Optionally, the twelfth information also includes information for permission checking, and the information for permission checking is used by the second device to determine whether the third device has permission to instruct to perform the first operation on the first identifier. For example, the information for permission checking may include information of the third device. Accordingly, the second device may determine whether the third device has permission to instruct to perform the first operation on the first identifier based on the information of the third device.

[0206] In a possible implementation, the first identifier included in the twelfth information may be replaced by the second identifier mentioned in S202 above.

[0207] Exemplarily, the twelfth information sent by the third device is a message.

[0208] Optionally, after S203b1, the method 200 further includes: the second device sends response information #2 to the third device, wherein the response information #2 indicates that the second device has received the twelfth information.

[0209] Optionally, if the first identifier included in the first information is replaced by the second identifier, and the second identifier corresponds to multiple third identifiers, the response information #2 indicates whether the second device has received an instruction instructing each of the multiple third identifiers to perform the first operation. For example, if the second identifier corresponds to the third identifier #1 and the third identifier #2, the response information #2 indicates whether the second device has received an instruction instructing the execution of the first operation for the third identifier #1, and / or indicates whether the second device has received an instruction instructing the execution of the first operation for the third identifier #2.

[0210] Optionally, if response information #2 indicates whether the second device has received an instruction to perform the first operation for the third identifier, the second device may, if it determines that the third device has the authority to instruct the execution of the first operation for the third identifier, indicate through response information #2 that the second device has received the instruction to perform the first operation for the third identifier; or, if it determines that the third device does not have the authority to instruct the execution of the first operation for the third identifier, the second device may, if it determines that the third device does not have the authority to instruct the execution of the first operation for the third identifier, indicate through response information #2 that the second device has not received the instruction to perform the first operation for the third identifier.

[0211] Optionally, if the first information includes the second identifier, the method 200 further includes: the second device determines multiple third identifiers corresponding to the second identifier. It should be understood that if the method 200 executes S201, and in S201, the third device registers the second identifier, multiple third identifiers, and the correspondence between the second identifier and the multiple third identifiers in the second device, the second device can determine the multiple third identifiers corresponding to the second identifier.

[0212] Optionally, if the second device determines multiple third identifiers corresponding to the second identifier, method 200 also includes S203b2.

[0213] S203b2, set the value of flag #a to value #a1.

[0214] Flag #a corresponds to the first identifier, and flag #a having a value of #a1 indicates that the first operation is to be performed on the first identifier. The second device sets flag #a to the value #a1, which is equivalent to the second device setting a flag for the first identifier to perform the first operation. For example, if the first operation is disable, it is equivalent to the second device setting a to-be-disabled flag for the first identifier, that is, flag #a having a value of #a1 can be called a to-be-disabled flag. For another example, if the first operation is write, it is equivalent to the second device setting a to-be-written flag for the first identifier, that is, flag #a having a value of #a1 can be called a to-be-written flag.

[0215] Optionally, the flag #a whose value is #a1 is stored in a non-volatile storage area corresponding to the second device.

[0216] Optionally, when the second device determines that the third device has the authority to instruct to perform the first operation on the first identifier, S203b2 is executed.

[0217] Optionally, in S203b2, the second device may also set a flag to execute the first operation for other identifiers in the plurality of third identifiers.

[0218] It should be noted that S203b2 is an optional step. For example, if the first operation includes writing or disabling, the method 200 may execute S203b2; if the first operation includes reading or inventorying, the method 200 may not execute S203b2.

[0219] S203b3, the second device sends the first information.

[0220] Correspondingly, the first device receives the first information.

[0221] After the second device receives the twelfth information from the third device, it may send the first information to the first device according to the twelfth information.

[0222] The first information includes a first identifier, and the first information indicates that a first operation is to be performed for the first identifier.

[0223] Optionally, if the twelfth information indicates the first condition, the first information also indicates the first condition.

[0224] Optionally, the first information also includes information #1. For example, if the twelfth information includes information #1, the first information may include information #1. For another example, if the third device registers the first identifier in the second device, but the method 200 does not perform S202, the first information may include information #1.

[0225] For more description about the first information, please refer to the description of the first information in S203a above.

[0226] In a possible implementation, the first identifier included in the first information may be replaced by the second identifier mentioned in S202 above.

[0227] It should be understood that if the first information includes the second identifier, the method 200 further includes: the first device determines at least one third identifier among multiple third identifiers corresponding to the second identifier. The manner in which the second device determines at least one third identifier can refer to the description in S203a above.

[0228] Optionally, after S203b2, the method 200 further includes: the first device sends response information #3 to the second device, wherein the response information #3 indicates that the second device has received the first information.

[0229] S204, set the value of flag #a to value #a1.

[0230] The flag #a corresponds to the first identifier, and the flag #a having the value #a1 indicates that the first operation is to be performed on the first identifier. The first device sets the flag #a to the value #a1, which is equivalent to the first device setting the flag to perform the first operation on the first identifier.

[0231] Optionally, the flag #a whose value is #a1 is stored in the context corresponding to the first identifier.

[0232] Optionally, when the first device determines that the third device has the authority to instruct to perform the first operation on the first identifier, S204 is executed.

[0233] Optionally, if the second device receives the second identifier and determines at least one third identifier corresponding to the second identifier, in S204, the second device may also set a flag for executing the first operation for an identifier other than the first identifier in the at least one third identifier.

[0234] It should be noted that S204 is an optional step. For example, if the first operation includes writing or disabling, the method 200 may execute S204; if the first operation includes reading or inventorying, the method 200 may not execute S204. For another example, if the first device saves the context corresponding to the first identifier, the method 200 executes S204; if the first device does not save the context corresponding to the first identifier, the method 200 does not execute S204.

[0235] Optionally, method 200 also includes S205 and S206.

[0236] S205: The first device sends fifth information.

[0237] Correspondingly, the second device receives the fifth information.

[0238] In a possible implementation, the fifth information includes a first identifier, and the fifth information is used to request first tag information of the M tags corresponding to the first identifier. The first tag information may refer to the description in S202 above.

[0239] In a possible implementation, the fifth information includes the first identifier, and the fifth information is used to request the correspondence between the first identifier and the M tags. The correspondence between the first identifier and the M tags can refer to the description in S202 above.

[0240] In a possible implementation, if the first information received by the first device includes the second identifier, the fifth information includes the second identifier. The fifth information is used to request at least one third identifier corresponding to the second identifier, and the first tag information of the tag corresponding to each third identifier in the at least one third identifier. Alternatively, the fifth information is used to request at least one third identifier corresponding to the second identifier, and the correspondence between each third identifier in the at least one third identifier and the tag corresponding to the third identifier. Among them, at least one third identifier includes the first identifier, and the first device is used to provide services for the tag corresponding to each third identifier in the at least one third identifier.

[0241] S206: The second device sends sixth information.

[0242] Correspondingly, the first device receives the sixth information.

[0243] In a possible implementation manner, the sixth information includes first tag information of M tags.

[0244] In a possible implementation manner, the sixth information includes a correspondence between the first identifier and the M tags.

[0245] In a possible implementation manner, the sixth information includes at least one third identifier and first tag information of a tag corresponding to each third identifier in the at least one third identifier.

[0246] In a possible implementation manner, the sixth information includes at least one third identifier and a corresponding relationship between each third identifier in the at least one third identifier and a label corresponding to the third identifier.

[0247] Optionally, the sixth information also includes a first flag, and the first flag indicates that the first identification is not disabled.

[0248] It should be understood that when the first device receives the sixth information, the M tags corresponding to the first identifier can be determined according to the sixth information. For example, the first device determines the M tags according to the first tag information of the M tags, or the first device determines the M tags according to the correspondence between the first identifier and the M tags.

[0249] It should be noted that S205 and S206 are optional steps. For example, if method 200 executes S202, method 200 may not execute S205 or S206. For another example, if the first information received by the first device includes information #1 mentioned in S203a above, method 200 may not execute S205 or S206.

[0250] S207, the first device sends second information.

[0251] Correspondingly, the tag receives the second information.

[0252] Exemplarily, in S207, the first device sends second information to M1 tags among the M tags, where the second information indicates to perform the first operation on each tag among the M1 tags, where M1≤M, and M1 is an integer.

[0253] For example, the second information may include a 2-bit field #3. If the value of field #3 is different, the second information indicates that the first operation performed on M1 tags is different. For more description of field #3, refer to the description of field #1 in S203a.

[0254] In a possible implementation, if the first operation includes reading, and the first device obtains the first tag information of the M tags based on the sixth information and / or the seventh information, then before S207, the method 200 also includes: the first device determines the first tag among the M tags based on the first tag information of the M tags. The first tag information of the first tag includes a second flag whose value is a second value. In other words, the first tag among the M tags is a tag that has successfully performed a write operation. Furthermore, in S207, the first device sends the second information to all the first tags among the M tags. In other words, the M1 tags include all the tags among the M tags that have successfully performed a write operation.

[0255] Exemplarily, in S207, the first device may send the second information to M1 tags through the reader. For example, the first device sends message #1 to the reader, and message #1 includes the second information and the identifiers of M1 tags; accordingly, the reader identifies the M1 tags according to the identifiers of the M1 tags, and sends the second information to the M1 tags.

[0256] S208: The tag sends third information.

[0257] Correspondingly, the first device receives the third information.

[0258] Exemplarily, in S208, each of the N tags sends third information to the first device, where the third information indicates that the first operation performed on the tag is successful.

[0259] Among them, N tags belong to M1 tags, N≤M1, and N is an integer.

[0260] Optionally, in S208, each of the N1 tags sends third information #a to the first device, where the third information #a indicates that execution of the first operation on the tag fails.

[0261] Among them, N1 labels belong to M1 labels, N1≤M1, and N1 is an integer. Any label in the N1 labels is different from any label in the N labels.

[0262] Exemplarily, in S208, the tag may send the third information or the third information #a to the first device through the reader / writer. For example, the tag sends message #2 to the reader / writer, and message #2 includes the third information or the third information #a; accordingly, the reader / writer sends the third information or the third information #a to the first device.

[0263] It should be understood that in S208, since the tag is not connected to the network or is not powered, the first device may not be able to receive the third information or the third information #a from each of the M1 tags.

[0264] Optionally, if the first operation includes inventory, after the first device receives the third information from tag #n among the N tags, if the legitimacy of any tag among the N tags has not been verified, the method 200 further includes: verifying the legitimacy of one tag among the N tags (e.g., tag #n). It should be understood that after the first device receives the third information from tag #n among the N tags, if the legitimacy of one tag among the N tags has been verified, the first device no longer verifies the legitimacy of tag #n.

[0265] Optionally, method 200 also includes S209.

[0266] S209, set the value of flag #a to value #a2.

[0267] Flag #a corresponds to the first identifier, and flag #a having a value of #a2 indicates that the first operation is successfully performed on the first identifier. The first device sets flag #a to the value #a2, which is equivalent to the first device setting a flag for the first identifier to successfully perform the first operation. For example, if the first operation is disable, it is equivalent to the first device setting a disabled flag for the first identifier, that is, flag #a having a value of #a2 can be called a disabled flag. For another example, if the first operation is write, it is equivalent to the first device setting a written flag for the first identifier, that is, flag #a having a value of #a2 can be called a written flag.

[0268] Optionally, the flag #a whose value is #a2 is stored in the context corresponding to the first identifier.

[0269] In a possible implementation, the first device may execute S209 upon receiving at least one third information.

[0270] In a possible implementation, the first device may execute S209 if the number of third information received satisfies the first condition. It should be understood that since the third information indicates that the first operation is successfully performed on the tag, the number of third information received by the first device is equal to the number of tags among the M tags that successfully perform the first operation. Based on this, the first condition described in S203a above may include one or more of the following: the number of third information is not less than the first threshold; the ratio between the number of third information and M is not less than the second threshold; the number of third information is equal to M; the ratio between the number of third information received within the first time period and M is not less than the third threshold. For more descriptions of the first condition, please refer to S203a above.

[0271] Optionally, if the number of third information received by the first device does not meet the first condition, the first device may continue to wait for the tag that has not fed back the third information or third information #a to feed back the third information or third information #a, or, the first device may again send the second information to the tags among the M tags that have not fed back the third information and third information #a and the tags that feed back the third information #a, until the number of third information received by the first device meets the first condition, and the first device executes S209.

[0272] It should be noted that S209 is an optional step. For example, if the first operation includes writing or disabling, method 200 may execute S209; if the first operation includes reading or inventorying, method 200 may not execute S209. For another example, if the first device saves the context corresponding to the first identifier, method 200 executes S209; if the first device does not save the context corresponding to the first identifier, method 200 does not execute S209.

[0273] It should also be noted that if method 200 executes S205 and S206, and the sixth information received by the first device includes the first flag, method 200 can execute S209; if the sixth information received by the first device does not include the first flag, or includes a flag used to indicate that the first identification is disabled (or is disabled), method 200 does not execute S209.

[0274] Further, the method 200 includes a step of the first device sending fourth information. Exemplarily, the first device sends the fourth information to the third device, and the method 200 continues to execute S210a. Also exemplarily, the first device sends the first information to the second device, and the method 200 continues to execute S210b1.

[0275] S210a, the first device sends fourth information.

[0276] Correspondingly, the third device receives the fourth information.

[0277] S210b1, the first device sends fourth information.

[0278] Correspondingly, the second device receives the fourth information.

[0279] The fourth information indicates that the first operation is successfully performed on the first identifier.

[0280] Optionally, the fourth information further indicates whether the first operation is successfully performed on each of the M tags.

[0281] Exemplarily, if the first operation includes disabling or writing, the fourth information includes the second tag information of M tags, the second tag information of the fourth tag among the M tags includes the third flag having a second value, and the second tag information of the fifth tag among the M tags includes the third flag having a third value. Among them, the third flag having a second value indicates that the first operation is to be performed on the fourth tag, and the third flag having a third value indicates that the first operation is successfully performed on the fifth tag. For example, if the first operation includes disabling, the third flag having a second value can be called a to-be-disabled flag, and the third flag having a third value can be called a disabled flag. For another example, if the first operation includes writing, the third flag having a second value can be called a to-be-written flag, and the third flag having a third value can be called a written flag.

[0282] In a possible implementation, the first device may execute S210a or S210b1 upon receiving at least one third information.

[0283] In a possible implementation, the first device may execute S210a or S210b1 if the amount of the received third information meets the first condition. For more descriptions of the first condition, refer to S203a and S209 above.

[0284] Optionally, if the number of third information received by the first device does not meet the first condition, the first device may continue to wait for the tag that has not fed back the third information or third information #a to feed back the third information or third information #a, or, the first device may again send the second information to the tags among the M tags that have not fed back the third information and third information #a and the tags that feed back the third information #a, until the number of third information received by the first device meets the first condition, and the first device executes S210a or S210b1.

[0285] Optionally, if the number of third messages received by the first device within the second time period after the first device sends the second message still does not meet the first condition, the first device may send a fourth message #a to the third device or the second device, and the fourth message #a indicates that the first operation for the first identifier has failed. The duration of the second time period is predefined or preconfigured, for example, the duration of the second time period is predefined by the enterprise or operator. The starting time of the second time period is the time when the first device sends the second message, or the starting time of the second time period is the time when the first device first receives the third message, and this application does not limit this.

[0286] It should be noted that if method 200 executes S205 and S206, and the sixth information received by the first device includes the first flag, method 200 can execute S210a or S210b1; if the sixth information received by the first device does not include the first flag, or includes a flag for indicating that the first identification is disabled (or is disabled), then the first device sends a fourth information #b to the second device or the third device each time it receives a third information or third information #a, and the fourth information #b indicates whether the first operation on the tag is successful. For example, if the first device receives the third information from tag #m, the first device sends the fourth information #b to the second device or the third device, and the fourth information #b indicates that the first operation on tag #m is successful. For another example, if the first device receives the third information #a from tag #n, the first device sends the fourth information #b to the second device or the third device, and the fourth information #b indicates that the first operation on tag #n fails.

[0287] Optionally, if method 200 executes S210b1, method 200 may further include S210b2 and / or S210b3.

[0288] S210b2, set the value of flag #a to value #a2.

[0289] The flag #a corresponds to the first identifier, and the flag #a having the value #a2 indicates that the first operation is successfully performed on the first identifier. The second device sets the flag #a to the value #a2, which is equivalent to the second device setting the flag that the first operation is successfully performed on the first identifier.

[0290] Optionally, the flag #a whose value is #a2 is stored in a non-volatile storage area corresponding to the second device.

[0291] It should be noted that S210b2 is an optional step. For example, if the first operation includes writing or disabling, the method 200 may execute S210b2; if the first operation includes reading or inventorying, the method 200 may not execute S210b2.

[0292] S210b3, the second device sends the thirteenth information.

[0293] Correspondingly, the third device receives the thirteenth information.

[0294] If the second device receives the fourth information, the thirteenth information sent by the second device to the third device based on the fourth information indicates that the first operation is successfully performed on the first identifier.

[0295] If the second device receives the fourth information #a, the second device sends the thirteenth information #a to the third device based on the fourth information #a, and the thirteenth information #a indicates that the first operation performed on the first identifier failed.

[0296] If the second device receives the fourth information #b, the second device sends the thirteenth information #b to the third device based on the fourth information #b, and the thirteenth information #b indicates whether the first operation is successfully performed on a certain tag (such as the tag #m or tag #n mentioned above).

[0297] In an embodiment of the present application, by corresponding M tags to a first identifier, the first device, the second device, and the third device can achieve the purpose of performing the first operation on the M tags by interactively indicating instructions to perform the first operation on the first identifier, thereby avoiding frequent interactive instructions between the first device, the second device, and the third device to perform the first operation on each of the M tags.

[0298] Optionally, if the first device executes S210a or 210b1 when the number of third information received is less than M, then after executing S210a or 210b1, the first device may continue to send second information to the tag among the M tags that did not successfully execute the first operation (for example, recorded as tag #t), so that tag #t can continue to try to execute the first operation.

[0299] Optionally, if the first device receives the third information from the tag #t, the first device may send the fourth information #b to the second device or the third device, thereby indicating to the second device or the third device that the tag #t has successfully performed the first operation.

[0300] Optionally, method 200 also includes the following steps.

[0301] Step 1: The first device receives eighth information, the eighth information includes a fourth identifier, the fourth identifier corresponds to a tag, and the eighth information indicates to perform a second operation on the fourth tag. For example, the second operation includes disabling, inventorying, reading or writing.

[0302] Optionally, the fourth identifier corresponds to a tag that is predefined or preconfigured. For example, the fourth identifier corresponds to a tag that is predefined by an enterprise or operator.

[0303] Step 2: The first device sends ninth information to the tag corresponding to the fourth identifier, and the ninth information instructs the tag corresponding to the fourth identifier to perform a second operation.

[0304] Step 3: The first device receives tenth information from the tag corresponding to the fourth identifier, where the tenth information indicates whether the second operation is successfully performed on the tag corresponding to the fourth identifier.

[0305] Step 4: The first device sends an eleventh message, where the eleventh message indicates whether the first operation is successfully performed on the fourth identifier.

[0306] For more description of the above steps 1 to 4, please refer to the description in S203a (or S203b1 and S203b3), S207, S208 and S201a (or S210b) above.

[0307] Based on the above solution, it can be known that the present application does not limit the number of tags corresponding to the identifiers (such as the first identifier, the third identifier or the fourth identifier) ​​mentioned in the present application. For example, an enterprise or operator can define the number of tags corresponding to different identifiers according to needs.

[0308] Combine the following Figures 3 to 7 , taking the first device as TMF, the second device as UDM, and the third device as NEF / BOSS as an example, the method provided in the embodiment of the present application is described. Exemplarily, the logical label in the following embodiment corresponds to the identifier (such as the first identifier, the third identifier, or the fourth identifier) ​​corresponding to the label in the above embodiment, and the physical label in the following embodiment corresponds to the label in the above embodiment.

[0309] Figure 3 3 is a schematic diagram of a communication method 300 provided in an embodiment of the present application. Figure 3 As shown, method 300 may include the following steps.

[0310] S301, signing of physical tag information.

[0311] The UDM account opening information includes the contract information of at least one physical tag.

[0312] S302, NEF / BOSS sends a logical label registration request (an example of the fourteenth information).

[0313] Accordingly, the UDM receives a logical label registration request.

[0314] The logical tag registration request is used to request the registration of a logical tag, or to request the registration of a group of logical tags, wherein each logical tag corresponds to at least one physical tag.

[0315] Optionally, if the logical label registration request is used to request registration of a logical label, the logical label registration request may include a logical label creation rule.

[0316] Optionally, if the logical label registration request is used to request registration of a group of logical labels, the logical label registration request may include a group of logical label creation rules.

[0317] Taking logical label creation rule #a as an example, logical label creation rule #a indicates a method of mapping at least one physical label #a to a logical label #a. In other words, logical label creation rule #a indicates a method of determining a logical label #a based on at least one physical label #a.

[0318] Exemplarily, the logical tag creation rule #a is at least one of the following.

[0319] (1) Mapping the X1th bit to the Y1th bit of the EPC of any physical tag #a in at least one physical tag #a to the logical tag #a. Optionally, X1 and Y1, or the difference between X1 and Y1 and X1, are predefined by the enterprise or operator. X1 and Y1 are non-negative integers.

[0320] (2) An enterprise or operator customizes a logical tag #a based on the User ID of at least one physical tag #a.

[0321] (3) A logical tag #a is equivalent to at least one physical tag #a.

[0322] Optionally, if the logical tag registration request is used to request registration of a group of logical tags, the logical tag registration request further indicates a method for determining the logical tag group identifier, or the logical tag registration request includes the logical tag group identifier, wherein the logical tag group identifier corresponds to a group of logical tags requested to be registered by the logical tag registration request.

[0323] Exemplarily, assume that at least one logical tag requested to be registered by the logical tag registration request includes logical tag #1 (corresponding to the first identifier in method 200), and logical tag #1 corresponds to M physical tags #1 (corresponding to the M tags in method 200). M is an integer greater than 1.

[0324] Optionally, method 300 also includes S303.

[0325] S303, UDM queries the saved logical label creation rules.

[0326] After receiving the logical label registration request, UDM first queries the saved logical label creation rules. If UDM queries and finds that the logical label creation rule corresponding to at least one logical label requested to be registered by the logical label registration request has been saved, UDM does not process it. If UDM does not save the logical label creation rule corresponding to at least one logical label requested to be registered by the logical label registration request, UDM maps the logical label requested to be registered by the logical label registration request based on the logical label registration request, and saves the mapped logical label and the logical label creation rule corresponding to the logical label.

[0327] Exemplarily, if the logical label registration request received by the UDM is used to request the registration of multiple logical labels, the UDM may have saved the logical label creation rules corresponding to some of the multiple logical labels. The UDM then only registers the remaining logical labels, that is, maps the logical labels, and saves the mapped logical labels and the logical label creation rules corresponding to the logical labels.

[0328] S304, UDM obtains the logical label and saves it.

[0329] The UDM may map out a logical label based on the logical label creation rule included in the logical label registration request, and save the mapped logical label and the logical label rule corresponding to the logical label.

[0330] Exemplarily, assuming that at least one logical label requested by the logical label registration request includes logical label #1, in S304, UDM maps logical label #1 from M physical labels #1 according to the logical label creation rule #1 corresponding to logical label #1, and saves logical label #1 and logical label creation rule #1.

[0331] Optionally, if the logical label registration request does not include a logical label creation rule, the UDM may map the logical label according to a predefined logical label creation rule, and save the logical label and the predefined logical label creation rule.

[0332] The embodiment of the present application does not limit the manner in which the UDM stores logical labels and logical label creation rules.

[0333] Exemplarily, the logical tag is independently signed and associated with the physical tag corresponding to the logical tag. In other words, the UDM independently saves the logical tag and the logical tag creation rule, and maintains (or saves) the association relationship between the logical tag and the physical tag corresponding to the logical tag.

[0334] As another example, the UDM stores the logical tag and the logical tag creation rule in the contract information of the physical tag corresponding to the logical tag.

[0335] S305, UDM sends a logical label registration response.

[0336] Accordingly, NEF / BOSS receives a logical tag registration response.

[0337] The logical tag registration response indicates that the UDM has registered at least one logical tag requested to be registered by the logical tag registration request.

[0338] Optionally, the logical tag registration response also includes at least one logical tag requested to be registered by the logical tag registration request.

[0339] Optionally, method 300 also includes S306 and S307.

[0340] S306, UDM sends a logical label creation rule.

[0341] Accordingly, TMF receives the logical label creation rules.

[0342] Exemplarily, after UDM maps at least one logical label based on a logical label registration request, if UDM saves information about a TMF that provides services for physical labels corresponding to one or more of the at least one logical label, UDM may send the logical label and logical label creation rules to the TMF.

[0343] Taking logical label rule #a as an example, logical label rule #a corresponds to logical label #a. If UDM saves information of TMF#a used to provide services for the physical label corresponding to logical label #a, then in S306, UDM can send logical label creation rule #a and logical label #a to TMF#a.

[0344] Optionally, if the logical tag registration request is used to request registration of multiple logical tags, there may be multiple TMFs used to provide services for the physical tags corresponding to at least one of the multiple logical tags. In S306, the UDM sends the logical tags and logical tag creation rules corresponding to the physical tags of the TMF services to multiple TMFs respectively.

[0345] Exemplarily, the UDM may send the logical labels and logical label creation rules corresponding to the physical labels of the TMF services to multiple TMFs at the same time.

[0346] As another example, the UDM may send the logical label and the logical label creation rule corresponding to the physical label of the TMF service to each TMF in turn in the multiple TMFs.

[0347] As another example, if the UDM sends multiple logical labels and the logical label creation rules corresponding to the logical labels to the same TMF, the UDM can send the multiple logical labels and the logical label creation rules corresponding to the multiple logical labels to the TMF at the same time, or send each of the multiple logical labels and the logical label creation rules corresponding to the logical labels to the TMF in turn.

[0348] For example, UDM saves logical label creation rule #1 corresponding to logical label #1, logical label creation rule #2 and logical label creation rule #3 corresponding to logical label #2, and UDM saves information of TMF #1 used to provide services for M physical labels #1, and information of TMF #2 used to provide services for physical labels corresponding to logical label #2 and physical labels corresponding to logical label #3, then UDM can execute step a and step b at the same time, or UDM can execute step a first and then execute step b, or UDM can execute step b first and then execute step a. Among them, step a is to send logical label #1 and logical label rule #1 to TMF #1, step b includes step b1 and step b2, step b2 is to send logical label #2 and logical label creation rule #2 to TMF #2, and step b2 is to send logical label #3 and logical label creation rule #3 to TMF #2.

[0349] Optionally, during the process of UDM executing step b, step b1 and step b2 may be executed simultaneously, or step b1 may be executed first and then step b2, or step b2 may be executed first and then step b1.

[0350] S307, TMF sends a logical label creation rule response.

[0351] Accordingly, the UDM receives a logical label creation rule response.

[0352] The logical label creation rule response indicates that the TMF has received the logical label and logical label creation rule from the UDM.

[0353] It should be noted that the embodiment of the present application is only described by taking the logical label being registered in the UDM as an example, and the present application does not limit this. For example, the logical label can also be registered in the AF.

[0354] In an embodiment of the present application, NEF / BOSS can register a logical label in UDM, and the logical label corresponds to one or more physical labels. Furthermore, when the logical label corresponds to multiple physical labels, if different network elements interact with each other to indicate instructions to perform the first operation on the logical label, the purpose of performing the first operation on multiple physical labels corresponding to the logical label can be achieved, thereby avoiding frequent interactions between different network elements to indicate instructions to perform the first operation on each of the multiple physical labels.

[0355] Combine the following Figure 4 , taking the first operation including disabling as an example, the method provided in an embodiment of the present application is described.

[0356] Figure 4 4 is a schematic diagram of a communication method 400 provided in an embodiment of the present application. Figure 4 As shown, method 400 may include the following steps.

[0357] S401, NEF / BOSS sends a disable logic tag request (an example of the twelfth information).

[0358] Accordingly, the UDM receives a request to disable the logical label.

[0359] The disable logical tag request indicates that a logical tag is disabled, or a group of logical tags are disabled. For ease of description, the logical tag indicated by the disable logical tag request is hereinafter referred to as logical tag #x.

[0360] Exemplarily, assume that the disable logical tag request indicates that the logical tag #1 is disabled, or indicates that the logical tag group #1 is disabled. The logical tag group #1 includes the logical tag #1. The logical tag #1 (corresponding to the first identifier in the method 200) corresponds to M physical tags #1 (corresponding to the M tags in the method 200), where M is an integer greater than 1.

[0361] Optionally, the request to disable the logical tag may also carry information for permission checking. For example, in S401, the NEF sends a request to disable the logical tag to the UDM, and the request to disable the logical tag may also carry information of the AF, which is used to trigger the NEF to send a request to disable the logical tag to the UDM. Accordingly, the UDM may determine whether the AF has the permission to disable the logical tag based on the information of the AF.

[0362] Optionally, the request to disable the logical tag also includes at least one disabling rule (corresponding to the first condition in method 200), each disabling rule corresponds to a logical tag #x, and each disabling rule is used to determine whether the logical tag #x corresponding to the disabling rule is successfully disabled.

[0363] Exemplarily, the disabling rules include one or more of the following: disabling rule #1, if a physical tag corresponding to the logical tag is successfully disabled, it means that the logical tag is successfully disabled; disabling rule #2, if all physical tags corresponding to the logical tag are successfully disabled, it means that the logical tag is successfully disabled; disabling rule #3, if the ratio of the number of successfully disabled physical tags to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), it means that the logical tag is successfully disabled; disabling rule #4, if the ratio of the number of successfully disabled physical tags to the number of all physical tags corresponding to the logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), it means that the logical tag is successfully disabled. The disabling rules can be customized by the enterprise or operator.

[0364] S402, UDM sets a flag of the logic label to be disabled.

[0365] UDM sets the pending disabled flag for logical label #x.

[0366] Exemplarily, assume that the UDM sets a to-be-disabled flag for logical label #1 (corresponding to the label #a with the value #a1 in method 200), or the UDM sets a to-be-disabled flag for at least one logical label in logical label group #1.

[0367] Optionally, the UDM stores the to-be-disabled flag of the logical label #x in a non-volatile storage area.

[0368] Optionally, if the logical label #x has been registered in the UDM, the method 400 executes S402.

[0369] Optionally, if the UDM determines that the AF / NEN / BOSS has the authority to disable the logical label #x, the UDM sets a pending disable flag for the logical label #x.

[0370] It should be noted that S402 is an optional step.

[0371] S403, UDM sends a disable logic tag response.

[0372] Accordingly, the NEF / BOSS receives a disable logic tag response.

[0373] The Disable Logical Label Response indicates that the UDM successfully received the Disable Logical Label Request.

[0374] Optionally, if the disable logical tag request indicates that multiple logical tags #x are to be disabled, the disable logical tag response indicates whether the UDM has received an instruction to disable each of the multiple logical tags #x. For example, if the disable logical tag request indicates that logical tags #1 and logical tags #2 are to be disabled, the disable logical tag response indicates whether the UDM has received an instruction to disable logical tag #1, and / or indicates whether the UDM has received an instruction to disable logical tag #2.

[0375] S404, UDM sends a notification of disabling the logical label.

[0376] Accordingly, TMF receives a notification of disabling the logical tag.

[0377] Exemplarily, in S404, the UDM sends a notification of disabling the logical label to the TMF used to provide services for the physical label corresponding to the logical label #x.

[0378] Optionally, if the request to disable the logical label indicates multiple logical labels #x, there may be multiple TMFs that are respectively used to provide services for the physical labels corresponding to at least one of the multiple logical labels #x. In this case, in S404, the UDM sends notifications of disabling the logical labels corresponding to the physical labels served by the TMFs to the multiple TMFs. The manner in which the UDM sends notifications of disabling logical labels to multiple TMFs can refer to the manner in which the UDM sends logical label creation rules to multiple TMFs in S306 above.

[0379] Optionally, if the request to disable the logical label also includes at least one disabling rule, then in S404, the UDM also sends the disabling rule of the logical label corresponding to the physical label of the TMF service to the TMF.

[0380] Exemplarily, assume that in S404, UDM sends a disabling logic label notification (corresponding to the first information in method 200) to the TMF used to provide services for logic label #1. Optionally, UDM also sends a disabling rule corresponding to logic label #1 to the TMF used to provide services for logic label #1.

[0381] Below Figure 4 Taking the TMF in FIG. 4 as an example of providing services for logical label #1, the remaining steps included in method 400 are described.

[0382] Optionally, if the TMF saves the context of the logical label #1, the method 400 further includes S405.

[0383] S405, TMF to logic label to be disabled flag.

[0384] Exemplarily, in S405, TMF sets a flag of logic label #1 to be disabled.

[0385] S406, TMF sends notification response #1.

[0386] Accordingly, UDM receives notification response #1.

[0387] Notification response #1 indicates that the TMF received a logical label disable notification for logical label #1.

[0388] S407, TMF counts or pages physical tags.

[0389] Exemplarily, in S407, the TMF counts or pages the M physical labels #1 corresponding to the logical label #1.

[0390] For example, TMF can initiate paging to active tags (such as Class C tags) among M physical tags #1, and / or, TMF can initiate inventory to passive tags (such as Class A tags or Class B tags) among M physical tags #1 to trigger M physical tags #1 to access the network.

[0391] It should be understood that, in combination with the above method 300, if before executing method 400, UDM sends logical label #1 and the logical label creation rule corresponding to logical label #1 to TMF, then before executing S407, TMF can determine M physical labels #1 according to the logical label creation rule corresponding to logical label #1. If UDM does not send logical label #1 and the logical label creation rule corresponding to logical label #1 to TMF, then before S407, TMF can request the logical label creation rule corresponding to logical label #1 from UDM. For example, TMF can send request information #a (corresponding to the fifth information in method 200) to UDM, and the request information #a includes logical label #1, and the request information #a is used to request the logical label creation rule corresponding to logical label #1. Then, UDM sends the logical label creation rule corresponding to logical label #1 to TMF based on the request information #a (corresponding to the sixth information in method 200). After TMF receives the logical label creation rule corresponding to logical label #1, it can determine the M physical labels #1 corresponding to logical label #1.

[0392] S408, the physical tag is connected to the network.

[0393] Exemplarily, in S408, one or more physical tags among the M physical tags #1 are connected to the network.

[0394] S409, TMF sends a physical tag disabling instruction.

[0395] Exemplarily, in S409, the TMF sends a physical tag disabling instruction (corresponding to the second information in method 200) to the M physical tags #1, or sends a physical tag disabling instruction to the physical tags connected to the network among the M physical tags #1.

[0396] Optionally, before executing S409, TMF may check whether the to-be-disabled flag of logical tag #1 is saved. If TMF saves the to-be-disabled flag of logical tag #1, TMF executes S409. If TMF does not save the to-be-disabled flag of logical tag #1, TMF does not process it.

[0397] S410, the physical tag sends feedback information #1.

[0398] Correspondingly, TMF receives feedback information #1.

[0399] Exemplarily, in S410, the TMF receives feedback information #1 from the physical tag #1.

[0400] Feedback information #1 (corresponding to the third information or third information #a in method 200) indicates whether the physical tag is disabled successfully.

[0401] It should be understood that in S410, since some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #1 from all the physical tags #1.

[0402] Optionally, after receiving feedback information #1, TMF may also set a disabled flag (corresponding to the third flag whose value is the third value in method 200) or a to-be-disabled flag (corresponding to the third flag whose value is the second value in method 200) for physical tag #1 according to the content indicated by feedback information #1. Specifically, if feedback information #1 indicates that physical tag #1 is disabled successfully, TMF sets a disabled flag for physical tag #1; if feedback information #1 indicates that the physical tag is not disabled successfully, or the disablement fails, TMF sets a to-be-disabled flag for physical tag #1.

[0403] S411, TMF determines whether the logical label is disabled successfully according to the logical label disabling rule.

[0404] Exemplarily, TMF determines whether logical label #1 is disabled successfully according to the disabling rule corresponding to logical label #1. TMF may obtain the disabling rule corresponding to logical label #1 from UDM, or the disabling rule corresponding to logical label #1 is predefined or preconfigured.

[0405] Taking the disabling rule corresponding to logical tag #1 as the disabling rule #1 described in S401 above as an example, if TMF receives a feedback message #1, and the feedback message #1 indicates that the physical tag is successfully disabled, TMF determines that the logical tag #1 is successfully disabled.

[0406] It should be understood that if TMF determines that logical tag #1 is not disabled successfully, TMF can repeat S407 to S410 until TMF determines that logical tag #1 is disabled successfully. Optionally, TMF repeats S407 to S410 only for physical tag #1 that is not disabled successfully, that is, in S407, TMF only counts or pages physical tag #1 that is not disabled successfully, and in S409, TMF only sends a physical tag disable instruction to physical tag #1 that is not disabled successfully.

[0407] If the TMF determines that the disabling of the logical tag #1 is successful, the method 400 continues to execute S412.

[0408] S412, TMF sends a logical tag disabling completion notification.

[0409] Accordingly, the UDM receives a logical tag disable completion notification.

[0410] Exemplarily, the logical label disabling completion notification (corresponding to the fourth information in method 400 ) sent by TMF indicates that the disabling of logical label # 1 is successful.

[0411] Optionally, the logical tag disabling completion notification also indicates whether each physical tag #1 in the M physical tags #1 is disabled successfully. For example, the logical tag disabling completion notification also includes a disabled flag or a to-be-disabled flag corresponding to each physical tag #1 in the M physical tags #1.

[0412] Optionally, method 400 also includes S413.

[0413] S413, UDM completes the process of disabling the logical label.

[0414] Exemplarily, in S413, the UDM deletes the stored logical tag #1, or sets a disabled flag for the logical tag #1 (corresponding to the flag #a with a value of #a2 in method 200).

[0415] S414, UDM sends notification response #2.

[0416] Accordingly, TMF receives notification response #2.

[0417] Notification response #2 indicates that the UDM has received the logical tag disable completion notification.

[0418] Optionally, if the TMF saves the context corresponding to the logical label #1, the method 400 also includes S415.

[0419] S415, TMF deletes the logical label context.

[0420] Exemplarily, in S415, TMF deletes the context corresponding to the logical label #1.

[0421] Optionally, method 400 also includes S416 and S417.

[0422] S416, UDM sends a logical label disabling completion report.

[0423] Accordingly, NEF / BOSS receives a logical tag disable completion report.

[0424] Illustratively, the logical tag disable completion report indicates that the disablement of logical tag #1 is successful.

[0425] S417, NEF / BOSS sends a report response.

[0426] In response, the UDM receives a report response.

[0427] Illustratively, the report response indicates that the NEF / BOSS has received the logical tag disable completion report.

[0428] In an embodiment of the present application, by corresponding multiple physical labels to one logical label, each network element (for example, including UDM, TMF, NEF or BOSS) can achieve the purpose of disabling multiple physical labels by interactively instructing the execution of disabling instructions on the logical label, thereby avoiding frequent interactive instructions between each network element to execute disabling instructions on each physical label in multiple physical labels.

[0429] In addition, when UDM and / or TMF sets the disable flag and the to-be-disabled flag for the logical tag, regardless of whether the physical tag can receive the physical tag disable instruction (or whether the disablement is successful), it can ensure that the network side can asynchronously process the disabling of the logical tag.

[0430] Combine the following Figure 5 , taking the first operation including inventory as an example, the method provided in the embodiment of the present application is described.

[0431] Figure 5 is a schematic diagram of a communication method 500 provided in an embodiment of the present application. Figure 5 As shown, method 500 may include the following steps.

[0432] S501, NEF / BOSS sends an inventory request (an example of the first information).

[0433] Accordingly, TMF receives an inventory request.

[0434] The inventory request indicates that an inventory is performed on a logical tag, or an inventory is performed on a group of logical tags. For ease of description, the logical tag indicated by the inventory request is hereinafter referred to as logical tag #x.

[0435] Exemplarily, assume that the inventory request indicates that an inventory is performed on logical tag #1, or indicates that an inventory is performed on logical tag group #1. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0436] Optionally, the inventory request further includes at least one inventory rule (corresponding to the first condition in method 200), each inventory rule corresponds to a logical tag #x, and each inventory rule is used to determine whether the inventory of the logical tag #x corresponding to the inventory rule is successful.

[0437] Exemplarily, the inventory rules include one or more of the following: Inventory rule #1, if the inventory of a physical tag corresponding to the logical tag is successful, it means that the inventory of the logical tag is successful; Inventory rule #2, if the inventory of all physical tags corresponding to the logical tag is successful, it means that the inventory of the logical tag is successful; Inventory rule #3, if the ratio of the number of physical tags that are successfully counted to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), it means that the inventory of the logical tag is successful; Inventory rule #4, if the ratio of the number of physical tags that are successfully counted to the number of all physical tags corresponding to the logical tag in time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), it means that the inventory of the logical tag is successful. The inventory rules can be customized by the enterprise or operator.

[0438] For example, if all physical tags corresponding to logical tag #x all correspond to one terminal, then the inventory rule corresponding to logical tag #x is inventory rule #1. For another example, if the inventory request indicates that the inventory of logical tag #x is used for positioning, then the inventory rule corresponding to logical tag #x is inventory rule #2.

[0439] Below Figure 5 Taking the TMF in FIG. 5 as an example of providing services for logical label #1, the remaining steps included in method 500 are described.

[0440] S502, TMF sends request information #1 (corresponding to the fifth information in method 200).

[0441] Accordingly, UDM receives request message #1.

[0442] The request information #1 includes a logical tag #1, and the request information #1 is used to request information of the logical tag #1.

[0443] S503, UDM sends information of logical label #1 (corresponding to the sixth information in method 200).

[0444] Correspondingly, TMF receives the information of logical label #1.

[0445] Exemplarily, the information of the logical label #1 includes the logical label creation rule corresponding to the logical label #1.

[0446] Exemplarily, the information of the logical label #1 includes the identifiers of the M physical labels #1 corresponding to the logical label #1.

[0447] Optionally, the information of the logic tag #1 also includes a logic tag disable flag, and the logic tag disable flag indicates whether the logic tag #1 is disabled.

[0448] It should be noted that S502 and S503 are optional steps. In combination with the above method 300, if before executing method 500, UDM sends logical label #1 and the logical label creation rule corresponding to logical label #1 to TMF, method 500 may not include S502 and S503.

[0449] S504, TMF sends a physical tag inventory request.

[0450] Exemplarily, in S504, the TMF sends a physical tag inventory request (corresponding to the second information in method 200) to M physical tags #1.

[0451] S505, the physical tag sends a physical tag inventory response.

[0452] Accordingly, TMF receives a physical tag inventory response.

[0453] Exemplarily, in S505, the TMF receives a physical tag inventory response from physical tag #1.

[0454] The physical tag inventory response (corresponding to the third information or the third information #a in method 200) indicates whether the physical tag inventory is successful.

[0455] It should be understood that in S505, since some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive physical tag inventory responses from all physical tags #1.

[0456] Optionally, if in S503, TMF obtains the logical tag disable flag, and the logical tag disable flag indicates that logical tag #1 is not disabled, then method 500 executes S506 to S510 below. If the logical tag indicates that logical tag #1 is disabled, then TMF performs an inventory on M physical tags #1 according to the existing scheme. For example, each time TMF receives a physical tag inventory response from a physical tag #1, TMF sends an inventory response message to NEF / BOSS, and the inventory response message indicates whether the physical tag #1 is successfully inventoried.

[0457] S506, obtaining a logical label.

[0458] It should be understood that after TMF receives the physical tag inventory response from physical tag #1, TMF can determine whether the inventory of logical tag #1 is successful according to the inventory rule corresponding to logical tag #1. TMF can obtain the inventory rule corresponding to logical tag #1 from the received inventory request, or the inventory rule corresponding to logical tag #1 is predefined or preconfigured.

[0459] Taking the inventory rule corresponding to logical tag #1 as the inventory rule #1 described in S501 above as an example, if TMF receives a physical tag inventory response, and the physical tag inventory response indicates that the physical tag is disabled successfully, TMF determines that the inventory of logical tag #1 is successful.

[0460] It should be understood that if TMF determines that the logical tag #1 is not successfully counted, TMF can repeat S504 to S505 until TMF determines that the logical tag #1 is successfully counted. Optionally, TMF only repeats S504 to S505 for the physical tag #1 that has not been successfully counted, that is, in S504, TMF only sends a physical tag inventory request to the physical tag #1 that has not been successfully counted.

[0461] If TMF determines that the inventory of logical tag #1 is successful, TMF can save logical tag #1. Further, in S506, TMF obtains the logical tag, which is equivalent to querying whether logical tag #1 has been saved, or in other words, TMF obtains the logical tag, which is equivalent to determining whether the inventory of logical tag #1 is successful.

[0462] Optionally, if TMF has saved logical tag #1, TMF does not perform further processing after receiving the physical tag inventory response.

[0463] Optionally, if the TMF fails to obtain the logical tag, the method 500 executes S507 and S508.

[0464] S507, TMF sends a legality verification request.

[0465] Correspondingly, UDM receives the legality verification request.

[0466] Exemplarily, the legitimacy verification request sent by the TMF includes the identifier of the physical tag #1, and the legitimacy verification request is used to request a legitimacy verification of the physical tag #1.

[0467] S508, UDM sends a validity verification response.

[0468] Correspondingly, TMF receives a validity verification response.

[0469] Exemplarily, the validity check response indicates whether physical tag #1 passes the validity check.

[0470] It should be noted that S507 and S508 are optional steps. For example, if TMF has not performed a validity check on any of the M physical tags #1, method 500 can execute S507 and S508. If TMF has performed a validity check on at least one of the M physical tags #1, TMF will no longer perform a validity check on the remaining physical tags #1.

[0471] It should be understood that, in the case where M physical tags #1 correspond to one logical tag #1, the M physical tags #1 have an associated relationship. In the case where the M physical tags #1 have an associated relationship, if any one of the M physical tags #1 passes the legitimacy check, it can be considered that the M physical tags #1 have passed the legitimacy check. Therefore, when the network performs a legitimacy check on at least one of the M physical tags #1, it can achieve the purpose of performing a legitimacy check on the M physical tags #1 and avoid frequent signaling interactions caused by performing a legitimacy check on all the physical tags #1 among the M physical tags #1.

[0472] S509, TMF saves the logical label.

[0473] As described in S506, if the TMF determines that the inventory of logical tag #1 is successful, the TMF saves the logical tag #1.

[0474] Optionally, method 500 also includes S510.

[0475] S510, TMF sends an inventory success response (corresponding to the fourth information in method 200).

[0476] Accordingly, NEF / BOSS receives a successful inventory response.

[0477] The inventory success response indicates that the inventory for logical tag #1 was successful.

[0478] In an embodiment of the present application, by corresponding multiple physical labels to one logical label, each network element (for example, including UDM, TMF, NEF or BOSS) can interactively instruct each other to perform an inventory on the logical label, thereby achieving the purpose of performing an inventory on multiple physical labels, thereby avoiding frequent interactive instructions between each network element to perform an inventory on each physical label in the multiple physical labels.

[0479] In addition, different inventory rules can be defined for different inventory requirements, so as to minimize the signaling interaction process required to perform inventory while meeting the inventory requirements. For example, in a warehouse inventory scenario, if multiple physical tags on a terminal (or an object) are mapped to a logical tag, the inventory rule corresponding to the logical tag can be determined as inventory rule #1 mentioned in S501, thereby reducing the signaling interaction required for inventory. For another example, in a positioning scenario, the inventory rule corresponding to the logical tag can be determined as inventory rule #2 mentioned in S501, thereby ensuring the accuracy of positioning.

[0480] Combine the following Figure 6 , taking the first operation including degree as an example, the method provided in the embodiment of the present application is described.

[0481] Figure 6 600 is a schematic diagram of a communication method 600 provided in an embodiment of the present application. Figure 6 As shown, method 600 may include the following steps.

[0482] S601, NEF / BOSS sends a read logical tag request (an example of first information).

[0483] Correspondingly, TMF receives a request to read the logical tag.

[0484] The read logical tag request indicates that a read operation is performed on a logical tag, or a read operation is performed on a group of logical tags. For ease of description, the logical tag indicated by the read logical tag request is hereinafter referred to as logical tag #x.

[0485] Exemplarily, assume that the read logical tag request indicates that a read operation is performed on logical tag #1, or indicates that a read operation is performed on logical tag group #1. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0486] Optionally, the read logical tag request further includes at least one read rule (corresponding to the first condition in method 200), each read rule corresponds to a logical tag #x, and each read rule is used to determine whether the logical tag #x corresponding to the read rule is read successfully.

[0487] Exemplarily, the read rule includes one or more of the following: read rule #1, if a physical tag corresponding to the logical tag is read successfully, it indicates that the logical tag is read successfully; read rule #2, if all physical tags corresponding to the logical tag are read successfully, it indicates that the logical tag is read successfully; read rule #3, if the ratio of the number of successfully read physical tags to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), it indicates that the logical tag is read successfully; read operation rule #4, if the ratio of the number of successfully read physical tags to the number of all physical tags corresponding to the logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), it indicates that the logical tag is read successfully. The read rule can be customized by the enterprise or operator.

[0488] Below Figure 6 Taking the TMF in FIG. 6 as an example of providing services for logical label #1, the remaining steps included in method 600 are described.

[0489] S602, TMF sends request information #2 (corresponding to the fifth information in method 200).

[0490] Accordingly, UDM receives request information #2.

[0491] The request information #2 includes the logical tag #1, and the request information #2 is used to request the information of the physical tag corresponding to the logical tag #1.

[0492] S603, UDM sends the information of the physical label (corresponding to the sixth information in method 200).

[0493] Correspondingly, TMF receives the information of the physical tag.

[0494] Exemplarily, the TMF receives information #1 of M physical labels #1 corresponding to the logical label #1 (corresponding to the first label information of the M labels in method 200).

[0495] Exemplarily, the information #1 of the physical tag #1 includes one or more of the following: an identifier or a written flag of the physical tag #1 (corresponding to the second flag whose value is the first value in method 200).

[0496] It should be noted that S602 and S603 are optional steps. In combination with the above method 300, if before executing method 600, UDM sends logical label #1 and the logical label creation rule corresponding to logical label #1 to TMF, method 600 may not include S602 and S603.

[0497] S604, TMF counts or pages physical tags.

[0498] Exemplarily, in S604, the TMF counts or pages the M physical labels #1 corresponding to the logical label #1.

[0499] For example, TMF can initiate paging to active tags (such as Class C tags) among M physical tags #1, and / or, TMF can initiate inventory to passive tags (such as Class A tags or Class B tags) among M physical tags #1 to trigger M physical tags #1 to access the network.

[0500] S605, the physical tag is connected to the network.

[0501] Exemplarily, in S605, one or more physical tags among the M physical tags #1 are connected to the network.

[0502] S606, TMF sends a physical tag read instruction.

[0503] Exemplarily, in S606, TMF sends a physical tag read instruction (corresponding to the second information in method 200) to M physical tags #1, or sends a physical tag read instruction to a physical tag #1 connected to the network among the M physical tags #1, or sends a physical tag read instruction to a physical tag #1 with a written mark among the M physical tags #1.

[0504] S607, the physical tag sends feedback information #2.

[0505] Correspondingly, TMF receives feedback information #2.

[0506] Exemplarily, in S607, the TMF receives feedback information #2 from the physical tag #1.

[0507] Feedback information #2 (corresponding to the third information or third information #a in method 200) indicates whether the physical tag is read successfully.

[0508] It should be understood that in S607, since some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #2 from all the physical tags #1.

[0509] S608, TMF determines whether the logical tag is read successfully according to the logical tag reading rule.

[0510] Exemplarily, TMF determines whether the reading of logical tag #1 is successful according to the read rule corresponding to logical tag #1. TMF can obtain the read rule corresponding to logical tag #1 from the read logical tag request, or the read rule corresponding to logical tag #1 is predefined or preconfigured.

[0511] Taking the read rule corresponding to logical tag #1 as the read rule #1 described in S601 above as an example, if TMF receives a feedback message #2, and feedback message #2 indicates that the physical tag is disabled successfully, TMF determines that logical tag #1 is disabled successfully.

[0512] It should be understood that if TMF determines that logical tag #1 is not read successfully, TMF can repeat S604 to S607 until TMF determines that logical tag #1 is read successfully. Optionally, TMF repeats S604 to S607 only for physical tag #1 that is not read successfully, that is, in S604, TMF only counts or pages physical tag #1 that is not read successfully, and in S606, TMF only sends physical tag read instructions to physical tag #1 that is not read successfully.

[0513] If the TMF determines that the read of logical tag #1 is successful, the method 600 continues to execute S609.

[0514] S609, TMF sends a notification of successful logical tag reading.

[0515] Correspondingly, NEF / BOSS receives a logical tag read success notification.

[0516] Exemplarily, the logical tag read success notification (corresponding to the fourth information in method 400 ) sent by TMF indicates that the logical tag # 1 is read successfully.

[0517] Optionally, method 600 also includes S610.

[0518] S610, NEF / BOSS sends a notification response.

[0519] Accordingly, TMF receives a notification response.

[0520] The notification response indicates that the NEF / BOSS successfully received the logical tag read success notification.

[0521] In an embodiment of the present application, by corresponding multiple physical labels to one logical label, each network element (for example, including TMF, NEF or BOSS) can achieve the purpose of executing read instructions on multiple physical labels by interactively instructing the execution of read instructions on the logical labels, thereby avoiding frequent interactive instructions between each network element to execute read instructions on each physical label in the multiple physical labels.

[0522] Combine the following Figure 7 , taking the first operation including writing as an example, the method provided in the embodiment of the present application is described.

[0523] Figure 7 700 is a schematic diagram of a communication method 700 provided in an embodiment of the present application. Figure 4As shown, method 700 may include the following steps.

[0524] S701, NEF / BOSS sends a write logical tag request (an example of the twelfth information).

[0525] Accordingly, the UDM receives a write logical tag request.

[0526] The write logical tag request indicates that a write is performed on a logical tag, or a write is performed on a group of logical tags. For ease of description, the logical tag indicated by the write logical tag request is hereinafter referred to as logical tag #x.

[0527] Exemplarily, assume that the write logical tag request indicates that a write is performed on logical tag #1, or indicates that a write is performed on logical tag group #1. Logical tag group #1 includes logical tag #1. Logical tag #1 (corresponding to the first identifier in method 200) corresponds to M physical tags #1 (corresponding to the M tags in method 200), where M is an integer greater than 1.

[0528] Optionally, the write logical tag request further includes at least one write rule (corresponding to the first condition in method 200), each write rule corresponds to a logical tag #x, and each write rule is used to determine whether the write to the logical tag #x corresponding to the write rule is successful.

[0529] Exemplarily, the writing rules include one or more of the following: writing rule #1, if a physical tag corresponding to the logical tag is written successfully, it means that the logical tag is written successfully; writing rule #2, if all physical tags corresponding to the logical tag are written successfully, it means that the logical tag is written successfully; writing rule #3, if the ratio of the number of physical tags written successfully to the number of all physical tags corresponding to the logical tag is not less than threshold #1 (corresponding to the second threshold in method 200), it means that the logical tag is written successfully; writing rule #4, if the ratio of the number of physical tags written successfully to the number of all physical tags corresponding to the logical tag within time period #1 (corresponding to the first time period in method 200) is not less than threshold #2 (corresponding to the third threshold in method 200), it means that the logical tag is written successfully. The writing rules can be customized by the enterprise or operator.

[0530] S702, UDM sets a logical label to-be-written flag.

[0531] UDM sets the pending write flag for logical label #x.

[0532] Exemplarily, assume that the UDM sets a pending write flag for logical tag #1 (corresponding to tag #a with a value of #a1 in method 200), or that the UDM sets a pending write flag for at least one logical tag in logical tag group #1.

[0533] Optionally, the UDM stores the pending-write flag of the logical label #x in a non-volatile storage area.

[0534] It should be noted that S702 is an optional step.

[0535] S703, UDM sends a write logical tag response.

[0536] Accordingly, NEF / BOSS receives a write logic tag response.

[0537] The Write Logical Tag Response indicates that the UDM successfully received the Write Logical Tag Request.

[0538] For more description of S703, please refer to the above S403.

[0539] S704, UDM sends a notification of writing a logical label.

[0540] Accordingly, TMF receives a write logical tag notification.

[0541] Exemplarily, in S704, the UDM sends a write logical label notification to the TMF used to provide services for the physical label corresponding to the logical label #x.

[0542] The manner in which the UDM sends a notification for writing a logical label may refer to the manner in which the UDM sends a notification for disabling a logical label described in S404 above.

[0543] Exemplarily, assume that in S704, UDM sends a write logic label notification (corresponding to the first information in method 200) to the TMF used to provide services for logic label #1. Optionally, UDM also sends a write rule corresponding to logic label #1 to the TMF used to provide services for logic label #1.

[0544] Below Figure 7 Taking the TMF in FIG. 7 as an example of providing services for logical label #1, the remaining steps included in method 700 are described.

[0545] Optionally, if the TMF saves the context of the logical label #1, the method 700 also includes S705.

[0546] S705, TMF to logic tag to-be-written flag.

[0547] Exemplarily, in S705, TMF sets the to-be-written flag of logical label #1.

[0548] S706, TMF sends notification response #3.

[0549] Accordingly, the UDM receives a notification response #3.

[0550] Notification response #3 indicates that TMF received the logical tag write notification for logical tag #1.

[0551] S707, TMF counts or pages physical tags.

[0552] Exemplarily, in S707, the TMF counts or pages the M physical labels #1 corresponding to the logical label #1.

[0553] For more description of S707, please refer to the above S407.

[0554] S708, the physical tag is connected to the network.

[0555] Exemplarily, in S708, one or more physical tags among the M physical tags #1 are connected to the network.

[0556] S709, TMF sends a physical tag write instruction.

[0557] Exemplarily, in S709, the TMF sends a physical label write instruction (corresponding to the second information in method 200) to the M physical labels #1, or sends a physical label write instruction to a physical label connected to the network among the M physical labels #1.

[0558] Optionally, before executing S709, TMF may check whether the to-be-written flag of logical tag #1 is saved. If TMF saves the to-be-written flag of logical tag #1, TMF executes S709. If TMF does not save the to-be-written flag of logical tag #1, TMF does not process it.

[0559] S710, the physical tag sends feedback information #3.

[0560] Correspondingly, TMF receives feedback information #3.

[0561] Exemplarily, in S710, the TMF receives feedback information #3 from the physical tag #1.

[0562] Feedback information #3 (corresponding to the third information or third information #a in method 200) indicates whether the writing to the physical tag is successful.

[0563] It should be understood that in S710, since some of the M physical tags #1 are not connected to the network or are not powered, the TMF may not be able to receive feedback information #3 from all the physical tags #1.

[0564] Optionally, after receiving feedback information #3, TMF may also set a written flag (corresponding to the third flag with the third value in method 200) or a to-be-written flag (corresponding to the third flag with the second value in method 200) for physical tag #1 according to the content indicated by feedback information #3. Specifically, if feedback information #3 indicates that physical tag #1 is written successfully, TMF sets a written flag for physical tag #1; if feedback information #3 indicates that the physical tag is not written successfully, or the writing fails, TMF sets a to-be-written flag for physical tag #1.

[0565] S711, TMF determines whether the logical label is written successfully according to the logical label writing rule.

[0566] Exemplarily, TMF determines whether the writing to logical label #1 is successful according to the writing rule corresponding to logical label #1. TMF may obtain the writing rule corresponding to logical label #1 from UDM, or the writing rule corresponding to logical label #1 is predefined or preconfigured.

[0567] Taking the write rule corresponding to logical tag #1 as the write rule #1 described in S701 above as an example, if TMF receives a feedback message #3, and feedback message #3 indicates that the physical tag is written successfully, TMF determines that the logical tag #1 is written successfully.

[0568] It should be understood that if TMF determines that the logical tag #1 is not written successfully, TMF can repeat S707 to S710 until TMF determines that the logical tag #1 is written successfully. Optionally, TMF only repeats S707 to S710 for the physical tag #1 that is not written successfully, that is, in S707, TMF only counts or pages the physical tag #1 that is not written successfully, and in S709, TMF only sends a physical tag write instruction to the physical tag #1 that is not written successfully.

[0569] If the TMF determines that the write to logical tag #1 is successful, the method 700 continues to execute S712.

[0570] S712, TMF sends a notification of successful writing of the logical label.

[0571] Correspondingly, UDM receives a notification that the logical label is written successfully.

[0572] Exemplarily, the logical tag write success notification (corresponding to the fourth information in method 700 ) sent by TMF indicates that the write to logical tag # 1 is successful.

[0573] Optionally, the logical tag write success notification also indicates whether the write to each physical tag #1 in the M physical tags #1 is successful. For example, the logical tag write completion notification also includes a written flag or a to-be-written flag corresponding to each physical tag #1 in the M physical tags #1.

[0574] Optionally, method 700 also includes S713.

[0575] S713, UDM completes the logical label writing process.

[0576] Exemplarily, in S713, the UDM sets a written flag for the logical tag #1 (corresponding to the flag #a with a value of #a2 in method 200).

[0577] S714, UDM sends notification response #4.

[0578] Accordingly, TMF receives notification response #4.

[0579] Notification response #4 indicates that the UDM has received the logical tag write completion notification.

[0580] Optionally, if the TMF saves the context corresponding to the logical label #1, the method 700 also includes S715.

[0581] S715, TMF sets the logical label written flag.

[0582] Exemplarily, in S715, TMF sets a written flag for logical label #1.

[0583] Optionally, method 700 also includes S716 and S717.

[0584] S716, UDM sends a logical label writing completion report.

[0585] Accordingly, NEF / BOSS receives a logical tag writing completion report.

[0586] Illustratively, the logical tag write completion report indicates that the write to logical tag #1 was successful.

[0587] S717, NEF / BOSS sends a report response.

[0588] In response, the UDM receives a report response.

[0589] Exemplarily, the report response indicates that the NEF / BOSS has received the logical tag write completion report.

[0590] In an embodiment of the present application, by corresponding multiple physical labels to one logical label, each network element (for example, including UDM, TMF, NEF or BOSS) can achieve the purpose of executing write on multiple physical labels by interactively instructing the execution of write instructions on the logical label, thereby avoiding frequent interactive instructions between each network element to execute write instructions on each physical label in multiple physical labels.

[0591] In addition, when UDM and / or TMF sets the write flag and the pending write flag for the logical tag, regardless of whether the physical tag can receive the physical tag write instruction (or whether the write is successful), it can ensure that the network side can asynchronously process the writing of the logical tag.

[0592] It should be understood that the order of execution of the above processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. For example, S415 in method 400 can be executed before S412, or S415 can be executed after S412.

[0593] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0594] It can be understood that in the above-mentioned various method embodiments, the methods and operations implemented by the devices (such as the first device, the second device, and the third device) can also be implemented by components of the devices (such as chips or circuits).

[0595] Above, combined Figures 2 to 7 The communication method provided by the embodiment of the present application is described in detail. The above communication method is mainly introduced from the perspective of interaction between devices. It can be understood that in order to realize the above functions, the first device, the second device and the third device include hardware structures and / or software modules corresponding to the execution of each function.

[0596] It is understandable that, in order to implement the functions in the above embodiments, the first device, the second device and the third device include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0597] Figure 8 and Fig. 9 1 is a schematic block diagram of possible devices provided by the embodiments of the present application. These devices can be used to implement the functions of the terminal side or the network side in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0598] Figure 8 A schematic block diagram of a device provided in an embodiment of the present application. Figure 8The illustrated apparatus 1500 may include a processing module 1510 and a communication module 1520 .

[0599] In one possible design, the apparatus 1500 may be used to implement Figures 2 to 7 A communication method implemented by a first device in any of the embodiments shown. For example, the processing module 1510 is used to implement the processing-related steps performed by the first device in each method embodiment; the communication module 1520 is used to implement the sending and / or receiving steps performed by the first device in each method embodiment, such as receiving the first information, sending the second information, receiving the third information, or sending the fourth information.

[0600] Exemplarily, the communication module 1510 is used to: receive first information, the first information includes a first identifier, the first identifier corresponds to M tags, the first information indicates that a first operation is performed on the first identifier; M≥2, M is an integer; send second information to M1 tags among the M tags, the second information indicates that the first operation is performed on the M1 tags, M1≤M, and M1 is an integer; receive third information from each of the N second tags, the third information indicates that the first operation is successfully performed on the tag; the N tags belong to M1 tags, N≤M1, and N is an integer; send fourth information, the fourth information indicates that the operation is successfully performed on the first tag.

[0601] For a more detailed description of the processing module 1510 and the communication module 1520, please refer to Figures 2 to 7 The relevant description in the method embodiment shown is directly obtained and will not be repeated here.

[0602] In another possible design, the apparatus 1500 may be used to implement Figures 2 to 7 The communication method implemented by the second device in any of the embodiments shown. For example, the processing module 1510 is used to implement the processing-related steps performed by the second device in each method embodiment; the communication module 1520 is used to implement the sending and / or receiving steps performed by the second device in each method embodiment, such as receiving the twelfth information, sending the first information, and receiving one or more of the fourth information.

[0603] Exemplarily, the communication module 1520 is used to: receive twelfth information, the twelfth information includes a first identifier, the first identifier corresponds to M tags, and the twelfth information indicates that a first operation is performed for the one identifier; M≥2, M is an integer; send first information, the first information includes a first identifier, and the first information indicates that a first operation is performed for the first identifier; receive fourth information, and the fourth information indicates that the first operation is successfully performed for the first identifier.

[0604] For a more detailed description of the processing module 1510 and the communication module 1520, please refer to Figures 2 to 7 The relevant description in the method embodiment shown is directly obtained and will not be repeated here.

[0605] It should be noted that the communication module may also be referred to as a transceiver module, a transceiver unit, a transceiver, a transceiver, or a transceiver device, etc. The processing module may also be referred to as a processor, a processing board, a processing unit, or a processing device, etc. Optionally, the communication module is used to perform the sending operation and the receiving operation of the first device or the second device in the above method, and the device used to implement the receiving function in the communication module may be regarded as a receiving module, and the device used to implement the sending function in the communication module may be regarded as a sending module, that is, the communication module may include a receiving module and a sending module.

[0606] It should also be noted that, in one possible design, the aforementioned processing module and / or communication module may be implemented through a virtual module, for example, the processing module may be implemented through a software function unit or a virtual device, and the communication module may be implemented through a software function or a virtual device. In another possible design, the processing module or the communication module may also be implemented through a physical device, for example, if the communication device is implemented using a chip / chip circuit, the communication module may be an input-output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module may be an integrated processor or microprocessor or integrated circuit.

[0607] The division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each example of the embodiments of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0608] Fig. 9 This is a schematic diagram of the structure of a communication device provided by another embodiment of the present application. Fig. 9 As shown, the device 1600 includes a processing circuit 1610 and a communication circuit 1620. The processing circuit 1610 and the communication circuit 1620 are coupled to each other.

[0609] It can be understood that the processing circuit 1610 may be one or more processors, or may be all or part of the circuits with processing functions in one or more processors.

[0610] It is understandable that the communication circuit 1620 may be a transceiver or an input-output interface.

[0611] Optionally, the device 1600 may further include a memory 1630 for storing instructions executed by the processing circuit 1610 or storing input data required for the processing circuit 1610 to run the instructions or storing data generated after the processing circuit 1610 runs the instructions.

[0612] It is understandable that the memory 1630 may be located outside the processing circuit 1610 , or located inside the processing circuit 1610 .

[0613] As an example, the processing circuit 1610 is used to implement the function of the processing module 1510 mentioned above, and the communication circuit 1620 is used to implement the function of the communication module 1520 mentioned above.

[0614] As an example, the apparatus 1600 may be a communication device, or may be a chip used in a communication device.

[0615] When device 1600 is a communication device, the communication circuit may be a transceiver; when device 1600 is a chip, the communication circuit may be an input-output circuit, a bus, a pin or other types of communication interfaces, wherein the input circuit in the input-output circuit may be used for receiving, and the output interface may be used for sending.

[0616] The present application also provides a computer program product. When the computer program product is run on a processor, it can implement the communication method executed by the first device or the communication method executed by the second device in the above method embodiment.

[0617] The present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on a processor, the communication method executed by the second device in the above method embodiment or the communication method executed by the second device can be implemented.

[0618] The present application also provides a communication system, including the aforementioned second device and the second device, the first device can be used to implement the communication method implemented by the first device in the above method embodiment, and the second device can be used to implement the communication method implemented by the second device in the above method embodiment.

[0619] It is understood that the processor in the embodiments of the present application can be the following devices or all or part of the circuits in the following devices for processing functions: central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0620] The terms "unit", "module" and the like used in this specification may be used to represent a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution.

[0621] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0622] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0623] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0624] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0625] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0626] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0627] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0628] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, the method being applied to a communication device, characterized in that: include: Receive first information, where the first information includes a first identifier, the first identifier corresponds to M tags, and the first information indicates to perform a first operation on the first identifier; M≥2, M is an integer; Sending second information to M1 tags among the M tags, where the second information indicates that the first operation is performed on the M1 tags, where M1≤M and M1 is an integer; Receiving third information from each of the N tags, the third information indicating that the first operation is successfully performed on the tag; the N tags belong to the M1 tags, N≤M1, and N is an integer; Send fourth information, where the fourth information indicates that the first operation is successfully performed on the first identifier.

2. The method according to claim 1, characterized in that The M tags correspond to the first terminal; or, The M tags correspond to P terminals, and any two of the M tags are of the same type, and P is an integer greater than 1.

3. The method according to claim 1, characterized in that Send the fourth message, including: If the quantity of the third information meets the first condition, sending the fourth information; The first condition includes one or more of the following: The amount of the third information is not less than a first threshold; The ratio between the amount of the third information and M is not less than a second threshold; The amount of the third information is equal to M; A ratio between the amount of the third information received in the first time period and M is not less than a third threshold.

4. The method according to claim 3, characterized in that: The first information also indicates the first condition.

5. The method according to any one of claims 1 to 4, characterized in that Before sending the second information, the method further includes: Sending fifth information, the fifth information including the first identifier, the fifth information being used to request first tag information of the M tags, the first tag information of any one of the M tags being used to determine the tag; Sixth information is received, where the sixth information includes first tag information of the M tags.

6. The method according to any one of claims 1 to 4, characterized in that Before sending the second information, the method further includes: Sending fifth information, where the fifth information includes the first identifier, and the fifth information is used to request a correspondence between the first identifier and the M tags; receiving sixth information, wherein the sixth information includes a correspondence between the M tags and the first identifier; The M labels are determined according to the corresponding relationship.

7. The method according to any one of claims 1 to 4, characterized in that Before receiving the first information, the method further includes: Receive the seventh message; The seventh information includes the first identifier and first tag information of the M tags, and the first tag information of any one of the M tags is used to determine the tag; or, The seventh information includes a correspondence between the first identifier and the M tags, and the correspondence is used to determine the M tags.

8. The method according to claim 5 or 6, characterized in that: The sixth information further includes a first flag, and the first flag indicates that the first identification is not disabled.

9. The method according to claim 5, characterized in that The first operation includes reading, and the first tag information of a first tag among the M tags includes a second flag whose value is a first value, and the second flag whose value is the first value indicates that an overwrite operation is successfully performed on the first tag.

10. The method according to any one of claims 1 to 9, characterized in that The first operation includes reading, and the M1 tags are tags on which a write operation has been successfully performed among the M tags.

11. The method according to any one of claims 1 to 8, characterized in that The first operation includes inventory, and the legitimacy of any of the N tags is not verified. Before sending the fourth information, the method further includes: A validity check is performed on one of the N tags.

12. The method according to any one of claims 1 to 11, characterized in that The fourth information further indicates whether the first operation is successfully performed on each of the M tags.

13. The method according to claim 12, characterized in that The first operation includes disabling or writing; The fourth information includes the second tag information of the M tags, the second tag information of the fourth tag among the M tags includes a third flag whose value is a second value, and the second tag information of the fifth tag among the M tags includes a third flag whose value is a third value; wherein the third flag whose value is the second value indicates that the first operation is to be performed on the fourth tag, and the third flag whose value is the third value indicates that the first operation is successfully performed on the fifth tag.

14. The method according to any one of claims 1 to 13, characterized in that The first identification is determined based on identification of one or more tags among the M tags, where the identification of the tag includes one or more of the following: a tag identification, an electronic product code, or a user identification.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: receiving eighth information, the eighth information including a fourth identifier, the fourth identifier corresponding to a tag, and the eighth information indicating to perform a second operation on the fourth identifier; Sending ninth information to the tag corresponding to the fourth identifier, wherein the ninth information indicates that the second operation is performed on the tag corresponding to the fourth identifier; receiving tenth information from the tag corresponding to the fourth identifier, the tenth information indicating whether the second operation is successfully performed on the tag corresponding to the fourth identifier; An eleventh message is sent, where the eleventh message indicates whether the second operation is successfully performed on the fourth identifier.

16. The method according to any one of claims 1 to 15, characterized in that The communication device includes a tag management function entity or a chip in the tag management function entity.

17. A communication method, the method being applied to a communication device, characterized in that: include: receiving twelfth information, the twelfth information including a first identifier, the first identifier corresponding to M tags, and the twelfth information indicating to perform a first operation on the first identifier; M≥2, M is an integer; Sending first information, where the first information includes the first identifier, and the first information indicates that the first operation is performed for the first identifier; Fourth information is received, where the fourth information indicates that the first operation is successfully performed on the first identifier.

18. The method according to claim 17, characterized in that The M tags correspond to the first terminal; or, The M tags correspond to P terminals, and any two of the M tags are of the same type, and P is an integer greater than 1.

19. The method according to claim 17 or 18, characterized in that The fourth information further indicates whether the first operation is successfully performed on each of the M tags.

20. The method according to claim 19, characterized in that The first operation includes disabling or writing, The fourth information includes the second tag information of the M tags, the second tag information of the fourth tag among the M tags includes a third flag whose value is a second value, and the second tag information of the fifth tag among the M tags includes a third flag whose value is a third value; wherein the third flag whose value is the second value indicates that the first operation is to be performed on the fourth tag, and the third flag whose value is the third value indicates that the first operation is successfully performed on the fifth tag.

21. The method according to any one of claims 17 to 20, characterized in that The method further comprises: Thirteenth information is sent, where the thirteenth information indicates that the first operation is successfully performed on the first identifier.

22. The method according to any one of claims 17 to 21, characterized in that Before receiving the fourth information, the method further includes: Send the seventh message; The seventh information includes the first identifier and first tag information of the M tags, and the first tag information of any one of the M tags is used to determine the tag; or, The seventh information includes a correspondence between the M tags and the first identifier, and the correspondence is used to determine the M tags.

23. The method according to any one of claims 17 to 22, characterized in that The first identification is determined based on identifications of one or more tags among the M tags, where the identifications of the M tags include one or more of the following: a tag identification, an electronic product code, or a user identification.

24. The method according to any one of claims 17 to 23, characterized in that Before receiving the twelfth information, the method further includes: receiving fourteenth information, wherein the fourteenth information indicates determining the first identifier; The first identifier is determined and saved.

25. The method according to claim 24, characterized in that The fourteenth information further indicates a method of determining the first identifier based on identifiers of one or more tags among the M tags.

26. The method according to claim 24 or 25, characterized in that The saving of the first identifier includes: saving the association relationship between the first identifier and the M tags; or, The first identifier is saved in the signing information of each tag in the M tags.

27. The method according to any one of claims 17 to 26, characterized in that The communication device includes a data management network element, an application function, a chip in the data management network element, or a chip in the application function.

28. A communication device, characterized in that: The method comprises modules for implementing the method as claimed in any one of claims 1 to 16.

29. The communication device according to claim 28, characterized in that The communication device includes any one of the following: a tag management function entity or a chip.

30. A communication device, characterized in that: Comprising modules for implementing the method as claimed in any one of claims 17 to 27.

31. The communication device according to claim 30, characterized in that: The communication device includes any one of the following: a data management network element, an application function or a chip.

32. A computer-readable storage medium, characterized in that: The computer-readable storage medium is stored in a communication device, and the computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are executed, the method according to any one of claims 1 to 16 or the method according to any one of claims 17 to 27 is implemented.

33. A computer program product, characterized in that When the computer program product is run on a communication device, the method according to any one of claims 1 to 16 is implemented, or the method according to any one of claims 17 to 27 is implemented.

Images