DRX determination method, device, terminal, and readable storage media

By allowing terminals to negotiate SL DRX configurations, the method addresses the reliability issues in SL DRX placement, ensuring compatibility and reducing power consumption through tailored DRX arrangements.

JP2024167435AActive Publication Date: 2024-12-03VIVO MOBILE COMM CO LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2024158270
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-10-22
Filing Date
2024-09-12
Publication Date
2024-12-03
Estimated Expiration
2041-10-20

AI Technical Summary

Technical Problem

The reliability of Discontinuous Reception (DRX) placement in sidelink (SL) communication is low due to network-side equipment not fully understanding the business characteristics of SL communication, leading to potential operation outside network coverage and inefficiencies.

Method used

A method and device for SL DRX placement negotiation between terminals, where terminals exchange and negotiate N sets of SL DRX configurations, allowing them to determine appropriate SL DRX arrangements compatible with the characteristics of SL communication.

Benefits of technology

Improves the reliability of SL DRX arrangements by enabling terminals to negotiate and determine DRX configurations that better suit the requirements of SL communication, enhancing compatibility and reducing power consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024167435000001_ABST
    Figure 2024167435000001_ABST
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is a divisional application of Japanese Patent Application No. 2023-522461, filed in Japan on April 12, 2023, entitled "DRX determination method, device, terminal, and readable storage medium."

[0002] The present application relates to the field of communications technology, and in particular to a DRX determination method, an apparatus, a terminal, and a readable storage medium. [Background technology]

[0003] Long Term Evolution (LTE) systems can support Sidelink (SL) for terminals to communicate directly with each other without going through network side equipment. To reduce terminal power consumption, a SL Discontinuous Reception (DRX) mechanism can be introduced.

[0004] The SL DRX mechanism is similar to the conventional Uu DRX mechanism, and the main difference between them is the different application of DRX configuration, 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 a network side device. In the prior art, the Uu DRX configuration is determined by the network side device. When the SL DRX mechanism reuses the Uu DRX mechanism, there are problems such as the terminal may operate outside the coverage area of ​​the network side device, and the network side device does not fully understand the business characteristics of SL communication, so the reliability of the SL DRX configuration determined by the network side device is relatively low. Summary of the Invention

[0005] The embodiments of the present application provide a DRX determination method, an apparatus, a terminal and a readable storage medium that can realize the negotiation of SL DRX configuration. According to a first aspect, there is provided a DRX decision method performed by a first terminal, the method comprising: Sending first information to a second terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and receiving feedback information for the first information transmitted by the second terminal.

[0006] According to a second aspect, there is provided a DRX decision method performed by a second terminal, the method comprising: Receiving first information sent by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and transmitting feedback information for the first information to the first terminal.

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

[0008] According to a fourth aspect, there is provided a DRX decision device, the DRX decision device comprising: A second receiving module for receiving first information sent by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and a second sending module for sending feedback information for the first information to the first terminal.

[0009] According to a fifth aspect, there is provided a terminal comprising a processor, a memory and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, performing steps of the method of the first aspect or performing steps of the method of the second aspect.

[0010] According to a sixth aspect, there is provided a readable storage medium having a program or instructions stored thereon, the program or instructions, when executed by a processor, performing steps of the method according to the first aspect or performing steps of the method according to the second aspect.

[0011] According to a seventh aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor running a program or instruction of a network side device to implement the method according to the first aspect, or used to implement the method according to the second aspect.

[0012] According to an eighth aspect, there is provided a program product, the program product being stored in a non-volatile storage medium, the program product being executed by at least one processor to implement the method according to the first aspect or to implement the method according to the second aspect. Effect of the Invention

[0013] In an embodiment of the present application, the first terminal instructs the second terminal of N sets of SL DRX configurations proposed by the first terminal, so that the second terminal can decide whether to accept the SL DRX configurations proposed by the first terminal and provide corresponding feedback. As can be seen, in an embodiment of the present application, the first terminal and the second terminal of the SL communication can negotiate and determine an appropriate SL DRX configuration by themselves, and in this way, the determined SL DRX configuration is more suited to the business characteristics of the SL communication, thereby improving the reliability of the determined SL DRX configuration. [Brief description of the drawings]

[0014] [Figure 1] 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied. [Diagram 2] FIG. 2 is a schematic diagram of a DRX cycle according to an embodiment of the present application; [Diagram 3] 1 is a flowchart of a DRX determination method according to an embodiment of the present application; [Figure 4] 2 is a second flowchart of a DRX determination method according to an embodiment of the present application. [Figure 5a] FIG. 1 is a schematic diagram of a PC5 unicast link establishment process according to an embodiment of the present application; [Figure 5b] FIG. 2 is a second schematic diagram of a PC5 unicast link establishment process according to an embodiment of the present application. [Figure 5c] FIG. 3 is a third schematic diagram of a PC5 unicast link establishment process according to an embodiment of the present application. [Figure 6a] FIG. 1 is a schematic diagram of a PC5 unicast link modification process according to an embodiment of the present application; [Figure 6b] FIG. 2 is a second schematic diagram of a PC5 unicast link modification process according to an embodiment of the present application; [Figure 6c] FIG. 3 is a third schematic diagram of a PC5 unicast link modification process according to an embodiment of the present application. [Figure 7a] FIG. 1 is a schematic diagram of a PC5 RRC relocation process according to an embodiment of the present application; [Figure 7b] FIG. 2 is a second schematic diagram of a PC5 RRC relocation process according to an embodiment of the present application. [Figure 7c] FIG. 3 is a schematic diagram of a PC5 RRC relocation process according to an embodiment of the present application; [Figure 8a] 1 is a schematic diagram of a PC5-S or PC5 RRC process according to an embodiment of the present application; [Figure 8b] FIG. 2 is a second schematic diagram of a PC5-S or PC5 RRC process according to an embodiment of the present application. [Figure 8c] FIG. 3 is a third schematic diagram of a PC5-S or PC5 RRC process according to an embodiment of the present application. [Figure 9] 1 is a structural diagram of a DRX determination device according to an embodiment of the present application; [Figure 10] 2 is a second structural diagram of a DRX determination device according to an embodiment of the present application; [Figure 11] 1 is a structural diagram of a terminal according to an embodiment of the present application; [Figure 12] 2 is a second structural diagram of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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, and obviously, the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art on the basis of the embodiments of the present application without any creative efforts are within the scope of protection of the present application. The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that data so used are interchangeable where appropriate, such that the embodiments of the present application may be performed in an order other than that shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. Note that "and / or" in the specification and claims represents at least one of the objects connected, and the character " / " generally represents an "or" relationship between the related objects.

[0016] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, 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 techniques described may be used in the above-mentioned systems and radio technologies, or in other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the description below, and these techniques may be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0017] 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied. 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 practical application, as shown in Fig. 1, a terminal may transmit information to a network side device via an uplink (UpLink, UL), and the network side device may transmit information to the terminal via a downlink (DownLink, DL). A first terminal 11 and a second terminal 13 may communicate directly via a sidelink (Sidelink, SL), that is, the first terminal 11 and the second terminal 13 may communicate without going through a network side device 12. The sidelink may be called a side link, an edge link, a sublink, etc.

[0019] In the embodiments of the present application, in one implementation manner, the first terminal may be a transmitting terminal of SL communication, and the second terminal may be a receiving terminal of SL communication; in another implementation manner, the first terminal may be a receiving terminal of SL communication, and the second terminal may be a transmitting terminal of SL communication; specifically, this may be determined according to actual circumstances, and the embodiments of the present application are not limited thereto.

[0020] The terminal may be called a terminal device or a user terminal (UE). In practical applications, the terminal may be a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device or a vehicle-mounted equipment (VUE), a pedestrian terminal (PUE), etc., and the wearable device includes a bracelet, an earphone, a pair of glasses, etc. The network side equipment may be a base station or a core network, where the base station may be referred to as a Node B, an evolved Node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other suitable term in the art, and the base station is not limited to a specific technical term as long as the same technical effect is achieved.

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

[0022] One, Sidelink.

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

[0024] The design of LTE Sidelink is applied to certain public safety services (e.g., emergency communication at disaster sites such as fires or earthquakes) or Vehicle to Everything (V2X) communication. Vehicle to Everything communication includes various services such as basic safety-type communication, advanced (autonomous) driving, formation, sensor expansion, etc. Since LTE Sidelink only supports broadcast communication, LTE Sidelink is mainly used for basic safety-type communication, and other advanced V2X services with strict Quality of Service (QoS) requirements in terms of latency, reliability, etc. are supported by 5th-Generation (5G) New Radio (NR) sidelink.

[0025] Second, Sidelink transmission format.

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

[0027] 3. Resource allocation mode.

[0028] The resource allocation mode for Sidelink may include the following two types:

[0029] 1) Mode 1: A base station (BS) schedules SL resource(s) to be used by UE for SL transmission(s). In this mode, a network side device (e.g., a base station) controls and assigns resources to each UE, so this mode may be called a base station scheduling mode.

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

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

[0032] Both LTE and NR have introduced a DRX mechanism, which achieves UE power saving by arranging DRX activation time (DRX on) and DRX deactivation time (DRX off).

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

[0034] If the UE does not monitor the PDCCH during the On Duration period of a certain DRX cycle, i.e., is not scheduled, after the On Duration period, the UE enters the off period of this DRX cycle, also called the DRX opportunity. In this case, the DRX on length of this DRX is the length of the On Duration of this DRX, and this DRX may be called the enabled 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 FIG. 2. In FIG. 2, the duration (On Duration) of the DRX cycle is DRX on.

[0035] During the On Duration period of a certain DRX cycle, the UE monitors the PDCCH in a certain slot, i.e., after receiving data scheduled in a certain slot, it is highly likely that the UE will continue to be scheduled in the next few slots. Therefore, every time the UE is scheduled for initial transmission data, the timer drx-InactivityTimer is started or restarted, and the UE is in an activated state until the timer times out. In this case, the DRX on length of this DRX is determined in conjunction with 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 an activated DRX. For example, if the On Duration of this DRX includes 10 slots, the scheduling time point is the sixth slot of the 10 slots, and the running time length of the drx-InactivityTimer is 10 slots, the DRX on length of this DRX includes 15 slots.

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

[0037] If the UE fails to decode transmitted or received data after configuring DRX, the UE needs to enter an activation time, monitor the control channel, and wait for retransmission scheduled by the network.

[0038] For downlink data reception, after the UE receives 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 data of this HARQ process is not successfully decoded, the UE starts a retransmission timer (drx-RetransmissionTimer) and monitors the PDCCH to wait for transmission.

[0039] For uplink data transmission, after the UE receives an 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) and enters an active state, monitoring the PDCCH and waiting for a transmission scheduled by the network.

[0040] Please refer to Fig. 3, which is a flowchart of a DRX determination method according to an embodiment of the present application. The DRX determination method shown in Fig. 3 may be performed by a first terminal.

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

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

[0043] When specifically implemented, in a first implementation manner, the N sets of SL DRX configurations may be SL DRX configurations generated by the first terminal. In a second implementation manner, the N sets of SL DRX configurations may be SL DRX configurations selected by the first terminal from SL DRX configurations previously acquired, where the 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, and may be specifically determined according to actual conditions, and the embodiments of the present application are not limited thereto.

[0044] Optionally, the SL DRX configuration includes at least one of the following: a periodicity, an offset to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer of the SL DRX.

[0045] Wherein, the target reference time is a reference time when the SL DRX configuration is 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, and may be specifically determined according to actual circumstances, 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, and may be specifically determined according to actual circumstances, and the embodiments of the present disclosure are not limited thereto.

[0046] Step 302, receiving feedback information for the first information sent 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, it can decide whether to accept the N sets of SL DRX configurations and provide corresponding feedback.

[0048] When specifically implemented, the second terminal's deciding whether to accept the N sets of SL DRX configurations may include any one of: 1) accepting at least one SL DRX configuration of the N sets of SL DRX configurations; 2) accepting only some parameters in at least one set of SL DRX configurations of the N sets of SL DRX configurations; and 3) rejecting the N sets of SL DRX configurations.

[0049] With respect to 1), the second terminal may indicate the SL DRX configuration accepted by the second terminal by the feedback information. After receiving the feedback information, the first terminal may determine a target SL DRX configuration from the SL DRX configurations accepted by the second terminal, and perform SL DRX communication with the second terminal using the target SL DRX configuration.

[0050] For 2), the second terminal may indicate a first parameter of the SL DRX configuration accepted by the second terminal by 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] If the first parameters are parameters accepted by the second terminal, the first terminal may re-propose the first parameters to the second terminal after receiving the feedback information, and the specific processing flow is the same as proposing an SL DRX configuration to the second terminal, and the main difference between the two is that the proposal targets of the two are different, so the specific processing flow of re-proposing the first parameters to the second terminal may refer to the processing flow of proposing an SL DRX configuration to the second terminal, and will not be further described here.

[0052] If the first parameter is a parameter rejected and modified by the second terminal, the first terminal may decide whether to accept the first parameter after receiving the feedback information. If accepted, the first terminal may determine a target SL DRX configuration among the SL DRX configurations accepted by both the first terminal and the second terminal, and use the target SL DRX configuration to perform SL DRX communication with the second terminal. 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 a DRX deactivation state (i.e., when there is data to be transmitted or received, it is in a continuous transmission / reception state instead of a DRX state), or release the direct link between the first terminal and the second terminal.

[0053] For 3), the second terminal may instruct the second terminal to reject the N sets of SL DRX configurations by the feedback information. Furthermore, the second terminal may further instruct the SL DRX configurations proposed by the second terminal by 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 a DRX deactivation state (i.e., when there is data to be transmitted or received, to be in a continuous transmission / reception state rather than a DRX state), or release the direct link between the first terminal and the second terminal.

[0055] If the feedback information indicates a SL DRX configuration proposed by the second terminal, the first terminal may decide whether to accept the SL DRX configuration proposed by the second terminal after receiving the feedback information. If accepted, the first terminal may determine a target SL DRX configuration among the SL DRX configurations accepted by both the first terminal and the second terminal, and use the target SL DRX configuration to perform SL DRX communication with the second terminal. 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 a DRX deactivation state (i.e., when there is data to be transmitted or received, it is in a continuous transmission / reception state rather than a DRX state), or release the direct link between the first terminal and the second terminal.

[0056] In the DRX determination method of the embodiment of the present application, the first terminal can instruct the second terminal of N sets of SL DRX configurations proposed by itself, and the second terminal can decide whether to accept the SL DRX configurations proposed thereby, and provide corresponding feedback. As can be seen, in the embodiment of the present application, the first terminal and the second terminal of the SL communication can negotiate and determine an appropriate SL DRX configuration by themselves, and in this way, the determined SL DRX configuration can be more suitable for the business characteristics of the SL communication, thereby improving the reliability of the determined SL DRX configuration.

[0057] First, the first information in the embodiments of the present application is described below.

[0058] Optionally, the first information includes at least one of the N sets of SL DRX configurations and N index values ​​having one-to-one correspondence 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 a first implementation manner, the N sets of SL DRX configurations may be generated by the first terminal, and in a second implementation manner, the N sets of SL DRX configurations may be selected by the first terminal. For the N sets of SL DRX configurations determined in different implementation manners, the manner in which the first information indicates the N sets of SL DRX configurations may be different, which is specifically described as follows:

[0060] For the N sets of SL DRX configurations determined by the above first implementation manner, the first information includes at least the N sets of SL DRX configurations, thus the second terminal can obtain the N sets of SL DRX configurations only after receiving the first information. Furthermore, the first information may further include the N index values, thus, when the second terminal accepts some or all 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 returning an index value, thereby saving signaling overhead.

[0061] For the N sets of SL DRX configurations determined by the above-mentioned second implementation manner, the second terminal can obtain the SL DRX configuration in a similar manner, so that 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 having one-to-one correspondence 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 by the second terminal to determine whether to accept 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 a SL DRX placement priority, a Quality of Service (QoS), a Logical Channel (LC) identifier (ID), a logical channel priority, a bearer identifier, a bearer priority, a QoS flow identifier, an application identifier (application ID), a service identifier, a source address Layer 2 identifier (source L2 ID), and a destination address Layer 2 identifier (destination L2 ID).

[0065] When specifically realized, the QoS may include parameters such as priority, delay, reliability, etc. of data packets or data streams. The SL DRX arrangement priority of an SL DRX arrangement may be used for one of the following: determining whether to allow modification of parameters in the SL DRX arrangement, for example, allowing modification of the SL DRX arrangement only when the SL DRX arrangement priority of a certain SL DRX arrangement is lower than a preset SL DRX arrangement priority, and not allowing modification of the SL DRX arrangement otherwise; and determining the target SL DRX arrangement, for example, when there are a plurality of SL DRX arrangements determined by negotiation between the first terminal and the second terminal, selecting the SL DRX arrangement with the highest SL DRX arrangement priority among the plurality of SL DRX arrangements as the target SL DRX arrangement, and adopting the SL DRX arrangement to perform SL DRX communication.

[0066] The feature information group may be configured by a network side device, pre-configured, configured by a V2X layer, or agreed upon by a protocol, and may be specifically determined according to actual circumstances, and the embodiments of the present application are not limited thereto. It should be noted that the specific parameters included in the feature information groups of corresponding different SL DRX configurations may be the same or different, and the number of parameters included in the feature information groups of corresponding different SL DRX configurations may be equal or unequal, and may be specifically determined according to actual circumstances, and the embodiments of the present disclosure are not limited thereto.

[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 a 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, and when negotiating the SL DRX configuration through different processes, the first information may be carried by different messages, which is specifically described as follows:

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

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

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

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

[0073] Second, the feedback information in the embodiment of the present application will be described below.

[0074] 1) Optionally, the feedback information is: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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.

[0075] Specifically, it is explained as follows:

[0076] If the feedback information includes M index values, it indicates that the second terminal accepts M sets of SL DRX configurations associated with the M index values ​​proposed by the first terminal.

[0077] If the feedback information includes M index values ​​and a first parameter in a first SL DRX configuration, it indicates that the second terminal accepts at least some 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 M sets of SL DRX configurations associated with the M index values.

[0078] In this case, optionally, the first parameter may be any one of a parameter accepted by the second terminal in the first SL DRX arrangement and a parameter modified by the second terminal in the first SL DRX arrangement.

[0079] When the feedback information includes K sets of SL DRX configurations, optionally, the K sets of SL DRX configurations include: a) the K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; b) the K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; c) the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

[0080] It indicates that, if the K sets of SL DRX configurations satisfy a), the second terminal accepts the K sets of SL DRX configurations proposed by the first terminal.

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

[0082] If the K sets of SL DRX configurations satisfy c), it indicates that the second terminal has rejected the proposal of the first terminal and has given its own proposal.

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

[0084] As can be understood, the manner in which the feedback information is carried is related to the manner in which the first information is carried. If the first information is carried by a direct link establishment request message, the feedback information may be carried by a direct link establishment accept message, if the first information is carried by a direct link modification request message, the feedback information may be carried by a direct link modification accept message, if the first information is carried by a direct link RRC relocation message, the feedback information may be carried by a direct link RRC relocation complete message, if the first information is carried by a SL DRX configuration request message, the feedback information may be carried by a SL DRX configuration response message.

[0085] Optionally, for the feedback information in 1), if the feedback information satisfies a first condition, after receiving feedback information for the first information sent by the second terminal, the method includes: If the first terminal rejects the feedback information, 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 sets of SL DRX configurations included in the feedback information are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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 includes: Sending second information to the second terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an SL DRX configuration between the first terminal and the second terminal.

[0086] In this optional embodiment, the feedback information satisfies a first condition, which indicates that the feedback information has provided a proposal from the second terminal. In this case, as can be seen from the above, the first terminal may decide whether to accept the proposal from the second terminal after receiving the feedback information. If the first terminal rejects the proposal from the second terminal, i.e., rejects the feedback information, it may perform a first operation.

[0087] Optionally, the second information is carried by a direct link release request message, in which case the cause of triggering the transmission of the direct link release request message is a failure in the negotiation of SL DRX configuration between the first terminal and the second terminal.

[0088] The above-mentioned setting of the direct link to a DRX deactivated state may be understood as setting the direct link between the first terminal and the second terminal to a DRX deactivated state, i.e., stopping data transmission and reception between the first terminal and the second terminal by adopting a DRX method, and when data transmission and reception exists between the first terminal and the second terminal, data is in a continuous transmission and reception state.

[0089] It should be noted that when steps 301 and 302 occur in a PC5 unicast link establishment process, the feedback information is carried by a direct link establishment accept message, indicating that a direct link connection has been established between the first terminal and the second terminal, so if the first operation includes triggering a renegotiation of SL DRX configuration between the first terminal and the second terminal, the first terminal may renegotiate the SL DRX configuration through other flows, such as a PC5 unicast link modification process, a PC5 RRC relocation process, a PC5-S or PC5 RRC process, etc.

[0090] If steps 301 and 302 occur in a process other than a PC5 unicast link establishment process, it indicates that a direct link connection has been established between the first terminal and the second terminal, so if the first operation includes triggering a renegotiation of SL DRX configuration between the first terminal and the second terminal, the first terminal may perform the renegotiation of SL DRX configuration through the same flow or a different flow, and specifically, may be determined according to actual circumstances, and the embodiments of the present application are not limited thereto.

[0091] 2) Optionally, the feedback information indicates rejection of the N sets of SL DRX configurations.

[0092] In response to the feedback information in 1), the second terminal indicates that it refuses to accept the proposal of the first terminal and does not provide its own proposal.

[0093] Alternatively, the feedback information may be carried by any one of a direct link establishment reject message, a direct link modification reject message, a direct link RRC relocation failure message, and a SL DRX configuration reject message.

[0094] As can be understood, the manner in which the feedback information is carried is related to the manner in which the first information is carried. If the first information is carried by a direct link establishment request message, the feedback information may be carried by a direct link establishment rejection message, if the first information is carried by a direct link modification request message, the feedback information may be carried by a direct link modification rejection message, if the first information is carried by a direct link RRC relocation message, the feedback information may be carried by a direct link RRC relocation failure message, if the first information is carried by a SL DRX configuration request message, the feedback information may be carried by a SL DRX configuration rejection message.

[0095] Optionally, after receiving feedback information for the first information transmitted by the second terminal, the method further comprises: performing a second operation; Here, the second operation is Sending second information to the second terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an SL DRX configuration between the first terminal and the second terminal.

[0096] Optionally, the second information is carried by a direct link release request message. In this case, the cause of triggering the transmission of the direct link release request message is the failure of the negotiation of the SL DRX configuration between the first terminal and the second terminal. The setting of the direct link to the DRX deactivation state can be referred to the description above, and will not be further described here.

[0097] It should be noted that when steps 301 and 302 occur in a 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 yet been established between the first terminal and the second terminal, so in this case, the second operation may not include sending second information to the second terminal.

[0098] In this optional embodiment, the renegotiation of SL DRX configuration may be the same as or different from the flow located in steps 301 and 302, and may be specifically determined according to actual circumstances, and the embodiments of the present application are not limited thereto.

[0099] In an embodiment of the present application, the terminal may acquire third information in advance, and the third information is used to indicate at least one of an upper threshold value of the SL DRX activation time length and a lower threshold value of the SL DRX activation time length.

[0100] When specifically implemented, the upper threshold and / or the lower threshold may be configured by a network side device, pre-configured, configured by a V2X layer, or agreed upon by a protocol, and may be specifically determined according to actual conditions, and the embodiments of the present application are not limited thereto.

[0101] When specifically implemented, the upper threshold and / or the lower threshold may be used by the terminal to at least one of determine an SL DRX activation time length proposed by the terminal itself and determine whether or not the terminal accepts an SL DRX activation time length proposed by another terminal, which is specifically described as follows:

[0102] Optionally, before transmitting the first information to the second terminal, the method further comprises: The method further includes determining the N sets of SL DRX configurations based on third information, wherein the third information is used to indicate at least one of an upper threshold for an SL DRX activation time length and a lower threshold for an SL DRX activation time length.

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

[0104] In this optional embodiment, the SL DRX activation time lengths included in the N sets of SL DRX configurations may satisfy at least one of being equal to or less than the upper threshold and being equal to or greater than the lower threshold. Of course, it can be understood that in other embodiments, the SL DRX activation time lengths included in the N sets of SL DRX configurations may be greater than the upper threshold or less than the lower threshold, and may be specifically determined according to actual circumstances, and the embodiments of the present application are not limited thereto.

[0105] Optionally, if the feedback information satisfies a first condition, after receiving feedback information for the first information sent by the second terminal, the method includes: 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 of an activation time length of a SL DRX and a lower threshold of an activation time length of a 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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 optional embodiment, the upper threshold and / or the lower threshold may be used to decide whether or not the first terminal accepts the SL DRX activation time length proposed by the second terminal.

[0107] When specifically implemented, with respect to the upper threshold, if the SL DRX activation time length indicated by the feedback information is greater than the upper threshold, the first terminal may reject the proposal, and if the SL DRX activation time length indicated by the feedback information is equal to or less than the upper threshold, the first terminal may accept the proposal. In this way, it is possible to avoid the successfully negotiated SL DRX activation time length being too long, and reduce the power consumption of the terminal.

[0108] For the lower threshold, if the SL DRX activation time length indicated by the feedback information is smaller than the lower threshold, the first terminal may accept this configuration, thus avoiding the first terminal from frequently triggering renegotiation.

[0109] Please refer to Fig. 4, which is a second flowchart of the DRX decision method according to an embodiment of the present application. The DRX decision method shown in Fig. 4 is executed by a network side device.

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

[0111] Step 401: receiving first information sent by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer.

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

[0113] In the DRX determination method of the embodiment of the present application, after the second terminal receives N sets of SL DRX configurations proposed by the first terminal, the second terminal can decide by itself whether to accept the SL DRX configurations proposed by the first terminal, and provide corresponding feedback. As can be seen, in the embodiment of the present application, the first terminal and the second terminal of the SL communication can negotiate and determine an appropriate SL DRX configuration by themselves, and in this way, the determined SL DRX configuration can be more suited to the business characteristics of the SL communication, thereby improving the reliability of the determined SL DRX configuration.

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

[0115] Optionally, the first information further includes N feature information groups having one-to-one correspondence with the N sets of SL DRX configurations.

[0116] Optionally, the feature information group includes at least one of: SL DRX allocation 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 periodicity, an offset to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer, where the target reference point is a reference 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 a SL DRX configuration request message.

[0119] Optionally, the feedback information comprises: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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.

[0120] Optionally, the K sets of SL DRX configurations are The K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; The K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

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

[0122] Optionally, the feedback information is carried by any one of a direct link establishment accept message, a direct link modification accept message, a direct link RRC relocation complete message, and a SL DRX configuration response message.

[0123] Optionally, if the feedback information satisfies a first condition, after transmitting feedback information for the first information to the first terminal, the method includes: receiving second information transmitted by the first terminal, the second information being used to indicate that negotiation of 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 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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.

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

[0125] Optionally, the feedback information is carried by any one of a direct link establishment reject message, a direct link modification reject message, a direct link RRC relocation failure message, and a SL DRX configuration reject message.

[0126] Optionally, after transmitting feedback information for the first information to the first terminal, the method further comprises: The method further includes receiving second information transmitted by the first terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed.

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

[0128] Optionally, before transmitting feedback information for the first information to the first terminal, the method further comprises: The method further includes generating the feedback information based on third information, the third information being used to indicate at least one of an upper threshold for an activation time length of a SL DRX and a lower threshold for an activation time length of a SL DRX.

[0129] In this optional embodiment, the upper threshold and / or the lower threshold may be used to decide whether or not the second terminal accepts the SL DRX activation time length proposed by the first terminal.

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

[0131] For the lower threshold, if the SL DRX activation time length indicated by the first information is smaller than the lower threshold, the second terminal may accept the configuration, not reject the configuration, and not start or activate a new SL DRX, or not negotiate a new SL DRX. In this way, it is possible to avoid the terminal from frequently triggering renegotiation.

[0132] It should be noted that this embodiment is an embodiment of a network side device corresponding to the embodiment of the method in Fig. 3, so reference can be made to the relevant description in the embodiment of the method in Fig. 3, and the same beneficial effects can be achieved. In order to avoid repetition of description, no further description will be given here.

[0133] It should be noted that the various optional embodiments introduced in the examples of the present application may be implemented in conjunction with each other or may be implemented alone, and the examples of the present application are not limited thereto.

[0134] For ease of understanding, the following is an example explanation. In the embodiment of the present application, 1) UE 1 (TX UE) sends a SL DRX pattern proposal, UE 2 (RX UE) decides whether to accept the SL DRX pattern proposal, and if not, may give further SL DRX pattern proposal. UE 1 finally decides whether to accept the proposal.

[0135] The information may be carried in an evolution of existing signaling flows or may introduce new signaling flows.

[0136] UE1 may propose one or more sets of SL DRX configurations, UE2 may decide on a set thereof, and UE2 may further modify some parameters.

[0137] Define the SL DRX placement priority. The SL DRX pattern with low priority may be modified.

[0138] 2) If the negotiation of the DRX configuration is not successful, a processing method is provided, such as a) rejection, b) link release, c) renegotiation, d) DRX off, etc. For details, please refer to the description below, and they will not be described here.

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

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

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

[0142] Step 1: UE 1 sends at least one set of SL DRX pattern information to UE 2, which is carried in a direct link establishment request message.

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

[0144] In addition, each set of SL DRX pattern information may be further associated with one index value and carried together in the direct link establishment request message.

[0145] In addition, each set of SL DRX pattern information may be further associated with a set of SL DRX pattern attributes, where the 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 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), and the SL DRX pattern attributes may be configured by the V2X layer, or configured by the base station, or pre-configured, or defined by a protocol.

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

[0147] The expression method of SL DRX pattern information that UE2 can accept is as follows: At least one index value in step 1; Some parameters of the SL DRX pattern information of the set related to at least one index value in step 1 and the corresponding index value, i.e., allowing the UE 2 to modify some parameters in the negotiation process; and at least one set of SL DRX pattern information. Here, there is no limitation as to whether the SL DRX pattern information is a copy of the at least one set of SL DRX pattern information in step 1, i.e., the UE 2 is allowed to modify some parameters in the negotiation process based on step 1. Furthermore, it may be further limited that only the SL DRX patterns whose priority in step 1 is lower than a certain threshold can be modified.

[0148] Step 3: According to step 2, if UE 2 allows some parameters to be modified in the negotiation process, after step 2, UE 1 further judges whether to accept the SL DRX pattern information fed back by UE 2; if not, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 performs one of the following: and UE1 sets the corresponding direct link to a DRX off state.

[0149] Step 4: The UE 2 determines that there is no acceptable SL DRX pattern information, and therefore feeds back a direct link establishment reject message.

[0150] The direct link establishment rejection message may further include a cause value being SL DRX negotiation failure.

[0151] next, UE1 triggers SL DRX renegotiation, i.e., goes to step 1 and re-initiates a direct link establishment request message; and UE1 sets the corresponding direct link to a DRX off state.

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

[0153] Figure 5a shows a case where the SL DRX configuration negotiation is successful. As shown in Figure 5a, the negotiation may include the following steps:

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

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

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

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

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

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

[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, where the direct link establishment rejection message may carry a rejection cause value that is a negotiation failure of SL DRX configuration.

[0163] Step 4: UE1 initiates renegotiation of SL DRX configuration, and sends a direct link establishment request message to UE2.

[0164] Figure 5c shows a case where the negotiation of 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 recommend at least one set of SL DRX configurations to UE2.

[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 to be modified, perform step 3.

[0168] Step 3: UE2 sends a direct link establishment accept message to UE1, where the direct link establishment accept 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 UE2 rejects the modified SL DRX configuration, it may perform step 5.

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

[0172] Example 2: 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 to UE 2, which is carried in a direct link modification request message.

[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 may be further associated with one index value and carried together in a direct link establishment request message, a direct link modification request message, and a PC5 RRC relocation message.

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

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

[0178] The expression method of SL DRX pattern information that UE2 can accept is as follows: At least one index value in step 1; Some parameters of the SL DRX pattern information of the set related to at least one index value in step 1 and the corresponding index value, i.e., allowing the UE 2 to modify some parameters in the negotiation process; and at least one set of SL DRX pattern information. Here, there is no limitation on whether it is at least one set of SL DRX pattern information in step 1, that is, it allows the UE 2 to modify some parameters in the negotiation process. Furthermore, it may be further limited that only the SL DRX patterns whose priority in step 1 is lower than a certain threshold can be modified.

[0179] According to step 2, if UE 2 allows some parameters to be modified in the negotiation process, after step 2, UE 1 further judges whether to accept the SL DRX pattern information fed back by UE 2. If it cannot be accepted, then: UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 does not release the direct link but triggers a renegotiation of SL DRX, i.e., goes to step 1 and re-initiates a direct link modification request message; and UE1 sets the corresponding direct link to a DRX off state.

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

[0181] The direct link modification reject message may further include a cause value of SL DRX negotiation failure.

[0182] next, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 triggers SL DRX renegotiation, i.e., goes to step 1 and re-initiates a direct link modification request message; and UE1 sets the corresponding direct link to a DRX off state.

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

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

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

[0186] Step 2: UE2 decides 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 accept message to UE1 to indicate the SL DRX configuration accepted by UE2.

[0189] Figure 6b shows a case where the negotiation of 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 recommend at least one set of SL DRX configurations to UE2.

[0191] Step 2: UE2 decides 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 reject message to UE1, where the direct link modification reject message may carry a reject cause value that is a negotiation failure of SL DRX configuration.

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

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

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

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

[0198] If the SL DRX configuration recommended by UE1 is to be modified, perform step 3.

[0199] Step 3: UE2 sends a direct link modification accept message, where the direct link modification accept 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 UE2 rejects the modified SL DRX configuration, it may perform step 5.

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

[0203] Example 3: SL DRX negotiation occurs in PC5 RRC relocation process.

[0204] Step 1: UE 1 sends at least one set of SL DRX pattern information to UE 2, which is carried in a PC5 RRC relocation message.

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

[0206] In addition, each set of SL DRX pattern information may be further associated with one index value and carried together in a direct link establishment request message, a direct link modification request message, and a PC5 RRC relocation message.

[0207] In addition, each set of SL DRX pattern information may be further associated with a set of SL DRX pattern attributes, where the 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 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), and the SL DRX pattern attributes may be configured by the V2X layer, or configured by the base station, or pre-configured, or defined by a protocol.

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

[0209] The expression method of SL DRX pattern information that UE2 can accept is as follows: At least one index value in step 1; Some parameters of the SL DRX pattern information of the set related to at least one index value in step 1 and the corresponding index value, i.e., allowing the UE 2 to modify some parameters in the negotiation process; and at least one set of SL DRX pattern information. Here, there is no limitation on whether it is at least one set of SL DRX pattern information in step 1, that is, it allows the UE 2 to modify some parameters in the negotiation process. Furthermore, it may be further limited that only the SL DRX patterns whose priority in step 1 is lower than a certain threshold can be modified.

[0210] According to step 2, if UE 2 allows some parameters to be modified in the negotiation process, after step 2, UE 1 further judges whether to accept the SL DRX pattern information fed back by UE 2. If it cannot be accepted, then: UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 does not release the direct link but triggers a renegotiation of SL DRX, i.e., goes to step 1 and re-initiates a PC5 RRC relocation message; and UE1 sets the corresponding direct link to a DRX off state.

[0211] Step 4: UE 2 determines that there is no acceptable SL DRX pattern information, so feeds back a PC5 RRC Relocation failure message.

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

[0213] next, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 triggers SL DRX renegotiation, i.e., goes to step 1 and re-initiates PC5 RRC relocation message; and UE1 sets the corresponding direct link to a DRX off state.

[0214] For ease of understanding, please refer to Figures 7a to 7c.

[0215] Figure 7a illustrates a successful SL DRX configuration negotiation. As shown in Figure 7a, the negotiation may include the following steps:

[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 the SL DRX configuration recommended by UE1 is accepted, execute step 3.

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

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

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

[0222] Step 2: UE2 decides 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 relocation failure message to UE1, where the direct link RRC relocation failure message may carry a rejection cause value that is a negotiation failure of SL DRX configuration.

[0225] Step 4: UE1 initiates SL DRX configuration renegotiation and sends a direct link RRC relocation message to UE2.

[0226] Figure 7c shows a case where the negotiation of 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 recommend at least one set of SL DRX configurations to UE2.

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

[0229] If the SL DRX configuration recommended by UE1 is to be modified, perform step 3.

[0230] Step 3: UE2 sends a direct link RRC relocation success message to UE1, where the direct link RRC relocation 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 UE2 rejects the modified SL DRX configuration, it may perform step 5.

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

[0234] Example 4: SL DRX negotiation occurs in the newly introduced PC5-S or PC5 RRC process.

[0235] The idea behind Examples 1, 2 and 3 is to modify the conventional signaling flow, while the idea behind Example 4 is to introduce a new signaling flow, the advantage of which is that it is decoupled from the conventional signaling flow and can occur independently.

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

[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 may be further associated with one index value and carried together in a direct link establishment request message, a direct link modification request message, and a PC5 RRC relocation message.

[0239] In addition, each set of SL DRX pattern information may be further associated with a set of SL DRX pattern attributes, where the 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 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), and the SL DRX pattern attributes may be configured by the V2X layer, or configured by the base station, or pre-configured, or defined by a protocol.

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

[0241] The expression method of SL DRX pattern information that UE2 can accept is as follows: At least one index value in step 1; Some parameters of the SL DRX pattern information of the set related to at least one index value in step 1 and the corresponding index value, i.e., allowing the UE 2 to modify some parameters in the negotiation process; and at least one set of SL DRX pattern information. Here, there is no limitation on whether it is at least one set of SL DRX pattern information in step 1, that is, it allows the UE 2 to modify some parameters in the negotiation process. Furthermore, it may be further limited that only the SL DRX patterns whose priority in step 1 is lower than a certain threshold can be modified.

[0242] If UE 2 allows some parameters to be modified in the negotiation process according to step 2, after step 2, UE 1 further judges whether to accept the SL DRX pattern information fed back by UE 2; if not, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 does not release the direct link but triggers a renegotiation of SL DRX, i.e., goes to step 1 and re-initiates a SL DRX configuration request message; UE1 performs one of the following: and UE1 sets the corresponding direct link to a DRX off state.

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

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

[0245] next, UE1 sends a direct link release request message to UE2 (the direct link release request message may further include that the cause value is SL DRX negotiation failure); UE1 triggers SL DRX renegotiation, i.e., goes to step 1 and re-initiates a SL DRX configuration request message; and UE1 sets the corresponding direct link to a DRX off state.

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

[0247] Figure 8a shows a case where the SL DRX configuration negotiation is successful. As shown in Figure 8a, the negotiation may include the following steps:

[0248] Step 1: UE1 sends a 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 the SL DRX configuration recommended by UE1 is accepted, execute step 3.

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

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

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

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

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

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

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

[0258] Figure 8c shows a case where the negotiation of 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 recommend at least one set of SL DRX configurations to UE2.

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

[0261] If the SL DRX configuration recommended by UE1 is to be modified, perform step 3.

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

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

[0264] If UE2 rejects the modified SL DRX configuration, it may perform step 5.

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

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

[0267] Prior to the first to fourth embodiments, the SL UE may further receive an upper limit value of one SL DRX on length configured by the V2X layer, configured by the base station, or configured in advance. If the enabled or activated SL DRX on length exceeds this upper limit value, the UE may reject link establishment, otherwise, may establish connection or recommend an available DRX configuration. The use of this value is embodied in that the UE can refer to it when determining whether to accept the SL DRX pattern in power saving and business QoS.

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

[0269] Prior to the first to fourth embodiments, the SL UE may further receive a lower limit value of one SL DRX on length configured by the V2X layer, configured by the base station, or pre-configured. If the enabled or activated SL DRX on length is less than the lower limit value, the UE rejects the configuration and cannot enable or activate a new SL DRX or negotiate a new SL DRX. The use of this value is realized to avoid the UE from triggering renegotiation frequently, which is beneficial to system performance.

[0270] The embodiment of the present invention designs the negotiation signaling details of SL DRX configuration and the negotiation unsuccessful processing, so as to ensure that sidelink DRX works normally and achieve the purpose of sidelink UE power saving.

[0271] It should be mentioned that for the DRX decision method according to the embodiment of the present application, the execution body may be a DRX decision device or a control module for executing the DRX decision method in the DRX decision device. In the embodiment of the present application, the execution of the DRX decision method by the DRX decision device is taken as an example to describe the DRX decision device according to the embodiment of the present application.

[0272] Please refer to FIG. 9, which is a structural diagram of a DRX determination device according to an embodiment of the present application.

[0273] As shown in FIG. 9, the DRX determination device 900 A first sending module 901 for sending first information to a second terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; a first receiving 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 ​​having one-to-one correspondence with the N sets of SL DRX configurations.

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

[0276] Optionally, the feature information group includes at least one of: SL DRX allocation 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 a period, an offset amount to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer; Here, the target reference point in time is a reference point in time at which the SL DRX configuration becomes valid.

[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 a SL DRX configuration request message.

[0279] Optionally, the feedback information comprises: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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 K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; The K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

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

[0282] Optionally, the feedback information is carried by any one of a direct link establishment accept message, a direct link modification accept message, a direct link RRC relocation complete message, and a SL DRX configuration response message.

[0283] Optionally, if the feedback information satisfies a first condition, the DRX determination device 900: A first execution module for executing a first operation if the first terminal rejects the feedback information; 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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 includes: Sending second information to the second terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an SL DRX configuration between the first terminal and the second terminal.

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

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

[0287] Optionally, the DRX determination device 900 is further comprising a second execution module for performing a second operation; Here, the second operation is Sending second information to the second terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an SL DRX configuration between the first terminal and the second terminal.

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

[0289] Optionally, the DRX decision device comprises: The present invention further includes a first determination module for determining the N sets of SL DRX configurations based on third information, wherein the third information is used to indicate at least one of an upper threshold value of an SL DRX activation time length and a lower threshold value of an SL DRX activation time length.

[0290] Optionally, if the feedback information satisfies a first condition, the DRX decision device: Further comprising a second determination module for 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 of an activation time length of a SL DRX and a lower threshold of an activation time length of a 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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 embodiment of the present application may be a device, a component in a terminal, an integrated circuit, or a chip. The 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 terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0292] The DRX determination device in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0293] The DRX determination device 900 according to the embodiment of the present application can implement each process implemented by the embodiment of the method of FIG. 3 and achieve the same technical effects, and will not be further described here to avoid repetition.

[0294] Please refer to FIG. 10, which is a second structural diagram of a DRX determination device according to an embodiment of the present application.

[0295] As shown in FIG. 10, the DRX determination device 1000 A second receiving module 1001 for receiving first information sent by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and a second sending module 1002 for sending feedback information for 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 ​​having one-to-one correspondence with the N sets of SL DRX configurations.

[0297] Optionally, the first information further includes N feature information groups having one-to-one correspondence with the N sets of SL DRX configurations.

[0298] Optionally, the feature information group includes at least one of: SL DRX allocation 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 a periodicity, an offset to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer, where the target reference point is a reference point at which 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 a SL DRX configuration request message.

[0301] Optionally, the feedback information comprises: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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 are The K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; The K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

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

[0304] Optionally, the feedback information is carried by any one of a direct link establishment accept message, a direct link modification accept message, a direct link RRC relocation complete message, and a SL DRX configuration response message.

[0305] Optionally, if the feedback information satisfies a first condition, after transmitting feedback information for the first information to the first terminal, the DRX determination device 1000: Further comprising a third receiving module for receiving second information transmitted by the first terminal, the second information being used to indicate that negotiation of 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 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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.

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

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

[0308] Optionally, the DRX determination device 1000 is Further comprising a fourth receiving module for receiving second information transmitted by the first terminal, the second information being used to indicate that negotiation of 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 decision device comprises: The method further includes a third determination module for generating the feedback information based on third information, the third information being used to indicate at least one of an upper threshold for an activation time length of a SL DRX and a lower threshold for an activation time length of a SL DRX.

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

[0312] The DRX determination device 1000 according to the embodiment of the present application can implement each process implemented by the embodiment of the method in FIG. 4 and achieve the same technical effects, and will not be further described here to avoid repetition of description.

[0313] Optionally, as shown in Fig. 11, an embodiment of the present application further provides 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 the program or instruction is executed by the processor 1101, each process of the method embodiment of Fig. 3 or Fig. 4 can be realized and the same technical effect can be achieved. In order to avoid repetition of description, no further description will be given here.

[0314] FIG. 12 is a hardware structural schematic diagram of a terminal implementing an embodiment of the present application.

[0315] The terminal 1200 includes components such as, but not limited to, 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.

[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 powering each component, and the power source may be logically connected to the processor 1210 by a power management system, so that the power management system can realize functions such as charge / discharge management and power consumption management. The terminal structure shown in FIG. 12 does not constitute a limitation on the terminal, and the terminal may include more or less components than the number of components shown, or a combination of some components, or a different arrangement of components, and will not be further described here.

[0317] It should be understood that in the embodiment of the present application, the input unit 1204 may include a graphics processor (Graphics Processing Unit, GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes image data of still or video images 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, or the like. 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 described further herein.

[0318] In the embodiment of the present application, the radio frequency unit 1201 receives downlink data from the network side device, and then causes the processor 1210 to process the data, and transmits uplink data to the network side device. In general, 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, where the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (e.g., a sound playback function, an image playback function, etc.), etc. The memory 1209 may include a high-speed random access memory or a non-volatile memory, where 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, the memory 1209 may be at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory device.

[0320] The processor 1210 may include one or more processing units. Alternatively, the processor 1210 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communication, such as a baseband processor. As can be understood, the modem processor does not have to be integrated into the processor 1210.

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

[0322] In this case, the radio frequency unit 1201 is Sending first information to a second terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and receiving feedback information for 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 ​​having one-to-one correspondence with the N sets of SL DRX configurations.

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

[0325] Optionally, the feature information group includes at least one of: SL DRX allocation 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 a period, an offset amount to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer; Here, the target reference point in time is a reference point in time at which the SL DRX configuration becomes valid.

[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 a SL DRX configuration request message.

[0328] Optionally, the feedback information comprises: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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.

[0329] Optionally, the K sets of SL DRX configurations are The K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; The K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

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

[0331] Optionally, the feedback information is carried by any one of a direct link establishment accept message, a direct link modification accept message, a direct link RRC relocation complete message, and a SL DRX configuration response message.

[0332] Optionally, if the feedback information satisfies a first condition, the processor 1210: if the first terminal rejects the feedback information, to perform 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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: Sending second information to the second terminal by a radio frequency unit 1201, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an SL DRX configuration between the first terminal and the second terminal.

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

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

[0336] Optionally, the processor 1210 further comprises: used to perform a second operation; Here, the second operation is Sending second information to the second terminal by a radio frequency unit 1201, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; setting the direct link to a DRX deactivation state; and triggering a renegotiation of an 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, 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 for an SL DRX activation time length and a lower threshold value for an SL DRX activation time length.

[0339] Optionally, if the feedback information satisfies a first condition, the processor 1210 is further used to determine whether to accept the feedback information based on third information, the third information being used to indicate at least one of an upper threshold of an activation time length of a SL DRX and a lower threshold of an activation time length of a 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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 Receiving first information sent by a first terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; and transmitting feedback information for 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 ​​having one-to-one correspondence with the N sets of SL DRX configurations.

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

[0344] Optionally, the feature information group includes at least one of: SL DRX allocation 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 periodicity, an offset to a target reference point, a duration, a running time of a deactivation timer, a running time of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time of a retransmission timer, where the target reference point is a reference 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 a SL DRX configuration request message.

[0347] Optionally, the feedback information comprises: M index values; M index values ​​and a first parameter in a first SL DRX configuration; K sets of SL DRX configurations, Here, the M index values ​​have a one-to-one correspondence 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.

[0348] Optionally, the K sets of SL DRX configurations are The K set of SL DRX arrangements is an SL DRX arrangement among the N set of SL DRX arrangements; The K sets of SL DRX configurations are obtained by modifying SL DRX configurations in the N sets of SL DRX configurations by the second terminal; the K sets of SL DRX allocations are SL DRX allocations other than the N sets of SL DRX allocations.

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

[0350] Optionally, the feedback information is carried by any one of a direct link establishment accept message, a direct link modification accept message, a direct link RRC relocation complete message, and a 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 a negotiation of a 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 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; 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.

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

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

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

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

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

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

[0358] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the method embodiment of Fig. 3 or Fig. 4 can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0359] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. The readable storage medium may be volatile or non-volatile. It should be noted that the readable storage medium may be non-transitory.

[0360] The embodiment of the present application further provides a chip, the chip including a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction of a network side device, and realize each process of the embodiment of the method of Fig. 3 or Fig. 4, and can achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0361] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0362] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes this element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0363] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present application may be substantially or in part embodied in the form of a software product. The computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0364] Although the embodiments of the present application have been described above in conjunction with the drawings, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which fall within the scope of protection of this application.

Claims

1. A discontinuous reception DRX determination method performed by a first terminal, comprising: sending first information to a second terminal, the first information being used to indicate N sets of sublink SL DRX configurations, where N is a positive integer; receiving feedback information for the first information transmitted by the second terminal, the feedback information including: indicating a rejection of acceptance of the N sets of SL DRX configurations; After receiving feedback information for the first information transmitted by the second terminal, the method includes: Executing a second operation, the second operation further including: adopting a DRX scheme to stop data transmission and reception between the first terminal and the second terminal; The SL DRX configuration includes at least one of a period, an offset amount to a target reference point, a duration, a running time length of a deactivation timer, a running time length of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time length of a retransmission timer, where the target reference point is a reference point at which the SL DRX configuration becomes effective.

2. The first information further includes N feature information groups that correspond 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 ​​that correspond one-to-one to the N sets of SL DRX configurations; 2. The method of claim 1, wherein 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.

3. 2. The method of 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 a SL DRX configuration request message.

4. The feedback information includes any one of M index values, M index values, 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 of claim 1.

5. If the feedback information satisfies a first condition, after receiving feedback information for the first information sent by the second terminal, the method includes: If the first terminal rejects the feedback information, 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 sets of SL DRX configurations included in the feedback information are obtained by modifying SL DRX configurations 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; The first operation includes: Sending second information to the second terminal, the second information being used to indicate that negotiation of 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 a DRX method; and triggering a renegotiation of SL DRX configuration between the first terminal and the second terminal.

6. The second operation is Sending second information to the second terminal, the second information being used to indicate that negotiation of SL DRX configuration between the first terminal and the second terminal has failed; and triggering a renegotiation of 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:

2. The method of claim 1, further comprising: 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 of an SL DRX activation time length and a lower threshold of an SL DRX activation time length.

8. If the feedback information satisfies a first condition, after receiving feedback information for the first information sent by the second terminal, the method includes: 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 of an activation time length of SL DRX and a lower threshold of an activation time length 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 SL DRX configurations in the N sets of SL DRX configurations by the second terminal; and and wherein 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.

9. A DRX determination method performed 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, where N is a positive integer; and transmitting feedback information for the first information to the first terminal, the feedback information including instructing the first terminal to reject acceptance of the N sets of SL DRX configurations; After transmitting feedback information for the first information to the first terminal, the method includes: Further comprising: adopting a DRX method to stop data transmission and reception between the first terminal and the second terminal; The SL DRX configuration includes at least one of a period, an offset amount to a target reference point, a duration, a running time length of a deactivation timer, a running time length of a round trip time (RTT) timer associated with a hybrid automatic repeat request (HARQ) process, and a running time length of a retransmission timer, wherein the target reference point is a reference point at which the SL DRX configuration becomes effective.

10. The first information further includes N feature information groups that correspond 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 ​​that correspond one-to-one to the N sets of SL DRX configurations; 10. The method of claim 9, wherein 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.

11. 10. The method of claim 9, 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 a SL DRX configuration request message.

12. The feedback information includes any one of M index values, M index values, 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.

10. The method of claim 9.

13. If the feedback information satisfies a first condition, after transmitting feedback information for the first information to the first terminal, the method includes: receiving second information transmitted by the first terminal, the second information being used to indicate that negotiation of 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 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 N sets of SL DRX configurations by the second terminal; and and wherein 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.

14. Before transmitting feedback information for the first information to the first terminal, the method further comprises:

10. The method of claim 9, further comprising: generating the feedback information based on third information, the third information being used to indicate at least one of an upper threshold for an SL DRX activation time length and a lower threshold for an SL DRX activation time length.

15. A terminal comprising a processor, a memory, and a program or instructions stored in the memory and operable on the processor, wherein, when the program or instructions are executed by the processor, the terminal implements steps of a DRX decision method according to any one of claims 1 to 8, or implements steps of a DRX decision method according to any one of claims 9 to 14.

Citation Information

Patent Citations

  • Method and system for configuring discontinuous reception (DRX) parameters in long term evolution system

    CN103945505A

  • DRX configuration method and device of sidelink

    CN111800894A

  • Method and device for reducing power of device in wireless communication system supporting direct device to device communication

    EP3113548A1

  • Radio terminal device, radio base station device and communication control method

    JP2013201508A

  • Method, Device, and System for Indicating Discontinuous Data Scheduling

    US20130229966A1