A method and apparatus for connection establishment

Abstract

The present disclosure provides a method and device for connection establishment, which can be applied to the technical field of communication. The method comprises: receiving, by a relay, indication information sent by a remote UE, and setting a cause according to the indication information, wherein the cause comprises at least one of the following: a cause for establishing a connection between the relay UE and a base station, and a cause for resuming a connection between the relay UE and the base station. The relay UE receives the indication information sent by the remote UE, and sets the cause for establishing a connection between the relay UE and the base station according to the indication information, wherein the cause comprises at least one of the following: a cause for establishing a connection between the relay UE and the base station, and a cause for resuming a connection between the relay UE and the base station, so that the relay UE can reasonably set the cause for establishing a connection or the cause for resuming a connection, and avoid MP addition failure.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method and apparatus for establishing a connection. Background Technology

[0002] In related technologies, in order to support direct communication between user equipment (UE) and UE, a sidelink communication method has been introduced. A UE can communicate with the base station without directly connecting to it, but through the relay of another UE. The UE that is not connected to the base station is called the remote UE, and the UE that provides the relay function is called the relay UE. The remote UE and the relay UE communicate through sidelink unicast. The relay UE in the idle state or inactive state has no Radio Resource Control (RRC) connection with the base station, while the relay UE in the connected state has an RRC connection with the base station.

[0003] A relay UE in an idle or inactive state can establish an RRC connection through the connection establishment process, thereby entering the connected state. The relay UE needs to send an RRC establishment request message to the base station, which must carry the reason for establishing the connection. Therefore, how to set the establishment reason or the recovery reason is an urgent problem to be solved. Summary of the Invention

[0004] In a first aspect, embodiments of this disclosure provide a method for establishing a connection, the method being executed by a relay terminal device (UE), the method comprising:

[0005] Receive indication information sent by the remote UE;

[0006] The reason for setting the instruction information includes at least one of the following: the reason for the relay UE to establish a connection with the base station, and the reason for the relay UE to restore the connection with the base station.

[0007] In one implementation, the reasons include:

[0008] The reason for the relay UE to establish a Radio Resource Control (RRC) connection with the base station in response to the relay UE being in an idle state is the reason for the relay UE to establish a connection with the base station;

[0009] The reason why the relay UE establishes an RRC connection with the base station in response to the relay UE being in an inactive state is the reason why the relay UE resumes its connection with the base station.

[0010] In one implementation,

[0011] The receipt of indication information sent by the remote UE includes: receiving a direct sidelink RRC message sent by the remote UE, wherein the sidelink RRC message carries the indication information;

[0012] The reason for setting the indication information includes setting the reason for establishing an RRC connection between the relay UE and the base station as the reason indicated by the indication information.

[0013] In one implementation,

[0014] The indication information received from the remote UE includes: receiving the sidelink relay adaptation protocol data unit (PDU) sent by the remote UE;

[0015] The reason for setting the information according to the instruction includes: setting the reason for establishing an RRC connection between the relay UE and the base station according to the Radio Link Control (RLC) entity corresponding to the SRAP PDU.

[0016] In one implementation, the reason for setting the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the SRAP PDU includes:

[0017] The RLC entity is the first RLC entity, and the first reason is set as the reason for the relay UE to establish an RRC connection with the base station.

[0018] In one implementation, the first reason is any of the following:

[0019] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0020] In one implementation, the method further includes:

[0021] Obtain the correspondence between the first RLC identifier and the first reason.

[0022] In one implementation, obtaining the correspondence between the first RLC and the first cause includes:

[0023] Obtain the correspondence between the first RLC identifier configured in the network device and the first reason;

[0024] Alternatively, receive the correspondence between the first RLC identifier and the first reason sent by the remote UE;

[0025] Alternatively, the correspondence between the first RLC identifier and the first reason can be obtained according to the standard specifications.

[0026] In one implementation, the reason for setting the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the SRAP PDU includes:

[0027] The RLC entity is a second RLC entity, and the second reason is set as the reason for the relay UE to establish an RLC connection with the base station.

[0028] In one implementation, the second reason is any of the following:

[0029] User-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice (mo-VoiceCall), user-initiated video call (mo-VideoCall), and user-initiated short message (mo-SMS).

[0030] In one implementation, the method further includes:

[0031] Obtain the identifier and configuration of the first or second RLC.

[0032] In one implementation, obtaining the identifier and configuration of the first RLC or the second RLC includes:

[0033] Obtain the identification and configuration of the first or second RLC in accordance with the standard specifications;

[0034] Alternatively, it may receive system information sent by a network device, the system information carrying the identifier and configuration of the first or second RLC.

[0035] Alternatively, it may receive an RRC message sent by a remote UE, the RRC message carrying the identifier and configuration of the first or second RLC.

[0036] In one implementation, the method further includes:

[0037] The corresponding first RLC entity or second RLC entity is established based on the identifier and configuration of the first or second RLC.

[0038] Secondly, embodiments of this disclosure provide a method for establishing a connection, the method being executed by a remote terminal device (UE), the method comprising:

[0039] Send indication information to the relay UE to indicate the reason for the relay UE establishing a connection with the base station.

[0040] In one implementation, sending indication information to the relay UE includes:

[0041] A direct sidelink radio resource control (RRC) message is sent to the relay UE, and the sidelink RRC message carries the indication information.

[0042] In one implementation, the method further includes:

[0043] Setting instruction information, wherein the setting instruction information includes at least one of the following:

[0044] The indication information is set according to the service type that triggers the connection establishment; the indication information is set by receiving the indication information sent by the network device.

[0045] In one implementation, sending indication information to the relay UE includes:

[0046] The relay UE is sent a Sidelink Relay Adaptation Protocol (SRAP) Data Unit (PDU), and the reason for the relay UE to establish an RRC connection with the base station is indicated based on the Radio Link Control (RLC) entity corresponding to the Sidelink SRAP PDU.

[0047] In one implementation, the method further includes:

[0048] An RRC message is sent to the relay UE, the RRC message carrying the identifier and configuration of the first RLC or the second RLC.

[0049] In one implementation, the method further includes:

[0050] Send the correspondence between the first RLC identifier and the first reason to the relay UE.

[0051] In one implementation, the method further includes:

[0052] Receive any of the following information sent by the network device:

[0053] The first RLC identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0054] In one implementation, the first reason is any of the following:

[0055] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0056] Thirdly, embodiments of this disclosure provide a method for establishing a connection, the method being executed by a network device, the method comprising:

[0057] Send indication information to the remote terminal device (UE) to indicate the reason for the relay UE establishing a connection with the base station.

[0058] In one implementation, sending the indication information to the remote UE includes:

[0059] The indication information determined when adding an indirect path is sent to the remote UE.

[0060] In one implementation, the method further includes:

[0061] Send any of the following information to the remote UE:

[0062] The first Radio Link Control (RLC) identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0063] Fourthly, embodiments of this disclosure provide a connection establishment apparatus, characterized in that the apparatus is disposed in a relay terminal device (UE), and the apparatus includes:

[0064] The receiving module is used to receive indication information sent by the remote UE;

[0065] The processing module is configured to set a reason according to the indication information, the reason including at least one of the following: the reason for the relay UE to establish a connection with the base station, and the reason for the relay UE to restore the connection with the base station.

[0066] In one implementation, the reasons include:

[0067] The reason for the relay UE to establish a Radio Resource Control (RRC) connection with the base station in response to the relay UE being in an idle state is the reason for the relay UE to establish a connection with the base station;

[0068] The reason why the relay UE establishes an RRC connection with the base station in response to the relay UE being in an inactive state is the reason why the relay UE resumes its connection with the base station.

[0069] In one implementation,

[0070] The receiving module is further configured to receive a direct sidelink RRC message sent by the remote UE, wherein the sidelink RRC message carries the indication information;

[0071] The processing module is further configured to set the reason for the relay UE to establish an RRC connection with the base station as the reason indicated by the indication information.

[0072] In one implementation,

[0073] The receiving module is also used to receive the sidelink relay adaptation protocol data unit (PDU) sent by the remote UE.

[0074] The processing module is also used to set the reason for the relay UE to establish an RRC connection with the base station according to the Radio Link Control (RLC) entity corresponding to the SRAP PDU.

[0075] In one implementation, the processing module is further configured to set the first reason as the reason for the relay UE to establish an RRC connection with the base station, since the RLC entity is a first RLC entity.

[0076] In one implementation, the first reason is any of the following:

[0077] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0078] In one implementation, the apparatus further includes:

[0079] The first acquisition module is used to acquire the correspondence between the first RLC identifier and the first reason.

[0080] In one implementation, the first acquisition module is further configured to:

[0081] Obtain the correspondence between the first RLC identifier configured in the network device and the first reason;

[0082] Alternatively, receive the correspondence between the first RLC identifier and the first reason sent by the remote UE;

[0083] Alternatively, the correspondence between the first RLC identifier and the first reason can be obtained according to the standard specifications.

[0084] In one implementation, the processing module is further configured to set the second reason as the reason for the relay UE to establish an RRC connection with the base station, since the RLC entity is a second RLC entity.

[0085] In one implementation, the second reason is any of the following:

[0086] User-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice (mo-VoiceCall), user-initiated video call (mo-VideoCall), and user-initiated short message (mo-SMS).

[0087] In one implementation, the apparatus further includes:

[0088] The second acquisition module is used to acquire the identifier and configuration of the first RLC or the second RLC.

[0089] In one implementation, the second acquisition module is further configured to:

[0090] Obtain the identification and configuration of the first or second RLC in accordance with the standard specifications;

[0091] Alternatively, it may receive system information sent by a network device, the system information carrying the identifier and configuration of the first or second RLC.

[0092] Alternatively, it may receive an RRC message sent by a remote UE, the RRC message carrying the identifier and configuration of the first or second RLC.

[0093] In one implementation, the apparatus further includes:

[0094] The module is used to establish a corresponding first RLC entity or second RLC entity based on the identifier and configuration of the first RLC or second RLC.

[0095] Fifthly, embodiments of this disclosure provide a connection establishment apparatus, the apparatus being disposed in a remote terminal device (UE), the apparatus comprising:

[0096] The sending module is used to send indication information to the relay UE to indicate the reason for the relay UE establishing a connection with the base station.

[0097] In one implementation, the transmitting module is further configured to send a direct sidelink radio resource control (RRC) message to the relay UE, wherein the sidelink RRC message carries the indication information.

[0098] In one implementation, the apparatus further includes:

[0099] A processing module is configured to set indication information, wherein the setting indication information includes at least one of the following:

[0100] The indication information is set according to the service type that triggers the connection establishment; the indication information is set by receiving the indication information sent by the network device.

[0101] In one implementation, the transmitting module is further configured to transmit a Sidelink Relay Adaptation Protocol (SRAP) Data Unit (PDU) to the relay UE, and to indicate the reason for the relay UE to establish an RRC connection with the base station based on the Radio Link Control (RLC) entity corresponding to the sidelink SRAP PDU.

[0102] In one implementation, the apparatus further includes:

[0103] The sending module is further configured to send an RRC message to the relay UE, the RRC message carrying the identifier and configuration of the first RLC or the second RLC.

[0104] In one implementation, the apparatus further includes:

[0105] The sending module is also used to send the correspondence between the first RLC identifier and the first reason to the relay UE.

[0106] In one implementation, the apparatus further includes:

[0107] The receiving module is used to receive any of the following information sent by the network device:

[0108] The first RLC identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0109] In one implementation, the first reason is any of the following:

[0110] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0111] Sixthly, embodiments of this disclosure provide a connection establishment apparatus, the apparatus being executed by a network device, the apparatus comprising:

[0112] The sending module is used to send indication information to the remote terminal device (UE) to indicate the reason why the relay UE establishes a connection with the base station.

[0113] In one implementation, the sending module is further configured to send the indication information determined when adding an indirect path to the remote UE.

[0114] In one implementation, the apparatus further includes:

[0115] The sending module is also configured to send any of the following information to the remote UE:

[0116] The first Radio Link Control (RLC) identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0117] In a seventh aspect, embodiments of this disclosure provide a computer-readable storage medium for storing instructions for a means of establishing the connection, which, when executed, cause the means of establishing the connection to perform the methods described in the first, second, or third aspects.

[0118] In a sixth aspect, embodiments of this disclosure also provide a computer program product including a computer program, which, when run on a computer, causes the computer to perform the methods described in the first or second aspect above.

[0119] In a seventh aspect, embodiments of this disclosure provide a chip system including at least one processor and an interface for supporting a communication device in implementing the functions involved in the first or second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the communication device. The chip system may be composed of chips or may include chips and other discrete devices.

[0120] Eighthly, embodiments of this disclosure also provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first or second aspect above.

[0121] This disclosure provides a method and apparatus for establishing a connection. A relay UE receives an indication message from a remote UE and sets a reason based on the indication message. The reason includes at least one of the following: the reason for the relay UE to establish a connection with a base station, or the reason for the relay UE to restore the connection with the base station. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failure. Attached Figure Description

[0122] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0123] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure;

[0124] Figure 2 A flowchart illustrating a connection establishment method provided in an embodiment of this disclosure;

[0125] Figure 3 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0126] Figure 4 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0127] Figure 5 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0128] Figure 6 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0129] Figure 7 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0130] Figure 8 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0131] Figure 9 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0132] Figure 10A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0133] Figure 11 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0134] Figure 12 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0135] Figure 13 A flowchart illustrating another connection establishment method provided in this embodiment of the disclosure;

[0136] Figure 14 A schematic diagram of a connection establishment device provided in an embodiment of this disclosure;

[0137] Figure 15 A schematic diagram of another connection establishment device provided in an embodiment of this disclosure;

[0138] Figure 16 A schematic diagram of another connection establishment device provided in an embodiment of this disclosure;

[0139] Figure 17 A schematic diagram of another connection establishment device provided in an embodiment of this disclosure;

[0140] Figure 18 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure;

[0141] Figure 19 This is a schematic diagram of the chip structure provided in an embodiment of this disclosure. Detailed Implementation

[0142] To better understand the connection establishment method disclosed in this embodiment, the communication system to which this embodiment applies is first described below.

[0143] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown is exemplified by a network device 11, a relay terminal device 12, and a remote terminal device 13.

[0144] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, long term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0145] The network device 11 in this disclosure is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the network device. The network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0146] In this disclosure, the relay terminal device 12 or remote terminal device 13 is a user-side entity used to receive or transmit signals, such as a mobile phone. Terminal devices can also be called terminal equipment, user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. Terminal devices can be communication-enabled vehicles, smart cars, mobile phones, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, etc. This disclosure does not limit the specific technology or device form used in the terminal devices.

[0147] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0148] In related technologies, in order to support direct communication between UEs, a sidelink communication method is introduced. A UE can communicate with the base station without directly connecting to it, but through another UE as a relay. The UE that is not connected to the base station is called the remote UE, and the UE that provides relay function is called the relay UE. The remote UE and the relay UE communicate through sidelink unicast. The relay UE in idle or inactive state has no Radio Resource Control (RRC) connection with the base station, while the relay UE in connected state has an RRC connection with the base station.

[0149] A relay UE in an idle or inactive state can establish an RRC connection through the connection establishment process, thereby entering the connected state. The relay UE needs to send an RRC establishment request message to the base station, which must carry the reason for establishing the connection. Therefore, how to set the establishment reason or the recovery reason is an urgent problem to be solved.

[0150] Please see Figure 2 , Figure 2 This is a flowchart illustrating a connection establishment method provided in an embodiment of the present disclosure, which is applied to a relay UE. Figure 2 As shown, the method may include, but is not limited to, the following steps:

[0151] Step S201: Receive indication information sent by the remote UE.

[0152] To improve transmission rate and reliability, remote UEs can maintain a connection with the network simultaneously through both direct and indirect paths. This feature is called multipath (MP) connection, and the remote UE can only support multipath connection when it is in a connected state.

[0153] The bearer of a remote UE can be transmitted through a direct path only, called a direct bearer; it can be transmitted through an indirect path only, called an indirect bearer; or it can be transmitted through both direct and indirect paths simultaneously, called a multipath bearer.

[0154] When adding an indirect path for a remote UE, the relay UE providing the indirect path can be in any RRC state, including connected, idle, or inactive. In order to provide data forwarding to the remote UE, the relay UE in the idle or inactive state needs to enter the connected state.

[0155] When a relay UE receives an indication message from a remote UE, in some embodiments, the relay UE triggers a connection establishment process when it is in an idle state; in other embodiments, the relay UE triggers a connection recovery process when it is in an inactive state.

[0156] Step S202: Set a reason according to the indication information. The reason includes at least one of the following: the reason for the relay UE to establish a connection with the base station, and the reason for the relay UE to restore the connection with the base station.

[0157] The reason for establishing a connection between the relay UE and the base station is set according to the current state of the relay UE (inactive or idle state).

[0158] In some embodiments, when the relay UE is in an idle state, a connection establishment process is triggered, and the reason for establishing the connection is set; that is, in response to the relay UE being in an idle state, the reason for the relay UE to establish a Radio Resource Control (RRC) connection with the base station is the reason for the connection establishment between the relay UE and the base station.

[0159] In some embodiments, when the relay UE is in an inactive state, a connection recovery process is triggered, and a connection recovery reason is set; in response to the relay UE being in an inactive state, the reason for the relay UE establishing an RRC connection with the base station is the reason for the relay UE to recover the connection with the base station.

[0160] The relay UE receives the indication information sent by the remote UE and sets the reason for establishing a connection with the base station according to the indication information. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0161] Please see Figure 3 , Figure 3 This is a flowchart illustrating a connection establishment method provided in an embodiment of this disclosure, the method being executed by a remote terminal device (UE). Figure 3 As shown, the method may include, but is not limited to, the following steps:

[0162] Step S301: The remote UE sends an indication message to the relay UE to indicate the reason why the relay UE established a connection with the base station.

[0163] When a remote UE needs to connect, it sends an indication message to the relay UE, indicating the reason for the relay UE to establish a connection with the base station, triggering either the connection restoration process or the connection establishment process of the relay UE. This allows the relay UE to complete the setting of the connection reason based on the received indication message.

[0164] When a remote UE has a connection requirement, it sends an indication message to the relay UE. The relay UE then sets the reason for establishing a connection with the base station based on the indication message sent by the remote UE. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0165] This disclosure provides another method for establishing a connection. Figure 4 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 4 As shown, the method for establishing this connection may include the following steps:

[0166] Step S401: The remote UE sends a direct sidelink radio resource control (RRC) message to the relay UE, the sidelink RRC message carrying the indication information.

[0167] When a remote UE needs to perform data forwarding, it sends a direct sidelink RRC message to the relay UE, the sidelink RRC message carrying the indication information. In practical applications, the method of sending the indication information is not limited to the sidelink RRC message; it can also send a sidelink relay adaptation protocol (SRAP) data unit (PDU). Specific embodiments of this disclosure are not limited to this.

[0168] Step S402: The relay UE receives the direct sidelink RRC message sent by the remote UE.

[0169] When a relay UE receives a direct sidelink RRC message from a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0170] Step S403: The relay UE sets the reason for establishing an RRC connection between the relay UE and the base station to the reason indicated by the indication information.

[0171] After the relay UE obtains the sidelink RRC message based on step 402, it parses the indication information carried by the message and sets the reason for establishing an RRC connection with the base station to the reason indicated by the indication information, that is, the reason for the connection is set to be the same as the indication information.

[0172] The remote UE sends a direct sidelink RRC message to the relay UE. The relay UE receives the direct sidelink RRC message sent by the remote UE and sets the reason for the relay UE to establish an RRC connection with the base station as the reason indicated by the indication information. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0173] This disclosure provides another method for establishing a connection. Figure 5 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 5 As shown, the method for establishing this connection may include the following steps:

[0174] Step S501: Remote UE sets instruction information.

[0175] The setting indication information includes at least one of the following: setting the indication information according to the service type that triggered the connection establishment; setting the indication information by receiving the indication information sent by the network device.

[0176] In some embodiments, the remote UE may set the indication information in, but is not limited to, the following two methods: Method 1: The remote UE determines the indication information based on the type of service transmitted on the indirect link; Method 2: When the base station adds an indirect path, it indicates the reason, and the remote UE determines the indication information based on the indication from the network device (such as the base station). No specific limitations are imposed.

[0177] In step S502, the remote UE sends a direct sidelink RRC message to the relay UE, and the sidelink RRC message carries the indication information.

[0178] When a remote UE needs to perform data forwarding, it sends a direct sidelink RRC message to the relay UE, the sidelink RRC message carrying the indication information. In practical applications, the method of sending the indication information is not limited to the sidelink RRC message; it can also be sent via a sidelink SRAP PDU. Specific embodiments of this disclosure are not limited to this method.

[0179] Step S503: The relay UE receives the direct sidelink RRC message sent by the remote UE.

[0180] When a relay UE receives a direct sidelink RRC message from a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0181] Step S504: The relay UE sets the reason for establishing an RRC connection between the relay UE and the base station to the reason indicated by the indication information.

[0182] After the relay UE obtains the sidelink RRC message based on step 502, it parses the indication information carried by the message and sets the reason for establishing an RRC connection with the base station to the reason indicated by the indication information, that is, it sets the reason for the connection to be the same as the indication information.

[0183] The remote UE sets indication information, which includes at least one of the following: setting the indication information according to the service type that triggered the connection establishment; setting the indication information by receiving the indication information sent by the network device, and sending a sidelink RRC message carrying the indication information to the relay UE; the relay UE receiving the direct sidelink RRC message sent by the remote UE and setting the reason for the relay UE to establish an RRC connection with the base station as the reason indicated by the indication information, thereby enabling the relay UE to reasonably set the reason for establishing a connection or the reason for restoring a connection, and avoiding MP addition failure.

[0184] This disclosure provides another method for establishing a connection. Figure 6 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 6 As shown, the method for establishing this connection may include the following steps:

[0185] Step S601: The remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0186] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0187] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0188] In practical applications, the method of sending indication information is not limited to sending sidelink SRAP PDU messages, but can also be sent by sending direct-connect sidelink RRC messages. The specific embodiments disclosed herein are not limited.

[0189] Step S602: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0190] When a relay UE receives a direct sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0191] Step S603: The relay UE sets the reason for establishing an RRC connection with the base station according to the RLC entity corresponding to the SRAP PDU.

[0192] After obtaining the SRAP PDU based on step 602, the relay UE parses and sets the RLC entity corresponding to the SRAP PDU. The relay UE sets the reason for establishing an RRC connection with the base station based on the RLC entity.

[0193] In practical applications, there is a correspondence between SRAP PDU and RLC entity, and there is a correspondence between RLC entity and cause. Therefore, relay UE can set the cause through SRAP PDU.

[0194] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the relay UE indicates the reason for establishing an RRC connection with the base station. After receiving the sidelink SRAP PDU sent by the remote UE, the relay UE sets the reason for establishing an RRC connection with the base station according to the RLC entity corresponding to the SRAP PDU. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failure.

[0195] This disclosure provides another method for establishing a connection. Figure 7 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 7 As shown, the method for establishing this connection may include the following steps:

[0196] Step S701: The remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0197] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0198] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0199] In practical applications, the method of sending indication information is not limited to sending sidelink SRAP PDU messages, but can also be sent by sending direct-connect sidelink RRC messages. The specific embodiments disclosed herein are not limited.

[0200] Step S702: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0201] When a relay UE receives a direct sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0202] Step S703: The RLC entity is the first RLC entity, and the relay UE sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0203] After the relay UE obtains the SRAP PDU based on step 702, it parses and sets the RLC entity corresponding to the SRAP PDU as the first RLC entity, and sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0204] The first reason is any of the following: emergency call, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice call (mo-VoiceCall), user-initiated video call (mo-VideoCall), user-initiated short message (mo-SMS), priority access for multimedia services (mps-PriorityAccess), and priority access for dedicated services (mcs-PriorityAccess).

[0205] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the relay UE indicates the reason for establishing an RRC connection with the base station. Upon receiving the sidelink SRAP PDU from the remote UE, and setting the RLC entity as the first RLC entity, the relay UE sets the first reason as the reason for establishing an RRC connection with the base station. This allows the relay UE to reasonably set the reason for establishing or resuming the connection, avoiding MP addition failures.

[0206] This disclosure provides another method for establishing a connection. Figure 8A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 8 As shown, the method for establishing this connection may include the following steps:

[0207] Step S801: The remote UE sends an RRC message to the relay UE. The RRC message carries the identifier and configuration of the first RLC or the second RLC.

[0208] The remote UE receives any of the following information sent by the network device: first RLC identifier and configuration, second RLC identifier and configuration. There is no limit to the specific content or quantity received.

[0209] The first RLC identifier and configuration, and the second RLC identifier and configuration can be sent to the remote UE by the base station; they can be sent to the remote UE via system messages, or via RRC reconfiguration messages; or they can be predefined by the standard. This disclosure does not limit the scope of the embodiments.

[0210] In step S802, the remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0211] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0212] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0213] In this embodiment of the disclosure, there is no limitation on the transmission order of the remote UE to the relay UE, which sends the identifier of the first RLC or the second RLC and the configured RRC message and sidelink SRAP PDU.

[0214] For example, the remote UE may first send an RRC message carrying the identifier of the first RLC or the second RLC and the configuration, and then send a sidelink SRAP PDU; or, send a sidelink SRAP PDU first, and then send an RRC message carrying the identifier of the first RLC or the second RLC and the configuration; or, send an RRC message carrying the identifier of the first RLC or the second RLC and the configuration, a sidelink SRAP PDU, or other sending orders simultaneously. This disclosure does not limit the specific transmission order.

[0215] Step S803: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0216] When a relay UE receives a sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0217] Step S804: The relay UE obtains the identifier and configuration of the first RLC or the second RLC.

[0218] The relay UE receives an RRC message sent by the remote UE, the RRC message carrying the identifier and configuration of the first RLC or the second RLC.

[0219] When a relay UE obtains the identifier and configuration of the first RLC or the second RLC, it may also use the following methods, for example: obtaining the identifier and configuration of the first RLC or the second RLC according to standard specifications; or receiving system information sent by a network device, wherein the system information carries the identifier and configuration of the first RLC or the second RLC. Specifically, this disclosure does not limit the scope of the embodiments.

[0220] In this embodiment of the disclosure, there is no limitation on the order in which the relay UE receives RRC messages and the sidelink SRAP PDU.

[0221] For example, the relay UE may receive the RRC message first and then the sidelink SRAP PDU; or, receive the sidelink SRAP PDU first and then the RRC message; or, receive the RRC message and the sidelink SRAP PDU simultaneously, or other transmission order, or other reception order, which are not limited in the embodiments disclosed herein.

[0222] Step S805: The relay UE sets the reason for establishing an RRC connection with the base station according to the RLC entity corresponding to the SRAP PDU.

[0223] After the relay UE obtains the SRAP PDU based on step 805, it parses and sets the RLC entity corresponding to the SRAP PDU. The relay UE sets the reason for establishing an RRC connection with the base station based on the RLC entity.

[0224] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the remote UE indicates the reason for establishing an RRC connection between the relay UE and the base station. The remote UE then sends an RRC message to the relay UE, which carries the identifier and configuration of the first or second RLC. The relay UE receives the sidelink SRAP PDU from the remote UE, obtains the RLC entity corresponding to the SRAP PDU, and sets the reason for establishing an RRC connection between the relay UE and the base station in the RLC entity. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failures.

[0225] This disclosure provides another method for establishing a connection. Figure 9 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 9 As shown, the method for establishing this connection may include the following steps:

[0226] Step S901: The remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0227] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0228] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0229] Step S902: The remote UE sends the correspondence between the first RLC identifier and the first cause to the relay UE.

[0230] In some embodiments, the correspondence between the first RLC identifier and the first reason is sent by the base station to the remote UE; it can also be sent to the remote UE via a system message or an RRC reconfiguration message. This disclosure does not limit the scope of the embodiments.

[0231] In this embodiment of the disclosure, the transmission order of the sidelink SRAP PDU, the correspondence between the first RLC identifier and the first cause sent by the remote UE to the relay UE is not limited.

[0232] Step S903: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0233] When a relay UE receives a direct sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0234] Step S904: The relay UE obtains the correspondence between the first RLC identifier and the first reason.

[0235] The correspondence between the first RLC identifier and the first cause received by the relay UE from the remote UE.

[0236] The relay UE can also obtain the correspondence between the first RLC and the first cause by the following methods: for example, obtaining the correspondence between the first RLC identifier and the first cause configured by the network device; or obtaining the correspondence between the first RLC identifier and the first cause according to standard specifications. Specifically, this disclosure does not limit the specific methods used.

[0237] In this embodiment of the disclosure, the transmission order of the relay UE receiving the sidelink SRAP PDU, the first RLC identifier and the correspondence between the first cause are not limited.

[0238] In step S905, the RLC entity is the first RLC entity, and the relay UE sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0239] After the relay UE obtains the SRAP PDU based on step 903, it parses and sets the RLC entity corresponding to the SRAP PDU as the first RLC entity, and sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0240] The first reason is any of the following: emergency call, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice call (mo-VoiceCall), user-initiated video call (mo-VideoCall), user-initiated short message (mo-SMS), priority access for multimedia services (mps-PriorityAccess), and priority access for dedicated services (mcs-PriorityAccess).

[0241] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the relay UE indicates the reason for establishing an RRC connection with the base station. The remote UE sends the mapping relationship between a first RLC identifier and a first reason to the relay UE. The relay UE receives the sidelink SRAP PDU from the remote UE, obtains the mapping relationship between the first RLC identifier and the first reason, and sets the RLC entity as the first RLC entity. The relay UE then sets the first reason as the reason for establishing an RRC connection with the base station. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failures.

[0242] This disclosure provides another method for establishing a connection. Figure 10 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 10 As shown, the method for establishing this connection may include the following steps:

[0243] Step S1001: The remote UE sends an RRC message to the relay UE. The RRC message carries the identifier and configuration of the first RLC or the second RLC.

[0244] Step S1002: The remote UE sends the correspondence between the first RLC identifier and the first cause to the relay UE.

[0245] Step S1003: The remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0246] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0247] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0248] The correspondence between the first RLC identifier and the first cause on the remote UE side is obtained by the network device.

[0249] In this embodiment of the disclosure, the order in which the remote UE sends the RRC message, the sidelink SRAP PDU, and the correspondence between the first RLC identifier and the first cause to the relay UE is not limited.

[0250] For example, the remote UE may first send an RRC message, then send a sidelink SRAP PDU, and finally send the correspondence between the first RLC identifier and the first cause; or, send the correspondence between the first RLC identifier and the first cause first, then send an RRC message, and finally send a sidelink SRAP PDU; or, send the RRC message, the sidelink SRAP PDU, and the correspondence between the first RLC identifier and the first cause simultaneously, or other sending orders, which are not limited in the embodiments disclosed herein.

[0251] Step S1004: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0252] When a relay UE receives a direct sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0253] Step S1005: The relay UE obtains the correspondence between the first RLC identifier and the first reason.

[0254] The correspondence between the first RLC identifier and the first cause received by the relay UE from the remote UE.

[0255] The relay UE can also obtain the correspondence between the first RLC and the first cause in the following ways, for example: obtaining the correspondence between the first RLC identifier configured by the network device and the first cause; or obtaining the correspondence between the first RLC identifier and the first cause according to standard provisions. Specifically, this disclosure does not limit the specific methods.

[0256] Step S1006: The relay UE obtains the identifier and configuration of the first RLC or the second RLC.

[0257] The relay UE receives an RRC message sent by the remote UE, the RRC message carrying the identifier and configuration of the first RLC or the second RLC.

[0258] The relay UE can also obtain the identifier and configuration of the first RLC or the second RLC in the following ways, for example: obtaining the identifier and configuration of the first RLC or the second RLC according to standard specifications; or receiving system information sent by a network device, wherein the system information carries the identifier and configuration of the first RLC or the second RLC. Specifically, this disclosure does not limit the specific implementation.

[0259] As an optional embodiment of this disclosure, when neither the first RLC entity nor the second RLC entity exists, the relay UE establishes a corresponding first RLC entity or second RLC entity based on the received identifier of the first RLC or second RLC and its configuration. When either the first RLC entity or the second RLC entity exists, it is not necessary to establish a corresponding first RLC entity or second RLC entity based on the identifier of the first RLC or the second RLC and its configuration.

[0260] In this embodiment of the disclosure, the transmission order of the relay UE receiving RRC messages, sidelink SRAP PDUs, and the correspondence between the first RLC identifier and the first cause is not limited.

[0261] For example, the relay UE may first receive the RRC message, then the sidelink SRAP PDU, and finally the correspondence between the first RLC identifier and the first cause; or, first receive the correspondence between the first RLC identifier and the first cause, then receive the RRC message, and finally receive the sidelink SRAP PDU; or, simultaneously receive the RRC message, the sidelink SRAP PDU, and the correspondence between the first RLC identifier and the first cause, or other receiving orders, which are not limited in the embodiments disclosed herein.

[0262] Step S1007: The RLC entity is the first RLC entity, and the relay UE sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0263] After the relay UE obtains the SRAP PDU based on step 1004, it parses and sets the RLC entity corresponding to the SRAP PDU as the first RLC entity, and sets the first reason as the reason for the relay UE to establish an RRC connection with the base station.

[0264] The first reason is any of the following: emergency call, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice call (mo-VoiceCall), user-initiated video call (mo-VideoCall), user-initiated short message (mo-SMS), priority access for multimedia services (mps-PriorityAccess), and priority access for dedicated services (mcs-PriorityAccess).

[0265] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the relay UE indicates the reason for establishing an RRC connection with the base station. The remote UE sends the mapping relationship between a first RLC identifier and a first reason to the relay UE. The relay UE receives the sidelink SRAP PDU from the remote UE, obtains the mapping relationship between the first RLC identifier and the first reason, and sets the RLC entity as the first RLC entity. The relay UE then sets the first reason as the reason for establishing an RRC connection with the base station. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failures.

[0266] This disclosure provides another method for establishing a connection. Figure 11 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being applied to the communication process between a remote UE and a relay UE, such as... Figure 11 As shown, the method for establishing this connection may include the following steps:

[0267] Step S1101: The remote UE sends a sidelink SRAP PDU to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0268] When a remote UE needs to perform data forwarding, it sends a sidelink SRAP PDU to the relay UE, and indicates the reason for the relay UE to establish an RRC connection with the base station based on the RLC entity corresponding to the sidelink SRAP PDU.

[0269] In some embodiments, the RLC entity described in this disclosure is used for MP transmission.

[0270] In practical applications, the method of sending indication information is not limited to sending sidelink SRAP PDU messages, but can also be sent by sending direct-connect sidelink RRC messages. The specific embodiments disclosed herein are not limited.

[0271] Step S1102: The relay UE receives the sidelink SRAP PDU sent by the remote UE.

[0272] When a relay UE receives a direct sidelink SRAP PDU sent by a remote UE, the relay UE in an idle or inactive state triggers a connection recovery process or a connection establishment process.

[0273] Step S1103: The RLC entity is a second RLC entity, and the second reason is set as the reason for the relay UE to establish an RRC connection with the base station.

[0274] After the relay UE obtains the SRAP PDU based on step 1102, it parses and sets the RLC entity corresponding to the SRAP PDU as the second RLC entity, and sets the second reason as the reason for the relay UE to establish an RRC connection with the base station.

[0275] The second reason can be any of the following: user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice (mo-VoiceCall), user-initiated video call (mo-VideoCall), or user-initiated short message (mo-SMS). Compared to the first reason, the second reason cannot be set as emergency call, high-priority access, priority access for multimedia services (mps-PriorityAccess), or priority access for dedicated services (mcs-PriorityAccess).

[0276] The remote UE sends a sidelink SRAP PDU to the relay UE. Based on the RLC entity corresponding to the sidelink SRAP PDU, the relay UE indicates the reason for establishing an RRC connection with the base station. The relay UE receives the sidelink SRAP PDU from the remote UE, sets the RLC entity to the second RLC entity, and then sets the second reason as the reason for establishing an RRC connection with the base station. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, avoiding MP addition failures.

[0277] Please see Figure 12 , Figure 12 This is a flowchart illustrating a connection establishment method provided in an embodiment of this disclosure, which is executed by a network device. Figure 12 As shown, the method may include, but is not limited to, the following steps:

[0278] Step S1201: The network device sends an indication message to the remote terminal device (UE) to indicate the reason why the relay UE establishes a connection with the base station.

[0279] When a remote UE needs to connect, the network device sends an indication message to the remote UE, indicating the reason for the relay UE to establish a connection with the base station, triggering either the connection restoration process or the connection establishment process of the relay UE. This allows the relay UE to complete the setting of the connection reason based on the received indication message.

[0280] When a remote UE has a connection requirement, the network device sends an indication message to the remote terminal device UE. The remote UE then sends the indication message to the relay UE. The relay UE sets the reason for establishing a connection with the base station based on the indication message from the network device. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0281] This disclosure provides another method for establishing a connection. Figure 13 A flowchart illustrating another connection establishment method provided in this disclosure embodiment, the method being executed by a network device, such as... Figure 13 As shown, the method for establishing this connection may include the following steps:

[0282] Step S1301: The network device sends the indication information set when adding an indirect path to the remote UE.

[0283] In some embodiments, the network device sends any of the following information to the remote UE: a first radio link control layer (RLC) identifier and configuration, a second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0284] When a remote UE has a connection requirement, the network device sends the indication information set when adding an indirect path to the remote UE. The remote UE then sends the indication information to the relay UE, which sets the reason for establishing a connection with the base station according to the indication information from the network device. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0285] With the above Figures 2 to 13 Corresponding to the connection establishment method provided in the embodiments, this disclosure also provides a packet loss processing device. Since the connection establishment device provided in the embodiments of this disclosure is similar to the one described above... Figures 2 to 13 The connection establishment method provided in the embodiments corresponds to the connection establishment apparatus provided in the embodiments of this disclosure, and will not be described in detail in the embodiments of this disclosure.

[0286] Figure 14 This is a schematic diagram of a connection establishment device provided in an embodiment of the present disclosure. The device is installed in a relay terminal device (UE), such as... Figure 14 As shown, the device includes:

[0287] The receiving module 141 is used to receive indication information sent by the remote UE;

[0288] Processing module 142 is configured to set a reason according to the indication information, the reason including at least one of the following: the reason for the relay UE to establish a connection with the base station, the reason for the relay UE to restore the connection with the base station.

[0289] The relay UE receives the indication information sent by the remote UE and sets the reason for establishing a connection with the base station according to the indication information. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0290] In one implementation, the reasons include:

[0291] The reason for the relay UE to establish a Radio Resource Control (RRC) connection with the base station in response to the relay UE being in an idle state is the reason for the relay UE to establish a connection with the base station;

[0292] The reason why the relay UE establishes an RRC connection with the base station in response to the relay UE being in an inactive state is the reason why the relay UE resumes its connection with the base station.

[0293] In one implementation, such as Figure 15 As shown, the receiving module 141 is further configured to receive a direct sidelink RRC message sent by the remote UE, wherein the sidelink RRC message carries the indication information;

[0294] The processing module 142 is further configured to set the reason for the relay UE to establish an RRC connection with the base station as the reason indicated by the indication information.

[0295] In one implementation, such as Figure 15 As shown, the receiving module 141 is also used to receive the sidelink relay adaptation protocol data unit (PDU) sent by the remote UE.

[0296] The processing module 142 is also used to set the reason for the relay UE to establish an RRC connection with the base station according to the Radio Link Control (RLC) entity corresponding to the SRAP PDU.

[0297] In one implementation, such as Figure 15 As shown, the processing module 142 is further configured to set the first reason as the reason for the relay UE to establish an RRC connection with the base station when the RLC entity is the first RLC entity.

[0298] In one implementation, the first reason is any of the following:

[0299] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0300] In one implementation, such as Figure 15 As shown, the device further includes:

[0301] The first acquisition module 143 is used to acquire the correspondence between the first RLC identifier and the first reason.

[0302] In one implementation, the first acquisition module 143 is further configured to:

[0303] Obtain the correspondence between the first RLC identifier configured in the network device and the first reason;

[0304] Alternatively, receive the correspondence between the first RLC identifier and the first reason sent by the remote UE;

[0305] Alternatively, the correspondence between the first RLC identifier and the first reason can be obtained according to the standard specifications.

[0306] In one implementation, the processing module 142 is further configured to set the second reason as the reason for the relay UE to establish an RRC connection with the base station, since the RLC entity is a second RLC entity.

[0307] In one implementation, the second reason is any of the following:

[0308] User-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice (mo-VoiceCall), user-initiated video call (mo-VideoCall), and user-initiated short message (mo-SMS).

[0309] In one implementation, such as Figure 15 As shown, the device further includes:

[0310] The second acquisition module 144 is used to acquire the identifier and configuration of the first RLC or the second RLC.

[0311] In one implementation, the second acquisition module is further configured to:

[0312] Obtain the identification and configuration of the first or second RLC in accordance with the standard specifications;

[0313] Alternatively, it may receive system information sent by a network device, the system information carrying the identifier and configuration of the first or second RLC.

[0314] Alternatively, it may receive an RRC message sent by a remote UE, the RRC message carrying the identifier and configuration of the first or second RLC.

[0315] In one implementation, such as Figure 15 As shown, the device further includes:

[0316] The module 145 is used to establish a corresponding first RLC entity or second RLC entity based on the identifier and configuration of the first RLC or second RLC.

[0317] Figure 16 This is a schematic diagram of another connection establishment apparatus provided in an embodiment of this disclosure. This disclosure provides a connection establishment apparatus disposed in a remote terminal device (UE), the apparatus comprising:

[0318] The sending module 161 is used to send indication information to the relay UE to indicate the reason for the relay UE to establish a connection with the base station.

[0319] In one implementation, the sending module 161 is further configured to send a direct sidelink radio resource control (RRC) message to the relay UE, wherein the sidelink RRC message carries the indication information.

[0320] When a remote UE has a connection requirement, it sends an indication message to the relay UE. The relay UE then sets the reason for establishing a connection with the base station based on the indication message sent by the remote UE. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0321] In one implementation, the apparatus further includes:

[0322] Processing module 162 is used to set indication information, wherein the setting indication information includes at least one of the following:

[0323] The indication information is set according to the service type that triggers the connection establishment; the indication information is set by receiving the indication information sent by the network device.

[0324] In one implementation, the sending module 161 is further configured to send a sidelink relay adaptation protocol SRAP data unit (PDU) to the relay UE, indicating the reason for the relay UE to establish an RRC connection with the base station based on the Radio Link Control (RLC) entity corresponding to the sidelink SRAP PDU.

[0325] In one implementation, the apparatus further includes:

[0326] The sending module 161 is further configured to send an RRC message to the relay UE, the RRC message carrying the identifier and configuration of the first RLC or the second RLC.

[0327] In one implementation, the apparatus further includes:

[0328] The sending module 161 is also used to send the correspondence between the first RLC identifier and the first reason to the relay UE.

[0329] In one implementation, the apparatus further includes:

[0330] The receiving module 163 is used to receive any of the following information sent by the network device:

[0331] The first RLC identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0332] In one implementation, the first reason is any of the following:

[0333] Emergency calls, high-priority access, user-terminated access (mt-Access), user-initiated signaling (mo-Signalling), user-initiated data (mo-Data), user-initiated voice calls (mo-VoiceCall), user-initiated video calls (mo-VideoCall), user-initiated short messages (mo-SMS), priority multimedia services (mps-PriorityAccess), and dedicated services (mcs-PriorityAccess).

[0334] Figure 17 This is a schematic diagram of another connection establishment apparatus provided in an embodiment of the present disclosure. The present disclosure provides a connection establishment apparatus executed by a network device, the apparatus comprising:

[0335] The sending module 171 is used to send indication information to the remote terminal device (UE) to indicate the reason for the relay UE to establish a connection with the base station.

[0336] When a remote UE has a connection requirement, the network device sends an indication message to the remote terminal device UE. The remote UE then sends the indication message to the relay UE. The relay UE sets the reason for establishing a connection with the base station based on the indication message from the network device. This allows the relay UE to reasonably set the reason for establishing or restoring the connection, thus avoiding MP addition failure.

[0337] In one implementation, the sending module 171 is further configured to send the indication information set when adding an indirect path to the remote UE.

[0338] In one implementation, the apparatus further includes:

[0339] The transmitting module 171 is further configured to transmit any of the following information to the remote UE:

[0340] The first Radio Link Control (RLC) identifier and configuration, the second RLC identifier and configuration, and the correspondence between the first RLC identifier and the first cause.

[0341] Please see Figure 18 , Figure 18 This is a schematic diagram of another communication device provided in an embodiment of the present disclosure. Figure 18 In this context, the communication device 1800 can be a network device, a terminal device, a chip, chip system, or processor that supports the implementation of the above methods in a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a terminal device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0342] The communication device 1800 may include one or more processors 1801. The processor 1801 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0343] Optionally, the communication device 1800 may further include one or more memories 1802, on which a computer program 1804 may be stored. The processor 1801 executes the computer program 1804 to cause the communication device 1800 to perform the methods described in the above method embodiments. Optionally, the memory 1802 may also store data. The communication device 1800 and the memory 1802 may be provided separately or integrated together.

[0344] Optionally, the communication device 1800 may also include a transceiver 1805 and an antenna 1806. The transceiver 1805 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1805 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0345] Optionally, the communication device 1800 may further include one or more interface circuits 1807. The interface circuits 1807 are used to receive code instructions and transmit them to the processor 1801. The processor 1801 executes the code instructions to cause the communication device 1800 to perform the methods described in the above method embodiments.

[0346] Communication device 1800 is a relay UE: transceiver 1805 is used to perform Figure 2 Step 201 and other steps in the process.

[0347] Communication device 1800 is a remote UE: transceiver 1805 is used for execution Figure 4 Step 401 and other steps in the process;

[0348] Communication device 1800 is a network device: transceiver 1805 is used for execution Figure 12 Steps 1201, etc.

[0349] In one implementation, the processor 1801 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0350] In one implementation, processor 1801 may store computer program 1803, which runs on processor 1801 and causes communication device 1800 to perform the methods described in the above method embodiments. Computer program 1803 may be embedded in processor 1801, in which case processor 1801 may be implemented in hardware.

[0351] In one implementation, the communication device 1800 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0352] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 18 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0353] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0354] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0355] (3) ASIC, such as modem;

[0356] (4) Modules that can be embedded in other devices;

[0357] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0358] (6) Others, etc.

[0359] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 19 The diagram shows the structure of the chip. Figure 19 The chip 1900 shown includes a processor 1901 and an interface 1903. The number of processors 1901 can be one or more, and the number of interfaces 1903 can be multiple.

[0360] For cases where the chip is used to implement the function of relaying the UE in the embodiments of this disclosure:

[0361] Interface 1903 is used for execution. Figure 2 Step 201 in the middle; Figure 4 Step 402, etc.

[0362] For cases where the chip is used to implement the functions of the remote UE in the embodiments of this disclosure:

[0363] Interface 1903 is used for execution. Figure 3 Step 301 in the middle, Figure 4 Step 401, etc.

[0364] Optionally, chip 1900 may also include memory 1902, which is used to store necessary computer programs and data.

[0365] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0366] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0367] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0368] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0369] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0370] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0371] It can be further understood that in this disclosure, "multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. The singular forms "a," "the," and "the" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0372] It is further understood that the meaning of words such as “in response to,” “if,” and “suppose” used in this disclosure depends on the context and the actual situation in which they are used. For example, the word “suppose” as used herein can be interpreted as “when” or “when…”.

[0373] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

Claims

1. A method of connection establishment, characterized by The method is performed by a relay terminal device UE, and the method comprises: receiving indication information sent by a remote UE, comprising: receiving a sidelink relay adaptation protocol SRAP data unit PDU sent by the remote UE, the indication information being set according to a service type triggering connection establishment; setting a cause according to the indication information, comprising: setting a cause of the relay UE establishing a radio resource control RRC connection with a base station according to a radio link control layer RLC entity corresponding to the SRAP PDU, the RLC entity and the cause having a corresponding relationship, the cause comprising at least one of the following: a cause of the relay UE establishing a connection with the base station, a cause of the relay UE resuming a connection with the base station.

2. The method of claim 1, wherein, The cause comprises: in response to the relay UE being in an idle state, the cause of the relay UE establishing a RRC connection with the base station being a cause of the relay UE establishing a connection with the base station; in response to the relay UE being in an inactive state, the cause of the relay UE establishing a RRC connection with the base station being a cause of the relay UE resuming a connection with the base station.

3. The method of claim 2, wherein: the receiving indication information sent by a remote UE further comprises: receiving a sidelink RRC message sent by the remote UE, the sidelink RRC message carrying the indication information; and wherein the setting a cause according to the indication information further comprises: setting a cause of the relay UE establishing a RRC connection with the base station to a cause indicated by the indication information.

4. The method of claim 1, wherein, The setting a cause of the relay UE establishing a RRC connection with the base station according to an RLC entity corresponding to the SRAP PDU comprises: the RLC entity is a first RLC entity, and a first cause is set as the cause of the relay UE establishing a RRC connection with the base station.

5. The method of claim 4, wherein, The first cause is any one of the following: emergency call, high priority access, user-terminated access, user-initiated signaling, user-initiated data, user-initiated voice call, user-initiated video call, user-initiated short message, multimedia service priority access with priority, dedicated service priority access.

6. The method of claim 5, wherein, The method further comprises: obtaining a corresponding relationship between the first RLC identifier and the first cause.

7. The method of claim 6, wherein, The obtaining a corresponding relationship between the first RLC and the first cause comprises: obtaining a corresponding relationship between the first RLC identifier and the first cause configured by a network device; or receiving a corresponding relationship between the first RLC identifier and the first cause sent by the remote UE; or obtaining a corresponding relationship between the first RLC identifier and the first cause according to a standard specification.

8. The method of claim 1, wherein, The reason for the relay UE to establish an RRC connection with the base station is set according to an RLC entity corresponding to an SRAP PDU. The second reason is set as the reason for the relay UE to establish an RRC connection with the base station.

9. The method of claim 8, wherein, The second reason is any one of the following: User terminated access mt-Access, user initiated signaling mo-Signalling, user initiated data mo-Data, user initiated voice mo-VoiceCall, user initiated video call mo-VideoCall, user initiated short message mo-SMS.

10. The method according to any one of claims 4-9, characterized in that, The method further comprises: Obtaining the identity and configuration of the first RLC or the second RLC.

11. The method of claim 10, wherein, The method further comprises: Obtaining the identity and configuration of the first RLC or the second RLC according to the standard; Or receiving system information sent by a network device, the system information carrying the identity and configuration of the first RLC or the second RLC; Or receiving an RRC message sent by a remote UE, the RRC message carrying the identity and configuration of the first RLC or the second RLC.

12. The method of claim 10, wherein, The method further comprises: Establishing a corresponding first RLC entity or second RLC entity according to the identity and configuration of the first RLC or the second RLC.

13. A method of connection establishment, characterized by The method is performed by a remote terminal device UE, and the method comprises: Sending indication information to the relay UE to indicate the reason for the relay UE to establish a connection with the base station, the indication information being set according to the type of service triggering connection establishment; The indication information is sent to the relay UE, including: sending a sidelink SRAP PDU to the relay UE, and indicating the reason for the relay UE to establish an RRC connection with the base station based on the sidelink SRAP PDU corresponding RLC entity, the RLC entity and the reason have a corresponding relationship, the reason includes at least one of the following: the reason for the relay UE to establish a connection with the base station, the reason for the relay UE to resume a connection with the base station.

14. The method of claim 13, wherein, The indication information is sent to the relay UE, including: The indication information is sent to the relay UE in a sidelink RRC message.

15. The method of claim 14, wherein, The method further comprises: Setting indication information, wherein the setting indication information includes at least one of the following: Setting the indication information according to the type of service triggering connection establishment; Setting the indication information by receiving the indication information sent by a network device.

16. The method of claim 13, wherein, The method further comprises: Sending an RRC message to the relay UE, the RRC message carrying the identity and configuration of the first RLC or the second RLC.

17. The method of claim 16, wherein, The method further comprises: Sending the first RLC identity and the first reason to the relay UE.

18. The method of claim 16 or 17, wherein, The method further comprises: Receiving any one of the following information sent by a network device: The first RLC identity and configuration, the second RLC identity and configuration, and the correspondence between the first RLC identity and the first cause.

19. The method of claim 17, wherein, The first cause is any one of the following: emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess.

20. A method of connection establishment, characterized by The method is performed by a network device, and the method comprises: sending, to a remote terminal device UE, indication information indicating a cause for the relay UE to establish a connection with a base station, the indication information being set according to a service type triggering the connection establishment, The indication information is used by the remote UE to send to the relay UE, so that the relay UE sets a cause for the relay UE to establish an RRC connection with the base station according to an RLC entity corresponding to the SRAP PDU, the RLC entity and the cause have a correspondence relationship, and the cause includes at least one of the following: a cause for the relay UE to establish a connection with the base station, and a cause for the relay UE to resume a connection with the base station.

21. The method of claim 20, wherein, The indication information sent to the remote UE includes: The indication information set when the indirect path is added is sent to the remote UE.

22. The method of claim 21, wherein, The method further comprises: At least one of the following is sent to the remote UE: The first RLC identity and configuration, the second RLC identity and configuration, and the correspondence between the first RLC identity and the first cause.

23. An apparatus for connection establishment, characterized by The device is arranged in a relay terminal device UE, and the device comprises: A receiving module for receiving indication information sent by a remote UE, comprising: receiving a sidelink relay adaptation protocol SRAP data unit PDU sent by the remote UE, the indication information being set according to a service type triggering the connection establishment; A processing module for setting a cause according to the indication information, comprising: setting a cause for the relay UE to establish an RRC connection with a base station according to an RLC entity corresponding to the SRAP PDU, the RLC entity and the cause having a correspondence relationship, and the cause including at least one of the following: a cause for the relay UE to establish a connection with the base station, and a cause for the relay UE to resume a connection with the base station.

24. An apparatus for connection establishment, characterized by The device is arranged in a remote terminal device UE, and the device comprises: A sending module for sending, to a relay UE, indication information indicating a cause for the relay UE to establish a connection with a base station, the indication information being set according to a service type triggering the connection establishment; The indication information is used by the remote UE to send to the relay UE, so that the relay UE sets a cause for the relay UE to establish an RRC connection with the base station according to an RLC entity corresponding to the SRAP PDU, the RLC entity and the cause have a correspondence relationship, and the cause includes at least one of the following: a cause for the relay UE to establish a connection with the base station, and a cause for the relay UE to resume a connection with the base station. The sending module is further configured to send a sidelink relay adaptation protocol (SRAP) protocol data unit (PDU) to the relay UE, and indicate a cause of the relay UE establishing a radio resource control (RRC) connection with a base station based on a radio link control (RLC) entity corresponding to the sidelink SRAP PDU, the RLC entity having a corresponding relationship with the cause, the cause including at least one of a cause of the relay UE establishing a connection with the base station or a cause of the relay UE resuming a connection with the base station.

25. An apparatus for connection establishment, the apparatus comprising: The apparatus is executed by a network device, and the apparatus includes: A sending module configured to send indication information to a remote terminal device (UE) to indicate a cause of a relay UE establishing a connection with a base station, the indication information being set according to a service type triggering connection establishment, The indication information is used by the remote UE to send to the relay UE, so that the relay UE sets the cause of the relay UE establishing a RRC connection with the base station according to a radio link control (RLC) entity corresponding to a sidelink relay adaptation protocol (SRAP) PDU, the RLC entity having a corresponding relationship with the cause, the cause including at least one of a cause of the relay UE establishing a connection with the base station or a cause of the relay UE resuming a connection with the base station.

26. A communications device, characterized by The apparatus includes a processor and a memory, and the memory stores a computer program, and the processor executes the computer program stored in the memory to enable the apparatus to perform the method of any one of claims 1 to 12, or perform the method of any one of claims 13 to 19, or perform the method of any one of claims 20 to 22.

27. A computer-readable storage medium storing instructions that, when executed, perform the method of any one of claims 1 to 12, or perform the method of any one of claims 13 to 19, or perform the method of any one of claims 20 to 22.

Images