Sidelink resource request methods, terminal devices, and network devices

Abstract

This application relates to a sidelink resource request method, a terminal device, and a network device. The method includes: during sidelink communication between a first terminal device and a second terminal device, the first terminal device sends first information to the network device, the first information indicating that the second terminal device is in a discontinuous reception DRX active state. Utilizing embodiments of this application can optimize the sidelink resource request mechanism.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a sidelink resource request method, a terminal device, and a network device. Background Technology

[0002] Device-to-Device (D2D) and Vehicle-to-Everything (V2X, also known as vehicle-to-everything) technologies are important components of mobile communications. In D2D or V2X scenarios, direct communication between devices is supported through sidelink (SL) transmission technology. Unlike traditional cellular systems where communication data is received or transmitted through base stations, V2X systems use direct terminal-to-terminal communication, resulting in higher spectral efficiency and lower transmission latency. V2X systems support two transmission modes: Mode 1 and Mode 2. In Mode 1, the terminal's transmission resources are allocated by the network, and the terminal transmits sidelink data on the sidelink according to the allocated resources. In Mode 2, the terminal selects resources from a resource pool for sidelink transmission. There is a scenario where the receiving terminal is a user configured with Discontinuous Reception (DRX). When the sending terminal configured with Mode 1 is in certain specific states, it can first use the resources of Mode 2 for sidelink transmission. After returning to normal, the sending terminal can request sidelink transmission resources from the network device. At this time, it uses Mode 1 to transmit data. According to existing regulations, the network device may consider the receiving terminal to be still in a sleep state. Therefore, the network device will not allocate resources to the sending terminal in a timely manner, which may lead to the failure of the sidelink resource request and thus the failure of the sidelink transmission. Summary of the Invention

[0003] In view of this, embodiments of this application provide a sidelink resource request method, a terminal device, and a network device, which can be used to optimize the sidelink resource request mechanism.

[0004] This application provides a sidelink resource request method applied to a terminal device, comprising: during sidelink communication between a first terminal device and a second terminal device, the first terminal device sends first information to a network device, wherein the first information is used to indicate that the second terminal device is in a discontinuous DRX activation state.

[0005] This application provides a sidelink resource request method applied to a terminal device, comprising: after receiving at least one sidelink message sent by a first terminal device, the second terminal device enters a DRX activation state and waits for sidelink transmission from the first terminal device.

[0006] This application provides a sidelink resource request method applied to a network device, comprising: during sidelink communication between a first terminal device and a second terminal device, the network device receiving first information sent by the first terminal device, wherein the first information is used to indicate that the second terminal device is in a DRX active state.

[0007] This application embodiment also provides a terminal device, including: a first transmitting module, configured to transmit first information to a network device during sidelink communication between the first terminal device and the second terminal device, wherein the first information is used to indicate that the second terminal device is in a discontinuous reception DRX activation state.

[0008] This application embodiment also provides a terminal device, including: a state processing module, configured to, after receiving at least one sidelink message sent by a first terminal device, cause the second terminal device to enter a DRX activation state and wait for sidelink transmission from the first terminal device.

[0009] This application embodiment also provides a network device, including: a receiving module, configured to receive first information sent by the first terminal device during sidelink communication between the first terminal device and the second terminal device, wherein the first information is used to indicate that the second terminal device is in a DRX active state.

[0010] This application embodiment also provides a terminal device, including: a processor and a memory, wherein the memory is used to store a computer program, and the processor calls and runs the computer program stored in the memory to perform the method described above.

[0011] This application embodiment also provides a network device, including: a processor and a memory, wherein the memory is used to store a computer program, and the processor calls and runs the computer program stored in the memory to perform the method described above.

[0012] This application also provides a chip, including: a processor, configured to call and run a computer program from a memory, causing a device on which the chip is installed to perform the method described above.

[0013] This application also provides a computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to perform the method described above.

[0014] This application also provides a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to perform the method described above.

[0015] This application also provides a computer program that causes a computer to perform the method described above.

[0016] Using the embodiments of this application, during the sidelink communication process of the terminal device, the sending terminal device can send information to the network device to report the DRX status of the receiving terminal device to the network. This can help the network device accurately determine the status of the receiving terminal device. Based on this, the network device can allocate sidelink transmission resources to the sending terminal device in a timely manner. Therefore, using the embodiments of this application can improve the probability of successfully requesting sidelink transmission resources. Attached Figure Description

[0017] Figure 1 and Figure 2 These are schematic diagrams of two side-link communication system architectures according to embodiments of this application.

[0018] Figure 3 This is a flowchart of a side-link resource request method on the sending terminal device side according to an embodiment of this application.

[0019] Figure 4 This is a flowchart of the side-link resource request method on the receiving terminal device side according to an embodiment of this application.

[0020] Figure 5 This is a flowchart of a network device-side crosslink resource request method according to an embodiment of this application.

[0021] Figure 6 This is a schematic diagram of the reporting process via physical layer signaling in an embodiment of this application.

[0022] Figure 7 This is a schematic diagram of the reporting process via media access control layer signaling in an embodiment of this application.

[0023] Figure 8 This is a schematic diagram of the reporting process via RRC signaling in an embodiment of this application.

[0024] Figure 9 This is a schematic structural block diagram of the transmitting terminal device according to an embodiment of this application.

[0025] Figure 10 This is a schematic structural block diagram of the receiving terminal device according to an embodiment of this application.

[0026] Figure 11 This is a schematic structural block diagram of a network device according to an embodiment of this application.

[0027] Figure 12 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0028] Figure 13This is a schematic block diagram of a chip according to an embodiment of this application.

[0029] Figure 14 This is a schematic block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0030] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0031] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) communication systems, or other communication systems.

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

[0033] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0034] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system such as an NR network, or terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0035] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).

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

[0037] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0038] In the embodiments of this application, the network device can be a device for communicating with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, wearable device, or a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

[0039] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located on land, water, or other similar locations.

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

[0041] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" is used to describe the relationship between related objects, for example, indicating that there are three possible relationships between related objects. For instance, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the related objects are in an "or" relationship. In the description of the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two objects, or an association relationship, or a relationship of instruction and being instructed, configuration and being configured, etc.

[0042] To clearly illustrate the ideas behind the embodiments of this application, a brief description of the relevant content of side link transmission in the communication system is first provided.

[0043] Two transmission modes are defined in the LTE D2D / V2X system: Mode A and Mode B. (Refer to...) Figure 1In Mode A, the terminal's transmission resources are allocated by the base station, and the terminal transmits data on the side link according to the resources allocated by the base station. The base station can allocate resources for a single transmission or for semi-static transmission. In Mode B, the terminal selects resources from the resource pool for data transmission. 3GPP divides D2D into different phases for research, as illustrated below.

[0044] • Proximity-based Service (ProSe): In ProSe, by configuring the location of the resource pool in the time domain, such as making the resource pool discontinuous in the time domain, the UE can send / receive data discontinuously on the side link, thereby achieving the effect of saving power.

[0045] • Vehicle-to-everything (V2X): In V2X, since the vehicle system has a continuous power supply, power efficiency is not the main issue, but data transmission latency is the main issue. Therefore, the system design requires terminal devices to continuously send and receive data.

[0046] • Wearable Devices (FeD2D): In FeD2D, it is discussed that base stations can configure the DRX parameters of remote terminals through relay terminals, but the specific details of how to perform DRX configuration have not yet been concluded.

[0047] Regarding the NR V2X system, building upon the LTE V2X system, the NR V2X system is not limited to broadcast scenarios but can also be extended to unicast and multicast scenarios. Similar to LTE V2X, NR V2X defines the aforementioned mode-1 and mode-2 resource granting modes; furthermore, terminals can be in a hybrid mode, using either mode-1 or mode-2 to acquire resources. Resource locations can be indicated through sidelink granting, for example, by indicating the time-frequency location of the corresponding Physical Sidelink Control Channel (PSCCH) and Physical Sidelink Shared Channel (PSSCH) resources.

[0048] Similar to LTE V2X, in NR V2X, terminal devices such as vehicle systems can be considered to have a continuous power supply, so power efficiency is not the main issue, while data transmission latency is the main issue. Therefore, the system design requires terminal devices to be able to continuously send and receive data.

[0049] Regarding the DRX mechanism, the UE can discontinuously monitor the Physical Downlink Control Channel (PDCCH) according to the DRX configuration to save energy. If the PDCCH includes identification information corresponding to the UE, such as any of the following: Cell Radio Network Temporary Identity (C-RNTI), Configuration Scheduling RNTI (CS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent Channel State Information RNTI (SP-CSI-RNTI), Transmit Power Control-PUCCH–RNTI (TPC-PUCCH-RNTI), or Transmit Power Control-PUCCH Shared Channel RNTI (TPC-PUCCH-RNTI), the UE can achieve this. With the Control-PUSCH-RNTI (TPC-PUSCH-RNTI) and Transmit Power Control-Sounding Reference Signal-RNTI (TPC-SRS-RNTI), the UE can perform corresponding DRX operations based on the control information. The network side can control the UE's DRX behavior by configuring a series of parameters. The UE can be in a DRX active state under at least one of the following conditions:

[0050] • During the execution of the timer drx-onDurationTimer or drx-InactivityTimer;

[0051] • During the operation of timer drx-RetransmissionTimerDL or drx-RetransmissionTimerUL;

[0052] • During the execution of the timer ra-ContentionResolutionTimer or the window msgB-ResponseWindow;

[0053] • There are unprocessed scheduling requests (SRs);

[0054] • PDCCH indicates that a new transmission period has begun.

[0055] Regarding mode-1 and mode-2, if the terminal is in certain specific states (such as RRC resume, connection establishment, problem detection, etc.), and if the resource pool sl-TxPoolExceptional is configured in the RRC signaling or system message (such as SIB12), the terminal can randomly select resources in the resource pool for transmission, that is, use mode-2 for side-line transmission. Here, according to existing regulations, if the sending terminal (Tx-UE) is in the aforementioned specific state and randomly selects resources from the sl-TxPoolExceptional resource pool for transmission, the receiving terminal (Rx-UE) can start a timer (e.g., an inactive timer) after receiving a message from the Tx-UE, enter the active state of DRX, and wait for subsequent transmission (entering the inactive state of DRX after the timer expires). Then, the Tx-UE enters the normal state and can use mode-1 to request sidelink transmission resources from the network. However, since the network side does not know that the Rx-UE's DRX configuration has entered the active state at this time, and still considers the Rx-UE to be in a dormant state, it may not issue configuration authorization in a timely manner, causing the Tx-UE to fail to request resources, and thus the sidelink transmission fails.

[0056] Analysis revealed that the main reason for the above problems is that the DRX mechanism contains both relatively static configurations (such as periodic timers "on duration timers") and relatively dynamic configurations (such as inactive timers "inactive-timers"). When the terminal side, such as Tx-UE, is in certain specific states, the network side may not be able to accurately determine the state of the terminal side, such as Rx-UE, which leads to the terminal side failing to request resources, and subsequently, the side-by-side transmission fails.

[0057] Therefore, this application provides a sidelink resource request method, applied to a first terminal device, with reference to... Figure 3 The method includes:

[0058] S101, during the side link communication between the first terminal device and the second terminal device, the first terminal device sends first information to the network device, the first information being used to indicate that the second terminal device is in a discontinuous DRX receiving active state.

[0059] According to an embodiment of this application, a first terminal device and a second terminal device perform sidelink communication. The first terminal device can send information to the network device to report that the second terminal device is in a DRX active state. This helps the network device accurately determine the state of the second terminal device. Based on this, the network device can allocate sidelink transmission resources to the first terminal device in a timely manner, improving the success rate of resource requests and avoiding sidelink transmission failures.

[0060] Correspondingly, embodiments of this application also provide a sidelink resource request method, applied to a second terminal device, referencing... Figure 4 The method includes:

[0061] S201, after receiving at least one sidelink message sent by the first terminal device, the second terminal device enters the DRX activation state and waits for sidelink transmission from the first terminal device.

[0062] According to an embodiment of this application, the first terminal device and the second terminal device perform sidelink communication. After the second terminal device receives the sidelink message sent by the first terminal device, the second terminal device can enter the DRX activation state. In the DRX activation state, the second terminal device can continuously receive sidelink messages to ensure the sidelink transmission quality.

[0063] Correspondingly, embodiments of this application also provide a side-link resource request method, applied to network devices, see reference. Figure 5 The method includes:

[0064] S301, during the side-link communication between the first terminal device and the second terminal device, the network device receives first information sent by the first terminal device, the first information being used to indicate that the second terminal device is in DRX active state.

[0065] According to an embodiment of this application, a first terminal device and a second terminal device communicate via a sidelink. The network device can receive information sent by the first terminal device, which includes the DRX activation status information of the second terminal device. Based on this information, the network device can accurately determine the status of the second terminal device. If the network device receives a sidelink resource allocation request, it can allocate resources in a timely manner, improving the success rate of resource requests and ensuring normal transmission of sidelink messages.

[0066] Optionally, after receiving at least one sidelink message sent by the first terminal device, the second terminal device starts a timer, enters the DRX active state, and receives data; after the timer expires, the second terminal device enters the DRX inactive state.

[0067] In an embodiment of this application, optionally, the at least one sidelink message is a sidelink message sent by the first terminal device to the second terminal device using transmission resources in the resource pool.

[0068] In an embodiment of this application, optionally, the at least one sidelink message is a sidelink message sent by the first terminal device to the second terminal device in mode 2.

[0069] In an embodiment of this application, optionally, the first terminal device is configured to transmit sidelink messages in mode 1.

[0070] In an embodiment of this application, optionally, the network device allocates sidelink transmission resources to the first terminal device according to mode 1.

[0071] Optionally, in an embodiment of this application, after the first terminal device sends at least one sidelink message to the second terminal device, the first terminal device sends first information to the network device.

[0072] Optionally, in an embodiment of this application, after the first terminal device sends at least one sidelink message to the second terminal device using transmission resources in the resource pool, the first terminal device sends first information to the network device.

[0073] Optionally, in an embodiment of this application, when the first terminal device sends at least one sidelink message to the second terminal device in mode 2, and the first terminal device switches from mode 2 to mode 1, the first terminal device sends first information to the network device.

[0074] In embodiments of this application, optionally, the first information is carried by at least one of the following:

[0075] ●Physical layer signaling;

[0076] ●Media access control layer signaling;

[0077] ● Radio Resource Control (RRC) signaling.

[0078] In an embodiment of this application, the first information may optionally be carried via Uplink Control Information (UCI).

[0079] In an embodiment of this application, the first information may optionally be carried by a Media Access Control Element (MAC CE).

[0080] In embodiments of this application, optionally, the first information includes at least one of the following:

[0081] ●The first information includes the layer 1 address information of the second terminal device;

[0082] ●The first information includes a first identifier, which corresponds to the second terminal device;

[0083] ●The first information includes the layer 2 address information of the second terminal device.

[0084] In an embodiment of this application, optionally, when the first information includes a first identifier, the first terminal device maintains a first list, the first list including identifier information of one or more terminal devices that communicate with the first terminal device via a sidelink; wherein the first identifier belongs to the first list.

[0085] Optionally, in embodiments of this application, the first information is carried via SidelinkUEInformationNR.

[0086] In an embodiment of this application, optionally, the first information includes at least 1 bit of the SidelinkUEInformationNR information, wherein the at least 1 bit is a first value indicating that the second terminal device is in a DRX active state, and the at least 1 bit is a second value indicating that the second terminal device is in a DRX inactive state.

[0087] Optionally, in an embodiment of this application, after the first terminal device sends the first information to the network device, the first terminal device uses the resources allocated by the network device to send a sidelink message to the second terminal device.

[0088] Using at least one embodiment of this application, after introducing a side-link power-saving mechanism, the transmitting UE in mode 1 can send a report to the network to synchronize the DRX status of the other UE; furthermore, using at least one embodiment of this application, at least one of the following information can be clarified:

[0089] (1) When does the sending UE trigger this report?

[0090] (2) What signal carries this report;

[0091] (3) What content should be included in the report.

[0092] The implementation of the sidelink resource request method of this application has been described above through multiple embodiments, which is applicable to both unicast and multicast scenarios. The implementation process of this application's embodiments is described below through several specific examples.

[0093] Example 1: Reporting via physical layer signaling

[0094] refer to Figure 6 In this embodiment, terminal UE1 reports the DRX status of the other terminal UE2 to the network device via physical layer signaling. This embodiment can be implemented in various ways, which are described in detail below.

[0095] Method 1:

[0096] Physical layer addresses are used to distinguish UEs that communicate with UE1 via the sidelink and are configured with DRX. For example, UE1 can indicate to the network that a UE is in DRX active state by including the physical layer address in the reporting message.

[0097] refer to Figure 6 The following is an illustrative description of one interaction process in this embodiment:

[0098] 1) UE1 sends message 1 to UE2 using, for example, resources from a randomly selected sl-TxPoolExceptional resource pool;

[0099] 2) When UE2 receives message 1 from UE1, it starts a timer (e.g., inactive-timer), enters the DRX active state, and waits for other messages from UE1;

[0100] 3) UE1 reports UCI information to the network, which is used to indicate that UE2 is in DRX active state; optionally, the UCI information includes UE2's layer 1 address information (e.g., 5 bits);

[0101] 4) UE1 obtains sidelink transmission resources through mode 1;

[0102] 5) UE1 sends message 2 to UE2 using the resources in the configuration authorization.

[0103] Method 2:

[0104] By adding specific parameters, UEs that communicate with UE1 via the side link and are configured with DRX can be distinguished.

[0105] For ease of description, this embodiment will refer to the added specific parameter as the "DRX_configuration_ID" parameter. Each UE can maintain this parameter list DRX_configuration_ID list, and by including the DRX_configuration_ID parameter pointing to the corresponding UE (peer UE, UE2 in this embodiment) in the reporting message, it can indicate to the network that the UE is in the DRXactive state.

[0106] refer to Figure 6 The following is an illustrative description of one interaction process in this embodiment:

[0107] 1) UE1 sends message 1 to UE2 using, for example, resources from a randomly selected sl-TxPoolExceptional resource pool;

[0108] 2) When UE2 receives message 1 from UE1, it starts a timer (e.g., inactive-timer), enters the DRX active state, and waits for other messages from UE1;

[0109] 3) UE1 reports UCI information to the network, which is used to indicate that UE2 is in DRX active state; optionally, the UCI information includes DRX_configuration_ID information pointing to UE2;

[0110] 4) UE1 obtains sidelink transmission resources through mode 1;

[0111] 5) UE1 sends message 2 to UE2 using the resources in the configuration authorization.

[0112] Example 2: Reporting via Media Access Control Layer Signaling

[0113] refer to Figure 7 In this embodiment, terminal UE1 reports the DRX status of the other terminal UE2 to the network device via media access control layer signaling. This embodiment can be implemented in various ways, which are described in detail below.

[0114] Method 1:

[0115] MAC layer addresses are used to distinguish UEs that communicate with UE1 via the sidelink and are configured with DRX. For example, the MAC layer address is included in the reporting message to indicate to the network that a UE is in DRX active state.

[0116] refer to Figure 7 The following is an illustrative description of one interaction process in this embodiment:

[0117] 1) UE1 sends message 1 to UE2 using, for example, resources from a randomly selected sl-TxPoolExceptional resource pool;

[0118] 2) When UE2 receives message 1 from UE1, it starts a timer (e.g., inactive-timer), enters the DRX active state, and waits for other messages from UE1;

[0119] 3) UE1 reports MAC CE information to the network, which is used to indicate that UE2 is in DRX active state; optionally, the MAC CE information includes UE2's layer 2 address information (or MAC address information, such as 16 bits);

[0120] 4) UE1 obtains sidelink transmission resources through mode 1;

[0121] 5) UE1 sends message 2 to UE2 using the resources in the configuration authorization.

[0122] Method 2:

[0123] UEs that communicate with UE1 via the sidelink and are configured with DRX are distinguished by adding specific parameters. For example, in this embodiment, the added specific parameter is denoted as the "DRX_configuration_ID" parameter. Each UE can maintain a parameter list DRX_configuration_ID list, and by including the DRX_configuration_ID parameter pointing to the corresponding UE (peer UE, UE2 in this embodiment) in the reporting message, the UE in the DRX active state is indicated to the network.

[0124] refer to Figure 7 The following is an illustrative description of one interaction process in this embodiment:

[0125] 1) UE1 sends message 1 to UE2 using, for example, resources from a randomly selected sl-TxPoolExceptional resource pool;

[0126] 2) When UE2 receives message 1 from UE1, it starts a timer (e.g., inactive-timer), enters the DRX active state, and waits for other messages from UE1;

[0127] 3) UE1 reports MAC CE information to the network, which is used to indicate that UE2 is in DRX active state; optionally, the MAC CE information includes DRX_configuration_ID information pointing to UE2;

[0128] 4) UE1 obtains sidelink transmission resources through mode 1;

[0129] 5) UE1 sends message 2 to UE2 using the resources in the configuration authorization.

[0130] Example 3: Reporting via RRC signaling

[0131] In this embodiment, terminal UE1 reports the DRX status of the other terminal UE2 to the network device via RRC signaling.

[0132] For example, refer to Figure 8 The UE is in RRC connected state, meaning it has already established a connection with the cellular network, and the UE ensures that it has obtained a valid system information block SIB12. The following is an illustrative description of an interaction process in this embodiment:

[0133] 1) UE1 sends message 1 to UE2 using, for example, resources from a randomly selected sl-TxPoolExceptional resource pool;

[0134] 2) When UE2 receives message 1 from UE1, it starts a timer (e.g., inactive-timer), enters the DRX active state, and waits for other messages from UE1;

[0135] 3) UE1 initiates the SidelinkUEInformation procedure, during which it reports a SidelinkUEInformationNR message to the network. This message is used to indicate that UE2 is in the DRX active state. Optionally, the SL-TxResourceReq IE parameter in the SidelinkUEInformationNR message includes a parameter used to indicate that UE2 is in the DRX active state.

[0136] 4) UE1 obtains sidelink transmission resources through mode 1;

[0137] 5) UE1 sends message 2 to UE2 using the resources in the configuration authorization.

[0138] The following is a brief explanation of the content of the SidelinkUEInformationNR message.

[0139] After the UE obtains SIB12, it can send a SidelinkUEInformationNR message to the network. This message is used to report at least one of the following pieces of information related to the sidelink UE in NR-side traversal communication:

[0140] • Whether you want to (or do not want to) receive or transmit NR-side link messages;

[0141] • Request the allocation or release of transmission resources used for NR-side link messages;

[0142] • Report Quality of Service (QoS) parameters and QoS files related to NR-side walkway messages;

[0143] • Report that a sidelink wireless link failure or sidelink RRC configuration failure has been detected;

[0144] • Report sidelink UE capability information for unicast to peer UEs;

[0145] • Radio Link Control (RLC) protocol for reporting side-link data radio bearers

[0146] RLC mode information is received from the peer UE used for unicast.

[0147] The process by which the UE reports the SidelinkUEInformationNR message to the network can be called the SidelinkUEInformation process.

[0148] Using at least one of the above embodiments of this application, it can be applied to the side link transmission mechanism. During the process of the UE changing from mode2 resource selection mode to mode1 resource selection mode, by having the UE report the DRX status of the other UE to the network, the problem of the network not being able to issue configuration authorization in a timely manner due to the network not knowing the current DRX active status of the other UE in the existing mechanism can be avoided.

[0149] The specific settings and implementation methods of the embodiments of this application have been described above from different perspectives through multiple embodiments. Corresponding to the processing method of at least one of the above embodiments, the embodiments of this application also provide a terminal device 100, see reference. Figure 9 It includes:

[0150] The first sending module 110 is used to send first information to the network device during the side link communication between the first terminal device and the second terminal device. The first information is used to indicate that the second terminal device is in a discontinuous reception DRX activation state.

[0151] Optionally, the first terminal device is configured to transmit sidelink messages in mode 1.

[0152] Optionally, after the first terminal device sends at least one sidelink message to the second terminal device, the first sending module sends first information to the network device.

[0153] Optionally, after the first terminal device sends at least one sidelink message to the second terminal device using transmission resources in the resource pool, the first sending module sends first information to the network device.

[0154] Optionally, when the first terminal device sends at least one sidelink message to the second terminal device in mode 2, and the first terminal device switches from mode 2 to mode 1, the first sending module sends first information to the network device.

[0155] Optionally, the first information is carried by at least one of the following: physical layer signaling, media access control layer signaling, and radio resource control (RRC) signaling.

[0156] Optionally, the first information is carried via UCI.

[0157] Optionally, the first information is carried via MAC CE.

[0158] Optionally, the first information is carried via SidelinkUEInformationNR.

[0159] Optionally, the first information includes the Layer 1 address information of the second terminal device.

[0160] Optionally, the first information includes a first identifier, which corresponds to the second terminal device.

[0161] Optionally, the first information includes the layer 2 address information of the second terminal device.

[0162] Optionally, the terminal device 100 further includes: a maintenance module for maintaining a first list, the first list including identification information of one or more terminal devices that communicate with the first terminal device via a side link; wherein the first identifier belongs to the first list.

[0163] Optionally, the first information includes at least one bit in the SidelinkUEInformationNR information, wherein the at least one bit is a first value indicating that the second terminal device is in a DRX active state, and the at least one bit is a second value indicating that the second terminal device is in a DRX inactive state.

[0164] Optionally, the terminal device 100 further includes a second sending module, configured to send a sidelink message to the second terminal device using resources allocated by the network device after the first terminal device sends the first information to the network device.

[0165] Corresponding to the processing method of at least one of the above embodiments, this application also provides a terminal device 200, with reference to... Figure 10 It includes:

[0166] The state processing module 210 is used to enable the second terminal device to enter the DRX activation state after receiving at least one side link message sent by the first terminal device, and wait for side link transmission from the first terminal device.

[0167] Optionally, the terminal device 200 further includes: an activation module, configured to activate a timer after receiving at least one sidelink message sent by the first terminal device; and after the timer expires, the state processing module causes the second terminal device to enter a DRX inactive state.

[0168] Optionally, the at least one sidelink message is a sidelink message sent by the first terminal device to the second terminal device using transmission resources in the resource pool.

[0169] Optionally, the at least one sidelink message is a sidelink message sent by the first terminal device to the second terminal device in mode 2.

[0170] Optionally, the first terminal device is configured to transmit sidelink messages in mode 1.

[0171] Corresponding to the processing method of at least one of the above embodiments, this application also provides a network device 300, referencing... Figure 11 It includes:

[0172] The receiving module 310 is used to receive first information sent by the first terminal device during the side link communication between the first terminal device and the second terminal device. The first information is used to indicate that the second terminal device is in the DRX active state.

[0173] Optionally, the first terminal device is configured to transmit sidelink messages in mode 1.

[0174] Optionally, the network device 300 further includes: an allocation module, configured to allocate sidelink transmission resources to the first terminal device according to mode 1.

[0175] Optionally, the first information is carried by at least one of the following: physical layer signaling, media access control layer signaling, and radio resource control (RRC) signaling.

[0176] Optionally, the first information is carried via UCI.

[0177] Optionally, the first information is carried via MAC CE.

[0178] Optionally, the first information is carried via SidelinkUEInformationNR.

[0179] Optionally, the first information includes the Layer 1 address information of the second terminal device.

[0180] Optionally, the first information includes a first identifier, which corresponds to the second terminal device.

[0181] Optionally, the first information includes the layer 2 address information of the second terminal device.

[0182] Optionally, if the first information includes a first identifier, the first terminal device maintains a first list, which includes identifier information of one or more terminal devices that communicate with the first terminal device via a sidelink; wherein the first identifier belongs to the first list.

[0183] Optionally, the first information includes at least one bit in the SidelinkUEInformationNR information, wherein the at least one bit is a first value indicating that the second terminal device is in a DRX active state, and the at least one bit is a second value indicating that the second terminal device is in a DRX inactive state.

[0184] The terminal devices 100, 200 and network device 300 in this application embodiment can realize the corresponding functions of the terminal devices in the aforementioned method embodiments. The processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal devices 100, 200 and network device 300 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here.

[0185] It should be noted that the functions described in the various modules (sub-modules, units, or components, etc.) of the terminal devices 100, 200, and network device 300 in the embodiments of this application can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.). For example, the first sending module and the second sending module can be different modules or the same module, both of which can realize their corresponding functions in the embodiments of this application. In addition, the sending module and receiving module in the embodiments of this application can be implemented by the transceiver of the device, and some or all of the other modules can be implemented by the processor of the device.

[0186] Figure 12 This is a schematic structural diagram of a communication device 600 according to an embodiment of the present application, wherein the communication device 600 includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of the present application.

[0187] Optionally, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to implement the methods described in the embodiments of this application.

[0188] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0189] Optionally, the communication device 600 may also include a transceiver 630, which the processor 610 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0190] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

[0191] Optionally, the communication device 600 may be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0192] Optionally, the communication device 600 may be a terminal device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0193] Figure 13This is a schematic structural diagram of a chip 700 according to an embodiment of this application, wherein the chip 700 includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0194] Optionally, chip 700 may further include memory 720. Processor 710 can retrieve and run computer programs from memory 720 to implement the methods described in this embodiment.

[0195] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0196] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0197] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0198] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0199] Optionally, the chip can be used in this application, such as Figure 9 or Figure 10 The terminal device in the embodiment, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application, will not be described in detail here for the sake of brevity.

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

[0201] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0202] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0203] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0204] Figure 14 This is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a terminal device 810 and a network device 820.

[0205] The terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the methods of various embodiments of this application, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the methods of various embodiments of this application. For the sake of brevity, further details are omitted here.

[0206] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state disks (SSDs)).

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

[0208] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0209] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of sidelink resource request, applied to a terminal device, the method comprising: in a sidelink communication process between a first terminal device and a second terminal device, the first terminal device sends first information to a network device, the first information being used to indicate that the second terminal device is in a discontinuous reception (DRX) active state; wherein the first terminal device sends the first information to the network device in the sidelink communication process between the first terminal device and the second terminal device comprises: in a case that the first terminal device sends at least one sidelink message to the second terminal device according to mode 2, and the first terminal device is converted from mode 2 to mode 1, the first terminal device sends the first information to the network device. wherein the first information is carried through medium access control (MAC) layer signaling, wherein the first information comprises a first identifier corresponding to the second terminal device, and the first information further comprises layer 2 address information of the second terminal device, the layer 2 address information comprising 16 bits.

2. The method of claim 1, wherein, The first terminal device sends the first information to the network device in the sidelink communication process between the first terminal device and the second terminal device further comprises: after the first terminal device sends at least one sidelink message to the second terminal device, the first terminal device sends the first information to the network device.

3. The method of claim 1, wherein, The first terminal device sends the first information to the network device in the sidelink communication process between the first terminal device and the second terminal device further comprises: after the first terminal device sends at least one sidelink message to the second terminal device using transmission resources in a resource pool, the first terminal device sends the first information to the network device. 4.The method of any one of claims 1-3, wherein the first information is further carried through at least one of the following: physical layer signaling, radio resource control (RRC) signaling.

5. The method of any one of claims 1-3, wherein, the first information is carried through uplink control information (UCI).

6. The method of any one of claims 1-3, wherein, the first information is carried through a medium access control (MAC) control element (CE).

7. The method of any one of claims 1-3, wherein, the first information is carried through sidelink terminal device information (SidelinkUEInformationNR). 8.The method of claim 1, wherein the first information further comprises layer 1 address information of the second terminal device. 9.The method of claim 1, in a case that the first information comprises a first identifier, the method further comprises: the first terminal device maintains a first list comprising identifier information of one or more terminal devices in sidelink communication with the first terminal device; wherein the first identifier belongs to the first list. 10.The method of claim 7, wherein The first information includes at least 1 bit in the SidelinkUEInformationNR information, the at least 1 bit being a first numerical value to indicate that the second terminal device is in a DRX active state, and the at least 1 bit being a second numerical value to indicate that the second terminal device is in a DRX inactive state.

11. The method of any one of claims 1-3, wherein, After the first terminal device sends the first information to the network device, the method further includes: The first terminal device sends a sidelink message to the second terminal device using the resource allocated by the network device.

12. A sidelink resource request method applied to a network device, the method comprising: In a sidelink communication process between a first terminal device and a second terminal device, the network device receives first information sent by the first terminal device, the first information being used to indicate that the second terminal device is in a DRX active state; The first information is sent by the first terminal device to the second terminal device according to mode 2, and the first terminal device is converted from mode 2 to mode 1, and the first information is sent to the network device. The first information is carried through medium access control layer signaling, wherein the first information includes a first identifier corresponding to the second terminal device, and the first information further includes layer 2 address information of the second terminal device, and the layer 2 address information includes 16 bits.

13. The method of claim 12, further comprising: The network device allocates sidelink transmission resources for the first terminal device according to mode 1.

14. The method of claim 12, wherein The first information is further carried through at least one of the following information: physical layer signaling, radio resource control (RRC) signaling.

15. The method of any one of claims 12-14, wherein, The first information is carried through UCI.

16. The method of any one of claims 12-14, wherein, The first information is carried through MAC CE.

17. The method of any one of claims 12-14, wherein, The first information is carried through sidelink terminal device information (SidelinkUEInformationNR).

18. The method of claim 12, wherein The first information further includes layer 1 address information of the second terminal device.

19. The method of claim 12, wherein, when the first information includes a first identifier, the method further comprises: The first terminal device maintains a first list including identifier information of one or more terminal devices in sidelink communication with the first terminal device; The first identifier belongs to the first list.

20. The method of claim 17, wherein The first information includes at least 1 bit in the SidelinkUEInformationNR information, the at least 1 bit being a first numerical value to indicate that the second terminal device is in a DRX active state, and the at least 1 bit being a second numerical value to indicate that the second terminal device is in a DRX inactive state.

21. A terminal device, comprising: The first sending module is configured to send, to a network device, first information in a sidelink communication process between the first terminal device and the second terminal device, the first information being used to indicate that the second terminal device is in a discontinuous reception (DRX) active state. The first sending module is configured to send, to a network device, first information in a sidelink communication process between the first terminal device and the second terminal device, the first information being used to indicate that the second terminal device is in a discontinuous reception (DRX) active state. The first information is carried through medium access control layer signaling, the first information includes a first identifier corresponding to the second terminal device, and the first information further includes layer 2 address information of the second terminal device, the layer 2 address information including 16 bits.

22. The terminal device of claim 21, wherein The first sending module is configured to send, to a network device, first information in a sidelink communication process between the first terminal device and the second terminal device, the first information being used to indicate that the second terminal device is in a discontinuous reception (DRX) active state.

23. The terminal device of claim 21, wherein The first sending module is configured to send, to a network device, first information in a sidelink communication process between the first terminal device and the second terminal device, the first information being used to indicate that the second terminal device is in a discontinuous reception (DRX) active state.

24. The terminal device of any one of claims 21-23, wherein The first information is further carried through at least one of the following: physical layer signaling, radio resource control (RRC) signaling.

25. The terminal device of any one of claims 21-23, wherein, The first information is carried through UCI.

26. The terminal device of any one of claims 21-23, wherein, The first information is carried through a MAC CE.

27. The terminal device of any one of claims 21-23, wherein, The first information is carried through sidelink terminal device information (SidelinkUEInformationNR).

28. The terminal device of claim 21, wherein The first information further includes layer 1 address information of the second terminal device.

29. The terminal device of claim 21, further comprising: a maintaining module configured to maintain a first list including identifier information of one or more terminal devices in sidelink communication with the first terminal device; and wherein the first identifier belongs to the first list.

30. The terminal device of claim 27, wherein The first information includes at least 1 bit in the SidelinkUEInformationNR information, the at least 1 bit being a first numerical value to indicate that the second terminal device is in a DRX active state, and the at least 1 bit being a second numerical value to indicate that the second terminal device is in a DRX inactive state.

31. The terminal device of any one of claims 21-23, further comprising: a second sending module configured to send, to the second terminal device, a sidelink message using resources allocated by the network device after the first terminal device sends the first information to the network device.

32. A network device, comprising: receiving module, configured to receive first information sent by the first terminal device in a sidelink communication process between the first terminal device and the second terminal device, the first information being used to indicate that the second terminal device is in a DRX active state; wherein the first information is at least one sidelink message sent by the first terminal device to the second terminal device according to mode 2, and the first terminal device sends to a network device in a case where the first terminal device is converted from mode 2 to mode 1. wherein the first information is carried through medium access control layer signaling, wherein the first information includes a first identifier corresponding to the second terminal device, and the first information further includes layer 2 address information of the second terminal device, and the layer 2 address information includes 16 bits.

33. The network device of claim 32, further comprising: an allocating module, configured to allocate sidelink transmission resources for the first terminal device according to mode 1.

34. The network device of any one of claims 32-33, wherein the first information is carried through at least one of the following: physical layer signaling, medium access control layer signaling, and radio resource control (RRC) signaling.

35. The network device of any of claims 32-33, wherein, the first information is carried through UCI.

36. The network device of any of claims 32-33, wherein, the first information is carried through a MAC CE.

37. The network device of any of claims 32-33, wherein, the first information is carried through sidelink terminal device information (SidelinkUEInformationNR).

38. The network device of claim 34, wherein the first information further includes layer 1 address information of the second terminal device.

39. The network device of claim 38, wherein, in a case where the first information includes a first identifier, the first terminal device maintains a first list including identifier information of one or more terminal devices in sidelink communication with the first terminal device, and the first identifier belongs to the first list.

40. The network device of claim 37, wherein the first information includes at least 1 bit in the SidelinkUEInformationNR information, the at least 1 bit being a first numerical value to indicate that the second terminal device is in a DRX active state, and the at least 1 bit being a second numerical value to indicate that the second terminal device is in a DRX inactive state.

41. A terminal device comprising: a processor and a memory, the memory being configured to store a computer program, and the processor being configured to invoke and run the computer program stored in the memory to execute the method of any one of claims 1-11.

42. A network device comprising: a processor and a memory, the memory being configured to store a computer program, and the processor being configured to invoke and run the computer program stored in the memory to execute the method of any one of claims 12-20.

43. A chip, comprising: a processor, configured to invoke and run a computer program from a memory, so that a device in which the chip is installed executes the method of any one of claims 1-20.

44. A computer readable storage medium for storing a computer program, wherein, The computer program causes a computer to perform the method of any one of claims 1 to 20.

45. A computer program product comprising computer program instructions, The computer program instructions cause a computer to perform the method of any one of claims 1 to 20.

Images