WO2020163998A1 - Procédé et dispositif de communication sans fil - Google Patents

Procédé et dispositif de communication sans fil Download PDF

Info

Publication number
WO2020163998A1
WO2020163998A1 PCT/CN2019/074884 CN2019074884W WO2020163998A1 WO 2020163998 A1 WO2020163998 A1 WO 2020163998A1 CN 2019074884 W CN2019074884 W CN 2019074884W WO 2020163998 A1 WO2020163998 A1 WO 2020163998A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
indication information
deactivation timer
drx
configuration information
Prior art date
Application number
PCT/CN2019/074884
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 PCT/CN2019/074884 priority Critical patent/WO2020163998A1/fr
Priority to CN201980019293.9A priority patent/CN111886904A/zh
Publication of WO2020163998A1 publication Critical patent/WO2020163998A1/fr

Links

Images

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
    • 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 communication, and more specifically, to methods and devices for wireless communication.
  • the data stream is usually bursty.
  • the terminal device has data transmission for a period of time, but there is no data transmission for a long period of time. Therefore, if the terminal device has been blindly checking the Physical Downlink Control Channel (PDCCH), it will cause excessive power consumption of the terminal device.
  • PDCCH Physical Downlink Control Channel
  • DRX Discontinuous Reception
  • LTE Long Term Evolution
  • the terminal device when the terminal device does not have data transmission, it can reduce power consumption by stopping receiving the Physical Downlink Control Channel (PDCCH) (the blind PDCCH detection will be stopped at this time), thereby increasing battery life.
  • the network device configures a DRX cycle (cycle) for the terminal device in the radio resource control connection (Radio Resource Control_CONNECTED, RRC_CONNECTED) state.
  • the DRX cycle consists of an activation period (On Duration) and a dormancy period (Opportunity for DRX).
  • On Duration the terminal device monitors and receives the PDCCH; during the Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption .
  • the duration of the activation period can be controlled by the DRX activation timer (drx-onDurationTimer) and the DRX deactivation timer (drx-InactivityTimer). That is, the terminal device starts the drx-InactivityTimer when receiving the PDCCH, so the OnDuration time will be extended with the start of the drx-onDurationTimer. However, since the drx-InactivityTimer needs to be restarted every time a PDCCH is received, the terminal device prolongs the time for blindly detecting the PDCCH, thereby increasing power consumption. In addition, because the drx-InactivityTimer is pre-configured by the network device, it cannot match the arrival characteristics of the service well.
  • the network is pre-configured with a specific value, such as 10ms, but because the arrival of the service is uncertain in advance, scheduling these uncertain services will cause the drx-InactivityTimer to restart frequently, making the terminal unable to enter the sleep period , Further increase the power consumption of the terminal equipment.
  • a wireless communication method and device are provided, which can reduce the power consumption of terminal devices.
  • a wireless communication method including:
  • the terminal device receives first indication information, where the first indication information is used to instruct the terminal device to stop, start or restart a deactivation timer for discontinuous reception of DRX;
  • the terminal device When the terminal device receives the physical downlink control channel PDCCH, it stops, starts or restarts the deactivation timer according to the first indication information.
  • a wireless communication method including:
  • the network device sends first indication information, where the first indication information is used to instruct the terminal device to stop, start, or restart a deactivation timer for discontinuous reception of DRX;
  • the network device sends the physical downlink control channel PDCCH.
  • a terminal device which is used to execute the method in the foregoing first aspect or each of its implementation manners.
  • the terminal device includes a functional module for executing the method in the foregoing first aspect or each implementation manner thereof.
  • a network device configured to execute the method in the second aspect or its implementation manners.
  • the network device includes a functional module for executing the method in the foregoing second aspect or each implementation manner thereof.
  • a terminal device including 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 method in the foregoing first aspect or each of its implementation manners.
  • a network device including 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 method in the above-mentioned second aspect or each implementation manner thereof.
  • a chip for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • 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 any one of the above-mentioned first aspect to the second aspect or each implementation manner thereof Method in.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program product which includes computer program instructions that cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the network device can dynamically indicate whether the terminal device needs to stop, start or restart the deactivation timer (drx-InactivityTimer) through the first indication information.
  • the network device can dynamically stop the drx-InactivityTimer from the terminal device to avoid The terminal device starts or restarts the drx-InactivityTimer after receiving the PDCCH, which can effectively reduce the time for the terminal device to blindly detect the PDCCH, thereby reducing the power consumption of the terminal device.
  • Figure 1 is an example of the application scenario of this application.
  • Fig. 2 is a schematic block diagram of DRX in an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a terminal device in an embodiment of the present application starting a deactivation timer.
  • FIG. 4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
  • 5 to 8 are schematic diagrams of stopping, starting, or restarting the deactivation timer of the terminal device according to the embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a chip of an embodiment of the present application.
  • Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • the communication system 100 may include a terminal device 110 and a network device 120.
  • the network device 120 may communicate with the terminal device 110 through an air interface.
  • the terminal device 110 and the network device 120 support multi-service transmission.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • NR New Radio
  • 5G systems etc.
  • the technical solutions of the embodiments of the present application can be applied to the long-term evolution (LTE) coverage of a wide area and the NR island coverage mode.
  • LTE long-term evolution
  • a large amount of LTE is deployed below 6GHz, and there is very little spectrum below 6GHz that can be used for 5G.
  • So NR must study the frequency spectrum application above 6GHz, and the high frequency band has limited coverage and fast signal fading.
  • a tight interworking mode between LTE and NR is proposed.
  • the main application scenarios of 5G include: Enhance Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive machine type of communication, mMTC ).
  • eMBB aims at users to obtain multimedia content, services and data, and its demand is growing rapidly.
  • URLLC Ultra-Reliable and Low Latency Communication
  • Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety protection, etc.
  • Typical features of mMTC include: high connection density, small data volume, delay-insensitive services, low-cost modules and long service life.
  • the network coverage in the embodiments of the present application may adopt wide-area Long Term Evolution (LTE) coverage and NR island coverage mode.
  • LTE Long Term Evolution
  • NR island coverage mode In order to protect mobile operators' early investment in LTE, a tight interworking mode between LTE and NR can be further adopted.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as sparse code multiple access (SCMA) systems, low-density signatures ( Low Density Signature (LDS) system, etc.
  • SCMA sparse code multiple access
  • LDS Low Density Signature
  • SCMA system and LDS system can also be called other names in the communication field;
  • the technical solutions of the embodiments of this application can be applied to multiple access technologies that use non-orthogonal multiple access technologies.
  • Carrier transmission systems such as non-orthogonal multiple access technology Orthogonal Frequency Division Multiplexing (OFDM), Filter Bank Multi-Carrier (FBMC), General Frequency Division Multiplexing ( Generalized Frequency Division Multiplexing, GFDM), filtered orthogonal frequency division multiplexing (Filtered-OFDM, F-OFDM) systems, etc.
  • OFDM Orthogonal Frequency Division Multiplexing
  • FBMC Filter Bank Multi-Carrier
  • GFDM General Frequency Division Multiplexing
  • GFDM Generalized Frequency Division Multiplexing
  • Filtered-OFDM Frequency Division Multiplexing
  • F-OFDM filtered orthogonal frequency division multiplexing
  • the network device 120 may be an access network device that communicates with the terminal device 110.
  • the access network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices 110 (for example, UE) located in the coverage area.
  • the network device 120 may be a base station (Base Transceiver Station, BTS) in a global system of mobile communication (GSM) system or a code division multiple access (Code Division Multiple Access, CDMA), or it may be The base station (NodeB, NB) in the Wideband Code Division Multiple Access (WCDMA) system, and the network device 120 may also be the Evolutional Node B (Evolutional Node B) in the Long Term Evolution (LTE) system. eNB or eNodeB).
  • the network device 120 may also be a next generation radio access network (Next Generation Radio Access Network, NG RAN), or a base station (gNB) in an NR system, or a cloud radio access network (Cloud Radio Access).
  • Next Generation Radio Access Network Next Generation Radio Access Network
  • gNB base station
  • Cloud Radio Access Cloud Radio Access
  • CRAN public Land Mobile Network
  • PLMN Land Mobile Network
  • the terminal device 110 may be any terminal device, including but not limited to: connected via a wired line, such as via a public switched telephone network (Public Switched Telephone Networks, PSTN), digital subscriber line (Digital Subscriber Line, DSL), Digital cable, 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 television networks such as DVB-H networks , Satellite network, AM-FM broadcast transmitter; and/or another terminal device set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal” or a "mobile terminal".
  • Examples of mobile terminals include, but are not limited to, satellites 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 phone transceivers Electronic device.
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, 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, terminal devices in 5G networks, or terminal devices 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 terminal devices 110.
  • FIG. 1 exemplarily shows a network device and a terminal device.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices.
  • the implementation of this application Not limited to this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, and the embodiment of the present application is not limited thereto.
  • the uplink channel of the embodiment of the present application may include a physical random access channel (Physical Random Access Channel, PRACH), a physical uplink control channel (Physical Uplink Control channel, PUCCH), and a physical uplink shared channel (Physical Uplink Shared channel, PUSCH) and so on.
  • the uplink reference signal may include an uplink demodulation reference signal (Demodulation Reference Signal, DMRS), a sounding reference signal (Sounding Reference Signal, SRS), a phase tracking reference signal (PT-RS), etc.
  • DMRS Downlink demodulation Reference Signal
  • SRS Sounding Reference Signal
  • PT-RS phase tracking reference signal
  • the uplink DMRS can be used for uplink channel demodulation
  • SRS can be used for uplink channel measurement
  • PT-RS can also be used for uplink channel measurement, uplink time-frequency synchronization or phase tracking.
  • the embodiments of the present application may include uplink physical channels or uplink reference signals with the same names and different functions as the above, and may also include uplink physical channels or uplink reference signals with different names and the same functions as the above. Not limited.
  • the communication device may include a network device 120 and a terminal device 110 having communication functions, and the network device 120 and the terminal device 110 may be the above-mentioned devices, which will not be repeated here;
  • the communication 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.
  • a packet-based data stream can be transmitted between the terminal device 110 and the network device 120.
  • the packet-based data stream is usually bursty.
  • the terminal device 110 has data transmission for a period of time, but there is no data transmission for a longer period of time. Therefore, if the terminal device 110 has been blindly checking the Physical Downlink Control Channel (PDCCH), it will cause excessive power consumption of the terminal device.
  • PDCCH Physical Downlink Control Channel
  • DRX Discontinuous Reception
  • the network can configure the terminal to wake up at the time predicted by the network (DRX ON), and the terminal monitors the downlink control channel; at the same time, the network can also configure the terminal to sleep at the time predicted by the network (DRX OFF), that is, The terminal equipment does not need to monitor the downlink control channel.
  • the network device 120 can schedule the terminal device 110 during the DRX ON time of the terminal device 110.
  • the radio frequency is turned off, which can reduce the number of terminals. Power consumption.
  • a Media Access Control (MAC) entity is configured with a DRX function by a Radio Resource Control (Radio Resource Control, RRC) to control the behavior of the terminal to monitor the PDCCH.
  • RRC Radio Resource Control
  • the DRX cycle configured by the network device for the terminal device consists of an activation period (On Duration) and a sleep period (Opportunity for DRX).
  • On Duration an activation period
  • Opportunity for DRX a sleep period
  • the MAC entity can monitor and receive PDCCH by the terminal device within the On Duration time; during the Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption.
  • the terminal device in the dormant period in the embodiment of the present application does not receive the PDCCH, but can receive data from other physical channels.
  • the embodiment of the present invention does not make specific limitations.
  • the terminal device may receive a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), acknowledgment/non-acknowledgement (ACK/NACK), etc.
  • PDSCH Physical Downlink Shared Channel
  • ACK/NACK acknowledgment/non-acknowledgement
  • SPS Semi-Persistent Scheduling
  • the terminal device can receive periodically configured PDSCH data.
  • the duration of the activation period can be controlled by the DRX-onDuration Timer (drx-onDurationTimer) and the DRX inactivation timer (drx-InactivityTimer).
  • the DRX-active period timer is also called the DRX-active period timer.
  • the deactivation timer is also called the inactivity timer.
  • the active period ends when the DRX-onDuration Timer (drx-onDurationTimer) expires.
  • the terminal device extends the duration of the activation period by starting the drx-InactivityTimer.
  • the terminal device starts the drx-InactivityTimer when receiving the PDCCH, so the OnDuration time will be extended with the start of the drx-onDurationTimer. It should be understood that, in the framework shown in FIG. 3, when the terminal device receives the PDCCH and has currently started the drx-InactivityTimer, it may restart the drx-InactivityTimer.
  • the terminal device prolongs the time for blindly detecting the PDCCH, thereby increasing the power consumption.
  • the drx-InactivityTimer is pre-configured by the network device, it cannot match the arrival characteristics of the service well. For example, suppose that the network is pre-configured with a specific value, such as 10ms, but because the arrival of the service is uncertain in advance, scheduling these uncertain services will cause the drx-InactivityTimer to restart frequently, making the terminal unable to enter the sleep period , Further increase the power consumption of the terminal equipment.
  • the embodiment of the present invention provides a method for managing a timer, which is used for a terminal device to stop, start or restart the deactivation timer in time, thereby reducing the power consumption of the terminal device.
  • FIG. 4 is a schematic flowchart of managing timers according to an embodiment of the present invention.
  • FIG. 4 shows a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application.
  • the method 200 may be interactively executed by a terminal device and a network device.
  • the terminal device shown in FIG. 4 may be the terminal device shown in FIG. 1, and the network device shown in FIG. 4 may be the access network device shown in FIG. 1.
  • the method 200 includes some or all of the following content:
  • the method 200 includes:
  • the network device generates first indication information, where the first indication information is used to instruct the terminal device to stop, start, or restart a deactivation timer for discontinuous reception of DRX.
  • S220 The network device sends the first indication information to the terminal device.
  • the network device can dynamically indicate whether the terminal device needs to stop, start or restart the deactivation timer (drx-InactivityTimer) through the first indication information.
  • the network device can dynamically stop the drx-InactivityTimer from the terminal device to avoid The terminal device starts or restarts the drx-InactivityTimer after receiving the PDCCH, which can effectively reduce the time for the terminal device to blindly detect the PDCCH, thereby reducing the power consumption of the terminal device.
  • the method for managing timers can be applied to a terminal device working in an unlicensed frequency band, and the terminal device is configured with a DRX cycle and a deactivation timer.
  • the deactivation timer can also be replaced with a DRX downlink retransmission timer (drx-RetransmissionTimerDL) or a DRX uplink retransmission timer (drx-RetransmissionTimerUL).
  • the terminal device When the terminal device receives the PDCCH, it stops, starts or restarts the deactivation timer only through the first indication information.
  • the UE receives network configuration information and configures DRX related parameters. These parameters may include at least one drx-InactivityTimer and other related DRX parameters, such as drx-onDurationTimer.
  • the UE detects the PDCCH during the DRX Active Time, and if it detects the PDCCH, it determines whether to start the drx-InactivityTimer according to the first indication information.
  • the terminal device when the PDCCH is used to schedule new data transmission (that is, when the PDCCH is a PDCCH used to schedule new downlink data or uplink new data), the terminal device starts drx-InactivityTimer, and the PDCCH is used for scheduling When retransmitting data, the terminal device does not start drx-InactivityTimer.
  • the DCI carried in the PDCCH carries an indication field
  • the first indication information is carried in the indication field for dynamically indicating whether to start the drx-InactivityTimer. For example, when the indication field is 1, the drx-InactivityTimer is started, and when the indication field is 0, the drx-InactivityTimer is not started. For another example, when the indication field is 0, the drx-InactivityTimer is started, and when the indication field is 1, the drx-InactivityTimer is not started.
  • a MAC CE can be used to dynamically indicate whether to start drx-InactivityTimer.
  • the MAC CE includes the first indication information.
  • the terminal device may start or not start drx-InactivityTimer upon receiving the PDCCH.
  • the UE does not start drx-InactivityTimer by default when it receives the PDCCH (the PDCCH schedules new data transmission), then when the UE receives the MAC CE carrying the first indication information, and the first indication information is used When indicating that the drx-InactivityTimer needs to be started, the UE starts the drx-InactivityTimer.
  • the UE starts/restarts drx-InactivityTimer by default when it receives a PDCCH (the PDCCH schedules new data transmission).
  • the UE receives the MAC CE that carries the first indication information, and the first indication The information is used to indicate that when the drx-InactivityTimer needs to be stopped, the UE stops the drx-InactivityTimer.
  • the UE Taking the first indication information to indicate the stop, start or restart of the deactivation timer through the data type used by the PDCCH for scheduling as an example, if the UE detects the PDCCH at the DRX Active Time and the PDCCH indicates that the drx-InactivityTimer is not started, the UE Do not start drx-InactivityTimer. If the PDCCH is detected in the DRX Active Time, and the PDCCH indicates that the drx-InactivityTimer is started, the UE starts the drx-InactivityTimer according to the pre-configured drx-InactivityTimer.
  • Fig. 5 is a schematic diagram of starting a deactivation timer according to an embodiment of the present application.
  • the UE starts the drx-onDurationTimer at a specific location according to the DRX parameter information configured by RRC.
  • the operation period of drx-onDurationTimer is DRX Active Time, and the time of DRX Active Time may at least depend on the time during the operation of drx-onDurationTimer and/or the time during the operation of drx-InactivityTimer.
  • the UE detects the PDCCH.
  • the UE If the UE receives a PDCCH and the PDCCH indicates not to start drx-InactivityTimer, the UE does not start drx-InactivityTimer; if the UE receives a PDCCH and the PDCCH indicates to start drx-InactivityTimer, the UE starts drx-InactivityTimer, that is, ActiveTime corresponds to During this period of time, the UE continues to detect PDCCH.
  • FIG. 5 is only an example of an embodiment of the present application, and should not be understood as a limitation of the present application.
  • a certain specific sequence such as a wake-up signal, can also be used to dynamically indicate whether to start the drx-InactivityTimer.
  • a wake-up signal can also be used to dynamically indicate whether to start the drx-InactivityTimer.
  • the UE detects the PDCCH, the UE starts the drx-InactivityTimer, and the network can then send a wake-up signal to dynamically stop the drx-InactivityTimer.
  • a C-RNTI scrambled PDCCH is used to indicate to start the drx-InactivityTimer
  • a new RNTI scrambled PDCCH is used to indicate not to start the drx-InactivityTimer.
  • the terminal device stops, starts, or restarts the target deactivation timer in at least one deactivation timer through the first indication information.
  • the UE receives network configuration information and configures DRX related parameters. These parameters include at least one drx-InactivityTimer and other related DRX parameters, such as drx-onDurationTimer.
  • the UE detects the PDCCH during the DRX Active Time, and if it detects the PDCCH, it decides to start/not start the drx-InactivityTimer according to the indication of the first indication information; if the first indication information indicates to start the drx-InactivityTimer, the The first indication information indicates a certain drx-InactivityTimer of the startup configuration.
  • the first indication information is only used to indicate the drx-InactivityTimer that the UE needs to start, that is, the UE decides to start a configured drx-InactivityTimer according to the indication of the first indication information.
  • the value of the drx-InactivityTimer selected by the network to be started is 0, it is equivalent to instructing the UE not to start the drx-InactivityTimer.
  • the network can be made to choose among multiple drx-InactivityTimer configurations, which can better match the characteristics of the service to a certain extent, avoiding that the network can only be configured with one drx-InactivityTimer value, and can be more accurate Adjust the UE's DRX activation time to achieve power saving effect.
  • the terminal device starts drx-InactivityTimer, and specifically instructs to start the Which one of the at least one drx-InactivityTimer is drx-InactivityTimer, when the PDCCH is used for scheduling retransmission of data, the drx-InactivityTimer is not started.
  • the DCI carried by the PDCCH carries an indication field
  • the first indication information is carried in the indication field for dynamically indicating whether to start drx-InactivityTimer, and/or which drx-InactivityTimer is started.
  • the first drx-InactivityTimer is started when the indication field is 001
  • the second drx-InactivityTimer is started when the indication field is 010
  • the third drx-InactivityTimer is started when the indication field is 100
  • the indication field is 000 Does not start drx-InactivityTimer at any time.
  • the third drx-InactivityTimer is started when the indication field is 000, and the value of the third drx-InactivityTimer is 0.
  • a MAC CE can be used to dynamically indicate whether the drx-InactivityTimer needs to be started, and/or which timer to start.
  • the UE does not start drx-InactivityTimer by default when receiving the PDCCH (the PDCCH schedules new data transmission).
  • the MAC CE indicates whether the drx-InactivityTimer needs to be started. , And which drx-InactivityTimer to start if it is indicated to be started.
  • the UE starts/restarts drx-InactivityTimer by default when receiving the PDCCH (the PDCCH schedules new data transmission), and when the UE receives the MAC CE that indicates that the drx-InactivityTimer needs to be stopped Stop the drx-InactivityTimer when.
  • the first indication information may indicate which configured drx-InactivityTimer the UE starts. Wherein, when the first indication information indicates that the value of the started drx-InactivityTimer is 0, it is equivalent to instructing the UE not to start the drx-InactivityTimer.
  • the time of DRX Active Time may at least depend on the time during the operation of drx-onDurationTimer and/or the time during the operation of drx-InactivityTimer.
  • DRX parameters configured by RRC are as follows:
  • the network device may configure two drx-InactivityTimers in the DRX configuration information for the UE, and each drx-InactivityTimer has a different value. For example, one is 10ms and the other is 2ms.
  • the first indication information can dynamically switch between different drx-InactivityTimers through DCI.
  • the network can also configure more drx-InactivityTimer in the DRX configured by the UE. For example, there can be a drx-InactivityTimer with a value of 0. If the DCI switches drx-InactivityTimer to a timer with a configuration value of 0, it means that drx-InactivityTimer does not start.
  • Fig. 6 is a schematic diagram of starting a deactivation timer according to an embodiment of the present application.
  • the UE detects 1 PDCCH, which is used to indicate not to start the drx-InactivityTimer or to indicate to start a drx-InactivityTimer with a value of 0.
  • the UE detects 2 PDCCHs, the first of which indicates to start the first deactivation timer (drx-InactivityTimer-Opt1), and the second PDCCH indicates to start the second deactivation timer (drx -InactivityTimer-Opt2), these two timers can be pre-configured through the network and have different lengths.
  • the network can dynamically change the UE to extend the Active Time, so that it can better adapt to the arrival attributes of the service to a certain extent, and achieve the effect of energy saving.
  • the PDCCH can also be replaced by a wake-up signal, or other signal based on a sequence.
  • different drx-InactivityTimer may correspond to different power saving modes.
  • the first deactivation timer corresponds to the non-power saving mode
  • the second deactivation timer corresponds to the power saving mode
  • the configuration parameter corresponding to drx-InactivityTimer-Opt1 is for the purpose of improving throughput or reducing time delay
  • the configuration parameter corresponding to drx-InactivityTimer-Opt2 is for the purpose of saving power.
  • the UE detects 1 PDCCH, which is used to indicate not to start the drx-InactivityTimer or to indicate to start a drx-InactivityTimer with a value of 0.
  • the UE detects 2 PDCCHs, the first of which indicates to start drx-InactivityTimer-Opt1, then the UE uses the parameters corresponding to power saving mode1.
  • the second PDCCH indicates to start drx-InactivityTimer-Opt2, and the UE adopts the parameters corresponding to power saving mode2.
  • Both timers are pre-configured by the network, and their corresponding power saving mode parameters are also pre-configured by the network.
  • the advantage of this is that the network can dynamically change the UE to extend the Active Time, and for different Active Time, the UE can use different power saving modes to better adapt to the arrival attributes of the service to a certain extent, and achieve the effect of energy saving.
  • the UE receives the PDCCH, and the PDCCH dynamically indicates whether the UE needs to start the drx-InactivityTimer, and further, indicates which drx-InactivityTimer the UE starts.
  • the DCI carried by the PDCCH carries an indication field to dynamically indicate whether the UE needs to start drx-InactivityTimer, and further, instruct the UE to start which drx-InactivityTimer; if drx-InactivityTimer-Opt1 is started, the corresponding mode will also take effect .
  • a MAC CE may be used to dynamically indicate whether the UE needs to start the drx-InactivityTimer, and further, to indicate which drx-InactivityTimer the UE starts.
  • the UE does not start drx-InactivityTimer by default when it receives the PDCCH (the PDCCH schedules new data transmission), and only when the UE receives the MAC CE for instructing to start the drx-InactivityTimer,
  • the UE receives a MAC CE used to instruct to start drx-InactivityTimer-Opt1 its corresponding configuration mode will also take effect.
  • the UE starts/restarts the drx-InactivityTimer by default when receiving the PDCCH (the PDCCH schedules new transmission data), and stops the drx-InactivityTimer when receiving the MAC CE indicating that the drx-InactivityTimer needs to be stopped.
  • the terminal device When the terminal device receives the PDCCH, it stops, starts or restarts the deactivation timer through the first indication information and the second indication information.
  • the first indication information is used to instruct the terminal device to stop, start or restart the deactivation timer
  • the second indication information is used to indicate whether the terminal device can start the deactivation timer within a target time period. Deactivate the timer.
  • the UE receives network configuration information and configures DRX related parameters. These parameters include at least one drx-InactivityTimer and other related DRX parameters, such as drx-onDurationTimer. Before starting the drx-OnDurationTimer, the UE first monitors the second indication information.
  • the second indication information may indicate whether it is possible or allowed to start the drx-InactivityTimer within the target time period.
  • the target time period may be the running time of drx-onDurationTimer or the running time of several drx-onDurationTimers.
  • the second indication information indicates that the drx-InactivityTimer is not allowed to be started during the following drx-onDurationTimer, even if the UE detects the first indication information for instructing the start of the drx-InactivityTimer during the operation of the drx-onDurationTimer, the drx-InactivityTimer is not started; If the second indication information indicates that the drx-InactivityTimer is allowed to be started during the following drx-onDurationTimer, the UE starts the drx-InactivityTimer when it detects the first indication information for instructing to start the drx-InactivityTimer during the operation period of the drx-onDurationTimer .
  • the UE before the UE enters Active Time, the UE will first detect the second indication information.
  • the second indication information may indicate whether the drx-InactivityTimer needs to be started and whether the drx-onDurationTimer needs to be started.
  • the Wake-up signal is a sequence-based signal.
  • the Wake-up signal may be used to instruct the terminal device to start or not to start the activation timer.
  • Fig. 8 is a schematic diagram of starting a deactivation timer according to an embodiment of the present application.
  • the UE detects the wake-up signal in a period of time before the drx-onDurationTimer.
  • the UE In a period of time before the first drx-onDurationTimer, the UE detects the wake-up signal, and the wake-up signal indicates that the terminal device drx-onDurationTimer needs to be started, and indicates that the terminal device drx-InactivityTimer is in Active Time. Does not work during this period. Then the UE will not start the drx-InactivityTimer even if it receives the PDCCH scheduling newly transmitted data.
  • the UE In a period of time before the second drx-onDurationTimer, the UE detects the wake-up signal, and the wake-up signal indicates that the terminal device drx-onDurationTimer needs to be started, and indicates that the terminal device drx-InactivityTimer is in Active Time. Can work during the period. Then, if the UE receives the PDCCH scheduling new transmission data, it needs to start the drx-InactivityTimer.
  • the UE detects a wake-up signal in a period of time before the third drx-onDurationTimer, and the wake-up signal indicates that the terminal device drx-onDurationTimer does not need to be started, then the terminal device does not start the drx-onDurationTimer.
  • FIG. 8 is only an example of this application, and should not be construed as a limitation to this application.
  • a drx-InactivityTimer activation/deactivation flag is defined to dynamically indicate whether the terminal device is allowed to start the drx-InactivityTimer within the target time period. For example, if drx-InactivityTimer activation/deactivation is marked as inactive state, it indicates that the terminal device is not allowed to start drx-InactivityTimer within the target time period, and drx-InactivityTimer activation/deactivation is marked as active state, indicating that the terminal The device is allowed to start drx-InactivityTimer within the target time period.
  • the UE receives network configuration information and configures DRX related parameters. These parameters include a drx-InactivityTimer and a drx-InactivityTimer activation/deactivation flag, and other related DRX parameters, such as drx-onDurationTimer.
  • the UE detects the PDCCH during the DRX Active Time, and if it detects the PDCCH, it decides whether to start the drx-InactivityTimer according to the drx-InactivityTimer activation/deactivation flag. Assume that the UE detects the PDCCH in DRX Active Time, and the PDCCH schedules new data transmission.
  • a drx-InactivityTimer activation/deactivation MAC CE dynamically indicates whether the terminal device is allowed to start the drx-InactivityTimer within the target time period. For example, if the drx-InactivityTimer activation/deactivation MAC CE is in the deactivated state, it indicates that the terminal device is not allowed to start the drx-InactivityTimer within the target time period, and the drx-InactivityTimer activation/deactivation MAC CE is in the active state. The terminal device is allowed to start drx-InactivityTimer within the target time period.
  • the UE receives a drx-InactivityTimer activation/deactivation MAC CE and indicates that the drx-InactivityTimer is in the deactivated state, the UE detects the PDCCH at the DRX Active Time, and the PDCCH schedules new data transmission, the UE does not start drx-InactivityTimer. If the UE receives a drx-InactivityTimer activation/deactivation MAC CE and indicates that the drx-InactivityTimer is active, the UE detects the PDCCH at the DRX Active Time, and when the PDCCH schedules new data transmission, the UE starts/restarts the drx-InactivityTimer .
  • the terminal device When the terminal device receives the PDCCH, it stops, starts or restarts the deactivation timer through the first indication information and the third indication information.
  • the first indication information is used to instruct the terminal device to stop, start or restart the deactivation timer
  • the third indication information is used to instruct the terminal device to switch the currently used RDX configuration information to The first configuration information or the second configuration information.
  • the UE receives network configuration information and configures at least one set of DRX related parameters.
  • Each set of DRX parameters includes a drx-InactivityTimer and other related DRX parameters, such as drx-onDurationTimer.
  • One set of DRX parameters does not include drx-InactivityTimer, or drx-InactivityTimer is 0.
  • the network device may indicate a specific DRX configuration parameter of the UE through the third indication information, for example, indicate a DRX configuration parameter whose drx-InactivityTimer is 0 or the DRX parameter of drx-InactivityTimer is not configured .
  • the UE detects the PDCCH in the DRX Active Time, and the PDCCH schedules new data transmission, and the UE does not start the drx-InactivityTimer.
  • the size of the sequence number of the foregoing processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not be implemented in this application.
  • the implementation process of the example constitutes any limitation.
  • FIG. 9 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 may include:
  • the communication unit 310 is configured to receive first indication information, where the first indication information is used to instruct the terminal device to stop, start or restart a deactivation timer for discontinuous reception of DRX;
  • the processing unit 320 is configured to stop, start or restart the deactivation timer according to the first indication information when receiving the physical downlink control channel PDCCH.
  • the first indication information is used to schedule new data through the PDCCH to instruct the terminal device to start or restart the deactivation timer, and/or, the first An indication information is used for scheduling retransmission data through the PDCCH to instruct the terminal device to stop the deactivation timer.
  • the first indication information instructs the terminal device to stop, start or restart the deactivation timer through the radio network temporary identifier RNTI adopted by the PDCCH.
  • the downlink control information DCI of the PDCCH includes the first indication information.
  • the communication unit 310 is specifically configured to:
  • the processing unit 320 is specifically configured to:
  • the first indication information is used to instruct the terminal device to start or restart the deactivation timer, start or restart the deactivation timer;
  • the first indication information is used to instruct the terminal device to stop the deactivation timer when the deactivation timer is stopped.
  • the processing unit 320 is specifically configured to:
  • the first indication information is used to instruct the terminal device to stop the deactivation timer when the deactivation timer is stopped.
  • the first indication information is used to instruct the terminal device to stop, start or restart the target deactivation timer in at least one deactivation timer.
  • the target deactivation timer is a default deactivation timer in the at least one deactivation timer.
  • the communication unit 310 is further configured to:
  • Receiving second indication information where the second indication information is used to indicate that the deactivation timer is not started or can be started within the target time period.
  • the processing unit 320 is specifically configured to:
  • the second indication information is used to indicate that the deactivation timer can be started within the target time period, stop and start according to the first indication information and the second indication information Or restart the deactivation timer.
  • the second indication information is further used to instruct the terminal device to start the DRX activation timer, and the target time period includes the terminal device in the DRX receiving all The time period occupied by at least one activation period after the second indication information.
  • the second indication information indicates through a different media access control MAC control unit CE that the deactivation timer is not started or can be started within the target time period.
  • the second indication information indicates, through a wake-up sequence, that the deactivation timer is not started or can be started within the target time period.
  • the second indication information is information sent by the network device to the terminal device through DRX configuration information.
  • the communication unit 310 is further configured to:
  • Receive DRX configuration information where the DRX configuration information includes at least one configuration information corresponding to at least one DRX, and the first configuration information in the at least one configuration information does not include a deactivation timer; or the first configuration information includes deactivation When the timer is used, the deactivation timer is zero.
  • the at least one piece of configuration information includes the first configuration information corresponding to the power saving mode and the second configuration information corresponding to the non-power saving mode.
  • the communication unit 310 is further configured to:
  • the third indication information is information sent by the network device to the terminal device through the downlink control information DCI or the media access control MAC control unit CE.
  • each configuration information of the at least one piece of configuration information includes an activation period timer.
  • the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment.
  • the terminal device 300 shown in FIG. 9 may correspond to the corresponding subject in executing the method 200 of the embodiment of the present application, that is, the foregoing and other operations and/or functions of each unit in the terminal device 300 are used to implement the respective methods in each method. For the sake of brevity, the corresponding process will not be repeated here.
  • Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device 400 may include:
  • the communication unit 410 is configured to:
  • the first indication information is used to schedule new data through the PDCCH to instruct the terminal device to start or restart the deactivation timer, and/or, the first An indication information is used for scheduling retransmission data through the PDCCH to instruct the terminal device to stop the deactivation timer.
  • the first indication information instructs the terminal device to stop, start or restart the deactivation timer through the radio network temporary identifier RNTI adopted by the PDCCH.
  • the downlink control information DCI of the PDCCH includes the first indication information.
  • the communication unit 410 is specifically configured to:
  • the first indication information is used to instruct the terminal device to stop, start or restart the target deactivation timer in at least one deactivation timer.
  • the target deactivation timer is a default deactivation timer in the at least one deactivation timer.
  • the communication unit 410 is further configured to:
  • the second indication information is further used to instruct the terminal device to start the DRX activation timer, and the target time period includes the terminal device in the DRX receiving all The time period occupied by at least one activation period after the second indication information.
  • the second indication information indicates through a different media access control MAC control unit CE that the deactivation timer is not started or can be started within the target time period.
  • the second indication information indicates, through a wake-up sequence, that the deactivation timer is not started or can be started within the target time period.
  • the second indication information is information sent by the network device to the terminal device through DRX configuration information.
  • the communication unit 410 is further configured to:
  • the DRX configuration information includes at least one configuration information corresponding to at least one DRX, and the first configuration information in the at least one configuration information does not include a deactivation timer; or the first configuration information includes deactivation When the timer is used, the deactivation timer is zero.
  • the at least one piece of configuration information includes the first configuration information corresponding to the power saving mode and the second configuration information corresponding to the non-power saving mode.
  • the communication unit 410 is further configured to:
  • Sending third instruction information where the third instruction information is used to instruct the terminal device to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.
  • the third indication information is information sent by the network device to the terminal device through the downlink control information DCI or the media access control MAC control unit CE.
  • each configuration information of the at least one piece of configuration information includes an activation period timer.
  • the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment.
  • the network device 400 shown in FIG. 10 may correspond to the corresponding subject in executing the method 200 of the embodiment of the present application, that is, the foregoing and other operations and/or functions of each unit in the network device 400 are used to implement each method. For the sake of brevity, the corresponding process will not be repeated here.
  • the communication device of the embodiment of the present application is described above from the perspective of functional modules in conjunction with FIG. 9 and FIG. 10. It should be understood that the functional module can be implemented in the form of hardware, can also be implemented in the form of software instructions, or can be implemented in a combination of hardware and software modules.
  • the steps of the method embodiments in the embodiments of the present application can be completed by hardware integrated logic circuits in the processor and/or instructions in the form of software, and the steps of the methods disclosed in the embodiments of the present application can be directly embodied as hardware.
  • the execution of the decoding processor is completed, or the execution is completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the foregoing method embodiments in combination with its hardware.
  • the communication unit 310 shown in FIG. 9 and the communication unit 410 shown in FIG. 10 may be implemented by a transceiver, and the processing unit shown in FIG. 9 may be implemented by a processor.
  • FIG. 11 is a schematic structural diagram of a communication device 500 according to an embodiment of the present application.
  • the communication device 500 shown in FIG. 11 includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 500 may further include a memory 520.
  • the memory 520 may be used to store instruction information, and may also be used to store codes and instructions executed by the processor 510.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 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 530 may include a transmitter and a receiver.
  • the transceiver 530 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 500 may be a terminal device of an embodiment of the application, and the communication device 500 may implement the corresponding process implemented by the terminal device in each method of the embodiment of the application, that is,
  • the communication device 500 may correspond to the terminal device 300 in the embodiment of the present application, and may correspond to a corresponding subject in executing the method 200 according to the embodiment of the present application.
  • details are not described herein again.
  • the communication device 500 may be a network device in an embodiment of the present application, and the communication device 500 may implement corresponding processes implemented by the network device in each method in the embodiments of the present application. That is to say, the communication device 500 in the embodiment of the present application may correspond to the network device 400 in the embodiment of the present application, and may correspond to the corresponding subject in executing the method 200 according to the embodiment of the present application. Repeat.
  • the various components in the communication device 500 are connected by a bus system, where in addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.
  • an embodiment of the present application also provides a chip, which may be an integrated circuit chip with signal processing capability, and can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • Fig. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 600 shown in FIG. 12 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be used to store instruction information, and may also be used to store codes and instructions executed by the processor 610.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the chip 600 may further include an input interface 630.
  • the processor 610 can control the input interface 630 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 600 may further include an output interface 640.
  • the processor 610 can control the output interface 640 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 the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application.
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device in the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal device in the various methods 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, etc. It should also be understood that the various components in the chip 600 are connected by a bus system, where in addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.
  • the processor may include but is not limited to:
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the processor may be used to implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the steps of the method disclosed in the embodiments of the present application may 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 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 storage includes but is not limited to:
  • 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 a 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
  • SLDRAM synchronous link dynamic random access memory
  • DR RAM Direct Rambus RAM
  • memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium stores one or more programs, and the one or more programs include instructions that, when executed by a portable electronic device that includes multiple application programs, can cause the portable electronic device to execute methods 300 to 500 The method of the illustrated embodiment.
  • the computer-readable storage medium may 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 enables 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 a computer program.
  • the computer program product 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 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 product 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 It's concise, so I won't repeat it here.
  • the embodiment of the application also provides a computer program.
  • the computer program When the computer program is executed by a computer, the computer can execute the method of the embodiment shown in method 200.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused 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 embodiment of the present application also provides a communication system.
  • the communication system may include a terminal device 300 as shown in FIG. 9 and a network device 400 as shown in FIG. 10, which is not repeated here for brevity.
  • system in this article may also be referred to as “network management architecture” or “network system”.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence or the parts that contribute to the prior art or the parts of the technical solutions, and the computer software products are stored in a storage medium.
  • Including several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.
  • the division of units or modules or components in the device embodiments described above is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or modules or components can be combined or integrated.
  • To another system, or some units or modules or components can be ignored or not executed.
  • the units/modules/components described as separate/display components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units/modules/components may be selected according to actual needs to achieve the objectives of the embodiments of the present application.

Landscapes

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

Abstract

La présente invention concerne un procédé et un dispositif de communication sans fil, aptes à réduire la consommation d'énergie d'un dispositif terminal. Le procédé comprend les étapes suivantes : un dispositif terminal reçoit des premières informations d'instruction, lesdites premières informations d'instruction étant utilisées pour commander au dispositif terminal d'arrêter, de démarrer, ou de redémarrer un temporisateur de désactivation de réception discontinue (DRX) ; lorsque ledit dispositif terminal reçoit un canal physique de commande de liaison descendante (PDCCH), il arrête, démarre, ou redémarre ledit temporisateur de désactivation d'après lesdites premières informations d'instruction. Dans les modes de réalisation de la présente invention, un dispositif de réseau peut, au moyen des premières informations d'instruction, commander de manière dynamique si le dispositif terminal doit arrêter, démarrer, ou redémarrer le temporisateur de désactivation (drx-InactivityTimer). Cela évite au dispositif terminal de démarrer ou de redémarrer le drx-InactivityTimer à réception du PDCCH et de réduire efficacement la durée nécessaire au dispositif terminal pour détecter le PDCCH à l'aveugle, ce qui réduit la consommation d'énergie du dispositif terminal.
PCT/CN2019/074884 2019-02-12 2019-02-12 Procédé et dispositif de communication sans fil WO2020163998A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/074884 WO2020163998A1 (fr) 2019-02-12 2019-02-12 Procédé et dispositif de communication sans fil
CN201980019293.9A CN111886904A (zh) 2019-02-12 2019-02-12 无线通信的方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074884 WO2020163998A1 (fr) 2019-02-12 2019-02-12 Procédé et dispositif de communication sans fil

Publications (1)

Publication Number Publication Date
WO2020163998A1 true WO2020163998A1 (fr) 2020-08-20

Family

ID=72045187

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074884 WO2020163998A1 (fr) 2019-02-12 2019-02-12 Procédé et dispositif de communication sans fil

Country Status (2)

Country Link
CN (1) CN111886904A (fr)
WO (1) WO2020163998A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022178813A1 (fr) * 2021-02-26 2022-09-01 华为技术有限公司 Procédé et appareil de communication de liaison latérale
WO2024055325A1 (fr) * 2022-09-16 2024-03-21 北京小米移动软件有限公司 Procédé et appareil de configuration de cycle drx, dispositif de communication, et support d'enregistrement

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113038630B (zh) * 2021-03-03 2022-09-06 中国人民解放军海军工程大学 一种基于大数据的信息收集分析方法及系统
CN113691330B (zh) * 2021-08-16 2023-04-18 紫光展锐(重庆)科技有限公司 一种pdcch检测方法及通信装置
CN115767440A (zh) * 2021-09-02 2023-03-07 大唐移动通信设备有限公司 一种信息处理方法、装置及可读存储介质
WO2023115468A1 (fr) * 2021-12-23 2023-06-29 上海移远通信技术股份有限公司 Procédé de communication sans fil et appareil de communication
CN117014109A (zh) * 2022-04-25 2023-11-07 华为技术有限公司 一种通信方法及装置
CN117751684A (zh) * 2022-07-20 2024-03-22 北京小米移动软件有限公司 媒体接入控制mac重置定时器的处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625432A (zh) * 2011-01-28 2012-08-01 华为技术有限公司 一种非连续接收的方法和装置
CN105722195A (zh) * 2011-01-28 2016-06-29 华为技术有限公司 一种非连续接收的方法和装置
CN108476471A (zh) * 2015-11-20 2018-08-31 夏普株式会社 终端装置、通信方法以及集成电路
EP3379894A1 (fr) * 2014-03-11 2018-09-26 LG Electronics Inc. Procédé pour compter un temporisateur drx (à réception discontinue) dans un système d'agrégation de porteuses et dispositif associé
CN109219116A (zh) * 2018-08-09 2019-01-15 华为技术有限公司 一种终端设备的休眠方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625432A (zh) * 2011-01-28 2012-08-01 华为技术有限公司 一种非连续接收的方法和装置
CN105722195A (zh) * 2011-01-28 2016-06-29 华为技术有限公司 一种非连续接收的方法和装置
EP3379894A1 (fr) * 2014-03-11 2018-09-26 LG Electronics Inc. Procédé pour compter un temporisateur drx (à réception discontinue) dans un système d'agrégation de porteuses et dispositif associé
CN108476471A (zh) * 2015-11-20 2018-08-31 夏普株式会社 终端装置、通信方法以及集成电路
CN109219116A (zh) * 2018-08-09 2019-01-15 华为技术有限公司 一种终端设备的休眠方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022178813A1 (fr) * 2021-02-26 2022-09-01 华为技术有限公司 Procédé et appareil de communication de liaison latérale
WO2024055325A1 (fr) * 2022-09-16 2024-03-21 北京小米移动软件有限公司 Procédé et appareil de configuration de cycle drx, dispositif de communication, et support d'enregistrement

Also Published As

Publication number Publication date
CN111886904A (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
WO2020163998A1 (fr) Procédé et dispositif de communication sans fil
WO2020200075A1 (fr) Procédé et appareil de communication
TWI821368B (zh) 非連續傳輸的方法和設備
US20220104134A1 (en) Method for wus monitoring and terminal device
CN114271021B (zh) 用于确定非连续接收持续定时器的启动状态的方法及设备
WO2021120013A1 (fr) Procédé de surveillance d'un signal de réveil, dispositif terminal et dispositif de réseau
WO2020019756A1 (fr) Procédé et appareil de détermination de ressource de transmission, et dispositif terminal
US20220039013A1 (en) Method and device for discontinuous reception
WO2020237594A1 (fr) Procédé et appareil de gestion de bwp et terminal
CN114270917B (zh) 一种drx配置方法及装置、终端设备、网络设备
WO2020001123A1 (fr) Appareil et procédé de détection de canal de commande de liaison descendante, et dispositif terminal
WO2021088017A1 (fr) Procédé de détermination de type d'informations de commande de liaison descendante, et appareil
WO2021092861A1 (fr) Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
US20220060985A1 (en) Method for detecting control channel and terminal device
WO2020077667A1 (fr) Procédé et dispositif d'activation de temporisateur, et terminal
WO2022006879A1 (fr) Procédé de transmission d'indication de radiomessagerie, dispositif électronique et support d'enregistrement
US20230199716A1 (en) Wireless communication method, and terminal and network device
US20230199714A1 (en) Information indication method and apparatus, terminal device and network device
WO2020061954A1 (fr) Procédé pour distinguer un message de radiomessagerie, dispositif de réseau et dispositif terminal
WO2020186467A1 (fr) Procédé et appareil pour réception discontinue sur spectre sans licence
WO2021142700A1 (fr) Procédé et appareil de mesure, et dispositif terminal
WO2021168814A1 (fr) Procédé et appareil de détermination de canal de commande, et support de stockage et processeur
WO2020124548A1 (fr) Procédé et appareil permettant de déterminer une ressource temps-fréquence, puce et programme informatique
TW202002558A (zh) 一種頻寬部分的啟動與配置方法及終端設備
WO2022126482A1 (fr) Procédé de détection de canal de commande, dispositif électronique, et support de stockage

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

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

Country of ref document: EP

Kind code of ref document: A1