A communication method and apparatus

Abstract

The application provides a communication method and device, relates to the technical field of communication, and is used for solving the problem that the power consumption of a terminal device is relatively large because the terminal device is used for listening to control information of scheduling uplink data and listening to control information of scheduling downlink data for a long time. The method comprises the following steps: a terminal device receives downlink control information DCI from a network device, the DCI schedules transmission of a physical downlink shared channel PDSCH, and the DCI also schedules transmission of a physical uplink shared channel PUSCH at the same time; the terminal device receives the PDSCH according to the DCI; and the terminal device transmits the PUSCH according to the DCI.

Description

[0001] This application claims priority to Chinese Patent Application No. 202110690133.6, filed with the State Intellectual Property Office of China on June 22, 2021, entitled "A Method for Scheduling Data Transmission", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] In wireless communication systems, to save power consumption of terminal devices while ensuring efficient data transmission, a discontinuous reception (DRX) mechanism is introduced to control the terminal device's behavior of listening to the Physical Downlink Control Channel (PDCCH). Network devices configure DRX parameters for terminal devices, allowing them to continuously listen to the PDCCH for scheduling information during the onDuration period of the DRX cycle. If the terminal device does not receive any scheduling information within the onDuration period, it can enter a sleep state and stop listening to the PDCCH to save power.

[0004] For augmented reality (AR) services, such as AR video conferencing or cloud gaming (CG), the downlink data sent from network devices to terminal devices is periodic, with short intervals between data transmissions. Furthermore, downlink data has high latency requirements, typically requiring a latency of no less than 10ms to avoid impacting user experience. Similarly, uplink data, such as video or audio, sent from terminal devices to network devices also exhibits periodic transmission characteristics. For example, in a certain AR service, downlink data transmits 60 frames per second, meaning the average arrival time interval between two adjacent downlink frames is 16.67ms, and the average arrival time interval for uplink data is also 16.67ms. However, the latency requirements for uplink data are not high; for example, the latency can be as low as 60ms.

[0005] Existing terminal devices require extended periods of time to monitor and schedule control information for both uplink and downlink data. Consequently, the time available for these devices to enter sleep mode to conserve power is relatively short. This results in high power consumption for terminal devices implementing AR services, particularly those with smaller battery capacities such as wearable devices, leading to insufficient battery life and a poor user experience. Summary of the Invention

[0006] This application provides a communication method and apparatus that solves the problem of high power consumption caused by the long-term use of terminal devices to monitor and schedule control information for uplink and downlink data in the prior art.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] In a first aspect, a communication method is provided, applied to a terminal device, the method comprising: receiving downlink control information (DCI) from a network device, the DCI scheduling the transmission of a physical downlink shared channel (PDSCH), the DCI also scheduling the transmission of a physical uplink shared channel (PUSCH); receiving the PDSCH according to the DCI; and sending the PUSCH according to the DCI, the PUSCH including uplink data.

[0009] In the above technical solution, network devices can simultaneously schedule PDSCH and PUSCH through a single DCI, enabling PDSCH and PUSCH to be transmitted within a shorter time. This limits data transmission to a shorter completion time, reducing the time terminal devices are in an active state and the time spent monitoring PDCCH, thereby reducing the power consumption of terminal devices. Furthermore, the fact that network devices can simultaneously schedule PDSCH and PUSCH through only one DCI effectively reduces the signaling overhead of the DCI.

[0010] In one possible implementation, prior to receiving the DCI from the network device, the method further includes: receiving first configuration information from the network device, the first configuration information indicating transmission parameters of the PUSCH, the transmission parameters including frequency domain resource allocation information and / or time domain resource allocation information.

[0011] In the above possible implementations, the network device instructs the terminal device on frequency domain resource allocation information and / or time domain resource allocation information for sending PUSCH in the first configuration information. This enables the terminal device to determine the transmission parameters for sending PUSCH according to the instructions in the first configuration information after receiving DCI, thereby enabling the transmission of PDSCH and PUSCH in a shorter time, reducing the signaling overhead of DCI, and effectively reducing the power consumption of the terminal device.

[0012] In one possible implementation, the time-domain resource allocation information includes a first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

[0013] In the above possible implementations, the network device indicates a first duration, i.e. the time slot interval for sending PUSCH and DCI, to the terminal device in the first configuration information. This allows the terminal device to determine the time slot for sending PUSCH based on the first duration after receiving DCI, thereby transmitting PDSCH and PUSCH in a shorter time, reducing the signaling overhead of DCI, and effectively reducing the power consumption of the terminal device.

[0014] In one possible implementation, the first configuration information includes a period value, which is used to determine the periodic time-domain resources that the PUSCH can use.

[0015] In the above possible implementations, the network device indicates a period value to the terminal device in the first configuration information, thereby enabling the terminal device to flexibly select the time domain resources for sending PUSCH from multiple periodically available time domain resources based on the period value. This improves the flexibility of PUSCH transmission, transmits PDSCH and PUSCH in a shorter time, reduces the signaling overhead of DCI, and effectively reduces the power consumption of the terminal device.

[0016] In one possible implementation, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located; or, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located at a second time interval, where the second time interval is the first time interval or the third time interval reported by the terminal device.

[0017] In the above possible implementations, the terminal device flexibly selects the time domain resource for transmitting PUSCH from multiple periodically available time domain resources based on the period value. For example, it can select the first periodic time domain resource after the time slot where DCI is located, or the first periodic time domain resource after the time slot where DCI is located with a second interval, thereby improving the flexibility of PUSCH transmission and transmitting PDSCH and PUSCH in a shorter time, reducing the power consumption of the terminal device.

[0018] In one possible implementation, the DCI indicates a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; sending the PUSCH according to the DCI specifically includes: determining a first duration based on the fourth duration and the fifth duration, wherein the first duration is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, and sending the PUSCH to the network device according to the first duration.

[0019] In the aforementioned possible implementations, network devices can indicate some transmission parameters of PUSCH via DCI instead of configuring them through RRC signaling, thus allowing for more flexible indication of transmission parameters. Furthermore, by sending PUSCH and HARQ-ACK feedback in the same time slot, effectively merging two uplink transmissions into a single uplink transmission, the power consumption of terminal devices can be further reduced, and communication efficiency improved.

[0020] In one possible implementation, the method further includes: receiving second configuration information from the network device, the second configuration information configuring M orthogonal frequency division multiplexing (OFDM) symbol positions, the M OFDM symbol positions being used for the transmission of the PUSCH, each OFDM symbol position corresponding to a value of a fifth duration, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

[0021] In the aforementioned possible implementations, the network device can indicate the positions of M OFDM symbols for PUSCH transmission to the terminal device through the second configuration information, and map the OFDM symbol positions one-to-one with the fifth duration indicated in the DCI, thereby flexibly indicating the transmission parameters of PUSCH. Furthermore, by sending PUSCH and HARQ-ACK feedback in the same time slot, that is, merging two uplink transmissions into one uplink transmission, the power consumption of the terminal device is further reduced, and communication efficiency is improved.

[0022] In one possible implementation, the DCI sending the PUSCH specifically includes: determining the OFDM symbol position corresponding to the fifth duration indicated by the DCI; and sending the PUSCH at the OFDM symbol position.

[0023] In the above possible implementations, the network device can indicate the positions of M OFDM symbols for transmitting PUSCH to the terminal device through the second configuration information, and then implicitly indicate the corresponding OFDM symbol positions in combination with the fifth duration in DCI. This allows for flexible indication of PUSCH transmission parameters, reduces the power consumption of the terminal device, and improves communication efficiency.

[0024] In one possible implementation, the transmission parameters also include at least one of the following: HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

[0025] In the above possible implementations, the network device can pre-instruct the terminal device on some parameters for transmitting PUSCH, thereby saving signaling overhead and improving communication efficiency.

[0026] In one possible implementation, the DCI includes at least one of HPN, DAI, RV, or MCS indications.

[0027] In the above possible implementations, the network device can dynamically indicate some transmission parameters of PUSCH through DCI, instead of using fixed transmission parameters pre-configured by the network device for the terminal device. This allows for dynamic adaptation to the current channel state, increasing the flexibility of PUSCH scheduling and improving data transmission performance.

[0028] In one possible implementation, the HARQ process number HPN of the PDSCH is the same as that of the PUSCH; the new data indication DAI of the PDSCH is the same as that of the PUSCH; and the redundant version RV of the PDSCH is the same as that of the PUSCH.

[0029] In the above possible implementations, network devices can implicitly instruct PDSCH and PUSCH to share the same transmission parameters, such as at least one of HPN, RV, or DAI, through DCI, thereby saving signaling overhead.

[0030] In one possible implementation, the DCI includes a first field that indicates whether the DCI schedules the PUSCH transmission.

[0031] In the above possible implementations, the network device adds a specific first field to the DCI of the downlink data to indicate whether the DCI triggers the transmission of PUSCH. This allows the network device to dynamically indicate whether to trigger the transmission of PUSCH each time PDSCH is scheduled, making the scheduling of PUSCH more flexible.

[0032] In one possible implementation, the method further includes: receiving third configuration information from the network device, the third configuration information including N sets of first configuration information for transmitting PUSCH, the first configuration information being used to indicate transmission parameters for transmitting PUSCH, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication; the DCI includes first indication information, the first indication information being used to indicate one of the N sets of first configuration information.

[0033] In the above possible implementations, the third configuration information may include the transmission parameters of all PUSCHs, thereby reducing the signaling overhead of PUSCH scheduling. Alternatively, the third configuration information may include only the transmission parameters of some PUSCHs, combined with the dynamic indication method of DCI in the aforementioned embodiments. By pre-configuring the transmission parameters of some PUSCHs through network devices and dynamically indicating the transmission parameters of some PUSCHs through DCI, the flexibility of PUSCH scheduling can be improved.

[0034] In one possible implementation, before receiving DCI from the network device, the method further includes: sending second indication information to the network device, the second indication information including a service type, or the transmission interval of uplink service data of the terminal device, or the second indication information including configuration parameters for requesting the network device to configure the PUSCH; the configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

[0035] In the above possible implementations, the terminal device actively reports the second indication information, thereby enabling the network device to flexibly configure the transmission parameters for scheduling PUSCH in a timely manner. The network device can simultaneously schedule PDSCH and PUSCH through a single DCI, reducing the invalid PDCCH monitoring time of the terminal device and saving power consumption for the terminal device.

[0036] Secondly, a communication method is provided for use in network devices. The method includes: sending downlink control information (DCI) to a terminal device, wherein the DCI schedules the transmission of the physical downlink shared channel (PDSCH) and simultaneously schedules the transmission of the physical uplink shared channel (PUSCH).

[0037] In one possible implementation, before sending downlink control information (DCI) to the terminal device, the method further includes: sending first configuration information to the terminal device, the first configuration information instructing the terminal device to send transmission parameters for the PUSCH, the transmission parameters including frequency domain resource allocation information and / or time domain resource allocation information.

[0038] In one possible implementation, the time-domain resource allocation information includes a first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

[0039] In one possible implementation, the first configuration information includes a period value, which indicates the periodic time-domain resources that the PUSCH sent by the terminal device can use.

[0040] In one possible implementation, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located; or, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located at a second time interval, the second time interval being the first time interval or the third time interval reported by the terminal device.

[0041] In one possible implementation, the DCI indicates a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; the fourth duration and the fifth duration are used by the terminal device to determine a first duration, the first duration being the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, and to send the PUSCH to the network device according to the first duration.

[0042] In one possible implementation, the method further includes: sending second configuration information to the terminal device, the second configuration information configuring M orthogonal frequency division multiplexing (OFDM) symbol positions, the M OFDM symbol positions being used for the transmission of the PUSCH, each OFDM symbol position corresponding to a fifth duration value, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

[0043] In one possible implementation, the DCI includes an indication of the fifth duration, used to instruct the terminal device to determine the OFDM symbol location corresponding to the fifth duration.

[0044] In one possible implementation, the transmission parameters also include at least one of the following: HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

[0045] In one possible implementation, the DCI includes at least one of HPN, DAI, RV, or MCS instructions.

[0046] In one possible implementation, the HARQ process number HPN of the PDSCH is the same as that of the PUSCH; the new data indication DAI of the PDSCH is the same as that of the PUSCH; and the redundant version RV of the PDSCH is the same as that of the PUSCH.

[0047] In one possible implementation, the DCI includes a first field that indicates whether the DCI schedules the PUSCH transmission.

[0048] In one possible implementation, the method further includes: sending third configuration information to the network device, the third configuration information including N sets of first configuration information for transmitting PUSCH, the first configuration information being used to indicate transmission parameters for transmitting PUSCH, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication; the DCI includes first indication information, the first indication information being used to indicate one of the N sets of first configuration information.

[0049] In one possible implementation, before sending downlink control information (DCI) to the terminal device, the method further includes: receiving second indication information from the terminal device, the second indication information including a service type, or the transmission interval of uplink service data of the terminal device, or the second indication information including a request for the network device to configure configuration parameters corresponding to the PUSCH to the terminal device; the configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

[0050] Thirdly, this application also provides a communication device, which can be a terminal device having the functions of a terminal device implementing any of the functions described in the first aspect. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0051] In one possible implementation, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions of the terminal device in any of the first aspects described above, as detailed in the method examples, and will not be repeated here.

[0052] In one possible implementation, the communication device includes a transceiver and a processor, and optionally a memory. The transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions of the terminal device in any of the first aspects described above. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0053] Fourthly, this application also provides a communication device, which can be a network device having the functions of a network device implementing any of the functions described in the second aspect above. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0054] In one possible implementation, the communication device includes a transceiver unit and a processing unit, which can perform the corresponding functions of the network device in any of the second aspects described above, as detailed in the method examples, and will not be repeated here.

[0055] In one possible implementation, the communication device includes a transceiver and a processor, and optionally a memory. The transceiver is used for sending and receiving data, and for communicating and interacting with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions of the network device described in any of the second aspects above. The memory is coupled to the processor and stores necessary program instructions and data for the communication device.

[0056] Fifthly, embodiments of this application provide a communication system that may include the terminal devices and network devices mentioned above.

[0057] Sixthly, embodiments of this application provide a computer-readable storage medium storing program instructions that, when executed on a computer, cause the computer to perform the methods described in either the first or second aspect above, or any possible design thereof. Exemplarily, the computer-readable storage medium can be any available medium accessible to a computer. For example, but not limited to, a computer-readable medium may include a non-transient computer-readable medium, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer.

[0058] In a seventh aspect, embodiments of this application provide a computer program product including computer program code or instructions, which, when run on a computer, causes the computer to implement the methods in either the first or second aspect described above and any possible design thereof.

[0059] Eighthly, this application also provides a chip including a processor coupled to a memory for reading and executing program instructions stored in the memory to enable the chip to implement the methods in either the first or second aspect described above and any possible design thereof.

[0060] Understandably, any of the communication devices, computer-readable storage media, computer program products, and communication systems provided in aspects three through eight above can be implemented by the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0061] Figure 1 A system architecture diagram of a communication system provided in this application embodiment;

[0062] Figure 2 An architectural diagram of a communication device provided in an embodiment of this application;

[0063] Figure 3 This is a schematic diagram of a DRX configuration for a terminal device provided in an embodiment of this application;

[0064] Figure 4 This is a schematic diagram of AR service data transmission provided in an embodiment of this application;

[0065] Figure 5 A schematic diagram of a scenario for transmitting AR service data packets provided in an embodiment of this application;

[0066] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application;

[0067] Figures 7-11 A schematic diagram of scheduling PUSCH and PDSCH provided for embodiments of this application. Figures 1 to 5 ;

[0068] Figure 12 A flowchart illustrating another communication method provided in an embodiment of this application;

[0069] Figure 13 A flowchart illustrating another communication method provided in an embodiment of this application;

[0070] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0071] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0072] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0073] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0074] First, a brief introduction will be given to the implementation environment and application scenarios of the embodiments of this application.

[0075] This application can be applied to existing new radio (NR) systems, as well as to any other wireless communication system with similar structure and function. Figure 1 As shown, the communication system includes at least a terminal device 101 and a network device 102.

[0076] The terminal device 101 involved in this application embodiment can be user equipment (UE), wherein the UE includes a handheld device, vehicle-mounted device, wearable device, or computing device with wireless communication function. For example, the UE can be a mobile phone, tablet computer, or computer with wireless transceiver function. The terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0077] In this application embodiment, the device for implementing the terminal's functions can be a terminal itself; it can also be a device capable of supporting the terminal in implementing those functions, such as a chip system, which can be installed in the terminal. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in this application embodiment, the device for implementing the terminal device functions is a UE (User Equipment) as an example to describe the technical solutions provided in this application embodiment.

[0078] The network device 102 involved in the embodiments of this application may include a base station (BS), which may be a device deployed in a wireless access network that can communicate wirelessly with terminals.

[0079] Base stations can take various forms, such as macro base stations, micro base stations, relay stations, and access points. For example, the base station involved in this application embodiment can be a 5G base station or an LTE base station. In 5G, a base station can also be called a transmission reception point (TRP) or gNB.

[0080] In this embodiment of the application, the device for implementing the function of the network device can be the network device itself; or it can be a device that enables the network device to implement the function, such as a chip system, which can be installed in the network device.

[0081] In the technical solutions provided in the embodiments of this application, the means for implementing the functions of a network device is a network device, and the network device is a base station as an example, the technical solutions provided in the embodiments of this application are described.

[0082] The technical solutions provided in this application can be applied to wireless communication between network devices and terminal devices. In this application, the term "wireless communication" can also be abbreviated as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0083] It should be noted that, Figure 1 This is just an example framework diagram. Figure 1 The number of network element nodes included is unlimited. Except... Figure 1 In addition to the functional nodes shown, other nodes may also be included, such as core network devices, gateway devices, application servers, etc., without restriction. Access network devices communicate with core network devices through wired or wireless networks, such as through Next Generation (NG) interfaces.

[0084] In practical implementation, Figure 1 The network elements shown, such as terminal equipment and network equipment, can be adopted. Figure 2 The shown composition or includes Figure 2 The components shown. Figure 2 This is a schematic diagram of the structure of a communication device 200 provided in an embodiment of this application. When the communication device 200 has the functions of the terminal device described in the embodiment of this application, the communication device 200 can be a terminal device or a chip or system-on-a-chip in the terminal device. When the communication device 200 has the functions of the network device described in the embodiment of this application, the communication device 200 can be a network device or a chip or system-on-a-chip in the network device.

[0085] like Figure 2 As shown, the communication device 200 may include a processor 201, a communication line 202, and a communication interface 203. Furthermore, the communication device 200 may also include a memory 204. The processor 201, memory 204, and communication interface 203 can be connected via the communication line 202.

[0086] The processor 201 can be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device, or any combination thereof. The processor 201 can also be other devices with processing capabilities, such as circuits, devices, or software modules.

[0087] Communication line 202 is used to transmit information between the components included in communication device 200.

[0088] Communication interface 203 is used to communicate with other devices or other communication networks. These other communication networks can be Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. Communication interface 203 can be an interface circuit, pins, RF module, transceiver, or any device capable of enabling communication.

[0089] Memory 204 is used to store instructions. These instructions can be computer programs.

[0090] The memory 204 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact optical disc (CD-ROM) or other optical disc storage, optical disk storage, magnetic disk storage medium or other magnetic storage device; optical disk storage includes compressed optical discs, laser discs, optical discs, digital universal optical discs, or Blu-ray discs, etc.

[0091] It should be noted that the memory 204 can exist independently of the processor 201, or it can be integrated with the processor 201. The memory 204 can be used to store instructions, program code, or some data, etc. The memory 204 can be located inside or outside the communication device 200, without limitation. The processor 201 is used to execute the instructions stored in the memory 204 to implement the methods provided in the following embodiments of this application.

[0092] In one example, processor 201 may include one or more CPUs, for example Figure 2 CPU0 and CPU1 in the CPU.

[0093] As an optional implementation, the communication device 200 includes multiple processors, for example, besides Figure 2 In addition to processor 201, it may also include processor 207.

[0094] As an optional implementation, the communication device 200 also includes an output device 205 and an input device 206. For example, the input device 206 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 205 is a device such as a display screen or speaker.

[0095] It should be noted that the communication device 200 can be a wearable device, desktop computer, laptop computer, network server, mobile phone, tablet computer, wireless terminal, embedded device, chip system, or other device. Figure 2 Equipment with a similar structure. Furthermore... Figure 2 The structural composition shown does not constitute a limitation on the communication device, except... Figure 2 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0096] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0097] In combination with the above Figure 1 In the connected state, terminal devices can continuously listen to the PDCCH during the onDuration period, or enter a sleep period and stop listening to the PDCCH, based on the DRX configuration information configured in the network device, to save power. For example, Figure 3 As shown, the DRX configuration can include configuration information for the DRX period and its duration (onDuration). During the onDuration period of this DRX period, the terminal device can continuously listen to the PDCCH to obtain scheduling information. If the terminal device does not receive any scheduling information during the onDuration period, it enters a sleep state and stops listening to the PDCCH to save power.

[0098] In addition, such as Figure 3 As shown, the terminal device can also start or restart the inactive timer InactivityTimer when it detects the PDCCH indicating the initial transmission of user data. InactivityTimer is the timer used by the terminal device to extend the activation time. Based on InactivityTimer, the duration for which the terminal device remains in the activation time after successfully decoding an uplink or downlink PDCCH indicating the initial transmission of user data can be determined. In other words, whenever the terminal device has initial data being scheduled, it starts or restarts the InactivityTimer.

[0099] In scenarios such as AR business, such as Figure 4 As shown, the downlink data sent from network devices to terminal devices mainly includes image or audio data. For example, the cloud (such as a server) sends image data to AR glasses, so that the AR glasses can generate images based on the received image data and present them to the user.

[0100] Downlink data is characterized by periodic transmission. For example, image data can be transmitted in units of image frames with short intervals between frames. Furthermore, downlink data has high requirements for transmission latency. To avoid stuttering in the video viewed by the user, the air interface latency is usually required to be no less than 10ms. That is, the data of an image frame needs to be transmitted within 10ms in the air interface, otherwise it will affect the user experience.

[0101] For example, such as Figure 5 As shown, the downlink data of a certain AR service transmits 60 frames of images per second, that is, the ideal arrival time interval of the data packets corresponding to two adjacent frames is 16.67ms on average, that is, the ideal arrival time interval of the data packets on the terminal device side can be 16.67ms.

[0102] In one implementation, the time required to generate data packets varies because the size and encoding method of each image frame may differ. Furthermore, due to differences in server processing speed for different data packets, and the different routing methods used by different data packets from the application server through the internet and core network to the base station, the arrival time of data packets at the base station may exhibit jitter. The actual arrival time of data packets after considering jitter can be as follows: Figure 5 As shown. Currently, the jitter range is typically [-4ms, 4ms] (or equivalently [0, 8ms]).

[0103] In addition, such as Figure 4As shown, the uplink data sent by the terminal device to the network device mainly includes: control information or action information generated by the terminal device in response to user operations (Type 1); in addition, the uplink data may also include: image or audio data sent by the terminal device to the network device (Type 2), which is used to provide feedback on the user's surrounding environment or scene, and can be used by the network device to update image data for the terminal device, etc.

[0104] For example, AR glasses respond to user actions by generating control information or action information and uploading it to the cloud (such as a server). The cloud (such as a server) can then calculate updated image data based on the acquired control or action information and send the updated image data back to the AR glasses, so that the AR glasses can present a picture to the user based on the updated image data.

[0105] In addition, AR glasses can also send and upload captured image data of the surrounding environment or scene to the cloud. The cloud can then calculate and generate image data based on this image data. For example, the generated image data can be sent to other terminal devices, such as as a background image.

[0106] Corresponding to the aforementioned downlink data, uplink data (Type 2), such as video or audio sent from terminal devices to network devices, also exhibits periodic transmission characteristics. For example, with an average arrival time interval of 16.67ms between data packets corresponding to two adjacent image frames, ... Figure 5 As shown, the average arrival time interval for uplink data can also be 16.67ms. However, the requirements for transmission latency for uplink data are not high. For example, the air interface latency can be 60ms, meaning that the data of an image frame can be transmitted within 60ms over the air interface.

[0107] It should be noted that, in light of the characteristics of the uplink and downlink data of the aforementioned AR service in this application, other uplink and downlink data services with similar characteristics may be referred to as AR-like services, which will not be further explained hereafter.

[0108] Currently, for AR and AR-like services, network devices schedule uplink (Type 2) and downlink data from terminal devices separately. This means the terminal device needs to be active to listen for both the downlink control information (DCI) for scheduling uplink (Type 2) data and the DCI for scheduling downlink data. Consequently, the terminal device needs to listen for a considerable amount of time, resulting in high power consumption.

[0109] It should be noted that DCI can be carried on PDCCH, uplink data can be carried on the Physical Uplink Shared Channel (PUSCH), and downlink data can be carried on the Physical Downlink Shared Channel (PDSCH).

[0110] Based on the above problems and the characteristics of uplink data (Type 2) and downlink data in the AR service, this application provides a communication method and apparatus. By aligning the scheduling of PDSCH with the scheduling of PUSCH, PDSCH and PUSCH can be scheduled in the same or adjacent time slots, so that the terminal device can be in the active time for a shorter period of time. This allows the terminal device to extend its sleep time, effectively reduce power consumption, and improve the user experience.

[0111] The following is combined with Figure 1 The communication system shown illustrates the implementation methods provided in the embodiments of this application. The devices in the following embodiments may have... Figure 2 The components are shown. The actions, terminology, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages used for interaction between devices in the embodiments of this application are merely examples; other names may be used in specific implementations without limitation.

[0112] This application provides a configuration method for discontinuous reception, applicable to, for example... Figure 1 The communication system shown. (As shown) Figure 6 As shown, the method may include:

[0113] 601: The network device sends a DCI to the terminal device, which schedules the transmission of PDSCH and also schedules the transmission of PUSCH.

[0114] In the field of communication technology, scheduling refers to the allocation of parameters and resources for data transmission according to a certain scheduling algorithm or protocol. In the embodiments of this application, scheduling through DCI means that the network device can instruct the terminal device to transmit PDSCH through the DCI, and the DCI can also instruct the transmission of PUSCH.

[0115] In other words, the DCI sent by the network device to the terminal device is used not only to schedule the transmission of PDSCH, but also to trigger the transmission scheduling of PUSCH.

[0116] Furthermore, in the embodiments of this application, when DCI schedules PDSCH, it can specifically indicate the transmission parameters of PDSCH to the terminal device through DCI.

[0117] In addition, the transmission parameters of PUSCH can be pre-configured for the terminal device by the network device through Radio Resource Control (RRC), or can be dynamically indicated by DCI.

[0118] In one implementation, the transmission parameters of the PUSCH may mainly include one or more of the following: frequency domain resource allocation (FDRA) information, time domain resource allocation (TDRA) information, Hybrid Automatic Repeat Request (HARQ) process number (HPN), downlink assignment index (DAI), redundancy version (RV), frequency hopping (FH), or modulation and coding scheme (MCS).

[0119] 602: The terminal device receives the DCI from the network device, receives the PDSCH based on the DCI, and sends the PUSCH based on the DCI. The PUSCH includes uplink data.

[0120] The terminal device can receive PDSCH at the time-frequency resource location indicated in DCI. The PDSCH carries downlink data, which can be downlink data packets.

[0121] Then, the terminal device can send a PUSCH according to the DCI, where the PUSCH carries uplink data, specifically uplink data packets. Uplink data, or downlink data, refers to service data, that is, data generated by the terminal device's application (APP) or network devices such as servers. Specifically, uplink data refers to the data packets corresponding to type 2 uplink data mentioned above.

[0122] Optionally, the PUSCH may also carry HARQ feedback corresponding to the previously transmitted PDSCH. HARQ feedback can be used to indicate whether the terminal device has successfully decoded and obtained the corresponding downlink data from the PDSCH. For example, HARQ feedback may include acknowledgement (ACK) or non-acknowledgement (NACK). For details, please refer to the relevant technical documentation; further explanation is omitted here.

[0123] In one implementation, the terminal device triggers PUSCH scheduling based on DCI, and the specific triggering method may include:

[0124] Method 1: Whenever a network device sends a DCI (Distributed Information Control Code) to a terminal device to schedule downlink data, the DCI causes the terminal device to automatically trigger the sending of a PUSCH.

[0125] One possible premise for adopting this implementation method is that the network device can configure a corresponding operating mode or state for the terminal device, that is, the terminal device is configured to a working mode or state in which the DCI schedules both PDSCH and PUSCH. Therefore, when the terminal device is configured in this working mode or state, each DCI for scheduling downlink data by the network device will trigger a PUSCH transmission by the terminal device. Conversely, when the terminal device is not configured in this working mode or state, the DCI for scheduling downlink data by the network device is only used for scheduling PDSCH.

[0126] Method 2: The DCI includes a first field, which is used to indicate whether the DCI schedules PUSCH transmission.

[0127] In other words, a specific field, such as a first field, can be added to the DCI for scheduling downlink data to indicate whether the DCI triggers PUSCH transmission. This method allows network devices to dynamically indicate whether to trigger PUSCH transmission each time PDSCH is scheduled, making PUSCH scheduling more flexible.

[0128] For example, the first field can occupy 1 bit. A value of "0" indicates that the DCI does not trigger PUSCH transmission, and in this case, the DCI only schedules the transmission of PDSCH. A value of "1" indicates that PUSCH transmission is triggered, and in this case, the DCI schedules the transmission of one PDSCH and one PUSCH simultaneously.

[0129] Specifically, based on Method 1 and Method 2, the various configuration methods of PUSCH transmission parameters will be described in detail below, and will not be repeated here.

[0130] like Figure 7As shown, since the arrival periods of uplink and downlink data packets in AR or AR-like services are the same, there will inevitably be one uplink data packet and one downlink data packet within each period (e.g., a period of 16.67ms). That is, within a period of 16.67ms, there are data packets to be transmitted for both uplink and downlink data, and there will be no situation where no data packets can be transmitted. Therefore, the scheduling time of uplink and downlink data can be aligned.

[0131] Furthermore, since downlink data transmission has high latency requirements, while uplink data transmission has lower latency requirements, downlink data transmission can be prioritized. That is, PDSCH transmission can be scheduled immediately after downlink data arrives. Conversely, uplink data transmission can be delayed after arrival. For example, the terminal device can schedule PUSCH and PDSCH within the same or similar timeframes. Figure 7 As shown.

[0132] Through the above implementation method, network devices can simultaneously schedule PDSCH and PUSCH using a single DCI, enabling PDSCH and PUSCH to be transmitted within a shorter time. This limits data transmission to a shorter completion time, reducing the time terminal devices are in an active state and the time spent monitoring PDCCH, thereby reducing the power consumption of terminal devices. Furthermore, since network devices can simultaneously schedule PDSCH and PUSCH using only a single DCI, the signaling overhead of the DCI is effectively reduced.

[0133] In one implementation, prior to step 601, i.e., before the network device sends the DCI to the terminal device, the method further includes:

[0134] S1: The network device sends first configuration information to the terminal device, the first configuration information indicating the transmission parameters of PUSCH.

[0135] S2: The terminal device receives the first configuration information from the network device.

[0136] In one implementation, the transmission parameters of PUSCH may include time-domain resource allocation information, which is used to indicate the time-domain resource location where the terminal device sends PUSCH.

[0137] Optionally, the time-domain resource allocation information may include a first duration, which may be used to represent the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

[0138] Specifically, the time slot interval between the time slot containing the DCI and the time slot containing the PUSCH can refer to the time slot interval between the start time slot of DCI transmission and the start time slot of PUSCH transmission, or the time slot interval between the last time slot of DCI transmission and the last time slot of PUSCH transmission, or the time slot interval between the time slot in which the terminal device receives the DCI and the time slot in which the terminal device sends the PUSCH, or the time slot interval between the time slot in which the network device sends the DCI and the time slot in which the terminal device sends the PUSCH, etc. This can be agreed upon according to the actual application, and this application does not impose specific restrictions in this regard.

[0139] For example, the first configuration information sent by the network device to the terminal device includes a first duration of K2, where K2 is in time slots, and the time slot where the DCI is located is time slot n. After receiving the DCI, the terminal device can send a PUSCH in time slot n+K2, as shown below. Figure 8 As shown.

[0140] In another implementation, the time-domain resources configured by the network device for transmitting PUSCH to the terminal device can also be periodic time-domain resources. That is, the network device configures multiple periodically occurring time-domain resources for the terminal device, such as... Figure 9 T1, T2, and T3, etc., are optional time-domain resources for terminal devices to send PUSCH.

[0141] Specifically, the first configuration information may include a period value, which is used by the terminal device to determine the periodic time-domain resources that the PUSCH can use. Thus, after receiving the DCI, the terminal device can select one of a plurality of periodically occurring time-domain resources to send the PUSCH, based on the period value included in the first configuration information.

[0142] The time slot in which the terminal device determines the PUSCH transmission location can be the first periodic time-domain resource after the time slot where the DCI is located; or, it can be the first periodic time-domain resource after the time slot where the DCI is located at a second interval. These will be explained below with reference to the accompanying drawings.

[0143] In one implementation, the time slot in which the terminal device determines the PUSCH transmission can be the first periodic time domain resource after the time slot in which the DCI is located.

[0144] For example, such as Figure 9As shown, the period value included in the first configuration information is t. Based on the period value T, the terminal device can determine that the periodic time domain resources available for PUSCH are T1, T2, and T3, etc. If the time slot where the DCI sent by the network device is located is time slot n, then after receiving the DCI, the terminal device can send PUSCH on the first periodic time domain resource after time slot n, i.e., as shown... Figure 9 PUSCH can be sent on T2.

[0145] In another implementation, taking into account the time consumed by the terminal device in packetizing uplink data and the time taken by the terminal device to generate PUSCH, the time slot in which the terminal device determines to send PUSCH can be the first periodic time domain resource after the time slot in which DCI is located, with an interval of the second duration.

[0146] Specifically, the second duration can be the first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, as indicated in the first configuration information.

[0147] Alternatively, the second duration can be equal to the third duration reported by the terminal device to the network device. For example, the third duration can be N², the preparation time for the terminal device to send the PUSCH, in units of OFDM symbols; that is, the third duration is N² OFDM symbols. This third duration is related to the processing speed of the terminal device and can be reported by the terminal device to the network device when it accesses the network device. Furthermore, the third duration can be the same as or different from the first duration, and the units of the first and third durations can also be in other forms; this application imposes limitations on this.

[0148] For example, such as Figure 10 As shown, the first duration is K2, the third duration is N2, and the time slot where the DCI is located is time slot n. After receiving the DCI, the terminal device can send PUSCH on the first periodic time domain resource after time slot n, with an interval of K2 time slots after time slot n, or after the end symbol of the DCI with an interval of N2 symbols. Figure 10 PUSCH can be sent on T3.

[0149] In one implementation, the first configuration information may be carried in RRC signaling. Furthermore, in addition to including the TDRA among the PUSCH transmission parameters mentioned in the aforementioned implementations, the first configuration information may also include other PUSCH transmission parameters. For example, the PUSCH transmission parameters indicated in the first configuration information may also include at least one of HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

[0150] Alternatively, the network device can configure the TDRA in the PUSCH transmission parameters through one RRC signaling, and then configure at least one parameter in the PUSCH transmission parameters, such as the HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS, through at least one RRC signaling.

[0151] Through the above implementation method, the network device instructs the terminal device on the transmission parameters for sending PUSCH in the first configuration information, thereby enabling the terminal device to determine the transmission parameters for sending PUSCH according to the instruction in the first configuration information after receiving DCI. This allows for the transmission of PDSCH and PUSCH in a shorter time, reducing the signaling overhead of DCI and effectively reducing the power consumption of the terminal device.

[0152] In one implementation, the network device can also indicate some transmission parameters of the PUSCH via DCI, instead of configuring them through RRC signaling, thus allowing for more flexible indication of transmission parameters. Specifically, this can be indicated implicitly via DCI, or through specific fields in the DCI. For example, the network device can also implicitly indicate the time-domain resource location of the transmitted PUSCH via DCI, or the network device can add an indication bit corresponding to the MCS of the PUSCH to the DCI, etc.

[0153] The following provides several exemplary implementations of indicating some transmission parameters of PUSCH via DCI. In these implementations, in addition to indicating some transmission parameters of PUSCH via DCI, the network device can still indicate other PUSCH transmission parameters in combination with the implementations described below and those described above. That is, the various optional implementations of this application can be combined with each other. Implementations obtained by combining any implementation of this application should be covered within the protection scope of this application, and will not be described further in this application.

[0154] 1. The location of the time-domain resources for transmitting PUSCH is implicitly indicated by DCI.

[0155] Specifically, in step 601 of the above embodiment, the network device sends the DCI indication fourth duration and fifth duration to the terminal device. The fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

[0156] Then, the terminal device can determine the first duration based on the fourth and fifth durations indicated in the DCI. The first duration is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located. Thus, the terminal device can determine the time slot position to send the PUSCH to the network device based on the first duration.

[0157] In one implementation, the terminal device can send PUSCH and HARQ-ACK feedback in the same time slot, that is, the terminal device can determine the first duration as the sum of the fourth duration and the fifth duration.

[0158] For example, such as Figure 11 As shown, the time slot where the DCI is located is n, the fourth duration indicated in the DCI is K0, and the fifth duration is K1. Then the terminal device can determine the time slot position for sending the PUSCH as n+K0+K1.

[0159] At this time, since PUSCH and HARQ-ACK feedback are sent in the same time slot, that is, HARQ-ACK and PUSCH are in one-to-one correspondence, HARQ-ACK does not need to be based on the codebook for feedback. Therefore, DCI does not need to indicate DAI information, which can further reduce the signaling overhead of DCI.

[0160] The above-described implementation method, in addition to reducing signaling overhead, further reduces the power consumption of the terminal device and improves communication efficiency by sending PUSCH and HARQ-ACK feedback in the same time slot, that is, merging two uplink transmissions into one uplink transmission.

[0161] 2. The DCI implicitly indicates that some transmission parameters of the PUSCH are the same as those of the PDSCH.

[0162] In one implementation, the network device may also implicitly indicate via DCI that the PDSCH and PUSCH share some of the same transmission parameters, such as at least one of HPN, RV, or DAI.

[0163] In other words, the HPN, NDI, and RV values ​​of the scheduled PDSCH and PUSCH can be the same. For example, the HPN of PDSCH can be the same as the HPN of PUSCH; or the NDI of PDSCH can be the same as the NDI of PUSCH; or the RV of PDSCH can be the same as the RV of PUSCH.

[0164] 3. Determine the symbol position of the Orthogonal Frequency Division Multiplexing (OFDM) corresponding to the transmitted PUSCH by using the fifth duration indicated in the DCI.

[0165] In one implementation, the network device can configure multiple different fifth durations for the terminal device, and each fifth duration value corresponds to an OFDM symbol position. Each OFDM symbol position can be defined by adding a start symbol and a symbol length.

[0166] Specifically, the network device can be configured in the following way, that is, before step 601 of the aforementioned embodiment, the method may further include:

[0167] S1: The network device sends the second configuration information to the terminal device. The second configuration information configures M OFDM symbol positions, and each OFDM symbol position corresponds to a value of a fifth duration.

[0168] Among them, M OFDM symbol positions can be used as symbol positions for PUSCH transmission. The fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located, for example, the aforementioned K1 value. That is, each K1 value corresponds to one OFDM symbol position. Here, M can be a positive integer greater than or equal to 2.

[0169] S2: The terminal device receives the second configuration information from the network device.

[0170] The terminal device receives the second configuration information and stores it locally, that is, it records the positions of M OFDM symbols and the values ​​of M fifth durations and their corresponding relationships.

[0171] In this implementation, step 602 described above may specifically include:

[0172] S3: The terminal device can determine the OFDM symbol position corresponding to the fifth duration based on the fifth duration indicated by the DCI and the second configuration information stored in step S2.

[0173] S4: The terminal device can send PUSCH to the network device according to the OFDM symbol location determined in step S3.

[0174] 4. The DCI includes at least one of the following: HPN, DAI, RV, or MCS indication.

[0175] In one embodiment, the DCI sent by the network device to the terminal device in step 601 of the above embodiment may also include some transmission parameters of PUSCH, such as at least one of HPN, DAI, RV or MCS indication.

[0176] Specifically, this can be indicated by adding a specific field to the DCI. For example, a second field can be added to the DCI to indicate the MCS used for transmitting the PUSCH.

[0177] Through the above implementation methods, network devices can dynamically indicate some transmission parameters of PUSCH through DCI, instead of using fixed transmission parameters pre-configured by the network device for the terminal device. This allows for dynamic adaptation to the current channel state, increasing the flexibility of PUSCH scheduling and improving data transmission performance.

[0178] In addition, this application also provides an implementation method in which a network device pre-configures multiple sets of different transmission parameters for transmitting PUSCH to a terminal device, and then sends a DCI instruction to the terminal device to indicate one of the sets, thereby enabling the terminal device to determine the transmission parameters for transmitting PUSCH.

[0179] Specifically, the network device can be configured in the following way, that is, before step 601 of the aforementioned embodiment, the method may further include:

[0180] S1: The network device sends third configuration information to the terminal device. The third configuration information includes N sets of PUSCH transmission parameters.

[0181] S2: Receive third configuration information from the network device.

[0182] Based on the foregoing, the transmission parameters of a PUSCH can include one or more of the following: frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication. Therefore, the transmission parameters of each group of PUSCHs in the third configuration information here can include one or more of the following: frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication. That is, the transmission parameters of the PUSCHs mentioned in the foregoing embodiments can be considered as a set of PUSCH transmission parameters.

[0183] In one implementation, the transmission parameters of each of the N groups of PUSCHs can be the first configuration information described in the preceding implementation, i.e., the third configuration information includes N groups (or N instances) of the first configuration information. The first configuration information is used to indicate the transmission parameters of the transmitted PUSCHs, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication.

[0184] For example, the first configuration information may specifically include the first time period or period value corresponding to the time and frequency resources for transmitting PUSCH.

[0185] In one implementation, the third configuration information may include transmission parameters for all PUSCHs, thereby reducing the signaling overhead of PUSCH scheduling. Alternatively, the third configuration information may include only transmission parameters for a subset of PUSCHs, combined with the dynamic DCI indication method described in the preceding implementations. By pre-configuring transmission parameters for some PUSCHs through network devices and dynamically indicating transmission parameters for some PUSCHs through DCI, the flexibility of PUSCH scheduling can be improved.

[0186] In this embodiment described above, in step 601 of the aforementioned embodiment, the DCI sent by the network device to the terminal device may include first indication information, wherein the first indication information is used to indicate one of the transmission parameters of N sets of PUSCH.

[0187] Step 602 of the aforementioned implementation method may specifically include:

[0188] S3: The terminal device determines the transmission parameters of the corresponding PUSCH based on the first indication information included in the DCI.

[0189] For example, the network device configures three sets of PUSCH transmission parameters for the terminal device. The first indication information included in the DCI can be 2 bits. The first indication information of 00 indicates the transmission parameters of the first set of PUSCH, the first indication information of 01 indicates the transmission parameters of the second set of PUSCH, the first indication information of 10 indicates the transmission parameters of the third set of PUSCH, and the first indication information of 11 can indicate that PUSCH transmission is not triggered.

[0190] S4: The terminal device sends PUSCH to the network device according to the determined transmission parameters.

[0191] Since the implementation method of this application is an optimization of the scheduling method for AR services and AR-like services, in order to distinguish different service types and match different scheduling methods, the terminal device can report the service type to the network device in advance, so that the network device can switch different scheduling methods according to different service types. Specifically, the relevant PUSCH transmission parameters can be configured for the corresponding terminal device, or specific fields in the DCI can be enabled, so as to achieve the aforementioned effect of scheduling PDSCH and PUSCH simultaneously through a DCI.

[0192] Specifically, when the terminal device determines that the current service type is AR service or AR-like service, it can be configured in the following way, that is, before step 601 of the aforementioned implementation method, such as Figure 12 As shown, the method may further include:

[0193] 1201: The terminal device sends a second instruction message to the network device.

[0194] The second indication information may include the current service type of the terminal device, or the transmission interval of the uplink service data of the terminal device. Specifically, the transmission interval of the uplink service data may refer to the time interval between uplink data packets. The network device can compare the transmission interval of the uplink service data with the transmission interval of the downlink service data to determine if their values ​​are the same or similar. This allows the network device to determine if the service type of the terminal device is AR service or AR-like service, and data transmission can be performed using the scheduling method provided in this application embodiment.

[0195] The second instruction information may also include instructions indicating that the latency tolerance of the uplink service on the terminal device is relatively large, or that the latency budget is relatively large.

[0196] Alternatively, the second indication information may include request information for requesting the network device to configure the configuration parameters corresponding to the PUSCH. Specifically, the configuration parameters corresponding to the PUSCH may include at least one of the first configuration information, second configuration information, or third configuration information described in the foregoing embodiments.

[0197] 1202: The network device receives the second instruction information and sends the configuration parameters corresponding to PUSCH to the terminal device.

[0198] If, according to the aforementioned implementation method, the configuration parameters corresponding to the PUSCH sent by the network device only indicate part of the transmission parameters of the PUSCH, then the network device also needs to explicitly indicate the transmission parameters of other PUSCHs through DCI. Therefore, the network device needs to enable specific indication bits in DCI.

[0199] For example, a first field can be added to the DCI subsequently sent to the terminal device to indicate that the DCI schedules PUSCH transmission. Alternatively, a second field can be added to the DCI to indicate the MCS transmitting the PUSCH.

[0200] The above implementation method enables the network device to flexibly configure and schedule the transmission parameters of PUSCH for the terminal device through the active reporting of the terminal device. The network device can simultaneously schedule PDSCH and PUSCH through a DCI, which reduces the invalid PDCCH monitoring time of the terminal device and saves power consumption for the terminal device.

[0201] In addition, this application also provides another communication method that does not change the existing DCI scheduling method, but achieves the effect of aligning uplink and downlink data scheduling by limiting the values ​​of the scheduling parameters of network devices.

[0202] Within a certain time period, network devices schedule PDSCH and PUSCH for terminal devices using the first scheduling method. Alternatively, it can be understood that terminal devices receive PDSCH and transmit PUSCH using the first scheduling method.

[0203] Among them, such as Figure 13 As shown, the first scheduling method may include:

[0204] 1301: The network device sends the first DCI to the terminal device and the second DCI to the terminal device.

[0205] The first DCI is used to schedule the transmission of PDSCH, which includes downlink data. The second DCI is used to schedule the transmission of PUSCH, which includes uplink data. The HARQ feedback corresponding to PUSCH and PDSCH is transmitted in the same time slot.

[0206] It should be noted that, in order to ensure that uplink and downlink scheduling occurs within the shortest possible time, network devices can send the first DCI to the terminal device and the second DCI to the terminal device within the sixth time period.

[0207] Specifically, the sixth duration can be X time slots. Preferably, the sixth duration corresponds to the same time slot or two adjacent time slots.

[0208] For example, if X = 1, meaning the sixth time period corresponds to one time slot, then the network device can send the first DCI and the second DCI in the same time slot. If X = 2, meaning the sixth time period corresponds to two time slots, then the network device can send the first DCI and the second DCI in two adjacent time slots. The network device can send the first DCI first and then the second DCI, or vice versa; the order in which the network device sends the first DCI and the second DCI is not specifically restricted.

[0209] 1302: The terminal device receives the first DCI and the second DCI from the network device, and receives the PDSCH according to the first DCI and sends the PUSCH according to the second DCI.

[0210] The terminal device can send PUSCH and the corresponding HARQ feedback for sending PDSCH in the same time slot.

[0211] For example, if the first DCI is transmitted in time slot n1, it indicates a fourth duration (i.e., the time slot interval between the time slot where the first DCI is located and the time slot where the PDSCH is located) and a fifth duration (i.e., the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located), for example, the fourth duration is K0 and the fifth duration is K1. The second DCI is transmitted in time slot n2, which indicates a first duration (i.e., the time slot interval between the time slot where the second DCI is located and the time slot where the PUSCH is located), for example, the first duration is K2. Here, n1 + K0 + K1 = n2 + K2, which ensures that the terminal device transmits the HARQ feedback in the same time slot as the PUSCH.

[0212] In other words, the first scheduling method refers to the network device sending two DCIs to the terminal device in the same or adjacent time slots, one for scheduling downlink data transmission and the other for scheduling uplink data transmission; that is, the two DCIs schedule PDSCH and PUSCH respectively. Optionally, the first scheduling method also includes the PDSCH HARQ feedback being in the same time slot as the PUSCH.

[0213] In one implementation, for AR or AR-like services, when the uplink and downlink traffic volumes of a terminal device are roughly equal, each time the network device schedules downlink data transmission for the terminal device, the terminal device must have uplink data to send to the network device.

[0214] During the seventh time period, the network device will only schedule the terminal device using the first scheduling method. The network device will not schedule uplink data transmission or downlink data transmission for the terminal device separately.

[0215] Correspondingly, during the seventh time period, the terminal device only receives PDSCH and transmits PUSCH using the first scheduling method. The terminal device does not receive PDSCH or transmit PUSCH separately.

[0216] In another implementation, if the uplink traffic of a certain terminal device is greater than the downlink traffic, the network device schedules the terminal device in the first scheduling mode within the seventh time period, or the network device schedules uplink data transmission for the terminal device alone and does not schedule downlink data transmission.

[0217] Correspondingly, during the seventh time period, the terminal device receives PDSCH and transmits PUSCH in the first scheduling mode, or the terminal device receives PDSCH but does not transmit PUSCH.

[0218] In another implementation, if the downlink traffic of a certain terminal device is greater than the uplink traffic, the network device schedules the terminal device in the first scheduling mode within the seventh time period, or the network device schedules downlink data transmission for the terminal device alone and does not schedule uplink data transmission.

[0219] Correspondingly, during the seventh time period, the terminal device receives PDSCH and transmits PUSCH in the first scheduling mode, or the terminal device transmits PUSCH but does not receive PDSCH.

[0220] The aforementioned seventh duration can be pre-set in the network device's settings, or it can be reported to the network device by the terminal device before the network device schedules data transmission for the terminal device, or it can be determined through negotiation between the network device and the terminal device. For example, the seventh duration can be set to 10ms or 100ms.

[0221] In one embodiment, before the network device schedules PDSCH and PUSCH for the terminal device using the first scheduling method, the terminal device may send third indication information to the network device. The third indication information may include the service type, or the transmission interval of the terminal device's uplink service data, or it may include a request for the network device to schedule data transmission for the terminal device using the first scheduling method. Alternatively, the third indication information may also include an indication that the terminal device has a high latency tolerance for its uplink service, or a high latency budget.

[0222] The embodiments described above, based on existing scheduling methods, use two DCIs in the same or adjacent time slots to schedule PDSCH and PUSCH respectively, thereby aligning uplink and downlink data scheduling. This also reduces the duration of invalid PDCCH monitoring by the terminal device, saving power consumption.

[0223] It is understood that the same step or a step or message with the same function in the embodiments of this application can be referenced and learned from each other in different embodiments.

[0224] Based on the above embodiments, this application also provides a communication device, which can be a terminal device. This communication device has the functions of the terminal devices in the various possible embodiments described above. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0225] In one possible design, such as Figure 14As shown, the communication device 1400 may include a transceiver unit 1401 and a processing unit 1402, which can perform the corresponding functions of the terminal device in the various possible embodiments described above.

[0226] For example, referring to step 602 in the above embodiment, the transceiver unit 1401 can be used to receive DCI from the network device. The processing unit 1402 can be used to receive PDSCH according to DCI and send PUSCH according to DCI, wherein the PUSCH includes uplink data.

[0227] Alternatively, in another implementation, refer to Figure 12 In step 1201, the transceiver unit 1401 can be used to send second instruction information to the network device.

[0228] Specifically, the communication device 1400 can realize the functions of the terminal device in the above possible embodiments, as detailed in the foregoing method examples, which will not be repeated here.

[0229] In addition, this application also provides a communication device, which can be a network device. This communication device has the functions of a network device implementing the various possible embodiments described above. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0230] In one possible design, such as Figure 14 As shown, the communication device 1400 may include a transceiver unit 1401 and a processing unit 1402, which can perform the corresponding functions of the network devices in the various possible embodiments described above.

[0231] For example, referring to step 601 in the above embodiment, the transceiver unit 1401 can be used to send the DCI to the terminal device. The processing unit 1402 can be used to generate the DCI that simultaneously schedules the PDSCH and PUSCH.

[0232] Alternatively, in another implementation, refer to Figure 12 In step 1202, the transceiver unit 1401 can be used to receive the second indication information and send the configuration parameters corresponding to PUSCH to the terminal device.

[0233] Specifically, the communication device 1400 can implement the functions of the network device in the various possible implementations described above. For details, please refer to the detailed descriptions in the aforementioned method examples, which will not be repeated here.

[0234] Understandable, combined Figure 2As shown, when the device is an electronic device, the transmission module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a baseband chip. When the device is a component having the functions of the first communication device and / or the second communication device in the above embodiments, the transmission module can be a radio frequency unit, and the processing module can be a processor. When the device is a chip system, the transmission module can be the input interface and / or output interface of the chip system, and the processing module can be the processor of the chip system, such as a central processing unit (CPU).

[0235] It should be noted that the specific execution process and embodiments in the above-mentioned device can refer to the steps and related descriptions executed by the terminal device or network device in the above-mentioned method embodiments. The technical problems solved and the technical effects brought about can also refer to the content described in the foregoing embodiments, and will not be repeated here.

[0236] In this embodiment, the communication device is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to specific circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the transmission device for this side link can employ the aforementioned... Figure 2 As shown in the figure.

[0237] For example, Figure 14 The function / implementation process of the processing unit 1402 can be achieved through... Figure 2 The processor 201 in the memory calls computer program instructions stored in memory 204 to implement the function. For example, Figure 14 The function / implementation process of the intermediate transceiver unit 1401 can be achieved through... Figure 2 The communication interface 203 in the middle.

[0238] In some implementations... Figure 2 The processor 201 can call computer execution instructions stored in the memory 204, so that the device 200 can perform the operations of the terminal device or network device in the above-described method embodiments, and implement the above-described possible implementation methods of this application.

[0239] The communication group devices in the above-described device embodiments can completely correspond to the terminal devices or network devices in the method embodiments, with corresponding modules or units performing the corresponding steps. For example, when the device is implemented as a chip, the transceiver unit can be an interface circuit for the chip to receive signals from other chips or devices. The transceiver unit used for sending or receiving is an interface circuit of the device, used to send signals to other devices. For example, when the device is implemented as a chip, the transceiver unit can be an interface circuit for sending signals to other chips or devices.

[0240] In an exemplary embodiment, a computer-readable storage medium or a computer program product including instructions is also provided, which can be executed by the processor 201 of the communication device 200 to perform the methods of the above embodiments. Therefore, the technical effects obtained can be referred to the above method embodiments, and will not be repeated here.

[0241] This application also provides a computer program product including instructions that, when executed, enable the computer to perform operations corresponding to the terminal device or network device described above.

[0242] This application also provides a system-on-a-chip (SoC) comprising a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuitry. The processing unit can execute computer instructions to cause the communication device to which the chip is applied to perform the operations of the terminal device and network device in the methods provided in the embodiments of this application.

[0243] Optionally, any of the communication devices provided in the above embodiments of this application may include the system chip.

[0244] Optionally, the computer instructions are stored in a storage unit.

[0245] This application also provides a communication system, which may include any of the terminal devices and network devices described in the above embodiments.

[0246] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

[0247] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0248] In conjunction with the above, this application also provides the following embodiments:

[0249] Example 1: A communication method applied to a terminal device, the method comprising: receiving downlink control information (DCI) from a network device, wherein the DCI schedules the transmission of a physical downlink shared channel (PDSCH) and simultaneously schedules the transmission of a physical uplink shared channel (PUSCH); receiving the PDSCH according to the DCI; and sending the PUSCH according to the DCI, wherein the PUSCH includes uplink data.

[0250] Example 2: According to the method described in Example 1, before the terminal device receives the DCI from the network device, the method further includes: receiving first configuration information from the network device, the first configuration information indicating the transmission parameters of the PUSCH, the transmission parameters including frequency domain resource allocation information and / or time domain resource allocation information.

[0251] Example 3: The method according to Example 2 includes: time-domain resource allocation information including a first duration, the first duration being the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

[0252] Example 4: The method according to Example 2 includes: first configuration information including a period value, the period value being used to determine the periodic time-domain resources that the PUSCH can use.

[0253] Example 5: The method according to Example 4 includes: the time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located; or, the time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located at a second time interval, the second time interval being the first time interval or the third time interval reported by the terminal device.

[0254] Example 6: The method according to Example 1 or Example 2 includes: DCI indicating a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; sending the PUSCH according to the DCI specifically includes: determining a first duration according to the fourth duration and the fifth duration, wherein the first duration is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, and sending the PUSCH to the network device according to the first duration.

[0255] Example 7: According to the method described in Example 2, the method further includes: receiving second configuration information from the network device, the second configuration information configuring M orthogonal frequency division multiplexing (OFDM) symbol positions, the M OFDM symbol positions being used for the transmission of the PUSCH, each OFDM symbol position corresponding to a fifth duration value, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

[0256] Example 8: According to the method described in Example 7, sending PUSCH based on DCI specifically includes: determining the OFDM symbol position corresponding to the fifth duration indicated by the DCI; and sending the PUSCH at the OFDM symbol position.

[0257] Example 9: The method according to any one of Examples 1 to 8 includes: the transmission parameters further include at least one of HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

[0258] Example 10: The method according to any one of Examples 1 to 8 includes: the DCI includes at least one of HPN, DAI, RV or MCS indication.

[0259] Example 11: The method according to Example 10 includes: the HARQ process number HPN of the PDSCH is the same as the HPN of the PUSCH; the new data indication DAI of the PDSCH is the same as the DAI of the PUSCH; and the redundant version RV of the PDSCH is the same as the RV of the PUSCH.

[0260] Example 12: The method according to any one of Examples 1 to 11 includes: the DCI includes a first field, the first field being used to indicate whether the DCI schedules the PUSCH transmission.

[0261] Example 13. The method according to any one of Examples 1 to 12, further comprising: receiving third configuration information from the network device, the third configuration information including N sets of first configuration information for transmitting PUSCH, the first configuration information being used to indicate transmission parameters for transmitting PUSCH, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication; the DCI includes first indication information, the first indication information being used to indicate one of the N sets of first configuration information.

[0262] Example 14: According to any one of Examples 1 to 13, before receiving DCI from a network device, the method further includes: sending second indication information to the network device, the second indication information including a service type, or the transmission interval of uplink service data of the terminal device, or the second indication information including configuration parameters for requesting the network device to configure the PUSCH; the configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

[0263] Example 15: A communication method applied to a network device, the method comprising: sending downlink control information (DCI) to a terminal device, wherein the DCI schedules the transmission of the physical downlink shared channel (PDSCH) and simultaneously schedules the transmission of the physical uplink shared channel (PUSCH).

[0264] Example 16: According to the method described in Example 15, before sending downlink control information (DCI) to the terminal device, the method further includes: sending first configuration information to the terminal device, wherein the first configuration information instructs the terminal device to send transmission parameters for the PUSCH, and the transmission parameters include frequency domain resource allocation information and / or time domain resource allocation information.

[0265] Example 17: According to the method described in Example 16, the time-domain resource allocation information includes a first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

[0266] Example 18: According to the method described in Example 16, the first configuration information includes a period value, which is used to indicate the periodic time domain resources that the PUSCH sent by the terminal device can use.

[0267] Example 19: According to the method described in Example 18, the time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located; or, the time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located at a second time interval, where the second time interval is the first time interval or the third time interval reported by the terminal device.

[0268] Example 20: According to the method described in Example 15 or Example 16, the DCI indicates a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; the fourth duration and the fifth duration are used by the terminal device to determine a first duration, the first duration being the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, and to send the PUSCH to the network device according to the first duration.

[0269] Example 21: The method according to Example 16 includes: sending second configuration information to the terminal device, the second configuration information configuring M orthogonal frequency division multiplexing (OFDM) symbol positions, the M OFDM symbol positions being used for the transmission of the PUSCH, each OFDM symbol position corresponding to a fifth duration value, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

[0270] Example 22: According to the method described in Example 21, the DCI includes an indication of the fifth duration, used to instruct the terminal device to determine the OFDM symbol position corresponding to the fifth duration.

[0271] Example 23: According to any one of Examples 15 to 22, the transmission parameters further include at least one of HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

[0272] Example 24: The method according to any one of Examples 15 to 22, wherein the DCI includes at least one of HPN, DAI, RV or MCS indication.

[0273] Example 25: According to the method described in Example 24, the HARQ process number HPN of the PDSCH is the same as the HPN of the PUSCH; the new data indication DAI of the PDSCH is the same as the DAI of the PUSCH; and the redundant version RV of the PDSCH is the same as the RV of the PUSCH.

[0274] Example 26: According to any one of Examples 15 to 25, the DCI includes a first field, which is used to indicate whether the DCI schedules the PUSCH transmission.

[0275] Example 27. The method according to any one of Examples 15 to 26, further comprising: sending third configuration information to the network device, the third configuration information including N sets of first configuration information for transmitting PUSCH, the first configuration information being used to indicate transmission parameters for transmitting PUSCH, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV, or MCS indication; the DCI includes first indication information, the first indication information being used to indicate one of the N sets of first configuration information.

[0276] Example 28: According to any one of Examples 15 to 27, before sending downlink control information (DCI) to the terminal device, the method further includes: receiving second indication information from the terminal device, the second indication information including a service type, or the transmission interval of uplink service data of the terminal device, or the second indication information including a request for the network device to configure configuration parameters corresponding to the PUSCH to the terminal device; the configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

[0277] Example 29: A communication method applied to a terminal device, the method comprising: receiving a PDSCH in a first scheduling mode, and transmitting a PUSCH; the first scheduling mode comprising: receiving a first DCI and a second DCI from a network device within a sixth time period, wherein the first DCI is used to schedule the transmission of the Physical Downlink Shared Channel (PDSCH), and the second DCI is used to schedule the transmission of the Physical Uplink Shared Channel (PUSCH), wherein the HARQ feedback corresponding to the PDSCH is transmitted in the same time slot as the PUSCH; receiving the PDSCH according to the first DCI, and transmitting the PUSCH according to the second DCI, wherein the PUSCH includes uplink data.

[0278] Example 30: The method according to Example 29 includes: within a seventh time period, the terminal device only receives PDSCH and transmits PUSCH using a first scheduling method, and the terminal device does not receive PDSCH or transmit PUSCH separately; or, within the seventh time period, the terminal device receives PDSCH and transmits PUSCH using the first scheduling method, or the terminal device receives PDSCH but does not transmit PUSCH separately; or, within the seventh time period, the terminal device receives PDSCH and transmits PUSCH using the first scheduling method, or the terminal device transmits PUSCH but does not receive PDSCH separately.

[0279] Example 31: The method according to Example 29 or Example 30 includes: before receiving the first DCI and the second DCI from the network device, the method further includes: sending third indication information to the network device, the third indication information including service type, or, the transmission interval of uplink service data of the terminal device, or, the third indication information including a request for the network device to schedule data transmission in the first scheduling mode.

[0280] Example 32: The method described in Examples 29 to 31 includes: the sixth duration corresponds to the same time slot or two adjacent time slots.

[0281] Example 33: A terminal device, the terminal device including one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when the one or more processors execute the computer instructions, cause the terminal device to perform the method as described in Examples 1 to 14, or as described in any one of Examples 29 to 32.

[0282] Example 34: A network device, the terminal device including one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when the one or more processors execute the computer instructions, cause the network device to perform the method as described in any one of Examples 15 to 28.

[0283] Example 35: A computer-readable storage medium storing computer-executable instructions, which, when invoked by the computer, cause the computer to perform any one of Examples 1-14 above, or any one of Examples 15 to 28 above, or any one of Examples 29 to 32 above.

[0284] Example 36: A chip coupled to a memory for reading and executing program instructions stored in the memory to implement the method described in any one of Examples 1-14 above, or the method described in any one of Examples 15 to 28 above, or the method described in any one of Examples 29 to 32 above.

[0285] Example 37: A computer program product, when the computer program product is run on a computer, causes the computer to perform the method as described in any one of Examples 1-14 above, or the method as described in any one of Examples 15 to 28 above, or the method as described in any one of Examples 29 to 32 above.

[0286] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Receive first configuration information from a network device, the first configuration information indicating transmission parameters of the Physical Uplink Shared Channel (PUSCH), the transmission parameters including frequency domain resource allocation information and / or time domain resource allocation information; The network device receives Downlink Control Information (DCI), which schedules the transmission of the Physical Downlink Shared Channel (PDSCH) and also schedules the transmission of the Physical Uplink Shared Channel (PUSCH). The DCI indicates that the transmission slot of the PUSCH is the slot where the Hybrid Automatic Repeat Request (HARQ) feedback of the PDSCH is located. Alternatively, the first configuration information includes a period value, which is used to determine the periodic time-domain resources that the PUSCH can use. Receive the PDSCH according to the DCI; The PUSCH, which includes uplink data, is sent according to the DCI.

2. The method according to claim 1, characterized in that, The time-domain resource allocation information includes a first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

3. The method according to claim 1 or 2, characterized in that, The time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located; Alternatively, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located, with a second duration after the second duration, where the second duration is the first duration or the third duration reported by the terminal device.

4. The method according to claim 1 or 2, characterized in that, The DCI indicates a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; Sending the PUSCH according to the DCI specifically includes: A first duration is determined based on the fourth duration and the fifth duration. The first duration is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located. The PUSCH is sent to the network device based on the first duration.

5. The method according to claim 1, characterized in that, The method further includes: The system receives second configuration information from the network device. The second configuration information configures M orthogonal frequency division multiplexing (OFDM) symbol positions. The M OFDM symbol positions are used for the transmission of the PUSCH. Each OFDM symbol position corresponds to a value of a fifth duration, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

6. The method according to claim 5, characterized in that, Sending the PUSCH according to the DCI specifically includes: The OFDM symbol position corresponding to the fifth duration is determined based on the fifth duration indicated by the DCI; The PUSCH is sent at the OFDM symbol location.

7. The method according to claim 1 or 2, characterized in that, The transmission parameters also include at least one of the following: HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

8. The method according to claim 1 or 2, characterized in that, The DCI includes at least one of HPN, DAI, RV, or MCS indications.

9. The method according to claim 8, characterized in that, The HARQ process number HPN of the PDSCH is the same as that of the PUSCH; the new data indication DAI of the PDSCH is the same as that of the PUSCH; and the redundant version RV of the PDSCH is the same as that of the PUSCH.

10. The method according to claim 1 or 2, characterized in that, The DCI includes a first field, which is used to indicate whether the DCI schedules the PUSCH transmission.

11. The method according to claim 1 or 2, characterized in that, The method further includes: Receive third configuration information from the network device, the third configuration information including N sets of first configuration information for transmitting PUSCH, the first configuration information being used to indicate transmission parameters for transmitting PUSCH, wherein the transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV or MCS indication; The DCI includes first indication information, which is used to indicate one of the N sets of first configuration information.

12. The method according to claim 1 or 2, characterized in that, Before receiving DCI from the network device, the method further includes: Send a second indication message to the network device. The second indication message includes a service type, or the transmission interval of the uplink service data of the terminal device, or the second indication message includes a request for the network device to configure the configuration parameters corresponding to the PUSCH. The configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

13. A communication method, characterized in that, Applied to network devices, the method includes: Send first configuration information to the terminal device, the first configuration information instructing the terminal device to send PUSCH transmission parameters, the transmission parameters including frequency domain resource allocation information and / or time domain resource allocation information. Downlink control information (DCI) is sent to the terminal device. The DCI schedules the transmission of the Physical Downlink Shared Channel (PDSCH) and also schedules the transmission of the Physical Uplink Shared Channel (PUSCH). The DCI indicates that the transmission time slot of the PUSCH is the time slot where the Hybrid Automatic Repeat Request (HARQ) feedback of the PDSCH is located. Alternatively, the first configuration information includes a period value, which is used to determine the periodic time domain resources that the PUSCH can use.

14. The method according to claim 13, characterized in that, The time-domain resource allocation information includes a first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located.

15. The method according to claim 13 or 14, characterized in that, The time slot where PUSCH is located is the first periodic time domain resource after the time slot where DCI is located; Alternatively, the time slot where the PUSCH is located is the first periodic time domain resource after the time slot where the DCI is located, with a second duration after the second duration, where the second duration is the first duration or the third duration reported by the terminal device.

16. The method according to claim 13, characterized in that, The DCI indicates a fourth duration and a fifth duration, wherein the fourth duration is the time slot interval between the time slot where the DCI is located and the time slot where the PDSCH is located, and the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located; The fourth duration and the fifth duration are used by the terminal device to determine the first duration, which is the time slot interval between the time slot where the DCI is located and the time slot where the PUSCH is located, and to send the PUSCH to the network device according to the first duration.

17. The method according to claim 13, characterized in that, The method further includes: Send second configuration information to the terminal device. The second configuration information configures M orthogonal frequency division multiplexing (OFDM) symbol positions. The M OFDM symbol positions are used for the transmission of the PUSCH. Each OFDM symbol position corresponds to a value of a fifth duration, wherein the fifth duration is the time slot interval between the time slot where the PDSCH is located and the time slot where the HARQ feedback of the PDSCH is located.

18. The method according to claim 17, characterized in that, The DCI includes an indication of the fifth duration, which is used to instruct the terminal device to determine the OFDM symbol location corresponding to the fifth duration.

19. The method according to claim 13 or 14, characterized in that, The transmission parameters also include at least one of the following: HARQ process number HPN, downlink allocation indicator DAI, redundancy version RV, or modulation and coding scheme MCS.

20. The method according to claim 13 or 14, characterized in that, The DCI includes at least one of HPN, DAI, RV, or MCS indications.

21. The method according to claim 20, characterized in that, The HARQ process number HPN of the PDSCH is the same as that of the PUSCH; the new data indication DAI of the PDSCH is the same as that of the PUSCH; and the redundant version RV of the PDSCH is the same as that of the PUSCH.

22. The method according to claim 13 or 14, characterized in that, The DCI includes a first field, which is used to indicate whether the DCI schedules the PUSCH transmission.

23. The method according to claim 13 or 14, characterized in that, The method further includes: Send third configuration information to the network device. The third configuration information includes N sets of first configuration information for transmitting PUSCH. The first configuration information is used to indicate the transmission parameters for transmitting PUSCH. The transmission parameters include at least one of frequency domain resource allocation information, time domain resource allocation information, HPN, DAI, RV or MCS indication. The DCI includes first indication information, which is used to indicate one of the N sets of first configuration information.

24. The method according to claim 13 or 14, characterized in that, Before sending downlink control information (DCI) to the terminal device, the method further includes: The system receives a second indication from the terminal device. The second indication includes a service type, or the transmission interval of the uplink service data of the terminal device, or the second indication includes a request for the network device to configure the configuration parameters corresponding to the PUSCH to the terminal device. The configuration parameters include at least one of the first configuration information, the second configuration information, or the third configuration information.

25. A terminal device, characterized in that, include: One or more processors and one or more memories; The one or more memories are coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the terminal device to perform the method as described in any one of claims 1-12.

26. A network device, characterized in that, include: One or more processors and one or more memories; The one or more memories are coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the network device to perform the method as described in any one of claims 13-24.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked by the computer, cause the computer to perform the method of any one of claims 1-12, or the method of any one of claims 13-24.

28. A chip, characterized in that, The chip is coupled to a memory for reading and executing program instructions stored in the memory. The chip includes units or modules for implementing the method as described in any one of claims 1-12, or includes units or modules for implementing the method as described in any one of claims 13-24.

29. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-12, or the method as described in any one of claims 13-24.

Images