CN111886904A

CN111886904A - Method and apparatus for wireless communication

Info

Publication number: CN111886904A
Application number: CN201980019293.9A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-02-12
Filing date: 2019-02-12
Publication date: 2020-11-03
Also published as: WO2020163998A1

Abstract

A method and apparatus for wireless communication are provided, which can reduce power consumption of a terminal device. The method comprises the following steps: the terminal equipment receives first indication information, wherein the first indication information is used for indicating the terminal equipment to stop, start or restart a deactivation timer of Discontinuous Reception (DRX); and when the terminal equipment receives a Physical Downlink Control Channel (PDCCH), stopping, starting or restarting the deactivation timer according to the first indication information. In the embodiment of the application, the network device may dynamically indicate, through the first indication information, whether the terminal device needs to stop, start, or restart a deactivation timer (drx-inactivity timer), so that the terminal device is prevented from starting or restarting the drx-inactivity timer upon receiving the PDCCH, the time for the terminal device to blindly detect the PDCCH can be effectively reduced, and the power consumption of the terminal device is further reduced.

Description

Method and apparatus for wireless communication

Technical Field

The embodiments of the present application relate to the field of communications, and more particularly, to a method and apparatus for wireless communication.

Background

The data stream is typically bursty, with the terminal device having data to transmit for a period of time, but not for the next longer period of time. Therefore, if the terminal device always performs blind detection on a Physical Downlink Control Channel (PDCCH), power consumption of the terminal device may be excessive.

In order to solve the above problem, a concept of Discontinuous Reception (DRX) is proposed in Long Term Evolution (LTE). Specifically, when the terminal device has no data transmission, the power consumption can be reduced by stopping receiving a Physical Downlink Control Channel (PDCCH) (at this time, PDCCH blind detection is stopped), so as to improve the battery service time. The network device configures a DRX cycle (cycle) for the terminal device in a Radio Resource Control (RRC _ CONNECTED) state. The DRX cycle consists of an active period (On Duration) and a dormant period (Opportunity for DRX), and the terminal equipment monitors and receives the PDCCH within the On Duration; during Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption.

In the NR protocol, the duration of the active period may be controlled by an activation timer (DRX-onDurationTimer) for DRX and a deactivation timer (DRX-inactivity timer) for DRX. That is, the terminal device starts the drx inactivity timer when receiving the PDCCH, so that the On Duration time is extended along with the start of the drx On Duration timer. However, each time the PDCCH is received, the drx-inactivity timer needs to be restarted, which results in that the terminal device prolongs the time for blind detection of the PDCCH, thereby increasing power consumption. In addition, because the drx-inactivity timer is configured by the network device in advance, the arrival characteristics of the service cannot be well matched. For example, it is assumed that the network is configured with a specific value in advance, for example, 10ms, but since the arrival of the service is predetermined, this may cause frequent restart of drx-inactivity timer due to scheduling of the service, so that the terminal cannot enter into the sleep period, further increasing the power consumption of the terminal device.

Disclosure of Invention

A method and apparatus for wireless communication are provided, which can reduce power consumption of a terminal device.

In a first aspect, a method of wireless communication is provided, including:

the terminal equipment receives first indication information, wherein the first indication information is used for indicating the terminal equipment to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and when the terminal equipment receives a Physical Downlink Control Channel (PDCCH), stopping, starting or restarting the deactivation timer according to the first indication information.

In a second aspect, a method of wireless communication is provided, including:

the network equipment sends first indication information, wherein the first indication information is used for indicating the terminal equipment to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and the network equipment sends a physical downlink control channel PDCCH.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof. Specifically, the terminal device includes a functional module configured to execute the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided for performing the method of the second aspect or its implementation manners. In particular, the network device comprises functional modules for performing the methods of the second aspect or its implementations.

In a fifth aspect, a terminal device is provided that includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method in the first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method of the second aspect or each implementation manner thereof.

In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or its implementation manners. Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device in which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manners thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.

A tenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Based on the above technical solution, the network device may dynamically indicate, through the first indication information, whether the terminal device needs to stop, start, or restart a deactivation timer (drx-inactivity timer). That is, if the network device considers that the terminal device is not scheduled any more in the next period of time after the PDCCH scheduling data is currently sent, the network device may dynamically cause the terminal device to stop drx-inactivity timer, so as to avoid that the terminal device starts or restarts drx-inactivity timer upon receiving the PDCCH, thereby effectively reducing the time for the terminal device to blindly detect the PDCCH, and further reducing the power consumption of the terminal device.

Drawings

Fig. 1 is an example of an application scenario of the present 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 activating and deactivating timer according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of a wireless communication method according to an embodiment of the present application.

Fig. 5 to 8 are schematic diagrams of the terminal device stopping, starting, or restarting the deactivation timer 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 of an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication device of an embodiment of the present application.

Fig. 12 is a schematic block diagram of a chip of an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air. Multi-service transport is supported between terminal device 110 and network device 120.

It should be understood that the embodiment of the present application is only illustrated as the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solution of the embodiment of the present application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, a Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, a New Radio (NR), a future 5G System, or the like.

Taking a 5G system as an example, the technical scheme of the embodiment of the present application may be applied to a Long Term Evolution (LTE) coverage of a wide area and an islanding coverage mode of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early LTE investment of a mobile operator, a work mode of tight connection (light interworking) between LTE and NR is provided.

The main application scenarios of 5G include: enhanced Mobile Ultra wide band (eMBB), Low-Latency and high-reliability Communication (URLLC), and massive machine type Communication (mMTC). Among them, the eMBB aims at users to obtain multimedia contents, services and data, and its demand is rapidly increasing. As the eMBB may be deployed in different scenarios. For example, indoor, urban, rural, etc. have relatively large differences in capabilities and needs, so that they cannot be analyzed in general and can be combined with detailed analysis of specific deployment scenarios. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety, and the like. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost and long service life of the module, etc.

In addition, since the complete 5G NR coverage is difficult to obtain, the network coverage of the embodiment of the present application may adopt a Long Term Evolution (LTE) coverage of a wide area and an islanding coverage mode of NR. Meanwhile, in order to protect the mobile operator from LTE investment in the early stage, a tight connection (light interworking) working mode between LTE and NR may be further adopted.

In particular, the technical solution of the embodiment of the present application may be applied to various communication systems based on non-orthogonal Multiple Access technologies, for example, a Sparse Code Multiple Access (SCMA) system, a Low Density Signature (LDS) system, and the like, and of course, the SCMA system and the LDS system may also be called other names in the communication field; further, the technical solution of the embodiment of the present application may be applied to a Multi-Carrier transmission system using a non-Orthogonal multiple access technology, for example, an Orthogonal Frequency Division Multiplexing (OFDM) using a non-Orthogonal multiple access technology, a Filter Bank Multi-Carrier (FBMC), a General Frequency Division Multiplexing (GFDM), a Filtered Orthogonal Frequency Division Multiplexing (F-OFDM) system, and the like.

In communication system 100 shown in fig. 1, network device 120 may be an access network device that communicates with terminal device 110. An access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

Alternatively, the network device 120 may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, or may be a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, and the network device 120 may also be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) System. Alternatively, the Network device 120 may also be a Next Generation Radio Access Network (NG RAN), or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Access Network device may be a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

Alternatively, the terminal device 110 may be any terminal device, including but not limited to: via a wireline connection, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Optionally, terminal-to-Device (D2D) communication may be performed between terminal devices 110.

Fig. 1 illustrates a network device and a terminal device, and optionally, the communication system 100 may include a plurality of network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited to the implementation of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited thereto in the embodiments of the present application.

Optionally, the Uplink Channel in the embodiment of the present application may include a Physical Random Access Channel (PRACH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and the like. The uplink Reference Signal may include an uplink Demodulation Reference Signal (DMRS), a Sounding Reference Signal (SRS), a phase tracking Reference Signal (PT-RS), and the like. The uplink DMRS can be used for demodulation of an uplink channel, the SRS can be used for measurement, uplink time-frequency synchronization or phase tracking of the uplink channel, and the PT-RS can also be used for measurement, uplink time-frequency synchronization or phase tracking of the uplink channel. It should be understood that, in the embodiment of the present application, an uplink physical channel or an uplink reference signal with the same name and different function as the above may be included, and an uplink physical channel or an uplink reference signal with the same name and different function as the above may also be included, which is not limited in the present application.

It should be understood that, in the embodiments of the present application, devices having a communication function in a network/system may be referred to as communication devices. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 120 and a terminal device 110 having a communication function, and the network device 120 and the terminal device 110 may be the devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In the communication framework shown in fig. 1, a packet-based data stream may be transmitted between end device 110 and network device 120, however, a packet-based data stream is typically bursty.

In other words, terminal device 110 has data transmitted for a period of time, but has no data transmitted for a subsequent longer period of time. Thus, if the terminal device 110 always performs blind detection on a Physical Downlink Control Channel (PDCCH), power consumption of the terminal device may be excessive.

In Long Term Evolution (LTE), a concept of Discontinuous Reception (DRX) is proposed. Specifically, the main idea of DRX is: the network can configure the terminal to wake up (DRX ON) at a time predicted by the network, and the terminal monitors a downlink control channel; meanwhile, the network can also configure the terminal to sleep (DRX OFF) at a time predicted by the network, that is, the terminal device does not need to monitor the downlink control channel. Thus, if network device 120 has data to transmit to terminal device 110, network device 120 may schedule terminal device 110 during the time terminal device 110 is DRX ON, and during DRC OFF, terminal power consumption may be reduced due to radio frequency OFF.

Specifically, a Media Access Control (MAC) entity (entity) configures a DRX function by a Radio Resource Control (RRC) for controlling a behavior of a terminal monitoring a PDCCH.

For example, as shown in fig. 2, the DRX cycle configured by the network device for the terminal device is composed of an active period (On Duration) and a dormant period (Opportunity for DRX), and in an RRC CONNECTED (RRC CONNECTED) mode, if the terminal device is configured with a DRX function, the MAC entity may monitor and receive a PDCCH during the On Duration; during Opportunity for DRX time, the terminal device does not receive the PDCCH to reduce power consumption.

It should be understood that the terminal device in the sleep period in the embodiment of the present application does not receive the PDCCH, but may receive data from other physical channels. For example, the terminal device may receive a Physical Downlink Shared Channel (PDSCH), an acknowledgement/non-acknowledgement (ACK/NACK), and the like. For another example, in Semi-Persistent Scheduling (SPS), the terminal device may receive PDSCH data configured periodically.

The duration of the active period may be controlled by a DRX-on duration timer (DRX-on duration timer) and a DRX deactivation timer (DRX-inactivity timer). Wherein the DRX-active period timer is also referred to as DRX-active phase timer. The deactivation timer is also referred to as an inactivity timer. Specifically, the active period ends when the DRX-on duration timer (DRX-on duration timer) expires. The terminal equipment prolongs the duration of the activation period by starting the drx-InactivityTimer.

As shown in fig. 3, the terminal device starts a drx-inactivity timer when receiving the PDCCH, and thus the On Duration time is extended along with the start of the drx-On Duration timer. It should be understood that in the framework shown in fig. 3, the terminal device may restart drx-inactivytytytimer when it receives PDCCH and has currently started drx-inactivytimer.

It can be seen that, each time the PDCCH is received, DRX-inactivity timer of DRX needs to be restarted, which results in that the terminal device prolongs the time for blind detection of the PDCCH, thereby increasing power consumption. In addition, because the drx-inactivity timer is configured by the network device in advance, the arrival characteristics of the service cannot be well matched. For example, it is assumed that the network is configured with a specific value in advance, for example, 10ms, but since the arrival of the service is predetermined, this may cause frequent restart of drx-inactivity timer due to scheduling of the service, so that the terminal cannot enter into the sleep period, further increasing the power consumption of the terminal device.

Therefore, 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 flow chart diagram of managing timers in an embodiment of the invention. Fig. 4 shows a schematic flow chart of a method 200 of wireless communication according to an embodiment of the application, which method 200 may be performed interactively by a terminal device and a network device. The terminal device shown in fig. 4 may be a terminal device as shown in fig. 1, and the network device shown in fig. 4 may be an access network device as shown in fig. 1. The method 200 includes some or all of the following:

as shown in fig. 4, the method 200 includes:

s210, the network device generates first indication information, wherein the first indication information is used for indicating the terminal device to stop, start or restart a deactivation timer of Discontinuous Reception (DRX).

S220, the network device sends the first indication information to the terminal device.

And S230, when the terminal equipment receives a Physical Downlink Control Channel (PDCCH), stopping, starting or restarting the deactivation timer according to the first indication information.

That is, the network device may dynamically indicate whether the terminal device needs to stop, start, or restart a deactivation timer (drx-inactivity timer) through the first indication information.

That is, if the network device considers that the terminal device is not scheduled any more in the next period of time after the PDCCH scheduling data is currently sent, the network device may dynamically cause the terminal device to stop drx-inactivity timer, so as to avoid that the terminal device starts or restarts drx-inactivity timer upon receiving the PDCCH, thereby effectively reducing the time for the terminal device to blindly detect the PDCCH, and further reducing the power consumption of the terminal device.

It should be understood that the method for managing timers provided in the embodiments of the present application may be applied to a terminal device operating in an unlicensed frequency band, the terminal device being configured with a DRX cycle and a deactivation timer. It should also be appreciated that in other alternative embodiments, the deactivation timer may also be replaced with a downlink retransmission timer for DRX (DRX-retransmission timer dl) or an uplink retransmission timer for DRX (DRX-retransmission timer ul).

The first embodiment is as follows:

and when the terminal equipment receives the PDCCH, stopping, starting or restarting the deactivation timer only through the first indication information.

The UE receives network configuration information, configures DRX related parameters, which may include at least one DRX-inactivity timer, and other DRX related parameters, such as DRX-onDurationTimer. And the UE detects the PDCCH during the DRX Active Time, and if the PDCCH is detected, whether a DRX-InactivetyTimer is started or not is determined according to the first indication information.

For example, when the PDCCH is used to schedule newly transmitted data (that is, when the PDCCH is used to schedule downlink newly transmitted data or uplink newly transmitted data), the terminal device starts a drx-inactivytytytimer, and when the PDCCH is used to schedule retransmission data, the terminal device does not start the drx-inactivytytimer.

For another example, the DCI carried by the PDCCH carries an indication field, and the first indication information is carried in the indication field and used for dynamically indicating whether to start drx-inactivity timer. For example, if the indication field is 1, drx-inactivytytytimer is activated, and if the indication field is 0, drx-inactivytimer is not activated. For another example, if the instruction field is 0, drx-inactivytytimer is activated, and if the instruction field is 1, drx-inactivytimer is not activated.

Also for example, whether a drx-InactivetyTimer needs to be started may be dynamically indicated by a MAC CE. For example, the MAC CE includes the first indication information.

Optionally, if the terminal device receives the PDCCH, drx-inactivytytytimer may be started or not started.

For example, assuming that the UE does not default to start drx-inactivity timer when receiving the PDCCH (that schedules newly transmitted data), when the UE receives the MAC CE carrying the first indication information, and the first indication information is used to indicate that drx-inactivity timer needs to be started, the UE starts drx-inactivity timer.

For another example, assume that the UE defaults to start/restart the drx-inactivity timer when receiving the PDCCH (that schedules new data transmission), and when the UE receives the MAC CE carrying the first indication information and the first indication information is used to indicate that the drx-inactivity timer needs to be stopped, the UE stops drx-inactivity timer.

Taking the example that the first indication information indicates to stop, start or restart the deactivation timer through the data type used for scheduling by the PDCCH, if the UE detects the PDCCH in DRX Active Time and the PDCCH indicates that DRX-InactivityTimer is not started, the UE does not start DRX-InactivityTimer. If the PDCCH is detected in the DRX Active Time and the PDCCH indicates that the DRX-InactivationTimer is started, the UE starts the DRX-InactivationTimer according to the preconfigured DRX-InactivationTimer.

Taking the first indication information indicating whether to start drx-inactivity timer through PDCCH as an example, the following describes the technical solution of the embodiment of the present application with reference to fig. 5.

Fig. 5 is a schematic diagram of an activation and deactivation timer according to an embodiment of the present application.

As shown in fig. 5, the UE starts a DRX-onDurationTimer at a specific location according to the RRC-configured DRX parameter information. The DRX Active Time is a DRX Active Time, and the Time of the DRX Active Time may depend on at least the Time of the DRX on duration timer and/or the Time of the DRX in duration timer. During this time, the UE detects the PDCCH. If the UE receives the PDCCH and the PDCCH indicates that the drx-InactivatyTimer is not started, the UE does not start the drx-InactivatyTimer; if the UE receives the PDCCH and the PDCCH indicates that the drx-inactivity timer is started, the UE starts the drx-inactivity timer, namely the Active Time is correspondingly prolonged, and the UE continues to detect the PDCCH in the period of Time.

It should be understood that fig. 5 is only an example of an embodiment of the present application and should not be construed as limiting the present application.

For example, in addition to indicating whether to activate drx-inactivytytimer through PDCCH, whether to activate drx-inactivytimer may be dynamically indicated through a certain sequence, such as wake-up signal (wake-up signal). For example, in the above embodiment, when the UE detects the PDCCH, the UE starts the drx-inactivity timer, and the network may then send a wake-up signal to dynamically stop the drx-inactivity timer.

For another example, in addition to dynamically indicating whether to start drx-inactivytytimer by adding an indication field to DCI carried by a PDCCH, whether to start drx-inactivytimer may be dynamically indicated by scrambling the PDCCH with a different RNTI. For example, a PDCCH scrambled with a C-RNTI indicates that drx-inactivytytimer is activated, and a PDCCH scrambled with a new RNTI indicates that drx-inactivytimer is not activated.

Example two:

and when the terminal equipment receives the PDCCH, stopping, starting or restarting a target deactivation timer in the at least one deactivation timer through the first indication information.

The UE receives network configuration information, configures DRX related parameters including at least one DRX-inactivity timer, and other DRX related parameters such as DRX-onDurationTimer. The UE detects the PDCCH during the DRX Active Time, and if the PDCCH is detected, the starting/non-starting of DRX-InactivetyTimer is determined according to the indication of the first indication information; if the first indication information indicates that a drx-inactivytytytimer is started, a certain drx-inactivytimer which is configured to be started can be further indicated by the first indication information.

Or, the first indication information is only used for indicating the drx-inactivytytimer which the UE needs to start, that is, the UE determines to start one drx-inactivytimer of the configuration according to the indication of the first indication information. When the value of the drx-inactivytytytimer which needs to be started and is selected by the network is 0, the method is equivalent to indicating that the UE does not start the drx-inactivytimer.

In the embodiment of the application, the network can select from multiple configured DRX-inactivity timers, so that the characteristics of the service can be better matched to a certain extent, the situation that the network can only configure one DRX-inactivity timer value is avoided, the DRX activation time of the UE can be more accurately adjusted, and the power saving effect is achieved.

For example, when the PDCCH is used to schedule newly transmitted data (that is, when the PDCCH is used to schedule downlink newly transmitted data or uplink newly transmitted data), the terminal device starts a drx-inactivity timer and specifically indicates which drx-inactivity timer of the at least one drx-inactivity timer is started, and when the PDCCH is used to schedule retransmission data, the drx-inactivity timer is not started.

For another example, the DCI carried by the PDCCH carries an indication field, and the first indication information is carried in the indication field and used for dynamically indicating whether to start a drx-inactivytytimer and/or which drx-inactivytimer to start. For example, when the indication field is 001, a first drx-inactivytytytimer is started, when the indication field is 010, a second drx-inactivytimer is started, when the indication field is 100, a third drx-inactivytimer is started, and when the indication field is 000, a drx-inactivytimer is not started. Or starting a third drx-inactivytytytimer when the indication field is 000, wherein the value of the third drx-inactivytimer is 0.

Also for example, whether drx-inactivity timer needs to be started, and/or which timer to start, may be dynamically indicated by a MAC CE. Optionally, in an implementation, it is assumed that the UE does not start drx-inactivity timer by default when receiving a PDCCH (that schedules new data transmission), when the UE receives a MAC CE, the MAC CE indicates whether drx-inactivity timer needs to be started, and if so, which drx-inactivity timer is specifically started. Optionally, in another implementation, it is assumed that the UE starts/restarts drx-inactivity timer by default when receiving PDCCH (which schedules new data transmission), and stops drx-inactivity timer when the UE receives MAC CE indicating that drx-inactivity timer needs to be stopped.

That is, when the UE detects a PDCCH in DRX Active Time, if the first indication information indicates that DRX-inactivity timer is not started, the UE does not start DRX-inactivity timer, and if the first indication information indicates that DRX-inactivity timer is started, the first indication information may further indicate which configured DRX-inactivity timer the UE starts. When the value of the drx-inactivity timer which is started by the first indication information is 0, the first indication information is equivalent to indicating that the UE does not start the drx-inactivity timer. The Time of DRX Active Time may depend at least on the Time during which the DRX on duration timer is running and/or the Time during which the DRX on duration timer is running.

For example, the RRC configured DRX parameters are as follows:

the network device may configure 2 DRX-inactivity timers, each with a different value, in the DRX configuration information for the UE. Say one is 10ms and one is 2 ms. The first indication information may be dynamically switched to different drx-inactivytytytimers through DCI. Further, the network may also configure more DRX-inactivity timers in the DRX configured by the UE, for example, there may be one DRX-inactivity timer with a value of 0, and if the DCI switching DRX-inactivity timer is a timer with a configuration value equal to 0, it means that the DRX-inactivity timer is not started.

Taking the first indication information indicating whether to start drx-inactivity timer through PDCCH as an example, the following describes the technical solution of the embodiment of the present application with reference to fig. 6.

Fig. 6 is a schematic diagram of an activation and deactivation timer according to an embodiment of the present application.

As shown in fig. 6, during the first and third drx on duration timers, the UE detects 1 PDCCH indicating that drx-inactivytytimer is not started or indicating that drx-inactivytytimer with a value of 0 is started. During the second drx onDuration timer, the UE detects 2 PDCCHs, of which the first indication starts the first deactivation timer (drx-inactivetytimer-Opt 1), and the second PDCCH indication starts the second deactivation timer (drx-inactivetytimer-Opt 2), which may be pre-configured by the network and have different lengths. Therefore, the network can dynamically change the UE to prolong the Time of Active Time, so that the arrival attribute of the service can be more adapted to a certain extent, and the effect of energy saving is achieved.

Of course, as with the embodiment, the PDCCH may be replaced by a wake-up signal or other sequence-based (sequence) signal.

It should be understood that in the embodiment of the present application, different drx-inactivity timers may correspond to different power saving modes.

TABLE 1 corresponding relationship table of drx-InactivityTimer and mode

As shown in table 1, the first deactivation timer (drx-inactivytimeter-Opt 1) corresponds to the non-power saving mode, and the second deactivation timer (drx-inactivytimeter-Opt 2) corresponds to the power saving mode. Specifically, the configuration parameters corresponding to the drx-inactivytytimeter-Opt 1 aim to improve throughput or reduce delay, and the configuration parameters corresponding to the drx-inactivytimeter-Opt 2 aim to save power.

As shown in fig. 7, during the first and third drx on duration timers, the UE detects 1 PDCCH indicating that drx-inactivytytimer is not started or indicating that drx-inactivytytimer with a value of 0 is started. During the second drx on duration timer, the UE detects 2 PDCCHs, where the first indication starts drx on duration timer Opt1, and the UE adopts the parameter corresponding to power saving mode 1. And the second PDCCH indicates that drx-InactivetyTimer-Opt 2 is started, and the UE adopts the parameter corresponding to power saving mode 2. Both timers are pre-configured by the network, and their corresponding power saving mode parameters are also pre-configured by the network. The method has the advantages that the network can dynamically change the UE to prolong the Time of Active Time and different Active Time, and the UE can adopt different power saving modes to be more adaptive to the arrival attribute of the service to a certain extent, so that the effect of saving energy is achieved.

The UE receives the PDCCH, and the PDCCH dynamically indicates whether the UE needs to start the drx-inactivity timer or not, and further indicates which drx-inactivity timer the UE starts.

For example, the DCI carried by the PDCCH carries an indication field to dynamically indicate whether the UE needs to start a drx-inactivity timer, and further, to indicate which drx-inactivity timer the UE starts; if drx-InactivatyTimer-Opt 1 is started, the corresponding mode will also take effect.

For another example, a MAC CE may dynamically indicate whether the UE needs to start a drx-inactivity timer, and further, indicate which drx-inactivity timer the UE starts. For this implementation, optionally, assuming that the UE does not start drx-inactivity timer by default when receiving a PDCCH (that schedules new data transmission), the corresponding configuration mode will also take effect only when the UE receives a MAC CE indicating that drx-inactivity timer is started, for example, when the UE receives a MAC CE indicating that drx-inactivity timer-Opt1 is started. Suppose that the UE defaults to start/restart the drx-inactivity timer when receiving the PDCCH (which schedules new data), and stops the drx-inactivity timer when receiving the MAC CE indicating that the drx-inactivity timer needs to be stopped.

Example three:

and when the terminal equipment receives the PDCCH, stopping, starting or restarting the deactivation timer through the first indication information and the second indication information. The first indication information is used for indicating the terminal equipment to stop, start or restart the deactivation timer, and the second indication information is used for indicating whether the terminal equipment can start the deactivation timer within a target time period.

The UE receives network configuration information, configures DRX related parameters including at least one DRX-inactivity timer, and other DRX related parameters such as DRX-onDurationTimer. The UE monitors the second indication information before starting the drx-OnDurationTimer, where the second indication information may indicate whether or not it is possible or allowable to start the drx-inactivity timer within the target time period. Wherein the target time period may be a time that drx-onDurationTimer runs or a time that several drx-onDurationTimer runs.

Taking the target time period as a drx-onDurationTimer period after the terminal device receives the second indication information as an example, when the UE monitors the second indication information before drx-onDurationTimer starts, if the second indication information indicates that drx-InactivityTimer is not allowed to start in a next drx-onDurationTimer period, the drx-InactivityTimer is not started even if the UE detects the first indication information indicating that drx-InactivityTimer is started in a drx-onDurationTimer running period; if the second indication information indicates that the next drx-onDurationTimer period allows the drx-inactivity timer to be started, the UE starts the drx-inactivity timer when detecting the first indication information indicating the start of the drx-inactivity timer during the drx-onDurationTimer operation period.

In the embodiment of the present application, before the UE enters Active Time, the UE may first detect the second indication information, and at the same Time, the second indication information may indicate whether to start drx-inactivity timer and whether to start drx-onduration timer, which may bring a power saving effect to a certain extent better than embodiments one and two.

Taking the second indication information as a wake-up (wake-up) signal and the first indication information as a PDCCH as an example, the following describes an embodiment of the present application with reference to fig. 7. Wherein 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 start an activation timer.

Fig. 8 is a schematic diagram of an activate-deactivate timer of an embodiment of the present application.

As shown in fig. 8, the UE detects the wake-up signal in the time domain for a time window before the drx onDurationTimer.

A UE detects a wake-up signal for a Time window before the first drx on duration timer and the wake-up signal indicates that the terminal drx on duration timer needs to be started, while indicating that the terminal drx inactive timer is not working during Active Time. The UE does not start drx-inactivtytimer even if it receives PDCCH scheduling newly transmitted data.

The UE detects a wake-up signal for a Time window before the second drx on duration timer and the wake-up signal indicates that the terminal drx on duration timer needs to start, while indicating that the terminal drx inactive timer is operational during Active Time. The UE needs to start drx-inactivtytimer if it receives PDCCH scheduling newly transmitted data.

Detecting a wake-up signal by the UE for a time window before the third drx-onDurationTimer, and if the wake-up signal indicates that the terminal device drx-onDurationTimer does not need to start, the terminal device does not start drx-onDurationTimer.

It should be understood that fig. 8 is only an example of the present application and should not be construed as limiting the present application.

For example, in other alternative embodiments, whether the terminal device is allowed to start the drx-inactivytytytimer within the target time period is dynamically indicated by defining a drx-inactivytimer activation/deactivation flag. For example, if the activation/deactivation flag of drx-inactivytytimer is in a deactivated state, the terminal device is instructed not to allow the drx-inactivytimer to be started within the target time period, and if the activation/deactivation flag of drx-inactivytimer is in an activated state, the terminal device is instructed to allow the drx-inactivytimer to be started within the target time period.

Specifically, the UE receives network configuration information, configures DRX related parameters, which include a DRX-inactivity timer and a DRX-inactivity timer activation/deactivation flag, and other DRX related parameters, such as DRX-onDurationTimer. And the UE detects the PDCCH during the DRX Active Time, and if the PDCCH is detected, whether to start the DRX-InactivetyTimer is determined according to the activation/deactivation indication of the DRX-InactivetyTimer. Suppose the UE detects PDCCH at DRX Active Time and the PDCCH schedules new data. If the activation/deactivation mark of the configured drx-InactivityTimer is in an activation state, starting/restarting the drx-InactivityTimer; if the activation/deactivation mark of the configured drx-InactivityTimer is in a deactivation state, the drx-InactivityTimer is not started;

for another example, in other alternative embodiments, the terminal device is dynamically instructed whether to allow the drx-inactivytytytimer to be started within the target time period by defining a drx-inactivytimer activation/deactivation MAC CE. For example, if drx-inactivytytimer activation/deactivation MAC CE is in a deactivated state, the terminal device is instructed not to allow drx-inactivytimer activation/deactivation MAC CE to be in an activated state in a target time period, and if drx-inactivytimer activation/deactivation MAC CE is in an activated state, the terminal device is instructed not to allow drx-inactivytimer activation in the target time period.

Specifically, if the UE receives a DRX-inactivity timer activation/deactivation MAC CE and indicates that the DRX-inactivity timer is in a deactivated state, the UE detects a PDCCH in DRX Active Time and does not start the DRX-inactivity timer when the PDCCH schedules newly transmitted data. If the UE receives a DRX-inactivity timer to activate/deactivate the MAC CE and indicates that the DRX-inactivity timer is in an activated state, the UE detects the PDCCH in the DRX Active Time and starts/restarts the DRX-inactivity timer when the PDCCH schedules newly transmitted data.

Example four:

and when the terminal equipment receives the PDCCH, stopping, starting or restarting the deactivation timer through the first indication information and the third indication information. Wherein the first indication information is used for indicating the terminal device to stop, start or restart the deactivation timer, and the third indication information is used for indicating the terminal device to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.

The UE receives the network configuration information and configures at least one DRX set of related parameters, where each DRX set of related parameters includes a DRX-inactivity timer and other related DRX parameters, such as DRX-onDurationTimer. One set of DRX parameters does not contain DRX-InactivetyTimer, or DRX-InactivetyTimer is 0.

In this embodiment of the application, the network device may indicate, by using the third indication information, a certain specific DRX configuration parameter of the UE, for example, indicate a DRX configuration parameter whose DRX-inactivity timer is 0 or is not configured with a DRX parameter of DRX-inactivity timer. Under such DRX configuration parameters, the UE detects the PDCCH at DRX Active Time, and the PDCCH schedules newly transmitted data, and the UE does not start DRX-inactivity timer.

The preferred embodiments of the present application have been described in detail with reference to the accompanying drawings, however, the present application is not limited to the details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the technical idea of the present application, and these simple modifications are all within the protection scope of the present application.

For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and various combinations that may be possible are not described in this application in order to avoid unnecessary repetition.

For example, various embodiments of the present application may be arbitrarily combined with each other, and the same should be considered as the disclosure of the present application as long as the concept of the present application is not violated.

It should be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Method embodiments of the present application are described in detail above with reference to fig. 1-8, and apparatus embodiments of the present application are described in detail below with reference to fig. 9-12.

Fig. 9 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application.

Specifically, as shown in fig. 9, the terminal device 300 may include:

a communication unit 310, configured to receive first indication information, where the first indication information is used to indicate that the terminal device stops, starts, or restarts a deactivation timer of Discontinuous Reception (DRX);

a processing unit 320, configured to stop, start, or restart the deactivation timer according to the first indication information when receiving a physical downlink control channel PDCCH.

Optionally, in some embodiments of the present application, the first indication information is used for scheduling new data through the PDCCH to indicate the terminal device to start or restart the deactivation timer, and/or the first indication information is used for scheduling retransmission data through the PDCCH to indicate the terminal device to stop the deactivation timer.

Optionally, in some embodiments of the present application, the first indication information indicates, through a radio network temporary identifier RNTI adopted by the PDCCH, that the terminal device stops, starts, or restarts the deactivation timer.

Optionally, in some embodiments of the present application, the downlink control information DCI of the PDCCH includes the first indication information.

Optionally, in some embodiments of the present application, the communication unit 310 is specifically configured to:

receiving a media access control, MAC, control element, CE, the MAC CE including the first indication information.

Optionally, in some embodiments of the present application, the processing unit 320 is specifically configured to:

receiving the PDCCH, wherein the first indication information is used for indicating the terminal equipment to start or restart the deactivation timer, and starting or restarting the deactivation timer;

the first indication information is used for indicating the terminal equipment to stop the deactivation timer, and then stopping the deactivation timer.

starting or restarting the deactivation timer upon receiving the PDCCH;

Optionally, in some embodiments of the present application, the first indication information is used to instruct the terminal device to stop, start or restart a target deactivation timer of at least one deactivation timer.

Optionally, in some embodiments of the present application, the target deactivation timer is a default deactivation timer of the at least one deactivation timer.

Optionally, in some embodiments of the present application, the communication unit 310 is further configured to:

receiving second indication information indicating that the deactivation timer is not activated or may be activated for a target time period.

and when the PDCCH is received and the second indication information is used for indicating that the deactivation timer can be started in the target time period, stopping, starting or restarting the deactivation timer according to the first indication information and the second indication information.

Optionally, in some embodiments of the present application, the second indication information is further used to indicate the terminal device to start an activation timer of DRX, where the target time period includes a time period occupied by at least one activation period after the terminal device receives the second indication information in DRX.

Optionally, in some embodiments of the present application, the second indication information indicates, by a different media access control MAC control element CE, that the deactivation timer is not activated or may be activated within the target time period.

Optionally, in some embodiments of the present application, the second indication information indicates that the deactivation timer is not started or may be started within the target time period through a wakeup sequence.

Optionally, in some embodiments of the present application, the second indication information is information that is sent by the network device to the terminal device through DRX configuration information.

receiving DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.

Optionally, in some embodiments of the present application, the at least one configuration information includes the first configuration information corresponding to a power saving mode and second configuration information corresponding to a non-power saving mode.

receiving third indication information, where the third indication information is used to indicate that the terminal device switches configuration information of the currently used RDX to the first configuration information or the second configuration information.

Optionally, in some embodiments of the present application, the third indication information is information that is sent by the network device to the terminal device through the downlink control information DCI or the media access control MAC control element CE.

Optionally, in some embodiments of the present application, each of the at least one configuration information includes an activation period timer.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. Specifically, the terminal device 300 shown in fig. 9 may correspond to a corresponding main body in 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 respectively for implementing corresponding flows in each method, and are not described herein again for brevity.

As shown in fig. 10, the network device 400 may include:

a communication unit 410, the communication unit 410 being configured to:

sending first indication information, wherein the first indication information is used for indicating a terminal device to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and sending a Physical Downlink Control Channel (PDCCH).

Optionally, in some embodiments of the present application, the communication unit 410 is specifically configured to:

and transmitting a Media Access Control (MAC) Control Element (CE), wherein the MAC CE comprises the first indication information.

Optionally, in some embodiments of the present application, the communication unit 410 is further configured to:

sending second indication information for indicating that the deactivation timer is not activated or may be activated within a target time period.

sending DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.

and sending third indication information, wherein the third indication information is used for indicating the terminal equipment to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. Specifically, the network device 400 shown in fig. 10 may correspond to a corresponding main body in the method 200 for executing 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 respectively for implementing corresponding flows in each method, and are not described herein again for brevity.

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 10. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.

Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

For example, in the embodiment of the present application, 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 configuration diagram of a communication device 500 according to an embodiment of the present application. The communication device 500 shown in fig. 11 comprises a processor 510, and the processor 510 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 11, the communication device 500 may further include a memory 520. The memory 520 may be used to store instructions and codes, instructions, etc. that may be executed by the processor 510. From the memory 520, the processor 510 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 520 may be a separate device from the processor 510, or may be integrated into the processor 510.

Optionally, as shown in fig. 11, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 530 may include a transmitter and a receiver, among others. The transceiver 530 may further include one or more antennas.

Optionally, the communication device 500 may be a terminal device in this embodiment, and the communication device 500 may implement a corresponding process implemented by the terminal device in each method in this embodiment, that is, the communication device 500 in this embodiment may correspond to the terminal device 300 in this embodiment, and may correspond to a corresponding main body in executing the method 200 in this embodiment, which is not described herein again for brevity.

Optionally, the communication device 500 may be a network device according to this embodiment, and the communication device 500 may implement corresponding processes implemented by the network device in the methods according to this embodiment. 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 a corresponding main body in executing the method 200 according to the embodiment of the present application, and for brevity, no further description is provided here.

It should be understood that the various components in the communication device 500 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

In addition, an embodiment of the present application further provides a chip, which may be an integrated circuit chip, and has signal processing capability, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiment of the present application.

Alternatively, the chip may be applied to various communication devices, so that the communication device mounted with the chip can execute the methods, steps and logic blocks 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 a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 12, the chip 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application. The memory 620 may be used to store instructions and codes, instructions, etc. that may be executed by the processor 610.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc. It will also be appreciated that the various components in the chip 600 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The processor may include, but is not limited to:

general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

The processor may be configured to implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, eprom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

The memory includes, but is not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program. The computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of applications, enable the portable electronic device to perform the methods of the illustrated embodiments of methods 300-500.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may 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 in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program product comprising the computer program.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer program product may 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 in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program. The computer program, when executed by a computer, enables the computer to perform the methods of the illustrated embodiment of method 200.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

The embodiment of the present application further provides a communication system, which may include the terminal device 300 shown in fig. 9 and the network device 400 shown in fig. 10, and for brevity, details are not repeated herein.

It should be noted that the term "system" and the like herein may also be referred to as "network management architecture" or "network system" and the like.

It is also to be understood that the terminology used in the embodiments of the present application and the appended claims is for the purpose of describing particular embodiments only, and is not intended to be limiting of the embodiments of the present application.

For example, as used in the examples of this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

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

If implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

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

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways.

For example, the division of a unit or a module or a component in the above-described device embodiments is only one logical function division, and there may be other divisions in actual implementation, for example, a plurality of units or modules or components may be combined or may be integrated into another system, or some units or modules or components may be omitted, or not executed.

Also for example, the units/modules/components described above as separate/display components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the units/modules/components can be selected according to actual needs to achieve the purposes of the embodiments of the present application.

Finally, it should be noted that the above shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

the terminal equipment receives first indication information, wherein the first indication information is used for indicating the terminal equipment to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and when the terminal equipment receives a Physical Downlink Control Channel (PDCCH), stopping, starting or restarting the deactivation timer according to the first indication information.
The method according to claim 1, wherein the first indication information indicates to the terminal device to start or restart the deactivation timer by using the PDCCH for scheduling new data, and/or wherein the first indication information indicates to the terminal device to stop the deactivation timer by using the PDCCH for scheduling retransmission data.
The method according to claim 1, wherein the first indication information indicates the terminal device to stop, start or restart a deactivation timer via a Radio Network Temporary Identity (RNTI) employed by the PDCCH.
The method of claim 1, wherein Downlink Control Information (DCI) of the PDCCH comprises the first indication information.
The method of claim 1, wherein the terminal device receives the first indication information, and comprises:

and the terminal equipment receives a Media Access Control (MAC) control unit (CE), wherein the MAC CE comprises the first indication information.
The method according to any one of claims 1 to 5, wherein stopping, starting or restarting the deactivation timer according to the first indication information when the terminal device receives a Physical Downlink Control Channel (PDCCH), comprises:

the terminal equipment receives the PDCCH, and when the first indication information is used for indicating the terminal equipment to start or restart the deactivation timer, the terminal equipment starts or restarts the deactivation timer;

the first indication information is used for indicating the terminal equipment to stop the deactivation timer, and the terminal equipment stops the deactivation timer.
The method according to any one of claims 1 to 5, wherein stopping, starting or restarting the deactivation timer according to the first indication information when the terminal device receives a Physical Downlink Control Channel (PDCCH), comprises:

when the terminal equipment receives the PDCCH, the terminal starts or restarts the deactivation timer;

the first indication information is used for indicating the terminal equipment to stop the deactivation timer, and the terminal equipment stops the deactivation timer.
The method according to any one of claims 1 to 7, wherein the first indication information is used for indicating that the terminal device stops, starts or restarts a target deactivation timer of at least one deactivation timer.
The method of claim 8, wherein the target deactivation timer is a default deactivation timer of the at least one deactivation timer.
The method according to any one of claims 1 to 9, further comprising:

the terminal device receives second indication information, wherein the second indication information is used for indicating that the deactivation timer is not started or can be started in a target time period.
The method of claim 10, wherein stopping, starting, or restarting the deactivation timer according to the first indication information when the terminal device receives a Physical Downlink Control Channel (PDCCH), comprises:

and when the terminal equipment receives the PDCCH and the second indication information is used for indicating that the deactivation timer can be started in the target time period, the terminal equipment stops, starts or restarts the deactivation timer according to the first indication information and the second indication information.
The method according to claim 10 or 11, wherein the second indication information is further used for indicating the terminal device to start an activation timer of DRX, and the target time period comprises a time period occupied by at least one active period after the terminal device receives the second indication information in DRX.
The method according to any of claims 10 to 12, wherein the second indication information indicates, by a different medium access control, MAC, control element, CE, that the deactivation timer is not or can be started within the target time period.
The method according to any one of claims 10 to 12, wherein the second indication information indicates through a wake-up sequence that the deactivation timer is not activated or can be activated within the target time period.
The method according to any of claims 10 to 14, wherein the second indication information is information sent by a network device to the terminal device via DRX configuration information.
The method according to any one of claims 1 to 15, further comprising:

the terminal equipment receives DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.
The method of claim 16, wherein the at least one configuration information comprises the first configuration information corresponding to a power saving mode and second configuration information corresponding to a non-power saving mode.
The method of claim 17, further comprising:

the terminal device receives third indication information, where the third indication information is used to indicate the terminal device to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.
The method according to claim 18, wherein the third indication information is information that is sent by a network device to the terminal device through downlink control information DCI or a media access control MAC control element CE.
The method of any of claims 16 to 19, wherein each configuration information of the at least one configuration information comprises an activation period timer.
A method of wireless communication, comprising:

the network equipment sends first indication information, wherein the first indication information is used for indicating the terminal equipment to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and the network equipment sends a physical downlink control channel PDCCH.
The method according to claim 21, wherein the first indication information indicates to the terminal device to start or restart the deactivation timer by using the PDCCH for scheduling new data, and/or wherein the first indication information indicates to the terminal device to stop the deactivation timer by using the PDCCH for scheduling retransmission data.
The method of claim 21, wherein the first indication information indicates the terminal device to stop, start or restart a deactivation timer via a Radio Network Temporary Identity (RNTI) employed by the PDCCH.
The method of claim 21, wherein Downlink Control Information (DCI) of the PDCCH comprises the first indication information.
The method of claim 21, wherein the network device sends the first indication information, comprising:

and the network equipment transmits a Media Access Control (MAC) control unit (CE), wherein the MAC CE comprises the first indication information.
The method according to any one of claims 21 to 25, wherein the first indication information is used to indicate that the terminal device stops, starts or restarts a target deactivation timer of at least one deactivation timer.
The method of claim 26, wherein the target deactivation timer is a default deactivation timer of the at least one deactivation timer.
The method of any one of claims 21 to 27, further comprising:

the network device sends second indication information, wherein the second indication information is used for indicating that the deactivation timer is not started or can be started in a target time period.
The method of claim 28, wherein the second indication information is further used for indicating the terminal device to start an activation timer of DRX, and the target time period comprises a time period occupied by at least one active period after the terminal device receives the second indication information in DRX.
The method according to claim 28 or 29, wherein the second indication information indicates, via a different medium access control, MAC, control element, CE, that the deactivation timer is not or can be started within the target time period.
The method according to claim 28 or 29, wherein the second indication information indicates through a wake-up sequence that the deactivation timer is not activated or can be activated within the target time period.
The method according to any of claims 28 to 31, wherein the second indication information is information sent by a network device to the terminal device via DRX configuration information.
The method of any one of claims 21 to 32, further comprising:

the network equipment sends DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.
The method of claim 33, wherein the at least one configuration information comprises the first configuration information corresponding to a power saving mode and second configuration information corresponding to a non-power saving mode.
The method of claim 34, further comprising:

and the network equipment sends third indication information, wherein the third indication information is used for indicating the terminal equipment to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.
The method of claim 35, wherein the third indication information is information sent by a network device to the terminal device through downlink control information DCI or a media access control MAC control element CE.
The method of any of claims 33 to 36, wherein each configuration information of the at least one configuration information comprises an activation period timer.
A terminal device, comprising:

a communication unit, configured to receive first indication information, where the first indication information is used to indicate that the terminal device stops, starts, or restarts a deactivation timer of Discontinuous Reception (DRX);

and the processing unit is used for stopping, starting or restarting the deactivation timer according to the first indication information when receiving a Physical Downlink Control Channel (PDCCH).
The terminal device according to claim 38, wherein the first indication information indicates to the terminal device to start or restart the deactivation timer by using the PDCCH for scheduling new data, and/or wherein the first indication information indicates to the terminal device to stop the deactivation timer by using the PDCCH for scheduling retransmission data.
The terminal device according to claim 38, wherein the first indication information indicates, via a radio network temporary identity RNTI adopted by the PDCCH, that the terminal device stops, starts or restarts the deactivation timer.
The terminal device of claim 38, wherein Downlink Control Information (DCI) of the PDCCH comprises the first indication information.
The terminal device of claim 38, wherein the communication unit is specifically configured to:

receiving a media access control, MAC, control element, CE, the MAC CE including the first indication information.
The terminal device according to any one of claims 38 to 42, wherein the processing unit is specifically configured to:

receiving the PDCCH, wherein the first indication information is used for indicating the terminal equipment to start or restart the deactivation timer, and starting or restarting the deactivation timer;

the first indication information is used for indicating the terminal equipment to stop the deactivation timer, and then stopping the deactivation timer.
The terminal device according to any one of claims 38 to 42, wherein the processing unit is specifically configured to:

starting or restarting the deactivation timer upon receiving the PDCCH;

the first indication information is used for indicating the terminal equipment to stop the deactivation timer, and then stopping the deactivation timer.
The terminal device according to any of claims 38 to 44, wherein the first indication information is used to indicate that the terminal device stops, starts or restarts a target deactivation timer of at least one deactivation timer.
The terminal device of claim 45, wherein the target deactivation timer is a default deactivation timer of the at least one deactivation timer.
The terminal device according to any of claims 38 to 46, wherein the communication unit is further configured to:

receiving second indication information indicating that the deactivation timer is not activated or may be activated for a target time period.
The terminal device of claim 47, wherein the processing unit is specifically configured to:

and when the PDCCH is received and the second indication information is used for indicating that the deactivation timer can be started in the target time period, stopping, starting or restarting the deactivation timer according to the first indication information and the second indication information.
The terminal device according to claim 47 or 48, wherein the second indication information is further used to instruct the terminal device to start an activation timer for DRX, and the target time period comprises a time period occupied by at least one active period after the terminal device receives the second indication information in DRX.
A terminal device according to any of claims 47-49, wherein said second indication information indicates via a different media access control, MAC, control element, CE, that said deactivation timer is or can be not started within said target time period.
The terminal device of any one of claims 47 to 49, wherein the second indication information indicates, via a wake-up sequence, that the deactivation timer is not started or can be started within the target time period.
The terminal device according to any of claims 47 to 51, wherein the second indication information is information sent by the network device to the terminal device via DRX configuration information.
The terminal device according to any of claims 38-52, wherein the communication unit is further configured to:

receiving DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.
The terminal device of claim 53, wherein the at least one configuration information comprises the first configuration information corresponding to a power saving mode and second configuration information corresponding to a non-power saving mode.
The terminal device of claim 54, wherein the communication unit is further configured to:

receiving third indication information, where the third indication information is used to indicate that the terminal device switches configuration information of the currently used RDX to the first configuration information or the second configuration information.
The terminal device of claim 55, wherein the third indication information is information sent by a network device to the terminal device through Downlink Control Information (DCI) or a Media Access Control (MAC) Control Element (CE).
A terminal device according to any of claims 53 to 56, wherein each of said at least one configuration information comprises an activation period timer.
A network device, comprising:

a communication unit to:

sending first indication information, wherein the first indication information is used for indicating a terminal device to stop, start or restart a deactivation timer of Discontinuous Reception (DRX);

and sending a Physical Downlink Control Channel (PDCCH).
The network device according to claim 58, wherein the first indication information indicates to the terminal device to start or restart the deactivation timer by using the PDCCH for scheduling new data, and/or wherein the first indication information indicates to the terminal device to stop the deactivation timer by using the PDCCH for scheduling retransmission data.
The network device of claim 58, wherein the first indication information indicates, via a Radio Network Temporary Identity (RNTI) employed by the PDCCH, that the terminal device stops, starts or restarts a deactivation timer.
The network equipment of claim 58, wherein Downlink Control Information (DCI) of the PDCCH comprises the first indication information.
The network device of claim 58, wherein the communication unit is specifically configured to:

and transmitting a Media Access Control (MAC) Control Element (CE), wherein the MAC CE comprises the first indication information.
The network device according to any one of claims 58 to 62, wherein the first indication information is used to indicate to the terminal device to stop, start or restart a target deactivation timer of at least one deactivation timer.
The network device of claim 63, wherein the target deactivation timer is a default deactivation timer of the at least one deactivation timer.
The network device of any one of claims 58 to 64, wherein the communication unit is further configured to:

sending second indication information for indicating that the deactivation timer is not activated or may be activated within a target time period.
The network device according to claim 65, wherein the second indication information is further configured to instruct the terminal device to start an activation timer for DRX, and the target time period comprises a time period occupied by at least one active period after the terminal device receives the second indication information in DRX.
The network device according to claim 65 or 66, wherein the second indication information indicates, via a different media access control, MAC, control element, CE, that the deactivation timer is not or can be started within the target time period.
The network device of claim 65 or 66, wherein the second indication information indicates, via a wakeup sequence, that the deactivation timer is not activated or can be activated within the target time period.
The network device according to any of claims 65 to 68, wherein the second indication information is information sent by the network device to the terminal device via DRX configuration information.
The network device of any one of claims 58 to 69, wherein the communication unit is further configured to:

sending DRX configuration information, wherein the DRX configuration information comprises at least one configuration information corresponding to at least one DRX, and a first configuration information in the at least one configuration information does not comprise a deactivation timer; or the deactivation timer is 0 when the first configuration information includes the deactivation timer.
The network device of claim 70, wherein the at least one configuration information comprises the first configuration information corresponding to a power saving mode and second configuration information corresponding to a non-power saving mode.
The network device of claim 71, wherein the communication unit is further configured to:

and sending third indication information, wherein the third indication information is used for indicating the terminal equipment to switch the configuration information of the currently used RDX to the first configuration information or the second configuration information.
The network device according to claim 72, wherein the third indication information is information that the network device sends to the terminal device through downlink control information DCI or a Media Access Control (MAC) Control Element (CE).
The network device of any of claims 70-73, wherein each configuration information of the at least one configuration information comprises an activation period timer.
A terminal device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any one of claims 1-20.
A network device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any one of claims 21 to 37.
A chip, comprising:

a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 20.
A chip, comprising:

a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 21 to 37.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 20.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 21 to 37.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 20.
A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 21 to 37.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 20.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 21-37.