WO2024055668A1

WO2024055668A1 - Data transmission method and apparatus

Info

Publication number: WO2024055668A1
Application number: PCT/CN2023/101746
Authority: WO
Inventors: 韩煦; 纪永昭; 翟鹏
Original assignee: 华为技术有限公司
Priority date: 2022-09-13
Filing date: 2023-06-21
Publication date: 2024-03-21
Also published as: CN117715161A

Abstract

The present application provides a data transmission method and apparatus, facilitating reduction of the power consumption of a terminal device. The method can be applied to the terminal device. The terminal device is currently in a first discontinuous reception (DRX) cycle. The method comprises: acquiring uplink data generated from a first uplink service, wherein the service type of the first uplink service is a non-low-latency service; determining that the terminal device is in a sleep state when acquiring the uplink data; sending the uplink data to a network device within an activation period in a second DRX cycle, wherein the second DRX cycle is a DRX cycle after the first DRX cycle.

Description

Data transmission method and device

This application claims priority to the Chinese patent application with application number 202211110292.5 and the application name "Data Transmission Method and Device" submitted on September 13, 2022, the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communications, and more specifically, to a data transmission method and device.

Background technique

Discontinuous reception (DRX) means that the terminal device only turns on the receiver to enter the active state at the necessary time to receive downlink data and signaling, and turns off the receiver to enter the dormant state at other times to stop receiving downlink data and signaling. This is a working mode that saves the power consumption of terminal equipment.

For example, the terminal device and the network device can negotiate and align a DRX cycle. The DRX cycle can include an activation period and a sleep period. During the activation period, the terminal device turns on the receiver and enters the active state to receive downlink data sent by the network device. and signaling. During the sleep period, the terminal device turns off the receiver and enters the sleep state, stopping receiving downlink data and signaling sent by the network device.

Further, if uplink data arrives after the terminal device enters the sleep state, the terminal device will be forced to wake up, and then send the uplink data to the network device. After completing the transmission of the uplink data, the terminal device enters the sleep state.

However, since the uplink data itself has its own business attributes, such as web page data, video data, background data, heartbeat data, game data, voice data, etc., and some of these services are not sensitive to delay or have low priority, such as games. For services other than data and voice data, if these uplink data are treated indiscriminately and all are forced to wake up, it will be very detrimental to the power consumption of the terminal equipment.

Contents of the invention

This application provides a data transmission method and device, which is beneficial to reducing the power consumption of terminal equipment.

In a first aspect, embodiments of the present application provide a data transmission method. The method is used for a terminal device. The terminal device is currently in the first discontinuous reception DRX cycle. The method may include: acquiring uplink data generated by the first uplink service, The service type of the first uplink service is a non-low-latency service; it is determined that the terminal device is in a sleep state when acquiring the uplink data; during the activation period in the second DRX cycle, the uplink data is sent to the network device, wherein, the The second DRX cycle is the DRX cycle after the first DRX cycle.

Using the data transmission method provided by the embodiments of the present application, when the terminal device obtains the uplink data to be transmitted while it is in the sleep state, and the uplink data is data generated by non-low-latency services, it can temporarily not be in the current location. The terminal device is forced to wake up within a DRX cycle, but sends the uplink data to the network device during the activation period of the DRX cycle after the first DRX cycle. This can avoid the terminal device being in a sleep state during the first DRX cycle. is forced to wake up, therefore, the power consumption of the terminal device can be reduced.

Optionally, the second DRX cycle may be adjacent to the first DRX cycle or not, which is not limited in this embodiment of the present application. For example, the second DRX cycle may be a DRX cycle next to the first DRX cycle.

In a possible implementation, after determining that the terminal device is in a sleep state when acquiring the uplink data, the method further includes: caching the uplink data.

Using the data transmission method provided by the embodiments of this application, the terminal device identifies uplink data services that are insensitive to delay and have low priority. If the uplink data generated by such services arrives during the sleep period of the first DRX cycle, the terminal The device caches uplink data, does not trigger uplink scheduling requests, and does not perform forced wake-up. When the next DRX activation period arrives, it sends an uplink scheduling request with the activation period to apply for uplink authorization, and schedules uplink data to obtain power consumption. income.

In a possible implementation, sending the uplink data to the network device during the activation period in the second DRX cycle includes: determining that the physical downlink shared channel PDSCH exists during the activation period in the second DRX cycle, the PDSCH is used to transmit downlink data; the uplink data is sent to the network device on the first physical uplink shared channel PUSCH, where the first PUSCH includes a first time period, and the first time period belongs to the second DRX cycle activation period.

Using the data transmission method provided by the embodiment of the present application, when the uplink data arrives in the first DRX cycle, the terminal device is not forced to wake up. After N milliseconds, the activation period of the next DRX cycle arrives. If there is a PDSCH in the activation period of the next DRX cycle, the terminal device will send the uplink data to the network device during the activation period of the next DRX cycle, that is, there is no need to specifically Line data forces the terminal device to wake up, thus saving power consumption.

In a possible implementation, before sending the uplink data to the network device on the first physical uplink shared channel PUSCH, the method further includes: waking up the terminal device at the first moment, wherein the PDSCH includes The second time period, the second time period and the first time both belong to the activation period in the second DRX cycle, and the starting time of the first time period and the starting time of the second time period are not earlier than at that first moment.

In a possible implementation, sending the uplink data to the network device during the activation period in the second DRX cycle includes: determining that there is no physical downlink shared channel PDSCH during the activation period in the second DRX cycle; Wake up the terminal equipment at a second time, where the second time belongs to the activation period in the second DRX cycle; send the uplink data to the network equipment on the second PUSCH, where the second PUSCH includes the second time period, the second time period belongs to the activation period in the second DRX cycle, and the starting time of the second time period is not earlier than the second time.

In the prior art, when the terminal device is in the sleep state during the first DRX cycle, the terminal device wakes up as soon as the uplink data arrives, and then sends a scheduling request to the network to apply for uplink authorization when the sending time of the scheduling request arrives. Send uplink data to the network device after authorization.

Using the data transmission method provided by the embodiment of the present application, when the uplink data arrives in the first DRX cycle, the terminal device is not forced to wake up. After N milliseconds, the activation period of the next DRX cycle arrives. If there is no PDSCH in the activation period of the next DRX cycle, the terminal equipment needs to first calculate the starting time for sending the uplink scheduling request during the activation period of the next DRX cycle, and send the uplink scheduling request as close as possible to the starting time. Wake up the terminal device, then send a scheduling request to the network device to apply for uplink authorization at the starting time of sending the scheduling request, and send the uplink data to the network device after authorization. That is to say, this application delays waking up the terminal device as much as possible, and therefore can save power consumption between the terminal device being woken up and sending the scheduling request.

In addition, although the uplink data is data for non-low-latency services, forcibly waking up the terminal equipment during the activation period of the second DRX cycle to send uplink data is compared to forcibly waking up the terminal equipment during the sleep period of the second DRX cycle. It is said that uplink data can be sent to network equipment earlier, thereby improving data transmission efficiency and ensuring data timeliness as much as possible.

That is to say, in the scenario where there is no PDSCH during the activation period of the first DRX, the wake-up of the terminal device can be delayed according to the sending time of the scheduling request, and further power consumption benefits can be obtained.

In a second aspect, embodiments of the present application also provide a data transmission device, which is used for terminal equipment. The terminal equipment is currently in the first discontinuous reception DRX cycle. The device includes: a processor and a communication interface, the processor and The communication interface is coupled, and the processor is configured to: obtain uplink data generated by a first uplink service, the service type of which is a non-low-latency service; determine that the terminal device is in a sleep state when obtaining the uplink data; During the activation period of two DRX cycles, the uplink data is sent to the network device through the communication interface, wherein the second DRX cycle is the DRX cycle after the first DRX cycle.

In a possible implementation, the device further includes: a memory configured to cache the uplink data after the processor determines that the terminal device is in a sleep state when acquiring the uplink data.

In a possible implementation, the processor is specifically configured to: determine that a physical downlink shared channel PDSCH exists during the activation period in the second DRX cycle, and the PDSCH is used to transmit downlink data; on, sending the uplink data to the network device through the communication interface, wherein the first PUSCH includes a first time period, and the first time period belongs to the activation period in the second DRX cycle.

In a possible implementation, the processor is also configured to wake up the terminal device at the first moment before sending the uplink data to the network device through the communication interface on the first physical uplink shared channel PUSCH, wherein, The PDSCH includes a second time period, the second time period and the first time both belong to the activation period in the second DRX cycle, and the starting time of the first time period and the starting time of the second time period The time is no earlier than the first time.

In a possible implementation, the processor is specifically configured to: determine that there is no physical downlink shared channel PDSCH during the activation period in the second DRX cycle; wake up the terminal device at the second moment, wherein the second moment Belongs to the activation period in the second DRX cycle; on the second PUSCH, sends the uplink data to the network device through the communication interface, wherein the second PUSCH includes a second time period, and the second time period belongs to the The activation period in the second DRX cycle, and the starting time of the second time period is not earlier than the second time.

In a third aspect, embodiments of the present application further provide a chip device, including at least one processor and an interface circuit. The interface circuit is used to provide data transmission or reception for the at least one processor. When the at least one processor executes a program code or instructions to implement the method described in the above first aspect or any possible implementation manner thereof.

In a fourth aspect, embodiments of the present application further provide a terminal device, which includes the above second aspect or any possible implementation thereof. The data transmission device described in the present manner may include the chip device described in the third aspect.

In a fifth aspect, embodiments of the present application further provide a computer-readable storage medium for storing a computer program. The computer program includes instructions for implementing the method described in the above-mentioned first aspect or any possible implementation manner thereof.

In a sixth aspect, embodiments of the present application further provide a computer program product. The computer program product contains instructions. When the instructions are run on a computer or a processor, the computer or the processor implements the first aspect or other aspects thereof. Any possible implementation of the method described.

The data transmission device, chip device, terminal equipment, computer storage medium and computer program product provided by the embodiments of the present application are all used to execute the data transmission method provided above. Therefore, the beneficial effects they can achieve can be referred to the above. The beneficial effects of the provided data transmission method will not be described again here.

Description of drawings

Figure 1 is a schematic block diagram of a data transmission system 100 according to an embodiment of the present application;

Figure 2 is a schematic block diagram of the protocol architecture 200 of the terminal device according to the embodiment of the present application;

Figure 3 is a schematic flow chart of downlink data transmission of terminal equipment in the prior art;

Figure 4 is another schematic flow chart of downlink data transmission of terminal equipment in the prior art;

Figure 5 is a schematic flow chart of uplink data transmission of terminal equipment in the prior art;

Figure 6 is a schematic flow chart of the data transmission method 300 according to the embodiment of the present application;

Figure 7 is a schematic flowchart of uplink data transmission of a terminal device according to an embodiment of the present application;

Figure 8 is a schematic flow chart of another uplink data transmission of the terminal device according to the embodiment of the present application;

Figure 9 is a schematic flow chart of the data transmission method 400 according to the embodiment of the present application;

Figure 10 is a schematic block diagram of the data transmission device 500 provided by the embodiment of the present application;

Figure 11 is a schematic block diagram of a data transmission device 600 provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

First, let's introduce the data transmission system used by the data transmission method and device provided by the embodiments of the present application.

FIG. 1 shows a schematic block diagram of a data transmission system 100 provided by an embodiment of the present application. The system 100 may include at least one network device, such as the network device 110 shown in FIG. 1 . The network device 110 can provide communication coverage for a specific geographical area, and can perform data transmission with terminal devices located in the coverage area.

Optionally, the network device 110 may be an evolved base station (eNB or eNodeB) in a long term evolution (long term evolution, LTE) system, or a cloud radio access network (cloud radio access network, CRAN) wireless controller in . The network equipment can also be a core network, a relay station, an access point, a vehicle-mounted device, a wearable device, a network-side device in a future fifth generation (5G) network, or a future evolved public land mobile network (public land mobile network). network, network equipment in PLMN), etc.

The system 100 may also include at least one terminal device located within the coverage of the network device 110, such as the terminal device 120 shown in FIG. 1 . The terminal device 120 may be a device that provides voice/data connectivity to the user.

Optionally, the terminal device can be a mobile phone (mobile phone), tablet computer, notebook computer, handheld computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality device Augmented reality (AR) devices, wireless terminals in self-driving (selfdriving), cellular phones, cordless phones, session initiation protocol (SIP) phones, personal digital assistants (PDA), with Handheld devices, computing devices, vehicle-mounted devices, smart home devices, wearable devices with wireless communication functions, terminal devices in 5G networks or terminal devices in future evolved public land mobile communication networks (public land mobile network, PLMN), etc. The embodiments of the present application do not limit this. Among them, wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.

It should be noted that FIG. 1 only illustrates one network device and one terminal device, but the embodiment of the present application is not limited thereto. Optionally, the system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices, which is not limited in the embodiments of this application.

Optionally, the system 100 may also include other network entities such as a network controller and a mobility management entity, to which the embodiments of the present application are not limited.

In a possible implementation, as shown in Figure 1 , sending data from the network device 110 to the terminal device 120 is called downlink data transmission, and sending data from the terminal device 120 to the network device 110 is called uplink data transmission.

The protocol architecture of the terminal device 120 in the system 100 is introduced below.

Figure 2 shows a schematic block diagram of the protocol architecture 200 of the terminal device provided by the embodiment of the present application. As shown in Figure 2, the protocol architecture 200 from the top to the bottom may include: application (APP) layer 210, packet data convergence protocol (packet data convergence protocol, PDCP) layer 220, media access control (medium access control, MAC) layer 230 and physical layer (physical, PHY) layer 240. Among them, the physical layer 240 belongs to layer one, the PDCP layer 220 and the MAC layer 230 belong to layer two, and layer one and layer two may belong to the modem of the terminal device.

It should be noted that only four layers in the protocol structure 200 are schematically shown in FIG. 2 , but the embodiment of the present application is not limited thereto. Optionally, the protocol structure 200 may also include a radio link control (radio link control, RLC) layer, a service data adaptation protocol (service data adaptation protocol, SDAP) layer, etc. Each layer can perform the corresponding functions of each layer. This application The embodiment does not limit this.

The following will exemplarily introduce the downlink data transmission method of terminal equipment in the prior art with reference to FIG. 3 and FIG. 4 .

As shown in Figure 3, taking discontinuous reception (DRX) cycle 1 as an example, the DRX cycle 1 may include an activation period and a sleep period. Among them, before the DRX cycle 1 comes, the terminal device monitors the downlink control information (DCI) from the network device (shaded in Figure 3 shown), the DCI is used to indicate whether there is downlink data to be transmitted during the activation period; if the DCI indicates that there is downlink data to be transmitted during the activation period, the terminal device is awakened at the beginning of the activation period , and monitor the physical downlink control channel (PDCCH), which is used to indicate the physical downlink shared channel (PDSCH) used to transmit downlink data, where the PDSCH includes time period 1 ( As shown in the shadow in Figure 3 shown), this time period 1 belongs to the activation period; the terminal device receives downlink data from the network device on the PUSCH. That is to say, the terminal device is in the awake state during the activation period and is in the sleep state during the sleep period.

As shown in Figure 4, taking discontinuous reception (DRX) cycle 1 as an example, the DRX cycle 1 may include an activation period and a sleep period. Among them, before the DRX cycle 1 comes, the terminal device monitors the downlink control information (DCI) from the network device (shaded in Figure 4 shown), the DCI is used to indicate whether there is downlink data to be transmitted during the activation period; if the PDCCH indicates that there is no downlink data to be transmitted during the activation period, the terminal equipment has been in the sleep state during the activation period (That is, the terminal device will not be awakened during the activation period.) Until the end of the sleep period, the terminal device continues to monitor the DCI of the next DRX cycle. That is to say, the terminal device is in a sleep state during both the activation period and the sleep period.

Taking the uplink transmission method scenario shown in Figure 3 as an example, the following will exemplarily introduce the prior art in conjunction with Figure 5. In this scenario, when the uplink data of the terminal device arrives during the sleep period in the DRX cycle 1, The uplink data transmission method of the terminal device.

As shown in Figure 5, taking Discontinuous Reception (DRX) cycle 1 as an example, if the uplink data of the terminal device arrives during the sleep period of DRX cycle 1, the terminal device is forced to wake up and activate the physical downlink control channel Send a scheduling request to the network device on the (physical uplink control channel, PUCCH). The scheduling request is used to request an uplink authorization. The PUCCH includes time period 1 (shaded in Figure 5 shown); the terminal device receives scheduling information from the network device. The scheduling information is used to indicate the physical uplink shared channel (PUSCH) used to transmit uplink data. The PUSCH includes time period 2 (such as Shadows in Figure 5 shown); the terminal device sends the uplink data to the network device on the PUSCH.

Based on the problems existing in the prior art, this application provides a data transmission method and device, which is beneficial to reducing the power consumption of terminal equipment.

Figure 6 shows a schematic flow chart of the data transmission method 300 provided by the embodiment of the present application. As shown in FIG. 6 , the method 300 can be used for the terminal device 120 described in FIG. 1 . Taking the terminal device using the protocol architecture 200 as shown in Figure 2 as an example, the method 300 can include the following steps S301 to S320. It should be noted that the steps listed below can be executed in various orders and/or occur simultaneously, It is not limited to the execution sequence shown in Figure 6.

S301. The APP layer of the terminal device determines that the service type of the first uplink service is a non-low-latency service.

It should be noted that the non-low-latency services described in the embodiments of this application refer to services that are not sensitive to delays or have low priority.

In a possible implementation, the APP layer can determine the service of the first uplink service according to a preset first mapping relationship. The type is non-low-latency service, and the first mapping relationship is used to indicate the corresponding relationship between the uplink service and the service type. The service type includes low-latency service or non-low-latency service.

In a possible implementation, the non-low-latency services described in this application may refer to services whose expected transmission delay is greater than the preset first delay threshold. The low-latency services described in this application may Refers to services whose expected transmission delay is less than the first delay threshold. For example, the first delay threshold may be 20ms (milliseconds). That is to say, the priority of non-low-latency services is lower than the priority of low-latency services.

For example, the low-latency service described in this application may include one or more of game data and voice data.

For example, the non-low-latency services described in this application may include one or more of web page data, video data, background data, heartbeat data and other data.

Optionally, the first delay threshold described in the embodiment of this application may be an average of the transmission delays of multiple services. For example, the expected transmission delay of video data may be greater than 160 ms, and the expected transmission delay of web page data may be greater than 80 ms.

S302. The APP layer sends the first notification information to layer two (that is, including the PDCP layer and the MAC layer). The first notification information is used to notify that the service type of the first uplink service is a non-low-latency service.

S303. The APP layer sends the uplink data generated by the first uplink service to the PDCP.

S304. The PDCP layer caches the uplink data.

S305. The PDCP layer sends second notification information to the MAC layer. The second notification information is used to notify the PDCP layer that the uplink data is cached.

S306. The MAC layer determines that the terminal device is in a sleep state when acquiring the uplink data.

S307. The MAC layer sends third notification information to the PHY layer of the terminal device. The third notification information is used to notify the PDCP layer that the uplink data is cached, and the uplink data requires DRX after the first DRX cycle. Sent to network devices during the activation period in the cycle.

S308. Based on the third notification message, the PHY layer determines whether there is a PDSCH for transmitting downlink data during the activation period in the second DRX cycle, where the second DRX cycle is the DRX cycle after the first DRX cycle. If it exists, continue to execute S309~S314; if it does not exist, continue to execute S315~S320.

For example, taking the downlink data transmission scenario shown in Figure 3 as an example, Figure 7 shows a schematic flow chart of uplink data transmission of a terminal device provided by an embodiment of the present application, and the process includes the above-mentioned S309-S314.

S309. The PHY layer wakes up the MAC layer at the beginning of the activation period in the second DRX cycle.

S310. The MAC layer receives downlink data from the network device on the PDSCH through the PHY layer, where the PDSCH includes time period a (shaded in Figure 7 shown), the time period a belongs to the activation period in the second DRX cycle, and the starting time of the time period a is not earlier than the starting time of the activation period in the second DRX cycle.

It should be noted that "no earlier" in the embodiments of this application includes equal to or later than.

S311. The MAC layer sends a scheduling request to the network device on the PUCCH through the PHY layer. The scheduling request is used to apply for uplink authorization. The PUCCH includes time period b (shaded in Figure 7 shown), the time period b belongs to the activation period in the second DRX cycle, and the starting time of the time period b is not earlier than the starting time of the activation period in the second DRX cycle.

S312. The MAC layer receives scheduling information from the network device through the PHY layer, and the scheduling information is used to indicate the PUSCH used to transmit the uplink data.

S313. The MAC layer reads the uplink data from the PDCP layer.

S314. The MAC layer sends the uplink data to the network device on the PUSCH through the PHY layer. The PUSCH includes time period c (shaded in Figure 7 shown), the time period c belongs to the activation period in the second DRX cycle, and the starting time of the time period c is not earlier than the end time of the time period b.

Using the data transmission method provided by the embodiment of the present application, when the uplink data arrives in the first DRX cycle, the terminal device is not forced to wake up. After N milliseconds, the activation period of the next DRX cycle arrives. If there is a PDSCH in the activation period of the next DRX cycle, the terminal device will send the uplink data to the network device during the activation period of the next DRX cycle, that is, there is no need to forcefully wake up the terminal device specifically for the uplink data. Therefore, power consumption can be saved.

For example, taking the downlink data transmission scenario shown in Figure 4 as an example, Figure 8 shows a schematic flow chart of uplink data transmission of a terminal device provided by an embodiment of the present application, and the process includes the above-mentioned S315 to S320.

S315. The PHY layer determines the PUCCH used to send scheduling requests during the activation period in the second DRX cycle. Including time period d (shaded in Figure 7 shown).

S316. The PHY layer wakes up the MAC layer before the time period d.

S317. The MAC layer sends a scheduling request to the network device on the PUCCH through the PHY layer. The scheduling request is used to apply for uplink authorization.

S318. The MAC layer receives scheduling information from the network device through the PHY layer, and the scheduling information is used to indicate the PUSCH used to transmit the uplink data.

S319. The MAC layer reads the uplink data from the PDCP layer.

S320. The MAC layer sends the uplink data to the network device on the PUSCH through the PHY layer. The PUSCH includes the time period e (shaded in Figure 8 as shown), the time period e belongs to the activation period in the second DRX cycle, and the starting time of the time period e is not earlier than the end time of the time period d.

Optionally, the second DRX cycle may be the next DRX cycle of the first DRX cycle, or one or more DRX cycles may be spaced between the second DRX cycle and the first DRX cycle. This embodiment of the present application applies This is not limited.

For example, if during the activation period in the next DRX cycle of the first DRX cycle, the network device pre-configures the PDSCH for downlink data transmission for the terminal device, then the second DRX cycle is the first DRX cycle. The next DRX cycle of the cycle.

For example, if the network device does not pre-configure the PDSCH for downlink data transmission for the terminal device during the activation period in the next DRX cycle of the first DRX cycle, then the second DRX cycle is the first DRX cycle. The first DRX cycle in which the PDSCH is configured after the DRX cycle.

It should be noted that if during the activation period in the next DRX cycle of the first DRX cycle, the network device does not pre-configure the PDSCH for downlink data transmission for the terminal device, and in the expected period of non-low-latency services Within the range of the transmission delay, the terminal equipment can wait until the activation period in the first DRX cycle configured with PDSCH after the first DRX cycle arrives, then the terminal equipment can adopt the method shown in Figure 7, in the first DRX cycle During the activation period of the first DRX cycle configured with PDSCH after the DRX cycle, the uplink data is transmitted to the opposite end through the network device; accordingly, if it is within the expected transmission delay range of the non-low-latency service, the terminal If the device does not have time to wait until the activation period in the first DRX cycle configured with PDSCH after the first DRX cycle arrives, the terminal device needs to transmit the uplink data to the opposite end through the network device as early as possible. If the terminal device can In the next DRX cycle of the first DRX cycle, the uplink data is transmitted to the opposite end through the network device in the manner shown in FIG. 8 .

Figure 9 shows a schematic flow chart of the data transmission method 400 provided by the embodiment of the present application. As shown in FIG. 9 , the method 400 can be used for the terminal device 120 described in FIG. 1 . Taking the terminal device currently in the first DRX cycle as an example, the method 400 may include the following steps S401 to S403. It should be noted that the steps listed below may be executed in various orders and/or occur simultaneously, and are not limited to those shown in Figure 9 the execution sequence shown.

S401. Obtain the uplink data generated by the first uplink service. The service type of the first uplink service is a non-low-latency service.

S402. Determine that the terminal device is in a sleep state when acquiring the uplink data.

Optionally, after S402, the method further includes: caching the uplink data.

S403. During the activation period in the second DRX cycle, send the uplink data to the network device, where the second DRX cycle is the DRX cycle after the first DRX cycle.

Optionally, the terminal device being in the sleep state when acquiring the uplink data may include: the terminal device being in the sleep period of the first DRX cycle as shown in Figure 3; or, the terminal device being in the sleep state as shown in Figure 4 activation phase or sleep phase.

In a possible implementation, S403 may include: determining that a physical downlink shared channel PDSCH exists during the activation period in the second DRX cycle, and the PDSCH is used to transmit downlink data; transmitting data to the first physical uplink shared channel PUSCH on the first physical uplink shared channel PUSCH. The network device sends the uplink data, wherein the first PUSCH includes a first time period, and the first time period belongs to the activation period in the second DRX cycle.

Optionally, before sending the uplink data to the network device on the first physical uplink shared channel PUSCH, the method further includes: waking up the terminal device at the first moment, wherein the PDSCH includes a second time period, Both the second time period and the first time belong to the activation period in the second DRX cycle, and the starting time of the first time period and the starting time of the second time period are not earlier than the first time. .

Optionally, after waking up the terminal device at the first moment, the method may further include: the terminal device receiving the downlink data from the network device on the PDSCH.

In another possible implementation, S403 may include: determining that there is no physical downlink shared channel PDSCH during the activation period in the second DRX cycle; waking up the terminal device at the second moment, where the second moment belongs to the The activation period in the second DRX cycle; sending the uplink data to the network device on the second PUSCH, where the second PUSCH includes a second time period, and the second time period belongs to the activation period in the second DRX cycle. period, and the starting time of the second time period is not earlier than the second time.

The data transmission method provided by the embodiment of the present application has been introduced above with reference to Figures 6 to 9. The data transmission device used to perform the above method 200 or method 300 will be further introduced below.

Figure 10 shows a schematic block diagram of a data transmission device 500 provided by an embodiment of the present application. As shown in Figure 10, the device 500 may include a processing unit 501 and a sending unit 502.

Optionally, the device 500 can be used in the above-mentioned system 100. Further, the device 500 can be used in the terminal device 120 in the above-mentioned system 100. For example, the device 500 can be executed by a processor or controller on the terminal device 120. A virtual device formed by software. Wherein, the terminal equipment is currently in the first discontinuous reception DRX cycle.

The processing unit 501 is configured to obtain uplink data generated by a first uplink service, and the service type of the first uplink service is a non-low-latency service; and determine that the terminal device is in a sleep state when obtaining the uplink data.

The sending unit 502 is configured to send the uplink data to the network device during the activation period in the second DRX cycle, where the second DRX cycle is the DRX cycle after the first DRX cycle.

In a possible implementation, the apparatus 500 may further include a storage unit 503, which is configured to cache the uplink data after the processing unit 501 determines that the terminal device is in a sleep state when acquiring the uplink data.

In a possible implementation, the processing unit 501 is also configured to determine that a physical downlink shared channel PDSCH exists during the activation period in the second DRX cycle, and the PDSCH is used to transmit downlink data; the sending unit 502 is specifically configured to The uplink data is sent to the network device on a first physical uplink shared channel PUSCH, where the first PUSCH includes a first time period, and the first time period belongs to the activation period in the second DRX cycle.

In a possible implementation, the processing unit 501 is also configured to wake up the terminal device at the first moment before the sending unit 503 sends the uplink data to the network device on the first physical uplink shared channel PUSCH, where , the PDSCH includes a second time period, the second time period and the first time both belong to the activation period in the second DRX cycle, and the starting time of the first time period and the starting time of the second time period The starting time is no earlier than the first time.

In a possible implementation, the processing unit 501 is also configured to determine that there is no physical downlink shared channel PDSCH during the activation period in the second DRX cycle; wake up the terminal device at the second moment, wherein the second moment Belonging to the activation period in the second DRX cycle; the sending unit 502 is specifically configured to send the uplink data to the network device on the second PUSCH, where the second PUSCH includes a second time period, and the second time period It belongs to the activation period in the second DRX cycle, and the starting time of the second time period is not earlier than the second time.

It should be noted that the information interaction, execution process, etc. between the above units are based on the same concept as the method embodiments of the present application. For details of their specific functions and technical effects, please refer to the method embodiments section, which will not be discussed here. Again. In an optional example , the device 500 can be used to execute various processes and/or steps corresponding to the terminal device in the above-mentioned method 200 or method 300 embodiments. To avoid duplication, they will not be described again here.

One or more of the various modules in the embodiment shown in Figure 10 can be implemented through software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or code and may be executed by a hardware processor. The hardware includes but is not limited to various integrated circuits, such as central processing unit (CPU), digital signal processor (DSP), field programmable gate array (FPGA) or dedicated Integrated circuit (ASIC, Application Specific Integrated Circuit).

Please refer to Figure 11. Figure 11 shows a schematic block diagram of a data transmission device 600 provided by an embodiment of the present application. The device 600 may include a processor 601 and a communication interface 602. The processor 601 is coupled to the communication interface 602.

In an optional example, those skilled in the art can understand that the device 600 may be specifically (or used for) a terminal device in the above method 200, and the device 600 may be the physical hardware structure of the device 500. The device 600 can be used to execute various processes and/or steps corresponding to the terminal device in the above-mentioned method 200 or method 300 embodiments. To avoid duplication, they will not be described again here.

The communication interface 602 is used to input data (such as downlink data) to the processor 601 and/or output data (such as uplink data) from the processor 601; the processor 601 is used to run computer programs or instructions to make the data The transmission device 600 implements the method described in the above method 200 or method 300 embodiment.

The processor 601 in the embodiment of this application includes but is not limited to a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC). ), off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA), discrete gate or transistor logic devices or discrete hardware components, etc. A general-purpose processor can be a microprocessor, a microcontroller, or any conventional processor.

For example, the processor 601 is used to obtain uplink data generated by a first uplink service, and the service type of the first uplink service is a non-low-latency service; determine that the terminal device is in a sleep state when obtaining the uplink data; in the second DRX During the activation period in the cycle, the uplink data is sent to the network device through the communication interface 602, where the second DRX cycle is the DRX cycle after the first DRX cycle.

Optionally, the data transmission device 600 may also include a memory 603.

The memory 603 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).

Specifically, the memory 603 is used to store program codes and instructions of the data transmission device 600 . Optionally, the memory 603 is also used to store data obtained when the processor 601 executes the above method 200 or method 300 embodiments, such as uplink data.

Alternatively, the memory 603 may be a separate device or integrated in the processor 601.

It should be noted that FIG. 11 only shows a simplified design of the data transmission device 600. In practical applications, the data transmission device 600 may also include other necessary components, including but not limited to any number of communication interfaces, processors, controllers, memories, etc., and all data transmission devices 600 that can implement the present application are within the protection scope of this application.

In a possible design, the data transmission device 600 may be a chip device. Optionally, the chip device can also include one or more memories for storing computer execution instructions. When the chip device is running, the processor can execute the computer execution instructions stored in the memory, so that the chip device executes the above command transmission method. .

Optionally, the chip device can be a field programmable gate array, a dedicated integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, or a programmable controller that implements related functions. or other integrated chips.

In a possible design, embodiments of the present application also provide a computer-readable storage medium for storing a computer program, the computer program including instructions for implementing the data transmission method described in the above method 200 or method 300 .

In a possible design, embodiments of the present application also provide a computer program product, the computer program product includes instructions, When the instruction is executed on the computer or the processor, the computer or the processor is caused to implement the data transmission method described in the above-mentioned method 200 or method 300.

It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk or optical disk and other media that can store program code.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

A data transmission method, characterized in that the method is used for terminal equipment, and the terminal equipment is currently in the first discontinuous reception DRX cycle, and the method includes:

Obtaining uplink data generated by the first uplink service, the service type of the first uplink service is non-low-latency service;

Determine that the terminal device is in a sleep state when acquiring the uplink data;

During the activation period in the second DRX cycle, the uplink data is sent to the network device, where the second DRX cycle is the DRX cycle after the first DRX cycle.
The method according to claim 1, characterized in that, after determining that the terminal device is in a sleep state when acquiring the uplink data, the method further includes:

Cache the upstream data.
The method according to claim 1 or 2, characterized in that, during the activation period in the second DRX cycle, sending the uplink data to the network device includes:

Determine that there is a physical downlink shared channel PDSCH during the activation period in the second DRX cycle, and the PDSCH is used to transmit downlink data;

The uplink data is sent to the network device on a first physical uplink shared channel PUSCH, where the first PUSCH includes a first time period, and the first time period belongs to activation in the second DRX cycle. Expect.
The method according to claim 3, characterized in that before sending the uplink data to the network device on the first physical uplink shared channel PUSCH, the method further includes:

Wake up the terminal equipment at a first time, wherein the PDSCH includes a second time period, the second time period and the first time both belong to the activation period in the second DRX cycle, and the Neither the starting time of the first time period nor the starting time of the second time period is earlier than the first time.
The method according to claim 1 or 2, characterized in that, during the activation period in the second DRX cycle, sending the uplink data to the network device includes:

Determine that there is no physical downlink shared channel PDSCH within the activation period in the second DRX cycle;

Wake up the terminal device at a second moment, where the second moment belongs to the activation period in the second DRX cycle;

Send the uplink data to the network device on a second PUSCH, wherein the second PUSCH includes a second time period, the second time period belongs to the activation period in the second DRX cycle, and the The starting time of the second time period is not earlier than the second time.
A data transmission device, characterized in that the device is used for terminal equipment, the terminal equipment is currently in the first discontinuous reception DRX cycle, the device includes: a processor and a communication interface, the processor and the Coupled with a communication interface, the processor is used to:

Obtaining uplink data generated by the first uplink service, the service type of the first uplink service is non-low-latency service;

Determine that the terminal device is in a sleep state when acquiring the uplink data;

During the activation period in the second DRX cycle, the uplink data is sent to the network device through the communication interface, where the second DRX cycle is the DRX cycle after the first DRX cycle.
The device of claim 6, further comprising: a memory,

The memory is used to cache the uplink data after the processor determines that the terminal device is in a sleep state when acquiring the uplink data.
The device according to claim 6 or 7, characterized in that the processor is specifically configured to:

Determine that there is a physical downlink shared channel PDSCH during the activation period in the second DRX cycle, and the PDSCH is used to transmit downlink data;

The uplink data is sent to the network device through the communication interface on the first physical uplink shared channel PUSCH, where the first PUSCH includes a first time period, and the first time period belongs to the first time period. The activation period in the second DRX cycle.
The device according to claim 8, characterized in that:

The processor is also configured to wake up the terminal device at the first moment before sending the uplink data to the network device through the communication interface on the first physical uplink shared channel PUSCH, wherein in the PDSCH Including a second time period, the second time period and the first moment both belong to the activation period in the second DRX cycle, and the starting moment of the first time period and the second time period The starting time is no earlier than the first time.
The device according to claim 6 or 7, characterized in that the processor is specifically configured to:

Determine that there is no physical downlink shared channel PDSCH within the activation period in the second DRX cycle;

Wake up the terminal device at a second moment, where the second moment belongs to the activation period in the second DRX cycle;

On the second PUSCH, the uplink data is sent to the network device through the communication interface, wherein the second PUSCH includes a second time period, and the second time period belongs to the second DRX cycle. activation period, and the starting time of the second time period is not earlier than the second time.
A chip device includes at least one processor and an interface circuit. The interface circuit is used to provide data transmission or reception for the at least one processor. It is characterized in that when the at least one processor executes program code or instructions When, the method described in any one of the above claims 1-5 is implemented.
A computer-readable storage medium used to store a computer program, characterized in that the computer program includes instructions for implementing the method described in any one of claims 1-5.
A computer program product, the computer program product contains instructions, which are characterized in that when the instructions are run on a computer or a processor, the computer or the processor implements any of the above claims 1-5. The method described in one item.