COMMUNICATION METHODS, TERMINALS, NETWORKING DEVICES, CHIPS, COMMUNICATION SYSTEMS, AND COMPUTER-READABLE STORAGE MEDIA

Abstract

This invention relates to a method of communication, a terminal, a network device, a chip, a communication system, and a computer-readable storage medium. This method comprises the following steps. A terminal transmitting first information, wherein the first information has one or more resource request information, wherein the resource request information has a first destination information, or the resource request information has a first destination information and one or more second destination information, and this terminal is a terminal on a side link.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] With the advancement of wireless communication technology, the 3rd Generation Partnership Project (3GPP) introduced relays. For example, in a user equipment-to-user equipment (UE-to-UE, U2U) relay link, different remote terminals, such as a source terminal and a destination terminal, can be connected via a relay terminal. In a U2U relay link, the remote terminal or relay terminal can request network equipment to configure and provide sidelink transmission-related configurations and resources.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and device that can better provide configuration for various terminal devices in the side link.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The terminal device sends first information, which includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in the side link.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The network device receives first information, which includes one or more resource request information of the terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in the side link.

[0009] An embodiment of the present application provides a terminal device, including:

[0010] A sending unit is used to send first information, which includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in the side link.

[0011] An embodiment of the present application provides a network device, including:

[0012] A receiving unit is used to receive first information, which includes one or more resource request information of a terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a side link.

[0013] An embodiment of the present application provides a terminal device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory so that the terminal device executes the above-mentioned communication method.

[0014] An embodiment of the present application provides a network device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory so that the network device executes the above-mentioned communication method.

[0015] The embodiment of the present application provides a chip for implementing the above-mentioned communication method. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.

[0016] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to execute the above-mentioned communication method.

[0017] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.

[0018] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.

[0019] In an embodiment of the present application, one or more target information in the resource request information sent by the terminal device in the side link is conducive to more accurately determining the relevant information of the side link, thereby providing a suitable configuration for the terminal device in the side link. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0021] 2A and 2B are schematic diagrams of 3GPP transmission modes.

[0022] 3A and 3B are schematic diagrams of the protocol definition of the LTE-V2X sidelink.

[0023] FIG4 is a schematic diagram of UE-to-UE relay.

[0024] FIG5 is a schematic diagram of a process of establishing a UE-to-UE relay connection.

[0025] FIG6 is a schematic diagram of a UE architecture in a UE-to-UE relay.

[0026] FIG7 is a schematic diagram of the SUI signaling process.

[0027] FIG8 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0028] FIG9 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0029] FIG10 is a schematic diagram of SUI reporting.

[0030] FIG11 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0031] FIG12 is a schematic block diagram of a network device according to an embodiment of the present application.

[0032] FIG13 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0033] FIG14 is a schematic block diagram of a chip according to an embodiment of the present application.

[0034] FIG15 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0036] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

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

[0038] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0039] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0040] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0041] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0042] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

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

[0044] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0045] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0046] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

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

[0048] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0049] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0050] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0051] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0052] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0053] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0054] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0055] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0056] 1. Long Term Evolution (LTE) Device to Device (D2D) / V2X

[0057] Device-to-device communication is a sidelink (SL) transmission technology based on D2D. Unlike traditional cellular systems where communication data is received or sent through base stations, the Internet of Vehicles system uses direct terminal-to-terminal communication, resulting in higher spectrum efficiency and lower transmission latency.

[0058] 3GPP includes two transmission modes: Mode 3 and Mode 4.

[0059] Mode 3: As shown in Figure 2A, the terminal's transmission resources are allocated by the base station, and the terminal transmits data on the sidelink based on the allocated resources. The base station can allocate resources for a single transmission or for semi-static transmission.

[0060] Mode 4: As shown in FIG2B , the vehicle terminal selects a resource in the resource pool for data transmission.

[0061] In 3GPP, D2D includes different phases:

[0062] (1) Proximity-based Service (ProSe): Device-to-device communication in Rel-12 / 13 is studied for ProSe scenarios, primarily targeting public safety services. In Proximity-based Service, by configuring the time domain location of resource pools, for example, discontinuous resource pools in the time domain, the UE can transmit / receive data discontinuously on the sidelink, thereby saving power.

[0063] (2) Internet of Vehicles: In Rel-14 / 15, the Internet of Vehicles system was studied for vehicle-to-vehicle communication scenarios, mainly for relatively high-speed vehicle-to-vehicle and vehicle-to-pedestrian communication services. In V2X, since the vehicle system has a continuous power supply, power efficiency is not the main issue, but data transmission latency is the main issue. Therefore, the system design requires terminal devices to continuously send and receive.

[0064] (3) Wearable devices, further enhanced device-to-device (FeD2D): In Rel-14, this topic studied the scenario of wearable devices accessing the network through mobile phones, mainly targeting low-speed and low-power access scenarios. In FeD2D, in the pre-research stage, 3GPP concluded that the base station can configure the discontinuous reception (DRX) parameters of the remote terminal through a relay terminal. However, because this topic did not enter the standardization stage, the specific details of how to configure DRX have not been determined.

[0065] NR V2X

[0066] Based on LTE V2X, NR V2X is not limited to broadcast scenarios, but has been further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.

[0067] Similar to LTE V2X, NR V2X also includes two resource authorization modes: mode-1 and mode-2.

[0068] Unlike LTE V2X, in addition to the feedback-free, UE-initiated Hybrid Automatic Repeat-reQuest (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication but also includes multicast communication.

[0069] NR-V2X supports data transmission under network scheduling, i.e. Mode 1. When the UE operates in Mode 1, the resource authorization for sidelink data transmission comes from the network, that is, the network issues resource authorization to the sending UE, and the sending UE uses the resource for sidelink transmission. Similar to the uplink transmission of the air interface (Uu interface), since the network side does not know the current data cache status of the UE side, the UE needs to report the current data cache status of the UE to the network, thereby triggering the network to issue resource authorization. The difference is that the buffer status report (BSR) / scheduling request (SR) in traditional cellular networks is only for uplink data, while for V2X, BSR / SR for sidelink data needs to be added.

[0070] In simple terms, the UE sends a scheduling request (SR or random access) to the base station, followed by a sidelink BSR. Based on the sidelink BSR, the base station can determine that the UE has data to transmit for sidelink communication and estimate the resources required to transmit the data. The base station can use the configured RNTI for the sidelink to schedule the transmission resources for the sidelink communication.

[0071] For the LTE-V2X sidelink BSR Media Access Control (MAC) Control Element (CE) format, Figures 3A and 3B show examples of the protocol-defined format (defined for even-numbered and odd-numbered items, respectively). Figure 3A shows the LTE-V2X sidelink BSR format (even-numbered items), and Figure 3B shows the LTE-V2X sidelink BSR format (odd-numbered items).

[0072] The following are examples of the meaning of the different fields for the sidelink BSR:

[0073] Target address identification: The "target index" field is used to identify the target address of the sidelink communication. The UE sets the value to the index of the relevant target address in the target address list reported in the sidelink user equipment information (Sidelink UE Information, SUI) message. If the UE reports multiple target address lists in the SUI message, the UE arranges the multiple target address lists in serial order to index the corresponding target addresses. Specifically, since the SUI message in LTE-V2X defines target address lists for different frequencies, for a certain target address, when it can be used for more than one frequency, there will be a situation where one target address corresponds to multiple target indexes, which will cause some target index redundancy. This problem is not solved in LTE-V2X. In NR-V2X, the signaling structure of the SUI message is modified to address this problem, that is, the frequency lists are placed in different target address structures, thereby avoiding this problem.

[0074] Logical Channel Group Identifier: This field identifies the logical channel group for which the UE buffer status is being reported. Here, the logical channel group identifier is used to indicate priority information (ProSe Per-Packet Priority, PPPP) and reliability information (ProSe Per-Packet Reliability, PPPR) related to the data to be transmitted. Specifically, the UE reports the amount of data associated with one or more PPPP and / or PPPR values ​​via the sidelink BSR. The mapping of PPPP and PPPR values ​​to logical channel groups can be configured by the base station, and the PPPP value and / or PPPR value is reflected by the logical channel group ID contained in the sidelink BSR. ;

[0075] Buffer size: Similar to the definition of uplink BSR, this field defines the total amount of data in all logical channels of the associated logical channel group (LCG) after the generation of the MAC protocol data unit (PDU), including all data available for transmission in the radio link control (RLC) layer and the packet data convergence protocol (PDCP) layer (for example, without considering the size of the RLC and MAC message headers).

[0076] In addition, the above format also applies to truncated sidelink BSRs. That is, when the resource grant size is insufficient to contain all the sidelink BSR information, the UE can truncate the sidelink BSR. During truncation, the buffer information for different target addresses and logical channel groups is sorted in descending order of priority based on the highest-priority logical channel in the logical channel group, with the higher-priority buffer information being included first, regardless of the value of the target index field.

[0077] For NR-V2X, the format definition of the sidelink BSR is similar, except that:

[0078] The target address identifier is expanded from 4 bits to 5 bits;

[0079] The logical channel group identifier is expanded from 2 bits to 3 bits;

[0080] The cache size has been expanded from 6 bits to 8 bits.

[0081] Therefore, a logical channel group under a target address needs to occupy 2 bytes, so there is no need to define the sidelink BSR format separately for the even number of items and the odd number of items.

[0082] For triggering of a sidelink BSR, the following examples of triggering conditions may be included, similar to those for an uplink BSR:

[0083] (1) New data to be transmitted appears in the RLC entity or PDCP entity (if there is other data to be transmitted, the priority of the new data is higher than the priority of any logical channel group to be transmitted with the same destination address, or there is no other data to be transmitted with the same destination address);

[0084] (2) After allocating resource grant space for data and triggering the fill BSR for the uplink channel, the number of remaining bits is equal to or greater than the size of the sidelink BSR (including buffer information of at least one logical channel group for at least one target address);

[0085] (3) The sidelink BSR retransmission timer expires and the MAC entity has data available for sidelink transmission;

[0086] (4) The sidelink BSR periodic timer expires.

[0087] Sidelink BSR can also be triggered when the UE is configured from autonomous resource selection mode to network scheduled resource selection mode. Autonomous resource selection mode may include the following examples:

[0088] Mode 2 and Mode 4 under LTE-V2X;

[0089] Mode 2 under NR-V2X.

[0090] 3. Side-by-side UE-2-UE relay technology

[0091] As shown in Figure 4, in Rel-17 ProSe, 3GPP includes a U2U (UE-to-UE) relay function based on Layer 2 and Layer 3 relays. That is, the source UE connects to the target UE through the relay UE, and the relay UE transfers data between the source UE and the target UE.

[0092] Figure 5 shows the specific connection establishment steps. The source UE, relay UE, and target UE discover each other through discovery messages or direct communication request (DCR) messages. The relay UE can help the source UE forward discovery messages or DCR messages. After discovering each other, the source UE and target UE select a relay and establish a connection with the appropriate relay. The relay then acts as a relay to establish an end-to-end direct communication interface (PC5) connection.

[0093] 3GPP Rel-17 includes Layer 2 end-to-end relay. As shown in Figure 6, the adaptation layer (e.g., the Sidelink Relay Adaptation Protocol (SRAP) layer) is placed above the control plane and user plane radio link control sublayer between the relay UE and the remote UE, such as the source UE / target UE. The PC5 Service Data Adaptation Protocol (SDAP) / Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) terminate between the source terminal and the target terminal, that is, between the two remote UEs. The adaptation layer (SRAP), RLC, Medium Access Control (MAC) and physical layer (PHY) terminate in each direct link (i.e., the link between the source terminal and the relay terminal and the link between the relay terminal and the target terminal).

[0094] An example of L2 UE-to-UE relay is as follows:

[0095] (1) The adaptation layer of the relay terminal supports sidelink bearer mapping between access PC5 RLC channels. For sidelink relay services, different end-to-end bearers, such as signaling radio bearers (SRBs) and data radio bearers (DRBs), of the same remote UE and / or different remote UEs can be mapped N:1 and multiplexed on a single PC5 RLC channel.

[0096] (2) The adaptation layer is used to support terminal identification for sideline services (multiplexing data from multiple terminals). The terminal PC5 radio bearer and terminal identification information are included in the adaptation layer so that the target can associate received data packets with a specific PDCP entity associated with the source terminal's radio bearer.

[0097] 4. Uu interface side link information reporting

[0098] As shown in Figure 7, Uu interface sidelink information reporting is performed through the SUI process. As long as the system broadcasts V2X-related system messages such as SIB12 acquisition (SIB12 acquisition), and the UE supports V2X sidelink communication capabilities, if the RRC-connected terminal (RRC_CONNECTED UE) wishes to conduct V2X sidelink communication, it can send a SUI message such as SidelinkUEInformationNR (New Radio Sidelink Terminal Information) to the serving cell. The purpose of this process is to notify the base station that the UE is interested in or no longer interested in V2X sidelink communication.

[0099] In addition, the SUI message (also called SUI signaling) can include the following uses:

[0100] (1) If an RRC_CONNECTED UE wishes to perform sidelink communication on a specific carrier frequency, it may send a SUI message to its serving cell. This SUI message carries the Quality of Service (QoS) flow information for each target address. Based on the UE's report, the serving cell may configure the UE with the relevant resources and parameters (SDAP / PDCP / RLC / MAC configuration) on the required carrier frequency.

[0101] (2) For network-based resource allocation, the base station can schedule V2X transmissions based on the sidelink BSR. To determine the destination address index in the BSR, the UE reports the relevant destination address to the base station via a SUI message, so that the base station and / or UE can determine the relevant index for subsequent sidelink BSR reporting.

[0102] An example of a SUI signaling format is as follows:

[0103] An example of a network configuration information signaling format is as follows:

[0104] In the current SUI format, UEs use the destination address (sl-DestinationIdentity) as an index / entry when requesting network parameters and resource configuration. The network can configure resource scheduling and protocol stack parameters for the UE based on the label of each destination address and the associated QoS flow. However, the following examples of problems exist in U2U relay:

[0105] For each remote UE: For each U2U link, the remote UE has two target endpoints. Specifically, for the SRAP / RLC / MAC / PHY layers, the target endpoint is the relay UE, while for the SDAP / PDCP layers, the target endpoint is the remote UE. Furthermore, the mapping between relay and remote UE can be non-one-to-one. For example, the same relay UE can provide relay services for multiple remote UEs, and the same pair of remote UEs can communicate through multiple relay UEs. Therefore, reporting two or more target endpoint IDs is crucial to inform the network of the U2U relay link topology, enabling parameter and resource configuration.

[0106] For a relay UE: it needs to let the network know that it is a relay UE so that the network can better provide it with configurations and resources.

[0107] FIG8 is a schematic flow chart of a method 800 according to an embodiment of the present application. The method can optionally be applied to the systems shown in FIG1 to FIG7 , but is not limited thereto. The method includes at least part of the following contents.

[0108] S810. The terminal device sends a first message, which includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information. The terminal device is a terminal device in a side link.

[0109] In an embodiment of the present application, the sidelink may be a sidelink relay link, such as a U2U relay link. The U2U relay link may be a single-hop relay link or a multi-hop relay link. The terminal device in the relay link may be a remote terminal or a relay terminal. The remote terminal and / or relay terminal in the relay link may each report their respective first information to the network device. In some examples, the first information may be a SUI. A resource request message in the first information may be used to request the network device for the resource and / or parameter configuration required by the terminal device for a particular U2U relay link.

[0110] In some examples, a resource request message may include multiple target information such as first target information and one or more second target information. The multiple second target information may also be a second target information list or a second target information list. If the first target information indicates a remote terminal on the first U2U relay link, one second target information may indicate a relay terminal on the first U2U relay link. If the first target information indicates a relay terminal on the first U2U relay link, one second target information may indicate a remote terminal on the first U2U relay link. For example, the terminal device is Remote UE1, the first target information indicates the remote terminal Remote UE4 on the U2U relay link Relaylink1, one second target information indicates the relay terminal Relay UE2 on the U2U relay link Relaylink1 that is directly connected to Remote UE1, and another second target information indicates the relay terminal Relay UE3 on the U2U relay link Relaylink1 that is not directly connected to Remote UE1. For another example, the terminal device is Remote UE1, the first target information indicates the relay terminal Relay UE2 directly connected to Remote UE1 on the U2U relay link, one second target information indicates the remote terminal Remote UE4 on the U2U relay link Relaylink1 reachable through Relay UE2, and another second target information indicates the remote terminal Remote UE5 on the U2U relay link Relaylink2 reachable through Relay UE2.

[0111] In some examples, a resource request message may include one type of target information, such as first target information. Multiple resource request messages may include multiple types of target information. For example, if the terminal device is Relay UE2, the first target information in one resource request message indicates the remote terminal Remote UE3 on the U2U relay link Relaylink1. For another example, if the terminal device is Remote UE1, the first target information in one resource request message indicates the remote terminal Remote UE4 on the U2U relay link Relaylink1, and the first target information in another resource request message indicates the relay terminal Relay UE2 directly connected to Remote UE1.

[0112] In an embodiment of the present application, one or more target information in a resource request message sent by a terminal device in a sidelink facilitates more accurate determination of sidelink-related information, thereby providing a suitable configuration for the terminal device in the sidelink. For example, one or more target information in a resource request message sent by a terminal device in a U2U relay link facilitates more accurate determination of the topology of the U2U relay link, thereby providing a suitable configuration for the terminal device.

[0113] In an embodiment of the present application, the resource request information in the first information may include one or more of the following information: first target information, second target information, capability information, QoS flow information, role information, RLC channel information, frequency information, synchronization reference type information, etc. For example, a UE in a U2U relay link may report to the network information such as different identities of different UEs in the U2U relay link for different links and the topology of the U2U relay link, so that the network can better provide resources and / or parameter configuration for the UE.

[0114] In the embodiment of the present application, the first information may have multiple formats, examples of which are as follows.

[0115] In one embodiment, the terminal device is a first remote terminal, and the second remote terminal is a counterpart remote terminal (or counterpart remote terminal) on a terminal-to-terminal U2U relay link where the first remote terminal is located. In this embodiment of the present application, the terminal device may be a first remote terminal. If the first remote terminal can communicate with one or more second remote terminals via a U2U relay link, the first remote terminal may send a first message including one or more resource request information to the network device.

[0116] In one embodiment, in the first format, the first target information of the resource request message may include the identifier of the second remote terminal. For example, a resource request message in the SUI may correspond to a relay link, and different resource requests may correspond to different relay links. The first target information in one resource request message may include the identifier of the second remote terminal Remote UE4 on the U2U relay link Relaylink1, while the first target information in another resource request message may include the identifier of the second remote terminal Remote UE6 on the U2U relay link Relaylink2.

[0117] In one embodiment, in the first format, one of the second target information in the resource request information includes the identifier of a relay terminal on the U2U relay link where the first remote terminal is located. In this embodiment of the present application, if the first target information in a resource request information includes the identifier of a second remote terminal on a U2U relay link, one of the second target information in the resource request information may include the identifier of a relay terminal on the U2U relay link. If the U2U relay link is a multi-hop relay link, the resource request information may include multiple pieces of second target information, and different pieces of second target information may include the identifiers of different relay terminals on the U2U relay link.

[0118] In one embodiment, in the first format, the second target information includes the identifier of the relay terminal directly connected to the first remote terminal. For example, a U2U relay link Relaylink1 includes a first remote terminal Remote UE1, relay terminals RelayUE2 and RelayUE3, and a second remote terminal Remote UE4. Remote UE1 sends a SUI to the network device. If the first target information in the SUI includes the identifier of Remote UE4, the second target information may include information such as the identifier of the relay terminal RelayUE2 directly connected to Remote UE1.

[0119] In one implementation, if the first format is adopted, the destination address information in the buffer status report (BSR) MAC CE is determined based on the identifier of the relay terminal.

[0120] In one implementation, if the first format is used, the terminal device reports the first information in the order of the remote terminals associated with the same relay terminal.

[0121] For example, if the relay terminals associated with remote UE1 and UE3 are both Relay1, and the relay UE associated with remote UE2 is Relay2, the resource request information containing remote UE1 and remote UE3 can be reported in an associated manner, and then the resource request information containing remote UE2 can be reported. One reporting order can be the resource request information containing remote UE1, the resource request information containing remote UE3, and the resource request information containing remote UE2.

[0122] In one embodiment, in the first format, the second target information also includes the capability information of the relay terminal. In an embodiment of the present application, in a resource request message, the identifier of the relay terminal and the capability information of the relay terminal can be jointly reported through the second target information. For example, the first remote terminal Remote UE1 in a U2U relay link Relaylink1 sends a SUI to a network device. If the first target information in the resource request information included in the SUI includes the identifier of Remote UE4, the second target information may include the identifier of the relay terminal RelayUE2 directly connected to Remote UE1 on the U2U relay link Relaylink1 and the capability information of RelayUE2.

[0123] In one embodiment, in the first format, the resource request information further includes capability information of the second remote terminal, that is, capability information of the remote terminal indicated by the first target information in the resource request information.

[0124] In one embodiment, the terminal device is a first remote terminal. In the second format, the first target information in the resource request information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located. For example, a resource request information in the SUI may correspond to a direct link between the first remote terminal and a relay UE, and different resource request information may correspond to direct links between the first remote terminal and different relays. The first target information in one resource request information includes an identifier of the relay terminal Relay UE2 directly connected to the first remote terminal, and the first target information in another resource request information includes an identifier of the relay terminal Relay UE4 directly connected to the first remote terminal.

[0125] In one embodiment, in the second format, the first target information of the resource request information includes the identifier of the relay terminal directly connected to the first remote terminal. For example, a U2U relay link Relaylink3 includes a first remote terminal Remote UE1, relay terminals RelayUE2, RelayUE3, RelayUE4, and a second remote terminal Remote UE5. Remote UE1 sends a SUI to the network device. If the first target information of the resource request information in the SUI includes the identifier of the relay terminal RelayUE2 directly connected to Remote UE3,

[0126] In one embodiment, in the second format, one or more second target information in the resource request information includes an identifier of the second remote terminal. The second remote terminal is the other remote terminal on the U2U relay link where the first remote terminal is located. The second remote terminal may also be the other remote terminal to which the first information reaches through the relay terminal in the first target information, or the other remote terminal of the U2U link associated with the relay UE. For example, a U2U relay link Relaylink3 includes a first remote terminal Remote UE1, RelayUE2 directly connected to Remote UE1, and a second remote terminal Remote UE5. The first remote terminal Remote UE1 sends a SUI to the network device. If the first target information in the SUI includes the identifier of RelayUE2 directly connected to Remote UE1, the second target information may include the identifier of the second remote terminal Remote UE5 on Relaylink3.

[0127] In one embodiment, in the second format, the second target information also includes capability information of the second remote terminal. In an embodiment of the present application, in a resource request message, the identifier of the second remote terminal and the capability information of the second remote terminal can be jointly reported via the second target information. For example, if the first remote terminal Remote UE1 in a U2U relay link Relaylink3 sends a SUI to a network device, and the first target information in the SUI includes the identifier of a relay terminal, such as RelayUE2, the second target information may include the identifier of the second remote terminal Remote UE5 associated with RelayUE2 on Relaylink3 and the capability information of Remote UE5.

[0128] In one embodiment, in the second format, the resource request information further includes capability information of the relay terminal, that is, capability information of the relay terminal indicated by the first target information in the resource request information.

[0129] In one embodiment, in the first format and / or the second format described above, the resource request information further includes QoS flow information, where the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal. For example, if the remote terminal to which Remote UE1 is connected on a U2U relay link, such as Relaylink1, is Remote UE4 in the above example, the QoS flow information in the resource request information may be QoS flow information between Remote UE1 and Remote UE4. For another example, if the remote terminal to which Remote UE1 is connected on a U2U relay link, such as Relaylink3, is Remote UE5 in the above example, the QoS flow information in the resource request information may be QoS flow information between Remote UE1 and Remote UE5.

[0130] In one embodiment, the resource request information also includes indication information for indicating the second remote terminal associated with the QoS flow information. In an embodiment of the present application, if the first target information in the resource request information includes the identifier of the relay terminal, and the resource request information also includes QoS flow information, then the resource request information may also indicate the identifier of the second remote terminal associated with the QoS flow information. For example, the first target information in a resource request information includes the identifier of a relay terminal such as RealyUE2. If the QoS flow information in the resource request information is QoS flow information between the first remote terminal Remote UE4 and the second remote terminal Remote UE4, then the resource request information also includes an indication information for indicating that the QoS flow information is associated with Remote UE4.

[0131] In one embodiment, in the first format and / or the second format described above, the radio link control (RLC) channel information in the resource request information is the RLC channel information between the first remote terminal and the relay terminal. For example, a U2U relay link Relaylink1 includes a first remote terminal Remote UE1, relay terminals RelayUE2 and RelayUE3, and a second remote terminal Remote UE4. In a resource request message in the SUI sent by Remote UE1 to the network device, the first target information includes an identifier of RelayUE2 or Remote UE4. In this case, the RLC channel information in the resource request information can be the RLC channel information between Remote UE1 and RelayUE2.

[0132] In one embodiment, the terminal device is a relay terminal, and in the third format, the resource request information includes the identifier of the remote terminal for which the relay terminal provides relay service. For example, the relay terminal RelayUE2 on the U2U relay link Relaylink1 sends a SUI to the network device. In one case, the first target information in a resource request information in the SUI includes the identifier of the first remote terminal Remote UE1 directly connected to RelayUE2 on the U2U relay link Relaylink1. In another case, the first target information in a resource request information in the SUI includes the identifier of the second remote terminal Remote UE4 directly connected to RelayUE2 on the U2U relay link Relaylink1.

[0133] In one embodiment, in the third format, the resource request information includes the capability information of the remote terminal. For example, the relay terminal RelayUE2 on the U2U relay link Relaylink1 sends a SUI to the network device. In one case, the first target information in a resource request message in the SUI includes the identifier of the first remote terminal Remote UE1, and the resource request message may also include the capability information of Remote UE1. In another case, the first target information in a resource request message in the SUI includes the identifier of the second remote terminal Remote UE4, and the resource request message may also include the capability information of Remote UE4.

[0134] In one embodiment, in the third format, the resource request information also includes QoS flow information, which is QoS flow information between two remote terminals for which the relay terminal provides relay services. For example, the relay terminal RelayUE2 on the U2U relay link Relaylink1 sends a SUI to the network device. In one case, the first target information in a resource request message in the SUI includes the identifier of the first remote terminal Remote UE1, and the resource request message may also include the QoS flow information between the Remote UE1 and Remote UE4. In another case, the first target information in a resource request message in the SUI includes the identifier of the second remote terminal Remote UE4, and the resource request message may also include the QoS flow information between the Remote UE1 and Remote UE4.

[0135] In one embodiment, in the third format, the RLC channel information in the resource request information is the RLC channel information between the relay terminal and the remote terminal. For example, refer to the example of the U2U relay link Relaylink1 described above. In a resource request information in the SUI sent by RelayUE2 on Relaylink1 to the network device, if the first target information includes Remote UE1, the RLC channel information in the resource request information may be the RLC channel information between RelayUE2 and Remote UE1; if the first target information includes the identifier of Remote UE4, the RLC channel information in the resource request information may be the RLC channel information between RelayUE2 and Remote UE4.

[0136] In one embodiment, the method further includes: the relay terminal reporting a Service Data Adaptation Protocol (SDAP) layer configuration from the remote terminal to the network device. For example, the terminal device sending the first information is a relay device. The relay device can receive the SDAP layer configuration sent by the remote device for which it provides relay service, and report the SDAP layer configuration to the network device. The SDAP layer configuration can be in the first information, such as the SUI.

[0137] In the first, second, or third formats described above, a resource request message can be understood as an information element (IE). Therefore, the UE can report information related to the remote UE and / or relay UE associated with the UE on a U2U relay link to the network device through an IE in the SUI, thereby providing the network with a more accurate topology of the U2U relay link, thereby facilitating configuration of more appropriate resources for the UE with respect to the U2U relay link.

[0138] In one embodiment, in the first format, the second format, or the third format, the resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal. The resource request information in the first information may explicitly or implicitly indicate the role of the terminal device sending the first information.

[0139] In one embodiment, the resource request information also includes the role information of the terminal device. For example, the resource request information may include a terminal role indication field, which indicates the terminal role through one or more bits. For example, in a SUI, a value of 1 in the terminal role indication field indicates that the role of sending the SUI is a remote terminal, and a value of 0 indicates that the role of sending the SUI is a relay terminal. For another example, in a SUI, a value of 11 in the terminal role indication field indicates that the role of sending the SUI is the first remote terminal, a value of 10 indicates that the role of sending the SUI is the second remote terminal, a value of 01 indicates that the role of sending the SUI is the relay terminal RelayUE1, and a value of 01 indicates that the role of sending the SUI is the relay terminal RelayUE2.

[0140] In one embodiment, when the first target information includes an identifier of the second remote terminal and the second target information includes an identifier of the relay terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0141] In one embodiment, when the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

[0142] In one embodiment, when the first target information includes an identifier of the relay terminal and the second target information in the resource request information is an identifier of the second remote terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0143] In one embodiment, in the fourth format, the first information includes first resource request information, second resource request information, and third resource request information. The first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association between the single-hop target information and the end-to-end target information. The single-hop target information may indicate target information of a terminal directly connected to the terminal device sending the first information. For example, if the terminal sending the first information is a first remote terminal, the single-hop target information is used to indicate a relay UE in a U2U relay link where the first remote terminal is located. The end-to-end target information may include information of the other remote terminal in the U2U relay link where the first remote terminal is located.

[0144] In an embodiment of the present application, the first resource request information, the second resource request information, and the third resource request information may be different IEs in the first information, respectively. For example, the first resource request information is the first IE, the second resource request information is the second IE, and the third resource request information is the third IE. For example, multiple resource request information in the SUI may correspond to a U2U relay link. The first target information in the first resource request information includes relevant information such as the identifier of the second remote terminal Remote UE4 on the U2U relay link Relaylink1. The first target information in the second resource request information includes relevant information such as the identifier of the relay terminal Relay UE2 on the U2U relay link Relaylink1. The third resource request information includes the association relationship between Remote UE4 and Relay UE2.

[0145] In one embodiment, the single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

[0146] In an embodiment of the present application, the identifier of the relay terminal in the single-hop target information may be the identifier of the relay terminal directly connected to the terminal device that sent the first information. Correspondingly, the capability information of the relay terminal may also be the capability information of the relay terminal directly connected to the terminal device that sent the first information.

[0147] In one embodiment, the end-to-end target information includes at least one of the following:

[0148] an identifier of the second remote terminal;

[0149] QoS flow information, QoS flow information between the first remote terminal and the second remote terminal;

[0150] Indication information, used to indicate a second remote terminal associated with the QoS flow information;

[0151] Capability information of the second remote terminal.

[0152] In this embodiment of the present application, the identifier of the second remote terminal in the end-to-end target information may be the identifier of the other remote terminal in the U2U relay link. Correspondingly, the capability information of the second remote terminal may also be the capability information of the other remote terminal in the relay link.

[0153] In one embodiment, the association between the above-mentioned single-hop target information and the end-to-end target information includes the association between the identifier of the relay terminal and the identifier of the second remote terminal, and / or the association between the identifier of the first resource request information and the identifier of the second resource request information. For example, the single-hop target information of the first resource request information R1 includes the identifier of RelayUE2, and the end-to-end target information of the second resource request information R2 includes the identifier of RemoteUE4. The third resource request information may include the association between the identifier of RelayUE2 and the identifier of RemoteUE4. And / or, the third resource request information may include the association between the identifier of R1 and the identifier of R2.

[0154] In one embodiment, the RLC channel information may include RLC mode information and / or packet delay budget (PDB) information for each RLC channel. The PDB information is determined based on terminal implementation and / or segmented QoS information. For example, the segmented QoS information may include QoS information corresponding to each hop segmented based on the overall QoS information in the U2U relay link.

[0155] In one implementation, the QoS flow information may include the QoS information currently required to be reported and / or the segmented QoS information.

[0156] In one embodiment, the identifier of the remote terminal is at least one of the following: a layer 2 identifier, a local identifier / UE identifier (Local ID / UE ID). For example, the Local ID / UE ID can be an ID assigned to the relay UE, or an 8-bit UE identifier carried in the SRAP packet header.

[0157] In one implementation, the identifier of the relay terminal is a layer 2 identifier.

[0158] In one embodiment, the resource request information further includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies, and carriers that the terminal device is interested in for U2U relay link communication.

[0159] In one embodiment, the resource request information further includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier for U2U relay link communication. The synchronization reference type may include Global Navigation Satellite System (GNSS), gNB, eNB, synchronous UE, etc.

[0160] In one embodiment, the first information further includes radio link failure (RLF) information. For example, the first information includes RLF information and one or more resource request information.

[0161] In one embodiment, when the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect link of the terminal device. For example, in the SUI sent by the first remote terminal RemoteUE1 to the network device, the RLF information may indicate the RLF of the direct link between RemoteUE1 and the relay terminal RelayUE2; and / or, the RLF information may indicate the RLF of the indirect link between RemoteUE1 and the second remote terminal RemoteUE4.

[0162] In one embodiment, when the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link. For example, in the SUI sent by the relay terminal RelayUE2 to the network device, the RLF information may indicate the RLF of the direct link between the relay terminal RelayUE2 and the first remote terminal RemoteUE1; or the RLF information may indicate the RLF of the indirect link between the RelayUE2 and another relay terminal RelayUE3.

[0163] In one embodiment, the RLF information is used to indicate the target address of the RLF and / or the cause of the RLF. For example, if the RLF information indicates an RLF in a direct link between RemoteUE1, which sends the SUI, and relay terminal RelayUE2, the target address of the RLF may be RelayUE2. If the RLF information indicates an RLF in a non-direct link between RemoteUE1, which sends the SUI, and a second remote terminal RemoteUE4, the target address of the RLF may be RemoteUE4.

[0164] In one embodiment, the first information also includes radio link control (RLC) channel information, where the RLC channel information corresponds to one or more carriers. In this embodiment of the present application, the UE can send sidelink transmissions to other UEs via the one or more carriers, i.e., it can support carrier aggregation (CA), and the signaling format for indicating RLC channel information after supporting carrier aggregation is enhanced.

[0165] An example of a signaling format indicating an RLC channel is as follows:

[0166] An example of the enhanced signaling format for indicating RLC channels after supporting CA is as follows:

[0167] Among them, the newly added mode list parameter sl-ModeList-r1X can indicate the RLC channel information of the corresponding one or more carriers.

[0168] FIG9 is a schematic flow chart of a communication method 900 according to an embodiment of the present application. The method can optionally be applied to the systems shown in FIG1 to FIG7 , but is not limited thereto. The method includes at least part of the following contents.

[0169] S910. The network device receives first information, which includes one or more resource request information of the terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in the side link.

[0170] In one embodiment, the terminal device is a first remote terminal, the first target information includes an identifier of a second remote terminal, and the second remote terminal is a counterpart remote terminal on a terminal-to-terminal U2U relay link where the first remote terminal is located.

[0171] In one embodiment, the second target information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located.

[0172] In one embodiment, the second target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0173] In one implementation, the target address information in the buffer status report BSR MAC CE is determined based on the identifier of the relay terminal.

[0174] In one implementation, the terminal device reports the first information in the order of remote terminals associated with the same relay terminal.

[0175] In one implementation, the second target information further includes capability information of the relay terminal.

[0176] In one embodiment, the resource request information further includes capability information of the second remote terminal.

[0177] In one embodiment, the terminal device is a first remote terminal, and the first target information includes an identifier of a relay terminal on a U2U relay link where the first remote terminal is located.

[0178] In one embodiment, the first target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0179] In one embodiment, the one or more second target information includes an identifier of a second remote terminal, where the second remote terminal is a counterpart remote terminal on the U2U relay link where the first remote terminal is located.

[0180] In one embodiment, the second target information further includes capability information of the second remote terminal.

[0181] In one implementation, the resource request information further includes capability information of the relay terminal.

[0182] In one embodiment, the resource request information further includes quality of service (QoS) flow information, where the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal.

[0183] In one embodiment, the resource request information further includes indication information for indicating the second remote terminal associated with the QoS flow information.

[0184] In one embodiment, the radio link control RLC channel information in the resource request information is RLC channel information between the first remote terminal and the relay terminal.

[0185] In one embodiment, the terminal device is a relay terminal, and the resource request information includes an identifier of a remote terminal for which the relay terminal provides relay service.

[0186] In one embodiment, the resource request information includes capability information of the remote terminal.

[0187] In one embodiment, the resource request information further includes QoS flow information, where the QoS flow information is QoS flow information between two remote terminals for which the relay terminal provides relay services.

[0188] In one implementation, the RLC channel information in the resource request information is RLC channel information between the relay terminal and the remote terminal.

[0189] In one embodiment, the method further includes: the relay terminal reporting the Service Data Adaptation Protocol (SDAP) layer configuration from the remote terminal to the network device.

[0190] In one embodiment, the resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal.

[0191] In one embodiment, the resource request information also includes role information of the terminal device.

[0192] In one embodiment, when the first target information includes an identifier of the second remote terminal and the second target information includes an identifier of the relay terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0193] In one embodiment, when the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

[0194] In one embodiment, when the first target information includes an identifier of the relay terminal and the second target information in the resource request information is an identifier of the second remote terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0195] In one embodiment, the first information includes first resource request information, second resource request information and third resource request information, the first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association between the single-hop target information and the end-to-end target information.

[0196] In one embodiment, the single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

[0197] In one embodiment, the end-to-end target information includes at least one of the following:

[0198] an identifier of the second remote terminal;

[0199] QoS flow information, QoS flow information between the first remote terminal and the second remote terminal;

[0200] Indication information, used to indicate a second remote terminal associated with the QoS flow information;

[0201] Capability information of the second remote terminal.

[0202] In one embodiment, the association relationship includes an association relationship between the identifier of the relay terminal and the identifier of the second remote terminal, and / or an association relationship between the identifier of the first resource request information and the identifier of the second resource request information.

[0203] In one embodiment, the RLC channel information includes RLC mode information and / or PDB information of each RLC channel, and the PDB information is determined based on QoS information implemented and / or segmented by the terminal.

[0204] In one implementation, the QoS flow information includes the QoS information currently required to be reported and / or the segmented QoS information.

[0205] In one embodiment, the identifier of the remote terminal is at least one of the following: a layer 2 identifier and a local identifier.

[0206] In one implementation, the identifier of the relay terminal is a layer 2 identifier.

[0207] In one embodiment, the resource request information further includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies, and carriers that the terminal device is interested in for terminal-to-terminal U2U relay link communication.

[0208] In one embodiment, the resource request information further includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U relay link communication.

[0209] In one implementation, the first information also includes radio link failure (RLF) information.

[0210] In one embodiment, when the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect link of the terminal device.

[0211] In one embodiment, when the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link.

[0212] In one implementation, the RLF information is used to indicate a target address where the RLF occurs and / or a reason why the RLF occurs.

[0213] In one embodiment, the first information further includes RLC channel information corresponding to one or more carriers, and the RLC channel information includes RLC channel mode information corresponding to the one or more carriers.

[0214] For a specific example of the network device executing method 900 of this embodiment, reference can be made to the relevant description of the network device, such as a base station, in the above method 800 , which will not be repeated here for the sake of brevity.

[0215] In the U2U relay link (abbreviated as U2U relay, U2U link, or U2U) of an embodiment of the present application, when the UE reports U2U relay link related information to the network, it may indicate one or more of the following information contents to obtain network resource scheduling or radio bearer related configuration:

[0216] UE role (U2U relay UE or U2U remote UE);

[0217] The remote UE of the U2U link;

[0218] Relay UE of the U2U link.

[0219] In the embodiment of the present application, the manner in which the above information is carried in the report message may include the following:

[0220] 1. Reporting of the remote UE (UE ID) and relay UE (UE ID)

[0221] (1) Report at the granularity of each remote UE (U2U link), and further carry the relay UE information of the U2U relay link in each reporting entry;

[0222] (2) Reporting is done at the granularity of each relay UE, and each reporting entry further carries the information of the remote UE associated with the relay UE;

[0223] (3) Each relay UE and the other remote UE report separately, that is, use independent IE to report.

[0224] 2. Reporting of UE roles

[0225] (1) Explicit reporting mode, that is, for each reporting entry, explicitly indicate the UE role of this UE for the link;

[0226] (2) Implicit reporting method, that is, the UE role of the UE is implicitly indicated through the specific content of other reported information.

[0227] Example 1: The same IE can be used for both end-to-end information and per-hop information in the SUI. The information in the IE may be different for different types of UEs sending SUIs. The following example shows:

[0228] Remote UE: The target remote UE ID is used as the reporting granularity (index) in the SUI, and the relay UE corresponding to the remote UE sending the SUI is reported in the SUI, as well as information such as the UE role (explicit / implicit).

[0229] Relay UE: The SUI uses two remote UE IDs as the reporting granularity (index) and indicates information such as the UE role (explicit / implicit).

[0230] For example, the first information may carry one or more of the following information:

[0231] 1. Target UE ID

[0232] (1) For a remote UE, the target UE ID can be the ID (L2 ID) of the peer / target remote UE.

[0233] (2) For a relay UE, the target UE ID may be the ID of the remote UE (L2 ID).

[0234] 2.UE Role

[0235] (1) For a remote UE, the UE role is a remote UE, such as a U2U Relay remote UE, specifically, an L2 U2U Relay remote UE or an L3 U2U Relay remote UE.

[0236] (2) For a relay UE, the UE role is a relay UE, such as a U2U Relay UE, specifically, an L2 U2U Relay UE or an L3 U2U Relay UE.

[0237] 3.QoS flow information

[0238] (1) For a remote UE, the QoS flow information may be the QoS flow between the remote UE and the peer / target UE.

[0239] (2) For a relay UE, the QoS flow information is the QoS flow between the two remote UEs providing relay service. For example, the relay UE can report the two remote UE IDs associated with the QoS flow so that the network knows the remote UEs corresponding to the relay UE. Furthermore, the relay UE can also report the SDAP layer configuration from the remote UE to the network.

[0240] 4. RLC channel information

[0241] (1) For the remote UE, the RLC channel information is the RLC channel information (RLC mode information) between the remote UE and the relay UE;

[0242] (2) For the relay UE, the RLC channel information is the RLC channel information (RLC mode information) between the relay UE and the remote UE.

[0243] 5. One (or more) relay UE ID information: This information is reported only when the UE is a remote UE, and the reported content is the relay UE associated with the U2U link (the target remote UE).

[0244] 6.UE capability information

[0245] (1) For a remote UE, the capability information is the capability information of the other (peer / target) remote UE;

[0246] (2) For a relay UE, the capability information is the capability information of the provided remote UE.

[0247] 7. Relay UE capability information: This information can be reported only when the UE sending the SUI is a remote UE. The content reported is the capabilities of the relay UE associated with the U2U link (the target remote UE). This information and the relay UE ID information can be reported jointly.

[0248] 8. Frequency information: at least one of the frequency domain resources, frequencies, and carriers used for U2U link communication that the UE is interested in.

[0249] 9. Synchronization reference type information, the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U link communication.

[0250] A schematic signaling structure of the first information is as follows:

[0251] Among them, the target UE ID can be sl-DestinationIdentityU2U-rxx, which may include the remote UE ID. The UE role can be ue-Type-r17. QoS flow information can be sl-QoS-InfoU2UList-rxx. RLC channel information can be sl-RLC-ModeIndicationU2UList-rxx. UE capability information can be sl-CapabilityInformationU2USidelink-rxx. A relay UE information can be SL-U2URelayIndication-rxx, sl-DestinationIdentityU2URelay-rxx in SL-U2URelayIndication-rxx can represent a relay UE ID information, and sl-CapabilityInformationSidelinkU2URelay-rxx in SL-U2URelayIndication-rxx can represent the capability information of the relay UE. The information of multiple relay UEs can be represented by sl-U2URelayIndicationList-rxx. sl-U2URelayIndicationList-rxx may include multiple SL-U2URelayIndication-rxx. Frequency information may be sl-TxInterestedFreqList-rxx. Synchronization reference type information may be sl-TypeTxSyncU2UList-rxx.

[0252] In the above example, the role of the UE sending the SUI can be implicitly indicated. For example, if sl-U2URelayIndication-rxx is present in the SUI, it indicates that the UE sending the SUI (on this U2U link) is a remote UE, otherwise it is a relay UE.

[0253] In addition, sl-DestinationIdentityU2U-rxx, sl-QoS-InfoU2UList-rxx, and sl-CapabilityInformationU2USidelink-rxx can indicate end-to-end related information (except the target UE ID when reported by the relay UE). sl-U2URelayIndicationList-rxx, sl-RLC-ModeIndicationU2UList-rxx, sl-TypeTxSyncU2UList-rxx, sl-TxInterestedFreqList-rxx, and SL-U2URelayIndication-rxx indicate information related to each hop.

[0254] In this case, since the SUI of the remote UE is indexed by the other remote UE, and the target address identifier (serial number) in the BSR must be based on the relay UE, the remote UE needs to report the SUI in the order of the remote UEs associated with the same relay UE to synchronize the BSR index between the network and the remote UE, as shown in Figure 10.

[0255] Example 2: The same IE is used for both end-to-end information and per-hop information in the SUI. The information in the IE may be different for different types of UEs sending SUIs. The example is as follows:

[0256] Remote UE: The relay terminal ID is used as the reporting granularity (index) in the SUI, and one or more remote UEs corresponding to / associated with the remote UE sending the SUI are reported in the SUI, as well as information such as the UE role (explicit / implicit).

[0257] Relay UE: The SUI uses two remote UE IDs as the reporting granularity (index) and indicates information such as the UE role (explicit / implicit).

[0258] For example, the first information may carry one or more of the following information:

[0259] 1. Target UE ID

[0260] (1) For the remote UE, the target UE ID is the relay UE ID (L2 ID);

[0261] (2) For a relay UE, the target UE ID is the ID of the remote UE (L2 ID). (See Example 1)

[0262] 2.UE role (see Example 1)

[0263] (1) For a remote UE, the UE role is a remote UE, such as a U2U Relay remote UE, specifically, an L2 U2U Relay remote UE or an L3 U2U Relay remote UE.

[0264] (2) For a relay UE, the UE role is a relay UE, such as a U2U Relay UE, specifically, an L2 U2U Relay UE or an L3 U2U Relay UE.

[0265] 3.QoS flow information

[0266] (1) For a remote UE, the QoS flow information is the QoS flow between the remote UE and the peer / target UE. The QoS flow information must specify the peer / target UE to which the QoS flow is associated.

[0267] (2) For a relay UE, the QoS flow information is the QoS flow between the two remote UEs providing the relay service. See Example 1.

[0268] 4. RLC channel information

[0269] (1) For the remote UE, the RLC channel information is the RLC channel information (RLC mode information) between the remote UE and the relay UE;

[0270] (2) For the relay UE, the RLC channel information is the RLC channel information (RLC mode information) between the relay UE and the remote UE.

[0271] 5.UE capability information

[0272] (1) For the remote UE, the capability information is the capability information of the relay UE;

[0273] (2) For a relay UE, the capability information is the capability information of the remote UE for which the relay terminal provides relay services.

[0274] 6. Peer / target remote UE ID information (one or more): This information can be reported only when the UE sending the SUI is a remote UE. The reported content is the peer / target remote UE ID information associated with / reachable by the relay UE.

[0275] 7. Peer / target remote UE capability information: This information can be reported only when the UE sending the SUI is a remote UE. The reported content is the capability information of the peer / target remote UE associated with / reachable by the relay UE corresponding to the target UE ID.

[0276] 8. Frequency information: at least one of the frequency domain resources, frequencies, and carriers used for U2U link communication that the UE is interested in.

[0277] 9. Synchronization reference type information, the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U link communication.

[0278] The signaling structure is as follows:

[0279] The target UE ID may be sl-DestinationIdentityU2U-rxx. If the UE role is a remote UE, sl-DestinationIdentityU2U-rxx may include the relay UE ID. The UE role may be ue-Type-r17. QoS flow information may be sl-QoS-InfoU2UList-rxx. RLC channel information may be sl-RLC-ModeIndicationU2UList-rxx. UE capability information may be sl-CapabilityInformationU2USidelink-rxx, which may include the capability information of the relay UE indicated by sl-DestinationIdentityU2U-rxx. The other party's remote UE information can be SL-U2UTargetIndication-rxx, the sl-DestinationIdentityU2UTarget-rxx in the SL-U2UTargetIndication-rxx can represent the other party's remote UE ID information, and the sl-CapabilityInformationSidelinkU2UTarget-rxx in the SL-U2UTargetIndication-rxx can represent the capability information of the other party's remote UE. The information of multiple other party's remote UEs can be represented by sl-U2UTargetIndicationList-rxx. The sl-U2UTargetIndicationList-rxx can include multiple sl-U2UTargetIndication-rxx. The frequency information can be sl-TxInterestedFreqList-rxx. The synchronization reference type information can be sl-TypeTxSyncU2UList-rxx.

[0280] In the above example, the role of the UE sending the SUI can be implicitly indicated. For example, if SL-U2UTargetIndication-rxx is present in the SUI, it indicates that the UE sending the SUI (on this U2U link) is a remote UE, otherwise it is a relay UE.

[0281] In addition, sl-U2UTargetIndicationList-rxx, SL-U2UTargetIndication-rxx, and sl-QoS-InfoU2UList-rxx can indicate end-to-end related information (except the target UE ID reported by the relay UE). sl-DestinationIdentityU2U-rxx, sl-RLC-ModeIndicationU2UList-rxx, sl-TypeTxSyncU2UList-rxx, sl-TxInterestedFreqList-rxx, and sl-CapabilityInformationU2USidelink-rxx indicate per-hop related information.

[0282] Example 3: The SUI uses different IEs for end-to-end information, per-hop information, and relay UE and remote UE. The example is as follows:

[0283] Remote UE: The relay terminal ID is used as the reporting granularity (index) in the SUI, and one or more remote UEs corresponding to / associated with the remote UE sending the SUI are reported in the SUI, and the UE role is indicated (implicitly).

[0284] Relay UE: The SUI uses two remote UE IDs as the reporting granularity (index) and indicates the UE role (implicit).

[0285] In one example, the first information of the Remote UE may carry information through the following multiple UEs:

[0286] The first IE (remote UE carries each hop information) is as follows:

[0287] 1. Target UE ID, which may be the ID of the relay UE (L2 ID);

[0288] 2. RLC channel information, which may be RLC channel information (RLC mode information) between the relay UE and the relay UE;

[0289] 3. UE capability information, which may be the capability information of the relay UE;

[0290] 4. Frequency information: at least one of the frequency domain resources, frequencies, and carriers used for U2U link communication that the UE is interested in.

[0291] Synchronization reference type information, the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U link communication.

[0292] The second IE (remote UE carries end-to-end information) is exemplified as follows:

[0293] 1. Target UE ID, which is the ID of the remote UE (L2 ID).

[0294] 2. QoS flow information, which is the QoS flow between the peer / target remote UE and the QoS flow information must indicate the peer / target remote UE to which the QoS flow is associated;

[0295] 3. UE capability information, which is the capability information of the remote UE of the terminal;

[0296] 4.UE capability information, the other party’s remote UE capability information.

[0297] The third IE (the remote UE carries the association relationship information between the end-to-end information and each hop information): the association relationship can be indexed by the target UE ID in the first IE and the second IE, or the first IE and the second IE identification information can be added and the added identification information can be used for indexing.

[0298] The schematic signaling structure of the first IE, the second IE, and the third IE in a SUI is as follows:

[0299] Among them, the first IE is SL-TxResourceReqCommU2URelayInfo-rxx, the second IE is SL-TxResourceReqCommU2UTargetInfo-rxx, and the third IE is SL-TxResourceReqCommU2UInfoIDList-rxx.

[0300] Another implementation method is to add identification information of the first IE and the second IE, and index by the identification information.

[0301] Among them, the first IE is SL-TxResourceReqCommU2URelayInfo-rxx, the second IE is SL-TxResourceReqCommU2UTargetInfo-rxx, and the third IE is SL-TxResourceReqCommU2UInfoIDList-rxx. The first IE includes the identifier of the first IE, i.e., sl-TxResourceReqCommU2UTargetInfoID-rxx, and the second IE includes the identifier of the second IE, i.e., sl-TxResourceReqCommU2UTargetInfoID-rxx.

[0302] Example 4: The first information sent by the relay UE carries an IE, for example: the SUI sent by the UE carries a fourth IE, and the fourth IE may include one or more of the following information.

[0303] 1. Target UE ID, which is the ID of the remote UE (L2 ID).

[0304] 2. QoS flow information, which is the QoS flow between two remote UEs providing relay services to the relay UE. See Example 1.

[0305] 3. RLC channel information, which is RLC channel information between the relay UE and the remote UE (eg, RLC mode information).

[0306] 4. UE capability information, which is the capability information of the remote UE for which the relay UE provides relay service.

[0307] 5. Frequency information: the frequency domain resources / frequencies / carriers that the UE is interested in for U2U link communication.

[0308] 6. Synchronization reference type information: the synchronization reference type used on the frequency domain resources / frequency / carrier of the U2U link communication.

[0309] A schematic signaling structure of the fourth IE is as follows:

[0310] The target UE ID may be sl-DestinationIdentityU2U-rxx. The RLC channel information may be sl-RLC-ModeIndicationU2UList-rxx. The synchronization reference type information may be sl-TypeTxSyncU2UList-rxx. The frequency information may be sl-TxInterestedFreqList-rxx. The UE capability information may be sl-CapabilityInformationU2USidelink-rxx. The QoS flow information may be sl-QoS-InfoU2UList-rxx.

[0311] Example 5: When PC5 RLF is indicated in the SUI, it indicates whether the RLF occurs per hop or E2E RLF

[0312] (1) For a remote UE, when indicating RLF, it indicates RLF of both the direct link and the indirect link:

[0313] RLF occurs with relay UE / directly connected UE: indicates the target address (L2 ID) where RLF occurs and the cause of RLF;

[0314] RLF occurs with the other remote UE: indicates the target address (L2 ID) where the RLF occurs and the cause of the RLF;

[0315] (2) For a relay UE, when indicating RLF, it only indicates the RLF of the direct link: it indicates the target address (L2 ID) where the RLF occurs and the reason for the RLF.

[0316] The above examples of the present application can solve the problem that the network cannot know the different identities of different UEs for different links in the U2U relay link and the topology of the U2U relay link, so that the network can better provide resources and parameter configuration for the UE.

[0317] In addition, for the case of multiple relay UEs in Example 1 (multipath U2U relay that may be introduced in the future), when determining the BSR index, the rule example is as follows:

[0318] (1) In the order in which the relay UE ID first appears;

[0319] (2) Add an indication field in the SUI to indicate the order of the relay UE.

[0320] The above examples can also be used in different ways in different modes, such as mode 2 using example 1 and mode 1 using example 2.

[0321] Figure 11 is a schematic block diagram of a terminal device 1100 according to an embodiment of the present application. The terminal device 1100 may include: a sending unit 1101, configured to send first information, where the first information includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a sidelink.

[0322] In one embodiment, the terminal device is a first remote terminal, the first target information includes an identifier of a second remote terminal, and the second remote terminal is a counterpart remote terminal on a terminal-to-terminal U2U relay link where the first remote terminal is located.

[0323] In one embodiment, the second target information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located.

[0324] In one embodiment, the second target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0325] In one implementation, the target address information in the buffer status report BSR MAC CE is determined based on the identifier of the relay terminal.

[0326] In one embodiment, the terminal device reports the first information in the order of remote terminals associated with the same relay terminal.

[0327] In one implementation, the second target information further includes capability information of the relay terminal.

[0328] In one embodiment, the resource request information further includes capability information of the second remote terminal.

[0329] In one embodiment, the terminal device is a first remote terminal, and the first target information includes an identifier of a relay terminal on a U2U relay link where the first remote terminal is located.

[0330] In one embodiment, the first target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0331] In one embodiment, the one or more second target information includes an identifier of a second remote terminal, where the second remote terminal is a counterpart remote terminal on the U2U relay link where the first remote terminal is located.

[0332] In one embodiment, the second target information further includes capability information of the second remote terminal.

[0333] In one implementation, the resource request information further includes capability information of the relay terminal.

[0334] In one embodiment, the resource request information further includes quality of service (QoS) flow information, where the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal.

[0335] In one embodiment, the resource request information further includes indication information for indicating the second remote terminal associated with the QoS flow information.

[0336] In one embodiment, the radio link control RLC channel information in the resource request information is RLC channel information between the first remote terminal and the relay terminal.

[0337] In one embodiment, the terminal device is a relay terminal, and the resource request information includes an identifier of a remote terminal for which the relay terminal provides relay service.

[0338] In one embodiment, the resource request information includes capability information of the remote terminal.

[0339] In one embodiment, the resource request information further includes QoS flow information, where the QoS flow information is QoS flow information between two remote terminals for which the relay terminal provides relay services.

[0340] In one implementation, the RLC channel information in the resource request information is RLC channel information between the relay terminal and the remote terminal.

[0341] In one embodiment, the method further includes: the relay terminal reporting the Service Data Adaptation Protocol (SDAP) layer configuration from the remote terminal to the network device.

[0342] In one embodiment, the resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal.

[0343] In one embodiment, the resource request information also includes role information of the terminal device.

[0344] In one embodiment, when the first target information includes an identifier of the second remote terminal and the second target information includes an identifier of the relay terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0345] In one embodiment, when the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

[0346] In one embodiment, when the first target information includes an identifier of the relay terminal and the second target information in the resource request information is an identifier of the second remote terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0347] In one embodiment, the first information includes first resource request information, second resource request information and third resource request information, the first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association between the single-hop target information and the end-to-end target information.

[0348] In one embodiment, the single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

[0349] In one embodiment, the end-to-end target information includes at least one of the following:

[0350] an identifier of the second remote terminal;

[0351] QoS flow information, QoS flow information between the first remote terminal and the second remote terminal;

[0352] Indication information, used to indicate a second remote terminal associated with the QoS flow information;

[0353] Capability information of the second remote terminal.

[0354] In one embodiment, the association relationship includes an association relationship between the identifier of the relay terminal and the identifier of the second remote terminal, and / or an association relationship between the identifier of the first resource request information and the identifier of the second resource request information.

[0355] In one embodiment, the RLC channel information includes RLC mode information and / or PDB information of each RLC channel, and the PDB information is determined based on QoS information implemented and / or segmented by the terminal.

[0356] In one implementation, the QoS flow information includes the QoS information currently required to be reported and / or the segmented QoS information.

[0357] In one embodiment, the identifier of the remote terminal is at least one of the following: a layer 2 identifier and a local identifier.

[0358] In one implementation, the identifier of the relay terminal is a layer 2 identifier.

[0359] In one embodiment, the resource request information further includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies, and carriers that the terminal device is interested in for terminal-to-terminal U2U relay link communication.

[0360] In one embodiment, the resource request information further includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U relay link communication.

[0361] In one implementation, the first information also includes radio link failure (RLF) information.

[0362] In one embodiment, when the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect link of the terminal device.

[0363] In one embodiment, when the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link.

[0364] In one implementation, the RLF information is used to indicate a target address where the RLF occurs and / or a reason why the RLF occurs.

[0365] In one implementation, the first information further includes RLC channel information of one or more carriers.

[0366] The terminal device 1100 of the embodiment of the present application can implement the corresponding functions of the terminal device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal device 1100 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the terminal device 1100 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0367] Figure 12 is a schematic block diagram of a network device 1200 according to an embodiment of the present application. The network device 1200 may include: a receiving unit 1201, configured to receive first information, where the first information includes one or more resource request information of a terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a sidelink.

[0368] In one embodiment, the terminal device is a first remote terminal, the first target information includes an identifier of a second remote terminal, and the second remote terminal is a counterpart remote terminal on a terminal-to-terminal U2U relay link where the first remote terminal is located.

[0369] In one embodiment, the second target information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located.

[0370] In one embodiment, the second target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0371] In one implementation, the target address information in the buffer status report BSR MAC CE is determined based on the identifier of the relay terminal.

[0372] In one implementation, the terminal device reports the first information in the order of remote terminals associated with the same relay terminal.

[0373] In one implementation, the second target information further includes capability information of the relay terminal.

[0374] In one embodiment, the resource request information further includes capability information of the second remote terminal.

[0375] In one embodiment, the terminal device is a first remote terminal, and the first target information includes an identifier of a relay terminal on a U2U relay link where the first remote terminal is located.

[0376] In one embodiment, the first target information includes an identifier of a relay terminal directly connected to the first remote terminal.

[0377] In one embodiment, the one or more second target information includes an identifier of a second remote terminal, where the second remote terminal is a counterpart remote terminal on the U2U relay link where the first remote terminal is located.

[0378] In one embodiment, the second target information further includes capability information of the second remote terminal.

[0379] In one implementation, the resource request information further includes capability information of the relay terminal.

[0380] In one embodiment, the resource request information further includes quality of service (QoS) flow information, where the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal.

[0381] In one embodiment, the resource request information further includes indication information for indicating the second remote terminal associated with the QoS flow information.

[0382] In one embodiment, the radio link control RLC channel information in the resource request information is RLC channel information between the first remote terminal and the relay terminal.

[0383] In one embodiment, the terminal device is a relay terminal, and the resource request information includes an identifier of a remote terminal for which the relay terminal provides relay service.

[0384] In one embodiment, the resource request information includes capability information of the remote terminal.

[0385] In one embodiment, the resource request information further includes QoS flow information, where the QoS flow information is QoS flow information between two remote terminals for which the relay terminal provides relay services.

[0386] In one implementation, the RLC channel information in the resource request information is RLC channel information between the relay terminal and the remote terminal.

[0387] In one embodiment, the method further includes: the relay terminal reporting the Service Data Adaptation Protocol (SDAP) layer configuration from the remote terminal to the network device.

[0388] In one embodiment, the resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal.

[0389] In one embodiment, the resource request information also includes role information of the terminal device.

[0390] In one embodiment, when the first target information includes an identifier of the second remote terminal and the second target information includes an identifier of the relay terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0391] In one embodiment, when the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

[0392] In one embodiment, when the first target information includes an identifier of the relay terminal and the second target information in the resource request information is an identifier of the second remote terminal, the resource request information is used to indicate that the terminal device is the first remote terminal.

[0393] In one embodiment, the first information includes first resource request information, second resource request information and third resource request information, the first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association between the single-hop target information and the end-to-end target information.

[0394] In one embodiment, the single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

[0395] In one embodiment, the end-to-end target information includes at least one of the following:

[0396] an identifier of the second remote terminal;

[0397] QoS flow information, QoS flow information between the first remote terminal and the second remote terminal;

[0398] Indication information, used to indicate a second remote terminal associated with the QoS flow information;

[0399] Capability information of the second remote terminal.

[0400] In one embodiment, the association relationship includes an association relationship between the identifier of the relay terminal and the identifier of the second remote terminal, and / or an association relationship between the identifier of the first resource request information and the identifier of the second resource request information.

[0401] In one embodiment, the RLC channel information includes RLC mode information and / or PDB information of each RLC channel, and the PDB information is determined based on QoS information implemented and / or segmented by the terminal.

[0402] In one implementation, the QoS flow information includes the QoS information currently required to be reported and / or the segmented QoS information.

[0403] In one embodiment, the identifier of the remote terminal is at least one of the following: a layer 2 identifier and a local identifier.

[0404] In one implementation, the identifier of the relay terminal is a layer 2 identifier.

[0405] In one embodiment, the resource request information further includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies, and carriers that the terminal device is interested in for terminal-to-terminal U2U relay link communication.

[0406] In one embodiment, the resource request information further includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U relay link communication.

[0407] In one implementation, the first information also includes radio link failure (RLF) information.

[0408] In one embodiment, when the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect link of the terminal device.

[0409] In one embodiment, when the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link.

[0410] In one implementation, the RLF information is used to indicate a target address where the RLF occurs and / or a reason why the RLF occurs.

[0411] In one implementation, the first information further includes RLC channel information of one or more carriers.

[0412] The network device 1200 of the embodiment of the present application can implement the corresponding functions of the network device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the network device 1200 can be found in the corresponding description in the above method embodiment, and will not be repeated here. It should be noted that the functions described in the various modules (sub-module, unit or component, etc.) in the network device 1200 of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0413] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 includes a processor 1310, which can call and execute a computer program from a memory to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0414] In one embodiment, the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to enable the communication device 1300 to implement the method in the embodiment of the present application.

[0415] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0416] In one embodiment, the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, the transceiver 1330 may send information or data to other devices, or receive information or data sent by other devices.

[0417] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0418] In one embodiment, the communication device 1300 may be a network device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0419] In one embodiment, the communication device 1300 may be a terminal device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0420] 14 is a schematic structural diagram of a chip 1400 according to an embodiment of the present application. The chip 1400 includes a processor 1410, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0421] In one embodiment, the chip 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

[0422] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0423] In one embodiment, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0424] In one embodiment, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0425] In one embodiment, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0426] In one embodiment, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0427] The chips used in the network device and the terminal device may be the same chip or different chips.

[0428] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0429] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0430] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0431] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0432] FIG15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. The communication system 1500 includes a terminal device 1510 and a network device 1520 .

[0433] Terminal device 1510 is used to send first information, which includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information. The terminal device is a terminal device in the side link.

[0434] The network device 1520 is used to receive first information, where the first information includes one or more resource request information of the terminal device.

[0435] The terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1520 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not described here in detail.

[0436] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

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

[0438] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0439] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: The terminal device sends first information, which includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in the side link.

2. The method according to claim 1, wherein: The terminal device is a first remote terminal, the first target information includes an identifier of a second remote terminal, and the second remote terminal is a counterpart remote terminal on a terminal-to-terminal U2U relay link where the first remote terminal is located.

3. The method according to claim 2, wherein: A second target information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located.

4. The method according to claim 3, wherein: The second target information includes an identifier of a relay terminal directly connected to the first remote terminal.

5. The method according to claim 3 or 4, wherein: The target address information in the buffer status report BSR medium access control element MAC CE is determined based on the identifier of the relay terminal.

6. The method according to claim 5, wherein: The terminal device reports the first information in the order of remote terminals associated with the same relay terminal.

7. The method according to any one of claims 3 to 6, wherein: The second target information also includes capability information of the relay terminal.

8. The method according to any one of claims 2 to 7, wherein: The resource request information also includes capability information of the second remote terminal.

9. The method according to claim 2, wherein: The terminal device is a first remote terminal, and the first target information includes an identifier of a relay terminal on a U2U relay link where the first remote terminal is located.

10. The method according to claim 9, wherein: The first target information includes an identifier of a relay terminal directly connected to the first remote terminal.

11. The method according to claim 9 or 10, wherein: The one or more second target information include an identifier of a second remote terminal, where the second remote terminal is a counterpart remote terminal on the U2U relay link where the first remote terminal is located.

12. The method according to claim 11, wherein: The second target information also includes capability information of the second remote terminal.

13. The method according to any one of claims 9 to 12, wherein: The resource request information also includes capability information of the relay terminal.

14. The method according to any one of claims 2 to 12, wherein: The resource request information also includes quality of service QoS flow information, and the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal.

15. The method according to claim 14, wherein: The resource request information also includes indication information for indicating the second remote terminal associated with the QoS flow information.

16. The method according to any one of claims 2 to 15, wherein: The radio link control RLC channel information in the resource request information is the RLC channel information between the first remote terminal and the relay terminal.

17. The method according to claim 1, wherein: The terminal device is a relay terminal, and the resource request information includes an identifier of a remote terminal for which the relay terminal provides relay service.

18. The method according to claim 17, wherein: The resource request information includes capability information of the remote terminal.

19. The method according to claim 17 or 18, wherein: The resource request information also includes QoS flow information, where the QoS flow information is QoS flow information between two remote terminals for which the relay terminal provides relay services.

20. The method according to any one of claims 17 to 19, wherein: The RLC channel information in the resource request information is the RLC channel information between the relay terminal and the remote terminal.

21. The method according to any one of claims 17 to 20, wherein: The method further includes: the relay terminal reporting the service data adaptation protocol SDAP layer configuration from the remote terminal to the network device.

22. The method according to claim 1, wherein: The resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal.

23. The method according to claim 22, wherein: The resource request information also includes role information of the terminal device.

24. The method according to claim 22, wherein: In a case where the first target information includes an identifier of a second remote terminal and the second target information includes an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a first remote terminal.

25. The method according to claim 22, wherein: In a case where the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

26. The method of claim 22, wherein: When the first target information includes an identifier of a relay terminal and the second target information in the resource request information is an identifier of a second remote terminal, the resource request information is used to indicate that the terminal device is a first remote terminal.

27. The method of claim 1, wherein: The first information includes first resource request information, second resource request information and third resource request information, the first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association relationship between the single-hop target information and the end-to-end target information.

28. The method according to claim 27, wherein: The single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

29. The method according to claim 27 or 28, wherein: The end-to-end target information includes at least one of the following: an identifier of a second remote terminal; QoS flow information, QoS flow information between the first remote terminal and the second remote terminal; Indication information, used to indicate a second remote terminal associated with the QoS flow information; Capability information of the second remote terminal.

30. The method according to any one of claims 27 to 29, wherein: The association relationship includes an association relationship between an identifier of the relay terminal and an identifier of the second remote terminal, and / or an association relationship between an identifier of the first resource request information and an identifier of the second resource request information.

31. The method of claim 16, 20 or 28, wherein: The RLC channel information includes RLC mode information and / or PDB information of each RLC channel, and the PDB information is determined based on QoS information implemented and / or segmented by the terminal.

32. The method of claim 14, 15, 19 or 29, wherein: The QoS flow information includes the QoS information currently required to be reported and / or the segmented QoS information.

33. The method of claim 2, 11, 17, 24, 25, 26, 29 or 30, wherein: The identifier of the remote terminal is at least one of the following: a layer 2 identifier and a local identifier.

34. The method of any one of claims 3 to 7, 9, 10, 24, 25, 26, 28 or 30, wherein: The identifier of the relay terminal is a layer 2 identifier.

35. The method according to any one of claims 1 to 34, wherein: The resource request information also includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies and carriers that the terminal device is interested in for terminal-to-terminal U2U relay link communication.

36. The method according to any one of claims 1 to 35, wherein: The resource request information also includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U relay link communication.

37. The method according to any one of claims 1 to 36, wherein: The first information also includes radio link failure RLF information.

38. The method of claim 37, wherein: In the case where the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect links of the terminal device.

39. The method of claim 37, wherein: In the case where the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link.

40. The method according to claim 38 or 39, wherein: The RLF information is used to indicate a target address where the RLF occurs and / or a reason why the RLF occurs.

41. The method of claim 1, wherein: The first information also includes radio link control RLC channel information associated with one or more carriers.

42. A communication method, comprising: A network device receives first information, wherein the first information includes one or more resource request information of a terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a side link.

43. The method of claim 42, wherein: The terminal device is a first remote terminal, the first target information includes an identifier of a second remote terminal, and the second remote terminal is a counterpart remote terminal on a terminal-to-terminal U2U relay link where the first remote terminal is located.

44. The method of claim 43, wherein: A second target information includes an identifier of a relay terminal on the U2U relay link where the first remote terminal is located.

45. The method of claim 44, wherein: The second target information includes an identifier of a relay terminal directly connected to the first remote terminal.

46. ​​The method according to claim 44 or 45, wherein: The target address information in the buffer status report BSR MAC CE is determined based on the identifier of the relay terminal.

47. The method of claim 46, wherein: The terminal device reports the first information in the order of remote terminals associated with the same relay terminal.

48. A method according to any one of claims 44 to 47, wherein: The second target information also includes capability information of the relay terminal.

49. A method according to any one of claims 43 to 48, wherein: The resource request information also includes capability information of the second remote terminal.

50. The method of claim 43, wherein: The terminal device is a first remote terminal, and the first target information includes an identifier of a relay terminal on a U2U relay link where the first remote terminal is located.

51. The method of claim 50, wherein: The first target information includes an identifier of a relay terminal directly connected to the first remote terminal.

52. The method of claim 50 or 51, wherein: The one or more second target information include an identifier of a second remote terminal, where the second remote terminal is a counterpart remote terminal on the U2U relay link where the first remote terminal is located.

53. The method of claim 52, wherein: The second target information also includes capability information of the second remote terminal.

54. A method according to any one of claims 50 to 53, wherein: The resource request information also includes capability information of the relay terminal.

55. The method according to any one of claims 43 to 53, wherein: The resource request information also includes quality of service QoS flow information, and the QoS flow information is QoS flow information between the first remote terminal and the second remote terminal.

56. The method of claim 55, wherein: The resource request information also includes indication information for indicating the second remote terminal associated with the QoS flow information.

57. The method according to any one of claims 43 to 46, wherein: The radio link control RLC channel information in the resource request information is the RLC channel information between the first remote terminal and the relay terminal.

58. The method of claim 42, wherein: The terminal device is a relay terminal, and the resource request information includes an identifier of a remote terminal for which the relay terminal provides relay service.

59. The method of claim 58, wherein: The resource request information includes capability information of the remote terminal.

60. The method of claim 58 or 59, wherein: The resource request information also includes QoS flow information, where the QoS flow information is QoS flow information between two remote terminals for which the relay terminal provides relay services.

61. The method according to any one of claims 58 to 60, wherein: The RLC channel information in the resource request information is the RLC channel information between the relay terminal and the remote terminal.

62. The method according to any one of claims 58 to 61, wherein: The method further includes: the relay terminal reporting the service data adaptation protocol SDAP layer configuration from the remote terminal to the network device.

63. The method of claim 42, wherein: The resource request information is used to indicate that the role of the terminal device is a first remote terminal or a relay terminal.

64. The method of claim 63, wherein: The resource request information also includes role information of the terminal device.

65. The method of claim 63, wherein: In a case where the first target information includes an identifier of a second remote terminal and the second target information includes an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a first remote terminal.

66. The method of claim 63, wherein: In a case where the first target information includes an identifier of a remote terminal and the resource request information does not contain second target information or an identifier of a relay terminal, the resource request information is used to indicate that the terminal device is a relay terminal.

67. The method of claim 63, wherein: When the first target information includes an identifier of a relay terminal and the second target information in the resource request information is an identifier of a second remote terminal, the resource request information is used to indicate that the terminal device is a first remote terminal.

68. The method of claim 42, wherein: The first information includes first resource request information, second resource request information and third resource request information, the first resource request information includes single-hop target information, the second resource request information includes end-to-end target information, and the third resource request information includes an association relationship between the single-hop target information and the end-to-end target information.

69. The method of claim 68, wherein: The single-hop target information includes at least one of the following: an identifier of the relay terminal; capability information of the relay terminal; frequency information; synchronization reference type information; and RLC channel information.

70. The method of claim 68 or 69, wherein: The end-to-end target information includes at least one of the following: an identifier of a second remote terminal; QoS flow information, QoS flow information between the first remote terminal and the second remote terminal; Indication information, used to indicate a second remote terminal associated with the QoS flow information; Capability information of the second remote terminal.

71. The method of any one of claims 68 to 70, wherein: The association relationship includes an association relationship between an identifier of the relay terminal and an identifier of the second remote terminal, and / or an association relationship between an identifier of the first resource request information and an identifier of the second resource request information.

72. The method of claim 57, 61 or 69, wherein: The RLC channel information includes RLC mode information and / or PDB information of each RLC channel, and the PDB information is determined based on QoS information implemented and / or segmented by the terminal.

73. The method of claim 55, 56, 60 or 70, wherein: The QoS flow information includes the QoS information currently required to be reported and / or the segmented QoS information.

74. The method of claim 43, 52, 58, 65, 66, 67, 70 or 71, wherein: The identifier of the remote terminal is at least one of the following: a layer 2 identifier and a local identifier.

75. The method of any one of claims 44 to 48, 50, 51, 65, 66, 67, 69 or 71, wherein The identifier of the relay terminal is a layer 2 identifier.

76. The method of any one of claims 42 to 75, wherein: The resource request information also includes frequency information, which is used to indicate at least one of the frequency domain resources, frequencies and carriers that the terminal device is interested in for terminal-to-terminal U2U relay link communication.

77. The method of any one of claims 42 to 76, wherein: The resource request information also includes synchronization reference type information, which is used to indicate the synchronization reference type used on at least one of the frequency domain resources, frequency, and carrier of the U2U relay link communication.

78. The method of any one of claims 42 to 77, wherein: The first information also includes radio link failure RLF information.

79. The method of claim 78, wherein: In the case where the terminal device is a first remote terminal, the RLF information is used to indicate the RLF of the direct and / or indirect links of the terminal device.

80. The method of claim 78, wherein: In the case where the terminal device is a relay terminal, the RLF information is used to indicate the RLF of the direct link.

81. The method of claim 79 or 80, wherein: The RLF information is used to indicate a target address where the RLF occurs and / or a reason why the RLF occurs.

82. The method of claim 42, wherein: The first information also includes radio link control RLC channel information, and the RLC channel information includes RLC channel information of one or more carriers.

83. A terminal device, comprising: A sending unit is used to send first information, wherein the first information includes one or more resource request information, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a side link.

84. A network device comprising: A receiving unit is used to receive first information, wherein the first information includes one or more resource request information of a terminal device, wherein one resource request information includes first target information, or one resource request information includes first target information and one or more second target information, and the terminal device is a terminal device in a side link.

85. A terminal device, comprising: A transceiver, a processor and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory so that the terminal device executes the method as described in any one of claims 1 to 41.

86. A network device comprising: A transceiver, a processor and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and run the computer program stored in the memory so that the network device executes the method as described in any one of claims 42 to 82.

87. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 41 or any one of claims 42 to 82.

88. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform a method as claimed in any one of claims 1 to 41 or any one of claims 42 to 82.

89. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 41 or any one of claims 42 to 82.

90. A computer program causing a computer to perform the method of any one of claims 1 to 41 or any one of claims 42 to 82.

91. A communication system comprising: A terminal device, configured to execute the method according to any one of claims 1 to 41; A network device, configured to execute the method as claimed in any one of claims 42 to 82.

Images