Relay communication method and device

CN118923192APending Publication Date: 2024-11-08GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094031.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-05-07
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In end-to-end relay communication, how to effectively allocate end-to-end user identities to achieve end-to-end transmission is a challenge.

Method used

A relay communication method is designed, which allocates end-to-end user identities to the first terminal and the second terminal through the relay terminal, optimizing the user identity allocation process in UE-to-UE Relay communication.

Benefits of technology

By allocating end-to-end user identities, UE-to-UE Relay communication is optimized, ensuring the accuracy and efficiency of data transmission, and solving the problem of user identity allocation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923192A_ABST
    Figure CN118923192A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a relay communication method and equipment, in UE-to-UE Relay communication, a scheme for distributing end-to-end user identifiers of a source terminal and / or a target terminal is designed, and the UE-to-UE Relay communication is optimized. The relay communication method is applied to a first terminal, a relay connection is established between the first terminal and a second terminal through a relay terminal, and the relay communication method comprises the following steps: the first terminal receives a first message; wherein the first message comprises at least one of the following: an end-to-end user identifier of the first terminal and an end-to-end user identifier of the second terminal (S210).
Need to check novelty before this filing date? Find Prior Art

Description

Relay communication method and device Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a method and device for relay communications. Background Art

[0002] In UE-to-UE relay (UE-2-UE Relay) communications, the Adaptation (ADAPT) layer sits above the PC5 Radio Link Control (RLC) layer. For both the source and destination terminals, the ADAPT layer sits between the PC5 RLC layer and the PC5 Packet Data Convergence Protocol (PDCP). The ADAPT layer must include the user identities of the source and / or destination terminals for end-to-end transmission. However, allocating end-to-end user identities remains a challenge.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method and device for relay communication. In UE-to-UE Relay communication, a scheme for allocating end-to-end user identifiers of source terminals and / or target terminals is designed, thereby optimizing UE-to-UE Relay communication.

[0005] In a first aspect, a relay communication method is provided, which is applied to a first terminal, wherein a relay connection is established between the first terminal and a second terminal via a relay terminal, the method comprising:

[0006] The first terminal receives a first message, wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal and an end-to-end user identifier of the second terminal.

[0007] In some embodiments, the first terminal is a source terminal, and the second terminal is a target terminal; or, the first terminal is a target terminal, and the second terminal is a source terminal.

[0008] In a second aspect, a relay communication method is provided, which is applied to a second terminal, wherein a relay connection is established between the second terminal and the first terminal via the relay terminal, the method comprising:

[0009] The second terminal sends a first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, and the end-to-end user identifier of the second terminal.

[0010] In some embodiments, the first terminal is a source terminal, and the second terminal is a target terminal; or, the first terminal is a target terminal, and the second terminal is a source terminal.

[0011] In a third aspect, a relay communication method is provided, which is applied to a relay terminal, wherein a relay connection is established between a first terminal and a second terminal via the relay terminal, the method comprising:

[0012] The relay terminal sends a first message, or the relay terminal forwards the first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, and the end-to-end user identifier of the second terminal.

[0013] In some embodiments, the first terminal is a source terminal, and the second terminal is a target terminal; or, the first terminal is a target terminal, and the second terminal is a source terminal.

[0014] In a fourth aspect, a terminal device is provided for executing the method in the first aspect.

[0015] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.

[0016] In a fifth aspect, a terminal device is provided for executing the method in the second aspect.

[0017] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned second aspect.

[0018] In a sixth aspect, a terminal device is provided for executing the method in the third aspect.

[0019] Specifically, the terminal device includes a functional module for executing the method in the third aspect above.

[0020] In the seventh aspect, a terminal device is provided, comprising a processor and a memory; the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the terminal device executes the method in the above-mentioned first aspect.

[0021] In an eighth aspect, a terminal device is provided, comprising a processor and a memory; the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the terminal device executes the method in the above-mentioned second aspect.

[0022] In the ninth aspect, a terminal device is provided, comprising a processor and a memory; the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the terminal device executes the method in the third aspect above.

[0023] In a tenth aspect, a device is provided for implementing the method in any one of the first to third aspects above.

[0024] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to third aspects described above.

[0025] In an eleventh aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to third aspects above.

[0026] In a twelfth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the above-mentioned first to third aspects.

[0027] In a thirteenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to third aspects above.

[0028] Through the above technical solution, in UE-to-UE Relay communication, the relay terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, or the second terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, thereby optimizing the UE-to-UE Relay communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

[0030] FIG2 is a schematic diagram of the UE-to-network relay transmission protocol stack in a 5G system.

[0031] FIG3 is a schematic diagram of a UE-to-UE Relay transmission protocol stack in a 5G system.

[0032] FIG4 is a schematic flowchart of a relay communication method provided according to an embodiment of the present application.

[0033] 5 to 7 are schematic flow charts of allocating end-to-end user identities according to embodiments of the present application.

[0034] FIG8 is a schematic flowchart of another relay communication method provided according to an embodiment of the present application.

[0035] FIG9 is a schematic flowchart of another relay communication method provided according to an embodiment of the present application.

[0036] FIG10 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

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

[0038] FIG12 is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

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

[0040] FIG14 is a schematic block diagram of a device provided according to an embodiment of the present application.

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

[0042] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

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

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

[0045] In some embodiments, the communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, an independent (SA) networking scenario, or a non-standalone (NSA) networking scenario.

[0046] In some embodiments, the communication system in the embodiments of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiments of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0047] In some embodiments, the communication system in the embodiments of the present application can be applied to the FR1 frequency band (corresponding to the frequency band range of 410MHz to 7.125GHz), can also be applied to the FR2 frequency band (corresponding to the frequency band range of 24.25GHz to 52.6GHz), and can also be applied to new frequency bands such as high-frequency bands corresponding to the frequency band range of 52.6GHz to 71GHz or the frequency band range of 71GHz to 114.25GHz.

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

[0049] The terminal device can be a station (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.

[0050] 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.).

[0051] 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, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc.

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

[0053] 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 WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, 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 or base station (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0054] 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. In some embodiments, 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. In some embodiments, the network device may also be a base station set up in a location such as land or water.

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

[0056] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include a source terminal 110, a target terminal 120, and a relay terminal 130. The relay terminal 130 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0057] In some embodiments, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0058] 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 100 shown in Figure 1 as an example, the communication device may include a source terminal 110, a target terminal 120, and a relay terminal 130 having communication functions. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

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

[0060] It should be understood that this document may involve a first communication device and a second communication device. The first communication device may be a terminal device, such as a mobile phone, machine facility, customer premises equipment (CPE), industrial equipment, vehicle, etc.; the second communication device may be a peer communication device of the first communication device, such as a terminal device, network equipment, machine facility, CPE, mobile phone, industrial equipment, vehicle, etc. In the embodiments of the present application, the first communication device may be a first terminal, and the second communication device may be a relay terminal or a second terminal; alternatively, the first communication device may be a second terminal, and the second communication device may be a first terminal or a relay terminal; alternatively, the first communication device may be a relay terminal, and the second communication device may be a first terminal or a second terminal.

[0061] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.

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

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

[0064] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0065] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may be an evolution of an existing LTE protocol, NR protocol, Wi-Fi protocol, or a protocol related to other communication systems. The present application does not limit the protocol type.

[0066] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0067] In some scenarios, a Layer 2 UE-to-Network (UE-to-Network) relay terminal (Relay UE) is introduced to directly connect to the network. Specifically, the remote terminal connects to the access network (e.g., gNB) and the core network (CN) (e.g., 5G Core Network (5GC)) through the UE-to-Network relay terminal.

[0068] Figure 2 shows a schematic diagram of the 5G system's transport protocol stack, specifically involving the remote UE, Layer 2 UE-to-Network relay UE, gNB, and 5GC. As shown in Figure 2, the remote UE may include the following layers: Internet Protocol (IP), Uu-Service Data Adaptation Protocol (SDAP), Uu-Packet Data Convergence Protocol (PDCP), PC5-Radio Link Control (RLC), PC5-Media Access Control (MAC), and PC5-Physics (PHY). The UE-to-Network relay may include the following layers: Adaptation (ADAPT), PC5-RLC, PC5-MAC, PC5-PHY, Uu-RLC, Uu-MAC, and Uu-PHY. The gNB may include the following layers: Uu-SDAP, Uu-PDCP, ADAPT, Uu-RLC, Uu-MAC, Uu-PHY, and the N3 protocol stack. 5GC may include the following layers: IP, N3 protocol stack.

[0069] As shown in Figure 2, the relay UE adaptation layer (ADAPT) is located above the control plane and user plane RLC layers of the PC5 interface between the remote UE and the relay UE, and above the control plane and user plane RLC layers of the Uu interface between the relay UE and the gNB. Uu-SDAP, Uu-PDCP, and Radio Resource Control (RRC) terminate between the remote UE and the gNB, while RLC, MAC, and PHY terminate in every link (including the link between the remote UE and the relay UE and the link between the relay UE and the gNB).

[0070] In some embodiments, the link between the relay UE and the network can be called a Uu link, a Uu path, the direct link between the remote UE and the network can also be called a Uu link, a Uu path, and the link between the remote UE and the relay UE can be called a PC5 link, a PC5 path.

[0071] For the uplink of L2UE-to-Network relay UE:

[0072] The relay terminal's adaptation layer supports uplink bearer mapping between access PC5 RLC channels, enabling transmission on the Uu path between the relay UE and the network and accessing the outbound Uu channel. For uplink relay services, different end-to-end bearers (e.g., signaling radio bearers (SRBs) and data radio bearers (DRBs)) for the same remote UE and / or different remote UEs can be mapped N:1 and multiplexed on a single Uu RLC channel.

[0073] The adaptation layer of the relay UE includes the identification information of the remote terminal of the uplink service to be relayed and the identification information of the radio bearer of the remote terminal, so that the gNB can associate the received data packets of the specific Packet Data Convergence Protocol (PDCP) entity associated with the radio bearer of the remote terminal.

[0074] For the downlink of L2UE-to-Network relay UE:

[0075] The adaptation layer of the relay UE may be configured to support downlink bearer mapping at the gNB to map the end-to-end radio bearers (e.g., SRBs, DRBs) of the remote terminal to Uu RLC channels over the Uu path between the relay UE and the network. The adaptation layer of the relay UE may be configured to support downlink N:1 bearer mapping and data multiplexing between multiple end-to-end radio bearers (e.g., SRBs, DRBs) of the remote UE and / or different remote UEs and Uu RLC channels over the Uu path between the relay UE and the network.

[0076] The relay UE's adaptation layer includes the remote terminal's identification information for the downlink service to be relayed. The remote terminal's radio bearer identification information and the remote terminal's identification information must be placed in the relay UE's adaptation layer by the gNB so that the relay UE can map data packets received from the remote terminal's radio bearer to the PC5 RLC channel associated with that radio bearer.

[0077] In some scenarios, terminal-to-terminal relay (UE-to-UE Relay) is introduced. As shown in Figure 3, the source terminal (Source UE) and the destination terminal (Destination UE) communicate through the relay terminal (Relay UE). In the terminal-to-terminal relay (UE-to-UE Relay) communication, the adaptation (ADAPT) layer is located above the PC5-RLC) layer. For the source terminal and the destination terminal, the adaptation (ADAPT) layer is located between the PC5-RLC layer and the PC5-PDCP. The adaptation (ADAPT) layer needs to include the user identity of the source terminal and / or the destination terminal for end-to-end transmission. The problem of how to allocate end-to-end identities can only be solved after this problem is solved before data transmission based on the above protocol stack can be carried out.

[0078] Based on the above problems, this application proposes a relay communication solution. In UE-to-UE Relay communication, a solution for allocating end-to-end user identities of source terminals and / or target terminals is designed to optimize UE-to-UE Relay communication.

[0079] The technical solution of this application is described in detail below through specific embodiments.

[0080] FIG4 is a schematic flow chart of a relay communication method 200 according to an embodiment of the present application. As shown in FIG4 , the method is applied to a first terminal, wherein a relay connection is established between the first terminal and a second terminal via a relay terminal. The relay communication method 200 may include at least part of the following contents:

[0081] S210, the first terminal receives a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

[0082] In an embodiment of the present application, the first terminal obtains the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal through the first message, so that the first terminal can apply the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal in its adaptation layer for end-to-end transmission, thereby optimizing UE-to-UE Relay communication.

[0083] In some embodiments, the end-to-end user identity may be equivalent to a layer 2 identity or a MAC layer identity.

[0084] In some embodiments, the end-to-end user identity may not be equal to the layer 2 identity or the MAC layer identity.

[0085] In some embodiments, the above S210 may also be executed by a relay terminal, that is, the relay terminal receives the first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, the end-to-end user identifier of the second terminal.

[0086] In some embodiments, the first terminal is a source terminal and the second terminal is a target terminal; or, the first terminal is a target terminal and the second terminal is a source terminal.

[0087] In some embodiments, the first message only includes the end-to-end user identifier of the first terminal. In this case, the first terminal may allocate the end-to-end user identifier of the second terminal.

[0088] In some embodiments, the first message only includes the end-to-end user identifier of the second terminal. In this case, the first terminal may allocate the end-to-end user identifier of the first terminal.

[0089] In some embodiments, the first message is sent by a relay terminal.

[0090] For example, the first terminal receives the first message sent by the relay terminal. That is, the relay terminal can allocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0091] For another example, a first terminal receives a first message generated and sent by a relay device based on a message sent by a second terminal, where the message sent by the second terminal may include some or all of the content included in the first message. That is, the relay terminal may assign the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal based on the message sent by the second terminal, or the second terminal may assign the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0092] In some embodiments, the first message is sent by the second terminal and forwarded by the relay terminal. For example, the first terminal receives the first message sent by the second terminal and forwarded by the relay terminal. In other words, the second terminal can allocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0093] For example, the first message is a message for configuring an end-to-end identifier.

[0094] In some embodiments, the first terminal sends a second message; wherein the second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0095] For example, when the first message is sent by the relay terminal, the relay terminal receives the second message.

[0096] For another specific example, when the first message is sent by the second terminal and forwarded by the relay terminal, the relay terminal receives the second message and forwards the second message to the second terminal.

[0097] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0098] In some embodiments, when the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0099] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the first terminal receives a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0100] In some embodiments, the third message only includes the end-to-end user identifier of the first terminal. In this case, the first terminal may reallocate the end-to-end user identifier of the second terminal.

[0101] In some embodiments, the third message only includes the end-to-end user identifier of the second terminal. In this case, the first terminal may reallocate the end-to-end user identifier of the first terminal.

[0102] In some embodiments, the third message is sent by a relay terminal.

[0103] For example, the first terminal receives the third message sent by the relay terminal. That is, the relay terminal can reallocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0104] For another example, a first terminal receives a third message generated and sent by a relay device based on a message sent by a second terminal, where the message sent by the second terminal may include some or all of the content included in the third message. In other words, the relay terminal may reallocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal based on the message sent by the second terminal, or the second terminal may reallocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0105] In some embodiments, the third message is sent by the second terminal and forwarded by the relay terminal. For example, the first terminal receives the third message sent by the second terminal and forwarded by the relay terminal. In other words, the second terminal can reallocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0106] In some embodiments, the end-to-end user identity described in this application may be equivalent to a layer 2 identity or a MAC layer identity, or the end-to-end user identity described in this application may not be equivalent to a layer 2 identity or a MAC layer identity.

[0107] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-RRC message, Media Access Control Control Element (MAC-CE), adaptation layer control (Control) protocol data unit (PDU).

[0108] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0109] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0110] It should be noted that the types of different messages in the above-mentioned first message, second message and third message can be the same or different, and this application does not limit this.

[0111] In some embodiments, the PC-S message is one of the following: Proximity-based Services (ProSe) direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject. reject), ProSe direct link modification reject, ProSe direct link authentication failure. The PC-S message may also be a new PC-S message, which is not limited in this application.

[0112] In some embodiments, the discovery message is one of the following: announcement message, response message, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, group member discovery announcement, group member discovery response, group member discovery solicitation, relay discovery additional information. The discovery message may also be a new discovery message, which is not limited in this application.

[0113] Therefore, in an embodiment of the present application, in UE-to-UE Relay communication, the relay terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, or the second terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, thereby optimizing the UE-to-UE Relay communication.

[0114] The technical solution of this application is described in detail below through Examples 1 to 3.

[0115] In embodiment 1, the relay terminal performs end-to-end user identification configuration, as shown in FIG5 . The specific process may include some or all of steps S11 to S16 .

[0116] S11, the relay terminal sends the end-to-end user identifier of the source terminal allocated by the relay terminal to the target terminal, wherein S11 can be implemented by one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU;

[0117] S12, the relay terminal sends the end-to-end user identifier of the target terminal allocated by the relay terminal to the source terminal, wherein S12 can be implemented by one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU;

[0118] S13, the source terminal sends an acknowledgment message (ACK) or a rejection message (reject) (optional) to the relay terminal, wherein the acknowledgment message is used to indicate that the source terminal accepts the end-to-end user identifier of the target terminal sent in S12, and the rejection message is used to indicate that the source terminal rejects the end-to-end user identifier of the target terminal sent in S12. The rejection here may be due to other conflicting / duplicate end-to-end user identifiers locally in the source terminal; wherein S13 may be implemented by one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU;

[0119] S14, the target terminal sends an acknowledgment message (ACK) or a rejection message (reject) (optional) to the relay terminal, wherein the acknowledgment message is used to indicate that the target terminal accepts the end-to-end user identifier of the source terminal sent in S11, and the rejection message is used to indicate that the target terminal rejects the end-to-end user identifier of the source terminal sent in S11. The rejection here may be due to other conflicting / duplicate end-to-end user identifiers locally in the target terminal. S14 may be implemented by one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU;

[0120] S15, the relay terminal sends the end-to-end user identifier of the source terminal reallocated by the relay terminal to the target terminal (optional), wherein S15 can be implemented by one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU;

[0121] S16, the relay terminal sends the end-to-end user identifier of the target terminal reallocated by the relay terminal to the source terminal (optional), wherein S16 can be implemented through one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0122] It should be noted that the above S11 and S12 can be performed simultaneously or sequentially, and S11 can be performed first and S12 later, or S12 can be performed first and S11 later. This embodiment does not limit this. The message types corresponding to the different steps in the above S11 to S16 can be the same or different, and this embodiment does not limit this.

[0123] In Example 2, the remote terminal (the source terminal and / or the target terminal) configures its own end-to-end user identifier. That is, Example 2 can ultimately achieve the allocation of its own end-to-end user identifier to the source terminal and the allocation of its own end-to-end user identifier to the target terminal. The following description uses the source terminal's configuration of its own end-to-end user identifier as an example. The target terminal can refer to the description of the source terminal and will not be repeated here. Specifically, as shown in Figure 6, the source terminal configures its end-to-end user identifier to the relay terminal and / or the target terminal. The specific process may include some or all of steps S21 to S23.

[0124] S21, the source terminal sends its allocated end-to-end user identifier to the relay terminal and / or the target terminal; wherein the message from the relay terminal to the target terminal may be a forwarded message from the source terminal without any processing above the access layer; or, the message from the relay terminal to the target terminal may be a newly generated message after receiving a message from the source terminal and performing processing above the access layer; wherein S21 may be implemented by one of the following: a PC-S message, a discovery message, a PC5-RRC message, a MAC-CE, or an adaptation layer control PDU;

[0125] S22, the relay terminal and / or the target terminal acknowledges (ACK) / rejects (rejects) the end-to-end user identity configuration of the source terminal in S21 (i.e., the end-to-end user identity of the source terminal). The rejection (reject) here may be due to the relay terminal and / or the target terminal having other conflicting / duplicate end-to-end user identities locally. The message from the relay terminal to the source terminal may be a forwarded message from the target terminal without any processing above the access layer. Alternatively, the message from the relay terminal to the source terminal may be a newly generated message after receiving a message from the target terminal and performing processing above the access layer. S22 may be implemented by one of the following: a PC-S message, a discovery message, a PC5-RRC message, a MAC-CE, or an adaptation layer control PDU.

[0126] S23, the source terminal sends the reallocated end-to-end user identifier of its own to the relay terminal and / or the target terminal; wherein, the message from the relay terminal to the target terminal may be a forwarded message from the source terminal without any processing above the access layer; or, the message from the relay terminal to the target terminal may be a newly generated message after receiving a message from the source terminal and performing processing above the access layer; wherein, S23 may be implemented through one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0127] In Example 3, the remote terminal (the source terminal and / or the target terminal) configures the end-to-end user identifier for the other terminal. That is, Example 3 can ultimately achieve the allocation of the target terminal's end-to-end user identifier to the source terminal, and the target terminal's allocation of the source terminal's end-to-end user identifier. The following description uses the source terminal's configuration of the target terminal's end-to-end user identifier as an example. The target terminal can refer to the description of the source terminal and will not be repeated here. Specifically, as shown in Figure 7, the source terminal configures the target terminal's end-to-end user identifier to the relay terminal and / or the target terminal. The specific process may include some or all of steps S31 to S33.

[0128] S31, the source terminal sends the assigned end-to-end user identifier of the target terminal to the relay terminal and / or the target terminal; wherein the message from the relay terminal to the target terminal may be a forwarded message from the source terminal without any processing above the access layer; or, the message from the relay terminal to the target terminal may be a newly generated message after receiving a message from the source terminal and performing processing above the access layer; wherein S31 may be implemented by one of the following: a PC-S message, a discovery message, a PC5-RRC message, a MAC-CE, or an adaptation layer control PDU;

[0129] S32: The relay terminal and / or the target terminal acknowledges (ACK) or rejects the end-to-end user identity configuration of the source terminal (i.e., the end-to-end user identity of the target terminal) in S31 above. The rejection here may be due to the relay terminal and / or the target terminal having other conflicting / duplicate end-to-end user identities locally. The message from the relay terminal to the source terminal may be a forwarded message from the target terminal without any processing above the access layer. Alternatively, the message from the relay terminal to the source terminal may be a newly generated message after receiving a message from the target terminal and performing processing above the access layer. S32 may be implemented by one of the following: a PC-S message, a discovery message, a PC5-RRC message, a MAC-CE message, or an adaptation layer control PDU.

[0130] S33, the source terminal sends the end-to-end user identifier of the reallocated target terminal to the relay terminal and / or the target terminal; wherein, the message from the relay terminal to the target terminal may be a forwarded message from the source terminal without processing above the access layer; or, the message from the relay terminal to the target terminal may be a newly generated message after receiving the message from the source terminal and processing above the access layer; wherein, S33 can be implemented through one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0131] It should be noted that the above-mentioned embodiment 2 and embodiment 3 can ultimately achieve the allocation of the source terminal's own end-to-end user identity and the target terminal's end-to-end user identity, or the target terminal's allocation of its own end-to-end user identity and the source terminal's end-to-end user identity.

[0132] The above, in combination with Figures 4 to 7, describes in detail the first terminal side embodiment of the present application. The following, in combination with Figure 8, describes in detail the second terminal side embodiment of the present application. It should be understood that the second terminal side embodiment corresponds to the first terminal side embodiment, and similar descriptions can refer to the first terminal side embodiment.

[0133] FIG8 is a schematic flow chart of a relay communication method 300 according to an embodiment of the present application. As shown in FIG8 , the method is applied to a second terminal, wherein a relay connection is established between the second terminal and the first terminal via the relay terminal. The relay communication method 300 may include at least part of the following contents:

[0134] S310, the second terminal sends a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

[0135] In an embodiment of the present application, the second terminal sends the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal through the first message, so that the first terminal and / or the relay terminal can apply the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal at its adaptation layer for end-to-end transmission, thereby optimizing UE-to-UE Relay communication.

[0136] In some embodiments, the end-to-end user identity may be equivalent to a layer 2 identity or a MAC layer identity.

[0137] In some embodiments, the end-to-end user identity may not be equal to the layer 2 identity or the MAC layer identity.

[0138] In some embodiments, the first terminal is a source terminal and the second terminal is a target terminal; or, the first terminal is a target terminal and the second terminal is a source terminal.

[0139] In some embodiments, the first terminal receives the first message, and / or the relay terminal receives the first message.

[0140] For example, the first terminal receives a first message sent by the second terminal and forwarded by the relay terminal. That is, the second terminal can allocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0141] For example, the first message is a message for configuring an end-to-end identifier.

[0142] In some embodiments, the second terminal receives a second message;

[0143] The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0144] For example, the second terminal receives the second message sent by the first device and forwarded by the relay device.

[0145] For another specific example, the second terminal receives a second message generated and sent by the relay device based on the message sent by the first terminal.

[0146] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0147] In some embodiments, when the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0148] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the second terminal sends a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0149] In some embodiments, the first terminal receives the third message, and / or the relay terminal receives the third message.

[0150] In some embodiments, the end-to-end user identity described in this application may be equivalent to a layer 2 identity or a MAC layer identity, or the end-to-end user identity described in this application may not be equivalent to a layer 2 identity or a MAC layer identity.

[0151] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0152] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0153] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0154] It should be noted that the types of different messages in the above-mentioned first message, second message and third message can be the same or different, and this application does not limit this.

[0155] In some embodiments, the PC-S message is one of the following: Proximity-based Services (ProSe) direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject. reject), ProSe direct link modification reject, ProSe direct link authentication failure. The PC-S message may also be a new PC-S message, which is not limited in this application.

[0156] In some embodiments, the discovery message is one of the following: announcement message, response message, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, group member discovery announcement, group member discovery response, group member discovery solicitation, relay discovery additional information. The discovery message may also be a new discovery message, which is not limited in this application.

[0157] Therefore, in an embodiment of the present application, in UE-to-UE Relay communication, the relay terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, or the second terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, thereby optimizing the UE-to-UE Relay communication.

[0158] The above, in combination with Figures 4 to 7, describes in detail the first terminal side embodiment of the present application. The following, in combination with Figure 9, describes in detail the relay terminal side embodiment of the present application. It should be understood that the relay terminal side embodiment corresponds to the first terminal side embodiment, and similar descriptions can refer to the first terminal side embodiment.

[0159] FIG9 is a schematic flow chart of a relay communication method 400 according to an embodiment of the present application. As shown in FIG9 , the method is applied to a relay terminal, wherein a relay connection is established between a first terminal and a second terminal via the relay terminal. The relay communication method 400 may include at least part of the following contents:

[0160] S410, the relay terminal sends a first message, or the relay terminal forwards a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

[0161] For example, the first terminal and / or the second terminal receives the first message.

[0162] In some embodiments, the first terminal is a source terminal and the second terminal is a target terminal; or, the first terminal is a target terminal and the second terminal is a source terminal.

[0163] In some embodiments, the end-to-end user identity may be equivalent to a layer 2 identity or a MAC layer identity.

[0164] In some embodiments, the end-to-end user identity may not be equal to the layer 2 identity or the MAC layer identity.

[0165] In some embodiments, when the relay terminal sends the first message to the first terminal and / or the second terminal, the relay terminal may allocate the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0166] In some embodiments, when a relay terminal sends a first message to a first terminal, the relay device generates and sends the first message based on a message sent by a second terminal, where the message sent by the second terminal may include some or all of the content included in the first message. That is, the relay terminal may assign the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal based on the message sent by the second terminal, or the second terminal may assign the end-to-end user identifier of the first terminal and / or the end-to-end user identifier of the second terminal.

[0167] In some embodiments, the relay terminal receives the second message, or the relay terminal forwards the second message;

[0168] The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0169] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or

[0170] In the case that the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0171] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the relay terminal sends a third message, or the relay terminal forwards the third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0172] In some embodiments, the first terminal and / or the second terminal receives the third message.

[0173] In some embodiments, the end-to-end user identity described in this application may be equivalent to a layer 2 identity or a MAC layer identity, or the end-to-end user identity described in this application may not be equivalent to a layer 2 identity or a MAC layer identity.

[0174] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0175] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0176] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0177] It should be noted that the types of different messages in the above-mentioned first message, second message and third message can be the same or different, and this application does not limit this.

[0178] In some embodiments, the PC-S message is one of the following: Proximity-based Services (ProSe) direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject. reject), ProSe direct link modification reject, ProSe direct link authentication failure. The PC-S message may also be a new PC-S message, which is not limited in this application.

[0179] In some embodiments, the discovery message is one of the following: announcement message, response message, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, group member discovery announcement, group member discovery response, group member discovery solicitation, relay discovery additional information. The discovery message may also be a new discovery message, which is not limited in this application.

[0180] Therefore, in an embodiment of the present application, in UE-to-UE Relay communication, the relay terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, or the second terminal allocates the end-to-end user identifier of the first terminal and the end-to-end user identifier of the second terminal to the first terminal, thereby optimizing the UE-to-UE Relay communication.

[0181] The above text, in combination with Figures 4 to 9, describes in detail the method embodiment of the present application. The following text, in combination with Figures 10 to 12, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0182] FIG10 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application. The terminal device 500 is a first terminal, wherein a relay connection is established between the first terminal and a second terminal via a relay terminal. As shown in FIG10 , the terminal device 500 includes:

[0183] The communication unit 510 is configured to receive a first message, wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

[0184] In some embodiments, the communication unit 510 is further configured to send a second message;

[0185] The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0186] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or

[0187] In the case that the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0188] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the communication unit 510 is also used to receive a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0189] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Controller MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

[0190] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0191] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0192] In some embodiments, the PC-S message is one of the following:

[0193] ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

[0194] In some embodiments, the discovery message is one of the following:

[0195] Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

[0196] In some embodiments, the end-to-end user identity is equivalent to a layer 2 identity or a media access control MAC layer identity; or

[0197] The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

[0198] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0199] It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the first terminal in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 500 are respectively for implementing the corresponding processes of the first terminal in the method 200 shown in Figure 4. For the sake of brevity, they will not be repeated here.

[0200] FIG11 shows a schematic block diagram of a terminal device 600 according to an embodiment of the present application. The terminal device 600 is a second terminal, wherein a relay connection is established between the second terminal and the first terminal via a relay terminal. As shown in FIG11 , the terminal device 600 includes:

[0201] The communication unit 610 is configured to send a first message, wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

[0202] In some embodiments, the communication unit 610 is further configured to receive a second message;

[0203] The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0204] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or

[0205] In the case that the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0206] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the communication unit 610 is also used to send a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0207] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Controller MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

[0208] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0209] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0210] In some embodiments, the PC-S message is one of the following:

[0211] ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

[0212] In some embodiments, the discovery message is one of the following:

[0213] Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

[0214] In some embodiments, the end-to-end user identity is equivalent to a layer 2 identity or a media access control MAC layer identity; or

[0215] The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

[0216] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0217] It should be understood that the terminal device 600 according to the embodiment of the present application may correspond to the second terminal in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 600 are respectively for implementing the corresponding processes of the second terminal in the method 300 shown in Figure 8. For the sake of brevity, they will not be repeated here.

[0218] FIG12 shows a schematic block diagram of a terminal device 700 according to an embodiment of the present application. The terminal device 700 is a relay terminal, wherein a relay connection is established between a first terminal and a second terminal via the relay terminal. As shown in FIG12 , the terminal device 700 includes:

[0219] The communication unit 710 is used to send a first message, or the communication unit 710 is also used to forward the first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, the end-to-end user identifier of the second terminal.

[0220] In some embodiments, the communication unit 710 is further configured to receive a second message, or the communication unit 710 is further configured to forward the second message;

[0221] The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0222] In some embodiments, when the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or

[0223] In the case that the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

[0224] In some embodiments, when the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the communication unit 710 is also used to send a third message, or the communication unit 710 is also used to forward the third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, the reallocated end-to-end user identifier of the second terminal.

[0225] In some embodiments, the first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Controller MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

[0226] In some embodiments, the second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0227] In some embodiments, the third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

[0228] In some embodiments, the PC-S message is one of the following:

[0229] ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

[0230] In some embodiments, the discovery message is one of the following:

[0231] Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

[0232] In some embodiments, the end-to-end user identity is equivalent to a layer 2 identity or a media access control MAC layer identity; or

[0233] The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

[0234] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0235] It should be understood that the terminal device 700 according to the embodiment of the present application may correspond to the relay terminal in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 700 are respectively for realizing the corresponding process of the relay terminal in the method 400 shown in Figure 9. For the sake of brevity, they will not be repeated here.

[0236] Figure 13 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device 800 shown in Figure 13 includes a processor 810, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0237] In some embodiments, as shown in FIG13 , the communication device 800 may further include a memory 820. The processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0238] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0239] In some embodiments, as shown in FIG13 , the communication device 800 may further include a transceiver 830 , and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, the transceiver 830 may send information or data to other devices, or receive information or data sent by other devices.

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

[0241] In some embodiments, the communication device 800 may specifically be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the first terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0242] In some embodiments, the communication device 800 may specifically be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the second terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0243] In some embodiments, the communication device 800 may specifically be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the relay terminal in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0244] Figure 14 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 900 shown in Figure 14 includes a processor 910, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0245] In some embodiments, as shown in FIG14 , the apparatus 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0246] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0247] In some embodiments, the apparatus 900 may further include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0248] In some embodiments, the apparatus 900 may further include an output interface 940. The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

[0250] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0251] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the relay terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0252] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, such as a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0253] FIG15 is a schematic block diagram of a communication system 1000 provided in an embodiment of the present application. As shown in FIG15 , the communication system 1000 includes a first terminal 1010 , a relay terminal 1020 , and a second terminal 1030 .

[0254] Among them, the first terminal 1010 can be used to implement the corresponding functions implemented by the first terminal in the above method, the relay terminal 1020 can be used to implement the corresponding functions implemented by the relay terminal in the above method, and the second terminal 1030 can be used to implement the corresponding functions implemented by the second terminal in the above method. For the sake of brevity, they will not be repeated here.

[0255] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0256] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, 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), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0258] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0259] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0260] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0261] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the relay terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0262] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0263] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the first terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0264] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0265] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the relay terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0266] The embodiment of the present application also provides a computer program.

[0267] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the first terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0268] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0269] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the relay terminal in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0270] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0272] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0273] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0274] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0275] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0276] 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 changes 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 in 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 method for relay communication, characterized in that: Applied to a first terminal, wherein a relay connection is established between the first terminal and a second terminal via a relay terminal, the method comprising: The first terminal receives a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

2. The method according to claim 1, wherein The method further comprises: The first terminal sends a second message; The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

3. The method according to claim 2, wherein In a case where the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or In a case where the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

4. The method according to claim 2 or 3, wherein: In a case where the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the method further includes: The first terminal receives a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, and the reallocated end-to-end user identifier of the second terminal.

5. The method according to any one of claims 1 to 4, characterized in that The first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Control Element MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

6. The method according to claim 2 or 3, wherein: The second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

7. The method according to claim 4, wherein The third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

8. The method according to any one of claims 5 to 7, characterized in that The PC-S message is one of the following: ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

9. The method according to any one of claims 5 to 7, characterized in that The discovery message is one of the following: Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

10. The method according to any one of claims 1 to 9, characterized in that The end-to-end user identifier is equivalent to a layer 2 identifier or a media access control MAC layer identifier; or The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

11. A method for relay communication, characterized in that: Applied to a second terminal, wherein a relay connection is established between the second terminal and the first terminal via a relay terminal, the method comprising: The second terminal sends a first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, the end-to-end user identifier of the second terminal.

12. The method according to claim 11, wherein The method further comprises: The second terminal receives a second message; The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

13. The method according to claim 12, wherein: In a case where the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or In a case where the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

14. The method according to claim 12 or 13, wherein: In a case where the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the method further includes: The second terminal sends a third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, and the reallocated end-to-end user identifier of the second terminal.

15. The method according to any one of claims 11 to 14, characterized in that The first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Control Element MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

16. The method according to claim 12 or 13, wherein: The second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

17. The method according to claim 14, wherein The third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

18. The method according to any one of claims 15 to 17, characterized in that The PC-S message is one of the following: ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

19. The method according to any one of claims 15 to 17, characterized in that The discovery message is one of the following: Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

20. The method according to any one of claims 11 to 19, characterized in that The end-to-end user identifier is equivalent to a layer 2 identifier or a media access control MAC layer identifier; or The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

21. A method for relay communication, characterized in that: Applied to a relay terminal, wherein a relay connection is established between a first terminal and a second terminal via the relay terminal, the method comprising: The relay terminal sends a first message, or the relay terminal forwards the first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, and the end-to-end user identifier of the second terminal.

22. The method according to claim 21, wherein The method further comprises: The relay terminal receives the second message, or the relay terminal forwards the second message; The second message is used to instruct the first terminal to accept the end-to-end user identifier carried in the first message, or the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

23. The method according to claim 22, wherein In a case where the end-to-end user identifier carried in the first message conflicts with a local configuration of the first terminal, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message; or In a case where the first terminal is locally configured with an end-to-end user identifier that is duplicated with the end-to-end user identifier carried in the first message, the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message.

24. The method according to claim 22 or 23, wherein: In a case where the second message is used to instruct the first terminal to reject the end-to-end user identifier carried in the first message, the method further includes: The relay terminal sends a third message, or the relay terminal forwards the third message; wherein the third message includes at least one of the following: the reallocated end-to-end user identifier of the first terminal, and the reallocated end-to-end user identifier of the second terminal.

25. The method according to any one of claims 21 to 24, characterized in that The first message is one of the following: PC-S message, discovery message, PC5-Radio Resource Control RRC message, Media Access Control Layer Control Element MAC-CE, Adaptation Layer Control Protocol Data Unit PDU.

26. The method according to claim 22 or 23, wherein The second message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

27. The method of claim 24, wherein: The third message is one of the following: PC-S message, discovery message, PC5-RRC message, MAC-CE, adaptation layer control PDU.

28. The method according to any one of claims 25 to 27, characterized in that The PC-S message is one of the following: ProSe direct link establishment request, ProSe direct link establishment accept, ProSe direct link establishment reject, ProSe direct link modification request, ProSe direct link modification accept, ProSe direct link authentication request, ProSe direct link authentication response, ProSe direct link authentication reject, ProSe direct link security mode command, ProSe direct link security mode complete, ProSe direct link security mode reject, ProSe direct link identifier update request, ProSe direct link identifier update ack, ProSe direct link identifier update reject, ProSe direct link modification reject, ProSe direct link authentication failure.

29. The method according to any one of claims 25 to 27, characterized in that The discovery message is one of the following: Announcement message announcement, response message response, solicitation message, UE-to-network relay discovery announcement, UE-to-network relay discovery response, UE-to-network relay discovery solicitation, Group member discovery announcement, Group member discovery response, Group member discovery solicitation, Relay discovery additional information.

30. The method according to any one of claims 21 to 29, wherein The end-to-end user identifier is equivalent to a layer 2 identifier or a media access control MAC layer identifier; or The end-to-end user identifier is not equivalent to a layer 2 identifier or a MAC layer identifier.

31. A terminal device, characterized in that: The terminal device is a first terminal, wherein a relay connection is established between the first terminal and a second terminal via a relay terminal, and the terminal device includes: A communication unit is configured to receive a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, and an end-to-end user identifier of the second terminal.

32. A terminal device, characterized in that: The terminal device is a second terminal, wherein a relay connection is established between the second terminal and the first terminal via a relay terminal, and the terminal device includes: A communication unit, configured to send a first message; wherein the first message includes at least one of the following: an end-to-end user identifier of the first terminal, an end-to-end user identifier of the second terminal.

33. A terminal device, characterized in that: The terminal device is a relay terminal, wherein a relay connection is established between the first terminal and the second terminal via the relay terminal, and the terminal device includes: A communication unit is used to send a first message, or the relay terminal forwards the first message; wherein the first message includes at least one of the following: the end-to-end user identifier of the first terminal, the end-to-end user identifier of the second terminal.

34. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method according to any one of claims 1 to 10.

35. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method according to any one of claims 11 to 20.

36. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method according to any one of claims 21 to 30.

37. A chip, characterized in that: include: A processor for calling and running a computer program from a memory so that a device equipped with the chip executes the method as claimed in any one of claims 1 to 10, or executes the method as claimed in any one of claims 11 to 20, or executes the method as claimed in any one of claims 21 to 30.

38. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 20, or the method according to any one of claims 21 to 30.

39. A computer program product, characterized in that The method comprises computer program instructions, which enable a computer to execute the method according to any one of claims 1 to 10, or to execute the method according to any one of claims 11 to 20, or to execute the method according to any one of claims 21 to 30.

40. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 20, or the method according to any one of claims 21 to 30.