CN117715161A

CN117715161A - Data transmission method and device

Info

Publication number: CN117715161A
Application number: CN202211110292.5A
Authority: CN
Inventors: 韩煦; 纪永昭; 翟鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-09-13
Filing date: 2022-09-13
Publication date: 2024-03-15
Also published as: WO2024055668A1

Abstract

The application provides a data transmission method and device, which are beneficial to reducing the power consumption of terminal equipment. The method may be used for a terminal device that is currently in a first discontinuous reception, DRX, cycle, the method comprising: acquiring uplink data generated by a first uplink service, wherein the service type of the first uplink service is non-low-delay service; determining that the terminal equipment is in a sleep state when acquiring the uplink data; and transmitting the uplink data to the network equipment in an activation period in a second DRX period, wherein the second DRX period is a DRX period after the first DRX period.

Description

Data transmission method and device

Technical Field

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

Background

Discontinuous reception (discontinuous reception, DRX) refers to an operation mode in which the terminal device turns on the receiver to enter an active state only for necessary time to receive downlink data and signaling, and turns off the receiver to enter a sleep state at other times to stop receiving downlink data and signaling, thereby saving power consumption of the terminal device.

For example, the terminal device may negotiate and align with the network device a DRX cycle, where the DRX cycle may include an active period and a sleep period, where the terminal device turns on the receiver to enter the active state during the active period to receive downlink data and signaling sent by the network device, and turns off the receiver to enter the sleep state during the sleep period to stop receiving downlink data and signaling sent by the network device.

Further, if the terminal device arrives after entering the sleep state, the terminal device will be awakened forcefully, then send the uplink data to the network device, and after completing the transmission of the uplink data, the terminal device enters the sleep state.

However, since the uplink data itself carries service attributes such as web page data, video data, background data, heartbeat data, game data, voice data, etc., and some of the services are insensitive to delay or have low priority, such as services other than game data and voice data, if the uplink data are handled indiscriminately and all of them are forcedly awakened, the power consumption of the terminal device is very disadvantageous.

Disclosure of Invention

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

In a first aspect, an embodiment of the present application provides a data transmission method, where the method is used for a terminal device, and the terminal device is currently in a first DRX cycle, and the method may include: acquiring uplink data generated by a first uplink service, wherein the service type of the first uplink service is non-low-delay service; determining that the terminal equipment is in a sleep state when acquiring the uplink data; and transmitting the uplink data to the network equipment in an activation period in a second DRX period, wherein the second DRX period is a DRX period after the first DRX period.

By adopting the data transmission method provided by the embodiment of the application, when the terminal equipment acquires the uplink data to be transmitted when the terminal equipment is in the sleep state, and the uplink data is the data generated by the non-low-delay service, the terminal equipment can be temporarily awakened in the first DRX period where the terminal equipment is currently located, and the uplink data is transmitted to the network equipment in the activation period of the DRX period after the first DRX period, so that the terminal equipment can be prevented from being awakened in the sleep state in the first DRX period, and the power consumption of the terminal equipment can be reduced.

Alternatively, the second DRX cycle may be adjacent to the first DRX cycle or not, which is not limited by the embodiments of the present application. For example, the second DRX cycle may be a next DRX cycle of the first DRX cycle.

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

By adopting the data transmission method provided by the embodiment of the application, the terminal equipment identifies the uplink data service which is insensitive to time delay and low in priority, if uplink data generated by the service arrives in the sleep period of the first DRX period, the terminal equipment performs uplink data caching, temporarily does not trigger an uplink scheduling request, does not perform forced awakening, and when the activation period of the next DRX arrives, the terminal equipment sends the uplink scheduling request along with the activation period to apply for uplink authorization and schedule the uplink data, so that power consumption benefits are obtained.

In one possible implementation, the sending the uplink data to the network device during the active period in the second DRX cycle includes: determining that a Physical Downlink Shared Channel (PDSCH) exists in an activation period of the second DRX period, wherein the PDSCH is used for transmitting downlink data; and sending the uplink data to the network equipment on a first Physical Uplink Shared Channel (PUSCH), wherein the first PUSCH comprises a first time period, and the first time period belongs to an activation period in the second DRX period.

By adopting the data transmission method provided by the embodiment of the application, when uplink data arrives in the first DRX period, the terminal equipment is not compulsorily awakened, and after N milliseconds, the activation period of the next DRX period arrives. If PDSCH exists in the active period of the next DRX cycle, the terminal device sends the uplink data to the network device along with the active period of the next DRX cycle, i.e. without having to wake up the terminal device specifically for the uplink data, so power consumption can be saved.

In one possible implementation, before the sending the uplink data to the network device on the first physical uplink shared channel PUSCH, the method further includes: the terminal equipment is awakened at a first time, wherein the PDSCH comprises a second time period, the second time period and the first time period both belong to an activation period in the second DRX period, 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.

In one possible implementation, the sending the uplink data to the network device during the active period in the second DRX cycle includes: determining that a Physical Downlink Shared Channel (PDSCH) does not exist in an activation period in the second DRX period; waking up the terminal device at a second time, wherein the second time belongs to an active period in the second DRX cycle; and sending the uplink data to the network equipment on a second PUSCH, wherein the second PUSCH comprises a second time period, the second time period belongs to an activation period in the second DRX period, and the starting time of the second time period is not earlier than the second time.

In the prior art, when a terminal device is in a sleep state in a first DRX cycle, the terminal device is first awakened as long as uplink data arrives, then a scheduling request is sent to a network to apply for uplink grant when a sending time of the scheduling request arrives, and the uplink data is sent to the network device after the grant.

By adopting the data transmission method provided by the embodiment of the application, when uplink data arrives in the first DRX period, the terminal equipment is not compulsorily awakened, and after N milliseconds, the activation period of the next DRX period arrives. If the PDSCH does not exist in the active period of the next DRX cycle, the terminal device needs to calculate the starting time of sending the uplink scheduling request in the active period of the next DRX cycle, wake up the terminal device when the starting time is as close as possible, then send the scheduling request to the network device at the starting time of sending the scheduling request to apply for uplink grant, and send the uplink data to the network device after the grant. That is, the present application delays waking up the terminal device as much as possible, and thus, power consumption generated between the terminal device being woken up and the scheduling request being transmitted can be saved.

In addition, although the uplink data is data of non-low-delay service, the terminal device is forcedly awakened to transmit the uplink data in the activation period of the second DRX period, compared with the situation that the terminal device is forcedly awakened in the sleep period of the second DRX period, the uplink data can be transmitted to the network device earlier, so that the data transmission efficiency is improved, and the timeliness of the data is guaranteed as much as possible.

That is, in a scenario where there is no PDSCH in the active period of the first DRX, the terminal device may be awakened in a deferred manner according to the transmission time of the scheduling request, and power consumption benefits may be further obtained.

In a second aspect, an embodiment of the present application further provides a data transmission apparatus, where the apparatus is used for a terminal device, and the terminal device is currently in a first DRX cycle, and the apparatus includes: a processor and a communication interface, the processor and the communication interface coupled, the processor to: acquiring uplink data generated by a first uplink service, wherein the service type of the first uplink service is non-low-delay service; determining that the terminal equipment is in a sleep state when acquiring the uplink data; and transmitting the uplink data to the network equipment through the communication interface in an activation period in a second DRX period, wherein the second DRX period is a DRX period after the first DRX period.

In one possible implementation, the apparatus further includes: and the memory is used for caching the uplink data after the processor determines that the terminal equipment is in a sleep state when acquiring the uplink data.

In one possible implementation, the processor is specifically configured to: determining that a Physical Downlink Shared Channel (PDSCH) exists in an activation period of the second DRX period, wherein the PDSCH is used for transmitting downlink data; and sending the uplink data to the network equipment through the communication interface on a first Physical Uplink Shared Channel (PUSCH), wherein the first PUSCH comprises a first time period, and the first time period belongs to an activation period in the second DRX period.

In one possible implementation, the processor is further configured to wake up the terminal device at a first time before sending the uplink data to the network device through the communication interface on a first physical uplink shared channel PUSCH, where the PDSCH includes a second time period, the second time period and the first time period both belong to an active period in the second DRX cycle, and a start time of the first time period and a start time of the second time period are not earlier than the first time period.

In one possible implementation, the processor is specifically configured to: determining that a Physical Downlink Shared Channel (PDSCH) does not exist in an activation period in the second DRX period; waking up the terminal device at a second time, wherein the second time belongs to an active period in the second DRX cycle; and sending the uplink data to the network equipment through the communication interface on a second PUSCH, wherein the second PUSCH comprises a second time period, the second time period belongs to an activation period in the second DRX period, 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 apparatus, including at least one processor and an interface circuit, where the interface circuit is configured to provide transmission or reception of data for the at least one processor, and when the at least one processor executes program code or instructions, implement the method described in the first aspect or any possible implementation manner thereof.

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

In a fifth aspect, embodiments of the present application also provide a computer readable storage medium storing a computer program comprising instructions for implementing the method described in the first aspect or any possible implementation thereof.

In a sixth aspect, embodiments of the present application further provide a computer program product comprising instructions which, when run on a computer or a processor, cause the computer or the processor to implement the method as described in the first aspect or any possible implementation thereof.

The data transmission device, the chip device, the terminal device, the computer storage medium and the computer program product provided in the embodiments of the present application are all configured to execute the data transmission method provided above, so that the beneficial effects that can be achieved by the data transmission device, the chip device, the terminal device, the computer storage medium and the computer program product can refer to the beneficial effects in the data transmission method provided above, and are not described herein again.

Drawings

Fig. 1 is a schematic block diagram of a data transmission system 100 of an embodiment of the present application;

fig. 2 is a schematic block diagram of a protocol architecture 200 of a terminal device of an embodiment of the present application;

fig. 3 is a schematic flow chart of downlink data transmission of a terminal device in the prior art;

Fig. 4 is another flow chart of downlink data transmission of a terminal device in the prior art;

fig. 5 is a schematic flow chart of uplink data transmission of a terminal device in the prior art;

fig. 6 is a schematic flow chart diagram of a data transmission method 300 of an embodiment of the present application;

fig. 7 is a schematic flow chart of uplink data transmission of the terminal device in the embodiment of the present application;

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

fig. 9 is a schematic flow chart of a data transmission method 400 of an embodiment of the present application;

fig. 10 is a schematic block diagram of a data transmission apparatus 500 provided in an embodiment of the present application;

fig. 11 is a schematic block diagram of a data transmission apparatus 600 provided in an embodiment of the present application.

Detailed Description

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, a data transmission system to which the data transmission method and apparatus provided in the embodiments of the present application are applied will be described.

Fig. 1 shows a schematic block diagram of a data transmission system 100 provided in an embodiment of the present application, where the system 100 may include at least one network device, such as the network device 110 shown in fig. 1. The network device 110 may provide communication coverage for a particular geographic area and may communicate data with terminal devices located within the coverage area.

Alternatively, the network device 110 may be an evolved node B (eNB or eNodeB) in a long term evolution (long term evolution, LTE) system, or a radio controller in a cloud radio access network (cloud radio access network, CRAN). The network device may 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 network device in a future evolved public land mobile network (public land mobile network, PLMN), etc.

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

Alternatively, the terminal device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (mobile internet device, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in a self-driving (self-driving), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device, a vehicle-mounted device, a smart home device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile communication network (public land mobile network, PLMN), etc., which the embodiments of the present application are not limited. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user.

It should be noted that, in fig. 1, only one network device and one terminal device are exemplarily shown, but embodiments of the present application are not limited thereto. Alternatively, the system 100 may include a plurality of network devices and each network device may include other numbers of terminal devices within a coverage area of the network device, which is not limited in the embodiments of the present application.

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

In one possible implementation, as shown in fig. 1, the network device 110 sends data to the terminal device 120 referred to as a downlink data transmission, and the terminal device 120 sends data to the network device 110 referred to as an uplink data transmission.

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

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

It should be noted that, fig. 2 only schematically illustrates 4 layers in the protocol structure 200, but embodiments of the present application are not limited thereto. Optionally, the protocol structure 200 may further include a radio link control (radio link control, RLC) layer, a service data adaptation protocol (service data adaption protocol, SDAP) layer, and the like, where each layer is capable of performing a function corresponding to each layer, which is not limited in this embodiment of the present application.

The downlink data transmission method of the terminal device in the prior art will be exemplarily described with reference to fig. 3 and 4.

As shown in fig. 3, taking Discontinuous Reception (DRX) cycle 1 as an example, the DRX cycle 1 may be packetIncluding an active period and a sleep period. Wherein the terminal device listens for downlink control information (downlink control information, DCI) from the network device before the DRX cycle 1 arrives (as hatched in fig. 3)Shown), the DCI is used to indicate whether there is downlink data to be transmitted in the active period; if the DCI indicates that there is downlink data to be transmitted in the active period, the terminal device wakes up at the start time of the active period and listens to a physical downlink control channel (physicaldownlink control channel, PDCCH) for indicating a physical downlink shared channel (physical downlink shared channel, PDSCH) for transmitting the downlink data, wherein the PDSCH includes a time period 1 (as shaded in FIG. 3) >Shown), the period 1 belongs to the activation period; the terminal device receives downlink data from the network device on the PUSCH. That is, the terminal device is in an awake state during the active period and in a sleep state during the sleep period.

As shown in fig. 4, taking a Discontinuous Reception (DRX) cycle 1 as an example, the DRX cycle 1 may include an active period and a sleep period. Wherein the terminal device listens for downlink control information (downlink control information, DCI) from the network device before the DRX cycle 1 arrives (as hatched in fig. 4Shown), the DCI is used to indicate whether there is downlink data to be transmitted in the active period; if the PDCCH indicates that there is no downlink data to be transmitted in the active period, the terminal device is in a sleep state (i.e. the terminal device is not awakened in the active period) until the sleep period is over, and the terminal device continues to monitor DCI of the next DRX cycle. That is, the terminal device is in a sleep state during both the active period and the sleep period.

Taking the scenario of the uplink transmission method shown in fig. 3 as an example, the uplink transmission method of the terminal device when the uplink data of the terminal device arrives in the sleep period in the DRX cycle 1 in the prior art will be exemplarily described with reference to fig. 5.

As shown in fig. 5, taking Discontinuous Reception (DRX) cycle 1 as an example, if the uplink data of the terminal device arrives within the sleep period of DRX cycle 1, the terminal device is forced to wake up, and sends a scheduling request to the network device on a physical downlink control channel (physical uplinkcontrol channel, PUCCH) for requesting to apply for uplink grant, where the PUCCH includes a period 1 (as shaded in fig. 5)Shown). The terminal device receives scheduling information from the network device, the scheduling information being used to indicate a physical downlink shared channel (physical uplink shared channel, PUSCH) for transmitting uplink data, the PUSCH including time period 2 (e.g. hatched +_in fig. 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, the application provides a data transmission method and device, which are beneficial to reducing the power consumption of terminal equipment.

Fig. 6 shows a schematic flow chart of a data transmission method 300 provided in an embodiment of the present application. As shown in fig. 6, the method 300 may be used with the terminal device 120 described in fig. 1. Taking the example that the terminal device employs the protocol architecture 200 as shown in fig. 2, the method 300 may include the following steps S301 to S320, it should be noted that the following steps may be performed in various orders and/or simultaneously, and are not limited to the execution order shown in fig. 6.

S301, an APP layer of the terminal equipment determines that the service type of the first uplink service is a non-low-delay service.

It should be noted that, the non-low latency service in the embodiments of the present application refers to a service that is not sensitive to latency or has a low priority.

In one possible implementation manner, the APP layer may determine that the service type of the first uplink service is a non-low latency service according to a preset first mapping relationship, where the first mapping relationship is used to indicate a correspondence between the uplink service and the service type, and the service type includes a low latency service or a non-low latency service.

In one possible implementation, the non-low latency service described in the present application may refer to a service whose expected transmission latency is greater than a preset first latency threshold, and the low latency service described in the present application may refer to a service whose expected transmission latency is less than the first latency threshold. By way of example, the first delay threshold may be 20ms (milliseconds). That is, non-low latency traffic has a lower priority than low latency traffic.

By way of example, the low latency services described herein may include one or more of gaming data, voice data.

By way of example, the non-low latency traffic described herein may include one or more of web page data, video data, background data, heartbeat data, and the like.

Alternatively, the first delay threshold described in the embodiments of the present application may be an average value of transmission delays of multiple services. By way of example, the expected transmission delay of video data may be greater than 160ms and the expected transmission delay of web page data may be greater than 80ms.

S302, the APP layer sends first notification information to layer two (namely, the PDCP layer and the MAC layer are included), wherein the first notification information is used for notifying that the service type of the first uplink service is non-low-delay service.

S303, the APP layer sends 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, wherein the second notification information is used for notifying the PDCP layer that the uplink data is cached.

S306, the MAC layer determines that the terminal equipment 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, wherein the third notification information is used for notifying that the PDCP layer is cached with the uplink data, and the uplink data needs to be sent to the network device in an activation period of a DRX period after the first DRX period.

S308, the PHY layer judges whether a PDSCH used for transmitting downlink data exists in an active period of a second DRX period based on the third notification message, wherein the second DRX period is a DRX period after the first DRX period. If so, continuing to execute S309-S314; if not, the process continues to S315 to S320.

Taking the downlink data transmission scenario shown in fig. 3 as an example, fig. 7 shows a schematic flow chart of uplink data transmission of the terminal device provided in the embodiment of the present application, where the flow includes S309 to S314 described above.

S309, the PHY layer wakes up the MAC layer at the starting time of the active period in the second DRX period.

S310, the MAC layer receives downlink data from the network device on the PDSCH through the PHY layer, wherein the PDSCH includes a time period a (as shaded in FIG. 7Shown), the period a belongs to an active period in the second DRX cycle, and a start time of the period a is not earlier than a start time of the active period in the second DRX cycle.

It should be noted that, the embodiments of the present application are not earlier than, including equal to or later than.

S311, the MAC layer passes through the PHY layer and is arranged on the PUCCHTransmitting a scheduling request to the network device, the scheduling request being used for applying for uplink grant, the PUCCH including a period b (as hatched in fig. 7Shown), the period b belongs to an active period in the second DRX cycle, and a start time of the period b is not earlier than a start time of the active period in the second DRX cycle.

S312, the MAC layer receives scheduling information from the network device through the PHY layer, wherein the scheduling information is used for indicating a PUSCH used for transmitting the uplink data.

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

S314. the MAC layer transmits the uplink data to the network device on the PUSCH including the time period c (as hatched in fig. 7 Shown), the period c belongs to the active period in the second DRX cycle, and the starting time of the period c is not earlier than the ending time of the period b.

Taking the downlink data transmission scenario shown in fig. 4 as an example, fig. 8 shows a schematic flow chart of uplink data transmission of the terminal device provided in the embodiment of the present application, where the flow includes S315 to S320 described above.

S315. the PHY layer determines a PUCCH for transmitting a scheduling request during the active period in the second DRX cycle, the PUCCH including a period d (as hatched in fig. 7Shown).

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

S317, the MAC layer sends a scheduling request to the network equipment on the PUCCH through the PHY layer, wherein the scheduling request is used for applying for uplink authorization.

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

And S319, the MAC layer reads the uplink data from the PDCP layer.

S320. the MAC layer transmits the uplink data to the network device on the PUSCH through the PHY layer, where the PUSCH includes a time period e (as hatched in fig. 8Shown), the period e belongs to the active period in the second DRX cycle, and the starting time of the period e is not earlier than the ending time of the period d.

Alternatively, the second DRX cycle may be a 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, which is not limited in the embodiments of the present application.

For example, if the network device configures PDSCH for downlink data transmission in advance for the terminal device during the active period of the next DRX cycle of the first DRX cycle, the second DRX cycle is the next DRX cycle of the first DRX cycle.

For example, if the network device does not configure the PDSCH for downlink data transmission in advance for the terminal device during the active period of the next DRX cycle of the first DRX cycle, the second DRX cycle is the DRX cycle after the first DRX cycle in which the PDSCH is configured for the first time.

It should be noted that, if the network device does not configure PDSCH for downlink data transmission in advance for the terminal device in the active period of the next DRX cycle of the first DRX cycle, and the terminal device can wait until the active period of the first DRX cycle configured with PDSCH comes within the range of the expected transmission delay of the non-low latency service, the terminal device may transmit the uplink data to the opposite terminal through the network device in the active period of the first DRX cycle configured with PDSCH after the first DRX cycle in a manner as shown in fig. 7; accordingly, if the terminal device does not wait until the activation period of the first DRX cycle configured with the PDSCH arrives within the range of the expected transmission delay of the non-low latency service, the terminal device needs to transmit the uplink data to the opposite terminal through the network device as early as possible, e.g., the terminal device may transmit the uplink data to the opposite terminal through the network device in the manner shown in fig. 8 in the next DRX cycle of the first DRX cycle.

Fig. 9 shows a schematic flowchart of a data transmission method 400 provided in an embodiment of the present application. As shown in fig. 9, the method 400 may be used with the terminal device 120 described in fig. 1. Taking the example that the terminal device is currently in the first DRX cycle, the method 400 may include the following steps S401 to S403, where it should be noted that the following steps may be performed in various orders and/or simultaneously, and are not limited to the execution order shown in fig. 9.

S401, uplink data generated by first uplink service is acquired, wherein the service type of the first uplink service is non-low-delay service.

S402, determining that the terminal equipment is in a sleep state when acquiring the uplink data.

Optionally, after S402, the method further includes: the upstream data is buffered.

S403, the uplink data is sent to the network equipment in an activation period in a second DRX period, wherein the second DRX period is a DRX period after the first DRX period.

Optionally, the terminal device in a sleep state when acquiring the uplink data may include: the terminal device is in a sleep period of a first DRX cycle as shown in fig. 3; alternatively, the terminal device is in an active or sleep period as shown in fig. 4.

In one possible implementation, S403 may include: determining that a Physical Downlink Shared Channel (PDSCH) exists in an activation period of the second DRX period, wherein the PDSCH is used for transmitting downlink data; and sending the uplink data to the network equipment on a first Physical Uplink Shared Channel (PUSCH), wherein the first PUSCH comprises a first time period, and the first time period belongs to an activation period in the second DRX period.

Optionally, before the sending the uplink data to the network device on the first physical uplink shared channel PUSCH, the method further includes: the terminal equipment is awakened at a first time, wherein the PDSCH comprises a second time period, the second time period and the first time period both belong to an activation period in the second DRX period, 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 time, the method may further include: the terminal device receives the downlink data from the network device on the PDSCH.

In another possible implementation, S403 may include: determining that a Physical Downlink Shared Channel (PDSCH) does not exist in an activation period in the second DRX period; waking up the terminal device at a second time, wherein the second time belongs to an active period in the second DRX cycle; and sending the uplink data to the network equipment on a second PUSCH, wherein the second PUSCH comprises a second time period, the second time period belongs to an activation period in the second DRX period, and the starting time of the second time period is not earlier than the second time.

The data transmission method provided in the embodiments of the present application is described above with reference to fig. 6 to 9, and the data transmission apparatus for performing the above-described method 200 or method 300 will be further described below.

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

Alternatively, the apparatus 500 may be used in the system 100, and further, the apparatus 500 may be used in the terminal device 120 in the system 100, e.g., the apparatus 500 may be a virtual apparatus formed by software executed by a processor or controller on the terminal device 120. Wherein the terminal device is currently in a first discontinuous reception, DRX, cycle.

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

The sending unit 502 is configured to send the uplink data to the network device during an active period in a second DRX cycle, where the second DRX cycle is a DRX cycle subsequent to the first DRX cycle.

In a possible implementation manner, the apparatus 500 may further include a storage unit 503, where the storage unit 503 is configured to buffer 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 further configured to determine that a physical downlink shared channel PDSCH exists during the active period in the second DRX cycle, where the PDSCH is used for transmitting downlink data; the sending unit 502 is specifically configured to send the uplink data to the network device on a first physical uplink shared channel PUSCH, where the first PUSCH includes a first period of time, and the first period of time belongs to an active period in the second DRX cycle.

In a possible implementation manner, the processing unit 501 is further configured to wake up the terminal device at a first time 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, and the second time period and the first time period both belong to an active period in the second DRX cycle, and a start time of the first time period and a start time of the second time period are not earlier than the first time.

In a possible implementation, the processing unit 501 is further configured to determine that there is no physical downlink shared channel PDSCH in the active period in the second DRX cycle; waking up the terminal device at a second time, wherein the second time belongs to an active period in the second DRX cycle; the sending unit 502 is specifically configured to send the uplink data to the network device on a second PUSCH, where the second PUSCH includes a second time period, the second time period belongs to an active period in the second DRX cycle, and a start time of the second time period is not earlier than the second time.

It should be noted that, because the content of information interaction and execution process between the above units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again. In an alternative example, the apparatus 500 may be configured to perform the respective processes and/or steps corresponding to the end device in the foregoing method 200 or method 300 embodiment, which are not described herein for the sake of avoiding repetition.

One or more of the various modules in the embodiment shown in fig. 10 may be implemented in 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 types of integrated circuits such as central processing units (CPU, central Processing Unit), digital signal processors (DSP, digital Signal Processor), field programmable gate arrays (FPGA, field Programmable Gate Array), or application specific integrated circuits (ASIC, application Specific Integrated Circuit).

Referring to fig. 11, fig. 11 shows a schematic block diagram of a data transmission apparatus 600 provided in an embodiment of the present application, the apparatus 600 may include a processor 601 and a communication interface 602, where the processor 601 is coupled to the communication interface 602.

In an alternative example, those skilled in the art will appreciate that the apparatus 600 may be embodied as (or used in) the terminal device in the method 200 described above, and the apparatus 600 may be a physical hardware structure of the apparatus 500. The apparatus 600 may be configured to execute each flow and/or step corresponding to the terminal device in the above-described method 200 or method 300 embodiment, and will not be described herein for avoiding repetition.

The communication interface 602 is used to input data (e.g., downstream data) to the processor 601 and/or output data (e.g., upstream data) from the processor 601; the processor 601 is configured to execute a computer program or instructions to cause the data transmission device 600 to implement the method described in the above embodiments of the method 200 or method 300.

The processor 601 in the embodiments of the present 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), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA), discrete gate or transistor logic, discrete hardware components, or the like. A general purpose processor may be a microprocessor, a microcontroller, or any conventional processor or the like.

For example, the processor 601 is configured to obtain uplink data generated by a first uplink service, where a service type of the first uplink service is a non-low latency service; determining that the terminal equipment is in a sleep state when acquiring the uplink data; the uplink data is transmitted to the network device through the communication interface 602 during an active period in a second DRX cycle, wherein the second DRX cycle is a DRX cycle subsequent to the first DRX cycle.

Optionally, the data transmission device 600 may further comprise a memory 603.

The memory 603 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM).

In particular, the memory 603 is used for storing program codes and instructions of the data transmission device 600. Optionally, the memory 603 is further configured to store data, such as uplink data, obtained during execution of the above-described method 200 or method 300 embodiments by the processor 601.

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 further include other necessary elements, 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 scope of protection of the present application.

In one possible design, the data transfer device 600 may be a chip device. Optionally, the chip device may further include one or more memories for storing computer-executable instructions that, when the chip device is running, are stored by the processor to cause the chip device to perform the above-described command transmission method.

Alternatively, the chip device may be a field programmable gate array, an application specific integrated chip, a system chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, a programmable controller or other integrated chips for realizing the relevant functions.

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

In one possible design, embodiments of the present application also provide a computer program product comprising instructions that, when executed on a computer or a processor, cause the computer or the processor to implement the data transmission method described in the method 200 or the method 300.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may 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 may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data transmission method, wherein the method is used for a terminal device, and the terminal device is currently in a first discontinuous reception DRX cycle, the method comprising:

acquiring uplink data generated by first uplink service, wherein the service type of the first uplink service is non-low-delay service;

determining that the terminal equipment is in a sleep state when acquiring the uplink data;

and sending the uplink data to the network equipment in an activation period in a second DRX period, wherein the second DRX period is a DRX period after the first DRX period.

2. The method of claim 1, wherein after the determining that the terminal device is in a sleep state when acquiring the uplink data, the method further comprises:

and caching the uplink data.

3. The method according to claim 1 or 2, wherein said sending the uplink data to the network device during the active period in the second DRX cycle comprises:

determining that a Physical Downlink Shared Channel (PDSCH) exists in an activation period of the second DRX period, wherein the PDSCH is used for transmitting downlink data;

and sending the uplink data to the network equipment on a first Physical Uplink Shared Channel (PUSCH), wherein the first PUSCH comprises a first time period, and the first time period belongs to an activation period in the second DRX period.

4. The method of claim 3, wherein prior to the transmitting the uplink data to the network device on the first physical uplink shared channel, PUSCH, the method further comprises:

and waking up the terminal equipment at a first time, wherein the PDSCH comprises a second time period, the second time period and the first time period both belong to an activation period in the second DRX period, 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.

5. The method according to claim 1 or 2, wherein said sending the uplink data to the network device during the active period in the second DRX cycle comprises:

determining that a Physical Downlink Shared Channel (PDSCH) does not exist in an activation period in the second DRX period;

waking up the terminal device at a second time, wherein the second time belongs to an active period in the second DRX cycle;

and sending the uplink data to the network equipment on a second PUSCH, wherein the second PUSCH comprises a second time period, the second time period belongs to an activation period in the second DRX period, and the starting time of the second time period is not earlier than the second time.

6. A data transmission apparatus for a terminal device, the terminal device currently being in a first discontinuous reception, DRX, cycle, the apparatus comprising: a processor and a communication interface, the processor and the communication interface coupled, the processor to:

and in the activation period in a second DRX period, sending the uplink data to the network equipment through the communication interface, wherein the second DRX period is a DRX period after the first DRX period.

7. The apparatus of claim 6, wherein the apparatus further comprises: the memory device is used for storing the data,

the memory is used for caching the uplink data after the processor determines that the terminal equipment is in a sleep state when acquiring the uplink data.

8. The apparatus according to claim 6 or 7, wherein the processor is specifically configured to:

And sending the uplink data to the network equipment through the communication interface on a first Physical Uplink Shared Channel (PUSCH), wherein the first PUSCH comprises a first time period, and the first time period belongs to an activation period in the second DRX period.

9. The apparatus of claim 8, wherein the device comprises a plurality of sensors,

the processor is further configured to wake up the terminal device at a first time before sending the uplink data to the network device through the communication interface on a first physical uplink shared channel PUSCH, where the PDSCH includes a second time period, both the second time period and the first time period belong to an active period in the second DRX cycle, and a start time of the first time period and a start time of the second time period are not earlier than the first time.

10. The apparatus according to claim 6 or 7, wherein the processor is specifically configured to:

And sending the uplink data to the network equipment through the communication interface on a second PUSCH, wherein the second PUSCH comprises a second time period, the second time period belongs to an activation period in the second DRX period, and the starting time of the second time period is not earlier than the second time.

11. Chip arrangement comprising at least one processor and interface circuitry for providing transmission or reception of data for said at least one processor, characterized in that the method of any of the preceding claims 1-5 is implemented when said at least one processor executes program code or instructions.

12. A computer readable storage medium storing a computer program, characterized in that the computer program comprises instructions for implementing the method of any of the preceding claims 1-5.

13. A computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to carry out the method of any one of the preceding claims 1-5.