Wireless communication method and apparatus

Abstract

Provided are a wireless communication method and apparatus. The method comprises: a first device receives a first message sent by a second device, wherein the first message is used for triggering the first device having the value of a flag bit as a first value to execute a target process, and the target process is used for the first device to report the service data to the second device; and when the first device determines that the target process has been completed, the first device sets the value of the flag bit from the first value to a second value. The second device triggers, by means of the first message, the first device having the value of the flag bit as the first value to execute the target process, and after completing execution of the target process, the triggered first device sets the value of the flag bit from the first value to the second value, thereby helping to prevent the first device from responding to the trigger of the first message again.

Description

Wireless communication method and device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically to a wireless communication method and apparatus. Background Art

[0002] In wireless communication systems, network devices can typically trigger terminal devices to execute a target process. However, this operation can occur in parallel, meaning the network device may trigger multiple terminal devices simultaneously. In this case, preventing a terminal device that has already completed a target process from responding again to the network device's trigger remains an unresolved issue.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and apparatus. The following introduces various aspects of the present application.

[0005] In a first aspect, a wireless communication method is provided, including: a first device receives a first message sent by a second device, the first message is used to trigger the first device whose flag bit has a first value to execute a target process, and the target process is used by the first device to report business data to the second device; if the first device determines that the target process has been completed, the first device sets the value of the flag bit from the first value to the second value.

[0006] According to a second aspect, a wireless communication method is provided, including: a first device receives a first message sent by a second device, wherein the first message is used to trigger the first device to report data; if the first data reporting of the first device is completed, the first device clears the first data from the memory, and / or changes the value of the first identifier from the first value to the second value.

[0007] According to a third aspect, a first device is provided, comprising: a receiving module for receiving a first message sent by a second device, wherein the first message is used to trigger the first device, whose flag bit has a first value, to execute a target process, wherein the target process is used by the first device to report business data to the second device; a determination module for determining whether the target process has been completed; and a setting module for setting the value of the flag bit from the first value to the second value when the determination module determines that the target process has been completed.

[0008] In a fourth aspect, a first device is provided, comprising: a first module for receiving a first message sent by a second device, wherein the first message is used to trigger the first device to report data; and a second module for clearing the first data from the memory after the first data reporting of the first device is completed, and / or changing the value of the first identifier from the first value to the second value.

[0009] In a fifth aspect, a first device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the first device executes the method described in the first aspect or the second aspect.

[0010] In a sixth aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes the method described in the first aspect and the second aspect.

[0011] In a seventh aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first and second aspects.

[0012] In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect and the second aspect.

[0013] In a ninth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first and second aspects.

[0014] In a tenth aspect, a computer program is provided, which enables a computer to execute the method described in the first and second aspects.

[0015] In the present application, the second device triggers the first device whose flag value is the first value to execute the target process through the first message, and after the triggered first device executes the target process, the flag value is set from the first value to the second value, thereby helping to avoid the first device responding to the trigger of the first message again. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a schematic structural diagram of a wireless communication system to which an embodiment of the present application is applicable.

[0017] FIG2 is a schematic diagram of the structure of an IoT communication system applicable to an embodiment of the present application.

[0018] FIG3 is a schematic diagram of the network structure of the IoT communication system.

[0019] FIG4 is a schematic structural diagram of an RF receiver.

[0020] FIG5 is a schematic diagram of the structure of an intermediate frequency receiver.

[0021] FIG6 is a schematic flow chart of an inventory check operation in an RFID system.

[0022] FIG7 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

[0023] FIG8 is a schematic flowchart of a wireless communication method provided in another embodiment of the present application.

[0024] FIG9 is a schematic flowchart of a wireless communication method provided in another embodiment of the present application.

[0025] FIG10 is a schematic flowchart of a wireless communication method provided in another embodiment of the present application.

[0026] FIG11 is a schematic structural diagram of a first device provided in one embodiment of the present application.

[0027] FIG12 is a schematic structural diagram of a first device provided in another embodiment of the present application.

[0028] FIG13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solution in this application will be described below with reference to the accompanying drawings.

[0030] Communication system architecture

[0031] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0032] FIG1 exemplarily shows a network device and a terminal device. Optionally, the wireless communication system 100 may include one or more network devices 110 and / or one or more terminal devices 120. For a network device 110, the one or more terminal devices 120 may all be located within the network coverage of the network device 110, or all be located outside the network coverage of the network device 110, or some may be located within the coverage of the network device 110 and others outside the network coverage of the network device 110. This is not limited in the embodiments of the present application.

[0033] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0034] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0035] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

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

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

[0038] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0039] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0040] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0041] Internet of Things (IoT) technology

[0042] The rise of IoT technology has posed new challenges to communication systems. IoT terminal devices can be used in scenarios such as logistics, warehousing, factory automation, and animal husbandry. IoT terminal devices and network equipment can perform intermittent, simple communications or perform rough location tracking. Even the simplest IoT terminal devices, such as NB-IoT devices used for coal and electricity metering, require batteries for power. However, despite their low energy consumption, the batteries within these devices only last for a few years before eventually becoming depleted. Therefore, batteries in IoT terminal devices require regular replacement, which is labor-intensive. Furthermore, some industrial scenarios are dangerous and unsuitable for manual operation. Consequently, battery-free IoT terminal devices have emerged.

[0043] Battery-free IoT terminal devices are numerous and inexpensive, and generally require no manual maintenance after installation. Radio frequency identification (RFID) terminal devices can, to some extent, meet people's demand for battery-free IoT terminal devices. However, the operation of RFID systems still requires human participation, such as the need for manual handheld readers in some RFID systems. Moreover, the wireless coverage range of a single RFID reader is limited (within 10 meters), so RFID systems deployed over a large area require more manual participation. For example, using an RFID system to take inventory of goods in a large supermarket requires a lot of manpower, material resources, and time.

[0044] IoT Communication System

[0045] Transplanting systems like RFID into cellular networks can effectively address the issue of limited coverage. This is because cellular networks (such as fourth-generation (4G) and 5G systems) have achieved nationwide coverage, or at least coverage of major cities, in some countries or regions (such as China, Europe, and the United States). With this wider network coverage, the communication and positioning process between IoT terminal devices and network devices can be performed without human intervention. Therefore, IoT terminal devices can operate continuously and efficiently. In addition, IoT terminal devices can even operate efficiently in environments unsuitable for human intervention (such as wilderness, mines, and factories). Therefore, when using IoT terminal devices, apart from the initial need to associate the IoT terminal device with a specific object, subsequent data reading, writing, and operation and maintenance can be performed through applications (such as smartphones), which is very convenient and efficient. Such communication systems can be called IoT communication systems or zero-power communication systems.

[0046] As shown in Figure 2, the IoT communication system can be composed of a network device 210 and a terminal device 220. The network device 210 can be called a reader, and the terminal device 220 can be called a tag. The IoT communication system adopts energy harvesting and backscatter communication technology. The network device 210 can send wireless power supply signals, downlink communication signals to the terminal device 220, and receive backscatter signals from the terminal device 220. A basic terminal device 220 may include an energy harvesting module 221, a backscatter communication module 222, and a low-power computing module 223. In addition, the terminal device 220 may also include a memory module (not shown in the figure) for storing some basic information (such as item identification, etc.). Alternatively, the terminal device 220 may also include a sensor module 224 for obtaining sensor data such as ambient temperature and ambient humidity.

[0047] Use cases for IoT communication systems can fall into four broad categories: inventory, sensors, tracking, and commands. Inventory refers to checking for missing items and replenishing missing items as they enter and leave the warehouse. Common sensors include temperature, pressure, and humidity. These sensors can be used in industrial, agricultural, and smart city applications. The information collected by these sensors can be uploaded to a third-party app through the IoT system for monitoring and management. Tracking generally refers to obtaining the approximate location of an object at irregular intervals. For example, users can use their smartphones to track the real-time location of their parcels. Commands, on the other hand, involve operating certain servos through the IoT system. These servos can be connected to IoT end devices. For example, while working or relaxing in the office, people can water their backyard plants using a mobile app. The watering servo can be connected to an IoT end device.

[0048] The network structure of an IoT communication system can be shown in Figure 3, which includes four network topologies. IoT terminal devices derive their energy from the surrounding environment, such as radio frequency (RF), solar energy, thermal energy, mechanical vibration, and wind energy. IoT terminal devices can be divided into three types: Type A, Type B, and Type C. Type A and Type B terminal devices can only communicate by reflecting and modulating received radio waves, a communication method known as backscattering. In other words, Type A and Type B terminal devices cannot actively transmit radio signals, and their power ranges from 1 to 10 microwatts (μW). Type A terminal devices have the lowest transmit power and the lowest hardware complexity, essentially approaching the level of RFID terminal devices. Type B terminal devices have slightly more complex hardware and may include signal amplification devices and certain energy storage devices. Therefore, the communication distance between Type B terminal devices and network devices is greater than that of Type A devices. Type C terminal devices have the ability to actively transmit radio waves, with a transmit power of approximately 1 to 10 milliwatts (mW) and the ability to store a certain amount of energy. All three types of end devices can harvest energy from the environment and operate continuously for several years or even more than 10 years. Furthermore, to conserve energy, Type A and Type B end devices essentially remain dormant until a network device triggers communication with them. They only begin operating when activated by a wireless signal from a network device.

[0049] Receivers in IoT end devices can be divided into two major types: Type 1 and Type 2. Type 1 receivers are wideband receivers, also known as RF receivers. RF receivers use RF bandpass filters to obtain signals within the intended bandwidth, then perform envelope detection and subsequent baseband processing. RF receivers have the simplest structure, with power consumption as low as a few uW or even lower. However, due to the poor precision of RF bandpass filters, even when the target signal occupies a narrow bandwidth, the RF receiver will often receive signals within a wider bandwidth. As a result, the RF receiver's reception process introduces significant noise and interference, resulting in poor reception performance, or in other words, poor reception sensitivity. The typical RF receiver reception process is shown in Figure 4.

[0050] Type 2 receivers are narrowband receivers, such as intermediate frequency (IF) receivers or zero-IF receivers. In addition to using RF bandpass filters to obtain signals within the intended reception bandwidth, narrowband receivers can also downconvert the RF signal and further filter the baseband signal using a low-pass filter to eliminate noise and interference. Therefore, narrowband receivers have a narrow reception bandwidth and good reception performance, or high reception sensitivity. However, narrowband receivers require a local oscillator (LO). LO power consumption is high; even the recommended LO consumes 100uW or more. Therefore, narrowband receivers have high relative power consumption, but their absolute power consumption is very low, making them suitable for use in zero-power devices. The typical reception process of an IF receiver can be shown in Figure 5.

[0051] The above-mentioned type A terminal equipment usually adopts a broadband receiver, the type C communication equipment usually adopts a narrowband receiver, and the type B terminal equipment may adopt one or both types of receivers.

[0052] In addition, in IoT communication systems, the tag density requirements for indoor and outdoor are 150 / 100m respectively. 2 and 0.20 / 100m 2 The indoor network coverage range is 10-50m, and the outdoor network coverage range is 50-500m. Based on this, within the coverage range of a cell (based on classic sector accounting), the minimum and maximum numbers of indoor and outdoor tags can be shown in Table 1.

[0053] Table 1

[0054] Inventory business

[0055] IoT communication systems are most commonly used for inventory operations, in which readers need to ensure that all qualified tags within their coverage area report the information stored in their respective memories, such as the tag's electronic product code (EPC). Typically, readers can trigger the initial access process by sending an inventory request to the tag, thereby reporting the information. However, if all qualified tags respond to the reader's inventory request at the same time, the system will not work. This is because for narrowband systems such as IoT, the wireless resources in domains such as time and frequency are very small compared to the number of tags within the coverage area, so it is necessary to control only some tags to trigger the initial access process.

[0056] Similar problems also exist in RFID systems. The inventory service of the RFID system can be shown in Figure 6. As shown in step S610, when the reader triggers the inventory service, it can first send a Select command to the tag. Through the Select command, the reader can select some tags that meet the conditions and mark them with inventory flags. The value of the inventory flag can be A or B. And the reader can divide the tags into 4 groups, and the inventory flags of the tags in each group can be controlled independently. In step S620, the reader sends a Query command to the tag. The reader can mark which group of tags is being inventoried, and whether the value of the inventory flag of the tag being inventoried is A or B. In the same Query command, a parameter Q can also be carried. After receiving the Query command, the tag that meets the conditions will generate a random number. The range of this random number can be [0, 2 Q -1]. Only tags with this random number equal to 0 will respond to the query command, initiating the initial access process as shown in step S630. Other tags can assign a counter to this random number and decrement this counter by 1 each time they receive a query command requesting an inventory of the same group of tags. When the random number counter reaches 0, the corresponding tag will initiate the initial access process.

[0057] As an example, the content of the above Query command may be as shown in Table 2.

[0058] Table 2

[0059] However, after a tag completes a specific inventory operation (after the initial access process), the value of the tag's inventory flag needs to be flipped (i.e., from A to B or from B to A). Otherwise, the tag will respond to the next Query command for the tag in its group and participate in the inventory process. In RFID systems, a tag's inventory flag flip is conditional. Specifically, a tag can flip its inventory flag if it meets the following conditions: If the tag is in the acknowledged, open, or secured state and receives a QueryAdjust or QueryRep command, and the session parameters of the QueryAdjust or QueryRep command match the session parameters of the previous Query command, and the tag is not in the process of a Kill or Access command, then the tag can flip the inventory flag of its current session and transition to the Ready state. The Kill and Access commands are used to deactivate a tag (rarely used) or change a tag from the open or secured state to the secured state. The Kill and Access commands can be used to perform specific control procedures after the tag completes initial access. Tags can also perform various memory read and write operations, which are not detailed here.

[0060] Based on the above description, in an RFID system's inventory service, if a reader is currently counting a tag, the tag's inventory flag will be flipped after the count is complete, unless the tag is in the process of a Kill or Access command, preventing the tag from responding to the next query. IoT systems also need to prevent tags that have already been counted from responding to system trigger messages again. However, the approach used in RFID systems to address this issue is not applicable to IoT systems. This is because readers in IoT systems perform tag inventory in parallel, potentially in the frequency, time, and code domains. This means that a reader may be counting multiple tags simultaneously on a single channel, but the inventory flag flipping method used in the RFID system described above cannot precisely control individual tags. Therefore, preventing terminal devices that have already completed inventory from responding to network device triggers remains an unresolved issue in IoT systems.

[0061] Based on this, the wireless communication method provided by an embodiment of the present application is described in detail below in conjunction with Figure 7. The method shown in Figure 7 is applicable to any terminal device and / or network device described above. For ease of understanding, the first device and the second device are used below to represent devices applicable to this method.

[0062] In the embodiments of the present application, the first device may be a terminal device. For example, the first device may be a tag. The second device may be a terminal device and / or a network device. For example, the second device may be a reader / writer device.

[0063] The solution of the embodiment of the present application can be applied to an IoT communication system. For example, the first device and the second device can be devices in the IoT communication system.

[0064] The solution of the embodiment of the present application can be applied to the business scenarios described above. For example, the solution of the embodiment of the present application can be applied to one or more of the following business scenarios: inventory, sensor, tracking, and command.

[0065] As shown in FIG. 7 , the method includes steps S710 - S720 .

[0066] In step S710, the first device receives a first message sent by the second device. The first message can be used to trigger the first device whose flag value is the first value to execute a target process. The target process can be used by the first device to report business data to the second device.

[0067] The flag bit may be a flag bit within the first device. The flag bit may have at least two values, for example, 0 and 1, and the first value may be 0 or 1. The first message may be a broadcast message, and the second device may send the first message to all corresponding first devices. When the flag bit value of the first device receiving the first message is the first value, the first device may respond to the first message and begin executing the target process, which may be an inventory process.

[0068] In step S720, if the first device determines that the target process has been completed, the first device sets the value of the flag bit from the first value to the second value. For example, if the first device determines that the inventory process has been completed, the first device may set the value of its flag bit to the second value. If the first message is received again, the first device will not respond to the trigger of the first message again.

[0069] Based on the method shown in Figure 7, the second device triggers the first device whose flag value is the first value to execute the target process through the first message, and after the triggered first device executes the target process, it sets the value of the flag from the first value to the second value, thereby helping to avoid the first device responding to the trigger of the first message again.

[0070] Completion of the target process can be determined based on one or more of the following: the first device completing the transmission of an uplink message in the target process; the first device completing the reception of a downlink message in the target process; the first device receiving a second message, which can be used to indicate completion of the target process. The second message can be sent by the second device or by a core network device connected to the second device; or other criteria within the first device.

[0071] As an example, if the first device has successfully sent the last uplink message, indicating that the first device has completed sending the uplink message in the target process, the first device can set the flag value from the first value to the second value to avoid responding to the next triggering of the first message.

[0072] As another example, if the first device has successfully received the last downlink message, indicating that the first device has completed receiving the downlink message in the target process, the first device can set the flag bit value from the first value to the second value to avoid responding to the next triggering of the first message.

[0073] As another example, the first device is explicitly informed by the second device that the target process has been completed. At this time, the first device can set the value of the flag bit from the first value to the second value to avoid responding to the next triggering of the first message.

[0074] As another example, the first device is explicitly informed by the core network connected to the second device that the target process has been completed. At this time, the first device can set the value of the flag bit from the first value to the second value to avoid responding to the next triggering of the first message.

[0075] As another example, the first device may determine that the target process has been completed according to other internal criteria. At this time, the first device may set the value of the flag bit from the first value to the second value to avoid responding to the triggering of the first message next time.

[0076] As another example, the first device may also determine that the target process has been completed based on multiple of the above situations, which will not be described in detail here.

[0077] In some implementations, the method shown in FIG. 7 may further include step S730. In step S730, if the target process is not completed, the first device maintains the flag bit at the first value. The target process being not completed may mean that the target process is still in progress or that the target process has failed. In this case, the first device may continue to maintain the flag bit at the first value, thereby providing an opportunity to complete the target process or restart the target process.

[0078] The incomplete target process may include one or more of the following situations: the first device does not receive confirmation information of the uplink message in the target process; the first device does not receive the downlink message in the target process; the target process is interrupted; the first device fails to successfully access the second device.

[0079] As an example, if the first device sends an uplink message to the second device but does not receive confirmation information for the uplink message, the first device may still keep the flag bit at the first value to continue waiting for confirmation information for the uplink message.

[0080] As another example, if the first device does not receive an expected downlink message within a certain period of time, the first device may still keep the value of the flag bit at the first value so as to continue waiting for the downlink message.

[0081] As another example, if the first device abandons the current target process due to some internal reason, it indicates that the target process is interrupted. In this case, the first device can still keep the value of the flag bit as the first value so as to respond to the next first message and restart the target process.

[0082] As another example, if the first device fails to successfully access the second device during the initial access process due to a conflict or other reasons, the first device can still keep the flag value as the first value to respond to the next first message and restart the target process.

[0083] As another example, the incomplete target process may include multiple of the above situations, which will not be described in detail here.

[0084] In some implementations, before the first device receives the first message sent by the second device, the method shown in FIG. 7 may further include step S740. In step S740, the first device receives a third message sent by the second device. The third message may be used to initialize the value of a flag bit of the first device to the first value, thereby facilitating triggering the first device via the first message. The third message may be a broadcast message, and the second device may broadcast the third message to all of its corresponding first devices.

[0085] In some implementations, the first device includes a state machine that can be used to determine whether the first device is in an initial state. The state machine can include at least two states, such as a first state and a second state. The first state can be an initial state, which can also be called an idle (IDLE) state. The initial state can be a state in which the first device is idle, such as a state in which the first device has not started to execute a process. The second state can be other states different from the initial state, which is not limited in this application. The terminal device in the initial state has not started any process, so executing the target process in response to the first message will not interrupt other ongoing processes.

[0086] In some implementations, if the first device determines, based on the state machine, that the first device is in the initial state and the value of the flag bit of the first device is the first value, the first device may respond to the trigger of the first message, execute the target process, and leave the initial state. During the execution of the target process, if the first message is received again, the first device will not respond to the first message again, thereby helping to avoid interruption of the target process.

[0087] As an example, the method shown in FIG. 7 is described below with reference to FIG. For example, the first device in FIG. 8 may be a tag, the second device may be a reader, and the target process may be an inventory process. The method shown in FIG. 8 may include steps S810-S860.

[0088] In step S810, the tag receives the first message from the reader. The first message here corresponds to the third message described above, and the first message can be used to initialize the tag's flag, for example, to initialize the flag to 0. In step S820, the tag receives the second message from the reader. The second message here corresponds to the first message described above, and the second message is used to trigger the terminal device with the flag value set to 0 to execute the inventory process. When the terminal device in the initial state and the flag value set to 0 receives the second message, it will start to execute the inventory process and leave the initial state. For example, the tag starts to execute the initial access process to subsequently exchange information with the reader. As shown in step S830, the tag sends the first uplink message to the reader, and the first uplink message is used to report business data. In step S840, the tag receives the third message from the reader, and the third message is used to indicate that the inventory process has been completed. At this time, the tag can determine that the inventory process has been completed, so in step S850, the tag changes the value of the flag to 1. In step S860, the tag receives the second message from the reader again. However, the value of the tag's flag bit is 1 at this time, so the tag no longer responds to the message to execute the inventory process, thus avoiding the tag from repeatedly executing the inventory process.

[0089] Based on the method shown in Figure 8, once it is determined that the target process has been completed, the tag can actively modify the value of the flag bit. In this way, the modification of the flag bit value can achieve precise control of a single tag. In addition, in this method, tags can be logically divided into two groups. Initially, based on the value of the flag bit initialized by the reader, the corresponding tags belong to the same group, for example, the group with a flag bit of 0. When the inventory business starts, the reader instructs the tag with a flag bit of 0 to perform the inventory process. After the tag with a flag bit of 0 completes the inventory process, the value of its flag bit will be modified to 1, and the tag will be included in the group with a flag bit of 1. As the inventory business progresses, the number of tags in the group with a flag bit of 1 will increase, and the number of tags in the group with a flag bit of 0 will decrease. When there are no more tags in the group with a flag bit of 0, no tags will respond to the reader's inventory message, and the reader can now consider the inventory business to be over.

[0090] The following introduces a wireless communication method provided by another embodiment of the present application.

[0091] As mentioned above, IoT communication systems can also be used for sensor services. In sensor services, terminal devices typically need to complete certain measurement tasks and report the measured data to network devices in some manner. For the Type A and Type B terminal devices mentioned above, when the terminal device has data to report, the network device is unaware. Therefore, the network device needs to periodically check whether the terminal device has data to report. However, during this check, how to prevent terminal devices that have already reported data from reporting again is an unresolved issue.

[0092] Based on this, the wireless communication method provided by another embodiment of the present application is described in detail below in conjunction with Figure 9. The method shown in Figure 9 is applicable to any terminal device and / or network device described above. For ease of understanding, the first device and the second device are used below to represent devices applicable to this method.

[0093] In the embodiments of the present application, the first device may be a terminal device. For example, the first device may be a tag. The second device may be a terminal device and / or a network device. For example, the second device may be a reader / writer device.

[0094] The solution of the embodiment of the present application can be applied to an IoT communication system. For example, the first device and the second device can be devices in the IoT communication system.

[0095] The solution of the embodiment of the present application can be applied to the business scenarios described above. For example, the solution of the embodiment of the present application can be applied to one or more of the following business scenarios: inventory, sensor, tracking, and command.

[0096] As shown in FIG9 , the method includes steps S910 - S920 .

[0097] In step S910, the first device receives a first message sent by the second device. The first message may be used to trigger the first device to report data, for example, triggering the first device to report first data, which may be data collected by a sensor.

[0098] In step S920, if the first data reporting of the first device is completed, the first device clears the first data from the memory and / or changes the value of the first identifier from the first value to the second value.

[0099] The first identifier can be used to determine whether the first data is valid data. The first identifier can have at least two values, such as 0 and 1, where the first value can be 0 or 1, which is not limited in this application. When the first identifier is the first value, it can indicate that the first data is valid data; otherwise, the first data is invalid data.

[0100] In some implementations, before the first device reports the first data, the first device may determine whether valid data exists in the memory. Furthermore, the first device may determine that valid data exists in the memory based on the presence of the first data in the memory. And / or, the first device may determine that valid data exists in the memory based on the value of the first identifier being the first value. If the first device determines that valid data exists in the memory, the first device reports the first data; otherwise, the first device does not report the first data.

[0101] Based on the method shown in Figure 9, after the first device completes reporting the first data, it clears the first data from its memory and / or changes the value of the first identifier from the first value to the second value. When the first device receives the first message again, it can determine that no valid data exists in its memory. Therefore, the first device will no longer report the first data, which helps prevent the first device from repeatedly reporting the first data.

[0102] In some implementations, before the first device reports the first data, the first device may determine whether the state of the first device is an initial state, where the initial state is a state in which the first device is idle. Furthermore, the first device may include a state machine, which may be used to indicate the state of the first device. For example, the state machine may include at least two states. The first state may be an initial state, which may also be called an idle state, and is used to indicate that the first device has not yet started executing any process. The second state may be other states different from the initial state, which is not limited in this application. The terminal device in the initial state has not started any process, so reporting data in response to the first message will not interrupt other ongoing processes.

[0103] As an example, the method shown in FIG9 is described below with reference to FIG10. For example, the first device in FIG10 may be a tag, the second device may be a reader, and the first data may be sensor data. The method shown in FIG10 may include steps S1010-S1040.

[0104] In step S1010, the tag receives the first message from the reader, and the first message is used to trigger the tag to report sensor data. The first message can be a broadcast message, that is, all tags corresponding to the reader can receive the first message. When the tag that receives the first message has valid data to report and is in the initial state, the tag will respond to the first message to report the data. For example, at this time, the tag in Figure 10 is in the initial state, and its first identifier is the first value, indicating that the tag has valid sensor data. Therefore, as shown in step S1020, the tag reports the first data. In step S1030, the tag modifies the value of the first identifier to the second value. In step S1040, the tag receives the first message from the reader again. However, at this time, the first identifier is the second value, indicating that the tag does not have valid sensor data. Therefore, the tag no longer responds to the first message to report data, avoiding the tag from repeatedly reporting the same sensor data.

[0105] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, so for parts not described in detail, reference can be made to the above method embodiments.

[0106] Figure 11 is a structural diagram of the first device provided by an embodiment of the present application. The first device 1100 in Figure 11 includes a receiving module 1110, a determining module 1120, and a setting module 1130. The receiving module 1110 is used to receive a first message sent by the second device, and the first message is used to trigger the first device whose flag value is the first value to execute the target process, and the target process is used by the first device to report business data to the second device. The determining module 1120 is used to determine whether the target process has been completed. The setting module 1130 is used to set the value of the flag from the first value to the second value when the determining module 1120 determines that the target process has been completed.

[0107] In some implementations, the determination module 1120 can determine that the target process has been completed based on one or more of the following: the first device completes sending of an uplink message in the target process; the first device completes receiving of a downlink message in the target process; the first device receives a second message, and the second message is used to indicate that the target process has been completed; other criteria within the first device.

[0108] In some implementations: the second message is sent by the second device; or, the second message is sent by a core network device connected to the second device.

[0109] In some implementations, the setting module 1130 is further configured to maintain the value of the flag bit at the first value when the determining module 1120 determines that the target process is not completed.

[0110] In some implementations, the determination module 1120 determines that the target process is not completed based on one or more of the following: the first device does not receive confirmation information of the uplink message in the target process; the first device does not receive the downlink message in the target process; the target process is interrupted; the first device does not successfully access the second device.

[0111] In some implementations, the receiving module 1110 is further configured to receive a third message sent by the second device before receiving the first message sent by the second device, where the third message is configured to initialize the value of the flag bit of the first device to the first value.

[0112] In some implementations, the third message is a broadcast message.

[0113] In some implementations, the first device includes a state machine configured to determine whether the first device is in an initial state.

[0114] In some implementations, if the first device determines based on the state machine that the first device is in the initial state and the value of the flag bit of the first device is the first value, the first device executes the target process and leaves the initial state.

[0115] In some implementations, the first device is a terminal device, and the second device is a terminal device or a network device.

[0116] In some implementations, the first device is a tag.

[0117] In some implementations, the target process is an inventory process.

[0118] Figure 12 is a schematic diagram of the structure of a first device provided in another embodiment of the present application. The first device 1200 in Figure 12 includes a first module 1210 and a second module 1220. The first module 1210 is configured to receive a first message sent by a second device, the first message being used to trigger the first device to report data; the second module 1220 is configured to, after the first device completes reporting the first data, clear the first data from memory and / or change the value of the first identifier from the first value to the second value.

[0119] In some implementations, the first identifier is used to determine whether the first data is valid data.

[0120] In some implementations, the first device 1200 further includes a determination module 1230 , which is configured to determine whether there is valid data in the memory before the first device reports the first data.

[0121] In some implementations, the determination module 1230 may determine that valid data exists in the memory based on the existence of first data in the memory and / or the value of the first identifier being the first value.

[0122] In some implementations, the determination module 1230 is further configured to determine whether the state of the first device is an initial state before the first device reports the first data, where the initial state is an idle state of the first device.

[0123] In some implementations, the first device includes a state machine, and the state machine is used to indicate a state of the first device.

[0124] In some implementations, the first device is a terminal device, and the second device is a terminal device or a network device.

[0125] In some implementations, the first device is a tag.

[0126] In some implementations, the first data is data collected by a sensor.

[0127] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1300 in Figure 13 can be used to implement the method described in the above method embodiment. The device 1300 can be a chip, a terminal device, or a base station.

[0128] The communication device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the above method embodiment. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0129] The communication device 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.

[0130] The communication device 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.

[0131] It should be understood that in the embodiment of the present application, the processor 1310 can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.

[0132] The memory 1320 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1310. A portion of the processor 1310 may also include a non-volatile random access memory. For example, the processor 1310 may also store information about the device type.

[0133] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 1310 or by instructions in the form of software. The method for requesting uplink transmission resources disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1320, and the processor 1310 reads the information in the memory 1320 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0134] It should be understood that in the embodiment of the present application, the processor 1310 may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0135] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the first device provided in the present application, and the program enables a computer to execute the wireless communication method in each embodiment of the present application.

[0136] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the wireless communication method performed by the first device in each embodiment of the present application.

[0137] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the wireless communication method performed by the first device in each embodiment of the present application.

[0138] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.

[0139] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0140] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0141] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0142] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. 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 document generally indicates that the related objects are in an "or" relationship.

[0143] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0144] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0145] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0147] 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.

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

[0149] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that, it includes: A first device receives a first message sent by a second device, where the first message is used to trigger the first device with the flag bit having a first value to execute a target process, and the target process is for the first device to report service data to the second device; If the first device determines that the target process has been completed, the first device sets the value of the flag bit from the first value to a second value.

2. The method according to claim 1, characterized in that, the completion of the target process is determined based on one or more of the following: The first device completes the sending of the uplink message in the target process; The first device completes the reception of the downlink message in the target process; The first device receives a second message, where the second message is used to indicate that the target process has been completed.

3. The method according to claim 2, characterized in that: The second message is sent by the second device; or, The second message is sent by a core network device connected to the second device.

4. The method according to any one of claims 1 to 3, characterized in that, the method further includes: If the target process is not completed, the first device keeps the value of the flag bit as the first value.

5. The method according to claim 4, characterized in that, the non-completion of the target process includes one or more of the following: The first device does not receive the confirmation information of the uplink message in the target process; The first device does not receive the downlink message in the target process; The target process is interrupted; The first device fails to successfully access the second device.

6. The method according to any one of claims 1 to 5, characterized in that, before the first device receives the first message sent by the second device, the method further includes: The first device receives a third message sent by the second device, where the third message is used to initialize the value of the flag bit of the first device to the first value.

7. The method according to claim 6, characterized in that, the third message is a broadcast message.

8. The method according to any one of claims 1 to 7, characterized in that, the first device includes a state machine, and the state machine is used to determine whether the first device is in an initial state.

9. The method according to claim 8, characterized in that, the method further includes: If the first device determines based on the state machine that the first device is in the initial state and the value of the flag bit of the first device is the first value, the first device executes the target process and leaves the initial state.

10. The method according to any one of claims 1 to 9, characterized in that, the first device is a terminal device, and the second device is a terminal device or a network device.

11. The method according to any one of claims 1 to 10, characterized in that, the first device is a tag.

12. The method according to any one of claims 1 to 11, characterized in that, the target process is an inventory process.

13. A wireless communication method, It is characterized in that it includes: The first device receives a first message sent by the second device, and the first message is used to trigger the first device to report data. If the first data reporting of the first device is completed, the first device clears the first data from the memory, and / or changes the value of the first identifier from the first value to the second value.

14. The method according to claim 13, it is characterized in that The first identifier is used to determine whether the first data is valid data.

15. The method according to claim 13 or 14, it is characterized in that The method further includes: Before the first device reports the first data, the first device determines whether there is valid data in the memory.

16. The method according to claim 15, it is characterized in that The first device determines whether there is valid data in the memory, including: If the first data exists in the memory, and / or the value of the first identifier is the first value, the first device determines that there is valid data in the memory.

17. The method according to any one of claims 13 to 16, it is characterized in that The method further includes: Before the first device reports the first data, the first device determines whether the state of the first device is the initial state, and the initial state is the state where the first device is idle.

18. The method according to claim 17, it is characterized in that The first device includes a state machine, and the state machine is used to indicate the state of the first device.

19. The method according to any one of claims 13 to 18, it is characterized in that The first device is a terminal device, and the second device is a terminal device or a network device.

20. The method according to any one of claims 13 to 19, it is characterized in that The first device is a tag.

21. The method according to any one of claims 13 to 20, it is characterized in that The first data is data collected by a sensor.

22. A first device, it is characterized in that The first device includes: A receiving module, configured to receive a first message sent by a second device, where the first message is used to trigger the first device with the value of the flag bit being the first value to execute a target process, and the target process is used for the first device to report service data to the second device; A determining module, configured to determine whether the target process has been completed; A setting module, configured to set the value of the flag bit from the first value to the second value when the determining module determines that the target process has been completed.

23. A first device, it is characterized in that The first device includes: A first module, configured to receive a first message sent by a second device, where the first message is used to trigger the first device to report data; A second module, configured to clear the first data from the memory after the first data reporting of the first device is completed, and / or change the value of the first identifier from the first value to the second value.

24. A first device, it is characterized in that Comprising a memory and a processor, the memory is used for storing programs, and the processor is used for calling the programs in the memory to enable the first device to execute the method according to any one of claims 1-12 or 13-21.

25. An apparatus, characterized in that it comprises a processor for calling a program from a memory to enable the apparatus to execute the method according to any one of claims 1-12 or 13-21.

26. A chip, characterized in that it comprises a processor for calling a program from a memory, such that a device installed with the chip executes the method according to any one of claims 1-12 or 13-21.

27. A computer-readable storage medium, characterized in that a program is stored thereon, and the program enables a computer to execute the method according to any one of claims 1-12 or 13-21.

28. A computer program product, characterized in that it comprises a program, and the program enables a computer to execute the method according to any one of claims 1-12 or 13-21.

29. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1-12 or 13-21.

Images