Configuration methods, terminal devices and network devices

Abstract

This application relates to a configuration method, a terminal device, and a network device; wherein, the configuration method includes: the terminal device receiving multiple DRX configurations. This application can enable multiple DRX configuration for a terminal device.

Description

Configuration method, terminal device, and network device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a configuration method, a terminal device, and a network device. Background Art

[0002] In the 5th Generation Mobile Communication Technology (5G) NR system, the network can configure the discontinuous reception (DRX) function for terminal devices, enabling them to monitor the physical downlink control channel (PDCCH) discontinuously to save power. For each Media Access Control (MAC) entity, the network only configures one set of DRX configurations for the terminal device. How to configure multiple DRXs for a terminal device is a technical problem that needs to be solved.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a configuration method, a terminal device, and a network device, which can implement multi-DRX configuration for the terminal device.

[0005] An embodiment of the present application provides a configuration method, including: a terminal device receives a multi-DRX configuration.

[0006] An embodiment of the present application provides a control method, including: a terminal device performs a first operation, where the first operation is related to PDCCH monitoring.

[0007] An embodiment of the present application provides a configuration method, including: a network device sends a multi-DRX configuration.

[0008] An embodiment of the present application provides a terminal device, including: a first transceiver module, used to receive a multi-DRX configuration.

[0009] An embodiment of the present application provides a terminal device, including: a second processing module, used to perform a first operation, where the first operation is related to PDCCH monitoring.

[0010] An embodiment of the present application provides a network device, including: a third transceiver module, configured to receive a multi-DRX configuration.

[0011] An embodiment of the present application provides a terminal device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory to enable the terminal device to perform the above-mentioned configuration method.

[0012] An embodiment of the present application provides a network device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory to enable the network device to perform the above-mentioned configuration method.

[0013] An embodiment of the present application provides a chip for implementing the above configuration method.

[0014] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above configuration method.

[0015] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned configuration method.

[0016] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above configuration method.

[0017] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned configuration method.

[0018] The configuration method proposed in the embodiment of the present application can realize multi-DRX configuration for the terminal device by receiving multi-DRX configuration through the terminal device, so as to be used for different goals or situations, or for different services or logical channels (logical channel, LCH) or service quality (Quality of Service, QoS) flows or QoS information, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG1 exemplarily shows a communication system 100 .

[0020] FIG2 is a schematic flowchart of a configuration method 200 according to an embodiment of the present application.

[0021] FIG3 is a schematic flowchart of a configuration method 300 according to an embodiment of the present application.

[0022] FIG4 is a schematic flowchart of a control method 400 according to an embodiment of the present application.

[0023] FIG5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application.

[0024] FIG6 is a schematic block diagram of a terminal device 600 according to an embodiment of the present application.

[0025] FIG7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application.

[0026] FIG8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application.

[0027] FIG9 is a schematic block diagram of a network device 900 according to an embodiment of the present application.

[0028] FIG10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.

[0029] FIG11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0031] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0032] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0033] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0034] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0035] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0036] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with 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 next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0037] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0038] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0039] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0040] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0041] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0042] In an embodiment of the present application, a network device may provide services for a cell, and a terminal device may communicate with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: a metro cell, a micro cell, a pico cell, a femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0043] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0044] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0045] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0046] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0048] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0049] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0050] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0051] 1. Background on XR / URLLC

[0052] 3GPP technology research involves extended reality (XR) and cloud gaming (CG). The services involved in this research include augmented reality (AR), virtual reality (VR), cloud gaming, etc. A major service of XR / CG is video streaming.

[0053] Application-layer data exchanged between a UE and an application server or peer UE, such as in AR / VR / cloud gaming / live streaming, typically includes data streams in multiple modes, including voice, video, text, and control information. These data streams typically require synchronization, for example, so that voice, video, subtitles, and other data can be displayed synchronously to the user. Currently, video playback synchronizes multiple data streams at the application layer. This involves caching multiple received data streams, extracting corresponding data frames from the multiple data streams based on the timestamps of the playback data streams, and displaying them synchronously to the user.

[0054] In related technologies, multimodal requirements, such as synchronization and coordination, cannot be fully met. Therefore, it is necessary to consider RAN support and enhancement of multimodality.

[0055] 2. 5G NR DRX Process

[0056] In 5G NR technology, the network can configure the DRX function for the terminal, so that the terminal can monitor the PDCCH discontinuously to achieve the purpose of terminal power saving. Each MAC entity is configured with a DRX configuration. The DRX configuration parameters include at least one of the following:

[0057] DRX duration timer (drx-onDurationTimer);

[0058] DRX slot offset (drx-SlotOffset);

[0059] DRX inactivity timer (drx-InactivityTimer);

[0060] DRX downlink retransmission timer (drx-RetransmissionTimerDL);

[0061] DRX uplink retransmission timer (drx-RetransmissionTimerUL);

[0062] DRX long cycle start offset (drx-LongCycleStartOffset);

[0063] DRX short cycle (drx-ShortCycle);

[0064] DRX short cycle timer (drx-ShortCycleTimer);

[0065] DRX downlink hybrid automatic repeat-request (HARQ) round-trip time timer (drx-HARQ-RTT-TimerDL);

[0066] DRX uplink HARQ round trip time timer (drx-HARQ-RTT-TimerUL).

[0067] If the terminal is configured with DRX, it needs to monitor the PDCCH during the DRX activation period. The DRX activation period includes the following situations:

[0068] Any of the five timers, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and ra-ContentionResolutionTimer, is running.

[0069] A reference signal (RS) is sent on the PUCCH and is in a pending state;

[0070] In a contention-based random access procedure, after successfully receiving a random access response, the terminal has not yet received an initial transmission indicated by a PDCCH scrambled with a Cell Radio Network Temporary Identifier (C-RNTI);

[0071] The terminal determines when to start the drx-onDurationTimer based on whether it is currently in a short DRX cycle or a long DRX cycle. The specific regulations are as follows:

[0072] If the Short DRX Cycle is used and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); or if the Long DRX Cycle is used and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset, then the drx-onDurationTimer is started at a moment drx-SlotOffset time slots after the start of the current subframe.

[0073] The condition for the terminal to start or restart the drx-InactivityTimer is: if the terminal receives a PDCCH indicating downlink or uplink initial transmission, the terminal starts or restarts the drx-InactivityTimer.

[0074] The conditions for the terminal to start and stop drx-RetransmissionTimerDL are:

[0075] When the terminal receives a PDCCH indicating a downlink transmission, or when the terminal receives a MAC packet data unit (PDU) on the configured downlink grant resources, the terminal stops the drx-RetransmissionTimerDL corresponding to the HARQ process. After completing the transmission of the HARQ process feedback for this downlink transmission, the terminal starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process.

[0076] If the timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ process of the terminal times out and the decoding of the downlink data transmitted using this HARQ process is unsuccessful, the terminal starts the drx-RetransmissionTimerDL corresponding to this HARQ process.

[0077] The conditions for the terminal to start and stop drx-RetransmissionTimerUL are:

[0078] When the terminal receives a PDCCH indicating an uplink transmission, or when the terminal sends a MAC PDU on the configured uplink grant resource, the terminal stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first repetition of the PUSCH.

[0079] If the timer drx-HARQ-RTT-TimerUL corresponding to a certain HARQ process of the terminal times out, the terminal starts the drx-RetransmissionTimerUL corresponding to this HARQ process.

[0080] As can be seen from the above DRX process, after completing uplink transmission or completing HARQ process feedback for downlink transmission, the terminal will first start a DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL for uplink transmission and drx-HARQ-RTT-TimerDL for downlink transmission). During the operation of this DRX HARQ RTT timer, the terminal is in a dormant state and does not monitor the PDCCH. After the timer expires, the terminal will start monitoring uplink retransmission scheduling, or determine whether to start monitoring downlink retransmission scheduling based on feedback. Among them, drx-HARQ-RTT-TimerUL and drx-HARQ-RTT-TimerDL are semi-statically configured by the network RRC.

[0081] For one MAC entity, the network configures only one set of DRX configurations. One set of DRX configurations contains only one set of cycles (for a DRX long cycle or a DRX short cycle, respectively). The cycle is an integer multiple of milliseconds (ms).

[0082] Existing technologies do not support multiple DRX configurations for different services. Configuring multiple DRX configurations for different services, objectives, or situations, or for multimodal scenarios, and how the terminal device uses these multiple DRX configurations to perform DRX operations, are technical challenges that need to be addressed. Furthermore, controlling the energy consumption of the terminal device also requires consideration.

[0083] FIG2 is a schematic flow chart of a configuration method 200 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0084] S210. The terminal device receives a multi-DRX configuration.

[0085] The terminal device may receive a multi-DRX configuration from the network device.

[0086] In some implementations, the DRX parameter configuration in the multi-DRX configuration is included in one or more of the following information:

[0087] DRX configuration information (DRX-config);

[0088] DRX configuration secondary group (DRX-configSecondaryGroup);

[0089] MAC-Cell Group Configuration (MAC-CellGroupConfig).

[0090] In some implementations, the multiple DRX configurations may be used for different purposes or situations, or the multiple DRX configurations may be configured for different services or LCHs or QoS flows or QoS information respectively.

[0091] In some embodiments, the different services are associated services, multimodal services, synchronized services, cooperatively transmitted services, or services with synchronization or coordination requirements;

[0092] The different LCHs are associated LCHs, LCHs for multi-mode, synchronized LCHs, coordinated transmission LCHs, or LCHs with synchronization or coordination requirements;

[0093] The DRX is an associated DRB, a DRX for multi-mode, a synchronized DRX, a coordinated transmission DRB, or a DRB with synchronization or coordination requirements;

[0094] Different QoS flows are associated QoS flows, multimodal QoS flows, synchronized QoS flows, coordinated transmission QoS flows, or QoS flows with synchronization or coordination requirements;

[0095] Different QoS flows are associated PDU sessions, PDU sessions for multimodality, synchronized PDU sessions, coordinated transmission PDU sessions, or PDU sessions with synchronization or coordination requirements;

[0096] The different QoS information is associated QoS information, QoS information for multi-modality, synchronized QoS information, coordinated transmission QoS information, or QoS information with synchronization or coordination requirements.

[0097] In some implementations, the DRX parameters in the multi-DRX configuration may include at least one of the following:

[0098] DRX duration timer (drx-onDurationTimer);

[0099] DRX slot offset (drx-SlotOffset);

[0100] DRX inactivity timer (drx-InactivityTimer);

[0101] DRX downlink retransmission timer (drx-RetransmissionTimerDL);

[0102] DRX uplink retransmission timer (drx-RetransmissionTimerUL);

[0103] DRX long cycle start offset (drx-LongCycleStartOffset);

[0104] DRX short cycle (drx-ShortCycle);

[0105] DRX short cycle timer (drx-ShortCycleTimer);

[0106] DRX downlink HARQ round trip time timer (drx-HARQ-RTT-TimerDL);

[0107] DRX uplink HARQ round trip time timer (drx-HARQ-RTT-TimerUL);

[0108] Non-integer DRX long cycle;

[0109] The starting offset (startoffest) corresponding to a non-integer DRX long cycle;

[0110] Non-integer DRX short cycle.

[0111] Each DRX parameter may be for the same function; and / or,

[0112] Multiple DRX parameters may be for the same function; and / or,

[0113] All or part of the multiple DRX parameters may be used for different purposes or situations, or may be configured for different services or LCHs or QoS flows or QoS information respectively.

[0114] In some embodiments, in a multi-DRX configuration, the same DRX configuration may be used for at least one target or situation, or the same DRX configuration may be configured for at least one service, LCH, QoS flow, or QoS information (QoS profile). For example, the same DRX configuration may be used for one or more targets, or for one or more situations, or for one or more services, or for one or more LCHs, or for one or more QoS flows, or for one or more QoS profiles.

[0115] In some embodiments, the multiple DRX configuration includes multiple configurations for at least one DRX parameter.

[0116] In one example, among the at least one DRX parameter, the same DRX parameter may have multiple values.

[0117] In one example, different values ​​may be used for different purposes or situations, or different values ​​may be configured for different services or LCHs or QoS flows or QoS information.

[0118] For example, the multi-DRX configuration includes multiple configurations of the parameter drx-onDurationTimer, such as multiple values ​​of the parameter drx-onDurationTimer; each value is used for a different target or situation, or each value is configured for different services or LCHs or QoS flows or QoS information.

[0119] In some implementations, in a multi-DRX configuration, a DRX configuration for the same function includes multiple DRX parameters.

[0120] In one example, the different DRX parameters included in the DRX configuration for the same function may be used for different purposes or situations, or may be configured separately for different services or LCHs or QoS flows or QoS information.

[0121] For example, the multi-DRX configuration includes a parameter drx-onDurationTimer 1 and a parameter drx-onDurationTimer 2, and these two DRX parameters are for the same function; and these two DRX parameters are used for different goals or situations, or are configured for different services or LCHs or QoS flows or QoS information.

[0122] Through the above process, the network device configures the terminal device with multiple DRX configurations. On this basis, the terminal device can perform DRX operations according to the multiple DRX configurations.

[0123] For example, the terminal device performs a DRX operation according to the multi-DRX configuration, including one of the following:

[0124] (1) The terminal device performs DRX operations according to each DRX parameter or the value of each DRX parameter;

[0125] (2) The terminal device processes the DRX parameters or the values ​​of the DRX parameters for the same function and performs the DRX operation.

[0126] (3) The terminal device processes some DRX parameters or values ​​of DRX parameters of the same function and performs DRX operations.

[0127] In some implementations, the terminal device performs a DRX operation according to each DRX parameter or a value of each DRX parameter, including:

[0128] The terminal device performs DRX operation for the service or LCH or QoS flow related to the DRX parameter according to the DRX parameter; or

[0129] The terminal device performs DRX operation for the service or LCH or QoS flow related to the value of the DRX parameter according to the value of the DRX parameter; or

[0130] The terminal device performs a DRX operation according to the DRX parameters, or performs a DRX operation on the corresponding MAC entity; or

[0131] The terminal device performs DRX operations according to the values ​​of the DRX parameters, or performs DRX operations on the corresponding MAC entity.

[0132] In some implementations, the terminal device performs processing on a DRX parameter or a value of a DRX parameter for the same function and performs a DRX operation, including:

[0133] The terminal device will perform a first operation on the DRX parameters or the values ​​of the DRX parameters of the same function, and use the result of the first operation to perform the DRX operation.

[0134] In one example, the first operation includes:

[0135] Take the maximum or minimum value among the DRX parameters for the same function; or,

[0136] Take the maximum or minimum value among the DRX parameters for the same function.

[0137] In some implementations, the terminal device performs processing on some DRX parameters or values ​​of the DRX parameters for the same function and performs a DRX operation, including:

[0138] The terminal device performs a first operation on some of the DRX parameters or values ​​of the DRX parameters for the same function, and executes the DRX operation using the result of the first operation.

[0139] In one example, the first operation includes:

[0140] Take the maximum or minimum value among the DRX parameters for the same function; or,

[0141] Take the maximum or minimum value among the DRX parameters for the same function.

[0142] Through the above configuration method, the embodiment of the present application can configure multiple sets of DRX parameters for the terminal device, and when multiple sets of DRX parameters are configured, the terminal device can use the DRX parameters to perform DRX operations.

[0143] The present application also provides a configuration method that can be applied to a network device. Figure 3 is a schematic flow chart of a configuration method 300 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following content.

[0144] S310: The network device sends a multi-DRX configuration.

[0145] The network device may send the multi-DRX configuration to the terminal device.

[0146] For specific content of the multi-DRX configuration sent by the network device, please refer to the relevant introduction about the multi-DRX configuration in the above configuration method 200, which will not be repeated here.

[0147] Example 1:

[0148] This embodiment introduces a specific method in which a terminal device receives a multi-DRX configuration configured by a network device and uses the multi-DRX configuration to perform a DRX operation.

[0149] The specific implementation process is as follows:

[0150] 1. The UE receives a DRX configuration configured by the network, where the DRX configuration is a multi-DRX configuration. Specifically, the configuration includes at least one of the following:

[0151] 1. Multiple DRX configurations are used for different purposes or situations, or are configured separately for services or LCHs or QOS flows or QOS profiles.

[0152] (1) For example, for multiple DRX configurations, each DRX configuration is used for a different target or situation, or for a different service, LCH, QoS flow, or QOS profile. In one example, the same DRX configuration can be used for one or more targets, or for one or more situations, or for one or more services, or for one or more LCHs, or for one or more QoS flows, or for one or more QOS profiles.

[0153] (2) For example, different DRX configurations may be configured for multi-modal services, LCHs, QOS flows, QoS profiles, or PDU sessions, or separate DRX configurations may be configured for each.

[0154] For the associated services, LCHs, QOS flows, QoS profiles or PDU sessions, configure different DRX configurations for each, or configure separate DRX configurations for each;

[0155] For synchronized services, LCHs, QOS flows, QoS profiles, or PDU sessions, configure different DRX configurations for each, or configure separate DRX configurations for each;

[0156] For coordinated transmission services, LCHs, QOS flows, QoS profiles, or PDU sessions, configure different DRX configurations for each, or configure separate DRX configurations for each.

[0157] For services, LCHs, QOS flows, QoS profiles, or PDU sessions that require synchronization or coordination, configure different DRX configurations for each, or configure separate DRX configurations for each.

[0158] 2. Multi-DRX configuration, including configuring multiple DRX parameters.

[0159] For example, the multiple DRX parameters include configuring different values ​​for the same DRX parameter.

[0160] For example, the multiple DRX parameters include, for the DRX configuration parameters of the same function or a DRX configuration parameter (such as on-duration timer), configuring multiple specific DRX parameters (such as on-duration timer1 for multimodal service 1 or QoS flow1, and on-duration timer2 for multimodal service 2 or QoS flow2).

[0161] For example, the DRX configuration parameters include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle.

[0162] For example, in a DRX configuration, only some DRX configuration parameters are multi-configured (for example, configuring two on-duration timers, or configuring two parameters for an on-duration timer), while other DRX configuration parameters are single-configured (for example, configuring one HARQ RTT timer, or configuring one parameter for the HARQ RTT timer).

[0163] For example, in DRX configuration, all DRX configuration parameters are multi-configuration, that is, all parameters have multiple sets or multiple values.

[0164] 2. The UE performs DRX operations according to the DRX configuration, which may include at least one of the following:

[0165] For any DRX on state determined by a timer, the UE can perform PDCCH monitoring (regardless of service, LCH, or QoS). The timer includes at least one of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL.

[0166] For a DRX on state determined by a timer related to a service, QoS, or LCH, the UE can only perform PDCCH monitoring for the service, LCH, or QoS (differentiating between services, LCH, or QoS). The timer includes at least one of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL.

[0167] For the DRX on state determined by a timer related to a service, QoS, or LCH, the UE can only perform PDCCH monitoring for the service, LCH, or QoS (differentiating between services, LCH, or QoS). For a common timer, the UE can perform any PDCCH monitoring in the DRX on state determined by it (without distinguishing between services, LCH, or QoS). The common timer includes at least one of the following: drx-onDurationTimer, drx-InactivityTimer. The timer related to the service, QoS, or LCH includes at least one of the following: drx-RetransmissionTimerUL.

[0168] For multiple DRX configurations, the UE maintains and executes DRX behaviors according to its own (each set of) DRX configuration parameters.

[0169] For example, DRX parameters or DRX parameter values ​​are respectively configured for QoS flow 1 and QoS flow 2, or DRX parameters or DRX parameter values ​​are respectively configured for LCH 1 and LCH 2. Taking the configuration of DRX parameters separately as an example, the DRX parameters for QoS flow 1 or LCH 1 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. The DRX parameters for QoS flow 2 or LCH 2 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. For QoS flow 1 or LCH 1, the UE determines the on-duration position, duration, inactive timer (inactive timer) duration, RRT timer (RTT timer) and Retx timer duration, DRX cycle according to its corresponding DRX parameters, thereby determining the DRX on (on) and off (off) time, and / or performing downlink control information (DCI) monitoring.The user equipment (UE) determines the on-duration position, duration, inactive timer duration, RTT timer and Retx timer duration, and DRX cycle for QoS flow 2 or LCH 2 according to its corresponding DRX parameters, thereby determining the DRX on and off time and / or performing DCI monitoring.

[0170] For multiple DRX configurations, the UE performs a first operation on a DRX parameter of the same function, or a same type of DRX parameter. The first operation may be called a combined operation, and performs a DRX behavior according to a result of the first operation.

[0171] For example, DRX parameters or DRX parameter values ​​are respectively configured for QoS flow 1 and QoS flow 2, or DRX parameters or DRX parameter values ​​are respectively configured for LCH 1 and LCH 2. Taking the configuration of DRX parameters separately as an example, the DRX parameters for QoS flow 1 or LCH 1 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. The DRX parameters for QoS flow 2 or LCH 2 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. If the DRX configuration parameter of the same function has multiple parameters or multiple values, a combined operation is performed for the DRX configuration parameter of this function (i.e., selecting which parameter or parameter value to use. For example, selecting its minimum value or selecting its maximum value. For example, for multiple on-duration timers, taking the minimum or maximum value among the on-duration timers as the final on-duration timer value. For another example, for multiple inactive timers, taking the maximum or minimum value as the final inactive timer value. For another example, for multiple startoffsets, taking the earliest or latest position indicated as the final startoffset value. For another example, for multiple RTT timers, taking the maximum or minimum value as the final RTT timer value).Based on the result of the combined operation, the UE determines the on-duration position, duration, inactive timer duration, RTT timer and Retx timer duration, DRX cycle, and / or determines the DRX on and off time, and / or performs DCI monitoring.

[0172] For multiple DRX configurations, the UE performs a combined operation on some DRX parameters with the same function, or some DRX parameters with the same function, and then performs a DRX behavior.

[0173] For example, DRX parameters or DRX parameter values ​​are respectively configured for QoS flow 1 and QoS flow 2, or DRX parameters or DRX parameter values ​​are respectively configured for LCH 1 or LCH 2. Taking the configuration of DRX parameters separately as an example, the DRX parameters for QoS flow 1 or LCH 1 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. The DRX parameters for QoS flow 2 or LCH 2 include at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. If a specific DRX configuration parameter with the same function has multiple parameters or multiple values, a combined operation is performed for the specific DRX configuration parameter with this function (i.e., which parameter or parameter value to use is selected. For example, its minimum value is selected, or its maximum value is selected. For example, for multiple on-duration timers, the minimum or maximum value among the on-duration timers is taken as the final on-duration timer value. For example, for multiple inactive timers, the maximum or minimum value among them is taken as the final inactive timer value. For example, for multiple startoffsets, for different QoS flows or LCHs, the corresponding startoffsets are used.For example, for multiple RTT timers, for different QoS flows or LCHs, the corresponding RTT timer values ​​are used. Based on the results of the combined operation on some DRX configuration parameters and / or the values ​​of the DRX configuration parameters, the UE determines the on-duration position, duration, inactive timer duration, RTT timer and Retx timer duration, DRX cycle, and / or determines the DRX on and off time, and / or performs DCI monitoring.

[0174] This embodiment proposes a method for configuring multiple sets of DRX parameters, and proposes a method for a terminal device to perform DRX operations using the DRX parameters when multiple sets of DRX parameters are configured.

[0175] The present application also provides a control method. FIG4 is a schematic flow chart of a control method 400 according to an embodiment of the present application. The method can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0176] S410. The terminal device performs a first operation, where the first operation is related to PDCCH monitoring.

[0177] Through the control method proposed in the embodiment of the present application, the terminal device can perform operations related to PDCCH monitoring, thereby increasing or reducing DCI monitoring opportunities and realizing energy consumption control of the terminal device.

[0178] The control method proposed in this embodiment can be applied to the scenario of performing multi-DRX configuration for the terminal device as described in the aforementioned configuration method, and can also be applied to the scenario of performing single DRX configuration for the terminal device.

[0179] In some implementations, the terminal device performs the first operation, including: the terminal device receiving a DRX parameter, where the DRX parameter includes at least one of the following:

[0180] DRX duration timer (drx-onDurationTimer);

[0181] DRX slot offset (drx-SlotOffset);

[0182] DRX deactivation timer (drx-InactivityTimer);

[0183] DRX downlink retransmission timer (drx-RetransmissionTimerDL);

[0184] DRX uplink retransmission timer (drx-RetransmissionTimerUL);

[0185] DRX long cycle start offset (drx-LongCycleStartOffset);

[0186] DRX short cycle (drx-ShortCycle);

[0187] DRX short cycle timer (drx-ShortCycleTimer);

[0188] DRX downlink HARQ round trip time timer (drx-HARQ-RTT-TimerDL);

[0189] DRX uplink HARQ round trip time timer (drx-HARQ-RTT-TimerUL);

[0190] Non-integer DRX long cycle;

[0191] The starting offset (startoffest) corresponding to a non-integer DRX long cycle;

[0192] Non-integer DRX short cycle.

[0193] In some embodiments, the first operation includes the terminal device performing a DRX long-short cycle conversion.

[0194] In one example, the terminal device performs the first operation, including: when a first condition is met, the terminal device performs the first operation.

[0195] In one example, the first operation includes converting from a DRX long cycle to a DRX short cycle.

[0196] The first condition may include:

[0197] Receive network instruction information;

[0198] For multi-modal QoS flow or PDU session or LCH or data packet arrival;

[0199] The associated QoS flow or PDU session or LCH or data packet arrives;

[0200] Synchronous QoS flow or PDU session or LCH or data packet arrival;

[0201] Co-transmitted QoS flow or PDU session or LCH or data packet arrival;

[0202] QoS flows, PDU sessions, LCHs, or data packets with synchronization or coordination requirements arrive;

[0203] A multimodal QoS flow, PDU session, LCH, or data packet starts to be transmitted or is transmitted;

[0204] The associated QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0205] The synchronized QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0206] The coordinated QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0207] A QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements starts to be transmitted or is transmitted;

[0208] The delay of a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to a first threshold;

[0209] The latency of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0210] The delay of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0211] The delay of the coordinated transmission QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0212] The delay of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is less than or equal to the first threshold;

[0213] Part of the data for a multimodal QoS flow, PDU session, LCH, or data packet has been transmitted;

[0214] Part of the data of the associated QoS flow or PDU session or LCH or data packet has been transmitted;

[0215] Part of the data of the synchronized QoS flow or PDU session or LCH or data packet has been transmitted;

[0216] Part of the data of the coordinated QoS flow, PDU session, LCH or data packet has been transmitted;

[0217] Part of the data of the QoS flow, PDU session, LCH or data packet that requires synchronization or coordination has been transmitted;

[0218] The amount of data to be transmitted for multimodal QoS flows, PDU sessions, LCHs, or data packets;

[0219] The amount of data to be transmitted for the associated QoS flow, PDU session, LCH, or data packet;

[0220] The amount of data to be transmitted by the synchronized QoS flow, PDU session, LCH or data packet;

[0221] The amount of data to be transmitted for the coordinated QoS flow, PDU session, LCH, or data packet;

[0222] The amount of data to be transmitted for QoS flows, PDU sessions, LCHs, or data packets that require synchronization or coordination;

[0223] The amount of data to be transmitted for the multimodal QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0224] The amount of data to be transmitted of the associated QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0225] The amount of data to be transmitted of the synchronized QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0226] The amount of data to be transmitted of the coordinated QoS flow, PDU session, LCH, or data packet is greater than or equal to the second threshold;

[0227] The amount of data to be transmitted of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is greater than or equal to the second threshold;

[0228] The terminal device has data for a multimodal QoS flow or LCH or data packet in its cache;

[0229] The data of the associated QoS flow or LCH or data packet exists in the cache of the terminal device;

[0230] The terminal device has data of a synchronized QoS flow or LCH or data packet in its cache;

[0231] The terminal device has data of the collaboratively transmitted QoS flow, PDU session, LCH, or data packet in its buffer;

[0232] The buffer of the terminal device contains data of a QoS flow or a PDU session or an LCH or a data packet with synchronization or collaboration requirements.

[0233] In one example, the terminal device performs the first operation including: when a second condition is met, the terminal device performs the first operation.

[0234] In one example, the first operation includes converting from a DRX short cycle to a DRX long cycle.

[0235] The second condition may include:

[0236] Receive network instruction information;

[0237] The multi-modal QoS flow or PDU session or LCH or data packet is transmitted;

[0238] The associated QoS flow or PDU session or LCH or data packet is transmitted;

[0239] The synchronized QoS flow or PDU session or LCH or data packet is transmitted;

[0240] The coordinated QoS flow or PDU session or LCH or data packet is transmitted;

[0241] The QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements is transmitted;

[0242] The latency for a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to a third threshold (the third threshold may be less than the first threshold);

[0243] The delay of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0244] The delay of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0245] The delay of the coordinated transmission QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0246] The delay of QoS flows, PDU sessions, LCHs, or data packets with synchronization or coordination requirements is less than or equal to the third threshold;

[0247] The necessary data for a multimodal QoS flow, PDU session, LCH, or data packet has been transmitted;

[0248] The necessary data in the associated QoS flow or PDU session or LCH or data packet has been transmitted;

[0249] The necessary data in the synchronized QoS flow or PDU session or LCH or data packet has been transmitted;

[0250] The necessary data in the coordinated QoS flow, PDU session, LCH or data packet has been transmitted;

[0251] The necessary data in the QoS flow, PDU session, LCH or data packet with synchronization or coordination requirements has been transmitted;

[0252] For a multimodal QoS flow, PDU session, LCH, or data packet, there is no data to be transmitted or the data packet has been deleted.

[0253] The associated QoS flow, PDU session, LCH, or data packet has no data to be transmitted or has been deleted;

[0254] The synchronized QoS flow, PDU session, LCH, or data packet has no data to be transmitted or has been deleted;

[0255] The QoS flow, PDU session, LCH or data packet of the coordinated transmission has no data to be transmitted or has been deleted;

[0256] The QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements has no data to be transmitted or has been deleted;

[0257] The amount of data to be transmitted for a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold (the fourth threshold may be less than the second threshold);

[0258] The amount of data to be transmitted of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0259] The amount of data to be transmitted of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0260] The amount of data to be transmitted of the coordinated QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0261] The amount of data to be transmitted of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is less than or equal to the fourth threshold;

[0262] There is no data for the multimodal QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0263] There is no data for the associated QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0264] There is no data of the synchronized QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0265] The terminal device does not have data for the co-transmitted QoS flow, PDU session, LCH, or data packet in its cache;

[0266] There is no data of QoS flow, PDU session, LCH or data packet with synchronization or coordination requirements in the cache of the terminal device.

[0267] The network indication information in the first condition and / or the second threshold may include at least one of the following:

[0268] Whether to perform DRX long-short cycle conversion;

[0269] Convert to long or short cycles;

[0270] Recommended DRX cycle configuration.

[0271] In some implementations, the network indication information may be at least one of a state transition MAC CE, a DRX command MAC CE, and a DCI carrying specific indication information.

[0272] In some implementations, the terminal device may trigger a DRX cycle transition. For example, the terminal device performs a first operation and sends first information to the network device, where the first information includes at least one of the following:

[0273] Whether to perform DRX long-short cycle conversion;

[0274] Convert to long or short cycles;

[0275] Recommended DRX cycle configuration.

[0276] The first information may be carried by RRC signaling or UL MAC CE or UCI.

[0277] In the above manner, the terminal device can perform DRX cycle conversion when there is business to be transmitted to increase or reduce DCI monitoring opportunities.

[0278] In some embodiments, the first operation includes the terminal device using a predetermined value or configuration for a set DRX parameter.

[0279] In one example, the terminal device performs the first operation, including: when a first condition is met, the terminal device performs the first operation.

[0280] In one example, the first operation includes using a first value or a first configuration for a set DRX parameter.

[0281] In one example, the terminal device performs the first operation including: when a second condition is met, the terminal device performs the first operation.

[0282] In one example, the first operation includes using a second value or a second configuration for a set DRX parameter.

[0283] In some implementations, the DRX parameters set above include at least one of the following:

[0284] DRX duration timer (drx-onDurationTimer);

[0285] DRX inactivity timer (drx-InactivityTimer);

[0286] DRX downlink retransmission timer (drx-RetransmissionTimerDL);

[0287] DRX uplink retransmission timer (drx-RetransmissionTimerUL);

[0288] DRX short cycle (drx-ShortCycle);

[0289] DRX short cycle timer (drx-ShortCycleTimer);

[0290] DRX downlink HARQ round trip time timer (drx-HARQ-RTT-TimerDL);

[0291] DRX uplink HARQ round trip time timer (drx-HARQ-RTT-TimerUL);

[0292] Non-integer DRX long cycle;

[0293] Non-integer DRX short cycle.

[0294] The first condition and the second condition in this embodiment can be referred to the above introduction and will not be repeated here.

[0295] In this example, the network indication information in the first condition and / or the second condition may include at least one of the following:

[0296] Whether to perform DRX parameter value or configuration conversion;

[0297] Converting to a first value or a first configuration;

[0298] the first value or the first configuration;

[0299] Convert to the second value or the second configuration.

[0300] In some implementations, the conversion of the DRX parameter value or configuration may be triggered by a terminal device. For example, the terminal device performs a first operation and sends second information to the network device, where the second information includes at least one of the following:

[0301] Whether to perform DRX parameter value or configuration conversion;

[0302] Converting to a first value or a first configuration;

[0303] the first value or the first configuration;

[0304] Convert to the second value or the second configuration.

[0305] The second information may be carried by radio resource control (RRC) signaling or uplink (UL) MAC control element (CE) or uplink control information (UCI).

[0306] In the above manner, the terminal device can use different DRX parameter values ​​or configurations to increase or decrease DCI monitoring opportunities when there is business to be transmitted.

[0307] In some embodiments, the terminal device performs a first operation, including: the terminal device receives a PDCCH skipping parameter.

[0308] In one example, the first operation includes: the terminal device performs or skips PDCCH monitoring.

[0309] In one example, the terminal device performs the first operation, including: when a first condition is met, the terminal device performs the first operation.

[0310] In one example, the first operation includes:

[0311] The terminal device ignores the indication of the PDCCH skip monitoring parameter; and / or,

[0312] The terminal device monitors the PDCCH.

[0313] In one example, the terminal device performs the first operation including: when a second condition is met, the terminal device performs the first operation.

[0314] In one example, the first operation includes the terminal device performing a PDCCH skip monitoring operation; and / or the terminal device skips monitoring the PDCCH.

[0315] The first condition and the second condition in this embodiment can be referred to the above introduction and will not be repeated here.

[0316] In this example, the network indication information in the first condition and / or the second condition may include at least one of the following:

[0317] Ignore the indication of PDCCH skip monitoring parameters;

[0318] Ignored time periods or points in time;

[0319] Whether PDCCH skip monitoring operation can be performed;

[0320] A time period or a time point during which a PDCCH skipping monitoring operation may be performed.

[0321] In some implementations, PDCCH skipping may be triggered by a terminal device. For example, the terminal device performs a first operation and sends third information to the network device. The third information includes at least one of the following:

[0322] Ignore the indication of PDCCH skip monitoring parameters;

[0323] Ignored time periods or points in time;

[0324] Whether PDCCH skip monitoring operation can be performed;

[0325] A time period or a time point during which a PDCCH skipping monitoring operation may be performed.

[0326] The third information may be carried by RRC signaling or UL MAC CE or UCI.

[0327] In the above manner, the terminal device can ignore PDCCH skipping or perform PDCCH skipping when there is business to be transmitted, so as to increase or reduce DCI monitoring opportunities.

[0328] Example 2:

[0329] This embodiment introduces an example of a terminal device performing a DRX long-short cycle conversion. This example is applicable to scenarios where a network device performs multiple DRX configurations for a terminal device, and is also applicable to scenarios where a network device performs single DRX configurations for a terminal device.

[0330] The specific implementation process is as follows:

[0331] 1. The UE receives DRX parameters configured by the network.

[0332] For example, the DRX parameter includes at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startoffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle.

[0333] 2. The UE performs a DRX long-short cycle conversion, for example, including at least one of the following:

[0334] When the first condition is met, the UE switches from a DRX long cycle to a DRX short cycle. Its function is to increase the PDCCH monitoring opportunity. The first condition may include at least one of the following: receiving network indication information, a multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet arrives, a multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the delay of the multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold, the ... multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the multimodal Part of the data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold, and there is data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0335] For example, the DRX long-short cycle switching is triggered by the network, or the network determines whether the first condition is met. For example, the network sends network indication information, which includes at least one of the following: state transition MAC CE, DRX Command MAC CE, and DCI carrying specific indication information.

[0336] For another example, the DRX long-short cycle transition is triggered by the UE, or the UE determines whether the first condition is met. Furthermore, if triggered or determined by the UE, the UE may send first information to the network. The first information may be DRX state transition information. The DRX state transition information may include at least one of the following: whether to perform the DRX long-short cycle transition, the conversion to a long cycle or a short cycle, and a recommended DRX cycle configuration. The DRX state transition information may be carried by the RRC, UL MAC CE, or UCI.

[0337] In one example, while data stream 1 is being transmitted (sending or receiving a MAC PDU), the MAC switches to using a short DRX cycle for PDCCH monitoring of another synchronous stream. The gNB indicates the use of a short DRX cycle for both the downlink (DL) and uplink (UL). For the uplink (UL), if the UE triggers the switch, the UE also needs to indicate the switch to the gNB (via UCI or MAC CE).

[0338] In one example, when transmitting (sending or receiving) a MAC PDU for (partial) packet 1, the MAC switches to using short DRX cycles to monitor the PDCCH for packet 1 and the PDCCH for another synchronization packet. For the downlink (UL), the gNB indicates the use of short DRX cycles. For the uplink (UL), the UE triggers this switch and also needs to indicate this to the gNB (via UCI or MAC CE).

[0339] In the above process, the terminal device switches from a long DRX cycle to a short DRX cycle, which can increase the PDCCH monitoring opportunity.

[0340] When the second condition is met, the UE switches from a DRX short cycle to a DRX long cycle. Its function is to reduce the PDCCH monitoring opportunities. The second condition may include at least one of the following: receiving network indication information, a multimodal (or associated, or synchronized, or cooperatively transmitted, or requiring synchronization or coordination) QoS flow or PDU session or LCH or data packet is transmitted, a multimodal (or associated, or synchronized, or cooperatively transmitted, or requiring synchronization or coordination) QoS flow or PDU session or LCH or data packet starts to transmit or is transmitted, a multimodal (or associated, or synchronized, or cooperatively transmitted, or requiring synchronization or coordination) QoS flow or PDU session or LCH or data packet has a delay less than or equal to a third threshold (the third threshold may be less than the above-mentioned first threshold), a multimodal (or associated, or synchronized, or cooperatively transmitted, or requiring synchronization or coordination) QoS flow or PDU session or LCH or data packet starts to transmit or is transmitted, The required data in the (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has no data to be transmitted or has been deleted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the fourth threshold (the fourth threshold may be less than the above-mentioned second threshold), and there is no data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0341] For example, the DRX long-short cycle transition is triggered by the network, or the network determines whether the second condition is met. For example, the network sends network indication information, which may indicate the transition or the transition to a long DRX cycle. The network indication information may include at least one of the following: a State Change MAC CE, a DRX Command MAC CE, or a DCI carrying specific indication information.

[0342] For another example, the DRX long-short cycle transition is triggered by the UE, or the UE determines whether the second condition is met. Furthermore, if triggered or determined by the UE, the UE may send first information to the network. The first information may be DRX state transition information. The DRX state transition information may include at least one of the following: whether to perform the DRX long-short cycle transition, the conversion to a long cycle or a short cycle, and a recommended DRX cycle configuration. The DRX state transition information may be carried by the RRC, UL MAC CE, or UCI.

[0343] In the above process, the terminal device switches from a DRX short cycle to a DRX long cycle, which can reduce the PDCCH monitoring opportunities.

[0344] This embodiment can be used for multi-modal or associated services. When there is a service to be transmitted, DRX cycle conversion can be performed to increase or decrease DCI monitoring opportunities.

[0345] Example 3:

[0346] This embodiment introduces an example of a terminal device performing DRX parameter conversion. This example is applicable to scenarios where a network device performs multi-DRX configuration for a terminal device, and is also applicable to scenarios where a network device performs single-DRX configuration for a terminal device.

[0347] The specific implementation process is as follows:

[0348] 1. The UE receives DRX parameters configured by the network.

[0349] For example, the DRX parameter includes at least one of the following: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, a non-integer DRX long cycle, a startOffest corresponding to a non-integer DRX long cycle, and a non-integer DRX short cycle. A second value or a second configuration is configured for the aforementioned parameter, and the second value or the second configuration can be considered as a default value, or a value used when the first condition is not met.

[0350] For some or all DRX parameters, a first value or a first configuration may be further configured, where the first value or configuration is a value used when the first condition is satisfied. For example, the DRX parameter configured with the first value or the first configuration includes at least one of the following: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-ShortCycle, drx-ShortCycleTimer, a non-integer DRX long cycle, or a non-integer DRX short cycle.

[0351] 2. The UE uses a first value or a first configuration for a specific DRX configuration parameter, such as a timer. For example, the first value or the first configuration includes at least one of the following:

[0352] When the first condition is met, the UE uses the first value or the first configuration for a specific DRX configuration parameter, such as a timer. Its function is to increase the PDCCH monitoring opportunity. The first condition may include at least one of the following: receiving network indication information, a multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet arrives, a multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the delay of the multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold, the multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the delay of the multimodal (or associated, or synchronized, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold, Part of the data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold, and there is data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0353] Among them, which configured grants (Configured Grant, CG) / dynamic grants (Dynamic Grant, DG) / HARQ entities (entity) / LCH / UE are allowed to use the first value can be configured by the network.

[0354] In some examples, after the terminal device uses the first value or the first configuration for a first duration, the UE switches to using the default value, i.e., using the second value or the second configuration. Alternatively, when the network instructs the UE to change to the default value, the UE switches to using the default value, i.e., using the second value or the second configuration.

[0355] For example, the transition is triggered by the network, or the network determines whether the first condition is met. For example, the network sends network indication information, where the network indication information is used to indicate the transition, or to indicate that the transition uses the first value or first configuration, or to indicate the first value or first configuration. The network indication information may include at least one of the following: a state transition MAC CE, a DRX Command MAC CE, or DCI carrying specific indication information.

[0356] For another example, the transition is triggered by the UE, or the UE determines whether the first condition is satisfied. Furthermore, if triggered or determined by the UE, the UE may send second information to the network. The second information may be DRX state transition information. The DRX state transition information may include at least one of the following: whether to transition, using the first value or first configuration for the transition, or the value of the first value or first configuration. The DRX state transition information may be carried by RRC, UL MAC CE, or UCI.

[0357] In one example, while data stream 1 is being transmitted (sending or receiving a MAC PDU), the MAC switches to using a specific inactivity timer to monitor another synchronization stream. For both downlink (DL) and uplink (UL), the gNB indicates the use of the new timer / value (via DCI or MAC CE). For the uplink, if the user equipment (UE) triggers the switch, the gNB also needs to indicate the switch to the gNB (via UCI or MAC CE).

[0358] In one example, when (partial) packet 1 is being transmitted (sent or received as a MAC PDU), the MAC switches to using a specific inactivity timer to monitor packet 1 and another synchronization packet. For the downlink (DL), the gNB further indicates the use of the new timer / value (via DCI or MAC CE). For the uplink (UL), the UE also needs to indicate this switch to the gNB (via UCI or MAC CE), if triggered by the UE.

[0359] In the above process, the terminal device may use the first value or the first configuration for a specific DRX parameter to increase the PDCCH monitoring opportunity.

[0360] When the second condition is met, for the above-mentioned DRX parameter, the first value or the first configuration returns to the default value, that is, the DRX parameter uses the second value or the second configuration. The second condition includes at least one of the following: receiving network indication information, multimodal (or associated, or synchronous, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is transmitted, multimodal (or associated, or synchronous, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the delay of the multimodal (or associated, or synchronous, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the third threshold (the third threshold may be less than the above-mentioned first threshold), the multimodal (or associated, or synchronous, or cooperatively transmitted, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the third threshold (the third threshold may be less than the above-mentioned first threshold), The required data in the (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has no data to be transmitted or has been deleted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the fourth threshold (the fourth threshold may be less than the above-mentioned second threshold), and there is no data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0361] For example, the transition is triggered by the network, or the network determines whether the second condition is met. For example, the network sends network indication information, where the network indication information is used to indicate the transition or to indicate that a default value (such as the second value or the second configuration) is used for the transition. The network indication information may include at least one of the following: a state transition MAC CE, a DRX Command MAC CE, or a DCI carrying specific indication information.

[0362] For another example, the transition is triggered by the UE, or the UE determines whether the second condition is met. Furthermore, if triggered or determined by the UE, the UE may send second information to the network. The second information may be DRX state transition information. The DRX state transition information may include at least one of the following: whether to transition, or indicating that a default value (such as the second value or the second configuration) is used for the transition. The DRX state transition information may be carried by the RRC, UL MAC CE, or UCI.

[0363] This embodiment can increase or decrease DCI monitoring opportunities for multi-modal or associated services when there is a service to be transmitted by using different timer lengths.

[0364] Example 4:

[0365] This embodiment introduces an example of a terminal device performing PDCCH skipping monitoring. This example is applicable to scenarios where a network device performs multi-DRX configuration for a terminal device, and is also applicable to scenarios where a network device performs single-DRX configuration for a terminal device.

[0366] The specific implementation process is as follows:

[0367] 1. The UE receives a PDCCH skipping parameter configured by the network. The PDCCH skipping parameter may include at least one of the following: PDCCHskippingDuration-list.

[0368] Second, the UE determines whether to ignore the PDCCH skipping. For example, when the network instructs (e.g., via DCI) the UE to perform PDCCH skipping, the UE determines whether to ignore the PDCCH skipping instruction, i.e., whether to perform PDCCH monitoring. This includes at least one of the following:

[0369] If the first condition is met, the UE ignores the PDCCH skipping indication and / or monitors the PDCCH (or monitors the PDCCH of the associated service). Alternatively, if the first condition is met, the UE ignores the PDCCH skipping indication and / or monitors the PDCCH (or monitors the PDCCH of the associated service) during the PDCCH skipping duration. This serves to increase the number of PDCCH monitoring opportunities. The first condition may include at least one of the following: receiving network indication information, a multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet arriving, a multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starting to be transmitted or being transmitted, a multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet having a delay less than or equal to a first threshold, a multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starting to be transmitted or being transmitted, Part of the data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold, and there is data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0370] Among them, which CG / DG / HARQ entity / LCH / UE is allowed to ignore PDCCH skipping can be configured by the network.

[0371] For example, the transition is triggered by the network, or the network determines whether the first condition is met. For example, the network sends network indication information, which is used to instruct the UE to ignore the PDCCH skipping indication, or to monitor the PDCCH during the time period indicated by the PDCCH skipping (or part of the time period / time point therein). The network indication information includes at least one of the following: a state transition MAC CE, a DRX Command MAC CE, and a DCI carrying specific indication information.

[0372] For another example, the transition is triggered by the UE, or the UE determines whether the first condition is met. Furthermore, if triggered or determined by the UE, the UE instructs the network to send third information, which may be an indication to ignore the PDCCH skipping operation. The third information (or indication information) may include at least one of the following: an indication to ignore PDCCH skipping, a time period or a time point to ignore. The third information (or indication information) may be carried by RRC, UL MAC CE, or UCI.

[0373] In the above process, the terminal device can increase the PDCCH monitoring opportunities.

[0374] If the second condition is met, the UE may perform automatic PDCCH skipping (e.g., perform PDCCH skipping, or inform the network that PDCCH skipping can be performed). The second condition includes at least one of the following: receiving network indication information, multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is transmitted, multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted, the delay of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the third threshold (the third threshold may be less than the above-mentioned first threshold), the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the third threshold (the third threshold may be less than the above-mentioned first threshold), The required data in the (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has been transmitted, the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet has no data to be transmitted or has been deleted, the amount of data to be transmitted of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet is less than or equal to the fourth threshold (the fourth threshold may be less than the above-mentioned second threshold), and there is no data of the multimodal (or associated, or synchronized, or coordinated transmission, or with synchronization or coordination requirements) QoS flow or PDU session or LCH or data packet in the UE's buffer.

[0375] For example, the transition is triggered by the UE, or the UE determines whether the second condition is met. Furthermore, if triggered or determined by the UE, the UE may indicate to the network information regarding PDCCH skipping that the UE can perform. This information may include at least one of the following: whether PDCCH skipping can be performed, a time period or time point during which PDCCH skipping can be performed. Based on the UE indication, the network may ultimately determine whether to instruct the UE to perform PDCCH skipping and / or the time period during which PDCCH skipping can be performed.

[0376] This embodiment can increase monitoring opportunities for multi-modal or associated services by ignoring PDCCH skipping when there is a service to be transmitted.

[0377] FIG5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application. The terminal device 500 includes:

[0378] The first transceiver module 510 is configured to receive a multi-DRX configuration.

[0379] In one embodiment, multiple DRX configurations are used for different purposes or situations, or the multiple DRX configurations are configured for different services or LCHs or QoS flows or QoS information respectively.

[0380] In one embodiment, in the multiple DRX configurations, the same DRX configuration is used for at least one target or situation, or the same DRX configuration is configured for at least one service or LCH or QoS flow or QoS information.

[0381] In one embodiment, the multiple DRX configuration includes multiple configurations for at least one DRX parameter.

[0382] In one implementation, in at least one DRX parameter, the same DRX parameter has multiple values.

[0383] In one embodiment, different values ​​are used for different purposes or situations, or different values ​​are configured for different services or LCHs or QoS flows or QoS information.

[0384] In one embodiment, in a multi-DRX configuration, a DRX configuration for a same function includes multiple DRX parameters.

[0385] In one embodiment, different DRX parameters are used for different purposes or situations, or different DRX parameters are configured for different services or LCHs or QoS flows or QoS information respectively.

[0386] In one embodiment, the DRX parameters in the multi-DRX configuration include at least one of the following:

[0387] DRX duration timer drx-onDurationTimer;

[0388] DRX slot offset drx-SlotOffset;

[0389] DRX inactivity timer drx-InactivityTimer;

[0390] DRX downlink retransmission timer drx-RetransmissionTimerDL;

[0391] DRX uplink retransmission timer drx-RetransmissionTimerUL;

[0392] DRX long cycle start offset drx-LongCycleStartOffset;

[0393] DRX short cycle drx-ShortCycle;

[0394] DRX short cycle timer drx-ShortCycleTimer;

[0395] DRX downlink HARQ round trip time timer drx-HARQ-RTT-TimerDL;

[0396] DRX uplink HARQ round trip time timer drx-HARQ-RTT-TimerUL;

[0397] Non-integer DRX long cycle;

[0398] The starting offset startoffest corresponding to the non-integer DRX long cycle;

[0399] Non-integer DRX short cycle.

[0400] In one embodiment, each DRX parameter is for the same function; and / or,

[0401] Multiple DRX parameters for the same function; and / or,

[0402] All or part of the multiple DRX parameters are used for different purposes or situations, or are configured for different services or LCHs or QoS flows or QoS information respectively.

[0403] FIG6 is a schematic block diagram of a terminal device 600 according to an embodiment of the present application. As shown in FIG6 , the terminal device 600 further includes:

[0404] The first processing module 620 is configured to perform a DRX operation according to the multi-DRX configuration.

[0405] In one embodiment, the first processing module 620 is configured to perform one of the following:

[0406] Perform DRX operation according to each DRX parameter or the value of each DRX parameter;

[0407] Processing is performed on the DRX parameters or values ​​of the DRX parameters of the same function, and a DRX operation is performed.

[0408] Processing is performed on some DRX parameters or values ​​of DRX parameters with the same function, and DRX operations are performed.

[0409] In one embodiment, the first processing module 620 is configured to perform a DRX operation on a service or LCH or QoS flow related to the DRX parameter according to the DRX parameter; or

[0410] According to the value of the DRX parameter, perform DRX operation on the service or LCH or QoS flow related to the value of the DRX parameter; or,

[0411] Perform DRX operation according to DRX parameters, or perform DRX operation for the corresponding MAC entity; or

[0412] According to the value of the DRX parameter, the DRX operation is performed, or the DRX operation is performed on the corresponding MAC entity.

[0413] In one embodiment, the first processing module 620 is configured to:

[0414] A first operation is performed on the DRX parameters or the values ​​of the DRX parameters for the same function, and the DRX operation is performed using the result of the first operation.

[0415] In one embodiment, the first processing module 620 is configured to:

[0416] A first operation is performed on some DRX parameters or values ​​of DRX parameters for the same function, and a DRX operation is performed using a result of the first operation.

[0417] In one embodiment, the first operation includes:

[0418] Take the maximum or minimum value among the DRX parameters for the same function; or,

[0419] Take the maximum or minimum value among the DRX parameters for the same function.

[0420] In one embodiment, the DRX parameter configuration in the multi-DRX configuration is included in one or more of the following information:

[0421] DRX configuration information DRX-config;

[0422] DRX configuration secondary group DRX-configSecondaryGroup;

[0423] MAC-Cell Group Configuration MAC-CellGroupConfig.

[0424] In one embodiment, the different services are associated services, services for multimodality, synchronized services, cooperatively transmitted services, or services with synchronization or coordination requirements;

[0425] Different LCHs are associated LCHs, LCHs for multi-mode, synchronized LCHs, coordinated transmission LCHs, or LCHs with synchronization or coordination requirements;

[0426] DRX is associated DRX, DRX for multi-modality, synchronized DRX, coordinated transmission DRX, or DRX with synchronization or coordination requirements;

[0427] Different QoS flows are associated QoS flows, multimodal QoS flows, synchronized QoS flows, coordinated transmission QoS flows, or QoS flows with synchronization or coordination requirements;

[0428] Different QoS flows are associated PDU sessions, PDU sessions for multimodality, synchronized PDU sessions, coordinated transmission PDU sessions, or PDU sessions with synchronization or coordination requirements;

[0429] The different QoS information is associated QoS information, QoS information for multi-modality, synchronized QoS information, coordinated transmission QoS information, or QoS information with synchronization or coordination requirements.

[0430] The terminal devices 500 and 600 of the embodiments of the present application are capable of implementing the corresponding functions of the terminal devices in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects corresponding to the various modules (sub-modules, units, or components, etc.) in the terminal devices 500 and 600 can be found in the corresponding descriptions in the aforementioned method embodiments and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) in the terminal devices 500 and 600 of the application embodiments can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0431] FIG7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application. The terminal device 700 includes:

[0432] The second processing module 710 is configured to perform a first operation, where the first operation is related to PDCCH monitoring.

[0433] In one embodiment, the second processing module 710 is configured to receive a DRX parameter, where the DRX parameter includes at least one of the following:

[0434] DRX duration timer drx-onDurationTimer;

[0435] DRX slot offset drx-SlotOffset;

[0436] DRX deactivation timer drx-InactivityTimer;

[0437] DRX downlink retransmission timer drx-RetransmissionTimerDL;

[0438] DRX uplink retransmission timer drx-RetransmissionTimerUL;

[0439] DRX long cycle start offset drx-LongCycleStartOffset;

[0440] DRX short cycle drx-ShortCycle;

[0441] DRX short cycle timer drx-ShortCycleTimer;

[0442] DRX downlink HARQ round trip time timer drx-HARQ-RTT-TimerDL;

[0443] DRX uplink HARQ round trip time timer drx-HARQ-RTT-TimerUL;

[0444] Non-integer DRX long cycle;

[0445] The starting offset startoffest corresponding to the non-integer DRX long cycle;

[0446] Non-integer DRX short cycle.

[0447] In one embodiment, the first operation includes the terminal device performing a DRX long-short cycle conversion.

[0448] In one embodiment, the second processing module 710 is configured to perform a first operation when a first condition is met.

[0449] In one embodiment, the first operation includes switching from a DRX long cycle to a DRX short cycle.

[0450] In one embodiment, the second processing module 710 is configured to perform the first operation when the second condition is met.

[0451] In one embodiment, the first operation includes switching from a DRX short cycle to a DRX long cycle.

[0452] FIG8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application. As shown in FIG8 , the terminal device 800 includes:

[0453] The second transceiver module 820 is configured to send first information to the network device, where the first information includes at least one of the following:

[0454] Whether to perform DRX long-short cycle conversion;

[0455] Convert to long or short cycles;

[0456] Recommended DRX cycle configuration.

[0457] In one implementation, the first information is carried by RRC signaling or UL MAC CE or UCI.

[0458] In one embodiment, the first operation includes the terminal device using a predetermined value or configuration for a set DRX parameter.

[0459] In one embodiment, the second processing module 710 is configured to perform a first operation when a first condition is met.

[0460] In one embodiment, the first operation includes using a first value or a first configuration for a set DRX parameter.

[0461] In some implementations, the second processing module 710 is configured to execute the first operation when the second condition is met.

[0462] In one embodiment, the first operation includes using a second value or a second configuration for a set DRX parameter.

[0463] In one embodiment, the set DRX parameters include at least one of the following:

[0464] DRX duration timer drx-onDurationTimer;

[0465] DRX inactivity timer drx-InactivityTimer;

[0466] DRX downlink retransmission timer drx-RetransmissionTimerDL;

[0467] DRX uplink retransmission timer drx-RetransmissionTimerUL;

[0468] DRX short cycle drx-ShortCycle;

[0469] DRX short cycle timer drx-ShortCycleTimer;

[0470] DRX downlink HARQ round trip time timer drx-HARQ-RTT-TimerDL;

[0471] DRX uplink HARQ round trip time timer drx-HARQ-RTT-TimerUL;

[0472] Non-integer DRX long cycle;

[0473] Non-integer DRX short cycle.

[0474] In one embodiment, the second transceiver module 820 is configured to send second information to the network device, where the second information includes at least one of the following:

[0475] Whether to perform DRX parameter value or configuration conversion;

[0476] Converting to a first value or a first configuration;

[0477] a first value or a first configuration;

[0478] Convert to the second value or the second configuration.

[0479] In one embodiment, the second information is carried by RRC signaling or UL MAC CE or UCI.

[0480] In one implementation, the second processing module 710 is configured to receive a PDCCH skip monitoring parameter.

[0481] In one embodiment, the first operation includes: the terminal device performs or skips PDCCH monitoring.

[0482] In one embodiment, the second processing module 710 is configured to perform a first operation when a first condition is met.

[0483] In one embodiment, the first operation includes,

[0484] The terminal device ignores the indication of the PDCCH skip monitoring parameter; and / or,

[0485] The terminal device monitors the PDCCH.

[0486] In one embodiment, the second processing module 710 is configured to perform the first operation when the second condition is met.

[0487] In one embodiment, the first operation includes the terminal device performing a PDCCH skip monitoring operation.

[0488] In one embodiment, the second transceiver module 820 is configured to send third information to the network device, where the third information includes at least one of the following:

[0489] Ignore the indication of PDCCH skip monitoring parameters;

[0490] Ignored time periods or points in time;

[0491] Whether PDCCH skip monitoring operation can be performed;

[0492] A time period or a time point during which a PDCCH skipping monitoring operation may be performed.

[0493] In one implementation, the third information is carried by RRC signaling or UL MAC CE or UCI.

[0494] In one embodiment, the first condition includes one or more of the following:

[0495] Receive network instruction information;

[0496] For multi-modal QoS flow or PDU session or LCH or data packet arrival;

[0497] The associated QoS flow or PDU session or LCH or data packet arrives;

[0498] Synchronous QoS flow or PDU session or LCH or data packet arrival;

[0499] Co-transmitted QoS flow or PDU session or LCH or data packet arrival;

[0500] QoS flows, PDU sessions, LCHs, or data packets with synchronization or coordination requirements arrive;

[0501] A multimodal QoS flow, PDU session, LCH, or data packet starts to be transmitted or is transmitted;

[0502] The associated QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0503] The synchronized QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0504] The coordinated QoS flow or PDU session or LCH or data packet starts to be transmitted or is transmitted;

[0505] A QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements starts to be transmitted or is transmitted;

[0506] The delay of a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to a first threshold;

[0507] The latency of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0508] The delay of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0509] The delay of the coordinated transmission QoS flow, PDU session, LCH, or data packet is less than or equal to the first threshold;

[0510] The delay of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is less than or equal to the first threshold;

[0511] Part of the data for a multimodal QoS flow, PDU session, LCH, or data packet has been transmitted;

[0512] Part of the data of the associated QoS flow or PDU session or LCH or data packet has been transmitted;

[0513] Part of the data of the synchronized QoS flow or PDU session or LCH or data packet has been transmitted;

[0514] Part of the data of the coordinated QoS flow, PDU session, LCH or data packet has been transmitted;

[0515] Part of the data of the QoS flow, PDU session, LCH or data packet that requires synchronization or coordination has been transmitted;

[0516] The amount of data to be transmitted for multimodal QoS flows, PDU sessions, LCHs, or data packets;

[0517] The amount of data to be transmitted for the associated QoS flow, PDU session, LCH, or data packet;

[0518] The amount of data to be transmitted by the synchronized QoS flow, PDU session, LCH or data packet;

[0519] The amount of data to be transmitted for the coordinated QoS flow, PDU session, LCH, or data packet;

[0520] The amount of data to be transmitted for QoS flows, PDU sessions, LCHs, or data packets that require synchronization or coordination;

[0521] The amount of data to be transmitted for the multimodal QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0522] The amount of data to be transmitted of the associated QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0523] The amount of data to be transmitted of the synchronized QoS flow, PDU session, LCH, or data packet is greater than or equal to a second threshold;

[0524] The amount of data to be transmitted of the coordinated QoS flow, PDU session, LCH, or data packet is greater than or equal to the second threshold;

[0525] The amount of data to be transmitted of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is greater than or equal to the second threshold;

[0526] The terminal device has data for a multimodal QoS flow or LCH or data packet in its cache;

[0527] The data of the associated QoS flow or LCH or data packet exists in the cache of the terminal device;

[0528] The terminal device has data of a synchronized QoS flow or LCH or data packet in its cache;

[0529] The terminal device has data of the collaboratively transmitted QoS flow, PDU session, LCH, or data packet in its buffer;

[0530] The buffer of the terminal device contains data of a QoS flow or a PDU session or an LCH or a data packet with synchronization or collaboration requirements.

[0531] In one embodiment, the second condition includes one or more of the following:

[0532] Receive network instruction information;

[0533] The multi-modal QoS flow or PDU session or LCH or data packet is transmitted;

[0534] The associated QoS flow or PDU session or LCH or data packet is transmitted;

[0535] The synchronized QoS flow or PDU session or LCH or data packet is transmitted;

[0536] The coordinated QoS flow or PDU session or LCH or data packet is transmitted;

[0537] The QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements is transmitted;

[0538] The delay of a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0539] The delay of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0540] The delay of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0541] The delay of the coordinated transmission QoS flow, PDU session, LCH, or data packet is less than or equal to the third threshold;

[0542] The delay of QoS flows, PDU sessions, LCHs, or data packets with synchronization or coordination requirements is less than or equal to the third threshold;

[0543] The necessary data for a multimodal QoS flow, PDU session, LCH, or data packet has been transmitted;

[0544] The necessary data in the associated QoS flow or PDU session or LCH or data packet has been transmitted;

[0545] The necessary data in the synchronized QoS flow or PDU session or LCH or data packet has been transmitted;

[0546] The necessary data in the coordinated QoS flow, PDU session, LCH or data packet has been transmitted;

[0547] The necessary data in the QoS flow, PDU session, LCH or data packet with synchronization or coordination requirements has been transmitted;

[0548] For a multimodal QoS flow, PDU session, LCH, or data packet, there is no data to be transmitted or the data packet has been deleted.

[0549] The associated QoS flow, PDU session, LCH, or data packet has no data to be transmitted or has been deleted;

[0550] The synchronized QoS flow, PDU session, LCH, or data packet has no data to be transmitted or has been deleted;

[0551] The QoS flow, PDU session, LCH or data packet of the coordinated transmission has no data to be transmitted or has been deleted;

[0552] The QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements has no data to be transmitted or has been deleted;

[0553] The amount of data to be transmitted for a multimodal QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0554] The amount of data to be transmitted of the associated QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0555] The amount of data to be transmitted of the synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0556] The amount of data to be transmitted of the coordinated QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold;

[0557] The amount of data to be transmitted of the QoS flow, PDU session, LCH, or data packet with synchronization or coordination requirements is less than or equal to the fourth threshold;

[0558] There is no data for the multimodal QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0559] There is no data for the associated QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0560] There is no data of the synchronized QoS flow or PDU session or LCH or data packet in the buffer of the terminal device;

[0561] The terminal device does not have data for the co-transmitted QoS flow, PDU session, LCH, or data packet in its cache;

[0562] There is no data of QoS flow, PDU session, LCH or data packet with synchronization or coordination requirements in the cache of the terminal device.

[0563] In one embodiment, the network indication information includes at least one of the following:

[0564] Whether to perform DRX long-short cycle conversion;

[0565] Convert to long or short cycles;

[0566] Recommended DRX cycle configuration.

[0567] In one embodiment, the network indication information includes at least one of the following:

[0568] Whether to perform DRX parameter value or configuration conversion;

[0569] Converting to a first value or a first configuration;

[0570] a first value or a first configuration;

[0571] In one embodiment, the network indication information includes at least one of the following:

[0572] Ignore the indication of PDCCH skip monitoring parameters;

[0573] Ignored time periods or points in time;

[0574] Whether PDCCH skip monitoring operation can be performed;

[0575] A time period or a time point during which a PDCCH skipping monitoring operation may be performed.

[0576] In one embodiment, the network indication information is at least one of a state transition MAC CE, a DRX command MAC CE, and a DCI carrying specific indication information.

[0577] The terminal devices 700 and 800 of the embodiments of the present application are capable of implementing the corresponding functions of the terminal devices in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects corresponding to the various modules (sub-modules, units, or components, etc.) in the terminal devices 700 and 800 can be found in the corresponding descriptions in the aforementioned method embodiments and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) in the terminal devices 700 and 800 of the application embodiments can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0578] FIG9 is a schematic block diagram of a network device 900 according to an embodiment of the present application. The network device 900 includes:

[0579] The third transceiver module 910 is configured to send a multi-DRX configuration.

[0580] In one embodiment, multiple DRX configurations are used for different purposes or situations, or the multiple DRX configurations are configured for different services or LCHs or QoS flows or QoS information respectively.

[0581] In one embodiment, in the multiple DRX configurations, the same DRX configuration is used for at least one target or situation, or the same DRX configuration is configured for at least one service or LCH or QoS flow or QoS information.

[0582] In one embodiment, the multiple DRX configuration includes multiple configurations for at least one DRX parameter.

[0583] In one implementation, in at least one DRX parameter, the same DRX parameter has multiple values.

[0584] In one embodiment, different values ​​are used for different purposes or situations, or different values ​​are configured for different services or LCHs or QoS flows or QoS information.

[0585] In one embodiment, in a multi-DRX configuration, a DRX configuration for a same function includes multiple DRX parameters.

[0586] In one embodiment, different DRX parameters are used for different purposes or situations, or different DRX parameters are configured for different services or LCHs or QoS flows or QoS information respectively.

[0587] In one embodiment, the DRX parameters in the multi-DRX configuration include at least one of the following:

[0588] DRX duration timer drx-onDurationTimer;

[0589] DRX slot offset drx-SlotOffset;

[0590] DRX inactivity timer drx-InactivityTimer;

[0591] DRX downlink retransmission timer drx-RetransmissionTimerDL;

[0592] DRX uplink retransmission timer drx-RetransmissionTimerUL;

[0593] DRX long cycle start offset drx-LongCycleStartOffset;

[0594] DRX short cycle drx-ShortCycle;

[0595] DRX short cycle timer drx-ShortCycleTimer;

[0596] DRX downlink HARQ round trip time timer drx-HARQ-RTT-TimerDL;

[0597] DRX uplink HARQ round trip time timer drx-HARQ-RTT-TimerUL;

[0598] Non-integer DRX long cycle;

[0599] The starting offset startoffest corresponding to the non-integer DRX long cycle;

[0600] Non-integer DRX short cycle.

[0601] In one embodiment, each DRX parameter is for the same function; and / or,

[0602] Multiple DRX parameters for the same function; and / or,

[0603] All or part of the multiple DRX parameters are used for different purposes or situations, or are configured for different services or LCHs or QoS flows or QoS information respectively.

[0604] In one embodiment, the DRX parameter configuration in the multi-DRX configuration is included in one or more of the following information:

[0605] DRX configuration information DRX-config;

[0606] DRX configuration secondary group DRX-configSecondaryGroup;

[0607] MAC-Cell Group Configuration MAC-CellGroupConfig.

[0608] In one embodiment, the different services are associated services, services for multimodality, synchronized services, cooperatively transmitted services, or services with synchronization or coordination requirements;

[0609] Different LCHs are associated LCHs, LCHs for multi-mode, synchronized LCHs, coordinated transmission LCHs, or LCHs with synchronization or coordination requirements;

[0610] DRX is associated DRX, DRX for multi-modality, synchronized DRX, coordinated transmission DRX, or DRX with synchronization or coordination requirements;

[0611] Different QoS flows are associated QoS flows, multimodal QoS flows, synchronized QoS flows, coordinated transmission QoS flows, or QoS flows with synchronization or coordination requirements;

[0612] Different QoS flows are associated PDU sessions, PDU sessions for multimodality, synchronized PDU sessions, coordinated transmission PDU sessions, or PDU sessions with synchronization or coordination requirements;

[0613] The different QoS information is associated QoS information, QoS information for multi-modality, synchronized QoS information, coordinated transmission QoS information, or QoS information with synchronization or coordination requirements.

[0614] The network device 900 of the embodiment of the present application can implement the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the network device 900 can be found in the corresponding description in the above method embodiment, and will not be repeated here. It should be noted that the functions described in the various modules (sub-module, unit or component, etc.) in the network device 900 of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0615] Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010, which can call and execute a computer program from a memory to enable the communication device 1000 to implement the method in the embodiment of the present application.

[0616] In one embodiment, the communication device 1000 may further include a memory 1020. The processor 1010 may call and execute a computer program from the memory 1020 to enable the communication device 1000 to implement the method in the embodiment of the present application.

[0617] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0618] In one embodiment, the communication device 1000 may further include a transceiver 1030 , and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, the transceiver 1030 may send information or data to other devices, or receive information or data sent by other devices.

[0619] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0620] In one embodiment, the communication device 1000 may be a network device of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0621] In one embodiment, the communication device 1000 may be a terminal device of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0622] 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application. The chip 1100 includes a processor 1110, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0623] In one embodiment, the chip 1100 may further include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

[0624] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0625] In one embodiment, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0626] In one embodiment, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0627] In one embodiment, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0628] In one embodiment, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0629] The chips used in the network device and the terminal device may be the same chip or different chips.

[0630] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0631] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0632] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0633] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0634] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0635] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0636] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0637] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A configuration method, comprising: The terminal device receives a discontinuous reception (DRX) configuration.

2. The method according to claim 1, wherein The multiple DRX configurations are for different targets or situations, or the multiple DRX configurations are respectively configured for different services or logical channels (LCHs) or quality of service (QoS) flows or QoS information.

3. The method according to claim 1 or 2, wherein In the multiple DRX configurations, the same DRX configuration is for at least one target or situation, or the same DRX configuration is configured for at least one service or LCH or QoS flow or QoS information.

4. According to the method of any one of claims 1-3, wherein The multiple DRX configurations include multiple configurations for at least one DRX parameter.

5. The method according to claim 4, wherein, Among the at least one DRX parameter, the same DRX parameter has multiple values.

6. The method according to claim 5, wherein, The different values are for different targets or situations, or the different values are respectively configured for different services or LCHs or QoS flows or QoS information.

7. According to the method according to any one of claims 1-3, wherein, In the multiple DRX configurations, the DRX configurations for the same function include multiple DRX parameters.

8. The method according to claim 7, wherein, The different DRX parameters are for different targets or situations, or the different DRX parameters are respectively configured for different services or LCHs or QoS flows or QoS information.

9. According to the method as claimed in any one of claims 1-8, wherein, The DRX parameters in the multiple DRX configurations include at least one of the following: DRX on-duration timer (drx-onDurationTimer); DRX slot offset (drx-SlotOffset); DRX inactivity timer (drx-InactivityTimer); DRX downlink retransmission timer (drx-RetransmissionTimerDL); DRX uplink retransmission timer (drx-RetransmissionTimerUL); DRX long cycle start offset (drx-LongCycleStartOffset); DRX short cycle (drx-ShortCycle); DRX short cycle timer (drx-ShortCycleTimer); DRX downlink hybrid automatic repeat request (HARQ) round-trip time timer (drx-HARQ-RTT-TimerDL); DRX uplink HARQ round-trip time timer (drx-HARQ-RTT-TimerUL); Non-integer DRX long cycle; Start offset (startoffest) corresponding to the non-integer DRX long cycle; Non-integer DRX short cycle.

10. The method according to claim 9, wherein Each of the DRX parameters is for the same function; and / or The multiple DRX parameters are for the same function; and / or All or some of the multiple DRX parameters are for different targets or situations, or are respectively configured for different services or LCHs or QoS flows or QoS information.

11. The method according to any one of claims 1-10, further comprising that the terminal device performs DRX operations according to the multiple DRX configurations.

12. The method according to claim 11, wherein, The terminal device performing DRX operations according to the multiple DRX configurations includes one of the following: The terminal device performs DRX operations according to each DRX parameter or the value of each DRX parameter; The terminal device processes DRX parameters or the values of DRX parameters for the same function and performs DRX operations; The terminal device processes DRX parameters or the values of DRX parameters for some of the same functions and performs DRX operations. The terminal device processes DRX parameters or the values of DRX parameters for some of the same functions and performs DRX operations.

13. The method according to claim 12, wherein, The terminal device performs DRX operations according to each DRX parameter or the value of each DRX parameter, including: The terminal device performs DRX operations on the service or LCH or QoS flow related to the DRX parameter according to the DRX parameter; or, The terminal device performs DRX operations on the service or LCH or QoS flow related to the value of the DRX parameter according to the value of the DRX parameter; or, The terminal device performs DRX operations according to the DRX parameter, or performs DRX operations on the corresponding MAC entity; or, The terminal device performs DRX operations according to the value of the DRX parameter, or performs DRX operations on the corresponding MAC entity.

14. The method according to claim 12, wherein, The terminal device processes DRX parameters or the values of DRX parameters for the same function and performs DRX operations, including: The terminal device performs a first operation on DRX parameters or the values of DRX parameters for the same function and performs DRX operations using the result of the first operation.

15. The method according to claim 12, wherein, The terminal device processes DRX parameters or the values of DRX parameters for some of the same functions and performs DRX operations, including: The terminal device performs a first operation on some of the DRX parameters or the values of DRX parameters for the same function and performs DRX operations using the result of the first operation.

16. The method according to claim 14 or 15, wherein, The first operation includes: Taking the maximum or minimum value of the DRX parameters for the same function; or, Taking the maximum or minimum value of the values of the DRX parameters for the same function.

17. According to the method as claimed in any one of claims 1-16, wherein, The DRX parameter configuration in the multi-DRX configuration is included in one or more of the following information: DRX configuration information DRX-config; DRX configuration secondary group DRX-configSecondaryGroup; Media access control MAC-cell group configuration MAC-CellGroupConfig.

18. According to the method described in any one of claims 1-17, wherein, The different services are associated services, services for multi-modal, synchronous services, co-transmission services, or services with synchronization or co-transmission requirements; The different LCHs are associated LCHs, LCHs for multi-modal, synchronous LCHs, co-transmission LCHs, or LCHs with synchronization or co-transmission requirements; The DRX is associated DRX, DRX for multi-modal, synchronous DRX, co-transmission DRX, or DRX with synchronization or co-transmission requirements; The different QoS flows are associated QoS flows, QoS flows for multi-modal, synchronized QoS flows, co-transmitted QoS flows, or QoS flows with synchronization or co-operation requirements; The different QoS flows are associated packet data unit (PDU) sessions, PDU sessions for multi-modal, synchronized PDU sessions, co-transmitted PDU sessions, or PDU sessions with synchronization or co-operation requirements; The different QoS information is associated QoS information, QoS information for multi-modal, synchronized QoS information, co-transmitted QoS information, or QoS information with synchronization or co-operation requirements.

19. A control method, comprising: The terminal device performs a first operation, and the first operation is related to the monitoring of the physical downlink control channel (PDCCH).

20. The method according to claim 19, wherein the terminal device performs a first operation, including: The terminal device receives DRX parameters, and the DRX parameters include at least one of the following: DRX on-duration timer (drx-onDurationTimer); DRX slot offset (drx-SlotOffset); DRX inactivity timer (drx-InactivityTimer); DRX downlink retransmission timer (drx-RetransmissionTimerDL); DRX uplink retransmission timer (drx-RetransmissionTimerUL); DRX long cycle start offset (drx-LongCycleStartOffset); DRX short cycle (drx-ShortCycle); DRX short cycle timer (drx-ShortCycleTimer); DRX downlink HARQ round-trip time timer (drx-HARQ-RTT-TimerDL); DRX uplink HARQ round-trip time timer (drx-HARQ-RTT-TimerUL); Non-integer DRX long cycle; Start offset (startoffest) corresponding to the non-integer DRX long cycle; Non-integer DRX short cycle.

21. The method according to claim 19 or 20, wherein, The first operation includes that the terminal device performs DRX long / short cycle conversion.

22. The method according to any one of claims 19-21, wherein, The terminal device performing the first operation includes: when a first condition is met, the terminal device performs the first operation.

23. The method according to claim 22, wherein, The first operation includes converting from a DRX long cycle to a DRX short cycle.

24. The method according to any one of claims 19-21, wherein, The terminal device performing the first operation includes: when a second condition is met, the terminal device performs the first operation.

25. The method according to claim 24, wherein, The first operation includes converting from a DRX short cycle to a DRX long cycle.

26. The method according to any one of claims 19-25, comprising that the terminal device sends first information to the network device, and the first information includes at least one of the following: Whether to perform DRX long / short cycle conversion; Conversion to a long cycle or a short cycle; Recommended DRX cycle configuration.

27. The method according to claim 26, wherein, The first information is carried by radio resource control (RRC) signaling, or an uplink (UL) MAC control element (CE), or uplink control information (UCI).

28. The method according to claim 19 or 20, wherein The first operation includes that the terminal device uses a predetermined value or configuration for the set DRX parameters.

29. The method according to claim 19, 20 or 28, wherein, The terminal device performs a first operation, including: when a first condition is satisfied, the terminal device performs the first operation.

30. The method according to claim 29, wherein The first operation includes using a first value or a first configuration for set DRX parameters.

31. The method according to claim 19, 20 or 28, wherein, The terminal device performs a first operation, including: when a second condition is satisfied, the terminal device performs the first operation.

32. The method according to claim 31, wherein The first operation includes using a second value or a second configuration for set DRX parameters.

33. The method according to claim 28, 30 or 32, wherein, The set DRX parameters include at least one of the following: DRX on-duration timer drx-onDurationTimer; DRX inactivity timer drx-InactivityTimer; DRX downlink retransmission timer drx-RetransmissionTimerDL; DRX uplink retransmission timer drx-RetransmissionTimerUL; DRX short cycle drx-ShortCycle; DRX short cycle timer drx-ShortCycleTimer; DRX downlink HARQ round-trip time timer drx-HARQ-RTT-TimerDL; DRX uplink HARQ round-trip time timer drx-HARQ-RTT-TimerUL; Non-integer DRX long cycle; Non-integer DRX short cycle.

34. The method according to any one of claims 19, 20, 28-33, including that the terminal device sends second information to the network device, and the second information includes at least one of the following: Whether to perform DRX parameter value or configuration conversion; Convert to the first value or the first configuration; The first value or the first configuration; Convert to the second value or the second configuration.

35. The method according to claim 34, wherein the second information is carried by RRC signaling or UL MAC CE or UCI.

36. The method according to claim 19, wherein the terminal device performs a first operation, including: The terminal device receives PDCCH skip monitoring parameters.

37. The method according to claim 19 or 36, wherein The first operation includes: the terminal device performs or skips PDCCH monitoring.

38. The method according to claim 19, 36 or 37, wherein, The terminal device performs a first operation, including: when a first condition is satisfied, the terminal device performs the first operation.

39. The method according to claim 38, wherein, The first operation includes The terminal device ignores the indication of the PDCCH skip monitoring parameter; and / or The terminal device monitors the PDCCH.

40. The method according to claim 19, 36 or 37, wherein The terminal device performs a first operation, including: when a second condition is satisfied, the terminal device performs the first operation.

41. The method according to claim 40, wherein, The first operation includes that the terminal device performs a PDCCH skip monitoring operation.

42. The method according to any one of claims 19, 36-41, including that the terminal device sends third information to the network device, and the third information includes at least one of the following: Indication of ignoring the PDCCH skip monitoring parameter; Ignored time period or time point; Whether the PDCCH skip monitoring operation can be performed; Time period or time point when the PDCCH skip monitoring operation can be performed.

43. The method according to claim 42, wherein, The third information is carried by RRC signaling or UL MAC CE or UCI.

44. The method according to any one of claims 19-43, wherein, The first condition includes one or more of the following: Receive network indication information; Arrival of multi-modal QoS flow or PDU session or LCH or data packet; Arrival of associated QoS flow or PDU session or LCH or data packet; Arrival of synchronized QoS flow or PDU session or LCH or data packet; Arrival of co-transmitted QoS flow or PDU session or LCH or data packet; Arrival of QoS flow or PDU session or LCH or data packet with synchronization or co-transmission requirements; Start or transmission of multi-modal QoS flow or PDU session or LCH or data packet; Start or transmission of associated QoS flow or PDU session or LCH or data packet; Start or transmission of synchronized QoS flow or PDU session or LCH or data packet; Start or transmission of co-transmitted QoS flow or PDU session or LCH or data packet; Start or transmission of QoS flow or PDU session or LCH or data packet with synchronization or co-transmission requirements; The delay of multi-modal QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold; The delay of associated QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold; The delay of synchronized QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold; The delay of co-transmitted QoS flow or PDU session or LCH or data packet is less than or equal to the first threshold; The delay of QoS flow or PDU session or LCH or data packet with synchronization or co-transmission requirements is less than or equal to the first threshold; Part of the data of multi-modal QoS flow or PDU session or LCH or data packet has been transmitted; Part of the data of associated QoS flow or PDU session or LCH or data packet has been transmitted; Part of the data of synchronized QoS flow or PDU session or LCH or data packet has been transmitted; Part of the data of co-transmitted QoS flow or PDU session or LCH or data packet has been transmitted; Part of the data of QoS flow or PDU session or LCH or data packet with synchronization or co-transmission requirements has been transmitted; The amount of data to be transmitted for multi-modal QoS flow or PDU session or LCH or data packet; The amount of data to be transmitted for associated QoS flow or PDU session or LCH or data packet; The amount of data to be transmitted for synchronized QoS flow or PDU session or LCH or data packet; The amount of data to be transmitted for co-transmitted QoS flow or PDU session or LCH or data packet; The amount of data to be transmitted for QoS flow or PDU session or LCH or data packet with synchronization or co-transmission requirements; The amount of data to be transmitted for multi-modal QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold; The amount of data to be transmitted for associated QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold; The amount of data to be transmitted for synchronized QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold; The amount of data to be transmitted for co-transmitted QoS flow or PDU session or LCH or data packet is greater than or equal to the second threshold; The amount of data to be transmitted for a QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements is greater than or equal to a second threshold; There is data in the buffer of the terminal device for a multi-modal QoS flow or LCH or data packet; There is data of an associated QoS flow or LCH or data packet in the buffer of the terminal device; There is data of a synchronized QoS flow or LCH or data packet in the buffer of the terminal device; There is data of a co-transmitted QoS flow or PDU session or LCH or data packet in the buffer of the terminal device; There is data of a QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements in the buffer of the terminal device.

45. The method according to claim 24, 25, 31, 32, 40 or 41, wherein The second condition includes one or more of the following: Receiving network indication information; A multi-modal QoS flow or PDU session or LCH or data packet has been transmitted; An associated QoS flow or PDU session or LCH or data packet has been transmitted; A synchronized QoS flow or PDU session or LCH or data packet has been transmitted; A co-transmitted QoS flow or PDU session or LCH or data packet has been transmitted; A QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements has been transmitted; The latency of a multi-modal QoS flow or PDU session or LCH or data packet is less than or equal to a third threshold; The latency of an associated QoS flow or PDU session or LCH or data packet is less than or equal to a third threshold; The latency of a synchronized QoS flow or PDU session or LCH or data packet is less than or equal to a third threshold; The latency of a co-transmitted QoS flow or PDU session or LCH or data packet is less than or equal to a third threshold; The latency of a QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements is less than or equal to a third threshold; The necessary data in a multi-modal QoS flow or PDU session or LCH or data packet has been transmitted; The necessary data in an associated QoS flow or PDU session or LCH or data packet has been transmitted; The necessary data in a synchronized QoS flow or PDU session or LCH or data packet has been transmitted; The necessary data in a co-transmitted QoS flow or PDU session or LCH or data packet has been transmitted; The necessary data in a QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements has been transmitted; There is no amount of data to be transmitted or the multi-modal QoS flow or PDU session or LCH or data packet has been deleted; There is no amount of data to be transmitted or the associated QoS flow or PDU session or LCH or data packet has been deleted; There is no amount of data to be transmitted or the synchronized QoS flow or PDU session or LCH or data packet has been deleted; There is no amount of data to be transmitted or the co-transmitted QoS flow or PDU session or LCH or data packet has been deleted; There is no amount of data to be transmitted or the QoS flow or PDU session or LCH or data packet with synchronization or coordination requirements has been deleted; The amount of data to be transmitted for a multi-modal QoS flow or PDU session or LCH or data packet is less than or equal to a fourth threshold; The amount of data to be transmitted for an associated QoS flow or PDU session or LCH or data packet is less than or equal to a fourth threshold; The amount of data to be transmitted for a synchronized QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold; The amount of data to be transmitted for a co - transmitted QoS flow, PDU session, LCH, or data packet is less than or equal to a fourth threshold; The amount of data to be transmitted for a QoS flow, PDU session, LCH, or data packet with synchronization or co - operation requirements is less than or equal to a fourth threshold; There is no data in the buffer of the terminal device for a multi - modal QoS flow, PDU session, LCH, or data packet; There is no data in the buffer of the terminal device for an associated QoS flow, PDU session, LCH, or data packet; There is no data in the buffer of the terminal device for a synchronized QoS flow, PDU session, LCH, or data packet; There is no data in the buffer of the terminal device for a co - transmitted QoS flow, PDU session, LCH, or data packet; There is no data in the buffer of the terminal device for a QoS flow, PDU session, LCH, or data packet with synchronization or co - operation requirements.

46. The method according to claim 44 or 45, wherein, The network indication information includes at least one of the following: Whether to perform DRX long - short cycle conversion; Convert to a long cycle or a short cycle; Recommended DRX cycle configuration.

47. The method according to claim 44 or 45, wherein, The network indication information includes at least one of the following: Whether to perform DRX parameter value or configuration conversion; Convert to a first value or a first configuration; The first value or the first configuration; Convert to a second value or a second configuration.

48. The method according to claim 44 or 45, wherein, The network indication information includes at least one of the following: Ignore the indication of the PDCCH skip listening parameter; The ignored time period or time point; Whether the PDCCH skip listening operation can be performed; The time period or time point when the PDCCH skip listening operation can be performed.

49. The method according to any one of claims 44, 45 - 48, wherein, The network indication information is at least one of a status - conversion MAC CE, a DRX - command MAC CE, and a DCI carrying specific indication information.

50. A configuration method, comprising: A network device sends a multi - DRX configuration.

51. The method according to claim 50, wherein, The multi - DRX configuration is for different targets or situations, or the multi - DRX configuration is configured separately for different services, LCHs, QoS flows, or QoS information.

52. The method according to claim 50 or 51, wherein In the multi - DRX configuration, the same DRX configuration is for at least one target or situation, or the same DRX configuration is configured for at least one service, LCH, QoS flow, or QoS information.

53. The method according to any one of claims 50 - 52, wherein The multi - DRX configuration includes multiple configurations for at least one DRX parameter.

54. The method according to claim 53, wherein Among the at least one DRX parameter, the same DRX parameter has multiple values.

55. The method according to claim 54, wherein, The different values are for different targets or situations, or the different values are configured separately for different services, LCHs, QoS flows, or QoS information.

56. According to the method of any one of claims 50 - 52, wherein, In the multi - DRX configuration, the DRX configuration for the same function includes multiple DRX parameters.

57. The method according to claim 56, wherein, The different DRX parameters are for different targets or situations, or the different DRX parameters are configured separately for different services, LCHs, QoS flows, or QoS information.

58. The method according to any one of claims 50 - 57, wherein The DRX parameters in the multi - DRX configuration include at least one of the following: The DRX duration timer drx - onDurationTimer; DRX slot offset drx-SlotOffset; DRX inactivity timer drx-InactivityTimer; DRX downlink retransmission timer drx-RetransmissionTimerDL; DRX uplink retransmission timer drx-RetransmissionTimerUL; DRX long cycle start offset drx-LongCycleStartOffset; DRX short cycle drx-ShortCycle; DRX short cycle timer drx-ShortCycleTimer; DRX downlink HARQ round-trip time timer drx-HARQ-RTT-TimerDL; DRX uplink HARQ round-trip time timer drx-HARQ-RTT-TimerUL; Non-integer DRX long cycle; Start offset corresponding to the non-integer DRX long cycle startoffest; Non-integer DRX short cycle.

59. The method according to claim 58, wherein, Each of the DRX parameters is for the same function; and / or, Multiple of the DRX parameters are for the same function; and / or, All or some of the multiple DRX parameters are used for different objectives or situations, or are configured separately for different services or LCH or QoS flows or QoS information.

60. The method according to any one of claims 50 - 59, wherein, The DRX parameter configuration in the multi-DRX configuration is included in one or more of the following information: DRX configuration information DRX-config; DRX configuration secondary group DRX-configSecondaryGroup; MAC-cell group configuration MAC-CellGroupConfig.

61. The method according to any one of claims 50-60, wherein, The different services are associated services, services for multi-modal, synchronous services, co-transmission services, or services with synchronization or co-transmission requirements; The different LCHs are associated LCHs, LCHs for multi-modal, synchronous LCHs, co-transmission LCHs, or LCHs with synchronization or co-transmission requirements; The DRX is an associated DRX, a DRX for multi-modal, a synchronous DRX, a co-transmission DRX, or a DRX with synchronization or co-transmission requirements; The different QoS flows are associated QoS flows, QoS flows for multi-modal, synchronous QoS flows, co-transmission QoS flows, or QoS flows with synchronization or co-transmission requirements; The different QoS flows are associated PDU sessions, PDU sessions for multi-modal, synchronous PDU sessions, co-transmission PDU sessions, or PDU sessions with synchronization or co-transmission requirements; The different QoS information is associated QoS information, QoS information for multi-modal, synchronous QoS information, co-transmission QoS information, or QoS information with synchronization or co-transmission requirements.

62. A terminal device, comprising: A first transceiver module, configured to receive a multi-DRX configuration.

63. A terminal device, comprising: A second processing module, configured to perform a first operation, where the first operation is related to PDCCH monitoring.

64. A network device, comprising: A third transceiver module, configured to receive a multi-DRX configuration.

65. A terminal device, comprising: A transceiver, a processor, and a memory, where the memory is configured to store a computer program, the transceiver is configured to communicate with other devices, and the processor is configured to call and run the computer program stored in the memory, so that the terminal device performs the method according to any one of claims 1 to 18 or 19 to 49.

66. A network device, comprising: A transceiver, a processor, and a memory, where the memory is configured to store a computer program, the transceiver is configured to communicate with other devices, and the processor is configured to call and run the computer program stored in the memory, so that the network device performs the method according to any one of claims 50 to 61.

67. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device installed with the chip performs the method according to any one of claims 1 to 18, 19 to 49, or 50 to 61.

68. A computer-readable storage medium, configured to store a computer program, where when the computer program is run by a device, the device performs the method according to any one of claims 1 to 18, 19 to 49, or 50 to 61.

69. A computer program product, comprising computer program instructions, where the computer program instructions cause a computer to perform the method according to any one of claims 1 to 18, 19 to 49, or 50 to 61.

70. A computer program, where the computer program causes a computer to perform the method according to any one of claims 1 to 18, 19 to 49, or 50 to 61.

Images