Method for configuring discontinuous reception in connected state, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a method for configuring discontinuous reception in a connected state, and a terminal and a network-side device. The method for configuring discontinuous reception in a connected state in the embodiments of the present application comprises: a first user equipment (UE) sending first request information to a network-side device, wherein the first request information is used for requesting the network-side device to adjust a DRX active time in a connected state.

Description

Configuration method, terminal and network side equipment for connected state discontinuous reception

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on September 12, 2023, with application number 202311176437.6 and invention name “Configuration method, terminal and network side device for connected state discontinuous reception”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a configuration method, terminal and network-side device for connected state discontinuous reception. Background Art

[0004] In related technologies, a discontinuous reception (DRX) mechanism has been introduced to reduce terminal energy consumption. This mechanism utilizes the intermittent arrival of data packets to allow user equipment (UE) to enter a sleep mode when there is no data.

[0005] However, for terminal devices, when communicating based on the DRX mechanism configured by network-side devices, there may be problems such as limited energy saving effects during the DRX implementation process due to reasons such as the DRX configuration not matching the terminal devices' own needs.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a configuration method for connected discontinuous reception, a terminal, and a network-side device, which can solve the problem of limited energy saving effect of the terminal.

[0008] In a first aspect, a method for configuring connected state discontinuous reception is provided, comprising: a first terminal UE sends a first request message to a network side device, wherein the first request message is used to request the network side device to adjust the connected state DRX activity time.

[0009] In a second aspect, a configuration method for connected state discontinuous reception is provided, including: a network side device receives a first request message sent by a first terminal UE, wherein the first request message is used to request the network side device to adjust the connected state DRX activity time.

[0010] In a third aspect, a configuration device for connected state discontinuous reception is provided, including: a sending module for sending a first request message to a network side device, wherein the first request message is used to request the network side device to adjust the connected state DRX activity time.

[0011] In a fourth aspect, a configuration device for connected state discontinuous reception is provided, including: a receiving module for receiving a first request message sent by a first terminal UE, wherein the first request message is used to request the network side device to adjust the connected state DRX activity time.

[0012] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0013] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect.

[0014] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0015] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the steps of the method described in the second aspect.

[0016] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0017] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0018] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0019] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0020] In an embodiment of the present application, the first UE sends a first request message to the network side device to request the network side device to adjust the connection state DRX activity time, thereby enabling the connection state DRX configuration configured for the first UE to meet the needs of the first UE, thereby further improving the energy saving effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1a is a schematic structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.

[0022] FIG1b is a schematic diagram of DCP monitoring timing provided by an exemplary embodiment of the present application.

[0023] FIG2 is a flowchart of a method for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0024] FIG3 is a second flowchart of a method for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0025] FIG4 is a third flowchart of a method for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0026] FIG5 is a fourth flowchart of a method for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0027] FIG6 is a fourth flowchart of a method for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0028] FIG. 7 is a schematic diagram showing a first structure of a device for configuring connected discontinuous reception according to an exemplary embodiment of the present application.

[0029] FIG8 is a second structural diagram of a device for configuring connected discontinuous reception provided by an exemplary embodiment of the present application.

[0030] FIG9 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.

[0031] FIG10 is a schematic structural diagram of a terminal provided by an exemplary embodiment of the present application.

[0032] FIG11 is a schematic structural diagram of a network-side device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0034] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0035] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0036] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0037] FIG1a shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0038] In addition, to facilitate the understanding of this solution, several technical features involved in this application are introduced here, as follows.

[0039] (1) Multi-card terminal

[0040] Currently, there are not only single-card terminals but also dual-card or multi-card terminals on the market, collectively referred to as multi-card terminals.

[0041] A multi-card terminal can contain multiple UEs, which are called multiple universal subscriber identification module (MUSIM) UEs. Among them, UE can be considered as a contracting entity, such as a terminal device can be configured with multiple contracting entities. The contracting entity can be reflected by a user identification module (Universal Subscriber Identity Module, SIM) card. One SIM card corresponds to the contracting entity of one network. The SIM card stores the identifier of the contracting entity, that is, the identifier of the UE, such as the user identity identifier (SUPI) or the international mobile subscription identity (IMSI). That is, when multiple SIM cards are inserted into a terminal or multiple electronic SIM card information is configured, the terminal and different contracting entities can constitute different UEs.

[0042] Among them, one feature of multi-card terminals is that they can reside on multiple networks at the same time, but the implementation methods of multi-card terminals are different. Some terminals can send and receive on multiple networks simultaneously without affecting each other. The capabilities of multi-card terminals can be single-send and single-receive, single-send and dual-receive, and dual-send and dual-receive.

[0043] (2) Connected Discontinuous Reception (C-DRX)

[0044] In connected mode or connected state, the purpose of using DRX is to save power or energy. For example, a terminal in DRX state does not need to continuously monitor the control channel. However, considering that the terminal does not monitor the control channel for a long time, once data arrives, the data transmission delay will increase. Therefore, in order to balance power saving and transmission delay, the 5G Media Access Control (MAC) supports two DRX cycles, namely DRX long cycle and DRX short cycle, according to the length of time the terminal monitors the channel. Among them, if the terminal data volume is predicted to arrive frequently or the service is sensitive to delay, the network side can configure the terminal to use DRX short cycle; if the terminal data volume is predicted to be sparse and not sensitive to delay, the network can configure the terminal to use DRX long cycle.

[0045] In addition, in order to facilitate the terminal to switch between the DRX long cycle and the DRX short cycle, the related art requires that the DRX long cycle is an integer multiple of the DRX short cycle, so as to ensure that the on-duration of the two is aligned.

[0046] (2) DCP signal

[0047] In 5G systems, a wake-up signal (WUS) based on the physical downlink control channel (PDCCH) is introduced to further improve terminal power conservation. The WUS notifies the terminal whether it needs to monitor the PDCCH during a specific DRX onDuration period. When there is no data, the terminal does not need to monitor the PDCCH during the onDuration period, effectively allowing the terminal to remain in sleep mode throughout the entire DRX long cycle, further saving power.

[0048] The WUS signal is a downlink control signal (DCI), which can be called DCI with cyclic redundancy check scrambled by Power Saving Radio Network Temporary Identifier (DCP). The PS-RNTI is the RNTI assigned by the network to the terminal specifically for power saving features. The DCI scrambled with this RNTI carries the network-side device's wake-up / sleep indication to the terminal. For example, as shown in Figure 1b, the DCP can be used to indicate whether the terminal should monitor the next DRX ON (DRX onduration).

[0049] DCP Configuration: DCP can be configured in the primary cell (PCell) or primary / secondary cell (PSCell). The corresponding PDCCH has its own DCI format, such as DCI format 2_6. DCP is configured per bandwidth part (BWP). Long-cycle DRX can be configured with DCP, but short-cycle DRX cannot.

[0050] DCP monitoring: Before DRX ON, the terminal can monitor the DCP PDCCH from the configured PS_offset until the end of the configured monitoring range. PS_offset is the offset of the DCP start time relative to the start time of the DRX monitoring duration timer (drx-onDurationTimer) corresponding to the DRX long cycle, that is, the offset based on DRX ON, in milliseconds.

[0051] Based on this, the technical solutions provided by the embodiments of the present application are described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0052] FIG2 is a flow chart illustrating a method 200 for configuring connected discontinuous reception according to an exemplary embodiment of the present application. The method 200 may be, but is not limited to, performed by a first UE, and may specifically be performed by hardware or software installed in the first UE. In this embodiment, the method 200 may include at least the following steps.

[0053] S210: The first UE sends first request information to a network-side device.

[0054] The first UE may be any one of the multi-card terminals or a single-card terminal, which is not limited here.

[0055] Compared with the situation in the related art where DRX configuration is performed by the network side device, in this embodiment, the adjustment of the connected state DRX active time (Active time) is achieved by sending a first request information to the network side device by the first UE, so that the DRX configuration meets the needs of the first UE to achieve energy saving effect.

[0056] In an embodiment of the present application, the first request information is used to request the network side device to adjust the DRX activity time of the connected discontinuous reception. In one implementation method, the first request information can be used to directly request the network side device to adjust the DRX activity time of the configured DRX configuration, such as extending, shortening, advancing or postponing the DRX activity time of the first UE (or the second UE); or the first request information can be used to request the network side device to configure a connected DRX configuration that meets its needs or preferences for the first UE to achieve the adjustment of the DRX activity time, such as the first request information is used to request the network side device to configure the connected DRX, request the network side device to update or adjust the configuration information of the connected DRX, or provide the network side device with the DRX configuration preferred by the first UE, etc., so that the network side device can configure the connected DRX configuration that meets its needs or preferences for the first UE. Therefore, by adjusting the connected DRX activity time in the above-mentioned different ways, the DRX configuration can meet the needs or preferences of the first UE, such as aligning or making the DRX activity time of the first UE the same as the DRX activity time of the second UE that shares terminal resources (such as physical layer resources, radio frequency resources), thereby ensuring energy saving.

[0057] For example, taking the case where multiple UEs in a multi-card terminal may share terminal resources (such as physical layer resources, radio frequency resources) as an example, in the related art, if the connection state DRX of each UE works independently, then for the entire system of the multi-card terminal, the terminal energy saving effect is limited. However, in the present application, by sending the first request information, the connection state DRX active time of the first UE can be made to meet its needs or preferences, such as being the same / similar to the DRX configuration or DRX active time of the second UE that shares the terminal resources (such as physical layer resources, radio frequency resources, etc.), thereby making the second UE also in the DRX active time when the first UE is in the DRX active time, or in the DRX inactive time when the first UE is in the DRX inactive time, the second UE is also in the DRX inactive time, effectively avoiding the problem of limited energy saving effect of the entire system of the multi-card terminal caused by the first UE being in the DRX active time and the second UE being in the DRX inactive time in the related art.

[0058] In some embodiments, the aforementioned "preferred DRX configuration" may also be understood as the DRX configuration expected or requested by the first UE, etc. The DRX configuration expected or requested by the first UE may be understood as the DRX configuration that the first UE expects or requests the network side device to configure for the first UE.

[0059] In addition, the first UE and the second UE described in this embodiment may, but are not limited to, belong to the same multi-card terminal. For example, the first UE and the second UE may belong to the same DRX UE group or have an associated relationship.

[0060] In particular, when the first UE and the second UE belong to the same multi-card terminal, the second UE may be one or more UEs other than the first UE in the multi-card terminal to which the first UE belongs, and the first UE and the second UE share resources of the multi-card terminal (such as physical layer resources and radio frequency resources). In addition, in the case where the first UE and the second UE belong to the same multi-card terminal, the first UE may correspond to a first contract or a first SIM card, and the second UE may correspond to a second contract or a second SIM card, without limitation herein.

[0061] In other embodiments, when the first UE sends the first request information, the first request information may be carried by at least one of a UE Assistance Information message, an RRC Reconfiguration Complete message, and an RRC Resume Request message.

[0062] Of course, after receiving the first request information sent by the first UE, the network side device may send first configuration information to the first UE according to the first request information, so that the first UE can adjust the DRX active time.

[0063] Optionally, corresponding to the first request information, the first configuration information may also be carried in at least one of an RRC reconfiguration message and an RRC recovery message, which is not limited here.

[0064] It is worth noting that in this embodiment, after the first UE requests the network-side device to adjust the connected state DRX active time by sending a first request message, the network-side device may adjust the DRX active time of the first UE to meet the needs or preferences of the first UE, or may adjust the DRX active time of the second UE to meet the needs or preferences of the first UE. Of course, the first UE and the second UE may belong to the same multi-card terminal, or may belong to the same DRX UE group or have an associated relationship, etc., which is not limited here.

[0065] In this embodiment, the first UE sends a first request message to the network side device to request the network side device to adjust the connected state DRX activity time, thereby enabling the connected state DRX configuration configured for the first UE to meet the needs of the first UE, thereby further improving the energy saving effect.

[0066] FIG3 is a flow chart of a method 300 for configuring connected discontinuous reception according to an exemplary embodiment of the present application. The method 300 may be, but is not limited to, performed by a first UE, and may specifically be performed by hardware or software installed in the first UE. In this embodiment, the method 300 may include at least the following steps.

[0067] S310: The first UE sends first request information to a network-side device.

[0068] The first request information is used to request the network side device to adjust the connected state DRX activity time.

[0069] It can be understood that the implementation process of S310 can refer to the relevant description in the aforementioned method embodiment 200. Of course, in this embodiment, in addition to referring to the relevant description in the aforementioned method embodiment 200, in some embodiments, in the case of requesting the network-side device to configure a connected DRX configuration that meets its needs or preferences for the first UE through the first request information to adjust the DRX active time, the first request information may include at least one of the DRX configuration preferred by the first UE, the second indication information, and the identifier of the second UE.

[0070] The preferred DRX configuration of the first UE may be used by the network side device to configure a DRX configuration that meets the requirements or preferences of the first UE. In this embodiment, the preferred DRX configuration may include but is not limited to at least one of the following 1)-11).

[0071] 1) A preferred connected state DRX long cycle (longDRX-Cycle), which is used by the network-side device to configure a DRX long cycle that meets the requirements of the first UE, such as relevant parameters of the DRX long cycle.

[0072] 2) The preferred connected DRX start offset value (drx StartOffset Preference) is used to request the network-side device to configure the start offset values ​​of the DRX long cycle and the DRX short cycle.

[0073] In some embodiments, the DRX long cycle start offset parameter (drx-LongCycleStartOffset Preference) may be used to request the network side device to configure the preferred DRX long cycle and DRX start offset value, which is not limited here.

[0074] 3) A preferred connected DRX short cycle (drx-ShortCycle), which is used by the network-side device to configure a DRX short cycle that meets the requirements of the first UE, such as relevant parameters of the DRX short cycle.

[0075] 4) The preferred connected DRX duration is a timeslot offset relative to the subframe start point. The DRX duration may also be referred to as the DRX onDuration. The timeslot offset may be an integer multiple of 1 / 32 milliseconds.

[0076] 5) Preferred connected state DRX short cycle timer (drx-ShortCycleTimer), used to request the network side device to configure the duration of the DRX short cycle used by the first UE, the unit is an integer, that is, the length of the DRX short cycle timer is an integer multiple of the DRX short cycle.

[0077] 6) Preferred connected state DRX continuous monitoring timer (drx-onDurationTimer). During the operation of the DRX continuous monitoring timer, the first UE needs to continuously monitor the PDCCH control channel, that is, the DRX continuous monitoring timer is used to indicate the duration of the first UE monitoring the PDCCH control channel within a DRX cycle.

[0078] 7) Preferred connected-state DRX inactivity timer (drx-InactivityTimer). The DRX inactivity timer indicates the duration of PDCCH monitoring after receiving a new PDCCH. In this embodiment, the DRX inactivity timer starts or restarts at the first symbol after the reception of the new (UL or DL) PDCCH is completed.

[0079] And the DRX inactivity timer stops when a DRX command is received. The DRX command may be a Medium Access Control Control Element (MAC CE) or the like.

[0080] 8) Preferred DRX downlink hybrid automatic repeat request round trip time timer (drx-HARQ-RTT-TimerDL): The DRX downlink hybrid automatic repeat request round trip time timer is configured according to the HARQ process granularity and is used to indicate the minimum time interval for waiting for downlink retransmission.

[0081] In some embodiments, the drx-HARQ-RTT-TimerDL is started at the first symbol after the positive acknowledgment (ACK) / negative acknowledgment (NACK) is sent. During the operation of the drx-HARQ-RTT-TimerDL, the corresponding MAC does not monitor the PDCCH, and when the drx-HARQ-RTT-TimerDL times out, the drx-RetransmissionTimerDL of the corresponding HARQ process is started.

[0082] 9) Preferred DRX uplink hybrid automatic repeat request round trip time timer (drx-HARQ-RTT-TimerUL): The DRX uplink hybrid automatic repeat request round trip time timer is configured according to the HARQ process granularity and represents the minimum time interval for waiting for uplink retransmission.

[0083] In some embodiments, the drx-HARQ-RTT-TimerUL is started at the first symbol after the ACK / NACK is sent. During the operation of the drx-HARQ-RTT-TimerUL, the corresponding MAC does not monitor the PDCCH, and when the drx-HARQ-RTT-TimerUL times out, the drx-HARQ-RTT-TimerUL of the corresponding HARQ process is started.

[0084] 10) Preferred DRX downlink retransmission timer (drx-RetransmissionTimerDL). The DRX downlink retransmission timer is configured based on the HARQ process granularity and indicates the maximum number of PDCCH slots that the UE needs to continuously monitor to receive the desired downlink retransmission data. In this embodiment, the DRX downlink retransmission timer starts at the first symbol after the drx-HARQ-RTT-TimerDL expires and stops when a PDCCH indicating a downlink retransmission is received.

[0085] 11) Preferred DRX uplink retransmission timer (drx-RetransmissionTimerUL). The DRX uplink retransmission timer is configured based on the HARQ process granularity and indicates the maximum number of PDCCH slots that the UE monitors to receive an uplink retransmission grant. In this embodiment, the timer starts at the first symbol after the drx-HARQ-RTT-TimerUL expires and stops when an uplink retransmission grant is received.

[0086] It can be understood that through the request of one or more preferred DRX configurations in the aforementioned 1)-11), the network side device can configure (or update) DRX for the first UE according to the DRX configuration preferred by the first UE, so that the configured DRX configuration meets the preferences or requirements of the first UE, such as being aligned or identical with the DRX configuration of the second UE, so that the DRX active time overlaps as much as possible, thereby maximizing the duration of the DRX inactive time and supporting terminal system energy saving.

[0087] For example, if the first UE and the second UE belong to the same multi-card terminal, then by satisfying the preference or needs of the first UE, the DRX active time of the first UE and the second UE can overlap as much as possible, which can help maximize the duration of the DRX inactive time of the multi-card terminal. For example, the duration of the DRX inactive time of the multi-card terminal is the intersection of the DRX inactive time of the first UE and the DRX inactive time of the second UE.

[0088] The second indication information is used to indicate the reason or purpose for initiating the first request information. Thus, the network side device can understand the reason or purpose for the first UE to send the first request information, thereby achieving efficient configuration of the DRX.

[0089] For example, if the initiation cause or purpose includes a multi-SIM cause (MUSIM cause) or purpose (purpose), the network side device can align the DRX configurations of UEs belonging to the same multi-SIM terminal, such as the DRX active time.

[0090] The identifier of the second UE is used to request the network side device to configure the connected state DRX for the first UE with reference to the connected state DRX configuration of the second UE, so that the configured DRX configuration of the first UE is aligned or the same as the DRX configuration of the second UE, or the DRX activity time overlaps as much as possible.

[0091] It is worth noting that if the first UE and the second UE belong to the same multi-card terminal, then by meeting the preferences or needs of the first UE, the DRX active time can be overlapped as much as possible, which is conducive to maximizing the duration of the DRX inactive time of the multi-card terminal. For example, the duration of the DRX inactive time of the multi-card terminal is the intersection of the DRX inactive time of the first UE and the DRX inactive time of the second UE.

[0092] Of course, in some embodiments, in addition to the aforementioned DRX configuration, the first request information may also include DCP configuration information preferred by the first UE. The preferred DCP configuration information includes a preferred first offset value (PS_Offset), which is the offset value of the DCP start time relative to the start time of the DRX continuous listening timer. This allows the DCP positions of UEs with shared resources to be aligned or identical, thereby maximizing overlap of DRX active times, thereby maximizing the duration of inactive time and supporting energy conservation in the terminal system. The unit of the offset value may be time slots.

[0093] For example, if both the first UE and the second UE are configured with DCP, then the first UE can provide the preferred DCP configuration information to the network-side device, so that the network-side device can configure the same or similar PS_Offset for the first UE as that for the second UE, thereby enabling the first UE and the second UE to monitor the DCP signal within the same or similar time. Of course, if neither the first UE nor the second UE is awakened, neither the first UE nor the second UE needs to monitor the PDCCH during the onDuration period and enters a dormant state, thereby maximizing the dormant time for the entire multi-card terminal and achieving maximum energy saving.

[0094] In some embodiments, the first UE may further receive fourth indication information sent by the network-side device; wherein the fourth indication information is used to indicate whether the first UE is allowed to send the first request information. In other words, the fourth indication information can be understood as on / off information. In this embodiment, the sending of the fourth indication information can avoid wasting resources due to sending invalid information when the sending of the first request information is not allowed.

[0095] In some embodiments, in order to ensure the feasibility of the configuration of the connected DRX, the first UE and the second UE may reside in the same operator network, reside in the same public land mobile network (PLMN) or be located in the same service cell, etc., without any restriction here.

[0096] In this embodiment, through configuration negotiation during independent configuration of connected DRX, the configured DRX configuration can meet the preferences or needs of the first UE, thereby achieving adjustment of the connected DRX active time. Especially when the first UE and the second UE belong to the same multi-card terminal, the duration of the DRX inactive time of the multi-card terminal can also be maximized, solving the problem of limited energy saving effects in related technologies.

[0097] FIG4 is a flow chart of a method 400 for configuring connected discontinuous reception according to an exemplary embodiment of the present application. The method 400 may be, but is not limited to, performed by a first UE, and may specifically be performed by hardware or software installed in the first UE. In this embodiment, the method 400 may include at least the following steps.

[0098] S410: The first UE sends first request information to a network-side device.

[0099] The first request information is used to request the network side device to adjust the connected state DRX activity time.

[0100] It can be understood that the implementation process of S410 can refer to the relevant descriptions in the aforementioned method embodiments 200-300. Of course, in this embodiment, in addition to referring to the relevant descriptions in the aforementioned method embodiments 200-300, in some embodiments, the situation of directly requesting the network side device to adjust the DRX active time of the configured DRX configuration through the first request information can be understood as: the first UE can request the network side device to adjust the connected state DRX active time through the first request information after the network side device has configured the DRX configuration. Among them, the DRX method configured by the network side can be a conventional method or as shown in the aforementioned method embodiment 300, which is not limited here.

[0101] Of course, for the situation where the network side device is requested to adjust the connected DRX activity time through the first request information, in this embodiment, the first request information may include at least one of the identifier of the second UE, the first information, the second information, the third information, and the first indication information.

[0102] The identifier of the second UE is used by the network-side device to establish an association relationship between the first UE and the second UE. The associated UEs may have the same DRX activity time, or the DRX activity time of the first UE may be adjusted with reference to the DRX activity time of the second UE, such as by delaying or advancing the time.

[0103] The first information is used to request establishment of a DRX UE group, wherein UEs in one DRX UE group have the same DRX active time.

[0104] It is worth noting that, compared with the DRX group in the related art, which is relative to one UE, in this embodiment, the DRX UE group is relative to multiple UEs, and multiple UEs in the DRX UE group can share a set of DRX parameters, such as drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycl, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL and other DRX parameters.

[0105] Optionally, in some embodiments, the multi-card terminals to which the first UE belongs may share a DRX UE group.

[0106] The second information is used to request the network-side device to associate the DRX activity time of the first UE and the second UE, wherein the first UE and the second UE having the associated relationship have the same DRX activity time. Optionally, the second UE can be indicated by the identifier of the second UE, or the second UE is a UE that has established an association relationship with the first UE before sending the first request, etc., which is not limited here.

[0107] The third information is used to request the network-side device to adjust the DRX active time of the first UE to be the same as the DRX active time of the second UE, such as by extending, shortening, or advancing the DRX active time of the first UE to be the same as the DRX active time of the second UE. The second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group.

[0108] The first indication information is used to indicate the reason or purpose for initiating the first request information, for example, the reason or purpose for initiating includes a multi-card reason or purpose; or, the first indication information can also be used to indicate the multi-card terminal resource sharing to which the first UE belongs, thereby enabling the network side device to align the DRX activity time of UEs belonging to the same multi-card terminal.

[0109] In this case, as a possible implementation manner, the first UE and the second UE that are associated with each other or belong to the same DRX UE group or have the same DRX activity time also satisfy at least one of the following 1)-5).

[0110] 1) The first UE and the second UE share a DRX inactivity timer, thereby enabling the DRX cycles of the first UE and the second UE to overlap, that is, the DRX activity time overlaps, etc., thereby further maximizing the DRX inactivity time and maximizing the energy saving effect.

[0111] 2) When the second UE is in DRX active time, the first UE is also in DRX active time. That is, the state of DRX active time is defined. For example, if the first UE and the second UE belong to the same multi-SIM terminal, then the DRX active time of the first UE and the second UE is the sum of the two, i.e., the DRX active time of the multi-SIM terminal is merged. This can reduce data transmission delays and maximize UE resource utilization.

[0112] 3) When the second UE is in DRX active time and the first UE needs to enter DRX inactive time, the first UE waits for a predetermined period before entering DRX inactive time, or the first UE and the second UE enter DRX inactive time simultaneously. In other words, the first UE maintains its current state definition but changes the state transition timing, thereby reducing data transmission delays and maximizing UE resource utilization.

[0113] Optionally, the predetermined duration may be determined by a protocol agreement, a high-level configuration, or a network-side configuration, or may be determined by the terminal according to the drx-InactivityTimer, such as the predetermined duration being equal to the running duration of the drx-InactivityTimer, or the predetermined duration being the duration from the current moment to the next start of the drx-InactivityTimer, which is not limited here.

[0114] 4) When the second UE is in the DRX active time, the first UE in the DRX inactive time monitors the network control channel or sends an uplink request. Thus, the definition of the DRX inactive time behavior of the first UE and the second UE is realized, which can reduce the delay of data transmission and maximize the utilization of UE resources.

[0115] 5) When the first UE and the second UE are in the same serving cell and the first UE is configured with DRX, the DRX activity time of the first UE and the second UE is the same.

[0116] That is, for multi-card terminals, through the configurations 1)-5) above, since the terminal resources in the multi-card terminal are shared, as long as one of the UEs is in the DRX active time, the shared terminal resources must remain in an active state, so that other UEs are still able to monitor the network scheduling or send uplink requests, which is conducive to reducing data transmission delays and maximizing the utilization of UE resources.

[0117] For example, for a multi-SIM terminal, when a UE is in DRX active time, even if other UEs temporarily have no data transmission and can enter DRX inactive time, they can still be regarded as being in DRX active time and support data transmission, effectively reducing data transmission delay.

[0118] In some embodiments, for the sending of the aforementioned first request information, the first request information can be carried in at least one of the UE auxiliary information message, RRC reconfiguration completion message, RRC recovery request message, RRC establishment request, registration request (Registration Request) message, registration update (Registration Update) message, attachment request (Attach Request) message, reattachment request (Reattach Request) message, and tracking area update request (Tracking Area Update Request) message for sending.

[0119] S420: Receive first configuration information sent by the network-side device.

[0120] The first configuration information corresponds to the first request information, which may include but is not limited to at least one of the following 1)-4).

[0121] 1) First confirmation information, used to indicate that establishment of the DRX UE group is complete.

[0122] 2) The third indication information is used to instruct the network side device to associate or adjust the DRX active time of the multi-card terminal to which the first UE belongs, so that the DRX active time of the UE belonging to a multi-card terminal is similar or the same.

[0123] 3) The second confirmation information is used to instruct the multi-SIM terminals to which the first UE belongs to share resources, that is, the network side device aligns the DRX activity time of each UE that shares resources.

[0124] 4) The identifier of the second UE is used to indicate a UE having the same DRX active time as the first UE.

[0125] In this embodiment, the aforementioned first UE and second UE may belong to the same multi-card terminal. For example, the second UE may be one or more UEs other than the first UE in the multi-card terminal to which the first UE belongs.

[0126] In addition, the first UE and the second UE may reside in the same operator network, reside in the same public land mobile network PLMN, be located in the same serving cell, etc., thereby ensuring the feasibility of the configuration of the connected DRX

[0127] In one embodiment, when a first condition is met, the first UE sends a first request message to the network side device, wherein the first condition includes at least one of the following: the first UE and the second UE can also reside in the same operator network; the first UE and the second UE reside in the same public land mobile network PLMN; the first UE and the second UE are located in the same service cell.

[0128] In some embodiments, similar to the aforementioned method embodiment 300, the first UE may also receive fourth indication information sent by the network-side device; wherein the fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information. In other words, the fourth indication information can be understood as on / off information. In this embodiment, the sending of the fourth indication information can avoid wasting resources due to sending invalid information when the sending of the first request information is not allowed.

[0129] S430: Adjust the DRX activity time according to the first configuration information.

[0130] For example, the first UE delays or advances the DRX active time according to the first configuration information, so that the DRX active time of the first UE is aligned with or identical to the DRX active time of the second UE or overlaps as much as possible, thereby maximizing the duration of the DRX inactive time and maximizing the energy saving effect.

[0131] In this embodiment, through the configuration negotiation of the connected state DRX active time, the configured DRX configuration can meet the preferences or needs of the first UE, such as being the same as or aligned with the DRX active time of the second UE, etc., especially when the first UE and the second UE belong to the same multi-card terminal, it can also maximize the duration of the DRX inactive time of the multi-card terminal, solving the problem of limited energy saving effect in related technologies.

[0132] FIG5 is a flow chart of a method 500 for configuring connected discontinuous reception according to an exemplary embodiment of the present application. The method 500 may be, but is not limited to, performed by a first UE, and may specifically be performed by hardware or software installed in the first UE. In this embodiment, the method 500 may include at least the following steps.

[0133] S510: Send second request information to the network side device.

[0134] The second request information is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX active time.

[0135] That is to say, in this embodiment, before requesting the network side device to adjust the DRX active time, the first UE can first associate with each other, and then when the DRX active time adjustment is required, the network side device and the first UE can adjust the DRX active time based on the pre-configured association relationship. As a result, the efficiency of the DRX active time adjustment can be improved, and unnecessary resource overhead during the DRX active time adjustment can be avoided, such as avoiding the need to carry relevant information of the associated UE or reference UE (such as the second UE) in the first request information.

[0136] In this embodiment, there may be multiple ways to establish the association relationship between UEs through the second request information. For example, in some embodiments, the first UE may determine the association relationship between UEs according to its own needs, and then send the association relationship between UEs to the network side device through the second request information, so that the network side device can confirm the association relationship between UEs. For example, the second request information may carry the identifier of the second UE associated with the first UE, etc. Correspondingly, after receiving the second request message, the network side device may send second configuration information to the first UE, and the second configuration information is used to instruct the first UE that the network side device confirms the association relationship between the first UE and the second UE.

[0137] In other embodiments, the first UE may also request the network-side device to establish an inter-UE association relationship. Based on this, the second request information may include but is not limited to at least one of the identifier of the second UE and UE capability information, wherein the UE capability information is used to indicate the ability of the first UE to support the associated DRX active time. Correspondingly, after receiving the second request information, the network-side device may send second configuration information to the first UE. Then, after receiving the second configuration information sent by the network-side device, the first UE may perform UE association or determine that the inter-UE association relationship is successfully established based on the second configuration information, which can be used for the subsequent sending of the first request information.

[0138] The second configuration information may include fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX active time.

[0139] S520: The first UE sends first request information to the network side device.

[0140] The first request information is used to request the network side device to adjust the connected state DRX activity time.

[0141] It is understood that the implementation process of S520 can refer to the relevant descriptions in the aforementioned method embodiments 200-400. Of course, in this embodiment, the implementation process of S520 can refer to the relevant descriptions in the aforementioned method embodiments 200-400 and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0142] In this embodiment, by pre-configuring the association relationship between UEs, sending the first request information based on the pre-configured association relationship can further improve the efficiency of adjusting the DRX activity time in the connected state and reduce data transmission delay and resource overhead.

[0143] FIG6 is a flow chart of a method 600 for configuring connected discontinuous reception according to an exemplary embodiment of the present application. This method 600 may be, but is not limited to, performed by a network-side device, specifically hardware or software installed in the network-side device. In this embodiment, the method 600 may include at least the following steps.

[0144] S610: The network side device receives first request information sent by the first UE.

[0145] The first request information is used to request the network side device to adjust the connected state DRX activity time.

[0146] Optionally, the first request information includes at least one of the following: an identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; first information, used to request the establishment of a DRX UE group, wherein the UEs in one of the DRX UE groups have the same DRX activity time; second information, used to request the network side device to associate the DRX activity time of the first UE with the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; third information, used to request the network side device to adjust the DRX activity time of the first UE to the same as the DRX activity time of the second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; first indication information, used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

[0147] Optionally, the initiation reason or purpose includes a multi-card reason or purpose.

[0148] Optionally, the method further includes: sending first configuration information to the first UE; wherein the first configuration information is used to instruct the first UE to adjust the DRX activity time.

[0149] Optionally, the first configuration information includes at least one of the following: a first confirmation message, used to indicate that the establishment of the DRX UE group is completed; a third indication message, used to indicate that the network side device has associated or adjusted the DRX activity time of the multi-card terminal to which the first UE belongs; a second confirmation message, used to indicate that the multi-card terminal to which the first UE belongs shares resources; an identifier of the second UE, used to indicate a UE with the same DRX activity time as the first UE.

[0150] Optionally, the multi-card terminals to which the first UE belongs share a DRX UE group.

[0151] Optionally, the first request information is used to request the network side device to adjust the connected state DRX activity time, including at least one of the following: requesting the network side device to configure the connected state DRX; the first request information is used to request the network side device to update the configuration information of the connected state DRX; and providing the DRX configuration preferred by the first UE to the network side device.

[0152] Optionally, the first request information includes at least one of the following: the DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; an identifier of the second UE, used to instruct the network side device to configure connected DRX for the first UE with reference to the DRX configuration of the second UE.

[0153] Optionally, the preferred DRX configuration includes at least one of the following: a preferred connected state DRX long cycle; a preferred connected state DRX start offset value; a preferred connected state DRX short cycle; a preferred connected state DRX duration time slot offset value relative to the subframe start point; a preferred connected state DRX short cycle timer; a preferred connected state DRX continuous listening timer; a preferred connected state DRX inactive timer; a preferred DRX downlink hybrid automatic repeat request round trip time timer; a preferred DRX uplink hybrid automatic repeat request round trip time timer; a preferred DRX downlink retransmission timer; and a preferred DRX uplink retransmission timer.

[0154] Optionally, the first request information also includes DCP configuration information preferred by the first UE.

[0155] Optionally, the preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous monitoring timer.

[0156] Optionally, the method further includes: sending fourth indication information to the first UE; wherein the fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

[0157] Optionally, the method also includes: receiving a second request message sent by the first UE; wherein the second request message is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX activity time.

[0158] Optionally, the second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support associated DRX active time.

[0159] Optionally, the method further includes: sending second configuration information to the first UE; wherein the second configuration information includes fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX activity time.

[0160] Optionally, the first UE and the second UE belong to the same multi-card terminal; or the first UE and the second UE satisfy at least one of the following: reside in the same operator network; reside in the same public land mobile network PLMN; and are located in the same serving cell.

[0161] It can be understood that method embodiment 600 has the same or corresponding technical features as the aforementioned method embodiments 200-400. Therefore, the relevant descriptions of the implementation methods in method embodiment 600 can refer to the relevant descriptions in the aforementioned method embodiments 200-400, and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0162] The method for configuring connected discontinuous reception provided in the embodiments of the present application may be executed by a device for configuring connected discontinuous reception. In the embodiments of the present application, the method for configuring connected discontinuous reception performed by the device for configuring connected discontinuous reception is used as an example to illustrate the device for configuring connected discontinuous reception provided in the embodiments of the present application.

[0163] As shown in Figure 7, it is a structural diagram of a configuration device 700 for connection-state discontinuous reception provided in an embodiment of the present application. The device 700 includes: a sending module 710, used to send a first request information to a network side device, wherein the first request information is used to request the network side device to adjust the connection-state DRX activity time.

[0164] Optionally, the apparatus 700 further includes a receiving module configured to receive first configuration information sent by a network-side device according to the first request information, and a configuration module configured to adjust the DRX activity time according to the first configuration information.

[0165] Optionally, the first request information includes at least one of the following: an identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; first information, used to request the establishment of a DRX UE group, wherein the UEs in one of the DRX UE groups have the same DRX activity time; second information, used to request the network side device to associate the DRX activity time of the first UE with the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; third information, used to request the network side device to adjust the DRX activity time of the first UE to the same as the DRX activity time of the second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; first indication information, used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

[0166] Optionally, the initiation reason or purpose includes a multi-card reason or purpose.

[0167] Optionally, the first UE and the second UE, which are associated with each other or belong to the same DRX UE group or have the same DRX active time, also satisfy at least one of the following: the first UE and the second UE share a DRX inactive timer; when the second UE is in the DRX active time, the first UE is in the DRX active time; when the second UE is in the DRX active time and the first UE needs to enter the DRX inactive time, the first UE waits for a predetermined period of time before entering the DRX inactive time, or the first UE and the second UE enter the DRX inactive time at the same time; when the second UE is in the DRX active time, the first UE in the DRX inactive time monitors the network control channel or sends an uplink request; when the first UE and the second UE are in the same service cell and the first UE is configured with DRX, the DRX active time of the first UE and the second UE is the same.

[0168] Optionally, when the first configuration information is used for DRX active time adjustment, the first configuration information includes at least one of the following: a first confirmation information, used to indicate that the establishment of the DRX UE group is completed; a third indication information, used to indicate that the network side device has associated or adjusted the DRX active time of the multi-card terminal to which the first UE belongs; a second confirmation information, used to indicate that the multi-card terminal to which the first UE belongs shares resources; an identifier of the second UE, used to indicate a UE with the same DRX active time as the first UE.

[0169] Optionally, the multi-card terminals to which the first UE belongs share a DRX UE group.

[0170] Optionally, the first request information is used to request the network side device to adjust the connected state DRX activity time, including at least one of the following: requesting the network side device to configure the connected state DRX; requesting the network side device to update the configuration information of the connected state DRX; providing the network side device with the DRX configuration preferred by the first UE.

[0171] Optionally, the first request information includes at least one of the following: the DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; an identifier of the second UE, used to instruct the network side device to configure connected DRX for the first UE with reference to the DRX configuration of the second UE.

[0172] Optionally, the preferred DRX configuration includes at least one of the following: a preferred connected state DRX long cycle; a preferred connected state DRX start offset value; a preferred connected state DRX short cycle; a preferred connected state DRX duration time slot offset value relative to the subframe start point; a preferred connected state DRX short cycle timer; a preferred connected state DRX continuous listening timer; a preferred connected state DRX inactive timer; a preferred DRX downlink hybrid automatic repeat request round trip time timer; a preferred DRX uplink hybrid automatic repeat request round trip time timer; a preferred DRX downlink retransmission timer; and a preferred DRX uplink retransmission timer.

[0173] Optionally, the first request information also includes DCP configuration information preferred by the first UE.

[0174] Optionally, the preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous monitoring timer.

[0175] Optionally, the receiving module is further used to receive fourth indication information sent by the network side device; wherein, the fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

[0176] Optionally, the sending module is also used to send a second request message to the network side device; wherein, the second request message is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX activity time.

[0177] Optionally, the second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support associated DRX active time.

[0178] Optionally, the receiving module is further used to receive second configuration information sent by the network side device; wherein, the second configuration information includes fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX activity time.

[0179] Optionally, the first UE and the second UE belong to the same multi-card terminal; or the first UE and the second UE satisfy at least one of the following: reside in the same operator network; reside in the same public land mobile network PLMN; and are located in the same serving cell.

[0180] The apparatus 700 for configuring connected discontinuous reception in the embodiment of the present application can be an electronic device, such as an electronic device having an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0181] The apparatus 700 for configuring connected discontinuous reception provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of FIG. 2 to FIG. 5 and achieve the same technical effects. To avoid repetition, they are not described here.

[0182] As shown in Figure 8, it is a structural diagram of a configuration device 800 for connected state discontinuous reception provided in an embodiment of the present application. The device 800 includes: a receiving module 810, used to receive a first request information sent by a first terminal UE, wherein the first request information is used to request the network side device to adjust the connected state DRX activity time.

[0183] Optionally, the apparatus 800 further includes a sending module, configured to send first configuration information to the first UE, where the first configuration information corresponds to the first request information.

[0184] Optionally, the first request information includes at least one of the following: an identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, the first UE and the second UE having the association relationship have the same DRX activity time; first information, used to request the establishment of a DRX UE group, wherein the UEs in one of the DRX UE groups have the same DRX activity time; second information, used to request the network side device to associate the DRX activity time of the first UE with the second UE, wherein the first UE and the second UE having the association relationship have the same DRX activity time; third information, used to request the network side device to adjust the DRX activity time of the first UE to the same as the DRX activity time of the second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; first indication information, used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

[0185] Optionally, the initiation reason or purpose includes a multi-card reason or purpose.

[0186] Optionally, the device further includes: a sending module, configured to send first configuration information to the first UE; wherein the first configuration information is used to instruct the first UE to adjust the DRX activity time.

[0187] Optionally, the first configuration information includes at least one of the following: a first confirmation message, used to indicate that the establishment of the DRX UE group is completed; a third indication message, used to indicate that the network side device has associated or adjusted the DRX activity time of the multi-card terminal to which the first UE belongs; a second confirmation message, used to indicate that the multi-card terminal to which the first UE belongs shares resources; an identifier of the second UE, used to indicate a UE with the same DRX activity time as the first UE.

[0188] Optionally, the multi-card terminals to which the first UE belongs share a DRX UE group.

[0189] Optionally, the first request information is used to request the network side device to adjust the connected state DRX activity time, including at least one of the following: requesting the network side device to configure the connected state DRX; requesting the network side device to update the configuration information of the connected state DRX; providing the network side device with the DRX configuration preferred by the first UE.

[0190] Optionally, the first request information includes at least one of the following: the DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; an identifier of the second UE, used to instruct the network side device to configure connected DRX for the first UE with reference to the DRX configuration of the second UE.

[0191] Optionally, the preferred DRX configuration includes at least one of the following: a preferred connected state DRX long cycle; a preferred connected state DRX start offset value; a preferred connected state DRX short cycle; a preferred connected state DRX duration time slot offset value relative to the subframe start point; a preferred connected state DRX short cycle timer; a preferred connected state DRX continuous listening timer; a preferred connected state DRX inactive timer; a preferred DRX downlink hybrid automatic repeat request round trip time timer; a preferred DRX uplink hybrid automatic repeat request round trip time timer; a preferred DRX downlink retransmission timer; and a preferred DRX uplink retransmission timer.

[0192] Optionally, the first request information also includes DCP configuration information preferred by the first UE.

[0193] Optionally, the preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous monitoring timer.

[0194] Optionally, the sending module is further used to send fourth indication information to the first UE; wherein, the fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

[0195] Optionally, the receiving module is also used to receive a second request message sent by the first UE; wherein, the second request message is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX activity time.

[0196] Optionally, the second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support associated DRX active time.

[0197] Optionally, the sending module is further used to send second configuration information to the first UE; wherein the second configuration information includes fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX activity time.

[0198] Optionally, the first UE and the second UE belong to the same multi-SIM terminal; or the first UE and the second UE satisfy at least one of the following: reside in the same operator network; reside in the same public land mobile network PLMN; and are located in the same serving cell.

[0199] In the embodiments of the present application, the apparatus 800 for configuring connected discontinuous reception can be an electronic device, such as an electronic device with an operating system, or a component within the electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device. For example, the terminal can include, but is not limited to, the types of network-side devices 12 listed above, and this embodiment of the present application does not specifically limit this.

[0200] The apparatus 800 for configuring connected discontinuous reception provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of FIG6 and achieve the same technical effect. To avoid repetition, details will not be given here.

[0201] As shown in Figure 9, an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores a program or instruction that can be run on the processor 901. For example, when the communication device 900 is a terminal, the program or instruction is executed by the processor 901 to implement the various steps of the embodiment of the method for configuring discontinuous reception in connected state, and can achieve the same technical effect. When the communication device 900 is a network-side device, the program or instruction is executed by the processor 901 to implement the various steps of the embodiment of the method for configuring discontinuous reception in connected state, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0202] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 2-5. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, Figure 10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0203] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.

[0204] Those skilled in the art will appreciate that the terminal 1000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG10 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0205] It should be understood that in an embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0206] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1001 may transmit the data to the processor 1010 for processing. Furthermore, the RF unit 1001 may send uplink data to the network-side device. Typically, the RF unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0207] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 may include a volatile memory or a non-volatile memory. Among them, 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), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0208] Processor 1010 may include one or more processing units. Optionally, processor 1010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1010.

[0209] The radio frequency unit 1001 is configured to send a first request message to a network side device, wherein the first request message is used to request the network side device to adjust the connected state DRX activity time.

[0210] Optionally, the first request information includes at least one of the following: an identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; first information, used to request the establishment of a DRX UE group, wherein the UEs in one of the DRX UE groups have the same DRX activity time; second information, used to request the network side device to associate the DRX activity time of the first UE with the second UE, wherein the first UE and the second UE with the association relationship have the same DRX activity time; third information, used to request the network side device to adjust the DRX activity time of the first UE to the same as the DRX activity time of the second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; first indication information, used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

[0211] Optionally, the initiation reason or purpose includes a multi-card reason or purpose.

[0212] Optionally, the first UE and the second UE, which are associated with each other or belong to the same DRX UE group or have the same DRX active time, also satisfy at least one of the following: the first UE and the second UE share a DRX inactive timer; when the second UE is in the DRX active time, the first UE is in the DRX active time; when the second UE is in the DRX active time and the first UE needs to enter the DRX inactive time, the first UE waits for a predetermined period of time before entering the DRX inactive time, or the first UE and the second UE enter the DRX inactive time at the same time; when the second UE is in the DRX active time, the first UE in the DRX inactive time monitors the network control channel or sends an uplink request; when the first UE and the second UE are in the same service cell and the first UE is configured with DRX, the DRX active time of the first UE and the second UE is the same.

[0213] Optionally, the radio frequency unit 1001 is used to receive first configuration information sent by the network side device; the processor 1010 is used to adjust the DRX activity time according to the first configuration information.

[0214] Optionally, the first configuration information includes at least one of the following: a first confirmation message, used to indicate that the establishment of the DRX UE group is completed; a third indication message, used to indicate that the network side device has associated or adjusted the DRX activity time of the multi-card terminal to which the first UE belongs; a second confirmation message, used to indicate that the multi-card terminal to which the first UE belongs shares resources; an identifier of the second UE, used to indicate a UE with the same DRX activity time as the first UE.

[0215] Optionally, the multi-card terminals to which the first UE belongs share a DRX UE group.

[0216] Optionally, the first request information is used to request the network side device to adjust the connected state DRX activity time, including at least one of the following: requesting the network side device to configure the connected state DRX; requesting the network side device to update the configuration information of the connected state DRX; providing the network side device with the DRX configuration preferred by the first UE.

[0217] Optionally, the first request information includes at least one of the following: the DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; an identifier of the second UE, used to instruct the network side device to configure connected DRX for the first UE with reference to the DRX configuration of the second UE.

[0218] Optionally, the preferred DRX configuration includes at least one of the following: a preferred connected state DRX long cycle; a preferred connected state DRX start offset value; a preferred connected state DRX short cycle; a preferred connected state DRX duration time slot offset value relative to the subframe start point; a preferred connected state DRX short cycle timer; a preferred connected state DRX continuous listening timer; a preferred connected state DRX inactive timer; a preferred DRX downlink hybrid automatic repeat request round trip time timer; a preferred DRX uplink hybrid automatic repeat request round trip time timer; a preferred DRX downlink retransmission timer; and a preferred DRX uplink retransmission timer.

[0219] Optionally, the first request information also includes DCP configuration information preferred by the first UE.

[0220] Optionally, the preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous monitoring timer.

[0221] Optionally, the radio frequency unit 1001 is further used to receive fourth indication information sent by the network side device; wherein the fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

[0222] Optionally, the radio frequency unit 1001 is also used to send a second request message to the network side device; wherein, the second request message is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX activity time.

[0223] Optionally, the second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support associated DRX active time.

[0224] Optionally, the radio frequency unit 1001 is further configured to receive second configuration information sent by the network side device; wherein the second configuration information includes fifth indication information, and the fifth indication information is used to indicate adjustment of the DRX active time.

[0225] Optionally, the first UE and the second UE belong to the same multi-card terminal; or the first UE and the second UE satisfy at least one of the following: reside in the same operator network; reside in the same public land mobile network PLMN; and are located in the same serving cell.

[0226] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiments 200-500, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0227] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG6 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0228] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, the network-side device 1100 includes an antenna 1101, a radio frequency device 1102, a baseband device 1103, a processor 1104, and a memory 1105. Antenna 1101 is connected to radio frequency device 1102. In the uplink direction, radio frequency device 1102 receives information via antenna 1101 and sends the received information to baseband device 1103 for processing. In the downlink direction, baseband device 1103 processes the information to be transmitted and sends it to radio frequency device 1102. Radio frequency device 1102 processes the received information and then sends it through antenna 1101.

[0229] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1103 , which includes a baseband processor.

[0230] The baseband device 1103 may, for example, include at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, one of the chips is, for example, a baseband processor, which is connected to the memory 1105 through a bus interface to call the program in the memory 1105 and execute the network device operations shown in the above method embodiment.

[0231] The network side device may further include a network interface 1106 , which is, for example, a Common Public Radio Interface (CPRI).

[0232] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1105 and executable on the processor 1104. The processor 1104 calls the instructions or programs in the memory 1105 to execute the method of executing each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0233] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the embodiment of the configuration method for discontinuous reception in the connection state is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0234] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0235] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned embodiment of the configuration method for discontinuous reception in the connection state, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0236] 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.

[0237] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-mentioned embodiment of the configuration method for discontinuous reception in connected state, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0238] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to implement the various processes in embodiments 200-500 of the above-mentioned configuration method for discontinuous reception in the connection state, and the network-side device can be used to implement the various processes in embodiment 600 of the above-mentioned configuration method for discontinuous reception in the connection state, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0239] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0240] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0241] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for configuring connected discontinuous reception, wherein: include: The first terminal UE sends a first request message to a network side device, wherein the first request message is used to request the network side device to adjust a connected discontinuous reception DRX activity time.

2. The method of claim 1, wherein: The first request information includes at least one of the following: An identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, wherein the first UE and the second UE having the association relationship have the same DRX activity time; The first information is used to request the establishment of a DRX UE group, wherein UEs in one of the DRX UE groups have the same DRX activity time; The second information is used to request the network side device to associate the DRX activity time of the first UE and the second UE; third information, used to request the network side device to adjust the DRX activity time of the first UE to be the same as the DRX activity time of a second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; The first indication information is used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

3. The method of claim 2, wherein: The initiation reason or purpose includes multiple card reasons or purposes.

4. The method of claim 2, wherein: The first UE and the second UE that have an associated relationship or belong to the same DRX UE group or have the same DRX activity time also satisfy at least one of the following: The first UE and the second UE share a DRX inactivity timer; In a case where the second UE is in the DRX active time, the first UE is in the DRX active time; When the second UE is in the DRX active time and the first UE needs to enter the DRX inactive time, the first UE enters the DRX inactive time after waiting for a predetermined time, or the first UE and the second UE enter the DRX inactive time at the same time; When the second UE is in the DRX active time, the first UE in the DRX inactive time monitors the network control channel or sends an uplink request; When the first UE and the second UE are in the same serving cell and the first UE is configured with DRX, the DRX activity time of the first UE and the second UE is the same.

5. The method according to any one of claims 1 to 4, wherein: The method further comprises: Receiving first configuration information sent by the network side device; The DRX activity time is adjusted according to the first configuration information.

6. The method of claim 5, wherein: The first configuration information includes at least one of the following: First confirmation information, used to indicate that the establishment of the DRX UE group is completed; The third indication information is used to indicate that the network side device has associated or adjusted the DRX activity time of the multi-card terminal to which the first UE belongs; The second confirmation information is used to instruct the multi-card terminals to which the first UE belongs to share resources; The identifier of the second UE is used to indicate a UE having the same DRX activity time as the first UE.

7. The method according to any one of claims 1 to 6, wherein: The multi-card terminals to which the first UE belongs share a DRX UE group.

8. The method of claim 1, wherein: The first request information is used to request the network side device to adjust the connected DRX activity time, including at least one of the following: Requesting the network side device to configure connected DRX; Requesting the network side device to update the connected state DRX configuration; Provide the network side device with the DRX configuration preferred by the first UE.

9. The method of claim 8, wherein: The first request information includes at least one of the following: a DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; The identifier of the second UE is used to instruct the network side device to configure a connected DRX configuration for the first UE with reference to the DRX configuration of the second UE.

10. The method of claim 9, wherein: The preferred DRX configuration includes at least one of the following: Preferred connected DRX long cycle; Preferred connected DRX start offset value; Preferred connected DRX short cycle; The preferred connected DRX duration is a timeslot offset relative to the start of a subframe; Preferred connected DRX short cycle timer; Preferred connected DRX continuous monitoring timer; Preferred connected DRX inactivity timer; Preferred DRX downlink hybrid automatic repeat request round trip time timer; Preferred DRX uplink hybrid automatic repeat request round trip time timer; Preferred DRX downlink retransmission timer; Preferred DRX uplink retransmission timer.

11. The method according to any one of claims 1 to 10, wherein: The first request information also includes DCP configuration information preferred by the first UE.

12. The method of claim 11, wherein: The preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous listening timer.

13. The method according to any one of claims 1 to 12, wherein: The method further comprises: Receiving fourth indication information sent by the network side device; The fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

14. The method according to any one of claims 1 to 13, wherein: Before the first terminal UE sends the first request information to the network side device, the method further includes: Sending second request information to the network side device; The second request information is used to request the network side device to establish a connection between the first UE and the second UE. , wherein the association relationship is used to adjust the DRX activity time.

15. The method of claim 14, wherein: The second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support the associated DRX activity time.

16. The method of claim 15, wherein: The method further comprises: Receiving second configuration information sent by the network side device; The second configuration information includes fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX activity time.

17. The method according to any one of claims 8 to 16, wherein: The first UE and the second UE belong to the same multi-card terminal; or, The first UE and the second UE satisfy at least one of the following: Reside on the same operator network; Reside on the same public land mobile network PLMN; Located in the same service area.

18. A method for configuring connected discontinuous reception, wherein: include: A network side device receives first request information sent by a first terminal UE, wherein the first request information is used to request the network side device to adjust a connected state DRX activity time.

19. The method of claim 18, wherein: The first request information includes at least one of the following: An identifier of the second UE, used by the network side device to establish an association relationship between the first UE and the second UE, wherein the first UE and the second UE having the association relationship have the same DRX activity time; The first information is used to request the establishment of a DRX UE group, wherein UEs in one of the DRX UE groups have the same DRX activity time; The second information is used to request the network side device to associate the DRX activity time of the first UE and the second UE; third information, used to request the network side device to adjust the DRX activity time of the first UE to be the same as the DRX activity time of a second UE, wherein the second UE is associated with the first UE, or the second UE and the first UE belong to the same DRX UE group; The first indication information is used to indicate the reason or purpose for initiating the first request information, or to indicate the sharing of multi-card terminal resources to which the first UE belongs.

20. The method of claim 19, wherein: The initiation reason or purpose includes multiple card reasons or purposes.

21. The method of any one of claims 18 to 20, wherein: The method further comprises: Sending first configuration information to the first UE; The first configuration information is used to instruct the first UE to adjust the DRX activity time.

22. The method of claim 21, wherein: The first configuration information includes at least one of the following: First confirmation information, used to indicate that establishment of the DRX UE group is completed; The third indication information is used to indicate the DRX activity of the network side device for the multi-card terminal to which the first UE belongs The times were related or adjusted; The second confirmation information is used to instruct the multi-card terminals to which the first UE belongs to share resources; The identifier of the second UE is used to indicate a UE having the same DRX activity time as the first UE.

23. The method of any one of claims 18 to 22, wherein: The multi-card terminals to which the first UE belongs share a DRX UE group.

24. The method of claim 18, wherein: The first request information is used to request the network side device to adjust the connected DRX activity time, including at least one of the following: Requesting the network side device to configure connected DRX; Requesting the network side device to update the configuration information of the connected state DRX; Provide the network side device with the DRX configuration preferred by the first UE.

25. The method of claim 20, wherein: The first request information includes at least one of the following: a DRX configuration preferred by the first UE; second indication information, used to indicate the reason or purpose for initiating the first request information; The identifier of the second UE is used to instruct the network side device to provide the connected state DRX configuration for the first UE with reference to the connected state DRX configuration of the second UE.

26. The method of claim 24 or 25, wherein: The preferred DRX configuration includes at least one of the following: Preferred connected DRX long cycle; Preferred connected DRX start offset value; Preferred connected DRX short cycle; The preferred connected DRX duration is a timeslot offset relative to the start of a subframe; Preferred connected DRX short cycle timer; Preferred connected DRX continuous monitoring timer; Preferred connected DRX inactivity timer; Preferred DRX downlink hybrid automatic repeat request round trip time timer; Preferred DRX uplink hybrid automatic repeat request round trip time timer; Preferred DRX downlink retransmission timer; Preferred DRX uplink retransmission timer.

27. The method of any one of claims 18 to 26, wherein: The first request information also includes DCP configuration information preferred by the first UE.

28. The method of claim 27, wherein: The preferred DCP configuration information includes a preferred first offset value, where the first offset value is an offset value of the DCP start time relative to the start time of the DRX continuous listening timer.

29. The method of any one of claims 18 to 28, wherein: The method further comprises: Sending fourth indication information to the first UE; The fourth indication information is used to indicate whether the first UE is allowed or not to send the first request information.

30. The method of any one of claims 18 to 29, wherein: Before receiving the first request information sent by the first terminal UE, the method further includes: Receiving second request information sent by the first UE; The second request information is used to request the network side device to establish an association relationship between the first UE and the second UE, and the association relationship is used to adjust the DRX activity time.

31. The method of claim 30, wherein: The second request information includes at least one of the following: an identifier of the second UE; UE capability information, used to indicate the capability of the first UE to support the associated DRX activity time.

32. The method of claim 30, wherein: The method further comprises: Sending second configuration information to the first UE; The second configuration information includes fifth indication information, and the fifth indication information is used to instruct the first UE to adjust the DRX activity time.

33. The method of any one of claims 25 to 32, wherein: The first UE and the second UE belong to the same multi-card terminal; or, The first UE and the second UE satisfy at least one of the following: Reside on the same operator network; Reside on the same public land mobile network PLMN; Located in the same service area.

34. A configuration device for connected discontinuous reception, wherein: include: The sending module is used to send a first request message to a network side device, wherein the first request message is used to request the network side device to adjust the DRX activity time in the connection state.

35. A configuration device for connected discontinuous reception, wherein: include: The receiving module is used to receive a first request message sent by a first terminal UE, wherein the first request message is used to request a network side device to adjust a connection state DRX activity time.

36. A terminal, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 17 are implemented.

37. A network side device, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 18 to 33 are implemented.

38. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 17, or implements the steps of the method according to any one of claims 18 to 33.

39. A chip, wherein: The chip includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method according to any one of claims 1 to 17 or the method according to any one of claims 18 to 33.

40. A computer program product, wherein: The program product is executed by at least one processor to implement the method according to any one of claims 1 to 17 or the method according to any one of claims 18 to 33.

Images