A communication method, controller and RFID system in RFID architecture

By introducing controllers in the RFID architecture, using public protocols to realize communication between receivers and exciters, the high cost and complexity problems caused by private protocols in the prior art are solved, and the compatibility and scalability of the system are improved.

CN115567904BActive Publication Date: 2024-11-08CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110750488.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-07-02
Publication Date
2024-11-08
Estimated Expiration
2041-07-02

AI Technical Summary

Technical Problem

The existing RFID architectures are cost-effective, complex, and poor compatibility and scalability because the communication between the receiver and the exciter is based on a private protocol.

Method used

Introducing a controller to establish a communication connection between the receiver and the exciter based on a public protocol, and send resource scheduling commands to the receiver through the controller, thereby realizing the control of the tag, reducing the receiver and the exciter in software and hardware. private agreements support requirements.

Benefits of technology

Reduces the cost and complexity of RFID architectures, improves compatibility and scalability, and simplifies interoperability between devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115567904B_ABST
    Figure CN115567904B_ABST
Patent Text Reader

Abstract

The present application discloses a communication method, a controller and an RFID architecture in an RFID architecture, wherein the RFID architecture includes a controller, an exciter, a tag and a receiver; the method includes: the controller establishes a first communication connection based on a public protocol with the exciter, and establishes a second communication connection based on a public protocol with the receiver; the controller sends a first command and / or a second command to the exciter based on the first communication connection, and sends a third command to the receiver based on the second communication connection; wherein the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; the third command is used to schedule resources for the receiver.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of radio frequency identification (RFID) technology, and in particular to a communication method, a controller and an RFID architecture in an RFID architecture. Background Art

[0002] At present, the RFID architecture includes a receiver, an exciter and a tag, and the three devices in the RFID architecture can communicate with each other. For the communication between the receiver and the exciter, the communication between the receiver and the exciter is realized based on a private protocol.

[0003] Since the RFID architecture realizes communication between the receiver and the exciter based on a private protocol, if you want to use the RFID architecture, you need to obtain authorization for the private protocol, and the receiver and the exciter need to support the private protocol in terms of software and hardware. This greatly increases the cost and complexity of the RFID architecture, and the compatibility and scalability of the RFID architecture are poor. Summary of the invention

[0004] To solve the above technical problems, embodiments of the present invention provide a communication method in an RFID architecture, an RFID architecture, a controller, a chip, and a computer-readable storage medium.

[0005] The embodiment of the present application provides a communication method in an RFID architecture, wherein the RFID architecture includes a controller, an actuator, a tag, and a receiver; the method includes:

[0006] The controller establishes a first communication connection based on a public protocol with the actuator, and establishes a second communication connection based on a public protocol with the receiver;

[0007] The controller sends a first command and / or a second command to the actuator based on the first communication connection, and sends a third command to the receiver based on the second communication connection;

[0008] Among them, the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; and the third command is used to schedule resources for the receiver.

[0009] An embodiment of the present application provides a controller, the controller comprising:

[0010] An establishing unit, configured to establish a first communication connection based on a public protocol with the exciter, and to establish a second communication connection based on a public protocol with the receiver;

[0011] a communication unit, configured to send a first command and / or a second command to the actuator based on the first communication connection, and to send a third command to the receiver based on the second communication connection;

[0012] Among them, the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; and the third command is used to schedule resources for the receiver.

[0013] The embodiment of the present application provides an RFID architecture, which includes a controller, an actuator, a tag and a receiver; wherein:

[0014] The controller is used to establish a first communication connection based on a public protocol with the exciter, and to establish a second communication connection based on a public protocol with the receiver; to send a first command and / or a second command to the exciter based on the first communication connection, and to send a third command to the receiver based on the second communication connection; wherein the first command is used to perform resource scheduling for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; and the third command is used to perform resource scheduling for the receiver.

[0015] An embodiment of the present application provides a communication device, including: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above methods.

[0016] The chip provided in the embodiment of the present application includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes any one of the above methods.

[0017] The core computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above methods.

[0018] In the technical solution of the embodiment of the present application, a controller is introduced into the RFID architecture. On the one hand, communication between the controller and the actuator is realized based on a public protocol, and on the other hand, communication between the controller and the receiver is realized based on a public protocol. The receiver and the actuator do not need to support private protocols in terms of software and hardware, which greatly reduces the cost and complexity of the RFID architecture, and the compatibility and scalability of the RFID architecture are good. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a schematic diagram of an RFID architecture;

[0020] Figure 2 The communication method in the RFID architecture provided in the embodiment of the present application is shown in FIG. Figure 1 ;

[0021] Figure 3 This is a schematic diagram of the RFID architecture provided in the embodiment of the present application. Figure 1 ;

[0022] Figure 4 This is a schematic diagram of the RFID architecture provided in the embodiment of the present application. Figure 2 ;

[0023] Figure 5 It is a schematic diagram of the protocol architecture provided in the embodiment of the present application;

[0024] Figure 6 The communication method in the RFID architecture provided in the embodiment of the present application is shown in FIG. Figure 2 ;

[0025] Figure 7 The communication method in the RFID architecture provided in the embodiment of the present application is shown in FIG. Figure 3 ;

[0026] Figure 8 It is a schematic diagram of the structural composition of the controller provided in an embodiment of the present application;

[0027] Fig. 9 This is a schematic diagram of the RFID architecture provided in the embodiment of the present application. Figure 3 ;

[0028] Fig.10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0029] Fig.11 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] It should be noted that the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the previous and subsequent associated objects are in an "or" relationship. It should also be understood that the "correspondence" mentioned in the embodiments of the present application can indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0032] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0033] Figure 1 is a schematic diagram of an RFID architecture, such as Figure 1 As shown, the RFID architecture includes a receiver, an activator and a tag, wherein the activator can also be called a reader. Figure 1 The RFID architecture shown is a separated RFID architecture, that is, the exciter, the receiver and the tag are separated in hardware. The functions of the three devices in the RFID architecture are described below.

[0034] 1) Receiver

[0035] The receiver's functions are mainly as follows:

[0036] I) is responsible for selecting the exciter and sending control commands to the exciter, triggering the exciter to emit an excitation signal through the control commands.

[0037] II) is responsible for sending resource configuration commands to the exciter, and performing resource configuration on the exciter through the resource configuration commands. As an example, the resource configuration command includes but is not limited to at least one of the following: frequency hopping sequence configuration signaling, time division configuration signaling, frequency division configuration signaling, antenna configuration signaling, transmission power configuration command, etc.

[0038] III) is responsible for receiving and demodulating the reflected signal sent by the tag.

[0039] 2) Exciter

[0040] The functions of the exciter are mainly as follows:

[0041] I) is responsible for transmitting the excitation signal, through which the tag is charged.

[0042] II) is responsible for sending control commands to the tag. As an example, the control command includes but is not limited to at least one of the following: a tag selection command, a tag identification command, and a tag read and write command.

[0043] The select command corresponds to the operation of selecting the number of tags for inventory and access. The inventory command corresponds to the operation of identifying tags. The access command corresponds to the operation of communicating with tags, such as the operation of reading from tags or writing to tags.

[0044] III) After receiving the control command or resource configuration command sent by the receiver, reply a confirmation message to the receiver.

[0045] 3) Tags

[0046] The main functions of the tag are: after the tag is charged, it sends a reflected signal to the receiver.

[0047] like Figure 1 As shown, the communication between the receiver and the exciter is implemented based on a private protocol. In other words, the commands exchanged between the receiver and the exciter are commands based on the private protocol. The communication between the receiver and the tag is implemented based on a public protocol. In other words, the signals exchanged between the receiver and the tag are signals based on the public protocol. The communication between the exciter and the tag is implemented based on a public protocol. In other words, the signaling exchanged between the exciter and the tag is signaling based on the public protocol. In addition, the communication between the receiver and the exciter is implemented based on the frequency band 840-845, the communication between the receiver and the tag is implemented based on the frequency band 920-925, and the communication between the exciter and the tag is implemented based on the frequency band 920-925.

[0048] from Figure 1 It can be seen that for the communication between the receiver and the exciter, the communication between the receiver and the exciter is realized based on a private protocol. Since the RFID architecture realizes the communication between the receiver and the exciter based on a private protocol, if you want to use the RFID architecture, you need to obtain authorization for the private protocol, and the receiver and the exciter need to support the private protocol in terms of software and hardware, which greatly increases the cost and complexity of the RFID architecture, and the compatibility and scalability of the RFID architecture are poor.

[0049] To this end, the following technical solutions of the embodiments of the present application are proposed. The embodiments of the present application propose an optimized RFID architecture, and customize new interaction commands and interaction processes based on the public protocol for the RFID architecture, replacing Figure 1 The interactive commands and interactive flow shown.

[0050] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0051] Figure 2 is a flow chart of a communication method in an RFID architecture provided in an embodiment of the present application, wherein the RFID architecture includes a controller, an actuator, a tag, and a receiver; Figure 2 As shown, the communication method in the RFID architecture includes the following steps:

[0052] Step 201: The controller establishes a first communication connection based on a public protocol with the actuator, and establishes a second communication connection based on a public protocol with the receiver.

[0053] In the embodiment of the present application, a controller is introduced into the RFID architecture, and the controller may also be referred to as an RFID control unit. The embodiment of the present application does not limit the name of the controller. In addition to the controller, the RFID architecture also includes an exciter, a tag, and a receiver.

[0054] In some optional embodiments, such as Figure 3 As shown, taking the controller as an RFID control unit as an example, the RFID architecture includes an RFID control unit, an exciter, a tag and a receiver, wherein the RFID control unit and the receiver are independently arranged, in other words, the RFID control unit is located outside the receiver.

[0055] In some optional embodiments, such as Figure 4 As shown, taking the controller as an RFID control unit as an example, the RFID architecture includes an RFID control unit, an exciter, a tag and a receiver, wherein the RFID control unit and the receiver are combined, in other words, the RFID control unit is located inside the receiver.

[0056] In the embodiment of the present application, the controller and the actuator communicate based on a public protocol, and the controller and the receiver communicate based on a public protocol. The actuator and the tag communicate based on a public protocol, and the receiver and the tag communicate based on a public protocol.

[0057] Here, the communication between the activator and the tag, and the communication between the receiver and the tag can refer to the aforementioned Figure 1 Understand the relevant plans.

[0058] Here, since the controller and the exciter communicate based on a public protocol, and the controller and the receiver communicate based on a public protocol, the controller, the exciter, and the receiver need to support a public protocol. In some optional implementations, the public protocol includes but is not limited to: WIFI protocol, 5G protocol, Ethernet protocol.

[0059] Take the exciter and receiver as an example. Figure 5 The left side of Figure 1 The protocol architecture supported by the exciter and receiver shown in the figure, the exciter and receiver support two sets of protocols, namely, RFID protocol and private protocol, wherein the RFID protocol includes physical layer-1 (PHY-1) and tag identification layer (TID), and the private protocol includes physical layer-2 (PHY-2), layer 2 (L2) and layer 3 (L3). Figure 5 The right side of Figure 3 and Figure 4 The protocol architecture supported by the exciter and receiver shown in the figure, the exciter and receiver support two sets of protocols, namely, RFID protocol and public protocol, wherein the RFID protocol includes physical layer-1 (PHY-1) and tag identification layer (TID), and the public protocol includes at least one of the following: WIFI protocol, 5G protocol, Ethernet protocol.

[0060] In the embodiment of the present application, the controller and the actuator communicate based on a public protocol, which is specifically manifested as: the controller and the actuator establish a first communication connection based on a public protocol. The controller and the receiver communicate based on a public protocol, which is specifically manifested as: the receiver establishes a second communication connection based on a public protocol.

[0061] In some optional embodiments, the controller establishes a first communication connection based on a public protocol with the exciter, and establishes a second communication connection based on a public protocol with the receiver, including: the controller establishes a first TCP / IP connection with the exciter, and establishes a second TCP / IP connection with the receiver.

[0062] Here, "TCP / IP connection" can be understood as "TCP connection and / or IP connection".

[0063] Step 202: The controller sends a first command and / or a second command to the exciter based on the first communication connection, and sends a third command to the receiver based on the second communication connection; wherein the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; and the third command is used to schedule resources for the receiver.

[0064] In an embodiment of the present application, the controller sends a first command and / or a second command to the actuator based on the first communication connection, and sends a third command to the receiver based on the second communication connection.

[0065] Here, the command sent by the controller to the exciter includes a first command and / or a second command, wherein the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflected signal to the receiver. Here, the first command is a non-transparent transmission command, and the second command is a transparent transmission command.

[0066] Here, the command sent by the controller to the receiver includes a third command, wherein the third command is used to perform resource scheduling on the receiver. Here, the third command is a non-transparent transmission command.

[0067] In the embodiment of the present application, the first command and the third command are commands customized based on a public protocol. It can be understood that the first command and the third command belong to private commands based on a public protocol. As an example, the functions implemented by the first command include: waking up the exciter, turning off the exciter, selecting the exciter, and configuring the resource configuration of the exciter. Here, the resource configuration includes, for example, frequency hopping sequence configuration, frequency hopping sequence configuration signaling, time division configuration signaling, frequency division configuration signaling, antenna configuration signaling, transmission power configuration command, etc. As an example, the functions implemented by the third command include: waking up the receiver, turning off the receiver, selecting the receiver, and configuring the resource configuration of the receiver. Here, the resource configuration includes, for example, frequency hopping sequence configuration, frequency hopping sequence configuration signaling, time division configuration signaling, frequency division configuration signaling, antenna configuration signaling, transmission power configuration command, etc.

[0068] In the embodiment of the present application, the second command is a public command based on a public protocol. As an example, the functions implemented by the second command include: tag selection (select), tag identification (inventory), and tag reading and writing (access).

[0069] In the above scheme, the transparent transmission command is used to realize the controller's control over the tag. After the controller sends the transparent transmission command to the exciter, the exciter forwards the transparent transmission command to the tag, thereby realizing the control over the tag. Here, the transparent transmission command sent by the exciter to the tag is called a control command.

[0070] In the above solution, the non-transparent command is used to implement resource scheduling of the controller to the exciter and the receiver.

[0071] It should be noted that the description of "resource scheduling" can also be replaced by "resource configuration".

[0072] In some optional implementations, after the controller sends the first command and / or the second command to the actuator based on the first communication connection, the controller receives a first response message sent by the actuator based on the first communication connection. As an example, the first response message may be a 200OK message.

[0073] In some optional implementations, after sending the third command to the receiver based on the second communication connection, the controller receives a second response message sent by the receiver based on the second communication connection. As an example, the second response message may be a 200OK message.

[0074] In some optional embodiments, after the controller sends the second command to the exciter based on the first communication connection, the controller sends a fourth command to the receiver based on the second communication connection, and the fourth command is used to trigger the receiver to receive the reflection signal. In one implementation, after the receiver receives the fourth command, it starts to monitor the reflection signal sent by the tag. In another implementation, after the receiver receives the fourth command, it starts to monitor the reflection signal sent by the tag according to the time indicated by the fourth command.

[0075] In some optional implementations, the controller sends a first command to the actuator through an application layer Hypertext Transfer Protocol (HTTP) or Message Queuing Telemetry Transport (MQTT) based on the first TCP / IP connection, and the first command carries resource scheduling information of the actuator. As an example, the resource scheduling information of the actuator includes at least one of the following:

[0076] an identification of the exciter;

[0077] frequency configuration of the exciter;

[0078] The power configuration of the exciter;

[0079] The antenna configuration of the exciter;

[0080] The transmission frame number of the exciter;

[0081] The receive frame number of the exciter.

[0082] In some optional implementations, the controller sends a second command to the actuator via HTTP or MQTT at the application layer based on the first TCP / IP connection, and the second command carries a control command of the tag. As an example, the control command of the tag includes at least one of the following: a tag selection command, a tag identification command, and a tag read and write command.

[0083] In some optional implementations, the controller sends a third command to the receiver through HTTP or MQTT at the application layer based on the second TCP / IP connection, and the third command carries resource scheduling information of the receiver. As an example, the resource scheduling information of the receiver includes at least one of the following:

[0084] an identification of the receiver;

[0085] a frequency configuration of the receiver;

[0086] a power configuration of the receiver;

[0087] the antenna configuration of the receiver;

[0088] The send frame number of the receiver;

[0089] The received frame number of the receiver.

[0090] In the embodiment of the present application, in order to implement the communication method in the above RFID architecture, each device in the RFID architecture needs to support

[0091] Controllers, actuators and receivers support public protocols.

[0092] The following describes the interaction between devices in the RFID architecture in conjunction with specific application examples. It should be noted that the following application examples are described by taking the controller as an RFID control unit.

[0093] Application Example 1

[0094] In this example, after a TCP / IP connection is established between the RFID control unit and the actuator, the RFID control unit uses HTTP through the application layer to schedule resources for the actuator. Specifically, the RFID control unit uses HTTP through the application layer to send a command for resource scheduling (i.e., the first command in the above scheme) to the actuator, and the command carries the resource scheduling information of the actuator. As an example, the content of the command sent by the RFID control unit to the actuator through the application layer using HTTP can be referred to as shown in the following Table 1.

[0095]

[0096] Table 1

[0097] In the contents shown in Table 1, the bold part is the content carried in the command sent by the RFID control unit to the exciter, which includes resource scheduling information. In specific implementation, these contents can be transmitted in the message body or through the extended header field through methods such as HTTP PUT or HTTP POST. This application does not limit the representation method of the message body, and the message body can be represented by JSON or other data protocols. After receiving the command sent by the RFID control unit, the exciter replies to the RFID control unit with a response message. As an example, the response message can be a 200OK message.

[0098] Application Example 2

[0099] In this example, after a TCP / IP connection is established between the RFID control unit and the receiver, the RFID control unit uses HTTP through the application layer to schedule resources for the receiver. Specifically, the RFID control unit sends a command for resource scheduling (i.e., the third command in the above scheme) to the receiver through the application layer using HTTP, and the command carries the resource scheduling information of the receiver. As an example, the content of the command sent by the RFID control unit to the receiver through the application layer using HTTP can be shown in Table 2 below.

[0100]

[0101]

[0102] Table 2

[0103] In the contents shown in Table 2, the bold part is the content carried in the command sent by the RFID control unit to the receiver, which includes resource scheduling information. In specific implementation, these contents can be transmitted in the message body or through the extended header field through methods such as HTTP PUT or HTTP POST. This application does not limit the representation method of the message body, and the message body can be represented by JSON or other data protocols. After receiving the command sent by the RFID control unit, the receiver replies to the RFID control unit with a response message. As an example, the response message can be a 200OK message.

[0104] Application Example 3

[0105] In this example, after a TCP / IP connection is established between the RFID control unit and the actuator, the RFID control unit controls the tag through HTTP through the application layer. Specifically, the RFID control unit sends a command for controlling the tag (i.e., the second command in the above solution) to the actuator through HTTP through the application layer. The functions implemented by the command include: tag selection (select), tag identification (inventory), and tag reading and writing (access). As an example, the content of the command sent by the RFID control unit to the actuator through HTTP through the application layer can be referred to as shown in Table 3 below.

[0106]

[0107] Table 3

[0108] In the contents shown in Table 3, the bold part is the content carried in the command sent by the RFID control unit to the actuator, which includes the control command for the tag. In specific implementation, these contents can be transmitted in the message body or through the extended header field through methods such as HTTP PUT or HTTP POST. This application does not limit the representation method of the message body, and the message body can be represented by JSON or other data protocols. After receiving the command sent by the RFID control unit, the actuator replies to the RFID control unit with a response message. As an example, the response message can be a 200OK message.

[0109] Application Example 4

[0110] In this example, after a TCP / IP connection is established between the RFID control unit and the exciter, the RFID control unit uses MQTT through the application layer to schedule resources of the exciter. Specifically, the RFID control unit sends a command for resource scheduling (i.e., the first command in the above scheme) to the exciter through the application layer using MQTT, and the command carries the resource scheduling information of the exciter. As an example, the content of the command sent by the RFID control unit to the exciter through the application layer using MQTT can be referred to as shown in Table 4 below.

[0111]

[0112] Table 4

[0113] In the contents shown in Table 4, the bold part is the content carried in the command sent by the RFID control unit to the actuator, which includes resource scheduling information. In specific implementation, these contents can be transmitted in the payload through the MQTT publish message. This application does not limit the representation method of the payload, and the payload can be represented by JSON or other data protocols.

[0114] Application Example 5

[0115] In this example, after a TCP / IP connection is established between the RFID control unit and the receiver, the RFID control unit uses MQTT through the application layer to schedule resources for the receiver. Specifically, the RFID control unit sends a command for resource scheduling (i.e., the first command in the above scheme) to the receiver through the application layer using MQTT, and the command carries the resource scheduling information of the receiver. As an example, the content of the command sent by the RFID control unit to the receiver through the application layer using MQTT can be referred to as shown in Table 5 below.

[0116]

[0117] Table 5

[0118] In the contents shown in Table 5, the bold part is the content carried in the command sent by the RFID control unit to the receiver, which includes resource scheduling information. In specific implementation, these contents can be transmitted in the payload through the MQTT publish message. This application does not limit the representation method of the payload, and the payload can be represented by JSON or other data protocols.

[0119] Application Example 6

[0120] In this example, after a TCP / IP connection is established between the RFID control unit and the actuator, the RFID control unit controls the tag through the application layer using MQTT. Specifically, the RFID control unit sends a command for controlling the tag (i.e., the second command in the above scheme) to the actuator through the application layer using MQTT. The functions implemented by the command include: tag selection (select), tag identification (inventory), and tag reading and writing (access). As an example, the content of the command sent by the RFID control unit to the actuator through the application layer using MQTT can be referred to as shown in Table 6 below.

[0121]

[0122] Table 6

[0123] In the contents shown in Table 6, the bold part is the content carried in the command sent by the RFID control unit to the actuator, which includes the control command for the tag. In specific implementation, these contents can be transmitted in the payload through the MQTT publish message. This application does not limit the representation method of the payload, and the payload can be represented by JSON or other data protocols.

[0124] Application Example 7

[0125] In this example, the RFID control unit configures the resources of the exciter and receiver. Figure 6 , including the following steps:

[0126] Step 601: The RFID control unit sends a first command for scheduling resources of the actuator to the actuator.

[0127] Here, the specific implementation of the first command can refer to the aforementioned related solutions.

[0128] Step 602: The actuator sends a 200 OK message to the RFID control unit.

[0129] Step 603: The RFID control unit sends a third command for scheduling resources for the receiver to the receiver.

[0130] Here, the specific implementation of the third command can refer to the aforementioned related solutions.

[0131] Step 604: The receiver sends a 200 OK message to the RFID control unit.

[0132] It should be noted that the execution order of the above steps 601 and 602, and the above steps 603 and 604 is not limited. Steps 601 and 602 may be executed first, and then steps 603 and 604. Alternatively, steps 603 and 604 may be executed first, and then steps 601 and 602.

[0133] Through the above steps 601 to 604, the RFID control unit completes resource configuration within one cycle.

[0134] Application Example 8

[0135] In this example, the RFID control unit can coordinate the delay between the exciter and the receiver, referring to Figure 7 , including the following steps:

[0136] Step 701: The RFID control unit sends a transparent transmission command to the actuator.

[0137] Here, the specific implementation of the transparent transmission command can refer to the solution related to the aforementioned second command.

[0138] Step 702: The actuator sends a 200 OK message to the RFID control unit.

[0139] Step 703: The RFID control unit sends a receiving command to the receiver.

[0140] Here, the receive command is used to trigger the receiver to start receiving or start monitoring the reflected signal sent by the tag.

[0141] Step 704: The actuator sends a transparent transmission command to the tag.

[0142] Here, the specific implementation of the transparent transmission command can refer to the solution related to the control command associated with the aforementioned second command.

[0143] Step 705: The tag sends a reflected signal to the receiver.

[0144] Step 706: The receiver sends a 200 OK message to the RFID control unit.

[0145] It should be noted that the execution order of step 703 is after step 701 and before step 704. Alternatively, step 703 may be executed simultaneously with step 701 or step 704.

[0146] Through the above steps 701 to 706, the RFID control unit completes a read and write operation on the tag.

[0147] Figure 8 is a schematic diagram of the structure of a controller provided in an embodiment of the present application, and the controller is applied in an RFID architecture, such as Figure 8 As shown, the controller includes:

[0148] An establishing unit 801 is used to establish a first communication connection based on a public protocol with the exciter, and to establish a second communication connection based on a public protocol with the receiver;

[0149] a communication unit 802, configured to send a first command and / or a second command to the actuator based on the first communication connection, and to send a third command to the receiver based on the second communication connection;

[0150] Among them, the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; and the third command is used to schedule resources for the receiver.

[0151] In some optional implementations, the establishing unit 801 is used to establish a first TCP / IP connection with the exciter, and to establish a second TCP / IP connection with the receiver.

[0152] In some optional implementations, the communication unit 802 is used to send a first command to the actuator through HTTP or MQTT of the application layer based on the first TCP / IP connection, where the first command carries resource scheduling information of the actuator.

[0153] In some optional implementations, the resource scheduling information of the actuator includes at least one of the following:

[0154] an identification of the exciter;

[0155] frequency configuration of the exciter;

[0156] The power configuration of the exciter;

[0157] The antenna configuration of the exciter;

[0158] The transmission frame number of the exciter;

[0159] The receive frame number of the exciter.

[0160] In some optional implementations, the communication unit 802 is used to send a second command to the actuator through HTTP or MQTT at the application layer based on the first TCP / IP connection, where the second command carries the control command of the tag.

[0161] In some optional implementations, the tag control command includes at least one of the following: a tag selection command, a tag identification command, and a tag read and write command.

[0162] In some optional implementations, the communication unit 802 is used to send a third command to the receiver through HTTP or MQTT at the application layer based on the second TCP / IP connection, where the third command carries resource scheduling information of the receiver.

[0163] In some optional implementations, the resource scheduling information of the receiver includes at least one of the following:

[0164] an identification of the receiver;

[0165] a frequency configuration of the receiver;

[0166] a power configuration of the receiver;

[0167] the antenna configuration of the receiver;

[0168] The send frame number of the receiver;

[0169] The received frame number of the receiver.

[0170] In some optional implementations, the communication unit 802 is configured to receive a first response message sent by the actuator based on the first communication connection after sending a first command and / or a second command to the actuator based on the first communication connection.

[0171] In some optional implementations, the communication unit 802 is configured to receive a second response message sent by the receiver based on the second communication connection after sending a third command to the receiver based on the second communication connection.

[0172] In some optional embodiments, the communication unit 802 is used to send a fourth command to the receiver based on the second communication connection after sending a second command to the exciter based on the first communication connection, and the fourth command is used to trigger the receiver to receive the reflected signal.

[0173] Those skilled in the art should understand that Figure 8 The implementation functions of each unit in the controller shown can be understood by referring to the relevant description of the aforementioned method. Figure 8 The functions of each unit in the controller shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0174] Fig. 9 is a schematic diagram of the RFID architecture provided in the embodiment of the present application, such as Fig. 9 As shown, the RFID architecture includes a controller 901, an exciter 902, a tag 903 and a receiver 904; wherein,

[0175] The controller 901 is used to establish a first communication connection based on a public protocol with the exciter 902, and to establish a second communication connection based on a public protocol with the receiver 904; to send a first command and / or a second command to the exciter 902 based on the first communication connection, and to send a third command to the receiver 904 based on the second communication connection; wherein the first command is used to perform resource scheduling for the exciter 902; the second command is used to trigger the exciter 902 to send a control command to the tag 903, thereby triggering the tag 903 to send a reflection signal to the receiver 904; and the third command is used to perform resource scheduling for the receiver 904.

[0176] In some optional implementations, the controller 901 and the receiver 904 are independently configured.

[0177] In some optional implementations, the controller 901 and the receiver 904 are combined into one.

[0178] Those skilled in the art should understand that Fig. 9 The implementation functions of each device in the RFID architecture shown can be understood by referring to the relevant description of the aforementioned method.

[0179] Fig.101 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. The communication device may be a controller, a receiver, an actuator, or a tag in the above RFID architecture. Fig.10 The communication device 1000 shown includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0180] Alternatively, if Fig.10 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0181] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0182] Alternatively, if Fig.10 As shown, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0183] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0184] The communication device 1000 can implement the corresponding processes in each method of the embodiments of the present application, which will not be described here for the sake of brevity.

[0185] Fig.11 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.11 The chip 1100 shown includes a processor 1110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0186] Alternatively, if Fig.11 As shown, the chip 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0187] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0188] Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0189] Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0190] Optionally, the chip can be applied to a controller, or a receiver, or an exciter, or a tag in the RFID architecture in the embodiments of the present application, and the chip can implement the corresponding processes in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0191] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0192] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0193] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0194] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0195] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0196] Optionally, the computer-readable storage medium can be applied to a controller, or a receiver, or an exciter, or a tag in the RFID architecture in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0197] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0198] Optionally, the computer program product can be applied to a controller, or a receiver, or an exciter, or a tag in the RFID architecture in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes in the various methods in the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0199] The embodiment of the present application also provides a computer program.

[0200] Optionally, the computer program may be applied to a controller, or a receiver, or an exciter, or a tag in the RFID architecture in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

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

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

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

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

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

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

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

Claims

1. A communication method in a radio frequency identification (RFID) architecture, characterized in that: The RFID architecture includes a controller, an actuator, a tag and a receiver; the method includes: The controller establishes a first communication connection based on a public protocol with the actuator, and establishes a second communication connection based on a public protocol with the receiver; The controller sends a first command and / or a second command to the actuator based on the first communication connection, and sends a third command to the receiver based on the second communication connection; Among them, the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; the third command is used to schedule resources for the receiver; the first command and the third command are non-transparent transmission commands, and the second command is a transparent transmission command.

2. The method according to claim 1, characterized in that The controller establishes a first communication connection based on a public protocol with the actuator, and establishes a second communication connection based on a public protocol with the receiver, including: The controller establishes a first TCP / IP connection with the actuator and a second TCP / IP connection with the receiver.

3. The method according to claim 2, characterized in that The controller sends a first command to the actuator based on the first communication connection, comprising: The controller sends a first command to the actuator through HTTP or MQTT at the application layer based on the first TCP / IP connection, where the first command carries resource scheduling information of the actuator.

4. The method according to claim 3, characterized in that The resource scheduling information of the actuator includes at least one of the following: an identification of the exciter; frequency configuration of the exciter; The power configuration of the exciter; The antenna configuration of the exciter; The transmission frame number of the exciter; The receive frame number of the exciter.

5. The method according to claim 2, characterized in that: The controller sends a second command to the actuator based on the first communication connection, comprising: The controller sends a second command to the actuator through HTTP or MQTT at the application layer based on the first TCP / IP connection, where the second command carries a control command for the tag.

6. The method according to claim 5, characterized in that The control command of the tag includes at least one of the following: a tag selection command, a tag identification command, and a tag read and write command.

7. The method according to claim 2, characterized in that: The controller sends a third command to the receiver based on the second communication connection, comprising: The controller sends a third command to the receiver through HTTP or MQTT at the application layer based on the second TCP / IP connection, where the third command carries resource scheduling information of the receiver.

8. The method according to claim 7, characterized in that The resource scheduling information of the receiver includes at least one of the following: an identification of the receiver; a frequency configuration of the receiver; a power configuration of the receiver; the antenna configuration of the receiver; The send frame number of the receiver; The received frame number of the receiver.

9. The method according to any one of claims 1 to 8, characterized in that After the controller sends the first command and / or the second command to the actuator based on the first communication connection, the method further includes: The controller receives a first response message sent by the actuator based on the first communication connection.

10. The method according to any one of claims 1 to 8, characterized in that After sending a third command to the receiver based on the second communication connection, the method further includes: The controller receives a second response message sent by the receiver based on the second communication connection.

11. The method according to any one of claims 1 to 8, characterized in that After the controller sends a second command to the actuator based on the first communication connection, the method further includes: The controller sends a fourth command to the receiver based on the second communication connection, where the fourth command is used to trigger the receiver to receive the reflected signal.

12. A controller, characterized in that: The controller comprises: An establishing unit, configured to establish a first communication connection based on a public protocol with the exciter, and to establish a second communication connection based on a public protocol with the receiver; a communication unit, configured to send a first command and / or a second command to the actuator based on the first communication connection, and to send a third command to the receiver based on the second communication connection; Among them, the first command is used to schedule resources for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; the third command is used to schedule resources for the receiver; the first command and the third command are non-transparent commands, and the second command is a transparent command.

13. An RFID system, characterized in that: The RFID system includes a controller, an exciter, a tag and a receiver; wherein, The controller is used to establish a first communication connection based on a public protocol with the exciter, and to establish a second communication connection based on a public protocol with the receiver; to send a first command and / or a second command to the exciter based on the first communication connection, and to send a third command to the receiver based on the second communication connection; wherein the first command is used to perform resource scheduling for the exciter; the second command is used to trigger the exciter to send a control command to the tag, thereby triggering the tag to send a reflection signal to the receiver; the third command is used to perform resource scheduling for the receiver; the first command and the third command are non-transparent transmission commands, and the second command is a transparent transmission command.

14. The RFID system according to claim 13, characterized in that: The controller is independently arranged from the receiver; or, The controller is integrated with the receiver.

15. A communication device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 11.

16. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 11.

17. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 11.