DRX configuration method for sidelink, terminal device, network device and computer-readable storage medium

Abstract

Embodiments of this application disclose a DRX configuration method for sidelink, a terminal device, a network device and a computer-readable storage medium, where the method includes: determining (S102), by a terminal device, DRX configuration information; and performing (S104) DRX configuration according to the configuration information. In the embodiments of this application, a terminal device can determine DRX configuration information, and perform DRX configuration according to the determined configuration information, thereby implementing power saving for terminal devices in sidelink. (FIG. 1)

Description

Sidelink DRX configuration methods and devices

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 201910780098.X, filed in China on August 22, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communications, and more particularly to a method and device for configuring discontinuous reception (DRX) on a sidelink. Background Technology

[0004] Both Long Term Evolution (LTE) and New Radio (NR) systems support sidelink transmission, meaning that terminal devices can directly transmit data over the radio interface. Additionally, LTE and NR systems introduce a DRX mechanism at the Uu interface, using configured DRX on and off times to achieve energy savings for terminal devices.

[0005] However, the DRX configuration scheme for the Uu port is not currently used in sidelink. Therefore, how to implement DRX configuration for terminal devices in sidelink is a technical problem that urgently needs to be solved in related technologies.

[0006] Summary of the Invention

[0007] The purpose of this application is to provide a DRX configuration method and device for a sidelink, so as to implement DRX configuration of the terminal device in the sidelink.

[0008] Firstly, a method for configuring DRX for sidelinks is provided, including:

[0009] The terminal device determines the DRX configuration information;

[0010] Configure DRX according to the configuration information.

[0011] Secondly, a method for configuring DRX on a sidelink is provided, the method being executed by a network device, including:

[0012] Send DRX configuration information to the terminal device; wherein the configuration information is used by the terminal device to configure DRX.

[0013] Thirdly, a terminal device is provided, the terminal device comprising:

[0014] The determination module is used to determine the configuration information of DRX;

[0015] The configuration module is used to configure DRX based on the configuration information.

[0016] Fourthly, a network device is provided, the network device comprising:

[0017] The sending module is used to send DRX configuration information to the terminal device; wherein the configuration information is used by the terminal device to configure DRX.

[0018] Fifthly, a terminal device is provided, the terminal device including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the DRX configuration method of the sidelink as described in the first aspect.

[0019] In a sixth aspect, a network device is provided, the network device including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the DRX configuration method for the sidelink as described in the second aspect.

[0020] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the DRX configuration method for the sidelink as described in the first and second aspects.

[0021] In this embodiment of the application, the terminal device can determine the configuration information of DRX and configure DRX according to the determined configuration information, so as to save the power of the terminal device in the sidelink system. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0023] Figure 1 is a schematic flowchart of a sidelink DRX configuration method according to an embodiment of this application;

[0024] Figure 2 is a schematic diagram of sidelink transmission according to an embodiment of this application;

[0025] Figure 3 is a schematic diagram of the activation period and dormancy period of UE1 and UE2 in the embodiment shown in Figure 2;

[0026] Figures 4 to 6 are schematic flowcharts of the DRX configuration method of the sidelink according to three specific embodiments of this application;

[0027] Figure 7 is a schematic flowchart of a sidelink DRX configuration method according to another embodiment of this application;

[0028] Figure 8 is a schematic diagram of the structure of a terminal device according to an embodiment of this application;

[0029] Figure 9 is a schematic diagram of the structure of a network device according to an embodiment of this application;

[0030] Figure 10 is a schematic diagram of the structure of a terminal device according to another embodiment of this application;

[0031] Figure 11 is a schematic diagram of the structure of a network device according to another embodiment of this application. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. In the various embodiments of this specification, "and / or" means at least one of the preceding and following terms.

[0033] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as LTE sidelink systems or NR sidelink systems, or to the sidelink communication systems that are subsequently evolved.

[0034] In the embodiments of this application, the terminal device may include, but is not limited to, a mobile station (MS), a mobile terminal, a mobile phone, user equipment (UE), a handset, portable equipment, a vehicle, etc. The terminal device can communicate with one or more core networks via a radio access network (RAN). For example, the terminal device may be a mobile phone (or "cellular" phone), a computer with wireless communication capabilities, etc. The terminal device may also be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device.

[0035] In this embodiment, a network device is an apparatus deployed in a wireless access network to provide wireless communication functions for terminal devices. The network device can be a base station, which may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with base station functionality may differ. For example, in LTE networks, it is called an Evolved Node B (eNB or eNodeB); in third-generation (3G) networks, it is called a Node B; or network devices in subsequent evolved communication systems, etc. However, the terminology used is not limiting.

[0036] As shown in Figure 1, one embodiment of this application provides a sidelink DRX configuration method 100, which can be executed by a terminal device and includes the following steps:

[0037] S102: Determine the DRX configuration information.

[0038] The terminal devices provided in the various embodiments of this specification can be either transmitting devices for sending sidelink data or receiving devices for receiving sidelink data. Of course, these two can be a single terminal device, because a single terminal device can perform not only the step of sending sidelink data but also the step of receiving sidelink data.

[0039] In this embodiment of the application, the terminal device that communicates with the terminal device via sidelink is referred to as the peer device.

[0040] Optionally, in one embodiment, the terminal device may receive configuration information sent by the peer device during this step. In this embodiment, the peer device may perform DRX configuration for the local terminal device.

[0041] Alternatively, in another embodiment, the terminal device can pre-agree on configuration information with the peer device, such as pre-agreeing on relevant parameters for DRX transmission, including the DRX period and offset, the duration of the DRX activation period, and the duration of the DRX sleep period. In this way, before transmitting DRX with the peer device, the terminal device can determine the configuration information to configure DRX according to the pre-agreeed configuration information.

[0042] Alternatively, in another embodiment, the network device may perform DRX configuration on the terminal device and the peer device. In this step, the terminal device may receive configuration information sent by the network device.

[0043] S104: Configure DRX based on configuration information.

[0044] Specifically, this step may involve configuring the terminal device in at least one of the following ways:

[0045] 1) DRX period and offset.

[0046] 2) The length of the DRX continuous listening timer (drx-onDuration Timer).

[0047] 3) The length of the DRX inactivity timer.

[0048] 4) The length of the Hybrid Automatic Repeat Request (HARQ) Round-Trip Time (RTT) timer (drx-HARQ-RTT-Timer).

[0049] 5) Length of the retransmission timer (drx-Retransmission Timer).

[0050] The functions and usage of the timers mentioned above can be specifically applied to the NR Uu interface, and will not be described again here.

[0051] The sidelink DRX configuration method provided in this application embodiment allows the terminal device to determine the DRX configuration information and configure the DRX according to the determined configuration information, thereby saving the terminal device's power in the sidelink system.

[0052] In a specific application scenario, as shown in Figure 2, UE1 can send sidelink data to UE2, UE1 can send sidelink data to UE3, UE1 can send sidelink data to UE4, and UE2 can send sidelink data to UE3.

[0053] Typically, a UE cannot simultaneously receive and send sidelink data. Therefore, when UE2 sends sidelink data to UE3, UE2 does not expect to receive sidelink data from UE1.

[0054] After configuring UE1 or UE2 with DRX using the sidelink DRX configuration method provided in this application embodiment, the activation and sleep periods of UE1 and UE2 are shown in Figure 3. In Figure 3, the vertically protruding part represents the activation / listening state, the vertically flat part represents the sleep state, and the horizontal direction is the time axis.

[0055] In Figure 3, when UE1 sends sidelink data to UE2, both UE1 and UE2 are active simultaneously. Optionally, when UE1 sends sidelink data to UE2, the active periods of UE1 and UE2 occupy the same time domain position.

[0056] Additionally, in Figure 3, when UE1 sends sidelink data to UE3 and UE4, UE1 is in an active period, and at the same time, UE2 is also in an active period. Thus, UE2 can send sidelink data to UE3.

[0057] In the embodiment shown in Figure 3, by configuring the terminal devices with DRX, the activation periods of a pair of terminal devices (e.g., UE1 and UE2) that are performing sidelink data transmission can be made consistent, which facilitates sidelink data transmission.

[0058] Optionally, in the embodiment shown in Figure 2, the time domain positions occupied by the activation period and the sleep period of UE1 and UE2 can be exactly the same, that is, the time domain positions occupied by the activation period of UE1 and UE2 are the same, and the time domain positions occupied by the sleep period of UE1 and UE2 are also the same.

[0059] As mentioned in Example 100, the peer device can configure DRX on the local terminal device. Optionally, before Example 100 is executed, the following steps may be included: the terminal device sends DRX assistance information or a DRX configuration request to the peer device. Or, the terminal device sends DRX assistance information or a DRX configuration request to the network device.

[0060] Thus, S102 in the previous embodiment can specifically refer to the terminal device receiving DRX configuration information. This configuration information can come from the peer device or from the network device.

[0061] For example, in the embodiments shown in Figures 2 and 3, UE2 sends DRX assistance information or DRX configuration request to UE1.

[0062] In one embodiment, the terminal device can send DRX assistance information, which can be used by the peer device to perform DRX configuration on the terminal device based on the DRX assistance information. Of course, the peer device can also ignore the assistance information and directly perform DRX configuration on the terminal device.

[0063] In this embodiment, the terminal device can send DRX assistance information. In this way, when configuring DRX for the terminal device, the peer device can fully consider the sidelink transmission status of the terminal device and combine it with its own sidelink transmission status to configure DRX for the terminal device. To a certain extent, this is equivalent to the terminal device and the peer device negotiating the optimal DRX configuration to maximize the energy saving of both the terminal device and the peer device.

[0064] In another embodiment, the terminal device may send a DRX configuration request to request the peer device to perform DRX configuration on the terminal device. In this embodiment, the peer device may directly perform DRX configuration on the terminal device.

[0065] Of course, in another embodiment, the terminal device can send DRX assistance information and DRX configuration request at the same time. For the functions of DRX assistance information and DRX configuration request, please refer to the above description.

[0066] In the above embodiments, the terminal device is a sidelink data receiving device, and the peer device is a sidelink data sending device; or, in the above embodiments, the terminal device is a sidelink data sending device, and the peer device is a sidelink data receiving device; of course, the terminal device mentioned in the above embodiments can not only send sidelink data to the peer device, but also receive sidelink data sent by the peer device, and correspondingly, the peer device can not only receive sidelink data sent by the terminal device, but also send sidelink data to the terminal device.

[0067] It should be noted that the terms "terminal device" and "peer device" mentioned in the various embodiments of this specification refer to the local terminal device. It can be understood that the peer device itself can be called the local terminal device, while the terminal device described above can be called the peer device.

[0068] In the above embodiments, after configuring DRX according to the configuration information, the terminal device can also send DRX feedback information to the peer device; wherein, the DRX feedback information can be used to indicate the configuration status of DRX, for example, indicating that the DRX configuration is successful, or indicating that the DRX configuration has failed, etc.

[0069] Optionally, the DRX assistance information mentioned in the above embodiments includes at least one of the following:

[0070] The desired DRX period and offset for the terminal device;

[0071] The desired length of the DRX continuous listening timer for the terminal device;

[0072] The desired length of the DRX inactive timer for the terminal device;

[0073] The desired length of the HARQ RTT timer for the terminal device;

[0074] The desired length of the retransmission timer for the terminal device;

[0075] The time-domain unit that the terminal device does not want DRX to be activated; the time-domain unit mentioned here can be a subframe, time slot, etc.

[0076] The terminal device wants the time-domain unit to be activated by DRX.

[0077] As mentioned in embodiment 100 above, the network device can perform DRX configuration for both the terminal device and the peer device. Optionally, step S102 of this embodiment may specifically involve the terminal device receiving DRX configuration information sent by the network device, which is determined by the network device. Of course, the peer device can also receive the configuration information sent by the network device and perform DRX configuration. In this embodiment, both the terminal device and the peer device maintain an RRC connection with the network device.

[0078] Optionally, in the above embodiments, the terminal device may also receive indication information; wherein the indication information is used to indicate the peer device to which the configuration information is targeted, for example, indicating the identification information of the peer device.

[0079] Optionally, after configuring DRX according to the configuration information, the terminal device can also send DRX feedback information to the network device. This DRX feedback information can be used to indicate the configuration status of DRX, such as indicating that the DRX configuration was successful or that the DRX configuration failed.

[0080] In practical applications, network devices can configure a transmit DRX mode for a terminal device and notify the terminal device of the peer device to which this transmit DRX mode is intended; similarly, they can configure a receive DRX mode for the peer device and notify the peer device of the terminal device to which this receive DRX mode is intended. The above example assumes the terminal device is the transmitting device and the peer device is the receiving device. In reality, even when the terminal device is the receiving device and the peer device is the transmitting device, the network device can still configure corresponding receive / transmit DRX modes for both the terminal device and the peer device.

[0081] This embodiment is particularly applicable to scenarios where the resource allocation mode of the terminal device is the network device scheduling mode (Mode 1). Because the network device allocates resources to a pair of terminal devices that are performing sidelink data transmission, it is easier to determine the time domain position of the sidelink data transmission of this pair of terminal devices. Therefore, when configuring the terminal device for DRX, the time period during which the terminal device does not perform sidelink data transmission can be configured as a sleep period as much as possible, which can save the terminal device's power to the greatest extent.

[0082] To explain in detail the DRX configuration method of the sidelink provided in various embodiments of this application, the following will be introduced in conjunction with several specific embodiments.

[0083] Example 1

[0084] As shown in Figure 4, this embodiment can be executed by a sidelink receiving device (hereinafter referred to as the receiving device), and includes the following steps:

[0085] S402: Send auxiliary information.

[0086] In this embodiment, the receiving device can send auxiliary information to the sidelink transmitting device (hereinafter referred to as the transmitting device). The transmitting device performs DRX configuration on the receiving device. The transmitting device can perform DRX configuration on the receiving device in conjunction with the auxiliary information, or it can ignore the auxiliary information and perform DRX configuration on the receiving device.

[0087] This auxiliary information includes at least one of the following:

[0088] The desired period and offset of the DRX received by the receiving device;

[0089] The desired length of the DRX continuous listening timer for the receiving device;

[0090] The desired length of the DRX inactive timer for the receiving device;

[0091] The desired length of the HARQ RTT timer for the receiving device;

[0092] The desired length of the retransmission timer for the receiving device;

[0093] The receiving device does not want DRX to be activated in the time domain unit. The time domain unit mentioned here can be a subframe, time slot, etc.

[0094] The receiving device wants the time-domain unit to be activated by DRX.

[0095] S404: Receives DRX configuration information.

[0096] After receiving the configuration information, the receiving device can perform DRX configuration according to the configuration information. For the specific configuration process, please refer to the description of the previous embodiment.

[0097] S406: Send DRX feedback information.

[0098] This DRX feedback information can be used to indicate the configuration status of DRX, such as indicating that DRX configuration was successful or that DRX configuration failed.

[0099] Optionally, in other embodiments, steps S402 and S406 can be omitted, that is, the transmitting device directly configures the receiving device for DRX.

[0100] Example 2

[0101] As shown in Figure 5, this embodiment can be executed by a sidelink transmitting device (hereinafter referred to as the transmitting device), including the following steps:

[0102] S502: Send auxiliary information.

[0103] In this embodiment, the transmitting device can send auxiliary information to the sidelink receiving device (hereinafter referred to as the receiving device). The receiving device performs DRX configuration on the transmitting device. The receiving device can perform DRX configuration on the transmitting device in conjunction with the auxiliary information, or it can ignore the auxiliary information and perform DRX configuration on the transmitting device.

[0104] This auxiliary information includes at least one of the following:

[0105] The period and offset of the DRX desired by the transmitting device;

[0106] The length of the DRX continuous listening timer desired by the transmitting device;

[0107] The length of the DRX inactive timer desired by the transmitting device;

[0108] The length of the HARQ RTT timer desired by the transmitting device;

[0109] The length of the retransmission timer desired by the transmitting device;

[0110] The time-domain unit that the transmitting device does not want DRX to be activated; the time-domain unit mentioned here can be a subframe, a time slot, etc.

[0111] The transmitting device wants the DRX to activate in the time domain.

[0112] S504: Receives DRX configuration information.

[0113] After receiving the configuration information, the transmitting device can configure DRX according to the configuration information. For the specific configuration process, please refer to the description of the previous embodiment.

[0114] S506: Send DRX feedback information.

[0115] This DRX feedback information can be used to indicate the configuration status of DRX, such as indicating that DRX configuration was successful or that DRX configuration failed.

[0116] Optionally, in other embodiments, steps S502 and S506 can be omitted, that is, the receiving device directly configures the transmitting device for DRX.

[0117] Example 3

[0118] As shown in Figure 6, in this embodiment, the network device can configure DRX for both the sidelink transmitting device (hereinafter referred to as the transmitting device) and the sidelink receiving device (hereinafter referred to as the receiving device). The transmitting device and the receiving device can receive the configuration information sent by the network device. In this embodiment, both the transmitting device and the receiving device maintain an RRC connection with the network device.

[0119] Optionally, in this embodiment, the transmitting device may also receive indication information; wherein the indication information is used to indicate the receiving device, for example, to indicate the identification information of the receiving device.

[0120] Optionally, in this embodiment, the receiving device may also receive indication information; wherein the indication information is used to indicate the sending device, for example, to indicate the identification information of the sending device.

[0121] The DRX configuration method of the sidelink according to an embodiment of this application has been described in detail above with reference to Figures 1 to 6. The DRX configuration method of the sidelink according to another embodiment of this application will now be described in detail with reference to Figure 7. It is understood that the interaction between the network device and the terminal device described from the network device side is the same as the description from the terminal device side in the method shown in Figure 1; to avoid repetition, relevant descriptions are appropriately omitted.

[0122] Figure 7 is a schematic diagram of the implementation flow of the DRX configuration method of the sidelink according to an embodiment of this application. It can be applied to the network device side. As shown in Figure 7, the method 700 includes:

[0123] S702: Sends DRX configuration information to the terminal device, which is used by the terminal device to configure DRX.

[0124] In this embodiment of the application, the terminal device can receive DRX configuration information and configure DRX according to the configuration information in order to save power of the terminal device in the sidelink system.

[0125] Optionally, as an embodiment, after sending the DRX configuration information, the method further includes:

[0126] The configuration information is sent to the peer device to which the configuration information is intended, and the configuration information is also used by the peer device to perform DRX configuration.

[0127] Optionally, as an embodiment, after sending the configuration information to the peer device to which the configuration information is targeted, the method further includes:

[0128] Send a first indication message to the terminal device; wherein the first indication message is used to indicate the peer device; and / or send a second indication message to the peer device; wherein the second indication message is used to indicate the terminal device.

[0129] The DRX configuration method of the sidelink according to an embodiment of this application has been described in detail above with reference to Figures 1 to 7. The terminal device according to an embodiment of this application will now be described in detail with reference to Figure 8.

[0130] Figure 8 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application. As shown in Figure 8, the terminal device 800 includes:

[0131] The determination module 802 can be used to determine the configuration information of DRX; the configuration module 804 can be used to configure DRX according to the configuration information.

[0132] The terminal device provided in this application embodiment can determine the DRX configuration information and configure the DRX according to the determined configuration information, so as to save the power of the terminal device in the sidelink system.

[0133] Optionally, as an embodiment, the determining module 802 can be used to receive DRX configuration information sent by the peer device; wherein the configuration information is determined by the peer device.

[0134] Optionally, as an embodiment, the terminal device is a sidelink receiving device and the peer device is a sidelink transmitting device; or, the terminal device is a sidelink transmitting device and the peer device is a sidelink receiving device.

[0135] Optionally, as an embodiment, the determining module 802 can be used to send DRX feedback information to the peer device; wherein the DRX feedback information indicates that the DRX configuration is successful or indicates that the DRX configuration has failed.

[0136] Optionally, as an embodiment, the determining module 802 can be used to send DRX assistance information or DRX configuration requests to the peer device; or, to send DRX assistance information or DRX configuration requests to the network device.

[0137] Optionally, as an embodiment, the DRX assistance information includes at least one of the following:

[0138] DRX period and offset;

[0139] The length of the DRX continuous listening timer;

[0140] The length of the DRX inactive timer;

[0141] The length of the HARQ round-trip timer;

[0142] The length of the retransmission timer;

[0143] The terminal device does not want the time-domain unit to be activated by DRX;

[0144] The terminal device wants the time-domain unit to be activated by DRX.

[0145] Optionally, as an embodiment, the configuration information is pre-agreed upon by the terminal device and the peer device.

[0146] Optionally, as an embodiment, the determining module 802 can be used to receive configuration information sent by the network device; wherein the configuration information is determined by the network device.

[0147] Optionally, as an embodiment, the determining module 802 can be used to receive indication information;

[0148] The indication information is used to indicate the peer device to which the configuration information is targeted; the network device is also used to perform DRX configuration for the peer device.

[0149] Optionally, as an embodiment, the determining module 802 can be used to send DRX feedback information to the network device; wherein the DRX feedback information indicates that the DRX configuration is successful or indicates that the DRX configuration has failed.

[0150] The terminal device 800 according to the embodiments of this application can refer to the process of the method 100 corresponding to the embodiments of this application. Furthermore, each unit / module in the terminal device 800 and the other operations and / or functions mentioned above are respectively implemented to achieve the corresponding process in the method 100 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0151] Figure 9 is a schematic diagram of a network device according to an embodiment of this application. As shown in Figure 9, the network device 900 includes:

[0152] The sending module 902 can be used to send DRX configuration information to the terminal device; wherein, the configuration information is used by the terminal device to perform DRX configuration.

[0153] In this embodiment of the application, the terminal device can receive DRX configuration information and configure DRX according to the configuration information in order to save power of the terminal device in the sidelink system.

[0154] Optionally, as an embodiment, the sending module 902 is further configured to: send the configuration information to the peer device to which the configuration information is targeted, the configuration information being used by the peer device to perform DRX configuration.

[0155] Optionally, as an embodiment, the sending module 902 is further configured to: send first indication information to the terminal device; wherein the first indication information is used to indicate the peer device; and / or, send second indication information to the peer device; wherein the second indication information is used to indicate the terminal device.

[0156] The terminal device 900 according to the embodiments of this application can refer to the process of the method 700 corresponding to the embodiments of this application. Furthermore, each unit / module in the terminal device 900 and the other operations and / or functions mentioned above are respectively implemented to achieve the corresponding process in the method 700 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0157] Figure 10 is a block diagram of a terminal device according to another embodiment of this application. The terminal device 1000 shown in Figure 10 includes at least one processor 1001, a memory 1002, at least one network interface 1004, and a user interface 1003. The various components in the terminal device 1000 are coupled together via a bus system 1005. It is understood that the bus system 1005 is used to implement communication between these components. In addition to a data bus, the bus system 1005 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 1005 in Figure 10.

[0158] The user interface 1003 may include a display, keyboard, clicking device (e.g., mouse, trackball), touchpad, or touch screen.

[0159] It is understood that the memory 1002 in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1002 of the systems and methods described in this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0160] In some implementations, memory 1002 stores elements, executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 10021 and application program 10022.

[0161] The operating system 10021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 10022 includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of this application embodiment can be included in the application program 10022.

[0162] In this embodiment of the application, the terminal device 1000 further includes: a computer program stored on a memory 1002 and executable on a processor 1001, wherein the computer program, when executed by the processor 1001, implements the steps of the method 100.

[0163] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 1001. The processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the processor 1001. The processor 1001 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature computer-readable storage media in the art. The computer-readable storage medium is located in memory 1002. Processor 1001 reads information from memory 1002 and, in conjunction with its hardware, completes the steps of the above method. Specifically, the computer-readable storage medium stores a computer program, which, when executed by processor 1001, implements the steps of the above method 100 embodiment.

[0164] It is understood that the embodiments described in this application can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.

[0165] For software implementation, the techniques described in the embodiments of this application can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of this application. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or externally.

[0166] The terminal device 1000 can implement the various processes implemented by the terminal device in the foregoing embodiments and can achieve the same or equivalent technical effects. To avoid repetition, it will not be described again here.

[0167] Please refer to Figure 11, which is a structural diagram of the network device used in this embodiment of the application. It implements the details of method embodiment 700 and achieves the same effect. As shown in Figure 11, the network device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, wherein:

[0168] In this embodiment of the application, the network device 1100 further includes: a computer program stored on a memory 1103 and executable on a processor 1101, wherein the computer program implements the steps of method 700 when executed by the processor 1101.

[0169] In Figure 11, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1101 and memory represented by memory 1103 together. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 1102 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium.

[0170] The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 can store the data used by the processor 1101 when performing operations.

[0171] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of method embodiments 100 and 700 described above, achieving the same technical effects. To avoid repetition, these will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0172] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0173] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0174] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for configuring discontinuous reception DRX on a secondary link, the method comprising: The terminal device determines the DRX configuration information; Configure DRX according to the configuration information.

2. The method as described in claim 1, wherein, The terminal device determines the DRX configuration information including: The terminal device receives the DRX configuration information sent by the peer device; The configuration information is determined by the peer device.

3. The method as described in claim 2, wherein, The terminal device is a secondary link receiving device, and the peer device is a secondary link transmitting device; or The terminal device is a secondary link transmitting device, and the peer device is a secondary link receiving device.

4. The method of claim 3, wherein, After configuring DRX according to the configuration information, the method further includes: Send DRX feedback information to the peer device; The DRX feedback information indicates whether the DRX configuration was successful or failed.

5. The method of claim 1, wherein, Before the terminal device determines the DRX configuration information, the method further includes: The terminal device sends DRX assistance information or a DRX configuration request to the peer device; or The terminal device sends DRX auxiliary information or DRX configuration requests to the network device.

6. The method of claim 5, wherein, The DRX assistance information includes at least one of the following: DRX period and offset; The length of the DRX continuous listening timer; The length of the DRX inactive timer; The length of the HARQ round-trip timer; The length of the retransmission timer; The terminal device does not want the time-domain unit to be activated by DRX; The terminal device wants the time-domain unit to be activated by DRX.

7. The method of claim 1, wherein, The configuration information is agreed upon in advance by the terminal device and the peer device.

8. The method of claim 1, wherein, The terminal device determines the DRX configuration information including: The terminal device receives DRX configuration information sent by the network device; The configuration information is determined by the network device.

9. The method of claim 8, wherein, The method further includes: Receive instruction information; The indication information is used to indicate the peer device to which the configuration information is targeted; the network device is also used to perform DRX configuration for the peer device.

10. The method of claim 8, wherein, After configuring DRX according to the configuration information, the method further includes: Send DRX feedback information to the network device; The DRX feedback information indicates whether the DRX configuration was successful or failed.

11. A method for configuring DRX on a secondary link, the method being executed by a network device, comprising: Send DRX configuration information to the terminal device; wherein the configuration information is used by the terminal device to configure DRX.

12. The method of claim 11, wherein, The method further includes: The configuration information is sent to the peer device to which the configuration information is intended, and the configuration information is also used by the peer device to perform DRX configuration.

13. The method of claim 12, wherein, The method further includes: Send first indication information to the terminal device; wherein the first indication information is used to instruct the peer device; and / or Send a second indication message to the peer device; wherein the second indication message is used to instruct the terminal device.

14. A terminal device, comprising: The determination module is used to determine the configuration information of DRX; The configuration module is used to configure DRX based on the configuration information.

15. The terminal device as described in claim 14, wherein, The determining module is used to receive DRX configuration information sent by the peer device; The configuration information is determined by the peer device.

16. The terminal device as described in claim 15, wherein, The terminal device is a secondary link receiving device, and the peer device is a secondary link transmitting device; or The terminal device is a secondary link transmitting device, and the peer device is a secondary link receiving device.

17. The terminal device as claimed in claim 16, wherein, The determining module is also used to send DRX feedback information to the peer device; The DRX feedback information indicates whether the DRX configuration was successful or failed.

18. The terminal device as claimed in claim 14, wherein, The determining module is also used for Send DRX assistance information or DRX configuration request to the peer device; or Send DRX assistance information or DRX configuration requests to network devices.

19. The terminal device as claimed in claim 18, wherein, The DRX assistance information includes at least one of the following: DRX period and offset; The length of the DRX continuous listening timer; The length of the DRX inactive timer; The length of the HARQ RTT timer; The length of the retransmission timer; The terminal device does not want the time-domain unit to be activated by DRX; The terminal device wants the time-domain unit to be activated by DRX.

20. The terminal device as claimed in claim 14, wherein, The configuration information is agreed upon in advance by the terminal device and the peer device.

21. The terminal device as claimed in claim 14, wherein, The determining module is used to receive DRX configuration information sent by the network device; The configuration information is determined by the network device.

22. The terminal device as described in claim 21, wherein, The determining module is also used to receive indication information; The indication information is used to indicate the peer device to which the configuration information is targeted; the network device is also used to perform DRX configuration for the peer device.

23. The terminal device as described in claim 21, wherein, The determining module is also used to send DRX feedback information to the network device; The DRX feedback information indicates whether the DRX configuration was successful or failed.

24. A network device, comprising: The sending module is used to send DRX configuration information to the terminal device; wherein the configuration information is used by the terminal device to configure DRX.

25. The network device as claimed in claim 24, wherein, The sending module is also used for The configuration information is sent to the peer device to which the configuration information is intended, and the configuration information is used by the peer device to perform DRX configuration.

26. The network device of claim 25, wherein, The sending module is also used for Send first indication information to the terminal device; wherein the first indication information is used to instruct the peer device; and / or Send a second indication message to the peer device; wherein the second indication message is used to instruct the terminal device.

27. A terminal device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the DRX configuration method for the sub-link as described in any one of claims 1 to 10.

28. A network device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the DRX configuration method for the sub-link as described in any one of claims 11 to 13.

29. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the DRX configuration method for a secondary link as described in any one of claims 1 to 13.