A resource reservation method and related devices

Abstract

Embodiments of this application disclose a resource reservation method and related devices. The method includes: A network device generates a resource reservation request message (RRQ). The RRQ includes a first resource reservation request message (RRQ1) and N second resource reservation request messages (RRQ2). The RRQ1 includes information indicating that the time for the network device to occupy a target channel is a first duration. The N RRQ2s correspond to the N user equipment (UE) one by one, and are respectively used to indicate that the N UEs transmit data with the network device during the first duration, where N≥1. The network device sends the RRQ. The RRQ1 is scrambled with a first common identifier known to the N UEs, and the N RRQ2s are respectively scrambled with the unique identifier of the corresponding UE. Using the embodiments of this application can achieve the purpose of resource reservation, thereby improving the success rate of data transmission.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to a resource reservation method and related devices. Background Art

[0002] With the rapid increase in wireless data traffic, the licensed spectrum has been difficult to meet the spectrum requirements for communication. Therefore, technologies for transmitting data using unlicensed spectrum resources have emerged, such as license assisted access (LAA) technology, enhanced license assisted access (eLAA) technology, and new radio-unlicense (NR-U) technology.

[0003] However, the unlicensed frequency bands used in the above technologies are shared frequency bands, and various communication systems may operate on these frequency bands, resulting in severe interference between different systems or even devices within the same system, thereby causing low spectrum utilization. To avoid or mitigate this problem, international organizations stipulate that devices using unlicensed frequency bands must follow the listen-before-talk mechanism. Based on the basic principle of the listen-before-talk mechanism, specific listen-before-talk implementation schemes have evolved in each communication system. In the Wireless Fidelity (WiFi) system, the listen-before-talk mechanism is also known as the carrier sense mechanism.

[0004] Carrier sensing includes physical carrier sensing and virtual carrier sensing. Virtual carrier sensing is also known as channel reservation or resource reservation. Virtual carrier sensing is mainly used to avoid interference caused by hidden nodes. As Figure 1 shown, when device 1 transmits data to device 2, device 3 may not be able to sense the transmission of device 1 due to its long distance from device 1, and thus may transmit simultaneously with device 1 (for example, transmit data to device 2), which causes interference to the reception of device 2. Therefore, device 1 and device 3 are hidden nodes to each other. The so-called virtual carrier sensing means that before device 1 transmits data to device 2, it first exchanges resource reservation request / response messages with device 2, and the resource reservation request / response messages carry the expected duration of the current transmission. After device 3 hears the resource reservation response message sent by device 2, it will not attempt to transmit data within the expected duration carried therein, thereby avoiding interference to the reception of device 2.

[0005] In the existing resource reservation technology of the virtual carrier sensing mechanism in the WiFi system, the access point (AP) sends a broadcast frame, multiple user-request to send (MU-RTS), and multiple target stations (STAs) reply with a resource reservation response message (clear to send, CTS) after receiving the MU-RTS, so as to achieve the function of resource reservation. Specifically, when the AP detects that the channel is idle and maintains the duration of the distributed coordination function inter-frame interval, the AP randomly selects a value within a predetermined range to set a backoff timer. If the channel remains idle until the backoff timer counts down to 0, the AP sends a resource reservation request MU-RTS frame. After the target STA receives the MU-RTS, it replies with a CTS frame. After the AP receives the CTS frame, it sends a data frame. After the AP receives the data frame, it sends an acknowledgment message. Since both the MU-RTS and CTS frames include a Duration field for the remaining time of the current transmission, a third-party device can set its own network allocation vector (NAV) according to the Duration field after receiving the MU-RTS / CTS. Before the NAV counts down to 0, the third-party device will not compete for the channel, thus avoiding interference caused by the third-party device sending data to the transmission between the sending device and the receiving device.

[0006] However, the MU-RTS not only carries the remaining time Duration of the current transmission process, but also includes the identifier of each target STA and on which or which 20MHz channels each target STA needs to reply with a CTS; this results in a longer frame length of the MU-RTS, more time-frequency resources occupied, affecting the probability of the target STA correctly receiving the MU-RTS, thus the transmission reliability is lower, and the resource reservation process may not be successfully completed. Summary of the Invention

[0007] The present invention provides a resource reservation method and related devices, which can achieve the purpose of resource reservation, thereby improving the success rate of data transmission.

[0008] In a first aspect, an embodiment of the present invention provides a resource reservation method, which includes: a network device generates a resource reservation request message RRQ, the RRQ includes a first resource reservation request message RRQ1 and N second resource reservation request messages RRQ2, the RRQ1 includes first duration information, the first duration information is used to indicate that the network device occupies the target channel for a first duration, the N RRQ2 are respectively used to request N user devices UE to transmit data with the network device within the first duration, the N RRQ2 correspond to the N UEs one by one, and N is an integer greater than or equal to 1;

[0009] The network device sends the RRQ, where the RRQ1 is scrambled with a first common identifier, and the N RRQ2s are respectively scrambled with unique identifiers of their corresponding UEs, and the first common identifier is an identifier known to at least one third-party device and the N UEs.

[0010] In summary, in the prior art, the identification information of all target devices is directly carried in the resource reservation request message (or resource reservation request frame), resulting in an overly long frame length of the resource reservation request frame, thereby reducing the success rate of resource reservation request frame transmission. Compared with the prior art, in the embodiment of the present application, the resource reservation request frame is divided into 1 RRQ1 and multiple RRQ2s. The RRQ1 is sent to a third-party device and does not carry the identification of the target device for subsequent data transmission, making the length of the RRQ1 much smaller than the resource reservation request frame (such as MU-RTS) in the prior art, greatly increasing the probability that the RRQ1 is correctly received by the third-party device; at the same time, each RRQ2 corresponds to a target device, and each RRQ2 only carries the identification of the target device corresponding to it, making the length of the RRQ2 much smaller than the resource reservation request frame (such as MU-RTS) in the prior art, greatly increasing the probability that the RRQ2 is correctly received by the corresponding target device, achieving the purpose of resource reservation, and thus improving the success rate of data transmission.

[0011] In a possible design, the RRQ1 further includes a cell identifier cell ID.

[0012] In the embodiment of the present application, the cell identifier cell ID is used to identify the cell where the UE that will subsequently transmit data with the network device is located. If the UE that receives the RRQ1 determines that the cell where the UE is located is not the cell identified by the cell ID based on the cell ID, then the UE will not search for the second resource reservation request RRQ2 in its specific search space. At the same time, the UE configures the network allocation vector NAV according to the time information included in the RRQ1, and before the NAV expires to 0, the UE will not compete for the target channel, so that while reducing the operating burden of the processor of the UE, interference to data transmission on the target channel is avoided.

[0013] In a possible design, the RRQ1 is transmitted in the common search space CSS, and the N RRQ2s are respectively transmitted in the specific search spaces USS of the corresponding UEs among the N UEs, and the CSS is a search space known to at least one third-party device and the N UEs.

[0014] In the embodiment of the present application, the first resource reservation request RRQ1 is transmitted in the common search space so that third-party devices other than the target device for transmitting data with the network device can also receive the RRQ1, enabling these third-party devices to set resource reservation timers according to the time information in the RRQ1 to achieve the purpose of reserving resources; while the N RRQ2s are respectively transmitted in the specific search spaces of their respective UEs to reduce interference with each other, enabling each UE to correctly receive its corresponding RRQ2, thereby preparing for subsequent data transmission and improving the success rate of data transmission.

[0015] In a possible design, the first general identifier is a predefined radio network temporary identifier RNTI; or, the first general identifier is the RNTI that the network device notifies the at least one third-party device and the N UEs through radio resource control RRC signaling or system information; or, the first general identifier is an RNTI calculated according to first information; the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

[0016] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE corresponding to the RRQ2 needs to send a resource reservation response message RRS to the network device.

[0017] In the embodiment of the present application, if the resource reservation request carries indication information that the UE corresponding to the RRQ2 needs to reply with a resource reservation response message, but the UE does not reply, then the network device will not schedule data transmission for this UE, avoiding waste of resources; if the resource reservation request carries indication information that the UE corresponding to the RRQ2 does not need to reply with a resource reservation response message, it indicates that the network device will directly schedule data transmission for this UE subsequently, saving the time for replying with the resource reservation response message, thereby reducing the time of the entire data transmission process and improving the efficiency of data transmission.

[0018] In a possible design, after the network device sends the RRQ, it further includes: the network device receives RRSs sent by M UEs among the N UEs, each RRS in the M RRSs includes a first resource reservation response message RRS1 and a second resource reservation response message RRS2, the RRS1 contains second duration information, the second duration information is used to indicate that the M UEs occupy the target channel for a second duration, and the RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 will transmit data with the network device within the second duration, where M is a positive integer less than or equal to N.

[0019] In the embodiments of the present application, the RRS1 carries time information for a third-party device to reserve a timer for device resources according to the time information after receiving the RRS1, so as to achieve the purpose of resource reservation; the RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 will transmit data to the network device within the time period included in the above time information, which can improve the success rate of data transmission.

[0020] In a possible design, the M RRS1s included in the M RRSs are all transmitted on the same time-frequency resource.

[0021] In the embodiments of the present application, since the M RRS1s include the same content, transmitting on the same time-frequency resource will not cause interference, and can reduce the occupation of time-frequency resources and save overhead.

[0022] In a possible design, the M RRS2s included in the M RRSs are respectively transmitted on different time-frequency resources.

[0023] In the embodiments of the present application, the M RRS2s are transmitted in different time-frequency resources so that the network device can distinguish which UE replied the RRS2 according to the time-frequency resource where the RRS2 is located when receiving the RRS2, and since the content included in the RRS2 replied by each UE is different, transmitting on different time-frequency resources also avoids interference between each other.

[0024] In a possible design, the RRS1 is scrambled with a second common identifier, and the M RRS2s are respectively scrambled with the unique identifiers corresponding to the M UEs, and the second common identifier is known to the M UEs and the at least one third-party device.

[0025] In a possible design, the second common identifier is a predefined RNTI; or, the second common identifier is the RNTI notified by the network device to the at least one third-party device and the M UEs; or, the second common identifier is an RNTI calculated according to second information; the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0026] In the above embodiments, the RRS1 is scrambled with a common identifier, so that the third-party device can receive the RRS1, avoiding transmission interference caused by the third-party device.

[0027] In a possible design, the RRQ1 includes indication information for indicating the time-frequency resource and / or transmission parameters used by the N UEs to transmit the RRS1;

[0028] Alternatively, the frequency-domain resources used by the N UEs to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0029] In a possible design, the N RRQ2s respectively include indication information for indicating the time-frequency resources and / or transmission parameters used by the corresponding UEs among the N UEs to transmit the RRS2 respectively.

[0030] Alternatively, the frequency-domain resources used by each of the N UEs to transmit its respective RRS2 are the same as the frequency-domain resources used by the RRQ2 corresponding to the UE among the N RRQ2s transmitted by the network device.

[0031] Alternatively, the RRQ1 includes indication information for indicating the transmission parameters used by the N UEs to transmit the N RRS2s respectively.

[0032] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval, where the first time interval is the time interval between the time when the N UEs receive the RRQ1 and the time when the N UEs finish transmitting the RRS1.

[0033] In a possible design, the N RRQ2s include one or more special RRQ2s. The UEs corresponding to the special RRQ2s do not need to reply to the network device with a resource reservation response message RRS. The special RRQ2s include indication information for indicating the transmission resources and / or transmission parameters for the UEs corresponding to the RRQ2s to transmit data with the network device.

[0034] In the embodiments of this application, when it is not necessary for the UE to reply with a resource reservation response, the network device can indicate the scheduling information for the subsequent data transmission of the UE in the RRQ2 corresponding to the UE, without additionally sending a dedicated data scheduling instruction to the UE, which can save the time of the entire data transmission process and improve the data transmission efficiency as a whole.

[0035] In a possible design, the network device receiving the RRS sent by M UEs among the N UEs includes:

[0036] When the time domain resource used by the network device to send the RRQ is time slot n, the network device receives RRSs sent by M UEs among the N UEs in time slot n + k, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0037] The embodiments of this application are mainly used to indicate the time domain resources for the user equipment UE to send RRSs.

[0038] In a second aspect, an embodiment of the present invention provides a resource reservation method, which includes: a user equipment UE receives a resource reservation request message RRQ sent by a network device, the RRQ includes a first resource reservation request message RRQ1 and a second resource reservation request message RRQ2, the RRQ1 includes first duration information, and the first duration information is used to indicate that the time for the network device to occupy a target channel is the first duration, the RRQ2 is used to request the UE to transmit data with the network device within the first duration, the RRQ1 is scrambled with a first common identifier, the RRQ2 is scrambled with a unique identifier corresponding to the UE, and the first common identifier is an identifier known to the UE and at least one third - party device.

[0039] In a possible design, the RRQ1 further includes a cell ID.

[0040] In a possible design, the RRQ1 is transmitted in a common search space CSS, and the RRQ2 is transmitted in a UE - specific search space USS, and the CSS is a search space known to the at least one third - party device and the UE.

[0041] In a possible design, the first common identifier is a predefined radio network temporary identifier RNTI; or the first common identifier is an RNTI notified by the network device to the at least one third - party device and the UE through radio resource control RRC signaling or system message; or the first common identifier is an RNTI calculated according to first information; the first information includes one or more of a cell ID, a system frame number, and a time slot number of the RRQ1.

[0042] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE needs to send a resource reservation response message RRS to the network device.

[0043] In a possible design, after the user equipment UE receives the RRQ sent by the network device, it further includes:

[0044] The UE generates an RRS according to the RRQ. The RRS includes RRS1 and RRS2. The RRS1 contains second duration information, and the second duration information is used to indicate that the UE occupies the target channel for a second duration. The RRS2 is used to confirm to the network device that the UE will transmit data to the network device within the second duration;

[0045] The UE sends the RRS to the network device.

[0046] In a possible design, the RRS1 is scrambled with a second common identifier, and the RRS2 is scrambled with a specific identifier corresponding to the UE. The second common identifier is known to the M UEs and the at least one third-party device.

[0047] In a possible design, the second common identifier is a predefined RNTI; or, the second common identifier is the RNTI notified by the network device to the at least one third-party device and the UE; or, the second common identifier is an RNTI calculated according to second information; the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0048] In a possible design, the RRQ1 includes indication information for indicating the time-frequency resources and / or transmission parameters used by the UE to transmit the RRS1;

[0049] Alternatively, the frequency-domain resources used by the UE to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0050] In a possible design, the RRQ2 includes indication information for indicating the time-frequency resources and / or transmission parameters used by the UE to transmit the RRS2;

[0051] Alternatively, the frequency-domain resources used by the UE to transmit the RRS2 are the same as the frequency-domain resources used by the network device to transmit the RRQ2;

[0052] Alternatively, the RRQ1 includes indication information for indicating the transmission parameters used by the UE to transmit the RRS2.

[0053] Different UEs use different transmission resources to transmit their respective corresponding RRS2s, enabling the network device to determine whether the current channel of the corresponding UE is available based on the reception of RRS2, and then only scheduling the data transmission of those UEs with available channels, thus avoiding resource waste caused by blind data transmission scheduling.

[0054] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval, where the first time interval is the time interval between the moment when the UE receives the RRQ1 and the moment when the UE finishes transmitting the RRS1.

[0055] In a possible design, when the UE does not need to reply to the network device with a resource reservation response message RRS, the RRQ2 includes indication information for indicating the transmission resources and / or transmission parameters for the UE to transmit data with the network device.

[0056] In a possible design, the UE sends the RRS to the network device, including: when the UE receives the RRQ in time slot n, the UE sends the RRS to the network device in time slot n + k, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0057] In a third aspect, an embodiment of the present invention provides a network device, which includes:

[0058] A processing unit, configured to generate a resource reservation request message RRQ. The RRQ includes a first resource reservation request message RRQ1 and N second resource reservation request messages RRQ2. The RRQ1 includes first duration information, which is used to indicate that the network device occupies the target channel for a first duration. The N RRQ2s are respectively used to request N user devices UEs to transmit data with the network device within the first duration. The N RRQ2s correspond to the N UEs one by one, and N is an integer greater than or equal to 1;

[0059] A transceiver unit, configured to send the RRQ. Among them, the RRQ1 is scrambled with a first common identifier, and the N RRQ2s are respectively scrambled with the unique identifiers of their corresponding UEs. The first common identifier is an identifier known to at least one third-party device and the N UEs.

[0060] In a possible design, the RRQ1 further includes a cell identifier cell ID.

[0061] In a possible design, the RRQ1 is transmitted in a common search space CSS, and the N RRQ2s are respectively transmitted in specific search spaces USS of the corresponding UEs among the N UEs. The CSS is a search space known to the at least one third-party device and the N UEs.

[0062] In a possible design, the first general identifier is a predefined radio network temporary identifier RNTI; alternatively, the first general identifier is an RNTI notified by the network device to the at least one third-party device and the N UEs through radio resource control RRC signaling or system information; alternatively, the first general identifier is an RNTI calculated according to first information, and the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

[0063] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE corresponding to the RRQ2 needs to send a resource reservation response message RRS to the network device.

[0064] In a possible design, the transceiver unit is further configured to, after sending the RRQ, receive RRSs sent by M UEs among the N UEs. Each RRS among the M RRSs includes a first resource reservation response message RRS1 and a second resource reservation response message RRS2. The RRS1 contains second duration information, and the second duration information is used to indicate that the M UEs occupy the target channel for a second duration. The RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 will transmit data with the network device within the second duration. M is a positive integer less than or equal to N.

[0065] In a possible design, the M RRS1s included in the M RRSs are all transmitted on the same time-frequency resource.

[0066] In a possible design, the M RRS2s included in the M RRSs are respectively transmitted on different time-frequency resources.

[0067] In a possible design, the M RRS1s are all scrambled with a second general identifier, and the M RRS2s are respectively scrambled with unique identifiers corresponding to the M UEs. The second general identifier is known to the M UEs and the at least one third-party device.

[0068] In a possible design, the second common identifier is a predefined RNTI; or, the second common identifier is the RNTI notified by the network device to the at least one third-party device and the M UEs; or, the second common identifier is an RNTI calculated according to second information, where the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0069] In a possible design, the RRQ1 includes indication information for indicating time-frequency resources and / or transmission parameters used by the N UEs to transmit the RRS1;

[0070] Or, the frequency-domain resources used by the N UEs to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0071] In a possible design, each of the N RRQ2s includes indication information for indicating time-frequency resources and / or transmission parameters used by the corresponding UE among the N UEs to transmit the RRS2;

[0072] Or, the frequency-domain resources used by each of the N UEs to transmit its respective RRS2 are the same as the frequency-domain resources used by the RRQ2 corresponding to the UE among the N RRQ2s transmitted by the network device;

[0073] Or, the RRQ1 includes indication information for indicating transmission parameters used by the N UEs to transmit the N RRS2s respectively.

[0074] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval, where the first time interval is the time interval between the moment when the N UEs receive the RRQ1 and the moment when the N UEs finish sending the RRS1.

[0075] In a possible design, the N RRQ2s include one or more special RRQ2s, and the UEs corresponding to the special RRQ2s do not need to send a resource reservation response message RRS to the network device, and the special RRQ2s include indication information for indicating transmission resources and / or transmission parameters for the UEs corresponding to the RRQ2s to transmit data to the network device.

[0076] In a possible design, the transceiver unit is used to receive the RRS sent by M UEs among the N UEs specifically as follows:

[0077] When the time-domain resource used for sending the RRQ is time slot n, the RRS sent by M UEs among the N UEs is received in time slot n + k, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0078] In a fourth aspect, an embodiment of the present invention provides a user equipment (UE), and the user equipment UE includes:

[0079] a transceiver unit, configured to receive a resource reservation request message (RRQ) sent by a network device, where the RRQ includes a first resource reservation request message (RRQ1) and a second resource reservation request message (RRQ2), the RRQ1 includes first duration information, and the first duration information is used to indicate that the time for which the network device occupies a target channel is a first duration, the RRQ2 is used to request the UE to transmit data with the network device within the first duration, the RRQ1 is scrambled with a first common identifier, the RRQ2 is scrambled with a unique identifier corresponding to the UE, and the first common identifier is an identifier known to the UE and at least one third-party device.

[0080] In a possible design, the RRQ1 further includes a cell identifier (cell ID).

[0081] In a possible design, the RRQ1 is transmitted in a common search space (CSS), and the RRQ2 is transmitted in a specific search space (USS) of the UE, and the CSS is a search space known to the at least one third-party device and the UE.

[0082] In a possible design, the first common identifier is a predefined radio network temporary identifier (RNTI); or the first common identifier is an RNTI notified by the network device to the at least one third-party device and the UE through radio resource control (RRC) signaling or a system message; or the first common identifier is an RNTI calculated according to first information, and the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

[0083] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE needs to send a resource reservation response message (RRS) to the network device.

[0084] In a possible design, the user equipment UE further includes a processing unit;

[0085] The processing unit is configured to generate an RRS according to the RRQ after the transceiver unit receives the RRQ sent by the network device. The RRS includes RRS1 and RRS2. The RRS1 contains second duration information, and the second duration information is used to indicate that the UE occupies the target channel for a second duration. The RRS2 is used to confirm to the network device that the UE will transmit data to the network device within the second duration.

[0086] The transceiver unit is further configured to send the RRS to the network device.

[0087] In a possible design, the RRS1 is scrambled with a second common identifier, and the RRS2 is scrambled with a specific identifier corresponding to the UE. The second common identifier is known to the M UEs and the at least one third-party device.

[0088] In a possible design, the second common identifier is a predefined RNTI; alternatively, the second common identifier is an RNTI notified by the network device to the at least one third-party device and the UE; alternatively, the second common identifier is an RNTI calculated according to second information. The second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0089] In a possible design, the RRQ1 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS1.

[0090] Alternatively, the frequency-domain resources used by the UE to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0091] In a possible design, the RRQ2 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS2.

[0092] Alternatively, the frequency-domain resources used by the UE to transmit the RRS2 are the same as the frequency-domain resources used by the network device to transmit the RRQ2.

[0093] Alternatively, the RRQ1 includes indication information for indicating transmission parameters used by the UE to transmit the RRS2.

[0094] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval. The first time interval is the time interval between the moment when the UE receives the RRQ1 and the moment when the UE finishes sending the RRS1.

[0095] In a possible design, when the UE does not need to reply to the resource reservation response message RRS to the network device, the RRQ2 includes indication information for indicating the transmission resources and / or transmission parameters for the UE to transmit data to the network device.

[0096] In a possible design, the transceiver unit is specifically configured to send the RRS to the network device as follows:

[0097] When receiving the RRQ in time slot n, send the RRS to the network device in time slot n + k, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0098] In a fifth aspect, an embodiment of the present invention provides a network device, which may include: a memory, and a processor, a transmitter, and a receiver coupled to the memory. Wherein, the transmitter is used to support the network device to execute the step of the network device sending information in the resource reservation method provided in the first aspect. The receiver is used to support the network device to execute the step of the network device receiving information in the resource reservation method provided in the first aspect. Wherein, the transmitter and the receiver may be integrated into a transceiver. The processor is used to support the network device to execute other processing steps of the network device in the resource reservation method provided in the first aspect except for sending information and receiving information.

[0099] It should be noted that the transmitter and the receiver in the embodiment of the present invention may be integrated together or coupled through a coupler. The memory is used to store the implementation code of the resource reservation method described in the first aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the resource reservation method provided in the first aspect, or any one of the possible implementation manners of the resource reservation method provided in the first aspect. The memory and the processor may be integrated together or coupled through a coupler.

[0100] The processor is used to execute the program instructions stored in the memory, so that the network device performs the following operations:

[0101] Generate a resource reservation request message RRQ, where the RRQ includes a first resource reservation request message RRQ1 and N second resource reservation request messages RRQ2. The RRQ1 includes first duration information, which is used to indicate that the network device occupies the target channel for a first duration. The N RRQ2s are respectively used to request N user devices UE to transmit data with the network device within the first duration. The N RRQ2s correspond one-to-one with the N UEs, and N is an integer greater than or equal to 1;

[0102] Send the RRQ through the transceiver, where the RRQ1 is scrambled with a first common identifier, and the N RRQ2s are respectively scrambled with the unique identifiers of their corresponding UEs. The first common identifier is an identifier known to at least one third-party device and the N UEs.

[0103] In a possible design, the RRQ1 further includes a cell ID.

[0104] In a possible design, the RRQ1 is transmitted in a common search space CSS, and the N RRQ2s are respectively transmitted in the specific search spaces USSs of their corresponding UEs among the N UEs. The CSS is a search space known to at least one third-party device and the N UEs.

[0105] In a possible design, the first common identifier is a pre-defined radio network temporary identifier RNTI; alternatively, the first common identifier is an RNTI notified by the network device to at least one third-party device and the N UEs through radio resource control RRC signaling or a system message; alternatively, the first common identifier is an RNTI calculated according to first information, and the first information includes one or more of a cell ID, a system frame number, and a time slot number of the RRQ1.

[0106] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE corresponding to the RRQ2 needs to send a resource reservation response message RRS to the network device.

[0107] In a possible design, the operation further includes: after sending the RRQ through the transceiver, receiving, through the transceiver, RRSs sent by M UEs among the N UEs, each of the M RRSs including a first resource reservation response message RRS1 and a second resource reservation response message RRS2, the RRS1 containing second duration information for indicating that the M UEs occupy the target channel for a second duration, and the RRS2 being used to confirm to the network device that the UE corresponding to the RRS2 will transmit data to the network device within the second duration, where M is a positive integer less than or equal to N.

[0108] In a possible design, the M RRS1s included in the M RRSs are all transmitted on the same time-frequency resource.

[0109] In a possible design, the M RRS2s included in the M RRSs are respectively transmitted on different time-frequency resources.

[0110] In a possible design, the RRS1 is scrambled with a second common identifier, and the M RRS2s are respectively scrambled with unique identifiers corresponding to the M UEs, and the second common identifier is known to the M UEs and the at least one third-party device.

[0111] In a possible design, the second common identifier is a predefined RNTI; or, the second common identifier is an RNTI notified by the network device to the at least one third-party device and the M UEs; or, the second common identifier is an RNTI calculated based on second information, where the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0112] In a possible design, the RRQ1 includes indication information for indicating the time-frequency resource and / or transmission parameters used by the N UEs to transmit the RRS1;

[0113] Or, the frequency-domain resources used by the N UEs to transmit the RRS1 are all the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0114] In a possible design, the N RRQ2s respectively include indication information for indicating the time-frequency resource and / or transmission parameters used by the corresponding UEs among the N UEs to transmit the RRS2;

[0115] Alternatively, for each UE among the N UEs, the frequency-domain resources used by the respective RRS2 are the same as the frequency-domain resources used by the RRQ2 corresponding to the UE among the N RRQ2s transmitted by the network device;

[0116] Alternatively, the RRQ1 includes indication information for indicating the transmission parameters respectively used by the N UEs to transmit the N RRS2s.

[0117] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval, where the first time interval is the time interval between the time when the N UEs receive the RRQ1 and the time when the N UEs finish transmitting the RRS1.

[0118] In a possible design, the N RRQ2s include one or more special RRQ2s, and the UEs corresponding to the special RRQ2s do not need to send a resource reservation response message RRS to the network device. The special RRQ2 includes indication information for indicating the transmission resources and / or transmission parameters for the UE corresponding to the RRQ2 to transmit data to the network device.

[0119] In a possible design, the receiving, by the transceiver, the RRS sent by M UEs among the N UEs includes:

[0120] When the time-domain resources used by the transceiver to send the RRQ are time slot n, the transceiver receives, in time slot n + k, the RRS sent by M UEs among the N UEs, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0121] In a sixth aspect, an embodiment of the present invention provides a user equipment, which may include: a memory, a processor, a transmitter, and a receiver coupled to the memory. The transmitter is used to support the user equipment to execute the step of the user equipment sending information in the resource reservation method provided in the second aspect. The receiver is used to support the user equipment to execute the step of the user equipment receiving information in the resource reservation method provided in the second aspect. The transmitter and the receiver may be integrated into a transceiver. The processor is used to support the user equipment to execute other processing steps of the user equipment in the resource reservation method provided in the second aspect except for sending information and receiving information.

[0122] It should be noted that the transmitter and receiver in the embodiments of the present invention may be integrated together or coupled through a coupler. The memory is used to store the implementation code of the resource reservation method described in the second aspect, and the processor is used to execute the program code stored in the memory, that is, to execute the resource reservation method provided in the second aspect, or any one of the possible implementation manners of the resource reservation method provided in the second aspect. The memory and the processor may be integrated together or coupled through a coupler.

[0123] The processor is used to execute the program instructions stored in the memory, so that the UE performs the following operations:

[0124] Receive a resource reservation request message RRQ sent by a network device through the transceiver, where the RRQ includes a first resource reservation request message RRQ1 and a second resource reservation request message RRQ2. The RRQ1 includes first duration information, and the first duration information is used to indicate that the network device occupies the target channel for a first duration. The RRQ2 is used to request the UE to transmit data to the network device within the first duration. The RRQ1 is scrambled with a first common identifier, and the RRQ2 is scrambled with a unique identifier corresponding to the UE. The first common identifier is an identifier known to the UE and at least one third-party device.

[0125] In a possible design, the RRQ1 further includes a cell identifier cell ID.

[0126] In a possible design, the RRQ1 is transmitted in a common search space CSS, and the RRQ2 is transmitted in a specific search space USS of the UE. The CSS is a search space known to the at least one third-party device and the UE.

[0127] In a possible design, the first common identifier is a predefined radio network temporary identifier RNTI; alternatively, the first common identifier is an RNTI notified by the network device to the at least one third-party device and the UE through radio resource control RRC signaling or a system message; alternatively, the first common identifier is an RNTI calculated according to first information, and the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

[0128] In a possible design, the RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE needs to send a resource reservation response message RRS to the network device.

[0129] In a possible design, the operation further includes: after receiving an RRQ sent by a network device through the transceiver, generating an RRS according to the RRQ, where the RRS includes RRS1 and RRS2, the RRS1 contains second duration information, and the second duration information is used to indicate that the UE occupies the target channel for a second duration, and the RRS2 is used to confirm to the network device that the UE will transmit data to the network device within the second duration;

[0130] Sending the RRS to the network device through the transceiver.

[0131] In a possible design, the RRS1 is scrambled with a second common identifier, and the RRS2 is scrambled with a specific identifier corresponding to the UE, and the second common identifier is known to the M UEs and the at least one third-party device.

[0132] In a possible design, the second common identifier is a predefined RNTI; alternatively, the second common identifier is an RNTI notified by the network device to the at least one third-party device and the UE; alternatively, the second common identifier is an RNTI calculated according to second information; the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

[0133] In a possible design, the RRQ1 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS1;

[0134] Alternatively, the frequency-domain resources used by the UE to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

[0135] In a possible design, the RRQ2 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS2;

[0136] Alternatively, the frequency-domain resources used by the UE to transmit the RRS2 are the same as the frequency-domain resources used by the network device to transmit the RRQ2;

[0137] Alternatively, the RRQ1 includes indication information for indicating transmission parameters used by the UE to transmit the RRS2.

[0138] In a possible design, the second duration is less than the first duration, and the second duration is equal to the first duration minus a first time interval, where the first time interval is the time interval between the moment when the UE receives the RRQ1 and the moment when the UE finishes sending the RRS1.

[0139] In a possible design, when the UE does not need to reply to the network device with a resource reservation response message RRS, the RRQ2 includes indication information for indicating transmission resources and / or transmission parameters for the UE to transmit data to the network device.

[0140] In a possible design, sending the RRS to the network device through the transceiver includes:

[0141] When receiving the RRQ through the transceiver in time slot n, sending the RRS to the network device through the transceiver in time slot n + k, where n and n + k are the numbers of time slots, k is a predefined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

[0142] In a seventh aspect, an embodiment of the present invention provides a resource reservation system, including one or more network devices and one or more user devices. Among them, the network device may be the network device described in the foregoing third aspect or fifth aspect, and the user device may be the user device described in the foregoing fourth aspect or sixth aspect.

[0143] In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which instructions are stored. When the instructions run on a computer, the computer is enabled to execute the resource reservation method described in any of the foregoing aspects.

[0144] In a ninth aspect, an embodiment of the present invention provides a computer program product including instructions. When the computer program product runs on a computer, the computer is enabled to execute the resource reservation method described in any of the foregoing aspects.

[0145] In a tenth aspect, an embodiment of the present invention provides a computer program including instructions. When the computer program runs on a computer, the computer is enabled to execute the resource reservation method described in any of the foregoing aspects.

[0146] In a tenth aspect, an embodiment of the present invention provides a device, which may include: a processor (the number of processors may be one or more), and one or more interfaces coupled to the processor. Wherein, the processor may be configured to call an implementation program of the resource reservation method provided in any of the foregoing aspects from a memory (the memory may be located inside the device or outside the device and coupled to the device), and execute the instructions included in the program. The interface may be configured to output the processing result of the processor.

[0147] In one possible design, the above device is a chip or a system on a chip (SoC).

[0148] To sum up, in the prior art, the identification information of all target devices is directly carried in the resource reservation request message (or called resource reservation request frame), resulting in an excessively long frame length of the resource reservation request frame, thereby reducing the success rate of the transmission of the resource reservation request frame. Compared with the prior art, some embodiments of the present application divide the resource reservation request frame into one RRQ1 and multiple RRQ2s. RRQ1 is sent to a third-party device and does not carry the identification of the target device for subsequent data transmission, so that the length of RRQ1 is much smaller than the resource reservation request frame (such as MU-RTS) in the prior art, greatly increasing the probability that RRQ1 is correctly received by the third-party device; at the same time, each RRQ2 corresponds to a target device, and each RRQ2 only carries the identification of the target device corresponding to it, so that the length of RRQ2 is much smaller than the resource reservation request frame (such as MU-RTS) in the prior art, greatly increasing the probability that RRQ2 is correctly received by the corresponding target device, and the purpose of resource reservation can be achieved, thereby improving the success rate of data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0149] The following will introduce the drawings required to be used in the embodiments of the present application.

[0150] Figure 1 It is a schematic diagram of the system architecture of a resource reservation method provided by an embodiment of the present application;

[0151] Figure 2 It is a schematic diagram of the timing process from a sending device competing for a channel to data transmission provided by an embodiment of the present application;

[0152] Figure 3 It is a schematic flowchart of a resource reservation method provided by an embodiment of the present application;

[0153] Figure 4 It is a schematic diagram of the composition of a resource reservation request message and resource allocation provided by an embodiment of the present application;

[0154] Figure 5Schematic flowchart of another resource reservation method provided by an embodiment of the present application;

[0155] Figure 6 Schematic diagram of resource allocation of a resource reservation response message provided by an embodiment of the present application;

[0156] Figure 7 Schematic diagram of resource allocation of another resource reservation response message provided by an embodiment of the present application;

[0157] Figure 8 Schematic diagram of the logical structure of a network device provided by an embodiment of the present application;

[0158] Figure 9 Schematic diagram of the hardware structure of a network device provided by an embodiment of the present application;

[0159] Figure 10 Schematic diagram of the logical structure of a user equipment provided by an embodiment of the present application;

[0160] Figure 11 Schematic diagram of the hardware structure of a user equipment provided by an embodiment of the present application;

[0161] Figure 12 Schematic diagram of the structure of a communication chip provided by an embodiment of the present application. Detailed implementation manners

[0162] To enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

[0163] The following will be described in detail respectively.

[0164] To better understand a resource reservation method, device, system, and computer-readable storage medium provided by an embodiment of the present invention, the system architecture of the resource reservation method applicable to the embodiment of the present invention will be described below. As Figure 1 shown in the system architecture 100, it may include at least one network device 101 and multiple user devices 102 (user equipment, UE). The network device 101 can perform data transmission with the user device 102, and the network device 101 allocates transmission resources for the user device 102.

[0165] The network device 101 involved in the embodiments of the present application may include various forms of network devices, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, cells, etc. An exemplary base station may be an evolved Node B (eNB), and a next-generation Node B (gNB) in a 5G system or a new radio (NR) system. Additionally, the base station may also be a transmission receive point (TRP), a central unit (CU), or other network entities. Further, in a distributed base station scenario, the network device 101 may be a baseband unit (BBU) and a remote radio unit (RRU), and in a cloud radio access network (CRAN) scenario, it may be a baseband pool BBUpool and a remote radio unit RRU. Moreover, the network device 101 may also be a core network device (core network, CN), a mobility management entity (MME) device, an access and mobility management function (AMF) device, a vehicle-to-everything control function (CF) device, a gateway (GateWay), a roadside unit (RSU), an operation administration and maintenance (OAM) device, an application server (APP server), or a third-party network element.

[0166] The user equipment 102 involved in the embodiments of the present application is a device capable of receiving scheduling and indication information from the network device 101, and may be devices such as mobile phones, computers, bracelets, smart watches, data cards, sensors, stations (STA), etc., which can be collectively referred to as terminal devices. For example, for the link between a bracelet and a mobile phone in a bracelet-mobile phone-base station scenario, the bracelet can be regarded as the user equipment 102, and the mobile phone as the network device 101.

[0167] In the present invention, the data sending device may be the network device 101, and the data receiving device may be the user equipment 102; or, the data sending device is the user equipment 102, and the data receiving device is the network device 101; or, the data sending device is the user equipment 102, and the data receiving device is also the user equipment 102.

[0168] It should be noted that the terms "system" and "network" in the embodiments of the present application can be used interchangeably. "Multiple" means two or more. In view of this, in the embodiments of the present application, "multiple" can also be understood as "at least two". "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / ", unless otherwise specified, generally represents an "or" relationship between the associated objects before and after.

[0169] It should be noted that the system architecture of the resource reservation method provided in the embodiments of the present application is not limited to Figure 1 the system architecture shown.

[0170] Based on the above system architecture, the resource reservation request method provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0171] Before the sending device sends data information to the receiving device, it is necessary to first listen to whether the target channel is idle. Only when the target channel is idle and the competition for the target channel is successful, can the sending device occupy the target channel to transmit data.

[0172] The following exemplarily gives the specific timing process from channel competition to data transmission:

[0173] It can be seen in Figure 2 , Figure 2 which exemplarily shows the process of the sending device competing for the channel. It can be seen that when the target channel is busy, the sending device (which can be a network device, for example) is in a continuous listening state. When the sending device listens and detects that the target channel is idle and the idle state lasts for the first preset duration, that is, the duration of the distributed coordination function interframe space (DIFS), the sending device performs a backoff process, that is, randomly selects a value within a predetermined range to set a backoff timer, and then the backoff timer starts to count down backward.

[0174] During the backoff process, the sending device continuously listens and detects the channel. If the target channel remains idle during the period when the backoff timer counts down backward until it reaches 0, then the sending device generates a resource request message (RRQ) and sends the RRQ to the receiving device, indicating that the sending device has successfully competed for the target channel. The RRQ sent by the sending device includes a Duration field, which is used to indicate the remaining time of the current transmission process. The remaining time of the current transmission process is Figure 2The period from when the sending device sends an RRQ until the receiving device sends an acknowledgement message (ACK). After a third-party device listening to the target channel hears the RRQ, it obtains the information in the Duration field and then sets its own network allocation vector (NAV) according to the information in the Duration field. Before the NAV times out to 0, the third-party device will not compete for the target channel, thus avoiding interference to the transmission between the sending device and the receiving device caused by the third-party device sending data.

[0175] The period from when the sending device hears that the target channel is idle until it sends an RRQ, that is, the period of DIFS plus the countdown of the backoff timer, is a process of clear channel assessment (CCA), which can effectively avoid collisions on the wireless channel.

[0176] After the receiving device receives the RRQ sent by the sending device, after a second preset duration, that is, the short interframe space (SIFS) duration, the receiving device sends a resource reservation response message (RRS) to the sending device. The RRS also includes a Duration field, and its value is the value of the Duration field in the RRQ minus the SIFS and the duration of the RRS, as Figure 2 shown. After a third-party device listening to the target channel hears the RRS, it obtains the information in the Duration field and then sets its own network allocation vector (NAV) according to the obtained Duration field information. Before the NAV times out to 0, the third-party device will not compete for the target channel, thus avoiding interference to the transmission between the sending device and the receiving device caused by the third-party device sending data.

[0177] After the sending device receives the RRS, it sends data to the receiving device after an SIFS duration. After the receiving device receives the data, it sends an ACK to the sending device after an SIFS duration. Thus, the entire process of the sending device competing for the target channel and data transmission is completed.

[0178] The embodiments of this application use orthogonal frequency division multiple access (OFDMA) technology for data transmission, that is, the network device can send data information to multiple UEs simultaneously. Specifically, the OFDMA technology can divide the transmission bandwidth into a series of orthogonal and non-overlapping subcarrier sets, and allocate different subcarrier sets to different users to achieve multiple access; the OFDMA technology can dynamically allocate available bandwidth resources to users in need, and it is easy to optimize the utilization of system resources. Since different users occupy non-overlapping subcarrier sets, in the case of ideal synchronization, there is no interference between multiple users in the system, that is, there is no multiple access interference (MAI).

[0179] Based on the above description, the resource reservation method provided by the embodiments of this application will be introduced below in combination with Figure 3 the flowchart shown. The method may include the following steps: Figure 3 The method shown may include the following steps:

[0180] S301. The network device generates a resource reservation request message RRQ. The RRQ includes one RRQ1 and N RRQ2s. The RRQ1 includes first duration information, which is used to indicate that the time for occupying the target channel is the first duration. The N RRQ2s are respectively used to request N user devices UE to transmit data with the network device within the first duration. The N RRQ2s correspond to the N UEs one by one.

[0181] After successfully competing for the target channel, the network device will generate a resource reservation request message RRQ. The RRQ includes 1 first resource reservation request RRQ1 and N (N≥1) second resource reservation requests RRQ2s.

[0182] Specifically, the RRQ1 includes first duration information, which is used to indicate that the time for the above network device to occupy the target channel is the first duration. Specifically, the first duration information is used to indicate to a third-party device that the time for the above network device to occupy the target channel is the first duration. The above N RRQ2s correspond to N UEs one by one, and are respectively used to request N UEs to transmit data with the above network device within the first duration. The above third-party device may be other network devices and UEs that compete for the above target channel in addition to the above N UEs and the above network device; the first duration information is included in the RRQ1 so that after the third-party device detects the RRQ1, it sets a resource reservation timer according to the first duration, so as to achieve resource reservation.

[0183] In addition to the first duration information, optionally, RRQ1 may further include one or more of the following information: the current cell identifier (cell ID) and indication information for indicating uplink or downlink transmission. Since the RRQ is always sent by the network device regardless of whether the final data transmission is from the network device to the UE or from the UE to the network device, it is necessary to indicate whether the subsequent scheduled transmission is an uplink transmission or a downlink transmission.

[0184] It should be noted that when a certain user equipment receives RRQ1 and obtains the first duration information and cell identifier information in the RRQ1, if the cell identifier in the RRQ1 is not the identifier of the cell where the user equipment is located, that is, the target cell targeted by the RRQ sent by the network device is not the cell where the user equipment is located, then the user equipment will no longer attempt to receive RRQ2 in its corresponding specific search space, but directly set the network allocation vector (NAV) according to the first duration information in RRQ1. Before the NAV expires to 0, the user equipment will not compete for the target channel. This reduces the operating burden of the processor of the user equipment while avoiding interference with data transmission on the target channel.

[0185] S302. The network device sends the above-mentioned RRQ, and the above N UEs receive the RRQ sent by the network device.

[0186] Specifically, the network device sends RRQ1 included in the above-mentioned RRQ in the common search space (CSS), so that both the above N UEs and third-party devices can search for and receive the RRQ1. The network device respectively sends the above N RRQ2s in the UE-specific search spaces (USSs) corresponding to the above N UEs, so that each of the N RRQ2s can only be searched for and received by the UE corresponding to the USS where it is located.

[0187] The first resource reservation request RRQ1 is transmitted in the common search space so that third-party devices other than the target device for transmitting data with the network device can also receive the RRQ1, enabling these third-party devices to set resource reservation timers according to the time information in the RRQ1 to achieve the purpose of reserving resources; while the N RRQ2s are respectively transmitted in the specific search spaces of their respective UEs to reduce interference with each other, enabling each UE to correctly receive its corresponding RRQ2, thereby preparing for subsequent data transmission and improving the success rate of data transmission.

[0188] To facilitate the understanding of the composition of the RRQ and the allocation of the transmission resources of the RRQ, an example is given as follows Figure 4 . Figure 4 The figure showing the composition of the RRQ and the allocation of the transmission resources is given with N being 3 as an example. Assume that Figure 4 each small grid in represents a transmission resource, then Figure 4 the small grids occupied by RRQ1 and three RRQ2s in are the transmission resources used by the network device to transmit the corresponding RRQ1 and three RRQ2s respectively. It can be seen that the RRQ is composed of one RRQ1 and three RRQ2s. The network device sends RRQ1 in the common search space CSS, and sends the three RRQ2s in the USSs corresponding to the respective UEs of the three RRQ2s. In a specific embodiment, the CSS and the USS may partially overlap. For example Figure 4 the CSS and the USS in UE2 in partially overlap, but the partially overlapping search space does not affect the search of UE2 for the RRQ. In addition, the USSs between different UEs also partially overlap, but this does not affect the normal search for the corresponding RRQ2 and the correct acquisition of the information in the corresponding RRQ2 among each other. This is because RRQ2 will be scrambled with the unique identifier of the corresponding UE, and only the corresponding UE can descramble RRQ2 to obtain the corresponding information. The content of scrambling will be introduced below

[0189] Scrambling is a processing method for digital signals, that is, multiplying the scrambling code by the original signal to obtain a new signal. The function of uplink scrambling is to distinguish users, and the function of downlink scrambling can be to distinguish cells and channels

[0190] The above RRQ1 is scrambled with a common identifier, and the common identifier is an identifier known to the above N UEs and the above third-party device. For example, the common identifier can be a standard pre-defined radio network temporary identify / identifier (RNTI), or it can be an RNTI notified by the network device to the above N UEs and the above third-party device, or it can be an RNTI calculated according to specific information, and the specific information can include one or more of information such as cell ID, current system frame number, time slot number of RRQ1, etc. Such a design enables a third-party device (i.e., a UE not within the RRQ2 transmission target range of the current RRQ) to also receive RRQ1, and then obtain the first duration therein for setting its own resource reservation timer. Before the resource reservation timer times out to 0, these third-party devices will not actively compete for the channel, thus avoiding interference to the current transmission (transmission between the network device and the UE)

[0191] Each of the above N RRQs 2 is scrambled with the unique identifier of its corresponding UE. The unique identifier of the UE can be, for example, the international mobile equipment identity (IMEI) of the UE, the international mobile subscriber identification number (IMSI), or a specific RNTI corresponding to the UE. The specific RNTI can be, for example, the cell radio network temporary identifier (C-RNTI).

[0192] The above N UEs respectively receive the RRQ. However, since the RRQ 2 is scrambled with the UE-specific identifier corresponding thereto, only the UE can descramble the RRQ 2 to obtain the information therein. Therefore, from the perspective of the UE, it can only correctly obtain the information of the RRQ 1 sent by the above network device and the information of the RRQ 2 corresponding to itself, and cannot correctly obtain the information of the other N-1 RRQs 2.

[0193] After the above N UEs receive the RRQ sent by the network device, they need to send a resource reservation response message (resource response, RRS) to the network device, that is, they need to reply with RRS; or they can also not send RRS to the network device, that is, they do not need to reply with RRS.

[0194] In a specific embodiment, whether the UE that receives the RRQ needs to reply with RRS to the network device can be predefined by a standard. For example, the standard can stipulate that the UE must reply with RRS after receiving the RRQ; or, whether the UE that receives the RRQ needs to reply with RRS to the network device can be indicated by the network device in the RRQ. For example, the network device can indicate in the RRQ 1 or RRQ 2 whether the UE needs to reply with RRS after receiving the RRQ; or, whether the UE that receives the RRQ needs to reply with RRS to the network device can be judged by the UE according to predefined rules. For example, when the reference signal receiving power (RSRP) of the downlink reference signal measured by the UE is greater than the threshold, the UE does not need to reply with RRS, otherwise it needs to reply with RRS.

[0195] If a UE corresponding to an RRQ2 needs to reply with a resource reservation response message RRS but fails to do so, the network device will not schedule data transmission for this UE, thus avoiding waste of resources. That is, the network device only schedules data transmission for UEs that have replied with the resource reservation response message, thereby improving resource utilization efficiency. If a UE corresponding to an RRQ2 does not need to reply with a resource reservation response message, it indicates that the network device will directly schedule data transmission for this UE subsequently, saving the time for replying with the resource reservation response message, thus reducing the time of the entire data transmission process and improving the data transmission efficiency.

[0196] The following will introduce from two aspects: needing to reply with RRS and not needing to reply with RRS.

[0197] I. Needing to reply with RRS.

[0198] In one embodiment, after receiving an RRQ, the UE needs to reply with an RRS to the network device that sent the RRQ to indicate that the UE can transmit data with the network device. In the case where the UE needs to reply with an RRS, if the network device does not receive the RRS replied by the UE, the network device considers that the current channel of the UE is busy and the UE cannot transmit data with the network device, and the network device will not schedule data transmission for this UE at a subsequent time.

[0199] It should be noted that although the N RRQ2s in the network device's RRQ correspond to N UEs, among these N UEs, some UEs may not correctly receive the corresponding RRQ2, or some UEs may not be able to reply with RRS due to a busy channel. Therefore, the network device may only receive RRS2 replied by M UEs, where M ≤ N. For UEs that do not reply with RRS, the network device will not schedule data transmission for these UEs at a subsequent time, thus avoiding waste of transmission resources and improving the utilization rate of transmission resources.

[0200] According to the above description, if the UE needs to reply with RRS, after step S302 above, the following steps S303 - S304 are further included, which can be specifically referred to Figure 5 as shown. Among them,

[0201] S303. M out of the N UEs respectively generate a resource reservation response message RRS according to the above RRQ. Each RRS includes RRS1 and RRS2. The RRS1 contains second duration information, and the second duration information is used to indicate that the M UEs occupy the target channel for a second duration. The RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 will transmit data with the network device within the second duration.

[0202] Specifically, among the N UEs, M UEs reply with RRS, and each of the M UEs generates a corresponding RRS according to the RRQ received by itself. The RRS generated by each UE includes a first resource reservation response message RRS1 and a second resource reservation response message RRS2. Among them, the RRS1 contains second duration information, and this second duration information is used to indicate that the above M UEs occupy the target channel for a second duration. Specifically, this second duration information is used to indicate to a third-party device that the above M UEs occupy the target channel for a second duration; including the second duration information in the RRS1 is to enable the third-party device to set a resource reservation timer according to this second duration after detecting the RRS1, so as to achieve resource reservation. In addition, RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 will transmit data to the network device within the second duration, which can improve the success rate of data transmission.

[0203] The second duration in the above RRS1 and the first duration in the above RRQ1 can be different. The second duration can be the duration after subtracting a first time interval from the first duration, and the first time interval is the time interval between the moment when the above M UEs receive the RRQ and the moment when the above M UEs send the corresponding RRS to the network device. In a specific embodiment, the time when the above M UEs reply with RRS is the same, and the specific reply time can be predefined.

[0204] S304. The M UEs send a resource reservation response message RRS.

[0205] After the above M UEs generate the RRS, they send the RRS to the network device. Similar to the above RRQ, the RRS sent by the above M UEs to the network device also needs to be scrambled.

[0206] Among them, RRS1 is scrambled with a common identifier, which may be the same as or different from the common identifier used by the above RRQ1. Similarly, the common identifier used by RRS1 is an identifier known to the above N UEs and the above third-party device. For example, the common identifier used by RRS1 may be a standard pre-defined radio network temporary identify / identifier (RNTI), or it may be an RNTI notified by the above network device to the above N UEs and the above third-party device, or it may be an RNTI calculated based on specific information, and the specific information may include one or more of information such as cell ID, current system frame number, time slot number of RRQ1 or RRS1, etc. Such a design enables the third-party device to also receive RRS1, and then obtain the second duration therein for setting its own resource reservation timer. Before the resource reservation timer expires to 0, these third-party devices will not actively compete for the channel, thus avoiding interference with the current transmission (transmission between the network device and the UE).

[0207] RRS2 in the above RRS is scrambled with the unique identifier of the UE that replies to the RRS. The unique identifier of the UE may be, for example, the international mobile equipment identity (IMEI), international mobile subscriber identification number (IMSI) of the UE, or a specific RNTI corresponding to the UE. The specific RNTI may be, for example, a cell radio network temporary identifier (C-RNTI).

[0208] In addition, when the UE replies to the RRS, it requires transmission resources, i.e., time-frequency resources. The network device may indicate in the RRQ the transmission resources used by the UE to reply to the RRS.

[0209] Specifically, the network device may indicate in the sent RRQ1 the transmission resources used by the UE to reply RRS1. Of course, the network device may also indicate in the sent RRQ1 the transmission parameters used by the UE to reply RRS1. The transmission parameter may be, for example, a Modulation and Coding Scheme (MCS), etc. Similarly, the network device may indicate in the sent RRQ2 the time-frequency resources used by the UE to reply RRS2. Of course, the network device may also indicate in RRQ2 the transmission parameters used by the UE to reply RRS2, such as MCS, etc. Alternatively, the network device may also indicate in RRQ1 the transmission parameters respectively used by all UEs to reply RRS2. Among them, the transmission parameters used by all UEs to reply RRS2 may be the same or different. The transmission parameter used by the UE to reply RRS2 may be, for example, MCS, etc. Among them, the transmission parameters used by RRS1 and RRS2 may also be predefined. For example, the MCS of the transmission parameter may be predefined as QPSK, 16QAM, 64QAM, etc.

[0210] The above-mentioned transmission resources may include both time-domain resources and frequency-domain resources, or may only include frequency-domain resources. However, for the latter case, other methods are required to determine the time-domain resources of RRS.

[0211] It should be noted that since there is only one RRQ1 in the RRQ, the transmission resources of RRS1 indicated by RRQ1 are also only one, that is, all UEs use the same transmission resources to reply RRS1, which can reduce the occupation of time-frequency resources and save overhead. However, in order to avoid interference and facilitate the network device to distinguish which UE has replied RRS, each UE uses its own different transmission resources to reply its corresponding RRS2. It can be understood that since all UEs use the same transmission resources to reply RRS1, in order to avoid interference, the content of RRS1 replied by all UEs is the same and the reply time is the same.

[0212] For example, it can be referred to Figure 6 . Figure 6 And Figure 4 is the same. Still taking N as 3 as an example for illustration. Assume Figure 4 and Figure 6 each small grid in represents a transmission resource. Then Figure 4 the small grids occupied by RRQ1 and 3 RRQ2s in are the transmission resources used by the network device to transmit this RRQ1 and 3 RRQ2s respectively, Figure 6 and the small grids occupied by RRS1 and 3 RRS2s in are the transmission resources specified by the network device for each UE to reply RRS. It can be seen that all UEs use the same transmission resources to reply RRS1. However, different UEs use different transmission resources to reply RRS2.

[0213] In one implementation, it is not necessary for the network device to indicate in the RRQ the transmission resources for the UE to reply with the RRS. Instead, the time-frequency resources of the RRS are mapped and generated according to the time-frequency resources of the RRQ and predefined rules. For example, the frequency-domain resources used by the UE to reply with RRS1 can be the same as the frequency-domain resources used by the network device to send RRQ1, and the frequency-domain resources used by the UE to send RRS2 can be the same as the frequency-domain resources used by the network device to send the corresponding RRQ2 for this UE.

[0214] In addition, the time-domain resources for the UE to reply with the RRS can be specified. For example, if the UE receives the RRQ in time slot n (i.e., the network device sends the RRQ in time slot n), it replies with the RRS in time slot n + k (i.e., the network device receives the RRS in time slot n + k). Here, n and n + k are time slot numbers, and k can be a standard predefined value or indicated by the network device in RRQ1 or RRQ2 or previously through other signaling (such as RRC signaling or system information) to the UE, where k is an integer greater than or equal to zero.

[0215] For example, reference can be made to Figure 7 . Figure 7 and Figure 4 , Figure 6 Taking N as 3 for illustration as in Figure 4 . If the small grids occupied by RRQ1 and three RRQ2s in Figure 7 are the transmission resources used by the network device to transmit the RRQ1 and the three RRQ2s respectively, then after UE1, UE2, and UE3 receive the RRQ1 and the corresponding RRQ2s, they determine the transmission resources for replying with the corresponding RRS according to the transmission resources where the RRQ1 and the corresponding RRQ2s are located. As shown in Figure 7 , the transmission resources used by all UEs to reply with RRS1 are the same as the transmission resources used by the network device to transmit RRQ1, and the transmission resources used by UE1, UE2, and UE3 to reply with RRS2 respectively are the same as the transmission resources used by the network device to transmit their respective corresponding RRQ2s. It should be noted that

[0216] In the embodiments of this application, after the network device receives the RRS sent by the UE, it sends downlink control information (DCI) to schedule the uplink or downlink data transmission of the corresponding UE. The DCI sent by the network device to the UE can include information such as resource allocation for uplink and downlink data transmission, hybrid automatic repeat request information (HARQ), and / or power control.

[0217] In the above embodiments, RRS1 is scrambled with a common identifier, enabling third-party devices to receive this RRS1 and avoiding transmission interference caused by third-party devices. At the same time, all UEs use the same transmission resources to send RRS1, occupying less time-frequency resources and thus having a smaller overhead. Different UEs use different transmission resources to transmit their respective corresponding RRS2, enabling the network device to determine whether the current channel of the corresponding UE is available based on the reception of RRS2, and then only scheduling the data transmission of those UEs with available channels, avoiding resource waste caused by blind data transmission scheduling. Additionally, compared with the method in the prior art of carrying the information of multiple STAs in one message (MU-RTS), in this solution, RRQ2 is sent separately for each UE, and the frame length of each RRQ2 is much smaller than that of MU-RTS. Therefore, the transmission reliability is significantly improved, the purpose of resource reservation can be achieved, and thus the success rate of data transmission can be increased.

[0218] II. No need to reply to RRS.

[0219] In the case where there is no need for the UE to reply to RRS, the network device can indicate the transmission resources and / or transmission parameters for the UE to transmit data in the RRQ2 sent to the UE, without having to send a dedicated DCI for transmission scheduling to the UE, which can overall save the time of the entire data transmission process and improve the efficiency of data transmission. Specifically, the transmission parameter can be MCS, etc.

[0220] In summary, in the prior art, directly carrying the identification information of all target devices in the resource reservation request message (or resource reservation request frame) results in an overly long frame length of this resource reservation request frame, thereby reducing the success rate of the transmission of the resource reservation request frame. Compared with the prior art, in the embodiments of this application, the resource reservation request frame is divided into one RRQ1 and multiple RRQ2. RRQ1 is sent to the third-party device and does not carry the identification of the target device for subsequent data transmission, making the length of RRQ1 much smaller than that of the resource reservation request frame in the prior art (such as MU-RTS), greatly increasing the probability of correct reception of RRQ1 by the third-party device; at the same time, each RRQ2 corresponds to one target device, and each RRQ2 only carries the identification of the target device corresponding to it, making the length of RRQ2 much smaller than that of the resource reservation request frame in the prior art (such as MU-RTS), greatly increasing the probability of correct reception of RRQ2 by the corresponding target device, achieving the purpose of resource reservation, and thus increasing the success rate of data transmission.

[0221] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of the interaction between network devices and user devices. It can be understood that, in order to implement the above functions, each network element, such as a network device, a user device, etc., includes a corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the network elements and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0222] The embodiments of the present application can perform function module division on network devices, user devices, etc. according to the above method examples. For example, each function module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software function module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0223] In the case of dividing each function module corresponding to each function, Figure 8 FIG. shows a possible schematic diagram of the logical structure of the network device involved in the above embodiments. The network device 800 includes: a transceiver unit 801 and a processing unit 802. Exemplarily, the transceiver unit 801 is used to support the network device to execute the steps of the network device receiving information in the method embodiments shown in the foregoing Figure 3 or Figure 5 The transceiver unit 801 is also used to support the network device to execute the steps of the network device sending information in the method embodiments shown in the foregoing Figure 3 or Figure 5 The processing unit 802 is used to support the network device to execute the steps of the network device generating information in the method embodiments shown in the foregoing Figure 3 or Figure 5 and other functions other than the functions of the transceiver unit 801.

[0224] Optionally, the network device 800 may further include a storage unit for storing code (program) or data. In one possible way, the processing unit 802 may call the code or data in the storage unit, so that the network device 800 generates a resource reservation request message RRQ. The RRQ includes a first resource reservation request message RRQ1 and N second resource reservation request messages RRQ2. The RRQ1 includes first duration information, which is used to indicate that the network device occupies the target channel for a first duration. The N RRQ2s are respectively used to request N user devices UE to transmit data with the network device within the first duration. The N RRQ2s correspond to the N UEs one by one, and N is an integer greater than or equal to 1. And it enables the network device 800 to send the RRQ. Among them, the RRQ1 is scrambled with a first general identifier, and the N RRQ2s are respectively scrambled with the unique identifiers of their corresponding UEs. The first general identifier is an identifier known to at least one third-party device and the N UEs.

[0225] In terms of hardware implementation, the above-mentioned processing unit 802 may be a processor or a processing circuit, etc. The transceiver unit 801 may be a transceiver or a transceiver circuit or an interface circuit, etc. The storage unit may be a memory. The above-mentioned processing unit, transceiver unit and storage unit may be integrated together or separated.

[0226] Figure 9 As shown, it is a schematic diagram of a possible hardware structure of the network device involved in the above embodiments provided by the embodiments of the present application. As Figure 9 shown, the network device 900 may include: one or more processors 901, one or more memories 902, a network interface 903, one or more transceivers 905, and one or more antennas 908. These components may be connected through a bus 904 or other means. Figure 9 Taking the connection through the bus as an example. Among them:

[0227] The network interface 903 may be used for the network device 900 to communicate with other communication devices, such as other network devices. Specifically, the network interface 903 may be a wired interface.

[0228] The transceiver 905 can be used to perform transmission processing on the signals output by the processor 901, such as signal modulation. The transceiver 905 can also be used to perform reception processing on the mobile communication signals received by the antenna 908. For example, signal demodulation. In some embodiments of the present application, the transceiver 905 can be regarded as a wireless modem. In the network device 900, the number of transceivers 905 can be one or more. The antenna 908 can be used to convert the electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert the electromagnetic waves in free space into electromagnetic energy in the transmission line. The number of antennas 908 can be one or more.

[0229] The memory 902 can be coupled to the processor 901 through a bus 904 or an input / output port, or the memory 902 can also be integrated with the processor 901. The memory 902 is used to store various software programs and / or multiple sets of instructions or data. Specifically, the memory 902 can include high-speed random access memory, and can also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 902 can store an operating system (hereinafter referred to as the system), such as embedded operating systems like uCOS, VxWorks, RTLinux, etc. The memory 902 can also store a network communication program, which can be used to communicate with one or more additional devices, one or more user devices, and one or more network devices.

[0230] The processor 901 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of the present application. The processor can also be a combination that implements a determined function, such as a combination including one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.

[0231] In the embodiments of the present application, the processor 901 can be used to read and execute computer-readable instructions. Specifically, the processor 901 can be used to call a program stored in the memory 902, such as an implementation program of the resource reservation method provided by one or more embodiments of the present application on the network device 900 side, and execute the instructions included in the program.

[0232] It can be understood that the network device 900 can be Figure 1 the network device 101 in the system 100 of the resource reservation method shown, and can be implemented as a base station transceiver, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, an eNodeB, or a gNB, etc.

[0233] It should be noted that Figure 9 The network device 900 shown is merely one implementation manner of the embodiments of the present application. In practical applications, the network device 900 may further include more or fewer components, which are not limited herein. For the specific implementation of the network device 900, reference may be made to the relevant descriptions in the foregoing Figure 3 or Figure 5 method embodiments shown, which will not be elaborated herein.

[0234] In the case of dividing each function into corresponding function modules, Figure 10 FIG. shows a possible schematic logical structure of the user equipment involved in the above embodiments. The user equipment 1000 includes: a transceiver unit 1001 and a processing unit 1002. Exemplarily, the transceiver unit 1001 is used to support the user equipment to execute the steps of receiving information by the user equipment in the foregoing Figure 3 or Figure 5 method embodiments shown. The transceiver unit 1001 is further used to support the user equipment to execute the steps of sending information by the user equipment in the foregoing Figure 3 or Figure 5 method embodiments shown. The processing unit 1002 is used to support the user equipment to execute the steps of generating information by the user equipment in the foregoing Figure 3 or Figure 5 method embodiments shown, as well as other functions other than the functions of the transceiver unit 1001.

[0235] Optionally, the user equipment 1000 may further include a storage unit for storing code (program) or data. In one possible manner, the processing unit 1002 may call the code or data in the storage unit, so that the user equipment 1000 receives a resource reservation request message RRQ sent by the network device. The RRQ includes a first resource reservation request message RRQ1 and a second resource reservation request message RRQ2. The RRQ1 includes first duration information, and the first duration information is used to indicate that the network device occupies the target channel for a first duration. The RRQ2 is used to request the UE to transmit data with the network device within the first duration. The RRQ1 is scrambled with a first common identifier, and the RRQ2 is scrambled with the unique identifier corresponding to the UE. The first common identifier is an identifier known to the UE and at least one third-party device.

[0236] In terms of hardware implementation, the above processing unit 1002 may be a processor or a processing circuit, etc. The transceiver unit 1001 may be a transceiver or a transceiver circuit or an interface circuit, etc. The storage unit may be a memory. The above processing unit, transceiver unit, and storage unit may be integrated or separated.

[0237] Such as Figure 11As shown, it is a schematic diagram of a possible hardware structure of the user equipment involved in the above embodiments provided by the embodiments of the present application. As Figure 11 shown, the user equipment 1100 may include: an input / output module (such as an audio input / output module 1105, a key input module 1106, and a display 1107, etc.), a user interface 1108, one or more processors 1101, one or more transceivers 1102, one or more antennas 1103, and one or more memories 1104. These components may be connected through a bus or other means. Figure 11 Taking the connection through a bus as an example. Among them:

[0238] The antenna 1103 can be used to convert electromagnetic energy into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in a transmission line. The transceiver 1102 can be used to perform transmission processing on the signals output by the processor 1101, and can also be used to perform reception processing on the mobile communication signals received by the antenna 1103. In the embodiments of the present application, the transceiver 1102 can be regarded as a wireless modem. In the user equipment 1100, the number of transceivers 1102 can be one or more.

[0239] In addition to Figure 11 the transceiver 1102 shown, the user equipment 1100 may further include other communication components, such as a GPS module, a Bluetooth module, a wireless fidelity (Wi-Fi) module, etc. Not limited to the wireless communication signals described above, the user equipment 11000 may also support other wireless communication signals, such as satellite signals, shortwave signals, and so on. Not limited to wireless communication, the user equipment 1100 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.

[0240] The input / output module can be used to implement the interaction between the user equipment 1100 and the user / external environment, and may mainly include an audio input / output module 1105, a key input module 1106, and a display 1107, etc. Specifically, the input / output module may further include: a camera, a touch screen, and sensors, etc. Among them, the input / output modules communicate with the processor 1101 through the user interface 1108.

[0241] The memory 1104 can be coupled to the processor 1101 via a bus or an input / output port, or the memory 1104 can also be integrated with the processor 1101. The memory 1104 is used to store various software programs and / or multiple sets of instructions. Specifically, the memory 1104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1104 can store an operating system (hereinafter referred to as the system), such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory 1102110 can also store a network communication program, which can be used to communicate with one or more additional devices, one or more user devices, and one or more network devices. The memory 1104 can also store a user interface program, which can vividly display the content of an application through a graphical operation interface and receive control operations of the user on the application through input controls such as menus, dialog boxes, and buttons.

[0242] In the embodiments of the present application, the memory 1104 can be used to store an implementation program of the resource reservation method provided by one or more embodiments of the present application on the user device 1100 side. For the implementation of the resource reservation method provided by one or more embodiments of the present application, please refer to the foregoing embodiments.

[0243] The processor 1101 can be used to read and execute computer-readable instructions. Specifically, the processor 1101 can be used to call a program stored in the memory 1104, such as an implementation program of the resource reservation method provided by one or more embodiments of the present application on the user device 1100 side, and execute the instructions included in the program to implement the methods involved in the previous embodiments. The processor 1101 can support one or more of the following communications: Global System for Mobile Communications (GSM) (2G) communication, Wideband Code Division Multiple Access (WCDMA) (3G) communication, Long Term Evolution (LTE) (4G) communication, and 5G communication, etc. Optionally, when the processor 1101 sends any message or data, it specifically sends it by driving or controlling the transceiver 1102. Optionally, when the processor 1101 receives any message or data, it specifically receives it by driving or controlling the transceiver 1102. Therefore, the processor 1101 can be regarded as a control center for performing sending or receiving, and the transceiver 1102 is the specific executor of the sending and receiving operations.

[0244] It can be understood that the user device 1100 can beFigure 1 The user equipment 102 in the system 100 of the resource reservation method shown can be implemented as an eMTC device, a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, a user agent, a mobile client, etc.

[0245] It should be noted that Figure 11 The user equipment 1100 shown is only one implementation manner of the embodiments of the present application. In practical applications, the user equipment 1100 may further include more or fewer components, which are not limited here. For the specific implementation of the user equipment 1100, reference may be made to the relevant descriptions in the foregoing Figure 3 or Figure 5 method embodiments shown, which will not be elaborated here.

[0246] See Figure 12 , Figure 12 which shows a schematic structural diagram of a device provided by the present application. As Figure 12 shown, the device 1200 may include: a processor 1201, and one or more interfaces 1202 coupled to the processor 1201. Among them:

[0247] The processor 1201 can be used to read and execute computer-readable instructions. In specific implementation, the processor 1201 may mainly include a controller, an arithmetic unit, and registers. Among them, the controller is mainly responsible for instruction decoding and sending control signals for the operations corresponding to the instructions. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, etc., and can also perform address operations and conversions. The registers are mainly responsible for storing the register operands and intermediate operation results temporarily stored during the execution of instructions, etc. In specific implementation, the hardware architecture of the processor 1201 may be an application-specific integrated circuits (ASIC) architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced RISC machines (ARM) architecture, or an NP architecture, etc. The processor 1201 can be single-core or multi-core.

[0248] The interface 1202 can be used to input the data to be processed into the processor 1201, and can output the processing result of the processor 1201 outward. In a specific implementation, the interface 1202 can be a general purpose input output (GPIO) interface, and can be connected to multiple peripheral devices (such as a liquid crystal display (LCD), a camera, a radio frequency (RF) module, etc.). The interface 1202 can be connected to the processor 1201 through the bus 1203.

[0249] In this application, the processor 1201 can be used to call the implementation program of the resource reservation method provided by one or more embodiments of this application on the network device or the user equipment side from the memory, and execute the instructions included in the program. The memory can be integrated with the processor 1201. In this case, the memory is a part of the device 1200. Alternatively, the memory is an external component of the device 1200, and the processor 1201 calls the instructions or data stored in the memory through the interface 1202.

[0250] The interface 1202 can be used to output the execution result of the processor 1201. For the resource reservation method provided by one or more embodiments of this application, reference can be made to the foregoing embodiments, and details are not described herein again.

[0251] The above device 1200 can be a communication chip or a system on a chip (SoC).

[0252] It should be noted that the functions corresponding to the processor 1201 and the interface 1202 can be implemented through hardware design, can also be implemented through software design, or can be implemented through a combination of software and hardware, and there is no limitation here.

[0253] Another aspect of this application provides a resource reservation system, which includes one or more network devices and one or more user devices. Among them, the network device can be Figure 8 or Figure 9 the network device described above, and the user device can be Figure 10 or Figure 11 the device described above.

[0254] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present invention are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

[0255] In summary, the above are only the preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims

1. A resource reservation method, characterized in that, Including: A user equipment (UE) receives a resource reservation request message (RRQ) sent by a network device. The RRQ includes a first resource reservation request message (RRQ1) and a second resource reservation request message (RRQ2). The RRQ1 includes first duration information, which is used to indicate that the network device occupies a target channel for a first duration. The RRQ2 is used to indicate that the UE transmits data to the network device within the first duration. The RRQ1 is scrambled with a first common identifier, and the RRQ2 is scrambled with a unique identifier of the UE. The first common identifier is an identifier of the UE.

2. The method according to claim 1, wherein The RRQ2 indicates transmission resources and / or transmission parameters for the UE to transmit data.

3. The method according to claim 1, wherein The RRQ1 further includes a cell identifier (cellID).

4. The method according to any one of claims 1 to 3, characterized in that The RRQ1 is transmitted in a common search space (CSS), and the RRQ2 is transmitted in a specific search space (USS) corresponding to the UE.

5. The method according to any one of claims 1 to 3, characterized in that The first common identifier is a pre-defined radio network temporary identifier (RNTI); alternatively, the first common identifier is an RNTI notified by the network device to the UE through radio resource control (RRC) signaling or a system message; alternatively, the first common identifier is an RNTI calculated based on first information, where the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

6. The method according to any one of claims 1 to 3, characterized in that, The RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE needs to send a resource reservation response message (RRS) to the network device.

7. The method according to any one of claims 1 to 3, characterized in that, After the user equipment (UE) receives the resource reservation request message (RRQ) sent by the network device, it further includes: The UE sends an RRS to the network device. The RRS includes a first resource reservation response message (RRS1) and a second resource reservation response message (RRS2). The RRS2 is used to confirm to the network device that the UE transmits data to the network device.

8. The method according to claim 7, wherein The RRS1 is scrambled with a second common identifier, and the RRS2 is scrambled with a unique identifier of the UE.

9. The method according to claim 8, wherein The second common identifier is a pre-defined RNTI; alternatively, the second common identifier is an RNTI notified by the network device to the UE; alternatively, the second common identifier is an RNTI calculated based on second information, where the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

10. The method according to claim 7, characterized in that, The RRQ1 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS1; Alternatively, the frequency-domain resources used by the UE to transmit the RRS1 are the same as the frequency-domain resources used by the network device to transmit the RRQ1.

11. The method according to claim 7, wherein The RRQ2 includes indication information for indicating time-frequency resources and / or transmission parameters used by the UE to transmit the RRS2; Alternatively, the frequency-domain resources used by the UE to transmit the RRS2 are the same as the frequency-domain resources used by the network device to transmit the RRQ2; Alternatively, the RRQ1 includes indication information for indicating transmission parameters used by the UE to transmit the RRS2.

12. The method according to any one of claims 1-3, 8-11, characterized in that, The RRQ2 is a special RRQ2. The UE does not need to reply to the network device with a resource reservation response message RRS. The special RRQ2 includes indication information for indicating transmission resources and / or transmission parameters for the UE to transmit data with the network device.

13. A resource reservation method, characterized in that, including: The network device generates a resource reservation request message RRQ. The RRQ includes a first resource reservation request message RRQ1 and N second resource reservation request message RRQ2s. The RRQ1 includes first duration information for indicating that the network device occupies the target channel for a first duration. The N RRQ2s are respectively used to indicate that N user equipment UEs transmit data with the network device within the first duration. The N RRQ2s correspond to the N UEs one by one. N is an integer greater than or equal to 1. The network device sends the RRQ. Among them, the RRQ1 is scrambled with a first common identifier, and the N RRQ2s are respectively scrambled with unique identifiers of their corresponding UEs.

14. The method according to claim 13, wherein The RRQ2 indicates transmission resources and / or transmission parameters for the UE corresponding to the RRQ2 to transmit data.

15. The method according to claim 13, wherein The RRQ1 further includes a cell identifier cellID.

16. The method according to any one of claims 13 to 15, characterized in that The RRQ1 is transmitted in a common search space CSS, and the N RRQ2s are respectively transmitted in specific search spaces USSs of the UEs corresponding to the N UEs. The CSS is a search space known to the N UEs.

17. The method according to any one of claims 13 to 15, characterized in that, The first common identifier is a pre-defined radio network temporary identifier RNTI; alternatively, the first common identifier is an RNTI notified by the network device to the N UEs through radio resource control RRC signaling or system information; alternatively, the first common identifier is an RNTI calculated according to first information, and the first information includes one or more of a cell identifier, a system frame number, and a time slot number of the RRQ1.

18. The method according to any one of claims 13 to 15, characterized in that The RRQ1 and / or the RRQ2 further includes indication information for indicating whether the UE corresponding to the RRQ2 needs to send a resource reservation response message RRS to the network device.

19. The method according to any one of claims 13 to 15, characterized in that After the network device sends the RRQ, it further includes: The network device receives RRSs sent by M UEs among the N UEs. Each RRS among the M RRSs includes a first resource reservation response message RRS1 and a second resource reservation response message RRS2. The RRS2 is used to confirm to the network device that the UE corresponding to the RRS2 transmits data with the network device. M is a positive integer less than or equal to N.

20. The method according to claim 19, wherein The M RRS1s included in the M RRSs are all transmitted on the same time-frequency resource.

21. The method according to any one of claims 13 to 15 and 20, characterized in that, The M RRS2s included in the M RRSs are respectively transmitted on different time-frequency resources.

22. The method according to claim 17, wherein The M RRS1s are all scrambled with a second common identifier, and the M RRS2s are respectively scrambled with unique identifiers corresponding to the M UEs themselves.

23. The method according to claim 22, wherein The second common identifier is a pre-defined RNTI; or, the second common identifier is the RNTI notified by the network device to the M UEs; or, the second common identifier is an RNTI calculated according to second information, where the second information includes one or more of a cell identifier, a system frame number, a time slot number of the RRQ1, and a time slot number of the RRS1.

24. The method according to claim 19, wherein The RRQ1 includes indication information for indicating time-frequency resources and / or transmission parameters used by the N UEs to transmit the RRS1; Or, frequency domain resources used by the N UEs to transmit the RRS1 are the same as frequency domain resources used by the network device to transmit the RRQ1.

25. The method according to claim 19, wherein The N RRQ2s respectively include indication information for indicating time-frequency resources and / or transmission parameters used by corresponding UEs among the N UEs to transmit the RRS2 respectively; Or, frequency domain resources used by each of the N UEs to transmit its respective RRS2 are the same as frequency domain resources used by the RRQ2 corresponding to the UE among the N RRQ2s transmitted by the network device; Or, the RRQ1 includes indication information for indicating transmission parameters used by the N UEs to transmit the N RRS2s respectively.

26. The method according to any one of claims 13 to 15, 20, 22 - 25, characterized in that, The N RRQ2s include one or more special RRQ2s, and UEs corresponding to the special RRQ2s do not need to send a resource reservation response message RRS to the network device, and the special RRQ2 includes indication information for indicating transmission resources and / or transmission parameters for data transmission between the RRQ2-corresponding UE and the network device.

27. The method according to claim 19, wherein The network device receives RRS sent by M UEs among the N UEs, including: When a time domain resource used by the network device to send the RRQ is time slot n, the network device receives RRS sent by M UEs among the N UEs in time slot n + k, where n and n + k are time slot numbers, k is a pre-defined integer greater than or equal to zero, or k is an integer greater than or equal to zero indicated by the network device in the RRQ1 or RRQ2, or k is an integer greater than or equal to zero indicated by the network device through RRC signaling before sending the RRQ.

28. A user equipment UE, characterized in that, It includes a processor, a transceiver, and a memory. The memory is used to store program instructions, and the processor is used to execute the program instructions stored in the memory, so that the UE executes the method according to any one of claims 1-12.

29. A network device, characterized in that, It includes a processor, a transceiver, and a memory. The memory is used to store program instructions, and the processor is used to execute the program instructions stored in the memory, so that the network device executes the method according to any one of claims 13-27.

30. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a computer device, it can implement the method according to any one of claims 1-12.

31. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a computer device, it can implement the method according to any one of claims 13-27.

Images