Terminal support information reporting method, acquisition method and device

By employing an index identifier to map assistance information with destination addresses, the method addresses signaling inefficiencies in sidelink communication, improving efficiency and power management in terminal devices.

JP7766817B2Active Publication Date: 2025-11-10BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024547715
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-02-14
Publication Date
2025-11-10
Estimated Expiration
2042-02-14

AI Technical Summary

Technical Problem

The existing sidelink communication method in terminal devices faces a challenge in signaling overhead due to the inability to extend the sidelink transmission resource request information list to include support information such as paging identifiers and SL DRX configurations, leading to inefficiencies in direct communication between terminal devices.

Method used

A method that uses an index identifier to establish a mapping relationship between assistance information and destination addresses in the sidelink resource request information list, allowing the network side device to identify the applicable terminal device without increasing signaling overhead.

Benefits of technology

This approach reduces signaling overhead by using an index identifier to indicate support information like paging identifiers and SL DRX configurations, enhancing communication efficiency and power management in terminal devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007766817000007
    Figure 0007766817000007
  • Figure 0007766817000008
    Figure 0007766817000008
  • Figure 0007766817000009
    Figure 0007766817000009
Patent Text Reader

Abstract

The present embodiment discloses a terminal assistance information reporting method, an acquisition method and an apparatus thereof, which are applicable to systems such as car networks and V2X, and the method includes a step of a first terminal device sending a sidelink (SL) resource request information list and an assistance information list to a network side device, where the resource request information list includes a plurality of resource requests of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information of the second terminal device, and the assistance information includes determining a terminal device identifier corresponding to the assistance information by an index identifier, and the terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list (301). By implementing the embodiment of the present application, an indication of the second terminal device to which the assistance information is applied can be realized by an existing destination address field in the sidelink (SL) resource request information list, and the signaling overhead of reporting the assistance information can be saved.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present application relates to the field of communication technology, and in particular to a terminal support information reporting method, an acquisition method and an apparatus therefor. [Background technology]

[0002] To support direct communication between terminal devices, a sidelink (also called SL) communication method is introduced, and the interface between terminal devices is a PC-5 (sidelink communication) interface. According to the correspondence between the transmitting terminal device and the receiving terminal device, the sidelink supports three transmission methods: unicast, multicast, and broadcast. When a first terminal device in a connected state communicates via the sidelink, it needs to send a SidelinkUEInformation (sidelink communication terminal information) message containing a sidelink transmission resource request information list to a network side device (e.g., a base station).

[0003] In the related art, when a first terminal device reports a sidelink transmission resource request information list to a network-side device, the destination address field in the transmission resource request in the sidelink transmission resource request information list is used to indicate the identifier of a second terminal device connected via unicast. However, since the signaling of the sidelink transmission resource request information list cannot currently be extended, it is not possible to add fields to the sidelink transmission resource request information list for indicating support information such as a paging identifier, sidelink discontinuous reception (SL DRX) support information, and SL DRX configuration. Adding the destination address (also referred to as an identifier) ​​of the second terminal device to the support information such as a paging identifier, SL DRX support information, and SL DRX configuration reported by the first terminal device would result in a large increase in signaling overhead. Therefore, how to indicate support information such as a paging identifier, SL DRX support information, and SL DRX configuration to achieve the goal of reducing signaling overhead is an issue that needs to be addressed urgently. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present application provide a terminal assistance information reporting method, an acquisition method and an apparatus therefor, which can save signaling overhead for reporting assistance information. [Means for solving the problem]

[0005] According to a first aspect, an embodiment of the present application provides a terminal assistance information reporting method, the method being performed by a first terminal device, the method comprising: a step of transmitting a side link (SL) resource request information list and an assistance information list to a network side device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, the assistance information list includes assistance information, and the assistance information includes an index identifier to determine an terminal device identifier corresponding to the assistance information; Here, the terminal device identifier corresponding to the assistance information is the destination address in the resource request located at the index identifier position in the resource request information list.

[0006] In this technical solution, a mapping relationship is established between the assistance information and the destination address of the second terminal device in the resource request information list by using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0007] In one implementation, the index identifier is carried in the aiding information.

[0008] In one possible implementation, the method further comprises setting the index identifier based on an index position in the resource request information list of a resource request corresponding to a destination address of a second terminal device.

[0009] In one implementation, the index identifier is determined by the position of the aiding information in the aiding information list.

[0010] In one possible implementation, the method further includes a step of setting support information to the same index position in the support information list based on an index position in the resource request information list of a resource request corresponding to a destination address of a second terminal device, wherein the support information list has the same length as the resource request information list.

[0011] In one implementation, the assistance information includes a paging identifier of a second terminal device, where the second terminal device is a remote terminal device.

[0012] In one implementation, the assistance information includes a sidelink discontinuous reception (SL DRX) configuration, where the sidelink discontinuous reception (SL DRX) configuration is a SL DRX configuration received by the first terminal device and transmitted from a second terminal device, and the first terminal device accepts the SL DRX configuration.

[0013] In one implementation, the support information includes received SL DRX support information, where the SL DRX support information is SL DRX support information transmitted from a second terminal device and received by the first terminal device.

[0014] According to a second aspect, an embodiment of the present application provides a terminal assistance information acquisition method, the method being performed by a network side device, the method comprising: receiving a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device, where the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information, and the assistance information includes a step of determining a terminal device identifier corresponding to the assistance information by an index identifier; Here, the terminal device identifier corresponding to the assistance information is the destination address in the resource request located at the index identifier position in the resource request information list.

[0015] In one implementation, the assistance information carries an index identifier for searching the resource request information list.

[0016] In one implementation, the index identifier is determined by the position of the aiding information in the aiding information list.

[0017] In one implementation, the method further includes a step of determining a destination address in a resource request located at the index identifier position in the resource request information list based on an index identifier in the received assistance information list, wherein the assistance information corresponding to the index identifier is applied to a second terminal device corresponding to the destination address.

[0018] In one implementation, the assistance information is a paging identifier, and the method further includes reporting by sending a paging message to the first terminal device, the destination address of which is the paging identifier.

[0019] In one implementation, the assistance information is a Sidelink Discontinuous Reception (SL DRX) configuration, and the method comprises: The method further includes scheduling sidelink transmission resources to a second terminal device corresponding to the destination address within an activation time of the second terminal device corresponding to the destination address.

[0020] In one implementation, the assistance information is SL DRX assistance information, the SL DRX assistance information comprising an advised SL DRX configuration, and the method further comprises: The method further includes determining, based on the SL DRX support information, an SL DRX configuration of the second terminal device corresponding to the destination address.

[0021] According to a third aspect, an embodiment of the present application provides a communication device, comprising: A transceiver module for transmitting a side link (SL) resource request information list and an assistance information list to a network side device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, the assistance information list includes assistance information, and the assistance information includes a transceiver module for determining a terminal device identifier corresponding to the assistance information by an index identifier; Here, the terminal device identifier corresponding to the assistance information is the destination address in the resource request located at the index identifier position in the resource request information list.

[0022] In one implementation, the index identifier is included in the aiding information.

[0023] In one implementation, the communication apparatus further includes a processing module for setting the index identifier based on an index position in the resource request information list of a resource request corresponding to a destination address of a second terminal device.

[0024] In one implementation, the index identifier is determined by the position of the aiding information in the aiding information list.

[0025] In one implementation, the communication device comprises: and further including a processing module for setting support information to the same index position in the support information list based on an index position in the resource request information list of a resource request corresponding to a destination address of a second terminal device, wherein the support information list has the same length as the resource request information list.

[0026] In one implementation, the assistance information includes a paging identifier of a second terminal device, where the second terminal device is a remote terminal device.

[0027] In one implementation, the assistance information includes a sidelink discontinuous reception (SL DRX) configuration, wherein the sidelink discontinuous reception (SL DRX) configuration is a SL DRX configuration received by the first terminal device and transmitted from a second terminal device, and the first terminal device accepts the SL DRX configuration.

[0028] In one implementation, the support information includes received SL DRX support information, where the SL DRX support information is SL DRX support information transmitted from a second terminal device and received by the first terminal device.

[0029] According to a fourth aspect, an embodiment of the present application provides another communication device, A transceiver module for receiving a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information, and the assistance information includes an index identifier, the transceiver module determining an terminal device identifier corresponding to the assistance information; Here, the terminal device identifier corresponding to the assistance information is the destination address in the resource request located at the index identifier position in the resource request information list.

[0030] In one implementation, the assistance information includes an index identifier for searching the resource request information list.

[0031] In one implementation, the index identifier is determined by the position of the aiding information in the aiding information list.

[0032] In one possible implementation, the communication device comprises: and further including a processing module for determining, based on an index identifier in the received assistance information list, a destination address in a resource request located at the index identifier position in the resource request information list, wherein the assistance information corresponding to the index identifier is applied to a second terminal device corresponding to the destination address.

[0033] In one implementation, the assistance information is a paging identifier, and the transceiver module further reports by sending a paging message to the first terminal device, the destination address of which is the paging identifier.

[0034] In one implementation, the assistance information is a sidelink discontinuous reception (SL DRX) configuration, and the transceiver module further schedules sidelink transmission resources to a second terminal device corresponding to the destination address within an activation time of the second terminal device corresponding to the destination address.

[0035] In one implementation, the support information is SL DRX support information, and the SL DRX support information includes an advised SL DRX configuration, and the processing module further determines an SL DRX configuration of a second terminal device corresponding to the destination address based on the SL DRX support information.

[0036] According to a fifth aspect, an embodiment of the present application provides another terminal assistance information reporting method, the method being performed by a first terminal device, the method comprising: The method includes a step of transmitting a sidelink (SL) resource request information list and an assistance information list to a network side device, wherein the resource request information list includes a plurality of resource requests, each corresponding to an index position, and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, wherein the index identifier corresponds to the index position corresponding to the resource request.

[0037] In this technical solution, a mapping relationship is established between the assistance information and the destination address of the second terminal device in the resource request information list by using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0038] In one implementation, the index identifier is carried in the corresponding aiding information.

[0039] In one possible implementation, the method further includes a step of determining an index position of the resource request in the resource request information list, and a step of setting an index identifier corresponding to the support information in the support information list based on the index position.

[0040] In one possible implementation, the support information list is of the same length as the resource request information list, and the index position of the resource request in the resource request information list is the same as the index position of the support information in the support information list.

[0041] In an alternative implementation, the method further comprises determining the aiding information.

[0042] In one alternative implementation, the support information comprises: one of a paging identifier transmitted from the second terminal device, sidelink discontinuous reception (SL DRX) configuration information transmitted from the second terminal device, and SL DRX assistance information transmitted from the second terminal device, where the SL DRX assistance information includes advised SL DRX configuration information.

[0043] According to a sixth aspect, an embodiment of the present application provides another terminal assistance information acquisition method, the method being performed by a network side device, the method comprising: receiving a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device, where the resource request information list includes a plurality of resource requests, each corresponding to an index position; and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, where the index identifier corresponds to an index position corresponding to the resource request; determining the resource requirements based on the index identifier; obtaining a destination address in the resource request, where the terminal device having the destination address is the second terminal device.

[0044] In this technical solution, a mapping relationship is established between the assistance information and the destination address of the second terminal device in the resource request information list by using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0045] In one implementation, the index identifier is included in the corresponding aiding information.

[0046] In one possible implementation, the support information list is of the same length as the resource request information list, and the index position of the resource request in the resource request information list is the same as the index position of the support information in the support information list.

[0047] In one possible implementation, the assistance information is a paging identifier, and the method further includes determining a paging message for the paging identifier and transmitting the paging message to the second terminal device via the first terminal device.

[0048] In an alternative implementation, the assistance information is sidelink discontinuous reception (SL DRX) configuration information, and the method further comprises scheduling sidelink transmission resources to the second terminal device based on the SL DRX configuration information within an activation time of the second terminal device.

[0049] In an alternative implementation form, the support information is SL DRX support information, and the SL DRX support information includes advised SL DRX configuration information, and the method further includes a step of determining SL DRX configuration information of the second terminal device based on the SL DRX support information.

[0050] According to a seventh aspect, an embodiment of the present application provides a communication device that implements some or all of the functions of the terminal device in the method according to the first aspect. For example, the functions of the communication device may include some or all of the functions of the embodiments of the present application, or may include a function that independently implements any of the embodiments of the present application. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software may include one or more units or modules corresponding to the above functions.

[0051] In one implementation, the configuration of a communication device may include a transceiver module and a processing module configured to support the communication device in performing corresponding functions in the above-described methods. The transceiver module is used to support communication between the communication device and other devices. The communication device may further include a storage module coupled to the transceiver module and the processing module for storing computer programs and data required by the communication device.

[0052] As an example, the processing module may be a processor, the transmitting and receiving module may be a transceiver or a communication interface, and the storage module may be a memory.

[0053] According to an eighth aspect, an embodiment of the present application provides a communication device that implements part or all of the functions of the network device in the method according to the second aspect. For example, the functions of the communication device may include part or all of the functions of the embodiments of the present application, or may include a function that independently implements any of the embodiments of the present application. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0054] In one implementation, the configuration of a communication device may include a transceiver module and a processing module configured to support the communication device in performing corresponding functions in the above-described methods. The transceiver module is used to support communication between the communication device and other devices. The communication device may further include a storage module coupled to the transceiver module and the processing module for storing computer programs and data required by the communication device.

[0055] As an example, the processing module may be a processor, the transmitting and receiving module may be a transceiver or a communication interface, and the storage module may be a memory.

[0056] According to a ninth aspect, an embodiment of the present application provides a communication device, the communication device including a processor, the processor executing the method according to the first aspect when calling a computer program in a memory.

[0057] According to a tenth aspect, an embodiment of the present application provides a communication device, the communication device including a processor, the processor executing the method according to the second aspect when calling a computer program in a memory.

[0058] According to an eleventh aspect, an embodiment of the present application provides a communication device, the communication device including a processor, the processor executing the method according to the fifth aspect when calling a computer program in a memory.

[0059] According to a twelfth aspect, an embodiment of the present application provides a communication device, the communication device including a processor, the processor executing the method according to the sixth aspect when calling a computer program in a memory.

[0060] According to a thirteenth aspect, an embodiment of the present application provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method according to the first aspect.

[0061] According to a fourteenth aspect, an embodiment of the present application provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method according to the second aspect.

[0062] According to a fifteenth aspect, an embodiment of the present application provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method according to the fifth aspect.

[0063] According to a sixteenth aspect, an embodiment of the present application provides a communication device, the communication device including a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the communication device to perform the method according to the sixth aspect.

[0064] According to a seventeenth aspect, an embodiment of the present application provides a communication device, the device including a processor and an interface circuit, the interface circuit receiving and transmitting code instructions to the processor, and the processor executing the code instructions to cause the device to perform the method according to the first aspect.

[0065] According to an eighteenth aspect, an embodiment of the present application provides a communication device, the device including a processor and an interface circuit, the interface circuit receiving and transmitting code instructions to the processor, and the processor executing the code instructions to cause the device to perform the method according to the second aspect.

[0066] According to a nineteenth aspect, an embodiment of the present application provides a communication device, the device including a processor and an interface circuit, the interface circuit receiving and transmitting code instructions to the processor, and the processor executing the code instructions, thereby causing the device to perform the method according to the fifth aspect.

[0067] According to a twentieth aspect, an embodiment of the present application provides a communication device, the device including a processor and an interface circuit, the interface circuit receiving and transmitting code instructions to the processor, and the processor executing the code instructions, thereby causing the device to perform the method according to the sixth aspect.

[0068] According to a 21st aspect, an embodiment of the present application provides a communication system, the system comprising a communication device according to the 3rd aspect and a communication device according to the 4th aspect, or the system comprising a communication device according to the 7th aspect and a communication device according to the 8th aspect, or the system comprising a communication device according to the 9th aspect and a communication device according to the 10th aspect, or the system comprising a communication device according to the 11th aspect and a communication device according to the 12th aspect, or the system comprising a communication device according to the 13th aspect and a communication device according to the 14th aspect, or the system comprising a communication device according to the 15th aspect and a communication device according to the 16th aspect, or the system comprising a communication device according to the 17th aspect and a communication device according to the 18th aspect, or the system comprising a communication device according to the 19th aspect and a communication device according to the 20th aspect.

[0069] According to a twenty-second aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for use by the terminal device, the instructions, when executed, causing the terminal device to perform the method of the first aspect.

[0070] According to a twenty-third aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for use by the terminal device, the instructions, when executed, causing the terminal device to perform the method according to the second aspect.

[0071] According to a 24th aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for use by the terminal device, the instructions, when executed, causing the terminal device to perform the method of the 5th aspect.

[0072] According to a twenty-fifth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for use by the terminal device, the instructions, when executed, causing the terminal device to perform the method according to the sixth aspect.

[0073] According to a twenty-sixth aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the first aspect above.

[0074] According to a twenty-seventh aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the second aspect above.

[0075] According to a twenty-eighth aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the fifth aspect above.

[0076] According to a twenty-ninth aspect, the present application further provides a computer program product comprising a computer program which, when executed on a computer, causes the computer to perform the method according to the sixth aspect above.

[0077] According to a thirtieth aspect, the present application provides a computer program which, when executed on a computer, causes the computer to carry out the method according to the first aspect above.

[0078] According to a thirty-first aspect, the present application provides a computer program which, when executed on a computer, causes the computer to carry out the method according to the second aspect above.

[0079] According to a thirty-second aspect, the present application provides a computer program which, when run on a computer, causes the computer to carry out the method according to the fifth aspect above.

[0080] According to a thirty-third aspect, the present application provides a computer program which, when run on a computer, causes the computer to carry out the method according to the sixth aspect above. [Brief explanation of the drawings]

[0081] In order to more clearly describe the technical solutions in the embodiments or background art of the present application, the following describes the drawings that need to be used in the embodiments or background art of the present application. [Figure 1] FIG. 1 is a schematic diagram of sidelink communication terminal information provided by an embodiment of the present application; [Figure 2] 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application; [Figure 3] 2 is a schematic flowchart of a terminal support information reporting method provided by an embodiment of the present application; [Figure 4] 4 is a schematic flowchart of another terminal support information reporting method provided by an embodiment of the present application; [Figure 5] 4 is a schematic flowchart of a further terminal support information reporting method provided by an embodiment of the present application; [Figure 6] 4 is a schematic flowchart of a further terminal support information reporting method provided by an embodiment of the present application; [Figure 7] 4 is a schematic flowchart of another terminal support information reporting method provided by an embodiment of the present application; [Figure 8] 1 is a schematic flowchart of a method for obtaining terminal support information provided by an embodiment of the present application; [Figure 9] 4 is a schematic flowchart of another terminal support information acquisition method provided by an embodiment of the present application; [Figure 10] 1 is a schematic configuration diagram of a communication device provided by an embodiment of the present application; [Figure 11] FIG. 1 is a schematic diagram of another communication device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0082] The following detailed description of the embodiments of the present application is provided in the accompanying drawings, in which the same or similar reference numerals throughout the drawings denote the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are illustrative and are intended to explain the present application and should not be construed as limiting the present application. In the description of the present application, unless otherwise specified, " / " means "or." For example, A / B can represent A or B. The "and / or" in the text simply describes the relationship between related objects and indicates that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0083] The terms used in the examples are for the purpose of describing particular examples and are not intended to limit the examples. Unless the context clearly dictates otherwise, the singular forms "a," "an," and "the" used in the examples and the appended claims also include the plural forms.

[0084] It should be understood that, although various pieces of information may be described using terms such as first, second, and third in the embodiments of the present application, these pieces of information should not be limited to these terms. These terms are used only to distinguish between pieces of information of the same type. For example, first information can be referred to as second information, and similarly, second information can be referred to as first information, without departing from the scope of the embodiments of the present application. Depending on the context, the term "when" used herein can be interpreted as "when," "when," or "responsive to determining."

[0085] The following detailed description of the embodiments of the present application is given, and examples of the embodiments are shown in the drawings, in which the same or similar reference numerals throughout indicate the same or similar elements. The embodiments described below with reference to the accompanying drawings are illustrative and are intended to explain the present application, but cannot be understood as limiting the present application.

[0086] In order to support direct communication between terminal devices, the sidelink (also called SL) communication method has been introduced, and the interface between terminal devices is the PC-5 (sidelink communication) interface. Depending on the correspondence between the transmitting terminal device and the receiving terminal device, sidelink supports three transmission methods: unicast, multicast, and broadcast.

[0087] When a first terminal device in a connected state communicates on the sidelink, it needs to send a SidelinkUEInformation message (sidelink communication terminal information) containing a sidelink (SL) transmission resource request information list to a network side device (e.g., a base station). Here, as shown in Figure 1, each element in the sidelink (SL) resource request information list is a sidelink (SL) resource request of a second terminal device, and the resource request includes the destination address of the second terminal device, the corresponding transmission method (including unicast, multicast, and broadcast), the quality of service (QoS), and the target transmission frequency.

[0088] At present, one terminal device is not directly connected to a base station, but can communicate with the base station through the relay of another terminal device. Here, the terminal device that is not connected to the base station is called a remote terminal device (remote UE), and the terminal device that provides the relay function is called a relay terminal device (relay UE). Unicast communication is performed between the remote terminal device and the relay terminal device via sidelink.

[0089] It should be understood that a paging message sent by a network side device to a second terminal device (e.g., a remote terminal device) is sent to a first terminal device (e.g., an intermediate terminal device) by dedicated signaling, and then forwarded to the second terminal device by the first terminal device. The first terminal device needs to report the paging identifier of the second terminal device to the network side device, and the paging identifier may be NG-5G-S-TMSI or I-RNTI.

[0090] To reduce the power consumption of terminal devices when performing sidelink communication, sidelink discontinuous reception (DRX) is introduced. The receiving terminal device monitors the physical sidelink control channel (PSCCH) only during the activation time, thereby achieving the purpose of energy saving.

[0091] Unicast sidelink discontinuous reception (SL DRX) setting information is transmitted by the transmitting terminal device to the receiving terminal device, and the receiving terminal device can transmit SL DRX assistance information including the advised SL DRX setting information to the transmitting terminal device. When the receiving terminal device is in a connected state, it reports the received SL DRX setting information to the base station. The base station can achieve power saving by adjusting Uu (cellular network communication interface) DRX so that SL DRX and Uu DRX overlap as much as possible. When the transmitting terminal device is in a connected state, it reports the received SL DRX assistance information to the base station. The base station determines the SL DRX setting based on this SL DRX assistance information.

[0092] In the related art, as shown in FIG. 1, when a first terminal device reports a sidelink resource request information list to a network-side device, the destination address field in the resource request in the sidelink resource request information list is used to indicate the identifier of a second terminal device connected via unicast. However, since the signaling of the sidelink resource request information list cannot currently be extended, it is not possible to add fields to the sidelink resource request information list for indicating assistance information such as a paging identifier, sidelink discontinuous reception (SL DRX) support information, and SL DRX configuration. Adding the destination address (also referred to as an identifier) ​​of the second terminal device to the assistance information such as a paging identifier, SL DRX support information, and SL DRX configuration reported by the first terminal device would result in a large increase in signaling overhead. Therefore, how to indicate assistance information such as a paging identifier, SL DRX support information, and SL DRX configuration to achieve the goal of reducing signaling overhead is an issue that needs to be addressed urgently.

[0093] Based on the above problems, this application proposes a terminal assistance information reporting method, an acquisition method and an apparatus therefor, which can realize the indication of the second terminal device to which the assistance information applies by using the existing destination address field in the sidelink (SL) resource request information list, and can save the signaling overhead of reporting the assistance information.

[0094] 2 is a schematic diagram of a communication system architecture provided by an embodiment of the present application. This communication system may include, but is not limited to, one network device and two terminal devices. The number and configuration of devices shown in FIG. 2 are merely exemplary and do not constitute limitations on the embodiment of the present application. In actual applications, the communication system may include two or more network devices and two or more terminal devices. Take the communication system shown in FIG. 2 as an example, including one network device 201 and two terminal devices 202. Here, the terminal device 202 is a sidelink terminal device.

[0095] It should be noted that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a long term evolution (LTE) system, a fifth generation (5G) mobile communication system, a 5G new radio (NR) system, or other future new mobile communication systems. It should be noted that the sidelink in the embodiments of the present application may also be referred to as a direct connection link or a direct link.

[0096] The network device 201 in the embodiments of the present application is a network-side entity for transmitting and receiving signals. For example, the network device 201 may be an evolved base station (eNB), a transmission reception point (TRP), a next generation base station (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present application do not limit the specific technology and device configuration adopted by the network device. The network device provided in the embodiments of the present application may be composed of a central unit (CU) and distributed units (DUs), where the CU is also called a control unit. A CU-DU structure is adopted to separate the protocol layers of a network device, for example, a base station, so that some protocol layer functions are centrally controlled by the CU and some or all of the remaining protocol layer functions are distributed to the DUs, and the DUs are centrally controlled by the CU.

[0097] In the present embodiment, the terminal device 202 is a user-side entity for receiving or transmitting signals, such as a mobile phone. The terminal device may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet, a PC with wireless transmission and reception capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device for industrial control, a wireless terminal device for self-driving, a wireless terminal device for remote medical surgery, a wireless terminal device for smart grids, a wireless terminal device for transportation safety, a wireless terminal device for smart cities, a wireless terminal device for smart homes, etc. The present embodiment does not limit the specific technology and device configuration adopted by the terminal device.

[0098] There are four types of sidelink transmission modes for sidelink communication. Sidelink transmission mode 1 and sidelink transmission mode 2 are used for device-to-device (D2D) communication. Sidelink transmission mode 3 and sidelink transmission mode 4 are used for V2X communication. When sidelink transmission mode 3 is adopted, resource allocation is scheduled by the network device 201. Specifically, the network device 201 transmits resource allocation information to the terminal device 202, and the terminal device 202 can allocate resources to other terminal devices so that the other terminal devices can transmit information to the network device 201 through the allocated resources. In V2X communication, the terminal device 202 can be a terminal device with good or reliable signals.

[0099] It should be noted that the communication system described in the embodiments of the present application is intended to more clearly explain the technical solutions of the embodiments of the present application and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art will understand that with the evolution of system architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application will be similarly applicable to similar problems.

[0100] Hereinafter, the terminal support information reporting method, the terminal support information obtaining method and the terminal support information obtaining device will be described in detail in conjunction with the drawings.

[0101] Referring to Figure 3, Figure 3 is a schematic flowchart of a terminal support information reporting method provided by an embodiment of the present application. Note that the terminal support information reporting method of the embodiment of the present application can be performed by a first terminal device. As shown in Figure 3, the terminal support information reporting method can include, but is not limited to, the following steps:

[0102] In step 301, send a side link (SL) resource request information list and an assistance information list to a network side device, where the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, the assistance information list includes assistance information, and the assistance information determines a terminal device identifier corresponding to the assistance information through an index identifier, where the terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list.

[0103] In some embodiments of the present application, the assistance information in this reported assistance information list may be a paging identifier, or may be sidelink discontinuous reception (SL DRX) assistance information, or may be SL DRX configuration, etc.

[0104] In one implementation, the length of the assistance information list may be 1. That is, the first terminal device may report an assistance information list to the network side device, and the assistance information list may include one or more pieces of assistance information, where each piece of assistance information in the assistance information list may determine a UE identifier to which the assistance information applies by an index identifier, and the UE identifier may be a destination address in a resource request located at an index identifier position in the resource request information list.

[0105] In addition, when a first terminal device in a connected state communicates via sidelink, it needs to transmit a SidelinkUEInformation message containing a sidelink (SL) transmission resource request information list to a network side device (e.g., a base station). Each element in the resource request information list is a resource request of a second terminal device, and the resource request includes the destination address of the second terminal device, a corresponding transmission method (including unicast, multicast, and broadcast), a quality of service (QoS), and a target transmission frequency. In an embodiment of the present application, when the first terminal device reports assistance information to the network side device, a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list is established using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information transmitted from the first terminal device applies based on this mapping relationship. This allows the existing destination address field in the resource request information list to indicate the second terminal device to which the assistance information applies.

[0106] It should be noted that in some embodiments of the present application, there are various ways to set this index identifier, for example, it may be included in the corresponding assistance information, or the index identifier corresponding to the assistance information may be set according to the index position in the resource request information list of the resource request. Below, examples are given to respectively describe different ways to set the index identifier, and how to establish a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list using the index identifier.

[0107] As an example of one possible implementation, assume that the resource request information list (eg, SL-TxResourceReqList-r16) reported from the first terminal device has four elements, as shown in Table 1 below.

[0108] [Table 1]

[0109] Assuming that the assistance information that the first terminal device needs to report is SL DRX configuration information, the reported SL DRX configuration information may be, for example, that for a second terminal device whose destination address (also referred to as identifier) ​​is 00000001, its SL DRX configuration information is A, and that for a second terminal device whose destination address (also referred to as identifier) ​​is 00000011, its SL DRX configuration information is B. Because the setting methods of the index identifiers are different, the formats of the assistance information lists reported by the first terminal device to the network side device are also different.

[0110] In one implementation, the index identifier is included in the corresponding assistance information. In such a case, the index identifier can be set based on the index position in the resource request information list of the transmission resource request corresponding to the destination address of the first terminal device or the second terminal device. In such an implementation, the assistance information list reported by the first terminal device to the network side device can be, for example, as shown in Table 2.

[0111] [Table 2]

[0112] Here, from Tables 1 and 2, the SL-DestinationIdentity-r16 of a UE whose SL DRX configuration in the reported support information list is A is the SL-DestinationIdentity-r16 of the second (index identifier) ​​entry in the resource request information list (e.g., SL-TxResourceReqList-r16), i.e., 00000001. In this way, the SL-DestinationIdentity-r16 of a UE whose SL DRX configuration in the reported support information list is B is the SL-DestinationIdentity-r16 of the fourth (index identifier) ​​entry in the resource request information list (e.g., SL-TxResourceReqList-r16), i.e., 00000011.

[0113] In another implementation, the index identifier in the embodiment of the present application is determined by the position of the assistance information in the assistance information list. In this case, the first terminal device needs to set the assistance information to the same index position in the assistance information list based on the index position in the resource request information list of the resource request corresponding to the destination address of the second terminal device, where the assistance information list has the same length as the resource request information list. If there is no assistance information for a certain target UE, it should be empty but the entry should be retained. In this implementation, the assistance information list reported by the first terminal device to the network side device can be, for example, as shown in Table 3 below.

[0114] [Table 3]

[0115] Here, if the SL DRX configuration in Table 3 is A, first determine that the index identifier of A is the second, which is its index position in the support information list, and then obtain the UE identifier of A by the index identifier, i.e., the SL-DestinationIdentity-r16 of the UE whose SL DRX configuration in the reported support information list is A is the SL-DestinationIdentity-r16 of the second (index identifier) ​​entry in the resource request information list (e.g., SL-TxResourceReqList-r16), i.e., 00000001.

[0116] In this way, if the SL DRX configuration in Table 3 is B, first determine that the index identifier of B is the fourth, which is its index position in the support information list, and then obtain the UE identifier of B by the index identifier, i.e., the SL-DestinationIdentity-r16 of the UE whose SL DRX configuration in the reported support information list is B is the SL-DestinationIdentity-r16 of the fourth (index identifier) ​​entry in the resource request information list (e.g., SL-TxResourceReqList-r16), i.e., 00000011.

[0117] In some embodiments of the present application, the assistance information in this reported assistance information list may be a paging identifier, or may be sidelink discontinuous reception (SL DRX) assistance information, or may be SL DRX configuration, etc. In one implementation, this assistance information may include a paging identifier of a second terminal device, where this second terminal device is a remote terminal device.

[0118] That is, when the first terminal device is a relay UE, the assistance information in the reported assistance information list may include a paging identifier of the second terminal device. For example, when the first terminal device is a relay UE, the relay UE needs to report the paging identifier of the second terminal device (e.g., a remote UE) to the network side device, so that the network side device can send a paging message sent to this second terminal device to this relay UE and forward this paging message to the second terminal device by the relay UE.

[0119] In one implementation, the assistance information may include a sidelink discontinuous reception (SL DRX) configuration, where the sidelink discontinuous reception (SL DRX) configuration is a SL DRX configuration received by the first terminal device and transmitted from the second terminal device, and the first terminal device accepts the SL DRX configuration.

[0120] That is, when a first terminal device receives an SL DRX configuration sent from a second terminal device, and the first terminal device accepts this SL DRX configuration, the support information in the support information list reported by this first terminal device may include this SL DRX configuration.

[0121] In one implementation, the assistance information may include received SL DRX assistance information, where the SL DRX assistance information is SL DRX assistance information received by the first terminal device and transmitted from the second terminal device.

[0122] That is, when a first terminal device receives SL DRX assistance information transmitted from a second terminal device, the assistance information in the assistance information list reported by this first terminal device may include this received SL DRX assistance information.

[0123] By implementing the embodiment of the present application, when reporting the terminal assistance information, an index identifier can be used to determine the identifier of the terminal device UE to which the terminal assistance information applies, and the identifier of this terminal device UE is the destination address in the transmission resource request located at the index identifier position in the resource request information list. Thus, the embodiment of the present application uses the index identifier to establish a mapping relationship between the assistance information and the destination address of the opposite terminal device UE in the resource request information list, thereby realizing instructions to the opposite terminal device when reporting the terminal assistance information and saving signaling overhead for reporting the terminal assistance information.

[0124] 4, which is a schematic flowchart of a terminal support information reporting method provided by an embodiment of the present application. The terminal support information reporting method of the embodiment of the present application can be performed by a first terminal device. As shown in FIG. 4, the terminal support information reporting method can include, but is not limited to, the following steps:

[0125] In step 401, a sidelink (SL) resource request information list and an assistance information list are sent to a network side device, where the resource request information list includes multiple resource requests, and one resource request corresponds to one index position, and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, where the index identifier corresponds to the index position corresponding to the resource request.

[0126] In some embodiments of the present application, the assistance information in this assistance information list may be a paging identifier, or may be sidelink discontinuous reception (SL DRX) assistance information, or may be SL DRX configuration, etc.

[0127] In one implementation, the length of the assistance information list may be 1. That is, in addition to transmitting the sidelink (SL) resource request information list to the network side device, the first terminal device may also transmit an assistance information list to the network side device, where the assistance information list may include assistance information of one or more second terminal devices and an index identifier corresponding to the assistance information, where the index identifier corresponds to the index position of the resource request in the resource request information list. Since the resource request includes the destination address of the second terminal device, after receiving the resource request information list and the assistance information list reported from the first terminal device, the network side device can use the existing destination address field in the resource request information list to indicate the second terminal device to which each piece of assistance information in the assistance information list applies, thereby saving signaling overhead for reporting the assistance information.

[0128] In addition, when a first terminal device in a connected state communicates via sidelink, it needs to transmit a SidelinkUEInformation (sidelink communication terminal information) message containing a sidelink (SL) transmission resource request information list to a network side device (e.g., a base station). Each element in this resource request information list is a resource request of a second terminal device, and this resource request includes the destination address of the second terminal device, a corresponding transmission method (including unicast, multicast, and broadcast), a quality of service (QoS), and a target transmission frequency. In an embodiment of the present application, when the first terminal device reports assistance information to the network side device, a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list is established using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information transmitted from the first terminal device applies based on this mapping relationship. This allows the existing destination address field in the resource request information list to indicate the second terminal device to which the assistance information applies.

[0129] It should be noted that in some embodiments of the present application, there are various ways to set this index identifier, for example, it may be included in the corresponding assistance information, or the index identifier corresponding to the assistance information may be set according to the index position in the resource request information list of the resource request. Below, examples are given to respectively describe different ways to set the index identifier, and how to establish a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list using the index identifier.

[0130] As an example of a possible implementation, assuming that the resource request information list (e.g., SL-TxResourceReqList-r16) reported from the first terminal device has four elements, for example, as shown in the above Table 1. Assuming that the assistance information that the first terminal device needs to report is SL DRX configuration information, the reported SL DRX configuration information may be, for example, that for a second terminal device whose destination address (also referred to as identifier) ​​is 00000001, its SL DRX configuration information is A, and that for a second terminal device whose destination address (also referred to as identifier) ​​is 00000011, its SL DRX configuration information is B. Since the setting methods of the index identifiers are different, the manner in which the first terminal device reports the assistance information list to the network side device also differs.

[0131] In one implementation, the index identifier is included in the corresponding assistance information. In this case, the first terminal device can determine an index position of the resource request in the resource request information list, and set an index identifier corresponding to the assistance information in the assistance information list based on the index position. After setting an index identifier corresponding to the assistance information in the assistance information list based on the index position, the first terminal device can send the set assistance information list and resource request information list to the network side device.

[0132] For example, the format of the assistance information list reported by the first terminal device to the network side device may be, for example, as shown in Table 2 above. Here, from Tables 1 and 2, the destination address of the second terminal device to which SL DRX setting information A in the reported assistance information list is applied is the destination address whose index position in the resource request information list (e.g., SL-TxResourceReqList-r16) is 2, i.e., 00000001. Thus, the destination address of the second terminal device to which SL DRX setting B in the reported assistance information list is applied is the destination address whose index position in the resource request information list (e.g., SL-TxResourceReqList-r16) is 4, i.e., 00000011. After receiving the resource request information list and the assistance information list sent by the first terminal device, the network side device can determine the resource request located at the index position in the resource request information list based on the index identifier corresponding to the assistance information in the assistance information list, and obtain the destination address in the resource request located at the index position, where the terminal device having the destination address is the second terminal device to which the assistance information is applied.

[0133] For example, assuming that the resource request information list transmitted from the first terminal device is, for example, as shown in Table 1 above, and the transmitted assistance information list is, for example, as shown in Table 2 above, the network side device can determine the resource request having the index position 2 in the resource request information list based on the index identifier "2" corresponding to the assistance information, and thereby know that the terminal device to which this assistance information (i.e., the SL DRX configuration information is A in Table 2 above) is applied is the second terminal device having the destination address "00000001". In this way, the network side device can determine the resource request having the index position 4 in the resource request information list based on the index identifier "4" corresponding to the assistance information, and thereby know that the terminal device to which this assistance information (i.e., the SL DRX configuration information is B in Table 2 above) is applied is the second terminal device having the destination address "00000011".

[0134] In another implementation, the support information list has the same length as the resource request information list, and the index position of the resource request in the resource request information list is the same as the index position of the support information in the support information list. Here, the index identifier corresponding to the support information may be the index position of the support information in the support information list. That is, the first terminal device needs to set the support information of the second terminal device to the same index position in the support information list based on the index position of the resource request of the second terminal device in the resource request information list. If a second terminal device does not have support information, the corresponding position in the support information list is empty.

[0135] For example, the format of the support information list reported by the first terminal device to the network side device may be as shown in Table 3 below.

[0136] [Table 4]

[0137] That is, it is assumed that the length of the assistance information list of the first terminal device set is the same as the length of the resource request information list, both of which are 4, and that the terminal device to which SL DRX setting information A is applied is the second terminal device having a destination address of 00000001, and the terminal device to which SL DRX setting information B is applied is the second terminal device having a destination address of 00000011. The first terminal device needs to set the SL DRX setting information A at an index position of 2 in the assistance information list based on the index position (e.g., 2) in the resource request information list of the resource request of the second terminal device. In this way, the first terminal device needs to set the SL DRX setting information B at an index position of 4 in the assistance information list based on the index position (e.g., 4) in the resource request information list of the resource request of the second terminal device. If another second terminal device does not have assistance information in the resource request information list, the corresponding position in the assistance information list is left empty, that is, the format of the assistance information list of this first terminal device set can be, for example, as shown in Table 3 above. The first terminal device sets the support information at the same index position in the support information list based on the index position of the resource request in the resource request information list, and then transmits the set support information list and resource request information list to the network side device.

[0138] In this example, after receiving the resource request information list and the assistance information list transmitted from the first terminal device, the network side device can determine a resource request located at an index position in the resource request information list based on an index identifier corresponding to the assistance information in the assistance information list, and obtain a destination address in the resource request located at the index position, where the terminal device having the destination address is the second terminal device to which the assistance information applies. For example, assuming that the resource request information list transmitted from the first terminal device is, for example, as shown in Table 1 above, and the transmitted assistance information list is, for example, as shown in Table 3 above, the network side device can determine the resource request located at index position 2 in the resource request information list based on the index identifier "2" corresponding to the assistance information (i.e., the position of the assistance information in the assistance information list), and thereby know that the terminal device to which this assistance information (i.e., the SL DRX configuration information is A in Table 3 above) applies is the second terminal device with destination address "00000001". In this way, the network side device can determine the resource request whose index position is 4 in the resource request information list based on the index identifier "4" corresponding to the assistance information, and thereby know that the terminal device to which this assistance information (i.e., the SL DRX setting information is B in Table 3 above) applies is the second terminal device having the destination address "00000011".

[0139] By implementing the embodiments of the present application, a mapping relationship is established between the assistance information and the destination address of the second terminal device in the resource request information list using an index identifier corresponding to the assistance information, so that the network side device identifies the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0140] In some embodiments of the present application, the assistance information in the reported assistance information list may be a paging identifier, or may be SL DRX assistance information, or may be SL DRX configuration information, etc. In addition, when the content of the assistance information reported by the first terminal device to the network side device is different, the roles played by the first terminal device and the second terminal device also differ. For example, when the assistance information transmitted by the first terminal device to the network side device is a paging identifier, the first terminal device is a relay terminal device, and the second terminal device is a remote terminal device. In addition, when the assistance information transmitted by the first terminal device to the network side device is SL DRX assistance information, the first terminal device is a transmitting terminal device, and the second terminal device is a receiving terminal device. In addition, when the assistance information transmitted by the first terminal device to the network side device is SL DRX configuration information, the first terminal device is a receiving terminal device, and the second terminal device is a transmitting terminal device. Each of these will be described in detail below based on the embodiments.

[0141] Referring to Figure 5, Figure 5 is a schematic flowchart of another terminal assistance information reporting method provided by an embodiment of the present application. Note that the terminal assistance information reporting method of the embodiment of the present application can be performed by a first terminal device. Here, the assistance information is a paging identifier. As shown in Figure 5, this terminal assistance information reporting method can include, but is not limited to, the following steps:

[0142] In step 501, a paging identifier sent from a second terminal device is received.

[0143] Optionally, in an embodiment of the present application, the first terminal device is a relay terminal device, and the second terminal device is a remote terminal device. When the second terminal device sends a paging request to the network side device, the second terminal device sends its own paging identifier to the first terminal device. The first terminal device can receive the paging identifier sent from the second terminal device and send the paging identifier to the network side device, so that the network side device can send a paging message of the paging identifier to the second terminal device via the first terminal device.

[0144] In step 502, a paging identifier is determined as aiding information for the second terminal device.

[0145] Optionally, when the first terminal device receives a paging identifier transmitted from a second terminal device, the first terminal device can determine the paging identifier as assistance information for the second terminal device. Since the first terminal device needs to report a resource request information list to the network side device to enable the network side device to configure the sidelink resources of the second terminal device in the list, the first terminal device can use the destination address of the second terminal device in the resource request information list to indicate which second terminal device the paging identifier applies to.

[0146] In one implementation form, after determining a paging identifier as the assistance information of the second terminal device, the first terminal device can determine an index position in the resource request information list of the sidelink resource request of the second terminal device, and set an index identifier corresponding to this paging identifier in the assistance information list based on this index position, thereby setting this paging identifier and its corresponding index identifier in the assistance information list.

[0147] For example, suppose that the resource request information list (e.g., SL-TxResourceReqList-r16) that the first terminal device needs to report has four elements, as shown in Table 1 above. Assume that the assistance information received by the first terminal device is a paging identifier C sent from a second terminal device having a destination address "00000001" and a paging identifier D sent from a second terminal device having a destination address "00000011". The first terminal device determines that the index position of the resource request of the second terminal device having the destination address "00000001" in the resource request information list is 2, and can set an index identifier corresponding to this paging identifier C in the assistance information list based on this index position, i.e., this index identifier is 2, and the form of this paging identifier C and the index identifier in the assistance information list can be, for example, as shown in Table 4 below. The first terminal device determines that the index position in the resource request information list of the resource request of the second terminal device having the destination address "00000011" is 4, and can set an index identifier corresponding to this paging identifier D in the aiding information list based on this index position, that is, this index identifier is 4, and the form of this paging identifier D and the index identifier in the aiding information list can be, for example, as shown in the following Table 4. The first terminal device sets this paging identifier C and its corresponding index identifier, paging identifier D and its corresponding index identifier in the aiding information list, and the form of this aiding information list can be, for example, as shown in Table 4.

[0148] [Table 5]

[0149] In another implementation form, after the first terminal device determines the paging identifier as the assistance information of the second terminal device, it can set the assistance information corresponding to the same index position in the assistance information list based on the index position in the resource request information list of the resource request, where the index identifier corresponding to the assistance information corresponds to the index position in the assistance information list of the assistance information, and the assistance information list has the same length as the resource request information list.

[0150] For example, assume that the sidelink (SL) resource request information list (e.g., SL-TxResourceReqList-r16) that the first terminal device needs to report has four elements, as shown in Table 1 above. Assume that the assistance information received by the first terminal device is a paging identifier C sent from a second terminal device having a destination address of "00000001" and a paging identifier D sent from a second terminal device having a destination address of "00000011". The first terminal device determines that the index position of the resource request of the second terminal device having the destination address of "00000001" in the resource request information list is 2, and based on this index position, the first terminal device can set this paging identifier C to the same index position in the assistance information list, for example, as shown in Table 5 below. The first terminal device determines that the index position in the resource request information list of the resource request of the second terminal device having the destination address "00000011" is 4, and based on this index position, can set this paging identifier D to the same index position in the support information list, for example, as shown in Table 5 below, set this paging identifier D to the position in the support information list whose index position is 4.

[0151] [Table 6]

[0152] In step 503, a side link (SL) resource request information list and a support information list are sent to a network side device.

[0153] Here, in an embodiment of the present application, the resource request information list includes multiple resource requests, where one resource request corresponds to one index position, and the support information list includes support information of the second terminal device and an index identifier corresponding to the support information, where the index identifier corresponds to the index position corresponding to the resource request.

[0154] That is, after receiving the paging identifier sent from the second terminal device, the first terminal device determines the paging identifier as the assistance information of the second terminal device, and establishes a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list by using an index identifier corresponding to the assistance information, so that the network side device identifies the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0155] Referring to Figure 6, Figure 6 is a schematic flowchart of a further terminal support information reporting method provided by an embodiment of the present application. Note that the terminal support information reporting method of the embodiment of the present application can be performed by a first terminal device. Here, the support information is SL DRX configuration information. As shown in Figure 6, the terminal support information reporting method can include, but is not limited to, the following steps:

[0156] In step 601, receive SL DRX configuration information sent from a second terminal device.

[0157] Optionally, in an embodiment of the present application, the first terminal device is a receiving terminal device, and the second terminal device is a transmitting terminal device. To save power, the network side device (e.g., a base station) can adjust the Uu DRX based on the SL DRX configuration information of the sidelink terminal device so that the SL DRX and Uu DRX overlap as much as possible. In this case, the first terminal device receives the SL DRX configuration information transmitted from the second terminal device, and the second terminal device decides whether to accept the SL DRX configuration information. If the first terminal device decides to accept the SL DRX configuration information, the first terminal device needs to report the SL DRX configuration information to the network side device, so that the network side device can adjust the Uu DRX so that the SL DRX and Uu DRX overlap as much as possible, thereby saving power.

[0158] In step 602, the SL DRX configuration information is determined as the assistance information of the second terminal device.

[0159] Optionally, when the first terminal device receives SL DRX configuration information transmitted from the second terminal device, the first terminal device can determine the SL DRX configuration information as assistance information for the second terminal device. Since the first terminal device needs to report a resource request information list to the network side device to enable the network side device to configure the sidelink resources of the second terminal device in the list, the first terminal device can use the destination address of the second terminal device in the resource request information list to indicate the terminal device of the SL DRX configuration information.

[0160] Here, the implementation method of setting the assistance information list when the assistance information is SL DRX configuration information is similar to the implementation method of setting the assistance information list when the assistance information is a paging identifier. In one implementation form, after determining the SL DRX configuration information as the assistance information of the second terminal device, the first terminal device determines an index position in the resource request information list for a sidelink resource request of the second terminal device, and sets an index identifier corresponding to the SL DRX configuration information in the assistance information list based on the index position, thereby being able to set the SL DRX configuration information and the corresponding index identifier in the assistance information list.

[0161] In another implementation form, after the first terminal device determines the SL DRX configuration information as the assistance information of the second terminal device, it can set the assistance information at the same index position in the assistance information list based on the index position in the resource request information list of the resource request, where the index identifier corresponding to the assistance information is the index position in the assistance information list of the assistance information, and the assistance information list has the same length as the resource request information list.

[0162] In step 603, a side link (SL) resource request information list and a support information list are sent to a network side device.

[0163] Here, in an embodiment of the present application, the resource request information list includes multiple resource requests, where one resource request corresponds to one index position, and the support information list includes support information of the second terminal device and an index identifier corresponding to the support information, where the index identifier corresponds to the index position corresponding to the resource request.

[0164] That is, after receiving the SL DRX setting information transmitted from the second terminal device, the first terminal device, if in a connected state, determines the SL DRX setting information as the assistance information of the second terminal device, and establishes a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list using an index identifier corresponding to the assistance information, so that the network-side device identifies the second terminal to which the assistance information transmitted from the first terminal device applies based on this mapping relationship. In this way, the existing destination address field in the resource request information list can be used to indicate the second terminal device to which the assistance information applies, and the signaling overhead of reporting the assistance information can be saved.

[0165] Referring to Figure 7, Figure 7 is a schematic flowchart of a further terminal support information reporting method provided by an embodiment of the present application. Note that the terminal support information reporting method of the embodiment of the present application can be performed by a first terminal device. Here, the support information is SL DRX support information. As shown in Figure 7, the terminal support information reporting method can include, but is not limited to, the following steps:

[0166] In step 701, receive SL DRX assistance information sent from a second terminal device, where the SL DRX assistance information includes advised SL DRX configuration information.

[0167] Optionally, in an embodiment of the present application, the first terminal device is a transmitting terminal device, and the second terminal device is a receiving terminal device. To save power, the network side device (e.g., a base station) can adjust the Uu DRX so that the SL DRX and the Uu DRX overlap as much as possible based on the SL DRX configuration information of the sidelink terminal device. Here, the SL DRX configuration information may be the SL DRX configuration information advised in the SL DRX assistance information transmitted from the receiving terminal device.

[0168] For example, a unicast SL DRX is sent by a transmitting terminal device (e.g., a first terminal device in an embodiment of the present application) to a receiving terminal device (e.g., a second terminal device in an embodiment of the present application), so that the receiving terminal device can send SL DRX assistance information to the transmitting terminal device, and this SL DRX assistance information includes advised SL DRX configuration information, so that when the transmitting terminal device is in a connected state, it reports the received SL DRX assistance information to a network side device (e.g., a base station), so that the network side device (e.g., a base station) determines the SL DRX configuration based on this SL DRX assistance information.

[0169] In step 702, the SL DRX assistance information is determined as the assistance information of the second terminal device.

[0170] Optionally, when the first terminal device receives SL DRX assistance information transmitted from the second terminal device, the first terminal device can determine the SL DRX assistance information as assistance information of the second terminal device. Since the first terminal device needs to report a resource request information list to the network side device to enable the network side device to configure the sidelink resources of the second terminal device in the list, the first terminal device can use the destination address of the second terminal device in the resource request information list to indicate the terminal device of the SL DRX assistance information.

[0171] Here, the implementation manner of setting the assistance information list when the assistance information is SL DRX assistance information is similar to the implementation manner of setting the assistance information list when the assistance information is a paging identifier. In one implementation form, after the first terminal device sets the SL DRX assistance information as the assistance information of the second terminal device, it determines an index position in the resource request information list of the sidelink resource request of the second terminal device, and sets an index identifier corresponding to the SL DRX assistance information in the assistance information list based on the index position, so that the SL DRX assistance information and the corresponding index identifier can be set in the assistance information list.

[0172] In another implementation form, after the first terminal device uses the SL DRX assistance information as the assistance information of the second terminal device, it can set the assistance information corresponding to the same index position in the assistance information list based on the index position in the resource request information list of the resource request, where the index identifier corresponding to the assistance information corresponds to the index position in the assistance information list of the assistance information, and the assistance information list has the same length as the resource request information list.

[0173] In step 703, a side link (SL) resource request information list and a support information list are sent to the network side device.

[0174] Here, in an embodiment of the present application, the resource request information list includes multiple resource requests, where one resource request corresponds to one index position, and the support information list includes support information of the second terminal device and an index identifier corresponding to the support information, where the index identifier corresponds to the index position corresponding to the resource request.

[0175] That is, after receiving the SL DRX assistance information sent from the second terminal device, the first terminal device, if in a connected state, determines the SL DRX assistance information as the assistance information of the second terminal device, and establishes a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list using an index identifier corresponding to the assistance information, so that the network side device identifies the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies using the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0176] It should be noted that the above embodiment describes the implementation of the terminal support information reporting method of the embodiment of the present application at the first terminal device side. The embodiment of the present application further proposes a terminal support information acquisition method, and the implementation of this terminal support information acquisition method at the network side device side will be described below. Referring to FIG. 8, FIG. 8 is a schematic flowchart of the terminal support information acquisition method provided by the embodiment of the present application. It should be noted that the terminal support information acquisition method of the embodiment of the present application can be performed by the network side device. As shown in FIG. 8, the terminal support information acquisition method may include, but is not limited to, the following steps:

[0177] In step 801, a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device are received, where the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information, and the assistance information determines a terminal device identifier corresponding to the assistance information through an index identifier, where the terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list.

[0178] In some embodiments of the present application, the assistance information in this reported assistance information list may be a paging identifier, or may be sidelink discontinuous reception (SL DRX) assistance information, or may be SL DRX configuration, etc.

[0179] In one implementation, the length of the assistance information list may be 1. That is, the first terminal device can report the assistance information list to the network side device. The network side device can receive the assistance information list sent from the first terminal device, where the assistance information list can include one or more pieces of assistance information, where each piece of assistance information in the assistance information list can determine a UE identifier to which the assistance information applies by an index identifier, and the UE identifier can be a destination address in a resource request located at an index identifier position in the resource request information list.

[0180] In addition, when a first terminal device in a connected state communicates via sidelink, it needs to transmit a SidelinkUEInformation message containing a sidelink (SL) transmission resource request information list to a network side device (e.g., a base station). Each element in the resource request information list is a resource request of a second terminal device, and the resource request includes the destination address of the second terminal device, a corresponding transmission method (including unicast, multicast, and broadcast), a quality of service (QoS), and a target transmission frequency. In an embodiment of the present application, when the first terminal device reports assistance information to the network side device, a mapping relationship between the assistance information and the destination address of the second terminal device in the resource request information list is established using an index identifier corresponding to the assistance information, so that the network side device can identify the second terminal to which the assistance information transmitted from the first terminal device applies based on this mapping relationship. This allows the existing destination address field in the resource request information list to indicate the second terminal device to which the assistance information applies.

[0181] In some embodiments of the present application, the index identifier may be set in various ways, for example, it may be included in each piece of support information, or it may be determined by the position of the support information in the support information list. Here, for the method of setting the index identifier, please refer to the description of the implementation form of each embodiment above, and the description will be omitted here.

[0182] In some embodiments of the present application, the assistance information in this reported assistance information list may be a paging identifier, or may be sidelink discontinuous reception (SL DRX) assistance information, or may be SL DRX configuration, etc. In one implementation, if the assistance information in this reported assistance information list is a paging identifier, the network side device may send paging information whose destination address is this paging identifier to the terminal device that reported this assistance information list.

[0183] That is, when the first terminal device is a relay UE, the assistance information in the reported assistance information list may include a paging identifier of the second terminal device. For example, when the first terminal device is a relay UE, the relay UE needs to report the paging identifier of the second terminal device (e.g., a remote UE) to the network side device, so that the network side device can forward a paging message sent to the remote UE to the relay UE and forward the paging message to the remote UE by the relay UE.

[0184] In one implementation, if the assistance information in this reported assistance information list is a sidelink discontinuous reception (SL DRX) configuration, the network side device may schedule sidelink transmission resources to the second terminal device corresponding to the destination address within the activation time of the second terminal device corresponding to this destination address.

[0185] For example, as shown in Table 2 above, assuming that the network side device receives the assistance information “SL DRX Configuration A” and determines that the SL DRX Configuration A applies to the terminal device whose SL-DestinationIdentity-r16 of the second (index identifier) ​​entry in the resource request information list (e.g., SL-TxResourceReqList-r16) is 00000001, the network side device can schedule sidelink transmission resources to the terminal device whose destination address is 00000001 within the activation time of the terminal device whose destination address is 00000001.

[0186] In one implementation, if the support information in this reported support information list is SL DRX support information, the network side device can determine the SL DRX configuration of the second terminal device corresponding to the destination address based on this SL DRX support information.

[0187] As an example, the SL DRX assistance information may include an advised SL DRX configuration. For example, assume that the assistance information in the assistance information list reported by the first terminal device received by the network side device is SL DRX assistance information, the advised SL DRX configuration included in this SL DRX assistance information is A, and the index identifier corresponding to this assistance information is 2. If the network side device determines, based on the index identifier, that the destination address in the resource request located at the second (index identifier) ​​position in the resource request information list is "00000001," the network side device can determine that this SL DRX assistance information applies to the terminal device whose destination address is "00000001," and can determine, based on the SL DRX assistance information, that the SL DRX configuration of the terminal device whose destination address is "00000001" is A.

[0188] By implementing the embodiment of the present application, when reporting the terminal assistance information, an index identifier can be used to determine the identifier of the terminal device UE to which the terminal assistance information applies, and the identifier of the terminal device UE is the destination address in the resource request located at the index identifier position in the resource request information list. Thus, the embodiment of the present application uses the index identifier to establish a mapping relationship between the assistance information and the destination address of the opposite terminal device UE in the resource request information list, thereby realizing instructions to the opposite terminal device when reporting the terminal assistance information and saving signaling overhead for reporting the terminal assistance information.

[0189] 9, which is a schematic flowchart of a method for obtaining terminal support information provided by an embodiment of the present application. The method for obtaining terminal support information according to the embodiment of the present application can be performed by a network-side device. As shown in FIG. 9, the method for obtaining terminal support information can include, but is not limited to, the following steps:

[0190] In step 901, a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device are received, where the resource request information list includes multiple resource requests, each corresponding to an index position, and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, where the index identifier corresponds to the index position corresponding to the resource request.

[0191] In the embodiments of the present application, the implementation form in which the first terminal device transmits the resource request information list and the support information list can be realized by any of the forms in each embodiment of the present application, and the embodiments of the present application are not limited to this, and no explanation will be given.

[0192] In step 902, a resource requirement is determined based on the index identifier.

[0193] Optionally, after receiving the resource request information list and the support information list sent from the first terminal device, the network side device can determine the resource request located at the index position in the resource request information list based on the index identifier corresponding to the support information in the support information list.

[0194] In step 903, obtain a destination address in the resource request, where the terminal device having the destination address is the second terminal device.

[0195] Optionally, after determining the resource requirement, the network side device can obtain a destination address from the resource requirement, and the terminal device having the destination address is the second terminal device to which the assistance information applies.

[0196] Since the setting methods of the index identifiers are different, the formats of the support information lists are also different. For example, as shown in Tables 2 and 4 above, the index identifiers may be included in the corresponding support information. For example, as shown in Tables 1, 3, and 5 above, the support information list has the same length as the resource request information list, and the index identifier corresponding to the support information can be understood as the index position of the support information in the support information list. That is, the network-side device can determine the index identifier corresponding to the support information based on the position of the support information in the support information list, and can also determine the resource request located at the index position in the resource request information list based on the index identifier.

[0197] In one implementation, the index identifier is included in the corresponding assistance information. For example, assume that the resource request information list (e.g., SL-TxResourceReqList-r16) reported by the first terminal device has four elements, for example, as shown in Table 1 above, and the reported assistance information list is, for example, as shown in Table 2 above. After the network side device receives the resource request information list and the assistance information list reported from the first terminal device, the network side device determines the resource request whose index position is 2 in the resource request information list based on the index identifier "2" corresponding to the assistance information, and obtains the destination address 00000001 in this resource request whose index position is 2, thereby knowing that the terminal device to which this assistance information (i.e., SL DRX configuration information is A in Table 2 above) applies is the second terminal device having the destination address "00000001". In this way, the network side device determines the resource request whose index position is 4 in the resource request information list based on the index identifier "4" corresponding to the assistance information, and by obtaining the destination address 00000011 in this resource request whose index position is 4, it can know that the terminal device to which this assistance information (i.e., SL DRX setting information is B in Table 2 above) is applied is the second terminal device having the destination address "00000011".

[0198] In another implementation, the assistance information list has the same length as the resource request information list, and the index position of the resource request in the resource request information list is the same as the index position of the assistance information in the assistance information list. The network side device can determine an index identifier corresponding to the assistance information based on the index position of the assistance information in the assistance information list.

[0199] For example, assume that the resource request information list (e.g., SL-TxResourceReqList-r16) reported from the first terminal device has four elements, for example, as shown in the above Table 1, and the reported assistance information list is, for example, as shown in the above Table 3. After receiving the resource request information list and the assistance information list transmitted from the first terminal device, the network side device determines the resource request whose index position in the resource request information list is 2 based on the index identifier "2" corresponding to the assistance information (i.e., the position of the assistance information in the assistance information list), and obtains the destination address 00000001 in this resource request whose index position is 2, thereby being able to know that the terminal device to which this assistance information (i.e., the SL DRX setting information is A in the above Table 3) applies is the second terminal device having the destination address "00000001". In this way, the network side device determines the resource request whose index position is 4 in the resource request information list based on the index identifier "4" corresponding to the assistance information, and by obtaining the destination address 00000011 in this resource request whose index position is 4, it can know that the terminal device to which this assistance information (i.e., SL DRX setting information is B in Table 3 above) is applied is the second terminal device having the destination address "00000011".

[0200] In some embodiments of the present application, the assistance information in the reported assistance information list may be a paging identifier, or may be SL DRX assistance information, or may be SL DRX configuration information, etc. In addition, when the content of the assistance information reported by the first terminal device to the network side device is different, the roles played by the first terminal device and the second terminal device also differ. For example, when the assistance information transmitted by the first terminal device to the network side device is a paging identifier, the first terminal device is a relay terminal device, and the second terminal device is a remote terminal device. In addition, when the assistance information transmitted by the first terminal device to the network side device is SL DRX assistance information, the first terminal device is a transmitting terminal device, and the second terminal device is a receiving terminal device. In addition, when the assistance information transmitted by the first terminal device to the network side device is SL DRX configuration information, the first terminal device is a receiving terminal device, and the second terminal device is a transmitting terminal device. Each of these will be described in detail below based on the embodiments.

[0201] In some embodiments of the present application, if the assistance information is a paging identifier, the network side device can determine a paging message of the paging identifier after obtaining the destination address in the resource request, and send the paging message to the second terminal device via the first terminal device. Optionally, in embodiments of the present application, the first terminal device is a relay terminal device, and the second terminal device is a remote terminal device. When the second terminal device sends a paging request to the network side device, the second terminal device sends its paging identifier to the first terminal device. The first terminal device receives the paging identifier sent from the second terminal device and sends the paging identifier to the network side device. The first terminal device determines the paging identifier as assistance information for the second terminal device, sets the paging identifier in an assistance information list, and reports it to the network side device. After receiving the assistance information list, the network side device determines a resource request located at an index position in the resource request information list based on an index identifier corresponding to a paging identifier in the assistance information list, obtains a destination address in the resource request located at the index position, and determines that the terminal device having the destination address is a second terminal device to which the paging identifier applies, so that the network side device can send a paging message of the paging identifier to the first terminal device, and the first terminal device forwards the paging message to the second terminal device.

[0202] In some embodiments of the present application, if the assistance information is sidelink discontinuous reception (SL DRX) configuration information, the network side device schedules sidelink transmission resources to the second terminal device based on the SL DRX configuration information within the activation time of the second terminal device.

[0203] Optionally, in an embodiment of the present application, the first terminal device is a receiving terminal device, and the second terminal device is a transmitting terminal device. To save power, the network side device (e.g., a base station) can adjust the Uu DRX so that the SL DRX and the Uu DRX overlap as much as possible based on the SL DRX configuration information of the sidelink terminal device. In this case, the first terminal device receives the SL DRX configuration information transmitted from the second terminal device, and the second terminal device decides whether to accept the SL DRX configuration information. If the first terminal device decides to accept the SL DRX configuration information, the first terminal device must determine the SL DRX configuration information as assistance information for the second terminal device, set the assistance information in an assistance information list, and report it to the network side device. After receiving the assistance information list, the network side device determines a resource request located at an index position in the resource request information list based on an index identifier corresponding to the SL DRX configuration information in the assistance information list, obtains a destination address in the resource request located at the index position, and determines that the terminal device having the destination address is a second terminal device to which the SL DRX configuration information applies, so that the network side device can schedule sidelink transmission resources to the second terminal device based on the SL DRX configuration information within the activation time of the second terminal device.

[0204] In some embodiments of the present application, if the support information is SL DRX support information, and the SL DRX support information includes advised SL DRX configuration information, the network side device determines the SL DRX configuration information of the second terminal device based on the SL DRX support information.

[0205] Optionally, the first terminal device is a transmitting terminal device and the second terminal device is a receiving terminal device. In order to save power, the network side device (e.g., a base station) can adjust the Uu DRX so that the SL DRX and the Uu DRX overlap as much as possible based on the SL DRX configuration information of the sidelink terminal device, where the SL DRX configuration information may be the SL DRX configuration information advised in the SL DRX assistance information sent from the receiving terminal device.

[0206] For example, a unicast SL DRX is sent by a transmitting terminal device (e.g., a first terminal device in an embodiment of the present application) to a receiving terminal device (e.g., a second terminal device in an embodiment of the present application), so that the receiving terminal device can send SL DRX assistance information to the transmitting terminal device, and this SL DRX assistance information includes advised SL DRX configuration information, so that when the transmitting terminal device is in a connected state, it reports the received SL DRX assistance information to a network side device (e.g., a base station), so that the network side device (e.g., a base station) determines SL DRX configuration based on this SL DRX assistance information. After receiving the assistance information list, the network side device determines a resource request located at an index position in the resource request information list based on an index identifier corresponding to the SL DRX configuration information in the assistance information list, obtains a destination address in the resource request located at the index position, and the terminal device having this destination address is the second terminal device to which this SL DRX configuration information applies, so that the network side device can adjust Uu DRX so that SL DRX and Uu DRX overlap as much as possible, thereby achieving power saving.

[0207] By implementing the embodiments of the present application, a mapping relationship is established between the assistance information and the destination address of the second terminal device in the resource request information list using an index identifier corresponding to the assistance information, so that the network side device identifies the second terminal to which the assistance information sent from the first terminal device applies based on this mapping relationship, thereby realizing the indication of the second terminal device to which the assistance information applies through the existing destination address field in the resource request information list, and saving the signaling overhead of reporting the assistance information.

[0208] In the above embodiments provided by the present application, the methods provided by the embodiments of the present application are described from the perspective of a terminal device (e.g., the first terminal device in the above method embodiments) and a network-side device. To realize each function in the methods provided by the above embodiments of the present application, the terminal device (e.g., the first terminal device in the above method embodiments) and the network-side device may include a hardware configuration and a software module, and each of the above functions may be realized in the form of a hardware configuration, a software module, or a hardware configuration plus a software module. Some of the above functions may be implemented in the form of a hardware configuration, a software module, or a hardware configuration plus a software module.

[0209] 10 is a schematic configuration diagram of a communication device 100 provided by an embodiment of the present application. The communication device 100 shown in FIG. 10 may include a transceiver module 1001 and a processing module 1002. The transceiver module 1001 may include a transmitting module and / or a receiving module, where the transmitting module is used to realize a transmitting function and the receiving module is used to realize a receiving function, and the transceiver module 1001 can realize the transmitting function and / or the receiving function.

[0210] It is understood that the communication device 100 may be a terminal device (e.g., the first terminal device in the method embodiment described above), a device in a terminal device, or a device that can be matched to and used with a terminal device, or that the communication device 100 may be a network device, a device in a network device, or a device that can be matched to and used with a network device.

[0211] When the communication device 100 is a terminal device (for example, the first terminal device in the above-mentioned method embodiment): In an embodiment of the present application, the transceiver module 1001 sends a sidelink (SL) resource request information list and an assistance information list to the network side device, where the resource request information list includes multiple resource requests, and one resource request corresponds to one index position, and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, where the index identifier corresponds to the index position corresponding to the resource request.

[0212] In one implementation, the index identifier is included in the corresponding aiding information.

[0213] In one possible implementation, the processing module 1002 determines an index position of the resource request in the resource request information list, and sets an index identifier corresponding to the support information in the support information list based on the index position.

[0214] In one possible implementation, the support information list is of the same length as the resource request information list, and the index position of the resource request in the resource request information list is the same as the index position of the support information in the support information list.

[0215] In one possible implementation, the processing module 1002 determines the aiding information.

[0216] In one possible implementation, the support information comprises: one of a paging identifier transmitted from the second terminal device, sidelink discontinuous reception (SL DRX) configuration information transmitted from the second terminal device, and SL DRX assistance information transmitted from the second terminal device, where the SL DRX assistance information includes advised SL DRX configuration information.

[0217] When the communication device 100 is a network device: In an embodiment of the present application, the transceiver module 1001 receives a sidelink (SL) resource request information list and an assistance information list sent from a first terminal device, where the resource request information list includes multiple resource requests, each corresponding to an index position, and the assistance information list includes assistance information of a second terminal device and an index identifier corresponding to the assistance information, where the index identifier corresponds to the index position corresponding to the resource request, and the processing module 1002 determines the resource request based on the index identifier and obtains a destination address in the resource request, where the terminal device having the destination address is the second terminal device.

[0218] In one implementation, the index identifier is included in the corresponding aiding information.

[0219] In one implementation, the support information list is the same length as the resource request information list, and the resource request has the same index position in the resource request information list as the support information has the same index position in the support information list.

[0220] In one implementation, the processing module 1002 further determines an index identifier corresponding to the aiding information based on an index position of the aiding information in the aiding information list.

[0221] In one possible implementation, if the assistance information is a paging identifier, the processing module 1002 further determines a paging message of the paging identifier, and the transceiver module 1001 further transmits the paging message to the second terminal device via the first terminal device.

[0222] In one possible implementation, if the assistance information is sidelink discontinuous reception (SL DRX) configuration information, the transceiver module 1001 further schedules sidelink transmission resources to the second terminal device based on the SL DRX configuration information within an activation time of the second terminal device.

[0223] In one possible implementation, if the support information is SL DRX support information and the SL DRX support information includes advised SL DRX configuration information, the processing module 1002 further determines the SL DRX configuration information of the second terminal device based on the SL DRX support information.

[0224] The specific manner in which each module of the device in the above embodiment performs its operation has been described in detail in the embodiment of this method, and therefore will not be described here.

[0225] 11, which is a schematic diagram of another communication device 110 provided by an embodiment of the present application. The communication device 110 may be a network device, a terminal device (e.g., the first terminal device in the above-mentioned method embodiment), a chip, chip system, processor, etc. that supports the network device to implement the above-mentioned method, or a chip, chip system, processor, etc. that supports the terminal device (e.g., the first terminal device in the above-mentioned method embodiment) to implement the above-mentioned method. This device can implement the method described in the above-mentioned method embodiment, and please refer to the description of the above-mentioned method embodiment for details.

[0226] The communication device 110 may include one or more processors 1101. The processor 1101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute a computer program, and process data of the computer program.

[0227] Optionally, the communication device 110 may further include one or more memories 1102 capable of storing computer programs 1104. The processor 1101 executes the computer programs 1104 so that the communication device 110 performs the methods described in the above method embodiments. Optionally, data may also be stored in the memory 1102. The communication device 110 and the memory 1102 may be provided separately or integrated.

[0228] Optionally, the communication device 110 may further include a transceiver 1105 and an antenna 1106. The transceiver 1105 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit for realizing a transmitting and receiving function. The transceiver 1105 may include a receiver and a transmitter, and the receiver may be referred to as a receiver or a receiving circuit for realizing a receiving function, and the transmitter may be referred to as a transmitter or a transmitting circuit for realizing a transmitting function.

[0229] Optionally, the communication device 110 may further include one or more interface circuits 1107. The interface circuit 1107 is used to receive and transmit code instructions to the processor 1101. The processor 1101 executes the code instructions to cause the communication device 110 to perform the methods described in the above method embodiments.

[0230] If the communication device 110 is a terminal device (e.g., the first terminal device in the method embodiment described above), the transceiver 1105 performs step 301 in Figure 3, step 401 in Figure 4, step 501 and step 503 in Figure 5, step 601 and step 603 in Figure 6, and step 701 and step 703 in Figure 7. The processor 1101 performs step 502 in Figure 5, step 602 in Figure 6, and step 702 in Figure 7.

[0231] If the communication device 110 is a network device, the transceiver 1105 performs step 801 in Figure 8 and step 901 in Figure 9. The processor 1101 performs steps 902 and 903 in Figure 9.

[0232] In one embodiment, the processor 1101 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transmitting / receiving circuit, an interface, or an interface circuit. The transmitting / receiving circuit, the interface, or the interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transmitting / receiving circuit, the interface, or the interface circuit may be used for reading and writing code / data, or the transmitting / receiving circuit, the interface, or the interface circuit may be used for transmitting or communicating signals.

[0233] In one implementation, the processor 1101 may store a computer program 1103 that, when executed on the processor 1101, causes the communication device 110 to perform the methods described in the method embodiments above. The computer program 1103 may be hardened within the processor 1101, in which case the processor 1101 may be implemented by hardware.

[0234] In one embodiment, the communication device 110 may include circuitry capable of implementing the transmit, receive, or communication functions of the method embodiments described above. The processors and transceivers described herein may be implemented in an integrated circuit (IC), analog IC, radio frequency integrated circuit (RFIC), hybrid signal IC, application specific integrated circuit (ASIC), printed circuit board (PCB), electronic device, etc. The processors and transceivers may also be fabricated in various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide semiconductor (nMOS), p-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0235] The communication device described in the above embodiment may be a network device or a terminal device (e.g., the first terminal device in the above method embodiment), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to that shown in FIG. 11. The communication device may be an independent device or part of a larger device. For example, the communication device may be as follows: (1) An independent integrated circuit IC, or chip, or chip system or subsystem; (2) A set of one or more ICs, which may optionally include a memory component for storing data, computer programs. (3) ASICs such as modems, (4) Modules that can be incorporated into other devices; (5) Receivers, terminal devices, smart terminal devices, mobile phones, wireless devices, handhelds, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, etc. (6) Others.

[0236] Those skilled in the art can also understand that the various illustrative logical blocks and steps described in the embodiments of the present application can be realized by electronic hardware, computer software, or a combination of both. Whether such functions are realized by hardware or software is determined by the specific application and the overall system design requirements. Those skilled in the art can use the above functions realized in various ways for each specific application, but this implementation should not be understood as going beyond the scope of protection of the embodiments of the present application.

[0237] An embodiment of the present application further provides a communication system including a communication device serving as a terminal device in the embodiment of Figure 10 and a communication device serving as a network device, or a communication device serving as a terminal device in the embodiment of Figure 11 and a communication device serving as a network device.

[0238] The present application further provides a computer-readable storage medium having stored thereon instructions that, when executed by a computer, implement the functionality of any of the method embodiments described above.

[0239] The present application further provides a computer program product which, when executed by a computer, implements the functionality of any of the method embodiments described above.

[0240] The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. The processes or functions according to the above embodiments of the present application are generated in whole or in part when the computer programs are loaded and executed by a computer. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer program may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another; for example, the computer program may be transmitted from one website, computer, server, or data center to another via wire (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.). The computer-readable storage medium may be any available medium accessible by a computer, or may include a data storage device such as a server, data center, or the like integrated with one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid state disk (SSD)).

[0241] Those skilled in the art will understand that the various numerals such as "1st," "2nd," etc. in the present application are merely for the convenience of explanation, and do not limit the scope of the embodiments of the present application, nor do they represent priority.

[0242] At least one in the present application can also be described as one or more, and more can be two, three, four or more, and the present application is not limited thereto. In the embodiments of the present application, for one technical feature, technical features in the technical feature category are distinguished by "first," "second," "third," "A," "B," "C," and "D," etc., and there is no order of precedence or chronology between the technical features described in the "first," "second," "third," "A," "B," "C," and "D."

[0243] The correspondences shown in each table in this application may be preset or predefined. The values ​​of the information in each table are merely examples and can be set to other values; the application is not limited to these. When setting the correspondences between information and each parameter, not all of the correspondences shown in each table need to be set. For example, in the tables of this application, the correspondences shown by certain rows may not be set. As another example, appropriate transformations such as splitting and merging can be performed based on the tables. The names of the parameters shown in the titles of the tables above may be other names understandable to the communication device, and the values ​​and display methods of the parameters may be other values ​​and display methods understandable to the communication device. The tables above may also be implemented using other data structures, such as arrays, queues, containers, stacks, linear tables, pointers, link tables, trees, diagrams, structures, classes, heaps, hash lists, or hash tables.

[0244] Predefined in this application can be understood as defined, predefined, stored, prestored, prenegotiated, pre-set, hardened, or pre-baked.

[0245] Those skilled in the art will recognize that the units and algorithm steps of each example described in the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented in hardware or software is determined by the specific application and design constraints of the technical solution. Those skilled in the art may realize the described functions using different methods for each specific application, but such realization should not be considered beyond the scope of the present application.

[0246] As will be apparent to those skilled in the art, for convenience and brevity of description, the specific operating processes of the above-described systems, devices and units may refer to the corresponding processes in the above-described method embodiments, and the description thereof will be omitted here.

[0247] As described above, the present application only provides specific embodiments, but the scope of protection of the present application is not limited thereto, and a person skilled in the art can easily imagine that modifications or replacements within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be determined based on the scope of protection of the claims.

Claims

1. 1. An assistance information reporting method performed by a first terminal device, comprising: sending a side link (SL) resource request information list and an assistance information list to a network side device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, the assistance information list includes assistance information, and the assistance information includes an index identifier to determine a terminal device identifier corresponding to the assistance information; The terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list; and further comprising: setting support information to an index position in the support information list of a resource request corresponding to a destination address of a second terminal device, the support information list being set to the same index position, the support information list being the same length as the resource request information list. A support information reporting method comprising:

2. the index identifier is determined by the position of the support information in the support information list; 2. The support information reporting method according to claim 1.

3. Further comprising receiving SL DRX assistance information transmitted from a second terminal device, wherein the SL DRX assistance information is included in the assistance information; 2. The support information reporting method according to claim 1.

4. A support information acquisition method executed by a network-side device, comprising: receiving a side link (SL) resource request information list and an assistance information list transmitted from a first terminal device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information, and the assistance information includes an index identifier to determine a terminal device identifier corresponding to the assistance information; The terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list; determining a destination address in the resource request located at the index identifier position in the resource request information list based on the index identifier, wherein aiding information corresponding to the index identifier applies to a second terminal device corresponding to the destination address, and the aiding information list has the same length as the resource request information list; A support information acquisition method comprising:

5. the index identifier is determined by the position of the support information in the support information list; 5. The support information acquisition method according to claim 4.

6. The assistance information includes sidelink discontinuous reception (SL DRX) assistance information.

5. The support information acquisition method according to claim 4.

7. A communication device, A transceiver module for transmitting a side link (SL) resource request information list and an assistance information list to a network side device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, the assistance information list includes assistance information, and the assistance information includes a transceiver module for determining a terminal device identifier corresponding to the assistance information by an index identifier; The terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list; and a processing module for setting the index identifier based on an index position in the resource request information list of a resource request corresponding to a destination address of a second terminal device, wherein the support information list has the same length as the resource request information list. A communication device comprising:

8. the index identifier is determined by the position of the support information in the support information list; 8. The communication device according to claim 7,

9. The transceiver module further receives SL DRX assistance information sent from a second terminal device, and the SL DRX assistance information is included in the assistance information.

8. The communication device according to claim 7,

10. A communication device, a transceiver module for receiving a side link (SL) resource request information list and an assistance information list transmitted from a first terminal device, wherein the resource request information list includes a resource request of a second terminal device, the resource request of the second terminal device includes a destination address of the second terminal device, and the assistance information list includes assistance information, and the assistance information includes an index identifier, the transceiver module determining a terminal device identifier corresponding to the assistance information; The terminal device identifier corresponding to the assistance information is a destination address in the resource request located at an index identifier position in the resource request information list; a processing module for determining, based on the index identifier, a destination address in the resource request located at the index identifier position in the resource request information list, wherein aiding information corresponding to the index identifier is applied to a second terminal device corresponding to the destination address, and the aiding information list has the same length as the resource request information list; A communication device comprising:

11. the index identifier is determined by the position of the support information in the support information list; 11. The communication device according to claim 10.

12. The assistance information includes sidelink discontinuous reception (SL DRX) assistance information.

11. The communication device according to claim 10.

13. A communication device, a processor and a memory, a computer program stored in the memory, and the processor executes the computer program stored in the memory to cause the device to perform the method according to any one of claims 1 to 3; A communication device comprising:

14. A communication device, a processor and a memory, A computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to perform the method according to any one of claims 4 to 6. A communication device comprising:

15. A computer-readable storage medium having instructions stored thereon, When said instructions are executed, the method according to any one of claims 1 to 3 is realized. A computer-readable storage medium comprising:

16. A computer-readable storage medium having instructions stored thereon, When said instructions are executed, the method according to any one of claims 4 to 6 is realized. A computer-readable storage medium comprising:

Citation Information

Patent Citations

  • Method and apparatus for requesting sidelink transmission resources in wireless communication system

    JP2021111967A

  • Configuration of radio connections in a multi-rat network

    WO2021260146A1