A connection failure processing method and device, and a readable storage medium

Abstract

The present disclosure provides a connection failure processing method, device and readable storage medium, wherein the method comprises: in response to a connection failure of the relay UE, recording relay link information. In the method of the present disclosure, the relay UE or the remote UE can record the relay link information when the connection failure occurs, and send it to the network device at an appropriate time. Therefore, the network device can not only receive the failure information of the Uu interface, but also receive the relay link information, and then the network device can optimize the sidelink according to the relay link information, or perform other appropriate related processing.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and in particular to a method, apparatus and readable storage medium for handling connection failures. Background Technology

[0002] To enable operators to better optimize networks, a minimum drive test (MDT) mechanism was introduced. When a user equipment (UE) experiences a connection failure, the cause could be a radio link failure or a handover failure. The UE can record the corresponding failure information. After the UE restores its connection with the base station, it can report the recorded failure information to the base station, which can then use this information to further optimize the network. In a new radio (NR) system, the communication interface between the terminal and the base station can be called the Uu interface.

[0003] To support direct communication between UEs, a sidelink communication method was introduced, with the PC-5 interface serving as the communication interface between UEs. In the event of a connection failure, the UE only stores the failure information from the Uu interface and not the failure information from the sidelink, thus preventing operators from optimizing for the sidelink. Summary of the Invention

[0004] In view of this, the present disclosure provides a method, apparatus and readable storage medium for handling connection failures.

[0005] According to a first aspect of the present disclosure, a method for handling connection failures is provided, the method being executed by a relay user equipment (UE), wherein the method includes:

[0006] In response to a connection failure of the relay UE, the relay link information is recorded.

[0007] Using this method, the relay UE can record relay link information when a connection failure occurs. At an appropriate time, the relay UE can send not only the Uu interface failure information to the network device, but also the relay link information, so that the network device can optimize the sidelink or perform other appropriate related processing based on the relay link information.

[0008] In one possible implementation, wherein,

[0009] The connection failure includes at least one of the following:

[0010] Wireless link failure, connection reconstruction failure, handover failure, reconfiguration failure.

[0011] In one possible implementation, wherein,

[0012] The response to a connection failure of the relay UE includes recording relay link information, including:

[0013] In response to a connection failure of the relay UE and the relay UE having established a sidelink unicast connection with at least one remote UE, the relay link information is recorded.

[0014] In one possible implementation, wherein,

[0015] The relay link information includes at least one of the following:

[0016] The identifier of the remote UE corresponding to the relay link,

[0017] The status of the remote UE corresponding to the relay link

[0018] The reasons for failure include wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0019] In one possible implementation, wherein,

[0020] The identifier of the remote UE includes at least one of the following:

[0021] The side-link layer 2 or layer 1 identifier of the remote UE,

[0022] The remote UE's cell radio network temporary identifier (C-RNTI)

[0023] The remote UE's 5G serving temporary mobile subscriber identity (5G-S-TMSI)

[0024] The inactive wireless network temporary identifier (I-RNTI) of the remote user equipment.

[0025] In one possible implementation, wherein,

[0026] In response to the remote UE being in a connected state, the C-RNTI is received from the remote UE.

[0027] In one possible implementation, wherein,

[0028] In response to the remote UE being in an idle state, the 5G-S-TMSI is received from the remote UE.

[0029] In one possible implementation, wherein,

[0030] In response to the remote UE being in an inactive state, the I-RNTI is received from the remote UE.

[0031] In one possible implementation, wherein,

[0032] The method further includes:

[0033] In response to the relay UE establishing a connection with the network, the recorded relay link information is sent to the network device.

[0034] According to a second aspect of the present disclosure, a method for handling connection failures is provided, the method being executed by a remote user equipment (UE), wherein the method includes:

[0035] In response to a connection failure of a relay UE, the relay link information is recorded.

[0036] Using this method, the remote UE can record trunk link information when a trunk UE experiences a connection failure. At an appropriate time, the remote UE can send not only the Uu interface failure information to the network device, but also the trunk link information, so that the network device can optimize the sidelink or perform other appropriate related processing based on the trunk link information.

[0037] In one possible implementation, wherein,

[0038] The connection failure includes at least one of the following:

[0039] Wireless link failure, connection reconstruction failure, handover failure, reconfiguration failure.

[0040] In one possible implementation, wherein,

[0041] Receive the connection failure indication sent by the relay UE.

[0042] In one possible implementation, the connection failure indicator is used to indicate the reason for the failure.

[0043] In one possible implementation, wherein,

[0044] The relay link information includes:

[0045] The identifier of the relay UE,

[0046] Reasons for failure.

[0047] In one possible implementation, wherein,

[0048] The reasons for the failure are wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0049] In one possible implementation, wherein,

[0050] Receive the Cell Radio Network Temporary Identifier (C-RNTI) or the Sidelink Layer 1 or Layer 2 Identifier from the relay UE.

[0051] In one possible implementation, wherein,

[0052] The method further includes:

[0053] In response to the establishment of a connection between the remote UE and the network, the recorded relay link information is sent to the network device.

[0054] According to a third aspect of the present disclosure, a communication apparatus is provided. This communication apparatus can be used to perform the steps executed by a relay user equipment (UE) in the first aspect or any possible design of the first aspect. The relay UE can implement the functions of the methods described above through hardware structures, software modules, or a combination of hardware structures and software modules.

[0055] When the communication device shown in the third aspect is implemented by a software module, the communication device may include a transceiver module, wherein the transceiver module can be used to support the communication device in performing communication.

[0056] When performing the steps described in the first aspect above, the transceiver module is used to record relay link information in response to a connection failure of the relay UE.

[0057] According to a fourth aspect of the present disclosure, a communication apparatus is provided. This communication apparatus can be used to perform the steps executed by a remote user equipment (UE) in the second aspect or any possible design of the second aspect. The remote UE can implement the functions of the methods described above through hardware structures, software modules, or a combination of hardware structures and software modules.

[0058] When the communication device shown in the fourth aspect is implemented by a software module, the communication device may include a transceiver module, wherein the transceiver module can be used to support the communication device in communicating.

[0059] When performing the steps described in the second aspect above, the transceiver module is used to record the relay link information in response to a connection failure of the relay UE.

[0060] According to a fifth aspect of the present disclosure, a communication device is provided, including a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program to implement the first aspect or any possible design of the first aspect.

[0061] According to a sixth aspect of the present disclosure, a communication device is provided, including a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program to implement the second aspect or any possible design of the second aspect.

[0062] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided, wherein instructions (or computer programs, programs) are stored therein, which, when invoked and executed on a computer, cause the computer to perform the first aspect or any possible design of the first aspect.

[0063] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided, wherein instructions (or computer programs, programs) are stored therein, which, when invoked and executed on a computer, cause the computer to perform the second aspect or any possible design of the second aspect described above.

[0064] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0065] The accompanying drawings, which are included to provide a further understanding of the embodiments of this disclosure and form part of this application, illustrate exemplary embodiments of this disclosure and, together with their descriptions, serve to explain the embodiments of this disclosure and do not constitute an improper limitation of the embodiments of this disclosure. In the drawings:

[0066] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0067] Figure 1 This is a schematic diagram of a wireless communication system architecture provided in an embodiment of this disclosure;

[0068] Figure 2 This is a flowchart illustrating a connection failure handling method according to an exemplary embodiment;

[0069] Figure 3 This is a structural diagram of a connection failure processing device according to an exemplary embodiment;

[0070] Figure 4 This is a structural diagram of another connection failure processing device according to an exemplary embodiment;

[0071] Figure 5 This is a structural diagram of another connection failure processing device according to an exemplary embodiment;

[0072] Figure 6This is a structural diagram of another connection failure processing device according to an exemplary embodiment;

[0073] Figure 7 This is a structural diagram of another connection failure processing device according to an exemplary embodiment. Detailed Implementation

[0074] The embodiments of this disclosure will now be further described in conjunction with the accompanying drawings and specific implementation details.

[0075] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0076] like Figure 1 As shown, the connection failure handling method provided in this embodiment can be applied to a wireless communication system 100, which may include, but is not limited to, a network device 101 and multiple user devices. The user devices are configured to support carrier aggregation and can connect to multiple carrier units of the network device 101, including a primary carrier unit and one or more secondary carrier units.

[0077] Among the multiple user equipments, the one directly connected to network device 101 and providing relay function is called relay user equipment (relay UE) 102, and the one not directly connected to network device 101 is called remote user equipment (remote UE) 103. Relay UE 102 and remote UE 103 communicate based on a sidelink, and remote UE 103 communicates with network device 101 through relay UE 102.

[0078] It should be understood that the wireless communication system 100 described above is applicable to both low-frequency and high-frequency scenarios. Application scenarios for the wireless communication system 100 include, but are not limited to, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, worldwide interoperability for microwave access (WiMAX) communication systems, cloud radio access network (CRAN) systems, future 5th-generation (5G) systems, new radio (NR) communication systems, or future evolved public land mobile network (PLMN) systems.

[0079] The user equipment shown above can be user equipment (UE), terminal, access terminal, terminal unit, terminal station, mobile station (MS), remote station, remote terminal, mobile terminal, wireless communication equipment, terminal agent, or user equipment, etc. This user equipment may have wireless transceiver capabilities, enabling it to communicate (e.g., wireless communication) with one or more network devices in one or more communication systems, and to receive network services provided by network device 102. These network devices include, but are not limited to, the base station shown in the diagram.

[0080] User equipment can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, user equipment in future 5G networks, or user equipment in future evolved PLMN networks, etc.

[0081] Network device 101 can be an access network device (or access point). Access network device refers to equipment that provides network access functionality, such as a radio access network (RAN) base station. Specifically, network device may include base station (BS) equipment, or base station equipment and radio resource management equipment used to control the base station equipment. This network device may also include relay stations (relay equipment), access points, and base stations in future 5G networks, base stations in future evolved PLMN networks, or NR base stations. Network device can be a wearable device or an in-vehicle device. Network device can also be a communication chip with a communication module.

[0082] For example, network equipment 101 includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (eNB) in LTE systems, radio network controllers (RNC), node B (NB) in WCDMA systems, radio controllers and base station controllers (BSC) in CRAN systems, base transceiver stations (BTS) in GSM or CDMA systems, home base stations (e.g., home evolved nodeB, or home node B, HNB), baseband units (BBU), transmitting and receiving points (TRP), transmitting points (TP), or mobile switching centers, etc.

[0083] The sidelink supports unicast, multicast, and broadcast transmission modes. To support higher transmission rates and higher reliability, a unicast connection needs to be established on the sidelink (SL).

[0084] This disclosure provides a method for handling connection failures. Figure 2 This is a flowchart illustrating a connection failure handling method according to an exemplary embodiment, such as... Figure 2 As shown, the method includes:

[0085] S21. In response to a connection failure in relay UE 102, relay UE 102 records relay link information.

[0086] S22. In response to the connection failure of relay UE 102, remote UE 103 records the relay link information.

[0087] S23. The relay UE 102 sends relay link information to the network device 101, or the remote UE 103 sends relay link information to the network device 101.

[0088] S24. Network device 101 receives relay link information sent by relay UE 102 or remote UE 103.

[0089] In this embodiment of the disclosure, when a connection failure occurs, either the relay UE 102 or the remote UE 103 can record the relay link information and send it to the network device 101 at an appropriate time. The network device 101 can receive not only the failure information of the Uu interface but also the relay link information, thereby allowing the network device to optimize the sidelink or perform other appropriate related processing based on the relay link information.

[0090] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0091] Step S101: In response to the connection failure of relay UE 102, record the relay link information.

[0092] In some possible implementations, network device 101, relay UE 102, and remote UE 103 are connected sequentially. A connection failure can occur between relay UE 102 and network device 101, or between relay UE 102 and remote UE 103. In one example, a connection failure between relay UE 102 and network device 101 will cause a connection failure between relay UE 102 and remote UE 103.

[0093] In one example, if a connection failure occurs between the relay UE 102 and the network device 101, it will not cause a connection failure between the relay UE 102 and the remote UE 103.

[0094] In one example, if a connection failure occurs between the relay UE 102 and the network device 101, it will not cause a connection failure between the relay UE 102 and the remote UE 103, and the relay UE 102 and the remote UE 103 will still communicate normally.

[0095] In some possible implementations, a remote UE, a relay UE, and another remote UE are connected sequentially. Connection failure could be due to a failure of the sidelink connection between the relay UE and any of the remote UEs.

[0096] In one example, a connection failure between relay UE 104 and remote UE 102 will cause a connection failure between remote UE 102 and remote UE 105.

[0097] In some possible implementations, the relay UE 102 may store the relay link information in its internal memory. Alternatively, the relay UE 102 may store the relay link information in a server or other node device.

[0098] In one example, relay UE 102 may store only one set of relay link information.

[0099] In some possible implementations, the relay UE 102 stores the relay link information for a set duration.

[0100] In this embodiment of the disclosure, the relay UE 102 can record relay link information when a connection failure occurs. At an appropriate time, the relay UE can send not only the failure information of the Uu interface to the network device, but also the relay link information, so that the network device can optimize the sidelink based on the relay link information.

[0101] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0102] In response to a connection failure of a relay UE, the relay link information is recorded.

[0103] Connection failure includes at least one of the following:

[0104] Wireless link failure, connection reconstruction failure, handover failure, reconfiguration failure.

[0105] In this embodiment of the disclosure, the relay UE 102 can record relay link information in multiple connection failure scenarios and send it to the network device 101, so that the network device 101 can optimize the sidelink in a timely and more targeted manner.

[0106] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0107] In step S201, in response to a connection failure of the relay UE 102 and the fact that the relay UE 102 has established a sidelink unicast connection with at least one remote UE 103, the relay link information is recorded.

[0108] In some possible implementations, a connection failure occurs between the relay UE 102 and the network device 101, and the relay UE 102 has established a sidelink unicast connection with at least one remote UE 103, recording the relay link information.

[0109] In one example, a connection failure between relay UE 102 and network device 101 affects all or part of the sidelink unicast connections between relay UE 102 and remote UE 103. After the connection failure between relay UE 102 and network device 101, the sidelink unicast connections between relay UE 102 and some remote UEs 103 can remain normal, while the sidelink unicast connections between relay UE 102 and another group of remote UEs 103 fail. In this case, relay UE 102 records the link information of the sidelink unicast connections, such as the link information of the sidelink unicast connections that failed.

[0110] In some possible implementations, the relay UE 102 has a normal connection with the network device 101, the relay UE 102 fails to establish a sidelink unicast connection with at least one remote UE 103, and the relay UE 102 maintains a normal connection with the other remote UE 103's sidelink unicast connections, recording relay link information.

[0111] In one example, the relay UE 102 has a normal connection with the network device 101. The relay UE 102 has established sidelink unicast connections with three remote UEs 103. After the sidelink connection between the relay UE 102 and one of the remote UEs 103 fails, the sidelink connections between the relay UE 102 and the other two remote UEs 103 remain normal. In this case, the relay UE 102 records the link information of the sidelink unicast connections, for example, the link information of the sidelink unicast connections that failed. In this embodiment of the present disclosure, the relay UE 102 can record relay link information only when the condition of establishing an SL unicast connection with at least one remote UE 103 is met. Therefore, the relay UE 102 can record more valuable relay link information, reduce the workload of the relay UE 102, and improve the working efficiency of the relay UE 102.

[0112] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0113] Step S101: In response to a connection failure of the relay UE, record the relay link information;

[0114] or,

[0115] Step S201: In response to a connection failure of the relay UE and the relay UE having established a sidelink unicast connection with at least one remote UE, record the relay link information.

[0116] The relay link information includes at least one of the following:

[0117] The identifier of the remote UE 103 corresponding to the relay link,

[0118] The status of the remote UE 103 corresponding to the relay link.

[0119] Reasons for failure.

[0120] The reasons for failure include wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0121] In some possible implementations, when the connection failure is caused by a radio link failure, the failure reason is set to radio link failure. When the connection failure is caused by a connection re-establishment failure, the failure reason is set to connection re-establishment failure. When the connection failure is caused by a handover failure, the failure reason is set to handover failure. When the connection failure is caused by a reconfiguration failure, the failure reason is set to reconfiguration failure.

[0122] In some possible implementations, the state of the remote UE 103 includes an idle state, an inactive state, and a connected state. The remote UE 103 may be in an idle state, an inactive state, or a connected state.

[0123] In this embodiment of the disclosure, the relay UE 102 can send various relay link information related to connection failure to the network device 101, enabling the network device 101 to optimize the sidelink in different aspects.

[0124] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0125] Step S101: In response to a connection failure of the relay UE, record the relay link information;

[0126] or,

[0127] Step S201: In response to a connection failure of the relay UE and the relay UE having established a sidelink unicast connection with at least one remote UE, record the relay link information.

[0128] The identifier of the remote UE 103 includes at least one of the following:

[0129] The side-link layer 2 or layer 1 identifier of the remote UE 103

[0130] The temporary identifier (C-RNTI) of the cell radio network for remote UE 103

[0131] 5G Service Temporary Mobile Subscriber Identity (5G-S-TMSI) of Remote UE 103

[0132] The inactive wireless network temporary identifier I-RNTI for remote user equipment 103.

[0133] In this embodiment of the disclosure, the relay UE 102 can record various identifiers of the remote UE 103 so that after reporting the relay link information, the network device 101 can more accurately locate the user equipment corresponding to the relay link, which facilitates more accurate optimization of the sidelink.

[0134] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0135] Step S101: In response to a connection failure of the relay UE, record the relay link information;

[0136] or,

[0137] Step S201: In response to a connection failure of the relay UE and the relay UE having established a sidelink unicast connection with at least one remote UE, record the relay link information.

[0138] The identifier of the remote UE 103 includes at least one of the following:

[0139] The sidelink layer 2 or layer 1 identifier of the remote UE 103

[0140] C-RNTI (CellRadioNetworkTemporaryIdentifier) ​​of remote UE 103

[0141] 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​of remote UE 103

[0142] I-RNTI (Inactive Radio Network Temporary Identity) for remote UE 103.

[0143] In one possible implementation, the method further includes:

[0144] In response to the remote UE 103 being in a connected state, C-RNTI is received from the remote UE 103.

[0145] In one possible implementation, the method further includes:

[0146] In response to the remote UE 103 being in an idle state, 5G-S-TMSI is received from the remote UE 103.

[0147] In one possible implementation, the method further includes:

[0148] In response to the remote UE 103 being inactive, I-RNTI is received from the remote UE 103.

[0149] In this embodiment of the disclosure, the relay UE 102 can receive the corresponding remote UE 103 identifier based on the different states of the remote UE 103, thereby enabling the relay UE 102 to record more valuable information about the remote UE 103 and improve the success rate and accuracy of the network device 101sidelink optimization process.

[0150] This disclosure provides a method for handling connection failures, which is executed by a relay user equipment (UE) 102. The method includes:

[0151] Step S101: In response to a connection failure of the relay UE, record the relay link information;

[0152] or,

[0153] Step S201: In response to a connection failure of the relay UE and the relay UE having established a sidelink unicast connection with at least one remote UE, record the relay link information.

[0154] The identifier of the remote UE 103 includes at least one of the following:

[0155] The sidelink layer 2 or layer 1 identifier of the remote UE 103

[0156] C-RNTI of remote UE 103

[0157] 5G-S-TMSI of remote UE 103

[0158] I-RNTI for remote UE 103.

[0159] The method also includes:

[0160] In response to the establishment of a connection between the relay UE 102 and the network, the recorded relay link information is sent to the network device 101.

[0161] In some possible implementations, after reporting the relay link information, the relay UE 102 can clear the current relay link information and record new relay link information.

[0162] In this embodiment of the disclosure, the relay UE 102 can promptly report the recorded relay link information after establishing a connection with the network, so that the network device 101 can optimize the sidelink in a timely manner.

[0163] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0164] Step S301: In response to the connection failure of relay UE 102, record the relay link information.

[0165] In some possible implementations, network device 101, relay UE 102, and remote UE 103 are connected in sequence. Connection failure may be a failure to connect relay UE 102 to network device 101, or a failure to connect relay UE 102 to remote UE 103.

[0166] In one example, a connection failure between relay UE 102 and network device 101 will cause a connection failure between relay UE 102 and remote UE 103.

[0167] In one example, if a connection failure occurs between the relay UE 102 and the network device 101, it will not cause a connection failure between the relay UE 102 and the remote UE 103.

[0168] In one example, if a connection failure occurs between the relay UE 102 and the network device 101, it will not cause a connection failure between the relay UE 102 and the remote UE 103, and the relay UE 102 and the remote UE 103 will still communicate normally.

[0169] In some possible implementations, a remote UE, a relay UE, and another remote UE are connected sequentially. Connection failure could be due to a failure of the sidelink connection between the relay UE and any of the remote UEs.

[0170] In one example, a connection failure between relay UE 104 and remote UE 102 will cause a connection failure between remote UE 102 and remote UE 105.

[0171] In this embodiment of the disclosure, the remote UE 103 can record relay link information when the relay UE 102 experiences a connection failure. At an appropriate time, the remote UE 103 can send not only the failure information of the Uu interface to the network device 101, but also the relay link information to the network device 101, so that the network device 101 can optimize the sidelink based on the relay link information or perform other appropriate related processing.

[0172] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0173] Step S301: In response to the connection failure of relay UE 102, record the relay link information.

[0174] Connection failure includes at least one of the following:

[0175] Wireless link failure, connection reconstruction failure, handover failure, reconfiguration failure.

[0176] In this embodiment of the disclosure, the remote UE 103 can record relay link information in multiple connection failure scenarios, so that the network device 101 can optimize the sidelink in a timely and more targeted manner after receiving the relay link information.

[0177] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0178] Step S301: In response to the connection failure of relay UE 102, record the relay link information. And,

[0179] Receive connection failure indication sent by relay UE 102.

[0180] In some possible implementations, a connection failure indicator is used to indicate the reason for the failure.

[0181] In some examples, the reasons for failure are wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0182] In this embodiment of the disclosure, the remote UE 103 can promptly determine the cause of the connection failure based on the connection failure indication sent by the relay UE 102, which is conducive to accurately reporting the cause of the failure to the network device 101, so that the network device 101 can optimize the sidelink in a timely manner.

[0183] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0184] Step S301: In response to the connection failure of relay UE 102, record the relay link information. And,

[0185] Relay link information includes one of the following:

[0186] Relay UE identifier,

[0187] The reasons for failure include wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0188] In this embodiment of the disclosure, the remote UE 103 can send various relay link information related to connection failures to the network device 101, enabling the network device 101 to optimize the sidelink in different aspects.

[0189] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0190] Step S301: In response to the connection failure of relay UE 102, record the relay link information. And,

[0191] Receive the Cell Radio Network Temporary Identifier (C-RNTI) or the Side Link Layer 1 or Layer 2 Identifier from the relay UE 102.

[0192] In some possible implementations, the relay link information includes one of the following: the identifier of the relay UE and the reason for failure, wherein the reason for failure is radio link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0193] In this embodiment of the disclosure, the remote UE 102 can obtain the C-RNTI of the relay UE 102 so that after reporting the relay link information to the network device 101, the network device 101 can promptly and accurately determine the relay UE 102 that has experienced a connection failure.

[0194] This disclosure provides a method for handling connection failures, which is executed by a remote user equipment (UE) 103. The method includes:

[0195] Step S301: In response to the connection failure of relay UE 102, record the relay link information. And,

[0196] In response to the establishment of a connection between the remote UE 103 and the network, the recorded relay link information is sent to the network device 101.

[0197] In this embodiment of the disclosure, the remote UE 103 can promptly report the recorded relay link information after establishing a connection with the network, so that the network device 101 can optimize the sidelink in a timely manner.

[0198] This disclosure provides a method for handling connection failures, which is implemented by network device 101. The method includes:

[0199] Receive relay link information sent by relay UE or remote UE.

[0200] In some possible implementations, the relay link information includes at least one of the following:

[0201] The identifier of the remote UE corresponding to the relay link,

[0202] The status of the remote UE corresponding to the relay link

[0203] The reasons for failure include wireless link failure, connection reconstruction failure, handover failure, or reconfiguration failure.

[0204] In some possible implementations, the identifier of the remote UE includes at least one of the following:

[0205] The remote UE's side-link layer 2 or layer 1 identifier,

[0206] Cellular Radio Network Temporary Identifier (C-RNTI) of the remote UE

[0207] 5G Service Temporary Mobile Subscriber Identity (5G-S-TMSI) of the remote UE

[0208] Temporary Identifier for Inactive Wireless Networks (I-RNTI) of Remote User Equipment.

[0209] Based on the same concept as the above method embodiments, this disclosure also provides a communication device that can have the functions of the relay user equipment UE 102 in the above method embodiments and is used to execute the steps performed by the relay UE 102 provided in the above embodiments. This function can be implemented in hardware, or in software, or in hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0210] In one possible implementation, such as Figure 3 The communication device 300 shown can serve as the relay UE 102 involved in the above method embodiments, and perform the steps executed by the relay UE 102 in the above method embodiments. For example... Figure 3 As shown, the communication device 300 may include a transceiver module 301. The transceiver module 301 can be used to support the communication device 300 in communication, and the transceiver module 301 may have wireless communication functions, such as being able to communicate wirelessly with other communication devices through a wireless air interface.

[0211] When performing the steps implemented by the relay UE 102, the transceiver module 301 records the relay link information in response to a connection failure of the relay UE 102.

[0212] When the communication device is a relay UE 102, its structure can also be as follows: Figure 4 As shown. Device 400 can be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0213] Reference Figure 4 The device 400 may include one or more of the following components: a processing component 402, a memory 404, a power supply component 406, a multimedia component 408, an audio component 410, an input / output (I / O) interface 412, a sensor component 414, and a communication component 416.

[0214] Processing component 402 typically controls the overall operation of device 400, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 402 may include one or more processors 420 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 402 may include one or more modules to facilitate interaction between processing component 402 and other components. For example, processing component 402 may include a multimedia module to facilitate interaction between multimedia component 408 and processing component 402.

[0215] Memory 404 is configured to store various types of data to support the operation of device 400. Examples of this data include instructions for any application or method operating on device 400, contact data, phonebook data, messages, pictures, videos, etc. Memory 404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0216] Power supply component 406 provides power to various components of device 400. Power supply component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 400.

[0217] Multimedia component 408 includes a screen that provides an output interface between device 400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 408 includes a front-facing camera and / or a rear-facing camera. When device 400 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0218] Audio component 410 is configured to output and / or input audio signals. For example, audio component 410 includes a microphone (MIC) configured to receive external audio signals when device 400 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 404 or transmitted via communication component 416. In some embodiments, audio component 410 also includes a speaker for outputting audio signals.

[0219] I / O interface 412 provides an interface between processing component 402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0220] Sensor assembly 414 includes one or more sensors for providing state assessments of various aspects of device 400. For example, sensor assembly 414 may detect the on / off state of device 400, the relative positioning of components such as the display and keypad of device 400, changes in the position of device 400 or a component of device 400, the presence or absence of user contact with device 400, the orientation or acceleration / deceleration of device 400, and temperature changes of device 400. Sensor assembly 414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 414 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 414 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0221] Communication component 416 is configured to facilitate wired or wireless communication between device 400 and other devices. Device 400 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 416 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 416 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0222] In an exemplary embodiment, the apparatus 400 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0223] Based on the same concept as the above method embodiments, this disclosure also provides a communication device that can have the functions of the remote user equipment UE 103 in the above method embodiments and is used to execute the steps performed by the remote UE 103 provided in the above embodiments. This function can be implemented in hardware, or in software, or in hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0224] In one possible implementation, such as Figure 5 The communication device 500 shown can serve as the remote UE 103 involved in the above method embodiments, and perform the steps executed by the remote UE 103 in the above method embodiments. For example... Figure 5 As shown, the communication device 500 may include a transceiver module 501. The transceiver module 501 can be used to support the communication device 500 in communication, and the transceiver module 501 may have wireless communication functions, such as being able to communicate wirelessly with other communication devices through a wireless air interface.

[0225] When performing steps implemented by the remote UE 103, the transceiver module 501 records relay link information in response to a connection failure of the relay UE 102.

[0226] When the communication device is a remote UE 103, its structure can also be as follows: Figure 4 As shown.

[0227] Based on the same concept as the above method embodiments, this disclosure also provides a communication device that can have the functions of the network device 101 in the above method embodiments and is used to execute the steps performed by the network device 101 provided in the above embodiments. This function can be implemented by hardware, or by software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0228] In one possible implementation, such as Figure 6 The communication device 600 shown can serve as the network device 101 involved in the above method embodiments, and perform the steps executed by the network device 101 in the above method embodiments. For example... Figure 6 As shown, the communication device 600 may include a transceiver module 601. The transceiver module 601 can be used to support the communication device 600 in communication, and the transceiver module 601 may have wireless communication functions, such as being able to communicate wirelessly with other communication devices through a wireless air interface.

[0229] When performing the steps implemented by network device 101, transceiver module 601 is used to receive relay link information sent by relay UE 102 or remote UE 103.

[0230] When the communication device is a network device, its structure can also be as follows: Figure 7 As shown. Taking network device 101 as a base station as an example, the structure of the communication device is explained. Figure 7 As shown, the device 700 includes a memory 701, a processor 702, a transceiver component 703, and a power supply component 706. The memory 701 is coupled to the processor 702 and can be used to store the programs and data necessary for the communication device 700 to implement its various functions. The processor 702 is configured to support the communication device 700 in performing the corresponding functions described above; this function can be implemented by calling the programs stored in the memory 701. The transceiver component 703 can be a wireless transceiver, used to support the communication device 700 in receiving signaling and / or data, and transmitting signaling and / or data via a wireless air interface. The transceiver component 703 can also be referred to as a transceiver unit or communication unit. The transceiver component 703 may include a radio frequency component 704 and one or more antennas 705. The radio frequency component 704 can be a remote radio unit (RRU), specifically used for transmitting radio frequency signals and converting radio frequency signals to baseband signals. The one or more antennas 705 are specifically used for radiating and receiving radio frequency signals.

[0231] When the communication device 700 needs to send data, the processor 702 performs baseband processing on the data to be sent and outputs a baseband signal to the radio frequency (RF) unit. The RF unit then performs RF processing on the baseband signal and transmits the RF signal as electromagnetic waves through an antenna. When data is sent to the communication device 700, the RF unit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 702. The processor 702 converts the baseband signal back into data and processes the data.

[0232] Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the embodiments of the present disclosure that follow the general principles of the embodiments of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of the embodiments of the present disclosure are indicated by the following claims.

[0233] It should be understood that the embodiments disclosed herein are not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from their scope. The scope of the embodiments disclosed herein is limited only by the appended claims.

[0234] Industrial applicability

[0235] When a connection failure occurs, the relay UE or remote UE can record the relay link information and send it to the network device at an appropriate time. Thus, the network device can receive not only the Uu interface failure information but also the relay link information, allowing it to optimize the sidelink or perform other appropriate related processing based on the relay link information.

Claims

1. A method for handling connection failure, the method being performed by a relay user equipment, UE, wherein, Comprising: In response to the relay UE occurring connection failure, record relay link information; wherein the relay link information comprises at least one of: The identity of the remote UE corresponding to the relay link, The state of the remote UE corresponding to the relay link, Failure reason; The response to the relay UE occurring connection failure, record relay link information, comprising: In response to the occurrence of connection failure between the relay UE and the network device, the sidelink unicast connection with at least one remote UE has been established, and the sidelink unicast connection between the relay UE and a part of remote UEs remains normal connection, and the sidelink unicast connection between the relay UE and another part of remote UEs occurs connection failure, record the link information of the sidelink unicast connection occurring connection failure.

2. The method of claim 1, wherein, The connection failure comprises at least one of: Radio link failure, connection reestablishment failure, handover failure, reconfiguration failure.

3. The method of claim 1, wherein, The response to the relay UE occurring connection failure, record relay link information, comprising: In response to the occurrence of connection failure of the relay UE and the relay UE having established sidelink unicast connection with at least one remote UE, record the relay link information.

4. The method of claim 1, wherein, The failure reason is radio link failure, connection reestablishment failure, handover failure or reconfiguration failure.

5. The method of claim 1, wherein, The identity of the remote UE comprises at least one of: The sidelink layer 2 or layer 1 identity of the remote UE, The cell radio network temporary identifier C-RNTI of the remote UE, The 5G service temporary mobile user identifier 5G-S-TMSI of the remote UE, The inactive radio network temporary identifier I-RNTI of the remote user equipment.

6. The method of claim 5, wherein, In response to the remote UE being in a connected state, receiving the C-RNTI from the remote UE.

7. The method of claim 5, wherein, In response to the remote UE being in an idle state, receiving the 5G-S-TMSI from the remote UE.

8. The method of claim 5, wherein, In response to the remote UE being in an inactive state, receiving the I-RNTI from the remote UE.

9. The method of claim 5, wherein, The method further comprises: In response to the relay UE establishing connection with the network, sending the recorded relay link information to the network device.

10. A method for handling connection failure, the method being performed by a remote user equipment (UE), wherein, Comprising: In response to the occurrence of connection failure of the relay UE, record the relay link information; wherein the relay link information comprises: The identity of the relay UE, Failure reason; The connection failure of the relay UE includes at least one of the following: a radio link failure, a connection reestablishment failure, a handover failure, and a reconfiguration failure. 11.The method of claim 10, wherein, The connection failure includes at least one of the following: a radio link failure, a connection reestablishment failure, a handover failure, and a reconfiguration failure. 12.The method of claim 10, wherein, The connection failure indication is received from the relay UE. 13.The method of claim 12, wherein, The connection failure indication carries a failure cause. 14.The method of claim 10 or 13, wherein, The failure cause is at least one of the following: a radio link failure, a connection reestablishment failure, a handover failure, and a reconfiguration failure. 15.The method of claim 10, wherein, The C-RNTI or the sidelink layer 1 or layer 2 identifier of the relay UE is received from the relay UE. 16.The method of claim 10, wherein, The method further comprises: sending the recorded relay link information to the network device in response to the remote UE establishing a connection with the network. 17.A communication apparatus comprising: a transceiver configured to record relay link information in response to a connection failure of a relay UE; wherein the relay link information comprises at least one of the following: an identifier of a remote UE corresponding to a relay link, a status of the remote UE corresponding to the relay link, a failure cause; the transceiver is configured to: record link information of a sidelink unicast connection in which the connection failure occurs in response to the connection failure of the relay UE, a sidelink unicast connection established with at least one remote UE, and a sidelink unicast connection between the relay UE and a part of the remote UE remaining in a normal connection and a sidelink unicast connection between the relay UE and another part of the remote UE in which the connection failure occurs. 18.A communication apparatus comprising: a transceiver configured to record relay link information in response to a connection failure of a relay UE; wherein the relay link information comprises: an identifier of the relay UE, a failure cause; wherein the connection failure of the relay UE includes a connection failure between the relay UE and a network device, a sidelink unicast connection established with at least one remote UE, and a sidelink unicast connection between the relay UE and a part of the remote UE remaining in a normal connection and a sidelink unicast connection between the relay UE and another part of the remote UE in which the connection failure occurs. 19.A communication apparatus comprising a processor and a memory; the memory is configured to store a computer program; The processor is configured to execute the computer program to implement the method of any one of claims 1-9.

20. A communication apparatus comprising a processor and a memory; The memory is configured to store a computer program; The processor is configured to execute the computer program to implement the method of any one of claims 10-16.

21. A computer readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of any one of claims 1-9.

22. A computer readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of any one of claims 10-16.

Images