WO2021081838A1 - Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau - Google Patents

Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau Download PDF

Info

Publication number
WO2021081838A1
WO2021081838A1 PCT/CN2019/114474 CN2019114474W WO2021081838A1 WO 2021081838 A1 WO2021081838 A1 WO 2021081838A1 CN 2019114474 W CN2019114474 W CN 2019114474W WO 2021081838 A1 WO2021081838 A1 WO 2021081838A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
cell
timer
configuration
configuration information
Prior art date
Application number
PCT/CN2019/114474
Other languages
English (en)
Chinese (zh)
Inventor
石聪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201980099433.8A priority Critical patent/CN114270917B/zh
Priority to PCT/CN2019/114474 priority patent/WO2021081838A1/fr
Publication of WO2021081838A1 publication Critical patent/WO2021081838A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • 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 embodiments of the present application relate to the field of mobile communication technologies, and in particular to a discontinuous reception (Discontinuous Reception, DRX) configuration method and device, terminal equipment, and network equipment.
  • DRX discontinuous Reception
  • each media access control entity (Media Access Control entity, MAC entity) has a DRX configuration.
  • a DRX cycle (DRX cycle)
  • the terminal device needs to blindly check the Physical Downlink Control Channel (PDCCH) during the DRX activation time.
  • PDCCH Physical Downlink Control Channel
  • cDRX refers to DRX (connected DRX) in the RRC connected state.
  • CA Carrier Aggregation
  • a cDRX enhancement solution is currently proposed. Specifically, for the carrier aggregation scenarios of FR1 and FR2 in NR, the behavior of the terminal device in blindly detecting the PDCCH on FR1 and FR2 is very different. If a common cDRX configuration is configured for the carrier of FR1 and FR2, it may cause the terminal device to blindly check the FR2 for too long, which will lead to additional power consumption.
  • the embodiments of the present application provide a DRX configuration method and device, terminal equipment, and network equipment.
  • the terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;
  • the terminal device monitors the PDCCH based on the first configuration information and the second configuration information.
  • the network device sends first configuration information to the terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;
  • the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.
  • the receiving unit is configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; 2. Configuration information, where the second configuration information is used to determine one or more scaling parameters;
  • the processing unit is configured to monitor the PDCCH based on the first configuration information and the second configuration information.
  • a sending unit configured to send first configuration information to a terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; sending a second configuration to the terminal device Information, the second configuration information is used to determine one or more scaling parameters;
  • the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.
  • the terminal device provided in the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the above-mentioned DRX configuration method.
  • the network device provided by the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the above-mentioned DRX configuration method.
  • the chip provided in the embodiment of the present application is used to implement the above-mentioned DRX configuration method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned DRX configuration method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned DRX configuration method.
  • the computer program product provided by the embodiments of the present application includes computer program instructions that cause a computer to execute the above-mentioned DRX configuration method.
  • the computer program provided in the embodiments of the present application when running on a computer, causes the computer to execute the above-mentioned DRX configuration method.
  • a method for terminal equipment to monitor the control channel discontinuously is proposed.
  • the network side has sufficient flexibility in the scheduling of PDCCH, and at the same time, the energy saving of the terminal equipment is taken into account, so that the terminal equipment is There is a better compromise between scheduling flexibility and energy saving.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the running time of drx-onDurationTimer provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a DRX configuration method provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of time and position of Example 1 provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of time and position of Example 2 provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram 1 of the structural composition of the DRX configuration device provided by an embodiment of the application.
  • FIG. 7 is a second schematic diagram of the structural composition of the DRX configuration device provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication system 5G communication system or future communication system.
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area.
  • the network device 110 may be an evolved base station (Evolutional Node B, eNB, or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or
  • the network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.
  • the communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110.
  • the "terminal” used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN public switched telephone network
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • a terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.
  • the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • each MAC entity has a DRX configuration.
  • the DRX configuration includes the following parameters: drx-onDurationTimer, drx-SlotOffset, drx-StartOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycle, drx-ShortCycle , Drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.
  • DRX Active Time DRX Active Time
  • drx-onDurationTimer drx-InactivityTimer
  • the pending state after the scheduling request (Scheduling Request, SR) is transmitted belongs to the DRX activation time.
  • the period during which the PDCCH indicating the newly transmitted data is not received belongs to the DRX activation time.
  • drx-onDurationTimer For drx-onDurationTimer, its start/restart is started at a fixed time point based on the configured DRX cycle, as shown in Figure 2. Specifically, the startup rules of drx-onDurationTimer are as follows:
  • the condition for the terminal device to start or restart the drx-InactivityTimer is: if the terminal device receives a PDCCH indicating downlink or uplink initial transmission (that is, new transmission), the terminal device starts or restarts the drx-InactivityTimer.
  • the behavior of the terminal equipment in blindly detecting the PDCCH on FR1 (mainly frequency bands below 6 GHz) and FR2 (mainly frequency bands above 6 GHz) is very different.
  • the basic parameter set (numerology) adopted by the FR2 carrier is larger than that of the FR1 carrier. Therefore, for the same time, such as 10 ms, the FR2 carrier has a much larger number of time slots than the FR1 carrier.
  • the blind detection of PDCCH is based on the configuration of control resource set (CORESET) and search space (SEARCHSPACE), and its granularity can reach symbol level.
  • CORESET control resource set
  • SEARCHSPACE search space
  • FR1 and FR2 have the same requirements for blind detection of PDCCH, the time required for FR2 Will be shorter than FR1. In other words, in the same time, the overhead of blind PDCCH detection on FR2 will be greater than that of FR1.
  • a common cDRX configuration is configured for the carriers of FR1 and FR2, it may cause the terminal device to blindly detect the PDCCH on the FR2 for too long, thereby causing additional power consumption.
  • the network can configure an additional set of DRX configurations, which can be called a secondary DRX (secondaryDRX) configuration.
  • secondaryDRX secondaryDRX
  • the network can configure a shorter blind detection timer, so the blind detection overhead of the terminal device on the FR2 can be optimized.
  • each carrier needs to be configured with an additional set of DRX configuration, which will increase the load of configuration signaling. For this reason, the following technical solutions of the embodiments of the present application are proposed. The technical solutions of the embodiments of the present application are intended to enhance the DRX configuration in the NR CA scenario.
  • FIG. 3 is a schematic flowchart of a DRX configuration method provided by an embodiment of the application. As shown in FIG. 3, the DRX configuration method includes the following steps:
  • Step 301 The terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer.
  • the network device sends the first configuration information to the terminal device. Accordingly, the terminal device receives the first configuration information sent by the network device, and the first configuration information is used to determine the DRX configuration. Further, optionally, the network device is a base station, such as a gNB.
  • the first configuration information is carried in first configuration signaling.
  • the terminal device receives the first configuration information sent by the network device.
  • the first configuration information may be recorded as DRX-config.
  • the DRX-config is configured in MAC-CellGroupConfig, where MAC-CellGroupConfig is used for the cell group ( cell group) Configure MAC parameters, where the MAC parameters include DRX configuration.
  • the DRX configuration is used to determine the configuration parameter of at least one timer.
  • the timer in the DRX configuration may also be referred to as a DRX timer.
  • the at least one timer includes at least one of the following:
  • DRX uplink retransmission timer (drx-RetransmissionTimerDL);
  • DRX downlink retransmission timer (drx-RetransmissionTimerUL).
  • the DRX configuration is a DRX configuration in an RRC connected state (ie, a cDTX configuration).
  • Step 302 The terminal device receives second configuration information sent by the network device, where the second configuration information is used to determine one or more scaling parameters.
  • the network device sends second configuration information to the terminal device. Accordingly, the terminal device receives the second configuration information sent by the network device, and the second configuration information is used to determine one Or multiple scaling parameters. Further, optionally, the network device is a base station, such as a gNB.
  • the second configuration information is carried in second configuration signaling.
  • the second configuration signaling and the first configuration signaling in the above solution are two independent configuration signalings.
  • the second configuration information is used to determine (or indicate) one or more scaling parameters, where the scaling parameters are used to scale the PDCCH monitoring duration.
  • Step 303 The terminal device monitors the PDCCH based on the first configuration information and the second configuration information.
  • At least one timer in the DRX configuration may be associated with the same common scaling parameter, or different timers in the DRX configuration may be associated with different scaling parameters (that is, the difference between the timer and the scaling parameter).
  • the association relationship is a one-to-one correspondence). The following describes how the terminal device monitors the PDCCH in combination with different association situations.
  • the second configuration information is used to determine a scaling parameter.
  • the scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer; wherein, the first cell needs to monitor the PDCCH The cell whose monitoring time is scaled.
  • the second configuration information is carried in the cell configuration of the first cell.
  • the way the terminal device monitors the PDCCH is:
  • the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, wherein the first time period is less than or equal to the maximum time period.
  • Long PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.
  • the terminal device monitors the PDCCH on the second cell during the running of the first timer.
  • the first timer is any timer in the DRX configuration.
  • the start time of the first duration is the start time of the first timer.
  • the terminal device determines the longest PDCCH monitoring duration corresponding to the first cell according to the scaling parameter and the duration of the first timer, which can be determined by the following formula (1.1) or formula (1.2 )to realise:
  • Timer is the duration of the first timer
  • ScalingFactor is the scaling parameter
  • the longest PDCCH monitoring duration can also be implemented by the following formula (2.1) or formula (2.2):
  • floor represents the round-down operation.
  • the second configuration information is used to determine multiple scaling parameters.
  • different scaling parameters in the plurality of scaling parameters have an association relationship with different timers; each scaling parameter in the plurality of scaling parameters is used to determine the running period of the timer associated with the scaling parameter, the terminal The longest PDCCH monitoring duration of the device on the first cell; wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
  • the second configuration information is carried in the cell configuration of the first cell.
  • the way the terminal device monitors the PDCCH is:
  • the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, wherein the first time period is less than or equal to the maximum time period.
  • Long PDCCH monitoring duration the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.
  • the terminal device monitors the PDCCH on the second cell during the running of the first timer.
  • the first timer is any timer in the DRX configuration.
  • the start time of the first duration is the start time of the first timer.
  • the terminal device determines the longest PDCCH monitoring duration corresponding to the first cell according to the duration of the first timer and the first scaling parameter associated with the first timer, which may refer to the foregoing Formula (1.1) or formula (1.2) or formula (2.1) or formula (2.2) can be realized. It should be pointed out that because different timers are associated with different scaling parameters, when the above formula is used to calculate the longest PDCCH monitoring duration, the selection of scaling parameters is not uniform, but different scaling parameters are selected for different timers.
  • the condition for the terminal device to start the timer (such as on-durationTimer, drx-inactivityTimer) will not change with the scaling parameter. For example, if the terminal device receives a PDCCH for indicating newly transmitted data during the operation of the drx-onDurationTimer, the drx-InactivityTimer is started.
  • the terminal equipment monitors the PDCCH on some serving cells during the operation of one or more DRX timers to scale, so as to reduce the terminal equipment’s presence in these serving cells.
  • the configuration method of the scaling parameter may be: 1) configure a common scaling parameter for at least one DRX timer that needs to scale the PDCCH monitoring duration (that is, the above-mentioned second configuration information is used to determine a related solution for the scaling parameter); Or, 2) configure a scaling parameter for each DRX timer that needs to scale the PDCCH monitoring duration (that is, the above-mentioned second configuration information is used to determine a related solution for multiple scaling parameters).
  • 1) the advantage of the solution is at least that the signaling overhead is less; 2) the advantage of the solution is that it can at least support a more flexible configuration.
  • each MAC entity is configured with one DRX configuration (that is, each MAC entity is configured with only one DRX configuration).
  • all aggregated carriers use this DRX configuration.
  • the network device can configure a scaling parameter.
  • the terminal device When the terminal device starts blind detection of the PDCCH according to the DRX configuration, for the carrier configured with the scaling parameter, the terminal device will scale the PDCCH monitoring duration during the operation of the corresponding timer, so that the blind detection time on the corresponding carrier is reduced to save power the goal of. In this way, only one set of DRX configuration can be maintained, and the power consumption saving on FR2 can be achieved at the same time.
  • the terminal device receives first configuration information sent by the network device, where the first configuration information includes DRX configuration (that is, DRX-config), where DRX-config is configured in MAC-CellGroupConfig.
  • DRX configuration that is, DRX-config
  • DRX-config is configured in MAC-CellGroupConfig.
  • the terminal device receives second configuration information sent by the network device.
  • the second configuration information is different from the first configuration information.
  • the second configuration information carries the first indication information and is used to indicate a scaling parameter.
  • the longest PDCCH monitoring duration of the terminal device on the SCell during the running of the timer is determined based on the duration of the timer and the scaling parameter.
  • the SCell is only exemplary, and represents a cell that needs to scale the PDCCH monitoring duration. For each cell (or carrier) that needs to scale the PDCCH monitoring duration, the longest PDCCH monitoring duration needs to be determined separately.
  • one or more timers in DRX-config include at least one of the following:
  • drx-onDurationTimer drx-InactivityTimer
  • drx-RetransmissionTimerDL drx-RetransmissionTimerUL.
  • the second configuration information is configured for a carrier (or cell), that is, for a certain carrier, if the second configuration information is configured, it means that the terminal device needs to scale the PDCCH monitoring duration on the carrier.
  • the second configuration information is carried in SCellConfig in CellGroupConfig.
  • the terminal device starts on-durationtimer at a fixed time based on DRX-config.
  • the behavior of terminal equipment monitoring PDCCH on each serving cell during on-durationtimer operation is as follows:
  • the terminal device scales the on-durationTimer duration according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to the on-durationTimer.
  • the terminal device is in the on-durationTimer operation period , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period.
  • the longest PDCCH monitoring duration is obtained by dividing or multiplying the on-durationTimer by the scaling parameter.
  • the terminal device monitors the PDCCH on the Cell during the on-duration timer operation.
  • the terminal device If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the DRX activation time, the terminal device starts the drx-InactivityTimer.
  • the behavior of terminal equipment monitoring PDCCH on each serving cell during the operation of drx-InactivityTimer is as follows:
  • the terminal device scales the duration of drx-inactivityTimer according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to drx-inactivityTimer.
  • the terminal device is in the operation period of drx-inactivityTimer , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period.
  • the longest PDCCH monitoring duration is obtained according to the drx-inactivityTimer divided by or multiplied by the scaling parameter.
  • the terminal device monitors the PDCCH on the Cell during the operation of the drx-inactivityTimer.
  • the terminal device receives the RRC configuration signaling sent by the network device, and the content of the RRC configuration signaling is as follows:
  • the first configuration information includes the DRX configuration, and the DRX parameters included in the DRX configuration include long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.
  • Second configuration information is used to configure a scaling parameter for the terminal device, and the scaling parameter is 2.
  • Serving cell configuration is used to configure two serving cells, cell0 and cell1, for the terminal device, where cell0 is PCell (corresponding to FR1) and cell1 is SCell (corresponding to FR2). And configure cell1 to use the scaling parameter (that is, configure cell1 as a cell that needs to scale the PDCCH monitoring duration).
  • the terminal device periodically starts the on-durationtimer based on the DRX configuration.
  • the terminal device monitors the PDCCH on cell0 during the on-durationtimer operation.
  • the terminal device determines its longest PDCCH monitoring duration on cell1 during on-durationTimer operation as floor(on-durationTimer/2) according to the scaling parameters, and does not exceed the maximum PDCCH monitoring time during on-durationTimer operation.
  • the PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.
  • the terminal device If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the on-durationTimer operation, the terminal device starts the drx-InactivityTimer.
  • the terminal device monitors the PDCCH on the cell0 during the operation of the drx-inactivityTimer.
  • the terminal device determines that the longest PDCCH monitoring duration on cell1 during the operation of drx-inactivityTimer is floor (drx-inactivityTimer/2) according to the scaling parameters, and does not exceed the maximum during the operation of drx-inactivityTimer.
  • the PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.
  • the conditions for the terminal device to start on-durationTimer and drx-inactivityTimer will not change with the scaling parameters. For example, the terminal device blindly detects the PDCCH indicating the uplink or downlink transmission on the PCell. At this time, the terminal device will start the drx-inactivityTimer. The drx-inactivityTimer will apply to PCell and SCell (even when the drx-inactivityTimer is started, the terminal device does not blindly detect the PDCCH on the SCell due to the scaling parameter).
  • the Scell needs to be configured with a scaling parameter used to scale the PDCCH monitoring duration.
  • the scaling parameter can be applied to the drx-onDurationTimer or drx-InactivityTimer operation period (A SCell may be configured with a PDCCH monitoring time scaling function when either drx -onDurationTimer or drx-InactivityTimer is running).
  • the DRX activation time of the Scell can be defined with reference to the definition in Table 1 below. It should be noted that the DRX activation time of the Scell represents the time that the terminal device needs to monitor the PDCCH on the Scell.
  • the second configuration information it can be based on CellGroupConfig and MAC-CellGroupConfig, where the information element (IE) of CellGroupConfig refers to the following Table 2-1, and the newly added content in Table 2-1 is drxScaling-Config( That is, the second configuration information).
  • IE information element
  • MAC-CellGroupConfig refers to the following Table 3-1.
  • the newly added content in Table 3-1 is drx-ScalingFactor (scaling parameter), and its meaning refers to Table 3-2.
  • scaling parameters are configured for each DRX timer that needs to scale the PDCCH monitoring time to realize the power saving of the terminal device blindly detecting the PDCCH on the FR2 or Scell.
  • each MAC entity is configured with one DRX configuration (that is, each MAC entity is configured with only one DRX configuration).
  • all aggregated carriers use this DRX configuration.
  • the network device can configure at least one scaling parameter (such as multiple scaling parameters).
  • the terminal device When the terminal device starts blind detection of the PDCCH according to the DRX configuration, for the carrier configured with the scaling parameter, the terminal device will scale the PDCCH monitoring duration during the operation of the corresponding timer according to the scaling parameter associated with the timer, so that the corresponding carrier
  • the blind inspection time is shortened to achieve the purpose of power saving. In this way, only one set of DRX configuration can be maintained, and the power consumption saving on FR2 can be achieved at the same time. The following describes the specific steps.
  • the terminal device receives first configuration information sent by the network device, where the first configuration information includes DRX configuration (that is, DRX-config), where DRX-config is configured in MAC-CellGroupConfig.
  • DRX configuration that is, DRX-config
  • DRX-config is configured in MAC-CellGroupConfig.
  • the terminal device receives the second configuration information sent by the network device, the second configuration information is different from the first configuration information, and the second configuration information carries the first indication information for indicating at least one scaling parameter (such as multiple scaling parameters). Parameters), where each scaling parameter is used to scale the PDCCH monitoring duration during the running of a timer in DRX-config.
  • the longest PDCCH monitoring duration of the terminal device on the SCell during the running of the timer is determined based on the duration of the timer and the scaling parameter associated with the timer.
  • the SCell is only exemplary, and represents a cell that needs to scale the PDCCH monitoring duration. For each cell (or carrier) that needs to scale the PDCCH monitoring duration, the longest PDCCH monitoring duration needs to be determined separately.
  • one or more timers in DRX-config include at least one of the following: drx-onDurationTimer, drx-InactivityTimer.
  • a scaling parameter is configured for each timer that needs to scale the PDCCH monitoring duration.
  • the second configuration information is configured for a carrier (or cell), that is, for a certain carrier, if the second configuration information is configured, it means that the terminal device needs to scale the PDCCH monitoring duration on the carrier.
  • the second configuration information is carried in SCellConfig in CellGroupConfig.
  • the terminal device starts on-durationtimer at a fixed time based on DRX-config.
  • the behavior of terminal equipment monitoring PDCCH on each serving cell during on-durationtimer operation is as follows:
  • the terminal device scales the on-durationTimer duration according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to the on-durationTimer.
  • the terminal device is in the on-durationTimer operation period , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period.
  • the longest PDCCH monitoring duration is obtained by dividing or multiplying the on-durationTimer by the scaling parameter associated with the on-durationTimer.
  • the terminal device monitors the PDCCH on the Cell during the on-duration timer operation.
  • the terminal device If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the DRX activation time, the terminal device starts the drx-InactivityTimer.
  • the behavior of terminal equipment monitoring PDCCH on each serving cell during the operation of drx-InactivityTimer is as follows:
  • the terminal device scales the duration of drx-inactivityTimer according to the scaling parameter associated with drx-inactivityTimer to obtain the longest PDCCH monitoring duration corresponding to drx-inactivityTimer.
  • the terminal device is in During the operation of the drx-inactivityTimer, monitor the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period.
  • the longest PDCCH monitoring duration is obtained by dividing or multiplying the drx-inactivityTimer by the scaling parameter associated with the drx-inactivityTimer.
  • the terminal device monitors the PDCCH on the Cell during the operation of the drx-inactivityTimer.
  • the terminal device receives the RRC configuration signaling sent by the network device, and the content of the RRC configuration signaling is as follows:
  • the first configuration information includes the DRX configuration, and the DRX parameters included in the DRX configuration include long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.
  • the second configuration information is used to configure at least one scaling parameter (such as multiple scaling parameters) for the terminal device.
  • the scaling parameter is 2; for drx-InactivityTimer, the scaling parameter is 4.
  • Serving cell configuration is used to configure two serving cells, cell0 and cell1, for the terminal device, where cell0 is PCell (corresponding to FR1) and cell1 is SCell (corresponding to FR2). And configure cell1 to use the scaling parameter (that is, configure cell1 as a cell that needs to scale the PDCCH monitoring duration).
  • the terminal device periodically starts the on-durationtimer based on the DRX configuration.
  • the terminal device monitors the PDCCH on cell0 during the on-durationtimer operation.
  • the terminal device determines its longest PDCCH monitoring duration on cell1 during on-durationTimer operation as floor(on-durationTimer/2) according to the scaling parameters, and does not exceed the maximum PDCCH monitoring time during on-durationTimer operation.
  • the PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.
  • the terminal device If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the on-durationTimer operation, the terminal device starts the drx-InactivityTimer.
  • the terminal device monitors the PDCCH on the cell0 during the operation of the drx-inactivityTimer.
  • the terminal device determines that its longest PDCCH monitoring duration on cell1 during the operation of drx-inactivityTimer is floor (drx-inactivityTimer/4) according to the scaling parameters, and does not exceed the maximum during the operation of drx-inactivityTimer.
  • the PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.
  • the conditions for the terminal device to start on-durationTimer and drx-inactivityTimer will not change with the scaling parameters. For example, the terminal device blindly detects the PDCCH indicating the uplink or downlink transmission on the PCell. At this time, the terminal device will start the drx-inactivityTimer. The drx-inactivityTimer will apply to PCell and SCell (even when the drx-inactivityTimer is started, the terminal device does not blindly detect the PDCCH on the SCell due to the scaling parameter).
  • the Scell needs to be configured with a scaling parameter used to scale the PDCCH monitoring duration.
  • the scaling parameter can be applied to the drx-onDurationTimer or drx-InactivityTimer operation period (A SCell may be configured with a PDCCH monitoring time scaling function when either drx -onDurationTimer or drx-InactivityTimer is running).
  • the DRX activation time of the Scell can be defined with reference to the definition in Table 4 below. It should be noted that the DRX activation time of the Scell represents the time that the terminal device needs to monitor the PDCCH on the Scell.
  • the second configuration information it can be based on CellGroupConfig and MAC-CellGroupConfig, where the IE of CellGroupConfig refers to the following Table 5-1, and the newly added content in Table 5-1 is drxScaling-Config (that is, the second configuration information), Refer to Table 5-2 for its meaning.
  • the IE of MAC-CellGroupConfig refers to the following Table 6-1.
  • the newly added content in Table 6-1 is drx-ScalingFactor (ie scaling parameter), and its meaning parameter is Table 6-2.
  • FIG. 6 is a schematic diagram 1 of the structural composition of the DRX configuration device provided by an embodiment of the application, which is applied to a terminal device.
  • the DRX configuration device includes:
  • the receiving unit 601 is configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; Second configuration information, where the second configuration information is used to determine one or more scaling parameters;
  • the processing unit 602 is configured to monitor the PDCCH based on the first configuration information and the second configuration information.
  • the second configuration information is used to determine a scaling parameter
  • the scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;
  • the first cell is a cell that needs to scale the PDCCH monitoring time.
  • the second configuration information is carried in the cell configuration of the first cell.
  • the processing unit 602 is configured to monitor the PDCCH on the first cell within the first time period during which the first timer is running for the first cell that needs to scale the PDCCH monitoring time, wherein, the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.
  • the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;
  • Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;
  • the first cell is a cell that needs to scale the PDCCH monitoring time.
  • the second configuration information is carried in the cell configuration of the first cell.
  • the processing unit 602 is configured to monitor the PDCCH on the first cell within the first time period during which the first timer is running for the first cell that needs to scale the PDCCH monitoring time, wherein, the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.
  • the start time of the first duration is the start time of the first timer.
  • the first timer is any timer in the DRX configuration.
  • the processing unit 602 is further configured to monitor the PDCCH on the second cell during the operation of the first timer for the second cell that does not need to scale the PDCCH monitoring time.
  • the at least one timer includes at least one of the following:
  • DRX uplink retransmission timer (drx-RetransmissionTimerDL);
  • DRX downlink retransmission timer (drx-RetransmissionTimerUL).
  • the processing unit 602 is further configured to start the drx-InactivityTimer if a PDCCH for indicating newly transmitted data is received during the operation of the drx-onDurationTimer.
  • the DRX configuration is a DRX configuration in an RRC connected state.
  • FIG. 7 is a second structural diagram of the DRX configuration device provided by an embodiment of the application, which is applied to network equipment. As shown in FIG. 7, the DRX configuration device includes:
  • the sending unit 701 is configured to send first configuration information to a terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; and a second configuration information is sent to the terminal device. Configuration information, where the second configuration information is used to determine one or more scaling parameters;
  • the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.
  • the second configuration information is used to determine a scaling parameter
  • the scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;
  • the first cell is a cell that needs to scale the PDCCH monitoring time.
  • the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;
  • Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;
  • the first cell is a cell that needs to scale the PDCCH monitoring time.
  • the second configuration information is carried in the cell configuration of the first cell.
  • the at least one timer includes at least one of the following:
  • DRX uplink retransmission timer (drx-RetransmissionTimerDL);
  • DRX downlink retransmission timer (drx-RetransmissionTimerUL).
  • the DRX configuration is a DRX configuration in an RRC connected state.
  • FIG. 8 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 800 may further include a memory 820.
  • the processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.
  • the memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.
  • the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 830 may include a transmitter and a receiver.
  • the transceiver 830 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 800 may specifically be a network device in an embodiment of the present application, and the communication device 800 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .
  • the communication device 800 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application.
  • I won’t repeat it here.
  • FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 900 may further include a memory 920.
  • the processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.
  • the memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.
  • the chip 900 may further include an input interface 930.
  • the processor 910 can control the input interface 930 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 900 may further include an output interface 940.
  • the processor 910 can control the output interface 940 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • FIG. 10 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. As shown in FIG. 10, the communication system 1000 includes a terminal device 1010 and a network device 1020.
  • the terminal device 1010 can be used to implement the corresponding function implemented by the terminal device in the above method
  • the network device 1020 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the 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), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I won’t repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application 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, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de configuration DRX, un dispositif terminal et un dispositif réseau. Le procédé comprend les étapes suivantes : un dispositif terminal reçoit des premières informations de configuration envoyées par un dispositif réseau, les premières informations de configuration étant utilisées pour déterminer une configuration DRX et la configuration DRX étant utilisée pour déterminer un paramètre de configuration d'au moins une minuterie ; le dispositif terminal reçoit des secondes informations de configuration envoyées par le dispositif réseau, les secondes informations de configuration étant utilisées pour déterminer un ou plusieurs paramètres de mise à l'échelle ; et le dispositif terminal surveille un canal de commande de liaison descendante physique (PDCCH) sur la base des premières informations de configuration et des secondes informations de configuration.
PCT/CN2019/114474 2019-10-30 2019-10-30 Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau WO2021081838A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980099433.8A CN114270917B (zh) 2019-10-30 2019-10-30 一种drx配置方法及装置、终端设备、网络设备
PCT/CN2019/114474 WO2021081838A1 (fr) 2019-10-30 2019-10-30 Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/114474 WO2021081838A1 (fr) 2019-10-30 2019-10-30 Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau

Publications (1)

Publication Number Publication Date
WO2021081838A1 true WO2021081838A1 (fr) 2021-05-06

Family

ID=75715701

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/114474 WO2021081838A1 (fr) 2019-10-30 2019-10-30 Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN114270917B (fr)
WO (1) WO2021081838A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11546871B2 (en) * 2018-04-18 2023-01-03 Ntt Docomo, Inc. Terminal, radio communication method, and base station
WO2023174041A1 (fr) * 2022-03-18 2023-09-21 华为技术有限公司 Procédé et appareil de communication
WO2024027559A1 (fr) * 2022-08-01 2024-02-08 维沃移动通信有限公司 Procédé de commande de ressources, terminal et dispositif électronique
WO2024092522A1 (fr) * 2022-11-01 2024-05-10 Oppo广东移动通信有限公司 Procédés et appareils de mise en œuvre de drx, et dispositif terminal

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116939783A (zh) * 2022-04-08 2023-10-24 北京紫光展锐通信技术有限公司 通信方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017132899A1 (fr) * 2016-02-03 2017-08-10 Nokia Technologies Oy Actionnement de temporiseur de réception discontinue pour longueur de tti modifiée
CN109922534A (zh) * 2017-12-13 2019-06-21 华硕电脑股份有限公司 随机接入程序期间处理带宽部分定时器的方法和设备
CN110392380A (zh) * 2018-04-16 2019-10-29 英特尔公司 用于drx模式中的波束管理和波束故障恢复的装置和方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017132899A1 (fr) * 2016-02-03 2017-08-10 Nokia Technologies Oy Actionnement de temporiseur de réception discontinue pour longueur de tti modifiée
CN109922534A (zh) * 2017-12-13 2019-06-21 华硕电脑股份有限公司 随机接入程序期间处理带宽部分定时器的方法和设备
CN110392380A (zh) * 2018-04-16 2019-10-29 英特尔公司 用于drx模式中的波束管理和波束故障恢复的装置和方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON, QUALCOMM INC., SAMSUNG, VERIZON, DEUTSCHE TELEKOM: "cDRX enhancement for CA", 3GPP DRAFT; R2-1913196 CDRX ENHANCEMENT FOR CA, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, China; 20191014 - 20191018, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051791208 *
MEDIATEK INC.: "Recommendations for NR UE Power Saving A Technical Contribution from MediaTek Inc.", 3GPP DRAFT; R1-1909740_RECOMMENDATIONS FOR NR UE POWER SAVING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. ; 20190801, 4 September 2019 (2019-09-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051766333 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11546871B2 (en) * 2018-04-18 2023-01-03 Ntt Docomo, Inc. Terminal, radio communication method, and base station
WO2023174041A1 (fr) * 2022-03-18 2023-09-21 华为技术有限公司 Procédé et appareil de communication
WO2024027559A1 (fr) * 2022-08-01 2024-02-08 维沃移动通信有限公司 Procédé de commande de ressources, terminal et dispositif électronique
WO2024092522A1 (fr) * 2022-11-01 2024-05-10 Oppo广东移动通信有限公司 Procédés et appareils de mise en œuvre de drx, et dispositif terminal

Also Published As

Publication number Publication date
CN114270917A (zh) 2022-04-01
CN114270917B (zh) 2023-10-03

Similar Documents

Publication Publication Date Title
WO2020019187A1 (fr) Procédé et appareil de surveillance de canal, dispositif terminal et dispositif de réseau
TWI821368B (zh) 非連續傳輸的方法和設備
WO2021081838A1 (fr) Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau
WO2020220239A1 (fr) Procédé et appareil permettant de commander un terminal afin de recevoir des informations, et terminal
WO2021120013A1 (fr) Procédé de surveillance d'un signal de réveil, dispositif terminal et dispositif de réseau
US20220039013A1 (en) Method and device for discontinuous reception
WO2020163998A1 (fr) Procédé et dispositif de communication sans fil
WO2021056136A1 (fr) Procédé de surveillance de wus, procédé d'envoi d'informations et dispositif
WO2021082012A1 (fr) Procédé pour déterminer l'état de démarrage d'un temporisateur continu de réception discontinue et dispositifs
WO2020019756A1 (fr) Procédé et appareil de détermination de ressource de transmission, et dispositif terminal
WO2020237594A1 (fr) Procédé et appareil de gestion de bwp et terminal
WO2020087326A1 (fr) Procédé et dispositif de surveillance de pdcch
US20220030565A1 (en) Method and device for adjusting pdcch monitoring period
WO2021088017A1 (fr) Procédé de détermination de type d'informations de commande de liaison descendante, et appareil
WO2020001123A1 (fr) Appareil et procédé de détection de canal de commande de liaison descendante, et dispositif terminal
WO2021092861A1 (fr) Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2020077667A1 (fr) Procédé et dispositif d'activation de temporisateur, et terminal
WO2021114206A1 (fr) Procédé et appareil de mesure de cli, dispositif terminal et dispositif de réseau
WO2021068173A1 (fr) Procédé et appareil de transmission de signal ainsi que dispositif terminal
WO2022021023A1 (fr) Procédé et appareil d'indication d'informations, dispositif terminal et dispositif de réseau
TWI813728B (zh) 一種訊號傳輸方法及適用該方法的裝置、網路設備及終端設備
WO2020186467A1 (fr) Procédé et appareil pour réception discontinue sur spectre sans licence
WO2020077600A1 (fr) Procédé et dispositif pour le déclenchement de procédure de reprise après défaillance de faisceau, et terminal
WO2020124548A1 (fr) Procédé et appareil permettant de déterminer une ressource temps-fréquence, puce et programme informatique
WO2020118718A1 (fr) Procédé et appareil pour la détermination de paramètres de configuration, et terminal

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: 19950293

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19950293

Country of ref document: EP

Kind code of ref document: A1