An information sending method and device

Abstract

The present invention provides an information sending method and apparatus, relating to the field of communication technologies. The method of the present invention is applied to a scenario where a remote terminal establishes communication with a network-side device through a relay terminal, and the method includes: obtaining first relevant information generated during the communication process, and sending the first relevant information to the network-side device; wherein the first relevant information includes one or more combinations of the following: relay terminal information; remote terminal information; identification information of a serving cell; time information; measurement information; cause information; type information corresponding to the communication process; and a successful handover report triggering condition. The solution of the present invention realizes the optimization of mobile robustness in a multi-hop network scenario.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to a method and apparatus for information transmission. Background Art

[0002] With the development of communication technologies, in order to achieve extended coverage, multi-hop communication has become the focus of current research. Multi-hop communication is the transmission of information to a network device by a terminal device through the forwarding of one or more relay devices.

[0003] However, the existing mobile robustness optimization of Self-Optimisation Network (SON) or Minimal Drive Test (MDT) mainly targets single-hop networks. In a multi-hop communication network, if a terminal collects information according to the information collection method of a single-hop network, the base station will not be able to identify the multi-hop network after receiving the report reported by the terminal, and thus the optimization of the multi-hop network cannot be achieved. Summary of the Invention

[0004] The purpose of the present invention is to provide a method and apparatus for information transmission, so as to achieve the mobile robustness optimization of a multi-hop network scenario and help the network better optimize the multi-hop network.

[0005] To achieve the above purpose, an embodiment of the present invention provides a method for information transmission, which is applied to a remote terminal to establish communication with a network-side device through a relay terminal, and includes:

[0006] Obtain first relevant information generated during the communication, and send the first relevant information to the network-side device;

[0007] Wherein, the first relevant information includes one or more combinations of the following:

[0008] Relay terminal information;

[0009] Remote terminal information;

[0010] Identification information of the serving cell;

[0011] Time information;

[0012] Measurement information;

[0013] Cause information;

[0014] Type information corresponding to the communication process;

[0015] Successive handover report triggering condition.

[0016] Optionally, the communication process includes one or more combinations of the following:

[0017] Connection establishment process;

[0018] Connection recovery process;

[0019] Radio link failure process;

[0020] Handover process.

[0021] Optionally, the relay terminal information includes: identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, location information of the relay terminal;

[0022] Wherein, the specified event includes at least one of the following events:

[0023] Connection establishment;

[0024] Radio link failure (RLF) detected;

[0025] Handover failure (HOF) detected;

[0026] Handover;

[0027] Return to connection after connection failure or re - establishment failure;

[0028] Re - establishment after connection failure;

[0029] Attempt to establish a PC5 connection after a remote terminal RLF, where RLF includes PC5 RLF or Uu RLF;

[0030] Attempt to establish a PC5 connection after a remote terminal HOF.

[0031] Optionally, the remote terminal information includes one or more combinations of the following:

[0032] Identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0033] Location information of the remote terminal;

[0034] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0035] Optionally, the time information includes one or more combinations of the following:

[0036] The duration from establishing the PC5 connection to the occurrence of the communication process;

[0037] The duration from the handover - related moment to RLF;

[0038] The duration experienced after RLF is detected;

[0039] The duration from RLF to establishing the PC5 connection;

[0040] Duration experienced after HOF is detected;

[0041] Duration from HOF to the establishment of a PC5 connection;

[0042] Duration from the establishment of a PC5 connection to entering the Radio Resource Control (RRC) connected state;

[0043] Duration from Radio Link Failure (RLF) to entering the RRC connected state;

[0044] Duration from HOF to entering the RRC connected state;

[0045] Wherein, RLF includes PC5 RLF or Uu RLF.

[0046] Optionally, the measurement information includes one or more combinations of the following:

[0047] PC5 measurement results of the remote terminal;

[0048] PC5 measurement results between the remote terminal and the relay terminal that has established a PC5 connection with the remote terminal;

[0049] Uu link measurement results of the remote terminal;

[0050] PC5 measurement results of the relay terminal;

[0051] PC5 measurement results between the relay terminal and the remote terminal that has established a PC5 connection with the relay terminal;

[0052] Uu link measurement results of the relay terminal.

[0053] Optionally, the cause information includes one or more combinations of the following:

[0054] Cause of connection establishment failure, wherein the connection establishment includes the relay terminal assisting the remote terminal in establishing a connection;

[0055] Cause of connection recovery failure;

[0056] Cause of radio link failure, wherein the radio link includes a PC5 link or a Uu link;

[0057] Cause of connection establishment, which is to establish a connection for the remote terminal.

[0058] Optionally, if the radio link is a PC5 link, the cause of radio link failure includes one or more combinations of the following:

[0059] T400 timer timeout;

[0060] The number of transmissions of the sidelink Radio Link Control (RLC) entity is greater than or equal to the first number of transmissions;

[0061] The number of consecutive Hybrid Automatic Repeat reQuest (HARQ) discontinuous transmissions of the Medium Access Control (MAC) entity is greater than or equal to the second transmission number;

[0062] The integrity check of the sidelink signaling radio bearer associated with the sidelink Packet Data Convergence Protocol (PDCP) entity fails.

[0063] Optionally, the connection establishment failure reason includes one or more of the following combinations:

[0064] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails;

[0065] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0066] Optionally, the connection recovery failure reason includes one or more of the following combinations:

[0067] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails;

[0068] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0069] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0070] Connection failure type, and the connection failure type includes one or more of the following combinations: Radio Link Failure (RLF) of the remote terminal, Handover Failure (HOF) of the remote terminal;

[0071] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0072] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0073] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0074] Timer T400 is greater than the timer threshold and has not timed out;

[0075] The number of transmissions of the sidelink Radio Link Control (RLC) entity is greater than or equal to the first transmission threshold and less than the first transmission number;

[0076] The number of consecutive HARQ discontinuous transmissions of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission number.

[0077] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0078] The identification information of the source cell of the last handover;

[0079] When it was a PC5 connection before handover, the identification information of the serving cell of the remote terminal before the last handover;

[0080] The identification information of the serving cell of the remote terminal where RLF is detected;

[0081] The identification information of the serving cell of the remote terminal where HOF is detected;

[0082] The identification information of the serving cell of the remote terminal that returns a connection after connection failure;

[0083] The identification information of the serving cell of the remote terminal that returns a connection after reconstruction failure.

[0084] Optionally, the identification information includes one or more of the following combinations:

[0085] Cell Radio Network Temporary Identifier C-RNTI;

[0086] Layer 2 identifier.

[0087] To achieve the above object, an embodiment of the present invention further provides an information sending device, including: a memory, a transceiver, and a processor;

[0088] The memory is used to store program instructions; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the program instructions in the memory;

[0089] The transceiver is used to perform the following operations:

[0090] Obtain first related information generated during communication, and send the first related information to the network side device;

[0091] Wherein, the communication is a communication established by a remote terminal through a relay terminal with the network side device; the first related information includes one or more of the following combinations:

[0092] Relay terminal information;

[0093] Remote terminal information;

[0094] The identification information of the serving cell;

[0095] Time information;

[0096] Measurement information;

[0097] Cause information;

[0098] The type information corresponding to the communication process;

[0099] Success handover report trigger condition.

[0100] Optionally, the communication process includes one or more of the following combinations:

[0101] Connection establishment process;

[0102] Connection recovery process;

[0103] Radio link failure process;

[0104] Handover process.

[0105] Optionally, the relay terminal information includes: identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, location information of the relay terminal;

[0106] Wherein, the specified event includes at least one of the following events:

[0107] Connection establishment;

[0108] Detecting radio link failure RLF;

[0109] Detecting handover failure HOF;

[0110] Handover;

[0111] Returning to the connection after connection failure or reconstruction failure;

[0112] Re - establishing after connection failure;

[0113] Attempting to establish a PC5 connection after the remote terminal RLF, where RLF includes PC5 RLF or Uu RLF;

[0114] Attempting to establish a PC5 connection after the remote terminal HOF.

[0115] Optionally, the remote terminal information includes one or more of the following combinations:

[0116] Identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0117] Location information of the remote terminal;

[0118] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0119] Optionally, the time information includes one or more of the following combinations:

[0120] Establish the duration of the occurrence of the PC5 connection to the communication process;

[0121] The duration from the handover-related moment to RLF;

[0122] The duration experienced after detecting RLF;

[0123] The duration from RLF to establishing a PC5 connection;

[0124] The duration experienced after detecting HOF;

[0125] The duration from HOF to establishing a PC5 connection;

[0126] The duration from establishing a PC5 connection to entering the Radio Resource Control (RRC) connected state;

[0127] The duration from RLF to entering the RRC connected state;

[0128] The duration from HOF to entering the RRC connected state;

[0129] Wherein, RLF includes PC5 RLF or Uu RLF.

[0130] Optionally, the measurement information includes one or more combinations of the following:

[0131] PC5 measurement results of the remote terminal;

[0132] PC5 measurement results between the remote terminal and the relay terminal that establishes a PC5 connection with the remote terminal;

[0133] Uu link measurement results of the remote terminal;

[0134] PC5 measurement results of the relay terminal;

[0135] PC5 measurement results between the relay terminal and the remote terminal that establishes a PC5 connection with the relay terminal;

[0136] Uu link measurement results of the relay terminal.

[0137] Optionally, the cause information includes one or more combinations of the following:

[0138] Reasons for connection establishment failure, wherein the connection establishment includes the relay terminal assisting the remote terminal in establishing a connection;

[0139] Reasons for connection recovery failure;

[0140] Reasons for radio link failure, wherein the radio link includes a PC5 link or a Uu link;

[0141] Reasons for connection establishment, and the connection establishment reason is to establish a connection for the remote terminal.

[0142] Optionally, if the wireless link is a PC5 link, the wireless link failure cause includes one or more of the following combinations:

[0143] The T400 timer expires;

[0144] The transmission times of the sidelink radio link control (RLC) entity are greater than or equal to the first transmission times;

[0145] The consecutive hybrid automatic repeat request (HARQ) discontinuous transmission times of the media access control (MAC) entity are greater than or equal to the second transmission times;

[0146] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0147] Optionally, the connection establishment failure cause includes one or more of the following combinations:

[0148] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails;

[0149] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0150] Optionally, the connection recovery failure cause includes one or more of the following combinations:

[0151] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails;

[0152] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0153] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0154] Connection failure type, and the connection failure type includes one or more of the following combinations: remote terminal radio link failure (RLF), remote terminal handover failure (HOF);

[0155] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0156] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0157] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0158] The T400 timer is greater than the timer threshold and has not timed out;

[0159] The transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold and less than the first transmission count;

[0160] The consecutive HARQ discontinuous transmission count of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission count.

[0161] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0162] The identification information of the source cell of the last handover;

[0163] When it was a PC5 connection before handover, the identification information of the serving cell of the remote terminal before the last handover;

[0164] The identification information of the serving cell of the remote terminal where RLF was detected;

[0165] The identification information of the serving cell of the remote terminal where HOF was detected;

[0166] The identification information of the serving cell of the remote terminal that returns a connection after connection failure;

[0167] The identification information of the serving cell of the remote terminal that returns a connection after reconstruction failure.

[0168] Optionally, the identification information includes one or more of the following combinations:

[0169] Cell Radio Network Temporary Identifier C-RNTI;

[0170] Layer 2 identifier.

[0171] To achieve the above object, an embodiment of the present invention further provides an information sending device, including:

[0172] A first sending module, configured to obtain first relevant information generated during communication and send the first relevant information to a network-side device;

[0173] Wherein, the communication is a communication established by a remote terminal through a relay terminal with a network-side device; the first relevant information includes one or more of the following combinations:

[0174] Relay terminal information;

[0175] Remote terminal information;

[0176] Identification information of the serving cell;

[0177] Time information;

[0178] Measurement information;

[0179] Cause information;

[0180] Type information corresponding to the communication process;

[0181] Success handover report trigger condition.

[0182] Optionally, the communication process includes one or more of the following combinations:

[0183] Connection establishment process;

[0184] Connection recovery process;

[0185] Radio link failure process;

[0186] Handover process.

[0187] Optionally, the relay terminal information includes: identification information of the relay terminal; and / or, the corresponding relationship between the identification information and a specified event; and / or, location information of the relay terminal;

[0188] Wherein, the specified event includes at least one of the following events:

[0189] Connection establishment;

[0190] Detecting a radio link failure RLF;

[0191] Detecting a handover failure HOF;

[0192] Handover;

[0193] Returning to the connection after a connection failure or a reestablishment failure;

[0194] Reestablishing after a connection failure;

[0195] Attempting to establish a PC5 connection after a remote terminal RLF, where the RLF includes a PC5 RLF or a Uu RLF;

[0196] Attempting to establish a PC5 connection after a remote terminal HOF.

[0197] Optionally, the remote terminal information includes one or more of the following combinations:

[0198] Identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0199] Location information of the remote terminal;

[0200] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0201] Optionally, the time information includes one or more of the following combinations:

[0202] Establish the duration of the occurrence of the PC5 connection to the communication process;

[0203] The duration from the relevant moment of handover to RLF;

[0204] The duration experienced after RLF is detected;

[0205] The duration from RLF to the establishment of the PC5 connection;

[0206] The duration experienced after HOF is detected;

[0207] The duration from HOF to the establishment of the PC5 connection;

[0208] The duration from the establishment of the PC5 connection to entering the radio resource control (RRC) connection state;

[0209] The duration from RLF to entering the RRC connection state;

[0210] The duration from HOF to entering the RRC connection state;

[0211] Wherein, RLF includes PC5 RLF or Uu RLF.

[0212] Optionally, the measurement information includes one or more combinations of the following:

[0213] PC5 measurement results of the remote terminal;

[0214] PC5 measurement results between the remote terminal and the relay terminal that establishes a PC5 connection with the remote terminal;

[0215] Uu link measurement results of the remote terminal;

[0216] PC5 measurement results of the relay terminal;

[0217] PC5 measurement results between the relay terminal and the remote terminal that establishes a PC5 connection with the relay terminal;

[0218] Uu link measurement results of the relay terminal.

[0219] Optionally, the cause information includes one or more combinations of the following:

[0220] Reasons for connection establishment failure, wherein the connection establishment includes the relay terminal assisting the remote terminal to establish a connection;

[0221] Reasons for connection recovery failure;

[0222] Reasons for radio link failure, wherein the radio link includes a PC5 link or a Uu link;

[0223] Connection establishment cause, where the connection establishment cause is to establish a connection for a remote terminal.

[0224] Optionally, if the wireless link is a PC5 link, the wireless link failure cause includes one or more of the following combinations:

[0225] Timeout of timer T400;

[0226] The number of transmissions of the sidelink radio link control (RLC) entity is greater than or equal to the first number of transmissions;

[0227] The number of consecutive hybrid automatic repeat request (HARQ) discontinuous transmissions of the media access control (MAC) entity is greater than or equal to the second number of transmissions;

[0228] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0229] Optionally, the connection establishment failure cause includes one or more of the following combinations:

[0230] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails;

[0231] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0232] Optionally, the connection recovery failure cause includes one or more of the following combinations:

[0233] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails;

[0234] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0235] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0236] Connection failure type, where the connection failure type includes one or more of the following combinations: remote terminal radio link failure (RLF), remote terminal handover failure (HOF);

[0237] Handover type, where the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0238] Handover failure type, where the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0239] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0240] The T400 timer is greater than the timer threshold and not timed out;

[0241] The transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold and less than the first transmission count;

[0242] The consecutive HARQ discontinuous transmission count of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission count.

[0243] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0244] The identification information of the source cell of the last handover;

[0245] When it was a PC5 connection before handover, the identification information of the serving cell of the remote terminal before the last handover;

[0246] The identification information of the serving cell of the remote terminal where RLF is detected;

[0247] The identification information of the serving cell of the remote terminal where HOF is detected;

[0248] The identification information of the serving cell of the remote terminal that returns to the connection after connection failure;

[0249] The identification information of the serving cell of the remote terminal that returns to the connection after reconstruction failure.

[0250] Optionally, the identification information includes one or more of the following combinations:

[0251] Cell Radio Network Temporary Identifier C-RNTI;

[0252] Layer 2 identifier.

[0253] To achieve the above object, an embodiment of the present invention further provides a processor-readable storage medium, where the processor-readable storage medium stores program instructions, and the program instructions are used to cause the processor to execute the transmission processing method executed by the first terminal as described above, or the transmission processing method executed by the second terminal, or the transmission processing method executed by the network-side device.

[0254] To achieve the above object, an embodiment of the present invention further provides a communication device, where the communication device stores program instructions, and the program instructions are used to cause the communication device to execute the information sending method as described above.

[0255] An embodiment of the present invention further provides a computer-readable storage medium, in which program instructions are stored, and the program instructions are used to execute the information sending method as described above.

[0256] An embodiment of the present invention further provides a computer program product, in which program instructions are stored, and the program instructions are used to execute the information sending method as described above.

[0257] The above technical solution of the present invention has at least the following beneficial effects:

[0258] In the application scenario where the remote terminal establishes communication with the network side device through the relay terminal in the above technical solution of the embodiment of the present invention, by obtaining the first relevant information generated during the communication process, the first relevant information includes at least one of relay terminal information, remote terminal information, identification information of the serving cell, time information, measurement information, cause information, type information corresponding to the communication process, and successful handover report triggering conditions, and sending the first relevant information to the network side device, different terminals collect their corresponding information according to the relevant operations performed by themselves in the communication and report the collected information to the network side device. In this way, after receiving the first relevant information, the network side device can identify the multi-hop network characteristics and then perform multi-hop network mobile robustness optimization based on the first relevant information. BRIEF DESCRIPTION OF THE DRAWINGS

[0259] Figure 1 Schematic diagram of the remote terminal, relay terminal to the network;

[0260] Figure 2 Flow chart of the method of the embodiment of the present invention;

[0261] Figure 3 One of the schematic diagrams of the scenario in the embodiment of the present invention;

[0262] Figure 4 Another schematic diagram of the scenario in the embodiment of the present invention;

[0263] Figure 5 Another schematic diagram of the scenario in the embodiment of the present invention;

[0264] Figure 6 Another schematic diagram of the scenario in the embodiment of the present invention;

[0265] Figure 7 Another schematic diagram of the scenario in the embodiment of the present invention;

[0266] Figure 8 Another schematic diagram of the scenario in the embodiment of the present invention;

[0267] Figure 9Schematic flowchart of the method according to another embodiment of the present invention;

[0268] Figure 10 One of the structural block diagrams of the device according to the embodiment of the present invention;

[0269] Figure 11 One of the module diagrams of the device according to the embodiment of the present invention;

[0270] Figure 12 Another structural diagram of the device according to the embodiment of the present invention;

[0271] Figure 13 Another module block diagram of the device according to the embodiment of the present invention. Detailed implementation manners

[0272] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0273] In the embodiments of the present application, the term "a plurality of" refers to two or more, and other quantifiers are similar thereto.

[0274] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0275] It should be noted that in a multi-hop network, a relay node is introduced. The relay node can be a terminal with relay function, also known as a relay terminal. The schematic diagram of user equipment to network (UE-to-Network Relay) is as Figure 1 shown. The communication interface between the relay terminal (relay UE) and the network-side device is the Uu interface, and the communication interface between the relay terminal and the remote terminal (remote UE) is a direct communication interface (for example: PC5 interface). The link between the relay terminal and the network-side device can be called a backhaul link (Backhaul link, BH) relative to the remote terminal. It should be noted that currently Figure 1A communication connection is established between the remote terminal shown in the figure and the network-side device through a relay terminal. In practical applications, the remote terminal can establish a communication connection with the network-side device through multiple relay terminals. Among them, the relay terminal close to the network-side device can also be called a UE-to-Network terminal; the relay terminal close to the remote terminal can also be called a UE-to-UE terminal. In the embodiments of this application, an example of two hops from the remote terminal to the network-side device is used for illustration.

[0276] Combined with Figure 1 As shown, for the remote terminal, in a good network environment, the remote terminal can directly establish communication with the network-side device through Uu. At this time, the remote terminal can be understood as an ordinary terminal, and collect various information generated during the communication process according to the existing method (single-hop network method) and report it to the network-side device; however, in a bad network environment, the remote terminal needs to establish communication with the network-side device through a relay terminal. First, the remote terminal needs to establish a connection with the relay terminal through a direct communication interface (for example: PC5 interface) (this connection is hereinafter referred to as a PC5 connection). Then the remote terminal needs to collect various information generated during the establishment of the PC5 connection and the subsequent communication process, and record the corresponding relationship between this information and the PC5; secondly, the remote terminal sends a message for requesting to establish communication with the network-side device to the relay terminal through the PC5 connection. After the remote terminal sends this message, it will record the interaction information generated by this message between the remote terminal and the relay terminal (including the response content of the network-side device forwarded by the relay terminal), and send the information recorded in each stage to the network-side device. That is to say, in a multi-hop network, the remote terminal may either directly establish communication with the network-side device through Uu or establish communication with the network-side device through a relay terminal based on PC5. However, the main content studied in the embodiments of this application is all the information generated during the process of the remote terminal establishing communication with the network-side device through the relay terminal of the PC5 connection (especially the information that can reflect the multi-hop characteristics).

[0277] For a relay terminal, if it does not receive a message from a remote terminal requesting to establish communication with a network-side device, then the relay terminal can act as an ordinary terminal and establish communication with the network-side device in a single-hop network manner, and collect various information generated during this communication process; if it receives a message from a remote terminal requesting to establish communication with the network-side device, then the relay terminal will no longer be an ordinary terminal. It will passively establish communication with the network-side device according to the received message, and record various information generated during this communication process, as well as record various information generated during the connection establishment process with the remote terminal. In this way, after receiving the information sent by the remote terminal and the relay terminal, the network-side device can identify which information is single-hop network information and which information is multi-hop network information, and then optimize the multi-hop network according to the information related to the multi-hop network. The following takes a two-hop network as an example for illustration.

[0278] As Figure 2 shown, an information sending method provided by an embodiment of the present invention is applied to a remote terminal establishing communication with a network-side device through a relay terminal, including:

[0279] Step 201, obtain first relevant information generated during the communication process;

[0280] Step 202, send the first relevant information to the network-side device.

[0281] Wherein, the first relevant information includes one or more combinations of the following:

[0282] Relay terminal information;

[0283] Remote terminal information;

[0284] Identification information of the serving cell;

[0285] Time information;

[0286] Measurement information;

[0287] Cause information;

[0288] Type information corresponding to the communication process;

[0289] Successive handover report triggering conditions.

[0290] Thus, in an application scenario where a remote terminal establishes communication with a network-side device through a relay terminal, by obtaining first relevant information generated during the communication process, the first relevant information includes at least one of relay terminal information, remote terminal information, identification information of the serving cell, time information, measurement information, cause information, type information corresponding to the communication process, and successful handover report triggering conditions, and sending the first relevant information to the network-side device, different terminals collect their corresponding information according to the relevant operations they perform during the communication and record the corresponding relationship between this information and the operations performed. In this way, after receiving the first relevant information, the network-side device can identify the multi-hop network characteristics and then perform mobile robustness optimization for the multi-hop network based on the first relevant information.

[0291] Optionally, the communication process includes one or more of the following combinations:

[0292] Connection establishment process;

[0293] Connection recovery process;

[0294] Radio link failure process;

[0295] Handover process.

[0296] Specifically, the connection establishment process can be a successful connection establishment process or a failed connection establishment process; the connection recovery process can be a successful connection recovery process or a failed connection recovery process; the handover process can be a successful handover process or a failed handover process.

[0297] In this embodiment, the remote terminal connection establishment process in a multi-hop network scenario includes two cases: the first case is that there is no RRC connection established between the relay terminal and the network-side device, and the second case is that there is already an RRC connection established between the relay terminal and the network-side device.

[0298] For the first case, after receiving the RRC connection establishment request from the remote terminal, the relay terminal establishes an RRC connection between the relay terminal and the network-side device; after establishing the connection, it forwards the remote terminal's connection establishment request to the network-side device. In this case, if the RRC connection establishment between the relay terminal and the network fails, it will in turn cause the RRC connection establishment of the remote terminal to fail.

[0299] For the second case, the relay terminal directly forwards the RRC connection establishment request of the remote terminal to assist the remote terminal in establishing an RRC connection.

[0300] In this embodiment, the connection recovery process in a multi-hop network scenario is similar to the connection establishment process and will not be elaborated here.

[0301] In this embodiment, the wireless link failure process in a multi-hop network scenario includes two cases. The first case is that the remote terminal detects a PC5 RLF, and the second case is that the relay terminal detects a Uu RLF. For the first case, after the remote terminal detects a PC5 RLF, it will trigger an RLF. For the second case, the relay terminal will send Uu RLF indication information to the remote terminal to notify the remote terminal of the abnormal Uu link, and the remote terminal will trigger an RLF after receiving the indication information.

[0302] In this embodiment, the handover process in a multi-hop network scenario includes: the handover between the direct connection and the PC5 connection between the remote terminal and the network-side device, the handover from the PC5 connection to the direct connection, and the handover from the PC5 connection to the PC5 connection (i.e., reselecting the relay terminal).

[0303] Optionally, the relay terminal information includes: the identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, the location information of the relay terminal;

[0304] Wherein, the specified event includes at least one of the following events:

[0305] Connection establishment;

[0306] Detecting a radio link failure (RLF);

[0307] Detecting a handover failure (HOF);

[0308] Handover;

[0309] Returning to the connection after connection failure or reconnection failure;

[0310] Re-establishing after connection failure;

[0311] Attempting to establish a PC5 connection after the remote terminal's RLF, where the RLF includes a PC5 RLF or a Uu RLF;

[0312] Attempting to establish a PC5 connection after the remote terminal's HOF.

[0313] Optionally, the remote terminal information includes one or more of the following combinations:

[0314] The identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0315] The location information of the remote terminal;

[0316] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0317] Optionally, the time information includes one or more of the following combinations:

[0318] Establish the duration of the PC5 connection for the occurrence of the communication process;

[0319] The duration from the handover-related moment to RLF;

[0320] The duration experienced after RLF is detected;

[0321] The duration from RLF to the establishment of the PC5 connection;

[0322] The duration experienced after HOF is detected;

[0323] The duration from HOF to the establishment of the PC5 connection;

[0324] The duration from the establishment of the PC5 connection to entering the Radio Resource Control (RRC) connected state;

[0325] The duration from RLF to entering the RRC connected state;

[0326] The duration from HOF to entering the RRC connected state;

[0327] Wherein, RLF includes PC5 RLF or Uu RLF.

[0328] Optionally, the measurement information includes one or more of the following combinations:

[0329] PC5 measurement results of the remote terminal;

[0330] PC5 measurement results between the remote terminal and the relay terminal that establishes a PC5 connection with the remote terminal;

[0331] Uu link measurement results of the remote terminal;

[0332] PC5 measurement results of the relay terminal;

[0333] PC5 measurement results between the relay terminal and the remote terminal that establishes a PC5 connection with the relay terminal;

[0334] Uu link measurement results of the relay terminal.

[0335] Optionally, the cause information includes one or more of the following combinations:

[0336] Reasons for connection establishment failure, wherein the connection establishment includes the relay terminal assisting the remote terminal to establish a connection;

[0337] Reasons for connection recovery failure;

[0338] Reasons for radio link failure, wherein the radio link includes a PC5 link or a Uu link;

[0339] Reasons for connection establishment, and the connection establishment reason is to establish a connection for the remote terminal.

[0340] Optionally, if the radio link is a PC5 link, the radio link failure cause includes one or more of the following combinations:

[0341] Timeout of the T400 timer;

[0342] The transmission times of the sidelink radio link control (RLC) entity are greater than or equal to the first transmission times;

[0343] The number of consecutive hybrid automatic repeat request (HARQ) discontinuous transmissions of the media access control (MAC) entity is greater than or equal to the second transmission times;

[0344] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0345] Optionally, the connection establishment failure cause includes one or more of the following combinations:

[0346] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails;

[0347] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0348] Optionally, the connection recovery failure cause includes one or more of the following combinations:

[0349] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails;

[0350] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0351] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0352] Connection failure type, and the connection failure type includes one or more of the following combinations: remote terminal radio link failure (RLF), remote terminal handover failure (HOF);

[0353] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0354] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0355] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0356] The T400 timer is greater than the timer threshold and has not timed out;

[0357] The transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold and less than the first transmission count;

[0358] The consecutive HARQ discontinuous transmission count of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission count.

[0359] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0360] The identification information of the source cell of the last handover;

[0361] When it was a PC5 connection before handover, the identification information of the serving cell of the remote terminal before the last handover;

[0362] The identification information of the serving cell of the remote terminal where RLF was detected;

[0363] The identification information of the serving cell of the remote terminal where HOF was detected;

[0364] The identification information of the serving cell of the remote terminal that returns to the connection after connection failure;

[0365] The identification information of the serving cell of the remote terminal that returns to the connection after reconstruction failure.

[0366] Optionally, the identification information includes one or more of the following combinations:

[0367] Cell Radio Network Temporary Identity C-RNTI;

[0368] Layer 2 identification.

[0369] It should also be known that in the embodiments of the present application, the remote terminal establishes communication with the network-side device through a relay terminal, and both the remote terminal and the relay terminal can obtain and send their respective first related information generated during the communication process.

[0370] Here, taking the remote terminal (such as the first terminal or the remote terminal) obtaining the first related information as an example for illustration.

[0371] During the above communication process, the relay terminal device information obtained by the first terminal is the identification information of the relay terminal, and / or the corresponding relationship between the identification information and a specified event.

[0372] Among them, various situations may occur during the process of the remote terminal establishing communication with the relay terminal. Here, these situations are referred to as events. For different events, in order to indicate the object to which the event occurs, it is necessary to establish a correspondence between the identifier of the object (here the object mainly refers to the relay terminal) and the specified event. And the events here can include, but are not limited to: connection establishment; detecting radio link failure (RLF); detecting handover failure (HOF); handover; returning to the connection after connection failure or reconstruction failure; re-establishing after connection failure; attempting to establish a PC5 connection after RLF of the remote terminal, where RLF includes PC5 RLF or Uu RLF; attempting to establish a PC5 connection after HOF of the remote terminal, including one or more of the above; and so on.

[0373] For example: When the remote terminal establishes a connection with the relay terminal, this connection establishment can be an established one or a to-be-established one. Then, for the event of connection establishment, the recorded content is: the correspondence between connection establishment and the identifier information of the relay terminal, that is, the identifier information of the relay terminal for which the connection is established; Another example: For the remote terminal detecting RLF, where RLF includes PC5 RLF and Uu RLF. If it is PC5 RLF, the remote terminal needs to determine the peer of this PC5 link, that is, which relay terminal it is. The recorded content is the correspondence between PC5 RLF and the identifier information of the relay terminal, that is, through this correspondence, it can be determined that the remote terminal has RLF on the PC5 link established with the relay terminal corresponding to this identifier information; and so on.

[0374] Alternatively, when a specified event occurs to the remote terminal, it can record the relay terminal when the specified event occurs. For example: the relay terminal during the connection establishment process, such as the relay terminal that has established a PC5 connection with the first terminal or the relay terminal that is to establish a PC5 connection with the first terminal; the relay terminal detecting RLF, including PC5 RLF and Uu RLF; the relay terminal detecting HOF during the PC5 handover process or the process of directly connecting to a PC5 connection; the source relay terminal, that is, the source relay terminal for handover or connection recovery, such as the relay terminal before the first terminal switches to a different relay terminal; the destination relay terminal, that is, the destination relay terminal for handover or connection recovery, such as the relay terminal as the handover target when the first terminal switches to a different relay terminal; the relay terminal that returns to the connection after connection failure or reconstruction failure; the relay terminal that re-establishes after connection failure; the relay terminal that attempts to establish a PC5 connection after RLF of the remote terminal; the relay terminal that attempts to establish a PC5 connection after HOF of the remote terminal.

[0375] For any one or more of the identifier information of the relay terminals obtained by the above first terminal, it is the C-RNTI or L2 ID corresponding to that relay terminal.

[0376] Optionally, in addition to recording the relay terminal device information, the remote terminal may also record its own device information. The remote terminal device information includes one or more of the following combinations:

[0377] The identification information of the remote terminal;

[0378] The location information of the remote terminal.

[0379] Among them, the identification information of the remote terminal, that is, the identification information of the first terminal, includes at least one of C-RNTI and layer 2 identification. For example, it can be the C-RNTI or L2 ID of the first terminal; the location information of the remote terminal, that is, the location information of the first terminal.

[0380] Optionally, in this embodiment, the time information obtained by the first terminal includes one or more of the following combinations:

[0381] The duration from establishing the PC5 connection to the occurrence of the communication process;

[0382] The duration from the handover-related moment to the radio link failure (RLF);

[0383] The duration experienced after detecting the RLF;

[0384] The duration from RLF to establishing the PC5 connection;

[0385] The duration experienced after detecting the handover failure (HOF);

[0386] The duration from HOF to establishing the PC5 connection;

[0387] The duration from establishing the PC5 connection to entering the radio resource control (RRC) connection state;

[0388] The duration from RLF to entering the RRC connection state;

[0389] The duration from HOF to entering the RRC connection state;

[0390] Among them, RLF includes PC5 RLF or Uu RLF.

[0391] Here, establishing the PC5 connection can be the last PC5 connection. For example, the time information includes the duration from establishing the PC5 connection to the occurrence of the communication process. If the communication process is a handover process, this duration can specifically be the duration from the start time of the last PC5 connection establishment before the first terminal performs the handover to the start time of the handover (such as the moment of receiving the handover configuration or the moment of handover execution, and the handover includes the handover from direct connection to PC5 connection, the handover from PC5 connection to direct connection, and the handover from PC5 connection to PC5 connection), or the duration from the end time of the last PC5 connection establishment before the remote terminal performs the handover to the end time of the handover, etc.

[0392] For the remote terminal in this embodiment, RLF includes PC5 RLF or Uu RLF, and the time information includes the duration from RLF to entering the RRC connected state, that is, the duration from detecting the RLF of the remote terminal (including the remote terminal autonomously detecting PC5 RLF or the relay terminal detecting Uu RLF) to the remote terminal entering the RRC connected state. The specific implementations of other durations are not listed one by one here.

[0393] In this embodiment, "detecting" can also be understood as "occurring".

[0394] It should be noted that the handover-related moment can be the last handover initialization moment, or it can also be the last handover execution moment. The duration experienced after detecting RLF can be the duration from the moment of detecting RLF (the remote terminal detects PC5 RLF or the relay terminal detects Uu RLF) to the moment when the first event occurs. The first event can be that the first terminal reports time-related information to the network-side device, or it can be the arrival of the recording cut-off time of the configured time-related information, etc. Similarly, the duration experienced after detecting HOF is also the duration from the moment of detecting HOF to the moment when the second event occurs. The second event can be the same as the first event or other set events.

[0395] Optionally, in this embodiment, the measurement information obtained by the first terminal includes one or more of the following combinations:

[0396] The PC5 measurement result of the remote terminal;

[0397] PC5 between the remote terminal and the relay terminal that establishes a PC5 connection with the remote terminal

[0398] The Uu link measurement result of the remote terminal.

[0399] Here, the Uu link measurement result includes one or more of the following combinations: reference signal received power (RSRP); reference signal received quality (RSRQ); received signal strength indication (RSSI); signal-to-interference plus noise ratio (SINR). The PC5 measurement result includes one or more of the following combinations: sidelink reference signal measurement result; sidelink discovery signal measurement result.

[0400] It should also be noted that the PC5 measurement results obtained by the first terminal include the PC5 measurement results between the first terminal and one or more terminals that can serve as its relay terminals (candidate relay terminals). Of course, the PC5 measurement results of the remote terminal include the PC5 measurement results between the first terminal and the relay terminal with which it has a PC5 connection. However, considering the requirements of mobile robustness optimization, the reported measurement information can be the measurement results of the PC5 connection between the remote terminal and the relay terminal with which it has established a PC5 connection.

[0401] Optionally, in this embodiment, the cause information obtained by the first terminal includes one or more of the following combinations:

[0402] The reason for connection establishment failure, where the connection establishment includes the relay terminal assisting the remote terminal to establish a connection;

[0403] The reason for connection recovery failure;

[0404] The reason for radio link failure, where the radio link includes a PC5 link or a Uu link.

[0405] Among them, from the connection establishment process of the first terminal in the above multi-hop network scenario, the reason for connection failure obtained by the first terminal will indicate the specific reason for failure.

[0406] From the radio link failure process of the first terminal in the above multi-hop network scenario, it can be known that the radio link failure may be due to the PC5 radio link failure or the Uu radio link failure. Therefore, optionally, the reason for radio link failure includes one or more of the following combinations:

[0407] PC5 radio link failure;

[0408] Uu radio link failure.

[0409] Among them, the reason for Uu radio link failure is the same as the reason for radio link failure between the single-hop network terminal and the network-side device, which will not be elaborated here.

[0410] Optionally, if the radio link is a PC5 link, the reason for radio link failure includes one or more of the following combinations:

[0411] T400 timer timeout;

[0412] The transmission times of the sidelink radio link control (RLC) entity are greater than or equal to the first transmission times;

[0413] The continuous hybrid automatic repeat request (HARQ) discontinuous transmission times of the media access control (MAC) entity are greater than or equal to the second transmission times;

[0414] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0415] That is to say, when the first terminal reports the reason for the radio link failure, it can report only whether it is caused by PC5 RLF or Uu RLF, or it can further report or only report the reason for PC5 RLF when the radio link failure is caused by PC5 RLF, such as the timeout of the T400 timer.

[0416] Among them, the T400 timer is a configured PC5 timer. If the T400 timer times out, then PC5 RLF. The first transmission count is the maximum number of transmissions configured for the transmission of the sidelink RLC entity. If the number of transmissions of the sidelink RLC entity is greater than or equal to this maximum number of transmissions, then PC5 RLF. The second transmission count is the maximum number of consecutive HARQ DTXs configured for the MAC entity. If the number of consecutive HARQ DTXs of the MAC entity is greater than or equal to this maximum number of transmissions, then PC5 RLF. The sidelink signaling radio bearer associated with the sidelink PDCP entity can be SL-SRB2 or SL-SRB3. If the integrity check of the sidelink PDCP entity associated with SL-SRB2 or SL-SRB3 fails, then PC5 RLF.

[0417] Among them, as known from the above content, for the connection establishment process of the first terminal in a multi-hop network scenario, there are two scenarios. One is that there is no RRC connection established between the relay terminal and the network, and the other is that there is an RRC connection established between the relay terminal and the network. Therefore, optionally, the connection establishment failure reason obtained by the first terminal includes one or more of the following combinations:

[0418] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails;

[0419] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0420] That is to say, for the scenario where an RRC connection has been established between the relay terminal and the network, the relay terminal has established a Uu connection with the network-side device, and the relay terminal can directly forward the RRC connection establishment request of the remote terminal to assist the remote terminal in establishing an RRC connection. Thus, if the connection establishment fails, the reason for the connection establishment failure is that the relay terminal is in the connected state and the remote terminal connection establishment fails; for the scenario where no RRC connection has been established between the relay terminal and the network, the relay terminal has not yet established a Uu connection with the network-side device. After receiving the RRC connection establishment request from the remote terminal, the relay terminal first establishes an RRC connection between the relay terminal and the network, and then forwards the connection establishment request of the remote terminal to the network side after establishing the connection. Thus, if the connection establishment fails between the relay terminal and the network side, the reason for the connection establishment failure is that the relay terminal is in the idle state or the inactive state, and the relay terminal connection establishment failure causes the remote terminal connection establishment failure.

[0421] Moreover, as known from the above content, for the connection recovery process of the first terminal in the multi-hop network scenario, it is similar to the connection establishment process, including two scenarios. One is that no RRC connection has been established between the relay terminal and the network, and the other is that an RRC connection has been established between the relay terminal and the network. Therefore, optionally, the connection recovery failure reason obtained by the first terminal includes one or more of the following combinations:

[0422] The relay terminal is in the connected state and the remote terminal connection recovery fails;

[0423] The relay terminal is in the idle state or the inactive state, the relay terminal connection recovery fails, and the remote terminal connection establishment fails.

[0424] That is to say, for the scenario where an RRC connection has been established between the relay terminal and the network, if the connection recovery fails, the reason for the connection recovery failure is that the relay terminal is in the connected state and the remote terminal connection establishment fails; for the scenario where no RRC connection has been established between the relay terminal and the network, if the connection recovery fails, the reason for the connection recovery failure is that the relay terminal is in the idle state or the inactive state, and the relay terminal connection establishment failure causes the remote terminal connection establishment failure.

[0425] Optionally, in this embodiment, the type information corresponding to the communication process obtained by the first terminal includes one or more of the following combinations:

[0426] Connection failure type, and the connection failure type includes one or more of the following combinations: remote terminal RLF, remote terminal HOF;

[0427] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0428] Handover failure type, where the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0429] In this way, the first terminal reports the connection failure type to indicate whether the reason for the connection failure of the first terminal in the connected state is RLF of the remote terminal or HOF of the remote terminal; the first terminal can also indicate the handover failure reason by reporting the handover failure type; the first terminal reports the handover type to indicate the specific handover implemented by the first terminal during the handover process in the multi-hop network scenario.

[0430] In addition, a Successful Handover Report (SHR) is a report used to inform the network-side device that although the handover is successful, there are critical issues during the handover process. In this embodiment, considering the multi-hop network scenario, optionally, the triggering conditions for the successful handover report obtained by the first terminal include one or more of the following combinations:

[0431] The T400 timer is greater than the timer threshold and has not timed out;

[0432] The transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold and less than the first transmission count;

[0433] The consecutive HARQ discontinuous transmission count of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission count.

[0434] Here, a timer threshold is configured for the T400 timer, a first transmission threshold is configured for the transmission of the sidelink RLC entity, and a second transmission threshold is configured for the consecutive HARQ DTX of the MAC entity. The first transmission count is the maximum transmission count configured for the transmission of the sidelink RLC entity; the second transmission count is the maximum transmission count configured for the consecutive HARQ DTX of the MAC entity.

[0435] If the T400 timer is greater than the timer threshold and has not timed out, then the SHR is triggered. If the transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold but less than the first transmission count, then the SHR is triggered. If the consecutive HARQ DTX count of the MAC entity is greater than or equal to the second transmission threshold but less than the second transmission count, then the SHR is triggered.

[0436] Optionally, in this embodiment, the identification information of the serving cell obtained by the first terminal includes one or more of the following combinations:

[0437] The identification information of the source cell of the last handover;

[0438] When the connection before the handover is a PC5 connection, the identification information of the serving cell of the remote terminal before the last handover;

[0439] The identification information of the serving cell of the remote terminal where RLF is detected;

[0440] The identification information of the serving cell of the remote terminal where HOF is detected;

[0441] The identification information of the serving cell of the remote terminal that returns the connection after connection failure;

[0442] The identification information of the serving cell of the remote terminal that returns the connection after reconstruction failure.

[0443] Here, the first terminal obtains the identification information of its serving cell for different communication processes.

[0444] In this embodiment, the last handover is the last handover before the moment when the first terminal sends the first relevant information to the network-side device. Thus, if the identification information of the serving cell reported by the first terminal includes the identification information of the source cell of the last handover, this identification information can be the identification information of the serving cell of the first terminal before the last handover. At this time, the last handover can be a handover from the first terminal directly connected to a PC5 connection, a handover from a PC5 connection to a direct connection, or a handover from a PC5 connection to a PC5 connection. If the identification information of the serving cell reported by the first terminal includes the identification information of the serving cell of the remote terminal when the connection before the handover is a PC5 connection and before the last handover, this identification information can be the identification information of the serving cell of the first terminal before the last handover when the last handover before time A (the time when the first terminal sends relevant information to the network-side device) is a handover from a PC5 connection to a direct connection, or a handover from a PC5 connection to a PC5 connection. If the identification information of the serving cell reported by the first terminal includes the identification information of the serving cell of the remote terminal where RLF is detected, this identification information can be the identification of the serving cell of the first terminal when the first terminal autonomously detects RLF or the relay terminal detects RLF. If the identification information of the serving cell reported by the first terminal includes the identification information of the serving cell of the remote terminal where HOF is detected, this identification information can be the identification of the serving cell when the first terminal detects HOF. If the identification information of the serving cell reported by the first terminal includes the identification information of the serving cell of the remote terminal that returns the connection after connection failure, this identification information can be the identification information of the serving cell of the first terminal when the first terminal fails to connect to a new relay terminal and then returns to connect to the old relay terminal. If the identification information of the serving cell reported by the first terminal includes the identification information of the serving cell of the remote terminal that returns the connection after reconstruction failure, this identification information can be the identification information of the serving cell of the first terminal when it returns to connect to the relay terminal after reconstruction failure.

[0445] Optionally, in this embodiment, the first terminal executes step 201, that is, after entering the connected state, the first terminal first reports, in a first dedicated signaling, an indication information that the first terminal has first related information; the network-side device can, according to the indication information, request the first terminal to report the first related information in a second dedicated signaling; and the first terminal reports the recorded first related information in a third dedicated signaling according to the request of the network-side device.

[0446] Wherein, the first dedicated signaling may be RRC Setup Complete or RRC ReconfigurationComplete or RRC Reestablishment Complete or RRC Resume Complete. The second dedicated signaling may be RRC Reconfiguration or UE Information Request. The third dedicated signaling may be UEInformation Response.

[0447] On the other hand, taking the relay terminal (such as the second terminal or the relay terminal) obtaining the first related information as an example for description:

[0448] Different from the first terminal, in this embodiment, the relay terminal connection establishment process in a multi-hop network scenario includes two scenarios. One scenario is that the relay terminal has data to be transmitted, and then it autonomously establishes an RRC connection with the network-side device; the other scenario is that after the relay terminal receives an RRC connection establishment request from a remote terminal or an RRC connection establishment request of a remote terminal forwarded by another relay terminal, it first establishes an RRC connection between the relay terminal and the network-side device, and after establishing the connection, forwards the connection establishment request of the remote terminal to the network side.

[0449] For the relay terminal, in this embodiment, the connection recovery process in a multi-hop network scenario is similar to the relay terminal connection establishment process, and will not be elaborated here.

[0450] For the relay terminal, in this embodiment, the radio link failure process in a multi-hop network scenario includes two cases. The first case is that the relay terminal detects a PC5 RLF, and the second case is that the relay terminal detects a Uu RLF. For the first case, the communication between the relay terminal that detects the PC5 RLF and the network-side device still needs to pass through one or more relay terminals, and the relay terminal detects the PC5 connection between it and another relay terminal and detects the PC5 RLF. For the second case, the relay terminal that detects the Uu RLF is directly connected to the network-side device, and the relay terminal that detects the Uu RLF will send Uu RLF indication information to the remote terminal to notify the remote terminal that the Uu link is abnormal.

[0451] For a relay terminal, in this embodiment, the handover process in a multi-hop network scenario includes: handover of the relay terminal between different cells, and handover of the relay terminal between different network-side devices; it also includes: handover of the connection between the relay terminal and the network-side device from direct connection to PC5 connection, handover from PC5 connection to direct connection, and handover from PC5 connection to PC5 connection (i.e., reselecting the relay terminal). At this time, the communication between the relay terminal and the network-side device also needs to pass through one or more relay terminals.

[0452] Optionally, the relay terminal device information obtained by the second terminal includes one or more of the following combinations:

[0453] Identification information of the relay terminal;

[0454] Location information of the relay terminal.

[0455] Among them, the identification information of the relay terminal can be the identification information of the second terminal or the identification information of other relay terminals that establish a PC5 connection with the second terminal; the location information of the relay terminal is the location information of the second terminal.

[0456] Optionally, the remote terminal device information obtained by the second terminal includes one or more of the following combinations:

[0457] Identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0458] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0459] Here, considering that the second terminal can establish a PC5 connection with one or more terminals, the identification information of the remote terminal that establishes a PC5 connection with the relay terminal refers to the remote terminal that establishes a PC5 connection with this second terminal. The number of remote terminals that establish a PC5 connection with the relay terminal refers to the number of remote terminals that establish a PC5 connection with this second terminal.

[0460] For the identification information of the remote terminal that has a PC5 connection with this second terminal, it is the C-RNTI or L2 ID corresponding to this remote terminal. Of course, the identification information of the relay terminal also includes at least one of C-RNTI and layer 2 identification, such as the C-RNTI or L2 ID corresponding to the relay terminal.

[0461] Optionally, the time information obtained by the second terminal. The time information here is similar to the type of time information obtained by the remote terminal.

[0462] For example, establish the duration of the PC5 connection during the communication process. If the communication process is a handover process, the duration can specifically be the duration from the start time of the last PC5 connection establishment before the second terminal performs the handover to the start time of the handover (such as the time when the handover configuration is received or the time when the handover is executed. The handover can be a handover from the direct connection between the second terminal and the network device to the PC5 connection, a handover from the PC5 connection to the direct connection, a handover from the PC5 connection to the PC5 connection, or a handover between different cells of the second terminal, or a handover between different network devices of the second terminal), or the duration from the end time of the last PC5 connection establishment before the second terminal performs the handover to the end time of the handover, etc.

[0463] In this embodiment, for the relay terminal, RLF includes PC5 RLF or Uu RLF, and the time information includes the duration from RLF to entering the RRC connected state, which can be the duration from the occurrence (or detection) of Uu RLF of the relay terminal to its entry into the RRC connected state, or the duration from the occurrence (or detection) of PC5 RLF of the relay terminal to its entry into the RRC connected state, which will not be listed one by one here.

[0464] It should be noted that the handover-related moments are similar to the implementation of the first terminal, which is the last handover initialization moment or the last handover execution moment. The duration experienced after detecting RLF is the duration from the moment when the relay terminal detects RLF to the moment when the first event occurs. The first event can be that the second terminal reports time-related information to the network device, or the expiration of the recording deadline of the configured time-related information, etc. Similarly, the duration experienced after detecting HOF is also the duration from the moment when HOF is detected to the moment when the second event occurs. The second event can be the same as the first event or other set events.

[0465] Optionally, the measurement information obtained by the second terminal includes one or more of the following combinations:

[0466] The PC5 measurement result of the relay terminal;

[0467] The PC5 measurement result between the relay terminal and the remote terminal that establishes a PC5 connection with the relay terminal;

[0468] The Uu link measurement result of the relay terminal.

[0469] The PC5 measurement results obtained by the second terminal are the PC5 measurement results between the second terminal and one or more terminals that can serve as its remote terminals (candidate terminals). Of course, the PC5 measurement results of the relay terminal include the PC5 measurement results between the second terminal and the remote terminal with which it has a PC5 connection. However, considering the requirements of mobile robustness optimization, the reported measurement-related information can be only the measurement results of the PC5 connection between the relay terminal and the remote terminal with which it has a PC5 connection. The Uu link measurement results of the relay terminal, similar to those of the remote terminal, include one or more of RSRP, RSRQ, RSSI, and SINR. The PC5 measurement results include sidelink reference signal measurement results and / or sidelink discovery signal measurement results.

[0470] Optionally, the cause information includes one or more of the following combinations:

[0471] Connection establishment cause, where the connection establishment cause is to establish a connection for the remote terminal;

[0472] Wireless link failure cause, where the wireless link includes the PC5 link or the Uu link.

[0473] Here, the second terminal can report the connection establishment cause, indicating that the Uu connection between the second terminal and the network-side device is established for the remote terminal, that is, the connection establishment by the relay terminal during the connection establishment process is triggered by the remote terminal.

[0474] In addition, from the above wireless link failure process in the multi-hop network scenario of the second terminal, it can be known that the wireless link failure may be due to the PC5 wireless link failure or the Uu wireless link failure. Therefore, optionally, the wireless link failure cause obtained by the second terminal includes one or more of the following combinations:

[0475] PC5 wireless link failure;

[0476] Uu wireless link failure.

[0477] That is to say, the wireless link failure in the multi-hop network scenario is caused by PC5 RLF or Uu RLF.

[0478] Among them, the cause of Uu wireless link failure is the same as that of the wireless link failure between the single-hop network terminal and the network-side device, which will not be elaborated here. For PC5 RLF, optionally, if the wireless link is the PC5 link, the wireless link failure cause obtained by the second terminal can also include one or more of the following combinations as the first terminal:

[0479] T400 timer timeout;

[0480] The transmission count of the sidelink RLC entity is greater than or equal to the first transmission count;

[0481] The number of consecutive HARQ discontinuous transmissions of the MAC entity is greater than or equal to the second transmission count;

[0482] The integrity check of the sidelink signaling radio bearer associated with the sidelink PDCP entity fails.

[0483] Wherein, the T400 timer is a configured PC5 RLF timer. If the T400 timer expires, then PC5 RLF. The first transmission count is the maximum transmission count of the transmission of the configured sidelink RLC entity. If the transmission count of the sidelink RLC entity is greater than or equal to the maximum transmission count, then PC5 RLF. The second transmission count is the maximum transmission count of the consecutive HARQ DTX of the configured MAC entity. If the number of consecutive HARQ DTX of the MAC entity is greater than or equal to the maximum transmission count, then PC5 RLF. The sidelink signaling radio bearer associated with the sidelink PDCP entity can be SL-SRB2 or SL-SRB3. If the integrity check of the sidelink PDCP entity associated with SL-SRB2 or SL-SRB3 fails, then PC5 RLF.

[0484] Optionally, in this embodiment, the type information corresponding to the communication process obtained by the second terminal includes one or more of the following combinations:

[0485] Connection failure type, and the connection failure type includes one or more of the following combinations: relay terminal RLF, relay terminal HOF;

[0486] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0487] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0488] In this way, the second terminal reports the connection failure type to indicate whether the reason for the connection failure of the second terminal in the connected state is relay terminal RLF or relay terminal HOF; the second terminal can also indicate the handover failure reason by reporting the handover failure type; the second terminal reports the handover type to indicate the specific handover achieved in the handover process in the multi-hop network scenario.

[0489] It should be understood that the second terminal can be directly connected to the network-side device, so the reported handover types can also include cell handover and / or network-side device handover; similarly, the handover failure types can also include cell handover failure and / or network-side device handover failure.

[0490] In addition, the triggering conditions for the second terminal to obtain the reported successful handover report are the same as those for the first terminal, and can also include one or more of the following combinations:

[0491] The T400 timer is greater than the timer threshold and has not timed out;

[0492] The transmission times of the sidelink RLC entity are greater than or equal to the first transmission threshold and less than the first number of transmissions;

[0493] The consecutive HARQ discontinuous transmission times of the MAC entity are greater than or equal to the second transmission threshold and less than the second number of transmissions.

[0494] Optionally, for the second terminal, the identification information of the serving cell of the relay terminal is obtained, so the identification information of the serving cell includes one or more of the following combinations:

[0495] The identification information of the source cell of the last handover;

[0496] When it was a PC5 connection before handover, the identification information of the serving cell of the relay terminal before the last handover;

[0497] The identification information of the serving cell of the relay terminal where RLF is detected;

[0498] The identification information of the serving cell of the relay terminal where HOF is detected;

[0499] The identification information of the serving cell of the relay terminal that returns to the connection after connection failure;

[0500] The identification information of the serving cell of the relay terminal that returns to the connection after reconstruction failure.

[0501] Here, the second terminal will obtain the identification information of its serving cell for different communication processes.

[0502] In this embodiment, the last handover is the last handover before the moment when the second terminal sends relevant information to the network device. Thus, if the identification information of the serving cell reported by the second terminal includes the identification information of the source cell of the last handover, the identification information may be the identification information of the serving cell of the second terminal before the last handover. At this time, the last handover may be the handover of the second terminal and the network device from a direct connection to a PC5 connection, the handover from a PC5 connection to a direct connection, the handover from a PC5 connection to a PC5 connection, or the cell handover of the second terminal or the handover of the network device. If the identification information of the serving cell reported by the second terminal includes the identification information of the serving cell of the relay terminal before the last handover when it is a PC5 connection before the handover, the identification information may be the identification information of the serving cell of the relay terminal when the last handover before time B (the moment when the second terminal sends relevant information to the network device) is the handover from a PC5 connection to a direct connection, or the handover from a PC5 connection to a PC5 connection. If the identification information of the serving cell reported by the second terminal includes the identification information of the serving cell of the relay terminal when RLF is detected, the identification information may be the identification of the serving cell of the second terminal when the second terminal detects RLF. If the identification information of the serving cell reported by the second terminal includes the identification information of the serving cell of the relay terminal when HOF is detected, the identification information may be the identification of the serving cell when the second terminal detects HOF. If the identification information of the serving cell reported by the second terminal includes the identification information of the serving cell of the relay terminal that returns to the connection after a connection failure, the identification information may be the identification information of the serving cell of the second terminal when the second terminal returns to connect to the old relay terminal after the connection failure with the new relay terminal. If the identification information of the serving cell reported by the second terminal includes the identification information of the serving cell of the relay terminal that returns to the connection after a reconstruction failure, the identification information may be the identification information of the serving cell of the second terminal when the second terminal returns to connect to the old network device after the connection reconstruction failure with the new network device.

[0503] Optionally, in this embodiment, the second terminal executes step 201, that is, after entering the connected state, the second terminal first reports the indication information of the second relevant information of the second terminal in the first dedicated signaling; the network device can request the second terminal to report the second relevant information in the second dedicated signaling according to the indication information; the second terminal reports the second relevant information in the third dedicated signaling according to the request of the network device.

[0504] Among them, the first dedicated signaling may be RRC Setup Complete, RRC Reconfiguration Complete, RRC Reestablishment Complete, or RRC Resume Complete. The second dedicated signaling may be RRC Reconfiguration or UE Information Request. The third dedicated signaling may be UE Information Response.

[0505] The following describes the application of the method of the above embodiments of the present invention in combination with specific scenarios:

[0506] Scenario 1: Connection establishment fails

[0507] As Figure 3 shown, the remote terminal (UE) establishes a PC5 connection with the relay UE through the discovery process and the PC5 connection establishment process. The remote UE in the RRC_IDLE state triggers the connection establishment process, and the remote UE starts T300. Among them, the relay UE is in the connected state (RRC_CONNETED state), and forwards the RRC establishment request message of the remote UE to the network-side device. T300 times out, and the remote terminal does not receive the connection establishment message from the network side, and the connection establishment of the remote terminal fails. Therefore, it can be understood that the reason for the failure of the remote terminal to establish a connection in this scenario is that the relay terminal is in the connected state and the connection establishment of the remote terminal fails.

[0508] In this way, the information recorded by the remote terminal when detecting the failure of connection establishment includes, in addition to the information included in the existing Connection Establishment failure (CEF) report, the following information:

[0509] Relay terminal-related information: The identification information (L2-ID or C-RNTI) of the relay terminal for connection establishment;

[0510] Remote terminal-related information: The location information of the remote terminal, the identification information (L2-ID or C-RNTI) of the remote terminal;

[0511] Identification information of the serving cell: The identification information of the serving cell for connection establishment;

[0512] Time-related information: The duration from connecting to the relay UE to the failure of connection establishment;

[0513] Measurement-related information: PC5 measurement results (such as SL-RSRP or SD-RSRP) between the relay terminal with a PC5 connection, PC5 measurement results when connection establishment fails, and Uu link measurement results when connection establishment fails;

[0514] Cause-related information: The reason for the connection establishment failure is that the relay UE is in the connected state and the connection establishment of the remote terminal fails.

[0515] After that, after the remote UE enters the RRC connected state, it reports the recorded information to the network device.

[0516] Since the relay UE is in the connected state and there is no connection establishment failure, no recording or reporting is performed.

[0517] Scenario 2: Connection establishment failure

[0518] As Figure 4 shown, the remote UE establishes a PC5 connection with the relay UE through the discovery process and the PC5 connection establishment process. The remote UE in the RRC_IDLE state triggers the connection establishment process, and the remote UE starts T300. Among them, the relay UE is in the non-connected state (RRC_IDLE state or RRC_INACTIVE state). For the received RRC establishment request message of the remote terminal, it will first establish an RRC connection (i.e., Uu connection) between the relay UE and the network device. Here, due to the failure of the connection establishment between the relay UE and the network device, after T300 times out, the remote terminal does not receive the connection establishment message from the network side, and the connection establishment of the remote terminal fails. Therefore, it can be understood that the reason for the connection establishment failure of the remote terminal in this scenario is that the relay terminal is in the idle state or the inactive state, and the connection establishment of the relay terminal fails.

[0519] In this way, the information recorded by the remote terminal when detecting the connection establishment failure includes, in addition to the information included in the existing CEF report, the following information:

[0520] Relay terminal-related information: The identification information (L2-ID or C-RNTI) of the relay UE for connection establishment;

[0521] Remote terminal-related information: The location information of the remote UE, the identification information (L2-ID or C-RNTI) of the remote UE;

[0522] Identification information of the serving cell: The identification information of the serving cell for connection establishment;

[0523] Time-related information: The duration from connecting to the relay UE to the connection establishment failure;

[0524] Measurement-related information: The PC5 measurement results (such as SL-RSRP or SD-RSRP) between the relay UE with a PC5 connection, the PC5 measurement results when the connection establishment fails, and the Uu link measurement results when the connection establishment fails;

[0525] Cause-related information: The reason for the connection establishment failure is that the relay UE is in the idle state or inactive state, the connection establishment of the relay UE fails, and the connection establishment of the remote UE fails.

[0526] Among them, since the relay UE fails to establish its connection with the network device when establishing its connection with the network device based on the RRC establishment request message of the remote UE, in addition to recording the information included in the existing connection failure report, the relay UE will record the following information:

[0527] Relay terminal-related information: The identification information (L2-ID or C-RNTI) of the relay UE, the location information of the relay UE;

[0528] Remote terminal-related information: The identification information of the remote UE with a PC5 connection, including the identification information of the remote UE that helps establish the RRC connection; at the same time, if this relay terminal is connected to two or more remote terminals through PC5 at the same time, the identification information of other remote terminals will be reported, and the number of remote terminals with a PC5 connection will be reported.

[0529] Measurement-related information: The PC5 measurement results between the relay UE and the remote UE with a PC5 connection, the Uu link measurement results and PC5 measurement results when the connection establishment fails.

[0530] Cause-related information: The reason for the connection establishment is to establish a connection for the remote UE.

[0531] Subsequently, after the relay UE or the remote UE enters the RRC connected state, the information recorded by each is reported to the network device.

[0532] Scenario 3: Radio Link Failure

[0533] As Figure 5 shown, after the remote UE is in the RRC connected state (i.e., the RRC connection between the remote UE and the network device is securely established), it receives the Uu RLF indication information of the relay UE (generated by the Uu RLF detected by the relay UE), which triggers the radio link failure between the remote UE and the network device. After the relay UE triggers the RLF, it will trigger the RRC re-establishment process to restore the RRC connection. After the remote UE triggers the RLF, it will trigger the RRC re-establishment process or the relay UE reselection process, depending on the implementation of the remote UE. At this time, the remote UE records the radio link failure report. Since the relay UE itself has a radio link failure, it will also record the radio link failure report. In addition to the content recorded after the existing RLF, the remote terminal and the relay terminal also record the following content.

[0534] The records of the remote UE also include the following information:

[0535] Relay terminal related information: Identification information of the relay UE that detected Uu RLF; Identification information of the relay UE that returns to the connection after connection failure or reconstruction failure; Identification information of the relay UE that is re-established after connection failure; Identification information of the relay UE that attempts to establish a PC5 connection after the remote UE RLF (such as the identification information of the relay UE that has a PC5 connection with the remote UE before the remote UE enters the connected state, and / or the identification information of the relay UE that fails to successfully establish a PC5 connection);

[0536] Identification information of the serving cell: Identification information of the serving cell of the remote UE when RLF is detected, Identification information of the serving cell of the remote UE that returns to the connection after connection failure or reconstruction failure;

[0537] Time related information: Duration elapsed after RLF is detected, Duration from detecting remote UE RLF to the remote UE establishing the last PC5 connection, Duration from the remote UE establishing the last PC5 connection to the remote UE entering the RRC connected state, Duration from detecting remote UE RLF to the remote UE entering the RRC connected state;

[0538] Measurement related information: Uu link measurement results when RLF occurs, PC5 measurement results between the relay UE with a PC5 connection when RLF occurs, PC5 measurement results when RLF occurs;

[0539] Type related information: Connection failure type (remote UE RLF);

[0540] Cause related information: Radio link failure cause (Uu RLF, Uu radio link failure cause).

[0541] The relay terminal records the following information:

[0542] Relay terminal related information: Location information of the relay UE, Identification information of the relay UE (L2-ID or C-RNTI);

[0543] Remote terminal related information: Identification information of the remote UE with a PC5 connection, including the identification information of the remote UE that helps establish the RRC connection; At the same time, if this relay terminal connects to 2 or more remote terminals through PC5 at the same time, then report the identification information of other remote terminals, and report the number of remote terminals with a PC5 connection;

[0544] Measurement related information: Uu link measurement results and PC5 measurement results when RLF occurs, PC5 measurement results between the relay UE and the remote UE with a PC5 connection.

[0545] Subsequently, after the relay UE or the remote UE enters the RRC connected state, report the information recorded by each to the network side device.

[0546] Scenario 4: Handover failure of the remote UE

[0547] As Figure 6 shown, the remote UE is in the RRC connected state and reports the PC5 measurement results and RRM measurement results to the network side; the network side device makes a handover decision based on the reported content, decides to hand over the remote UE from the PC5-RRC connection to the Uu connection, and sends a handover command; after receiving the handover command, the remote UE starts timer T304; if the timer T304 of the remote UE expires and the handover process is not completed, the handover fails, and a reconstruction process will be triggered after the handover fails. At this time, the relay UE in this scenario does not experience a handover failure and does not record or report.

[0548] The information recorded by the remote UE when the handover of the remote UE fails includes, in addition to the content that needs to be recorded in the existing HOF, the following information:

[0549] Relay terminal related information: identification information of the relay UE before the last handover when the connection is PC5 before the handover, identification information of the relay UE that has experienced HOF, identification information of the relay UE that returns to the connection after the handover or reconstruction fails;

[0550] Identification information of the serving cell: identification information of the source cell of the last handover, identification information of the serving cell of the remote UE before the last handover when the connection is PC5 before the handover, identification information of the serving cell of the remote UE that has experienced HOF, identification information of the serving cell of the remote UE that returns to the connection after the reconstruction fails;

[0551] Time related information: duration elapsed after detecting the HOF of the remote UE, duration from detecting the HOF of the remote UE to the last time the remote UE established a PC5 connection, duration from the last time the remote UE established a PC5 connection to the remote UE entering the RRC connected state, duration from detecting the HOF of the remote UE to the remote UE entering the RRC connected state

[0552] Measurement related information: Uu link measurement results when HOF occurs, PC5 measurement results between the relay UE with a PC5 connection when HOF occurs, PC5 measurement results when HOF occurs;

[0553] Type related information: connection failure type (remote UE HOF), handover failure type (handover from PC5 connection to direct connection).

[0554] Subsequently, after the remote UE enters the RRC connected state, it reports the recorded information to the network side device.

[0555] Scenario 5: Handover failure of the relay UE

[0556] As Figure 7As shown in the figure, the relay UE is in the RRC connected state, and reports the PC5 measurement results and RRM measurement results to the network side; the network side device makes a handover decision based on the reported content, decides to hand over the relay UE to the target cell, and sends a handover command; the relay UE receives the handover command and starts T304; if the handover process is not completed after T304 times out, the handover fails. At this time, the remote UE does not experience a handover failure and does not record or report it.

[0557] When the relay UE fails to hand over, the recorded information includes, in addition to the content that needs to be recorded for existing handover failures, the following information:

[0558] Relay terminal related information: the location information of the relay terminal; remote terminal related information: the identification information of the remote UE with a PC5 connection, including the identification information of the remote UE that helps establish the RRC connection; at the same time, if this relay terminal is connected to two or more remote terminals through PC5 at the same time, the identification information of other remote terminals is reported, and the number of remote terminals with a PC5 connection is reported.

[0559] Measurement related information: the PC5 measurement results between the relay UE with a PC5 connection, the Uu link measurement results and the PC5 measurement results when the handover fails.

[0560] Subsequently, after the relay UE enters the RRC connected state, it reports the recorded information to the network side device.

[0561] Scenario 6: The remote UE successfully hands over, but a critical problem occurs

[0562] As Figure 8 shown in the figure, the remote UE is in the RRC connected state, and reports the PC5 measurement results and RRM measurement results to the network side; the remote UE sends an RRC Reconfiguration sidelink message through the PC5 connection and starts a timer T400; during the period when the timer T400 is started, a handover command is received, instructing the UE to switch from the PC5 connection to the PC5 connection, and the UE successfully hands over. At this time, the PC5 link between the relay UE and the remote UE is released, and the relay UE does not need to record and report. Since the RRC Reconfiguration sidelink process is terminated by receiving a handover command during the period when T400 is started, it is possible that the terminated RRCReconfiguration sidelink fails, resulting in PC5 RLF. Therefore, the remote UE records the above critical problems in the handover success report. The information recorded by the remote UE includes, in addition to the information in the existing successful handover report, the following information:

[0563] Relay terminal related information: the identification information of the source relay UE for the handover, the identification information of the target relay UE for the handover;

[0564] Measurement-related information: PC5 measurement results between the source relay UE for handover and the target relay UE for handover, PC5 measurement results between the remote terminal and the target relay UE for handover, and PC5 measurement results of the remote terminal;

[0565] Successful handover report triggering condition: The triggering condition is that the T400 timer is greater than the timer threshold and has not timed out.

[0566] It should be noted that the network-side device in the embodiment of the present invention may be, but is not limited to: a base station, a central control unit (CU).

[0567] As Figure 9 shown, an information receiving method in an embodiment of the present invention includes:

[0568] Step 901, a network-side device receives first related information generated during communication sent by a remote terminal and / or a relay terminal; wherein, the remote terminal establishes communication with the network-side device through the relay terminal.

[0569] Step 902, the network-side device performs mobile robustness optimization according to the first related information.

[0570] By receiving the first related information in step 901, the network-side device can perform mobile robustness optimization in a multi-hop network scenario.

[0571] Optionally, the first related information includes one or more combinations of the following:

[0572] Relay terminal information;

[0573] Remote terminal information;

[0574] Identification information of the serving cell;

[0575] Time information;

[0576] Measurement information;

[0577] Cause information;

[0578] Type information corresponding to the communication process;

[0579] Successful handover report triggering condition.

[0580] It should be noted that the method in this embodiment is implemented in cooperation with the above information sending method, and the implementation manner of the above method embodiment is applicable to this embodiment and can achieve the same technical effect.

[0581] As Figure 10As shown in the figure, an embodiment of the present invention further provides a transmission processing device, including: a memory 1020, a transceiver 1010, and a processor 1000;

[0582] The memory 1020 is used to store program instructions; the transceiver 1010 is used to transmit and receive data under the control of the processor 1000; the processor 1000 is used to read the program instructions in the memory 1020, and the transceiver 1010 is used to perform the following operations:

[0583] Obtain first correlation information generated during the communication process, and send the first correlation information to the network-side device;

[0584] Wherein, the communication is a communication established by a remote terminal through a relay terminal with the network-side device; the first correlation information includes one or more combinations of the following:

[0585] Relay terminal information;

[0586] Remote terminal information;

[0587] Identification information of the serving cell;

[0588] Time information;

[0589] Measurement information;

[0590] Cause information;

[0591] Type information corresponding to the communication process;

[0592] Successive handover report triggering condition.

[0593] Optionally, the communication process includes one or more combinations of the following:

[0594] Connection establishment process;

[0595] Connection recovery process;

[0596] Radio link failure process;

[0597] Handover process.

[0598] Optionally, the relay terminal information includes: identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, location information of the relay terminal;

[0599] Wherein, the specified event includes at least one of the following events:

[0600] Connection establishment;

[0601] Detecting radio link failure RLF;

[0602] Handover failure HOF detected;

[0603] Handover;

[0604] Return the connection after connection failure or re - establishment failure;

[0605] Re - establish after connection failure;

[0606] Attempt to establish a PC5 connection after the remote terminal RLF, where RLF includes PC5 RLF or Uu RLF;

[0607] Attempt to establish a PC5 connection after the remote terminal HOF.

[0608] Optionally, the remote terminal information includes one or more combinations of the following:

[0609] The identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal;

[0610] The location information of the remote terminal;

[0611] The number of remote terminals that establish a PC5 connection with the relay terminal.

[0612] Optionally, the time information includes one or more combinations of the following:

[0613] The duration from establishing the PC5 connection to the occurrence of the communication process;

[0614] The duration from the handover - related moment to RLF;

[0615] The duration experienced after detecting RLF;

[0616] The duration from RLF to establishing the PC5 connection;

[0617] The duration experienced after detecting HOF;

[0618] The duration from HOF to establishing the PC5 connection;

[0619] The duration from establishing the PC5 connection to entering the Radio Resource Control RRC connected state;

[0620] The duration from RLF to entering the RRC connected state;

[0621] The duration from HOF to entering the RRC connected state;

[0622] Wherein, RLF includes PC5 RLF or Uu RLF.

[0623] Optionally, the measurement information includes one or more combinations of the following:

[0624] The PC5 measurement result of the remote terminal;

[0625] PC5 measurement results between a remote terminal and a relay terminal that establishes a PC5 connection with the remote terminal;

[0626] Uu link measurement results of the remote terminal;

[0627] PC5 measurement results of the relay terminal;

[0628] PC5 measurement results between a relay terminal and a remote terminal that establishes a PC5 connection with the relay terminal;

[0629] Uu link measurement results of the relay terminal.

[0630] Optionally, the cause information includes one or more of the following combinations:

[0631] Connection establishment failure cause, where the connection establishment includes the relay terminal assisting the remote terminal to establish a connection;

[0632] Connection recovery failure cause;

[0633] Radio link failure cause, where the radio link includes a PC5 link or a Uu link;

[0634] Connection establishment cause, and the connection establishment cause is to establish a connection for the remote terminal.

[0635] Optionally, if the radio link is a PC5 link, the radio link failure cause includes one or more of the following combinations:

[0636] T400 timer timeout;

[0637] The transmission times of the sidelink radio link control (RLC) entity are greater than or equal to the first transmission times;

[0638] The consecutive hybrid automatic repeat request (HARQ) discontinuous transmission times of the media access control (MAC) entity are greater than or equal to the second transmission times;

[0639] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0640] Optionally, the connection establishment failure cause includes one or more of the following combinations:

[0641] The relay terminal is in the connected state and the connection establishment of the remote terminal fails;

[0642] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0643] Optionally, the connection recovery failure reason includes one or more of the following combinations:

[0644] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails;

[0645] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0646] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0647] Connection failure type, and the connection failure type includes one or more of the following combinations: remote terminal RLF, remote terminal HOF;

[0648] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0649] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0650] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0651] The T400 timer is greater than the timer threshold and has not timed out;

[0652] The transmission times of the sidelink RLC entity are greater than or equal to the first transmission threshold and less than the first transmission times;

[0653] The consecutive HARQ discontinuous transmission times of the MAC entity are greater than or equal to the second transmission threshold and less than the second transmission times.

[0654] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0655] The identification information of the source cell of the last handover;

[0656] When the connection before handover is a PC5 connection, the identification information of the serving cell of the remote terminal before the last handover;

[0657] The identification information of the serving cell of the remote terminal where RLF is detected;

[0658] The identification information of the serving cell of the remote terminal where HOF is detected;

[0659] The identification information of the serving cell of the remote terminal that returns to the connection after the connection failure;

[0660] After the reconstruction fails, the identification information of the serving cell of the connected remote terminal is returned.

[0661] Optionally, the identification information includes one or more combinations of the following:

[0662] Cell Radio Network Temporary Identifier C-RNTI;

[0663] Layer 2 identifier.

[0664] Embodiments of the present invention provide a method and apparatus for information transmission. Among them, the method and the apparatus are based on the same application concept. Since the principles for solving problems by the method and the apparatus are similar, the implementation of the apparatus and the method can be referred to each other, and the repeated parts will not be described again.

[0665] Among them, in Figure 10 the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1000 and the memory represented by the memory 1020 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 1010 may be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on the transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, and other transmission mediums. For different user devices, the user interface 1030 may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0666] The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 may store the data used by the processor 1000 when performing operations.

[0667] Optionally, the processor 1000 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). The processor 1000 may also adopt a multi-core architecture.

[0668] The processor 1000 is configured to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions by invoking the program instructions stored in the memory. The processor 1000 and the memory 1020 may also be physically separated.

[0669] For the device according to the embodiment of the present invention, in view of relay communication, by obtaining first relevant information of a target process, where the first relevant information includes at least one of relay terminal relevant information, remote terminal relevant information, identification information of a serving cell, time relevant information, measurement relevant information, cause relevant information, type relevant information, and a successful handover report triggering condition, the first relevant information can be sent to a network-side device, so that the network-side device can perform mobile robustness optimization for a multi-hop network scenario based on the first relevant information.

[0670] It should be noted here that the above device provided by the embodiment of the present invention can implement all the method steps implemented by the method embodiment executed by the first terminal, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiment will not be specifically described in this embodiment.

[0671] As Figure 11 shown, the embodiment of the present invention further provides an information sending device, including:

[0672] A first sending module 1110, configured to

[0673] obtain first relevant information generated during a communication process, and send the first relevant information to a network-side device;

[0674] wherein the communication is a communication established by a remote terminal through a relay terminal with a network-side device; the first relevant information includes one or a combination of the following:

[0675] Relay terminal information;

[0676] Remote terminal information;

[0677] Identification information of a serving cell;

[0678] Time information;

[0679] Measurement information;

[0680] Cause information;

[0681] Type information corresponding to the communication process;

[0682] Successful handover report triggering condition.

[0683] Optionally, the communication process includes one or a combination of the following:

[0684] Connection establishment process;

[0685] Connection recovery process;

[0686] Radio link failure process;

[0687] Handover process.

[0688] Optionally, the relay terminal information includes: identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, location information of the relay terminal;

[0689] Wherein, the specified event includes at least one of the following events:

[0690] Connection establishment;

[0691] Detecting a radio link failure RLF;

[0692] Detecting a handover failure HOF;

[0693] Handover;

[0694] Returning to the connection after connection failure or reconstruction failure;

[0695] Re - establishing after connection failure;

[0696] Attempting to establish a PC5 connection after a remote terminal RLF, where RLF includes PC5 RLF or Uu RLF;

[0697] Attempting to establish a PC5 connection after a remote terminal HOF.

[0698] Optionally, the remote terminal information includes one or a combination of the following:

[0699] Identification information of the remote terminal, including the identification information of the remote terminal establishing a PC5 connection with the relay terminal;

[0700] Location information of the remote terminal;

[0701] The number of remote terminals establishing a PC5 connection with the relay terminal.

[0702] Optionally, the time information includes one or a combination of the following:

[0703] The duration from establishing the PC5 connection to the occurrence of the communication process;

[0704] The duration from the handover - related moment to RLF;

[0705] The duration experienced after detecting RLF;

[0706] The duration from RLF to establishing the PC5 connection;

[0707] The duration experienced after HOF is detected;

[0708] The duration from HOF to the establishment of a PC5 connection;

[0709] The duration from the establishment of a PC5 connection to entering the Radio Resource Control (RRC) connected state;

[0710] The duration from Radio Link Failure (RLF) to entering the RRC connected state;

[0711] The duration from HOF to entering the RRC connected state;

[0712] Wherein, RLF includes PC5 RLF or Uu RLF.

[0713] Optionally, the measurement information includes one or more combinations of the following:

[0714] PC5 measurement results of the remote terminal;

[0715] PC5 measurement results between the remote terminal and the relay terminal that has established a PC5 connection with the remote terminal;

[0716] Uu link measurement results of the remote terminal;

[0717] PC5 measurement results of the relay terminal;

[0718] PC5 measurement results between the relay terminal and the remote terminal that has established a PC5 connection with the relay terminal;

[0719] Uu link measurement results of the relay terminal.

[0720] Optionally, the cause information includes one or more combinations of the following:

[0721] Reasons for connection establishment failure, wherein the connection establishment includes the relay terminal assisting the remote terminal in establishing a connection;

[0722] Reasons for connection recovery failure;

[0723] Reasons for radio link failure, wherein the radio link includes a PC5 link or a Uu link;

[0724] Reasons for connection establishment, and the connection establishment reason is to establish a connection for the remote terminal.

[0725] Optionally, if the radio link is a PC5 link, the reasons for radio link failure include one or more combinations of the following:

[0726] The T400 timer expires;

[0727] The number of transmissions of the sidelink Radio Link Control (RLC) entity is greater than or equal to the first number of transmissions;

[0728] The number of consecutive hybrid automatic repeat request (HARQ) discontinuous transmissions of the media access control (MAC) entity is greater than or equal to a second transmission number.

[0729] The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

[0730] Optionally, the connection establishment failure cause includes one or more of the following combinations:

[0731] The relay terminal is in the connected state, and the connection establishment of the remote terminal fails.

[0732] The relay terminal is in the idle state or the inactive state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

[0733] Optionally, the connection recovery failure cause includes one or more of the following combinations:

[0734] The relay terminal is in the connected state, and the connection recovery of the remote terminal fails.

[0735] The relay terminal is in the idle state or the inactive state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

[0736] Optionally, the type information corresponding to the communication process includes one or more of the following combinations:

[0737] Connection failure type, and the connection failure type includes one or more of the following combinations: remote terminal radio link failure (RLF), remote terminal handover failure (HOF);

[0738] Handover type, and the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection;

[0739] Handover failure type, and the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

[0740] Optionally, the successful handover report triggering condition includes one or more of the following combinations:

[0741] The T400 timer is greater than the timer threshold and has not timed out;

[0742] The number of transmissions of the sidelink radio link control (RLC) entity is greater than or equal to a first transmission threshold and less than a first transmission number;

[0743] The number of consecutive HARQ discontinuous transmissions of the MAC entity is greater than or equal to a second transmission threshold and less than a second transmission number.

[0744] Optionally, the identification information of the serving cell includes one or more of the following combinations:

[0745] The identification information of the source cell of the last handover;

[0746] When the connection before handover is a PC5 connection, the identification information of the serving cell of the remote terminal before the last handover;

[0747] The identification information of the serving cell of the remote terminal where RLF is detected;

[0748] The identification information of the serving cell of the remote terminal where HOF is detected;

[0749] The identification information of the serving cell of the remote terminal that returns the connection after connection failure;

[0750] The identification information of the serving cell of the remote terminal that returns the connection after reconstruction failure.

[0751] Optionally, the identification information includes one or more of the following combinations:

[0752] Cell Radio Network Temporary Identifier C-RNTI;

[0753] Layer 2 identifier.

[0754] In the application scenario where the device according to the embodiment of the present invention establishes communication between a remote terminal and a network-side device through a relay terminal, by obtaining first relevant information generated during the communication, the first relevant information includes at least one of relay terminal information, remote terminal information, identification information of the serving cell, time information, measurement information, cause information, type information corresponding to the communication process, and successful handover report trigger conditions, and sending the first relevant information to the network-side device. Different terminals collect their corresponding information according to the relevant operations they perform during the communication and record the corresponding relationship between this information and the executed operations. In this way, after receiving the first relevant information, the network-side device can identify the multi-hop network characteristics and further optimize the mobility robustness of the multi-hop network based on the first relevant information.

[0755] It should be noted here that the above device provided by the embodiment of the present invention can implement all the method steps implemented by the above information sending method embodiment and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiment are not specifically described in this embodiment again.

[0756] In some embodiments of the present invention, a processor-readable storage medium is further provided. The processor-readable storage medium stores program instructions, and the program instructions are used to cause the processor to execute the transmission processing method executed by the first terminal as described above.

[0757] When the program instruction is executed by the processor, it can implement all the implementation manners in the method embodiments as described above. To avoid repetition, they will not be elaborated here. Figure 2 To avoid repetition, they will not be elaborated here.

[0758] As Figure 12 shown, the present invention further provides a transmission processing apparatus, including: a memory 1220, a transceiver 1210, and a processor 1200; the memory 1220 is configured to store program instructions; the processor 1200 is configured to read the program instructions in the memory 1220; the transceiver 1210 is configured to transmit and receive data under the control of the processor 1200, and perform the following operations:

[0759] Receive first related information generated during a communication process sent by a remote terminal and / or a relay terminal;

[0760] wherein, the remote terminal establishes communication with a network-side device through the relay terminal.

[0761] After receiving the first related information generated during the communication process sent by the remote terminal and / or the relay terminal, it further includes: performing mobility robustness optimization according to the first related information.

[0762] Optionally, the first related information includes one or more combinations of the following:

[0763] Relay terminal information;

[0764] Remote terminal information;

[0765] Identification information of a serving cell;

[0766] Time information;

[0767] Measurement information;

[0768] Cause information;

[0769] Type information corresponding to the communication process;

[0770] Successive handover report triggering condition.

[0771] Wherein, in Figure 12Among them, the bus architecture may include any number of interconnected buses and bridges, specifically, various circuits of one or more processors represented by processor 1200 and memory represented by memory 1220 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and thus will not be further described herein. The bus interface provides an interface. The transceiver 1210 may be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission media include wireless channels, wired channels, optical fiber cables and other transmission media. The processor 1200 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 when executing operations.

[0772] The processor 1200 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0773] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the information receiving method embodiments executed by the network side device, and can achieve the same technical effects, and the same parts and beneficial effects as the method embodiments in this embodiment will not be specifically described herein.

[0774] As Figure 13 shown, the embodiments of the present invention also provide an information receiving device, including:

[0775] A receiving module 1310, configured to receive first relevant information generated during communication sent by a remote terminal and / or a relay terminal;

[0776] Wherein, the remote terminal establishes communication with the network side device through the relay terminal.

[0777] Optionally, the first relevant information includes one or more combinations of the following:

[0778] Relay terminal information;

[0779] Remote terminal information;

[0780] Identification information of the serving cell;

[0781] Time information;

[0782] Measurement information;

[0783] Cause information;

[0784] Type information corresponding to the communication process;

[0785] Success handover report trigger condition.

[0786] The device according to the embodiment of the present invention receives first related information and can perform mobile robustness optimization in a multi-hop network scenario. This device applies the above information receiving method executed by the network-side device, and the implementation manners of the above method embodiments are applicable to this device and can also achieve the same technical effects.

[0787] In some embodiments of the present invention, a processor-readable storage medium is further provided. The processor-readable storage medium stores program instructions, and the program instructions are used to cause the processor to execute the information receiving method executed by the network-side device as described above.

[0788] When the program instructions are executed by the processor, they can implement all the implementation manners in the above method embodiments as shown. To avoid repetition, they are not described herein again. Figure 9 shown in the method embodiments, and to avoid repetition, they are not described herein again.

[0789] It should be noted that the division of units in the embodiments of the present application is illustrative. It is only a logical function division, and there may be other division manners in actual implementation. In addition, in each embodiment of the present application, the functional units can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0790] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or 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 several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: various media 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 disc that can store program codes.

[0791] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described herein again.

[0792] The technical solutions provided by the embodiments of the present application can be applied to a variety of systems, especially 5G systems. For example, the applicable systems can be Global System of Mobile communication (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) systems, Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunication System (UMTS), Worldwide interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems, etc. Both terminal devices and network devices are included in these various systems. The system may also include a core network part, such as an Evolved Packet System (EPS), 5G System (5GS), etc.

[0793] The terminal device involved in the embodiments of the present application can be a device that provides voice and / or data connectivity to users, such as a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device can be called a user equipment (UE). The wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges language and / or data with the radio access network. For example, devices such as personal communication service (PCS) phones, cordless phones, session initiated protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). The wireless terminal device can also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, which is not limited in the embodiments of the present application.

[0794] The network device involved in the embodiments of the present application may be a base station, which may include multiple cells that provide services to terminals. Depending on specific application scenarios, the base station may also be referred to as an access point, or may be a device in the access network that communicates with wireless terminal devices through one or more sectors over the air interface, or other names. The network device can be used to mutually replace the received air frames and Internet Protocol (IP) packets, and act as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the management of the attributes of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or may be a network device (NodeB) in a Wide-band Code Division Multiple Access (WCDMA), or may also be an evolved network device (evolutional Node B, eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), or may also be a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., which are not limited in the embodiments of the present application. In some network architectures, the network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0795] A network device and a terminal device can each use one or more antennas for Multi-Input Multi-Output (MIMO) transmission. The MIMO transmission can be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). According to the form and quantity of the combined antennas, the MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can also be diversity transmission, precoding transmission, beamforming transmission, etc.

[0796] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0797] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for realizing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0798] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the processor-readable memory generate a manufactured product including an instruction device, and the instruction device realizes the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0799] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide for realizing the functions in the process Figure 1One or more processes and / or boxes Figure 1 Steps of the functions specified in one or more boxes.

[0800] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these changes and modifications.

Claims

1. An information sending method, characterized in that, An application establishes communication between a remote terminal and a network - side device through a relay terminal, including: Obtaining first - related information generated during the communication process and sending the first - related information to the network - side device; Wherein, the first - related information includes one or more combinations of the following: Time information; the time information includes one or more combinations of the following: the duration from establishing a PC5 connection to the occurrence of the communication process; the duration from a handover - related moment to RLF; the duration experienced after detecting RLF; the duration from RLF to establishing a PC5 connection; the duration experienced after detecting HOF; the duration from HOF to establishing a PC5 connection; the duration from establishing a PC5 connection to entering the Radio Resource Control (RRC) connected state; the duration from RLF to entering the RRC connected state; the duration from HOF to entering the RRC connected state; wherein, RLF includes PC5 RLF or Uu RLF; Successful handover report trigger conditions; the successful handover report trigger conditions include one or more combinations of the following: the T400 timer is greater than the timer threshold and not timed out; the transmission count of the sidelink RLC entity is greater than or equal to the first transmission threshold and less than the first transmission count; the consecutive Hybrid Automatic Repeat reQuest (HARQ) non - continuous transmission count of the MAC entity is greater than or equal to the second transmission threshold and less than the second transmission count; Wherein, the first - related information further includes one or more combinations of the following: Relay - terminal information; Remote - terminal information; Identification information of the serving cell; Measurement information; Cause information; Type information corresponding to the communication process.

2. The method according to claim 1, wherein The communication process includes one or more combinations of the following: Connection - establishment process; Connection - recovery process; Radio - link - failure process; Handover process.

3. The method according to claim 1, characterized in that, The relay - terminal information includes: identification information of the relay terminal; and / or, the correspondence between the identification information and a specified event; and / or, the location information of the relay terminal; Wherein, the specified event includes at least one of the following events: Connection establishment; Detecting Radio - Link Failure (RLF); Detecting Handover Failure (HOF); Handover; Returning to the connection after connection failure or re - establishment failure; Re - establishing after connection failure; Attempting to establish a PC5 connection after RLF of the remote terminal, where RLF includes PC5 RLF or Uu RLF; Attempting to establish a PC5 connection after HOF of the remote terminal.

4. The method according to claim 1, characterized in that The remote - terminal information includes one or more combinations of the following: Identification information of the remote terminal, including the identification information of the remote terminal that establishes a PC5 connection with the relay terminal; Location information of the remote terminal; The number of remote terminals that establish a PC5 connection with the relay terminal.

5. The method according to claim 1, wherein The measurement information includes one or more combinations of the following: PC5 measurement results of the remote terminal; PC5 measurement results between the remote terminal and the relay terminal that establishes a PC5 connection with the remote terminal; Uu - link measurement results of the remote terminal; PC5 measurement results of the relay terminal; PC5 measurement results between the relay terminal and the remote terminal that establishes a PC5 connection with the relay terminal; Uu - link measurement results of the relay terminal.

6. The method according to claim 1, characterized in that, The cause information includes one or more combinations of the following: Reasons for connection establishment failure, where the connection establishment includes a relay terminal assisting a remote terminal in establishing a connection; Reasons for connection recovery failure; Reasons for radio link failure, where the radio link includes a PC5 link or a Uu link; Reasons for connection establishment, where the reasons for connection establishment are to establish a connection for a remote terminal.

7. The method according to claim 6, characterized in that If the radio link is a PC5 link, the reasons for the radio link failure include one or more of the following combinations: Timeout of the T400 timer; The number of transmissions of the sidelink radio link control (RLC) entity is greater than or equal to the first number of transmissions; The number of consecutive hybrid automatic repeat request (HARQ) discontinuous transmissions of the media access control (MAC) entity is greater than or equal to the second number of transmissions; The integrity check of the sidelink signaling radio bearer associated with the sidelink packet data convergence protocol (PDCP) entity fails.

8. The method according to claim 6, wherein The reasons for the connection establishment failure include one or more of the following combinations: The relay terminal is in a connected state, and the connection establishment of the remote terminal fails; The relay terminal is in an idle state or a non-active state, the connection establishment of the relay terminal fails, and the connection establishment of the remote terminal fails.

9. The method according to claim 6, wherein The reasons for the connection recovery failure include one or more of the following combinations: The relay terminal is in a connected state, and the connection recovery of the remote terminal fails; The relay terminal is in an idle state or a non-active state, the connection recovery of the relay terminal fails, and the connection recovery of the remote terminal fails.

10. The method according to claim 1, characterized in that The type information corresponding to the communication process includes one or more of the following combinations: Connection failure type, where the connection failure type includes one or more of the following combinations: remote terminal radio link failure (RLF), remote terminal handover failure (HOF); Handover type, where the handover type includes one or more of the following combinations: handover from direct connection to PC5 connection, handover from PC5 connection to direct connection, handover from PC5 connection to PC5 connection; Handover failure type, where the handover failure type includes one or more of the following combinations: handover failure from direct connection to PC5 connection, handover failure from PC5 connection to direct connection, handover failure from PC5 connection to PC5 connection.

11. The method according to claim 1, wherein The identification information of the serving cell includes one or more of the following combinations: The identification information of the source cell of the last handover; When the connection before handover is a PC5 connection, the identification information of the serving cell of the remote terminal before the last handover; The identification information of the serving cell of the remote terminal where RLF is detected; The identification information of the serving cell of the remote terminal where HOF is detected; The identification information of the serving cell of the remote terminal that returns to the connection after connection failure; The identification information of the serving cell of the remote terminal that returns to the connection after reconstruction failure.

12. The method according to claim 3 or 4, characterized in that, The identification information includes one or more of the following combinations: Cell radio network temporary identifier (C-RNTI); Layer 2 identifier.

13. An information sending device, characterized in that, Including: A memory, a transceiver, and a processor; The memory is used to store program instructions; The transceiver is used to transmit and receive data under the control of the processor; The processor is used to read the program instructions in the memory; The transceiver is used for: Obtaining first relevant information generated during the communication process and sending the first relevant information to the network-side device; Wherein, the communication is established by a remote terminal through a relay terminal with a network-side device; the first related information includes one or more combinations of the following: Time information; the time information includes one or more combinations of the following: the duration from establishing a PC5 connection to the occurrence of the communication process; the duration from a handover-related moment to RLF; the duration elapsed after detecting RLF; the duration from RLF to establishing a PC5 connection; the duration elapsed after detecting HOF; the duration from HOF to establishing a PC5 connection; the duration from establishing a PC5 connection to entering the radio resource control (RRC) connected state; the duration from RLF to entering the RRC connected state; the duration from HOF to entering the RRC connected state; wherein, RLF includes PC5 RLF or Uu RLF; Successful handover report triggering conditions; the successful handover report triggering conditions include one or more combinations of the following: the T400 timer is greater than the timer threshold and has not timed out; the transmission times of the sidelink RLC entity are greater than or equal to the first transmission threshold and less than the first number of transmissions; the consecutive HARQ non-consecutive transmission times of the MAC entity are greater than or equal to the second transmission threshold and less than the second number of transmissions; Wherein, the first related information further includes one or more combinations of the following: Relay terminal information; Remote terminal information; Identification information of the serving cell; Measurement information; Cause information; Type information corresponding to the communication process.

14. A transmission processing device, characterized in that, Including: A first sending module, configured to obtain the first related information generated during the communication process and send the first related information to the network-side device; Wherein, the communication is established by a remote terminal through a relay terminal with a network-side device; the first related information includes one or more combinations of the following: Time information; the time information includes one or more combinations of the following: the duration from establishing a PC5 connection to the occurrence of the communication process; the duration from a handover-related moment to RLF; the duration elapsed after detecting RLF; the duration from RLF to establishing a PC5 connection; the duration elapsed after detecting HOF; the duration from HOF to establishing a PC5 connection; the duration from establishing a PC5 connection to entering the radio resource control (RRC) connected state; the duration from RLF to entering the RRC connected state; the duration from HOF to entering the RRC connected state; wherein, RLF includes PC5 RLF or Uu RLF; Successful handover report triggering conditions; the successful handover report triggering conditions include one or more combinations of the following: the T400 timer is greater than the timer threshold and has not timed out; the transmission times of the sidelink RLC entity are greater than or equal to the first transmission threshold and less than the first number of transmissions; the consecutive HARQ non-consecutive transmission times of the MAC entity are greater than or equal to the second transmission threshold and less than the second number of transmissions; Wherein, the first related information further includes one or more combinations of the following: Relay terminal information; Remote terminal information; Identification information of the serving cell; Measurement information; Cause information; Type information corresponding to the communication process.

15. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program for causing the processor to execute the information sending method according to any one of claims 1 to 12.

Images