CN118118873A

CN118118873A - Label management method and device

Info

Publication number: CN118118873A
Application number: CN202211490289.0A
Authority: CN
Inventors: 廖婷; 宗在峰; 周晓云; 郑小春
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-25
Filing date: 2022-11-25
Publication date: 2024-05-31
Also published as: WO2024109448A1

Abstract

The application provides a label management method and a device, in the method, when label operation is executed aiming at the coverage area of the same access network element and labels belonging to different operation requesters, a management function network element receives a plurality of requests from different operation requesters and then sends a request to the same access network element. The one request can request that a tag operation be performed on tags belonging to different operation requesters. The method and the device provided by the application can realize that the management function network element requests the access network element to execute the label operation aiming at the labels belonging to different operation requesters each time, and can improve the label management efficiency. Especially, aiming at the scene that a plurality of operation requesters all require to execute the label operation in the same time period, the response speed to the operation requesters can be improved, the service experience is improved, and a great amount of future requirements on label management are met as much as possible.

Description

Label management method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and apparatus for tag management.

Background

At present, when enterprises with demands for storage, logistics, fixed asset management, industrial manufacturing and the like manage articles, labels are generally attached to or embedded in related articles, and the labels are managed by using a passive internet of things consisting of the labels, readers and operation requesters. To achieve tag management, the reader and the operation requester typically need to be deployed in the same area as the tag, e.g., in a local area network. In order to improve the efficiency and the deployment cost of tag management, a passive Internet of things and a core network are combined, and a deployment reader is integrated in a base station; after the core network obtains the requirements of enterprises, checking the labels through the base station; therefore, the core network and the base station manage labels of multiple enterprises or multiple scenes of one enterprise.

With the improvement of technical development and environmental protection requirements and the increasing of the requirements on article management in the fields of logistics, storage and the like, the passive internet of things has a larger application and deployment prospect, and the passive internet of things is likely to cover the number of trillion devices in the future. How to improve the efficiency of the currently applicable label management process so as to meet a great deal of future requirements for label management as much as possible becomes a problem to be solved.

Disclosure of Invention

The application provides a method and a device for managing labels, which can improve the efficiency of label management and meet a great amount of demands for label management in the future as much as possible.

In a first aspect, a method of label management is provided, which may be performed by a management function element, where the management function element may be a component (e.g., a circuit, a chip, or a system-on-chip) or the like in a configuration management function element, which is not limited in this application.

The method comprises the following steps: the management function network element receives a first request from a first operation requester, wherein the first request is used for requesting to execute a label operation on at least one first label; the management function network element receives a second request from a second operation requester, the second request being used for requesting to execute the tag operation on at least one second tag; in case that the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, the management function network element sends a third request to the access network element, the third request being for requesting to perform the tag operation on the at least one first tag and the at least one second tag.

According to the scheme, when the label operation is required to be executed for the labels belonging to the same access network element and the labels belonging to different operation requesters, the management function network element receives a plurality of requests from the different operation requesters and then sends the requests to the same access network element for requesting the label operation of the labels belonging to the different operation requesters. Compared with the method that the access network element is requested to execute the label operation aiming at the label belonging to one operation requester each time, the scheme can realize that the management function network element requests the access network element to execute the label operation aiming at the labels belonging to different operation requesters, and can improve the efficiency of label management. Especially, aiming at the scene that a plurality of operation requesters all require to execute the label operation in the same time period, the response speed to the operation requesters can be improved, the service experience is improved, and a great amount of future requirements on label management are met as much as possible.

In addition, compared with a mode of adding the deployment of the access network elements so that N access network elements can simultaneously execute the label operation on the labels belonging to N operation requesters (namely, each access network element executes the label operation on the labels belonging to one operation requester), N is more than or equal to 2; the scheme can save the deployment of network elements of the access network and save the deployment cost.

In addition, compared with the management function network element which requests the access network element to execute the label operation on the labels belonging to different operation requesters through different messages, the above scheme can save signaling overhead.

In a possible implementation manner, the third request is a request message in a case where the information of the at least one first tag and the information of the at least one second tag may be transmitted in a combined manner, for example, in a case where the tag range of the at least one first tag and the tag range of the at least one second tag may be subjected to mask aggregation. This approach can further save signaling overhead.

In another possible implementation, the third request may be two request messages, such as a third request #a and a third request #b. Wherein the third request #a is for requesting to perform the tag operation on the at least one first tag, and the third request #b is for requesting to perform the tag operation on the at least one second tag. The method can be widely adaptive to the label range, and can also reduce the complexity of management function network element processing.

With reference to the first aspect, in certain implementations of the first aspect, the first request includes information of the at least one first tag, the second request includes information of the at least one second tag, and the method further includes: the management function network element determines a first area corresponding to the at least one first label according to the information of the at least one first label, and determines a second area corresponding to the at least one second label according to the information of the at least one second label; the management function network element determines that the at least one first tag and the at least one second tag both belong to the coverage area according to the first area and the second area.

With reference to the first aspect, in certain implementation manners of the first aspect, the first request includes information of a first area, where the first area corresponds to the at least one first tag, the second request includes information of a second area, where the second area corresponds to the at least one second tag, and the method further includes: the management function network element determines that the at least one first tag and the at least one second tag both belong to the coverage area according to the first area and the second area.

With reference to the first aspect, in certain implementations of the first aspect, the third request includes information of the at least one first tag and information of the at least one second tag, or the third request includes information of the first area and information of the second area.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the management function network element receives a result of the label operation performed on at least one third label by the access network element; in case the at least one third tag belongs to the at least one first tag, the management function network element sends the result to the first operation requester; or in case the at least one third tag belongs to the at least one second tag, the management function network element sends the result to the second operation requester.

According to the scheme, after the management function network element receives the result of the label operation of the third label from the access network element, the result is respectively sent to the operation requesting party corresponding to the third label. On the basis of improving the efficiency of label management and improving user experience, the processing complexity and the cost of an operation requester are not increased.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the management function network element sends first indication information and second indication information to the access network element, the first indication information is used for indicating that the at least one first label corresponds to a first frequency unit, the second indication information is used for indicating that the at least one second label corresponds to a second frequency unit, the first frequency unit and the second frequency unit are both contained in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit are not overlapped.

According to the scheme, the management function network element indicates to the access network element that the labels belonging to different operation requesters respectively correspond to the frequency units which are not overlapped with each other, so that the access network element can execute label operation on the labels belonging to different operation requesters at the frequency units which are not overlapped with each other, label management efficiency is further improved, and user experience is improved.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the access network element receives the first indication information and the second indication information from the management function network element; the access network element sends a third message and a fourth message in the first frequency unit and the second frequency unit respectively according to the first indication information and the second indication information, wherein the third message is used for activating the third tag belonging to the at least one first tag in the coverage area, and the fourth message is used for activating the third tag belonging to the at least one second tag in the coverage area.

According to the scheme, the management function network element indicates to the access network element that the labels belonging to different operation requesters respectively correspond to the frequency units which are not overlapped with each other, and the access network element can execute label operation on the labels belonging to different operation requesters at the frequency units which are not overlapped with each other, so that the label management efficiency is further improved, and the user experience is improved.

With reference to the first aspect, in certain implementation manners of the first aspect, in a case that the at least one third tag belongs to the at least one first tag, the method includes: in case the result comprises information indicating the first frequency unit; the management function network element sending the result to the first operation requester, comprising: the management function network element sends the result to the first operation request party according to the first indication information; or the at least one third tag belongs to the at least one second tag, comprising: in case the result includes the information indicating the second frequency unit; the management function network element sending the result to the second operation requester, comprising: and the management function network element sends the result to the second operation requester according to the second indication information.

According to the scheme, after the management function network element receives the label operation executing result from the access network element, the corresponding relation between the label and the frequency unit is used for judging which operation requesting party the label corresponding to the label belongs to, and then the label is sent to the corresponding operation requesting party. Therefore, the processing complexity and the cost of the operation requester are not increased on the basis of improving the label management efficiency and the user experience. And because the deployment scale of the network element of the access network is bigger than the deployment scale of the network element of the management function, the network element of the management function processes the deployment scale, and compared with the network element of the access network, the cost of upgrading the equipment is lower.

In a second aspect, a method of tag management is provided, which may be performed by an access network element, where the access network element may be a component (e.g., a circuit, chip, or chip system) or the like in a configuration access network element, which is not limited in this regard.

The method comprises the following steps: the access network element receives a third request from the management function network element, wherein the third request is used for requesting to execute label operation on the at least one first label and the at least one second label; the access network element sends a first message to a tag in a coverage area, wherein the first message is used for activating a third tag in the coverage area, and the third tag belongs to the at least one first tag or the at least one second tag; wherein the at least one first tag and the at least one second tag belong to different operation requesters, respectively.

According to the scheme, the access network element can execute the label operation for the labels belonging to different operation requesters in the same area, and compared with the case that the access network element is requested to execute the label operation for the labels belonging to one operation requester at one time, the label management efficiency can be improved. Especially, aiming at the scene that a plurality of operation requesters all require to execute the label operation in the same time period, the response speed to the operation requesters can be improved, the service experience is improved, and a great amount of future requirements on label management are met as much as possible.

With reference to the second aspect, in certain implementations of the second aspect, the third request includes information of the at least one first tag and information of the at least one second tag; the first message includes information of the at least one first tag and information of the at least one second tag; or the third request comprises information of a first area corresponding to the information of the at least one first tag and information of a second area corresponding to the information of the at least one second tag; the first message includes information of the first region and information of the second region.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the access network element receives a second message from the third tag, wherein the second message comprises information of the third tag; the access network element sends a result of performing the label operation on the third label to the management function network element, the result being used to indicate that the label operation has been performed on the third label.

With reference to the second aspect, in some implementations of the second aspect, the first message includes a third message and a fourth message, and the access network element sends the first message to a tag in a coverage area, including: the access network element sends a third message through the first frequency unit, wherein the third message is used for activating the third tag belonging to the at least one first tag in the coverage area; the access network element sends a fourth message through the second frequency unit, the fourth message being used to activate the third tag belonging to the at least one second tag within the coverage area, the third message and the fourth message being sent simultaneously.

According to the scheme, the access network element executes the label operation on the labels belonging to different operation requesters through the frequency units which are not overlapped with each other, so that the label management efficiency can be further improved, and the user experience is improved.

In a possible implementation manner, the access network element performs a label operation on at least one first label and at least one second label based on different frequency units according to its own capability.

In another possible implementation, the access network element performs a label operation for the at least one first label and the at least one second label based on different frequency units according to the capabilities of the at least one first label and the at least one second label, respectively.

In yet another possible implementation, the access network element performs a label operation for the at least one first label and the at least one second label based on the different frequency units based on the indication of the management function network element. For example, the method further comprises: the access network element receives first indication information and second indication information from the management function network element, wherein the first indication information is used for indicating that the at least one first label corresponds to a first frequency unit, the second indication information is used for indicating that the at least one second label corresponds to a second frequency unit, the first frequency unit and the second frequency unit are both contained in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit are not overlapped.

With reference to the second aspect, in certain implementations of the second aspect, the access network element receives a second message from a third tag, including: the access network element receives the second message from the third tag through the first frequency unit under the condition that the third tag belongs to the at least one first tag; or if the third tag belongs to the at least one second tag, the access network element receives the second message from the third tag through the second frequency unit.

According to the scheme, the access network element receives the messages from the labels belonging to different operation requesters through the frequency units which are not overlapped with each other, so that the access network element can send the result to the management function network element and indicate the information of the frequency units.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: in case the third tag belongs to the at least one first tag, the result comprises information indicating the first frequency unit; or the third tag belongs to the at least one second tag, the result comprising information indicating the second frequency unit.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: in case the result comprises information indicating the first frequency unit; the management function network element sending the result to the first operation requester, comprising: the management function network element sends the result to the first operation request party according to the first indication information; or the at least one third tag belongs to the at least one second tag, comprising: in case the result includes the information indicating the second frequency unit; the management function network element sending the result to the second operation requester, comprising: and the management function network element sends the result to the second operation requester according to the second indication information.

According to the scheme, the access network element sends the result to the management function network element and simultaneously indicates the information of the frequency unit, so that the management function network element can determine which operation requester the result is sent to according to the information of the frequency unit.

In a third aspect, a method of tag management is provided, which may be performed by a management function element, where the management function element may be a component (e.g., a circuit, a chip, or a system-on-chip) or the like in a configuration management function element, which is not limited in this regard.

The method comprises the following steps: the management function network element receives a first request from a tag operation requester, wherein the first request is used for requesting at least one first tag to execute tag operation; the management function network element sends a fourth request to the access network element according to the first request, wherein the fourth request is used for requesting the at least one first label to execute the label operation; in the event that the tag operation performed on the at least one first tag is not completed, the management function network element receives a second request from a second operation requester, the second request being for requesting the tag operation performed on the at least one second tag; in case that the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, the management function network element determines whether to suspend the tag operation performed on the at least one first tag according to the priority of the first operation requester and the priority of the second operation requester.

According to the scheme, the management function network element can provide differentiated services for different operation requesters according to the priorities, so that resources are coordinated to better meet the requirements of the operation requesters with different priorities. Particularly, for operation requesters with high priority, the label management efficiency can be improved, and the user experience is improved.

With reference to the third aspect, in certain implementations of the third aspect, the determining, by the management function network element, whether to suspend the tag operation performed on the at least one first tag according to the priority of the first operation requester and the priority of the second operation requester includes: in the case that the priority of the first operation requester is lower than the priority of the second operation requester, the management function network element determines to suspend the tag operation performed on the at least one first tag.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the management function network element sends a fifth request to the access network element, the fifth request being for requesting that the label operation be performed on at least one second label.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the access network element receives the fifth request from the management function network element; the access network element suspends the tag operation performed on the at least one first tag and performs the tag operation on the at least one second tag.

According to the scheme, the fifth request implicitly indicates the access network element to stop the label operation executed on the at least one first label, so that signaling overhead can be saved.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the management function network element sends a seventh request to the access network element for requesting to abort the label operation performed on the at least one first label.

According to the scheme, the seventh request display is used for indicating the access network element to stop the label operation performed on the at least one first label, so that the time for the access network element to stop the label operation performed on the at least one first label can be flexibly controlled.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the access network element receives the seventh request from the management function network element; the access network element aborts the tag operation performed on the at least one first tag, comprising: the access network element aborts the label operation performed on the at least one first label according to the seventh request.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the management function network element receiving a fifth message from the access network element, the fifth message being for indicating that the label operation performed on the at least one second label has ended; the first management network element sends a sixth request to the access network element, where the sixth request is used to instruct to perform the tag operation on the at least one first tag, or the sixth request is used to instruct to perform the tag operation on a first tag that is not performed with the tag operation in the at least one first tag.

In the above solution, the management function network element sends the sixth request after receiving the fifth message from the access network element, where the fifth message is used to indicate to the management function network element that the label operation performed on the at least one second label has ended, and the sixth message is used to indicate to the access network element to continue performing the label operation on the at least one first label. The management function network element determines when the access network element continues to execute the label operation on at least one first label, so that the management function network element can manage the access network element more perfectly, and the management function network element can coordinate the label management resources better, so as to better meet the demands of operation requesters with different priorities.

In a fourth aspect, a method of tag management is provided, which may be performed by an access network element, where the access network element may be a component (e.g., a circuit, chip, or chip system) or the like in a configuration access network element, which is not limited in this regard. The advantages of the fourth aspect may be seen from the advantages of the third aspect.

The method comprises the following steps: the access network element receives a fourth request from the management function network element, wherein the fourth request is used for requesting to execute label operation on the at least one first label; the access network element executes the label operation on the at least one first label according to the fourth request; in case the label operation performed on the at least one first label is not ended, the access network element receives a fifth request from the management function element, the fifth request being for requesting the label operation performed on at least one second label; the access network element aborts the label operation performed on the at least one first label; and the access network element executes the label operation on the at least one second label according to the fifth request, and the at least one first label and the at least one second label both belong to the coverage area of the access network element.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the access network element sending a fifth message to the management function element, the fifth message being for indicating that the label operation performed on the at least one second label has ended; the access network element performs the label operation on the at least one first label or performs the label operation on a first label of the at least one first label that is not performed with the label operation.

After finishing the label operation performed on the at least one second label, the access network element continues to perform the label operation performed on the at least one first label by default, or performs the label operation on the first label which is not performed with the label operation in the at least one first label by default, so that signaling overhead can be saved.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the access network element sending a fifth message to the management function element, the fifth message being for indicating that the label operation performed on the at least one second label has ended; the access network element receives a sixth request from the management function element, the sixth request being used for indicating to perform the tag operation on the at least one first tag, or the sixth request being used for indicating to perform the tag operation on a first tag that is not performed with the tag operation in the at least one first tag; and the access network element executes the label operation according to the sixth request.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the access network element receiving a seventh request from the management function element, the seventh request being for requesting to abort the tag operation performed on the at least one first tag; the access network element aborts the tag operation performed on the at least one first tag, comprising: the access network element aborts the label operation performed on the at least one first label according to the seventh request.

In a fifth aspect, a method of tag management is provided, which may be performed by an access network element, where the access network element may be a component (e.g., a circuit, chip, or chip system) or the like in a configuration access network element, which is not limited in this regard.

The method comprises the following steps: the access network element receives an eighth request from the operation requester, wherein the eighth request is used for indicating to execute a label operation on one label; the access network element sends a label selection message according to the eighth request, wherein the label selection message is used for indicating the label to respond to the label selection message, and the label selection message comprises first identification information of the label; the access network element receives a seventh message from the tag, the seventh message being for responding to the tag selection message, the seventh message including second identification information of the tag.

Optionally, the resource carrying the tag selection message is used to activate the tag.

In one possible implementation, the tag selection message implicitly indicates that the tag is responsive to the tag selection message; in another possible implementation, the tag selection message further includes an indication message, the indication message indicating that the tag is responsive to the tag selection message.

Optionally, the first identification information and the second identification information are the same. The first identification information or the second identification information may be an operator identification code corresponding to the tag, or an electronic product code of the tag.

Optionally, the first identification information and the second identification information are different. The tag corresponds to a plurality of identification information. For example, a tag has both a vendor-configured identity and an operator-assigned identity.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes: the access network element and the one tag do not perform a random access procedure until the access network element receives the seventh message from the tag.

In a sixth aspect, a method of tag management is provided, which may be performed by a tag, where the tag may refer to a component (e.g., a circuit, chip, or system-on-chip) or the like in a configuration tag, as the application is not limited in this respect.

The method comprises the following steps: a tag receives a tag selection message from an access network element, the tag selection message being used to instruct the tag to respond to the tag selection message, the tag selection message including first identification information of the tag; in response to the tag selection message, the tag sends a seventh message to the access network element, the seventh message including second identification information of the tag.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: before the first tag sends a seventh message to the access network element, the one tag and the access network element do not execute a random access procedure.

In a seventh aspect, a method of tag management is provided, which may be performed by an access network element, where the access network element may be a component (e.g., a circuit, a chip, or a system-on-chip) or the like in the access network element, which is not limited in this regard.

The method comprises the following steps: the access network element receives an eighth request from the operation requester, wherein the eighth request is used for indicating to execute a label operation on one label; the access network element sends a label selection message according to the eighth request, wherein the label selection message is used for indicating the label to respond to the label selection message, and the label selection message comprises first identification information of the label; the access network element receiving an eighth message from the tag, the eighth message being for responding to the tag selection message, the eighth message including authentication information; responding to the eighth message, the access network element sends a ninth message to the tag, wherein the ninth message comprises the verification information, and the ninth message is used for requesting the tag to verify; in response to the ninth message, the access network element receives a seventh message from the tag, the seventh message including second identification information of the tag.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the authentication information includes one or more of: random number, check value, secret key, public key, private key.

In an eighth aspect, a method of tag management is provided, which may be performed by a tag, where the tag may refer to a component (e.g., a circuit, a chip, or a system-on-chip) or the like in a configuration tag, which is not limited in this regard by the present application.

The method comprises the following steps: a tag receives a tag selection message from an access network element, wherein the tag selection message is used for indicating the tag to respond to the tag selection message, and the tag selection message comprises first identification information of the tag; in response to the tag selection message, the tag sends an eighth message to the access network element, the eighth message including authentication information; the tag receives a ninth message from the access network element, the ninth message being for responding to the eighth message, the ninth message including the authentication information, the ninth message being for requesting the tag to authenticate; and in case that the tag passes the verification, responding to the ninth message, and sending a seventh message to the access network element by the tag, wherein the seventh message comprises second identification information of the tag.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the authentication information includes one or more of: random number, check value, secret key, public key, private key.

A ninth aspect provides a communications device having functionality to implement any one of the first to fourth aspects, or a method in any one of the possible implementations of these aspects. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the functions described above.

In a tenth aspect, a communications apparatus is provided that includes a processor and a memory. Optionally, a transceiver may also be included. Wherein the memory is for storing a computer program, the processor is for invoking and running the computer program stored in the memory and controlling the transceiver to transceive signals to cause the communication device to perform the method as in any one of the first to fourth aspects, or any one of the possible implementations of these aspects.

In an eleventh aspect, there is provided a communication device comprising a processor and a communication interface for receiving data and/or information and transmitting the received data and/or information to the processor, the processor processing the data and/or information, and the communication interface further being for outputting the data and/or information after processing by the processor, such that the method as in any one of the first to fourth aspects, or in any one of the possible implementations of these aspects, is performed.

In a twelfth aspect, there is provided a computer readable storage medium having stored therein computer instructions which, when run on a computer, cause the method as in any one of the first to fourth aspects, or any possible implementation of these aspects, to be performed.

A thirteenth aspect provides a computer program product comprising computer program code which, when run on a computer, causes the method as in any one of the first to fourth aspects, or any possible implementation of any one of these aspects, to be performed.

A fourteenth aspect provides a communication system, comprising: a management function network element and an access network element; the management function network element is used for receiving a first request from a first operation requester, wherein the first request is used for requesting to execute a label operation on at least one first label, and is also used for receiving a second request from a second operation requester, and the second request is used for requesting to execute the label operation on at least one second label; in the case that the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, the management function network element sends a third request to the access network element, where the third request is used to request the at least one first tag and the at least one second tag to execute the tag operation; the access network element sends a first message to a tag within a coverage area, the first message being used to activate a third tag within the coverage area, the third tag belonging to the at least one first tag or the at least one second tag.

A fifteenth aspect provides a communication system, comprising: the management function network element receives a first request from a tag operation requester, wherein the first request is used for requesting at least one first tag to execute tag operation; the management function network element sends a fourth request to the access network element according to the first request, wherein the fourth request is used for requesting the at least one first label to execute the label operation; in the event that the tag operation performed on the at least one first tag is not completed, the management function network element receives a second request from a second operation requester, the second request being for requesting the tag operation performed on the at least one second tag; in the case that the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, the management function network element determines whether to suspend the tag operation performed on the at least one first tag according to the priority of the first operation requester and the priority of the second operation requester; the access network element executes the label operation on the at least one first label according to the fourth request; in case the label operation performed on the at least one first label is not ended, the access network element receives a fifth request from the management function element, the fifth request being for requesting the label operation performed on the at least one second label; the access network element aborts the label operation performed on the at least one first label; the access network element performs the label operation on the at least one second label according to the fifth request.

Drawings

Fig. 1 is a schematic diagram showing an example of a communication architecture to which the present application is applied.

Fig. 2 shows a schematic diagram of an example of a method 100 of random access of a tag.

Fig. 3 shows a schematic interaction diagram of a registration process 200.

Fig. 4 (a) shows a schematic diagram of a method 300 for tag management provided by the present application.

Fig. 4 (b) shows a schematic diagram of a method 310 for tag management provided by the present application.

Fig. 4 (c) shows a schematic diagram of a method 320 for tag management provided by the present application.

Fig. 5 shows a schematic diagram of a method 400 of tag management provided by the present application.

Fig. 6 shows a schematic diagram of a method 500 of tag management provided by the present application.

Fig. 7 shows a schematic diagram of a method 600 of tag management provided by the present application.

Fig. 8 shows a schematic diagram of a method 700 of tag management provided by the present application.

Fig. 9 is a schematic block diagram of a communication device provided by the present application.

Fig. 10 is another schematic block diagram of a communication device provided by the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical scheme provided by the embodiment of the application can be applied to various communication systems, such as: long term evolution (long termevolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunicationsystem, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) telecommunications system, fifth generation (5th generation,5G) system or New Radio (NR) or future 3GPP system, etc.

Generally speaking, the number of connections supported by the conventional communication system is limited and is also easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine typecommunication, MTC), vehicle-to-everything (vehicle to everything, V2X) communication (which may also be referred to as car-to-network communication), for example, vehicle-to-vehicle (vehicle to vehicle, V2V) communication (which may also be referred to as car-to-car communication), vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication (which may also be referred to as car-to-infrastructure communication), vehicle-to-pedestrian (vehicle to pedestrian, V2P) communication (which may also be referred to as car-to-person communication), vehicle-to-network (vehicleto network, V2N) communication (which may also be referred to as car-to network communication).

In order to facilitate understanding of the embodiments of the present application, some technical terms related to the present application are described below.

1. Label (tag):

Tags may also be referred to as terminals, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, user equipment, target terminals. The terminal may be a passive internet of things terminal or a tag. The terminal may be a passive device, which may be a passive tag that may collect energy to send and receive messages via backscatter technology, including but not limited to radio frequency identification (radio frequency identification, RFID), bluetooth, zigbee, etc. unpowered terminal tags. The terminal may also be a semi-passive device or an active device. The active device may be a device with a wireless transceiving function, such as a mobile phone (mobile phone), a tablet (pad), a computer with a wireless transceiving function, a virtual reality (virtualreality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G mobile communication system, or a terminal in a future evolution network, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

2. Reader (reader) or reader:

the reader interacts with the tag through radio frequency signals or wireless signals. In one possible implementation, the reader may send instructions from the server or application function to the tag, or the reader may send messages from the tag to the server or application function. In one possible implementation, the reader may obtain the information stored in the specified tag according to the instruction issued by the server. For example, if the operation is an inventory operation (or may be called an inventory operation), the reader acquires the identification information of the tag; the identification information may be a unique identification of the tag or a temporary identification of the tag. For example, if a read operation is performed, the reader reads the data in the tag memory area. Alternatively, in some cases where it is necessary to rewrite information stored in the tag, the reader may also have a write function, for example, if a write operation is performed, the reader writes data into the storage area of the tag. In addition, the reader may perform a deactivation operation on the tag. After the invalidation operation is performed, the tag is invalidated, and operations such as obtaining tag information, checking operation, reading operation, message interaction operation with the tag or writing operation can not be performed. In one possible implementation, the tag is disabled and cannot be executed to obtain the tag information, which may be understood that after the tag is disabled, the reader cannot obtain the tag information of the disabled tag. In another possible implementation, the tag failing to be able to perform a message interaction with the tag may be understood as the reader failing to interact with the failing tag after the tag fails. In the present application, the reader may be a terminal device, or may be an access network device, a station, eNodeB, gNodeB, an access backhaul (IAB) node, etc., and the present application does not limit the form of the reader.

Or it should be understood that the name of the reader is not limited in the present application, and the reader may be named as a reader or other names, that is, the names of the reader and the reader may be interchanged, where the reader and the reader have functions related to the reader in the present application, for example, the reader and the reader have functions of performing operations (such as acquiring tag information, checking operation, reading operation, writing operation, invalidation operation or message interaction operation with the tag, etc.) described in the present application on a terminal (such as a tag), acquiring charging related information and/or charging information, transmitting charging information to a charging function (charging function, CHF) network element, etc.

3. Operation requesting party: may be a server or an application function. In the embodiment of the present application, the operation requester may be understood as a device that sends an operation instruction, for example, the operation requester may be a server (server) or a passive internet of things (passiveIoT, P-IoT) server or an application function (application function, AF) or other devices that send an operation instruction. The operation requester may correspond to a class of users, which may include, without limitation, an enterprise, tenant, third party, or company. The operation request party corresponds to a certain type of user, and can be understood that the operation request party belongs to the type of user and is managed by the type of user.

4. Label operation:

(a) For inventory operations (or inventory operations) of tags, i.e., inventory existing conditions of tags or acquisition of tag identifications. When the operation requester requests inventory of a certain range, an inventory instruction may be sent to the reader, and the instruction may include area location information of inventory, identification information of the label, and the like. And after receiving the checking instruction, the reader executes the checking operation according to the identification information of the tag in the instruction. And after the completion of the checking operation performed by the reader, sending a checking result to the operation requester.

It will be appreciated that each tag will have an identification. In one possible implementation, the tag's identity may be a globally unique code, such as an electronic product code (electronic product code, EPC) or a terminal identity (terminalidentification, TID), or a temporary identity, such as an identity assigned by the network or an identity assigned by the operation requester. The identification information of the tag included in the inventory instruction may be an identification of one or more tags, such as a range of identifications of the tags, or the like. For example, the inventory instructions may include "inventory; tag identification: 1-100; a reader identification 1, a reader identification 2; new region of Shanghai Pudong. The instruction means to request a reader inventory tag with a range of tags ranging from 1 to 100 for a reader identification of 1 and a reader identification of 2 in the new region of Shanghai Pudong.

In one possible implementation, the inventory operation may further include a full tag inventory operation, i.e., obtaining the identity of tags within the coverage of the reader. It will be appreciated that this type of operation may take additional nomenclature to distinguish the above-described inventory operations, such as what is referred to as a full label inventory operation or what is referred to as a non-limiting inventory operation; or when the label identification range in the checking operation is not limited, the checking operation can be understood as obtaining the label identification within the coverage range of the reader.

(B) And reading the data of the tag. The tag may have a memory function, and its memory area may store data. If the operation request party wants to read the tag, a read instruction is sent to the reader, the reader reads the data from the tag storage area according to the instruction, and the data is sent to the server.

(C) And writing operation, namely writing data into the tag. The operation requester can send a writing instruction to the reader, and the reader performs writing operation on the tag according to the instruction and writes data into a storage area of the tag.

(D) And (3) disabling operation even if the tag is disabled. The operation requester may send a deactivation instruction to the reader, which may include a tag identification (i.e., identification information of the tag that is desired to be deactivated). The reader performs the invalidation operation on the tag according to the invalidation instruction, and after the operation is completed, the tag is invalidated and cannot be checked or other operations are performed.

(E) And acquiring information of the tag. In one possible implementation, the reader obtains or receives tag information sent by the tag. The reader transmits the tag information to the operation requester or the core network device. In one possible implementation manner, before the reader obtains the tag information sent by the tag, the reader may receive the operation instruction and send the operation instruction to the tag; the operation instruction may be from an operation requester or from a core network device, which is not limited by the present application. In one possible implementation, the tag information may include tag identification information and/or tag stored information.

(F) And interoperating with the tag's message. In one possible implementation, the reader sends a message to the tag from the operation requester (server or application function). In another possible implementation, the reader receives the message sent by the tag and sends the message from the tag to the operation requester (server or application function). In another possible implementation, the reader may interact with the tag, such as interacting with a random number, before receiving the message sent by the tag.

(G) A load (payload) is sent to the tag. In one possible implementation, the server or application function may send the load to the tag through the reader. After receiving the load from the server or the application function, the reader sends the load to the tag. In another possible implementation, the core network device may send the load to the tag through the reader. And after receiving the load from the core network equipment, the reader sends the load to the tag. For example, the load may be an instruction sent by the core network device or the server or the application function to the tag, data written by the core network device or the server or the application function to the tag, application layer information sent by the core network device or the server or the application function to the tag, or the like, or the load may be other information related to the tag, which is not limited in this application.

The label operation of the present application will be described mainly by way of example of the label counting operation, but the present application is not limited to the example of the label counting operation.

5. Passive internet of things (P-IoT):

The passive internet of things may also be referred to as the environment internet of things (a-IoT). Some network nodes of the passive internet of things may be passive. The nodes are not equipped with or mainly rely on power supply equipment such as batteries, and the nodes acquire energy from the environment and are used for sensing, transmitting, distributed computing and other functions of data. The passive internet of things architecture may include a passive tag, a reader (reader), and a server (server). The reader performs non-contact bidirectional data communication in a wireless radio frequency mode, and reads and writes an electronic tag or a radio frequency card (tag) in a wireless radio frequency mode, so that the aims of identifying a target and exchanging data are fulfilled.

At present, passive internet of things (IoT) internet of things terminals such as RFID mainstream are applied to the following application scenarios: (a) logistics and storage: including inventory and tracking of cargo, and monitoring of the environment and cargo status during transportation of high value cargo (e.g., vaccine); (a) industrial manufacture: including environmental and device status monitoring.

With the technical development and environmental protection requirements, the passive internet of things has a larger application deployment prospect, and the number of devices in the billions level is predicted to be covered in the future. The terminal functions, however, are simple, which results in the need to rely on external stimuli, typically from a reader (writer), to send information out. The current deployment has the characteristics of short communication distance between the card reader and the terminal, difficult management and the like.

It should be noted that, the communication method of the present application is illustrated by taking the passive internet of things as an example. The method of the application is not limited to the passive internet of things technology, and can be applied to other technologies, such as the semi-active internet of things technology, the semi-passive internet of things technology, the active internet of things technology and the like. The semi-active internet of things technology can be understood as a terminal in the middle can be a semi-active terminal. The terminal involved in the semi-passive internet of things technology may be a semi-passive terminal. The terminal involved in the active internet of things technology may be an active terminal.

Fig. 1 is a schematic diagram showing an example of a communication architecture to which the present application is applied. The function of the access network device for executing the reader is taken as an example, and a plurality of operation requesters are taken as application functions (application function, AF) network elements 1 and AF2 respectively as examples. For example, AF1 and AF2 can also be understood here as two different application scenarios. The AF1 and the AF2 may send, to the same management function network element, an instruction to perform a label operation on a label in the service area, and after receiving the instructions from the plurality of operation requesters, the management function network element instructs the access network device to perform the label operation on the label in the service area according to identification information of the label in the instructions. And after the access network equipment executes the label operation, feeding back the label operation result to the management function network element. And the management function network element feeds back the label operation result to the AF1 and the AF2 after processing the label operation result. Optionally, the communication between TMF and AF1 (or AF 2) may also be performed based on other network elements, such as network open (network exposurefunction, NEF) network elements, which is not limited by the present application.

The network elements involved in the communication architecture shown in fig. 1 are described below, respectively.

1. And (3) tag: see in particular the relevant description of the tags above.

2. An access network element: also known as access network devices or radio access network (radio access network, RAN) devices or access devices or base stations. The RAN can manage radio resources, provide access services for the ue, and complete forwarding of ue data between the ue and the core network, and may also be understood as a base station in the network.

An access network element in the present application may be understood as an example of an integrated deployment of a reader by an access network element, or an example of an access network element with a reader function. Wherein the reader function may be referred to the relevant description of the reader above. For example, with the new air interface wireless technology of integrating a card reader in a base station, it is understood that the inventory capability of the card reader (including reading, writing, destroying, locking operations on a tag) is integrated into the base station so that the base station can support the inventory capability. The passive tag is excited by the air interface wireless technology and then checked, so that the function similar to the reader-writer in ISO18000-6C is realized on the base station, the communication distance between the passive terminal and the card reader is increased, and the unified management of the operator base station is combined.

The access network element in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with a user equipment. The access network elements include, but are not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home evolved Node B, heNB, or home Node B, HNB), a baseband unit (baseBandunit, BBU), an Access Point (AP) in a wireless fidelity (WIRELESS FIDELITY, WIFI) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmissionand reception point, TRP), etc., may also be a gNB in a 5G mobile communication system, such as an NR system, or a transmission point (TRP or TP), one or a set of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system, or may also be a network Node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a centralized unit (centralized unit, CU) and DUs. The gNB may also include an active antenna unit (ACTIVE ANTENNA units, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resourcecontrol, RRC), packet data convergence layer protocol (PACKET DATA convergence protocol, PDCP) layer. The DU is responsible for handling physical layer protocols and real-time services, and implements functions of a radio link control (radio link control, RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. The information of the RRC layer is generated by the CU and finally becomes PHY layer information through PHY layer encapsulation of DU or is converted from the information of the PHY layer. Thus, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be sent by a DU, or by a du+aau. It is understood that the access network element may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network elements in the access network, or may be divided into access network elements in a Core Network (CN), which is not limited in the present application.

3. Application function network element: the network element represents the application function of a third party or an operator, is an interface for the third generation partnership project (3 ^rd generation partnership project,3 GPP) mobile communication system to acquire external application data, and is mainly used for transferring the requirement of an application side on a network side. For example, in fig. 1, the application function network element may be an AF network element, taking a 5G mobile communication system as an example.

4. Network opening network element: the apparatus may be used to enable 3GPP to securely provide network service capabilities, etc., to an AF (e.g., service capability server (services capability server, SCS), application server (application server, AS), etc.) of a third party. For example, in fig. 1, taking a 5G mobile communication system as an example, the network opening network element may be a NEF network element, and in future communication systems, such as 6G, the network opening network element may still be a NEF network element, or have other names, which is not limited by the present application. When the network opening network element is a NEF, the NEF may provide Nnef services to other network function network elements.

5. Management function network element: the management function network element performs information interaction with the reader (including an access network element with a reader function, a base station integrated deployment reader and the like) and the operation requesting party respectively, so that unified management of passive internet of things terminals of a plurality of operation requesting parties (such as a plurality of scenes or a plurality of enterprises and the like) can be realized.

In the embodiment of the application, the management function network element performs information interaction with one or more access network elements and a plurality of operation requesters respectively. Specifically, the management function network element is configured to receive tag operation instructions from the one or more operation requesters, and further configured to instruct the one or more access network elements to perform tag operations. Wherein the one or more access network elements comprise the access network elements referred to in the present application.

The management function network elements may be deployed, for example, alone or in combination with network elements such as access and mobility management functions (ACCESS AND mobility management function, AMF), user plane functions (user plane function, UPF), and the like. Or the management function network element may be a functional module integrated in the AMF network element. For example, the management function network element in the present application is further described by taking a label management network element (TAG MANAGEMENT function, TMF) as an example, but the present application is not limited to the name of the management function network element.

It is understood that with the improvement of technical development and environmental protection requirements and the increasing demands for article management in the fields of logistics, warehouse and industrial manufacturing, the passive internet of things will have a larger application deployment prospect, and the number of devices in the billions level will be predicted to be covered in the future. For example, as the demand for tag management increases, a large number of tag operation instructions from multiple operation requesters may be received for one management function network element in a short time. In order to meet a great deal of future demands for label management, how to improve the management efficiency of the current label management process becomes a problem to be solved. In view of this, the present application proposes a method for managing labels, so as to improve the management efficiency of the current label management process.

Before describing the tag management method provided by the present application in detail, a description will be briefly given of a random access procedure and a tag registration procedure of a tag that may be involved in the tag management method provided by the present application.

S101, the access network element sends a Query command to the tag, and accordingly, the tag receives the Query command from the access network element.

Wherein, the Query command comprises Q value, Q is more than or equal to 0 and Q is an integer. Illustratively, the access network element in S101 broadcasts a Query command to tags within the coverage area.

S102, the tag sends an inquiry command response to the access network element, and accordingly, the access network element receives the inquiry command response from the tag.

It should be appreciated that the probability of each tag selected within the coverage area replying to a Query command is 2 ^-Q. Illustratively, when q=4, the probability of each tag within the coverage area replying to a Query command isWhen q=0, the probability of each tag within the coverage area replying to the Query command is 1, i.e. a tag with Q value of 0 must reply to the Query command.

Wherein, the Query response command carries a random number #1. For example, the length of the random data #1 may be 16 bits, or may be other lengths, which is not limited in the present application.

S103, the access network element sends an Acknowledgement (ACK) message to the tag, and correspondingly, the tag receives the acknowledgement message from the access network element.

Wherein, the confirmation message carries the random number # 1. After receiving the ACK message, the passive tag that sent the random number in S102 acknowledges itself as being uniquely hit. It can be understood that in the random access process of this round, the tag is a tag that is successfully accessed randomly.

Optionally, S104, the tag sends identification information of the tag to the access network element, and accordingly, the access network element receives the identification information of the tag from the tag.

The identification information of the tag includes a Protocol Control (PC) code, EPC, cyclic redundancy check (cyclic redundancy check, CRC) and the like of the tag.

In the present application, the method 100 is performed by the tag and the access network element after being activated by the access network element. The access network element sends a label selection message to the label, and correspondingly, the label receives the label selection message from the access network element. The tag selection message includes a tag range for selecting tags indicated by the tag range or for filtering unselected tags within the coverage area. It is understood that a tag range includes identification information of one or more tags.

In a first possible implementation manner, for the method 100, in the case that the tag range includes identification information of a plurality of tags, Q > 0 included in the Query command in S101; in the case where the tag range includes identification information of one tag (hereinafter, referred to as tag #a), that is, the tag range is the identification information of the tag #a, q=0 included in the Query command in S101.

In a second possible implementation, in case the tag range includes identification information of one tag (hereinafter referred to as tag #a), i.e., in case the tag range is identification information of tag #a, the method 100 is replaced with a method 100' of tag access. The method 100' differs from the method 100 in that: s101 in the method 100 is not performed, and S102 in the method 100 is replaced with the identification information of the tag in S102', S104, which is carried in a seventh message for responding to the acknowledgement message.

And S102', the label sends an eighth message to the access network element, and accordingly, the access network element receives the eighth message from the label. The response message includes a random number #1.

In a third possible implementation manner, in the case where the tag range includes identification information of one tag (hereinafter referred to as tag #a), that is, in the case where the tag range is the identification information of the tag #a, the method 100 of random access is replaced with the method 100 of tag access. The method 100 "differs from S100 in that: s101 to S103 in the method 100 are not performed, and S104 in the method 100 is replaced with S104".

S104', the tag sends a seventh message to the access network element, and accordingly, the access network element receives the seventh message from the tag, and the seventh message is used for responding to the tag selection message.

Wherein the tag selection response message includes identification information of the tag #a. The access network element may determine, according to the identification information of the tag #a, that the tag selection response message is from the tag #a.

Compared with the random access method 100, the scheme can simplify the connection process between the tag and the access network element, thereby improving the tag access efficiency and further improving the tag management efficiency.

It will be appreciated that, assuming that the operation requester only instructs the access network element to inventory or inventory the tag, after the tag and the access network element (i.e. the reader) perform the method 100 or 100' or 100", the tag inventory may not be performed between the tag and the network side based on the registration procedure 200. The tag can send the identification information of the tag to the access network element through the last step in 100 or 100', and then the access network element sends the checking result to the core network; or the label inventory is performed between the label and the network side based on the registration procedure 200, in which case the last step in 100 or 100' or 100″ may be combined with S201. For example, taking S104 in combination with S201 as an example, the identification information of the tag in S104 is carried in the request message of registration in S201.

It should also be appreciated that, assuming that the tag also instructs the access network element to perform other tag operations (e.g., read operations or write operations) on the tag in addition to the inventory operations, the tag inventory is performed between the tag and the access network element based on the registration procedure 200 after the tag performs a random access procedure with the access network element (i.e., reader). After the label checking is performed, other label operations are performed between the label and the access network element.

Fig. 3 shows a schematic interaction diagram of a registration process 200.

S201, the label sends a registration request message to the access network element.

The registration request message carries identification information of the tag, for example, EPC of the tag.

S202, the access network element sends a registration request message to the TMF. Wherein the access network element transparently transmits the registration request message to the TMF.

And S203, the TMF selects a proper tag authentication network element to authenticate the tag, and the tag, the TMF and the tag authentication network element interact to complete the authentication flow. The tag authentication network element may be an operation requester that initiates a tag operation for the tag.

And S206, the TMF sends a registration response message to the access network element. Optionally, the registration response message is transmitted by the access network element to the TMF.

S207, the access network element sends a registration response message to the tag.

The following describes the methods 300-700 of tag management provided by the present application in connection with fig. 4-8.

Fig. 4 (a) shows a schematic diagram of a method 300 for tag management provided by the present application. In the method 300, after processing the tag operation requests from the multiple operation requesters, the management function network element requests the access network element to execute the tag operation. Wherein the first operation requester and the second operation requester among the plurality of operation requesters are described as an example. The first operation requester and the second operation requester may belong to two enterprises, respectively, e.g. the first operation requester belongs to enterprise 1 and the second operation requester belongs to enterprise 2. Or the first operation requester and the second operation requester may respectively belong to two different scenes, for example, the first operation requester is used for managing the tag belonging to the scene 1, and the second operation requester is used for managing the tag belonging to the scene 2. Or the first operation requester and the second operation requester may belong to the same enterprise or the same scene, and the first operation requester and the second operation requester perform a tag operation on at least one first tag and at least one second tag, respectively, wherein the at least one first tag and the at least one second tag are not repeated. The method 300 includes the steps of:

s301, the first operation request sends a first request to the management function network element, and accordingly, the management function network element receives the first request from the first operation requester.

Wherein the first request is for requesting that a tag operation be performed on at least one first tag.

It should be understood that in the present application, the first tag may be understood as a type of tag, which belongs to the first operation requester.

S302, the second operation request sends a second request to the management function network element, and accordingly, the management function network element receives the second request from the second operation requester.

Wherein the second request is for requesting that a tag operation be performed on at least one second tag.

It should be understood that in the present application, the second tag may be understood as a type of tag, which belongs to the second operation requester.

It should be understood that S301 may be performed before or after S302, or S301 and S302 may be performed simultaneously.

It should also be appreciated that the management function network element processes the first request and the second request to determine an access network element performing the tagging operation and a third request sent to the access network element performing the tagging operation.

Example 1, an access network element performing a label operation may be determined as follows: the management function network element judges whether the region of at least one first label and the region of at least one second label are overlapped; further, in the case that the region to which the at least one first label belongs and the region to which the at least one second label belongs partially or completely overlap, the management function network element corresponds to the access network element according to the overlapping region of the two regions. For example, whether part or all of the overlapping area of the two areas belongs to the coverage area of the same access network element.

Several possible implementations of example 1 are given below.

Example 1-1, the first request includes information of at least one first tag and the second request includes information of at least one second tag. The management function network element determines a first area corresponding to the at least one first label according to the information of the at least one first label, and determines a second area corresponding to the at least one second label according to the information of the at least one second label. The management function network element determines that at least one first label and at least one second label belong to the coverage area of the access network element according to the first area and the second area. Thus, the first management network element determines that a label operation is performed by the access network element on the at least one first label and the at least one second label.

1-2, The first request includes information of a first area, where the first area is an area corresponding to at least one first tag, the second request includes information of a second area, where the second area is an area corresponding to at least one second tag, and the management function network element determines that the at least one first tag and the at least one second tag both belong to a coverage area according to the first area and the second area. Thus, the first management network element determines that a label operation is performed by the access network element on the at least one first label and the at least one second label.

Optionally, in examples 1-1 and 1-2, the management function network element pre-configures a correspondence between information of the third area and information of the one or more access network elements. Wherein the third region comprises the first region and the second region, and the one or more access network elements comprise access network elements.

Examples 1-3, including information of at least one first tag, the second request includes information of at least one second tag. The management function network element determines an access network element #1 corresponding to the at least one first label according to the information of the at least one first label, and determines an access network element #2 corresponding to the at least one second label according to the information of the at least one second label. The management function network element determines the access network element shared by the access network element #1 and the access network element #2 as the network element for executing the label operation.

Examples 1-4, the first request includes information of a first region, the first region being a region corresponding to at least one first tag, and the second request includes information of a second region, the second region being a region corresponding to at least one second tag. The management function network element determines an access network element #1 corresponding to the at least one first label according to the information of the at least one first label, and determines an access network element #2 corresponding to the at least one second label according to the information of the at least one second label. The management function network element determines the access network element shared by the access network element #1 and the access network element #2 as the network element for executing the label operation.

Optionally, in examples 1-3 and 1-4, the management function network element pre-configures a correspondence between information of the one or more labels and information of the one or more access network elements. Wherein the one or more labels comprise at least one first label and at least one second label, and the one or more access network elements comprise network elements performing label operations.

Examples 1-5, the first request includes information of a first region and information of at least one first tag, and the second request includes information of a second region and information of at least one first tag, wherein the at least one first tag corresponds to the first region and the at least one second tag corresponds to the second region. The steps performed by the management function network element may be referred to as the steps performed by the management function network element in examples 1-2 or examples 1-3.

In case the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, S303 is performed.

S303, the management function network element sends a third request to the access network element, and correspondingly, the access network element receives the third request from the management function network element.

Alternatively, the management function network element may determine a plurality of access network elements performing the label operation, where the plurality of access network elements performing the label operation includes an access network element.

Wherein the third request is for requesting that a tag operation be performed on the at least one first tag and the at least one second tag.

Example 2, the third request may have a number of possible implementations.

Example 2-1, the third request includes information of at least one first tag and information of at least one second tag. Wherein example 2-1 may be combined with example 1-1, example 1-3, or example 1-4. It will be appreciated that the third request may be a message in case the information of the at least one first tag and the information of the at least one second tag may be transmitted in combination, for example in case the tag range of the at least one first tag and the tag range of the at least one second tag may be mask aggregated. Or the third request may be two messages sent simultaneously, for example comprising a third request #1 and a third request #2, wherein the third request #1 comprises information of at least one first tag and the third request #2 comprises information of at least one second tag.

Example 2-2, the third request includes information of the first region and information of the second region. Wherein example 2-2 may be combined with examples 1-1, examples 1-3, and examples 1-4. It will be appreciated that the third request may be one message or two messages sent simultaneously. For example, a third request #1 and a third request #2, wherein the third request #1 includes information of at least one first tag and the third request #2 includes information of at least one second tag.

S304, the access network element sends a first message to the tag in the coverage area.

Wherein the first message activates a third tag within the coverage area, the third tag belonging to at least one first tag or at least one second tag. For example, the access network element broadcasts a first message. As another example, the first message may be a tag selection message.

Example 3 the first message may have a number of possible implementations. Example 3-1, the first message includes information of the at least one first tag and information of the at least one second tag. Example 3-2, the first message includes information of the first region and information of the second region. Wherein example 3-1 may be combined with example 2-1 or example 2-2, and example 3-1 may be combined with example 2-1 or example 2-2. In the case where example 3-1 is combined with example 2-2, or where example 3-2 is combined with example 2-1, the access network element pre-configures a correspondence between at least one first label and the first area, and a correspondence between at least one second label and the second area.

It is to be appreciated that after the third tag is activated, the interaction between the third tag and the access network element may be found in the description related to method 100, method 100', method 100 "and method 200 above.

According to the scheme, when the label operation is required to be executed for the coverage area of the network element belonging to the same access network and the labels belonging to different operation requesters, the management function network element receives a plurality of requests from different operation requesters and then sends a request to the network element of the same access network. The one request can request that a tag operation be performed on tags belonging to different operation requesters. Compared with the method that the access network element performs the label operation on the label belonging to one operation requester every time the access network element is requested, the label management efficiency can be improved. Especially, aiming at the scene that a plurality of operation requesters all require to execute the label operation in the same time period, the response speed to the operation requesters can be improved, the service experience is improved, and a great amount of future requirements on label management are met as much as possible.

Optionally, the method 300 further comprises: in the label operation performed by the access network element on the labels in the coverage area, after the label belonging to at least one first label or at least one second label (hereinafter referred to as a third label) is activated, a message (hereinafter referred to as a second message) is also sent to the access network element. And after receiving the information from the third label, the access network element reports the result of executing the label operation to the management function network element. Then, in the results of performing the label operation on the at least one third label, the management function network element sends the result corresponding to the label belonging to the first operation requester, and sends the result corresponding to the label belonging to the second operation requester. Specific examples are given below in connection with S305 to S307 b.

S305, the at least one third tag sends a second message to the access network element, and accordingly, the access network element receives the second message from the at least one third tag.

Wherein the second message includes information of the third tag. It should be understood that in the present application, the third tag may be understood as a type of tag belonging to the coverage area of the access network element and belonging to the first operation requester or to the second operation requester.

Illustratively, the third tag is a random access successful tag, so that S305 follows the method 100. For example, where the access network element performs a label operation on labels within coverage area with reference to method 100, the second message may be a separate message. For another example, in the case where the access network element performs the label operation on the label in the coverage area with reference to the methods 100 and 200, the second message may be the registration request message in step S201.

S306, the access network element sends a result of performing the label operation on the third label to the management function network element, and the management function network element receives a result of performing the label operation on the third label from the access network element, wherein the result is used for indicating that the label operation has been performed on the third label.

Specifically, the access network element may report to the first management network element once every time the access network element receives the second message. For example, the second message in S305 is the registration request message in S201, and the access network element sends the result of performing the label operation on the third label to the management function network element based on the registration request message in S202. Or the access network element may report the result to the first management network element together after the label operation is completed, e.g. the second message in S305 is a separate message instead of the registration request message in S201.

S307 includes S307a or S307b.

S307a, in case the at least one third tag belongs to the at least one first tag, the management function network element sends the result to the first operation requester.

S307b, in case the at least one third tag belongs to the at least one second tag, the management function network element sends the result to the second operation requester.

For example, the management function network element may determine, once each time a result corresponding to a third tag is received, whether the third tag belongs to at least one first tag or at least one second tag. Or the management function network element can also judge after receiving the results corresponding to all the third labels from the access network element. For another example, the result of performing the tag operation on the third tag includes information of the third tag, such as a tag identification of the third tag, and the like.

There are a number of implementations as to how the management function network element determines whether the third tag belongs to the at least one first tag or the at least one second tag. For example, the management function network element may make the above determination according to whether the tag identification of the third tag is within the tag set of at least one first tag or the tag set of at least one second tag. The management function network element can determine that the third tag belongs to the first tag, provided that the tag identification of the third tag belongs to the tag set of at least one first tag. Or, for example, the management function network element may determine according to whether the first n bits of the tag identifier of the third tag are identical to the first n bits of the tag identifier of the first tag, and whether the first n bits of the tag identifier of the third tag are identical to the first n bits of the tag identifier of the second tag. Assuming that the first n of the tag identification of the third tag is the same as the first n of the tag identification of the second tag, the management function network element can determine that the third tag belongs to the second tag. Wherein n is a positive integer. The tag identification of the third tag herein may be, for example, the EPC code or TID of the third tag.

According to the scheme, the deployment scale of the access network element is larger than the deployment scale of the management function network element, and compared with the deployment scale of the access network element, the deployment scale of the access network element is processed by the management function network element, the cost of upgrading equipment is lower.

It should be appreciated that in the above steps of the method 300, the access network element performs tag operations on tags within the coverage area one by one. Optionally, the method 300 may further include: the air interface resource interacted by the access network element and the label in the coverage area corresponds to different frequency units, and the labels belonging to different operation requesters correspond to different frequency units respectively. The access network element may then also perform tag operations individually for the tags within each frequency unit, respectively. The frequency unit referred to in the present application may be understood as one or more frequency points, one or more frequency bands, one or more frequency ranges, one or more frequency domain positions, etc.

And the air interface resource of the interaction between the access network element and the tag in the coverage area is a third frequency unit. For example, the third frequency unit may be a frequency resource belonging to the passive internet of things dedicated, or may be a part of a frequency resource belonging to the 3GPP system, and the part of the frequency resource may be used by the passive internet of things alone or shared by the passive internet of things and a network element in the 3GPP system.

For example, at least one first tag corresponds to a first frequency unit, at least one second tag corresponds to a second frequency unit, and the first frequency unit and the second frequency unit do not overlap in the frequency domain. And the first frequency unit and the second frequency unit are both contained in a third frequency unit applicable to the network element of the access network. The at least one first tag corresponding to the first frequency unit may be understood as the first tag interacting with the access network element based solely on information indicative of the first frequency unit. Similarly, the at least one second tag corresponding to the second frequency unit may be understood as the first tag interacting with the access network element based solely on information indicative of the second frequency unit. Specifically, the information indicating the first frequency unit may be an identification of the first frequency unit, or an identification of a cell corresponding to the first frequency unit, or an identification of a sector corresponding to the first frequency unit. Similarly, the information indicating the second frequency unit may be an identification of the second frequency unit, or an identification of a cell corresponding to the second frequency unit, or an identification of a sector corresponding to the second frequency unit.

Further specific examples are given below for steps S301 to S307b of the method 300.

Step S303 may further include: step 1, a management function network element sends first indication information and second indication information to an access network element, and correspondingly, the access network element receives the first indication information and the second indication information from the first management network element.

The first indication information is used for indicating that at least one first tag corresponds to a first frequency unit, and the second indication information is used for indicating that at least one second tag corresponds to a second frequency unit.

It should be appreciated that the first indication information may be displayed to indicate that the first tag corresponds to the first frequency unit, e.g. the first indication information comprises a correspondence of at least one first tag to the first frequency unit. Or the first indication information may implicitly indicate that the first tag corresponds to the first frequency unit. The following is a description of examples 4-1 to 4-4.

Example 4-1, the first indication information includes correspondence between identification information of at least one first tag and one or more cells belonging to a coverage area of a network element of the access network. The management function network element may determine at least one first tag according to the identification information of the at least one first tag, and determine frequency resources corresponding to one or more cells as first frequency units.

Example 4-2, the first indication information includes correspondence between identification information of at least one first tag and one or more sectors belonging to a coverage area of the access network element. The management function network element may determine at least one first tag according to the identification information of the at least one first tag, and determine frequency resources corresponding to one or more sectors as the first frequency unit. It should also be understood that a cell in the present application may include multiple sectors. For example, the cell #1 includes a plurality of sectors, and the frequency resource corresponding to the sector #1 in the plurality of sectors can be understood as a part of the frequency resources corresponding to the cell # 1. The sectors herein may also have other names, as the application is not limited in this regard.

In example 4-3, the first indication information includes a correspondence between information of the first area and one or more cells, where the management function network element determines identification information of at least one first tag according to the information of the one or more first areas, and determines frequency resources corresponding to the one or more cells as the first frequency unit.

Example 4-4, the first indication information includes information of the first region and a correspondence of one or more sectors. The management function network element determines the identification information of at least one first tag according to the information of one or more first areas, and determines the frequency resource corresponding to one or more sectors as a first frequency unit.

It should also be appreciated that the second indication information may be displayed indicating that the second tag corresponds to the second frequency unit, e.g. the second indication information comprises a correspondence of at least one second tag to the second frequency unit. Or the second indication information may implicitly indicate that the second tag corresponds to the second frequency unit. The implementation is similar to the implementation that the first indication information implicitly indicates that the first tag corresponds to the first frequency unit, and specific reference may be made to examples 4-1 to 4-4.

For example, the first indication information and the second indication information may be separately transmitted; may also be sent with the third request, such as carried in the third request.

Optionally, before step 1, the management function network element acquires the first indication information and the second indication information. For example, the management function network element pre-configures the first indication information and the second indication information. For another example, the management function network element obtains the first indication information from the first operation requester and requests Fang Huoqu the second indication information from the second operation.

Step 2 may be a specific example of step 304. Wherein the first message comprises a third message and a fourth message.

Step 2, the access network element sends a third message and a fourth message in the first frequency unit and the second frequency unit respectively according to the first indication information and the second indication information, wherein the third message is used for activating the third tag belonging to the at least one first tag in the coverage area, and the fourth message is used for activating the third tag belonging to the at least one second tag in the coverage area.

The access network element illustratively broadcasts a third message at the first frequency unit according to the first indication information, and the access network element broadcasts a fourth message at the second frequency unit according to the second indication information. One or more of the at least one first tag receives a third message from the access network element based on the first frequency element within the coverage area of the access network element. One or more of the at least one second tag receives a third message from the access network element based on the second frequency element within the coverage area of the access network element.

It will be appreciated that the message content of the third message and the fourth message are different. For example, the object to be subjected to the tag operation indicated by the third message is at least one first tag, and the object to be subjected to the tag operation indicated by the fourth message is at least one second tag.

In one possible implementation, the third message and the fourth message are sent simultaneously.

Step 3 is a specific example of step S305.

And 3, under the condition that the third tag belongs to at least one first tag, the third tag sends a second message to the access network element through the first frequency unit, and correspondingly, the access network element receives the second message from the third tag through the first frequency unit.

And under the condition that the third tag belongs to at least one second tag, the third tag sends a second message to the access network element through the second frequency unit, and correspondingly, the access network element receives the second message from the third tag through the second frequency unit.

Step 4 and step 5 are a specific example of S306 and S307.

S306 may further include: and 4a, the access network element determines that the third tag belongs to at least one first tag according to the first indication information. The access network element also sends information indicating the first frequency unit to the management function network element, and correspondingly, the management function network element receives information indicating the first frequency unit from the access network element.

Wherein the information indicating the first frequency unit may be transmitted together with a result of performing a tag operation on the third tag or may be transmitted separately.

Or S306 may further include: and 4b, the access network element determines that the third label belongs to at least one second label according to the first indication information, and correspondingly, the management function network element receives information for indicating the second frequency unit from the access network element.

Wherein the information indicating the second frequency unit may be transmitted together with a result of performing a tag operation on the third tag or may be transmitted separately.

Step 5a is a specific example of S307 a. Step 5b is a specific example of S307 b.

And step 5a, the management function network element sends the result to the first operation requester according to the information for indicating the first frequency unit.

And step 5b, the management function network element sends the result to the second operation requester according to the information for indicating the second frequency unit.

It can be appreciated that, in the method 300, the management function network element receives the request #1 from one operation requester, and may not immediately instruct the access network element to perform the tag operation corresponding to the request #1, where a large number of tag operation instructions from multiple operation requesters may be received in a short time for one management function network element. Instead, after receiving at least one request #2 of the other operation requesters, the management function network element processes the request #1 and the at least one request #2, and instructs the access network element to perform the tag operation. For example, the management function network element is preconfigured with a time period and a start time. And starting from the starting time, every other time period, the management function network element processes the received request #1 and at least one request #2 in the time period and then instructs the access network element to execute the label operation.

For the above case, the present application also provides methods 310 and 320. In the method 310 and the method 320, after the management function network element receives the request #1 from an operation requester, the access network element may be instructed to perform the tag operation corresponding to the request # 1. In the case that the tag operation corresponding to the request #1 has not been executed, the management function network element receives at least one request #2 of the other operation requesters. Further, in a possible implementation manner, in the method 310, the management function network element determines whether to suspend the tag operation corresponding to the request #1 according to the priorities of the one operation requester and other operation requesters; in another possible implementation manner, in the method 320, after the management function network element receives a request #2, the management function network element may also instruct the access network element to execute the tag operation corresponding to the request #2 immediately, and the access network element determines whether the tag operations corresponding to the request #1 and the request #2 can be executed simultaneously, or whether to suspend the tag operation corresponding to the request # 1. Or in the method 320, after receiving a request #2, the management function network element immediately instructs the access network element to execute the label operation corresponding to the request #2, and the access network element directly executes the label operation corresponding to the request #2 without executing the foregoing judgment. Method 310 and method 320 are described below in conjunction with (b) of fig. 4 and (c) of fig. 4, respectively.

Fig. 4 (b) shows a schematic diagram of a method 310 for tag management provided by the present application. Wherein, for the description related to the first operation requester and the second operation requester, reference may be made to the method 300. The method 310 includes the steps of:

S311, the first operation request sends a first request to the management function network element, and accordingly, the management function network element receives the first request from the first operation requester.

Wherein the first request is for requesting that a tag operation #1 be performed on at least one first tag.

And S312, the management function network element sends a fourth request to the access network element according to the first request, and correspondingly, the access network element receives the fourth request from the management function network element.

Wherein the fourth request is for requesting that the tag operation #1 be performed on at least one first tag.

For example, the management function network element performs S312 upon receiving the first request. Or the management function network element starts timing from the reception of the first request, and when the time reaches the time threshold #2, it is assumed that the first management network element has not received a request for performing a tag operation on tags other than the first tag except for the first request, and S312 is performed.

And S313, the access network element executes a label operation #1 on at least one first label according to the fourth request.

The manner in which the tagging operation #1 is performed may be found in the description above with respect to method 100, method 100', method 100", and method 200. It will be appreciated that prior to S313, the access network element sends a tag selection message #1 to at least one first tag, or the access network element broadcasts the tag selection message #1 in the coverage area. The tag selection message #1 includes identification information of at least one first tag or information of a first area.

In case the label operation #1 performed by the access network element on the at least one first label is not ended, S314 is performed.

S314, the second operation request sends a second request to the management function network element, and accordingly, the management function network element receives the second request from the second operation requester.

Wherein the second request is for requesting that label operation #2 be performed on at least one second label.

For example, the management functional network element determines whether the label operation #1 performed by the access network element on the at least one first label is ended according to whether information for indicating the end of the label operation is received by the access network element.

S315, the management function network element determines whether to suspend the label operation #1 executed on at least one first label according to the priority of the first operation requester and the priority of the second operation requester.

Example 5-1, priority here may be understood as the priority of the level of service subscribed by the different operation requesters with the network (e.g., 3GPP network) where the management function network element is located. The 3GPP network thus provides corresponding tag-managed services to an operation requester according to the priority of the operation requester. For example, the higher the priority of the first operation requester, the more timely the 3GPP network responds to the first operation requester, and the shorter the response time. Conversely, the less timely the response, the longer the response time. Therefore, the management function network element can provide differentiated services for different operation requesters according to the priority, and can coordinate resources so as to better meet the requirements of the operation requesters with different grades.

Example 5-2, the priority here may be the order of time when the management function network element received the messages of the plurality of operation requesters requesting to perform the tag operation. For example, the priority of the first operation requester is higher than the priority of the second operation requester, it being understood that the time when the first request is received by the management function network element is earlier than the time when the second request is received by the management function network element.

Specifically, in the case where the priority of the first operation requester is lower than the priority of the second operation requester, the management function network element determines to suspend the tag operation #1 performed on the at least one first tag. Or in case the priority of the second operation requester is lower than the priority of the first operation requester, the management function network element determines not to suspend the tag operation #1 performed on the at least one first tag.

Optionally, the method 310 further includes: in case the management function network element determines to abort the label operation #1 performed on the at least one first label, the management function network element may further instruct the access network element to perform the label operation #2 on the at least one second label first. After the end of the label operation #2, the access network element may resume the label operation #1 on the at least one first label, or resume the label operation #1 on the at least one first label. Specific examples are given below in connection with S316 to S319.

S316, the management function network element sends a fifth request to the access network element, and correspondingly, the access network element receives the fifth request from the management function network element.

Wherein the fifth request is for requesting that label operation #2 be performed on at least one second label. It will be appreciated that, prior to S316, the access network element sends a tag selection message #2 to the at least one second tag, where the tag selection message #2 includes identification information of the at least one second tag, or includes information of the second area.

Specifically, the management function network element determines a fifth request from the second request.

Illustratively, the tag operation #1 and the tag operation #2 may be the same operation, or may be different operations.

S317, the access network element suspends the label operation #1 performed on the at least one first label, and performs the label operation #2 on the at least one second label.

The manner in which label operation #2 is performed may be found in the description above with respect to method 100, method 100', method 100", and method 200.

For example, the fifth request implicitly instructs the access network element to abort performing the tagging operation #1. When receiving a request for executing a tag operation on other tags in the process of executing the tag #1, the access network element determines to suspend the tag operation #1 according to the request for executing the tag operation on the other tags. It will be appreciated that by implicitly instructing the access network element to abort the tagging operation performed on the at least one first tag by the fifth request, signalling overhead can be saved.

For another example, before S317, the management function network element further sends a message for instructing to suspend performing the tagging operation #1 to the access network element for displaying a message for instructing to suspend performing the tagging operation #1. For example, the management function network element sends a seventh request to the access network element, and accordingly, the access network element receives the seventh request from the management function network element. The seventh request is for requesting to suspend the tag operation performed on the at least one first tag. Specifically, the access network element suspends the tag operation performed on the at least one first tag according to the seventh request. It will be appreciated that by the seventh request display instructing the access network element to suspend the tag operation performed on the at least one first tag, the time at which the access network element suspended the tag operation performed on the at least one first tag can be flexibly controlled.

One possible implementation way, after the access network element performs the label operation #2, the label operation #1 is continuously performed by default, or the label operation #1 is re-performed by default.

In another possible implementation, after S317, the access network element needs to continue to perform the label operation #1 or re-perform the label operation #1 according to the instruction of the management function network element. For example, S318 and S319 give specific examples of how the management function network element instructs the access network element to continue performing the label operation #1 or to re-perform the label operation #1.

It should be appreciated that in the case where the access network element does not send the result of the label that has been performed the label operation to the management function network element, continuing to perform the label operation #1 can reduce overhead as compared to re-performing the label operation #1. Re-executing the tagging operation #1 can save memory space of the access network element compared to continuing to execute the tagging operation #1. In case the access network element has sent the result of the label that has been performed the label operation to the management function element, the access network element continues by default the label operation #1.

And S318, the access network element sends a fifth message to the management function network element, and correspondingly, the management function network element receives the fifth message from the access network element.

Wherein the fifth message is used to indicate that the tag operation #2 performed on the at least one second tag has ended.

S319, the first management network element sends a sixth request to the access network element, and accordingly, the access network element receives the sixth request from the management function network element.

Wherein the sixth request is for instructing to perform the tag operation #1 on the at least one first tag, or the sixth request is for instructing to perform the tag operation #1 on a first tag, among the at least one first tag, on which the tag operation is not performed.

It should be understood that, after the first management network element learns that the label operation #2 performed by the access network element has ended, the access network element is instructed to continue performing the label operation #1 or re-perform the label operation #1 through the sixth request.

S321 and S322 may be referred to the description of S311 and S312 in the method 310.

S323, the access network element sends (or broadcasts) a tag selection message #1 in the coverage area, where the tag selection message #1 includes identification information of at least one first tag, or includes information of a first area. Accordingly, the first tag receives the tag selection message #1 and the second tag, which receives the tag selection message #2, is activated.

S324, the access network element executes label operation #1 to at least one first label according to the fourth request.

In case the label operation #1 performed by the access network element on the at least one first label is not ended, S325 is performed.

S325 can refer to the description of S314.

S326 may be described with reference to S316.

In the subsequent step, there may be various schemes, for example scheme 1 or scheme 2.

Scheme 1:

S327a, the access network element determines whether to suspend the tag operation #1. Specifically, the access network element determines whether to suspend the tag operation #1 performed on the at least one first tag according to the priority of the first operation requester and the priority of the second operation requester. See in particular S315, with the difference that: the management function network element in S315 is replaced with an access network element.

Optionally, the scheme 1 further includes: in case the access network element determines to suspend the tagging operation #1, the access network element first performs the tagging operation #2 on at least one second tag. After the end of the label operation #2, the access network element may resume the label operation #1 on the at least one first label, or resume the label operation #1 on the at least one first label.

Or scheme 1 further comprises: and under the condition that the access network element determines not to suspend the label operation #1, the access network element continues to execute the label operation #1, and after the label operation #1 is ended, the access network element executes the label operation #2 on at least one second label.

According to the scheme, the access network element can provide differentiated services for different operation requesters according to the priorities, so that resources are coordinated to better meet the requirements of the operation requesters with different priorities. Particularly, for operation requesters with high priority, the label management efficiency can be improved, and the user experience is improved.

Scheme 2:

S327b, the access network element sends (or broadcasts) a tag selection message #2 in the coverage area, where the tag selection message #2 includes identification information of at least one second tag, or includes information of a second area. Accordingly, the second tag receives the tag selection message #2, and the second tag that received the tag selection message #2 is activated.

S328, the access network element executes the label operation #1 and the label operation #2.

A first possible implementation of scheme 2:

The access network element sends the tag selection message #2 in S327b and the tag selection message #1 in S324 based on different frequency units, respectively. Thus, the access network element performs the label operation #1 and the label operation #2 simultaneously based on different frequency units.

For example, in S324, the access network element sends a tag selection message #1 based on the first frequency unit, and accordingly, the first tag receives the tag selection message #1 based on the first frequency unit. In S327b, the access network element sends a tag selection message #2 based on the second frequency unit, and correspondingly, the second tag receives the tag selection message #2 based on the second frequency unit. In S328, the access network element performs a label operation #1 on the first label based on the first frequency unit, and performs a label operation #2 on the second label based on the second frequency unit.

In particular, an understanding of the frequency bin, the first frequency bin, the second frequency bin may be found in the relevant description of the method 300.

It will be appreciated that in this implementation, tag operation #1 and tag operation #2 may be the same tag operation or may be different tag operations.

A second possible implementation of scheme 2:

In the case where the tag operation #1 and the tag operation #2 are the same tag operation, in S328, the access network element may perform the tag operation #1 and the tag operation #2 at the same time.

In the case where the tag operation #1 and the tag operation #2 are not the same tag operation, in S328, the access network element may determine the order of execution of the tag operation #1 and the tag operation #2 by referring to the manner of S327 a.

The following describes methods 400 to 700 for tag management provided by the present application in connection with fig. 5 to 8. Where method 400 and method 500 may be understood as specific embodiments of method 300, method 600 and method 700 may be understood as specific embodiments of method 310. In the methods 400 to 700, the first operation requester and the second operation requester are respectively exemplified by AF1 and AF2, the access network element is exemplified by RAN, the management function network element is exemplified by TMF, the information of at least one first tag is exemplified by tag identification set #1, the information of at least one second tag is exemplified by tag identification set #2, the first tag is exemplified by tag #1, the second tag is exemplified by tag #2, the first area is exemplified by service area #1, and the second area is exemplified by service area # 2. Several descriptions are collectively made below for methods 400 through 700.

(1) A more specific example is given below for the case where AF1 and AF2 belong to the same business. At least one first tag belonging to scene 1 managed by AF1 and at least one second tag belonging to scene 2 managed by AF 2. The at least one first tag may be a bicycle that enters the coverage area and the at least one second tag may be an electric vehicle that enters the coverage area. Wherein the ranges of EPCs of bicycles and electric vehicles entering the coverage area do not overlap. In this scenario, how TMF distinguishes between electric vehicles and bicycles for one enterprise can be achieved in the following manner. The access network element obtains EPCs of one or more tags and sends the EPCs to the TMF, and the TMF can distinguish the electric vehicle from the bicycle according to the EPCs. Or the access network element acquires the TIDs of one or more tags and then sends the TIDs to the TMF, and the TMF can distinguish the electric vehicle from the bicycle according to the TIDs of the electric vehicle and the bicycle entering the coverage area.

(2) The method 400 to 700 will be described mainly by way of example, and the inventory operations in the method 400 to 700 may be replaced by other label operations.

Fig. 5 shows a schematic diagram of a method 400 of tag management provided by the present application. Method 400 may be understood as one possible example of method 300.

S401, the AF1 sends an inventory request #1 to the TMF, and accordingly, the TMF receives the inventory request #1 from the AF 1.

Wherein the inventory request #1 includes a service area #1 and a tag identification set #1. The service area #1 is used for indicating an area in which an inventory operation is performed, the tag identification set #1 is used for indicating p 'tags #1 belonging to a scene or an enterprise in which the AF1 is located, and the tag identification set #1 includes tag identifications of the p' tags #1. The inventory request #1 is used to instruct the TMF to inventory p' tags #1 in the service area #1. Wherein, p 'is more than or equal to 1 and p' is an integer.

For example, taking the tag in the present application as a passive internet of things terminal as an example, the tag identifier in the present application may be EPC or TID.

S402, the AF2 sends an inventory request #2 to the TMF, and accordingly, the TMF receives the inventory request #2 from the AF 2.

Wherein the inventory request #2 includes a service area #2 and a tag identification set #2. The service area #2 is used for indicating an area in which the inventory operation is performed, the tag identification set #2 is used for indicating m 'tags #2 belonging to a scene or an enterprise in which the AF2 is located, and the tag identification set #2 includes tag identifications of the m' tags #2. The inventory request #2 is used to instruct the TMF to inventory m' tags #2 in the service area #2. Wherein m 'is not less than 1 and m' is an integer.

As an example, the tag identifications in the tag identification set #1 carry information for indicating the enterprise 1, such as an enterprise prefix (company prefix) or an enterprise identification. Similarly, the tag identifications in tag identification set #2 carry information for indicating enterprise 2. Or the tag identifications in the tag identification set #1 carry information for indicating the scene 1, such as a scene identification. Similarly, the tag identifications in the tag identification set #2 carry a scene identification for indicating the scene 2. Illustratively, the enterprise prefix, enterprise identification, scene identification, etc. may be carried in the EPC or TID of the tag.

It is understood that S401 and S402 may be one specific example of S301 and S302.

S403, the TMF determines to enable the same RAN to perform the checking operation.

For example, the TMF may determine, based on the coverage area of the RAN to which service area #1 and service area #2 both belong, to enable the RAN to inventory the tags indicated by tag identification set #1 and tag identification set # 2.

It is to be appreciated that service area #1 and service area #2 may collectively belong to the coverage area of one or more RANs. The present application is described by taking one RAN of the plurality of RANs as an example, and other RANs of the plurality of RANs can refer to the solution provided by the present application.

S404, the TMF sends an inventory command #1 to the RAN, and accordingly, the RAN receives the inventory command #1 from the TMF.

Wherein, inventory command #1 includes tag identification set #1 and tag identification set #2. The inventory command #1 is used for instructing the RAN to inventory the tags indicated by the tag identification set #1 and the tag identification set #2.

Alternatively, the TMF may perform S404 whenever it is determined that inventory requests from r AF' S may be judged by the same base station, r being equal to or greater than 2 and r being an integer. Such a combined inventory may improve efficiency. Or the TMF may periodically transmit the inventory command #1, for example, the TMF performs S404 every time period # 1. Since the TMF does not determine when the AF triggers the counting request, the problem that the waiting time of the TMF is too long and the judging efficiency of counting is reduced can be reduced by periodically triggering.

It is understood that S404 may be a specific example of S303, and S303 does not include step 1.

S405, the RAN transmits a tag selection command #1 to the tag, and accordingly, the tag receives a tag selection command #1.

Wherein the tag select command #1 is used to inventory p 'tags #1 and m' tags #2. The tags interacting with the RAN in fig. 5 may be understood as some or all of the above-described p 'tags #1 and m' tags #2.

For example, the RAN sends or broadcasts a tag select command #1 to all tags within coverage. Within the coverage, tags belonging to p 'tags #1 and m' tags #2 receive the tag selection command #1 and are activated, and then S406 is performed.

As one example, the tag is identified as EPC. If the EPCs in tag identification set #1 and tag identification set #2 may be mask aggregated, e.g., the EPCs in tag identification set #1 and tag identification set #2 are consecutively encoded, then inventory command #1 includes tag identification set #3. The tag identification set #3 is obtained by performing mask aggregation according to the tag identification set #1 and the tag identification set #2. In this case, the tag selection command #1 may include the tag identification set #3. Or the tag selection command #1 includes a tag selection command #1-1 and a tag selection command #1-2. Wherein the tag selection command #1-1 includes a tag identification set #1, and the tag selection command #1-2 includes a tag identification set #2.

As another example, taking tag identification as EPC, if EPC in tag identification set #1 and EPC in tag identification set #2 cannot be mask aggregated, tag select command #1 includes tag select command #1-1 and tag select command #1-2. Wherein the tag selection command #1-1 includes a tag identification set #1, and the tag selection command #1-2 includes a tag identification set #2.

The inventory flow #1, including S406 to S409, is described below. The inventory flow #1 is repeated n times, the sum of the numbers of p ' tags #1 and m ' tags #2 is n ', n is greater than or equal to n ', and n ' are positive integers.

The following description will take the ith checking flow #1 as an example, where i is greater than or equal to 1 and less than or equal to n', and i is an integer.

It is understood that S405 may be a specific example of S304.

S406, the tag and the RAN execute a random access procedure.

Wherein the tag activated in S405 performs S406. S406 may refer to the description of the method 100.

And S407, the label with successful random access sends label identification to the RAN, and correspondingly, the RAN receives identification information from the label with successful random access.

It is understood that S407 may be a specific example of S305.

Taking one tag (hereinafter referred to as "tag #i") among p 'tags #1 and m' tags #2 as an example, the tag of the tag #i is identified as EPC #i. After the random access of the tag #i is successful, the EPC #i is transmitted to the RAN.

S408, the RAN sends the tag identification to the TMF, and accordingly, the TMF receives the tag identification from the RAN.

Wherein the tag identity is received by the RAN from a tag for which the random access was successful.

It is understood that S408 may be a specific example of S306.

Optionally, S409, the TMF sends a continue checking request to the RAN, and accordingly, the RAN receives the continue checking request from the TMF. For example, in the case of executing S409, the RAN starts executing the i+1st inventory flow #1 after receiving the continue inventory request. If S409 is not executed, the RAN starts execution of the i+1st inventory flow #1 after S408 is completed.

Example 1, in one possible implementation of S405, S405 may be performed once before each time inventory flow #1 is performed. This can improve the success rate of the inventory. It should be appreciated that in a particular implementation, the RAN may be required to repeatedly send tag select command #1 multiple times to activate tag #i. It is possible that the first time the RAN sends the tag select command #1, the tag #i is not activated, for example: tag #i is not powered or tag #i moves out of coverage of the RAN. The RAN then once again sends the tag select command #1, the tag # i is activated, for example: tag #i is powered on or moves into the coverage area of the RAN.

Alternatively, when the tag #i only needs or supports the TMF to transmit the command of the inventory operation, only the inventory flow #1 described above may be executed. If the tag #i also needs or also supports the TMF to send commands for other tag operations, the inventory flow #1 further includes: the tag identification in S407 may be carried in a registration request sent by the tag #i to the RAN. For example, here the registration request may be referred to in step S201 of the method 200. Subsequently, the tag identification in S408 is carried in the registration request sent by the RAN to the TMF. For example, the registration request here may refer to step S202 in the method 200. After the tag #i is registered with the TMF, the TMF may transmit a registration response message to the RAN, which then transmits the registration response message to the tag #i. See, for example, steps S204 and S205 in method 200.

Further, the type of tag or the user using the tag may decide whether the tag needs authentication. If the tag #i requires authentication, the TMF may also authenticate the tag in the inventory flow #1 of the tag, which may be referred to as step S203 in the method 200. Thus, in addition to step S406 and step S409, the description of the method 200 may be referred to in inventory flow # 1.

Inventory flow #1 is described above.

S410, the RAN sends an end of inventory message to the TMF, and accordingly, the TMF receives the end of inventory message from the RAN.

For example, the RAN repeatedly performs S405, and then performs S410 after determining that the inventory has ended, without receiving the response message of the tag after the elapsed time period # 2.

S411, the TMF determines the correspondence between the checking result and AF1 or AF 2.

The checking result here is the tag identification reported by the RAN at S408.

For example, consider a network in which AF1 belongs to enterprise 1, AF2 belongs to enterprise 2, and TMF belongs to the operator. One possible implementation manner, when the enterprise 1 signs up with the operator, the TMF prestores the correspondence between the enterprise 1 and the tag identification set #1, and the correspondence between the enterprise 2 and the tag identification set # 2. And the TMF determines the corresponding relation between the checking result and the AF1 or the AF2 according to the corresponding relation between the checking result and the stored data when signing. Or in another possible implementation manner, the TMF determines the corresponding relationship between AF1 and the tag identification set #1 according to the tag identification set #1 included in the inventory request #1 received from AF1 in S401, and determines the corresponding relationship between AF2 and the tag identification set #2 according to the tag identification set #2 included in the inventory request #2 received from AF2 in S402. Thus, the TMF can determine the correspondence of the checking result with AF1 or AF 2.

S412, the TMF sends the inventory result #1 to the AF 1.

The tag indicated by the inventory result #1 corresponds to AF1, and the tag indicated by the inventory result #1 is included in p' tags #1.

S413, the TMF transmits the inventory result #2 to the AF 2.

The tag indicated by the checking result #2 corresponds to AF2, and the tag indicated by the checking result #2 is included in m' tags #2.

It is understood that S412 and S413 may be one specific example of S307a and S307 b.

There are many possible implementations of S411 to S413 described above.

For example, in the first case of S411, the TMF may perform S411 after performing the inventory procedure #1 each time, that is, after the TMF receives the tag identification from the RAN report each time, determine the correspondence between the tag identification and the AF1 or AF 2. The end of inventory message is then received in S410. Or in case two of S411, the TMF may determine all tag identifiers reported by the RAN after S410.

In the case one of S412 and S413, corresponding to the case one of S411, the TMF may send the tag identification to the corresponding AF1 or AF2 each time S411 is performed. It is understood that the inventory result #1 includes only one tag identifier each time S412 is performed, and the inventory result #2 includes only one tag identifier each time S413 is performed. In the second case of S412 and S413, corresponding to the first case or the second case of S411, the TMF may execute S412 and S413 after judging all the inventory results.

Advantageous effects of method 400 may be seen as advantageous effects of method 300.

Fig. 6 shows a schematic diagram of a method 500 of tag management provided by the present application. Method 500 may be understood as another possible example of method 300.

S501 to S502 can be referred to the description of S401 to S402.

S503, the TMF determines to start the same RAN to inventory in different sectors.

For example, the TMF may determine, according to the coverage area of the RAN to which the service area #1 and the service area #2 belong, that the RAN is enabled to inventory the tag indicated by the tag identification set #1 (referred to as at least one tag # 1) and the tag indicated by the tag identification set #2 (referred to as at least one tag # 2). Subsequently, the TMF further determines that service area #1 and service area #2 respectively belong to different sectors of the RAN. For example, service area #1 belongs to sector #1 of the RAN, and service area #2 belongs to sector #2 of the RAN. The label indicated by the label identification set #1 corresponds to the sector #1, and the label indicated by the label identification set #2 corresponds to the sector #2.

Alternatively, the TMF acquires the correspondence #1 and the correspondence #2 when signing up with the operator. The label indicated by the label identification set #1 corresponds to the sector #1, and the label indicated by the label identification set #2 corresponds to the sector #2.

It is understood that the information for indicating the correspondence #1 and the information for indicating the correspondence #2 may be one specific example of the first indication information and the second indication information in the method 300, respectively.

S504, the TMF sends an inventory command #2 to the RAN, and accordingly, the RAN receives the inventory command #2 from the TMF.

For a specific description, see S404, with the difference that:

Inventory command #1 is replaced with inventory command #2. The inventory command #2 further includes a correspondence #1 and a correspondence #2, compared to the inventory command # 1.

It is understood that S504 may be a specific example of S303, and S303 includes step 1.

S505 includes S505a and S505b, and the present application does not limit the order in which S505a and S505b are performed. For example, S505a may be performed before or after S505b, or S505a and S505b may be performed simultaneously. The following description will be made with an example in which S505a and S505b are performed simultaneously.

S505a, the RAN sends a tag selection command 2-1 to the tag of sector #1.

Tag select command 2-1 is used to inventory p' tags #1 located in sector #1.

S505b, the RAN sends a tag selection command 2-2 to the tag of sector #2.

Tag select command 2-2 is used to inventory m' tags #2 located in sector #2.

For example, the RAN may broadcast tag selection order 2-1 and tag selection order 2-2 simultaneously using different frequency bands, respectively. Specifically, the RAN broadcasts the tag selection command 2-1 using a frequency band corresponding to the sector #1 (hereinafter referred to as the frequency band #1 for convenience of explanation), and broadcasts the tag selection command 2-2 using a frequency band corresponding to the sector #2 (hereinafter referred to as the frequency band #2 for convenience of explanation).

Accordingly, tag #1 or tag #2 detects signals in different frequency bands, respectively. For example, tag #1 detects a signal in band #1, and tag #2 detects a signal in band # 2. For example, when tag #1 detects tag selection command 2-1 in band #1, it is activated, and then S506b is performed. For example, when tag #2 detects tag selection command 2-2 in band #2, it is activated, and then S506a is performed.

It is understood that S505 may be a specific example of step 2.

S506 includes S506a and S506b, and the present application does not limit the order in which S506a and S506b are performed. For example, S506a may be performed before or after S506b, or S506a and S506b may be performed simultaneously. The following description will be made with an example in which S506a and S506b are performed simultaneously.

S506a, the inventory flow #2 is repeated m times, the sum of the numbers of m 'tags #2 is m', m is more than or equal to m ', and m' are positive integers.

The j-th inventory flow #2 is described below as an example, where j is 1.ltoreq.j.ltoreq.m', and j is an integer.

The jth inventory flow #2 may refer to the description of the ith inventory flow #1, except that: replacing the tag #i related to the inventory flow #1 with a tag #j, and replacing the EPC #i with an EPC #j, wherein the tag #j is any tag of m' tags #2; replacing the coverage area of the RAN with sector #2; s405 referred to in example 1 is replaced with S505a.

In the inventory flow #2, the tag of the sector #2 performs information interaction with the RAN using the frequency band # 2.

S506b, the inventory flow #3 is repeated for p times, the sum of the numbers of the p 'tags #1 is p', p is more than or equal to p ', and p' are positive integers.

In the following, the kth inventory flow #3 is taken as an example, where k is 1.ltoreq.k.ltoreq.p', and k is an integer.

The kth inventory flow #3 may refer to the description of the ith inventory flow #1, except that: replacing the tag #i related to the inventory flow #1 with a tag #k, and replacing the EPC #i with an EPC #k, wherein the tag #k is any tag of the p' tags #1; replacing the coverage area of the RAN involved in inventory procedure #1 with sector #1; s405 referred to in example 1 is replaced with S505b.

In the inventory flow #3, the tag of the sector #1 performs information interaction with the RAN using the frequency band # 1.

S507, the RAN sends an end of inventory message to the TMF, and accordingly, the TMF receives the end of inventory message from the RAN.

For example, in the inventory flow #2 and the inventory flow #3, the RAN repeatedly transmits the continuous inventory request message to the RAN, and after the time length #2 has elapsed, the response message of the tag is not received, and it may be determined that the inventory has ended, and then S507 is performed.

S508, the TMF judges the corresponding relation between the checking result and the AF1 or the AF 2.

The counting result here is the label identification reported by the RAN in the counting flow #2 and the counting flow # 3.

For example, in S508, the TMF may classify the tag identifications received from the RAN with reference to the manner in S411, and determine which tags belong to AF1 and which tags belong to AF2.

For another example, the RAN also carries the indication information of the sector #2 in the message of reporting the tag identifier in the inventory flow #2. The RAN also carries the indication information of sector #1 in the message of reporting the tag identifier in inventory flow # 3. The RAN can determine whether the tag label transmitted by the RAN belongs to the tag label set #1 or the tag label set #2 according to the correspondence between the sector #1 and the tag label set #1 or the correspondence between the sector #2 and the tag label set #2.

S509, the TMF transmits the inventory result #3 to the AF 1.

The tag indicated by the inventory result #3 corresponds to AF1, and the tag indicated by the inventory result #3 is included in p' tags #1.

S510, the TMF sends the inventory result #4 to the AF 2.

The tag indicated by the inventory result #4 corresponds to AF2, and the tag indicated by the inventory result #4 is included in m' tags #2.

It is understood that S508 to S510 may be one specific example of step 4 and step 5.

There are many possible implementations of S508 to S510 described above.

For example, in case one of S508, the TMF may perform S508 after performing the checking procedure #2 or the checking procedure #3 each time, that is, after the TMF receives the tag identification from the RAN report each time, it determines whether the tag identification belongs to AF1 or AF2. Then the end of inventory message is received in S507. Or in the second case of S508, after S507, the TMF may determine all the tag identifiers reported by the RAN.

In the first case of S509 and S510, corresponding to the first case of S508, the TMF may send the tag identifier to the corresponding AF1 or AF2 each time S508 is performed. It is understood that each time S509 is performed, only one tag identification is included in the inventory result #3, and each time S510 is performed, only one tag identification is included in the inventory result # 4. In the second case of S509 and S510, corresponding to the first case or the second case of S508, the TMF may execute S509 and S510 after judging the correspondence of all the inventory results to AF1 or AF2.

Advantageous effects of method 500 may be seen from the advantageous effects of method 300.

Fig. 7 shows a schematic diagram of a method 600 of tag management provided by the present application. Method 600 may be understood as one possible example of method 310. Wherein method 600 gives a specific example for the priority in example 5-2 in method 310, and the priority of AF1 is higher than the priority of AF2 in method 600 is illustrated as an example. In the method 600, when the counting process of the RAN on the tag of the AF1 has not been completed, the AF2 also sends a counting request to the TMF, and the TMF instructs the RAN to perform tag counting according to the time sequence of receiving the counting requests of the AF1 and the AF 2.

S601, AF1 sends an inventory request #3 to the TMF, and accordingly, the TMF receives the inventory request #3 from AF 1.

Wherein the inventory request #3 includes a service area #3 and a tag identification set #3. The service area #3 is used for indicating an area in which the inventory operation is performed, the tag identification set #3 is used for indicating x 'tags #1 belonging to a scene or an enterprise in which the AF1 is located, and the tag identification set #3 includes tag identifications of the x' tags # 1. The inventory request #3 is used to instruct the TMF to inventory x' tags #1 in the service area #3. Wherein x 'is not less than 1 and x' is an integer.

It is understood that S601 may be a specific example of S311.

S602, the TMF determines to start the RAN to inventory.

For example, the TMF determines to start the RAN for counting according to the coverage area of the RAN to which the service area #3 belongs.

S603, the TMF sends an inventory command #3 to the RAN, and accordingly, the RAN receives the inventory command #3 from the TMF.

Wherein inventory command #3 includes tag identification set #3. The inventory command #3 is used to instruct the RAN to inventory the tag indicated by the tag identification set #3.

It is understood that S603 may be a specific example of S312.

S604, the RAN transmits a tag selection command #3 to the tag #1, and accordingly, the tag #1 receives the tag selection command #3.

Wherein the tag select command #3 is used to inventory x' tags #1. Tag #1 in fig. 7, which interacts with the RAN, can be understood as some or all of the x' tags #1.

S605 includes S605a and S605b. In the execution process of S605a, S605b is executed.

S605a, checking flow #4 is repeated for x times, the sum of the numbers of x 'tags #1 is x', x is more than or equal to x ', and x' are positive integers.

The following description will take an a-th inventory flow #4 as an example, where a is 1.ltoreq.a.ltoreq.x', and a is an integer.

The a-th inventory flow #4 may refer to the description of the i-th inventory flow #1, except that: replacing the tag #i related to the inventory flow #1 with a tag #a, and replacing the EPC #i with an EPC #a, wherein the tag #a is any tag of x' tags # 1; s405 referred to in example 1 is replaced with S604.

For example, in the process of the a-th inventory flow #4, S605b is executed.

It is understood that S604 to S605a may be one specific example of S313.

S605b, AF2 sends an inventory request #4 to the TMF, and accordingly, the TMF receives inventory request #4 from AF 2.

Wherein the inventory request #4 includes a service area #4 and a tag identification set #4. The service area #4 is used for indicating an area in which the inventory operation is performed, the tag identification set #4 is used for indicating y 'tags #2 belonging to a scene or business where the AF2 is located, and the tag identification set #4 includes tag identifications of the y' tags # 2. The inventory request #4 is used to instruct the TMF to inventory y' tags #2 in the service area #4. Wherein y 'is not less than 1 and y' is an integer.

It is understood that S605b may be a specific example of S314.

S606, the TMF determines that the RAN finishes counting and then sends a counting command #4 to the RAN.

Specifically, the TMF determines not to terminate the inventory flow #4 based on the inventory request #3 being received first and the inventory request #4 being received later.

It is understood that S606 may be a specific example of S315.

S607, the RAN sends an end of inventory message to the TMF, and accordingly, the TMF receives the end of inventory message from the RAN. The end of inventory message is used to instruct the end of the x-time inventory flow # 4.

Optionally, S608, the TMF sends the inventory result #5 to the AF1, and accordingly, the AF1 receives the inventory result #5 from the TMF.

The tag indicated by the inventory result #5 corresponds to AF1, and the tag indicated by the inventory result #5 is included in x' tags # 1. The execution sequence of S608 follows S607, but the present application is not limited to S608 being executed before any one of steps S609 to S613.

S609, the TMF sends an inventory command #4 to the RAN, and accordingly, the RAN receives the inventory command #4 from the TMF.

Wherein inventory command #4 includes tag identification set #4. The inventory command #4 is used to instruct the RAN to inventory the tag indicated by the tag identification set #4.

It is understood that S609 may be a specific example of S316.

S610, the RAN sends a tag selection command #4 to the tag, and accordingly, the tag receives a tag selection command #4.

Wherein the tag select command #4 is used to inventory y' tags #2. Tag #2 in fig. 7, which interacts with the RAN, can be understood as part or all of the above-described y' tags #2.

S611, the checking flow #5 is repeated for y times, the sum of the numbers of the y 'tags #1 is y', y is more than or equal to y ', and y' are positive integers.

The following description will take the b-th inventory flow #5 as an example, where b is 1.ltoreq.b.ltoreq.y', and b is an integer.

The b-th inventory flow #5 may refer to the description of the i-th inventory flow #1, except that: replacing the tag #i related to the inventory flow #1 with a tag #b, and replacing the EPC #i with an EPC #b, wherein the tag #b is any tag of y' tags # 1; s405 referred to in example 1 is replaced with S610.

It is understood that S610 to S611 may be one specific example of S317.

S612, the RAN sends an end of inventory message to the TMF, and accordingly, the TMF receives the end of inventory message from the RAN. The end of inventory message is used to instruct the end of inventory flow #5 for y times.

Optionally, S613, the TMF sends the inventory result #6 to the AF2, and accordingly, the AF2 receives the inventory result #6 from the TMF.

The tag indicated by the inventory result #6 corresponds to AF2, and the tag indicated by the inventory result #6 is included in y' tags #2.

Advantageous effects of method 600 may be seen from the advantageous effects of method 310.

In another possible implementation, the TMF does not perform S606, and S609 is performed after receiving inventory request #4 of S605b before performing S607. The RAN receives the inventory command #4 in S609 in the process of executing S605 a. The RAN determines that S605a is performed and then S610 and S611 are performed.

Fig. 8 shows a schematic diagram of a method 700 of tag management provided by the present application. Method 700 may be understood as another possible example of method 310. Wherein method 700 gives a specific example for the priority in example 5-1 in method 310, and method 700 is described with the example of AF1 having a lower priority than AF 2.

S701 to S704 may refer to descriptions corresponding to S601 to S604.

S705 includes S705a and S705b. In the execution process of S705a, S705b is executed.

It is understood that S704 to S705a may be one specific example of S313.

S705a, checking flow #6 is repeated for x1 times, the sum of the numbers of x 'labels #1 is x', x 'is not less than x1 is not less than 1, and x1 and x' are positive integers. It should be appreciated that in S705a, the RAN has not yet completed all of the inventory of x' tags #1.

The following description will take an a-th inventory flow #6 as an example, where a is 1.ltoreq.a.ltoreq.x', and a is an integer.

The a-th inventory flow #6 can refer to the description of the i-th inventory flow #1, except that: replacing the tag #i related to the inventory flow #1 with a tag #a, and replacing the EPC #i with an EPC #a, wherein the tag #a is any tag of x' tags # 1; s405 referred to in example 1 is replaced with S704.

For example, after the x1 st inventory flow #6 ends, S605b is executed.

S705b, AF2 sends an inventory request #4 to the TMF, and accordingly, the TMF receives the inventory request #4 from AF 2.

See for details the description of S605 b.

It is understood that S705b may be a specific example of S314.

S706, the TMF determines that the checking flow #6 is aborted and the RAN is started to check the tag of AF 2.

Here, description will be made taking as an example that the priority of AF2 is higher than that of AF 1. The TMF determines to suspend the counting flow #6 and start the RAN to count the tag of AF2 according to the priority of AF2 being higher than the priority of AF 1.

It is understood that S706 may be a specific example of S315.

S710 to S711 are performed next. S710 to S711 may be described with reference to S609 to S610.

Optionally, at least one of S707 or S708 or S709 may also be performed at S710 to S711, two implementations being given below.

In the first implementation, S710 to S711, and S609 to S610 differ in that: the RAN performs S710, i.e., upon receiving the inventory command #4, suspends the inventory flow #6, and performs S711. It will be appreciated that inventory command #4 implicitly instructs the RAN to abort inventory flow #6.

Optionally, the method 700 further comprises: s709, the TMF sends an inventory result #7-1 to the AF1, and accordingly, the AF1 receives the inventory result #7-1 from the TMF. The inventory result #7-1 includes the x1' tag identifications. For example, the x1 'tag identifications here may be received by the RAN from the x' tags #1 in inventory flow # 6. The RAN may send the tag identification of one tag #1 out of x' tags #1 to the TMF every time the tag identification of the one tag #1 is received. The TMF may transmit to the AF1 without receiving the tag identification of one tag #1 from the RAN in S709, or may transmit the tag identifications of x 'tags #1 together to the AF1 after receiving the tag identifications of x' tags # 1. Or the RAN will send the tag identifications of x 'tags #1 together to the TMF, which in S709 sends the tag identifications of x' tags #1 together to the AF1.

Or in a second implementation, the method 700 further includes: s707 and S708. After the TMF executes S708, that is, after the TMF receives the inventory flow #6 termination message, S710 is executed.

S707, the TMF sends an abort inventory flow #6 message to the RAN, and accordingly, the RAN receives the abort inventory flow #6 message from the RAN.

Wherein the abort inventory flow #6 message indicates RAN abort inventory flow #6.

S708, the RAN sends an inventory flow #6 abort message to the TMF, and accordingly, the TMF receives the inventory flow #6 abort message from the RAN.

Wherein the inventory flow #6 abort message indicates that the RAN has aborted inventory flow #6.

Alternatively, if in the inventory flow #6 of S705a, the RAN immediately transmits to the TMF each time the tag identification is received, then the inventory flow #6 in the second implementation does not carry the tag identification in the abort message. Or if in the checking flow #6 of S705a, the RAN does not immediately send the tag identifier to the TMF every time the RAN receives, the checking flow #6 suspension message may further carry x1' tag identifiers received by the RAN in S705a, 0 is less than or equal to x1' isless than or equal to x1, and x1' is an integer.

Optionally, the method 700 further comprises: s709, the TMF sends an inventory result #7-1 to the AF1, and accordingly, the AF1 receives the inventory result #7-1 from the TMF. The inventory result #7-1 includes the x1' tag identifications. Reference may be made specifically to S709 in the first implementation. Alternatively, the TMF may also obtain x1' tag identifications from the inventory flow #6 abort message.

S712, checking flow #7 is repeated y times, the sum of the numbers of y 'labels #2 is y', y is more than or equal to y ', and y' are positive integers.

Specifically, referring to the description of S611, the inventory flow #5 in S611 is replaced with the inventory flow #7.

S713, the RAN sends an end of inventory message to the TMF, and accordingly, the TMF receives the end of inventory message from the RAN. The end of inventory message is used to instruct the end of inventory flow #5 for y times.

It is understood that S713 may be a specific example of S318.

S714, the TMF sends the checking result #8 to the AF2, and accordingly, the AF2 receives the checking result #8 from the TMF.

The tag indicated by the inventory result #8 corresponds to AF2, and the tag indicated by the inventory result #8 is included in y' tags #2.

It should be noted that S714 is only required to be executed after S713, and the present application is not limited to S714 being executed before any of steps S715 to S720.

At S715, the TMF determines to continue to execute inventory flow #6.

S716, the TMF sends an inventory command #3 'to the RAN, and accordingly, the RAN receives the inventory command #3' from the TMF.

It is understood that S716 may be a specific example of S319.

S717, the RAN transmits a tag selection command #3 'to the tag #1, and accordingly, the tag #1 receives the tag selection command #3' from the RAN.

S718, inventory flow #6 is repeated x2 times. x '. Gtoreq.x2.gtoreq.1, x2 and x' are positive integers.

S719, the RAN sends an inventory flow #6 end message to the TMF, and accordingly, the TMF receives the inventory flow #6 end message from the RAN.

S720, the TMF sends an inventory result #7-2 to the AF1, and accordingly, the AF1 receives the inventory result #7-2 from the TMF.

Two implementations are specifically given below with respect to S716 through S720.

The implementation mode is as follows:

s716 and S717 refer to the description of S703 and S704, in other words, the inventory command #3 'and the inventory command #3 coincide, and the tag selection command #3' coincides with the tag selection command # 3.

S718 may refer to the description of S605a, in other words, the inventory flow #6 in S718 coincides with the inventory flow #4 in S605a, x2=x.

S719 and S720 refer to S607 and S608.

In one implementation, the RAN may not store the tag identifications of the x1' tags #1 checked in S705a, which reduces the complexity of the processing of the access network device. Corresponding to implementation one, S709 may or may not be executed in method 700. In the case where the RAN does not store the tag identifications of x1 'tags #1, the inventory flow #6 suspension message in S708 does not carry the tag identifications of x1' tags # 1. S709 is not performed so that signaling overhead can be reduced.

The implementation mode II is as follows:

In implementation two, if S707 is performed. In S716, the inventory command #3 'includes the tag identification set #3'. The inventory command #3 is used to instruct the RAN to inventory the tag indicated by the tag identification set #3'. The tag identification set #3 'includes tag identifications of x2' tags #1 other than x1 'tags #1 among x' tags #1. The x2' tags #1 are tags #1 that the RAN has not yet checked.

The TMF determines the tag identification set #3 'according to the x1' tag identifications reported in the termination message of the endpoint procedure #6 in S707, and the tag identification set # 3.

In S717, the tag selection command #3 'is used for checking x2' tags # 1. Tag #1 interacting with the RAN in S718 may be understood as part or all of the x2' tags # 1.

Or in implementation two, S707 is not performed. Inventory command #3' in S716 coincides with inventory command #3. The RAN stores the identities of the x1' tags that have been checked in S705 a. And determines the tag identification set #3 from the tag identification set #3 and the already stored identifications. The tag identification set #3 includes x2' tags #1 that have not yet been checked by the RAN.

In S718, x2' =x ' -x1'.

In S719, the tag identification included in the inventory flow #6 end message is included in the tag identifications of x2' tags # 1.

If S709 is performed, only the tag identification acquired from the RAN in S719 is included in S720. Or if S709 is not performed, the method 700 needs to perform S707. After executing S707, the TMF stores the tag identifications of x1' tags #1, and in combination with the tag identifications acquired from the RAN in S719, the TMF reports the tag identifications acquired in total in the x-time inventory flow #6 to the AF1 in S720. The tag identifications collectively acquired in the x-time inventory flow #6 are included in the tag identification set #3.

Advantageous effects of method 700 may be seen from the advantageous effects of method 310.

Fig. 9 and 10 are schematic structural diagrams of a possible communication device according to an embodiment of the present application. These communication devices may be used to implement the functions of the transmitting device or the receiving device in the above-described method embodiments, and thus may also implement the advantages provided by the above-described method embodiments. In the embodiment of the present application, the communication device may be a transmitting device or a receiving device, and may also be a module (e.g., a chip) applied to the transmitting device or the receiving device.

As shown in fig. 9, the communication apparatus 800 includes a processing unit 810 and a transceiving unit 820. The communication device 800 is used to implement the functions of the transmitting device or the receiving device in the method embodiments shown in fig. 4 to 8 described above.

When the communication apparatus 800 is used to implement the function of the management function network element in the method embodiment shown in (a) in fig. 4: a transceiver unit 820 for receiving a first request from a first operation requester, the first request being for requesting to perform a tag operation on at least one first tag; the transceiver unit 820 is further configured to receive a second request from a second operation requester, where the second request is for requesting to perform the tag operation on at least one second tag; the transceiver unit 820 is further configured to send a third request to the access network element, where the at least one first tag and the at least one second tag both belong to a coverage area of the access network element, the third request being configured to request the at least one first tag and the at least one second tag to perform the tag operation.

Optionally, the transceiver unit 820 is further configured to receive a result of performing the tag operation on at least one third tag from the access network element; the transceiver unit 820 is further configured to send the result to the first operation requester, in case the at least one third tag belongs to the at least one first tag; or the transceiver unit 820 is further configured to send the result to the second operation requester, in case the at least one third tag belongs to the at least one second tag.

Optionally, the transceiver unit 820 is further configured to send first indication information and second indication information to the access network element, where the first indication information is used to indicate that the at least one first tag corresponds to a first frequency unit, and the second indication information is used to indicate that the at least one second tag corresponds to a second frequency unit, and the first frequency unit and the second frequency unit are both included in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit do not overlap.

Optionally, in the case that the result includes information indicating the first frequency unit; the transceiver unit 820 is specifically configured to send the result to the first operation requester according to the first indication information; or in case the result comprises the information indicating the second frequency unit; the transceiver unit 820 is specifically configured to send the result to the second operation requester according to the second indication information.

When the communication device 800 is used to implement the function of the access network element in the method embodiment shown in (a) in fig. 4: a transceiver unit 820 for receiving a third request from the management function network element, the third request being for requesting to perform a label operation on the at least one first label and the at least one second label; the transceiver unit 820 is further configured to send a first message to a tag in the coverage area, where the first message is used to activate a third tag in the coverage area, where the third tag belongs to the at least one first tag or the at least one second tag; wherein the at least one first tag and the at least one second tag belong to different operation requesters, respectively.

Optionally, the transceiver unit 820 is further configured to receive a second message from the third tag, where the second message includes information of the third tag; the transceiver unit 820 is further configured to send, to the management function network element, a result of performing the label operation on the third label, where the result is used to indicate that the label operation has been performed on the third label.

Optionally, the transceiver unit 820 is further configured to receive first indication information and second indication information from the management function network element, where the first indication information is used to indicate that the at least one first tag corresponds to a first frequency unit, the second indication information is used to indicate that the at least one second tag corresponds to a second frequency unit, the first frequency unit and the second frequency unit are both included in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit do not overlap.

Optionally, the first message includes a third message and a fourth message, and the transceiver unit 820 is specifically configured to send the third message through the first frequency unit, where the third message is used to activate the third tag belonging to the at least one first tag in the coverage area; the transceiver unit 820 is specifically configured to send a fourth message through the second frequency unit, where the fourth message is used to activate the third tag belonging to the at least one first tag in the coverage area, and the third message and the fourth message are sent simultaneously.

Optionally, in the case that the third tag belongs to the at least one first tag, the transceiver unit 820 is specifically configured to receive, through the first frequency unit, the second message from the third tag; or the third tag belongs to the at least one second tag, the transceiver unit 820 is specifically configured to receive the second message from the third tag through the second frequency unit.

When the communication apparatus 800 is used to implement the function of the management function network element in the method embodiment shown in (b) in fig. 4: a transceiver unit 820 for receiving a first request from a tag operation requester, the first request being for requesting at least one first tag to perform a tag operation; the management function network element sends a fourth request to the access network element according to the first request, wherein the fourth request is used for requesting the at least one first label to execute the label operation; the transceiver unit 820 is further configured to receive a second request from a second operation requester, where the second request is for requesting the at least one second tag to perform the tag operation, if the tag operation performed on the at least one first tag is not finished; in case that the at least one first tag and the at least one second tag both belong to the coverage area of the access network element, the processing unit 810 is configured to determine whether to suspend the tag operation performed on the at least one first tag according to the priority of the first operation requester and the priority of the second operation requester.

Optionally, in case the priority of the first operation requester is lower than the priority of the second operation requester, the processing unit 810 is specifically configured to determine to abort the tag operation performed on the at least one first tag.

Optionally, the transceiver unit 820 is further configured to send a fifth request to the access network element, where the fifth request is used to request to perform the tag operation on at least one second tag.

Optionally, the transceiver unit 820 is further configured to receive the fifth request from the management function network element; the access network element suspends the tag operation performed on the at least one first tag and performs the tag operation on the at least one second tag.

Optionally, the transceiver unit 820 is further configured to send a seventh request to the access network element, where the seventh request is for requesting to suspend the tag operation performed on the at least one first tag.

Optionally, the transceiver unit 820 is further configured to receive the seventh request from the management function network element; the processing unit 810 is specifically configured to suspend the tag operation performed on the at least one first tag according to the seventh request.

Optionally, the transceiver unit 820 is further configured to receive a fifth message from the access network element, where the fifth message is used to indicate that the tag operation performed on the at least one second tag has ended; the transceiver unit 820 is further configured to send a sixth request to the access network element, where the sixth request is used to instruct to perform the tag operation on the at least one first tag, or the sixth request is used to instruct to perform the tag operation on a first tag that is not performed with the tag operation in the at least one first tag.

When the communication device 800 is used to implement the function of the access network element in the method embodiment shown in (b) in fig. 4: a transceiver unit 820 for receiving a fourth request from the management function network element, the fourth request being for requesting to perform a tag operation on the at least one first tag; a processing unit 810 for performing the tag operation on the at least one first tag according to the fourth request; the transceiver unit 820 is further configured to receive a fifth request from the management function network element, where the tag operation performed on the at least one first tag is not ended, the fifth request being for requesting the at least one second tag to perform the tag operation; the processing unit 810 is further configured to suspend the tag operation performed on the at least one first tag; the processing unit 810 is further configured to perform the tag operation on the at least one second tag according to the fifth request.

Optionally, the transceiver unit 820 is configured to send a fifth message to the management function network element, where the fifth message is used to indicate that the label operation performed on the at least one second label has ended; the processing unit 810 is further configured to perform the tag operation on the at least one first tag, or perform the tag operation on a first tag that is not performed with the tag operation among the at least one first tag.

Optionally, the transceiver unit 820 is configured to send a fifth message to the management function network element, where the fifth message is used to indicate that the label operation performed on the at least one second label has ended; a transceiver unit 820, configured to receive a sixth request from the management function network element, where the sixth request is used to instruct to perform the tag operation on the at least one first tag, or the sixth request is used to instruct to perform the tag operation on a first tag that is not performed with the tag operation in the at least one first tag; the processing unit 810 is further configured to perform the tag operation according to the sixth request.

Optionally, the transceiver unit 820 is configured to receive a seventh request from the management function network element, where the seventh request is used to request to suspend the tag operation performed on the at least one first tag; the processing unit 810 is specifically configured to suspend the tag operation performed on the at least one first tag according to the seventh request.

For more details on the processing unit 810 and the transceiver unit 820 described above, reference is made to the relevant description in the method embodiments shown in fig. 4 to 8.

As shown in fig. 10, the communication device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 may be a transceiver or an input-output interface. Optionally, the communication device 900 may further include a memory 930 for storing instructions executed by the processor 910 or for storing input data required by the processor 910 to execute the instructions or for storing data generated after the processor 910 executes the instructions.

When the communication device 900 is used to implement the method shown in fig. 10, the processor 910 is configured to implement the functions of the processing unit 810, and the interface circuit 920 is configured to implement the functions of the transceiver unit 820.

When the communication device is a chip applied to the management function network element, the management function network element chip realizes the function of the management function network element in the method embodiment. The management function network element chip receives information from other modules (such as a radio frequency module or an antenna) in the management function network element, and the information is sent to the management function network element by the access network element; or the management function network element chip sends information to other modules (such as a radio frequency module or an antenna) in the management function network element, and the information is sent to the access network element by the management function network element.

When the communication device is a chip applied to the access network element, the terminal chip realizes the function of the access network element in the embodiment of the method. The chip of the access network element receives information from other modules (such as a radio frequency module or an antenna) in the access network element, and the information is sent to the access network element by the management function network element; or the chip of the access network element sends information to other modules (such as a radio frequency module or an antenna) in the base station, and the information is sent to the management function network element by the access network element.

It is to be appreciated that the processor in embodiments of the application may be a central processing unit (central processingunit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSPs), application Specific Integrated Circuits (ASICs), field programmable gate arrays (fieldprogrammable GATE ARRAY, FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

The method steps of the embodiments of the present application may be implemented in hardware or in software instructions executable by a processor. The software instructions may be comprised of corresponding software modules that may be stored in random access memory, flash memory, read only memory, programmable read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. The storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a base station or terminal. The processor and the storage medium may reside as discrete components in a base station or terminal.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user device, or other programmable apparatus. The computer program or instructions may 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 program or instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired or wireless means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, e.g., floppy disk, hard disk, tape; but also optical media such as digital video discs; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage medium.

In various embodiments of the application, where no special description or logic conflict exists, terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments based on their inherent logic.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. In the text description of the present application, the character "/", generally indicates that the associated objects are an or relationship; in the formula of the present application, the character "/" indicates that the front and rear associated objects are a "division" relationship. "including at least one of A, B and C" may mean: comprises A; comprises B; comprising C; comprises A and B; comprises A and C; comprises B and C; including A, B and C.

It will be appreciated that the various numerical numbers referred to in the embodiments of the present application are merely for ease of description and are not intended to limit the scope of the embodiments of the present application. The sequence number of each process does not mean the sequence of the execution sequence, and the execution sequence of each process should be determined according to the function and the internal logic.

Claims

1. A method of tag management, comprising:

the management function network element receives a first request from a first operation requester, wherein the first request is used for requesting to execute label operation on at least one first label;

The management function network element receives a second request from a second operation requester, wherein the second request is used for requesting to execute the label operation on at least one second label;

and under the condition that the at least one first tag and the at least one second tag belong to the coverage range of an access network element, the management function network element sends a third request to the access network element, wherein the third request is used for requesting the at least one first tag and the at least one second tag to execute the tag operation.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The first request includes information of the at least one first tag and the second request includes information of the at least one second tag, the method further comprising:

The management function network element determines a first area corresponding to the at least one first label according to the information of the at least one first label, and determines a second area corresponding to the at least one second label according to the information of the at least one second label;

The management function network element determines that the at least one first tag and the at least one second tag belong to the coverage area according to the first area and the second area;

Or alternatively

The first request includes information of a first area, the first area is an area corresponding to the at least one first tag, the second request includes information of a second area, the second area is an area corresponding to the at least one second tag, and the method further includes:

And the management function network element determines that the at least one first label and the at least one second label belong to the coverage area according to the first area and the second area.

3. A method according to claim 1 or 2, characterized in that,

The third request includes information of the at least one first tag and information of the at least one second tag, or the third request includes information of the first area and information of the second area.

4. A method according to any one of claims 1 to 3, further comprising:

The management function network element receives a result of the label operation performed on at least one third label by the access network element;

In case the at least one third tag belongs to the at least one first tag, the management function network element sends the result to the first operation requester; or alternatively

In case the at least one third tag belongs to the at least one second tag, the management function network element sends the result to the second operation requester.

5. The method according to any one of claims 1 to 4, further comprising:

The management function network element sends first indication information and second indication information to the access network element, the first indication information is used for indicating that the at least one first label corresponds to a first frequency unit, the second indication information is used for indicating that the at least one second label corresponds to a second frequency unit, the first frequency unit and the second frequency unit are both contained in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit are not overlapped.

6. The method of claim 5, wherein the method further comprises:

The access network element receives the first indication information and the second indication information from the management function network element;

The access network element sends a third message and a fourth message in the first frequency unit and the second frequency unit respectively according to the first indication information and the second indication information, wherein the third message is used for activating the third tag belonging to the at least one first tag in the coverage area, and the fourth message is used for activating the third tag belonging to the at least one second tag in the coverage area.

7. The method of claim 6, wherein the step of providing the first layer comprises,

Said, in case said at least one third tag belongs to said at least one first tag, comprising: in case the result comprises information indicating the first frequency unit;

the management function network element sending the result to the first operation requester, including:

The management function network element sends the result to the first operation requester according to the first indication information;

Or alternatively

Said, in case said at least one third tag belongs to said at least one second tag, comprising: in case the result comprises the information indicating a second frequency unit;

The management function network element sending the result to the second operation requester, including:

and the management function network element sends the result to the second operation requester according to the second indication information.

8. A method of tag management, comprising:

The access network element receives a third request from the management function network element, wherein the third request is used for requesting to execute label operation on the at least one first label and the at least one second label;

the access network element sends a first message to a tag in a coverage area, wherein the first message is used for activating a third tag in the coverage area, and the third tag belongs to the at least one first tag or the at least one second tag;

Wherein the at least one first tag and the at least one second tag belong to different operation requesters, respectively.

9. The method of claim 8, wherein the step of determining the position of the first electrode is performed,

The third request includes information of the at least one first tag and information of the at least one second tag;

the first message includes information of the at least one first tag and information of the at least one second tag;

Or alternatively

The third request comprises information of a first area corresponding to the information of the at least one first tag and information of a second area corresponding to the information of the at least one second tag;

the first message includes information of the first region and information of the second region.

10. The method according to claim 8 or 9, characterized in that the method further comprises:

the access network element receives a second message from the third tag, wherein the second message comprises information of the third tag;

The access network element sends a result of performing the label operation on the third label to the management function network element, where the result is used to indicate that the label operation has been performed on the third label.

11. The method according to any of claims 8 to 10, wherein the first message comprises a third message and a fourth message, and wherein the access network element sends the first message to tags within coverage, comprising:

The access network element sends a third message through the first frequency unit, wherein the third message is used for activating the third tag belonging to the at least one first tag in the coverage area;

the access network element sends a fourth message through a second frequency unit, the fourth message is used for activating the third tag belonging to the at least one second tag in the coverage area, and the third message and the fourth message are sent simultaneously.

12. The method of claim 11, wherein the method further comprises:

The access network element receives first indication information and second indication information from the management function network element, the first indication information is used for indicating that the at least one first label corresponds to the first frequency unit, the second indication information is used for indicating that the at least one second label corresponds to the second frequency unit, the first frequency unit and the second frequency unit are both contained in a third frequency unit applicable to the access network element, and the first frequency unit and the second frequency unit are not overlapped.

13. The method according to claim 11 or 12, wherein the access network element receiving the second message from the third tag comprises:

in the case that the third tag belongs to the at least one first tag, the access network element receives the second message from the third tag through the first frequency unit;

Or alternatively

And in the case that the third tag belongs to the at least one second tag, the access network element receives the second message from the third tag through the second frequency unit.

14. The method of claim 13, wherein the method further comprises:

In case the third tag belongs to the at least one first tag, the result comprises information indicating the first frequency unit; or alternatively

In case the third tag belongs to the at least one second tag, the result comprises information indicating the second frequency unit.

15. A method of tag management, comprising:

the access network element receives an eighth request from an operation requester, wherein the eighth request is used for indicating to execute a label operation on one label;

the access network element sends a tag selection message according to the eighth request, wherein the tag selection message is used for indicating the tag to respond to the tag selection message, and the tag selection message comprises first identification information of the tag;

the access network element receives a seventh message from the tag, the seventh message being configured to respond to the tag selection message, the seventh message including second identification information of the tag.

16. The method of claim 15, wherein the step of determining the position of the probe is performed,

The access network element and the one tag do not perform a random access procedure before the access network element receives the seventh message from the tag.

17. A method for label management, characterized in that,

A tag receives a tag selection message from an access network element, wherein the tag selection message is used for indicating the tag to respond to the tag selection message, and the tag selection message comprises first identification information of the tag;

and responding to the label selection message, and sending a seventh message to the access network element by the label, wherein the seventh message comprises second identification information of the label.

18. The method of claim 17, wherein the step of determining the position of the probe is performed,

And before the first tag sends a seventh message to the access network element, the one tag and the access network element do not execute a random access procedure.

19. A method of tag management, comprising:

The access network element receives an eighth message from the tag, the eighth message being used for responding to the tag selection message, the eighth message comprising verification information;

In response to the eighth message, the access network element sends a ninth message to the tag, where the ninth message includes the authentication information, and the ninth message is used to request the tag to authenticate;

In response to the ninth message, the access network element receives a seventh message from the tag, the seventh message including second identification information of the tag.

20. The method of claim 19, wherein the authentication information includes one or more of:

Random number, check value, secret key, public key, private key.

21. A method of tag management, comprising:

In response to the tag selection message, the tag sends an eighth message to the access network element, the eighth message including authentication information;

The tag receives a ninth message from the access network element, wherein the ninth message is used for responding to the eighth message, the ninth message comprises the verification information, and the ninth message is used for requesting the tag to verify;

and in the case that the tag passes the verification, responding to the ninth message, and sending a seventh message to the access network element by the tag, wherein the seventh message comprises second identification information of the tag.

22. The method of claim 21, wherein the authentication information includes one or more of:

Random number, check value, secret key, public key, private key.

23. An apparatus for tag management, comprising: comprising means for implementing any one of claims 1 to 7, or any one of claims 8 to 14, or any one of claims 15 or 16 or 17 or 18 or 19 or 20 or 21 or 22.

24. An apparatus for tag management, comprising:

A processor for executing a computer program stored in a memory to cause the apparatus to perform any one of claims 1 to 7, or any one of claims 8 to 14, or any one of claims 15 or 16 or 17 or 18 or 19 or 20 or 21 or 22.

25. The apparatus of claim 24, further comprising the memory.

26. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when run on a computer, causes the computer to perform any one of claims 1 to 7, or any one of claims 8 to 14, or any one of claims 15 or 16 or 17 or 18 or 19 or 20 or 21 or 22.

27. A communication system comprising a management function network element and an access network element;

The management function network element is used for receiving a first request from a first operation requester, wherein the first request is used for requesting to execute a label operation on at least one first label, and is also used for receiving a second request from a second operation requester, and the second request is used for requesting to execute the label operation on at least one second label; in the case that the at least one first tag and the at least one second tag both belong to the coverage area of an access network element, the management function network element sends a third request to the access network element, where the third request is used to request the at least one first tag and the at least one second tag to execute the tag operation; the access network element sends a first message to a tag in a coverage area, wherein the first message is used for activating a third tag in the coverage area, and the third tag belongs to the at least one first tag or the at least one second tag.