RRC connection method, device and readable storage medium

Abstract

An embodiment of the present application provides an RRC connection method, i.e., a device, and belongs to the field of communication technologies. The method includes: when a relay UE is in RRC_IDLE or RRC_INACTIVE mode, the relay UE determines whether a first condition is satisfied; when the relay UE satisfies the first condition, the relay UE triggers an RRC connection establishment or RRC connection recovery process; wherein the first condition includes one or more of the following: the relay UE determines to provide a relay service for one or more remote terminals (Remote UEs); the relay UE receives one or more first messages from one or more Remote UEs, each first message carrying a first cause value (cause value) indicating that each Remote UE requests RRC connection recovery or RRC connection establishment.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and specifically to an RRC connection method, device, and readable storage medium. Background Art

[0002] In the Radio Resource Control (RRC) connection establishment process in the Sidelink Relay (SL Relay) scenario, if the relay terminal (also known as the relay user equipment, Relay UE) has not yet entered the Radio Resource Control Connected state (RRC_CONNECTED) when receiving a message from the remote terminal (also known as the remote user equipment, Remote UE), it must first trigger the establishment of its own RRC connection over the Uu air interface before providing relay services to the Remote UE. The specific details of the RRC connection establishment and RRC connection recovery process initiated by the Relay UE have not yet been determined. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide an RRC connection method and device, which solves the problem that the current network is unable to reasonably control and accept the access request of the Relay UE.

[0004] In a first aspect, an embodiment of the present application provides an RRC connection method, the method comprising:

[0005] When the relay terminal Relay UE is in a radio resource control idle state RRC_IDLE or a radio resource control inactive state RRC_INACTIVE, the Relay UE determines whether a first condition is met;

[0006] When the Relay UE meets the first condition, the Relay UE triggers an RRC connection establishment or RRC connection recovery process;

[0007] The first condition includes one or more of the following:

[0008] The Relay UE determines to provide a relay service for one or more remote terminals Remote UE;

[0009] The Relay UE receives one or more first messages from one or more Remote UEs, where each of the first messages carries a first cause value for each of the Remote UEs to request RRC connection recovery or RRC connection establishment.

[0010] In a second aspect, an embodiment of the present application provides an RRC connection device, the device comprising:

[0011] A first determining module, configured to, when the Relay UE is in RRC_IDLE or RRC_INACTIVE, determine, by the Relay UE, whether a first condition is satisfied;

[0012] A triggering module, configured to trigger, when the Relay UE meets a first condition, the Relay UE to trigger an RRC connection establishment or RRC connection recovery process;

[0013] The first condition includes one or more of the following:

[0014] The Relay UE determines to provide a relay service for one or more Remote UEs;

[0015] The Relay UE receives one or more first messages from one or more Remote UEs, where each of the first messages carries a first cause value for each of the Remote UEs to request RRC connection recovery or RRC connection establishment.

[0016] In a third aspect, an embodiment of the present application provides a SL UE, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the RRC connection method described in the first aspect.

[0017] In a fourth aspect, an embodiment of the present application provides a readable storage medium, characterized in that a program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the RRC connection method described in the first aspect are implemented.

[0018] In a fifth aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0019] In a sixth aspect, an embodiment of the present application further provides a computer program product, which is stored in a non-volatile storage medium and is configured to be executed by at least one processor to implement the steps of the method described above.

[0020] In a seventh aspect, an embodiment of the present application further provides an execution device, which is configured to execute the method described above.

[0021] In the embodiment of the present application, when the Relay UE in RRC_IDLE or RRC_INACTIVE meets the above-mentioned first condition, the RRC connection establishment or RRC connection recovery process is triggered, and the RRC connection establishment (for RRC_IDLE) or RRC connection recovery (for RRC_INACTIVE) process initiated by the Relay UE is determined to ensure that the network reasonably controls and accepts the access request of the Relay UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1a This is a schematic diagram of the existing relay network structure;

[0023] Figure 1b Schematic diagram of the RRC connection establishment process;

[0024] Figure 2 A schematic diagram of the RRC connection method flow provided in an embodiment of the present application;

[0025] Figure 3a This is one of the application scenario diagrams provided in the embodiment of the present application;

[0026] Figure 3b The second schematic diagram of the application scenario provided in the embodiment of the present application;

[0027] Figure 4 A schematic diagram of the structure of the RRC connection device provided in an embodiment of the present application;

[0028] Figure 5 This is one of the schematic diagrams of the Relay UE structure provided in an embodiment of the present application;

[0029] Figure 6 This is the second structural diagram of the Relay UE provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first," "second," and the like are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0032] To better understand the solutions of the embodiments of the present application, the following contents are first introduced:

[0033] 1. Sidelink Relay Mechanism

[0034] Relay technology in wireless communication systems adds one or more relay nodes between the base station and the terminal, which is responsible for forwarding the wireless signal once or multiple times. That is, the wireless signal has to go through multiple hops before reaching the terminal.

[0035] Wireless relay technology not only expands cell coverage and fills blind spots, but also increases cell capacity through spatial resource reuse. For indoor coverage, relay technology can also overcome penetration loss and improve indoor coverage quality.

[0036] Taking a simple two-hop relay as an example, wireless relay splits a base station-terminal link into two links: base station-relay station and relay station-terminal. This allows one poor-quality link to be replaced with two high-quality links, achieving higher link capacity and better coverage.

[0037] Currently, the relay supported in LTE is a UE-to-network relay, where one end of the relay is connected to the UE and the other end is connected to the network. The user equipment (UE) connected to the relay is called the remote UE, also known as the remote terminal.

[0038] NR will also study how to support the UE-to-Network Relay mechanism, typical scenarios such as Figure 1aThis is a typical UE-to-network scenario. A remote UE needs to transmit data to the network, but due to poor coverage, it uses a relay terminal (also known as relay user equipment, or Relay UE) to relay the data. The Uu interface connects the Relay UE to the base station, and the Sidelink (PC5) interface connects the Relay UE to the remote UE. Generally speaking, the Relay UE is open and can serve any remote UE.

[0039] 2. RRC connection establishment process in Sidelink Relay scenario, see Figure 1b :

[0040] Step 1. The Remote UE and the Relay UE perform a discovery procedure and then establish a PC5 RRC connection.

[0041] Step 2. The Remote UE sends an RRCSetupRequest message to the base station, and the base station replies with an RRCSetup message. Specifically, these two messages are relayed by the Relay UE to the base station or the Remote UE. If the Relay UE has not yet entered the RRC_CONNECTED state when it receives the message from the Remote UE, it must first trigger the establishment of its own RRC connection over the Uu air interface before it can provide relay services to the Remote UE.

[0042] Step 3. A dedicated Signaling Radio Bearer (SRB) 1 bearer is established between the base station and the Remote UE. This dedicated Remote UE SRB1 bearer consists of two Radio Link Control (RLC) channels: PC5 (between the Remote UE and the Relay UE) and Uu (between the Relay UE and the base station). Specifically, these two RLC channels are used for the Remote UE to send and receive SRB1-type RRC messages with the base station.

[0043] Step 4. The Remote UE sends an RRCSetupComplete message to the base station. Specifically, this message is forwarded by the Relay UE to the base station.

[0044] Step 5. Security is activated between the Remote UE and the base station. The messages and procedures for activating security reuse the existing mechanisms.

[0045] Step 6. A dedicated SRB2 / DRB bearer is established between the base station and the Remote UE. This dedicated SRB2 / DRB bearer consists of two RLC channels: PC5 (between the Remote UE and the Relay UE) and Uu (between the Relay UE and the base station). Specifically, these two RLC channels are used by the Remote UE to send and receive SRB2-type RRC / NAS messages and uplink and downlink service data with the base station. This is achieved by reusing the existing RRC reconfiguration mechanism.

[0046] 3.Cause value

[0047] Currently, the protocol pre-configures multiple Cause values, as follows:

[0048] EstablishmentCause::=ENUMERATED{emergency,highPriorityAccess,mt-Access,mo-Signallingmo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS,mps-PriorityAccess,mcs-PriorityAccess,spare6,spare5,spare4,spare3,spare2,spare1}

[0049] ResumeCause::=ENUMERATED{emergency,highPriorityAccess,mt-Access,mo-Signalling,mo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS,rna-Update,mps-PriorityAccess,mcs-PriorityAccess,spare1,spare2,spare3,spare4,spare5}

[0050] exist Figure 1b Step 2 describes a technical scenario: If the Relay UE has not yet entered RRC_CONNECTED when receiving a message from the Remote UE, it must first trigger the establishment of its own RRC connection over the Uu air interface before providing relay services to the Remote UE. The specific details of the Relay UE-initiated RRC connection establishment (for RRC_IDLE) or RRC connection recovery (for RRC_INACTIVE) process have not yet been standardized.

[0051] Among them, in response to the above content, in the embodiments of the present application, the details discussed include: how the Relay UE should determine and use the cause value to initiate its own RRC connection establishment or recovery process.

[0052] The following describes the RRC connection method provided in the embodiment of the present application in detail through specific embodiments and application scenarios in conjunction with the accompanying drawings.

[0053] The technology described in this article is not limited to the fifth-generation mobile communication (5th-generation, 5G) system and subsequent evolution communication systems, and is not limited to the evolution (LTE-Advanced, LTE-A) system of LTE / LTE, and can also be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems.

[0054] The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communication (GSM). An OFDMA system can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies.

[0055] See also Figure 2 , an embodiment of the present application provides an RRC connection method, the method comprising:

[0056] Step 201: When the Relay UE is in RRC_IDLE or RRC_INACTIVE, the Relay UE determines whether a first condition is met;

[0057] Step 202: When the Relay UE meets the first condition, the Relay UE triggers an RRC connection establishment or RRC connection recovery process;

[0058] The first condition mentioned above includes one or more of the following:

[0059] (1) The Relay UE determines to provide relay services for one or more Remote UEs;

[0060] (2) The Relay UE receives one or more first messages from one or more Remote UEs, each of which carries a first cause value indicating that each Remote UE requests RRC connection recovery or RRC connection establishment. It should be noted that whether each first message is used to request RRC connection recovery or RRC connection establishment depends on the RRC state of the Remote UE that sends the first message. If the Remote UE is in RRC_IDLE state, the corresponding first message is used to request RRC connection establishment; if the Remote UE is in RRC_INACTIVE state, the corresponding first message is used to request RRC connection recovery. The first cause value corresponds to the cause value of the Remote UE.

[0061] In the embodiment of the present application, when the Relay UE meets the first condition above, the RRC connection establishment or RRC connection recovery process is triggered to ensure that the network reasonably controls and accepts the access request of the Relay UE.

[0062] In the embodiment of the present application, the RRC status of the Relay UE and the Remote UE may be in the following four situations:

[0063] Case 1: The Relay UE is in RRC_IDLE mode, and all Remote UEs are in RRC_IDLE mode.

[0064] Case 2: The Relay UE is in RRC_IDLE mode and all Remote UEs are in RRC_INACTIVE mode.

[0065] Case 3: The Relay UE is in RRC_INACTIVE mode and all Remote UEs are in RRC_IDLE mode.

[0066] Case 4: The relay UE is RRC_INACTIVE and all remote UEs are RRC_INACTIVE.

[0067] Case 5: The relay UE is in RRC_IDLE mode, some remote UEs are in RRC_IDLE mode, and some remote UEs are in RRC_INACTIVE mode.

[0068] Case 6: The Relay UE is RRC_INACTIVE, some Remote UEs are RRC_IDLE, and some Remote UEs are RRC_INACTIVE.

[0069] In some implementations, there may be the following four combinations:

[0070] (1) When the Relay UE is in RRC_INACTIVE, the access stratum (AS) of the Relay UE determines target information, where the target information includes a second cause value and / or a second access category (AC);

[0071] (2) When the Relay UE is in RRC_IDLE, the AS of the Relay UE determines target information, where the target information includes the second cause value and / or the second AC;

[0072] (3) When the relay UE is in RRC_INACTIVE mode, the non-access stratum (NAS) of the relay UE determines target information, where the target information includes at least one of the second cause value, the second AC, and triggering of a NAS signaling procedure;

[0073] (4) When the Relay UE is in RRC_IDLE, the NAS of the Relay UE determines target information, where the target information includes at least one of the second cause value, the second AC, and triggering the NAS signaling process;

[0074] For the above four combinations, in one possible implementation, when the Relay UE is in RRC_IDLE, the Relay UE triggers the RRC connection establishment process determined by the NAS of the Relay UE;

[0075] When the Relay UE is in RRC_INACTIVE, the Relay UE triggers the RRC connection recovery procedure, which is determined by the AS of the Relay UE.

[0076] Further, the method further includes: when the relay UE is in RRC_INACTIVE, the AS of the relay UE determines target information, where the target information includes a second cause value and / or a second AC;

[0077] When the Relay UE is in RRC_IDLE, the AS of the Relay UE sends first indication information to the NAS of the Relay UE, and the NAS of the Relay UE determines target information according to the first indication information, where the target information includes at least one of: a second cause value, a second AC, and triggering a NAS signaling process.

[0078] Furthermore, for the scenario with only cause value, the method also includes: when the target information does not include the second AC, the Relay UE does not perform the Unified Access Control (UAC) operation, and directly sends an RRC connection establishment request message or an RRC connection recovery request message to the network device, and the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0079] Furthermore, for scenarios with cause value and AC, the method also includes: when the target information includes a second cause value and a second AC, the Relay UE performs a UAC operation according to the second AC; after the access barring according to the UAC operation is lifted, the Relay UE sends an RRC connection establishment request message or an RRC connection recovery request message to the network device, and the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0080] In a possible implementation, when the target information includes the second cause value, the AS of the relay UE determines the target information, including any one of the following:

[0081] (1) The AS of the Relay UE assigns a preset cause value to the second cause value. The preset cause value is a cause value agreed upon by the protocol, pre-configured, or configured by the network, such as emergency, highPriorityAccess, mps-PriorityAccess, mcs-PriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, or rna-Update.

[0082] Specifically, this method does not rely on distinguishing between the Relay UE itself and the Remote UE, and is set using a fixed method.

[0083] (2) The AS of the relay UE assigns a first cause value specified in all received first cause values ​​to the second cause value;

[0084] Specifically, this method only considers the Remote UE situation and is set according to one of the cause values ​​of all Remote UEs.

[0085] A first cause value specified in all the first cause values ​​above, including any of the following:

[0086] (a) The first cause value carried by the first first message among all first messages; it should be noted that, from the perspective of reception by the Relay UE, the first cause value carried by the first first message refers to the cause value carried by the first first message received by the Relay UE first; from the perspective of transmission by the Remote UE, the first cause value carried by the first first message refers to the cause value carried by the first message sent by the Remote UE first selected by the Relay UE;

[0087] (b) any one of all first cause values;

[0088] (c) The highest priority among all first cause values ​​in a preset priority order. The preset priority order is a protocol-agreed, pre-configured, or network-configured priority order. For example: emergency > highPriorityAccess, mps-PriorityAccess, mcs-PriorityAccess > mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS > rna-Update. If the priorities are the same, the RelayUE is further allowed to randomly select one of them.

[0089] (3) The AS of the relay UE assigns the highest priority among all the first cause values ​​and rna-Update to the second cause value. The priority is the priority agreed by the protocol, pre-configured, or configured by the network.

[0090] Specifically, this method is equivalent to considering the Relay UE situation and the Remote UE situation. This method can be used in the following scenarios: the upper layer of the Relay UE has no signaling and / or services, but the AS of the Relay UE has RNAU requirements;

[0091] The upper layer is a general term for layers above the AS, such as the NAS and application layer.

[0092] (4) The AS of the Relay UE assigns the cause value provided by the upper layer to the second cause value.

[0093] Specifically, this approach only considers the relay UE scenario and can be used in scenarios where the relay UE's upper layer has signaling and / or services. Furthermore, this approach is applicable whether the relay UE's AS has or does not have RNAU requirements, without limitation.

[0094] In a possible implementation, when the target information includes a second AC, the AS of the Relay UE determines the target information, including: the AS of the Relay UE determines the second AC based on a mapping relationship between the second cause value and the second AC, where the mapping relationship is agreed upon by the protocol, pre-configured, or network configured.

[0095] In a possible implementation manner, the first indication information is used to indicate at least one of the following:

[0096] (1) Receiving a connection establishment request or connection recovery request from one or more Remote UEs;

[0097] (2) Determine to provide relay services for one or more Remote UEs;

[0098] (3) a first cause value of one or more Remote UEs, the first cause value being carried in the first message;

[0099] (4) The third cause value recommended by the AS of the Relay UE. It should be noted that the determination of the third cause value can refer to the method for the AS of the Relay UE to determine the second cause value. For example, the AS of the Relay UE sets the first cause value carried by one of all the received first messages to the third cause value; or the AS of the Relay UE sets the one with a higher priority among all the first cause values ​​and rna-Update to the third cause value.

[0100] (5) Indicates the service attributes of one or more Remote UEs. The service attributes may include: high / medium / low priority service, emergency / non-emergency service, whether it is a high priority service, whether it is an emergency service, etc.

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

[0102] When the relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection recovery message or an RRC connection establishment message from the network device, the AS of the relay UE indicates to the NAS of the relay UE that the RRC connection recovery is successful and / or that the relay UE enters the RRC_CONNECTED state; the relay UE sends an RRC connection recovery complete message to the network device;

[0103] Alternatively, when the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection release message, an RRC connection rejection message from the network device or determines that the RRC connection recovery has failed, the AS of the Relay UE indicates to the NAS of the Relay UE that the RRC connection recovery triggered for providing relay service has failed.

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

[0105] When the relay UE sends an RRC connection request message to the network device and receives an RRC connection establishment message from the network device, the relay UE's AS indicates to the relay UE's NAS that the RRC connection is successfully established and / or enters RRC_CONNECTED; the relay UE sends an RRC connection establishment complete message to the network device and triggers the NAS signaling process;

[0106] Alternatively, when the Relay UE sends an RRC connection request message to the network device and receives an RRC connection reject message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE indicates to the NAS of the Relay UE that the RRC connection establishment for providing relay service has failed.

[0107] The solution of this application is described below with reference to specific embodiments:

[0108] Example 1: See Figure 3a The Relay UE AS layer determines the cause value. In this embodiment, the Relay UE is currently in RRC_INACTIVE. The RRC connection recovery process is initiated on the Uu air interface.

[0109] Step 1: When the Relay UE is currently in RRC_INACTIVE and satisfies at least one of the following conditions, the Relay UE triggers the RRC connection recovery procedure on the Uu air interface.

[0110] Condition 1: The Relay UE determines to provide relay services for one or more Remote UEs

[0111] Condition 2: The Relay UE receives an RRC connection establishment request or RRC connection restoration request message from at least one of the one or more Remote UEs.

[0112] Step 2: The Relay UE AS layer determines the cause value 2 carried in the RRC Connection Recovery Request message. Specifically, based on the Relay UE's own situation (whether upper layer signaling and / or services have arrived, and whether the AS layer has RNAU requirements) and / or the Remote UE's situation, it decides to execute either step 2.1 or step 2.2:

[0113] Step 2.1: Applicable when the Relay UE has no signaling and / or services in its upper layer and the AS layer has no RNAU requirements. The AS layer uses one of the following methods to set the cause value:

[0114] Method 1: Assign cause value 1 in the first received RRC connection establishment request or RRC connection recovery request message to the above cause value 2

[0115] Method 2: Assign one of the cause value 1s in all received RRC connection establishment request or RRC connection recovery request messages to the above cause value 2

[0116] Under method 2, the specific selection method can be self-selection by the UE, or selection based on a certain priority order. The priority order can be determined by protocol agreement, pre-configuration or network configuration. For example: emergency>highPriorityAccess,mps-PriorityAccess,mcs-PriorityAccess>

[0117] mt-Access,mo-Signalling,mo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS>

[0118] rna-Update. In the case of the same priority, the UE is further allowed to randomly select one of them.

[0119] Method 3: Select one of the cause values ​​supported by the existing protocol and assign it to the cause value 2 above.

[0120] Under Method 3, the cause value supported by existing protocols can be all or some of the values. The specific value(s) can be determined by protocol agreement, pre-configuration, or network configuration. For example, at least one of: emergency, highPriorityAccess, mps-PriorityAccess, mcs-PriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, and rna-Update.

[0121] Step 2.2: Applicable when the Relay UE itself does not have upper layer signaling and / or services, but the AS layer has RNAU requirements. The AS layer uses one of the following methods to set the cause value

[0122] Method 1: Same as step 2.1 Method 1.

[0123] Method 2: Select one of the cause value 1 and rna-Update in all received RRC connection establishment request or RRC connection recovery request messages and assign it to the above cause value 2

[0124] Under method 2, the specific selection method can be self-selection by the UE, or selection based on a certain priority order. The priority order can be determined by protocol agreement, pre-configuration or network configuration. For example: emergency>highPriorityAccess,mps-PriorityAccess,mcs-PriorityAccess>

[0125] mt-Access,mo-Signalling,mo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS>

[0126] rna-Update. In the case of the same priority, the UE is further allowed to randomly select one of them.

[0127] Method 3: Same as step 2.1 Method 3.

[0128] Method 4: Set cause value 2 to rna-Update.

[0129] Step 2.3: Applicable to the case where the Relay UE has its own upper layer signaling and / or services, the AS layer uses one of the following methods to set the cause value

[0130] Method 1: Same as step 2.1 Method 1.

[0131] Method 2: Select one of the cause value 1 in all received RRC connection establishment request or RRC connection recovery request messages and the cause value provided by the upper layer and assign it to the above cause value 2;

[0132] Under Method 2, the UE can select the access points independently or based on a certain priority order. The priority order can be determined by protocol agreement, pre-configuration, or network configuration. For example, emergency > highPriorityAccess, mps-PriorityAccess, mcs-PriorityAccess > mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS > rna-Update. If the priorities are the same, the UE is further allowed to randomly select one of the access points.

[0133] Method 3: Same as step 2.1 Method 3.

[0134] Method 4: Cause value 2 is set to the cause value provided by the upper layer.

[0135] Step 3: The Relay UE sends an RRC connection restoration request message to the base station, where the RRC connection restoration request message carries the cause value 2.

[0136] Step 4: The Relay UE AS layer sends an indication message to the NAS layer based on whether the RRC connection recovery process is successful. Specifically, the AS layer uses one of the following methods to determine the content of the indication message.

[0137] Step 4.1: If the RRC connection is restored successfully, the Relay UE AS layer further sends an indication of "RRC connection restored successfully and / or entered RRC_CONNECTED" to the NAS layer.

[0138] Step 4.2: If the RRC connection recovery fails, the Relay UE AS layer further notifies the NAS layer of the "RRC connection release cause value and / or entry into RRC_IDLE".

[0139] According to step 4.2, a new "RRC connection release cause value" is defined to indicate an RRC connection recovery failure dedicated to the relay service or an RRC connection recovery failure for the non-relay service.

[0140] Example 2: See Figure 3b The Relay UE NAS layer determines the cause value. In this embodiment, the Relay UE is currently in RRC_IDLE. The RRC connection establishment process is initiated on the Uu air interface.

[0141] Step 1: When the Relay UE is currently in RRC_IDLE and satisfies at least one of the following conditions, the Relay UE triggers the RRC connection establishment process on the Uu air interface.

[0142] Condition 1: The Relay UE determines to provide relay services for one or more Remote UEs

[0143] Condition 2: The Relay UE receives an RRC connection establishment request or RRC connection restoration request message from at least one of the one or more Remote UEs.

[0144] Step 2: The Relay UE AS layer sends an indication message to the NAS layer. The indication message includes at least one of the following:

[0145] Indicates receipt of a connection request from a Remote UE: The term "connection request" generally refers to a connection establishment request and a connection restoration request. Depending on the RRC state of each Remote UE, it may specifically refer to an RRC connection establishment request or an RRC connection restoration request.

[0146] Indicates the need to provide relay services for Remote UE;

[0147] Cause value 1 indicating at least one Remote UE: The "cause value 1" is carried in the RRC Connection Establishment Request or RRC Connection Recovery Request message of the Remote UE;

[0148] Indicates the cause value 3 recommended by the Relay UE AS layer: Specifically, the AS layer refers to all cause value 1s and the situation of its own AS layer to determine cause value 3. The final recommended cause value 3 is independent of cause value 1 and can be the same or different.

[0149] Step 3: After receiving the instruction information from the AS layer, the Relay UE NAS layer provides the AS layer with at least one of the following information:

[0150] Cause value 2: Specifically, the Relay UE NAS layer determines cause value 2 based on whether there is signaling and / or service demand, and the indication information provided by the AS layer.

[0151] Triggered NAS signaling process: the NAS signaling process is a service establishment request process or a mobility registration process.

[0152] Step 4: The Relay UE sends an RRC connection establishment request message to the base station, where the RRC connection establishment request message carries the cause value 2.

[0153] Step 5: The AS layer of the Relay UE further sends an indication message to the NAS layer based on whether the RRC connection recovery process is successful. Specifically, the AS layer uses one of the following methods to determine the content of the indication message.

[0154] Step 5.1: If the RRC connection is restored successfully, the Relay UE AS layer further sends an indication of "RRC connection restored successfully and / or entered RRC_CONNECTED" to the NAS layer.

[0155] According to step 5.1, initiate and complete the NAS signaling process mentioned in step 3.

[0156] Step 5.2: If the RRC connection recovery fails, the Relay UE AS layer further notifies the NAS layer of the "RRC connection release cause value and / or entry into RRC_IDLE".

[0157] According to step 5.2, a new "RRC connection release cause value" is defined to indicate an RRC connection recovery failure dedicated to the relay service or an RRC connection recovery failure for the non-relay service.

[0158] It should be noted that the RRC connection method provided in the embodiment of the present application can be executed by an RRC connection device, or a control module in the RRC connection device for executing the RRC connection method. In the embodiment of the present application, the RRC connection device provided in the embodiment of the present application is described by taking the RRC connection method executed by the RRC connection device as an example.

[0159] See also Figure 4 , an embodiment of the present application provides an RRC connection device, the device comprising:

[0160] A first determining module 401 is configured to, when the Relay UE is in RRC_IDLE or RRC_INACTIVE, determine whether the Relay UE satisfies a first condition;

[0161] The triggering module 402 is configured to trigger the Relay UE to trigger an RRC connection establishment or RRC connection recovery process when the Relay UE meets a first condition;

[0162] The first condition includes one or more of the following:

[0163] The Relay UE determines to provide a relay service for one or more Remote UEs;

[0164] The Relay UE receives one or more first messages from one or more Remote UEs, where each of the first messages carries a first cause value for each of the Remote UEs to request RRC connection recovery or RRC connection establishment.

[0165] In a possible implementation manner, when the Relay UE is in RRC_IDLE, the Relay UE triggering the RRC connection establishment procedure is determined by the NAS of the Relay UE;

[0166] In the case that the Relay UE is in RRC_INACTIVE, whether the Relay UE triggers the RRC connection recovery procedure is determined by the AS of the Relay UE.

[0167] In a possible implementation, the device further includes:

[0168] A second determining module is configured to: when the Relay UE is in RRC_INACTIVE, determine target information by the AS of the Relay UE, where the target information includes: a second cause value and / or a second AC;

[0169] The third determination module is configured to, when the Relay UE is in RRC_IDLE, cause the AS of the Relay UE to send first indication information to the NAS of the Relay UE, and the NAS of the Relay UE to determine target information based on the first indication information, where the target information includes at least one of the second cause value, the second AC, and triggering the NAS signaling process.

[0170] In a possible implementation, the device further includes:

[0171] The first sending module is used to, when the target information does not include the second AC, cause the Relay UE to not perform a UAC operation and directly send an RRC connection establishment request message or an RRC connection recovery request message to the network device, where the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0172] In a possible implementation, the device further includes:

[0173] an execution module, configured to, when the target information includes the second cause value and the second AC, cause the relay UE to perform a UAC operation according to the second AC;

[0174] The second sending module is used to send, by the Relay UE, an RRC connection establishment request message or an RRC connection recovery request message to the network device after the access barring of the UAC operation is lifted, where the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0175] In a possible implementation manner, when the target information includes the second cause value, the first determining module is further configured to perform any of the following:

[0176] The AS of the Relay UE assigns a preset cause value to the second cause value, where the preset cause value is a cause value agreed upon by a protocol, pre-configured, or configured by the network;

[0177] The AS of the relay UE assigns a first cause value specified in all received first cause values ​​to the second cause value;

[0178] The AS of the Relay UE assigns the highest priority among all the first cause values ​​and rna-Update to the second cause value, where the priority is a priority agreed upon by the protocol, pre-configured, or configured by the network;

[0179] The AS of the Relay UE assigns the cause value provided by the upper layer to the second cause value.

[0180] In a possible implementation manner, when the target information includes the second cause value, the first determining module is further configured to:

[0181] The AS of the Relay UE determines the second AC according to a mapping relationship between the second cause value and the second AC, where the mapping relationship is agreed upon by a protocol, pre-configured, or configured by a network.

[0182] In a possible implementation manner, a first cause value specified in all the first cause values ​​includes any one of the following:

[0183] a first cause value carried by the first first message among all the first messages;

[0184] Any one of the first cause values;

[0185] The one with the highest priority among all the first cause values ​​in a preset priority order, where the preset priority order is a priority order agreed upon by a protocol, pre-configured, or configured by a network.

[0186] In a possible implementation manner, the first indication information is used to indicate at least one of the following:

[0187] receiving a connection establishment request or a connection recovery request from the one or more Remote UEs;

[0188] Determining to provide a relay service for the one or more Remote UEs;

[0189] a first cause value of the one or more Remote UEs, where the first cause value is carried in the first message;

[0190] The third cause value recommended by the AS of the Relay UE;

[0191] Indicates the service attributes of the one or more Remote UEs.

[0192] In a possible implementation, the device further includes:

[0193] The third sending module is used to:

[0194] When the relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection recovery message or an RRC connection establishment message from the network device, the AS of the relay UE sends second indication information to the NAS of the relay UE, where the second indication information includes: RRC connection recovery success and / or entering RRC_CONNECTED; the relay UE sends an RRC connection recovery complete message to the network device;

[0195] Alternatively, when the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection release message, an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends a third indication to the NAS of the Relay UE, and the third indication information includes: RRC connection recovery failure triggered for providing relay service.

[0196] In a possible implementation, the device further includes:

[0197] The fourth sending module is used to:

[0198] When the relay UE sends an RRC connection request message to the network device and receives an RRC connection establishment message from the network device, the AS of the relay UE sends fourth indication information to the NAS of the relay UE, where the fourth indication information includes: RRC connection establishment success and / or entering RRC_CONNECTED; the relay UE sends an RRC connection establishment complete message to the network device and triggers the NAS signaling process;

[0199] Alternatively, when the Relay UE sends an RRC connection request message to the network device and receives an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends fifth indication information to the NAS of the Relay UE, and the fifth indication information is used to indicate that the RRC connection establishment for providing relay service has failed.

[0200] The RRC connection device in the embodiments of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), an ATM, or an kiosks, etc., which are not specifically limited in the embodiments of the present application.

[0201] The "virtual device" in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0202] The RRC connection device provided in the embodiment of the present application can achieve Figures 2 to 3b To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0203] Optional, such as Figure 5 As shown, an embodiment of the present application further provides a Relay UE 500, including a memory 501, a processor 502, and a program or instruction stored in the memory 501 and executable on the processor 502. When the program or instruction is executed by the processor 502, each process of the above-mentioned RRC connection method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0204] It should be noted that the electronic devices in the embodiments of the present application include mobile electronic devices and non-mobile electronic devices.

[0205] Figure 6 A schematic diagram of the hardware structure of a Relay UE implementing an embodiment of the present application.

[0206] The Relay UE 600 includes but is not limited to components such as a radio frequency unit 601 , a network module 602 , an audio output unit 603 , an input unit 604 , a sensor 605 , a display unit 606 , a user input unit 607 , an interface unit 608 , a memory 609 , and a processor 610 .

[0207] Those skilled in the art will appreciate that the Relay UE 600 may further include a power source (such as a battery) for supplying power to various components. The power source may be logically connected to the processor 610 through a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. Figure 6 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0208] The processor 610 is configured to, when the Relay UE is in RRC_IDLE or RRC_INACTIVE, determine, by the Relay UE, whether a first condition is met;

[0209] The processor 610 is further configured to trigger, by the relay UE, an RRC connection establishment or RRC connection recovery process when the relay UE meets the first condition;

[0210] The first condition includes one or more of the following:

[0211] The Relay UE determines to provide a relay service for one or more Remote UEs;

[0212] The Relay UE receives one or more first messages from one or more Remote UEs, where each of the first messages carries a first cause value for each of the Remote UEs to request RRC connection recovery or RRC connection establishment.

[0213] Optionally, the processor 610 is configured to: when the relay UE is in RRC_IDLE, triggering the RRC connection establishment process by the relay UE is determined by the NAS of the relay UE;

[0214] In the case that the Relay UE is in RRC_INACTIVE, whether the Relay UE triggers the RRC connection recovery procedure is determined by the AS of the Relay UE.

[0215] Optionally, the processor 610 is configured to: determine, by the AS of the relay UE, target information, where the target information includes a second cause value and / or a second AC;

[0216] Processor 610 is configured to: the AS of the Relay UE sends first indication information to the NAS of the Relay UE, and the NAS of the Relay UE determines target information according to the first indication information, where the target information includes at least one of the second cause value, the second AC, and triggering the NAS signaling process.

[0217] Optionally, the processor 610 is used to: when the target information does not include the second AC, the RelayUE does not perform the UAC operation, and directly sends an RRC connection establishment request message or an RRC connection recovery request message to the network device, and the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0218] Optionally, the processor 610 is configured to: when the target information includes the second cause value and the second AC, the relay UE performs a UAC operation according to the second AC;

[0219] The processor 610 is configured to, after the access barring according to the UAC operation is lifted, send, by the Relay UE, an RRC connection establishment request message or an RRC connection recovery request message to the network device, where the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

[0220] Optionally, when the target information includes the second cause value, the processor 610 is configured to perform any of the following:

[0221] The AS of the Relay UE assigns a preset cause value to the second cause value, where the preset cause value is a cause value agreed upon by a protocol, pre-configured, or configured by the network;

[0222] The AS of the relay UE assigns a first cause value specified in all received first cause values ​​to the second cause value;

[0223] The AS of the Relay UE assigns the highest priority among all the first cause values ​​and rna-Update to the second cause value, where the priority is a priority agreed upon by the protocol, pre-configured, or configured by the network;

[0224] The AS of the Relay UE assigns the cause value provided by the upper layer to the second cause value.

[0225] Optionally, when the target information includes a second cause value, the processor 610 is configured to: determine the second AC by the AS of the Relay UE according to a mapping relationship between the second cause value and the second AC, where the mapping relationship is a protocol agreement, pre-configuration, or network configuration.

[0226] Optionally, a first cause value specified in all the first cause values ​​includes any one of the following:

[0227] a first cause value carried by the first first message among all the first messages;

[0228] Any one of the first cause values;

[0229] The one with the highest priority among all the first cause values ​​in a preset priority order, where the preset priority order is a priority order agreed upon by a protocol, pre-configured, or configured by a network.

[0230] Optionally, the first indication information is used to indicate at least one of the following:

[0231] receiving a connection establishment request or a connection recovery request from the one or more Remote UEs;

[0232] Determining to provide a relay service for the one or more Remote UEs;

[0233] a first cause value of the one or more Remote UEs, where the first cause value is carried in the first message;

[0234] The third cause value recommended by the AS of the Relay UE;

[0235] Indicates the service attributes of the one or more Remote UEs.

[0236] Optionally, the processor 610 is configured to: when the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection recovery message or an RRC connection establishment message from the network device, the AS of the Relay UE sends second indication information to the NAS of the Relay UE, where the second indication information includes: RRC connection recovery success and / or entering RRC_CONNECTED; the Relay UE sends an RRC connection recovery completion message to the network device;

[0237] Alternatively, when the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection release message, an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends a third indication to the NAS of the Relay UE, and the third indication information includes: RRC connection recovery failure triggered for providing relay service.

[0238] Optionally, the processor 610 is configured to: when the Relay UE sends an RRC connection request message to the network device and receives an RRC connection establishment message from the network device, the AS of the Relay UE sends fourth indication information to the NAS of the Relay UE, where the fourth indication information includes: RRC connection establishment success and / or entering RRC_CONNECTED; the Relay UE sends an RRC connection establishment completion message to the network device and triggers the NAS signaling process;

[0239] Alternatively, when the Relay UE sends an RRC connection request message to the network device and receives an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends fifth indication information to the NAS of the Relay UE, and the fifth indication information is used to indicate that the RRC connection establishment for providing relay service has failed.

[0240] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The graphics processor 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 607 includes a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here. The memory 609 may be used to store software programs and various data, including, but not limited to, applications and operating systems. The processor 610 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and applications, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 610.

[0241] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, the various processes of the above-mentioned RRC connection method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0242] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0243] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned RRC connection method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0244] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0245] An embodiment of the present application further provides a computer program product, which is stored in a non-volatile storage medium and configured to be executed by at least one processor to implement the steps of the method described above.

[0246] The embodiment of the present application further provides an execution device, which is configured to execute the method described above.

[0247] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0248] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0249] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A sidelink radio resource control (RRC) connection method, characterized in that: include: When the relay terminal Relay UE is in a radio resource control idle state RRC_IDLE or a radio resource control inactive state RRC_INACTIVE, the Relay UE determines whether a first condition is met; When the Relay UE meets the first condition, the Relay UE triggers an RRC connection establishment or RRC connection recovery process; The first condition includes: the relay UE receives one or more first messages from one or more remote UEs, each of the first messages carrying a first cause value of each remote UE requesting RRC connection recovery or RRC connection establishment; The method further includes: the AS of the relay UE determining target information, where the target information includes a second cause value and a second access type AC; The AS of the Relay UE determines the target information, including any one of the following: The AS of the Relay UE assigns a preset cause value to the second cause value, where the preset cause value is a cause value agreed upon by the protocol, pre-configured, or configured by the network; The AS of the relay UE assigns a first cause value specified in all received first cause values ​​to the second cause value; The AS of the Relay UE assigns the highest priority among all the first cause values ​​and rna-Update to the second cause value, where the priority is a priority agreed upon by the protocol, pre-configured, or configured by the network; The AS of the Relay UE assigns the cause value provided by the upper layer to the second cause value; The AS of the Relay UE determines the target information, further comprising: the AS of the Relay UE determines the second AC according to a mapping relationship between the second cause value and the second AC, where the mapping relationship is agreed upon by a protocol, pre-configured, or configured by a network.

2. The method according to claim 1, characterized in that When the Relay UE is in RRC_IDLE, the Relay UE triggers the RRC connection establishment process determined by the Non-Access Stratum NAS of the Relay UE; In the case that the Relay UE is in RRC_INACTIVE, the Relay UE triggers the RRC connection recovery procedure, which is determined by the access layer AS of the Relay UE.

3. The method according to claim 1, characterized in that The method further comprises: In a case where the target information includes the second cause value and the second AC, the Relay UE performs a UAC operation according to the second AC; After the access barring of the UAC operation is lifted, the Relay UE sends an RRC connection establishment request message or an RRC connection recovery request message to the network device, where the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

4. The method according to claim 1, wherein A first cause value specified in all first cause values ​​includes any of the following: a first cause value carried by the first first message among all the first messages; Any one of the first cause values; The one with the highest priority among all the first cause values ​​in a preset priority order, where the preset priority order is a priority order agreed upon by a protocol, pre-configured, or configured by a network.

5. The method according to claim 3, characterized in that The method further comprises: When the relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection recovery message or an RRC connection establishment message from the network device, the AS of the relay UE sends second indication information to the NAS of the relay UE, where the second indication information includes: RRC connection recovery success and / or entering RRC_CONNECTED; The Relay UE sends an RRC connection recovery complete message to the network device; or, When the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection release message, an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends third indication information to the NAS of the Relay UE, and the third indication information includes: the RRC connection recovery failure of providing relay service.

6. The method according to claim 3, characterized in that The method further comprises: When the relay UE sends an RRC connection request message to the network device and receives an RRC connection establishment message from the network device, the AS of the relay UE sends fourth indication information to the NAS of the relay UE, where the fourth indication information includes: RRC connection establishment success and / or entering RRC_CONNECTED; The Relay UE sends an RRC connection establishment complete message to the network device and triggers the NAS signaling process; or, When the Relay UE sends an RRC connection request message to the network device and receives an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends fifth indication information to the NAS of the Relay UE, where the fifth indication information is used to indicate that the RRC connection establishment for providing relay service has failed.

7. An RRC connection device, characterized in that: The device comprises: A first determining module is configured to, when the Relay UE is in RRC_IDLE or RRC_INACTIVE, determine whether the Relay UE satisfies a first condition; A triggering module, configured to trigger, when the Relay UE meets a first condition, the Relay UE to trigger an RRC connection establishment or RRC connection recovery process; The first condition includes: the relay UE receives one or more first messages from one or more remote UEs, each of the first messages carrying a first cause value of each remote UE requesting RRC connection recovery or RRC connection establishment; The apparatus further includes: a second determining module, configured to: determine, by the AS of the Relay UE, target information, where the target information includes a second cause value and a second AC; The second determining module is further configured to: The AS of the Relay UE assigns a preset cause value to the second cause value, where the preset cause value is a cause value agreed upon in a protocol, pre-configured, or configured by the network; The AS of the relay UE assigns a first cause value specified in all received first cause values ​​to the second cause value; The AS of the Relay UE assigns the highest priority among all the first cause values ​​and rna-Update to the second cause value, where the priority is a priority agreed upon by the protocol, pre-configured, or configured by the network; The AS of the Relay UE assigns the cause value provided by the upper layer to the second cause value; The second determining module is further configured to: The AS of the Relay UE determines the second AC according to a mapping relationship between the second cause value and the second AC, where the mapping relationship is agreed upon by a protocol, pre-configured, or configured by a network.

8. The device according to claim 7, characterized in that When the Relay UE is in RRC_IDLE, the Relay UE triggers the RRC connection establishment procedure determined by the NAS of the Relay UE; In the case that the Relay UE is in RRC_INACTIVE, whether the Relay UE triggers the RRC connection recovery procedure is determined by the AS of the Relay UE.

9. The device according to claim 7, characterized in that The device further comprises: an execution module, configured to, when the target information includes the second cause value and the second AC, cause the relay UE to perform a UAC operation according to the second AC; The second sending module is used to send, by the Relay UE, an RRC connection establishment request message or an RRC connection recovery request message to the network device after the access barring of the UAC operation is lifted, where the RRC connection establishment request message or the RRC connection recovery request message carries the second cause value.

10. The device according to claim 7, characterized in that A first cause value specified in all first cause values ​​includes any of the following: a first cause value carried by the first first message among all the first messages; Any one of the first cause values; The one with the highest priority among all the first cause values ​​in a preset priority order, where the preset priority order is a priority order agreed upon by a protocol, pre-configured, or configured by a network.

11. The device according to claim 9, characterized in that The device further comprises: The third sending module is used to: When the relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection recovery message or an RRC connection establishment message from the network device, the AS of the relay UE sends second indication information to the NAS of the relay UE, where the second indication information includes: RRC connection recovery success and / or entering RRC_CONNECTED; the relay UE sends an RRC connection recovery complete message to the network device; or, When the Relay UE sends an RRC connection recovery request message to the network device and receives an RRC connection release message, an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends third indication information to the NAS of the Relay UE, and the third indication information includes: RRC connection recovery failure triggered for providing relay service.

12. The device according to claim 9, characterized in that The device further comprises: The fourth sending module is used to: When the relay UE sends an RRC connection request message to the network device and receives an RRC connection establishment message from the network device, the AS of the relay UE sends fourth indication information to the NAS of the relay UE, where the fourth indication information includes: RRC connection establishment success and / or entering RRC_CONNECTED; the relay UE sends an RRC connection establishment complete message to the network device and triggers the NAS signaling process; or, When the Relay UE sends an RRC connection request message to the network device and receives an RRC connection rejection message from the network device or determines that the RRC connection recovery fails, the AS of the Relay UE sends fifth indication information to the NAS of the Relay UE, where the fifth indication information is used to indicate that the RRC connection establishment for providing relay service has failed.

13. A SL UE, characterized in that: The invention comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the RRC connection method according to any one of claims 1 to 6.

14. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the RRC connection method according to any one of claims 1 to 6 are implemented.

Images