Wireless communication method, communication device, apparatus, and storage medium

Abstract

A wireless communication method, communication device, apparatus, and storage medium are provided. The wireless communication method includes: a first device receiving a first command sent by a second device, the first command including a first parameter, the first parameter being used to determine a first timeslot value; the first device sending a second parameter to the second device, the second parameter being a target parameter for accessing the second device, the sending time of the second parameter being determined based on the first timeslot value; wherein the second parameter is carried in a first uplink frequency domain resource among multiple uplink frequency domain resources, and all multiple uplink frequency domain resources can be used to carry the target parameter.

Description

Wireless communication method, communication equipment, device and storage medium Technical Field

[0001] The present application relates to the technical field of environmental Internet of Things, and more specifically, to a wireless communication method, communication equipment, apparatus, and storage medium. Background Art

[0002] In radio frequency identification (RFID) technology, a first device (eg, an ambient energy Internet of Things terminal device) can randomly access a second device to use the services of the second device.

[0003] To expand the application of cellular IoT, it is expected that RFID technology can be applied to cellular IoT. However, if RFID technology in related technologies is still used in cellular IoT scenarios, the efficiency of first devices accessing the communication system will be reduced, thereby affecting the quality of service.

[0004] Summary of the Invention

[0005] The present application provides a wireless communication method, communication equipment, apparatus, and storage medium. The following introduces various aspects of the present application.

[0006] In a first aspect, a wireless communication method is provided, including: a first device receives a first command sent by a second device, the first command includes a first parameter, and the first parameter is used to determine a first time slot value; the first device sends a second parameter to the second device, the second parameter is a target parameter for accessing the second device, and the sending time of the second parameter is determined based on the first time slot value; wherein the second parameter is carried on a first uplink frequency domain resource among multiple uplink frequency domain resources, and the multiple uplink frequency domain resources can all be used to carry the target parameter.

[0007] According to a second aspect, a wireless communication method is provided, including: a second device sends a first command to a first device, the first command includes a first parameter, and the first parameter is used to determine a first time slot value; the second device receives a second parameter sent by the first device, the second parameter is a target parameter for accessing the second device, and the sending time of the second parameter is determined based on the first time slot value; wherein the second parameter is carried on a first uplink frequency domain resource among multiple uplink frequency domain resources, and the multiple uplink frequency domain resources can all be used to carry the target parameter.

[0008] According to a third aspect, a communication device is provided, which is a first device and includes: a receiving unit for receiving a first command sent by a second device, the first command including a first parameter, and the first parameter is used to determine a first time slot value; a sending unit for sending a second parameter to the second device, the second parameter being a target parameter for accessing the second device, and the sending time of the second parameter is determined based on the first time slot value; wherein the second parameter is carried on a first uplink frequency domain resource among multiple uplink frequency domain resources, and the multiple uplink frequency domain resources can all be used to carry the target parameter.

[0009] In a fourth aspect, a communication device is provided, which is a second device, and includes: a sending unit for sending a first command to a first device, the first command including a first parameter, and the first parameter is used to determine a first time slot value; a receiving unit for receiving a second parameter sent by the first device, the second parameter being a target parameter for accessing the second device, and the sending time of the second parameter is determined based on the first time slot value; wherein the second parameter is carried on a first uplink frequency domain resource among multiple uplink frequency domain resources, and the multiple uplink frequency domain resources can all be used to carry the target parameter.

[0010] In a fifth aspect, a communication device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the communication device executes the method described in the first aspect or the second aspect.

[0011] 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 or the second aspect.

[0012] 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 aspect or the second aspect.

[0013] 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 as described in the first aspect or the second aspect.

[0014] In a ninth aspect, a computer program product is provided, characterized in that it includes a program, and the program enables a computer to execute the method described in the first aspect or the second aspect.

[0015] In a tenth aspect, a computer program is provided, which enables a computer to execute the method as described in the first aspect or the second aspect.

[0016] In the wireless communication method provided in an embodiment of the present application, a first device receives a first command sent by a second device, the first command including a first parameter, the first parameter being used to determine a first time slot value; the first device sends a second parameter to the second device, the second parameter being a target parameter for accessing the second device, the sending time of the second parameter being determined based on the first time slot value; wherein the second parameter is carried on a first uplink frequency domain resource among multiple uplink frequency domain resources, and the multiple uplink frequency domain resources can all be used to carry the target parameter. In this way, multiple first devices can access the second device in parallel, effectively improving the access capacity and access efficiency of the communication system, and improving the service quality of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0018] Figure 2 is a structural example diagram of an A-IoT terminal device.

[0019] FIG3 is a structural diagram of an energy harvesting module in FIG2 .

[0020] FIG4 is a schematic diagram of the backscatter communication process of an A-IoT terminal device.

[0021] FIG5 is an example diagram of the encoding method of an A-IoT terminal device.

[0022] FIG6 a is a schematic diagram of an application scenario of an A-IoT terminal device provided in an embodiment of the present application.

[0023] Figure 6b is a schematic diagram of an application scenario of an A-IoT terminal device provided in another embodiment of the present application.

[0024] FIG7 a is a schematic diagram of a single tag access process according to an embodiment of the present application.

[0025] FIG7 b is a schematic diagram of a process of accessing multiple tags according to another embodiment of the present application.

[0026] FIG8 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0027] FIG9 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application.

[0028] FIG10 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0029] FIG. 11 is a schematic diagram of a device to which an embodiment of the present application can be applied. DETAILED DESCRIPTION

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

[0031] Communication system architecture

[0032] Figure 1 illustrates a wireless communication system 100 used in an embodiment of the present application. 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 provides communication coverage for a specific geographic area and can communicate with the terminal device 120 within the coverage area. The terminal device 120 can access a network (e.g., a wireless network) through the network device 110.

[0033] FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

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

[0035] 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), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), 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.

[0036] 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, and an IoT terminal device, etc.

[0037] Alternatively, a UE can function as a base station. For example, a UE can act as a dispatching entity, providing sidelink signals between UEs in V2X or D2D applications. For example, a cell phone and a car can communicate with each other using sidelink signals. A cell phone and a smart home device can also communicate without relaying the communication signal through a base station.

[0038] 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, vehicle-to-everything (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 equipment.

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

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

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

[0042] 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).

[0043] During the standardization discussion, zero-power IoT can also be referred to as Ambient power enabled IoT, or Ambient IoT for short. In some technical literature, it is also referred to as passive IoT. The so-called Ambient IoT device refers to an IoT device that uses various environmental energies, such as wireless radio frequency energy, light energy, solar energy, thermal energy, mechanical energy, and other environmental energies to drive itself. This device may have no energy storage capacity or may have a very limited energy storage capacity (such as using a capacitor with a capacity of tens of uF). Compared with existing IoT devices, Ambient IoT devices have many advantages such as no conventional battery, no maintenance, small size, low complexity and low cost, and a long life cycle. For the sake of simplicity, Ambient IoT can be abbreviated as A-IoT in the following text.

[0044] Possible communication technologies used by A-IoT systems

[0045] A-IoT communication adopts energy harvesting and backscatter communication technology, and has the characteristics of low power consumption and low cost. The A-IoT terminal device in the embodiment of the present application may refer to an IoT device that uses various environmental energies (such as wireless radio frequency energy, light energy, solar energy, thermal energy, mechanical energy and other environmental energies) to drive itself. This A-IoT terminal device may have no energy storage capacity or may have a very limited energy storage capacity (such as using a capacitor with a capacity of tens of uF). Compared with existing IoT devices, A-IoT terminal devices have many advantages such as no conventional battery, no maintenance, small size, low complexity, low cost, and long life cycle. In this scenario, the terminal device 120 mentioned above can be called a "zero-power device" or "A-IoT terminal device". The working principle of the A-IoT terminal device is exemplarily introduced below in conjunction with Figures 2 to 7.

[0046] As shown in Figure 2 , the AIoT may include a network device 210 and an A-IoT terminal device 220. Network device 210 may be, for example, network device 110 in Figure 1 . A-IoT terminal device 220 may be, for example, terminal device 120 in Figure 1 . Network device 210 is configured to send wireless power supply signals to A-IoT terminal device 220 and receive backscattered signals from A-IoT terminal device 220.

[0047] In some embodiments, the A-IoT terminal device 220 may include an energy collection module 221 and a backscatter communication module 222. In some cases, the A-IoT terminal device 220 may also include a low-power computing module 223. The low-power computing module 223 can be used to provide computing functions for the A-IoT terminal device 220, such as data processing, etc. In other cases, the A-IoT terminal device 220 may also include a sensor module 224 for collecting external information (for example, ambient temperature, ambient humidity, etc.). In other cases, the A-IoT terminal device 220 may also include a storage module for storing some information (for example, external information collected by the above-mentioned sensors, or item identification, etc.).

[0048] The energy harvesting module 221 is used to harvest energy. In some implementations, energy can be harvested via a power supply signal sent by another device or from the external environment. The power supply signal can be a radio frequency signal sent by the network device 210. Therefore, the energy harvesting module can be a radio frequency (RF) power harvesting module.

[0049] FIG3 shows a possible structure of the energy harvesting module 221. As shown in FIG3, the energy harvesting module 221 can harvest the energy of the spatial electromagnetic waves of the radio frequency signal based on the principle of electromagnetic induction, and store the harvested energy in the capacitor C, which is the process of charging the capacitor C. When the charging process of the capacitor C is completed, the capacitor C can begin to discharge to provide energy to the A-IoT terminal device 220. For example, the discharge of the capacitor C can be used to drive the A-IoT terminal device 220 to perform low-power demodulation of data sent by other devices. For another example, the discharge of the capacitor C can be used to drive the A-IoT terminal device 220 to modulate the data to be sent. For another example, the discharge of the capacitor C can be used to drive the sensor of the A-IoT terminal device 220 to collect data. For another example, the discharge of the capacitor C can be used to drive the A-IoT terminal device 220 to read data from the memory 215, etc.

[0050] The following describes the backscattering communication principle in conjunction with Figure 4. Referring to Figure 4, the A-IoT terminal device 220 receives a wireless signal sent by another device (such as the network device 210) and modulates the wireless signal to load the data to be sent. Then, the A-IoT terminal device 220 radiates the modulated signal from the antenna. This information transmission process is called backscattering communication. The above-mentioned wireless signal can also be called a carrier signal. A carrier signal can refer to an unmodulated wireless signal. The carrier signal can be, for example, a sine wave signal. Among them, backscattering communication and load modulation functions are inseparable. The load modulation function can be understood as adjusting and controlling the circuit parameters of the oscillation circuit of the A-IoT terminal device according to the beat of the data stream, so that parameters such as the impedance of the A-IoT terminal device change accordingly, thereby completing the modulation process.

[0051] In some implementations, the A-IoT terminal device 220 may also be provided with a logic processing unit to perform corresponding computing functions.

[0052] Generally, the load modulation function can be implemented through two methods: resistive load modulation and capacitive load modulation. Figure 5 shows a circuit diagram of an A-IoT terminal device based on resistive load modulation technology. In resistive load modulation, a resistor RL can be connected in parallel to the load. The switch S can be controlled based on the binary data stream to realize the connection or disconnection of the resistor RL. In this way, the connection and disconnection of the resistor RL will cause a change in the circuit voltage, and the change in the circuit voltage can control the amplitude of the backscattered signal of the A-IoT terminal device, thereby realizing the modulation of the backscattered signal, that is, performing amplitude-shift keying (ASK) modulation on the backscattered signal.

[0053] Similarly, in capacitive load modulation, the on / off switching of the capacitor can be controlled based on a binary data stream to change the circuit resonant frequency, thereby changing the operating frequency of the backscattered signal to implement frequency-shift keying (FSK) modulation.

[0054] It can be seen that the A-IoT terminal device uses load modulation to modulate the incoming signal, thereby realizing the backscatter communication process. Therefore, the A-IoT terminal device has significant advantages: (1) The A-IoT terminal device does not actively transmit signals, so it does not require a complex RF link, such as a power amplifier, RF filter, etc.; (2) The A-IoT terminal device does not need to actively generate high-frequency signals, so it does not need a high-frequency crystal oscillator; (3) With the help of backscatter communication, the signal transmission of the A-IoT terminal device does not consume the terminal's own energy.

[0055] With the rapid development of cellular IoT, the 3rd Generation Partnership Project (3GPP) has standardized IoT technologies such as narrowband IoT (NB-IoT), machine-type communications (MTC), and reduced capability (REDCAP). However, many IoT communication requirements remain unmet using existing technologies, such as those in demanding communication environments (high and low temperatures, high humidity, high voltage, high radiation, or high-speed motion), the need for extremely small terminal form factors, and extremely low costs. Therefore, to address these unmet IoT communication needs, cellular networks also need to develop ultra-low-cost, extremely small, battery-free, and maintenance-free IoT solutions. Environmental IoT precisely addresses this need.

[0056] Based on the discussion of A-IoT application scenarios in 3GPP SA1, A-IoT can be used in at least the following four scenarios: (1) Object recognition, such as logistics, production line product management, and supply chain management. (2) Environmental monitoring, such as temperature, humidity, and harmful gas monitoring in the working environment and natural environment. (3) Positioning, such as indoor positioning, intelligent object search, and production line item positioning. (4) Intelligent control, such as intelligent control of various electrical appliances in smart homes (turning on and off air conditioners, adjusting temperatures), and intelligent control of various facilities in agricultural greenhouses (automatic irrigation and fertilization).

[0057] In a low-power IoT based on a cellular network, as shown in FIG6a , the A-IoT terminal device 220 can directly transmit and receive carrier signals from the network device 210, and send or backscatter corresponding data or signals to the network device 210. In other implementations, as shown in FIG6b , communication between the A-IoT terminal device 220 and the network device 210 can also be achieved through an intermediate node 230 (such as a relay node). In this case, the intermediate node 230 sends a carrier signal to the A-IoT terminal device 220, and the A-IoT terminal device 220 sends or backscatters corresponding data or signals to the intermediate node 230.

[0058] Classification of A-IoT terminal devices

[0059] Based on current 3GPP discussions, A-IoT terminals can be divided into two categories based on energy storage capabilities and the ability to generate RF signals for signal transmission.

[0060] Device type 1: The transmission power is about 1uW, and it has energy storage function. It does not have independent signal generation and uplink and downlink signal amplification functions. Signal transmission can only rely on backscattering.

[0061] Device type 2: The device has a transmission power of several hundred uW, has energy storage function, has the function of uplink and downlink signal amplification, and can independently generate signals or use backscattering to send signals.

[0062] A-IoT industry applications, use cases and business models

[0063] A-IoT supports many industrial applications, such as automated warehousing, smart homes, smart agriculture, and finding personal belongings.

[0064] As an example, in automated warehousing applications, automated warehouse inventory scenarios include multiple stages, including verification and unloading, warehousing, inventory counting, outbound delivery, and inspection and loading. As goods are transferred, stored, and inventoried, a vast amount of warehouse information is generated. This information is typically characterized by frequent data read operations and large data volumes. Ambient IoT devices are connected to items of varying value and purpose, such as pallets and individual products, and are equipped with relevant communication equipment. Through information exchange between communication devices and tags, efficient management of inventory and storage information can be achieved accurately and quickly at each stage.

[0065] For automated warehousing, 3GPP has defined an inventory use case, aimed at discovering the presence of goods (e.g., boxes, drawers, packages, tools, etc.) within a specific area. Upon receiving a request from the network within a specific area, the A-IoT devices attached to these goods report their associated identifiers to the network, optionally along with other information such as status, measurement results, and location. This service model follows the device-originated–device-terminated (DO-DTT) model.

[0066] Random Access in RFID Technology

[0067] In radio frequency identification (RFID) technology, when an interrogator wants to read or write to a tag, it first sends a query command to all tags. This command includes a parameter Q (Q is an integer between 0 and 15). Upon receiving this command, tags within the interrogator's RF field generate a random number between 0 and 2^Q-1, use this random number as their response time slot, and load this random number into a time slot counter. Only tags whose time slot in the time slot counter is 0 will send a 16-bit random number (RN16) as a response to the interrogator. After receiving the RN16 from the tag, the interrogator sends an acknowledgement character (ACK) with the same RN16-bit parameter. If a tag receives a valid ACK, it immediately transitions to the acknowledgement state and backscatters its protocol control (PC), extended capabilities port (ECP), and cyclic redundancy check-16 (CRC-16). When the tag is in the confirmation state, it executes the REQ_RN (RN16) instruction sent by the reader. After receiving the valid instruction, the tag sends a new RN16 (handle handl) and switches to other states (open state or protection state). In this state, the reader can read and write to this tag alone.

[0068] Query command, QueryRep command, and tag reply

[0069] For example, the fields included in the Query command may be as shown in Table 1. As shown in Table 1, DR indicates the data rate from the tag to the reader; M indicates the encoding method; TRext indicates whether the preamble includes a pilot signal; Target indicates the filtered tags; Sel is short for session and indicates the Target filtering condition; and Q indicates the parameter Q described above.

[0070] Table 1

[0071] Exemplarily, the fields included in the response message (the above-mentioned RN16) that the tag replies to the Query command may be as shown in Table 2.

[0072] Table 2

[0073] The QueryRep command can be understood as an instruction for a high-speed tag to enter the next time slot. Upon receiving this command, the tag decrements its slot counter by 1. If the slot counter is 0, it indicates that it is the tag's turn to transmit information. For example, the fields included in the QueryRep command may be as shown in Table 3.

[0074] Table 3

[0075] For example, the fields included in the response message that the tag replies to the QueryRep command may be as shown in Table 4.

[0076] Table 4

[0077] For example, an interrogator sends an ACK to acknowledge a single tag as shown in Table 5. The single tag is the tag that sends an RN16 to the interrogator before the interrogator responds to the ACK command. The ACK command is used to respond to the RN16 (ACK echoes the tag's backscattered RN16).

[0078] Table 5

[0079] For ease of understanding, the tag access process in the related art is described below with reference to FIG. 7 a and FIG. 7 b .

[0080] As shown in FIG7 a , the process of single tag reply is as follows.

[0081] The reader can first send a select command to select the tag to communicate with next.

[0082] After sending the select command, you can send a Query command to the selected tag after the call wait time T4, and enter call waiting again after sending the Query command.

[0083] During the call waiting process, each selected tag receives a Query command and generates a random number to load into its slot counter. Subsequently, each selected tag receives a QueryRep command to change the time slot in its slot counter. When a single tag's slot reaches 0, it sends an RN16 to the interrogator. The duration of the interrogator's call waiting is calculated as T1 + the time the tag sends RN16 + T2 in Figure 7a. T1 is the time period when the slot counter of a single tag reaches 0 according to the method described above.

[0084] After the call wait ends, the reader can send an ACK command to the single tag. If the tag can receive a valid ACK command, after the next T1 period, the tag can backscatter its PC, EPC and CRC to the reader.

[0085] Optionally, the reader can proceed with subsequent processes based on the EPC reported by the tag. For example, if the EPC is valid, the reader can continue to send a QueryRep command or other commands to enable other tags to access the tag or execute other services through other commands. Other services can be services that can be executed after access is completed. For another example, if the EPC is invalid, the reader can send a NAK command.

[0086] As mentioned above, the tags selected by the reader are all generated based on the query command to load the random number into the time slot counter to determine its transmission time. Therefore, in the scenario where multiple tags are connected, some special cases may still exist.

[0087] Exemplarily, as shown in FIG7 b , if multiple tags access simultaneously, the following situations may occur.

[0088] Collided reply: After the reader sends a Query command, multiple tags may have their time slots set to 0 simultaneously, meaning that the random numbers generated by these tags are identical. In this case, multiple tags simultaneously send RN16 messages to the reader using the same uplink frequency domain resource, causing a collision in the reply messages and generating a collision detection.

[0089] No reply: After the reader sends the QueryRep command, there may be no tag reporting message, which means no response.

[0090] Invalid ACK: When the reader responds to the ACK command for the RN16 reported by the tag, it may not receive the PC, EPC, CRC and other information reported by the tag. In this case, the ACK is an invalid response.

[0091] In some embodiments, if any of the above three situations occurs during multi-terminal access, the reader resends the QueruAdjust command to adjust the value of the parameter Q or the reader resends the QueryRep command.

[0092] In related technologies, RFID tag access is serial. That is, when a tag is connected, the reader can read and write to it independently. At this time, because the reader does not send a QueryRep command, other tags cannot obtain a slot opportunity. Only after a tag completes the read and write operation can other tags be connected.

[0093] However, the 3GPP system has a coverage advantage over related RFID technologies, enabling it to provide inventory services over a wider area. Given the expanded coverage of the 3GPP system, the number of devices to be inventoried / accessed has also increased significantly. Traditional RFID-based serial access of multiple tags significantly prolongs the inventory process, impacting service quality. Therefore, a more efficient access technology is needed.

[0094] In response to the above problems, the embodiments of the present application are described in detail below.

[0095] Figure 8 is a flow chart of the wireless communication method provided in an embodiment of the present application. The method of Figure 8 is described from the perspective of the interaction between the first device and the second device. The first device is a terminal device, which may be, for example, the A-IoT terminal device (such as a tag) mentioned above. Of course, the terminal device may also be other types of terminal devices, such as a terminal device that performs random access in a similar manner to the A-IoT terminal device. The second device may be the network device or intermediate device mentioned above. The network device may be any type of communication device that provides coverage for the terminal device, for example, the network device may be a base station or a reader. The intermediate device may also be referred to as an intermediate node, and the intermediate device may be an intermediate device connected to the first device and the network device. The intermediate device may be an electronic device that enables the first device and the network device to communicate through the intermediate device. For example, the intermediate device may be an intermediate UE. The intermediate UE may be, for example, a router or a relay device.

[0096] 8 , in step S810, the first device receives a first command sent by the second device. For example, the first command may be a query command. Alternatively, the first command may be an inventory request, a paging command, an inventory command, or the like.

[0097] In an embodiment of the present application, the first command or a parameter in the first command may be used to indicate the timing for the first device to access the second device. For example, the first command may include a first parameter, and the first parameter is used to determine a first time slot value. The first time slot value may serve as a response time slot value when the first device accesses the second device. For example, the first parameter may be a Q value in a Query command. As an example, the Q value may be an integer between 0 and 15. The first time slot value may be a random number generated based on the Q value. As an example, the first time slot value may be a random number between 0 and 2^Q-1.

[0098] In some embodiments, the first command may include a first parameter. The first parameter may be for one first device, or the first parameter may be for multiple first devices simultaneously. The first parameter is used to determine a first time slot value for the first device or multiple first devices.

[0099] In some other embodiments, the first command may include multiple first parameters, which may be used to determine first time slot values ​​of multiple terminal devices corresponding to the parameters one by one.

[0100] In some embodiments, the second device may send the first command via a downlink frequency domain resource.

[0101] In other embodiments, the second device may send the first command through multiple downlink frequency domain resources.

[0102] In some embodiments, the first command is carried in a first downlink frequency domain resource. Optionally, the second device may monitor the first command on the first downlink frequency domain resource. The downlink frequency domain resources mentioned in various embodiments of the present application may be a downlink carrier, a downlink resource block (RB), a downlink bandwidth part (BWP), a downlink control resource set (CORESET), etc.

[0103] In some embodiments, the first downlink frequency domain resource may be a downlink frequency domain resource dedicated to transmitting a downlink signal enabling the first device to access the second device. That is, regardless of the number of terminal devices, the second device only transmits downlink signals on the first downlink frequency domain resource, and these terminal devices can share this downlink frequency domain resource to receive downlink signals. Optionally, the downlink signal mentioned here may include a Query command, a QueryRep command, or an ACK instruction.

[0104] As an example, the first downlink frequency domain resource may be a downlink frequency domain resource agreed upon by the system.

[0105] As another example, the first downlink frequency domain resource may be a downlink frequency domain resource selected from multiple downlink frequency domain resources in the system. For example, the first downlink frequency domain resource may be a downlink frequency domain resource selected from multiple downlink frequency domain resources in the system according to the capability of the terminal device.

[0106] In other embodiments, each of the multiple downlink frequency domain resources in the system is used to carry the first command corresponding to each, and the first downlink frequency domain resource can be a downlink frequency domain resource corresponding to the first command of the first device selected from the multiple downlink frequency domain resources in the system. For example, the multiple downlink frequency domain resources are respectively used to transmit a Query command, and the Query command transmitted on each downlink frequency domain resource has a corresponding terminal device, the first device is one of the multiple terminal devices, and the first downlink frequency domain resource is a downlink frequency domain resource for transmitting the first command of the first device. The first parameter in each Query command can be the same or different.

[0107] In step S820, the first device sends a second parameter to the second device.

[0108] The second parameter is a target parameter for accessing the second device. For example, the second parameter may be RN16 as a response message. The target parameter may be a random number. For example, it may be a 16-bit random number corresponding to RN16.

[0109] In some embodiments, the sending time of the second parameter may be determined based on the first time slot value. For example, the sending time of the second parameter may be the moment when the first time slot value decreases from the random value generated according to the Q value to 0.

[0110] In an embodiment of the present application, there may be multiple uplink frequency domain resources in the system. All of the multiple uplink frequency domain resources may be used to carry the target parameter. The second parameter is carried on a first uplink frequency domain resource among the multiple uplink frequency domain resources.

[0111] In some embodiments, the first uplink frequency domain resource may be determined according to the capability of the first device and / or the second uplink frequency domain resource provided by the second device. The second uplink frequency domain resource may include multiple uplink frequency domain resources.

[0112] As an example, the second uplink frequency domain resource may be an uplink frequency domain resource supported by the terminal and / or an uplink frequency domain resource indicated by the second device through the first command or other command. The uplink frequency domain resource supported by the terminal may be one or more. The uplink frequency domain resource indicated by the second device through the first command or other command may also be one or more.

[0113] The embodiment of the present application does not specifically limit the method for determining the first frequency domain resource from multiple uplink frequency domain resources.

[0114] For example, the first uplink frequency domain resource may be an uplink frequency domain resource selected randomly or according to a certain weight by the first device from multiple uplink frequency domain resources. As an example, this method corresponds to the second device sending the first command on only one downlink frequency domain resource.

[0115] For another example, there are multiple downlink frequency domain resources and multiple uplink frequency domain resources in the system, and the multiple downlink frequency domain resources and the multiple uplink frequency domain resources have a one-to-one, one-to-many or many-to-one mapping relationship. The first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among the multiple uplink frequency domain resources. Among them, the first downlink frequency domain resource is a downlink frequency domain resource used to send a downlink signal to the first device so that the first device can access the second device. Exemplarily, multiple downlink frequency domain resources are all used to transmit Query commands or QueryRep commands. As an example, this method corresponds to the second device being able to send a first command on multiple downlink frequency domain resources.

[0116] As an implementation manner, the first command indicates the first parameter and the first uplink frequency domain resource. For example, the first command may indicate a correspondence between the first parameter and the first uplink frequency domain resource.

[0117] As an example, when sending the first command, the second device indicates the first parameter for one or more uplink frequency domain resources. The first parameters indicated on these different uplink frequency domain resources can be the same or different. That is, the second device indicates multiple sets of (uplink frequency domain resources, Q value).

[0118] As another example, the second device may indicate the first parameter for all uplink frequency domain resources. When this method corresponds to a one-to-one correspondence between all uplink frequency domain resources and all downlink frequency domain resources, only the first parameter needs to be indicated.

[0119] In some embodiments, the first parameter is used to determine a time at which a target parameter is transmitted on multiple uplink frequency domain resources. For example, when the first parameter is indicated for one or more uplink frequency domain resources, the first parameters can be used to determine a time at which a first device that receives the first parameter transmits the target parameter on the corresponding uplink frequency domain resource.

[0120] The embodiment of the present application introduces multiple uplink frequency domain resources in the random access of the first device, so that multiple first devices can access the second device in parallel, thereby allowing multiple first devices to access the second device in the same time slot. Compared with the RFID in the related art that can only access a single first device in the same time slot, the access capacity and access efficiency of the communication system are effectively improved.

[0121] In some embodiments, the wireless communication method provided by the embodiments of the present application further includes: the first device receiving a second command sent by the second device.

[0122] The second command is used to adjust the first time slot value. As an example, the second command may be a QueryRep command.

[0123] In some embodiments, the second command indicates the first uplink frequency domain resource. For example, the second command indicates a corresponding relationship between a slot indication in the second command and the first uplink frequency domain resource.

[0124] In other embodiments, the second command is carried on a second downlink frequency domain resource among the multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding second commands. In other words, the second device can independently send the second command on the multiple downlink frequency domain resources.

[0125] As an example, the second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among multiple downlink frequency domain resources.

[0126] In some embodiments, the multiple downlink frequency domain resources and the multiple uplink frequency domain resources have a one-to-one, one-to-many or many-to-one mapping relationship. In short, the second downlink frequency domain resource and the first uplink frequency domain resource have a corresponding relationship.

[0127] In some embodiments, before adjusting the first time slot value according to the second command, the first device needs to first determine whether the second command is valid.

[0128] As an example, the first device may determine whether the second command is valid by determining whether the second command is applicable to the first uplink frequency domain resource.

[0129] As an example, if the second command does not indicate any uplink frequency domain resource, it means that it is valid. In this case, it means that the second command is applicable to any uplink frequency domain resource, that is, the second command is applicable to the first uplink frequency domain resource.

[0130] As another example, the second command is valid if it indicates the first uplink frequency domain resource, otherwise it is invalid.For example, the second command indicates one or more uplink frequency domain resources and the one or more uplink frequency domain resources include the first uplink frequency domain resource.

[0131] As another example, the first device may determine whether the second command is valid by including an identification field of the first device in the second command. For example, the identification field of the first device may be a session ID. If the second command includes the session ID, the second command is valid; otherwise, it is invalid.

[0132] In some embodiments, after determining that the second command is valid, the first device adjusts the first time slot value according to the second command. For example, if the second command is valid, the first time slot value of the first device is reduced by 1, otherwise it is not reduced by 1.

[0133] In some embodiments, when the first time slot value of the first device is decremented to 0, the first device sends the second parameter to the second device.

[0134] In some embodiments, in order to ensure that the first device successfully accesses the second device, the wireless communication method provided in the embodiment of the present application further includes: the first device receives a third command sent by the second device.

[0135] The third command is a confirmation command for the second parameter. For example, the third command may be an ACK instruction.

[0136] In some embodiments, the third command includes a second parameter.

[0137] In some embodiments, the third command may be transmitted via a single downlink frequency domain resource in the system. For example, when the third command is an ACK instruction, one or more first devices may be ACKed. Each first device is associated with a second parameter and a corresponding uplink frequency domain resource.

[0138] As an example, the third command indicates the first uplink frequency domain resource and the second parameter. For example, the third command indicates the correspondence between the first uplink frequency domain resource and the second parameter. For example, when the second device sends the third command, it indicates the second parameter for one or more uplink frequency domain resources. That is, the second device indicates multiple sets of (uplink frequency domain resources, second parameters), the first uplink frequency domain resource is the uplink frequency domain resource corresponding to the first device, and the first uplink frequency domain resource is one of the multiple uplink frequency domain resources.

[0139] In some embodiments, if the third command received by the first device includes the first uplink frequency domain resource and the second parameter, the first device determines that the third command is received successfully.

[0140] In some embodiments, the third command is carried on a third downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can be used to carry their respective corresponding third commands.

[0141] In some embodiments, the multiple downlink frequency domain resources have a one-to-one mapping relationship with the multiple uplink frequency domain resources. In short, there is a corresponding relationship between the third downlink frequency domain resource and the first uplink frequency domain resource.

[0142] In some embodiments, if the third command received by the first device through the third downlink frequency domain resource includes the second parameter, the first device determines that the third command is received successfully.

[0143] The following describes the embodiments of the present application in more detail with reference to specific examples. In the following examples, the first device is an A-IoT terminal device. The second device is a base station. It should be noted that the following examples are merely intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Based on the examples given, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0144] Example 1:

[0145] In this example, a wireless communication system with a single downlink frequency domain resource and multiple uplink frequency domain resources is used. The Query command indicates the Q value for each uplink frequency domain resource, the QueryRep command indicates the uplink frequency domain resource applicable to the slot, and the ACK command indicates the corresponding RN16 for the uplink frequency domain resource.

[0146] The specific implementation process of this embodiment is as follows.

[0147] 1. The A-IoT terminal receives a Query command sent by the base station. In some embodiments, the specific command name of the Query command can also be inventory request, paging, inventory, etc.

[0148] For example, an A-IoT terminal listens for a query command on a certain downlink frequency domain resource. That is, the base station only needs to send a query command on this certain downlink frequency domain resource, and all A-IoT terminals listen for the query command on this certain downlink frequency domain resource. In some embodiments, the downlink frequency domain resource can be a downlink carrier, a downlink RB, a downlink BWP, a downlink CORESET, etc.

[0149] 2. The A-IoT terminal determines the first uplink frequency domain resource.

[0150] As an implementation method, the A-IoT terminal can determine the first uplink frequency domain resource based on the terminal capability and / or the second uplink frequency domain resource provided by the base station. For example, the second uplink frequency domain resource may be one or more uplink frequency domain resources supported by the terminal; and / or the second uplink frequency domain resource may be an uplink frequency domain resource supported by the current network. As an example, the uplink frequency domain resources supported by the current network may be indicated to the terminal by the base station through a Query command or other commands. If there are multiple uplink frequency domain resources supported by the terminal and / or supported by the base station, the terminal may also select an uplink frequency domain resource randomly or according to a certain weight.

[0151] 3. The A-IoT terminal generates a random number from 0 to 2^Q-1 according to the Q value indicated for the first uplink frequency domain resource in the Query command, and uses it as the access slot value.

[0152] As an implementation, when sending a Query command, the base station indicates a Q value for one or more uplink frequency domain resources. Optionally, the Q values ​​indicated on these different uplink frequency domain resources can be the same or different. That is, the base station indicates multiple sets of (uplink frequency domain resources, Q values).

[0153] 4. The A-IoT terminal receives the QueryRep command and determines whether the QueryRep command is applicable to the first uplink frequency domain resource. If applicable, the slot value is reduced by 1; otherwise, the slot value is not reduced by 1.

[0154] In the embodiment of the present application, there is no specific limitation on the method for determining whether the QueryRep command is applicable to the first uplink frequency domain resource.

[0155] As an implementation manner: the QueryRep command does not indicate any uplink frequency domain resource. In this case, it means that the QueryRep command is applicable to any uplink frequency domain resource.

[0156] As another implementation manner: the QueryRep command indicates one or more uplink frequency domain resources and includes the first uplink frequency domain resource.

[0157] 5. When the slot value decreases to 0, the A-IoT terminal sends the first RN16 to the base station.

[0158] 6. After the A-IoT terminal sends the first RN16, the A-IoT terminal can also receive an ACK command.

[0159] Optionally, the base station may ACK one or more terminals when sending an ACK command, and each terminal is associated with RN16 and corresponding uplink frequency domain resources, that is, the ACK command may indicate multiple sets of (RN16, uplink frequency domain resources).

[0160] Optionally, if the ACK command sent by the base station includes the first uplink frequency domain resource and the first RN16, the terminal determines that the ACK command is received successfully.

[0161] This embodiment of the application performs random access of A-IoT terminals based on a single downlink frequency domain resource and multiple uplink frequency domain resources. The Query command indicates the Q value for each uplink carrier, the QueryRep command indicates the uplink carrier applicable to the slot, and the ACK command indicates the corresponding RN16 for the uplink carrier. This approach can simultaneously improve the capacity of the wireless communication system and the access efficiency of A-IoT terminals, while also improving the service quality of the wireless communication system.

[0162] Example 2

[0163] In this example, a wireless communication system with multiple downlink frequency domain resources and multiple uplink frequency domain resources is targeted. The multiple downlink frequency domain resources can be the transmission frequency domain resources of the Query command or the QueryRep command. In some embodiments, the Query command can also be sent through a downlink transmission resource. That is, in this embodiment, the Query command is sent through one downlink frequency domain resource or multiple downlink frequency domain resources. The purpose of sending through one downlink frequency domain resource or multiple downlink frequency domain resources is to determine a set of downlink frequency domain resources (i.e., multiple downlink transmission resources) for subsequently sending the QueryRep command. The QueryRep command can be sent independently on each downlink frequency domain resource. The A-IoT terminal only listens for the QueryRep command on the downlink carrier corresponding to the uplink carrier to which it belongs and calculates the slot. The A-IoT terminal determines its respective uplink frequency domain resources. For example, the A-IoT terminal can determine its respective uplink frequency domain resources through capability or random access.

[0164] The specific implementation process of this embodiment is as follows.

[0165] 1. The A-IoT terminal receives a Query command sent by the base station. In some embodiments, the specific command name of the Query command can also be inventory request, paging, inventory, etc.

[0166] As an implementation, the A-IoT terminal determines a second downlink frequency domain resource. For example, the second downlink frequency domain resource may be a system-agreed downlink frequency domain resource. Alternatively, the second downlink frequency domain resource may be selected from multiple downlink frequency domain resources in the system based on the terminal's capabilities. The A-IoT terminal may monitor for Query commands on the second downlink frequency domain resource.

[0167] In some embodiments, the base station sends the Query command only on the second downlink frequency domain resources.

[0168] In other embodiments, the base station may send the Query command in a plurality of downlink frequency domain resources in the system, where the plurality of downlink frequency domain resources include the second downlink frequency domain resource.

[0169] The embodiment of the present application does not specifically limit the downlink frequency domain resources. For example, the downlink frequency domain resources can be a downlink carrier, a downlink RB, a downlink BWP, a downlink CORESET, etc.

[0170] 2. The A-IoT terminal determines the second uplink frequency domain resource according to the terminal capability and / or the uplink frequency domain resource provided by the base station.

[0171] As an example, the uplink frequency domain resource corresponding to the second downlink frequency domain resource is used as the second uplink frequency domain resource. The network is configured with multiple uplink frequency domain resources and multiple downlink frequency domain resources, and there is a one-to-one mapping relationship. This method corresponds to the base station sending a query command on multiple downlink frequency domain resources.

[0172] As another example, the terminal selects an uplink frequency domain resource randomly or according to a certain weight from multiple uplink frequency domain resources. This method corresponds to the base station sending a Query command on only one downlink frequency domain resource.

[0173] 3. The A-IoT terminal generates a random number from 0 to 2^Q-1 according to the Q value indicated in the Query command for the second uplink frequency domain resource or for all uplink frequency domain resources, and uses it as the access slot value.

[0174] As an implementation, when sending a Query command, the base station indicates the Q value for one or more uplink frequency domain resources. The Q values ​​indicated on these different uplink frequency domain resources can be the same or different. That is, the base station indicates multiple sets of (uplink frequency domain resources, Q values).

[0175] As another implementation manner, the base station indicates the Q value for all uplink frequency domain resources. In this case, only the Q value needs to be indicated.

[0176] 4. The A-IoT terminal determines the third downlink frequency domain resource for receiving the QueryRep command.

[0177] There is a corresponding relationship between the third downlink frequency domain resource and the second uplink frequency domain resource. The base station independently sends a QueryRep command on multiple downlink frequency domain resources.

[0178] 5. The A-IoT terminal receives a QueryRep command on the third downlink frequency domain resource. If the QueryRep command is received and it is determined that it meets its own session ID, the slot value is reduced by 1; otherwise, it is not reduced by 1.

[0179] 6. When the slot value decreases to 0, the A-IoT terminal sends a second RN16 to the base station.

[0180] 7. After the A-IoT terminal sends the second RN16, the A-IoT terminal receives an ACK command on the third downlink frequency domain resource.

[0181] Optionally, if the received ACK command includes the second RN16, the terminal determines that the ACK command is received successfully.

[0182] The embodiment of the present application performs random access of A-IoT terminals based on multiple downlink frequency domain resources and multiple uplink frequency domain resources. The Quary command is sent through one downlink carrier or multiple downlink carriers (intended to determine the downlink carrier set to which the QueryRep command is subsequently sent), and the A-IoT terminal determines its own uplink carrier (for example, by capability or random determination). The QueryRep command is sent independently on each downlink carrier, and the A-IoT terminal only listens for the QueryRep command on the downlink carrier corresponding to the uplink carrier to which it belongs and calculates the slot. In this way, the capacity of the wireless communication system and the access efficiency of the A-IoT terminal can be improved at the same time.

[0183] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 11 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0184] As shown in FIG9 , a communication device 900 provided in an embodiment of the present application is shown. The communication device 900 may be the first device described above and may include a receiving unit 910 and a sending unit 920 .

[0185] The receiving unit 910 is configured to receive a first command sent by a second device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value.

[0186] The sending unit 920 is configured to send a second parameter to the second device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value.

[0187] The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and the plurality of uplink frequency domain resources can be used to carry the target parameter.

[0188] Optionally, the first command indicates a first parameter and a first uplink frequency domain resource.

[0189] Optionally, the first parameter is used to determine a sending time of the target parameter on multiple uplink frequency domain resources.

[0190] Optionally, the first command is carried on a first downlink frequency domain resource among multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding first commands.

[0191] Optionally, the first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among multiple uplink frequency domain resources.

[0192] Optionally, the first command is a query command.

[0193] Optionally, the receiving unit 910 is further used to: receive a second command sent by a second device, where the second command is used to adjust the first time slot value.

[0194] Optionally, the second command indicates the first uplink frequency domain resource.

[0195] Optionally, the second command is carried on a second downlink frequency domain resource among multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding second commands.

[0196] Optionally, the second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among multiple downlink frequency domain resources.

[0197] Optionally, the second command is a repeat query command.

[0198] Optionally, the receiving unit 910 is further configured to: receive a third command sent by the second device, where the third command is a confirmation command for the second parameter.

[0199] Optionally, the third command indicates the first uplink frequency domain resource and the second parameter.

[0200] Optionally, the third command is carried on a third downlink frequency domain resource among the multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding third commands.

[0201] Optionally, the third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among multiple downlink frequency domain resources.

[0202] Optionally, the third command includes a second parameter.

[0203] Optionally, the target parameter is a random number.

[0204] Optionally, the first device is an A-IoT terminal.

[0205] Optionally, the second device is a network device; or, the second device is an intermediate device communicatively connected to the network device and the first device.

[0206] As shown in FIG10 , a communication device 1000 is provided in an embodiment of the present application. The communication device 1000 may be the second device described above and may include a sending unit 1010 and a receiving unit 1020 .

[0207] The sending unit 1010 is configured to send a first command to a first device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value.

[0208] The receiving unit 1020 is configured to receive a second parameter sent by the first device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value.

[0209] The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and the plurality of uplink frequency domain resources can be used to carry the target parameter.

[0210] Optionally, the first command indicates a first parameter and a first uplink frequency domain resource.

[0211] Optionally, the first parameter is used to determine a sending time of the target parameter on multiple uplink frequency domain resources.

[0212] Optionally, the first command is carried on a first downlink frequency domain resource among multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding first commands.

[0213] Optionally, the first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among multiple uplink frequency domain resources.

[0214] Optionally, the first command is a query command.

[0215] Optionally, the sending unit 1010 is further used to: send a second command to the first device, where the second command is used to adjust the first time slot value.

[0216] Optionally, the second command indicates the first uplink frequency domain resource.

[0217] Optionally, the second command is carried on a second downlink frequency domain resource among multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding second commands.

[0218] Optionally, the second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among multiple downlink frequency domain resources.

[0219] Optionally, the second command is a repeat query command.

[0220] Optionally, the sending unit 1010 is further configured to send a third command to the first device, where the third command is a confirmation command for the second parameter.

[0221] Optionally, the third command indicates the first uplink frequency domain resource and the second parameter.

[0222] Optionally, the third command is carried on a third downlink frequency domain resource among the multiple downlink frequency domain resources, and the multiple downlink frequency domain resources can be used to carry their respective corresponding third commands.

[0223] Optionally, the third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among multiple downlink frequency domain resources.

[0224] Optionally, the third command includes a second parameter.

[0225] Optionally, the target parameter is a random number.

[0226] Optionally, the first device is an A-IoT terminal.

[0227] Optionally, the second device is a network device; or, the second device is an intermediate device communicatively connected to the network device and the first device.

[0228] FIG11 is a schematic block diagram of a communication device to which embodiments of the present application may be applied. The dashed lines in FIG11 indicate that the unit or module is optional. Apparatus 1100 may be used to implement the method described in the above method embodiment. Apparatus 1100 may be a chip or a communication device.

[0229] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the above method embodiment. The processor 1110 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.

[0230] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store programs that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the above method embodiments. The memories 1120 may be independent of the processor 1110 or integrated into the processor 1110.

[0231] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips via the transceiver 1130.

[0232] 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 network element, application function network element, or first communication device provided in the present application, and the program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in each embodiment of the present application.

[0233] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the first network element, application function network element, or first communication device provided in the embodiments of the present application, and the program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in various embodiments of the present application.

[0234] The present application also provides a computer program. This computer program can be applied to the first network element, application function network element, or first communication device provided in the present application, and the computer program causes a computer to execute the method performed by the first network element, application function network element, or first communication device in each embodiment of the present application.

[0235] 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" 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" and any variations thereof are intended to cover non-exclusive inclusions.

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

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

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

[0239] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0240] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

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

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

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

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

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

[0246] 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)).

[0247] 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 the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The first device receives a first command sent by the second device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value; The first device sends a second parameter to the second device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value; The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and all of the plurality of uplink frequency domain resources can be used to carry the target parameter.

2. The method according to claim 1, characterized in that The first command indicates the first parameter and the first uplink frequency domain resource.

3. The method according to claim 1, characterized in that The first parameter is used to determine a sending time of the target parameter on the multiple uplink frequency domain resources.

4. The method according to claim 1, wherein The first command is carried on a first downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding first commands.

5. The method according to claim 4, characterized in that The first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among the multiple uplink frequency domain resources.

6. The method according to any one of claims 2 to 5, characterized in that The first command is a query command.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first device receives a second command sent by the second device, where the second command is used to adjust the first time slot value.

8. The method according to claim 7, characterized in that The second command indicates the first uplink frequency domain resource.

9. The method according to claim 7, characterized in that The second command is carried on a second downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding second commands.

10. The method according to claim 9, characterized in that The second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

11. The method according to any one of claims 7 to 10, characterized in that The second command is a repeat query command.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: The first device receives a third command sent by the second device, where the third command is a confirmation command for the second parameter.

13. The method according to claim 12, characterized in that The third command indicates the first uplink frequency domain resource and the second parameter.

14. The method according to claim 12, characterized in that The third command is carried on a third downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding third commands.

15. The method according to claim 14, characterized in that The third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

16. The method according to any one of claims 12 to 15, characterized in that The third command includes the second parameter.

17. The method according to any one of claims 1 to 16, characterized in that The target parameter is a random number.

18. The method according to any one of claims 1 to 17, characterized in that The first device is an A-IoT terminal.

19. The method according to any one of claims 1 to 18, characterized in that The second device is a network device; or, the second device is an intermediate device that is communicatively connected to the network device and the first device.

20. A wireless communication method, characterized in that: include: The second device sends a first command to the first device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value; The second device receives a second parameter sent by the first device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value; The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and all of the plurality of uplink frequency domain resources can be used to carry the target parameter.

21. The method according to claim 20, characterized in that The first command indicates the first parameter and the first uplink frequency domain resource.

22. The method according to claim 20, characterized in that The first parameter is used to determine a sending time of the target parameter on the multiple uplink frequency domain resources.

23. The method according to claim 20, characterized in that The first command is carried on a first downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding first commands.

24. The method according to claim 23, wherein The first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among the multiple uplink frequency domain resources.

25. The method according to any one of claims 21 to 24, characterized in that The first command is a query command.

26. The method according to any one of claims 20 to 25, characterized in that The method further comprises: The second device sends a second command to the first device, where the second command is used to adjust the first time slot value.

27. The method according to claim 26, characterized in that The second command indicates the first uplink frequency domain resource.

28. The method according to claim 26, characterized in that The second command is carried on a second downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding second commands.

29. The method according to claim 28, characterized in that The second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

30. The method according to any one of claims 26 to 29, characterized in that The second command is a repeat query command.

31. The method according to any one of claims 20 to 30, characterized in that The method further comprises: The second device sends a third command to the first device, where the third command is a confirmation command for the second parameter.

32. The method according to claim 31, characterized in that The third command indicates the first uplink frequency domain resource and the second parameter.

33. The method according to claim 31, wherein The third command is carried on a third downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding third commands.

34. The method according to claim 33, wherein The third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

35. The method according to any one of claims 31 to 34, characterized in that The third command includes the second parameter.

36. The method according to any one of claims 20 to 25, characterized in that The target parameter is a random number.

37. The method according to any one of claims 20 to 26, characterized in that The first device is an A-IoT terminal.

38. The method according to any one of claims 20 to 37, characterized in that The second device is a network device; or, the second device is an intermediate device that is communicatively connected to the network device and the first device.

39. A communication device, characterized in that: The communication device is a first device, and the communication device includes: a receiving unit, configured to receive a first command sent by a second device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value; a sending unit, configured to send a second parameter to the second device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value; The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and all of the plurality of uplink frequency domain resources can be used to carry the target parameter.

40. The communication device according to claim 39, wherein The first command indicates the first parameter and the first uplink frequency domain resource.

41. The communication device according to claim 39, wherein: The first parameter is used to determine a sending time of the target parameter on the multiple uplink frequency domain resources.

42. The communication device according to claim 39, wherein: The first command is carried on a first downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding first commands.

43. The communication device according to claim 42, characterized in that The first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among the multiple uplink frequency domain resources.

44. The communication device according to any one of claims 40 to 43, characterized in that The first command is a query command.

45. The communication device according to any one of claims 39 to 44, characterized in that The receiving unit is further configured to: A second command sent by the second device is received, where the second command is used to adjust the first time slot value.

46. The communication device according to claim 45, characterized in that The second command indicates the first uplink frequency domain resource.

47. The communication device according to claim 45, characterized in that The second command is carried on a second downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding second commands.

48. The communication device according to claim 47, characterized in that The second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

49. The communication device according to any one of claims 45 to 48, characterized in that The second command is a repeat query command.

50. The communication device according to any one of claims 39 to 49, characterized in that The receiving unit is further configured to: A third command sent by the second device is received, where the third command is a confirmation command for the second parameter.

51. The communication device according to claim 50, characterized in that The third command indicates the first uplink frequency domain resource and the second parameter.

52. The communication device according to claim 50, characterized in that The third command is carried on a third downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding third commands.

53. The communication device according to claim 52, characterized in that The third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

54. The communication device according to any one of claims 50 to 53, characterized in that The third command includes the second parameter.

55. The communication device according to any one of claims 39 to 54, characterized in that The target parameter is a random number.

56. The communication device according to any one of claims 39 to 55, characterized in that The first device is an A-IoT terminal.

57. The communication device according to any one of claims 39 to 56, characterized in that The second device is a network device; or, the second device is an intermediate device that is communicatively connected to the network device and the first device.

58. A communication device, characterized in that The communication device is a second device, and the communication device includes: a sending unit, configured to send a first command to a first device, where the first command includes a first parameter, and the first parameter is used to determine a first time slot value; a receiving unit, configured to receive a second parameter sent by the first device, where the second parameter is a target parameter for accessing the second device, and a sending time of the second parameter is determined based on the first time slot value; The second parameter is carried on a first uplink frequency domain resource among a plurality of uplink frequency domain resources, and all of the plurality of uplink frequency domain resources can be used to carry the target parameter.

59. The communication device according to claim 58, characterized in that The first command indicates the first parameter and the first uplink frequency domain resource.

60. The communication device according to claim 58, wherein The first parameter is used to determine a sending time of the target parameter on the multiple uplink frequency domain resources.

61. The communication device according to claim 58, wherein The first command is carried on a first downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding first commands.

62. The communication device according to claim 61, characterized in that The first uplink frequency domain resource is an uplink frequency domain resource corresponding to the first downlink frequency domain resource among the multiple uplink frequency domain resources.

63. The communication device according to any one of claims 59 to 62, characterized in that The first command is a query command.

64. The communication device according to any one of claims 58 to 63, characterized in that The sending unit is further configured to: A second command is sent to the first device, where the second command is used to adjust the first time slot value.

65. The communication device according to claim 64, characterized in that The second command indicates the first uplink frequency domain resource.

66. The communication device according to claim 64, characterized in that The second command is carried on a second downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding second commands.

67. The communication device according to claim 66, characterized in that The second downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

68. The communication device according to any one of claims 64 to 67, characterized in that The second command is a repeat query command.

69. The communication device according to any one of claims 58 to 68, characterized in that The sending unit is further configured to: A third command is sent to the first device, where the third command is a confirmation command for the second parameter.

70. The communication device according to claim 69, characterized in that The third command indicates the first uplink frequency domain resource and the second parameter.

71. The communication device according to claim 69, wherein The third command is carried on a third downlink frequency domain resource among a plurality of downlink frequency domain resources, and the plurality of downlink frequency domain resources can all be used to carry their respective corresponding third commands.

72. The communication device according to claim 71, characterized in that The third downlink frequency domain resource is a downlink frequency domain resource corresponding to the first uplink frequency domain resource among the multiple downlink frequency domain resources.

73. The communication device according to any one of claims 69 to 72, characterized in that The third command includes the second parameter.

74. The communication device according to any one of claims 58 to 73, characterized in that The target parameter is a random number.

75. The communication device according to any one of claims 58 to 74, characterized in that The first device is an A-IoT terminal.

76. The communication device according to any one of claims 58 to 75, characterized in that The second device is a network device; or, the second device is an intermediate device that is communicatively connected to the network device and the first device.

77. A communication device, characterized in that The system comprises 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 to execute the method according to any one of claims 1-19 or 20-38.

78. A device, characterized in that The device comprises a processor configured to call a program from a memory to execute the method according to any one of claims 1 to 19 or 20 to 38.

79. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 19 or 20 to 38.

80. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1-19 or 20-38.

81. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 19 or 20 to 38.

82. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 19 or 20 to 38.

Images