RRC connection methods and devices in SL Relay scenarios

Abstract

The embodiment of the application provides an RRC connection method in a SL Relay scene, and belongs to the technical field of communication. The method comprises the following steps: in the case that a Relay UE is in an idle state IDLE or an inactivation state INACTIVE, a non-access layer NAS of the Relay UE receives first request information from an access layer AS of the Relay UE, and the first request information is used for indicating that the Relay UE establishes a NAS connection; and the NAS of the Relay UE sends first information to the AS of the Relay UE according to the first request information, and the first information is used for establishing the NAS connection.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of communication, in particular to a RRC connection method and device in a SL Relay scenario. BACKGROUND

[0002] In a radio resource control (RRC) connection establishment procedure in a sidelink relay (SL Relay) scenario, if a relay terminal (also known as a relay user equipment, Relay UE) has not entered a radio resource control connected state (RRC_CONNECTED) at the moment when a message of a remote terminal (Remote UE) is received, the Relay UE needs to first trigger an RRC connection establishment of its own over a Uu air interface, and then can provide relay services for the Remote UE. Details of the RRC connection establishment or RRC connection recovery procedure initiated by the Relay UE have not been determined. SUMMARY

[0003] Embodiments of the present application aim to provide a RRC connection method and device in a SL Relay scenario, to solve the technical problem that the network cannot reasonably control and admit access requests of Relay UEs.

[0004] In a first aspect, embodiments of the present application provide a RRC connection method in a SL Relay scenario, the method comprising:

[0005] In a case where a Relay UE is in an IDLE or INACTIVE state, a non-access stratum (NAS) of the Relay UE receives first request information from an access stratum (AS) of the Relay UE, the first request information being used to indicate that the Relay UE establishes an NAS connection;

[0006] The NAS of the Relay UE sends first information to the AS of the Relay UE according to the first request information, the first information being used to establish an NAS connection.

[0007] In a second aspect, embodiments of the present application provide a RRC connection device in a SL Relay scenario, the device comprising:

[0008] A first receiving module is configured to, in a case where a Relay UE is in an IDLE or INACTIVE state, receive, by a non-access stratum (NAS) of the Relay UE, first request information from an access stratum (AS) of the Relay UE, the first request information being used to indicate that the Relay UE establishes an NAS connection;

[0009] The first sending module is configured to send, by the NAS of the Relay UE, first information for establishing a NAS connection to the AS of the Relay UE according to the first request information.

[0010] In a third aspect, an embodiment of the present application provides a Relay UE, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction is executed by the processor to implement the steps of the RRC connection method in the SL Relay scenario as described in the first aspect.

[0011] In a fourth aspect, an embodiment of the present application provides a readable storage medium, characterized in that the readable storage medium stores a program or instruction, and the program or instruction is executed by a processor to implement the steps of the RRC connection method in the SL Relay scenario as described in the first aspect.

[0012] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the method as described in the first aspect.

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

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

[0015] In the embodiment of the present application, the NAS of the Relay UE sends the first information for the NAS connection to the AS of the Relay UE according to the first request information sent by the AS of the Relay UE, so that the AS can establish the NAS connection through the first information, thereby ensuring that the network reasonably controls and admits the access request of the Relay UE. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1a FIG. 1 is a schematic diagram of an existing relay network structure;

[0017] Figure 1b FIG. 3 is a schematic diagram of an RRC connection establishment process in the SL Relay scenario;

[0018] Figure 2 FIG. 4 is a schematic diagram of an RRC connection method in the SL Relay scenario provided by an embodiment of the present application;

[0019] Figure 3 Application flow diagram provided for the embodiments of the present application;

[0020] Figure 4 RRC connection device structure diagram in the SL Relay scenario provided for the embodiments of the present application;

[0021] Figure 5 Relay UE structure diagram provided for the embodiments of the present application;

[0022] Figure 6 Relay UE structure diagram provided for the embodiments of the present application. DETAILED DESCRIPTION

[0023] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0024] The terms “first”, “second”, and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be exchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by “first”, “second”, etc. are generally a class, not limited to the number of objects, for example, the first object can be one or more. In addition, “and / or” in the specification and claims indicates at least one of the connected objects, and the character “ / ” generally indicates that the front and rear associated objects are in an “or” relationship.

[0025] 1. Sidelink Relay mechanism

[0026] Relay technology in a wireless communication system is to add one or more relay nodes between a base station and a terminal, which is responsible for one or more times of forwarding wireless signals, that is, wireless signals need to go through multiple hops to reach the terminal.

[0027] Wireless relay technology can not only be used to expand cell coverage and compensate for cell coverage blind spots, but also can improve cell capacity through spatial resource reuse. For indoor coverage, relay technology can also overcome penetration loss and improve indoor coverage quality.

[0028] Wireless relay is to split a base station-terminal link into two links, base station-relay station and relay station-terminal, so as to replace a link with poor quality with two links with good quality, to obtain higher link capacity and better coverage.

[0029] Currently supported in LTE Relay is UE-to-Network relay, i.e. one end of the Relay is connected to UE, and the other end is connected to the network side. The UE connected to the Relay is called Remote UE.

[0030] NR will also study how to support UE-to-Network Relay mechanism, typical scenarios such as Figure 1a are shown. This is a typical UE-to-Network scenario, Remote UE needs to transmit data with the network side, but due to poor coverage, find Relay UE as a relay, where the Relay UE and the base station are Uu interface, and the Relay UE and the Remote UE are Sidelink (PC5) interface. Generally, the Relay UE is open and can serve any Remote UE.

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

[0032] Step 1. Remote UE and Relay UE perform discovery process, and then establish PC5 RRC connection.

[0033] Step 2. Remote UE sends RRCSetupRequest message to the base station, and the base station replies RRCSetup message to Remote UE. Specifically, the two messages are sent to the base station or Remote UE by Relay UE. If the Relay UE has not entered RRC_CONNECTED at the time of receiving the message of Remote UE, it needs to first trigger its own RRC connection on Uu air interface, and then can provide relay service for Remote UE.

[0034] Step 3. A Signaling Radio Bearer (SRB) 1 dedicated bearer is established between the base station and the Remote UE, which is composed of two segments of Radio Link Control (RLC) channels, PC5 (between Remote UE and Relay UE) and Uu (between Relay UE and base station). Specifically, the two segments of RLC channels are used for the Remote UE to send / receive RRC messages of SRB1 type to / from the base station.

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

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

[0037] Step 6. A SRB2 / DRB dedicated bearer is established between the base station and the Remote UE, which is composed of two segments of RLC channels, PC5 (between Remote UE and Relay UE) and Uu (between Relay UE and base station). Specifically, the two segments of RLC channels are used for the Remote UE to send / receive RRC / NAS messages of SRB2 type and uplink / downlink traffic data to / from the base station. Specifically, existing RRC reconfiguration mechanisms are reused.

[0038] 3. Cause value

[0039] Currently, multiple Cause values are pre-configured in the protocol, as follows:

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

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

[0042] In step 2 of the method, a technical scenario is described: if the Relay UE has not entered RRC_CONNECTED at the moment of receiving the message of the Remote UE, it needs to first trigger its own RRC connection establishment over the Uu air interface, and then can provide relay services for the Remote UE. Details of the RRC connection establishment (for RRC_IDLE) or RRC connection resume (for RRC_INACTIVE) procedure initiated by the Relay UE have not yet been standardized. Figure 1b

[0043] For this technical scenario, details involved in the discussion include: what cause value should the Relay UE use to initiate its own RRC connection establishment or resume procedure.

[0044] The RRC connection method in the SL Relay scenario provided by the embodiments of the present application will be described in detail below in combination with the accompanying drawings, through specific embodiments and application scenarios.

[0045] The technology described herein is not limited to a 5th-generation (5G) system and subsequent evolution communication system, and is also not limited to an LTE / LTE-Advanced (LTE-A) system, 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. ​

[0046] The terms "system" and "network" are frequently used interchangeably. A CDMA system can implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. UTRA includes Wideband-CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system can implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). LTE and LTE-A are releases 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 can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.

[0047] Referring to Figure 2 The embodiments of the present application provide an RRC connection method in a SL Relay scenario, and the method comprises the following steps:

[0048] In the case that the Relay UE is in IDLE or INACTIVE, the NAS of the Relay UE receives first request information from the AS of the Relay UE;

[0049] The NAS of the Relay UE sends first information to the AS of the Relay UE according to the first request information;

[0050] The first request information is used to instruct the Relay UE to establish a Non-Access Stratum (NAS) connection; and the first information is used to establish the NAS connection.

[0051] In a possible implementation, the first request information comprises one or more of the following:

[0052] (1) a cause value;

[0053] The cause value can be an existing cause value or a new cause value, the existing cause value comprising an existing RRC establishment cause value and a resume cause value, and the new cause value indicating establishment / resume of the RRC connection for relay service;

[0054] (2) a bit value;

[0055] The bit value can be encoded in multiple ways:

[0056] Method 1: if indication = 0, it indicates that the remote UE is for non-urgent service; if indication = 1, it indicates that the remote UE is for urgent service.

[0057] Method 2: if indication = 0, it indicates that the remote UE is for non-high priority service; if indication = 1, it indicates that the remote UE is for high priority service.

[0058] Method 3: if indication = 0, it indicates that the remote UE is for non-relay service; if indication = 1, it indicates that the remote UE is for relay service.

[0059] (3) an access category of a remote UE;

[0060] (4) an access identity of the remote UE;

[0061] (5) a service type of the remote UE.

[0062] In a possible implementation, the first information is one of the following:

[0063] (1) a registration request message (REGISTRATION REQUEST);

[0064] (2) a deregistration request message (DEREGISTRATION REQUEST);

[0065] (3) SERVICE REQUEST message (SERVICE REQUEST);

[0066] (4) CONTROL PLANE SERVICE REQUEST message (CONTROL PLANE SERVICE REQUEST);

[0067] (5) RRC setup request message;

[0068] (6) RRC resume request message.

[0069] In a possible implementation, after the NAS of the Relay UE receives the first request information from the AS of the Relay UE, the method further includes: the NAS of the Relay UE sending a first cause value to the AS of the Relay UE.

[0070] It should be noted that the case described in the embodiments of the present application is that the NAS of the Relay UE sends the first cause value to the AS of the Relay UE at the same time of providing the first information, that is, the first cause value is not in the first information.

[0071] In a possible implementation, the first cause value is determined by any of the following:

[0072] (1) The NAS of the Relay UE determines, according to a first preset priority, a cause value with the highest priority from one or more second cause values and one or more third cause values as the first cause value; wherein the second cause value is a cause value of the Remote UE, which is carried in the RRC connection setup request or the RRC connection resume request, and the third cause value is a cause value used by the Relay UE when the Relay UE needs to enter a connected state.

[0073] (2) The NAS of the Relay UE selects, according to a first preset priority, a cause value with the highest priority from one or more second cause values as the first cause value;

[0074] (3) In the case where there are multiple Remote UEs that establish connections, the NAS of the Relay UE determines a cause value corresponding to a first Remote UE that establishes a connection as the first cause value.

[0075] It should be noted that in actual scenarios, there can be a case that the Relay UE has established SL connections with UE 1 and UE 2 before, and then there is no service entering the IDLE state. Now the Relay UE establishes SL connections with UE 3 and UE 4, and at this time, the Relay UE needs to establish an RRC connection. In this case, the first Remote UE that establishes a connection refers to the first UE that establishes a connection among UE 3 and UE 4.

[0076] (4) In the case that there are multiple Remote UEs with established connections, the NAS of the Relay UE determines any one of the multiple cause values corresponding to all Remote UEs with established connections as the first cause value;

[0077] (5) In the case that the Relay UE itself needs to enter the connected state, the NAS of the Relay UE determines any one of the one or more third cause values as the first cause value;

[0078] Specifically, the case that the Relay UE itself needs to enter the connected state includes the case that the Relay UE needs to send uplink data, or the case that the Relay UE has NAS signaling to send, the NAS signaling including: REGISTRATION REQUEST; DEREGISTRATION REQUEST; SERVICE REQUEST; CONTROL PLANE SERVICE REQUEST.

[0079] (6) The NAS of the Relay UE determines the first cause value according to the first request information;

[0080] Further, the first preset priority is configured in the following manner:

[0081] (1) Pre-configuration; the pre-configuration including: Universal Subscriber Identity Module (USIM); SIM card; Embedded-SIM (eSIM) card; other equivalent forms of SIM card; Universal Integrated Circuit Card (UICC); Mobile Equipment (ME);

[0082] (2) Configured by the network side; the network side configuration including: configured by a Policy Control Function (PCF); configured by an application server, etc.

[0083] In a possible implementation, before the step of receiving, by the NAS of the Relay UE, the first request information from the AS of the Relay UE, the method further includes:

[0084] (1) The NAS of the Relay UE determines a first access type and / or a first access class;

[0085] (2) The NAS of the Relay UE sends the first access type and / or the first access class to the AS of the Relay UE.

[0086] (3) The AS of the Relay UE performs a Unified Access Control (UAC) procedure.

[0087] It should be noted that further, the manner in which the NAS of the Relay UE determines the first access type and / or the first access class can refer to the manner in which the NAS of the Relay UE determines the first cause value, and specifically the NAS of the Relay UE determines the first access type in any of the following ways:

[0088] (1) The NAS of the Relay UE determines, according to a second preset priority, the access type with the highest priority from one or more second access types and one or more third access types as the first access type; wherein the second access type is the access type of the Remote UE, and the third access type is the access type used when the Relay UE itself needs to enter a connected state.

[0089] (2) The NAS of the Relay UE selects, according to a second preset priority, the access type with the highest priority from one or more second access types as the first access type.

[0090] (3) In the case where there are multiple Remote UEs that have established connections with the Relay UE, the NAS of the Relay UE determines the access type of the first Remote UE that has established a connection as the first access type.

[0091] (4) In the case where there are multiple Remote UEs that have established connections with the Relay UE, the NAS of the Relay UE determines any one of the access types of all Remote UEs that have established connections as the first access type.

[0092] (5) In the case where the Relay UE needs to send uplink data, or in the case where the Relay UE itself needs to enter a connected state, or in the case where the Relay UE initiates a mobility registration update procedure, the NAS of the Relay UE determines any one of the one or more third access types as the first access type.

[0093] (6) The NAS of the Relay UE determines the first access type according to the first request information.

[0094] (7) The NAS of the Relay UE determines a default access type as the first access type.

[0095] The second preset priority is configured in the following manner:

[0096] (1) pre-configuration; the pre-configuration includes: USIM; SIM card; eSIM card; other equivalent forms of SIM card; UICC; ME;

[0097] (2) configured by the network side. The network side configuration includes: PCF configuration; application server provides and the like.

[0098] The default preset priority is configured in the following manner:

[0099] (1) pre-configuration; the pre-configuration includes: USIM; SIM card; eSIM card; other equivalent forms of SIM card; UICC; ME;

[0100] (2) configured by the network side. The network side configuration includes: PCF configuration; application server provides and the like.

[0101] Specifically, the NAS of the Relay UE determines the first access level as any of the following:

[0102] (1) the NAS of the Relay UE determines the first access level as the highest priority access level in one or more second access levels and one or more third access levels according to the third preset priority; wherein the second access level is the access level of the Remote UE, and the third access level is the access level used when the Relay UE itself needs to enter the connected state.

[0103] (2) the NAS of the Relay UE selects the highest priority access level from one or more second access levels as the first access level according to the third preset priority;

[0104] (3) in the case where there are multiple Remote UEs connected with the Relay UE, the NAS of the Relay UE determines the access level of the first connected Remote UE as the first access level;

[0105] (4) in the case where there are multiple Remote UEs connected with the Relay UE, the NAS of the Relay UE determines any one of the access levels of all connected Remote UEs as the first access level;

[0106] (5) the NAS of the Relay UE determines the third access level of the Relay UE as the first access type when the Relay UE itself needs to enter the connected state;

[0107] (6) The NAS of the Relay UE determines the first access class according to the first request information;

[0108] (7) The NAS of the Relay UE determines the default access class as the first access class;

[0109] The third preset priority is configured in the following manner:

[0110] (1) Pre-configuration; the pre-configuration includes: USIM; SIM card; eSIM card; SIM card and other equivalent forms; UICC; ME;

[0111] (2) Configured by the network side; the network side configuration includes: PCF configuration; application server provision and the like.

[0112] The default access class is configured in the following manner:

[0113] (1) Pre-configuration; the pre-configuration includes: USIM; SIM card; eSIM card; SIM card and other equivalent forms; UICC; ME;

[0114] (2) Configured by the network side; the network side configuration includes: PCF configuration; application server provision and the like.

[0115] In a possible implementation, the first information includes a first service type.

[0116] The first service type is determined in the following manner:

[0117] (1) In the case where there are multiple service types sent by the Remote UE, the NAS of the Relay UE determines the service type of the first Remote UE that establishes a connection as the first service type;

[0118] (2) The NAS of the Relay UE determines any one of the service types carried in all first RRC connection establishment request or first RRC connection recovery request messages as the first service type;

[0119] (3) In the case where there is traffic of the Remote UE, the NAS of the Relay UE determines the first service type according to the traffic type of the Remote UE;

[0120] (4) The NAS of the Relay UE determines a preset service type as the first service type;

[0121] (5) The NAS of the Relay UE determines the first service type according to the first request information.

[0122] In a possible implementation, after the AS of the Relay UE receives the first information from the NAS of the Relay UE, the method further includes: the AS of the Relay UE sends a first message according to the first information, the first message being any one of the following:

[0123] (1) an RRC setup request message;

[0124] (2) an RRC resume request message.

[0125] In a possible implementation, the first message includes a first cause value;

[0126] The scheme of the present application is described below in combination with specific embodiments:

[0127] Referring to Figure 3 , the Relay UE is in a 5GMM-IDLE state. According to an indication of the AS layer of the Relay UE, the NAS layer of the Relay UE decides a cause value.

[0128] 0. Optionally, an existing mechanism. The Remote UE and the Relay UE establish a PC5 connection.

[0129] 1. The Relay UE receives an RRC connection setup request or an RRC connection resume request message from at least one Remote UE of the one or more Remote UEs.

[0130] 2. The AS layer of the Relay UE sends a request information to the NAS layer of the Relay UE, the request information indicating the NAS layer of the Relay UE to enter a 5GMM connected state. The request information includes at least one of the following:

[0131] (1) a cause value;

[0132] (2) a bit value;

[0133] (3) a type indication, which can include an Access Category of the Remote UE, an Access identity of the Remote UE, and a service type of the Remote UE;

[0134] 3. Optionally, the Relay UE performs a UAC procedure, wherein an Access Category required for performing the UAC procedure is set according to the following manner:

[0135] (1) The NAS of the Relay UE determines the access type required for performing the UAC procedure according to the preset priority, from the access type of one or more Remote UEs and the access type used by the Relay UE itself to enter the connected state with the highest priority; wherein the preset priority can be preconfigured by USIM; SIM card; eSIM card; SIM card; UICC; ME, or other equivalent forms, or configured by the network side, for example: PCF configuration; application server provision, and the like.

[0136] (2) The NAS of the Relay UE determines the access type required for performing the UAC procedure according to the preset priority, from the access type of one or more Remote UEs with the highest priority;

[0137] (3) In the case of multiple connected Remote UEs, the NAS of the Relay UE determines the access type required for performing the UAC procedure as the access type of the first connected Remote UE;

[0138] (4) In the case of multiple connected Remote UEs, the NAS of the Relay UE determines the access type required for performing the UAC procedure as any one of the access types of all connected Remote UEs;

[0139] (5) In the case of the Relay UE needing to send uplink data, or in the case of the Relay UE itself needing to enter the connected state, or in the case of the Relay UE initiating a mobility registration update procedure, the NAS of the Relay UE determines the access type required for performing the UAC procedure as any one of the access types used by the Relay UE itself to enter the connected state;

[0140] (6) The NAS of the Relay UE determines the access type required for performing the UAC procedure according to the request information received from the AS of the Relay UE;

[0141] (7) The NAS of the Relay UE determines the default access type as the AccessCategory required for performing the UAC procedure;

[0142] 4. The NAS layer of the Relay UE triggers a NAS message to enter the connected state, wherein the NAS message is one of: a service request message, a registration message.

[0143] 4.1 the NAS message is SERVICE REQUEST, and the service type information element in the service type IE in the SERVICE REQUEST message is set to one of the following:

[0144] (1) In the case where there are multiple service types sent by Remote UEs, the NAS of the Relay UE determines the service type of the first Remote UE that establishes a connection as the above-mentioned service type;

[0145] (2) The NAS of the Relay UE determines any one of the service types carried in all RRC connection establishment request or RRC connection resume request messages as the above-mentioned service type;

[0146] (3) In the case where there is traffic of the Remote UE, the NAS of the Relay UE determines the above-mentioned service type according to the traffic type of the Remote UE;

[0147] (4) The NAS of the Relay UE determines a preset service type as the above-mentioned service type;

[0148] (5) The NAS of the Relay UE determines the above-mentioned service type according to request information received from the AS of the Relay UE.

[0149] 5. The AS layer of the Relay UE sends an RRCSetupRequest / RRCResumeRequest message, and the message carries a cause value. The method for determining the cause value is any one of the following:

[0150] (1) The NAS of the Relay UE determines, according to a preset priority, one or more cause values carried in an RRC connection establishment request or an RRC connection resume request, and a cause value with the highest priority among one or more cause values used by the Relay UE itself to enter a connected state as the first cause value. The preset priority can be preconfigured through a USIM, a SIM card, an eSIM card, a SIM card, a UICC, an ME, or other equivalent forms, or configured by a network side, for example, configured by a PCF, provided by an application server, or the like.

[0151] (2) The NAS of the Relay UE selects, according to a preset priority, a cause value with the highest priority from one or more cause values carried in an RRC connection establishment request or an RRC connection resume request as the above-mentioned cause value;

[0152] (3) In the case where there are multiple Remote UEs that establish connections, the NAS of the Relay UE determines the cause value of the first Remote UE that establishes a connection as the above-mentioned cause value;

[0153] (4) In the case where there are multiple Remote UEs that establish connections, the NAS of the Relay UE determines any one of the cause values of all Remote UEs that establish connections as the above-mentioned cause value;

[0154] (5) In the case where the Relay UE itself needs to enter the connected state, the NAS of the Relay UE determines any one of the cause values used by the Relay UE itself to enter the connected state as the above-mentioned cause value;

[0155] (6) The NAS of the Relay UE determines the above-mentioned cause value according to the request information received from the AS of the Relay UE;

[0156] It should be noted that the RRC connection device in the SL Relay scenario provided in the embodiments of the present application can be an RRC connection device in the SL Relay scenario, or a control module in the RRC connection device in the SL Relay scenario for executing the RRC connection method in the SL Relay scenario. In the embodiments of the present application, the RRC connection device in the SL Relay scenario executes the RRC connection method in the SL Relay scenario as an example, and the RRC connection device in the SL Relay scenario provided in the embodiments of the present application is described.

[0157] Referring to Figure 4 , the embodiments of the present application provide an RRC connection device 500 in a SL Relay scenario, characterized in that the device comprises:

[0158] A first receiving module 401 is configured to, in the case where a Relay UE is in an idle state IDLE or an inactive state INACTIVE, a non-access stratum NAS of the Relay UE receives first request information from an access stratum AS of the Relay UE, and the first request information is used to instruct the Relay UE to establish a NAS connection;

[0159] A first sending module 402 is configured to, according to the first request information, the NAS of the Relay UE sends first information to the AS of the Relay UE, and the first information is used to establish a NAS connection.

[0160] Optionally, the first request information comprises one or more of the following:

[0161] a cause value;

[0162] bit value;

[0163] access type of the remote UE;

[0164] access class of the remote UE;

[0165] service type of the remote UE.

[0166] Optionally, the first information is any of the following:

[0167] a registration request message;

[0168] a deregistration request message;

[0169] a service request message;

[0170] a control plane service request message;

[0171] an RRC setup request message;

[0172] an RRC resume request message.

[0173] Optionally, the first sending module is further configured to send, by the NAS of the relay UE, a first cause value to the AS of the relay UE.

[0174] Optionally, the first cause value is determined by any of the following:

[0175] the NAS of the relay UE determines, according to a first preset priority, a highest-priority cause value from one or more second cause values and one or more third cause values as the first cause value;

[0176] the NAS of the relay UE selects, according to a first preset priority, a highest-priority cause value from the one or more second cause values as the first cause value;

[0177] in a case where there are multiple connected remote UEs, the NAS of the relay UE determines a cause value of a first connected remote UE as the first cause value;

[0178] in a case where there are multiple connected remote UEs, the NAS of the relay UE determines any one of cause values of all connected remote UEs as the first cause value;

[0179] in a case where the relay UE itself needs to enter a connected state, the NAS of the relay UE determines any one of the one or more third cause values as the first cause value;

[0180] The NAS of the Relay UE determines the first cause value according to the first request information;

[0181] The second cause value is a cause value of the Remote UE, and the third cause value is a cause value used by the Relay UE itself to enter a connected state.

[0182] Optionally, the first preset priority is configured by one of the following:

[0183] Pre-configuration;

[0184] Configuration by a network side.

[0185] Optionally, the apparatus further comprises:

[0186] A first determining module configured to determine, by the NAS of the Relay UE, a first access type and / or a first access class;

[0187] A first sending module configured to send, by the NAS of the Relay UE, the first access type and / or the first access class to an AS of the Relay UE.

[0188] The apparatus further comprises a performing module configured to perform, by the AS of the Relay UE, a UAC procedure.

[0189] Optionally, the first determining module is configured to perform any one of the following:

[0190] The NAS of the Relay UE determines, according to a second preset priority, a highest-priority access type from one or more second access types and one or more third access types as the first access type;

[0191] The NAS of the Relay UE determines, according to a second preset priority, a highest-priority access type from one or more second access types as the first access type;

[0192] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines an access type of a first connected Remote UE as the first access type;

[0193] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines any one of access types of all connected Remote UEs as the first access type;

[0194] In a case that the Relay UE needs to send uplink data, or in a case that the Relay UE itself needs to enter a connected state, or the Relay UE initiates a mobility registration update procedure, the NAS of the Relay UE determines any one of one or more third access types as the first access type;

[0195] The NAS of the Relay UE determines the first access type according to the first request information;

[0196] The NAS of the Relay UE determines a default access type as the first access type;

[0197] The second access type is an access type of the Remote UE, and the third access type is an access type used in a case that the Relay UE itself needs to enter a connected state.

[0198] Optionally, the second preset priority is configured by one of the following:

[0199] Preconfigured;

[0200] Configured by a network side.

[0201] Optionally, the default access type is configured by one of the following:

[0202] Preconfigured;

[0203] Configured by a network side.

[0204] Optionally, the first determining module is configured to any one of the following:

[0205] The NAS of the Relay UE determines, according to a third preset priority, a highest-priority access level from one or more second access levels and one or more third access levels as the first access level;

[0206] The NAS of the Relay UE determines, according to a third preset priority, a highest-priority access level from one or more second access levels as the first access level;

[0207] In a case that there are multiple connected Remote UEs, the NAS of the Relay UE determines an access level of a first connected Remote UE as the first access level;

[0208] In a case that there are multiple connected Remote UEs, the NAS of the Relay UE determines any one of access levels of all connected Remote UEs as the first access level.

[0209] the NAS of the Relay UE determines a third access level of the Relay UE as the first access type in case that the Relay UE itself needs to enter into connected state;

[0210] the NAS of the Relay UE determines the first access level according to the first request information;

[0211] the NAS of the Relay UE determines a default access level as the first access level;

[0212] wherein the second access level is an access level of the Remote UE, and the third access level is an access level used in case that the Relay UE itself needs to enter into connected state.

[0213] Optionally, the third preset priority is configured by one of the following:

[0214] preconfigured;

[0215] configured by a network side.

[0216] Optionally, the default access level is configured by one of the following:

[0217] preconfigured;

[0218] configured by a network side.

[0219] Optionally, the first information comprises a first service type.

[0220] Optionally, the first determining module is further configured to determine any one of the following:

[0221] in case that there are multiple service types sent by Remote UEs, the NAS of the Relay UE determines a service type of a first Remote UE that establishes a connection as the first service type;

[0222] the NAS of the Relay UE determines any one of service types carried in all the first RRC connection establishment request messages or the first RRC connection resume request messages as the first service type;

[0223] in case that there is traffic of Remote UE, the NAS of the Relay UE determines the first service type according to a traffic type of Remote UE;

[0224] the NAS of the Relay UE determines a preset service type as the first service type;

[0225] The NAS of the Relay UE determines the first service type according to the first request information.

[0226] Optionally, the first sending module, after the AS of the Relay UE receives the first information from the NAS of the Relay UE, sends a first message according to the first information, and the first message is any one of the following:

[0227] an RRC setup request message;

[0228] an RRC resume request message.

[0229] Optionally, the first message contains the first cause value.

[0230] The RRC connection device in the SL Relay scenario 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. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., and the embodiments of the present application are not limited in this regard.

[0231] The RRC connection device in the SL Relay scenario in the embodiments of the present application can be a device with an operating system. The operating system can be an Android operating system, an ios operating system, or other possible operating systems, and the embodiments of the present application are not limited in this regard.

[0232] The RRC connection device in the SL Relay scenario provided by the embodiments of the present application can implement the method embodiments Figures 2 to 3 The processes implemented by the method embodiments are not repeated here to avoid repetition.

[0233] Optionally, as Figure 5As shown, the embodiments of the present application also provide a Relay UE 500, comprising a memory 501, a processor 502, a program or instruction stored in the memory 501 and executable on the processor 502, which, when executed by the processor 502, implements each process of the RRC connection method in the SL Relay scenario as described above, and achieves the same technical effects. To avoid repetition, details are not described here.

[0234] It should be noted that the electronic device in the embodiments of the present application includes a mobile electronic device and a non-mobile electronic device.

[0235] Figure 6 A hardware structure schematic diagram of an electronic device according to an embodiment of the present application.

[0236] The electronic device 600 includes, but is not limited to, 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, etc.

[0237] Those skilled in the art can understand that the electronic device 600 can also include a power supply (such as a battery) for powering each component, and the power supply can be logically connected to the processor 610 through a power management system, so as to realize the functions of managing charging, discharging, and power consumption management through the power management system. Figure 6 The electronic device structure shown in the above does not constitute a limitation on the electronic device, and the electronic device can include more or fewer components than shown, or combine certain components, or different component arrangements, which are not described here.

[0238] The processor 610 is configured to, in a case where the relay terminal Relay UE is in an idle state IDLE or an inactive state INACTIVE, receive, by a non-access stratum NAS of the Relay UE, first request information from an access stratum AS of the Relay UE, the first request information being used to instruct the Relay UE to establish a NAS connection.

[0239] The processor 610 is configured to send, by the NAS of the Relay UE, first information to the AS of the Relay UE according to the first request information, the first information being used to establish a NAS connection.

[0240] Optionally, the first request information includes one or more of the following:

[0241] A cause value;

[0242] A bit value;

[0243] Access type of the Remote UE;

[0244] Access class of the Remote UE;

[0245] Service type of the Remote UE.

[0246] Optionally, the first information is any of the following:

[0247] A registration request message;

[0248] A deregistration request message;

[0249] A service request message;

[0250] A control plane service request message;

[0251] An RRC setup request message;

[0252] An RRC resume request message.

[0253] Optionally, the processor 610 is configured to send, by the NAS of the Relay UE, a first cause value to the AS of the Relay UE.

[0254] Optionally, the first cause value is determined by any of the following:

[0255] The NAS of the Relay UE determines, according to a first preset priority, a highest-priority cause value from one or more second cause values and one or more third cause values as the first cause value;

[0256] The NAS of the Relay UE selects, according to a first preset priority, a highest-priority cause value from one or more second cause values as the first cause value;

[0257] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines a cause value of a first connected Remote UE as the first cause value;

[0258] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines any one of cause values of all connected Remote UEs as the first cause value;

[0259] In a case where the Relay UE itself needs to enter a connected state, the NAS of the Relay UE determines any one of one or more third cause values as the first cause value;

[0260] The NAS of the Relay UE determines the first cause value according to the first request information;

[0261] The second cause value is a cause value of the Remote UE, and the third cause value is a cause value used by the Relay UE itself to enter a connected state.

[0262] Optionally, the first preset priority is configured by one of the following:

[0263] Pre-configuration;

[0264] Configuration by a network side.

[0265] Optionally, the processor 610 is configured to determine, by the NAS of the Relay UE, a first access type and / or a first access class;

[0266] The processor 610 is configured to send, by the NAS of the Relay UE, the first access type and / or the first access class to an AS of the Relay UE.

[0267] Optionally, the processor 610 is configured to perform any one of the following:

[0268] The NAS of the Relay UE determines, according to a second preset priority, a highest-priority access type from one or more second access types and one or more third access types as the first access type;

[0269] The NAS of the Relay UE selects, according to a second preset priority, a highest-priority access type from one or more second access types as the first access type;

[0270] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines an access type of a first connected Remote UE as the first access type;

[0271] In a case where there are multiple connected Remote UEs, the NAS of the Relay UE determines any one of access types of all connected Remote UEs as the first access type;

[0272] In a case where the Relay UE needs to send uplink data, or in a case where the Relay UE itself needs to enter a connected state, or in a case where the Relay UE initiates a mobility registration update process, the NAS of the Relay UE determines any one of one or more third access types as the first access type;

[0273] The NAS of the Relay UE determines the first access type according to the first request information;

[0274] The NAS of the Relay UE determines the default access type as the first access type;

[0275] The second access type is the access type of the Remote UE, and the third access type is the access type used when the Relay UE itself needs to enter a connected state.

[0276] Optionally, the second preset priority is configured by one of the following:

[0277] Preconfigured;

[0278] Configured by the network side.

[0279] Optionally, the default access type is configured by one of the following:

[0280] Preconfigured;

[0281] Configured by the network side.

[0282] Optionally, the processor 610 is configured to perform any one of the following:

[0283] The NAS of the Relay UE determines the first access level from one or more second access levels according to a third preset priority, the first access level being the access level with the highest priority in the one or more second access levels and the one or more third access levels;

[0284] The NAS of the Relay UE determines the first access level from one or more second access levels according to a third preset priority, the first access level being the access level with the highest priority in the one or more second access levels and the one or more third access levels;

[0285] In the case where there are multiple connected Remote UEs, the NAS of the Relay UE determines the access level of the first connected Remote UE as the first access level;

[0286] In the case where there are multiple connected Remote UEs, the NAS of the Relay UE determines any one of the access levels of all connected Remote UEs as the first access level;

[0287] The NAS of the Relay UE determines the third access level of the Relay UE as the first access type when the Relay UE itself needs to enter a connected state.

[0288] The NAS of the Relay UE determines the first access level according to the first request information;

[0289] The NAS of the Relay UE determines a default access level as the first access level;

[0290] The second access level is the access level of the Remote UE, and the third level is the access level used when the Relay UE itself needs to enter a connected state.

[0291] Optionally, the third preset priority is configured by one of the following:

[0292] Preconfigured;

[0293] Configured by the network side.

[0294] Optionally, the default access level is configured by one of the following:

[0295] Preconfigured;

[0296] Configured by the network side.

[0297] Optionally, the first information includes a first service type.

[0298] Optionally, the processor 610 is configured to determine any one of the following:

[0299] In the case where there are multiple Remote UEs sending service types, the NAS of the Relay UE determines the service type of the first Remote UE that establishes a connection as the first service type;

[0300] The NAS of the Relay UE determines any one of the service types carried in all the first RRC connection establishment request or first RRC connection recovery request messages as the first service type;

[0301] In the case where there is traffic of the Remote UE, the NAS of the Relay UE determines the first service type according to the traffic type of the Remote UE;

[0302] The NAS of the Relay UE determines a preset service type as the first service type;

[0303] The NAS of the Relay UE determines the first service type according to the first request information.

[0304] Optionally, the processor 610 is configured to, after the AS of the Relay UE receives the first information from the NAS of the Relay UE, send, by the AS of the Relay UE, a first message according to the first information, the first message being any one of the following:

[0305] an RRC setup request message;

[0306] an RRC resume request message.

[0307] Optionally, the first message comprises the first cause value.

[0308] Optionally, the processor 610 is configured to:

[0309] receive, by the AS of the Relay UE, the first access type and / or the first access class from the NAS of the Relay UE;

[0310] the processor 610 is configured to perform, by the AS of the Relay UE, a unified access control (UAC) procedure.

[0311] It should be understood that, in the embodiments of the present application, the input unit 604 can include a graphics processing unit (GPU) 6041 and a microphone 6042. The graphics processing unit 6041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 606 can include a display panel 6061, which can 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 can include two parts of a touch detection device and a touch controller. The other input devices 7072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, and the like, which are not described here in detail. The memory 609 can be used to store software programs and various data, including but not limited to application programs and an operating system. The processor 610 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 610

[0312] The embodiments of the present application also provide a readable storage medium, which stores a program or instructions, the program or instructions are executed by a processor to implement various processes of the RRC connection method in the SL Relay scenario, and achieve the same technical effects. To avoid repetition, details are not described here.

[0313] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, etc.

[0314] The embodiment of the present application further provides a chip, which comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running programs or instructions to realize the processes of the RRC connection method in the SL Relay scenario and achieve the same technical effects. To avoid repetition, details are not described herein.

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

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

[0317] The embodiment of the present application further provides an execution device configured to execute the above method.

[0318] It should be noted that in this document, the term "comprising" or "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the present application is not limited to the order of performing the functions shown or discussed, but can also include performing the functions in a substantially simultaneous manner or in a reverse order, for example, the described method can be performed in an order different from that described, and various steps can also be added, omitted or combined. In addition, the features described with reference to certain examples can be combined in other examples.

[0319] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, also can be through hardware, but many cases the former is the better embodiment. Based on such understanding, the technical solutions of the present application essentially or say the part of the contribution to the prior art can be embodied in the form of software products, the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disc, optical disc), including a number of instructions to make a terminal (may be a mobile phone, computer, server, air conditioner, or network equipment, etc.) executes the method described in various embodiments of the present application.

[0320] The embodiments of the present application are described above in conjunction with the drawings, but the present application is not limited to the above-mentioned specific embodiments, the above-mentioned specific embodiments are only illustrative, but not limited, those skilled in the art can make many forms without departing from the purpose of the present application and the scope of the claims under the inspiration of the present application, all belong to the protection of the present application.

Claims

1. A radio resource control (RRC) connection method in a side-link relay (SL) scenario, characterized in that, The method comprises: In a case where the relay terminal (Relay UE) is in an idle state (IDLE) or an inactive state (INACTIVE), a non-access stratum (NAS) of the Relay UE receives first request information from an access stratum (AS) of the Relay UE, the first request information being used to instruct the Relay UE to establish a NAS connection; The NAS of the Relay UE sends first information to the AS of the Relay UE according to the first request information, the first information being used to establish a NAS connection; After the step of receiving the first request information from the AS of the Relay UE by the NAS of the Relay UE, the method further comprises: the NAS of the Relay UE sends a first cause value to the AS of the Relay UE; The first cause value is determined by any one of the following: The NAS of the Relay UE determines, according to a first preset priority, a cause value with the highest priority from one or more second cause values and one or more third cause values as the first cause value; In a case where the Relay UE itself needs to enter a connected state, the NAS of the Relay UE determines any one of the one or more third cause values as the first cause value; The second cause value is a cause value of a remote terminal (Remote UE), and the third cause value is a cause value used by the Relay UE when the Relay UE itself needs to enter a connected state.

2. The method of claim 1, wherein, The first request information comprises one or more of the following: A cause value; A bit value; An access type of a remote terminal (Remote UE); An access level of the Remote UE; A service type of the Remote UE.

3. The method of claim 1, wherein, The first information is any one of the following: A registration request message; A deregistration request message; A service request message; A control plane service request message; An RRC setup request message; An RRC resume request message.

4. The method of claim 1, wherein, The first preset priority is configured in one of the following ways: Preconfigured; Configured by a network side.

5. The method of claim 1, wherein, Before the step of receiving the first request information from the AS of the Relay UE by the NAS of the Relay UE, the method further comprises: The NAS of the Relay UE determines a first access type and / or a first access level; The NAS of the Relay UE sends the first access type and / or the first access level to the AS of the Relay UE; The AS of the Relay UE performs a unified access control (UAC) procedure.

6. The method of claim 5, wherein, The determination of the first access type by the NAS of the Relay UE comprises any one of the following: The NAS of the Relay UE determines, according to a second preset priority, an access type with the highest priority from one or more second access types and one or more third access types as the first access type; The NAS of the Relay UE selects, according to a second preset priority, an access type with the highest priority from the one or more second access types as the first access type; In a case where multiple Remote UEs establish connections with the Relay UE, the NAS of the Relay UE determines an access type of a first Remote UE that establishes a connection as the first access type; In a case where multiple Remote UEs establish connections with the Relay UE, the NAS of the Relay UE determines any one of access types of all Remote UEs that establish connections as the first access type; In a case where the Relay UE needs to send uplink data, or in a case where the Relay UE itself needs to enter a connected state, or in a case where the Relay UE initiates a mobility registration update procedure, the NAS of the Relay UE determines any one of one or more third access types as the first access type; The NAS of the Relay UE determines the first access type according to the first request information; The NAS of the Relay UE determines a default access type as the first access type; The second access type is an access type of the Remote UE, and the third access type is an access type used in a case where the Relay UE itself needs to enter a connected state.

7. The method of claim 6, wherein, The second preset priority is configured in the following manner: Preconfigured; Configured by a network side.

8. The method of claim 6, wherein, The default access type is configured in the following manner: Preconfigured; Configured by a network side.

9. The method of claim 5, wherein, The NAS of the Relay UE determining the first access level includes any one of the following: The NAS of the Relay UE determines, according to a third preset priority, an access level with the highest priority from one or more second access levels and one or more third access levels as the first access level; The NAS of the Relay UE determines, according to a third preset priority, an access level with the highest priority from one or more second access levels as the first access level; In a case where multiple Remote UEs establish connections with the Relay UE, the NAS of the Relay UE determines an access level of a first Remote UE that establishes a connection as the first access level; In a case where multiple Remote UEs establish connections with the Relay UE, the NAS of the Relay UE determines any one of access levels of all Remote UEs that establish connections as the first access level; The NAS of the Relay UE determines, in a case where the Relay UE itself needs to enter a connected state, a third access level of the Relay UE as the first access type; The NAS of the Relay UE determines the first access level according to the first request information; The NAS of the Relay UE determines a default access level as the first access level; The second access level is an access level of the Remote UE, and the third access level is an access level used when the Relay UE itself needs to enter a connected state.

10. The method of claim 9, wherein, The third preset priority is configured in one of the following manners: Pre-configuration; Configuration by a network side.

11. The method of claim 9, wherein, The default access level is configured in one of the following manners: Pre-configuration; Configuration by a network side.

12. The method of claim 1, wherein, The first information includes a first service type.

13. The method of claim 12, wherein, The first service type is determined in any of the following manners: In a case where multiple service types sent by the Remote UE exist, the NAS of the Relay UE determines a service type of a first Remote UE that establishes a connection as the first service type; The NAS of the Relay UE determines any one of service types carried in a first RRC connection establishment request or a first RRC connection resumption request message as the first service type; In a case where the Remote UE has traffic, the NAS of the Relay UE determines the first service type according to a traffic type of the Remote UE; The NAS of the Relay UE determines a preset service type as the first service type; The NAS of the Relay UE determines the first service type according to the first request information.

14. The method of claim 1, wherein, After the AS of the Relay UE receives the first information from the NAS of the Relay UE, the method further includes: The AS of the Relay UE sends a first message according to the first information, and the first message is any of the following: An RRC establishment request message; An RRC resumption request message.

15. The method of claim 14, wherein, The first message includes the first cause value.

16. An RRC connection apparatus in a SL Relay scenario, the apparatus comprising: The apparatus includes: A first receiving module, configured to, in a case where the Relay UE is in an IDLE or INACTIVE state, receive, by a non-access layer NAS of the Relay UE, first request information from an access layer AS of the Relay UE, the first request information being used to instruct the Relay UE to establish an NAS connection; A first sending module, configured to send, by the NAS of the Relay UE, first information to the AS of the Relay UE according to the first request information, the first information being used to establish an NAS connection; The first sending module is further configured to, after the NAS of the Relay UE receives first request information from the AS of the Relay UE, send, by the NAS of the Relay UE, a first cause value to the AS of the Relay UE; The first cause value is determined in any of the following manners: The NAS of the Relay UE determines, according to a first preset priority, a highest-priority cause value from one or more second cause values and one or more third cause values as the first cause value; In a case where the Relay UE itself needs to enter a connected state, the NAS of the Relay UE determines any one of the one or more third cause values as the first cause value; The second cause value is a cause value of the Remote UE, and the third cause value is a cause value used by the Relay UE when the Relay UE needs to enter a connected state.

17. The apparatus of claim 16, wherein, The first request information includes one or more of the following: a cause value; a bit value; an access type of the Remote UE; an access class of the Remote UE; a service type of the Remote UE.

18. The apparatus of claim 16, wherein, The first information is any of the following: a registration request message; a deregistration request message; a service request message; a control plane service request message; an RRC setup request message; an RRC resume request message.

19. The apparatus of claim 16, wherein, The first preset priority is configured in one of the following ways: preconfigured; configured by a network side.

20. The apparatus of claim 16, wherein the apparatus further includes a first determination module configured to determine, by a NAS of the Relay UE, a first access type and / or a first access class; the first sending module is further configured to send, by the NAS of the Relay UE, the first access type and / or the first access class to an AS of the Relay UE; and the apparatus further includes an execution module configured to perform, by the AS of the Relay UE, a UAC procedure.

21. A Relay UE, characterized by, A processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implement the steps of the RRC connection method in the SL Relay scenario according to any one of claims 1 to 15.

22. A readable storage medium, characterized by A readable storage medium stores a program or instructions, the program or instructions, when executed by a processor, implement the steps of the RRC connection method in the SL Relay scenario according to any one of claims 1 to 15.

Images