WO2024055668A1 - Procédé et appareil de transmission de données - Google Patents

Procédé et appareil de transmission de données Download PDF

Info

Publication number
WO2024055668A1
WO2024055668A1 PCT/CN2023/101746 CN2023101746W WO2024055668A1 WO 2024055668 A1 WO2024055668 A1 WO 2024055668A1 CN 2023101746 W CN2023101746 W CN 2023101746W WO 2024055668 A1 WO2024055668 A1 WO 2024055668A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx cycle
uplink data
time period
uplink
terminal device
Prior art date
Application number
PCT/CN2023/101746
Other languages
English (en)
Chinese (zh)
Inventor
韩煦
纪永昭
翟鹏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024055668A1 publication Critical patent/WO2024055668A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communications, and more specifically, to a data transmission method and device.
  • Discontinuous reception 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • This application provides a data transmission method and device, which is beneficial to reducing the power consumption of terminal equipment.
  • 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.
  • the terminal device 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.
  • 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.
  • the second DRX cycle may be a DRX cycle next to the first DRX cycle.
  • the method further includes: caching the uplink data.
  • 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.
  • 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.
  • the terminal device 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.
  • the method 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.
  • 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.
  • the terminal device 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.
  • the terminal device 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Figure 1 is a schematic block diagram of a data transmission system 100 according to an embodiment of the present application.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • wearable devices can also be called wearable smart devices.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • FIG. 1 only illustrates one network device and one terminal device, but the embodiment of the present application is not limited thereto.
  • 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.
  • 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.
  • network entities such as a network controller and a mobility management entity, to which the embodiments of the present application are not limited.
  • 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.
  • 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.
  • APP application
  • PDCP packet data convergence protocol
  • MAC medium access control
  • PHY physical layer
  • the physical layer 240 belongs to layer one
  • the PDCP layer 220 and the MAC layer 230 belong to layer two
  • layer one and layer two may belong to the modem of the terminal device.
  • 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.
  • RLC radio link control
  • SDAP service data adaptation protocol
  • the DRX cycle 1 may include an activation period and a sleep period.
  • 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.
  • DCI downlink control information
  • PDSCH physical downlink control channel
  • the DRX cycle 1 may include an activation period and a sleep period.
  • 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.
  • DCI downlink control information
  • DRX cycle 1 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.
  • 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.
  • 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.
  • 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.
  • the method 300 can be used for the terminal device 120 described in FIG. 1 .
  • 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.
  • the APP layer of the terminal device determines that the service type of the first uplink service is a non-low-latency service.
  • non-low-latency services described in the embodiments of this application refer to services that are not sensitive to delays or have low priority.
  • 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.
  • 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.
  • 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.
  • the low-latency service described in this application may include one or more of game data and voice data.
  • 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.
  • the first delay threshold described in the embodiment of this application may be an average of the transmission delays of multiple services.
  • the expected transmission delay of video data may be greater than 160 ms
  • the expected transmission delay of web page data may be greater than 80 ms.
  • 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.
  • the APP layer sends the uplink data generated by the first uplink service to the PDCP.
  • the PDCP layer caches the uplink data.
  • 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.
  • the MAC layer determines that the terminal device is in a sleep state when acquiring the uplink data.
  • 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.
  • 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.
  • 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.
  • the PHY layer wakes up the MAC layer at the beginning of the activation period in the second DRX cycle.
  • 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.
  • 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.
  • 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.
  • the MAC layer reads the uplink data from the PDCP layer.
  • 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.
  • the terminal device 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.
  • 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.
  • 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).
  • the PHY layer wakes up the MAC layer before the time period d.
  • 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 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.
  • the MAC layer reads the uplink data from the PDCP layer.
  • 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.
  • 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.
  • 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 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.
  • the second DRX cycle is the first DRX cycle.
  • 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
  • the terminal device 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.
  • the terminal device 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.
  • 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.
  • Figure 9 shows a schematic flow chart of the data transmission method 400 provided by the embodiment of the present application.
  • the method 400 can be used for the terminal device 120 described in FIG. 1 .
  • 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.
  • the service type of the first uplink service is a non-low-latency service.
  • non-low-latency services described in the embodiments of this application refer to services that are not sensitive to delays or have low priority.
  • S402. Determine that the terminal device is in a sleep state when acquiring the uplink data.
  • the method further includes: caching the uplink data.
  • 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.
  • 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.
  • the method 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. .
  • the method may further include: the terminal device receiving the downlink data from the network device on the PDSCH.
  • 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 terminal device 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.
  • Figure 10 shows a schematic block diagram of a data transmission device 500 provided by an embodiment of the present application.
  • the device 500 may include a processing unit 501 and a sending unit 502.
  • 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.
  • the device 500 can be executed by a processor or controller on the terminal device 120.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 Electrode EPROM, EEPROM
  • Volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory 603 is used to store program codes and instructions of the data transmission device 600 .
  • 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.
  • the memory 603 may be a separate device or integrated in the processor 601.
  • FIG. 11 only shows a simplified design of the data transmission device 600.
  • 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.
  • the data transmission device 600 may be a chip device.
  • the chip device can also include one or more memories for storing computer execution instructions.
  • the processor can execute the computer execution instructions stored in the memory, so that the chip device executes the above command transmission method. .
  • 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.
  • 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 .
  • 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.
  • 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.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne un procédé et un appareil de transmission de données, facilitant la réduction de la consommation d'énergie d'un dispositif terminal. Le procédé peut être appliqué au dispositif terminal. Le dispositif terminal est actuellement dans un premier cycle de réception discontinue (DRX). Le procédé consiste à : acquérir des données de liaison montante générées à partir d'un premier service de liaison montante, le type de service du premier service de liaison montante étant un service qui n'est pas à faible latence ; déterminer que le dispositif terminal est dans un état de veille lors de l'acquisition des données de liaison montante ; envoyer les données de liaison montante à un dispositif réseau dans une période d'activation dans un second cycle DRX, le second cycle DRX étant un cycle DRX après le premier cycle DRX.
PCT/CN2023/101746 2022-09-13 2023-06-21 Procédé et appareil de transmission de données WO2024055668A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211110292.5A CN117715161A (zh) 2022-09-13 2022-09-13 数据传输方法和装置
CN202211110292.5 2022-09-13

Publications (1)

Publication Number Publication Date
WO2024055668A1 true WO2024055668A1 (fr) 2024-03-21

Family

ID=90153941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/101746 WO2024055668A1 (fr) 2022-09-13 2023-06-21 Procédé et appareil de transmission de données

Country Status (2)

Country Link
CN (1) CN117715161A (fr)
WO (1) WO2024055668A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500299A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 用户设备及不连续接收状态下的上行发送方法
US20150304955A1 (en) * 2014-04-18 2015-10-22 Apple Inc. Deterministic RRC Connections
CN108200639A (zh) * 2018-02-13 2018-06-22 广东欧珀移动通信有限公司 业务数据的发送方法、装置及终端
CN110557806A (zh) * 2018-05-31 2019-12-10 电信科学技术研究院有限公司 一种数据传输方法、终端设备及网络设备
CN111757430A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 通信方法与装置
CN114885409A (zh) * 2022-07-08 2022-08-09 展讯通信（上海）有限公司 调度请求发送方法、装置、设备、存储介质及产品

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500299A (zh) * 2008-02-02 2009-08-05 华为技术有限公司 用户设备及不连续接收状态下的上行发送方法
US20150304955A1 (en) * 2014-04-18 2015-10-22 Apple Inc. Deterministic RRC Connections
CN108200639A (zh) * 2018-02-13 2018-06-22 广东欧珀移动通信有限公司 业务数据的发送方法、装置及终端
CN110557806A (zh) * 2018-05-31 2019-12-10 电信科学技术研究院有限公司 一种数据传输方法、终端设备及网络设备
CN111757430A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 通信方法与装置
CN114885409A (zh) * 2022-07-08 2022-08-09 展讯通信（上海）有限公司 调度请求发送方法、装置、设备、存储介质及产品

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Evaluation of user experience for using a DRX configuration optimised for low power consumption", 3GPP DRAFT; R2-122676 EVALUATION OF USER EXPERIENCE FOR USING A DRX CONFIGURATION OPTIMISED FOR LOW POWER CONSUMPTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FR, vol. RAN WG2, no. Prague, Czech Republic; 20120521 - 20120525, 14 May 2012 (2012-05-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050607059 *

Also Published As

Publication number Publication date
CN117715161A (zh) 2024-03-15

Similar Documents

Publication Publication Date Title
WO2022121522A1 (fr) Procédé et appareil de commutation de système, dispositif électronique, et support de stockage lisible
WO2006073606A2 (fr) Procede d'actionnement d'une station mobile wlan
WO2005091705A2 (fr) Systeme de gestion d'energie et procede destine a un dispositif de communications sans fil
WO2022012388A1 (fr) Procédé et dispositif de communication
WO2020237703A1 (fr) Procédé et dispositif de commutation de mode de communication, support de stockage, processeur, et système
US20150103720A1 (en) Method and device for data transmission in wireless local area network
WO2021218842A1 (fr) Procédé de déclenchement de réception de liaison descendante, terminal et dispositif côté réseau
CN110891328B (zh) 用于对齐唤醒的方法与移动设备
US20240196327A1 (en) Monitoring method and apparatus, wake-up signal transmission method and apparatus, terminal, and network-side device
WO2023083068A1 (fr) Procédé et système d'alignement de réveil, et appareil associé
WO2021164593A1 (fr) Procédé et appareil de transmission de données
WO2021218855A1 (fr) Procédé de déclenchement de réception en liaison descendante, et terminal et dispositif côté réseau
WO2024055668A1 (fr) Procédé et appareil de transmission de données
WO2015127599A1 (fr) Procédé d'attribution de ressources en liaison montante, terminal d'accès et point d'accès
US20230111984A1 (en) Methods and Apparatus for Adaptive Power Profiling in A Baseband Processing System
US20190073407A1 (en) Optimized data synchronization
WO2022147730A1 (fr) Procédé et appareil de traitement de signal d'économie d'énergie, dispositif de communication, et support de stockage
KR20210106958A (ko) Drx 운용 방법 및 이를 지원하는 장치
WO2014024175A2 (fr) Gestion de compteurs de temps
CN115484660A (zh) 波束指示方法及装置、存储介质、终端、网络设备
WO2021000308A1 (fr) Appareil et procédé de réception discontinue
US20240155729A1 (en) Wireless communication device, mobile device including same, and method of operating same
WO2022133937A1 (fr) Procédé, appareil et système de communication de liaison latérale
CN115278902B (zh) 数据传输方法、装置、计算机设备和介质
US20240314403A1 (en) Information transmission method and apparatus, and terminal and network side device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23864407

Country of ref document: EP

Kind code of ref document: A1