The application provides a data transmission method and a communication device, which can reduce the number of times that a first device (such as a reader) transmits scheduling information, thereby reducing the overhead when the first device transmits the scheduling information.
In a first aspect, a method of data transmission is provided, which may be performed by a second device (e.g., a tag), or may also be performed by a component (e.g., a chip or a circuit) of the second device, which is not limited. For convenience of description, an example will be described below as being executed by the second device.
The method may include: the second device obtains scheduling information of first downlink data from the first device; and the second equipment receives second downlink data from the first equipment according to the scheduling information of the first downlink data, wherein the sending time of the second downlink data is positioned after the sending time of the first downlink data.
Based on the above technical solution, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data. When there are a plurality of second devices, the plurality of second devices can all receive the second downlink data from the first device according to the scheduling information of the first downlink data. When the second downlink data sent by the first device to the plurality of second devices is multiple times, the plurality of second devices can all receive the second downlink data sent by the first device each time according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
The time for transmitting the second downlink data is located after the time for transmitting the first downlink data, which may be expressed as that the second downlink data is located after the first downlink data in a time domain position, or that a time domain resource of the second downlink data is located after a time domain resource of the first downlink data.
For example, the scheduling information of the first downlink data may include at least one of the following transmission parameters of the first downlink data: bandwidth, frequency domain resource location, time domain resource location, subcarrier spacing, cyclic Prefix (CP) type, line code parameters, channel coding parameters, modulation scheme, number of repetitions, spreading factor, data rate, time length, modulation depth, duty cycle, number of occupied time units, redundancy version.
With reference to the first aspect, in certain implementations of the first aspect, the second downlink data is downlink data received from the first device before the second device sends the uplink data to the first device.
With reference to the first aspect, in certain implementation manners of the first aspect, before the second device receives the second downlink data, the method further includes: the second device determines the type of the first downstream data and/or the second device determines the identity of the first downstream data.
Based on the above technical solution, after the second device determines the type of the first downlink data and/or after the second device determines the identifier of the first downlink data, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data. By the method, the time for the second equipment to determine the first downlink data can be reduced, and the efficiency of the second equipment for receiving the second downlink data is improved.
With reference to the first aspect, in certain implementations of the first aspect, the type of the first downlink data is any one of: multicast, broadcast or unicast.
With reference to the first aspect, in certain implementations of the first aspect, the identification of the first downlink data is a logical channel identification.
With reference to the first aspect, in some implementations of the first aspect, the second device obtains scheduling information of the first downlink data, including: the second device receives scheduling information of first downlink data from the first device.
Based on the technical scheme, the second device can determine the scheduling information of the first downlink data, so that the second downlink data from the first device can be received according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the second equipment receives a synchronizing signal from the first equipment, wherein the synchronizing signal is used for indicating whether the synchronizing signal is followed by scheduling information of first downlink data or not; the second device obtains scheduling information of the first downlink data, including: and the second equipment determines the scheduling information of the first downlink data according to the synchronous signal.
Based on the technical scheme, the second device can determine the scheduling information of the first downlink data according to the synchronous signals, so that the first device can send the first downlink data to the second device at any time, the scheduling flexibility of the first device is improved, in addition, the first device and the second device can be guaranteed to understand consistently, and the communication reliability is improved.
With reference to the first aspect, in certain implementations of the first aspect, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
With reference to the first aspect, in certain implementation manners of the first aspect, before the second device receives the second downlink data, the method further includes: the second device receives indication information from the first device, wherein the indication information is used for indicating the second device to receive second downlink data from the first device according to scheduling information of the first downlink data.
Based on the technical scheme, the second equipment can accurately receive the second downlink data from the first equipment, so that the resource consumption of the second equipment is reduced, and the efficiency of the second equipment for receiving the second downlink data is improved.
In a second aspect, a method of data transmission is provided, which may be performed by a first device (e.g., a reader), or may also be performed by a component of the first device (e.g., a chip or a circuit), without limitation. For convenience of description, an example will be described below as being executed by the first device.
The method may include: the first equipment determines scheduling information of first downlink data; and the first equipment sends second downlink data to the second equipment according to the scheduling information of the first downlink data, wherein the sending time of the second downlink data is positioned after the sending time of the first downlink data.
Based on the above technical scheme, the first device may send the second downlink data to the second device according to the scheduling information of the first downlink data. By the method, the first device can only send the scheduling information of the first downlink data to the second device without sending the scheduling information of the second downlink data to the second device, so that the second device can also receive the second downlink data from the first device according to the scheduling information of the first downlink data, the times of sending the scheduling information by the first device can be reduced, and the cost when the first device sends the scheduling information is reduced.
With reference to the second aspect, in some implementations of the second aspect, the second downlink data is downlink data sent to the second device before the first device receives uplink data from the second device.
With reference to the second aspect, in some implementations of the second aspect, before the first device sends the second downlink data, the method further includes: the first device determines a type of the first downlink data and/or the first device determines an identification of the first downlink data.
Based on the above technical solution, after the first device determines the type of the first downlink data and/or after the first device determines the identifier of the first downlink data, the first device may send the second downlink data to the second device according to the scheduling information of the first downlink data. By the method, the time for the first device to determine the first downlink data can be reduced, and the efficiency of the first device for transmitting the second downlink data is improved.
With reference to the second aspect, in certain implementations of the second aspect, the type of the first downlink data is any one of: multicast, broadcast or unicast.
With reference to the second aspect, in certain implementations of the second aspect, the identification of the first downlink data is a logical channel identification.
With reference to the second aspect, in some implementations of the second aspect, before the first device sends the second downlink data, the method further includes: the first device transmits scheduling information of the first downlink data to the second device.
Based on the technical scheme, the second device can receive the scheduling information of the first downlink data from the first device, so that the second device can receive the second downlink data from the first device according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
With reference to the second aspect, in some implementations of the second aspect, before the first device sends the second downlink data, the method further includes: the first device sends a synchronization signal to the second device, where the synchronization signal is used to indicate whether there is scheduling information of the first downlink data after the synchronization signal.
Based on the technical scheme, the second device can determine the scheduling information of the first downlink data according to the synchronous signals, so that the first device can send the first downlink data to the second device at any time, the scheduling flexibility of the first device is improved, in addition, the first device and the second device can be guaranteed to understand consistently, and the communication reliability is improved.
With reference to the second aspect, in certain implementations of the second aspect, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
With reference to the second aspect, in some implementations of the second aspect, before the first device sends the second downlink data, the method further includes: the first device sends indication information to the second device, wherein the indication information is used for indicating the second device to receive second downlink data from the first device according to scheduling information of the first downlink data.
Based on the technical scheme, the second equipment can accurately receive the second downlink data from the first equipment, so that the resource consumption of the second equipment is reduced, and the efficiency of the second equipment for receiving the second downlink data is improved.
In a third aspect, there is provided an apparatus for data transmission, which may be performed by a second device (e.g. a tag), or may also be performed by a component (e.g. a chip or a circuit) of the second device, which is not limited thereto. For convenience of description, an example will be described below as being executed by the second device.
The apparatus may include: the device comprises an acquisition unit and a receiving and transmitting unit, wherein the acquisition unit is used for acquiring scheduling information of first downlink data from first equipment; and the receiving and transmitting unit is used for receiving second downlink data from the first equipment according to the scheduling information of the first downlink data, wherein the sending time of the second downlink data is positioned after the sending time of the first downlink data.
Based on the above technical solution, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data. When there are a plurality of second devices, the plurality of second devices can all receive the second downlink data from the first device according to the scheduling information of the first downlink data. When the second downlink data sent by the first device to the plurality of second devices is multiple times, the plurality of second devices can all receive the second downlink data sent by the first device each time according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
With reference to the third aspect, in some implementations of the third aspect, the second downlink data is downlink data received from the first device before the apparatus sends the uplink data to the first device.
With reference to the third aspect, in certain implementations of the third aspect, the apparatus further includes a processing unit, where the processing unit is configured to determine a type of the first downlink data, and/or the processing unit is configured to determine an identification of the first downlink data.
With reference to the third aspect, in some implementations of the third aspect, the type of the first downlink data is any one of: multicast, broadcast or unicast.
With reference to the third aspect, in some implementations of the third aspect, the identification of the first downlink data is a logical channel identification.
With reference to the third aspect, in some implementations of the third aspect, the transceiver unit is configured to receive scheduling information of the first downlink data from the first device.
With reference to the third aspect, in some implementations of the third aspect, the apparatus further includes a processing unit, a transceiver unit, and a receiving unit, where the transceiver unit is configured to receive a synchronization signal from the first device, where the synchronization signal is used to indicate whether there is scheduling information of the first downlink data after the synchronization signal; and the processing unit is used for determining the scheduling information of the first downlink data according to the synchronous signals.
With reference to the third aspect, in certain implementations of the third aspect, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
With reference to the third aspect, in some implementations of the third aspect, the processing unit is configured to receive indication information from the first device, where the indication information is used to instruct the apparatus to receive second downlink data from the first device according to scheduling information of the first downlink data.
In a fourth aspect, there is provided an apparatus for data transmission, which may be performed by a first device (e.g. a reader), or may also be performed by a component (e.g. a chip or a circuit) of the first device, which is not limited thereto. For convenience of description, an example will be described below as being executed by the first device.
The apparatus may include: the processing unit is used for determining the scheduling information of the first downlink data; and the receiving and transmitting unit is used for transmitting second downlink data to the second equipment according to the scheduling information of the first downlink data, wherein the transmission time of the second downlink data is positioned after the transmission time of the first downlink data.
Based on the above technical scheme, the first device may send the second downlink data to the second device according to the scheduling information of the first downlink data. By the method, the first device can only send the scheduling information of the first downlink data to the second device without sending the scheduling information of the second downlink data to the second device, so that the second device can also receive the second downlink data from the first device according to the scheduling information of the first downlink data, the times of sending the scheduling information by the first device can be reduced, and the cost when the first device sends the scheduling information is reduced.
With reference to the fourth aspect, in some implementations of the fourth aspect, the second downstream data is downstream data that is sent to the second device before the apparatus receives upstream data from the second device.
With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is configured to determine a type of the first downlink data, and/or the processing unit is configured to determine an identification of the first downlink data.
With reference to the fourth aspect, in some implementations of the fourth aspect, the type of the first downlink data is any one of: multicast, broadcast or unicast.
With reference to the fourth aspect, in some implementations of the fourth aspect, the identification of the first downlink data is a logical channel identification.
With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is configured to send scheduling information of the first downlink data to the second device.
With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is configured to send a synchronization signal to the second device, where the synchronization signal is used to indicate whether the synchronization signal is followed by scheduling information of the first downlink data.
With reference to the fourth aspect, in certain implementations of the fourth aspect, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
With reference to the fourth aspect, in some implementations of the fourth aspect, the transceiver is configured to send, to the second device, indication information, where the indication information is used to instruct the second device to receive, according to scheduling information of the first downlink data, the second downlink data from the apparatus.
In a fifth aspect, a communication device is provided for performing the method of any of the possible implementations of the first and second aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method in any of the possible implementations of the first and second aspects.
In one implementation, the apparatus is a first device or a second device. When the apparatus is a first device or a second device, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.
In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for the first device or the second device. When the apparatus is a chip, a system-on-chip or a circuit for a first device or a second device, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuit, etc. on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.
In a sixth aspect, there is provided a communication apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform the method of any one of the possible implementations of the first and second aspects. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.
In one implementation, the apparatus is a first device or a second device.
In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for the first device or the second device.
In a seventh aspect, the present application provides a processor configured to perform the method provided in the above aspects.
The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited in this application.
In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method in any one of the possible implementations of the first and second aspects.
In a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first and second aspects described above.
In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored on a memory through the communication interface, and executing the method provided by any one of the possible implementation manners of the first aspect and the second aspect.
Optionally, as an implementation manner, the chip further includes a memory, where a computer program or an instruction is stored in the memory, and the processor is configured to execute the computer program or the instruction stored in the memory, where the computer program or the instruction is executed, and the processor is configured to execute a method provided by any one of possible implementation manners of the first aspect and the second aspect.
In an eleventh aspect, a chip is provided, the chip comprising logic circuitry and a communication interface, the communication interface being configured to receive data and/or information to be processed and to transmit the data and/or information to be processed to the logic circuitry, the logic circuitry being configured to perform the method provided by any one of the possible implementations of the first and second aspects.
Drawings
Fig. 1 shows a schematic diagram of a communication scenario suitable for use in embodiments of the present application.
Fig. 2 shows a schematic diagram of a communication process suitable for use in embodiments of the present application.
Fig. 3 shows a schematic diagram of yet another communication procedure suitable for use in embodiments of the present application.
The network device in this embodiment of the present application may be a device for communicating with a terminal device, which may be a base station (base transceiver station, BTS) in a global system for mobile communications (global system for mobile communications, GSM) or code division multiple access (code division multiple access, CDMA), a base station (NodeB, NB) in a wideband code division multiple access (wideband code division multiple access, WCDMA) system, an evolved NodeB (eNB or eNodeB) in an LTE system, a wireless controller in a cloud wireless access network (cloud radio access network, CRAN) scenario, or a network device in a relay station, an access point, an in-vehicle device, a wearable device, and a 5G network, or a network device in a future evolution PLMN network, one or a group of base stations (including a plurality of antenna panels) in a 5G system, or a network node that forms a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), or the embodiment of the present application is not limited.
In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.
In the embodiment of the application, the terminal device or the network device includes a hardware layer, an operating system layer running above the hardware layer, and an application layer running above the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like. Further, the embodiment of the present application is not particularly limited to the specific structure of the execution body of the method provided in the embodiment of the present application, as long as the communication can be performed by the method provided in the embodiment of the present application by running the program recorded with the code of the method provided in the embodiment of the present application, and for example, the execution body of the method provided in the embodiment of the present application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call the program and execute the program.
The rapid development of IoT technology makes everything interconnected a step by step, but the problem of battery life of IoT terminal devices greatly increases the maintenance difficulty and maintenance cost of the terminal devices, and becomes a main bottleneck restricting IoT development. Passive backscatter communication based on wireless power transmission, envelope detection demodulation and reflection scatter modulation techniques is expected to solve the service life and maintenance problems of terminal equipment, so that the next-generation terminal equipment has ultra-low cost, high density and maintenance-free performance.
Backscatter communication systems typically consist of an exciter, a receiver, a reflector (or tag), with a communication link that includes an exciter to reflector downlink and a reflector to receiver uplink. The downlink is typically modulated by amplitude shift keying (amplitude shift keying, ASK), and the reflector can demodulate the downlink modulated signal based on a low power envelope detector. The reflector changes the load of the antenna based on the information bits to be transmitted so that the information bits thereof can be modulated onto the incident carrier wave, thereby realizing wireless transmission of uplink data. The reflector does not need high-power consumption devices such as a radio frequency oscillator, a power amplifier, a low-noise amplifier and the like, so the reflector has the characteristics of low cost and ultra-low power consumption.
Reflectors can be classified into passive reflectors and semi-passive reflectors, depending on whether they are battery powered or not. The passive reflector does not have a power supply, the downlink radio frequency signal needs to be rectified, and the direct current voltage output by rectification is used as the power supply for analog and digital circuits. The semi-passive reflector itself has a power supply that is independent of the rectified output of the downstream radio frequency signal.
A widely used ultra-high frequency (UHF) radio frequency identification (Radio Frequency Identification, RFID) system is one type of backscatter communication system. In a typical passive UHF RFID system architecture, a reader provides energy to a tag by sending a downstream excitation signal to the tag, which receives the signaling sent by the reader, and sends an upstream signal to the reader via backscatter technology. In this way, the reader can recognize the label and perform operations such as reading/writing on the label.
In addition to the backscatter communication system, there is a system with a wake-up mechanism in which a network device can send a downlink wake-up signal (WUS) to a terminal device in a power saving mode (power saving mode, PSM) or sleep mode to enable the terminal device to save more power. The modulation mode of the wake-up signal can adopt on-off keying (OOK)/ASK, so that the terminal equipment can demodulate the downlink modulation signal based on the envelope detector with low power consumption, thereby reducing the standby power consumption of the terminal wake-up receiver and prolonging the standby life.
Since the backscatter communication system and the wake-up system are typically asynchronous systems, i.e. the terminal device and the network device do not achieve strict synchronization. Therefore, a synchronization signal (also called a preamble) needs to be inserted before the valid data of the downlink signal for the terminal to complete the downlink signal detection and frame synchronization functions.
Fig. 1 shows a schematic diagram of a communication scenario suitable for use in embodiments of the present application. The communication system in fig. 1 may include at least one terminal device (e.g., terminal device 110, terminal device 120, terminal device 130, terminal device 140, terminal device 150, and terminal device 160) and a network device 170. The network device 170 is configured to provide a communication service for a terminal device and access the core network, and the terminal device may access the network by searching for a synchronization signal, a broadcast signal, etc. transmitted by the network device 170, thereby establishing communication with the network device. Terminal device 110, terminal device 120, terminal device 130, terminal device 140, and terminal device 160 in fig. 1 may perform uplink and downlink transmission with network device 170. For example, the network device 170 may transmit downlink data to the terminal device 110, the terminal device 120, the terminal device 130, the terminal device 140, and the terminal device 160, and may also receive uplink data transmitted by the terminal device 110, the terminal device 120, the terminal device 130, the terminal device 140, and the terminal device 160.
In addition, the terminal device 140, the terminal device 150, and the terminal device 160 may be regarded as one communication system, and the terminal device 160 may transmit downlink data to the terminal device 140 and the terminal device 150, or may receive uplink data transmitted by the terminal device 140 and the terminal device 150.
It should be appreciated that the network devices included in the communication system may be one or more. A network device may transmit data to one or more terminals. Multiple network devices may also transmit data to one or more terminals simultaneously.
In a passive internet of things system, a reader may send a waveform containing a high level continuously to a tag, which may reflect information to a receiver over a reverse link after receiving energy. In the RFID air interface protocol ISO 18000-6C, dynamic slotted ALOHA technology is used to reflect information to a receiver after a tag receives energy.
In the following embodiments, it is assumed that the reader is a first device and the tag is a second device. The first device may be a network device, or may be a terminal device, or may be other devices, and the second device may be a terminal device, or may be other devices.
In the following embodiments, the first downstream data and the second downstream data are mentioned a plurality of times. It should be understood that, the data sent by the first device to the second device is downlink data, the data sent by the first device to the second device is denoted as first downlink data, the data sent by the first device to the second device after the first downlink data is denoted as second downlink data, and the naming of the first downlink data and the second downlink data should not limit the scope of the embodiments of the present application.
Fig. 2 shows a schematic diagram of a communication process suitable for use in embodiments of the present application. As shown in fig. 2, the communication process between the first device and the second device may be described as follows.
The first device may send selection signaling (e.g., select signaling) to the second device, which may select a particular second device/second device group for inventory and access, wherein the second device group is a collection of multiple second devices. The selection signaling may include the following parameters: an object (target), a function (action), a store (memory bank), a pointer (pointer), a length (length), a mask, and a truncate (truncate). For the meaning of the individual parameters reference can be made to EPCTM Radio-Frequency Identity Protocols Generation-2UHF RFID Standard, release 2.1.
The first device may send first downlink data (e.g., query signaling) to the second devices, the parameters of the first downlink data including Q, each of the second devices/second device groups to be inventoried from (0, 2)Q -1) selecting a random number within the range of the counter and storing it in the corresponding slot counter. When the random number selected by the second equipment is not 0, the second equipment enters an arbitration state; when the random number selected by the second device is 0, the second device enters a response state and sends uplink data (such as RN16 signaling) to the first device. After receiving the uplink data from the second device, the first device sends acknowledgement signaling (such as ACK signaling) containing the uplink data to the second device, so as to acknowledge the second device. The second device being authenticated enters the authentication state and reports its electronic product code (electronic product code, EPC), thereby completing the basic information inventory process of the second device. When the second device that completes the inventory process receives the inventory request from the first deviceWhen the second downstream data (such as queryrep signaling, and querydjust signaling), the inventory flag of the second device is set to be inverted, and enters into the ready state, ending the inventory process.
When the second downlink data received by the second device in the second device/second device group entering the arbitration state is queryrep signaling, the value in the time slot counter corresponding to the second device is reduced by 1 until the value in the time slot counter corresponding to the second device becomes 0, the second device enters the response state, and the response process is repeated.
When the second downlink data received by the second device in the second device/second device group entering the arbitration state is queryadjust signaling, the second device adjusts the Q value and re-transmits the Q value from (0, 2)Q -1) selecting a random number within the range of the time slot counter and storing the random number in the corresponding time slot counter, thereby updating the random number originally stored in the time slot counter. When the random number selected by the second equipment is not 0, the second equipment enters an arbitration state; when the random number selected by the second device is 0, the second device enters a response state, and repeats the above-mentioned response process.
In the prior art, a first device may send a synchronization signal to a second device, where the synchronization signal carries scheduling information of downlink data. The second device, after receiving the synchronization signal, often needs to perform a number of sliding correlations to obtain time synchronization. However, the scheduling information of the downlink data carried by the synchronization signal may increase the complexity of the second device when performing the sliding correlation operation. For example, the scheduling information of the downlink data carried by the synchronization signal occupies N bits, and the complexity of the second device performing the sliding correlation operation may increase by 2N Multiple times.
In order to avoid increasing the complexity of the second device in performing the sliding-related operation, the first device may not carry the scheduling information of the downlink data in the synchronization signal, for example, the first device may carry the scheduling information of the downlink data in the control information of the downlink data.
Fig. 3 shows a schematic diagram of yet another communication procedure suitable for use in embodiments of the present application. As shown in fig. 3, after the first device sends the selection signaling to the second device (e.g., the second device 1, and also e.g., the second device 2), the first device further sends first downlink data and control information of the first downlink data to the second device, where the control information of the first downlink data carries scheduling information of the first downlink data.
When the random number selected by the second device 1 is 0, the second device 1 enters a response state and transmits uplink data to the first device. After receiving the uplink data from the second device 1, the first device sends an acknowledgement signaling containing the uplink data to the second device 1, so that the second device 1 can be acknowledged. The confirmed second device 1 enters the confirmation state and reports its electronic product code, thereby completing the basic information inventory process of the second device 1. When the second device 1 that completes the inventory process receives the second downstream data from the first device, the inventory flag of the second device 1 will be set in reverse, and enter a ready state, ending the inventory process.
When the second device 2 that enters the arbitration state receives the second downstream data from the first device and the control information of the second downstream data, in the case where the value in the slot counter corresponding to the second device 2 becomes 0, the second device 2 enters the response state and repeats the same response procedure as the second device 1. Wherein, the control information of the second downlink data carries scheduling information of the second downlink data.
For a specific description of the communication procedure between the first device and the second device, reference may be made to the description in fig. 2, and no further description is given here.
When there are a plurality of second devices, the second devices entering the arbitration state determine whether the value in the slot counter is 0 every time the second devices receive the second downlink data, considering that the second downlink data transmitted from the first device to the second devices may be multiple times. When there is a value of 0 in the slot counter of the second device, the second device enters a response state and repeats the same response procedure as the second device 1.
As shown in fig. 3, it is assumed that the plurality of second devices includes the second device 1 and the second device 2, and further includes the second device 3. When the second device 1, the second device 2 and the second device 3 receive the first downlink data from the first device, the second device 1 determines that the value in its time slot counter is 0, the second device 2 determines that the value in its time slot counter is 1, and the second device 3 determines that the value in its time slot counter is 2, so that the second device 1 enters a response state and repeats the same response procedure as the second device 1, and the second device 2 and the second device 3 enter an arbitration state. When the second device 2 and the second device 3 receive the second downstream data from the first device, the second device 2 determines that the value in its slot counter becomes 0, the second device 3 determines that the value in its slot counter becomes 1, and therefore the second device 2 enters the response state, and repeats the same response procedure as the second device 1, and the second device 3 enters the arbitration state. When the second device 3 receives the second downstream data from the first device again, the second device 3 determines that the value in its slot counter becomes 0, the second device 3 enters a response state, and repeats the same response procedure as the second device 1.
When the first device sends multiple downlink data (such as first downlink data and multiple second downlink data) to the second device, the first device also sends control information corresponding to the multiple downlink data (such as control information of the first downlink data and control information corresponding to the multiple second downlink data) to the second device, where the control information corresponding to the multiple downlink data carries scheduling information corresponding to the multiple downlink data, for example, the control information of the first downlink data carries scheduling information of the first downlink data, and for example, the control information of the second downlink data carries scheduling information of the second downlink data, so that overhead when the first device sends the scheduling information is increased.
In view of the above technical problems, the present application provides a data transmission method, by which the number of times of sending scheduling information can be reduced, thereby reducing overhead when the first device sends the scheduling information.
A method for data transmission according to an embodiment of the present application is described below with reference to fig. 4 to 7.
Fig. 4 is a schematic diagram of a method 400 for data transmission according to an embodiment of the present application. As shown in fig. 4, the method 400 may include the following steps.
The second device obtains scheduling information for the first downlink data from the first device 410.
The scheduling information of the first downlink data may be carried in the control information of the first downlink data. The scheduling information of the first downlink data may include at least one of the following transmission parameters of the first downlink data: bandwidth, frequency domain resource location, time domain resource location, subcarrier spacing, cyclic Prefix (CP) type, line code parameters, channel coding parameters, modulation scheme, number of repetitions, spreading factor, data rate, time length, modulation depth, duty cycle, number of occupied time units, redundancy version.
And 420, the second device receives the second downlink data from the first device according to the scheduling information of the first downlink data, wherein the sending time of the second downlink data is after the sending time of the first downlink data.
It should be understood that after the first device sends the first downlink data to the second device, the first device may send the second downlink data to the second device once, or may send the second downlink data to the second device multiple times.
The time for sending the second downlink data may be expressed as that the second downlink data is located after the first downlink data in a time domain position, or may be expressed as that a time domain resource of the second downlink data is located after a time domain resource of the first downlink data, or may have other expression forms, which is not limited in this embodiment of the present application.
In one embodiment, the scheduling information of the first downlink data is used to instruct the second device to receive the second downlink data from the first device at the specified time domain resource location. The second device receiving second downlink data from the first device according to the scheduling information of the first downlink data may include: and the second equipment receives the second downlink data from the first equipment according to the time domain resource position specified by the scheduling information of the first downlink data.
The sending, by the first device, the second downlink data to the second device may include: and the first equipment sends the second downlink data to the second equipment according to the scheduling information of the first downlink data.
In the following, taking an example that the scheduling information of the first downlink data is carried in the control information of the first downlink data, an exemplary explanation is given for the second device receiving the second downlink data from the first device according to the scheduling information of the first downlink data.
Fig. 5 shows a schematic diagram of a communication procedure according to an embodiment of the present application. As shown in fig. 5, after the first device sends the selection signaling to the second device (e.g., the second device 1, and also e.g., the second device 2), the first device further sends first downlink data and control information of the first downlink data to the second device, where the control information of the first downlink data carries scheduling information of the first downlink data.
When the random number selected by the second device 1 is 0, the second device 1 enters a response state and transmits uplink data to the first device. After receiving the uplink data from the second device 1, the first device sends an acknowledgement signaling containing the uplink data to the second device 1, so that the second device 1 can be acknowledged. The confirmed second device 1 enters the confirmation state and reports its electronic product code, thereby completing the basic information inventory process of the second device 1. When the second device 1 that completes the inventory process receives the second downstream data from the first device, the inventory flag of the second device 1 will be set in reverse, and enter a ready state, ending the inventory process.
When the second device 2 that enters the arbitration state receives the second downlink data from the first device according to the scheduling information of the first downlink data, the second device 2 enters the response state in a case where the value in the slot counter corresponding to the second device 2 becomes 0, and repeats the same response procedure as the second device 1.
For a specific description of the communication procedure between the first device and the second device, reference may be made to the description in fig. 2, and no further description is given here.
Based on the above technical solution, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data. When there are a plurality of second devices, the plurality of second devices can all receive the second downlink data from the first device according to the scheduling information of the first downlink data. When the second downlink data sent by the first device to the plurality of second devices is multiple times, the plurality of second devices can all receive the second downlink data sent by the first device each time according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
Optionally, the second downlink data is downlink data received from the first device before the second device sends uplink data to the first device.
Illustratively, as shown in fig. 5, assuming that there are two second devices, respectively denoted as second device 1 and second device 2, when the second device 1 and second device 2 receive the first downlink data from the first device, the second device 1 determines that the value in its time slot counter is 0, and the second device 2 determines that the value in its time slot counter is 1, so that the second device 1 enters the response state and transmits the uplink data to the first device, and the second device 2 enters the arbitration state. When the second device 2 receives the second downlink data from the first device, the second device 2 determines that the value in the time slot counter of the second device becomes 0, so that the second device 2 enters a response state and sends uplink data to the first device, and the second downlink data is the downlink data received from the first device before the second device 2 sends the uplink data to the first device.
Optionally, before the first device sends the second downlink data, the first device determines a type of the first downlink data, and/or the first device determines an identifier of the first downlink data.
Optionally, before the second device receives the second downlink data, the second device determines the type of the first downlink data, and/or the second device determines the identifier of the first downlink data.
The type of the first downlink data may be any one of the following: multicast, broadcast or unicast.
The identifier of the first downlink data may be a Logical Channel Identifier (LCID).
In one possible manner, after receiving the first downlink data from the first device according to the scheduling information of the first downlink data, the second device may determine the type of the first downlink data by analyzing the first downlink data, and/or the second device may determine the identifier of the first downlink data by analyzing the first downlink data.
In another possible manner, after receiving the first downlink data from the first device according to the scheduling information of the first downlink data, the second device may determine the type of the first downlink data by receiving the indication information from the first device, and/or the second device may determine the identity of the first downlink data by receiving the indication information from the first device. The indication information may be carried in control information of the first downlink data.
In this way, after the second device determines the type of the first downlink data and/or after the second device determines the identifier of the first downlink data, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data, so that the time for the second device to determine the first downlink data is reduced, and further the efficiency of the second device to receive the second downlink data is improved.
Alternatively, the downstream data (e.g., the first downstream data and the second downstream data) may be a media access control (medium access control, MAC) element (CE), where the downstream data includes a MAC header field and the MAC header field includes LCID indication information.
The manner in which the second device determines the type of the second downlink data and/or the manner in which the second device determines the identifier of the second downlink data may refer to the foregoing description, which is not described herein.
Optionally, the type of the second downlink data is the same as the type of the first downlink data, and/or the identifier of the second downlink data is the same as the identifier of the first downlink data.
As shown in fig. 5, it is assumed that the first downlink data is a queryrep signaling sent by the first device to the second device (e.g., the second device 1, and also referred to as the second device 2) for the first time, and the second downlink data is a queryrep signaling sent by the first device to the second device again, where the type of the second downlink data is the same as the type of the first downlink data, and/or the identifier of the second downlink data is the same as the identifier of the first downlink data.
Taking the example that the scheduling information of the queryrep signaling is carried in the control information of the queryrep signaling, the first device may send the control information of the queryrep signaling to the second device when the queryrep signaling is sent to the second device for the first time, so that the second device may receive the queryrep signaling according to the scheduling information of the queryrep signaling. When the first device sends the queryrep signaling to the second device again, the second device may receive the queryrep signaling sent again by the first device according to the scheduling information of the queryrep signaling sent for the first time by the first device.
By the method, the first device does not need to send scheduling information of the queryrep signaling to the second device again, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
Optionally, the type of the second downlink data is different from the type of the first downlink data, and/or the identifier of the second downlink data is different from the identifier of the first downlink data, where the size of the transmission block of the second downlink data is the same as the size of the transmission block of the first downlink data.
As shown in fig. 5, it is assumed that the first downlink data is a query signaling sent by the first device to the second device (e.g., the second device 1, and also referred to as the second device 2) for the first time, the second downlink data is a query yrep signaling sent by the first device to the second device again, and the transmission block sizes of the query signaling and the query yrep signaling are the same, where the type of the second downlink data and the type of the first downlink data are different, and/or the identifier of the second downlink data and the identifier of the first downlink data are different.
Taking the example that the scheduling information of the query signaling is carried in the control information of the query signaling, the first device may send the control information of the query signaling to the second device when sending the query signaling to the second device for the first time, so that the second device may receive the query signaling according to the scheduling information of the query signaling. When the first device sends the queryrep signaling to the second device again, the second device may receive the queryrep signaling sent again by the first device according to the scheduling information of the query signaling sent for the first time by the first device.
By the method, the first device does not need to send scheduling information of the queryrep signaling to the second device again, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
Optionally, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
The synchronization signals may be different sequences of the synchronization signals, different lengths of the synchronization signals, different repetition times of the synchronization signals, or a value set of different spreading factors of the synchronization signals.
The modulation scheme and the channel coding rate may be indicated jointly, for example, the combination of the modulation scheme and the channel coding rate may be determined by an index, which may be a modulation coding scheme (modulation and coding scheme, MCS) index.
Illustratively, the number of repetitions in the scheduling information of the first downlink data is associated with the synchronization signal. Assuming that the synchronization signal has 3 coverage levels, which are respectively denoted as coverage level 0, coverage level 1 and coverage level 2, a value set of the repetition number can be determined according to the coverage level of the synchronization signal. For example, when the coverage level of the synchronization signal is coverage level 0, the value set of the repetition number is {1,2,4,8}; for another example, when the coverage level of the synchronization signal is coverage level 1, the value set of the repetition number is {4,8,16,32}; for another example, when the coverage level of the synchronization signal is coverage level 2, the value set of the repetition number is {16,32,64,128}.
Compared with the scheme that the number of repetitions is {1,2,4,8,16,32,64,128} and the downlink control information (such as the control information of the first downlink data) needs to use 3 bits to indicate the number of repetitions no matter which coverage level the synchronization signal is in, in this embodiment of the present application, the number of repetitions is determined according to the synchronization signal, and the downlink control information (such as the control information of the first downlink data) may use 2 bits to indicate the number of repetitions, so that signaling overhead when the number of repetitions is indicated by using the downlink control information can be reduced.
Alternatively, the scheduling information of the second downlink data may be carried in the first downlink data.
As shown in fig. 5, assuming that the first downlink data is a query signaling sent by the first device to the second device (e.g., the second device 1, and also, e.g., the second device 2), and the second downlink data is a query yrep signaling sent again by the first device to the second device, scheduling information of the query yrep signaling may be carried in the query signaling.
Optionally, before the second device receives the second downlink data from the first device, the second device receives indication information from the first device, where the indication information is used to instruct the second device to receive the second downlink data from the first device according to the scheduling information of the first downlink data.
The indication information may be carried in control information of the first downlink data, or the indication information may be carried in the first downlink data.
By the method, the second device can accurately receive the second downlink data from the first device, so that the resource consumption of the second device is reduced, and the efficiency of the second device for receiving the second downlink data is improved.
Optionally, the second device may receive the second downlink data from the first device according to the scheduling information of the first downlink data, predefined by the protocol.
Based on step 410, the second device obtains the scheduling information of the first downlink data from the first device, mainly in two possible ways.
In one possible manner, the second device receives the scheduling information of the first downlink data from the first device before the second device receives the second downlink data from the first device. For example, the second device receives control information of first downlink data from the first device, where the control information of the first downlink data carries scheduling information of the first downlink data.
Based on the technical scheme, the second device can determine the scheduling information of the first downlink data, so that the second downlink data from the first device can be received according to the scheduling information of the first downlink data. By the method, the first device can avoid sending the scheduling information of the second downlink data to the second device, so that the sending times of the scheduling information can be reduced, and the overhead when the first device sends the scheduling information is reduced.
In another possible manner, before the second device receives the second downlink data from the first device, the second device receives a synchronization signal from the first device, where the synchronization signal is used to indicate whether there is scheduling information of the first downlink data after the synchronization signal, and the second device determines the scheduling information of the first downlink data according to the synchronization signal.
Illustratively, the synchronization signal is used to indicate that there is no scheduling information for the first downlink data following the synchronization signal. The second device determining scheduling information of the first downlink data according to the synchronization signal may include: the synchronization signal comprises indication information, wherein the indication information is used for indicating scheduling information of the first downlink data; or, the synchronization signal includes indication information, where the indication information is used to instruct the second device to determine, according to the scheduling information of the first downlink data received before the synchronization signal, the scheduling information of the current first downlink data.
Fig. 6 shows a schematic diagram of yet another communication procedure provided in an embodiment of the present application. As shown in fig. 6, after receiving the first downlink data from the first device and the control information of the first downlink data from the first device, the second device receives the first downlink data from the first device again, and receives a synchronization signal from the first device, where the synchronization signal includes indication information, where the indication information is used to instruct the second device to determine the scheduling information of the first downlink data received again according to the scheduling information of the first downlink data received before the synchronization signal (where the scheduling information of the first downlink data is carried in the control information of the first downlink data). For example, assuming that the first downlink data received by the second device is the query1 signaling, the first downlink data received by the second device again is the query2 signaling, the second device receives a synchronization signal from the first device, where the synchronization signal includes indication information, where the indication information is used to instruct the second device to determine scheduling information of the query2 signaling according to the scheduling information of the query1 signaling.
As shown in fig. 6, after receiving the first downlink data from the first device, the second device receives the first downlink data from the first device again, and receives a synchronization signal from the first device, where the synchronization signal includes indication information, where the indication information is used to indicate scheduling information of the received first downlink data again.
Illustratively, the synchronization signal is used to indicate scheduling information for the first downlink data following the synchronization signal. The second device determining scheduling information of the first downlink data according to the synchronization signal may include: the second device receives the synchronization signal from the first device, and then receives the scheduling information of the first downlink data from the first device (the scheduling information of the first downlink data is carried in the control information of the first downlink data).
Fig. 7 shows a schematic diagram of yet another communication procedure provided in an embodiment of the present application. As shown in fig. 7, after receiving the first downlink data from the first device, the second device receives the first downlink data from the first device again, and receives a synchronization signal from the first device, where the synchronization signal is used to indicate that the synchronization signal is followed by scheduling information of the first downlink data. The second device receives scheduling information of first downlink data from the first device after the synchronization signal (the scheduling information of the first downlink data is carried in control information of the first downlink data). For example, assuming that the first downlink data received by the second device is the query1 signaling, the first downlink data received by the second device again is the query2 signaling, the second device receives a synchronization signal from the first device, where the synchronization signal is used to indicate that the synchronization signal is followed by scheduling information of the query2 signaling. The second device receives scheduling information of the query2 signaling from the first device after the synchronization signal (the scheduling information of the query2 signaling is carried in control information of the query2 signaling).
For a specific description of the communication procedure between the first device and the second device, reference may be made to the description in fig. 2, and no further description is given here.
Based on the technical scheme, the second device can determine the scheduling information of the first downlink data according to the synchronous signals, so that the first device can send the first downlink data to the second device at any time, the scheduling flexibility of the first device is improved, in addition, the first device and the second device can be guaranteed to understand consistently, and the communication reliability is improved.
Optionally, the modulation mode of the downlink data (such as the first downlink data and the second downlink data) may be any one of the following: OOK, multicarrier on-off keying (MC-OOK), double-sideband amplitude shift keying (double-sideband amplitude-shift keying, DSB-ASK), single-sideband amplitude shift keying (single-sideband amplitude-shift keying, SSB-ASK), phase-inversion amplitude shift keying (phase-reversal amplitude shift keying, PR-ASK), multiple amplitude shift keying (multiple amplitude-shift keying, MASK), frequency shift keying (frequency-shift keying, k), gaussian frequency shift keying (gauss frequency shift keying, GFSK), multiple frequency shift keying (multiple frequency-shift keying, MFSK), binary phase shift keying (binary phase shift keying, BPSK), quadrature phase shift keying (quadrature phase shift keying, QPSK), pulse amplitude modulation (Pulse amplitude modulation, PAM), pulse width modulation (Pulse-width modulation, PWM), pulse position modulation (Pulse position modulation, PPM), pulse density modulation (Pulse density modulation, PDM), and Pulse code modulation (Pulse-code modulation, PWM).
Alternatively, the second device may send the first capability information to the first device.
Accordingly, the first device may receive first capability information from the second device.
Wherein the first capability information may include at least one of: whether a downlink control channel is supported, whether channel coding is supported, the type of channel coding supported, whether a line code is supported, the type of line code supported, whether hybrid automatic repeat request acknowledgement (hybrid automatic repeat request acknowledgement, HARQ-ACK) feedback is supported.
Wherein, for the downlink control channel and/or the downlink data channel, the first capability information may include at least one of: whether channel coding is supported, the type of channel coding supported, whether line codes are supported, the type of line codes supported, and whether HARQ-ACK feedback is supported.
Optionally, at least one of the following in the first capability information may be associated with each other: whether a downlink control channel is supported, whether channel coding is supported, the type of channel coding supported, whether a line code is supported, the type of line code supported, and whether hybrid automatic repeat request acknowledgement feedback is supported.
In this way, when the plurality of pieces of associated content exist in the first capability information, one piece of content in the plurality of pieces of associated content can be sent when the second device sends the first capability information to the first device, so that the first device can know the plurality of pieces of content associated with the one piece of content, and further the overhead when the second device sends the first capability information to the first device can be reduced.
For example, assuming that whether the second device supports channel coding is associated with whether the second device supports downlink control channels, the first device may also learn whether the second device supports downlink control channels when the second device sends itself to the first device whether it supports channel coding. For example, when the second device sends self-supporting channel coding to the first device, the first device may also learn that the second device supports the downlink control channel; for another example, when the second device sends to the first device that the second device does not support channel coding, the first device may also learn that the second device does not support the downlink control channel.
For example, assuming that whether the second device supports HARQ-ACK feedback is associated with whether the second device supports downlink control channels, when the second device sends itself to the first device whether the second device supports HARQ-ACK feedback, the first device may also learn whether the second device supports downlink control channels. For example, when the second device sends self-supporting HARQ-ACK feedback to the first device, the first device may also learn that the second device supports the downlink control channel; for another example, when the second device sends feedback that does not support HARQ-ACK to the first device, the first device may also learn that the second device does not support the downlink control channel.
Alternatively, the second device may send the second capability information to the first device.
Accordingly, the first device may receive second capability information from the second device.
Wherein the second capability information may include at least one of: support downlink control channel, support channel coding, support line code, support HARQ-ACK feedback.
Wherein, for the downlink control channel and/or the downlink data channel, the second capability information may include at least one of: support channel coding, support line codes, support HARQ-ACK feedback.
It should be appreciated that when the second device does not include a certain item of content in the second capability information sent to the first device, the first device may learn that the second device does not have the certain item of content in the second capability information. For example, when the second capability information sent by the second device to the first device does not include that the second device supports the downlink control channel, the first device may learn that the second device does not support the downlink control channel; for another example, when the second capability information sent by the second device to the first device does not include that the second device supports channel coding, the first device may learn that the second device does not support channel coding; for another example, when the second capability information sent by the second device to the first device does not include the second device supporting the line code, the first device may learn that the second device does not support the line code; for another example, when the second device does not include the second device supporting HARQ-ACK feedback in the second capability information sent by the second device to the first device, the first device may learn that the second device does not support HARQ-ACK feedback.
Optionally, at least one of the following in the second capability information may be associated with each other: support downlink control channel, support channel coding, support line code, support HARQ-ACK feedback.
In this way, when the plurality of pieces of associated content exist in the second capability information, one piece of content in the plurality of pieces of associated content can be sent when the second capability information is sent to the first device by the second device, so that the first device can know the plurality of pieces of content associated with the one piece of content, and further the overhead when the second device sends the second capability information to the first device can be reduced.
For example, assuming that the second device supports channel coding in association with the second device supporting the downlink control channel, the first device may also learn that the second device supports the downlink control channel when the second device transmits its own supported channel coding to the first device.
For example, assuming that the second device supports HARQ-ACK feedback is associated with the second device supporting the downlink control channel, the first device may also learn that the second device supports the downlink control channel when the second device sends itself to the first device supporting HARQ-ACK feedback.
Alternatively, the first device may send the first configuration information to the second device.
Accordingly, the second device may receive the first configuration information from the first device.
Wherein the first configuration information may include at least one of: whether a downlink control channel is enabled, whether channel coding is enabled, the type of channel coding enabled, whether line code is enabled, the type of line code enabled, and whether HARQ-ACK feedback is enabled.
Wherein, for the downlink control channel and/or the downlink data channel, the capability information may include at least one of: whether channel coding is enabled, the type of channel coding enabled, whether line code is enabled, the type of line code enabled, and whether HARQ-ACK feedback is enabled.
Optionally, at least one of the following in the first configuration information may be associated with each other: whether a downlink control channel is enabled, whether channel coding is enabled, the type of channel coding enabled, whether line code is enabled, the type of line code enabled, and whether HARQ-ACK feedback is enabled.
In this way, when the first configuration information includes a plurality of pieces of associated content, one piece of content of the plurality of pieces of associated content can be sent when the first device sends the first configuration information to the second device, so that the second device can learn the plurality of pieces of content associated with the one piece of content, and further, the overhead when the first device sends the first configuration information to the second device can be reduced.
For example, assuming that whether the first device enables channel coding is associated with whether the first device enables a downlink control channel, the second device may also learn whether the first device enables the downlink control channel when the first device transmits itself to the second device whether channel coding is enabled. For example, when the first device sends the self-enabled channel code to the second device, the second device may also learn that the first device enables the downlink control channel; for another example, when the first device transmits to the second device that the first device does not enable the channel coding, the second device may also learn that the first device does not enable the downlink control channel.
For example, assuming that whether the first device enables HARQ-ACK feedback is associated with whether the first device enables the downlink control channel, the second device may also learn whether the first device enables the downlink control channel when the first device sends itself whether HARQ-ACK feedback to the second device. For example, when the first device sends self-enabled HARQ-ACK feedback to the second device, the second device may also learn that the first device enables the downlink control channel; for another example, when the first device sends the feedback that does not enable HARQ-ACK to the second device, the second device may also learn that the first device does not enable the downlink control channel.
Alternatively, the first device may send the second configuration information to the second device.
Accordingly, the second device may receive second configuration information from the first device.
Wherein the second configuration information may include at least one of: enabling downlink control channels, enabling channel coding, enabling line codes, enabling HARQ-ACK feedback.
Wherein, for the downlink control channel and/or the downlink data channel, the second configuration information may include at least one of: enabling channel coding, enabling line codes, enabling HARQ-ACK feedback.
It should be appreciated that when the second configuration information sent by the first device to the second device does not include a certain item of content, the second device may learn that the first device does not have the item of content in the second configuration information. For example, when the second configuration information sent by the first device to the second device does not include the self-enabled downlink control channel, the second device may learn that the first device does not enable the downlink control channel; for another example, when the second configuration information sent by the first device to the second device does not include the self-enabled channel coding, the second device may learn that the first device does not enable the channel coding; for another example, when the second configuration information sent by the first device to the second device does not include the self-enabled line code, the second device may learn that the first device does not enable the line code; for another example, when the second configuration information sent by the first device to the second device does not include self-enabled HARQ-ACK feedback, the second device may learn that the first device does not enable HARQ-ACK feedback.
Optionally, at least one of the following in the second configuration information may be associated with each other: enabling downlink control channels, enabling channel coding, enabling line codes, enabling HARQ-ACK feedback.
In this way, when the plurality of pieces of associated content exist in the second configuration information, one piece of content in the plurality of pieces of associated content can be sent when the first device sends the second configuration information to the second device, so that the second device can know the plurality of pieces of content associated with the one piece of content, and further the overhead when the first device sends the second configuration information to the second device can be reduced.
For example, assuming that the first device-enabled channel code is associated with a first device-enabled downlink control channel, the second device may also learn of the first device-enabled downlink control channel when the first device transmits its own-enabled channel code to the second device.
For example, assuming that the first device enabled HARQ-ACK feedback is associated with the first device enabled downlink control channel, the second device may also learn that the first device is enabled downlink control channel when the first device sends its own enabled HARQ-ACK feedback to the second device.
It should be understood that "enable" in embodiments of the present application may also be expressed as "active".
Optionally, the second device may send third capability information to the first device.
Accordingly, the first device may receive third capability information from the second device.
Wherein the third capability information may include at least one of: whether energy harvesting is supported, whether low power receivers are supported, and whether backscatter communications are supported.
In one possible approach, the third capability information includes the second device supporting energy harvesting.
Wherein the second device supporting energy harvesting may refer to the second device supporting the autonomous harvesting of energy from the environment and may convert the energy into electrical energy. Wherein the source of energy may include at least one of: light, radio waves, temperature differences, vibrations, movements, salinity gradients, wind, water currents.
It will be appreciated that the benefit of energy harvesting is to replace the battery to power the device or to supplement the battery energy, thereby extending the device lifetime. The second device may provide energy generated by energy harvesting to its own signal processing or data storage circuitry to maintain normal operation.
In another possible manner, the third capability information includes that the second device supports a low power consumption receiver.
It should be appreciated that the low power receiver may avoid using larger power consumption rf modules, such as high linearity mixers, voltage controlled oscillators that provide accurate local oscillator signals, etc., and thus may achieve lower power consumption levels
Wherein the second device supporting the low power consumption receiver may mean that the second device supports receiving signals in a non-coherent receiving manner.
The signal may be, for example, a signal from a first device.
The incoherent receiving mode may be envelope detection, differential demodulation, or the like, for example.
For example, when the incoherent receiving mode is envelope detection, the envelope detection may obtain an envelope or amplitude line of the low-frequency original signal after half-wave or full-wave rectification of the received high-frequency or intermediate-frequency signal.
In this way, the second device can receive the signal using the reception means of envelope detection, thereby obtaining the envelope of the original signal. After the second device digitally samples the envelope of the original signal, it may be compared to an amplitude or energy threshold set by the second device to determine whether the received signal is a 1 or 0. It should be appreciated that the second device may also determine whether the received signal is a 1 or 0 according to other manners, which embodiments of the present application are not particularly limited.
Wherein, the second device supports the low power consumption receiver may mean that the second device is provided with the low power consumption receiver, or that the second device is provided with both the low power consumption receiver and the legacy receiver.
It should be appreciated that unlike conventional receivers and low power consumption receivers, the receiver architecture of conventional receivers may be superheterodyne, zero intermediate frequency, or low intermediate frequency, and may support coherent reception. The conventional receiver needs to adopt a plurality of high-performance and high-precision module circuits to ensure the receiving performance of the receiver, such as a low-noise amplifier with high gain and high linearity, a mixer with high linearity, a voltage-controlled oscillator capable of providing an accurate local oscillation signal, and the like, and the module circuits have higher power consumption, and the power consumption of the conventional receiver is higher than that of the low-power receiver within a certain period of time.
It will also be appreciated that when the second device is provided with both a low power receiver and a legacy receiver, the second device may achieve a power saving effect by turning off the legacy receiver and turning on the low power receiver.
It will also be appreciated that when the second device is provided with both a low power receiver and a legacy receiver, the second device may receive a wake-up signal via the low power receiver, triggering the legacy receiver on via the wake-up signal. Wherein the wake-up signal may be transmitted by the first device.
In another possible manner, the third capability information includes that the second device supports backscatter communications.
Wherein the second device supporting backscatter communications may refer to the second device supporting sending information to the first device without an actively transmitting radio frequency link; alternatively, the second device supporting backscatter communication may mean that the second device supports sending information to the first device if it has an actively transmitting radio frequency link itself but does not need to be turned on, i.e. the second device relies primarily on an exciting device outside the first device or a continuous carrier transmitted by the first device for modulation.
For example, the second device may reflect a portion or all of the incoming carrier wave by adjusting the impedance of the antenna of the second device; for another example, the second device may not reflect the incoming carrier wave by adjusting the impedance of the antenna of the second device; as another example, the second device may absorb energy of the incoming carrier wave.
In this way, the second device can modulate digital information onto an incoming carrier wave by adjusting the impedance of its own antenna and send it to the first device.
Optionally, the maximum bandwidth supported by the second device is limited.
In one possible way, the maximum upstream bandwidth supported by the second device does not exceed X1.
Illustratively, X1 may be a specific value. For example, X1 may be 20MHz, or X1 may be 5MHz, or X1 may be 3MHz, or X1 may be 1.4MHz, or X1 may be 1MHz, or X1 may be 720kHz, or X1 may be 540kHz, or X1 may be 360kHz, or X1 may be 180kHz.
Illustratively, X1 may be a bandwidth occupied by K1 resource blocks, where K1 is a positive integer. For example, K1 may be a positive integer less than or equal to 11, or K1 may be a positive integer less than or equal to 25, or K1 may be a positive integer less than or equal to 51, or K1 may be a positive integer less than or equal to 106.
In another possible way, the maximum downlink bandwidth supported by the second device does not exceed Y1.
Illustratively, Y1 may be a specific value. For example, Y1 may be 20MHz, or Y1 may be 5MHz, or Y1 may be 3MHz, or Y1 may be 1.4MHz, or Y1 may be 1MHz, or Y1 may be 720kHz, or Y1 may be 540kHz, or Y1 may be 360kHz, or Y1 may be 180kHz.
Illustratively, Y1 may be a bandwidth occupied by K2 resource blocks, where K2 is a positive integer. For example, K2 may be a positive integer less than or equal to 11, or K2 may be a positive integer less than or equal to 25, or K2 may be a positive integer less than or equal to 51, or K2 may be a positive integer less than or equal to 106.
Optionally, the maximum uplink bandwidth supported by the second device is less than or equal to the maximum downlink bandwidth supported by the second device.
Optionally, the number of transmit and/or receive antennas supported by the second device is limited.
In one possible way, the number of receive antennas supported by the second device does not exceed X2.
Illustratively, X2 may be a specific value. For example, X2 may be 1, or X2 may be 2, or X2 may be 4.
In another possible way, the number of branches of the receiving antenna supported by the second device does not exceed X3.
Illustratively, X3 may be a specific value. For example, X3 may be 1, or X3 may be 2, or X3 may be 4.
In another possible way, the number of receive antennas supported by the second device does not exceed Y2.
Illustratively, Y2 may be a specific value. For example, Y2 may be 1, or Y2 may be 2, or Y2 may be 4.
In another possible way, the number of branches of the transmit antennas supported by the second device does not exceed Y3.
Illustratively, Y3 may be a specific value. For example, Y3 may be 1, or Y3 may be 2, or Y3 may be 4.
Optionally, the number of transmit antennas supported by the second device is greater than or equal to the number of receive antennas supported by the second device.
Optionally, the number of branches of the transmitting antenna supported by the second device is greater than or equal to the number of branches of the receiving antenna supported by the second device.
It should be understood that the "number of branches of the receiving antenna" may be expressed as "number of radio frequency channels of the receiving antenna" or "number of radio frequency chains of the receiving antenna". The "number of branches of the transmitting antenna" may be expressed as "number of radio frequency channels of the transmitting antenna" or "number of radio frequency chains of the transmitting antenna".
It should be noted that the second device may not receive downlink and transmit uplink simultaneously on the serving cell with the paired spectrum.
It will be appreciated that the examples in fig. 4-7 in the embodiments of the present application are merely for convenience of understanding the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from the examples of fig. 4-7 that various equivalent modifications or variations may be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application. For example, "the transmission time of the second downlink data is located after the transmission time of the first downlink data" in fig. 4 may be replaced with "the time domain resource of the second downlink data is located after the time domain resource of the first downlink data".
It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features, or may, in some circumstances, be combined with other features, without limitation.
It is also to be understood that the aspects of the embodiments of the present application may be used in any reasonable combination, and that the explanation or illustration of the terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.
It should be further understood that the magnitude of the various numerical numbers in the embodiments of the present application do not imply any order of execution, but are merely convenient to distinguish between the embodiments, and should not be construed as limiting the implementation of the embodiments of the present application.
It is also understood that in this application, "at least one" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
It may be further understood that, in the embodiments of the present application, some information names, such as scheduling information of the first downlink data, scheduling information of the second downlink data, indication information, etc., are referred to, and it should be understood that the names do not limit the protection scope of the embodiments of the present application.
It should also be understood that in the foregoing embodiments of the method and operations implemented by a device (such as a network device, and also such as a terminal device), the method and operations may also be implemented by component parts of the device (e.g., a chip or a circuit).
Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for performing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.
The method for data transmission provided in the embodiment of the present application is described in detail above with reference to fig. 4 to 7. The following describes in detail the communication device provided in the embodiment of the present application with reference to fig. 8 to 10.
Fig. 8 is a schematic block diagram of a communication device provided in an embodiment of the present application. The apparatus 800 comprises a transceiver unit 810, which transceiver unit 810 may be adapted to implement the respective communication functions. The transceiver unit 810 may also be referred to as a communication interface or a communication unit.
Optionally, the apparatus 800 may further include an acquiring unit 820, where the acquiring unit 820 may be configured to implement a corresponding acquiring function, such as acquiring the scheduling information of the first downlink data from the first device.
Optionally, the apparatus 800 may further comprise a processing unit 830, where the processing unit 830 may be configured to implement a corresponding processing function, such as determining the type of the first downlink data.
Optionally, the apparatus 800 further includes a storage unit, where the storage unit may be configured to store instructions and/or data, and the processing unit 830 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the first device or the second device in the foregoing method embodiments.
The apparatus 800 may be configured to perform the actions performed by the first device or the second device in the above method embodiments, where the apparatus 800 may be a component of the first device or a component of the second device, the transceiver unit 810 is configured to perform operations related to the transceiver of the first device or the second device in the above method embodiments, the acquiring unit 820 is configured to perform operations related to the acquisition of the first device or the second device in the above method embodiments, and the processing unit 830 is configured to perform operations related to the processing of the first device or the second device in the above method embodiments.
As a design, the apparatus 800 is configured to perform the actions performed by the second device in the method embodiments above.
A possible implementation manner, an obtaining unit 820, configured to obtain scheduling information of first downlink data from the first device; the transceiver 810 is configured to receive second downlink data from the first device according to the scheduling information of the first downlink data, where a transmission time of the second downlink data is located after a transmission time of the first downlink data.
Optionally, the second downlink data is downlink data received from the first device before the apparatus 800 sends uplink data to the first device.
Optionally, the apparatus 800 further comprises a processing unit 830, the processing unit 830 being configured to determine a type of the first downlink data, and/or the processing unit 830 being configured to determine an identity of the first downlink data.
Optionally, the type of the first downlink data is any one of the following: multicast, broadcast or unicast.
Optionally, the identification of the first downlink data is a logical channel identification.
Optionally, the transceiver 810 is configured to receive scheduling information of the first downlink data from the first device.
Optionally, the apparatus 800 further includes a processing unit 830, a transceiver unit 810, configured to receive a synchronization signal from the first device, where the synchronization signal is used to indicate whether there is scheduling information of the first downlink data after the synchronization signal; the processing unit 830 is configured to determine scheduling information of the first downlink data according to the synchronization signal.
Optionally, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
Optionally, the processing unit 830 is configured to receive indication information from the first device, where the indication information is used to instruct the apparatus 800 to receive second downlink data from the first device according to scheduling information of the first downlink data.
The apparatus 800 may implement steps or processes corresponding to those performed by the second device in the method embodiment according to the embodiment of the present application, and the apparatus 800 may include a unit for performing the method performed by the second device in the embodiment shown in any of fig. 4 to 7.
As another design, the apparatus 800 is configured to perform the actions performed by the first device in the method embodiments above.
In a possible implementation manner, the processing unit 830 is configured to determine scheduling information of the first downlink data; the transceiver 810 is configured to send second downlink data to the second device according to the scheduling information of the first downlink data, where a sending time of the second downlink data is located after a sending time of the first downlink data.
Optionally, the processing unit 830 is configured to determine a type of the first downlink data, and/or the processing unit 830 is configured to determine an identification of the first downlink data.
Optionally, the type of the first downlink data is any one of the following: multicast, broadcast or unicast.
Optionally, the identification of the first downlink data is a logical channel identification.
Optionally, the transceiver 810 is configured to send scheduling information of the first downlink data to the second device.
Optionally, the transceiver 810 is configured to send a synchronization signal to the second device, where the synchronization signal is used to indicate whether the synchronization signal is followed by scheduling information of the first downlink data.
Optionally, at least one of the following in the scheduling information of the first downlink data is associated with a synchronization signal: repetition number, modulation scheme, channel coding rate or line code parameters.
Optionally, the transceiver 810 is configured to send, to the second device, indication information, where the indication information is used to instruct the second device to receive, according to the scheduling information of the first downlink data, the second downlink data from the apparatus.
The apparatus 800 may implement steps or processes performed corresponding to the first device in the method embodiments according to the embodiments of the present application. The apparatus 800 may include means for performing the method performed by the first device in any of the embodiments shown in fig. 4-7.
It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.
It should also be appreciated that the apparatus 800 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the apparatus 800 may be specifically configured as the first device or the second device in the foregoing embodiments, and may be used to perform each flow and/or step corresponding to the first device or the second device in the foregoing method embodiments, which are not repeated herein.
The apparatus 800 of each of the above aspects has a function of implementing the corresponding step performed by the first device or the second device in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), other units, such as an acquiring unit, may be replaced by an acquirer, and the processing unit may be replaced by a processor, to perform the transceiver operation, the acquiring operation, and the related processing operations, respectively, in the various method embodiments.
The transceiver 810 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), the acquiring unit may be an acquiring circuit, and the processing unit may be a processing circuit.
It should be noted that the apparatus in fig. 8 may be the device in the foregoing embodiment, or may be a chip or a chip system, for example: system on chip (SoC). The receiving and transmitting unit can be an input and output circuit and a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.
As shown in fig. 9, another communication device 900 is provided in an embodiment of the present application. The apparatus 900 comprises a processor 910, the processor 910 being coupled to a memory 920, the memory 920 being for storing computer programs or instructions and/or data, the processor 910 being for executing the computer programs or instructions stored by the memory 920 or for reading the data stored by the memory 920 for performing the methods in the method embodiments above.
Optionally, the processor 910 is one or more.
Optionally, the memory 920 is one or more.
Alternatively, the memory 920 may be integrated with the processor 910 or provided separately.
Optionally, as shown in fig. 9, the apparatus 900 further comprises a transceiver 930, where the transceiver 930 is used for receiving and/or transmitting signals. For example, the processor 910 is configured to control the transceiver 930 to receive and/or transmit signals.
Alternatively, the apparatus 900 is configured to implement the operations performed by the first device or the second device in the above method embodiments.
For example, the processor 910 is configured to execute a computer program or instructions stored in the memory 920 to implement the relevant operations of the first device in the above method embodiments. For example, the method performed by the first device in any of the embodiments shown in fig. 4-7.
It should be appreciated that the processors referred to in the embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should also be understood that the memories mentioned in the embodiments of the present application may be volatile memories and/or nonvolatile memories. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).
It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.
It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Referring to fig. 10, an embodiment of the present application provides a chip system 1000. The system-on-chip 1000 (or may also be referred to as a processing system) includes logic 1010 and an input/output interface 1020.
Logic 1010 may be a processing circuit in system-on-chip 1000. Logic 1010 may be coupled to the memory unit to invoke instructions in the memory unit so that system-on-chip 1000 may implement the methods and functions of embodiments of the present application. The input/output interface 1020 may be an input/output circuit in the chip system 1000, outputting information processed by the chip system 1000, or inputting data or signaling information to be processed into the chip system 1000 for processing.
As an option, the chip system 1000 is configured to implement the operations performed by the first device or the second device in the above method embodiments.
For example, the logic 1010 is configured to implement the operations related to the processing performed by the first device in the above method embodiment, such as the operations related to the processing performed by the first device in the embodiment shown in any one of fig. 4 to 7; the input/output interface 1020 is configured to implement the operations related to transmission and/or reception performed by the first device in the above method embodiments, such as the operations related to transmission and/or reception performed by the first device in the embodiments shown in any one of fig. 4 to 7.
The present application also provides a computer-readable storage medium having stored thereon computer instructions for implementing the method performed by the first device or the second device in the above-described method embodiments.
For example, the computer program, when executed by a computer, enables the computer to implement the method performed by the first device in the above-described method embodiments.
Embodiments of the present application also provide a computer program product containing instructions that, when executed by a computer, implement a method performed by a first device or a second device in the above method embodiments.
The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable media include, but are not limited to, U disk, removable hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program code.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.