WO2021036339A1

WO2021036339A1 - Communication method and apparatus in closed-loop application scene

Info

Publication number: WO2021036339A1
Application number: PCT/CN2020/089651
Authority: WO
Inventors: 胡丹; 官磊; 李胜钰; 马蕊香
Original assignee: 华为技术有限公司
Priority date: 2019-08-28
Filing date: 2020-05-11
Publication date: 2021-03-04
Also published as: CN112449421A; CN112449421B

Abstract

Provided in the present application are a communication method and apparatus in a closed-loop application scene, which are used to solve the problems of high signaling overhead, high communication delay, and the inability to ensure service quality caused by the application of the prior art to closed-loop data transmission. In the present application: a terminal device receives downlink data on a first time-frequency resource, determines a target uplink configuration authorization associated with the first time-frequency resource from among a plurality of configured uplink configuration authorizations, and uses the associated target uplink configuration authorization to communicate with a network device. Further, when the downlink data is decoded correctly, same directly triggers uplink data to be sent in the target uplink configuration authorization by using a configuration authorization mode, and ACK is no longer fed back. The configuration authorization is used for uplink data transmission to implicitly indicate HARQ feedback information, so that the signaling overhead of HARQ feedback may be reduced, the communication delay is reduced, and the quality of service is ensured.

Description

Communication method and device in closed loop application scenario

Cross-references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910804715.5, and the application name is "a communication method and device in a closed-loop application scenario" on August 28, 2019, the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of communication technology, and in particular to a communication method and device in a closed-loop application scenario.

Background technique

The International Telecommunication Union (ITU) will enhance mobile bandwidth (Enhanced Mobile Broadband, eMBB), ultra-reliable low-latency communication (URLLC), and mass machine-type communications (Massive Machine-type). Communications, mMTC) are defined as the three typical services of the fifth generation (5th Generation, 5G) mobile communication system.

Among them, URLLC is one of the three typical 5G services. The main application scenarios include: driverless, telemedicine, and Industrial Internet of Things (IIoT), etc. Closed-loop applications are important business application scenarios of IIoT. In In closed-loop applications, how network equipment and terminal equipment communicate is a current research hotspot. At present, downlink data is transmitted using downlink semi-persistent scheduling, and uplink data is transmitted using scheduling. If these existing technologies are applied to closed-loop application scenarios, This will lead to problems such as high signaling overhead, high communication delay, and inability to guarantee service quality.

Summary of the invention

The present application provides a communication method and device in a closed-loop application scenario to solve the problems of high signaling overhead, high communication delay, and inability to guarantee service quality caused by the application of the prior art to the closed-loop application scenario.

In the first aspect, the present application provides a communication method. The execution subject of the method may be a terminal device or a chip applied to the terminal device. In the following, the execution subject is a terminal device as an example for description. The terminal device can receive the first configuration information and the second configuration information from the network device. Among them, the first configuration information is used to configure downlink semi-persistent scheduling, and the second configuration information is used to configure N uplink configuration grants. The terminal device determines the first time-frequency resource according to the resource of the second downlink semi-persistent scheduling, and receives the first downlink data from the network device on the first time-frequency resource. The first downlink data may adopt downlink semi-persistent scheduling The terminal device determines the target uplink configuration grant associated with the first time-frequency resource among the N uplink configuration grants configured by the second configuration information, and determines the second time-frequency resource according to the target uplink configuration grant, and Communicate with the network device on the second time-frequency resource. In the above method, when the terminal device communicates with the network device, the downlink data is transmitted using the downlink semi-persistent scheduling resource, and the uplink data is transmitted using the target uplink configuration grant determined from multiple uplink configuration grants. No additional scheduling signaling is required. Effectively realize the closed-loop data transmission of uplink and downlink.

In a possible design, the first configuration information includes a first identifier, and the first identifier may be used to identify the downlink semi-persistent scheduling, and the terminal device may determine the first identifier in the second configuration information. Identifies a second identifier that meets the first preset rule. The terminal device determines that the uplink configuration authorization corresponding to the second identifier is the target uplink configuration authorization. In the above method, the terminal device can determine the target uplink configuration authorization associated with DL SPS according to the configuration identifier, eliminating the process of sending uplink scheduling signaling, saving control signaling overhead, reducing transmission delay, and improving the reliability of the closed-loop transmission system Sex.

In a possible design, the first configuration information includes a first transmission period of downlink data, and the terminal device determines in the second configuration information that the first transmission period meets a second preset rule for uplink The second transmission period of the data; the terminal device determines that the uplink configuration grant corresponding to the second transmission period is the target uplink configuration grant. Since in the prior art, the first configuration information already includes the transmission period of the downlink data, the second configuration information already includes the transmission period of the uplink data. It can be seen that in this design, there is no need to make any improvements to the first configuration information and the second configuration information in the prior art, and the terminal device can determine the target uplink configuration authorization. It has better compatibility with the existing technology and is easy to implement.

In a possible design, the first configuration information includes a third identifier, and the third identifier is used to identify the target uplink configuration authorization. The terminal device may determine the target uplink configuration grant associated with the first time-frequency resource according to the third identifier.

In a possible design, the first configuration information includes a first time domain offset. The terminal device may determine the second time unit according to the first time unit and the first time domain offset. The terminal device determines that the uplink configuration grant corresponding to the second time unit is the target uplink configuration grant. Wherein, the first time unit is a time unit corresponding to the first time-frequency resource, and the second time unit is a time unit corresponding to the second time-frequency resource.

In a possible design, the first configuration information includes a first frequency domain offset. The terminal device determines a second frequency domain unit according to the first frequency domain unit and the first frequency domain offset; the terminal device determines that the uplink configuration authorization corresponding to the second frequency domain unit is the target uplink configuration authorization. Wherein, the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is a frequency domain unit corresponding to the second time-frequency resource.

In a possible design, the first configuration information includes a first time domain offset and a first frequency domain offset. The terminal device determines the second time unit according to the first time unit and the first time domain offset; the terminal device determines the second frequency domain unit according to the first frequency domain unit and the first frequency domain offset; wherein, The first time unit is a time unit corresponding to the first time-frequency resource, the second time unit is a time unit corresponding to the second time-frequency resource, and the first frequency domain unit is the The frequency domain unit corresponding to the first time-frequency resource, the second frequency domain unit is the frequency domain unit corresponding to the second time-frequency resource; the terminal device determines the uplink configuration grant corresponding to the second time-frequency resource Configure authorization for the target uplink.

In a possible design, when the first downlink data is decoded correctly, the terminal device sends the first uplink data to the network device on the second time-frequency resource, and the network device no longer sends the first downlink data. Affirmative information. When the first downlink data is decoded incorrectly, the terminal device no longer sends a negative response to the first uplink data and the first downlink data to the network device. Wherein, the first uplink data is transmitted in an uplink configuration authorization mode. In the above manner, the terminal device implicitly indicates the HARQ feedback information by using the configuration authorization for uplink data transmission, which can reduce the signaling overhead of the HARQ feedback, reduce the communication delay, and ensure the quality of service.

In the second aspect, the present application provides a communication method. The execution subject of the method may be a network device or a chip applied to the network device. The following describes the example that the execution subject is a network device. The network device sends the first configuration information and the second configuration information to the terminal device. The first configuration information may be used to configure downlink semi-persistent scheduling, and the second configuration information may be used to configure N uplink configuration grants, where N is an integer greater than 1. The network device determines the first time-frequency resource according to the resources of the downlink semi-persistent scheduling, and sends the first downlink data on the first time-frequency resource, and the first downlink data is transmitted in a downlink semi-persistent scheduling manner. The network device determines the target uplink configuration grant associated with the first time-frequency resource among the N uplink configuration grants configured by the second configuration information. The network device determines the second time-frequency resource according to the target uplink configuration authorization, and communicates with the terminal device on the second time-frequency resource. In the above manner, the network device sends the first downlink data on the first time-frequency resource, and determines the target uplink configuration grant associated with the first time-frequency resource from the multiple configured uplink configuration grants, and uses the associated target uplink configuration grant Communicate with network equipment. The uplink communication process does not require additional scheduling by network equipment, reduces scheduling signaling overhead, reduces time delays in communication, and ensures service quality.

In a possible design, the first configuration information includes a first identifier, and the network device determines a second identifier that satisfies the first preset rule with the first identifier; the network device determines the uplink configuration authorization corresponding to the second identifier Configure authorization for the target uplink.

In a possible design, the first configuration information includes a first transmission period of downlink data, and the network device determines the second transmission period that meets a second preset rule with the first transmission period; the network device determines The uplink configuration grant corresponding to the second transmission period is the target uplink configuration grant.

In a possible design, the first configuration information includes a third identifier, and the third identifier is used to identify the target uplink configuration authorization, and the network device determines the connection with the first time according to the third identifier. Target uplink configuration authorization associated with frequency resources.

In a possible design, the first configuration information includes a first time domain offset, and the network device determines the second time unit according to the first time unit and the first time domain offset; The uplink configuration grant corresponding to the second time unit is the target uplink configuration grant. Wherein, the first time unit is a time unit corresponding to the first time-frequency resource, and the second time unit is a time unit corresponding to the second time-frequency resource;

In a possible design, the first configuration information includes a first frequency domain offset, and the network device determines the second frequency domain unit according to the first frequency domain unit and the first frequency domain offset; the network device determines The uplink configuration grant corresponding to the second frequency domain unit is the target uplink configuration grant. Wherein, the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is a frequency domain unit corresponding to the second time-frequency resource.

In a possible design, the first configuration information includes a first time domain offset and a first frequency domain offset, and the network device determines the second time according to the first time unit and the first time domain offset. Unit; the network device determines the second frequency domain unit according to the first frequency domain unit and the first frequency domain offset; wherein, the first time unit is the time unit corresponding to the first time-frequency resource, so The second time unit is a time unit corresponding to the second time-frequency resource, the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is a time unit corresponding to the first time-frequency resource. The frequency domain unit corresponding to the second time-frequency resource; the network device determines that the uplink configuration grant corresponding to the second time-frequency resource is the target uplink configuration grant.

In a possible design, the network device may receive the first uplink data from the terminal device on the second time-frequency resource, and the first uplink data is transmitted in an uplink configuration authorization manner.

In a possible design, when the first uplink data is successfully detected, the network device determines that the first downlink data is successfully decoded by the terminal device; and/or, when the first uplink data is not successfully detected For the first uplink data, the network device determines that the first downlink data has not been successfully decoded by the terminal device. In the above manner, if the network device successfully detects the first uplink data, it is equivalent to the network device receiving the ACK feedback of the first downlink data. If the network device fails to detect the first uplink data, it is equivalent to the network device receiving the NACK feedback of the first downlink data. It can be seen that the first uplink data can implicitly indicate the HARQ feedback of the first downlink data, eliminating HARQ signaling overhead, reducing transmission delay, and ensuring communication quality.

In a third aspect, a communication device is provided, and the beneficial effects can be referred to the description of the first aspect and will not be repeated here. The communication device has the function of realizing the behavior in the method example of the first aspect described above. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. In a possible design, the communication device includes: a transceiving module, configured to receive first configuration information and second configuration information from a network device, the first configuration information is used to configure downlink semi-persistent scheduling, and the first configuration information is used to configure downlink semi-persistent scheduling. The second configuration information is used to configure N uplink configuration grants, where N is an integer greater than 1. The transceiver module is also used to receive first downlink data on the first time-frequency resource, and the first downlink data uses downlink For transmission in a semi-persistent scheduling manner, the first time-frequency resource is determined according to the resources of the downlink semi-persistent scheduling; a processing module is configured to determine a target uplink configuration grant associated with the first time-frequency resource; the processing The module is also used to communicate with the network device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration authorization. These modules can perform the corresponding functions in the above-mentioned method examples of the first aspect. For details, please refer to the detailed description in the method examples, which will not be repeated here.

In the fourth aspect, a communication device is provided, and the beneficial effects can be referred to the description of the second aspect and will not be repeated here. The communication device has the function of realizing the behavior in the method example of the second aspect described above. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. In a possible design, the communication device includes: a transceiver module, configured to send first configuration information and second configuration information to a terminal device, the first configuration information is used to configure downlink semi-persistent scheduling, and the second The configuration information is used to configure N uplink configuration grants, where N is an integer greater than 1. The transceiver module is also used to send first downlink data on the first time-frequency resource, and the first downlink data uses the downlink half. Transmission in a continuous scheduling mode, the first time-frequency resource is determined according to the first configuration information; a processing module, configured to determine a target uplink configuration grant associated with the first time-frequency resource, the target uplink configuration grant One of the N uplink configuration grants; the processing module is further configured to communicate with the terminal device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration grant. These modules can perform the corresponding functions in the method example of the second aspect. For details, please refer to the detailed description in the method example, which will not be repeated here.

In a fifth aspect, a communication device is provided. The communication device may be the terminal device in the foregoing method embodiment, or a chip set in the terminal device. The communication device includes a communication interface, a processor, and optionally, a memory. The memory is used to store a computer program or instruction, and the processor is coupled with the memory and a communication interface. When the processor executes the computer program or instruction, the communication device executes the method executed by the terminal device in the foregoing method embodiment.

In a sixth aspect, a communication device is provided. The communication device may be the network device in the foregoing method embodiment, or a chip set in the network device. The communication device includes a communication interface, a processor, and optionally, a memory. The memory is used to store a computer program or instruction, and the processor is coupled with the memory and a communication interface. When the processor executes the computer program or instruction, the communication device executes the method executed by the network device in the foregoing method embodiment.

In a seventh aspect, a computer program product is provided. The computer program product includes: computer program code, which when the computer program code is running, causes the methods executed by the terminal device in the above aspects to be executed.

In an eighth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code is executed, the method executed by the network device in the above aspects is executed.

In a ninth aspect, the present application provides a chip system, which includes a processor, configured to implement the functions of the terminal device in the methods of the foregoing aspects. In a possible design, the chip system further includes a memory for storing program instructions and/or data. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a tenth aspect, the present application provides a chip system, which includes a processor, and is configured to implement the functions of the network device in the methods of the foregoing aspects. In a possible design, the chip system further includes a memory for storing program instructions and/or data. The chip system can be composed of chips, and can also include chips and other discrete devices.

In an eleventh aspect, the present application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed, the method executed by the terminal device in the above aspects is implemented.

In a twelfth aspect, this application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed, the method executed by the network device in the above aspects is implemented.

Description of the drawings

FIG. 1 is a schematic diagram of a possible communication architecture in an embodiment of this application;

2 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 3 is a schematic diagram of a possible time unit in an embodiment of this application;

4 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 5 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 6 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 7 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 8 is a schematic diagram of a possible communication method in a closed-loop communication scenario in an embodiment of this application;

FIG. 9 is a schematic diagram of a communication device 900 in an embodiment of the application;

FIG. 10 is a schematic diagram of a communication device 1000 in an embodiment of this application.

detailed description

As shown in FIG. 1, it is a schematic diagram of a possible network architecture to which the embodiment of this application is applicable, including a terminal device 110 and an access network device 120. The terminal device 110 and the access network device 120 can communicate through the Uu air interface, which can be understood as a universal UE to network interface between the terminal device and the network device. Uu air interface transmission includes uplink transmission and downlink transmission.

For example, uplink transmission refers to the terminal device 110 sending uplink information to the access network device 120. The uplink information may include one or more of uplink data information, uplink control information, and reference signals (RS). The channel used to transmit uplink information is called an uplink channel, and the uplink channel may be a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH). The PUSCH is used to carry uplink data, and the uplink data may also be referred to as uplink data information. The PUCCH is used to carry uplink control information (uplink control information, UCI) fed back by the terminal device. UCI may include channel state information (channel state information, CSI), acknowledgement (acknowledgement, ACK)/negative acknowledgement (negative acknowledgement, NACK), etc.

For example, downlink transmission refers to the access network device 120 sending downlink information to the terminal device 110. The downlink information may include one or more of downlink data information, downlink control information, and downlink reference signals. The downlink reference signal may be a channel state information reference signal (CSI-RS) or a phase tracking reference signal (PTRS). The channel used to transmit downlink information is called a downlink channel, and the downlink channel may be a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH). The PDCCH is used to carry downlink control information (DCI), the PDSCH is used to carry downlink data, and the downlink data may also be referred to as downlink data information.

Optionally, in the network architecture shown in FIG. 1, a core network device 130 may also be included. The terminal device 110 may be connected to the access network device 120 in a wireless manner, and the access network device 120 may be connected to the core network device 130 in a wired or wireless manner. The core network device 130 and the access network device 120 may be separate and different physical devices, or the core network device 130 and the access network device 120 may be the same physical device, and the core network device 130 and the access network device 120 are integrated on the physical device. All/part of the logic functions of the networked device 120.

It should be noted that in the network architecture shown in FIG. 1, the terminal device 110 may be a fixed location or may be movable, which is not limited. The network architecture shown in FIG. 1 may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not limited. In the architecture shown in Figure 1, the number of terminal equipment, access network equipment, and core network equipment is not limited.

The technical solutions in the embodiments of the present application can be applied to various communication systems. For example, long-term evolution (LTE) systems, fifth generation (5G) mobile communication systems, and future mobile communication systems.

Based on the network architecture provided in Figure 1, the closed-loop application scenarios in IIoT are described below. The network device in this application scenario may be the access network device 120 in FIG. 1, and the terminal device may be the terminal device 110 in FIG. 1. As shown in Figure 2, the closed-loop application process may include:

S200: The network device sends downlink data to the terminal device, where the downlink data may instruct the terminal device to perform corresponding processing. A possible closed-loop application scenario of industrial automation: the terminal device is a robotic arm, and the downlink data instructs the robotic arm to execute a specific command, for example, adjust the angle of the robotic arm downward by 5 degrees.

S201: The terminal device performs corresponding processing according to the instruction of the downlink data. Still using the above example, the terminal device is a robotic arm, the downlink data indicates that the angle of the robotic arm is adjusted downward by 5 degrees, and the robotic arm can adjust the angle according to the instructions of the downlink data. It should be noted that in practical applications, due to processing errors of the robotic arm, the actual adjustment angle of the robotic arm may be greater than 5 degrees, or less than 5 degrees, or exactly 5 degrees.

S202: The terminal device sends uplink data to the network device, where the uplink data carries information such as the actual processing result of the terminal device.

It can be known from the description in S201 that the terminal device can perform corresponding processing according to the instruction of the downlink data to obtain the actual processing result. Further, in S202, the terminal device may generate uplink data according to the actual processing result. For example, the actual processing result may be carried in the uplink data. The terminal device sends uplink data to the network device. Still using the example in S202 above, the actual processing result of the robotic arm is that the angle is adjusted downward by M degrees. The degree M may be carried in the uplink data and sent to the network device.

S203: The network device compares the actual processing result of the terminal device with the expected processing result. If the two are the same, the process ends. If the two are different, return to S200 to repeat the above process.

In the embodiment of the present application, after receiving the uplink data, the network device can obtain the actual processing result of the terminal device carried in the uplink data. The network device then compares the actual processing result of the terminal device with the expected processing result. If the two are the same, it can be considered that the current processing of the terminal device meets the conditions, and the process ends. If the two are different, it can be considered that the current processing of the terminal device does not meet the conditions, and continues to send downlink data, instructing the terminal device to perform the corresponding processing again. It should be noted that the expected processing result may be specifically the expected processing result of the terminal device when the network device sends the downlink data to the terminal device. For example, if the above example is still used, the network device sends downlink data to the robotic arm, instructing to adjust the angle of the robotic arm downward by 5 degrees, then the expected processing of the network device can be considered as a downward adjustment of 5 degrees.

Still using the above example, the network device sends downlink data to the robotic arm, and the downlink data can indicate that the angle of the robotic arm is adjusted downward by 5 degrees. After receiving the downlink data, the terminal device can adjust the angle according to the instruction of the downlink data. Due to processing errors and other reasons, although the network device instructs to adjust the angle of the robot arm down by 5 degrees, the robot arm actually only adjusts it down by 4 degrees. At this time, the robotic arm can send uplink data to the network device, and the uplink data can indicate that the robotic arm is actually adjusted by only 4 degrees. After receiving the uplink data, the network device can compare the processing result of the robot arm adjusted only by 4 degrees with the expected processing result of the robot arm adjusted by 5 degrees. If the two do not match, the network device continues to send the downlink data to the robot arm. Downlink data again instructs to adjust the angle of the robotic arm downward by 1 degree. Similar to the above process, if the network device finds that the actual processing result of the robotic arm is adjusted downward by 1 degree (accumulated 5 degrees), which is consistent with the expected processing result, the above process is ended. Otherwise, the network device continues to send downlink data, instructing the robotic arm to adjust the angle again.

It can be seen from the description of the flow in FIG. 2 that in a closed-loop application scenario, the downlink data triggers the transmission of the corresponding uplink data. In an example, the downlink data is transmitted based on a semi-persistent scheduling (SPS) method, and the uplink data is transmitted based on a grant based (GB) method. Wherein, when transmitting uplink data based on the scheduling method, the network device first sends the PDCCH for uplink scheduling to the terminal device. After receiving the PDCCH for uplink scheduling, the terminal device sends the uplink data according to the above-mentioned PDCCH scheduling. . The interaction process of the entire closed-loop application is complicated, the signaling overhead is large, and the service delay cannot be guaranteed.

Based on the foregoing, the present application provides a communication method. The principle of the method is to change the transmission mode of uplink data from a scheduling-based transmission to a scheduling-free transmission. In the scheduling-free transmission mode, the terminal device can transmit uplink data according to the configuration information, without additional scheduling by the network device. Thereby reducing the signaling overhead of the entire closed-loop application and ensuring service delay.

Some nouns or terms used in this application are explained below, and these nouns or terms are also part of the content of the invention.

1. Terminal equipment

A terminal device may be referred to as a terminal for short, also called a user equipment (UE), which is a device with a wireless transceiver function. Terminal devices can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on the water (such as ships, etc.); they can also be deployed in the air (such as airplanes, drones, balloons, and satellites, etc.). The terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, and a wireless terminal device in telemedicine. Terminal equipment, wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, and wireless terminal equipment in smart home. The terminal device can also be fixed or mobile. The embodiment of the present application does not limit this.

In the embodiments of the present application, the device used to implement the function of the terminal may be a terminal device; it may also be a device capable of supporting the terminal device to implement the function, such as a chip system, and the device may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. In the technical solutions provided by the embodiments of the present application, the device for implementing the functions of the terminal device is a terminal device as an example to describe the technical solutions provided by the embodiments of the present application.

2. Network equipment

The network device may be an access network device, and the access network device may also be referred to as a radio access network (radio access network, RAN) device, which is a device that provides wireless communication functions for terminal devices. The access network equipment includes, but is not limited to: next-generation base stations (generation nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), baseband unit (BBU), and transmitting and receiving points. point, TRP), transmitting point (transmitting point, TP), the base station in the future mobile communication system or the access point in the WiFi system, etc. The access network equipment can also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or a network The equipment can be a relay station, a vehicle-mounted device, and a network device in the future evolved PLMN network.

The terminal device can communicate with multiple access network devices of different technologies. For example, the terminal device can communicate with an access network device that supports long term evolution (LTE), or can communicate with an access network device that supports 5G. , It can also communicate with the access network equipment supporting LTE and the access network equipment supporting 5G at the same time. The embodiments of the present application are not limited.

In the embodiments of the present application, the device used to implement the function of the network device may be a network device; it may also be a device capable of supporting the network device to implement the function, such as a chip system, and the device may be installed in the network device. In the technical solutions provided in the embodiments of the present application, the device used to implement the functions of the network equipment is a network device as an example to describe the technical solutions provided in the embodiments of the present application.

3. Downlink (DL) semi-persistent scheduling (SPS)

DL SPS can be considered as a combination of scheduling-based downlink transmission and scheduling-free downlink transmission. The specific process may be: when the network device performs downlink transmission for the first time, the network device first sends a PDCCH for scheduling the terminal device to the terminal device, and the terminal device receives downlink data according to the scheduling of the PDCCH. Subsequently, the network device may send downlink data according to the pre-configured period P, and correspondingly, the terminal device receives the downlink data according to the pre-configured period P. The network equipment can realize multiple downlink data transmissions by sending one PDCCH, reducing signaling overhead.

4. Uplink (UL) configuration authorization (configured grant, CG)

The uplink configuration authorization means that the uplink transmission of the terminal equipment does not require the scheduling of the network equipment, and the terminal equipment performs the uplink transmission according to the configuration information. Uplink configuration authorized transmission is also called grant free (GF) or scheduling-free (scheduling-free) uplink transmission. There are two types of uplink configuration authorization, namely, type 1 uplink configuration authorization and type 2 uplink configuration authorization. The difference between the two is that all the parameters in the type 1 uplink configuration authorization are pre-configured by the network device. Therefore, when the terminal device uses the type 1 uplink configuration authorization to send uplink service data, it directly uses the parameters configured by the network device That's it, no additional scheduling information is needed. When the terminal device uses the type 2 uplink configuration to authorize the transmission of uplink service data, it needs to receive an additional trigger message to perform uplink data transmission.

For type 1 and type 2 uplink configuration authorizations, one or more of the following information can be pre-configured through high-level parameters: frequency hopping mode, demodulation reference signal (demodulation reference signal, DMRS) configuration, modulation and coding scheme (modulation) and coding scheme, MCS) form selection, frequency domain resource allocation method selection, PUSCH RBG size configuration selection, power control loop selection, open-loop power control parameters (including target signal-to-noise ratio and path loss compensation factor, etc.), automatic retransmission Request (hybrid automatic repeat request, HARQ) process number, retransmission times, redundancy version sequence, period, etc.

Further, for type 1 uplink configuration authorization, the above configuration information may include, in addition to one or more of the above information, time-frequency resource allocation, time domain offset, antenna port, precoding, number of layers , Sounding reference signal (SRS) resource indication, modulation order, target code rate, transmission block size, frequency hopping offset, path loss reference index, Beta-offset indication, etc.

For type 2 uplink configuration authorization, resource allocation obeys the configuration of the above-mentioned high-level parameters. In addition, the terminal device needs to receive trigger information before it can perform scheduling-free transmission.

Five, time unit

The time unit is the time domain unit used for data transmission, which can include radio frames, subframes, slots, mini-slots, and time domain symbols (symbol). Domain unit. In a 5G new radio (NR), a radio frame may include 10 subframes, and a subframe may include one or more time slots. The specific number of time slots included in a subframe is related to the subcarrier interval.

The frame structure parameter (numerology) may include sub-carrier spacing and/or cyclic prefix (CP) type, etc. CP type can also be called CP length, or CP for short. The CP type may be an extended CP or a normal CP. The next time slot of the extended CP may include 12 time domain symbols, and the next time slot of the normal CP may include 14 time domain symbols. Time domain symbols can be referred to simply as symbols. The time domain symbols can be orthogonal frequency division multiplexing (OFDM) symbols, or discrete fourier transform spread orthogonal frequency division multiplexing, DFT-s- OFDM) symbol. In the embodiments of the present application, the time domain symbol is an OFDM symbol as an example for description.

As shown in Table 1, in the NR system, 5 kinds of frame structure parameters can be supported, numbered from 0 to 4. For example, the frame structure parameter numbered 2 is: the sub-carrier interval is 60 kHz, and the CP is the normal CP or the extended CP.

Table 1 Supported frame structure parameters (numerologies)

There can be different slot lengths for different subcarrier intervals. For example, when the subcarrier interval is 15kHz, one time slot is 1 millisecond (millisecond, ms); when the subcarrier interval is 30kHz, one time slot is 0.5ms. Mini-slot, also called mini-slot, can be a unit smaller than a slot, and a mini-slot can include one or more symbols. For example, a mini-slot may include 2 symbols, 4 symbols, or 7 symbols. One slot may include one or more mini-slots.

As shown in Figure 3, taking the 15kHz subcarrier interval as an example, a radio frame can last for 10ms, and each subframe can last for 1ms. A radio frame includes 10 subframes, and each time slot lasts for 1ms. Each subframe can last for 1ms. Including 1 time slot, each time slot can include 14 symbols. Further, the mini-slot may include 4 symbols, 2 symbols, 7 symbols, and so on.

Six, frequency domain unit

The frequency domain unit may include one or more resource blocks (resources block, RB), resource element (resources element, RE), resource block group (resources block group, RBG), or resource element group (resource element group, REG). For example, the RBG may include one or more RBs, such as 6; the RB may include one or more REs, such as 12; the REG may include one time domain symbol in the time domain and one RB in the frequency domain.

Seven, high-level signaling

High-level signaling may refer to signaling sent by a high-level protocol layer, and the high-level protocol is at least one protocol layer above the physical layer. For example, the high-level protocol layer may include at least one of the following: medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) ) Layer, radio resource control (RRC) layer and non-access stratum (NAS).

In the embodiments of the present application, words such as “first” and “second” are only used for the purpose of distinguishing description, and cannot be understood as indicating or implying relative importance, nor as indicating or implying order. "At least one" means one or more, and "plurality" means two or more. "And/or" describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects before and after are in an "or" relationship. "The following at least one item (a)" or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a). For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c It can be single or multiple.

As shown in FIG. 4, an embodiment of the present application provides a schematic flowchart of a communication method. The method may be executed by a terminal device and a network device, or may also be executed by a chip in the terminal device and a chip in the network device. The network device in FIG. 4 may be the access network device 120 in FIG. 1 described above, and the terminal device may be the terminal device 110 in FIG. 1 described above. The method shown in FIG. 4 may include the following operations.

S401: The network device sends first configuration information to the terminal device, where the first configuration information is used to configure DL SPS resources. Correspondingly, the terminal device receives the first configuration information.

For example, the first configuration information may include one of the cycle K of DL SPS data transmission, the MCS table used by DL SPS, the PUCCH resource for transmitting HARQ feedback information of DL SPS, or the number of HARQ processes of DL SPS or Multiple.

S402: The network device sends second configuration information to the terminal device, where the second configuration information is used to configure N uplink configuration grants, where N is an integer greater than 1. Correspondingly, the terminal device receives the second configuration information.

For example, in the embodiment of the present application, the second configuration information may include N pieces of configuration information, and each piece of configuration information in the N pieces of configuration information is used to configure an uplink configuration authorization, that is, the N pieces of configuration information Used to configure N uplink configuration authorizations. Further, any one of the "N uplink configuration grants" may be a type 1 uplink configuration grant or a type 2 uplink configuration grant.

One possible application scenario is that network equipment can configure different uplink configuration authorizations for different types of services. For example, for a service with a longer period of data generation, you can configure a configuration authorization with a longer time interval; for example, for a service with a shorter period of data generation, you can configure a configuration authorization with a shorter time interval; for example, for a longer data block. For large services, larger time-frequency resources can be configured; for example, for services with smaller data blocks, smaller time-frequency resources can be configured.

S403: The network device sends first downlink data to the terminal device on the first time-frequency resource, and the first downlink data is transmitted in a DL SPS manner. Correspondingly, the terminal device receives the first downlink data on the first time-frequency resource. Wherein, the first time-frequency resource is determined according to downlink semi-persistent scheduling resources.

S404: The terminal device determines a target uplink configuration grant associated with the first time-frequency resource, where the target uplink configuration grant is one of N uplink configuration grants. The terminal device determining the target uplink configuration authorization associated with the first time-frequency resource may also be referred to as: the terminal device determining the target uplink configuration authorization associated with the DL SPS.

S405: The network device determines the target uplink configuration grant associated with the first time-frequency resource. The network device determining the target uplink configuration authorization associated with the first time-frequency resource may also be referred to as: the network device determining the target uplink configuration authorization associated with the DL SPS.

S406: The terminal device communicates with the network device on the second time-frequency resource. The second time-frequency resource is a time-frequency resource determined according to the target uplink configuration grant.

Specifically, when the first downlink data is decoded correctly, the terminal device sends the first uplink data to the network device on the second time-frequency resource, and does not send the first downlink data to the network device. For a positive response to the data, the first uplink data is transmitted in an uplink configuration authorization mode. When the first downlink data is decoded incorrectly, the terminal device does not send a negative response to the first uplink data and the first downlink data to the network device. Correspondingly, when the network device successfully detects the first uplink data, it is determined that the first downlink data is successfully decoded by the terminal device. When the first uplink data is not successfully detected, it is determined that the first downlink data has not been successfully decoded by the terminal device. It should be noted that when the network device successfully decodes the first uplink data, it can be considered that the first uplink data is successfully detected. When the network device fails to function to decode the first uplink data, it can be considered that the first uplink data is not successfully detected. Or, when the demodulation signal-to-noise ratio of the first uplink data is greater than or equal to the first threshold, it can be considered that the first uplink data is successfully detected. When the demodulated signal-to-noise ratio of the first uplink data is less than the first threshold, it can be considered that the first uplink data is not successfully detected.

It can be seen from the above that, in this embodiment of the application, the terminal device receives downlink data on the first time-frequency resource, and determines the target uplink configuration grant associated with the first time-frequency resource from the configured multiple uplink configuration grants, and uses all the uplink configuration grants associated with the first time-frequency resource. The associated target uplink configuration authorizes communication with the network device. Further, when the downlink data is decoded correctly, it directly triggers the uplink data to be sent in the target uplink configuration grant in the configuration grant mode, and no ACK is fed back. By using the configuration grant for uplink data transmission to implicitly indicate the HARQ feedback information, the signaling overhead of the HARQ feedback can be reduced, the communication delay is reduced, and the quality of service is guaranteed.

It should be noted that the sequential execution sequence in S401 to S406 in FIG. 4 is only an exemplary description, and is not intended to limit the application. For example, S404 can be executed before S405, and S404 can also be executed after S405, or S404 and S405 can be executed simultaneously.

Example one

The first configuration information in FIG. 4 above may include a first identification (identification, ID), and the first identification may be used to identify the DL SPS. Specifically, the first identifier may also be referred to as a first configuration identifier.

A specific implementation of the foregoing S404 may be: in the second configuration information, the terminal device determines a second identifier that satisfies the first preset rule with the first identifier. The second identification may also be referred to as a second configuration identification. The terminal device determines that the uplink configuration authorization corresponding to the second identifier is the target uplink configuration authorization. Wherein, the first preset rule may be: the first identifier is the same as the second identifier; or, the first identifier is in a multiple relationship with the second identifier; or, the result of the first identifier relative to the first value is the same as the second identifier. The result of the identification relative to the second value is the same; or, the first identification and the second identification are binary sequences, and the bitwise inversion of the first identification is the same as the second identification. The first value is predefined or pre-configured. The result of the first identifier relative to the first value may specifically be the result obtained by performing modulo, remainder, or quotient between the first identifier and the first value. The second value is predefined or pre-configured, and the result of the second identifier relative to the second value can be specifically the second identifier and the second value are modulo, remainder, or quotient, and the operation is obtained the result of. The first value and the second value can be equal or unequal. It can be understood that the above-mentioned first preset rule is only an exemplary description, and is not intended as a limitation to the present application.

As described in S402, the second configuration information may include N configuration information, which is specifically used to configure N uplink configuration grants. The terminal device may obtain the first identifier in the first configuration information. Then, among the N pieces of configuration information in the second configuration information, search for a second identifier that satisfies the first preset rule with the first identifier. Finally, the uplink configuration authorization corresponding to the second identifier is used as the target uplink configuration authorization.

A specific implementation of the foregoing S405 may be: the network device determines the second identifier that meets the first preset rule with the first identifier; the network device determines that the uplink configuration authorization corresponding to the second identifier is the target uplink configuration authorization.

For example, in the embodiments of this application, the "identification" is referred to as the "configuration identifier", the "first configuration information" is referred to as the "DL SPS configuration information", and the "uplink configuration grant" is referred to as the "UL GF". The "association relationship between the first time-frequency resource and the target uplink configuration grant" is referred to as "the association relationship between the DL SPS and the target UL GF" as an example, and the foregoing process is described in detail.

The configuration information of the DL SPS includes a parameter, and this parameter may be a configuration identifier, and the configuration identifier is used to distinguish the current DL SPS from other DL SPS. The second configuration information includes configuration information of N UL GFs, and the configuration information of each UL GF includes a parameter. This parameter may be a configuration identifier, and the configuration identifier is used to distinguish the current UL GF from other UL GFs. If the configuration identifier of the DL SPS and the configuration identifier of a UL GF meet the first preset rule, it can be determined that there is an association relationship between the DL SPS and the UL GF.

The following takes the same value of the configuration identifier of the DL SPS and the configuration identifier of the UL GF as an example for description. Assuming that the network device configures one DL SPS and two UL GFs for the terminal device, the configuration information of the DL SPS includes a configuration identifier with a value of 1. The two UL GFs are respectively the first UL GF and the second UL GF. Wherein, the configuration information of the first UL GF includes a configuration identifier with a value of 1; the configuration information of the second UL GF includes a configuration identifier with a value of 2. Since the configuration identifier of the DL SPS is the same as the configuration identifier of the first UL GF, it can be determined that the DL SPS and the first UL GF have an association relationship. Correspondingly, the network equipment and terminal equipment can use the first UL GF to perform closed-loop data transmission.

In this example, the terminal device can determine the target uplink configuration authorization associated with DL SPS according to the configuration identifier, eliminating the process of sending uplink scheduling signaling, saving control signaling overhead, reducing transmission delay, and improving closed-loop transmission System reliability.

Example two

The first configuration information in FIG. 4 may include a third identifier, and the third identifier is used to identify the target uplink configuration authorization. The third identifier may also be referred to as a configuration identifier.

A specific implementation of the foregoing S404 may be: the terminal device determines a target uplink configuration grant associated with the first time-frequency resource according to the third identifier.

A specific implementation of the foregoing S405 may be: the network device determines the target uplink configuration grant associated with the first time-frequency resource according to the third identifier.

For example, the network device may assign an identifier to each of the N uplink configuration authorizations, where the identifier is used to identify the corresponding uplink configuration authorization, and the N uplink configuration authorizations correspond to N identifiers in total. The network device determines a target uplink configuration authorization associated with downlink semi-persistent scheduling, and obtains an identifier corresponding to the target uplink configuration authorization. The identifier corresponding to the target uplink configuration authorization is the aforementioned third identifier. Finally, the third identifier is placed in the first configuration information of the downlink semi-persistent scheduling. Optionally, the first configuration information may further include a first identifier, and the first identifier is used to identify downlink semi-persistent scheduling. Finally, the first configuration information is sent to the terminal device through high-layer signaling. Correspondingly, after obtaining the first configuration information, the terminal device may obtain the third identifier from the first configuration information, and determine that the uplink configuration authorization identified by the third identifier is the above-mentioned target uplink configuration Authorization.

In the embodiment of this application, the terminal device can determine the target uplink configuration authorization corresponding to DL SPS according to the third identifier, eliminating the process of sending uplink scheduling signaling for uplink data corresponding to DL SPS, and saving control signaling overhead. Reduce the transmission delay and improve the system reliability of closed-loop transmission.

Example three

The first configuration information in FIG. 4 may include the first transmission period of the downlink data. The first transmission period is specifically: when the network device sends downlink data to the terminal device in DL SPS mode, the transmission of the downlink data cycle. The second configuration information may include N configuration authorization configuration information, and each configuration authorization configuration information includes one uplink data transmission period. If the first transmission period and the uplink data transmission period in the configuration information of a configuration authorization meet the second preset rule, it can be determined that there is an association relationship between the DL SPS and the configuration authorization. Correspondingly, the transmission period of the uplink data authorized by the configuration is recorded as the second transmission period.

A specific implementation of the above S404 may be: in the second configuration information, the terminal device determines the second transmission period that meets the second preset rule with the first transmission period; the terminal device determines that the uplink configuration authorization corresponding to the second transmission period is Target uplink configuration authorization. For example, the second preset rule may be that the first transmission period and the second transmission period are the same, or the first transmission period and the second transmission period are in a multiple relationship, and the multiple may be an integer multiple or a non-integer multiple, which is not limited. For a more detailed description of the second preset rule, refer to the previous definition of the first preset rule.

A specific implementation of the above S405 may be: in the second configuration information, the network device determines the second transmission period that meets the second preset rule with the first transmission period; the network device determines that the uplink configuration authorization corresponding to the second transmission period is Target uplink configuration authorization.

Specifically, the following description will be made by taking the second preset rule that the value of the first transmission period and the second transmission period are the same as an example. For example, the network device configures one DL SPS and two configuration grants for the terminal device, and the data transmission period of the DL SPS is 10 time slots. The second configuration information includes two configuration authorization configuration information, which are the configuration information of the first configuration authorization and the second configuration authorization, respectively. Wherein, the transmission period of the data authorized by the first configuration is 10 time slots; the transmission period of the data authorized by the second configuration is 20 time slots. Since the transmission period of the data of the DL SPS is the same as the transmission period of the data of the first configuration authorization, it can be determined that there is an association relationship between the DL SPS and the first configuration authorization. Correspondingly, the first configuration authorization is the target configuration authorization, and the transmission period of the data authorized by the first configuration is the second transmission period.

It is understandable that, in this example, in addition to using the data transmission period, the association between the downlink semi-persistent scheduling and the target uplink configuration grant is determined. The HARQ process number or redundancy version in the configuration information can also be used to determine the association relationship between the two.

For example, the first configuration information in FIG. 4 includes the first HARQ process number and the first HARQ process number of the downlink data, specifically: when the network device sends the downlink data to the terminal device in the DL SPS mode, the downlink data The HARQ process ID used. The second configuration information may include N configuration authorization configuration information, and each configuration authorization configuration information includes a HARQ process number of uplink data. If the first HARQ process number and the HARQ process number of the uplink data in the configuration information of a configuration grant satisfy the third preset rule, it can be determined that there is an association relationship between the DL SPS and the configuration grant. Correspondingly, the HARQ process ID used by the uplink data authorized by the configuration is marked as the second HARQ process ID.

A specific implementation of the above S404 may be: in the second configuration information, the terminal device determines the second HARQ process number that meets the third preset rule with the first HARQ process number; the terminal device determines the uplink corresponding to the second HARQ process number Configure authorization to configure authorization for the target uplink. The third preset rule may be: the first HARQ process ID is the same as the second HARQ process ID. Alternatively, the first HARQ process number and the second HARQ process number are in a multiple relationship, and the multiple may be an integer multiple or a non-integer multiple, which is not limited. For a more detailed description of the third preset rule, please refer to the previous definition of the first preset rule.

A specific implementation of the above S405 may be: in the second configuration information, the network device determines the second HARQ process number that meets the third preset rule with the first HARQ process number; the network device determines the uplink corresponding to the second HARQ process number Configure authorization to configure authorization for the target uplink.

Specifically, the following takes the third preset rule that the first HARQ process ID and the second HARQ process ID have the same value as an example for description. For example, the network device configures one DL SPS and two configuration authorizations for the terminal device, and the HARQ process number used by the DL SPS is 1. The second configuration information includes two configuration authorization configuration information, which are the configuration information of the first configuration authorization and the second configuration authorization, respectively. Wherein, the HARQ process number authorized by the first configuration is 1; the HARQ process number authorized by the second configuration is 0. Since the HARQ process number of the DL SPS is the same as the HARQ process number authorized by the first configuration, it can be determined that there is an association relationship between the DL SPS and the first configuration authorization. Correspondingly, the first configuration authorization is the target configuration authorization, and the HARQ process number authorized by the first configuration is the second HARQ process number.

For example, the first configuration information in FIG. 4 includes a first redundancy version of downlink data, and the first redundancy version is specifically: when a network device sends downlink data to a terminal device in a DL SPS mode, the downlink data The redundancy version used by the data. The second configuration information may include N configuration authorization configuration information, and each configuration authorization configuration information may include a redundant version of uplink data. If the fourth preset rule is satisfied between the first redundancy version and the redundancy version of the uplink data in the configuration information in a configuration authorization, it can be determined that there is an association relationship between the DL SPS and the configuration authorization. Correspondingly, the redundancy version of the uplink data authorized by the configuration is recorded as the second redundancy version.

A specific implementation of the above S404 may be: in the second configuration information, the terminal device determines the second redundancy version that meets the fourth preset rule with the first redundancy version; the terminal device determines the uplink corresponding to the second redundancy version Configure authorization to configure authorization for the target uplink. For example, the fourth preset rule may be that the first redundancy version is the same as the second redundancy version. For a more detailed description of the fourth preset rule, please refer to the previous definition of the first preset rule.

A specific implementation of the above S405 may be: in the second configuration information, the network device determines the second redundancy version that meets the fourth preset rule with the first redundancy version; the network device determines the uplink corresponding to the second redundancy version Configure authorization to configure authorization for the target uplink.

Specifically, the following takes the fourth preset rule that the first redundancy version is the same as the second redundancy version as an example for description. For example, a network device configures one DL SPS and two configuration authorizations for the terminal device, and the redundancy version of the DL SPS is redundancy version 1. The second configuration information includes two configuration authorization configuration information, which are the configuration information of the first configuration authorization and the second configuration authorization, respectively. Among them, the redundancy version authorized by the first configuration is 1, and the redundancy version authorized by the second configuration is 0. Since the redundancy version of the DL SPS is the same as the redundancy version of the first configuration authorization, it can be determined that there is an association relationship between the DL SPS and the first configuration authorization. Correspondingly, the first configuration authorization is the target configuration authorization, and the redundancy version of the first configuration authorization is the second redundancy version.

In the embodiment of this application, the terminal device can determine the target uplink configuration authorization corresponding to DL SPS according to the data transmission period, HARQ process number or redundancy version, and it is not necessary to send uplink scheduling signaling for the uplink data corresponding to DL SPS. The process saves control signaling overhead, reduces transmission delay, and improves the system reliability of closed-loop transmission.

Example four

The first configuration information in FIG. 4 above may include the first time domain offset. It is assumed that the value of the first time domain offset is P, P is a real number, and the unit of P may be a time domain symbol, a time slot, and a subframe. Or wireless frames, etc. In this application, the unit of the first time domain offset is described by taking a time domain symbol as an example.

A specific implementation of the foregoing S404 may be: the terminal device determines a second time unit according to the first time unit and the first time domain offset, and the first time unit is the location of the first time-frequency resource. Corresponding time unit, the second time unit is a time unit corresponding to the second time-frequency resource. The terminal device may determine that the uplink configuration grant corresponding to the second time unit is the target uplink configuration grant.

Specifically, the terminal device may determine the first time-frequency resource for receiving the first downlink data. According to the first time-frequency resource, the first time unit is determined in the time domain. Determine the second time unit according to the first time unit and the first time domain offset in the first configuration information. For example, taking the first time unit as a reference and performing offset according to the first time domain offset, the second time unit is obtained.

A specific implementation of the foregoing S405 may be: the network device determines the second time unit according to the first time unit and the first time domain offset. The network device may determine that the uplink configuration grant corresponding to the second time unit is the target uplink configuration grant.

Assume that the network device configures two uplink configuration grants for the terminal device, namely UL GF#1 and UL GF#2. Among them, there is a difference of p1 time domain symbols between the first time domain resource that can send uplink data in UL GF#1 and the time domain resource that can send downlink data in DL SPS. There is a difference of p2 time domain symbols between the first time domain resource that can send uplink data in UL GF#2 and the time domain resource that sends downlink data in DL SPS. If the value of the first time domain offset in the first configuration information is p2, the terminal device can determine that the target uplink configuration grant associated with the DL SPS is UL GF#2. If the value of the first time domain offset in the first configuration information is p1, the terminal device can determine that the target uplink configuration grant associated with the DL SPS is UL GF#1. Among them, both p1 and p2 are real numbers.

In the embodiment of this application, the terminal device can determine the target uplink configuration grant associated with the DL SPS according to the first time domain offset in the first configuration information, eliminating the need to send uplink scheduling signaling for the uplink data corresponding to the DL SPS The process saves control signaling overhead, reduces transmission delay, and improves the system reliability of closed-loop transmission.

Example 5

The first configuration information in FIG. 4 may include the first frequency domain offset. It is assumed that the value of the first frequency domain offset is Q, Q is a real number, and the unit of Q may be RE, REG, RB, or RBG. In this application, the unit of the first frequency domain offset is described by taking the RB as an example.

A specific implementation of the above S404 may be: the terminal device determines the second frequency domain unit according to the first frequency domain unit and the first frequency domain offset, and the first frequency domain unit is the frequency domain unit corresponding to the first time-frequency resource , The second frequency domain unit is a frequency domain unit corresponding to the second time-frequency resource. The terminal device determines that the uplink configuration grant corresponding to the second frequency domain unit is the target uplink configuration grant. Specifically, the terminal device may determine the first time-frequency resource for transmitting the first downlink data. According to the first time-frequency resource, the first frequency domain unit is determined in the frequency domain. According to the first frequency domain unit and the first frequency domain offset, the second frequency domain unit is determined. For example, the first frequency domain unit can be used as a reference, and the offset is performed according to the first frequency domain offset to obtain the second frequency domain unit.

A specific implementation of the foregoing S405 may be: the network device determines the second frequency domain unit according to the first frequency domain unit and the first frequency domain offset. The network device determines that the uplink configuration grant corresponding to the second frequency domain unit is the target uplink configuration grant.

Assume that the network device configures two uplink configuration grants for the terminal device, namely UL GF#1 and UL GF#2. Wherein, there is a difference of q1 RBs between the frequency domain resource for sending uplink data on UL GF#1 and the first frequency domain resource for sending downlink data in DL SPS. There is a difference of q2 RBs between the frequency domain resources for sending uplink data in UL GF#2 and the frequency domain resources for sending downlink data in DL SPS. If the value of the first frequency domain offset in the first configuration information is q1, the target uplink configuration grant associated with DL SPS is UL GF#1. If the value of the first frequency domain offset in the first configuration information is q2, the target uplink configuration grant associated with the DL SPS is UL GF#2. Among them, q1 and q2 are real numbers.

In the embodiment of this application, the terminal device can determine the target uplink configuration authorization associated with the DL SPS according to the first frequency domain offset in the first configuration information, eliminating the need to send uplink scheduling signaling for the uplink data corresponding to the DL SPS The process saves control signaling overhead, reduces transmission delay, and improves the system reliability of closed-loop transmission.

Example 6

The first configuration information in FIG. 4 may include the first time domain offset and the first frequency domain offset. It is assumed that the value of the first time domain offset is P, the value of the first frequency domain offset is Q, and P and Q are real numbers.

A specific implementation of the foregoing S404 may be: the terminal device determines the second time unit according to the first time unit and the first time domain offset. The first time unit is a time unit corresponding to a first time-frequency resource, and the second time unit is a time unit corresponding to a second time-frequency resource. The terminal device determines a second frequency domain unit according to the first frequency domain unit and the first frequency domain offset, where the first frequency domain unit is the frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is The domain unit is a frequency domain unit corresponding to the second time-frequency resource; the terminal device determines that the uplink configuration grant corresponding to the second time-frequency resource is the target uplink configuration grant.

A specific implementation of the above S405 may be: the network device determines the second time unit according to the first time unit and the first time domain offset; the network device determines the second time unit according to the first frequency domain unit and the first frequency domain Offset, determine the second frequency domain unit. The terminal device determines that the uplink configuration grant corresponding to the second time-frequency resource is the target uplink configuration grant. The second time-frequency resource corresponds to the second time unit in the time domain, and corresponds to the second frequency domain unit in the frequency domain.

Assume that the network device configures two uplink configuration grants for the terminal device, UL GF#1 and UL GF#2. Among them, there is a difference of p1 time domain symbols between the time domain resources for sending uplink data in UL GF#1 and the time domain resources for sending downlink data in DL SPS, and the frequency domain resources for sending uplink data in UL GF#1 are compared with those in DL SPS. The frequency domain resources for sending downlink data differ by q1 RBs. There is a difference of p2 time domain symbols between the time domain resource for sending uplink data in UL GF#2 and the time domain resource for sending downlink data in DL SPS, and the frequency domain resource for sending uplink data in UL GF#2 is compared with the downlink data sent in DL SPS. The frequency domain resources of the data differ by q2 RBs. If the value of the first time domain offset in the first configuration information is p2 and the value of the first frequency domain offset is q2, the target uplink configuration grant associated with DL SPS is UL GF#2. If the value of the first time domain offset in the first configuration information is p1 and the value of the first frequency domain offset is q1, the target uplink configuration grant associated with the DL SPS is UL GF#1. Among them, p1, p2, q1, and q2 are all real numbers.

In the embodiment of this application, the terminal device can determine the target uplink configuration authorization associated with DL SPS according to the first time domain offset and the first frequency domain offset in the first configuration information, and the uplink corresponding to DL SPS is omitted. The process of data sending uplink scheduling signaling saves control signaling overhead, reduces transmission delay, and improves the system reliability of closed-loop transmission.

In the embodiment of the present application, the establishment of an association relationship between a DL SPS and an uplink configuration authorization is taken as an example for description. It is understandable that, by using the method shown in the above-mentioned process in FIG. 4, an association relationship between one DL SPS and multiple uplink configuration grants can also be established. Correspondingly, the number of target uplink configuration authorizations in the process of FIG. 4 is multiple. For example, a specific implementation may be: the first configuration information includes three time domain offsets, which are p1, p2, and p3, and the terminal device can determine the p1 time domain symbol and p2 time domain symbol after DL SPS PDSCH transmission. The corresponding UL GF of the time domain symbols and the p3th time domain symbol are associated with the DL SPS. Alternatively, a specific implementation may be: the first configuration information includes the frequency domain offset q1 and a fourth identifier, where the fourth identifier is used to identify the first UL GF associated with the DL SPS. After receiving the first configuration information, the terminal device may determine the first UL GF according to the fourth identifier, and determine the second UL GF according to the frequency domain offset q1. The DL SPS is associated with the first UL GF and the second UL GF. In the embodiment of the present application, when an association relationship between a DL SPS and multiple uplink configuration grants is established, a closed-loop application of downlink transmission and multiple uplink transmissions can be formed.

Alternatively, by using the method shown in the above flow chart in Figure 4, an association relationship between multiple DL SPSs and a target uplink configuration authorization can also be established. Correspondingly, the number of DL SPS in the process of FIG. 4 is multiple. For example, when a network device transmits DL SPS PDSCH on multiple time-frequency resources, the multiple time-frequency resources correspond to the same UL GF. The terminal equipment transmits the UL GF PUSCH on the time-frequency resource corresponding to the above UL GF. For example, suppose that DL SPS#1, DL SPS#2, DL SPS#3, and UL GF#1 all have an association relationship. When the network device sends the PDSCH on DL SPS#1, DL SPS#2, DL SPS#3, the terminal device sends the PUSCH on UL GF#1. In the embodiment of the present application, when multiple DL SPS and one UL GF are established, a closed-loop application of multiple downlink transmissions and one uplink transmission can be formed.

The embodiment of this application provides an application scenario. When the method of the embodiment of this application is used to establish an association relationship between a DL SPS and a UL GF, or establish an association relationship between multiple DL SPSs and a UL GF, or establish one The association relationship between the DL SPS and multiple UL GFs. After that, the UL GF with which the association relationship is established can only be used for closed-loop uplink transmission, and cannot be used for other uplink transmissions.

For example, in the embodiment of the present application, a closed-loop application is provided, in which the DL SPS mode is used for downlink transmission, the GB mode is used for uplink transmission, and HARQ feedback is sent. As shown in Figure 5, a complete closed-loop application process may include: a network device sends downlink data to a terminal device, and the downlink data may be sent in the SPS PDSCH. After receiving the downlink data, the terminal device sends HARQ feedback to the network device. Specifically, if the downlink data is decoded correctly, the HARQ feedback is ACK. If the downlink data is decoded incorrectly, the HARQ feedback is NACK. The network device sends an uplink schedule (UL-Grant) to the terminal device, and the terminal device sends uplink data to the network device according to the uplink schedule of the network device, and the uplink data can be sent in the PUSCH.

It can be seen from the above records that in the closed-loop application of the above example, a complete closed-loop application process includes "downlink data, HARQ feedback, uplink authorization, and uplink data". There are many interactions in the entire closed-loop application, high signaling overhead, and high communication delay.

As an example, the communication method provided in FIG. 4 is used to provide a closed-loop application in which the DL SPS mode is used for downlink transmission, the target uplink configuration authorization is used for uplink transmission, and the HARQ feedback link is skipped. As shown in Figure 6, a complete closed-loop application process may include: the network device sends downlink data to the terminal device, the downlink data is transmitted in the DL SPS mode, and the downlink data can be sent in the PDSCH. After receiving the downlink data, the terminal device sends the uplink data to the network device if the decoding of the downlink data is correct. If the downlink data is decoded incorrectly, no more uplink data is sent to the network device. The uplink data can be transmitted in a standard uplink configuration grant mode, and the uplink data can be sent in the PUSCH.

In the embodiment of this application, comparing the closed-loop application shown in FIG. 5 with the closed-loop application shown in FIG. 6, it can be found that: in the closed-loop application shown in FIG. 5, four interactions between the network device and the terminal device are required However, in the closed-loop application shown in Figure 6, only two interactions are required between the network device and the terminal device, which reduces the communication delay and ensures the reliability of the service. At the same time, in the closed-loop application shown in Figure 6, there is no need to send HARQ feedback, uplink scheduling and other signaling, which saves signaling overhead.

As shown in FIG. 7, an embodiment of the present application provides a schematic flowchart of a communication method. The communication method may be executed by a terminal device and a network device, or may also be executed by a chip in the terminal device and a chip in the network device. The network device in FIG. 7 may be the access network device 120 in FIG. 1, and the terminal device may be the terminal device 110 in FIG. 1. The method shown in FIG. 7 includes the following operations.

S700: The network device sends fourth configuration information to the terminal device, where the fourth configuration information indicates a transmission parameter of downlink data. Correspondingly, the terminal device receives the fourth configuration information.

The fourth configuration information may include the first type of information, that is, information related to PDSCH. The first type of information includes one or more of the following parameters: frequency domain resource indication information, time domain resource indication information, virtual resource block to physical resource block mapping type, physical resource block binding size, MCS, new data indication , Redundancy version, initialization information of demodulation reference signal, antenna port number, carrier indication information, bandwidth part indication information or transmission configuration indication (TCI). The fourth configuration information may also include second type information, and the second type information includes one or more of the following parameters: hybrid automatic repeat request, HARQ process number or data allocation information, etc.

S701: The network device sends a PDSCH to the terminal device according to the transmission parameters of the downlink data, where the PDSCH includes control information. Correspondingly, the terminal equipment receives the PDSCH according to the transmission parameters of the downlink data.

The control information may include a third type of information, that is, information related to PUSCH. The third type of information may include one or more of the following parameters: carrier indication information, bandwidth part indication information, frequency domain resource indication information, time domain resource indication information, frequency domain frequency hopping indication, MCS, new data indication, redundancy The remaining version, hybrid automatic repeat request HARQ process number, precoding information layer number, PUSCH power control information, antenna port information, SRS resource indication information, SRS request information, channel state measurement information trigger or new data indication, etc. If the fourth configuration information in S800 includes the second type of information, the control information in S801 may not include the second type of information. If the fourth configuration information in S800 does not include the second type of information, the control information in S801 includes the second type of information.

Specifically, in the foregoing S800, the network device may send the fourth configuration information to the terminal device through high-level signaling. Correspondingly, the terminal device can determine the relevant parameters for PDSCH reception according to the fourth configuration information in the above S800. Compared with the manner in which the terminal device determines the relevant parameters for the PDSCH reception according to the scheduling of the network device, the network device does not need to send additional PDSCH scheduling information. Scheduling information, thereby reducing signaling overhead, reducing communication delay, and ensuring service quality.

S702: If the terminal device decodes the PDSCH correctly, it sends the PUSCH to the network device according to the control information included in the PDSCH, and no longer sends ACK feedback information to the network device.

In the embodiment of the present application, the terminal device may send the PUSCH to the network device according to the control information embedded in the PDSCH. Compared with the manner in which the terminal device sends the PUSCH according to the PDCCH scheduling, the signaling overhead can be reduced. At the same time, the data information and control information in the PDSCH are jointly coded to further improve the transmission efficiency.

S703: If the terminal device decodes the PDSCH incorrectly, it no longer sends PUSCH and NAKC feedback information to the network device.

For the operation of the terminal device in S702 and S703, the network device can perform PUSCH detection. If the network device successfully detects the PUSCH, it is determined that the terminal device has successfully decoded the PDSCH. If the network device fails to detect the PUSCH, it is determined that the terminal device has not successfully decoded the PUDSCH.

It can be seen from the above that, in the embodiment of the present application, when the PDSCH decoding is correct, the uplink data transmission of the PUSCH is directly triggered, and the AKC is no longer fed back. The HARQ feedback information is implicitly indicated through uplink data transmission, which reduces the signaling overhead of HARQ feedback, reduces communication delay, and ensures service quality.

Optionally, before the foregoing S700, it may further include: the terminal device detects the DMRS. If the DMRS is detected, the terminal device executes the step of receiving the fourth configuration information in S700. Otherwise, the process ends.

When the process shown in FIG. 7 is applied to a closed-loop application, a complete closed-loop application process may include: a network device sends a PDSCH to a terminal device, and the control information of the PDSCH is embedded in the control information of the PUSCH. The terminal device sends the PUSCH to the network device according to the control information of the PUSCH. In the entire closed-loop application process, only PDSCH and PUSCH are transmitted, without sending uplink scheduling and HARQ feedback, which saves signaling overhead, reduces transmission delay, and ensures service reliability.

As shown in FIG. 8, an embodiment of the present application provides a schematic flowchart of a communication method. The method may be executed by a terminal device and a network device, or may also be executed by a chip in the terminal device and a chip in the network device. The network device in FIG. 8 may be the access network device 120 in FIG. 1, and the terminal device may be the terminal device 110 in FIG. 1. The method shown in Fig. 8 includes the following operations.

S800: The network device sends the first configuration information to the terminal device. Correspondingly, the terminal device receives the first configuration information.

S801: The network device sends second configuration information to the terminal device. Correspondingly, the terminal device receives the second configuration information. For the first configuration information and the second configuration information, reference may be made to the record in the process shown in FIG. 4, which will not be described here.

S802: The terminal device determines the association relationship between the DL SPS and the target uplink configuration authorization according to the first configuration information, or according to the first configuration information and the second configuration information. For the specific implementation process of S802, refer to the related description of S404.

S803: The network device determines the association relationship between the DL SPS and the target uplink configuration authorization according to the first configuration information, or according to the first configuration information and the second configuration information. For the specific implementation process of S803, refer to the related description of S405.

S804: The terminal device performs data transmission with the network device according to the association relationship between the downlink semi-persistent scheduling and the target uplink configuration authorization. For the specific implementation process of S804, refer to the related descriptions of S403 and S406.

Optionally, the foregoing S800 and S801 may also be replaced with: the network device sends third configuration information. Correspondingly, the terminal device receives the third configuration information. The third configuration information is used to configure the association relationship between the downlink semi-persistent scheduling and the target uplink configuration grant. Correspondingly, the above S802 can also be replaced with: the terminal device determines the association relationship between the DL SPS and the target uplink configuration authorization according to the third configuration information. Assuming there are N uplink configuration grants, and N is a positive integer, the network device can determine that there is an association relationship between downlink semi-persistent scheduling and the i-th uplink configuration grant, where i is a positive integer less than or equal to N. The network device can configure the association relationship between the downlink semi-persistent scheduling and the i-th uplink configuration grant to the terminal device through the third configuration information.

In the above-mentioned embodiments provided by the present application, the methods provided by the embodiments of the present application are respectively introduced from the perspective of network equipment, terminal equipment, and interaction between the network equipment and the terminal equipment. In order to realize the functions in the methods provided in the above embodiments of the present application, the network equipment and the terminal equipment may include hardware structures and/or software modules, which are implemented in the form of hardware structures, software modules, or hardware structures plus software modules. . Whether a certain function of the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.

9 and 10 are schematic structural diagrams of possible communication devices provided by embodiments of this application. These communication devices can implement the functions of the terminal equipment or network equipment in the foregoing method embodiments, and therefore can also achieve the beneficial effects of the foregoing method embodiments. In the embodiment of the present application, the communication device may be the terminal device 110 shown in FIG. 1, or the access network device 120 shown in FIG. 1, or may be applied to the terminal device or the access network device. Module (such as chip).

As shown in FIG. 9, the communication device 900 includes a transceiver module 901 and a processing module 902. The communication device 900 may be used to implement the functions of the terminal device or the network device in the method embodiment shown in FIG. 4, FIG. 7 or FIG. 8.

When the communication device 900 is used to implement the function of the terminal device in the method embodiment shown in FIG. 4: the transceiver module 901 is configured to receive first configuration information and second configuration information from a network device, and the first configuration information is used for Configure downlink semi-persistent scheduling resources, the second configuration information is used to configure N uplink configuration grants, and the N is an integer greater than 1. The transceiver module 901 is further configured to receive first downlink data on a first time-frequency resource, where the first downlink data is transmitted using a downlink semi-persistent scheduling mode, and the first time-frequency resource is based on the downlink semi-persistent The scheduled resources are determined. The processing module 902 is configured to determine a target uplink configuration grant associated with the first time-frequency resource, where the target uplink configuration grant is one of the N uplink configuration grants. The processing module 902 is configured to control the transceiver module 901 to communicate with the network device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration authorization.

When the communication device 900 is used to implement the function of the network device in the method embodiment shown in FIG. 4: the transceiver module 901 is used to send the first configuration information and the second configuration information to the terminal device; the first configuration information is used for configuration For downlink semi-persistent scheduling resources, the second configuration information is used to configure N uplink configuration grants, and the N is an integer greater than 1. The transceiver module 901 is further configured to send first downlink data on a first time-frequency resource, where the first downlink data is transmitted using a downlink semi-persistent scheduling mode, and the first time-frequency resource is based on the downlink semi-persistent The scheduled resource is determined; a processing module 902, configured to determine a target uplink configuration grant associated with the first time-frequency resource, where the target uplink configuration grant is one of the N uplink configuration grants; a processing module 902, It is also used to control the transceiver module 901 to communicate with the terminal device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration authorization.

When the communication device 900 is used to implement the function of the terminal device in the method embodiment shown in FIG. 7: the transceiver module 901 is configured to receive fourth configuration information sent by the network device, where the fourth configuration information indicates the transmission parameter of the downlink data. The processing module 902 is configured to receive the PDSCH according to the transmission parameters of the downlink data, and the PDSCH carries the control information of the PUSCH. The transceiver module 901 is also used to control the transceiver module 901 to send the PUSCH to the network device according to the control information when the PDSCH decoding is correct, and control the transceiver module 901 to no longer send ACK feedback information to the network device. Or, when the PDSCH decoding error occurs, the transceiver module 901 is controlled to no longer send PUSCH and NACK feedback information to the network device.

When the communication device 900 is used to implement the function of the network device in the method embodiment shown in FIG. 7: the transceiver module 901 is configured to send fourth configuration information to the terminal device, where the fourth configuration information indicates the transmission parameter of the downlink data. The processing module 902 is configured to control the transceiver module 901 to send the PDSCH to the terminal device according to the transmission parameters of the downlink data. Optionally, the processing module 902 is further configured to determine that the PUSCH has been successfully decoded by the terminal device when the PDSCH is successfully detected; otherwise, determine that the PUSCH has not been successfully decoded by the terminal device.

When the communication device 900 is used to implement the function of the terminal device in the method embodiment shown in FIG. 8: the transceiver module 901 is configured to receive the first configuration information and the second configuration information sent by the network device. The processing module 902 is configured to determine the association relationship between the DL SPS and the target uplink configuration authorization according to the first configuration information, or according to the first configuration information and the second configuration information. The processing module 902 is further configured to perform data transmission with the network device according to the association relationship between the DL SPS and the target uplink configuration authorization.

When the communication device 900 is used to implement the function of the network device in the method embodiment shown in FIG. 8: the transceiver module 901 is used to send the first configuration information and the second configuration information to the terminal device. The processing module 902 is configured to determine the association relationship between the DL SPS and the target uplink configuration authorization according to the first configuration information, or according to the first configuration information and the second configuration information. The processing module 902 is further configured to perform data transmission with the terminal device according to the association relationship between the DL SPS and the target uplink configuration authorization.

For a more detailed description of the foregoing transceiver module 901 and processing module 902, reference may be made to the relevant description in the foregoing method embodiment, which will not be described here.

As shown in FIG. 10, the communication device 1000 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are coupled with each other. It can be understood that the interface circuit 1020 may be a transceiver or an input/output interface. Optionally, the communication device 1000 may further include a memory 1030 for storing instructions executed by the processor 1010 or storing input data required by the processor 1010 to run the instructions or storing data generated after the processor 1010 runs the instructions.

When the communication device 1000 is used to implement the method in the foregoing method embodiment, the processor 1010 is used to perform the function of the foregoing processing module 902, and the interface circuit 1020 is used to perform the function of the foregoing transceiver module 901.

When the foregoing communication device is a chip applied to a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment. The terminal device chip receives information from other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or antenna). The antenna) sends information, which is sent from the terminal device to the network device.

When the foregoing communication device is a chip applied to a network device, the network device chip implements the function of the network device in the foregoing method embodiment. The network device chip receives information from other modules in the network device (such as radio frequency modules or antennas), and the information is sent by the terminal device to the network device; or, the network device chip sends information to other modules in the network device (such as radio frequency modules or antennas). The antenna) sends information, which is sent by the network device to the terminal device.

It is understandable that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (digital signal processors, DSP), and application-specific integrated circuits. (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

The method steps in the embodiments of the present application can be implemented by hardware, or can be implemented by a processor executing software instructions. Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or well-known in the art Any other form of storage medium. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in an access network device or terminal device. Of course, the processor and the storage medium may also exist as discrete components in the access network device or the terminal device.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on the computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a DVD; and it may also be a semiconductor medium, such as a solid state disk (SSD).

In the various embodiments of this application, if there are no special instructions and logical conflicts, the terms and/or descriptions between different embodiments are consistent and can be mutually cited. The technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

In this application, "at least one" refers to one or more, and "multiple" refers to two or more. "And/or" describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the associated object before and after is an "or" relationship; in the formula of this application, the character "/" indicates that the associated object before and after is a kind of "division" Relationship.

It can be understood that the various numerical numbers involved in the embodiments of the present application are only for easy distinction for description, and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, the order of execution of the processes should be determined by their functions and internal logic.

Claims

A communication method in a closed-loop application scenario, characterized in that it includes:

Receiving first configuration information from a network device, where the first configuration information is used to indicate resources for downlink semi-persistent scheduling;

Receiving second configuration information from the network device, where the second configuration information is used to indicate N uplink configuration grants, where N is an integer greater than 1;

Receiving first downlink data on a first time-frequency resource, where the first downlink data is transmitted in a downlink semi-persistent scheduling manner, and the first time-frequency resource is determined according to the resources of the downlink semi-persistent scheduling;

Determining a target uplink configuration grant associated with the first time-frequency resource, where the target uplink configuration grant is one of the N uplink configuration grants;

Communicate with the network device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration grant.
The method according to claim 1, wherein the first configuration information includes a first identifier, the first identifier is used to identify the downlink semi-persistent scheduling, and the determination is related to the first time-frequency resource The associated target uplink configuration authorization includes:

In the second configuration information, determine a second identifier that satisfies a first preset rule with the first identifier;

It is determined that the uplink configuration grant corresponding to the second identifier is the target uplink configuration grant.
The method of claim 1, wherein the first configuration information further includes a first transmission period of downlink data, and the determining a target uplink configuration grant associated with the first time-frequency resource includes:

In the second configuration information, determining a second transmission period of uplink data that meets a second preset rule with the first transmission period;

It is determined that the uplink configuration grant corresponding to the second transmission period is the target uplink configuration grant.
The method according to claim 1, wherein the first configuration information further comprises a third identifier, the third identifier is used to identify the target uplink configuration authorization, and the determination is related to the first time frequency Target uplink configuration authorization for resource association, including:

According to the third identifier, a target uplink configuration grant associated with the first time-frequency resource is determined.
The method of claim 1, wherein the first configuration information further includes a first time domain offset, and the determining a target uplink configuration grant associated with the first time-frequency resource includes:

Determine a second time unit according to the first time unit and the first time domain offset, where the first time unit is the time unit corresponding to the first time-frequency resource, and the second time unit is the The time unit corresponding to the second time-frequency resource;

It is determined that the uplink configuration grant corresponding to the second time unit is the target uplink configuration grant.
The method of claim 1, wherein the first configuration information further includes a first frequency domain offset, and the determining a target uplink configuration grant associated with the first time-frequency resource includes:

According to the first frequency domain unit and the first frequency domain offset, a second frequency domain unit is determined, where the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is The domain unit is a frequency domain unit corresponding to the second time-frequency resource;

Determine that the uplink configuration grant corresponding to the second frequency domain unit is the target uplink configuration grant.
The method according to claim 1, wherein the first configuration information further includes a first time domain offset and a first frequency domain offset, and the determining the target uplink associated with the first time-frequency resource Configure authorization, including:

Determine a second time unit according to the first time unit and the first time domain offset, where the first time unit is the time unit corresponding to the first time-frequency resource, and the second time unit is the The time unit corresponding to the second time-frequency resource;

According to the first frequency domain unit and the first frequency domain offset, a second frequency domain unit is determined, where the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is The domain unit is a frequency domain unit corresponding to the second time-frequency resource;

It is determined that the uplink configuration grant corresponding to the second time-frequency resource is the target uplink configuration grant.
The method according to any one of claims 1 to 7, wherein the communicating with the network device on the second time-frequency resource comprises:

When the first downlink data is decoded correctly, the first uplink data is sent to the network device on the second time-frequency resource, and the affirmation of the first downlink data is not sent to the network device In response, the first uplink data is transmitted in an uplink configuration authorization mode; and/or,

When the first downlink data is decoded incorrectly, not sending a negative response to the first uplink data and the first downlink data to the network device.
A communication method in a closed-loop application scenario, characterized in that it includes:

Sending first configuration information to the terminal device, where the first configuration information is used to indicate downlink semi-persistent scheduling resources;

Sending second configuration information to the terminal device, where the second configuration information is used to indicate N uplink configuration grants, where N is an integer greater than 1;

Sending first downlink data on a first time-frequency resource, where the first downlink data is transmitted in a downlink semi-persistent scheduling manner, and the first time-frequency resource is determined according to the resources of the downlink semi-persistent scheduling;

Determining a target uplink configuration grant associated with the first time-frequency resource, where the target uplink configuration grant is one of the N uplink configuration grants;

Communicate with the terminal device on a second time-frequency resource, where the second time-frequency resource is a time-frequency resource determined according to the target uplink configuration grant.
The method according to claim 9, wherein the first configuration information includes a first identifier, the first identifier is used to identify the downlink semi-persistent scheduling, and the second configuration information includes a second identifier , The determining the target uplink configuration grant associated with the first time-frequency resource includes:

Determine the second identifier that meets the first preset rule with the first identifier;

It is determined that the uplink configuration grant corresponding to the second identifier is the target uplink configuration grant.
The method according to claim 9, wherein the first configuration information further includes a first transmission period of downlink data, the second configuration information includes a second transmission period of uplink data, and the determination and the The target uplink configuration grant associated with the first time-frequency resource includes:

Determine the second transmission period that satisfies a second preset rule with the first transmission period;

It is determined that the uplink configuration grant corresponding to the second transmission period is the target uplink configuration grant.
The method according to claim 9, wherein the first configuration information further includes a third identifier, the third identifier is used to identify the target uplink configuration authorization, and the determination is related to the first time frequency Target uplink configuration authorization for resource association, including:

According to the third identifier, a target uplink configuration grant associated with the first time-frequency resource is determined.
The method according to claim 9, wherein the first configuration information further includes a first time domain offset, and the determining a target uplink configuration grant associated with the first time-frequency resource comprises:

Determine a second time unit according to the first time unit and the first time domain offset, where the first time unit is the time unit corresponding to the first time-frequency resource, and the second time unit is the The time unit corresponding to the second time-frequency resource;

It is determined that the uplink configuration grant corresponding to the second time unit is the target uplink configuration grant.
The method of claim 9, wherein the first configuration information further includes a first frequency domain offset, and the determining a target uplink configuration grant associated with the first time-frequency resource includes:

According to the first frequency domain unit and the first frequency domain offset, a second frequency domain unit is determined, where the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is The domain unit is a frequency domain unit corresponding to the second time-frequency resource;

Determine that the uplink configuration grant corresponding to the second frequency domain unit is the target uplink configuration grant.
The method according to claim 9, wherein the first configuration information further includes a first time domain offset and a first frequency domain offset, and the determining the target uplink associated with the first time-frequency resource Configure authorization, including:

Determine a second time unit according to the first time unit and the first time domain offset, where the first time unit is the time unit corresponding to the first time-frequency resource, and the second time unit is the The time unit corresponding to the second time-frequency resource;

According to the first frequency domain unit and the first frequency domain offset, a second frequency domain unit is determined, where the first frequency domain unit is a frequency domain unit corresponding to the first time-frequency resource, and the second frequency domain unit is The domain unit is a frequency domain unit corresponding to the second time-frequency resource;

It is determined that the uplink configuration grant corresponding to the second time-frequency resource is the target uplink configuration grant.
The method according to any one of claims 9 to 15, wherein the communicating with the terminal device on the second time-frequency resource comprises:

The first uplink data from the terminal device is received on the second time-frequency resource, and the first uplink data is transmitted in an uplink configuration authorization manner.
The method of claim 16, wherein:

When the first uplink data is successfully detected, it is determined that the first downlink data is successfully decoded by the terminal device; and/or,

When the first uplink data is not successfully detected, it is determined that the first downlink data has not been successfully decoded by the terminal device.
A communication device in a closed-loop application scenario, characterized by comprising a module for executing the method according to any one of claims 1 to 8 or 9 to 17.
A communication device in a closed-loop application scenario, which is characterized by comprising a processor and a communication interface, the communication interface being used to receive signals from other communication devices other than the communication device and transmit them to the processor or The signal from the processor is sent to other communication devices other than the communication device, and the processor is used to implement any one of claims 1 to 8 or 9 to 17 through logic circuits or execution code instructions Methods.
A computer-readable storage medium, characterized in that, the computer-readable storage medium stores a computer program, and when the computer program is run, the computer program can realize the method described in any one of claims 1 to 8 or 9 to 17. Methods.
A computer program product, characterized by comprising computer program code, when the computer program code is executed, the method according to any one of claims 1 to 8 or 9 to 17 is realized.
A communication system, characterized by comprising a communication device in a closed-loop application scenario according to claim 19.