CN115696628A

CN115696628A - RRC (radio resource control) connection method and equipment under SL Relay scene

Info

Publication number: CN115696628A
Application number: CN202110849037.1A
Authority: CN
Inventors: 张奕忠; 康艳超; 郑倩
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-07-27
Filing date: 2021-07-27
Publication date: 2023-02-03
Also published as: WO2023005798A1

Abstract

The embodiment of the application provides an RRC connection method in an SL Relay scene, and belongs to the technical field of communication. The method comprises the following steps: under the condition that Relay UE is in IDLE state IDLE or 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, wherein the first request information is used for indicating the Relay UE to establish 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, wherein the first information is used for establishing NAS connection.

Description

RRC (radio resource control) connection method and equipment under SL Relay scene

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a RRC (radio resource control) connection method and equipment in an SL Relay scene.

Background

In a Radio Resource Control (RRC) connection establishment procedure in a Sidelink Relay (SL Relay) scenario, if a Relay terminal (i.e., relay user equipment, relay UE) does not enter a Radio Resource Control CONNECTED state (RRC _ CONNECTED) at a time when receiving a message of a Remote terminal (Remote UE), it needs to trigger establishment of its RRC connection at a Uu air interface, and then can provide a Relay service for the Remote UE. And details of the RRC connection establishment or RRC connection recovery procedure initiated by the specific Relay UE are not determined.

Disclosure of Invention

An object of the embodiments of the present application is to provide an RRC connection method and device in an SL Relay scenario, so as to solve the technical problem that the current network cannot reasonably control and admit an access request of Relay UE.

In a first aspect, an embodiment of the present application provides an RRC connection method in an SL Relay scenario, where the method includes:

when Relay UE is in IDLE or INACTIVE, receiving first request information by a NAS of the Relay UE, wherein the first request information is used for indicating the Relay UE to establish 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, wherein the first information is used for establishing NAS connection.

In a second aspect, an embodiment of the present application provides an RRC connection apparatus in an SL Relay scenario, where the apparatus includes:

a first receiving module, configured to receive, when Relay UE is IDLE or INACTIVE, first request information from an access stratum AS of the Relay UE by a non-access stratum NAS of the Relay UE, where the first request information is used to instruct the Relay UE to establish 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, where the first information is used to establish NAS connection.

In a third aspect, an embodiment of the present application provides a Relay UE, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps of the RRC connection method in the SL Relay scenario according to the first aspect.

In a fourth aspect, an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and the program or the instruction, when executed by a processor, implements the steps of the RRC connection method in the SL Relay scenario according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

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

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

In the embodiment of the application, the NAS of the Relay UE sends the first information for 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, and the network can reasonably control and accept the access request of the Relay UE.

Drawings

Fig. 1a is a schematic diagram of a conventional relay network structure;

fig. 1b is a schematic diagram illustrating an RRC connection establishment procedure in an SL Relay scenario;

fig. 2 is a schematic flowchart of an RRC connection method in an SL Relay scene according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of an application provided by an embodiment of the present application;

fig. 4 is a structural diagram of an RRC connection device in an SL Relay scenario according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of Relay UE provided in the embodiment of the present application;

fig. 6 is a schematic structural diagram of a Relay UE provided in the embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application are capable of operation in sequences other than those illustrated or described herein, and that the terms "first," "second," etc. are generally used in a generic sense and do not limit the number of terms, e.g., a first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/", and generally means that the former and latter related objects are in an "or" relationship.

Sidelink Relay mechanism

Relay (Relay) technology in a wireless communication system is to add one or more Relay nodes between a base station and a terminal, and is responsible for forwarding wireless signals one or more times, that is, wireless signals can reach the terminal through multiple hops.

The wireless relay technology can be used for expanding cell coverage, making up cell coverage blind spots, and simultaneously improving cell capacity through spatial resource multiplexing. For indoor coverage, the Relay technology can also play a role in overcoming penetration loss and improving indoor coverage quality.

Taking the simpler two-hop relay as an example, the wireless relay is to divide a base station-terminal link into two links, namely a base station-relay station and a relay station-terminal, so that there is an opportunity to replace a link with poor quality with two links with better quality, so as to obtain higher link capacity and better coverage.

Currently, a Relay supported in LTE is a UE-to-Network Relay, that is, one end of the Relay is connected to the UE, and the other end is connected to the Network side. The UE connected to the Relay is called a Remote UE (Remote UE).

The NR will also investigate how to support the UE-to-Network Relay mechanism, a typical scenario is shown in fig. 1 a. This is a typical UE-to-Network scenario, where a Remote UE needs to transmit data with a Network side, but finds a Relay UE as its Relay due to poor coverage, where a Uu interface is between the Relay UE and a base station, and a Sidelink (PC 5) interface is between the Relay UE and the Remote UE. Generally, relay UEs are open and can serve any Remote UE.

RRC connection establishment procedure in the sidelink Relay scenario, see fig. 1b:

and step 1. The remote UE and the Relay UE execute a discovery process and then establish the PC5 RRC connection.

And 2, the Remote UE sends an RRCSetuprequest message to the base station, and the base station replies the RRCSetupmessage to the Remote UE. Specifically, the two messages are relayed by Relay UE to base station or Remote UE. If Relay UE does not enter RRC _ CONNECTED at the moment of receiving the message of the Relay UE, the Relay UE needs to trigger to establish RRC connection of the Relay UE at a Uu air interface, and then Relay service can be provided for the Relay UE.

And step 3, establishing a Signaling Radio Bearer (SRB) 1 special Bearer between the base station and the Remote UE, wherein the SRB1 special Bearer of the Remote UE consists of two Radio Link Control (RLC) channels, namely a PC5 (between the Remote UE and the Relay UE) and a Uu (between the Relay UE and the base station). Specifically, two RLC channels are used for Remote UEs to send/receive SRB1 type RRC messages to/from the base station.

And 4. The remote UE sends RRCSetupcomplete message to the base station. Specifically, this message is relayed by the Relay UE to the base station.

And 5, activating safety between the remote UE and the base station. Activating secure messages and flows reuses existing mechanisms.

And 6, establishing an SRB2/DRB special bearer between the base station and the Remote UE, wherein the SRB2/DRB special bearer of the Remote UE consists of two RLC channels, namely PC5 (between the Remote UE and the Remote UE) and Uu (between the Remote UE and the base station). Specifically, the two RLC channels are used for the Remote UE to send/receive SRB2 type RRC/NAS messages and uplink and downlink service data to/from the base station. In particular, by reusing existing RRC reconfiguration mechanisms.

3.Cause value

Various Cause values are preconfigured in the current protocol as follows:

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}

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}

in step 2 of fig. 1b, a technical scenario is depicted: if Relay UE does not enter RRC _ CONNECTED at the time of receiving the message of the Remote UE, it needs to trigger the RRC connection established over the Uu air interface first, and then can provide the Relay service for the Remote UE. The details of the RRC connection establishment (for RRC IDLE) or RRC connection recovery (for RRC INACTIVE) procedure initiated by a specific Relay UE are not yet standardized.

Wherein, aiming at the technical scene, the detail related to discussion comprises the following steps: which cause value should be used by the Relay UE to initiate its RRC connection establishment or recovery procedure.

The RRC connection method in the SL Relay scenario provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

The technology described herein is not limited to a fifth-generation mobile communication (5 th-generation, 5G) system and a later-evolution communication system, and is not limited to an LTE/LTE evolution (LTE-a) system, and may also be used for 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.

The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system can implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA)), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX)), IEEE 802.20, flash-OFDM, and the like. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership project" (3 rd Generation Partnership project,3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3 GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.

Referring to fig. 2, an embodiment of the present application provides an RRC connection method in an SL Relay scenario, where the method includes:

step 201: under the condition that the Relay UE is IDLE or INACTIVE, the NAS of the Relay UE receives first request information from an AS of the Relay UE;

step 202: the NAS of the Relay UE sends first information to an AS of the Relay UE according to the first request information;

the first request message is used for instructing the Relay UE to establish a Non-Access Stratum (NAS) connection; the first information is used for establishing the NAS connection.

In one possible implementation, the first request information includes one or more of:

(1) A cause value;

the cause value may be an existing cause value comprising an existing RRC establishment cause value and a recovery (resume) cause value or a new cause value indicating that an RRC connection is established/recovered for the relay service;

(2) A bit value;

the bit value can be encoded in a plurality of ways:

mode 1: if the indication =0, indicating that the remote UE is a non-emergency service; if indication =1, it indicates that the remote UE is in emergency service.

Mode 2: if indication =0, indicating that the remote UE is a non-high priority service; if indication =1, it indicates that the remote UE is a high priority service.

Mode 3: if indication =0, indicating that the remote UE is a non-relay service; if indication =1, it indicates that the remote UE is a relay service.

(3) Access Category (Access Category) of a Remote terminal (Remote UE);

(4) Access class (Access identity) of Remote UE;

(5) Service type (service type) of Remote UE.

In one possible embodiment, the first information is one of:

(1) A REGISTRATION REQUEST message (REGISTRATION REQUEST);

(2) A DEREGISTRATION REQUEST message (DEREGISTRATION REQUEST);

(3) SERVICE REQUEST message (SERVICE REQUEST);

(4) CONTROL PLANE SERVICE REQUEST message (CONTROL plan SERVICE REQUEST);

(5) An RRC establishment request message;

(6) RRC resume request message.

In a possible implementation manner, 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 sends the first cause value to the AS of the Relay UE.

It should be noted that, in the embodiment of the present application, the NAS of the Relay UE sends the first cause value to the AS of the Relay UE while providing the first information, that is, the first cause value is not in the first information. )

In one possible embodiment, the first cause value is determined by any one of:

(1) Determining, by the NAS of the Relay UE, one or more second cause values and a cause value with the highest priority among one or more third cause values as a first cause value according to the first preset priority; the second cause value is a cause value of the Remote UE, the second cause value is carried in an RRC connection establishment request or an RRC connection recovery 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.

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

(3) When a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines a reason value corresponding to the first Remote UE for establishing connection as a first reason value;

it should be noted that in an actual scenario, there may be a case: the Relay UE has previously established an SL connection with UE 1 and UE 2, and then no traffic enters IDLE state. Now again a SL connection is established with UE 3, UE 4, which now requires the relay UE to establish an RRC connection. In this case, the first Remote UE to establish a connection refers to the first established UE of UE 3 and UE 4.

(4) Under the condition that a plurality of connection-establishing Remote UEs exist, determining any one reason value in a plurality of reason values corresponding to all the connection-establishing Remote UEs as a first reason value by the NAS of the Relay UE;

(5) When the Relay UE needs to enter a connection state, the NAS of the Relay UE determines any one of the one or more third cause values as a first cause value;

specifically, the requirement that the Relay UE itself enters into the connection includes: the Relay UE needs to send uplink data, or the Relay UE has NAS signaling to send, where the NAS signaling includes: REGISTRATION REQUEST; DERIGISTRATION REQUEST; SERVICE REQUEST; CONTROL plan SERVICE REQUEST.

(6) The NAS of the Relay UE determines a first reason value according to the first request information;

further, the first preset priority is configured in one of the following manners:

(1) Pre-configuring; the pre-configuration includes: universal Subscriber Identity Module (USIM); a SIM card; an Embedded-SIM (eSIM) card; SIM card other equivalents; universal Integrated Circuit Card (UICC); mobile Equipment (ME);

(2) Configured by the network side. The network side configuration comprises: a Policy Control Function (PCF) for configuration; application server provisioning, etc.

In a possible implementation manner, before the step of receiving, by the non-access stratum NAS of the Relay UE, the first request message from the access stratum AS of the Relay UE, the method further includes:

(1) Determining a first access type and/or a first access grade by the NAS of the Relay UE;

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

(3) The AS of the Relay UE executes a Unified Access Control (UAC) flow.

It should be noted that, in a manner that the NAS of the Relay UE determines the first access type and/or the first access class, the above-mentioned manner that the NAS of the Relay UE determines the first cause value may be referred to, and specifically, the determining, by the NAS of the Relay UE, the first access type includes any one of the following:

(1) Determining one or more second access types and the access type with the highest priority in one or more third access types as the first access type by the NAS of the Relay UE according to the second preset priority; the second access type is the access type of the Remote UE, and the third access type is the access type used by the Remote UE when the Remote UE needs to enter a connected state.

(2) The NAS of the Relay UE selects an access type with the highest priority from one or more second access types as a first access type according to a second preset priority;

(3) Under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, the NAS of the Relay UE determines the access type of the first Remote UE which establishes connection as a first access type;

(4) Under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, determining any one of access types of all the Remote UEs which establish connection as a first access type by the NAS of the Relay UE;

(5) When Relay UE needs to send uplink data, or when the Relay UE needs to enter a connected state, or the Relay UE initiates a mobility registration updating process, the NAS of the Relay UE determines any one of one or more third access types as a first access type;

(6) Determining a first access type by the NAS of the Relay UE according to the first request information;

(7) The NAS of the Relay UE determines a default (default) access type as a first access type;

the second preset priority is configured in one of the following manners:

(1) Pre-configuring; the pre-configuration includes: a USIM; a SIM card; an eSIM card; SIM card other equivalents; a UICC; ME;

(2) Configured by the network side. The network side configuration comprises: PCF carries on the disposition; application server provisioning, etc.

The default preset priority is configured in one of the following ways:

(1) Pre-configuring; the preconfiguration includes: a USIM; a SIM card; an eSIM card; SIM cards and other equivalent forms; a UICC; ME;

Specifically, the NAS of the Relay UE determining the first access class includes any one of:

(1) Determining one or more second access levels and the access level with the highest priority in the one or more third access levels as the first access level by the NAS of the Relay UE according to the third preset priority; the second access level is the access level of the Remote UE, and the third level is the access level used by the Remote UE under the condition that the Remote UE needs to enter a connected state.

(2) The NAS of the Relay UE selects an access grade with the highest priority from one or more second access grades as a first access grade according to a third preset priority;

(3) Under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, determining the access grade of the first Remote UE which establishes connection as a first access grade by the NAS of the Relay UE;

(4) Under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, the NAS of the Relay UE determines any one access grade of the access grades of all the Remote UEs which establish connection as a first access grade;

(5) The NAS of the Relay UE determines a third access grade of the Relay UE as a first access type under the condition that the Relay UE needs to enter a connected state;

(6) The NAS of the Relay UE determines a first access grade according to the first request information;

(7) The NAS of the Relay UE determines a default access grade as a first access grade;

the third preset priority is configured in one of the following manners:

(1) Pre-configuring; the pre-configuration includes: a USIM; a SIM card; an eSIM card; SIM cards and other equivalent forms; a UICC; ME;

(2) Configured by the network side. The network side configuration comprises: PCF carries out configuration; application server provisioning, etc.

The default access class is configured by one of:

In one possible embodiment, the first information comprises a first service type.

Specifically, the first service type is determined by any one of:

(1) Under the condition that a plurality of service types sent by Remote UE exist, determining the service type of the first Remote UE establishing connection as a first service type by NAS of the Remote UE;

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

(3) Under the condition that the Remote UE has service, determining a first service type by the NAS of the Remote UE according to the service type of the Remote UE;

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

(5) And the NAS of the Relay UE determines the first service type according to the first request information.

In one possible embodiment, 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, wherein the first message is any one of the following messages:

(1) An RRC establishment request message;

(2) RRC resume request message.

In a possible embodiment, the first message includes a first cause value;

the scheme of the present application is described below with reference to specific examples:

referring to fig. 3, the relay UE is in 5GMM-IDLE state. And according to the indication of the AS layer of the Relay UE, the NAS layer of the Relay UE determines a cause value.

0. Alternatively, existing mechanisms. The Remote UE and the Relay UE establish PC5 connection.

The relay UE receives an RRC connection setup request or an RRC connection resume request message from at least one of the one or more Remote UEs.

And 2, the AS layer of the Relay UE sends a piece of request information to the NAS layer of the Relay UE, and the request information indicates the NAS layer of the Relay UE to enter a 5GMM connection state. The request information includes at least one of:

(1) A cause value;

(2) A bit value;

(3) The type indication may include an Access Category of the Remote UE, an Access identity of the Remote UE, and a service type of the Remote UE;

3. optionally, the Relay UE performs a UAC procedure, where an Access Category (Access type) required for performing the UAC procedure is set according to the following manner:

(1) The NAS of the Relay UE determines the access types of one or more Relay UEs and the access type with the highest priority in the access types used by the one or more Relay UEs needing to enter the connection state as the access type needed by the UAC process according to the preset priority; the preset priority can pass through a USIM (Universal subscriber identity Module); a SIM card; an eSIM card; a SIM card; a UICC; ME, etc. or other equivalent forms are preconfigured or configured by the network side, for example: PCF carries out configuration; application server provisioning, etc.

(2) The NAS of the Relay UE selects an access type with the highest priority from the access types of one or more Remote UEs as an access type required for executing a UAC process according to the preset priority;

(3) Under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines the access type of the first Remote UE for establishing connection as the access type required by the UAC process;

(4) Under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines any one access type of the access types of all the Remote UEs for establishing connection as an access type required by the execution of a UAC (Universal authentication code) process;

(5) When Relay UE needs to send uplink data, or when Relay UE needs to enter a connection state, or the Relay UE initiates a mobility registration updating process, NAS of the Relay UE determines any one of one or more access types used by the Relay UE needing to enter the connection state as an access type needed for executing a UAC process;

(6) The NAS of the Relay UE determines an access type required for executing a UAC process according to request information received from the AS of the Relay UE;

(7) The NAS of the Relay UE determines a default (default) Access type as an Access Category required for executing a UAC (user Access control) process;

the NAS layer of the Relay UE triggers NAS information to enter a connection state, wherein the NAS information is one of the following items: service request message, registration message.

4.1 the NAS message is a SERVICE REQUEST, and the SERVICE type IE in the SERVICE REQUEST message has a SERVICE type information element set as one of the following:

(1) Under the condition that a plurality of service types sent by Remote UE exist, determining the service type of the first Remote UE establishing connection as the service type by the NAS of the Remote UE;

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

(3) Under the condition that the Remote UE has service, determining the service type by the NAS of the Remote UE according to the service type of the Remote UE;

(4) Determining a preset service type as the service type by the NAS of the Relay UE;

(5) The NAS of the Relay UE determines the service type according to the request information received from the AS of the Relay UE.

5, the AS layer of the Relay UE sends an RRCSetupRequest/RRCReseumRequest message, the message carries a cause value, and the method for determining the cause value is any one of the following methods:

(1) The NAS of the Relay UE determines one or more cause values carried in the RRC connection establishment request or the RRC connection recovery request and one or more cause values with the highest priority in the cause values used by the Relay UE which need to enter a connection state as a first cause value according to a preset priority; wherein the preset priority can pass through the USIM; a SIM card; an eSIM card; a SIM card; a UICC; ME, etc. or other equivalent forms are preconfigured or configured by the network side, for example: PCF carries out configuration; application server provisioning, etc.

(2) The NAS of the Relay UE selects a cause value with the highest priority from one or more cause values carried in the RRC connection establishment request or the RRC connection recovery request as the cause value according to the preset priority;

(3) When a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines the cause value of the first Remote UE for establishing connection as the cause value;

(4) When a plurality of Remote UEs establishing connection exist, the NAS of the Relay UE determines any one reason value of the reason values of all the Remote UEs establishing connection as the reason value;

(5) When the Relay UE needs to enter the connection state, the NAS of the Relay UE determines any one of the cause values used by one or more Relay UEs needing to enter the connection state as the cause value;

(6) The NAS of the Relay UE determines the reason value according to request information received from the AS of the Relay UE;

it should be noted that, in the RRC connection device in the SL Relay scenario provided in the embodiment of the present application, the execution main body may be the RRC connection device in the SL Relay scenario, or a control module in the RRC connection device in the SL Relay scenario, which is used for executing the RRC connection method in the SL Relay scenario. In the embodiment of the present application, an RRC connection device in an SL Relay scene provided in the embodiment of the present application is described by taking an example of a method for an RRC connection device in an SL Relay scene to execute an RRC connection in the SL Relay scene.

Referring to fig. 4, an RRC connection apparatus 500 in an SL Relay scene is provided in an embodiment of the present application, where the apparatus includes:

a first receiving module 401, configured to receive, when Relay UE is in an IDLE state IDLE or an INACTIVE state INACTIVE, first request information from an access stratum AS of the Relay UE by a non-access stratum NAS of the Relay UE, where the first request information is used to instruct the Relay UE to establish NAS connection;

a first sending module 402, 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, where the first information is used to establish NAS connection.

Optionally, the first request information includes one or more of:

a cause value;

a bit value;

access type of Remote UE;

access class of the Remote UE;

a service type of the Remote UE.

Optionally, the first information is any one of:

a registration request message;

a deregistration request message;

a service request message;

a control plane service request message;

an RRC establishment request message;

RRC resume request message.

Optionally, the first sending module is further configured to send the first cause value to the AS of the Relay UE by the NAS of the Relay UE.

Optionally, the first cause value is determined by any one of:

determining, by the NAS of the Relay UE, one or more second cause values and a cause value with a highest priority among the one or more third cause values as the first cause value according to a first preset priority;

the NAS of the Relay UE selects a reason value with the highest priority from one or more second reason values as the first reason value according to a first preset priority;

in the case that a plurality of Remote UEs for establishing connection exist, determining a cause value of the Remote UE for establishing connection as a first cause value by the NAS of the Relay UE;

when a plurality of connection-establishing Remote UEs exist, determining any one cause value of the cause values of all the connection-establishing Remote UEs as the first cause value by the NAS of the Relay UE;

when the Relay UE needs to enter a connected state, the NAS of the Relay UE determines any one reason value in one or more third reason values as the first reason value;

the NAS of the Relay UE determines the first reason value according to the first request information;

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.

Optionally, the first preset priority is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the apparatus further comprises:

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

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 the AS of the Relay UE.

The device also comprises an execution module used for the AS of the Relay UE to execute the UAC flow.

Optionally, the first determining module is configured to any one of:

determining, by the NAS of the Relay UE, one or more second access types and an access type with the highest priority among one or more third access types as the first access type according to a second preset priority;

the NAS of the Relay UE selects an access type with the highest priority from one or more second access types as the first access type according to a second preset priority;

under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines the access type of the Remote UE for establishing connection firstly as the first access type;

under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines any one access type of access types of all the Remote UEs for establishing connection as the first access type;

when the Relay UE needs to send uplink data, or when the Relay UE needs to enter a connected state, or 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;

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 the access type of the Remote UE, and the third access type is the access type used by the Relay UE when the Relay UE needs to enter a connected state.

Optionally, the second preset priority is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the default access type is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the first determining module is configured to:

determining, by the NAS of the Relay UE, one or more second access classes and an access class with a highest priority among the one or more third access classes as the first access class according to a third preset priority;

the NAS of the Relay UE selects an access grade with the highest priority from one or more second access grades as the first access grade according to a third preset priority;

under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Remote UE determines the access grade of the Remote UE for establishing connection at first as the first access grade;

under the condition that a plurality of Remote UEs for establishing connection exist, the NAS of the Relay UE determines any one access grade of access grades of all the Remote UEs for establishing connection as the first access grade;

the NAS of the Relay UE determines a third access class of the Relay UE as the first access type under the condition that the Relay UE needs to enter a connected state;

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 grade as the first access grade;

the second access class is the access class of the Remote UE, and the third class is the access class used by the Relay UE when the Relay UE needs to enter a connected state.

Optionally, the third preset priority is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the default access class is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the first information includes a first service type.

Optionally, the first determining module is further configured to determine any one of:

under the condition that a plurality of service types sent by Remote equipment (Remote) UE exist, determining the service type of the first Remote UE establishing connection as the first service type by the NAS of the Relay UE;

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

under the condition that the Remote UE has service, the NAS of the Remote UE determines the first service type according to the service type of the Remote UE;

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

and the NAS of the Relay UE determines the first service type according to the first request information.

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

an RRC establishment request message;

RRC resume request message.

Optionally, the first message includes the first cause value;

the RRC connection device in the SL Relay scenario in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine or a self-service machine, and the like, and the embodiment of the present application is not particularly limited.

The RRC connection device in the SL Relay scenario 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 is not specifically limited in the embodiment of the present application.

The RRC connection device in the SL Relay scenario provided in the embodiment of the present application can implement each process implemented by the method embodiments in fig. 2 to fig. 3, and for avoiding repetition, details are not repeated here

Optionally, as shown in fig. 5, an embodiment of the present application further provides a Relay UE 500, which includes a memory 501, a processor 502, and a program or an instruction stored in the memory 501 and executable on the processor 502, where the program or the instruction is executed by the processor 502 to implement each process of the RRC connection method embodiment in the SL Relay scenario, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

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

Fig. 6 is a schematic diagram of a hardware structure of an electronic device implementing the embodiment of the present application.

The electronic device 600 includes, but is not limited to: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

Those skilled in the art will appreciate that the electronic device 600 may further comprise a power source (e.g., a battery) for supplying power to the various components, and the power source may be logically connected to the processor 610 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 6 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.

The processor 610 is configured to receive, when Relay terminal Relay UE is in an IDLE state IDLE or an INACTIVE state INACTIVE, first request information from an access stratum AS of the Relay UE by a non-access stratum NAS of the Relay UE, where the first request information is used to instruct the Relay UE to establish NAS connection;

a processor 610, 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, where the first information is used to establish NAS connection.

Optionally, the first request information includes one or more of:

a cause value;

a bit value;

access type of Remote UE;

an access class of the Remote UE;

a service type of the Remote UE.

Optionally, the first information is any one of:

a registration request message;

a deregistration request message;

a service request message;

a control plane service request message;

an RRC establishment request message;

RRC resume request message.

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

Optionally, the first cause value is determined by any one of:

determining, by the NAS of the Relay UE, one or more second cause values and a cause value with the highest priority among one or more third cause values as the first cause value according to a first preset priority;

the second cause value is a cause value of the Remote UE, and the third cause value is a cause value used when the Relay UE needs to enter a connected state.

Optionally, the first preset priority is configured by one of:

pre-configuring;

configured by the network side.

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

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

Optionally, the processor 610 is configured to any one of:

determining, by the NAS of the Relay UE, one or more second access types and an access type with a highest priority among the one or more third access types as the first access type according to a second preset priority;

under the condition that a plurality of Remote UEs for establishing connection exist, determining the access type of the Remote UE for establishing connection as the first access type by the NAS of the Relay UE;

determining, by the NAS of the Relay UE, any one of one or more third access types as the first access type when the Relay UE needs to send uplink data, or when the Relay UE itself needs to enter a connected state, or when the Relay UE initiates a mobility registration update procedure;

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 needs to enter a connected state.

Optionally, the second preset priority is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the default access type is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the processor 610 is configured to any one of:

under the condition that a plurality of Remote UEs for establishing connection exist, determining the access grade of the Remote UE for establishing connection as the first access grade by the NAS of the Relay UE;

the NAS of the Relay UE determines a default access class as the first access class;

the second access level is the access level of the Remote UE, and the third level is the access level used by the Remote UE when the Remote UE needs to enter a connected state.

Optionally, the third preset priority is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the default access class is configured by one of:

pre-configuring;

configured by the network side.

Optionally, the first information includes a first service type.

Optionally, the processor 610 is configured to determine any of:

under the condition that the Remote UE has service, determining the first service type by the NAS of the Remote UE according to the service type of the Remote UE;

Optionally, the processor 610 is configured to, after the AS of the Relay UE receives first information from the NAS of the Relay UE, send a first message according to the first information, where the first message is any one of:

an RRC establishment request message;

RRC resume request message.

Optionally, the first message includes the first cause value;

optionally, the processor 610 is configured to:

the AS of the Relay UE receives the first access type and/or the first access class from the NAS of the Relay UE;

the processor 610 is configured to execute a unified access control UAC procedure for the AS of the Relay UE.

It is to be understood that, in the embodiment of the present application, the input Unit 604 may include a Graphics Processing Unit (GPU) 6041 and a microphone 6042, and the Graphics Processing Unit 6041 processes image data of a still picture or a video obtained by an image capturing apparatus (such as a camera) in a video capturing mode or an image capturing mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 607 includes a touch panel 6071 and other input devices 6072. A touch panel 6071 also referred to as a touch screen. The touch panel 6071 may include two portions of a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. The memory 609 may be used to store software programs as well as various data including, but not limited to, application programs and an operating system. The processor 610 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 610

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored in the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the RRC connection method embodiment in the SL Relay scenario, and can achieve the same technical effect, and in order to avoid repetition, the program or the instruction is not described herein again.

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 Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction to implement each process of the RRC connection method embodiment in the SL Relay scene, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

Embodiments of the present application also provide a computer program product stored in a non-volatile storage medium, the computer program product being configured to be executed by at least one processor to implement the steps of the method described above.

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

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one of 8230, and" comprising 8230does not exclude the presence of additional like elements in a process, method, article, or apparatus comprising the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may 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 instructions for enabling a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

Claims

1. A Radio Resource Control (RRC) connection method in a side link Relay (SL Relay) scene is characterized by comprising the following steps:

under the condition that Relay terminal Relay UE is in IDLE state IDLE or 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, wherein the first request information is used for indicating the Relay UE to establish NAS connection;

2. The method of claim 1, wherein the first request information comprises one or more of:

a cause value;

a bit value;

the access type of Remote terminal Remote UE;

access class of the Remote UE;

a service type of the Remote UE.

3. The method according to claim 1, wherein the first information is any one of:

a registration request message;

a deregistration request message;

a service request message;

a control plane service request message;

an RRC establishment request message;

RRC resume request message.

4. The method of claim 1, wherein after the step of the NAS of the Relay UE receiving the first request information from the AS of the Relay UE, the method further comprises: and the NAS of the Relay UE sends a first reason value to the AS of the Relay UE.

The AS sends the content of the first cause value to the network side i.e. written in the rights 16 and 17.

5. The method of claim 4, wherein the first cause value is determined by any one of:

in the case that a plurality of Remote UEs for establishing connection exist, determining, by the NAS of the Relay UE, a cause value corresponding to the Remote UE for establishing connection as the first cause value;

when a plurality of connection-establishing Remote UEs exist, determining any one cause value in a plurality of cause values corresponding to all the connection-establishing Remote UEs as the first cause value by the NAS of the Relay UE;

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.

6. The method of claim 5, wherein the first predetermined priority is configured by one of:

pre-configuring;

configured by the network side.

7. The method of claim 1, wherein prior to the step of the non-access stratum (NAS) of the Relay UE receiving the first request information from the Access Stratum (AS) of the Relay UE, the method further comprises:

the NAS of the Relay UE determines a first access type and/or a first access grade;

the NAS of the Relay UE sends the first access type and/or the first access class to an AS of the Relay UE;

and the AS of the Relay UE executes a Unified Access Control (UAC) flow.

8. The method of claim 7, wherein the NAS of the Relay UE determining the first access type comprises any one of:

under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, the NAS of the Relay UE determines the access type of the Remote UE which establishes connection firstly as the first access type;

under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, determining any one of access types of all the Remote UEs which establish connection as the first access type by the NAS of the Relay UE;

9. The method of claim 8, wherein the second predetermined priority is configured by one of:

pre-configuring;

configured by the network side.

10. The method of claim 8, wherein the default access type is configured by one of:

pre-configuring;

configured by the network side.

11. The method of claim 7, wherein the NAS of the Relay UE determining the first access class comprises any one of:

determining, by the NAS of the Relay UE, according to a third preset priority, one or more second access classes and an access class with a highest priority among the one or more third access classes as the first access class;

under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, determining the access grade of the Remote UE which establishes connection with the first one as the first access grade by the NAS of the Relay UE;

under the condition that a plurality of Remote UEs which establish connection with the Relay UE exist, the NAS of the Relay UE determines any one access grade of the access grades of all the Remote UEs which establish connection as the first access grade;

12. The method of claim 11, wherein the third predetermined priority is configured by one of:

pre-configuring;

configured by the network side.

13. The method of claim 11, wherein the default access class is configured by one of:

pre-configuring;

configured by the network side.

14. The method of claim 1, wherein the first information comprises a first service type.

15. The method of claim 14, wherein the first service type is determined by any one of:

under the condition that a plurality of service types sent by Remote UE exist, determining the service type of the first connection-establishing Remote UE as the first service type by the NAS of the Relay UE;

the NAS of the Relay UE determines any one of the service types carried in all the first RRC connection establishment requests or the first RRC connection restoration request messages as the first service type;

16. The method of claim 4, wherein after the AS of the Relay UE receives the first information from the NAS of the Relay UE, the method further comprises:

the AS of the Relay UE sends a first message according to the first information, wherein the first message is any one of the following items:

an RRC establishment request message;

RRC resume request message.

17. The method of claim 16, wherein the first message includes the first cause value.

18. An RRC connection apparatus in an SL Relay scenario, the apparatus comprising:

a first receiving module, configured to receive, when a Relay UE is in IDLE or INACTIVE, first request information from an access stratum AS of the Relay UE, where the first request information is used to indicate the Relay UE to establish NAS connection;

19. The apparatus of claim 18, wherein the first request information comprises one or more of:

a cause value;

a bit value;

access type of Remote UE;

an access class of the Remote UE;

a service type of the Remote UE.

20. The method of claim 118, wherein the first information is any one of:

a registration request message;

a deregistration request message;

a service request message;

a control plane service request message;

an RRC establishment request message;

RRC resume request message.

21. The apparatus of claim 18, wherein the first sending module is further configured to send the first cause value to the AS of the Relay UE after the NAS of the Relay UE receives the first request message from the AS of the Relay UE.

22. The apparatus of claim 21, wherein the first cause value is determined by any one of:

under the condition that a plurality of Remote UEs for establishing connection exist, determining a cause value corresponding to the Remote UE for establishing connection as a first cause value by the NAS of the Relay UE;

23. The apparatus of claim 22, wherein the first predetermined priority is configured by one of:

pre-configuring;

configured by the network side.

24. The apparatus of claim 18,

the apparatus further comprises a first determining module configured to determine a first access type and/or a first access class by the NAS of the Relay UE;

the first sending module is further configured to send the first access type and/or the first access class to an AS of the Relay UE by the NAS of the Relay UE;

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

26. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the RRC connection method in an SL Relay scenario according to any of claims 1 to 17.