Relay communication method and terminal

Abstract

The invention relates to a relay communication method and a terminal, and the method comprises the steps that a first terminal sends first information, and the first information is used for indicating relay state information; in the embodiment of the invention, the appropriate relay can be selected for the terminal based on the relay state information indicated by the first information in the relay scene, so that the communication quality is improved.

Description

[0001] Divisional Statement This application is a divisional application of PCT International Patent Application No. PCT / CN2023 / 106516, filed on July 10, 2023, entitled “Relay Communication Method and Terminal”, which entered the Chinese national phase as Chinese Patent Application No. 202380096783.5, and the disclosure of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, and more particularly, to a relay communication method and terminal. BACKGROUND

[0003] With the development of wireless communication technology, a relay is introduced in the 3rd Generation Partnership Project (3GPP). A remote terminal can be connected to a network through a relay terminal. A source terminal and a target terminal can also be connected through a relay terminal. Communication based on a relay terminal can extend the communication distance and improve the communication reliability. SUMMARY

[0004] Embodiments of the present application provide a relay communication method and terminal, which avoid the signaling interaction process of a conventional user equipment (UE) that only supports single-hop relay connected to a multi-hop relay.

[0005] Embodiments of the present application provide a relay communication method, comprising: A first terminal sends first information, the first information being used to indicate relay state information.

[0006] Embodiments of the present application provide a relay communication method, comprising: A second terminal receives first information, the first information being used to indicate relay state information.

[0007] Embodiments of the present application provide a first terminal, comprising: A first sending unit is configured to send first information, the first information being used to indicate relay state information.

[0008] Embodiments of the present application provide a second terminal, comprising: A first receiving unit is configured to receive first information, the first information being used to indicate relay state information.

[0009] Embodiments of the present application provide a terminal device, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and run the computer program stored in the memory, so that the terminal device executes the above-mentioned relay communication method.

[0010] The embodiment of the present application provides a chip for implementing the relay communication method. Specifically, the chip comprises a processor configured to invoke and run a computer program from a memory, so that a device installed with the chip performs the relay communication method.

[0011] The embodiment of the present application provides a computer readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the relay communication method.

[0012] The embodiment of the present application provides a computer program product comprising computer program instructions, which cause a computer to perform the relay communication method.

[0013] The embodiment of the present application provides a computer program, which, when executed on a computer, causes the computer to perform the relay communication method.

[0014] The embodiment of the present application provides a relay communication method, which can select a suitable relay for a terminal based on relay state information indicated by first information in a relay scenario, and improve communication quality. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a schematic diagram of an application scenario according to the embodiment of the present application; Figure 2A is a schematic diagram of 3GPP transmission mode A; Figure 2B is a schematic diagram of 3GPP transmission mode B; Figure 3 is a schematic flowchart of a relay communication method according to an embodiment of the present application; Figure 4 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 5 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 6 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 7 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 8 is a schematic flowchart of a relay communication method according to an embodiment of the present application; Figure 9 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 10 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 11is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 12 is a schematic flowchart of a relay communication method according to another embodiment of the present application; Figure 13A is a schematic flowchart of a relay between a network and a terminal according to Example 1 of the present application; Figure 13B is a schematic flowchart of a relay between terminals according to Example 1 of the present application; Figure 14A is a schematic flowchart of a relay between a network and a terminal according to Example 2 of the present application; Figure 14B is a schematic flowchart of a relay between terminals according to Example 2 of the present application; Figure 15A is a schematic flowchart of a relay between a network and a terminal according to Example 3 of the present application; Figure 15B is a schematic flowchart of a relay between terminals according to Example 3 of the present application; Figure 16 is a schematic block diagram of a first terminal according to an embodiment of the present application; Figure 17 is a schematic flowchart of a first terminal according to another embodiment of the present application; Figure 18 is a schematic block diagram of a second terminal according to an embodiment of the present application; Figure 19 is a schematic flowchart of a second terminal according to another embodiment of the present application; Figure 20 is a schematic structural diagram of a communication device according to an embodiment of the present application; Figure 21 is a schematic structural diagram of a chip according to an embodiment of the present application; Figure 22 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0016] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

[0017] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: 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, evolved system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system or other communication systems, etc.

[0018] Generally, the traditional communication system supports a limited number of connections, which is easy to implement. However, with the development of communication technology, the mobile communication system will not only support the traditional communication, but 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.

[0019] In an embodiment, the communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, can be applied to a dual connectivity (DC) scenario, and can be applied to a standalone (SA) network deployment scenario.

[0020] In an embodiment, the communication system in the embodiments of the present application can be applied to an unlicensed spectrum, which can also be regarded as a shared spectrum, or can be applied to a licensed spectrum, which can also be regarded as a non-shared spectrum.

[0021] Embodiments of the present application describe various embodiments in combination with network devices and terminal devices, wherein the terminal device can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal (remote terminal), a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device, etc.

[0022] The terminal device can be a station (STATION, ST) in a WLAN, can be 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 function, 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.

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

[0024] In the embodiments of the present application, the terminal device can 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 treatment, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc.

[0025] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes, etc. The wearable device is a portable device that is directly worn on the body or integrated into the clothes or accessories of the user. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes devices with full functions, large size, and the ability to realize complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and devices that focus on a certain type of application function and need to be used in cooperation with other devices, such as smart phones, such as various smart wristbands and smart jewelry for monitoring vital signs, etc.

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

[0027] By way of example and not limitation, in embodiments of the present application, a network device can have a mobile characteristic, for example, the network device can be a mobile device. Alternatively, the network device can be a satellite, a balloon station. For example, the satellite can 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. Alternatively, the network device can also be a base station disposed at a location on land, water, etc.

[0028] In embodiments of the present application, a network device can serve a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell can include a Metro cell, a Micro cell, a Pico cell, a Femto cell, etc., and these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.

[0029] Figure 1 A communication system 100 is exemplarily shown. The communication system includes one network device 110 and two terminal devices 120. In an implementation, the communication system 100 can include multiple network devices 110, and each network device 110 can include other numbers of terminal devices 120 within its coverage, which is not limited in embodiments of the present application.

[0030] In an implementation, the communication system 100 can further include a mobility management entity (MME), an access and mobility management function (AMF), and other network entities, which are not limited in embodiments of the present application.

[0031] The network device can include an access network device and a core network device. That is, the wireless communication system also includes a plurality of core networks for communicating with the access network device. The access network device can be an evolved node B (eNB or e-NodeB) macro base station, micro base station (also referred to as a "small base station"), pico base station, access point (AP), transmission point (TP), or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next radio (NR) system, or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0032] It should be understood that the devices with communication functions in the network / system in the embodiments of the present application can be referred to as communication devices. For example, the communication system shown in the embodiments of the present application can include network devices and terminal devices with communication functions, and the network devices and terminal devices can be specific devices in the embodiments of the present application, which will not be described here. The communication devices can also include other devices in the communication system, such as network controllers, mobile management entities, and other network entities, which are not limited in the embodiments of the present application. Figure 1

[0033] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is only used to describe the association relationship of the associated objects. For example, A and / or B can represent three cases: A alone, A and B together, and B alone. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects.

[0034] It should be understood that the "indication" mentioned in the embodiments of the present application can be direct indication, indirect indication, or an indication with an associated relationship. For example, A indicates B, which can mean that B can be obtained directly through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0035] In the description of the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between the two, or an associated relationship between the two, or an indication and being indicated, configuration and being configured, etc.

[0036] ​For the convenience of understanding the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described as follows, and the following related technologies can be combined with the technical solutions of the embodiments of the present application in any manner as optional solutions, which all belong to the protection scope of the embodiments of the present application.

[0037] I. Long Term Evolution (LTE) Device to Device (D2D) / Vehicle to X (V2X) Device to device communication is a kind of sidelink (SL) transmission technology based on D2D. Unlike the way of receiving or transmitting communication data through a base station in a traditional cellular system, a vehicle-to-everything (V2X) system or other sidelink communication system can adopt a terminal-to-terminal direct communication manner, thus having higher spectrum efficiency and lower transmission delay.

[0038] 3GPP includes two transmission modes: mode A and mode B.

[0039] Mode A: As shown in Figure 2A , the transmission resource of the terminal is allocated by the base station, and the terminal transmits data on the sidelink according to the resource allocated by the base station. The base station can allocate a single transmission resource for the terminal, or can allocate a semi-static transmission resource for the terminal.

[0040] Mode B: As shown in Figure 2B , the vehicle terminal selects a resource in the resource pool for data transmission.

[0041] In 3GPP, D2D includes different stages: (1) Proximity based Service (ProSe): In Rel-12 / 13, device to device communication is studied for the scenario of ProSe, which mainly aims at public safety type services.

[0042] In ProSe, by configuring the location of the resource pool in the time domain, for example, the resource pool is non-continuous in the time domain, the UE can non-continuously transmit / receive data on the sidelink, thereby achieving power saving effect.

[0043] (2) Vehicle to X (V2X): In Rel-14 / 15, the vehicle to X system studies the scenario of vehicle to vehicle communication, which mainly faces the business of relatively high-speed vehicle to vehicle and vehicle to pedestrian communication; In V2X, since the vehicle system has continuous power supply, power efficiency is not the main problem, and the delay of data transmission is the main problem, so the terminal device is required to continuously transmit and receive in the system design.

[0044] (3) Wearable, Further Enhancement to Device-to-Device (FeD2D): In Rel-14, this topic is studied for the scenario that wearable devices access the network through a mobile phone, and it mainly faces the scenario of low mobile speed and low power access.

[0045] In FeD2D, in the pre-research stage, 3GPP concludes that the base station can configure the discontinuous reception (DRX) parameters of the remote terminal through a relay terminal, but since this topic has not further entered the standardization stage, the specific details of how to configure the DRX are not concluded.

[0046] Multi-carrier: In Rel-15 LTE V2X, a multi-carrier mechanism is introduced, specifically, the multi-carrier mechanism is embodied in that a UE can support packet splitting, transmitting a packet with multiple carriers to improve data transmission rate; packet duplication, duplicating one same packet twice and sending with two carriers to improve transmission reliability; and multi-carrier reception enhancement at the receiving end. Specifically, for packet duplication: V2X sidelink communication supports sidelink packet duplication, which is performed at the UE's Packet Data Convergence Protocol (PDCP) layer. For sidelink packet duplication for transmission, PDCP Protocol Data Unit (PDU) is duplicated at the PDCP entity. The duplicated Packet Data Protocol (PDP) PDU of the same PDCP entity is submitted to two different Radio Link Control (RLC) entities and is associated to two different sidelink logical channels respectively. The duplicated PDP PDU of the same PDCP entity is only allowed to be transmitted on different sidelink carriers. The UE can activate or deactivate sidelink packet duplication based on (pre-)configuration. Sidelink packet duplication is not applicable for transmission with Rel-14 transmission profile (TS 23.285

[72] ). The Proximity Services Per-Packet Reliability (PPPR) value supported by sidelink packet duplication can be (pre-)configured by a PPPR threshold. For resource allocation with UE autonomous resource selection and scheduling, the UE shall perform sidelink packet duplication for data with configured PPPR values until the packet duplication configuration is cancelled for these PPPR values. For scheduled resource allocation, the UE associates, through a Sidelink Buffer Status Report (BSR), the amount of data associated with one or more PPPR values and the destination to which the data belongs. The mapping of PPPR values to logical channel groups can be configured by the eNB, and the PPPR values are reflected by the associated logical channel group IDentity (ID) included in the sidelink BSR. A list of one or more PPPR values can be reported by an RRC connected UE in a sidelink UE information.

[0047] II. NR V2X NR V2X is based on LTE V2X, and is not limited to broadcast scenarios, but is further extended to unicast and groupcast scenarios, in which V2X applications are studied.

[0048] Similar to LTE V2X, NR V2X also includes two resource grant modes, mode-1 / 2. Further, a user can be in a hybrid mode, i.e., both mode-1 and mode-2 can be used for resource acquisition. The resource acquisition is indicated by the way of sidelink grant, i.e., the sidelink grant indicates the time-frequency location of the corresponding PSCCH and PSSCH resources.

[0049] Unlike LTE V2X, in addition to the feedback-free, UE self-initiated Hybrid Automatic Repeat-reQuest (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, not limited to unicast communication, but also including groupcast communication.

[0050] As in LTE V2X, in NR V2X, since the vehicle-mounted system has continuous power supply, power efficiency is not a major problem, and the latency of data transmission is a major problem, so the terminal device is required to continuously transmit and receive in the system design.

[0051] For example, the sidelink terminal will trigger the sidelink RRC reconfiguration procedure in the following scenarios: Release of sidelink data bearer in unicast communication; Establishment of sidelink data bearer in unicast communication; Modification of the related configuration of the sidelink data bearer in unicast communication; In the terminal-to-network relay scenario, release of the PC5 relay RLC channel between the layer-2 relay terminal and the remote terminal; In the terminal-to-network relay scenario, establishment of the PC5 relay RLC channel between the layer-2 relay terminal and the remote terminal; In the terminal-to-network relay scenario, modification of the configuration parameters related to the PC5 relay RLC channel between the layer-2 relay terminal and the remote terminal; Reconfiguration of the reporting of NR sidelink measurement related parameters; Reconfiguration of the sidelink CSI reference signal resource and CSI reporting delay boundary; Reconfiguration of the opposite terminal sidelink DRX.

[0052] III. Terminal-to-network relay The remote terminal performs measurement reporting, and includes the relay terminal identifier, the serving cell identifier, the reference signal received power (RSRP) measurement result and other information in the measurement reporting information. When the remote terminal performs a non-direct path to direct path link switching, the serving relay terminal can use SL-RSRP to perform measurement on the sidelink; when the remote terminal performs a direct path to non-direct path link switching, the serving relay terminal can use SD-RSRP to perform measurement on the sidelink. In addition, two new measurement reporting trigger events are defined for terminal-to-network relay switching when performing measurement reporting. Event 1: When the link quality of the serving relay terminal is lower than the configured threshold value, and optionally, the link quality of the adjacent cell is higher than the configured threshold value, the remote terminal performs measurement reporting. Event 2: When the link quality of the serving cell is lower than the configured threshold value, and optionally, the link quality of the relay terminal is higher than the configured threshold value, the remote terminal performs measurement reporting. In addition, in order to assist the remote terminal to perform direct link to non-direct link switching, a new timer is introduced. When the remote terminal receives an RRC reconfiguration message indicating direct link to non-direct link switching, the remote terminal starts the timer. When the timer expires, the remote terminal performs RRC reestablishment.

[0053] In terminal-to-network relay, the network side configures a bearer ID for end-to-end data transmission of the relay terminal for the remote terminal and the relay terminal, and additionally configures a bearer parameter on the PC5 interface between the relay terminal and the remote terminal. In the configuration of the sidelink relay adaptation protocol (SRAP) layer, the network maps the bearer ID and the PC5 RLC channel ID, and the relay terminal can understand the specific configuration information used by the remote terminal through the RLC channel ID. However, the relay terminal cannot understand the specific information of the quality of service (QoS) of the corresponding service transmitted by the remote terminal using the configuration information. The backward compatibility problem after introducing multi-hop relay can be solved in the embodiments of the present application, and the problem that a remote user supporting only single-hop relay accesses a multi-hop relay network can be avoided.

[0054] Figure 3 is a schematic flowchart of a relay communication method according to an embodiment of the present application. The method 300 can be optionally applied to the system shown in Figure 1 but is not limited thereto. The method includes at least part of the following contents.

[0055] S310, the first terminal sends first information, the first information being used for indicating relay state information. In embodiments of the present application, the first terminal can send the first information to the second terminal. For example, the first terminal is a relay terminal, and the second terminal is a remote terminal, a source terminal or a target terminal. The first information can indicate the relay state information of the first terminal. The relay state information can include relay capability information, for example, whether the first terminal supports relay, a currently working relay type, a specific relay hop number, etc. In a relay scenario, the relay state information indicated based on the first information can select a suitable relay for the terminal, and improve the communication quality. For example, a remote user or a target that only supports single-hop relay can be avoided from accessing a multi-hop relay network, unnecessary network access operations are reduced, and the overall communication quality of the communication network is improved.

[0056] In an embodiment, the second terminal is a remote terminal or a target terminal.

[0057] In an embodiment, the first terminal is a relay terminal.

[0058] In an embodiment, the relay state information is used for indicating at least one of: working in a single-hop relay state; working in a multi-hop relay state; a currently working hop number.

[0059] For example, the first information can indicate a currently working relay type of the relay terminal, for example, working in a single-hop relay state or working in a multi-hop relay state. The first information can also indicate a currently working relay hop number of the relay terminal, for example, a hop number of 1 indicates that the relay works in a single-hop relay state, and a hop number of 3 indicates that the relay works in a multi-hop relay state and is at the third hop.

[0060] In an embodiment, the first information is in a first message. In embodiments of the present application, the first terminal can send the first message to the second terminal, and carry the first information in the first message to explicitly or implicitly indicate the relay state information of the first terminal.

[0061] In an embodiment, the first information is indicated by one or more indication bits in the first message. In embodiments of the present application, the relay state information of the first terminal can be explicitly indicated by the indication bits in the first message. For example, a value of 1 of the indication bits in the first message can indicate that the first terminal works in a single-hop relay state. If a value of 0 of the indication bits in the first message can indicate that the first terminal works in a multi-hop relay state. Or, if a value of 11 of the indication bits in the first message can indicate that the first terminal works in a multi-hop relay state and is at the third hop.

[0062] In an embodiment, the first information is at least one of the following in the first message: Layer 2 identity; Relay Service Code (RSC), or Relay Service Identification (RSID); Service identity; Physical layer parameter.

[0063] In embodiments of the present application, the relay status information of the first terminal can be implicitly indicated by other identity, code or parameter in the first message.

[0064] For example, if the Layer 2 identity in the first message is singular, it indicates that the relay status information is working in single-hop relay state, and if it is plural, it indicates that the relay status information is working in multi-hop relay state. For another example, if the Layer 2 identity in the first message is singular, it indicates that the relay status information is working in multi-hop relay state, and if it is plural, it indicates that the relay status information is working in single-hop relay state.

[0065] For another example, the RSC or service ID can be divided into several value ranges. If the RSC or service ID in the first message is in the first value range, it indicates that the relay status information is working in single-hop relay state, and if it is in the second value range, it indicates that the relay status information is working in multi-hop relay state.

[0066] In an embodiment, the physical layer parameter includes at least one of a relay service reference signal sequence and a reference signal cyclic shift. For example, a corresponding relationship between the physical layer parameter and the relay status information can be set. For example, among 128 reference signal sequences, the first 64 reference signal sequences correspond to single-hop, and the last 64 reference signal sequences correspond to multi-hop. For another example, among 128 reference signal sequences, the first 32 reference signal sequences correspond to single-hop, the next 32 reference signal sequences correspond to 2-hop, the next 32 reference signal sequences correspond to 3-hop, and the last 32 reference signal sequences correspond to 4-hop. For another example, the number of bits of the reference signal cyclic shift is singular for single-hop and plural for multi-hop.

[0067] Figure 4 FIG. 4 is a schematic flow chart of a relay communication method 400 according to another embodiment of the present application. The method can include one or more features of the above-mentioned methods. In an embodiment, the first message includes a discovery message.

[0068] In an embodiment, the discovery message includes a discovery announcement message, and the first terminal sends the first information including: S410, the first terminal broadcasts a discovery notification message to the second terminal, the discovery notification message being used to indicate the relay status information of the first terminal. For example, the first terminal, e.g. a relay terminal, indicates the relay status information of the relay terminal by broadcasting the discovery notification message. The second terminal, e.g. a remote terminal or a target terminal, receiving the discovery notification message can determine whether the relay terminal can be used for access.

[0069] For example, if the relay status information of the relay terminal is working in a multi-hop relay status, and the remote terminal or the target terminal only supports working in a single-hop relay status, the remote terminal or the target terminal does not use the relay terminal for access. If the relay status information of the relay terminal is working in a multi-hop relay status, and the remote terminal or the target terminal supports working in a multi-hop relay status, the remote terminal or the target terminal can use the relay terminal for access.

[0070] For another example, if the relay status information of the relay terminal is working in a single-hop relay status, and the remote terminal or the target terminal only supports working in a single-hop relay status, the remote terminal or the target terminal uses the relay terminal for access. If the relay status information of the relay terminal is working in a single-hop relay status, and the remote terminal or the target terminal supports working in a multi-hop relay status, the remote terminal or the target terminal cannot use the relay terminal for access if the terminal only supporting multi-hop relay cannot access single-hop relay, and vice versa.

[0071] Figure 5 is a schematic flow chart of a relay communication method 500 according to another embodiment of the present application. The method can comprise one or more features of the above-described methods. In one implementation, as shown in Figure 5 the method further comprises: S510, the first terminal receives a discovery request message sent by the second terminal, the discovery request message being used to indicate the relay status information of the second terminal.

[0072] For example, the second terminal indicates the relay status information supported by the second terminal by sending the discovery request message. Upon receiving the discovery request message, the first terminal can determine whether the second terminal can use the first terminal for access based on the relay status information of the second terminal.

[0073] For example, the discovery request message can indicate that the second terminal, e.g., a remote terminal or a target terminal, supports working in a multi-hop relay state. If the first terminal, e.g., a relay terminal, works in the multi-hop relay state, the first terminal can determine that the second terminal can access through the first terminal. If the first terminal, e.g., a relay terminal, works in a single-hop relay state, if a terminal only supporting multi-hop relay cannot access a single-hop relay, the first terminal can determine that the second terminal cannot access through the first terminal; if a terminal supporting multi-hop relay can access a single-hop relay, the first terminal can also determine that the second terminal can access through the first terminal.

[0074] For example, the discovery request message can indicate that the second terminal, e.g., a remote terminal or a target terminal, supports working in a single-hop relay state. If the first terminal, e.g., a relay terminal, works in the single-hop relay state, the first terminal can determine that the second terminal can access through the first terminal. If the first terminal, e.g., a relay terminal, works in a multi-hop relay state, the first terminal can determine that the second terminal cannot access through the first terminal.

[0075] In an embodiment, as shown in FIG. 6, the discovery message includes a discovery response message, S310 the first terminal sends first information, including: Figure 5 S310, the first terminal sends first information, including: S520, the first terminal sends a discovery response message to the second terminal, the discovery response message being used to indicate relay state information of the first terminal.

[0076] For example, the discovery response message sent by the first terminal to the second terminal indicates relay state information of the first terminal, i.e., a relay terminal. The second terminal, e.g., a remote terminal or a target terminal, can determine whether the second terminal can access through the relay terminal according to the relay state information of the relay terminal. If the first terminal works in a multi-hop relay state and the second terminal also supports working in a multi-hop relay state, the second terminal can access a communication system, e.g., a sidelink communication system or an uplink / downlink communication system, through the first terminal as a relay. If the first terminal works in a multi-hop relay state but the second terminal only supports working in a single-hop relay state, the second terminal cannot access the communication system through the first terminal as a relay.

[0077] Figure 6 is a schematic flow chart of a relay communication method 600 according to another embodiment of the present application. The method can include one or more features of the above method. In an embodiment, the first message includes a PC5 signaling (PC5-S) message.

[0078] In an embodiment, as shown in FIG. 6, the discovery message includes a discovery response message, S310 the first terminal sends first information, including: Figure 6 S310, the first terminal sends first information, including: S610, the first terminal receives a connection establishment request message sent by the second terminal, the connection establishment request message being used to indicate the relay status information of the second terminal.

[0079] In an embodiment, the connection establishment request message is a ProSe direct link establishment request message. For example, the connection establishment request message sent by the second terminal to the first terminal can be a direct communication request (DCR) message, for example, a ProSe direct link establishment request message. The first terminal receiving the ProSe direct link establishment request message can determine whether the second terminal can access the communication system through the first terminal according to the relay type supported by the second terminal.

[0080] For example, if the ProSe direct link establishment request message indicates that the relay status information of the second terminal is to support working in a multi-hop relay state, the first terminal currently works in a single-hop relay state, and a terminal supporting only multi-hop relay cannot access a single-hop relay, the second terminal does not select the first terminal as a relay of the second terminal; if a terminal supporting only multi-hop relay can access a single-hop relay, the second terminal can also select the first terminal as a relay of the second terminal; and if the first terminal currently works in a multi-hop relay state, the second terminal can select the first terminal as a relay of the second terminal.

[0081] For example, if the ProSe direct link establishment request message indicates that the relay status information of the second terminal is to support working in a single-hop relay state, the first terminal currently works in a single-hop relay state, the first terminal is selected as a relay of the second terminal; and if the first terminal currently works in a multi-hop relay state, the first terminal is not selected as a relay of the second terminal.

[0082] In an embodiment, the PC5 signaling message includes a security mode configuration message and / or a connection establishment response message, and the first terminal sends the first information, including: S620, the first terminal sends a security mode configuration message and / or a connection establishment response message to the second terminal, the security mode configuration message and / or the connection establishment response message being used to indicate the relay status information of the first terminal.

[0083] In an embodiment, the security mode configuration message is a ProSe direct link security mode command message. For example, the security mode configuration message sent by the first terminal to the second terminal can comprise a Safe Mode Command (SMC) message. The second terminal receiving the SMC message can select whether to access the communication system through the first terminal according to the relay type supported by the second terminal.

[0084] For example, if the ProSe direct link security mode command message indicates that the relay status information of the first terminal is working in a multi-hop relay state, and the second terminal does not support working in the multi-hop relay state, the second terminal can not select the first terminal as a relay of the second terminal; if the second terminal supports working in the multi-hop relay state, the second terminal can select the first terminal as a relay of the second terminal.

[0085] For another example, if the ProSe direct link security mode command message indicates that the relay status information of the first terminal is working in a single-hop relay state, and the second terminal supports working in the single-hop relay state, the second terminal selects the first terminal as a relay of the second terminal; if the second terminal supports working in the multi-hop relay state, the second terminal does not select the first terminal as a relay of the second terminal if only a terminal supporting multi-hop relay can not access a single-hop relay; if the terminal supporting multi-hop relay can access a single-hop relay, the second terminal can also select the first terminal as a relay of the second terminal.

[0086] In an embodiment, the connection establishment response message is a ProSe direct link establishment accept message. For example, the connection establishment response message sent by the first terminal to the second terminal can comprise a Direct Communication Accept (DCA) message. Specifically, the DCA message can be a ProSe direct link establishment accept message. The ProSe direct link establishment accept message sent by the first terminal to the second terminal can comprise the relay status information of the first terminal. The second terminal receiving the ProSe direct link establishment accept message can select whether to access the communication system through the first terminal according to the relay type supported by the second terminal.

[0087] For example, if the ProSe Direct Link Setup Accept message indicates that the relay status information of the first terminal is working in a multi-hop relay state, and the second terminal does not support working in the multi-hop relay state, the second terminal does not select the first terminal as a relay of the second terminal; if the second terminal supports working in the multi-hop relay state, the second terminal selects the first terminal as the relay of the second terminal.

[0088] For another example, if the ProSe Direct Link Setup Accept message indicates that the relay status information of the first terminal is working in a single-hop relay state, and the second terminal supports working in the single-hop relay state, the second terminal selects the first terminal as the relay of the second terminal; if the second terminal supports working in the multi-hop relay state, if only the terminal supporting the multi-hop relay cannot access the single-hop relay, the second terminal does not select the first terminal as the relay of the second terminal; if the terminal supporting the multi-hop relay can access the single-hop relay, the second terminal can also select the first terminal as the relay of the second terminal.

[0089] Figure 7 FIG. 7 is a schematic flow chart of a relay communication method 700 according to another embodiment of the present application. The method can include one or more features of the above-described methods. In an implementation, the first message includes a PC5 radio resource control layer message.

[0090] In an implementation, the PC5 radio resource control layer message includes a capability-related message, and the method further includes: S710, the first terminal receives a first capability-related message sent by the second terminal, the first capability-related message being used to indicate relay status information of the second terminal.

[0091] For example, after the second terminal sends the first capability-related message to the first terminal, the first terminal receiving the first capability-related message can determine whether the second terminal can access the communication system through the first terminal according to the relay type supported by the second terminal.

[0092] For example, if the first capability-related message indicates that the relay status information of the second terminal is working in a multi-hop relay state, and the first terminal is currently working in a single-hop relay state, if only the terminal supporting the multi-hop relay cannot access the single-hop relay, the first terminal can determine not to use the first terminal as the relay of the second terminal; if the terminal supporting the multi-hop relay can access the single-hop relay, the first terminal can also determine to use the first terminal as the relay of the second terminal; if the first terminal is currently working in the multi-hop relay state, the first terminal determines to use the first terminal as the relay of the second terminal.

[0093] For example, if the first capability related message indicates that the relay status information of the second terminal is working in the single-hop relay state, and the first terminal is currently working in the single-hop relay state, the first terminal can determine to use the first terminal as the relay of the second terminal; if the first terminal is currently working in the multi-hop relay state, the first terminal determines not to use the first terminal as the relay of the second terminal.

[0094] In an embodiment, as shown in FIG. 8, Figure 7 S310, the first terminal sends first information, including: S720, the first terminal sends a second capability related message to the second terminal, the second capability related message being used to indicate the relay status information of the first terminal.

[0095] For example, after the first terminal sends the second capability related message to the second terminal, the second terminal receiving the second capability related message can select whether to access the communication system through the first terminal according to the relay type supported by the second terminal.

[0096] For example, if the second capability related message indicates that the relay status information of the first terminal is working in the multi-hop relay state, and the second terminal does not support working in the multi-hop relay state, the second terminal does not select to use the first terminal as the relay of the second terminal; if the second terminal supports working in the multi-hop relay state, the second terminal selects to use the first terminal as the relay of the second terminal.

[0097] For another example, if the second capability related message indicates that the relay status information of the first terminal is working in the single-hop relay state, and the second terminal supports working in the single-hop relay state, the second terminal selects to use the first terminal as the relay of the second terminal; if the second terminal supports working in the multi-hop relay state, if only the terminal supporting the multi-hop relay cannot access the single-hop relay, the second terminal does not select to use the first terminal as the relay of the second terminal; if the terminal supporting the multi-hop relay can access the single-hop relay, the second terminal can also select to use the first terminal as the relay of the second terminal.

[0098] Figure 8 FIG. 8 is a schematic flowchart of a relay communication method according to an embodiment of the present application. The method 800 can optionally be applied to the system shown in FIG. 7, but is not limited thereto. The method includes at least part of the following contents. Figure 1

[0099] S810, the second terminal receives first information, the first information being used to indicate the relay status information.

[0100] In an embodiment, the first information is in the first message.

[0101] In an embodiment, the first information is indicated by one or more indication bits in the first message.​

[0102] In an embodiment, the first information is at least one of the following in the first message: a layer 2 identity; a relay service code (RSC); a service identity; a physical layer parameter.

[0103] In an embodiment, the physical layer parameter comprises at least one of a relay service reference signal sequence and a reference signal cyclic shift.

[0104] In an embodiment, the relay status information is used to indicate at least one of: operating in a single-hop relay status; operating in a multi-hop relay status; a current hop count.

[0105] In an embodiment, the first message comprises a discovery message.

[0106] Figure 9 is a schematic flowchart of a relay communication method 900 according to another embodiment of the application. The method can comprise one or more features of the above-mentioned methods. In an embodiment, the discovery message comprises a discovery announcement message, S810 the second terminal receives first information comprising: S910, the second terminal receives a discovery announcement message broadcasted by the first terminal, the discovery announcement message being used to indicate relay status information of the first terminal.

[0107] Figure 10 is a schematic flowchart of a relay communication method 1000 according to another embodiment of the application. The method can comprise one or more features of the above-mentioned methods. In an embodiment, the method further comprises: S1010, the second terminal sends a discovery request message to the first terminal, the discovery request message being used to indicate relay status information of the second terminal.

[0108] In an embodiment, as shown in Figure 10 the discovery message comprises a discovery response message, S810 the second terminal receives first information comprising: S1020, the second terminal receives a discovery response message sent by the first terminal, the discovery response message being used to indicate relay status information of the first terminal.

[0109] Figure 11 is a schematic flowchart of a relay communication method 1100 according to another embodiment of the application. The method can comprise one or more features of the above-mentioned methods. In an embodiment, the first message comprises a PC5 signaling message.

[0110] In an embodiment, as shown in Figure 11 The method further comprises: S1110, the second terminal sends a connection setup request message to the first terminal, the connection setup request message being used to indicate the relay status information of the second terminal.

[0111] In an embodiment, the connection setup request message is a Proximity Services Direct Link Setup Request message.

[0112] In an embodiment, the PC5 signaling message comprises a security mode configuration message and / or a connection setup response message, and the second terminal receives the first information, comprising: S1120, the second terminal receives the security mode configuration message and / or the connection setup response message sent by the first terminal, the security mode configuration message and / or the connection setup response message being used to indicate the relay status information of the first terminal.

[0113] In an embodiment, the security mode configuration message is a Proximity Services Direct Link Security Mode Command message, and / or the connection setup response message is a Proximity Services Direct Link Setup Accept message.

[0114] Figure 12 is a schematic flow chart of a relay communication method 1200 according to another embodiment of the present application. The method can comprise one or more features of the above-mentioned methods. In an embodiment, the first message comprises a PC5 radio resource control layer message.

[0115] In an embodiment, the PC5 radio resource control layer message comprises a capability related message, and the method further comprises: S1210, the second terminal sends a first capability related message to the first terminal, the first capability related message being used to indicate the relay status information of the second terminal.

[0116] In an embodiment, as shown in Figure 12 S810, the second terminal receives the first information, comprising: S1220, the second terminal receives a second capability related message sent by the first terminal, the second capability related message being used to indicate the relay status information of the first terminal.

[0117] In an embodiment, the first terminal is a relay terminal.

[0118] In an embodiment, the second terminal is a remote terminal or a target terminal.

[0119] The second terminal of the embodiment can perform the specific examples of the relay communication method 800 to 1200. For brevity, the related descriptions of the second terminal in the embodiments of the first terminal performing the relay communication method 300 to 700 are not repeated here.

[0120] The embodiments of the present application can be used in a multi-hop terminal-to-terminal relay scenario. In order to avoid the traditional UE supporting only single-hop relay being connected to a multi-hop relay, the embodiments of the present application can provide specific signaling interaction processes. The following are several specific examples.

[0121] Example 1: Indication by discovery message In this example, the way of indicating different types of relays (including but not limited to single-hop and multi-hop) through a discovery message can include at least one of the following: 1. Explicit indication: explicitly passing the above indication in the signaling.

[0122] 2. Implicit indication: indicating by at least one of the following information of itself: a) Layer 2 ID: different Layer 2 IDs are reserved for different access control modes, and are distinguished by Layer 2 ID. For example, odd Layer 2 ID indicates single-hop, and even Layer 2 ID indicates multi-hop.

[0123] b) RSC, service ID: different RSCs and / or service IDs are reserved for different access control modes, and are distinguished by RSC and / or service ID. For example, the first value range of RSC and / or service ID indicates single-hop, and the second value range indicates multi-hop.

[0124] c) Physical layer parameters (such as reference signal (RS) sequence, RS cyclic shift): different physical layer parameters are reserved for different access control modes, and are distinguished by physical layer parameters. For example, among the 128 reference signal sequences, the first 64 indicate single-hop, and the last 64 indicate multi-hop.

[0125] As shown in the flow of the discovery indication (only case 1 is shown) Figure 13A ​Case 1. Discovery model-A, where a relay UE (e.g. Relay 1 or Relay 2) indicates the relay capability supported by the relay UE through a broadcast discovery announcement message. For example, in a multi-hop scenario from network to Relay 1 to Relay 2, Relay 1 indicates in the discovery message sent to remote UE that Relay 1 works in single-hop relay status, and Relay 2 indicates in the discovery message sent to remote UE that Relay 2 works in multi-hop relay status. Remote UE decides whether to access Relay 2 or not based on the capability.

[0126] Case 2. Discovery model-B, including: a) Remote UE indicates the relay capability supported by the remote UE through sending a discovery solicitation message, so that a relay UE can determine whether it can be accessed by itself, and / or, b) Relay UE indicates the relay capability supported by the relay UE through sending a discovery response message, so that a remote UE can determine whether it can be accessed by the relay.

[0127] In particular, the content indicated in the messages exchanged between the relay UE and / or remote UE can include: 1. The relay UE can indicate whether it supports single-hop remote UE access, and / or whether it supports multi-hop relay UE access.

[0128] 2. The remote UE can indicate whether it supports access to a multi-hop relay UE.

[0129] The multi-hop in this example can be more than 1 hop.

[0130] Figure 13A The scenario shown is for network relay (relay between network and terminal). As Figure 13B shown, the procedure is similar in the scenario of device relay (relay between terminals).

[0131] Example 2: Indication through PC5-S message In this example, the way to indicate different types of relays (including but not limited to single-hop, multi-hop) through PC5-S message can include at least one of the following: 1. Explicit indication: the above indication is explicitly passed through PC5-S signaling.

[0132] 2. Implicit indication: indicated by at least one of the following information of itself: a) Layer-2 ID: Different Layer-2 IDs are reserved for different access control modes, and are distinguished by Layer-2 ID.

[0133] b) Service ID: Different service IDs are reserved for different access control modes, and are distinguished by service ID.

[0134] c) Physical layer parameters (such as RS sequence, RS cyclic shift): Different physical layer parameters are reserved for different access control modes, and are distinguished by physical layer parameters.

[0135] As shown in Figure 14A , the flow indicated by PC5-S includes: 1. The remote UE indicates the relay capability supported by the remote UE by sending a DCR message, so as to facilitate the relay UE to judge whether it can access through itself, and / or, 2. The relay UE indicates the relay capability supported by the relay UE by sending SMC and / or DCA message, so as to facilitate the remote UE to judge whether it can access through the relay.

[0136] Specifically, the content indicated in the message exchanged between the above-mentioned relay UE and / or remote UE can include: 1. The relay UE can indicate whether it supports access of traditional single-hop remote UE, and / or whether it supports access of multi-hop relay UE.

[0137] 2. The remote UE can indicate whether it supports access of multi-hop relay UE.

[0138] The multi-hop in this example can be more than 1 hop.

[0139] Figure 14A The scenario of network relay (relay between network and terminal) is shown. As Figure 14B shown, in the scenario of device relay (relay between terminals), the flow is also similar.

[0140] Example 3: Indication by PC5-RRC In this example, the way of indicating different types of relays (including but not limited to single-hop, multi-hop) by PC5-RRC message can include at least one of the following: 1. Explicit indication: the above indication is explicitly transmitted in PC5-RRC signaling.

[0141] 2. Implicit indication: indicated by at least one of the following information of itself: a) Layer-2 ID: Different Layer-2 IDs are reserved for different access control modes, and are distinguished by Layer-2 ID.

[0142] b) Physical layer parameters (e.g. RS sequence, RS cyclic shift): Different physical layer parameters are reserved for different access control modes, and the different physical layer parameters are used to distinguish the different access control modes.

[0143] As shown in FIG. 1, the procedure indicated by the PC5-RRC includes: Figure 15A 1. The remote UE indicates the relay capability supported by the remote UE by sending a capability-related message, so as to facilitate the relay UE to determine whether the remote UE can access through the relay UE, and / or, 2. The relay UE indicates the relay capability supported by the relay UE by sending a capability-related message, so as to facilitate the remote UE to determine whether the remote UE can access through the relay UE.

[0144] Specifically, the content indicated in the message exchanged between the relay UE and / or the remote UE can include: 1. The relay UE can indicate whether to support access of a traditional single-hop remote UE and / or whether to support access of a multi-hop relay UE.

[0145] 2. The remote UE can indicate whether to support access of a multi-hop relay UE.

[0146] The multi-hop in the present example can be more than one hop.

[0147] Figure 15A The scenario of network relay (relay between network and terminal) is shown. As shown in FIG. 1, the procedure is similar in the scenario of device relay (relay between terminals). Figure 15B

[0148] Through the scheme of the embodiments of the present application, in the relay scenario, through the specific signaling interaction procedure in the above examples, a suitable relay terminal can be selected to access the network according to the relay type supported by the relay terminal, the remote terminal and the target terminal, so as to solve the backward compatibility problem. For example, a UE that only supports single-hop relay is prevented from being connected to a multi-hop relay UE.

[0149] Figure 16 is a schematic block diagram of a first terminal 1600 according to an embodiment of the present application. The first terminal 1600 can include: A first sending unit 1601 configured to send first information, the first information being used to indicate relay state information.

[0150] In an implementation manner, the first information is in a first message.

[0151] In an implementation manner, the first information is indicated by one or more indication bits in the first message.

[0152] ​​In an embodiment, the first information is at least one of the following in the first message: a layer 2 identity; a relay service code (RSC); a service identity; a physical layer parameter.

[0153] In an embodiment, the physical layer parameter comprises at least one of a relay service reference signal sequence and a reference signal cyclic shift.

[0154] In an embodiment, the relay status information is used to indicate at least one of: working in a single-hop relay status; working in a multi-hop relay status; a current hop count.

[0155] In an embodiment, the first message comprises a discovery message.

[0156] Figure 17 is a schematic flow chart of a first terminal 1700 according to another embodiment of the present application. The first terminal can comprise one or more features of the first terminal described above. In an embodiment, the discovery message comprises a discovery announcement message, and the first sending unit 1601 is further configured to broadcast, to a second terminal, a discovery announcement message, the discovery announcement message being used to indicate relay status information of the first terminal.

[0157] In an embodiment, as shown in Figure 17 the first terminal 1700 further comprises: a first receiving unit 1701 configured to receive a discovery request message sent by a second terminal, the discovery request message being used to indicate relay status information of the second terminal.

[0158] In an embodiment, as shown in Figure 17 the discovery message comprises a discovery response message, and the first sending unit 1601 is further configured to send, to a second terminal, a discovery response message, the discovery response message being used to indicate relay status information of the first terminal.

[0159] In an embodiment, as shown in Figure 17 the first message comprises a PC5 signaling message.

[0160] In an embodiment, as shown in Figure 17 the first terminal 1700 further comprises: a second receiving unit 1702 configured to receive a connection establishment request message sent by a second terminal, the connection establishment request message being used to indicate relay status information of the second terminal.

[0161] In an embodiment, the connection establishment request message is a Proximity Service Direct Link Setup Request message.

[0162] In an embodiment, the PC5 signaling message comprises a security mode configuration message and / or a connection establishment response message, and the first sending unit 1601 is further configured to send the security mode configuration message and / or the connection establishment response message to the second terminal, the security mode configuration message and / or the connection establishment response message being used to indicate the relay status information of the first terminal.

[0163] In an embodiment, the security mode configuration message is a Proximity Service Direct Link Security Mode Command message, and / or the connection establishment response message is a Proximity Service Direct Link Setup Accept message.

[0164] In an embodiment, the first message comprises a PC5 radio resource control layer message.

[0165] In an embodiment, as shown in FIG. 17, the PC5 radio resource control layer message comprises a capability related message, and the first terminal 1700 further comprises: Figure 17 a third receiving unit 1703, configured to receive a first capability related message sent by the second terminal, the first capability related message being used to indicate the relay status information of the second terminal.

[0166] In an embodiment, the first sending unit is further configured to send a second capability related message to the second terminal, the second capability related message being used to indicate the relay status information of the first terminal.

[0167] In an embodiment, the second terminal is a remote terminal or a target terminal.

[0168] In an embodiment, the first terminal is a relay terminal.

[0169] Figure 18 FIG. 18 is a schematic block diagram of a second terminal 1800 according to an embodiment of the present application. The second terminal 1800 can comprise: a first receiving unit 1801, configured to receive first information, the first information being used to indicate relay status information.

[0170] In an embodiment, the first information is in a first message.

[0171] In an embodiment, the first information is indicated by one or more indication bits in the first message.

[0172] In an embodiment, the first information is at least one of the following in the first message: a layer 2 identity; a relay service code (RSC);​ service identity; physical layer parameter.

[0173] In an embodiment, the physical layer parameter comprises at least one of a relay service reference signal sequence and a reference signal cyclic shift.

[0174] In an embodiment, the relay status information is used to indicate at least one of: operating in a single-hop relay status; operating in a multi-hop relay status; a current hop count.

[0175] In an embodiment, the first message comprises a discovery message.

[0176] Figure 19 is a schematic flowchart of a second terminal 1900 according to another embodiment of the present application. The second terminal can comprise one or more features of the terminals described above. In an embodiment, the discovery message comprises a discovery announcement message, and the first receiving unit 1801 is further configured to receive a discovery announcement message broadcasted by the first terminal, the discovery announcement message being used to indicate relay status information of the first terminal.

[0177] In an embodiment, the discovery message comprises a discovery response message, and the first receiving unit 1801 is further configured to receive a discovery response message sent by the first terminal, the discovery response message being used to indicate relay status information of the first terminal.

[0178] Figure 19 is a schematic flowchart of a second terminal 1900 according to another embodiment of the present application. The second terminal can comprise one or more features of the second terminals described above. In an embodiment, the second terminal 1900 further comprises: a first sending unit 1901 configured to send a discovery request message to the first terminal, the discovery request message being used to indicate relay status information of the second terminal.

[0179] In an embodiment, as shown in Figure 19 the discovery message comprises a discovery response message, and the first receiving unit 1801 is further configured to receive a discovery response message sent by the first terminal, the discovery response message being used to indicate relay status information of the first terminal.

[0180] In an embodiment, the first message comprises a PC5 signaling message.

[0181] In an embodiment, as shown in Figure 19 the second terminal 1900 further comprises: The second sending unit 1902 is used to send a connection establishment request message to the first terminal, the connection establishment request message being used to indicate the relay status information of the second terminal.

[0182] In one implementation, the connection establishment request message is a direct link establishment request message for neighboring services.

[0183] In one embodiment, the PC5 signaling message includes a security mode configuration message and / or a connection establishment response message. The first receiving unit 1801 is further configured to receive the security mode configuration message and / or connection establishment response message sent by the first terminal. The security mode configuration message and / or connection establishment response message are used to indicate the relay status information of the first terminal.

[0184] In one implementation, the security mode configuration message is a neighboring service direct link security mode command message, and / or the connection establishment response message is a neighboring service direct link establishment accept message.

[0185] In one implementation, the first message includes a PC5 radio resource control layer message.

[0186] In one implementation, such as Figure 19 As shown, the PC5 radio resource control layer message includes capability-related messages, and the second terminal 1900 also includes: The third sending unit 1903 is used to send a first capability-related message to the first terminal, the first capability-related message being used to indicate the relay status information of the second terminal.

[0187] In one embodiment, the first receiving unit 1801 is further configured to receive a second capability-related message sent by the first terminal, the second capability-related message being used to indicate the relay status information of the first terminal.

[0188] In one implementation, the first terminal is a relay terminal.

[0189] In one implementation, the second terminal is a remote terminal or a target terminal.

[0190] The second terminals 1800 and 1900 in this embodiment can implement the corresponding functions of the second terminal in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in this second terminal can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the second terminal of this embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0191] Figure 20 FIG. 20 is a schematic structural diagram of a communication device 2000 according to an embodiment of the present application. The communication device 2000 includes a processor 2010. The processor 2010 can invoke and run a computer program from a memory, so that the communication device 2000 implements the method in the embodiments of the present application.

[0192] In an embodiment, the communication device 2000 can further include a memory 2020. The processor 2010 can invoke and run a computer program from the memory 2020, so that the communication device 2000 implements the method in the embodiments of the present application.

[0193] The memory 2020 can be a separate device independent of the processor 2010, or can be integrated in the processor 2010.

[0194] In an embodiment, the communication device 2000 can further include a transceiver 2030. The processor 2010 can control the transceiver 2030 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0195] The transceiver 2030 can include a transmitter and a receiver. The transceiver 2030 can further include an antenna, and the number of antennas can be one or more.

[0196] In an embodiment, the communication device 2000 can be a first terminal of the embodiments of the present application, and the communication device 2000 can implement the corresponding processes implemented by the first terminal in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0197] In an embodiment, the communication device 2000 can be a second terminal of the embodiments of the present application, and the communication device 2000 can implement the corresponding processes implemented by the second terminal in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0198] Figure 21 FIG. 21 is a schematic structural diagram of a chip 2100 according to an embodiment of the present application. The chip 2100 includes a processor 2110. The processor 2110 can invoke and run a computer program from a memory, so that the chip 2100 implements the method in the embodiments of the present application.

[0199] In an embodiment, the chip 2100 can further include a memory 2120. The processor 2110 can invoke and run a computer program from the memory 2120, so that the chip 2100 implements the method in the embodiments of the present application.

[0200] The memory 2120 can be a separate device independent of the processor 2110, or can be integrated in the processor 2110.

[0201] In an embodiment, the chip 2100 can further include an input interface 2130. The processor 2110 can control the input interface 2130 to communicate with other devices or chips, and specifically, can acquire information or data sent by other devices or chips.

[0202] In an embodiment, the chip 2100 can further include an output interface 2140. The processor 2110 can control the output interface 2140 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

[0203] In an embodiment, the chip can be applied to the first terminal in the embodiments of the present application, and the chip can implement the corresponding procedures implemented by the first terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

[0204] In an embodiment, the chip can be applied to the second terminal in the embodiments of the present application, and the chip can implement the corresponding procedures implemented by the second terminal in the various methods of the embodiments of the present application. For the sake of brevity, details are not repeated here.

[0205] The chip applied to the first terminal and the second terminal can be the same chip or different chips.

[0206] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

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

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

[0209] It should be understood that the above-mentioned memory is an example but not a limiting description, for example, the memory in the embodiments of the present application can also be a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM), and a direct memory bus random access memory (Direct Rambus RAM, DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable type of memory.

[0210] Figure 22 is a schematic block diagram of a communication system 2200 according to the embodiments of the present application. The communication system 2200 includes a first terminal 2210 and a second terminal 2220.

[0211] The first terminal 2210 is configured to send first information, the first information being used to indicate relay status information.

[0212] The second terminal 2220 is configured to receive the first information, the first information being used to indicate relay status information.

[0213] The first terminal 2210 can be configured to implement the corresponding functions of the first terminal in the above-mentioned method, and the second terminal 2220 can be configured to implement the corresponding functions of the second terminal in the above-mentioned method. For the sake of brevity, it will not be repeated here.

[0214] In the above embodiments, all or part of the processes can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the processes can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed by a computer, the computer instructions generate all or part of the processes or functions in the embodiments of the present application. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center through a wired (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. containing one or more available media sets. The available medium can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, solid state disk (SSD)), etc.

[0215] It should be understood that the size of the sequence number of each process described above in various embodiments of the present application does not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0216] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0217] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A relay communication method, comprising: a first terminal sending first information, the first information being used to indicate relay status information.

2. The method of claim 1, wherein, the first information being in a first message.

3. The method of claim 2, wherein, the first information being a relay service code (RSC) in the first message.

4. The method of claim 2, wherein, the relay status information being used to indicate at least one of: working in a single-hop relay state; and working in a multi-hop relay state.

5. The method of any one of claims 2 to 4, wherein, the first message comprising a discovery message.

6. The method of claim 5, wherein, the discovery message comprising a discovery announcement message, the first terminal sending the first information comprising: the first terminal broadcasting a discovery announcement message to a second terminal, the discovery announcement message being used to indicate the relay status information of the first terminal.

7. The method of claim 6, wherein, the discovery message comprising a discovery response message, the first terminal sending the first information comprising: the first terminal sending a discovery response message to a second terminal, the discovery response message being used to indicate the relay status information of the first terminal. 8.A relay communication method, comprising: a second terminal receiving first information, the first information being used to indicate relay status information. 9.A first terminal, comprising: a first sending unit configured to send first information, the first information being used to indicate relay status information.

10. The first terminal according to claim 9, wherein, the first information being in a first message.

11. The first terminal according to claim 10, wherein the first information being a relay service code (RSC) in the first message.

12. The first terminal according to claim 10, wherein the relay status information being used to indicate at least one of: working in a single-hop relay state; and working in a multi-hop relay state.

13. The first terminal according to any one of claims 10 to 12, wherein, the first message comprising a discovery message.

14. The first terminal according to claim 13, wherein, the discovery message comprising a discovery announcement message, the first sending unit being further configured to broadcast a discovery announcement message to a second terminal, the discovery announcement message being used to indicate the relay status information of the first terminal. the discovery message comprising a discovery response message, the first sending unit being further configured to send a discovery response message to a second terminal, the discovery response message being used to indicate the relay status information of the first terminal. 15.A second terminal, comprising: a first receiving unit configured to receive first information, the first information being used to indicate relay status information.

16. The second terminal according to claim 15, wherein the first information being in a first message.

17. The second terminal according to claim 16, wherein the first information being a relay service code (RSC) in the first message.

18. The second terminal according to claim 16 or 17, wherein, the first message comprising a discovery message.

19. The second terminal according to claim 18, wherein, the discovery message comprising a discovery announcement message, the first receiving unit being further configured to receive a discovery announcement message broadcasted by a first terminal, the discovery announcement message being used to indicate the relay status information of the first terminal. the discovery message comprising a discovery response message, the first receiving unit being further configured to receive a discovery response message sent by a first terminal, the discovery response message being used to indicate the relay status information of the first terminal.

20. A terminal device comprising: a processor and a memory, the memory being configured to store a computer program, the processor being configured to invoke and run the computer program stored in the memory, so that the terminal device performs the method according to any one of claims 1 to 7 or 8.

Images