WO2021134161A1

WO2021134161A1 - Rrc connection method, device and system

Info

Publication number: WO2021134161A1
Application number: PCT/CN2019/129781
Authority: WO
Inventors: 彭文杰; 罗海燕; 王君; 戴明增
Original assignee: 华为技术有限公司
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2021-07-08
Also published as: CN114846900A

Abstract

The embodiments of the present application provide an RRC connection method, a device and a system, so as to implement an RRC connection between a remote device and a radio access network device. The method provided in the present application comprises: a first terminal receiving an RRC setup request of a second terminal from the second terminal; and the first terminal sending the RRC setup request to a network device by means of a first SRB, the first SRB being located on a common control channel. The second terminal performs RRC signaling exchange with the radio access network device by reusing SRB0, SRB1 or SRB2 of the first terminal, helping the second terminal at the edge of a cell or outside the coverage of the cell to successfully access the radio access network device and communicate therewith.

Description

A RRC connection method, equipment and system

Technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a radio resource control (radio resource control, RRC) connection method, device, and system.

Background technique

In a wireless communication system, data communication between terminals can be carried out through network equipment, or communication between terminals can be directly carried out without the aid of network equipment. The wireless communication interface (such as the PC5 interface) between the terminals is similar to the air interface (such as the Uu interface) between the terminal and the wireless access network equipment (such as the base station). The link between the terminals may also be called a sidelink. A typical application scenario of sidelink communication is the Internet of Vehicles (V2X, V2X). In the Internet of Vehicles, each vehicle is a terminal, and data can be directly transmitted between vehicles through sidelink without going through network equipment, thereby effectively reducing communication delay.

The above-mentioned communication between terminals is also called relay technology. In the existing relay technology, it is stipulated that the second terminal, such as the remote device, can communicate with the base station through the first terminal, such as the relay device. For example, when a remote device needs to send user plane data or control plane data (such as RRC messages) to the base station, the remote device can communicate to the center through the wireless communication interface (such as PC5 port) between the remote device and the relay device. After the device sends user plane data or control plane data, the relay device can send the user plane data or control plane data of the remote device to the base station through the wireless communication interface between the relay device and the base station. Correspondingly, when the base station needs to send user plane data or control plane data to the remote device, the base station may also send the user plane data or control plane data to the remote device through the relay device.

How to ensure the effective establishment of the RRC connection between the remote device and the base station is a problem that the industry is looking forward to solving.

Summary of the invention

The embodiments of the present application provide an RRC connection method, device, and system to implement an RRC connection between a remote device and a base station.

In order to achieve the foregoing objectives, the embodiments of the present application provide the following technical solutions:

The first aspect of the embodiments of the present application provides an RRC connection method. The method may include: a first terminal receives an RRC establishment request of the second terminal from a second terminal. The first terminal sends the RRC establishment request to the network device through a first SRB; wherein, the first SRB is located in a common control channel. Based on the method provided in the first aspect, the second terminal may send an RRC message for sending to the wireless access network device to the first terminal, and send the RRC message to the wireless access network device through the first terminal. In this way, after receiving the RRC message sent by the second terminal, the first terminal sends the RRC message to the radio access network device to implement the RRC connection between the second terminal and the radio access network device.

In a first possible design of the first aspect, with reference to the first aspect, the first terminal sends the RRC establishment request and the identifier of the second terminal to the network device through the first SRB. In this way, when there are multiple second terminals, the above-mentioned identification of the second terminal may be used to enable the radio access network device to learn which second terminal the RRC establishment request is associated with.

In the second possible design of the first aspect, in combination with the first aspect or the first possible design of the first aspect, the first terminal receives the RRC setup message from the network device; the first terminal sends The second terminal sends the RRC setup message. In this way, the second terminal can learn that the wireless access network device agrees to access by the second terminal.

In a third possible design of the first aspect, in combination with the first aspect or the first possible design of the first aspect, the first terminal receives an RRC rejection message from the network device; the first terminal sends The second terminal sends the RRC reject message; and the first terminal releases the connection with the second terminal. In this way, the second terminal can learn that the wireless access network device rejects the access of the second terminal, so that the second terminal triggers the release of the connection with the first terminal.

In the fourth possible design of the first aspect, in combination with the first aspect or any one of the foregoing possible designs, the first terminal receives the scheduling request SR configuration of the first SRB from the network device; A terminal sends an SR to the network device based on the SR configuration. In this way, the first SRB can be associated with the SR configuration.

In the fifth possible design of the first aspect, in combination with the fourth possible design of the first aspect, the first terminal sends an SR to the network device based on the SR configuration, specifically including: When the first SRB has data to be transmitted and there is no scheduling resource, the first terminal sends the SR to the network device. In this way, the first terminal can send an SR to the radio access network device when required.

In the sixth possible design of the first aspect, in combination with the first aspect or any one of the possible designs of the first aspect described above, the first SRB corresponds to a logical channel group and is used for the first terminal to trigger a buffer state Report the BSR to request resource scheduling. In this way, the first SRB association can be associated with the logical channel group, thereby triggering the BSR.

In the seventh possible design of the first aspect, in combination with the first aspect or any one of the foregoing first aspects, the first terminal receives the second SRB and/or data radio bearer from the network device Logical channel information corresponding to the DRB, the second SRB is used for the second RRC message of the second terminal, the second SRB is located in a dedicated control channel or the second RRC message includes a non-access stratum NAS message. In this way, different SRBs or DRBs can be associated with logical channels, or different terminals can be associated with different logical channels.

In the eighth possible design of the first aspect, in combination with the first aspect or any one of the possible designs of the first aspect described above, the first terminal sends an RLC PDU to the network device, and the RLC PDU has an indication Information, used to indicate whether the first terminal has an adaptation layer. In this way, through the indication information on the RLC PDU, the network device can learn whether the first terminal has an adaptation layer, thereby improving communication efficiency.

In the second aspect of the embodiments of the present application, an RRC connection method is provided. The method may include: a network device receives an RRC establishment request of a second terminal from a first terminal through a first SRB; wherein, the first SRB is located in a public Control channel. Based on the method provided in the second aspect, the second terminal may send an RRC message for sending to the wireless access network device to the first terminal, and send the RRC message to the wireless access network device through the first terminal. In this way, after receiving the RRC message sent by the second terminal, the first terminal sends the RRC message to the radio access network device to implement the RRC connection between the second terminal and the radio access network device.

In a first possible design of the second aspect, with reference to the second aspect, the network device receives the RRC establishment request and the identifier of the second terminal from the first terminal through the first SRB.

In the second possible design of the second aspect, in combination with the second aspect or the first possible design of the second aspect, the network device sends an RRC setup message to the first terminal.

In the third possible design of the second aspect, in combination with the second aspect or the first possible design of the second aspect, the network device sends an RRC rejection message to the first terminal.

In the fourth possible design of the second aspect, in combination with the second aspect or any one of the foregoing possible designs, the network device sends the scheduling request SR configuration of the first SRB to the first terminal; the network The device receives an SR based on the SR configuration from the first terminal.

In the fifth possible design of the second aspect, in combination with the fourth possible design of the second aspect, the network device receives the data sent by the first terminal when the first SRB has data to be transmitted and no scheduling resources are available. The SR.

In the sixth possible design of the second aspect, in combination with any one of the foregoing possible designs of the second aspect or the first aspect, the first SRB corresponds to a logical channel group and is used to trigger a buffer status report BSR to request resources Scheduling.

In the seventh possible design of the second aspect, in combination with any one of the foregoing possible designs of the second aspect or the first aspect, the network device sends a second SRB and/or a data radio bearer to the first terminal Logical channel information corresponding to the DRB, the second SRB is used for the second RRC message of the second terminal, the second SRB is located in a dedicated control channel or the second RRC message includes a non-access stratum NAS message.

In the eighth possible design of the second aspect, in combination with any one of the foregoing possible designs of the second aspect or the first aspect, the network device receives an RLC PDU from the first terminal, and the RLC PDU has an indication Information used to indicate whether the first terminal has an adaptation layer.

The third aspect of the embodiments of the present application further provides an RRC connection method. The method may include: the second terminal sends the RRC establishment request of the second terminal to the first terminal. Based on the method provided in the third aspect, the second terminal may send an RRC message for sending to the wireless access network device to the first terminal, and send the RRC message to the wireless access network device through the first terminal. In this way, after receiving the RRC message sent by the second terminal, the first terminal sends the RRC message to the radio access network device to implement the RRC connection between the second terminal and the radio access network device.

In a possible design of the third aspect, in combination with the third aspect, the second terminal receives an RRC rejection message from the first terminal; and the second terminal triggers a connection with the first terminal freed. In this way, the second terminal can learn that the wireless access network device rejects the access of the second terminal, so that the second terminal triggers the release of the connection with the first terminal.

In the fourth aspect of the embodiments of the present application, an RRC connection method is further provided. The method may include: a first terminal receives an RRC establishment request of the second terminal from a second terminal; and the first terminal sends to the network The device sends a first RRC message, where the first RRC message includes the RRC establishment request. Based on the method provided in the fourth aspect, the second terminal may send an RRC message for sending to the wireless access network device to the first terminal, and send the RRC message to the wireless access network device through the first terminal. In this way, after receiving the RRC message sent by the second terminal, the first terminal sends the RRC message to the radio access network device to implement the RRC connection between the second terminal and the radio access network device.

In the first possible design of the fourth aspect, with reference to the fourth aspect, the first RRC message further includes the identity of the second terminal. In this way, when there are multiple second terminals, the above-mentioned identification of the second terminal may be used to enable the radio access network device to learn which second terminal the RRC establishment request is associated with.

In the second possible design of the fourth aspect, in combination with the fourth aspect or the first possible design of the fourth aspect, the first terminal receives a second RRC message from the network device, and the second RRC The message includes an RRC setup message; and the first terminal sends the RRC setup message to the second terminal. In this way, the second terminal can learn that the wireless access network device agrees to access by the second terminal.

In a third possible design of the fourth aspect, in combination with the fourth aspect or the first possible design of the fourth aspect, the first terminal receives a third RRC message from the network device, and the third RRC The message includes an RRC rejection message; and the first terminal sends the RRC rejection message to the second terminal. In this way, the second terminal can learn that the wireless access network device rejects the access of the second terminal, so that the second terminal triggers the release of the connection with the first terminal.

In the fourth possible design of the fourth aspect, in combination with the fourth aspect or any one of the above possible designs, the first terminal receiving the RRC establishment request from the second terminal specifically includes: the first terminal receiving the RRC establishment request from the second terminal The second terminal receives the sidelink RRC message, where the sidelink RRC message includes the RRC establishment request.

In the fifth possible design of the fourth aspect, in combination with the third or fourth possible design of the fourth aspect, the first terminal sends the RRC establishment request to the second terminal, which specifically includes: The first terminal sends a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC setup message; or, the first terminal sends the RRC reject message to the second terminal, which specifically includes: The first terminal sends a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC rejection message.

In the sixth possible design of the fourth aspect, in combination with the fourth aspect or any one of the foregoing possible designs of the fourth aspect, the first terminal receives the second SRB and/or data radio bearer from the network device Logical channel information corresponding to the DRB, the second SRB is used for the fifth RRC message of the second terminal, the second SRB is located in a dedicated control channel or the fifth RRC message includes a non-access stratum NAS message. In this way, different SRBs or DRBs can be associated with logical channels, or different terminals can be associated with different logical channels.

The fifth aspect of the embodiments of the present application further provides an RRC connection method. The method may include: a network device receives a first RRC message from a first terminal, where the first RRC message includes an RRC establishment request of the second terminal. In this way, after receiving the RRC message sent by the second terminal, the first terminal sends the RRC message to the radio access network device to implement the RRC connection between the second terminal and the radio access network device.

In the first possible design of the fifth aspect, with reference to the fifth aspect, the first RRC message further includes the identity of the second terminal.

In the second possible design of the fifth aspect, in combination with the fifth aspect or the first possible design of the fifth aspect, the network device sends a second RRC message to the first terminal, and the second RRC The message includes the RRC setup message.

In the third possible design of the fifth aspect, in combination with the fifth aspect or the first possible design of the fifth aspect, the network device sends a third RRC message to the first terminal, and the third RRC The message includes an RRC rejection message.

In the fourth possible design of the fifth aspect, in combination with the fifth aspect or any of the above possible designs, the network device sends the second SRB and/or the logical channel corresponding to the data radio bearer DRB to the first terminal Information, the second SRB is used for the fifth RRC message of the second terminal, the second SRB is located on a dedicated control channel or the fifth RRC message includes a non-access stratum NAS message.

In a sixth aspect, a communication device is provided, including: a processor and a memory; the memory is used to store computer execution instructions, and when the communication device is running, the processor executes the computer execution instructions stored in the memory to enable the The communication device executes the RRC connection method described in any of the foregoing aspects or any possible design in any of the foregoing aspects.

In a seventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium stores instructions, which when run on a computer, enables the computer to execute any of the above-mentioned aspects or any of the above-mentioned aspects It is possible to design the RRC connection method described.

In an eighth aspect, a computer program product containing instructions is provided, which when running on a computer, enables the computer to execute the RRC connection method described in any of the foregoing aspects or any possible design in any of the foregoing aspects.

In a ninth aspect, a chip system is provided. The chip system includes a processor and a communication interface for supporting a communication device to implement the functions involved in any of the foregoing aspects. In a possible design, the chip system further includes a memory, and the memory is used to store program instructions and data necessary for the communication device. The chip system can be composed of chips, or include chips and other discrete devices.

Among them, the technical effects brought by any of the design methods of the sixth aspect to the ninth aspect may refer to the technical effects brought about by the RRC connection method described in any possible design of any of the above aspects, and will not be repeated here.

Description of the drawings

FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the application;

Figure 2 is a schematic diagram of a protocol stack provided by an embodiment of the application;

FIG. 3 is a schematic diagram of the composition of a communication device provided by an embodiment of the application;

FIG. 4 is a flowchart of an RRC connection method provided by an embodiment of this application;

FIG. 5 is a schematic diagram of another protocol stack provided by an embodiment of the application;

FIG. 6 is a flowchart of another RRC connection method provided by an embodiment of this application;

FIG. 7 is a schematic diagram of yet another protocol stack provided by an embodiment of the application;

FIG. 8 is a schematic diagram of the composition of another communication device provided by an embodiment of the application;

FIG. 9 is a schematic diagram of the composition of still another communication device provided by an embodiment of this application;

FIG. 10 is a schematic diagram of the composition of a communication system provided by an embodiment of this application.

Detailed ways

First, in order to facilitate the understanding of the embodiments of the present application, some protocol stacks involved in the embodiments of the present application are described:

RRC layer: Mainly responsible for generating RRC messages, measurement configuration and reporting, and can also be responsible for other functions: such as sending dedicated non-access stratum (NAS) messages, transmitting terminal (user equipment, UE) access capability information, etc. . RRC messages are classified into cell-level and UE-level. For example, system broadcast messages and the like belong to cell-level RRC messages, and RRC connection control, etc., belong to UE-level RRC messages.

UE-level RRC messages are transmitted using signaling radio bearer (SRB). The existing agreement defines three SRBs: SRB0, SRB1, and SRB2. SRB0: A radio bearer that exists by default. RRC messages that use SRB0 are transparent at the PDCP layer. There is neither integrity protection nor encryption and decryption processing. These messages are all sent using a common control channel (CCCH). SRB1: used to send RRC messages, these messages are all sent using a dedicated control channel (dedicated control channel, DCCH). SRB2: Used to send RRC messages including NAS messages. The priority of SRB2 is lower than that of SRB1, and SRB2 is always configured after security activation. In addition to SRB0, each SRB has a corresponding PDCP layer for integrity protection, encryption and decryption, and each PDCP layer has 1 or 2 corresponding RLC layers.

PDCP layer: mainly processes RRC messages from the control plane and IP packets from the data plane. Its functions include: header compression and decompression, encryption/decryption, integrity protection, transmission of user data and control plane data, reordering and Retransmission processing, etc.

RLC layer: Mainly responsible for segmentation/cascading and reorganization of RLC service data unit (SDU), error correction through automatic repeat request (ARQ), and RLC protocol data unit (protocol data unit) , PDU) perform reordering, duplicate packet detection, and re-segment RLC PDU.

MAC layer: It is mainly responsible for matching logical channels and transmission channels, multiplexing multiple MAC SDUs belonging to one or different logical channels to the same MAC PDU, and sending them to the PHY (physical) layer, through the hybrid automatic repeat request ( Hybrid automatic repeat request, HARQ) to perform error correction, scheduling processing, logical channel priority processing, scheduling information reporting, random access process processing, etc.

PHY layer: Creates, maintains, and tears down the physical links required to transmit data, and provides mechanical, electronic, functional and standardized characteristics. Simply put, the PHY layer ensures that the original data can be transmitted on various physical media.

Term explanation:

Broadcast communication, unicast communication and multicast communication are supported on Sidelink.

Broadcast communication is similar to the base station broadcasting system information, that is, the terminal does not encrypt the data of the broadcast service, and any other terminal within the effective receiving range can receive the data of the broadcast service if it is interested in the broadcast service.

Unicast communication is similar to data communication after the RRC connection is established between the terminal and the base station, and the unicast connection between the terminals is required to be established first. After the unicast connection is established, the aforementioned terminal may perform data communication based on the negotiated identifier, and the data may be encrypted or unencrypted. Compared with broadcast communication, in unicast communication, unicast communication is generally performed between terminals that have established a unicast connection.

Multicast communication refers to communication between all terminals in a communication group, and any terminal in the group can send and receive data of the multicast service.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

The solution provided by the embodiments of the present application can be applied to the relay system shown in FIG. 1. The relay system can be a long term evolution (LTE) or a new radio (NR) system to implement remote RRC connection between equipment and wireless access network equipment. As shown in Figure 1, the relay system may include remote equipment, relay equipment, and wireless access network equipment. Among them, the remote device may refer to a device far away from the wireless access network device. The remote device cannot be directly connected to the wireless access network device, but is connected to the wireless access network device through one or more relay devices. The remote device can establish a wireless communication interface (such as PC5 port or sidelink) with the relay device, and the relay device closest to the wireless access network device can establish a wireless communication interface with the wireless access network device (such as LTE air interface or NR air interface). It should be noted that the network architecture shown in Figure 1 is only an exemplary architecture diagram. Although not shown, in addition to the network functional entities shown in Figure 1, the network shown in Figure 1 may also include other functional entities, such as: core network Network elements, etc., are not restricted.

Exemplarily, the remote device in FIG. 1 may be a remote user equipment (remote user equipment, remote UE), such as a wearable device (smart watch, smart bracelet, etc.), or smart furniture (or Home appliances), cars in the Internet of Vehicles, robotic arms in the industrial Internet, smart refueling equipment and other devices that are far away from the wireless access network equipment and need to be connected to the wireless access network equipment through a relay device.

The relay device in Figure 1 can be a relay user equipment (relay UE), for example, it can be a variety of handheld devices, vehicle-mounted devices, wearable devices, computing devices or connected to wireless modems with wireless communication functions. Other processing equipment; may also include subscriber units, cellular phones, smart phones, wireless data cards, personal digital assistants (PDAs), computers, tablet computers, and wireless Modem, handheld, laptop computer, cordless phone or wireless local loop (WLL) station, machine type communication (MTC) Terminals, mobile stations (Mobile Station, MS), etc., are not restricted.

The radio access network device in Figure 1 can also be named as an access network device, which is mainly used to implement wireless physical entity functions, resource scheduling and wireless resource management, wireless access control, and mobility management; exemplary, wireless The access network equipment may be a radio access network (RAN) next-generation base station (generation nodeB, gNB), or an LTE base station eNB or any other access unit.

Taking the remote device communicating with the wireless access network device through a relay device as an example, a protocol stack as shown in FIG. 2 can be established between the remote device, the relay device, and the wireless access network device. As shown in Figure 2, the remote device may include an RRC layer, a V2X layer, an SL-PDCP layer, an SL-RLC layer, an SL-MAC layer, and an SL-PHY layer. The relay device can include V2X layer, SL-PDCP layer, SL-RLC layer, SL-MAC layer, SL-PHY layer, and can also include adaptation layer, RRC layer, RLC layer, MAC layer, PHY layer . The access network equipment may include the RRC layer, the adaptation layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer. In the embodiments of the present application, the V2X layer can also be understood as the PC5 signaling layer, such as the PC5 signaling protocol (PC5 signaling protocol). Exemplarily, the RRC layer of the remote device corresponds to the RRC layer of the radio access network device, and the wireless communication interface technology between the remote device and the radio access network device, such as LTE or NR air interface technology, is used between the two. For example, it can be called Uu port. Exemplarily, the V2X layer, SL-PDCP layer, SL-RLC layer, SL-MAC layer, SL-PHY layer and the V2X layer, SL-PDCP layer, SL-RLC layer, SL- The MAC layer and the SL-PHY layer correspond to each other. These protocol layers adopt the wireless communication interface technology between the remote device and the relay device, such as PC5 port or sidelink or D2D air interface technology. The adaptation layer, RRC layer, RLC layer, MAC layer, PHY layer and the adaptation layer of radio access network equipment, RRC layer, RLC layer, MAC layer, and PHY layer correspond to each other. These protocol layers use relay equipment and wireless Wireless communication interface technology between network devices.

It should be noted that the network element, the interface name between each network element, and the naming of each protocol stack in the above-mentioned Figure 1 architecture are just an example. The specific implementation of the network element, the interface name between the network elements, and the protocol stack can be Other names are not specifically limited in the embodiments of this application.

Exemplarily, the remote device, relay device, and wireless access network device in FIG. 1 may be referred to as communication devices or include communication devices (such as chip or system-on-chip) for implementing the RRC connection method provided in the embodiments of the present application. Etc.), in order to implement the RRC connection method provided in the embodiments of the present application, these communication devices may include the components shown in FIG. 3. FIG. 3 is a schematic diagram of the composition of a communication device 300 according to an embodiment of the application. As shown in FIG. 3, the communication device 300 includes at least one processor 301, a communication line 302, and at least one communication interface 303; further, it may also include a memory 304. Exemplarily, the processor 301, the memory 304, and the communication interface 303 may be connected through a communication line 302. In the embodiments of the present application, at least one may be one, two, three, or more, which is not limited in the embodiments of the present application.

In the embodiment of the present application, the processor 301 may be a central processing unit (CPU), a general-purpose processor network processor (NP), a digital signal processor (DSP), or a micro-processing unit. Device, microcontroller, programmable logic device (PLD) or any combination of them. The processor may also be any other device with processing functions, such as a circuit, a device, or a software module.

In the embodiment of the present application, the communication line 302 may include a path for transmitting information between components included in the communication device.

In the embodiment of the present application, the communication interface 303 is used to communicate with other devices or communication networks (such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.). The communication interface 303 may be a module, a circuit, a transceiver or any device capable of realizing communication.

In the embodiment of the present application, the memory 304 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and/or instructions, and may also be a random access memory (random access memory). , RAM) or other types of dynamic storage devices that can store information and/or instructions, and can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory only memory, CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store The desired program code in the form of instructions or data structures and any other medium that can be accessed by the computer, but not limited to this.

In a possible design, the memory 304 may exist independently of the processor 301, that is, the memory 304 may be a memory external to the processor 301. In this case, the memory 304 may be connected to the processor 301 through the communication line 302 for storing instructions Or program code. When the processor 301 calls and executes the instructions or program codes stored in the memory 304, it can implement the RRC connection method provided in the following embodiments of the present application. In another possible design, the memory 304 can also be integrated with the processor 301, that is, the memory 304 can be an internal memory of the processor 301. For example, the memory 304 is a cache that can be used to temporarily store some data and/ Or instruction information, etc.

As an implementable manner, the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3. As another achievable manner, the communication device 300 may include multiple processors, such as the processor 301 and the processor 307 in FIG. 3. As yet another achievable manner, the communication apparatus 300 may further include an output device 305 and an input device 306. Exemplarily, the input device 306 may be a device such as a keyboard, a mouse, a microphone, or a joystick, and the output device 305 may be a device such as a display screen and a speaker.

It should be noted that the aforementioned communication device 300 may be a general-purpose device or a special-purpose device. For example, the communication device 300 may be a desktop computer, a portable computer, a network server, a PDA, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure in FIG. 3. The embodiment of the present application does not limit the type of the communication device 300. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

In the following, with reference to FIG. 1, taking the remote device as the second terminal and a relay device directly connected to the remote device as the first terminal as an example, the RRC connection method provided in the embodiment of the present application will be described in detail. It should be noted that the name of the message between each network element or the name of each parameter in the message in the following embodiments of the present application is just an example, and other names may also be used in specific implementations. The embodiments of the present application do not make specific details about this. limited.

FIG. 4 is an RRC connection method provided by an embodiment of this application, which is used to implement an RRC connection between a second terminal and a network device. The method can be executed interactively by the first terminal, the second terminal, and the network device. Exemplarily, the first terminal is a relay device, the second terminal is a remote device, the network device is a wireless access network device, and a wireless communication interface is established between the first terminal and the second terminal, such as a PC5 port or a side chain A sidelink (SL) or other device-to-device (D2D) link, the first terminal and the second terminal can communicate with each other through a PC5 port or a sidelink or D2D link. A wireless communication interface, such as an LTE air interface or an NR air interface, is established between the first terminal and the wireless access network device. Exemplarily, the LTE air interface may be a Uu interface, and the first terminal and the radio access network device may communicate with each other through the LTE air interface or the NR air interface. As shown in Figure 4, the method may include the following steps.

401. The first terminal receives an RRC establishment request from the second terminal.

402. The first terminal sends an RRC establishment request to the radio access network device through the first SRB.

The above steps are mainly described from the first terminal. It can be understood that, as far as the network is concerned, the radio access network receives the RRC establishment request of the second terminal from the first terminal through the first SRB. As far as the second terminal is concerned, the second terminal sends the RRC establishment request of the second terminal to the first terminal, for the first terminal to send the foregoing RRC establishment request to the wireless network device through the first SRB.

In the embodiment of the present invention, the second terminal can reuse the SL-SRB0 of the sidelink unicast connection to send the RRC establishment request to the first terminal. The SL-SRB0 is used to carry the sidelink unicast connection between the second terminal and the first terminal. High layer signaling or SL RRC signaling. Optionally, in order to allow the first terminal to recognize whether the signaling for unicast connection or the signaling used for communication between the second terminal and the radio access network device is sent through the SL-SRB0, the first terminal or Indication information is added to the header of the SL RLC layer of the second terminal. When the first terminal receives the instruction information sent by the second terminal, it can learn that this is an RRC message sent by the second terminal to the radio access network device, so that the RRC message is further forwarded to the radio access network device.

Exemplarily, the foregoing indication information may be a binary bit number of 0 or 1, or other symbols. Specifically, which symbol is used to represent the indication information may be pre-defined by the agreement, which is not limited in the embodiment of the present application. For example, taking the number of bits "1" to indicate that the RRC message comes from the second terminal as an example, the second terminal may include the number of bits "1" in the SL RLC header of the data when the data is processed by the SL RLC layer, and then go through the subsequent steps. The processing is sent to the first terminal.

Exemplarily, the foregoing RRC setup request (RRC setupRequest) may be generated by the RRC layer of the second terminal, and the RRC layer of the second terminal corresponds to the RRC layer of the radio access network device. The RRC establishment request may be used for the second terminal to request the establishment of an RRC connection with the radio access network device. Exemplarily, the RRC establishment request can be replaced by an RRC connection request (RRC connection request), or an RRC reestablishment request (RRC connection reestablishment request or RRC reestablishment request), or an RRC connection restoration request or an RRC restoration request (RRC). connection resume request or RRC resume request) or other request messages used to establish an RRC connection. The foregoing RRC requests can be collectively referred to as RRC messages, which are not limited in the present invention.

It can be understood that the data sent by the second terminal to the first terminal may include the foregoing RRC message. For example, the data may include a data packet header and a payload, and the above-mentioned RRC message may be included in the payload of the data. Specifically, with reference to Figure 2, the second terminal may process the above-mentioned data through the SL-RLC layer, SL-MAC layer, and SL-PHY layer of the second terminal, and then forward the data to the first terminal through the channel between the second terminal and the first terminal. Terminal sent. Optionally, in order to make the data processed by the SL-RLC layer, SL-MAC layer, and SL-PHY layer of the second terminal suitable for transmission on this channel, the SL-RLC layer, SL-MAC layer, and SL-PHY layer of the second terminal -The specific format of the PHY layer protocol stack is specified by the wireless communication interface protocol between the second terminal and the first terminal. In the embodiments of this application, the data processed by the PDCP layer can be called PDCP protocol data unit (PDU), the data processed by the RLC layer can be called RLC PDU, and the data processed by the MAC layer can be called It is MAC PDU.

Exemplarily, the RRC message included in the foregoing data is unchanged after being processed by different protocol layers, and the header of the corresponding protocol layer may be added after the data has passed through different protocol layers. For example, after the data is processed by the PDCP layer, a PDCP header will be added, which can include the PDCP sequence number; later, when the data is processed by the MAC layer, a MAC header will be added, and the MAC header can include LCID, source address ( One or more of the source address field and the target address (target address) field. Since the above data is sent by the second terminal to the first terminal, the source address field may include the part of the layer 2 identifier allocated by the second terminal for the unicast connection between the second terminal and the first terminal, and the destination address field It may include the part of the layer 2 identifier allocated by the first terminal for the unicast connection. Exemplarily, the LCID included in the MAC header can be used to identify the logical channel for data transmission. The layer 2 identifier can be used to identify the first terminal or the second terminal in the unicast connection. In the embodiment of the present application, the above layer 2 identifier can be the identifier of the terminal on the channel, for example, the terminal is on the PC5 port or the sidelink sidelink Or the ID of the D2D link.

Optionally, before step 401, the second terminal discovers the first terminal and selects or reselects the first terminal. After selecting the first terminal, the second terminal establishes a sidelink unicast connection with the first terminal.

Exemplarily, the first SRB is located on the common control channel, or SRB0. For example, when the first terminal changes from an idle state to a connected state, it may perform random access first to obtain uplink synchronization. Subsequently, an RRC establishment request is sent to the radio access network device through SRB0 to establish an RRC connection such as a control plane. In this embodiment, the second terminal establishes a control plane connection with the wireless access network device through the first terminal. When transmitting the RRC signaling of the second terminal, the sidelink SRB (SL-SRB0) between the second terminal and the first terminal and the SRB0 between the first terminal and the radio access network device are reused. It can be understood that the reuse of the SRB of the first terminal in the embodiment of the present invention (such as the reuse of SRB0, SRB1, or SRB2) refers to the reuse of part of the protocol stack of the SRB between the first terminal and the radio access network device, such as the RLC layer, MAC Layer, PHY layer. Specifically, the SRB-based communication between the second terminal and the radio access network device may reuse the SRB-based communication between the first terminal and the radio access network device. It can be understood that the foregoing reuse action may also be a multiplexing action, such as multiplexing at least one of SRB0, SRB1, and SRB2 of the first terminal, or multiplexing the sidelink SRB between the first terminal and the second terminal.

Specifically, the first terminal reuses SRB0 to send the RRC connection request of the second terminal to the radio access network device. In the prior art, the connected terminal cannot send signaling to the radio access network device through SRB0. This embodiment introduces a resource scheduling request mechanism to realize that the first terminal in the connected state sends the foregoing RRC connection request through SRB0. Two implementation methods are listed as follows:

Realization method one,

The first terminal receives the scheduling request SR configuration of the first SRB from the radio access network device; and

The first terminal sends an SR to the wireless access network device based on the SR configuration.

Exemplarily, the SR configuration is introduced for the first SRB in this embodiment, that is, the radio access network device provides the SR configuration of the first SRB for the first terminal. Optionally, when the first SRB has data to be transmitted and there is no scheduling resource, the first terminal sends an SR to the radio access network device. For example, when the first terminal in the connected state has SRB0 signaling that needs to be sent, and there are currently no available resources, the first terminal may send an SR to the radio access network device according to the SR configuration. Furthermore, the introduction of SR configuration for SRB0 can also be understood as the SR configuration introduced by the first terminal to forward the RRC connection request of the second terminal to the radio access network device.

Realization method two,

The first SRB corresponds to a logical channel group and is used by the first terminal to trigger a buffer status report BSR to request resource scheduling.

Exemplarily, in this embodiment, the corresponding logical channel group is configured for SRB0. For example, the wireless access network device configures the corresponding logical channel group for SRB0 of the first terminal, so that the first terminal can request resource scheduling by triggering the BSR. Specifically, the radio access network device sends the configuration of the logical channel group corresponding to SRB0 to the first terminal. When SRB0 has data to be transmitted and needs to request scheduling, the first terminal sends a BSR to the radio access network device, and the BSR carries the indication information of the foregoing logical channel group. It can be understood that the logical channel corresponding to the above SRB0 is logical channel 0, which is not limited in the present invention. Exemplarily, the logical channel group corresponding to the SRB0 configuration of the first terminal may be 1. When there is data to be transmitted on SRB0 that needs to be scheduled to request scheduling, the BSR may be reported to the base station, and the logical channel group may be carried in the BSR. Indication information and corresponding cache status information.

In a scenario of the embodiment of the present invention, there may be multiple second terminals accessing the wireless access network device through the first terminal. In order to enable the first terminal to distinguish between different second terminals, the first terminal is connected to the wireless access network. When the device sends the RRC connection request of the second terminal, it needs to carry the identification (identify, ID) allocated by the first terminal to the second terminal, which is used to identify which second terminal is in the communication process between the first terminal and the wireless access network device . In this embodiment, the identifier may be an index (index). Specifically, after the first terminal receives the RRC establishment request from the second terminal, it will allocate the above-mentioned identifier to the second terminal, and add the identifier to the header of the adaptation layer located on the RLC layer of the first terminal, and then compare it with the first terminal. The RRC connection request of the two terminals is sent to the radio access network device together.

Optionally, when the wireless access network device accepts the access of the second terminal, after step 402, the method may further include:

The first terminal receives the RRC establishment message from the radio access network device; and,

The first terminal sends the foregoing RRC establishment message to the second terminal.

Optionally, when the wireless access network device rejects the access of the second terminal, after step 402, the method may further include:

The first terminal receives an RRC rejection message from the radio access network device;

The first terminal sends the above-mentioned RRC rejection message to the second terminal; and

The first terminal releases the connection with the second terminal.

In this embodiment, if the radio access network device rejects the access of the second terminal, the second terminal will not send the completion of the RRC establishment, but will trigger the unicast connection release procedure with the first terminal.

Exemplarily, the radio access network device may also receive the second terminal identifier, so as to associate the second terminal identifier with the RRC establishment request, and maintain the second terminal identifier as the context of the second terminal; or the second terminal identifier and the RRC Reject the request for association. For example, after receiving the RRC establishment request of the second terminal, the radio access network device determines whether to allow the second terminal to access. If allowed, the radio access network device sends the RRC setup message of the second terminal to the first terminal, and carries the terminal identifier of the second terminal on the head of the adaptation layer of the radio access network device. The first terminal receives the terminal identification of the second terminal and the corresponding RRC setup message from the radio access network device, and can know which second terminal is corresponding to the terminal identification, so that the unicast connection with the second terminal can be used Send the RRC setup message to the second terminal. If not allowed, the radio access network device sends an RRC rejection message of the second terminal to the first terminal, and carries the terminal identifier of the second terminal on the head of the adaptation layer of the radio access network device. In the same way, the first terminal receives the terminal identification of the second terminal and the corresponding RRC rejection message from the radio access network device, and can know which second terminal is corresponding to the terminal identification, so that it can communicate with the second terminal. The unicast connection sends an RRC reject message to the second terminal.

Optionally, when the wireless access network device accepts the access of the second terminal, the method further includes:

The second terminal sends an RRC establishment complete message to the first terminal; and,

The first terminal sends the RRC establishment complete message of the second terminal to the radio access network device.

Exemplarily, after receiving the RRC establishment message sent by the radio access network device, the second terminal further resumes or completes the RRC establishment. The restoration or completion of the RRC establishment may be understood as sending to the first terminal the completion of the RRC establishment or the completion of the RRC re-establishment or the completion of the RRC restoration. The restoration or completion of the RRC establishment can reuse the SL-SRB1 between the second terminal and the first terminal for transmission. The SL-SRB1 is generally used to transmit the RRC message of the sidelink unicast connection. In this embodiment, the SL-SRB1 is reused to transmit the SRB1 signaling between the second terminal and the radio access network device.

Since the purpose of the embodiments of the present application is to realize the RRC connection between the second terminal and the radio access network device, the RRC message sent by the second terminal to the first terminal needs to be sent to the radio access network device. In order for the first terminal to send the RRC message, indication information can be added to instruct the first terminal to send the RRC message to the radio access network device, so that the first terminal can determine according to the indication information that the data received from the second terminal is sent to the wireless The data of the access network equipment is then sent to the radio access network equipment RRC message. For example, the indication information is added to the headers of the first terminal and the second terminal SL and RLC. The indication information is used by the first terminal to identify whether the signaling for unicast connection or the signaling used for communication between the second terminal and the radio access network device is sent through the SL-SRB1. Correspondingly, after the first terminal receives the indication information, when it is determined that this is the RRC signaling sent by the second terminal to the radio access network device, it will be further forwarded to the radio access network device.

In a possible design, the indication information may be included in the RLC PDU, that is, the indication information is included in the data when the data is processed by the RLC layer, for example, included in the RLC packet header. Exemplarily, the indication information may be a binary bit number of 0, 1, or other symbols. Specifically, which symbol is used to represent the indication information may be pre-defined by the agreement, which is not limited in the embodiment of the present application. For example, taking the bit number "1" to instruct the first terminal to send an RRC message to the radio access network device as an example, the second terminal may include the bit number "1" in the data packet header when the data is processed by PDCP , And send it to the first terminal after subsequent processing.

In another possible design, the protocol specifies that the first data transmitted on a certain logical channel (such as the first logical channel) is data or an RRC message sent to the radio access network device. At this time, the above indication may be the identifier of the first logical channel, and the indication is included in the first data. For example, when the first data is processed by the MAC layer, the identifier of the first logical channel is included in the data packet header. Exemplarily, the protocol provisions may refer to rules agreed in advance that need to be complied by the first terminal and the second terminal. For example, if the protocol stipulates that the data transmitted on LCID0 is data or RRC message sent to the radio access network device, the second terminal may send the first data including LCID0 and the first RRC message to the first terminal through LCID0. After receiving the first data, the first terminal may determine to send an RRC message to the radio access network device according to LCID0 in the first data.

Optionally, this method also includes:

The first terminal sends an RLC PDU to the radio access network device, where the RLC PDU has indication information for indicating whether the first terminal has an adaptation layer. For example, the RLC PDU has an RLC PDU header, and the RLC PDU header has the above-mentioned indication information.

Exemplarily, the RRC establishment complete message is a message carried by SRB1. In this embodiment, the SRB1 of the first terminal is reused to send the message carried by the SRB1 of the second terminal. When the first terminal is connected to multiple second terminals, in order to distinguish the second terminals, when the first terminal sends the RRC establishment to the radio access network device, the indication information needs to be added to the RLC header of the first terminal for It is indicated that there is an adaptation layer above the RLC, so that the radio access network device determines to hand over the received data to the adaptation layer for processing according to the indication. The adaptation layer may carry the terminal identifier of the second terminal, so that the radio access network device can know which second terminal's RRC message is after receiving the indication information.

Further, as shown in FIG. 5, the radio access network device can perform RRC configuration for the second terminal through the first terminal, and can also reuse the SRB1 between the radio access network device and the first terminal, and/or the second terminal SL-SRB1 between the terminal and the first terminal. In the same way, the SRB2 between the second terminal and the radio access network device can reuse the SRB2 between the first terminal and the radio access network device. At this time, the adaptation layer is also required, and the indication information on the RLC header of the radio access network device is used to indicate that there is an adaptation layer above the RLC. Those skilled in the art can understand that as far as radio access network equipment is concerned, the adaptation layer can be between the PDCP layer and the RLC layer, and the protocol stack is RRC layer, PDCP layer, and adaptation layer from top to bottom. RLC layer, MAC layer and PHY layer. As far as the first terminal is concerned, its protocol stack consists of an adaptation layer, an RLC layer, a MAC layer and a PHY layer from top to bottom. Exemplarily, the adaptation layer of the radio access network device and the adaptation layer of the first terminal (that is, have a peer-to-peer relationship), and the adaptation layer of the first terminal is responsible for decapsulating data to obtain the foregoing indication information, for example.

Optionally, the method of this embodiment further includes:

The first terminal receives the logical channel information corresponding to the second SRB and/or the data radio bearer DRB from the radio access network device. The second SRB is used for the second RRC message of the second terminal, and the second SRB is located in the dedicated control channel or The second RRC message includes a dedicated configuration of the second terminal or a non-access stratum NAS message.

Exemplarily, the SRB and/or DRB of the second terminal need to reuse the SRB and/or DRB of the first terminal. In order to distinguish different second terminals, one implementation manner is to introduce an adaptation layer. Another implementation manner is to distinguish by using different logical channels for the SRB and/or DRB of different second terminals. Or, it is distinguished by using different logical channels for different second terminals. Specifically, the wireless access network device configures the first terminal with a logical channel identifier corresponding to the SRB1 of the second terminal, and the logical channel identifier is used when transmitting the SRB1RRC message of the second terminal between the first terminal and the wireless access device. Logical channel identifier. Optionally, the radio access network device may also configure one or more of the priority of the logical channel, the logical channel group to which it belongs, and the RLC entity. The above configuration action may occur after the wireless access device sends the RRC establishment request to the first terminal, or before the wireless access device receives the RRC establishment complete message sent by the first terminal, which is not limited in the present invention.

Subsequently, when the first terminal sends the SRB1 RRC message of the second terminal to the radio access network device, it may send it through the foregoing logical channel. Correspondingly, the signaling corresponding to the logical channel received by the first terminal from the wireless access network device is the signaling carried by the SRB1 of the second terminal. Further, the wireless access device configures the SRB2 of the second terminal and the logical channel identifier corresponding to each DRB for the first terminal.

In a possible design, the first terminal sends data to the radio access network device through a data radio barrier (DRB) between the first terminal and the radio access network device. For example, the first terminal can process the data through the RLC layer, MAC layer, and PHY layer corresponding to the radio access network device in the first terminal, that is, through the data radio bearer between the first terminal and the radio access network device ( data radio barrier, DRB) sends data to the radio access network device. Exemplarily, the RLC layer, MAC layer, and PHY layer corresponding to the radio access network device in the first terminal may be as shown in FIG. 2, which are the PHY layer, MAC layer, and RLC layer of the radio access network device in the first terminal. PHY layer 2, MAC layer 2, and RLC layer 2 connected end-to-end.

In another possible design, the first terminal passes the signaling through the RLC layer, MAC layer, and PHY layer corresponding to the radio access network device in the first terminal, that is, through the first terminal and the radio access network device. The inter-signaling radio barrier (SRB) 1 sends signaling to the radio access network device.

In this embodiment, the second terminal reuses the SRB of the first terminal to perform RRC signaling interaction with the radio access network equipment, which can help the second terminal at the edge of the cell or outside the cell coverage to successfully access the radio access network equipment, thereby Obtain the wireless access network device configuration and communicate.

Figure 4 uses the transmission of the RRC establishment request between the first terminal and the radio access network device through SRB0 as an example. When the first terminal and the radio access network device transmits the RRC establishment request through SRB1, as shown in Figure 6 As shown, the following steps can be included.

601. The first terminal receives an RRC establishment request of the second terminal from the second terminal.

602. The first terminal sends a first RRC message to the radio access network device, where the first RRC message includes the foregoing RRC establishment request.

For terms that are the same or similar to the above and their functional descriptions appearing in this embodiment, reference may be made to the foregoing descriptions, which are not repeated here.

The above steps are mainly described based on the first terminal. It can be understood that, as far as the network is concerned, the radio access network device receives the first RRC message from the first terminal, and the first RRC message includes the RRC establishment request of the second terminal. As far as the second terminal is concerned, the second terminal sends the RRC establishment request of the second terminal to the first terminal, for the first terminal to send a first RRC message to the radio access network device, the first RRC message includes the above-mentioned RRC establishment request .

Exemplarily, as shown in Figure 7, the second terminal packs the RRC establishment request in an SL RRC message and transmits it to the first terminal, and then the first terminal packs the received RRC establishment request of the second terminal into the RRC generated by itself. The message is passed to the wireless access network device. Specifically, the second terminal may send an RRC establishment request to the first terminal through an SL RRC message. It can be understood that the second terminal carries the RRC establishment request as a container in the SL RRC message and sends it to the first terminal. The foregoing RRC establishment request is, for example, transmitted based on a wireless communication interface between the second terminal and the radio access network device. The wireless communication interface (for example, referred to as a Uu port) may be an LTE standard air interface or an NR standard air interface.

Exemplarily, the foregoing first RRC message may further include the identity of the second terminal. In a possible application scenario, the first terminal needs to provide services for multiple second terminals. Therefore, the first terminal will assign a terminal identifier to each second terminal, and the terminal identifier and the second terminal corresponding to the terminal identifier Second, the RRC establishment request received by the terminal is sent to the radio access network device. In this embodiment, the first terminal may package the identifier of the second terminal and the RRC establishment request of the second terminal in an RRC message of the first terminal and send it to the radio access network device. For example, the identifier of the second terminal and the corresponding RRC establishment request are information elements in the RRC message of the first terminal, and the RRC message of the first terminal is an uplink RRC message.

In this embodiment, if the wireless access network device agrees to the access of the second terminal, the above method may further include:

The first terminal receives a second RRC message from the radio access network device, where the second RRC message includes an RRC setup message; and

The first terminal sends the RRC setup message to the second terminal.

Optionally, the foregoing second RRC message may also include the identity of the second terminal. When multiple second terminals are connected to the first terminal, it is used to identify which second terminal is associated with the RRC establishment message.

Exemplarily, the first terminal sends a sidelink RRC message to the second terminal, and the sidelink RRC message includes the foregoing RRC establishment message.

Specifically, after the radio access network device receives the terminal identification of the second terminal and the RRC establishment request sent by the first terminal, if the second terminal is allowed to access, it will generate an RRC establishment message for the second terminal and send it To the first terminal. For example, the radio access network device sends the identifier of the second terminal and its corresponding RRC setup message as information elements in the downlink RRC message of the first terminal to the first terminal. When the first terminal receives the identification of the second terminal sent by the radio access network device, it can identify which second terminal the RRC establishment message is associated with, and use the SL-SRB with the second terminal to identify the radio access network device as the first terminal. The RRC setup message generated by the second terminal is sent to the second terminal.

In this embodiment, if the wireless access network device rejects the access of the second terminal, the above method may further include:

The first terminal receives a third RRC message from the radio access network device, the third RRC message including an RRC rejection message; and

The first terminal sends the RRC rejection message to the second terminal.

Optionally, the foregoing third RRC message may also include the identity of the second terminal. When multiple second terminals are connected to the first terminal, it is used to identify which second terminal the RRC reject message is associated with.

Exemplarily, if the radio access network device does not approve the access of the second terminal, it will generate an RRC rejection message for the second terminal and send it to the first terminal. Specifically, the radio access network device needs to send the identity of the second terminal and the RRC rejection message as information elements of the downlink RRC message of the first terminal to the first terminal. Optionally, if the radio access network device rejects the access of the second terminal, the first terminal will send an RRC reject message to the second terminal.

Exemplarily, the first terminal sends a sidelink RRC message to the second terminal, and the sidelink RRC message includes the foregoing RRC rejection message.

Those skilled in the art can understand that the format of the sidelink RRC message sent by the first terminal to the second terminal and the sidelink RRC message sent by the second terminal to the first terminal may be the same or a common RRC message, or may contain different formats. Information element or information.

In this embodiment, the above method may further include:

The first terminal receives the logical channel information corresponding to the second SRB and/or the data radio bearer DRB from the radio access network device. The second SRB is used for the fourth RRC message of the second terminal, and the second SRB is located on the dedicated control channel or the first Fourth, the RRC message includes the dedicated configuration or non-access stratum NAS message of the second terminal.

Exemplarily, when the second terminal performs SRB1 and SRB2 signaling interaction between the first terminal and the radio access network device, it reuses the SL-SRB1 and SL-SRB2 between the second terminal and the first terminal, and SRB1 and SRB2 between the first terminal and the radio access network device. The specific reuse method is similar to the previous article, so I won't repeat it. Wherein, SL-SRB1 is an SRB used to transfer SL RRC messages between the second terminal and the first terminal, and SL-SRB2 is an SRB used to transfer upper layer signaling between the second terminal and the first terminal.

If the radio access network device rejects the access request of the second terminal, the above-mentioned SRB1 and/or SRB2 signaling interaction is not performed, and the second terminal will release the unicast connection with the first terminal.

Exemplarily, when the first terminal is connected to multiple second terminals, both the first terminal or the wireless access network device may assign the terminal identifier to the second terminal. Optionally, when the radio access network device allocates a terminal identifier to the second terminal, it will be carried in the RRC setup message sent by the radio access network device to the first terminal. At this time, in order to let the first terminal know the correspondence between the RRC establishment message and the RRC establishment request sent by the first terminal to the radio access network device, the RRC establishment message may be limited to carry the same identification information as the RRC establishment request. For example, transaction ID.

In this embodiment, the SRB1 between the first terminal and the radio access network device is used to transmit the RRC establishment request. Further, the SL-SRB1 between the second terminal and the first terminal is used to transmit the RRC establishment message and/or the RRC rejection message. Thereby avoiding changes to SRB0 and improving safety performance.

This application provides another embodiment, which relates to a method for a second terminal to access the network through the first terminal and restore the previous context of the second terminal in the core network, which may include the following steps.

The first terminal receives the upper layer signaling sent by the second terminal; and

The first terminal sends the NAS information of the second terminal to the core network device of the first terminal.

It can be understood that the foregoing method is described based on the second terminal. As far as the core network device is concerned, the core network device receives the NAS information of the second terminal from the first terminal.

Exemplarily, after the second terminal discovers and selects a suitable first terminal, the second terminal establishes a sidelink unicast connection with the first terminal. Subsequently, the NAS layer of the second terminal may initiate a process of restoring the context of the second terminal. The context may refer to a PDU session previously established by the second terminal with the core network device.

In this embodiment, the upper layer signaling may be PC5-S or sidelink or D2D link upper layer signaling, for example, signaling generated by the V2X layer. Taking PC5-S signaling as an example, the PC5-S signaling may include the NAS message of the second terminal, and the NAS message may be generated by the NAS layer of the second terminal and sent to the V2X layer. Specifically, the NAS message may include the 5th Generation System Architecture Evolution Temporary Mobile Station Identifier (5G-S-TMSI) of the second terminal or the globally unique temporary identifier (Globally Unique Temporary). Identity, GUTI). Optionally, the NAS message may also include a protocol data unit (protocol data unit, PDU) session identifier or PDU session status.

It can be understood that, after receiving the upper layer signaling of the second terminal from the PC5 interface, for example, the first terminal may send the NAS information of the second terminal in the upper layer signaling to the core network device of the first terminal. Specifically, the upper layer of the first terminal may send to the NAS layer, and then the NAS message of the second terminal is transferred to the core network device of the first terminal through the NAS message of the first terminal.

Optionally, the method of this embodiment further includes:

The core network device of the first terminal sends the NAS information of the second terminal to the core network device of the second terminal.

Exemplarily, the core network equipment of the first terminal and the core network equipment of the second terminal may be the same or different. If they are different, the core network device of the first terminal can find the core network device of the second terminal based on the 5G-S-TMSI or GUTI of the second terminal, and obtain the context of the second terminal, so as to resume the PDU session of the second terminal. If they are the same, the core network device resumes the PDU session of the second terminal. Specifically, the core network device restores the PDU session of the second terminal to the first terminal. It can be understood that the foregoing restoration process is to restore the PDU session of the second terminal between the first terminal and the core network device.

Optionally, this implementation method also includes:

The core network device of the first terminal replies a confirmation message to the first terminal for confirming that the restoration is successful; and,

The first terminal sends a confirmation message to the second terminal.

Exemplarily, the confirmation message is PC5-S signaling, which is used to confirm the successful recovery. After completing the signaling interaction, the first terminal may receive the PDU session data of the second terminal from the core network device and forward it to the second terminal.

In this embodiment, the second terminal restores the context between the second terminal and the core network device through the first terminal, thereby avoiding re-establishing a new PDU session and saving core network overhead.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, the first terminal, the second terminal, and the wireless access network device include hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application may divide the first terminal, the second terminal, and the wireless access network device into functional modules according to the above method examples. For example, each functional module may be divided corresponding to each function, or two or more The functions are integrated in a processing module. The above-mentioned integrated modules can be implemented in the form of hardware or software function modules. Optionally, the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

FIG. 8 shows a schematic diagram of the composition of a communication device. The communication device may be a first terminal or a chip or a system on a chip in the first terminal. The communication device may be used to execute the first terminal involved in the above-mentioned embodiment. Features. The communication device shown in FIG. 8 includes: a receiving unit 80 and a sending unit 81.

The receiving unit 80 is configured to receive the RRC establishment request of the second terminal from the second terminal. For example, the generating unit 80 may be used to support the communication device to perform step 401 and step 601.

The sending unit 81 is configured to send an RRC establishment request to the radio access network device. For example, the sending unit 81 may be used to support the communication device to perform step 402 and step 602.

One implementation is described as follows.

Optionally, the sending unit 81 sends the RRC establishment request to the radio access network device through the first SRB. The first SRB may be located on the common control channel.

Exemplarily, the sending unit 81 sends the RRC establishment request and the identifier of the second terminal to the radio access network device through the first SRB.

Exemplarily, the receiving unit 80 is further configured to receive an RRC setup message from the radio access network device; the sending unit 81 is further configured to send the RRC setup message to the second terminal. Further, the receiving unit 80 is configured to receive the RRC establishment message and the identifier of the second terminal from the radio access network device.

Exemplarily, the receiving unit 80 is further configured to receive an RRC rejection message from the radio access network device; the sending unit 81 is further configured to send the RRC rejection message to the second terminal. Further, the receiving unit 80 is configured to receive the RRC reject message and the identifier of the second terminal from the radio access network device.

As shown in FIG. 8, the communication device may further include a processing module 82, configured to release the connection between the first terminal and the second terminal.

Exemplarily, the receiving unit 80 is further configured to receive the scheduling request SR configuration of the first SRB from the radio access network device; the sending unit 81 is further configured to send to the radio access network device based on the SR configuration SR.

Exemplarily, when the first SRB has data to be transmitted and no scheduled resources, the sending unit 81 is further configured to send the SR to the radio access network device.

Exemplarily, the first SRB corresponds to a logical channel group, and the processing module 82 is further configured to trigger a buffer status report BSR to request resource scheduling.

Exemplarily, the receiving unit 80 is further configured to receive logical channel information corresponding to a second SRB and/or a data radio bearer DRB from the radio access network device, where the second SRB is used for the second terminal of the second terminal. RRC message, the second SRB is located in a dedicated control channel or the second RRC message includes a dedicated configuration of the second terminal or a non-access stratum NAS message.

Exemplarily, the sending unit 81 is further configured to send an RLC PDU to the radio access network device, where the RLC PDUC has indication information for indicating whether the first terminal has an adaptation layer.

Another implementation is described below.

Optionally, the sending unit 81 sends a first RRC message to the radio access network device, where the first RRC message includes an RRC establishment request.

Exemplarily, the first RRC message further includes the identity of the second terminal.

Exemplarily, the receiving unit 80 is further configured to receive a second RRC message from the radio access network device, where the second RRC message includes an RRC setup message; and the sending unit 81 is further configured to send the second terminal RRC establishment message. Further, the receiving unit 80 is configured to receive the second RRC message from the radio access network device, including the RRC setup message and the identifier of the second terminal.

Exemplarily, the receiving unit 80 is further configured to receive a third RRC message from the radio access network device, where the third RRC message includes an RRC rejection message; and the sending unit 81 is further configured to send the second terminal RRC rejected the message. Further, the receiving unit 80 is configured to receive a third RRC message from the radio access network device, including the RRC reject message and the identifier of the second terminal.

Exemplarily, the receiving unit 80 is further configured to receive a sidelink RRC message from the second terminal, where the sidelink RRC message includes the RRC establishment request.

Exemplarily, the sending unit 81 is further configured to send a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC setup message.

Exemplarily, the sending unit 81 is further configured to send a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC rejection message.

Optionally, all relevant content of the steps involved in the foregoing method embodiment can be cited in the functional description of the corresponding functional module, which will not be repeated here. The communication device provided in the embodiment of the present application is used to perform the function of the first terminal in the above-mentioned RRC connection method, and therefore can achieve the same effect as the above-mentioned RRC connection method.

As yet another achievable manner, the communication device shown in FIG. 8 may include: a processing module and a communication module. The generating unit 82 is integrated in the processing module, and the sending unit 81 and the receiving unit 80 are integrated in a communication module. The processing module is used to control and manage the actions of the communication device. For example, the communication module is used to support the communication device to execute 401-402, 601-602 and communicate with other network entities, such as the relay device shown in Figure 1 or other networks. The entities communicate with each other. Further, the communication device may also include a storage module for storing the program code and data of the communication device.

Exemplarily, the processing module may be a processor or a controller. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of DSP and microprocessor, and so on. The communication module can be a transceiver circuit or a communication interface. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device shown in FIG. 8 may be the communication device shown in FIG. 3.

Fig. 9 shows a schematic diagram of the composition of a communication device. The communication device may be a network device or a chip or a system on a chip in the network device. The communication device can be used to perform the functions of the radio access network device involved in the foregoing embodiments. The communication device shown in FIG. 9 includes: a receiving unit 90 and a sending unit 91.

The receiving unit 90 is configured to receive the RRC establishment request of the second terminal from the first terminal.

The sending unit 91 is configured to send an RRC message to the first terminal, where the RRC message includes an RRC establishment message or an RRC rejection message.

One implementation is described as follows.

Optionally, the receiving unit 90 receives the RRC establishment request of the second terminal from the first terminal through the first SRB.

Exemplarily, the first SRB is located on a common control channel.

Exemplarily, the receiving unit 90 is further configured to receive the RRC establishment request and the identifier of the second terminal from the first terminal through the first SRB.

Exemplarily, the sending unit 91 is further configured to send an RRC setup message to the first terminal. Further, the sending unit 91 is configured to send an RRC setup message and an identifier of the second terminal to the first terminal.

Exemplarily, the sending unit 91 is further configured to send an RRC rejection message to the first terminal. Further, the sending unit is configured to send the RRC reject message and the identifier of the second terminal to the first terminal.

Exemplarily, the sending unit 91 is further configured to send a scheduling request SR configuration of the first SRB to the first terminal; the receiving unit 90 is further configured to receive an SR based on the SR configuration from the first terminal.

Exemplarily, the receiving unit 90 is further configured to receive the SR sent by the first terminal when the first SRB has data to be transmitted and there is no scheduling resource.

Exemplarily, the first SRB corresponds to a logical channel group and is used to trigger a buffer status report BSR to request resource scheduling.

Exemplarily, the sending unit 91 is further configured to send logical channel information corresponding to a second SRB and/or a data radio bearer DRB to the first terminal, where the second SRB is used for a second RRC message of the second terminal The second SRB is located in a dedicated control channel or the second RRC message includes a dedicated configuration of the second terminal or a non-access stratum NAS message.

Exemplarily, the receiving unit 90 is further configured to receive an RLC PDU from the first terminal, where the RLC PDU has indication information for indicating whether the first terminal has an adaptation layer.

Another implementation is described below.

Exemplarily, the receiving unit 90 is further configured to receive a first RRC message from the first terminal, where the first RRC message includes an RRC establishment request of the second terminal.

Exemplarily, the sending unit 91 is further configured to send a second RRC message to the first terminal, where the second RRC message includes an RRC setup message and an identifier of the second terminal. Further, the sending unit 91 is configured to send a second RRC message to the first terminal, where the second RRC message includes an RRC setup message and an identifier of the second terminal.

Exemplarily, the sending unit 91 is further configured to send a third RRC message to the first terminal, where the third RRC message includes an RRC rejection message and an identifier of the second terminal. Further, the sending unit 91 is configured to send a second RRC message to the first terminal, where the second RRC message includes an RRC setup message and an identifier of the second terminal.

Exemplarily, the sending unit 91 is further configured to send logical channel information corresponding to a second SRB and/or a data radio bearer DRB to the first terminal, where the second SRB is used for the fifth RRC message of the second terminal The second SRB is located in a dedicated control channel or the fifth RRC message includes a dedicated configuration or a non-access stratum NAS message of the second terminal.

Optionally, all relevant content of the steps involved in the foregoing method embodiment can be cited in the functional description of the corresponding functional module, which will not be repeated here. The communication device provided in the embodiment of the present application is used to perform the function of the radio access network device in the above-mentioned RRC connection method, and therefore can achieve the same effect as the above-mentioned RRC connection method.

As yet another achievable manner, the communication device shown in FIG. 9 may include: a processing module and a communication module. The receiving unit 90 and the sending unit 91 may be integrated in a communication module. The processing module is used to control and manage the actions of the communication device. The communication module is used to support the communication device to perform the receiving and sending steps and to communicate with other network entities, for example, to communicate with the remote device or relay device shown in FIG. 1 or other network entities. Further, the communication device may also include a storage module for storing the program code and data of the communication device.

Exemplarily, the processing module may be a processor or a controller. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module can be a transceiver circuit or a communication interface. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device shown in FIG. 9 may be the communication device shown in FIG. 3.

FIG. 10 shows a schematic diagram of the composition of a communication system. As shown in FIG. 10, the communication system may include a second terminal 100, a first terminal 101, and a wireless access network device 102. A first channel is established between the second terminal 100 and the first terminal 101, and the second terminal 100 can communicate with the first terminal 101 through the first channel. A second channel is established between the first terminal 101 and the wireless access network device 102, and the first terminal 101 and the wireless access network device 102 can communicate with each other through the second channel.

Exemplarily, the first terminal 101 has the function of the communication device shown in FIG. 8, and can be used to receive a message sent by the second terminal 100 through the first channel for instructing the first terminal 101 to send an RRC message to the radio access network device 102.

The wireless access network device 102 has the function of the communication device shown in FIG. 9 and can be used to receive the second data of the RRC message sent by the first terminal 101 from the wireless communication interface between the wireless access network device 102 and the first terminal 101 . It should be noted that all relevant content of the steps involved in the foregoing method embodiments can be cited in the functional description of the corresponding network element of the communication system, and will not be repeated here. The RRC connection provided in the embodiment of the present application is used to execute the above-mentioned RRC connection method, and therefore, the same effect as the above-mentioned RRC connection method can be achieved.

It is understandable that the remote terminal can not only send the RRC message to the wireless access network device through the relay terminal, but also can send the RRC message to the wireless access network device through the relay device with more than two hops. When a remote terminal sends an RRC message to a radio access network device through a relay device with more than two hops, the specific sending process can refer to the method provided in the embodiment of the present application, which will not be repeated.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or include one or more data storage devices such as servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Although this application has been described in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and understand by viewing the drawings, the disclosure, and the appended claims in the process of implementing the claimed application. Implement other changes of the disclosed embodiment. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "one" does not exclude a plurality. A single processor or other unit may implement several functions listed in the claims. Certain measures are described in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

Although the application has been described in combination with specific features and embodiments, it is obvious that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary descriptions of the application as defined by the appended claims, and are deemed to cover any and all modifications, changes, combinations or equivalents within the scope of the application. Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A radio resource control RRC connection method is characterized in that it includes:

The first terminal receives the RRC establishment request of the second terminal from the second terminal; and

Sending, by the first terminal, the RRC establishment request to the network device through the first SRB;

Wherein, the first SRB is located on a common control channel.
The method according to claim 1, wherein the sending step specifically includes:

The first terminal sends the RRC establishment request and the identifier of the second terminal to the network device through the first SRB.
The method according to claim 1 or 2, further comprising:

Receiving, by the first terminal, an RRC setup message from the network device;

The first terminal sends the RRC setup message to the second terminal.
The method according to claim 1 or 2, further comprising:

Receiving, by the first terminal, an RRC rejection message from the network device;

Sending, by the first terminal, the RRC reject message to the second terminal; and

The first terminal performs connection release with the second terminal.
The method according to any one of claims 1-4, characterized in that:

Receiving, by the first terminal, the scheduling request SR configuration of the first SRB from the network device;

The first terminal sends an SR to the network device based on the SR configuration.
The method according to claim 5, wherein the first terminal sending an SR to the network device based on the SR configuration specifically comprises:

When the first SRB has data to be transmitted and no scheduling resources, the first terminal sends the SR to the network device.
The method according to any one of claims 1-4, characterized in that:

The first SRB corresponds to a logical channel group and is used by the first terminal to trigger a buffer status report BSR to request resource scheduling.
The method according to any one of claims 1-7, further comprising:

The first terminal receives the logical channel information corresponding to the second SRB and/or the data radio bearer DRB from the network device, the second SRB is used for the second RRC message of the second terminal, and the second SRB The dedicated control channel or the second RRC message includes a dedicated configuration or non-access stratum NAS message of the second terminal.
The method according to any one of claims 1 to 7, further comprising:

The first terminal sends an RLC PDU to the network device, and the RLC PDUC has indication information for indicating whether the first terminal has an adaptation layer.
A radio resource control RRC connection method is characterized in that it includes:

The network device receives the RRC establishment request of the second terminal from the first terminal through the first SRB;

Wherein, the first SRB is located on a common control channel.
The method according to claim 10, wherein the receiving step specifically includes:

The network device receives the RRC establishment request and the identifier of the second terminal from the first terminal through the first SRB.
The method according to claim 10 or 11, further comprising:

The network device sends an RRC setup message to the first terminal.
The method according to claim 10 or 11, further comprising:

The network device sends an RRC rejection message to the first terminal.
The method according to any one of claims 10-13, characterized in that:

Sending, by the network device, the scheduling request SR configuration of the first SRB to the first terminal;

The network device receives an SR configured based on the SR from the first terminal.
The method according to claim 14, wherein the receiving, by the network device from the first terminal, the SR based on the SR configuration specifically comprises:

The network device receives the SR sent by the first terminal when the first SRB has data to be transmitted and there is no scheduling resource.
The method according to any one of claims 10-13, characterized in that:

The first SRB corresponds to a logical channel group and is used to trigger a buffer status report BSR to request resource scheduling.
The method according to any one of claims 10-16, further comprising:

The network device sends the second SRB and/or the logical channel information corresponding to the data radio bearer DRB to the first terminal, where the second SRB is used for the second RRC message of the second terminal, and the second SRB The dedicated control channel or the second RRC message includes a dedicated configuration or non-access stratum NAS message of the second terminal.
The method according to any one of claims 10 to 17, further comprising:

The network device receives an RLC PDU from the first terminal, where the RLC PDU has indication information for indicating whether the first terminal has an adaptation layer.
A radio resource control RRC connection method is characterized in that it includes:

The first terminal receives the RRC establishment request of the second terminal from the second terminal; and

The first terminal sends a first RRC message to the network device, where the first RRC message includes the RRC establishment request.
The method according to claim 19, wherein:

The first RRC message also includes the identity of the second terminal.
The method according to claim 19 or 20, further comprising:

Receiving, by the first terminal, a second RRC message from the network device, the second RRC message including an RRC setup message; and

The first terminal sends the RRC setup message to the second terminal.
The method according to claim 19 or 20, further comprising:

Receiving, by the first terminal, a third RRC message from the network device, the third RRC message including an RRC rejection message; and

The first terminal sends the RRC rejection message to the second terminal.
The method according to any one of claims 19-22, characterized in that:

The receiving of the RRC establishment request by the first terminal from the second terminal specifically includes:

The first terminal receives a sidelink RRC message from the second terminal, where the sidelink RRC message includes the RRC establishment request.
The method according to any one of claims 21 or 22, characterized in that:

The sending of the RRC setup message by the first terminal to the second terminal specifically includes:

The first terminal sends a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC setup message; or,

The sending of the RRC rejection message by the first terminal to the second terminal specifically includes:

The first terminal sends a sidelink RRC message to the second terminal, where the sidelink RRC message includes the RRC rejection message.
The method according to any one of claims 19-24, further comprising:

The first terminal receives the logical channel information corresponding to the second SRB and/or the data radio bearer DRB from the network device, the second SRB is used for the fifth RRC message of the second terminal, and the second SRB Located in the dedicated control channel or the fifth RRC message includes a dedicated configuration or non-access stratum NAS message of the second terminal.
A radio resource control RRC connection method is characterized in that it includes:

The network device receives a first RRC message from the first terminal, where the first RRC message includes an RRC establishment request of the second terminal.
The method of claim 26, wherein:

The first RRC message also includes the identity of the second terminal.
The method according to claim 26 or 27, further comprising:

The network device sends a second RRC message to the first terminal, where the second RRC message includes an RRC setup message.
The method according to claim 26 or 27, further comprising:

The network device sends a third RRC message to the first terminal, where the third RRC message includes an RRC rejection message.
The method according to any one of claims 26-29, further comprising:

The network device sends the second SRB and/or the logical channel information corresponding to the data radio bearer DRB to the first terminal, where the second SRB is used for the fifth RRC message of the second terminal, and the second SRB Located in the dedicated control channel or the fifth RRC message includes a dedicated configuration or non-access stratum NAS message of the second terminal.
A communication device, characterized in that the communication device includes one or more processors and one or more memories; the one or more memories are coupled with the one or more processors, and the one or more Each memory is used to store computer program code, where the computer program code includes computer instructions;

When the one or more processors execute the computer instructions, the communication device is caused to execute the radio resource control RRC method according to any one of claims 1-30.
A computer storage medium, wherein the computer storage medium includes computer instructions, when the computer instructions run on a computer, the computer is caused to execute the wireless resource control according to any one of claims 1-30 RRC method.
A computer program product, characterized in that, when the Korean product is running on a computer, the computer is caused to execute the RRC method for radio resource control according to any one of claims 1-30.