DRX Determination Method, Device, Terminal, and Readable Storage Medium

Abstract

To provide a SL DRX determination method, device, terminal for improving reliability of a side link (SL) non-linked reception (DRX) arrangement, and readable storage media.SOLUTION: A DRX determination method includes transmitting, by a first terminal, first information to a second terminal. The first information is used to indicate N sets of sub-link SL DRX arrangement, where N is a positive integer. The method also includes receiving feedback information for the first information transmitted by the second terminal.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] (Cross - reference to Related Applications) This application is a divisional application of Japanese Patent Application No. 2023 - 522461, titled "DRX Determination Method, Apparatus, Terminal, and Readable Storage Medium", filed in Japan on April 12, 2023.

[0002] This application belongs to the field of communication technologies, and specifically relates to a DRX determination method, apparatus, terminal, and readable storage medium.

Background Art

[0003] The Long Term Evolution (LTE) system can support a Sidelink (SL) for direct communication between terminals without going through network - side equipment. To reduce the power consumption of terminals, a SL Discontinuous Reception (DRX) mechanism can be introduced.

[0004] The SL DRX mechanism is similar to the conventional Uu DRX mechanism. The main difference is that the application of DRX configuration is different. The SL DRX configuration is used for transmission and reception between a pair of terminals, while the Uu DRX configuration is used for transmission and reception between a terminal and network - side equipment. In the prior art, the Uu DRX configuration is determined by network - side equipment. Considering that when the SL DRX mechanism re - uses the Uu DRX mechanism, there may be problems such as the terminal operating outside the coverage range of the network - side equipment and the network - side equipment not fully understanding the service characteristics of SL communication, the reliability of the SL DRX configuration determined by network - side equipment is relatively low.

Summary of the Invention

[0005] Embodiments of this application provide a DRX determination method, apparatus, terminal, and readable storage medium that can realize negotiation of SL DRX configuration. According to a first aspect, a DRX determination method executed by a first terminal is provided, and the method includes: transmitting first information to a second terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer; receiving feedback information on the first information transmitted by the second terminal.

[0006] According to a second aspect, a DRX determination method executed by a second terminal is provided, and the method includes: receiving first information transmitted by a first terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer; transmitting feedback information on the first information to the first terminal.

[0007] According to a third aspect, a DRX determination device is provided, and the DRX determination device includes: a first transmission module for transmitting first information to a second terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer; a first reception module for receiving feedback information on the first information transmitted by the second terminal.

[0008] According to a fourth aspect, a DRX determination device is provided, and the DRX determination device includes: a second reception module for receiving first information transmitted by a first terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer; a second transmission module for transmitting feedback information on the first information to the first terminal.

[0009] According to a fifth aspect, a terminal is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, it realizes the steps of the method described in the first aspect or realizes the steps of the method described in the second aspect.

[0010] According to a sixth 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, it realizes the steps of the method described in the first aspect or realizes the steps of the method described in the second aspect.

[0011] According to a seventh aspect, a chip is provided, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor runs a program or instruction of a network-side device and is used to realize the method described in the first aspect or realize the method described in the second aspect.

[0012] According to an eighth aspect, a program product is provided, which is stored in a non-volatile storage medium. The program product is executed by at least one processor to realize the method described in the first aspect or realize the method described in the second aspect.

Advantages of the Invention

[0013] In the embodiments of the present application, the first terminal can instruct the second terminal to accept or not accept the SL DRX configuration proposed by the first terminal by indicating N sets of SL DRX configurations proposed by itself, and perform corresponding feedback. As can be seen, in the embodiments of the present application, the first terminal and the second terminal in SL communication can negotiate and determine an appropriate SL DRX configuration by themselves. In this way, the determined SL DRX configuration can better conform to the service characteristics of SL communication, thereby improving the reliability of the determined SL DRX configuration.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5a

Figure 5b

Figure 5c

Figure 6a

Figure 6b

Figure 6c

Figure 7a

Figure 7b

Figure 7c

Figure 8a

Figure 8b

Figure 8c

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0015] The following clearly and completely describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, not all of them. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the protection scope of the present application. Terms such as "first" and "second" in the description and claims of the present application are used to distinguish similar objects and are not for describing a specific order or sequence. It should be understood that such data is interchangeable when appropriate, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, without limiting the number of objects. For example, the first object may be one or more. In addition, "and / or" in the description and claims represents at least one of the connected objects, and the character " / " generally represents that the related objects before and after are in an "or" relationship.

[0016] It should be noted 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 applied to 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), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the described technology may be used in the systems and radio technologies mentioned above, or in other systems and radio technologies. However, the following description describes the New Radio (NR) system for illustrative purposes and uses NR terms in most of the following descriptions, and these technologies may also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0017] FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application are applicable. The wireless communication system includes a first terminal 11, a network-side device 12, and a second terminal 13. Here, the network-side device 12 may communicate with the first terminal 11 and the second terminal 13 respectively, and the first terminal 11 may communicate with the second terminal 12.

[0018] In actual applications, as shown in FIG. 1, the terminal may send information to the network-side device via the uplink (UpLink, UL), and the network-side device may send information to the terminal via the downlink (DownLink, DL). The first terminal 11 and the second terminal 13 may communicate directly via the sidelink (Sidelink, SL), that is, the first terminal 11 and the second terminal 13 may communicate without going through the network-side device 12. The sidelink may also be referred to as a side link, an edge link, a sublink, etc.

[0019] In an embodiment of the present application, in one implementation manner, the first terminal may be a transmitting terminal for SL communication, and the second terminal may be a receiving terminal for SL communication. In another implementation manner, the first terminal may be a receiving terminal for SL communication, and the second terminal may be a transmitting terminal for SL communication. Specifically, it may be determined according to the actual situation, and the embodiments of the present application do not limit this.

[0020] The terminal may also be referred to as a terminal device or a user terminal (User Equipment, UE). In actual applications, the terminal may be a mobile phone, a tablet personal computer, a laptop computer (or called a notebook computer), a personal digital assistant (Personal Digital Assistant, PDA), a palm top computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (Mobile Internet Device, MID), a wearable device or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. The wearable device may include a bracelet, earphones, glasses, etc. The network-side device may be a base station or a core network. Here, the base station may be called Node B, evolved Node B, access point, base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, basic service set (Basic Service Set, BSS), extended service set (Extended Service Set, ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting receiving point (Transmitting Receiving Point, TRP) or other appropriate terms in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms.

[0021] For the convenience of understanding, the following describes some contents related to the embodiments of this application.

[0022] I. Sidelink.

[0023] The Long Term Evolution (LTE) system can support Sidelink for directly transmitting data between terminals without going through network-side devices.

[0024] The design of LTE Sidelink is applicable to specific public safety matters (e.g., emergency communication at disaster sites such as fire sites or earthquakes) or Vehicle to Everything (V2X) communication. Vehicle to Everything communication includes various services, such as basic safety communication, advanced (automatic) driving, platooning, sensor extension, etc. Since LTE Sidelink only supports broadcast communication, LTE Sidelink is mainly used for basic safety communication. Other advanced V2X services with strict Quality of Service (QoS) requirements in terms of latency, reliability, etc. are supported by the 5th-Generation (5G) New Radio (NR) sidelink.

[0025] II. Transmission formats of Sidelink.

[0026] Sidelink transmission may include multiple transmission formats: Broadcast, Groupcast, and Unicast. Unicast is, as the name implies, a one-to-one transmission. Both Groupcast and Broadcast are one-to-many transmissions, but in Broadcast, there is no concept of UEs belonging to the same group. Unicast and Groupcast communications of Sidelink support the physical layer Hybrid Automatic Repeat Request (HARQ) feedback mechanism.

[0027] III. Resource allocation mode.

[0028] The sidelink resource allocation mode may include the following two types.

[0029] 1) Mode 1: The base station (BS) schedules the SL resources to be used by the UE for SL transmission (BS schedules SL resource(s) to be used by UE for SL transmission(s)). In this mode, since the network-side device (e.g., the base station) controls the resources and allocates them to each UE, this mode may be called the base station scheduling mode.

[0030] 2) Mode 2: The UE determines the SL transmission resources within the SL resources configured by the BS / network or pre-configured SL resources (UE determines, i.e., BS does not schedule, SL transmission resource(s) within SL resources configured by BS / network or pre-configured SL resources). In this mode, since each UE autonomously selects the resources, this mode may be called the UE autonomous mode.

[0031] IV. Uu air interface discontinuous reception (DRX), hereinafter abbreviated as Uu DRX.

[0032] Both LTE and NR have introduced the DRX mechanism. The DRX mechanism achieves power saving of the UE by configuring the DRX activation time (DRX on) and the DRX deactivation time (DRX off).

[0033] During the On Duration period of the DRX cycle, the UE shall monitor the Physical Downlink Control Channel (PDCCH).

[0034] If the UE is not monitoring the PDCCH during the On Duration period of a certain DRX cycle, that is, if it is not scheduled, after the On Duration period, the UE enters the off period of this DRX cycle, which is also called the Opportunity for DRX. In this case, the DRX on duration of this DRX is the length of the On Duration of this DRX, and this DRX may be called an active DRX. For example, if the On Duration of this DRX includes 10 slots, the DRX on length of this DRX includes 10 slots. For ease of understanding, refer to Figure 2. In Figure 2, the duration (On Duration) of the DRX cycle is DRX on.

[0035] During the On Duration period of a certain DRX cycle, when monitoring the PDCCH in a certain slot, that is, after receiving data scheduled in a certain slot, it is very likely that scheduling will continue in the next several slots. Therefore, each time the UE is scheduled with initial transmission data, the timer drx-InactivityTimer is started or restarted, and the UE remains in the activated state until this timer times out. In this case, the DRX on length of this DRX is jointly determined by the On Duration length of this DRX, the running time length of the drx-InactivityTimer, and the scheduling time point, and this DRX may be called the activated DRX. For example, if the On Duration of this DRX includes 10 slots, the scheduling time point is the 6th slot among these 10 slots, and the running time length of the drx-InactivityTimer is 10 slots, then the DRX on length of this DRX includes 15 slots.

[0036] When arranging DRX, parameters such as the duration timer (onDurationTimer), DRX inactivity timer (drx-InactivityTimer), DRX retransmission timer (drx-RetransmissionTimer), long DRX cycle start offset value (longDRX-CycleStartOffset) are arranged.

[0037] After the UE arranges DRX, if the decoding of transmitted or received data fails, the UE needs to enter the activation time, monitor the control channel, and wait for retransmission scheduled by the network.

[0038] For downlink data reception, after the UE receives the downlink data transmission indicated by the PDCCH and feeds back HARQ information, it starts a downlink backhaul timer (HARQ Round Trip Time (RTT) Timer) for the corresponding HARQ process. After the HARQ RTT Timer times out and the decoding of the data for this HARQ process fails, the UE starts a retransmission timer (drx-RetransmissionTimer), monitors the PDCCH, and waits for the transmission.

[0039] For uplink data transmission, after the UE receives the uplink data transmission indicated by the PDCCH, it starts an uplink backhaul timer HARQ RTT Timer for the corresponding HARQ process. After the HARQ RTT Timer times out, the UE starts a retransmission timer (drx-ULRetransmissionTimer), enters the active state, monitors the PDCCH, and waits for the transmission scheduled by the network.

[0040] Referring to Figure 3, Figure 3 is one of the flowcharts of the DRX determination method according to the embodiments of the present application. The DRX determination method shown in Figure 3 may be executed by a first terminal.

[0041] As shown in Figure 3, the DRX determination method may include the following steps.

[0042] Step 301, transmit first information to a second terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer.

[0043] When specifically implemented, in the first implementation manner, the N sets of SL DRX configurations may be the SL DRX configurations generated by the first terminal. In the second implementation manner, the N sets of SL DRX configurations may be the SL DRX configurations selected from the SL DRX configurations pre-acquired by the first terminal. Here, at least one set of SL DRX configurations may be configured by a network-side device, pre-configured, configured by a V2X layer, or agreed upon by a protocol. Specifically, it may be determined according to the actual situation, and the embodiments of the present application are not limited thereto.

[0044] Optionally, the SL DRX configuration includes at least one of the period of the SL DRX, the offset amount with respect to the target reference time point, the duration length, the running time length of the inactivation timer, the running time length of the round-trip time (RTT) timer related to the hybrid automatic repeat request (HARQ) process, and the running time length of the retransmission timer.

[0045] Here, the target reference time point is the reference time point when the SL DRX configuration becomes effective. When specifically implemented, the target reference point may be determined by the first terminal, configured by a network-side device, pre-configured, configured by a V2X layer, or agreed upon by a protocol. Specifically, it may be determined according to the actual situation, and the embodiments of the present application are not limited thereto. It should be noted that the specific parameters included in the corresponding different SL DRX configurations may be the same or different, and the number of parameters included in the corresponding different SL DRX configurations may be equal or unequal. Specifically, it may be determined according to the actual situation, and the embodiments of the present disclosure are not limited thereto.

[0046] Step 302: Receive feedback information for the first information transmitted by the second terminal.

[0047] In an embodiment of the present application, after the second terminal obtains the N sets of SL DRX configurations proposed by the first terminal, the second terminal can determine whether to accept the N sets of SL DRX configurations and perform corresponding feedback.

[0048] When specifically realized, determining whether the second terminal accepts the N sets of SL DRX configurations may include any one of the following: 1) accepting at least one set of SL DRX configurations among the N sets of SL DRX configurations; 2) accepting only some parameters in at least one set of SL DRX configurations among the N sets of SL DRX configurations; 3) rejecting the N sets of SL DRX configurations.

[0049] For 1), the second terminal may indicate the SL DRX configuration accepted by the second terminal according to the feedback information. After receiving the feedback information, the first terminal may determine the target SL DRX configuration among the SL DRX configurations accepted by the second terminal and perform SL DRX communication with the second terminal using this target SL DRX configuration.

[0050] For 2), the second terminal may indicate the first parameter of the SL DRX configuration accepted by the second terminal according to the feedback information, and the first parameter may be a parameter accepted by the second terminal or a parameter rejected and modified by the second terminal.

[0051] When the first parameter is a parameter acceptable to the second terminal, after receiving the feedback information, the first terminal may re-propose the first parameter to the second terminal. The specific processing flow is the same as proposing the SL DRX configuration to the second terminal. Since the main difference between the two is that the proposed objects are different, the specific processing flow of re-proposing the first parameter to the second terminal may refer to the processing flow of proposing the SL DRX configuration to the second terminal, and will not be elaborated here any further.

[0052] When the first parameter is a parameter rejected and modified by the second terminal, after receiving the feedback information, the first terminal may decide whether to accept the first parameter. If accepted, determine the target SL DRX configuration among the SL DRX configurations accepted by both the first terminal and the second terminal, and use this target SL DRX configuration to perform SL DRX communication with the second terminal. If rejected, re-negotiate the SL DRX configuration with the second terminal, or set the direct link between the first terminal and the second terminal to the DRX non-active state (that is, when there is data to be transmitted and received, it is not in the DRX state but in the continuous transmission and reception state), or release the direct link between the first terminal and the second terminal.

[0053] Regarding (3), the second terminal may instruct the second terminal to reject the N sets of SL DRX configurations according to the feedback information. Furthermore, the second terminal may further instruct the SL DRX configuration proposed by the second terminal according to the feedback information.

[0054] If the feedback information does not indicate the SL DRX configuration proposed by the second terminal, after receiving the feedback information, the first terminal may renegotiate the SL DRX configuration with the second terminal, or set the direct link between the first terminal and the second terminal to the DRX-inactive state (i.e., when there is data to be transmitted and received, it is not in the DRX state but in the continuous transmission and reception state), or release the direct link between the first terminal and the second terminal.

[0055] If the feedback information indicates the SL DRX configuration proposed by the second terminal, after receiving the feedback information, the first terminal may decide whether to accept the SL DRX configuration proposed by the second terminal. If accepted, the first terminal may determine the target SL DRX configuration among the SL DRX configurations accepted by both the first terminal and the second terminal, and perform SL DRX communication with the second terminal using this target SL DRX configuration. If rejected, the first terminal may renegotiate the SL DRX configuration with the second terminal, or set the direct link between the first terminal and the second terminal to the DRX-inactive state (i.e., when there is data to be transmitted and received, it is not in the DRX state but in the continuous transmission and reception state), or release the direct link between the first terminal and the second terminal.

[0056] In the DRX determination method of the embodiments of the present application, the first terminal may instruct the second terminal of N sets of SL DRX configurations proposed by itself, and the second terminal may decide whether to accept the SL DRX configuration proposed thereby, and perform corresponding feedback. As can be seen, in the embodiments of the present application, the first terminal and the second terminal in the SL communication can negotiate and determine an appropriate SL DRX configuration by themselves. In this way, the reliability of the determined SL DRX configuration can be improved because the determined SL DRX configuration conforms to the service characteristics of the SL communication.

[0057] 1. The following describes the first information in the embodiments of the present application.

[0058] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations. That is, the first information can indicate the N sets of SL DRX configurations by carrying at least one of the N sets of SL DRX configurations and the N index values.

[0059] As can be seen from the above, in the first implementation method, the N sets of SL DRX configurations may be generated by the first terminal, and in the second implementation method, the N sets of SL DRX configurations may be selected by the first terminal. For the N sets of SL DRX configurations determined by different implementation methods, the manner in which the first information indicates the N sets of SL DRX configurations may be different. Specifically, it is described as follows.

[0060] For the N sets of SL DRX configurations determined by the above first implementation method, the first information includes at least the N sets of SL DRX configurations. In this way, the second terminal can obtain the N sets of SL DRX configurations only after receiving the first information. Further, the first information may further include the N index values. In this way, when the second terminal accepts some or all of the parameters of at least one set of SL DRX configurations among the N sets of SL DRX configurations, it can indicate the accepted SL DRX configuration by directly replying with the index value, thereby saving signaling overhead.

[0061] For the N sets of SL DRX configurations determined by the second implementation method, since the second terminal can obtain the SL DRX configuration in a similar manner, the first information may only include the N index values, thereby saving signaling overhead.

[0062] Optionally, the first information further includes N feature information groups that correspond one-to-one with the N sets of SL DRX configurations.

[0063] When specifically implemented, the feature information group corresponding to the SL DRX configuration may be used to determine whether the second terminal accepts this SL DRX configuration or whether to modify some parameters of this SL DRX configuration.

[0064] Optionally, the feature information group includes at least one of SL DRX configuration priority, Quality of Service (QoS), Logical Channel (LC) identifier (ID), logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0065] When specifically implemented, QoS may include parameters such as the priority, delay, reliability, etc. of data packets or data streams. The SL DRX configuration priority of the SL DRX configuration is to determine whether to allow modification of the parameters in this SL DRX configuration. For example, only when the SL DRX configuration priority of a certain SL DRX configuration is lower than the preset SL DRX configuration priority, the modification of this SL DRX configuration is allowed, otherwise, the modification of this SL DRX configuration is not allowed, and to determine the target SL DRX configuration. For example, when there are multiple SL DRX configurations determined by negotiation between the first terminal and the second terminal, the SL DRX configuration with the highest SL DRX configuration priority among these multiple SL DRX configurations is selected as the target SL DRX configuration, and the SL DRX configuration may be adopted to perform SL DRX communication. It may be used for any one of them.

[0066] The characteristic information group may be arranged by network-side devices, pre-arranged, arranged by the V2X layer, or agreed upon by a protocol. Specifically, it may also be determined according to the actual situation. The embodiments of the present application do not limit this. It should be noted that the specific parameters included in the characteristic information groups corresponding to different SL DRX configurations may be the same or different, and the number of parameters included in the characteristic information groups corresponding to different SL DRX configurations may be equal or not equal. Specifically, it may also be determined according to the actual situation. The embodiments of the present disclosure do not limit this.

[0067] Optionally, the first information may be carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control (RRC) reconfiguration message, and an SL DRX configuration request message.

[0068] When specifically implemented, the first terminal and the second terminal may negotiate the SL DRX configuration through different processes. When negotiating the SL DRX configuration through different processes, the first information may be carried by different messages. Specifically, it is described as follows.

[0069] Method 1: The first terminal may multiplex a conventional process, such as a PC5 unicast link establishment process, a PC5 unicast link modification process, a PC5 RRC reconfiguration process, etc., to negotiate the SL DRX configuration, thereby saving signaling overhead.

[0070] Specifically, when the negotiation of the SL DRX configuration occurs in the PC5 unicast link establishment process, the first information may be carried by a direct link establishment request message. When the negotiation of the SL DRX configuration occurs in the PC5 unicast link modification process, the first information may be carried by a direct link modification request message. When the negotiation of the SL DRX configuration occurs in the PC5 RRC reconfiguration process, the first information may be carried by a direct link RRC reconfiguration message.

[0071] Method 2: A dedicated process for negotiating the SL DRX configuration, such as a PC5-Signaling (S) or a PC5 RRC process, may be newly introduced. In this way, the negotiation of the SL DRX configuration can be decoupled from the combination with other flows and occur independently of other flows, thereby improving the flexibility of the negotiation of the SL DRX configuration.

[0072] When the negotiation of the SL DRX configuration occurs in the newly introduced process, the first information may be carried by an SL DRX configuration request message.

[0073] II. The following describes the feedback information in the embodiments of the present application.

[0074] 1) Optionally, the feedback information is M index values, and M index values, and a first parameter in a first SL DRX configuration, and any one of K sets of SL DRX configurations, wherein the M index values correspond one-to-one to M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer.

[0075] Specifically, it is described as follows.

[0076] When the feedback information includes M index values, it means that the second terminal accepts M sets of SL DRX configurations related to the M index values proposed by the first terminal.

[0077] When the feedback information includes M index values and a first parameter in a first SL DRX configuration, it means that the second terminal accepts at least some of the parameters of at least one set of SL DRX configurations proposed by the first terminal, where the at least one set of SL DRX configurations is an SL DRX configuration among the M sets of SL DRX configurations related to the M index values.

[0078] In this case, optionally, the first parameter may be either a parameter accepted by the second terminal in the first SL DRX configuration or a parameter modified by the second terminal in the first SL DRX configuration.

[0079] When the feedback information includes the K sets of SL DRX configurations, optionally, the K sets of SL DRX configurations are a) the K sets of SL DRX configurations being the SL DRX configurations among the N sets of SL DRX configurations, and b) the K sets of SL DRX configurations being obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal, and c) the K sets of SL DRX configurations being SL DRX configurations other than the N sets of SL DRX configurations, satisfying any one of them.

[0080] When the K sets of SL DRX configurations satisfy a), it represents that the second terminal accepts the K sets of SL DRX configurations proposed by the first terminal.

[0081] When the K sets of SL DRX configurations satisfy b), it represents that the second terminal accepts some proposals of the first terminal and gives its own proposals for the parts it does not accept.

[0082] When the K sets of SL DRX configurations satisfy c), it represents that the second terminal rejects the proposals of the first terminal and gives its own proposals.

[0083] For the feedback information in 1), optionally, the feedback information may be carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0084] As can be understood, the method of carrying the feedback information is related to the method of carrying the first information. When the first information is carried by a directory link establishment request message, the feedback information may be carried by a directory link establishment acceptance message. When the first information is carried by a directory link modification request message, the feedback information may be carried by a directory link modification acceptance message. When the first information is carried by a directory link RRC reconfiguration message, the feedback information may be carried by a directory link RRC reconfiguration completion message. When the first information is carried by an SL DRX configuration request message, the feedback information may be carried by an SL DRX configuration response message.

[0085] For the feedback information in 1), selectively, when the feedback information satisfies a first condition, after receiving the feedback information for the first information transmitted by the second terminal, the method further includes performing a first operation when the first terminal rejects the feedback information. Here, the first condition is that the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, that the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal, and includes any one of that the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations. The first operation is Transmitting second information to the second terminal, where the second information is used to indicate that negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. Setting the direct link to the DRX inactive state. Including any one of triggering renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0086] In this alternative embodiment, the feedback information satisfying the first condition represents that the feedback information has given a proposal of the second terminal. In this case, as can be understood from the content, after receiving the feedback information, the first terminal may decide whether to accept the proposal of the second terminal. If the proposal of the second terminal is rejected, that is, the feedback information is rejected, a first operation may be executed.

[0087] Optionally, the second information is carried by a direct link release request message. In this case, the reason for triggering the transmission of the direct link release request message is that negotiation of the SL DRX configuration between the first terminal and the second terminal has failed.

[0088] The setting the direct link to the DRX inactive state means setting the direct link between the first terminal and the second terminal to the DRX inactive state, that is, stopping data transmission and reception between the first terminal and the second terminal using the DRX method. If there is data transmission and reception between the first terminal and the second terminal, it may be understood that the data is in a continuous transmission and reception state.

[0089] It should be noted that when steps 301 and 302 occur in the PC5 unicast link establishment process, the feedback information is carried by the direct link establishment acceptance message. To indicate that a direct link connection has already been established between the first terminal and the second terminal, when the first operation includes triggering a re-negotiation of the SL DRX configuration between the first terminal and the second terminal, the first terminal may perform the re-negotiation of the SL DRX configuration through other processes, such as the PC5 unicast link modification process, the PC5 RRC reconfiguration process, the PC5-S or PC5 RRC process, etc.

[0090] When steps 301 and 302 occur in a process other than the PC5 unicast link establishment process, to indicate that a direct link connection has already been established between the first terminal and the second terminal, when the first operation includes triggering a re-negotiation of the SL DRX configuration between the first terminal and the second terminal, the first terminal may perform the re-negotiation of the SL DRX configuration through the same flow or a different flow, specifically, it may also be determined according to the actual situation, and the embodiments of the present application do not limit this.

[0091] 2) Optionally, the feedback information instructs to reject the acceptance of the N sets of SL DRX configurations.

[0092] It represents that for the feedback information in 1), the second terminal rejects the acceptance of the proposal of the first terminal and does not give its own proposal.

[0093] Optionally, the feedback information may be carried by any one of a direct link establishment rejection message, a direct link modification rejection message, a direct link RRC reconfiguration failure message, and an SL DRX configuration rejection message.

[0094] As can be understood, the method by which the feedback information is carried is related to the method by which the first information is carried. When the first information is carried by a directory link establishment request message, the feedback information may be carried by a directory link establishment rejection message. When the first information is carried by a directory link modification request message, the feedback information may be carried by a directory link modification rejection message. When the first information is carried by a directory link RRC reconfiguration message, the feedback information may be carried by a directory link RRC reconfiguration failure message. When the first information is carried by an SL DRX configuration request message, the feedback information may be carried by an SL DRX configuration rejection message.

[0095] Optionally, after receiving the feedback information for the first information sent by the second terminal, the method further includes performing a second operation, wherein the second operation includes sending second information to the second terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed, setting the directory link to a DRX non-active state, and triggering a renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0096] Optionally, the second information is carried by a directory link release request message. In this case, the reason for triggering the transmission of the directory link release request message is that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. For the above-mentioned setting the directory link to a DRX non-active state, reference may be made to the description and will not be further elaborated here.

[0097] It should be noted that when steps 301 and 302 occur in the PC5 unicast link establishment process, the feedback information is carried by a direct link establishment rejection message, indicating that a direct link connection has not been established between the first terminal and the second terminal yet. In this case, the second operation may not include transmitting second information to the second terminal.

[0098] In this alternative embodiment, the renegotiation of the SL DRX configuration may be the same as or different from the flow where steps 301 and 302 are located. Specifically, it may be determined according to the actual situation, and the embodiments of this application do not limit this.

[0099] In the embodiments of this application, the terminal may pre-acquire third information, and the third information is used to indicate at least one of an upper limit threshold value of the active time duration of SL DRX and a lower limit threshold value of the active time duration of SL DRX.

[0100] When specifically implemented, the upper limit threshold value and / or the lower limit threshold value may be arranged by the network-side device, pre-arranged, arranged by the V2X layer, or agreed upon by the protocol. Specifically, it may be determined according to the actual situation, and the embodiments of this application do not limit this.

[0101] When specifically implemented, the upper limit threshold value and / or the lower limit threshold value may be used for at least one of determining the active time duration of SL DRX proposed by the terminal itself and determining whether to accept the active time duration of SL DRX proposed by other terminals. Specifically, it is described as follows.

[0102] Optionally, before transmitting the first information to the second terminal, the method is as follows: Further including determining the N sets of SL DRX configurations based on third information, where the third information is used to indicate at least one of an upper threshold value of the activation time duration of SL DRX and a lower threshold value of the activation time duration of SL DRX.

[0103] In this alternative embodiment, the upper threshold value and / or the lower threshold value are used by the first terminal to determine the N sets of SL DRX configurations.

[0104] In this alternative embodiment, the activation time duration of SL DRX included in the N sets of SL DRX configurations may satisfy at least one of being less than or equal to the upper threshold value and being greater than or equal to the lower threshold value. Of course, as can be understood, in other embodiments, the activation time duration of SL DRX included in the N sets of SL DRX configurations may be a value greater than the upper threshold value or a value less than the lower threshold value, and specifically, it may be determined according to the actual situation, and the embodiments of this application do not limit this.

[0105] Optionally, when the feedback information satisfies a first condition, after receiving the feedback information on the first information transmitted by the second terminal, the method further includes: Determining whether to accept the feedback information based on third information, where the third information is used to indicate at least one of an upper threshold value of the activation time duration of SL DRX and a lower threshold value of the activation time duration of SL DRX. Here, the first condition is: The feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration. The K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal, The method includes any one of: the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations.

[0106] In this alternative embodiment, the upper threshold value and / or the lower threshold value may be used to determine whether the first terminal accepts the activation time duration of the SL DRX proposed by the second terminal.

[0107] When specifically implemented, for the upper threshold value, if the SL DRX activation time duration indicated by the feedback information is greater than the upper threshold value, the first terminal may reject this proposal; if the SL DRX activation time duration indicated by the feedback information is less than or equal to the upper threshold value, the first terminal may accept this proposal. In this way, it is possible to avoid the SL DRX activation time duration for which negotiation has succeeded being too long and reduce the power consumption of the terminal.

[0108] For the lower threshold value, if the SL DRX activation time duration indicated by the feedback information is less than the lower threshold value, the first terminal may accept this configuration. In this way, it is possible to avoid the first terminal frequently triggering renegotiation.

[0109] Referring to FIG. 4, FIG. 4 is a second flowchart of the DRX determination method according to an embodiment of the present application. The DRX determination method shown in FIG. 4 is executed by network-side equipment.

[0110] As shown in FIG. 4, the DRX determination method may include the following steps.

[0111] Step 401: Receive the first information sent by the first terminal, where the first information is used to indicate N sets of sub-link SL DRX configurations, and N is a positive integer.

[0112] Step 402: Send feedback information regarding the first information to the first terminal.

[0113] In the DRX determination method according to the embodiments of the present application, after the second terminal receives the N sets of SL DRX configurations proposed by the first terminal, the second terminal can decide whether to accept the proposed SL DRX configurations by itself and perform corresponding feedback. As can be seen, in the embodiments of the present application, the first terminal and the second terminal in SL communication can negotiate and determine an appropriate SL DRX configuration by themselves. In this way, the reliability of the determined SL DRX configuration can be improved because the determined SL DRX configuration is more suitable for the service characteristics of SL communication.

[0114] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations.

[0115] Optionally, the first information further includes N groups of characteristic information that correspond one-to-one with the N sets of SL DRX configurations.

[0116] Optionally, the group of characteristic information includes at least one of SL DRX configuration priority, quality of service (QoS), logical channel identifier, logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0117] Optionally, the SL DRX configuration includes at least one of a period of the SL DRX, an offset amount with respect to a target reference time point, a duration length, an operation time length of an inactivation timer, an operation time length of a round-trip time (RTT) timer related to a hybrid automatic repeat request (HARQ) process, and an operation time length of a retransmission timer, where the target reference time point is a reference time point at which the SL DRX configuration becomes effective.

[0118] Optionally, the first information is carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control (RRC) reconfiguration message, and an SL DRX configuration request message.

[0119] Optionally, the feedback information is M index values, M index values, and a first parameter in a first SL DRX configuration, any one of K sets of SL DRX configurations, where the M index values correspond one-to-one to M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer.

[0120] Optionally, the K sets of SL DRX configurations satisfy any one of the following: the K sets of SL DRX configurations are SL DRX configurations among the N sets of SL DRX configurations; the K sets of SL DRX configurations are obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX configurations are SL DRX configurations other than the N sets of SL DRX configurations.

[0121] Optionally, the first parameter is either a parameter accepted by the second terminal in the first SL DRX configuration or a parameter modified by the second terminal in the first SL DRX configuration.

[0122] Optionally, the feedback information is carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0123] Optionally, when the feedback information satisfies a first condition, after transmitting the feedback information on the first information to the first terminal, the method further includes: receiving second information transmitted by the first terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. Here, the first condition is: the feedback information includes M index values and a first parameter in the first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration; the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal; any one of the K sets of SL DRX configurations included in the feedback information being an SL DRX configuration other than the N sets of SL DRX configurations.

[0124] Optionally, the feedback information indicates rejection of acceptance of the N sets of SL DRX configurations.

[0125] Optionally, the feedback information is carried by any one of a directory link establishment rejection message, a directory link modification rejection message, a directory link RRC reconfiguration failure message, and an SL DRX configuration rejection message.

[0126] Optionally, after sending the feedback information for the first information to the first terminal, the method further includes: receiving second information sent by the first terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed.

[0127] Optionally, the second information is carried by a directory link release request message.

[0128] Optionally, before sending the feedback information for the first information to the first terminal, the method further includes: generating the feedback information based on third information, where the third information is used to indicate at least one of an upper limit threshold value of the activation time duration of the SL DRX and a lower limit threshold value of the activation time duration of the SL DRX.

[0129] In this optional embodiment, the upper limit threshold value and / or the lower limit threshold value may be used to determine whether the second terminal accepts the activation time duration of the SL DRX proposed by the first terminal.

[0130] When specifically implemented, if the SL DRX activation time length indicated by the first information is greater than the upper limit threshold with respect to the upper limit threshold, the second terminal may reject this proposal. If the SL DRX activation time length indicated by the first information is less than or equal to the upper limit threshold, the second terminal may accept this proposal or recommend an SL DRX activation time length. In this way, it is possible to avoid the SL DRX activation time length that has succeeded in negotiation from being too long and reduce the power consumption of the terminal.

[0131] With respect to the lower limit threshold, if the SL DRX activation time length indicated by the first information is less than the lower limit threshold, the second terminal may accept this configuration, without rejecting this configuration, without starting or activating a new SL DRX, or without negotiating a new SL DRX. In this way, it is possible to avoid the terminal from frequently triggering re-negotiation.

[0132] It should be noted that since this embodiment corresponds to an embodiment of the network-side device of the method in FIG. 3, reference may be made to the relevant description in the embodiment of the method in FIG. 3, and the same beneficial effects can be achieved. To avoid repetition of the description, it will not be described further here.

[0133] It should be noted that various alternative embodiments introduced in the embodiments of this application may be implemented in combination with each other or separately, and the embodiments of this application are not limited thereto.

[0134] For the convenience of understanding, it is exemplarily described as follows. In the embodiment of this application, 1) UE 1 (TX UE) sends an SL DRX configuration (SL DRX pattern) proposal, and UE 2 (RX UE) decides whether to accept the SL DRX configuration proposal. If not accepted, it may further give an SL DRX configuration proposal. UE 1 finally decides whether to accept the proposal.

[0135] The above information may be carried in an evolved form of the conventional signaling flow or a new signaling flow may be introduced.

[0136] UE1 may propose one set or multiple sets of SL DRX configurations, UE2 may determine one of the sets, and further, UE2 may modify some parameters.

[0137] Define the SL DRX configuration priority. The SL DRX pattern with a lower priority may be modified.

[0138] 2) For the case where the negotiation of the DRX configuration fails, provide processing methods, such as a) rejection, b) link release, c) re - negotiation, d) DRX off, etc. Specifically, refer to the following description and it will not be described here.

[0139] 3) The UE configures an SL DRX on - length upper - limit threshold for determining whether the corresponding activated or active SL DRX on - length is greater than or equal to this threshold.

[0140] 4) The UE configures an SL DRX on - length lower - limit threshold for determining whether the corresponding activated or active SL DRX on - length is greater than or equal to this threshold.

[0141] Example 1: The SL DRX negotiation occurs in the PC5 unicast link establishment process.

[0142] Step 1: UE1 sends at least one set of SL DRX pattern information carried in the direct link establishment request message to UE2.

[0143] Specifically, the SL DRX pattern information for each set may include parameters such as period, offset amount, on duration length, Inactivity timer length, RTT timer length related to the HARQ process, retransmission timer length, etc.

[0144] Note that the SL DRX pattern information for each set may further be related to one index value and be carried together in the direct link establishment request message.

[0145] Note that the SL DRX pattern information for each set may further be related to a set of SL DRX pattern attributes. This set of SL DRX pattern attributes includes at least one of priority, QoS (referring to delay, reliability, etc.), logical channel identifier (LCID), bearer identifier (bearer ID), QoS flow identifier (QoS flow index), application identifier (application ID), service identifier (service identifier), source address layer 2 identifier (source L2 ID), and destination address layer 2 identifier (destination L2 ID). The SL DRX pattern attributes may be arranged by the V2X layer, or arranged by the base station, or pre-arranged, or defined by the protocol.

[0146] Step 2: UE2 feeds back to UE1 the acceptable SL DRX pattern information carried in the direct link establishment acceptance message.

[0147] The representation method of the SL DRX pattern information acceptable to UE2 is at least one index value in Step 1, and Some parameters of a part of the set of SL DRX pattern information related to the index value corresponding to at least one index value in Step 1, that is, those that allow UE 2 to modify some parameters in the negotiation process, It is any one of at least one set of SL DRX pattern information. Here, it is not limited whether it is a copy of at least one set of SL DRX pattern information in Step 1, that is, UE 2 is allowed to modify some parameters based on Step 1 in the negotiation process. Further, it may be further limited that only the SL DRX patterns with a priority in Step 1 lower than a certain threshold can be modified.

[0148] Step 3: Based on Step 2, when UE 2 is allowed to modify some parameters in the negotiation process, after Step 2, UE 1 further determines whether to accept the SL DRX pattern information feedback by UE2. If it cannot be accepted, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is the failure of SL DRX negotiation), UE1 executes either setting the corresponding direct link to the DRX off state.

[0149] Step 4: Since UE 2 determines that there is no acceptable SL DRX pattern information, it feeds back a direct link establishment rejection message.

[0150] The direct link establishment rejection message may further include that the cause value is the failure of SL DRX negotiation.

[0151] Next, UE1 triggers the renegotiation of SL DRX, i.e., moves to step 1 and restarts the direct link establishment request message, and UE1 may perform either one of setting the corresponding direct link to the DRX off state.

[0152] For ease of understanding, refer to FIGS. 5a to 5c.

[0153] FIG. 5a shows the case where the negotiation of the SL DRX configuration is successful. As shown in FIG. 5a, the following steps may be included.

[0154] Step 1: UE1 sends a direct link establishment request message to UE2 to recommend at least one set of SL DRX configurations.

[0155] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0156] If UE2 accepts the SL DRX configuration recommended by UE1, execute step 3.

[0157] Step 3: UE2 sends a direct link establishment acceptance message to UE1 to indicate the SL DRX configuration accepted by UE2.

[0158] FIG. 5b shows the case where the negotiation of the SL DRX configuration fails. As shown in FIG. 5b, the following steps may be included.

[0159] Step 1: UE1 sends a direct link establishment request message to UE2 to recommend at least one set of SL DRX configurations.

[0160] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0161] If the SL DRX configuration recommended by UE1 is rejected, execute Step 3.

[0162] Step 3: UE2 sends a direct link establishment rejection message to UE1, and the direct link establishment rejection message may carry a rejection cause value indicating a failure in the negotiation of the SL DRX configuration.

[0163] Step 4: UE1 starts re-negotiating the SL DRX configuration and sends a direct link establishment request message to UE2.

[0164] Figure 5c shows the case where the negotiation of the SL DRX configuration fails. As shown in Figure 5c, the following steps may be included.

[0165] Step 1: UE1 sends a direct link establishment request message to UE2 for recommending at least one set of SL DRX configurations.

[0166] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0167] If the SL DRX configuration recommended by UE1 is modified, execute Step 3.

[0168] Step 3: UE2 sends a direct link establishment acceptance message to UE1, and the direct link establishment acceptance message may carry the modified SL DRX configuration.

[0169] Step 4: UE1 decides whether to accept the SL DRX configuration modified by UE2.

[0170] If the SL DRX configuration modified by UE2 is rejected, Step 5 may be executed.

[0171] Step 5: UE1 sends a directory link release request message to UE2, and the directory link release request message may carry a release cause value that is a negotiation failure of the SL DRX configuration.

[0172] Embodiment 2: The SL DRX negotiation occurs in the PC5 unicast link modification process.

[0173] Step 1: UE 1 sends at least one set of SL DRX pattern information carried in a directory link modification request message to UE2.

[0174] Specifically, each set of SL DRX pattern information may include parameters such as a period, an offset amount, an on duration length, an inactivity timer length, an RTT timer length related to a HARQ process, and a retransmission timer length.

[0175] In addition, each set of SL DRX pattern information is further related to one index value and may be carried together in a directory link establishment request message, a directory link modification request message, and a PC5 RRC reconfiguration message.

[0176] Note that the SL DRX pattern information of each set may further be related to the SL DRX pattern attributes of a set. The SL DRX pattern attributes of this set include at least one of priority, QoS (referring to delay, reliability, etc.), logical channel identifier (LCID), bearer identifier (bearer ID), QoS flow identifier (QoS flow index), application identifier (application ID), service identifier (service identifier), source address layer 2 identifier (source L2 ID), and destination address layer 2 identifier (destination L2 ID). The SL DRX pattern attributes may be arranged by the V2X layer, or arranged by the base station, or pre-arranged, or defined by a protocol, etc.

[0177] Step 2: UE2 feeds back to UE1 the acceptable SL DRX pattern information carried in the direct link modification acceptance message.

[0178] The expression method of the SL DRX pattern information acceptable to UE2 is at least one index value in Step 1, and part of the parameters of the SL DRX pattern information of the set related to the index value corresponding to at least one index value in Step 1, that is, those that allow UE 2 to modify some parameters in the negotiation process, and any one of at least one set of SL DRX pattern information. Here, it is not limited whether it is at least one set of SL DRX pattern information in Step 1, that is, UE 2 is allowed to modify some parameters in the negotiation process. Further, it may be further limited that only the SL DRX pattern with a priority lower than a certain threshold in Step 1 can be modified.

[0179] Based on Step 2, if UE 2 allows to modify some parameters in the negotiation process, after Step 2, UE 1 further determines whether to accept the SL DRX pattern information fed back by UE2. If it cannot be accepted, then, UE1 may send a direct link release request message to UE2 (the direct link release request message may further include that the cause value is the failure of SL DRX negotiation), UE1 does not release the direct link, but triggers the re-negotiation of SL DRX, that is, migrates to Step 1 and restarts the direct link modification request message, UE1 may execute any one of setting the corresponding direct link to the DRX off state.

[0180] Step 4: Since UE 2 determines that there is no acceptable SL DRX pattern information, it feeds back a direct link modification rejection message.

[0181] The direct link modification rejection message may further include that the cause value is the failure of SL DRX negotiation.

[0182] Next, UE1 may send a direct link release request message to UE2 (the direct link release request message may further include that the cause value is the failure of SL DRX negotiation), UE1 triggers the re-negotiation of SL DRX, that is, migrates to Step 1 and restarts the direct link modification request message, UE1 may execute any one of setting the corresponding direct link to the DRX off state.

[0183] For ease of understanding, refer to FIGS. 6a to 6c.

[0184] Figure 6a shows the case where the negotiation of the SL DRX configuration is successful. As shown in Figure 6a, the following steps may be included.

[0185] Step 1: UE1 sends a direct link modification request message to UE2 to recommend at least one set of SL DRX configurations.

[0186] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0187] If the SL DRX configuration recommended by UE1 is accepted, execute Step 3.

[0188] Step 3: UE2 sends a direct link modification acceptance message to UE1 to indicate the SL DRX configuration accepted by UE2.

[0189] Figure 6b shows the case where the negotiation of the SL DRX configuration fails. As shown in Figure 6b, the following steps may be included.

[0190] Step 1: UE1 sends a direct link modification request message to UE2 to recommend at least one set of SL DRX configurations.

[0191] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0192] If the SL DRX configuration recommended by UE1 is rejected, execute Step 3.

[0193] Step 3: UE2 sends a direct link modification rejection message to UE1, and the direct link modification rejection message may carry a cause value indicating the failure of the SL DRX configuration negotiation.

[0194] Step 4: UE1 sends a directory link release request message to UE2, and the directory link release request message may carry a release cause value indicating a negotiation failure of the SL DRX configuration.

[0195] Figure 6c shows the case where the negotiation of the SL DRX configuration fails. As shown in Figure 6c, it may include the following steps.

[0196] Step 1: UE1 sends a directory link modification request message to UE2 to recommend at least one set of SL DRX configurations.

[0197] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0198] If modifying the SL DRX configuration recommended by UE1, execute Step 3.

[0199] Step 3: UE2 sends a directory link modification acceptance message, and the directory link modification acceptance message may carry the modified SL DRX configuration to UE1.

[0200] Step 4: UE1 decides whether to accept the SL DRX configuration modified by UE2.

[0201] If rejecting the SL DRX configuration modified by UE2, Step 5 may be executed.

[0202] Step 5: UE1 sends a directory link release request message to UE2, and the directory link release request message may carry a release cause value indicating a negotiation failure of the SL DRX configuration.

[0203] Embodiment 3: The SL DRX negotiation occurs in the PC5 RRC reconfiguration process.

[0204] Step 1: UE 1 sends at least one set of SL DRX pattern information carried in the PC5 RRC reconfiguration message to UE2.

[0205] Specifically, each set of SL DRX pattern information may include parameters such as period, offset amount, on duration length, Inactivity timer length, RTT timer length related to the HARQ process, retransmission timer length, etc.

[0206] In addition, each set of SL DRX pattern information is further related to one index value and may be carried together in the direct link establishment request message, direct link modification request message, and PC5 RRC reconfiguration message.

[0207] In addition, each set of SL DRX pattern information may be further related to a set of SL DRX pattern attributes. This set of SL DRX pattern attributes includes at least one of priority, QoS (referring to delay, reliability, etc.), logical channel identifier (LCID), bearer identifier (bearer ID), QoS flow identifier (QoS flow index), application identifier (application ID), service identifier (service identifier), source address layer 2 identifier (source L2 ID), and destination address layer 2 identifier (destination L2 ID). The SL DRX pattern attributes may be configured by the V2X layer, or by the base station, or pre-configured, or defined by the protocol.

[0208] Step 2: UE2 feeds back the acceptable SL DRX pattern information carried in the PC5 RRC reconfiguration complete message to UE1.

[0209] The representation method of the SL DRX pattern information acceptable to UE2 is At least one index value in step 1, and Some parameters of a part of the set of SL DRX pattern information related to the index value corresponding to at least one index value in step 1, that is, those that allow UE 2 to modify some parameters in the negotiation process, It is any one of at least one set of SL DRX pattern information. Here, it is not limited whether it is at least one set of SL DRX pattern information in step 1, that is, UE 2 is allowed to modify some parameters in the negotiation process. Further, it may be further limited that only SL DRX patterns with a priority in step 1 lower than a certain threshold can be modified.

[0210] Based on step 2, when UE 2 is allowed to modify some parameters in the negotiation process, after step 2, UE 1 further determines whether to accept the SL DRX pattern information fed back by UE2. If it cannot be accepted, then, UE1 may perform any one of the following: sending a direct link release request message to UE2 (the direct link release request message may further include that the cause value is a failure in SL DRX negotiation), UE1 does not release the direct link but triggers re - negotiation of SL DRX, that is, migrates to step 1 and restarts the PC5 RRC re - configuration message, UE1 may perform any one of setting the corresponding direct link to the DRX off state.

[0211] Step 4: Since UE 2 determines that there is no acceptable SL DRX pattern information, it feeds back a PC5 RRC re - configuration failure message.

[0212] The PC5 RRC reconfiguration failure message may further include that the cause value is the failure of the SL DRX negotiation.

[0213] Next, UE1 may send a direct link release request message to UE2 (the direct link release request message may further include that the cause value is the failure of the SL DRX negotiation), UE1 may trigger the renegotiation of SL DRX, that is, transition to step 1 and restart the PC5 RRC reconfiguration message, UE1 may perform any one of setting the corresponding direct link to the DRX off state.

[0214] For the convenience of understanding, refer to FIGS. 7a to 7c.

[0215] FIG. 7a shows the case where the negotiation of the SL DRX configuration is successful. As shown in FIG. 7a, the following steps may be included.

[0216] Step 1: UE1 sends a direct link RRC reconfiguration message to UE2 to recommend at least one set of SL DRX configurations.

[0217] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0218] If accepting the SL DRX configuration recommended by UE1, execute step 3.

[0219] Step 3: UE2 sends a direct link RRC reconfiguration success message to UE1 to indicate the SL DRX configuration accepted by UE2.

[0220] FIG. 7b shows the case where the negotiation of the SL DRX configuration fails. As shown in FIG. 7b, the following steps may be included.

[0221] Step 1: UE1 sends a direct link RRC reconfiguration message to UE2 to recommend at least one set of SL DRX configurations to UE2.

[0222] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0223] If the SL DRX configuration recommended by UE1 is rejected, execute Step 3.

[0224] Step 3: UE2 sends a direct link RRC reconfiguration failure message to UE1, and the direct link RRC reconfiguration failure message may carry a rejection cause value indicating a failure in the negotiation of the SL DRX configuration.

[0225] Step 4: UE1 starts re - negotiation of the SL DRX configuration and sends a direct link RRC reconfiguration message to UE2.

[0226] Figure 7c shows the case where the negotiation of the SL DRX configuration fails. As shown in Figure 7c, the following steps may be included.

[0227] Step 1: UE1 sends a direct link RRC reconfiguration message to UE2 to recommend at least one set of SL DRX configurations to UE2.

[0228] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0229] If the SL DRX configuration recommended by UE1 is modified, execute Step 3.

[0230] Step 3: UE2 sends a direct link RRC reconfiguration success message to UE1, and the direct link RRC reconfiguration success message may carry the modified SL DRX configuration.

[0231] Step 4: UE1 decides whether to accept the SL DRX configuration modified by UE2.

[0232] If the SL DRX configuration modified by UE2 is rejected, step 5 may be executed.

[0233] Step 5: UE1 sends a direct link release request message to UE2, and the direct link release request message may carry a release cause value indicating a failure in the negotiation of the SL DRX configuration.

[0234] Embodiment 4: The SL DRX negotiation occurs in a newly introduced PC5-S or PC5 RRC process.

[0235] The concepts of Embodiments 1, 2, and 3 are realized by modifying the conventional signaling flow, while the concept of this Embodiment 4 is to introduce a new signaling flow, and the advantage is that it is decoupled from the combination with the conventional signaling flow and can occur independently.

[0236] Step 1: UE 1 sends at least one set of SL DRX pattern information carried in a newly introduced PC5-S or PC5 RRC message (which may be named an SL DRX configuration request message) to UE2.

[0237] Specifically, each set of SL DRX pattern information may include parameters such as a period, an offset amount, an on duration length, an inactivity timer length, an RTT timer length related to a HARQ process, and a retransmission timer length.

[0238] In addition, each set of SL DRX pattern information is further related to one index value and may be carried together in a direct link establishment request message, a direct link modification request message, and a PC5 RRC reconfiguration message.

[0239] In addition, the SL DRX pattern information of each set may be further related to the SL DRX pattern attributes of a set. The SL DRX pattern attributes of this set include at least one of priority, QoS (referring to delay, reliability, etc.), logical channel identifier (LCID), bearer identifier (bearer ID), QoS flow identifier (QoS flow index), application identifier (application ID), service identifier (service identifier), source address layer 2 identifier (source L2 ID), and destination address layer 2 identifier (destination L2 ID). The SL DRX pattern attributes may be arranged by the V2X layer, or arranged by the base station, or pre-arranged, or defined by the protocol.

[0240] Step 2: UE2 feeds back to UE1 the acceptable SL DRX pattern information carried in the newly introduced PC5-S or PC5 RRC message (which may be named the SL DRX configuration response message).

[0241] The expression method of the SL DRX pattern information acceptable to UE2 is at least one index value in Step 1, and part of the parameters of the SL DRX pattern information of the set related to the index value corresponding to at least one index value in Step 1, that is, those that allow UE 2 to modify some parameters in the negotiation process, and It is any one of at least one set of SL DRX pattern information. Here, it is not limited whether it is at least one set of SL DRX pattern information in step 1, that is, UE 2 is allowed to modify some parameters in the negotiation process. Further, it may be further limited that only the SL DRX pattern with the priority in step 1 lower than a certain threshold can be modified.

[0242] Based on step 2, when UE 2 is allowed to modify some parameters in the negotiation process, after step 2, UE 1 further determines whether to accept the SL DRX pattern information fed back by UE 2. If it cannot be accepted, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is the failure of SL DRX negotiation), UE1 does not release the direct link, but triggers the renegotiation of SL DRX, that is, migrates to step 1 and restarts the SL DRX configuration request message, UE1 executes any one of setting the corresponding direct link to the DRX off state.

[0243] Step 4: Since UE 2 determines that there is no acceptable SL DRX pattern information, it feeds back a newly introduced PC5-S or PC5 RRC message (which may be named as the SL DRX configuration rejection message).

[0244] The SL DRX configuration rejection message may further include that the cause value is the failure of SL DRX negotiation.

[0245] Next, UE1 sends a directory link release request message to UE2 (the directory link release request message may further include that the cause value is a negotiation failure of SL DRX), and UE1 triggers the renegotiation of SL DRX, that is, proceeds to step 1 and restarts the SL DRX configuration request message, and UE1 may perform any one of setting the corresponding directory link to the DRX off state.

[0246] For ease of understanding, refer to FIGS. 8a to 8c.

[0247] FIG. 8a shows the case where the negotiation of the SL DRX configuration is successful. As shown in FIG. 8a, the following steps may be included.

[0248] Step 1: UE1 sends an SL DRX configuration request message to UE2 to recommend at least one set of SL DRX configurations.

[0249] Step 2: UE2 decides whether to accept the SL DRX configuration recommended by UE1.

[0250] If UE2 accepts the SL DRX configuration recommended by UE1, execute step 3.

[0251] Step 3: UE2 sends an SL DRX configuration response message to UE1 to indicate the SL DRX configuration accepted by UE2.

[0252] FIG. 8b shows the case where the negotiation of the SL DRX configuration fails. As shown in FIG. 8b, the following steps may be included.

[0253] Step 1: UE1 sends an SL DRX configuration request message to UE2 to recommend at least one set of SL DRX configurations.

[0254] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0255] If UE2 rejects the SL DRX configuration recommended by UE1, execute Step 3.

[0256] Step 3: UE2 sends a SL DRX configuration rejection message to UE1, and the SL DRX configuration rejection message may carry a rejection cause value indicating a negotiation failure of the SL DRX configuration.

[0257] Step 4: UE1 initiates renegotiation of the SL DRX configuration and sends a SL DRX configuration request message to UE2.

[0258] Figure 8c shows the case where the negotiation of the SL DRX configuration fails. As shown in Figure 8c, the following steps may be included.

[0259] Step 1: UE1 sends a SL DRX configuration request message to UE2 to recommend at least one set of SL DRX configurations.

[0260] Step 2: UE2 determines whether to accept the SL DRX configuration recommended by UE1.

[0261] If UE2 modifies the SL DRX configuration recommended by UE1, execute Step 3.

[0262] Step 3: UE2 sends a SL DRX configuration response message to UE1, and the SL DRX configuration response message may carry the modified SL DRX configuration.

[0263] Step 4: UE1 determines whether to accept the SL DRX configuration modified by UE2.

[0264] If UE1 rejects the SL DRX configuration modified by UE2, Step 5 may be executed.

[0265] Step 5: UE1 sends a directory link release request message to UE2, and the directory link release request message may carry a release cause value that is a negotiation failure of the SL DRX configuration.

[0266] Example 5: The SL UE has an upper limit value of one SL DRX on length that is configured by the V2X layer, or configured by the base station, or pre-configured.

[0267] Before Examples 1 to 4, the SL UE may further receive an upper limit value of one SL DRX on length that is configured by the V2X layer, or configured by the base station, or pre-configured. If the activated or active SL DRX on length exceeds this upper limit value, the UE may reject the link establishment; otherwise, it may establish the connection or recommend an available DRX configuration. The use of this value is embodied in that it can be referred to when the UE determines whether to accept the SL DRX pattern in terms of power saving and service QoS.

[0268] Example 6: The SL UE has a lower limit value of one SL DRX on length that is configured by the V2X layer, or configured by the base station, or pre-configured.

[0269] Before Examples 1 to 4, the SL UE may further receive a lower limit value of one SL DRX on length that is configured by the V2X layer, or configured by the base station, or pre-configured. If the activated or active SL DRX on length is less than this lower limit value, the UE may reject the configuration, activate or active a new SL DRX, or is unable to negotiate a new SL DRX. The use of this value is embodied in that it can avoid the UE triggering frequent re-negotiations, which is advantageous for system performance.

[0270] Embodiments of the present invention design the details of sidelink DRX configuration negotiation signaling and the processing for unsuccessful negotiation, thereby ensuring the normal operation of sidelink DRX and achieving the purpose of sidelink UE power saving.

[0271] It should be noted that for the DRX determination method according to the embodiments of the present application, the execution entity may be a DRX determination device or a control module for executing the DRX determination method in this DRX determination device. In the embodiments of the present application, taking the execution of the DRX determination method by the DRX determination device as an example, the DRX determination device according to the embodiments of the present application will be described.

[0272] Referring to FIG. 9, FIG. 9 is one of the structural diagrams of the DRX determination device according to the embodiments of the present application.

[0273] As shown in FIG. 9, the DRX determination device 900 includes a first transmission module 901 for transmitting first information to a second terminal, where the first information is used to indicate N sets of sidelink (SL) DRX configurations, and N is a positive integer, and the first transmission module 901, and a first reception module 902 for receiving feedback information for the first information transmitted by the second terminal.

[0274] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations.

[0275] Optionally, the first information further includes N groups of feature information that correspond one-to-one with the N sets of SL DRX configurations.

[0276] Optionally, the feature information group includes at least one of SL DRX configuration priority, quality of service QoS, logical channel identifier, logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0277] Optionally, the SL DRX configuration includes at least one of the period of the SL DRX, the offset amount with respect to the target reference time point, the duration, the running time of the inactivation timer, the running time of the round-trip time RTT timer related to the hybrid automatic repeat request HARQ process, and the running time of the retransmission timer. Here, the target reference time point is the reference time point when the SL DRX configuration becomes effective.

[0278] Optionally, the first information is carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control RRC reconfiguration message, and an SL DRX configuration request message.

[0279] Optionally, the feedback information is M index values, M index values, and the first parameter in the first SL DRX configuration, any one of K sets of SL DRX configurations, Here, the M index values correspond one-to-one with M sets of SL DRX configurations among the N sets of SL DRX configurations. The first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations. M is a positive integer less than or equal to N, and K is a positive integer.

[0280] Optionally, the K sets of SL DRX configurations are The SL DRX configuration of the K set is the SL DRX configuration among the SL DRX configurations of the N set, The SL DRX configuration of the K set is obtained by modifying the SL DRX configuration in the SL DRX configurations of the N set by the second terminal, Any one of the following is satisfied: the SL DRX configuration of the K set is an SL DRX configuration other than the SL DRX configurations of the N set.

[0281] Optionally, the first parameter is either a parameter accepted by the second terminal in the first SL DRX configuration or a parameter modified by the second terminal in the first SL DRX configuration.

[0282] Optionally, the feedback information is carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0283] Optionally, when the feedback information satisfies a first condition, the DRX determination device 900 further includes a first execution module for executing a first operation when the first terminal rejects the feedback information, where the first condition is the feedback information includes M index values and a first parameter in the first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, the SL DRX configuration of the K set included in the feedback information is obtained by modifying the SL DRX configuration in the SL DRX configurations of the N set by the second terminal, Either one of the following is included: the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations.

[0284] The first operation is transmitting second information to the second terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed, and setting the direct link to the DRX-inactive state, and either one of triggering a renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0285] Optionally, the feedback information instructs to reject the acceptance of the N sets of SL DRX configurations.

[0286] Optionally, the feedback information is carried by any one of a direct link establishment rejection message, a direct link modification rejection message, a direct link RRC reconfiguration failure message, and an SL DRX configuration rejection message.

[0287] Optionally, the DRX decision device 900 further includes a second execution module for executing a second operation, where the second operation is transmitting second information to the second terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed, and setting the direct link to the DRX-inactive state, and either one of triggering a renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0288] Optionally, the second information is carried by a directory link release request message.

[0289] Optionally, the DRX determination device further includes a first determination module for determining the N sets of SL DRX configurations based on third information, where the third information is used to indicate at least one of an upper limit threshold value of the activation time duration of the SL DRX and a lower limit threshold value of the activation time duration of the SL DRX.

[0290] Optionally, when the feedback information satisfies a first condition, the DRX determination device further includes a second determination module for determining whether to accept the feedback information based on third information, where the third information is used to indicate at least one of an upper limit threshold value of the activation time duration of the SL DRX and a lower limit threshold value of the activation time duration of the SL DRX, where the first condition is the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal, and the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations.

[0291] The DRX determination device in the embodiments of this application may be a device, or may be a component, integrated circuit, or chip in a terminal. This device may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include, but is not limited to, the types of terminal 11 listed above. The non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a deposit and payment machine, or a self-service machine, etc. The embodiments of this application are not specifically limited.

[0292] The DRX determination device in the embodiments of this application may be a device having an operating system. This operating system may be an Android operating system, an iOS operating system, or other possible operating systems. The embodiments of this application are not specifically limited.

[0293] The DRX determination device 900 according to the embodiments of this application realizes each process realized by the method embodiment in FIG. 3 and can achieve the same technical effects. To avoid repetition of the description, it will not be described further here.

[0294] Referring to FIG. 10, FIG. 10 is a second structural diagram of the DRX determination device according to the embodiments of this application.

[0295] As shown in FIG. 10, the DRX determination device 1000 includes a second receiving module 1001 for receiving first information transmitted by a first terminal, where the first information is used to indicate N sets of sub-link SL DRX configurations, and N is a positive integer, and the second receiving module 1001, and a second transmitting module 1002 for transmitting feedback information regarding the first information to the first terminal.

[0296] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations.

[0297] Optionally, the first information further includes N groups of characteristic information that correspond one-to-one with the N sets of SL DRX configurations.

[0298] Optionally, the group of characteristic information includes at least one of SL DRX configuration priority, quality of service QoS, logical channel identifier, logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0299] Optionally, the SL DRX configuration includes at least one of the period of SL DRX, the offset amount with respect to the target reference time point, the duration length, the running time length of the inactivation timer, the running time length of the round-trip time RTT timer related to the hybrid automatic repeat request HARQ process, and the running time length of the retransmission timer, where the target reference time point is the reference time point when the SL DRX configuration becomes effective.

[0300] Optionally, the first information is carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control RRC reconfiguration message, and an SL DRX configuration request message.

[0301] Optionally, the feedback information is M index values, M index values, and the first parameter in the first SL DRX configuration, any one of the K sets of SL DRX configurations, Here, the M index values correspond one-to-one with M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer.

[0302] Optionally, the K sets of SL DRX configurations satisfy any one of the following: the K sets of SL DRX configurations are among the SL DRX configurations of the N sets of SL DRX configurations; the K sets of SL DRX configurations are obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX configurations are SL DRX configurations other than the N sets of SL DRX configurations.

[0303] Optionally, the first parameter is either a parameter accepted by the second terminal in the first SL DRX configuration or a parameter modified by the second terminal in the first SL DRX configuration.

[0304] Optionally, the feedback information is carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0305] Optionally, when the feedback information satisfies a first condition, after transmitting the feedback information on the first information to the first terminal, the DRX determination device 1000 further includes a third receiving module for receiving second information transmitted by the first terminal, and the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. Here, the first condition is that the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, and the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal, and any one of the K sets of SL DRX configurations included in the feedback information is an SL DRX configuration other than the N sets of SL DRX configurations.

[0306] Optionally, the feedback information instructs to reject the acceptance of the N sets of SL DRX configurations.

[0307] Optionally, the feedback information is carried by any one of a direct link establishment rejection message, a direct link modification rejection message, a direct link RRC reconfiguration failure message, and an SL DRX configuration rejection message.

[0308] Optionally, the DRX determination device 1000 further includes a fourth receiving module for receiving second information transmitted by the first terminal, and the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed.

[0309] Optionally, the second information is carried by a direct link release request message.

[0310] Optionally, the DRX determination device Further comprising a third determination module for generating the feedback information based on third information, where the third information is used to indicate at least one of an upper threshold value of the activation time duration of SL DRX and a lower threshold value of the activation time duration of SL DRX.

[0311] The DRX determination device in the embodiments of the present application may be a device, or may be a component, integrated circuit, or chip in network-side equipment. The network-side equipment may include the types of network-side equipment 12 listed above, but is not limited thereto, and the embodiments of the present application do not specifically limit it.

[0312] The DRX determination device 1000 according to the embodiments of the present application realizes each process realized by the embodiment of the method in FIG. 4 and can achieve the same technical effect, and for the sake of avoiding repeated description, it will not be described further herein.

[0313] Optionally, as shown in FIG. 11, the embodiments of the present application further provide a terminal 1100, including a processor 1101, a memory 1102, and a program or instruction stored in the memory 1102 and operable on the processor 1101. For example, when this program or instruction is executed by the processor 1101, each process of the embodiment of the method in FIG. 3 or FIG. 4 above can be realized and the same technical effect can be achieved. For the sake of avoiding repeated description, it will not be described further herein.

[0314] FIG. 12 is a schematic diagram of the hardware structure of a terminal for realizing the embodiments of the present application.

[0315] This terminal 1200 includes components such as a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209, and a processor 1210, but is not limited thereto.

[0316] As can be understood by those skilled in the art, the terminal 1200 may further include a power source (e.g., a battery) for supplying power to each component. The power source may be logically connected to the processor 1210 by a power management system, thereby enabling the power management system to implement functions such as charge and discharge management and power consumption management. The terminal structure shown in FIG. 12 does not constitute a limitation on the terminal. The terminal may include more or fewer components than those shown, or a combination of some components, or a different arrangement of components, which will not be further described herein.

[0317] It should be understood that in the embodiments of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042. The graphics processing unit 12041 processes the image data of a still image or a video obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be arranged in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. The other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, and an operation lever, which will not be further described herein.

[0318] In the embodiments of the present application, after receiving the downlink data from the network-side device, the radio frequency unit 1201 causes the processor 1210 to process it, and also transmits the uplink data to the network-side device. Generally, the radio frequency unit 1201 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0319] The memory 1209 may be used to store software programs or instructions and various data. The memory 1209 may mainly include a program or instruction storage area and a data storage area. Here, the program or instruction storage area can store an operating system, an application program or instruction (such as a voice playback function, an image playback function, etc.) required for at least one function. Note that the memory 1209 may include a high-speed random access memory and may also include a non-volatile memory. Here, 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. For example, it may be at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory devices.

[0320] The processor 1210 may include one or more processing units. Optionally, the processor 1210 may integrate an application processor and a modem processor. Here, the application processor mainly processes an operating system, a user interface, and an application program or instruction, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. As can be understood, the above modem processor may not be integrated into the processor 1210.

[0321] In Case 1, the terminal 1200 is the above first terminal.

[0322] In this case, the radio frequency unit 1201 To send first information to a second terminal, where the first information is used to indicate N sets of sub-link SL DRX configurations, and N is a positive integer, It is used to receive feedback information on the first information transmitted by the second terminal.

[0323] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations.

[0324] Optionally, the first information further includes N groups of feature information that correspond one-to-one with the N sets of SL DRX configurations.

[0325] Optionally, the feature information group includes at least one of SL DRX configuration priority, quality of service QoS, logical channel identifier, logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0326] Optionally, the SL DRX configuration includes at least one of the period of SL DRX, the offset amount with respect to the target reference time point, the duration, the running time of the inactivation timer, the running time of the round-trip time RTT timer related to the hybrid automatic repeat request HARQ process, and the running time of the retransmission timer. Here, the target reference time point is the reference time point when the SL DRX configuration becomes effective.

[0327] Optionally, the first information is carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control RRC reconfiguration message, and an SL DRX configuration request message.

[0328] Optionally, the feedback information is M index values, and M index values, and a first parameter in the first SL DRX configuration, and either one of K sets of SL DRX configurations, wherein the M index values correspond one-to-one to M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer.

[0329] Optionally, the K sets of SL DRX configurations are the K sets of SL DRX configurations are SL DRX configurations among the N sets of SL DRX configurations, the K sets of SL DRX configurations are obtained by modifying the SL DRX configurations in the N sets of SL DRX configurations by the second terminal, and the K sets of SL DRX configurations satisfy either one of being SL DRX configurations other than the N sets of SL DRX configurations.

[0330] Optionally, the first parameter is either one of a parameter accepted by the second terminal in the first SL DRX configuration and a parameter modified by the second terminal in the first SL DRX configuration.

[0331] Optionally, the feedback information is carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0332] Optionally, when the feedback information satisfies a first condition, the processor 1210 When the first terminal rejects the feedback information, it is used to execute a first operation. Here, the first condition is the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration; the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal; and the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations.

[0333] The first operation includes transmitting second information to the second terminal by the radio frequency unit 1201, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to the DRX inactive state; and triggering a renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0334] Optionally, the feedback information instructs to reject the acceptance of the N sets of SL DRX configurations.

[0335] Optionally, the feedback information is carried by any one of a direct link establishment rejection message, a direct link modification rejection message, a direct link RRC reconfiguration failure message, and an SL DRX configuration rejection message.

[0336] Optionally, the processor 1210 further used to perform a second operation, wherein the second operation is to transmit second information to the second terminal by the radio frequency unit 1201, and the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed, set the direct link to the DRX inactive state, and includes any one of triggering a renegotiation of the SL DRX configuration between the first terminal and the second terminal.

[0337] Optionally, the second information is carried by a direct link release request message.

[0338] Optionally, the processor 1210 is further used to determine the N sets of SL DRX configurations based on third information, and the third information is used to indicate at least one of an upper threshold value of the activation time length of the SL DRX and a lower threshold value of the activation time length of the SL DRX.

[0339] Optionally, when the feedback information meets a first condition, the processor 1210 is further used to determine whether to accept the feedback information based on third information, and the third information is used to indicate at least one of an upper threshold value of the activation time length of the SL DRX and a lower threshold value of the activation time length of the SL DRX, wherein the first condition is that the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, and the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal. Either one of the following is included: the K sets of SL DRX configurations included in the feedback information are SL DRX configurations other than the N sets of SL DRX configurations.

[0340] In Case 2, the terminal 1200 is the second terminal.

[0341] In this case, the radio frequency unit 1201 is to receive the first information transmitted by the first terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer, and is used to transmit feedback information on the first information to the first terminal.

[0342] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations.

[0343] Optionally, the first information further includes N groups of feature information that correspond one-to-one with the N sets of SL DRX configurations.

[0344] Optionally, the group of feature information includes at least one of SL DRX configuration priority, quality of service (QoS), logical channel identifier, logical channel priority, bearer identifier, bearer priority, QoS flow identifier, application identifier, service identifier, source address layer 2 identifier, and destination address layer 2 identifier.

[0345] Optionally, the SL DRX configuration includes at least one of a period of the SL DRX, an offset amount with respect to a target reference time point, a duration length, an operation time length of an inactivation timer, an operation time length of a round-trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and an operation time length of a retransmission timer, where the target reference time point is a reference time point at which the SL DRX configuration becomes effective.

[0346] Optionally, the first information is carried by any one of a direct link establishment request message, a direct link modification request message, a direct link radio resource control (RRC) reconfiguration message, and an SL DRX configuration request message.

[0347] Optionally, the feedback information includes M index values, M index values, and a first parameter in a first SL DRX configuration, any one of a set of K SL DRX configurations, where the M index values correspond one-to-one to M sets of the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer.

[0348] Optionally, the set of K SL DRX configurations satisfies any one of the following: being one of the SL DRX configurations of the N sets of SL DRX configurations, being obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal, being an SL DRX configuration other than the N sets of SL DRX configurations.

[0349] Optionally, the first parameter is either a parameter accepted by the second terminal in the first SL DRX configuration or a parameter modified by the second terminal in the first SL DRX configuration.

[0350] Optionally, the feedback information is carried by any one of a direct link establishment acceptance message, a direct link modification acceptance message, a direct link RRC reconfiguration completion message, and an SL DRX configuration response message.

[0351] Optionally, when the feedback information satisfies a first condition, the radio frequency unit 1201 is further used to receive second information transmitted by the first terminal, and the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. Here, the first condition is the feedback information includes M index values and a first parameter in the first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration, the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal, and any one of the K sets of SL DRX configurations included in the feedback information is an SL DRX configuration other than the N sets of SL DRX configurations.

[0352] Optionally, the feedback information indicates a rejection of the acceptance of the N sets of SL DRX configurations.

[0353] Optionally, the feedback information is carried by any one of a directory link establishment rejection message, a directory link modification rejection message, a directory link RRC relocation failure message, and an SL DRX configuration rejection message.

[0354] Optionally, the radio frequency unit 1201 is further used to receive second information transmitted by the first terminal, and the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed.

[0355] Optionally, the second information is carried by a directory link release request message.

[0356] Optionally, the processor 1210 is further used to generate the feedback information based on third information, and the third information is used to indicate at least one of an upper limit threshold value of the activation time duration of the SL DRX and a lower limit threshold value of the activation time duration of the SL DRX.

[0357] It should be noted that the terminal 1200 in this embodiment can implement each process in the embodiment of the method in FIG. 3 in the embodiment of the present application, and can achieve the same beneficial effects. To avoid repetition of description, it will not be described further here.

[0358] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When this program or instruction is executed by a processor, each process of the embodiment of the method in FIG. 3 or FIG. 4 is realized, and the same technical effects can be achieved. To avoid repetition of description, it will not be described further here.

[0359] Here, the processor is the processor in the terminal described in the above embodiments. 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, etc. The readable storage medium may be volatile or non-volatile. It should be noted that the readable storage medium may be non-transitory.

[0360] Embodiments of the present application further provide a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor runs a program or instruction of a network-side device, and is used to implement each process of the method embodiments in FIG. 3 or FIG. 4 above, and the same technical effect can be achieved. To avoid repetition of the description, it will not be described further here.

[0361] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system-on-chip, a chip system, or a system-on-a-chip, etc.

[0362] It should be noted that in this specification, the terms "comprising", "including" or any other variation thereof are intended to cover non-exclusive "including", whereby a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed or elements specific to such a process, method, article or apparatus. In the case of an element limited by the phrase "comprising one...", in the absence of further limitations, it is not excluded that there are other same elements in the process, method, article or apparatus comprising this element. It should be pointed out that the scope of the method and apparatus in the embodiments of the present application is not limited to executing functions in the order illustrated or discussed, but may include executing functions in a basically simultaneous manner or in the reverse order based on the functions involved. For example, a method described in a different procedure from the described one can be executed, and various steps can be added, omitted or combined. Also, features described with reference to some examples can be combined in other examples.

[0363] As can be clearly understood by those skilled in the art from the description of the above embodiments, the method of the above examples can be realized in the form of software and the necessary general-purpose hardware platform. Of course, it may also be realized by hardware, but in many cases, the former is a more preferred embodiment. Based on such an understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the part that contributes to the prior art. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the embodiments of the present application.

[0364] In the above, the embodiments of the present application have been described while associating with the drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely exemplary and not restrictive. Those skilled in the art can perform many forms based on the suggestion of the present application without departing from the spirit of the present application and the scope of the claims, and all of them belong to the protection scope of the present application.

Claims

1. A discontinuous reception DRX determination method executed by a first terminal, comprising: transmitting first information to a second terminal, where the first information is used to indicate N sets of sublink SL DRX configurations, and N is a positive integer; receiving feedback information for the first information transmitted by the second terminal, where the feedback information indicates rejecting acceptance of the N sets of SL DRX configurations; after receiving the feedback information for the first information transmitted by the second terminal, the method further comprises: performing a second operation, where the second operation further comprises stopping data transmission and reception between the first terminal and the second terminal by adopting a DRX mode; The SL DRX configuration includes at least one of a period of SL DRX, an offset amount with respect to a target reference time point, a duration, an operation time length of an inactivation timer, an operation time length of a round-trip time RTT timer related to a hybrid automatic repeat request HARQ process, and an operation time length of a retransmission timer. Here, the target reference time point is the reference time point when the SL DRX configuration becomes effective. A discontinuous reception DRX determination method.

2. The first information further includes N groups of characteristic information corresponding one-to-one to the N sets of SL DRX configurations, or the first information includes at least one of the N sets of SL DRX configurations and N index values corresponding one-to-one to the N sets of SL DRX configurations; The method according to claim 1, wherein the group of characteristic information includes at least one of an SL DRX configuration priority, a quality of service QoS, a logical channel identifier, a logical channel priority, a bearer identifier, a bearer priority, a QoS flow identifier, an application identifier, a service identifier, a source address layer 2 identifier, and a destination address layer 2 identifier.

3. The method according to claim 1, wherein the first information is carried by any one of a sublink establishment request message, a sublink modification request message, a sublink radio resource control RRC reconfiguration message, and an SL DRX configuration request message.

4. The feedback information includes any one of M index values, the M index values, and a first parameter in a first SL DRX configuration, and a K set of SL DRX configurations, where the M index values correspond one-to-one to M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer. The method according to claim 1.

5. When the feedback information satisfies a first condition, after receiving the feedback information for the first information transmitted by the second terminal, the method includes: When the first terminal rejects the feedback information, further including performing a first operation. Here, the first condition is: The feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration; The K set of SL DRX configurations included in the feedback information is obtained by modifying the SL DRX configuration in the N set of SL DRX configurations by the second terminal; The K set of SL DRX configurations included in the feedback information is any one of SL DRX configurations other than the N set of SL DRX configurations. The first operation is: Transmitting second information to the second terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed; Stopping data transmission and reception between the first terminal and the second terminal by adopting the DRX method; Triggering renegotiation of the SL DRX configuration between the first terminal and the second terminal. The method according to claim 4 includes any one of the above.

6. The second operation is: Transmitting second information to the second terminal, where the second information is used to indicate that the negotiation of the SL DRX configuration between the first terminal and the second terminal has failed. The method according to claim 1, further comprising any one of triggering renegotiation of the SL DRX configuration between the first terminal and the second terminal.

7. Before transmitting the first information to the second terminal, the method further comprises: determining the N sets of SL DRX configurations based on third information, the third information being used to indicate at least one of an upper threshold value of the activation time length of the SL DRX and a lower threshold value of the activation time length of the SL DRX, the method according to claim 1.

8. When the feedback information satisfies a first condition, after receiving the feedback information on the first information transmitted by the second terminal, the method further comprises: determining whether to accept the feedback information based on third information, the third information being used to indicate at least one of an upper threshold value of the activation time length of the SL DRX and a lower threshold value of the activation time length of the SL DRX, wherein the first condition is: the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration; the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configuration in the N sets of SL DRX configurations by the second terminal; the method according to claim 1, comprising any one of the K sets of SL DRX configurations included in the feedback information being an SL DRX configuration other than the N sets of SL DRX configurations.

9. A DRX determination method executed by a second terminal, comprising: receiving first information transmitted by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, N being a positive integer; transmitting feedback information on the first information to the first terminal, the feedback information including indicating rejection of acceptance of the N sets of SL DRX configurations; After transmitting the feedback information on the first information to the first terminal, the method further comprises: Further including stopping performing data transmission and reception between the first terminal and the second terminal by adopting a DRX mode, The SL DRX configuration includes at least one of a period of SL DRX, an offset amount with respect to a target reference time point, a duration length, an operation time length of an inactivation timer, an operation time length of a round-trip time (RTT) timer related to a hybrid automatic repeat request (HARQ) process, and an operation time length of a retransmission timer, where the target reference time point is a reference time point when the SL DRX configuration becomes effective, which is a DRX determination method. **Claim 10** The first information further includes N feature information groups that correspond one-to-one with the N sets of SL DRX configurations, or the first information includes at least one of the N sets of SL DRX configurations and N index values that correspond one-to-one with the N sets of SL DRX configurations, The feature information group includes at least one of an SL DRX configuration priority, a quality of service (QoS), a logical channel identifier, a logical channel priority, a bearer identifier, a bearer priority, a QoS flow identifier, an application identifier, a service identifier, a source address layer 2 identifier, and a destination address layer 2 identifier. The method according to claim 9. **Claim 11** The first information is carried by any one of a sublink establishment request message, a sublink modification request message, a sublink radio resource control (RRC) reconfiguration message, and an SL DRX configuration request message. The method according to claim 9. **Claim 12** The feedback information includes any one of M index values, the M index values, and a first parameter in a first SL DRX configuration, and K sets of SL DRX configurations, where the M index values correspond one-to-one with M sets of SL DRX configurations among the N sets of SL DRX configurations, the first SL DRX configuration includes at least one set of SL DRX configurations among the M sets of SL DRX configurations, M is a positive integer less than or equal to N, and K is a positive integer. The method according to claim 9. **Claim 13** When the feedback information satisfies a first condition, after transmitting the feedback information for the first information to the first terminal, the method further includes receiving second information transmitted by the first terminal, where the second information is used to indicate that negotiation of an SL DRX configuration between the first terminal and the second terminal has failed where the first condition is the feedback information includes M index values and a first parameter in a first SL DRX configuration, and the first parameter is a parameter modified by the second terminal in the first SL DRX configuration the K sets of SL DRX configurations included in the feedback information are obtained by modifying the SL DRX configurations in the N sets by the second terminal The method according to claim 12, including any one of the K sets of SL DRX configurations included in the feedback information being an SL DRX configuration other than the N sets of SL DRX configurations

14. Before transmitting the feedback information for the first information to the first terminal, the method further includes generating the feedback information based on third information, where the third information is used to indicate at least one of an upper threshold value of the activation time length of SL DRX and a lower threshold value of the activation time length of SL DRX. The method according to claim 9

15. A terminal including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, where when the program or instruction is executed by the processor, the steps of the DRX determination method according to any one of claims 1 to 8 are realized, or the steps of the DRX determination method according to any one of claims 9 to 14 are realized

Images