RU2771926C2 - Method for controlling wireless connection, distributed block, centralized block and base station system - Google Patents

Abstract

FIELD: communication technologies.

SUBSTANCE: method for controlling a wireless connection relates to a base network system including a centralized block and a distributed block that communicate with each other and communicate with a terminal via a radio interface. The method includes: reception by the distributed block of a request for radio resource control (hereinafter – RRC) connection sent by the terminal; sending by the distributed block of a control plane message containing a request for RRC connection to the centralized block via a control plane connection; reception by the distributed unit via the control plane connection of a control plane message that is sent by the centralized block and contains a message about establishing RRC connection; sending by the distributed block of a message about establishing RRC connection to the terminal; reception by the distributed block of a message about completion of establishing RRC connection, sent by the terminal; sending by the distributed unit of a message about completion of establishing RRC connection, sent to the centralized block.

EFFECT: providing the control of a wireless connection in 5G system in cases, when base station functions are divided.

18 cl, 26 dwg

Description

The present application claims the priority of Chinese Patent Application No. 201710313783.2, filed May 5, 2017 with the Chinese Patent Office, which is hereby incorporated by reference in its entirety.

The technical field to which the invention belongs

The present application relates generally to communication technologies, and in particular to a wireless connection management method, a distributed module, a centralized module, and a base station system.

State of the art

In the 5th Generation mobile communication technology (5G) mobile communication system, a base station may include a Centralized Unit (CU) and a Distributed Unit (DU). More specifically, the functions of the base station in the original access network are separated, some of the functions of the base station are deployed in the CU, and the rest of the functions are deployed in the DU. Multiple DUs share one CU. This reduces costs and facilitates network scalability. The CU-DU separation may be based on a protocol stack. In an exemplary manner, a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer can be deployed in a CU, and a Radio Link Control (RLC) layer, an access control layer to media (Media Access Control, MAC) and physical layer can be deployed in the DU.

The process of establishing an RRC connection is a necessary process for a terminal in terms of gaining access to a communication network. In the existing network architecture in which the base station is a stand-alone device, such as in a Long Term Evolution (LTE) system, the base station supports all protocol layer processing. The RRC connection establishment process may be directly handled by the base station. However, if the base station functions are performed by the DU and the CU in the 5G system, the RRC connection process must be handled through an interface located between the DU and the CU. Thus, at the time of establishing an RRC connection between the DU and the CU, it is necessary to provide a processing method and an interface transmission method.

The essence of the invention

The present application provides a wireless connection management method, a distributed unit, a centralized unit, and a base station system for performing wireless connection management in a 5G system in cases where the functions of the base station are separated.

The first aspect of the present application provides a method for managing a wireless connection, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and way includes:

first, the distributed unit receiving a first message sent by the terminal, where the first message is used to request the establishment of an air interface control plane connection for the terminal; further sending by the distributed block of the first message to the centralized block; and then receiving by the distributed unit a second message sent by the centralized unit, where the second message is used to instruct the establishment of an air interface control plane connection between the terminal and the distributed unit.

In this method, the distributed unit communicating with the terminal sends, to the centralized unit, an air interface control plane connection request message sent by the terminal so that the centralized unit can perform air interface control plane connection processing and wireless connection control in the 5G system in those cases. when the functions of the base station are separated.

Optionally, the method further includes:

establishment by a distributed unit of a control plane connection between a distributed unit and a centralized unit, where

sending a distributed block the first message to a centralized block includes:

the distributed unit sending a third message to the centralized unit via a control plane connection, where the third message includes the first message, and the third message further includes at least one of the following information:

the first terminal identifier corresponding to the terminal, the identifier of the cell accessed by the terminal, and the second terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface, and the second terminal identifier is an identifier allocated by the allocated block for the terminal over the plane interface control between the distributed unit and the centralized unit.

Optionally, the second message is sent over a control plane connection; the second message includes a third terminal identifier; and the third terminal ID is an ID allocated by the centralized unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

Optionally, the method further includes:

receiving by the distributed unit the first signaling bearer configuration information sent by the centralized unit.

Optionally, the first signaling bearer configuration information includes at least one of the following information:

the first signaling bearer identifier, the media access control layer configuration parameter used by the distributed unit to establish the first signaling bearer, the physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, the logical channel configuration parameter used by the distributed unit to establishing a first signaling bearer, and first information about establishing a signaling bearer user plane transmission path on the centralized unit side.

In an exemplary embodiment, the distributed unit receives, via a second message, the first signaling bearer configuration information sent by the centralized unit.

Optionally, the method further includes:

sending, by the distributed unit, first information about establishing a transmission path of the user plane of the signaling bearer on the side of the distributed unit to the centralized unit.

In an exemplary embodiment, the distributed unit sending the first signaling bearer user plane transmission path establishment information on the distributed unit side to the centralized unit includes:

adding, by the distributed unit, first information about establishing a signaling bearer user plane transmission path on the side of the distributed unit to a third message, and sending the third message to the centralized unit.

In another possible embodiment, before the distributed unit sends the first message to the centralized unit, the method further includes:

reception by the distributed unit of a fourth message sent by the centralized unit, where the fourth message includes at least one of the following information: cell ID, second signaling bearer configuration information, and second signaling bearer user plane transmission path establishment information on the side of the centralized unit ; and

the distributed unit sending a fifth message to the centralized unit, where the fifth message includes at least one of the following information: a cell ID, a second signaling bearer identifier, and second signaling bearer user plane transmission path establishment information on the side of the distributed unit.

In an exemplary embodiment, a distributed block sending a first message to a centralized block includes:

sending, by the distributed unit, a first message to the centralized unit via a user plane transmission path corresponding to second signaling bearer user plane transmission path establishment information on the centralized unit side; and

carrying by the distributed unit the cell ID and/or the second terminal ID in the first message when the first message is sent to the centralized unit.

In an exemplary embodiment, the reception by the distributed unit of the second message sent by the centralized unit includes:

the distributed unit receiving, via the user plane transmission path corresponding to the second information about establishing the user plane transmission path of the signaling bearer on the side of the distributed unit, the second message sent by the centralized unit; and

receiving by the distributed unit the cell ID and/or the third terminal ID which is included in the second message sent by the centralized unit.

In another possible embodiment, before the distributed unit sends the first message to the centralized unit, the method further includes:

the distributed unit sending a sixth message to the centralized unit, where the sixth message is used to request to establish, for the terminal, a user plane transmission path that is between the distributed unit and the centralized unit and which is a second signaling bearer, and the sixth message includes at least one of the following: a first terminal ID corresponding to the terminal, a second terminal ID corresponding to the terminal, and a cell ID to which the terminal has access; and

the distributed unit receiving the seventh message sent by the centralized unit, wherein the seventh message includes the third terminal identifier and the second signaling bearer user plane transmission path establishment information on the centralized unit side.

Optionally, the method further includes:

sending, by the distributed unit, second information about establishing a transmission path of the user plane of the signaling bearer on the side of the distributed unit to the centralized unit.

In an exemplary embodiment, the distributed unit carries the second signaling bearer user plane path establishment information on the distributed unit side into a sixth message and sends the sixth message to the centralized unit.

In an exemplary embodiment, a distributed block sending a first message to a centralized block includes:

sending, by the distributed unit, a first message to the centralized unit via a user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the centralized unit side.

In an exemplary embodiment, the reception by the distributed unit of the second message sent by the centralized unit includes:

the distributed unit receiving a second message on a user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the side of the distributed unit.

The second aspect of the present application provides a wireless connection management method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and way includes:

receiving by the distributed unit a first message sent by the terminal, where the first message is used to request an air interface control plane connection establishment for the terminal;

sending a distributed block of an eighth message to the terminal based on the first message, where the eighth message is used to instruct to establish an air interface control plane connection for the terminal; and

the distributed unit sending a ninth message to the centralized unit, where the ninth message includes a connection parameter used to establish an air interface control plane connection.

In an exemplary embodiment, the connection parameter used to establish a radio interface control plane connection includes at least one of the following information: a fourth terminal identifier corresponding to the terminal and a reason for establishing a terminal control plane connection, where the fourth terminal identifier is a terminal identifier allocated core network, or the fourth terminal ID is a random number.

According to the first aspect and the second aspect, the method further includes:

sending by the distributed unit information about the establishment of a user plane transmission path on the side of the distributed unit to the centralized unit through the control plane connection between the distributed unit and the centralized unit, where

the user plane transmission path establishment information on the distributed block side includes at least one of the following information: first signaling bearer user plane transmission path establishment information on the distributed block side, and third signaling bearer user plane transmission path establishment information on the distributed block side. side of the distributed block.

Optionally, the method further includes:

receiving, by the distributed unit via a control plane connection between the distributed unit and the centralized unit, the first signaling bearer configuration information and/or the third signaling bearer configuration information that are/are sent by the centralized unit, where

the first signaling bearer configuration information includes at least one of the following information: a first signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish the first signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the first signaling bearer, and the first signaling bearer user plane transmission path establishment information on the centralized unit side; and

the third signaling bearer configuration information includes at least one of the following information: a third signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the third signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the third signaling bearer, and second signaling bearer user plane transmission path establishment information on the centralized unit side.

Optionally, the method further includes:

receiving, by the distributed unit, the bearer configuration information sent by the centralized unit; and

sending by the distributed unit information about the establishment of the transmission path of the user plane of the data bearer on the side of the distributed unit to the centralized unit, where

the bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

A third aspect of the present application provides a connection control method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and the method includes:

receiving, by the distributed unit, an access request message sent by the terminal;

obtaining, by a distributed block based on the access request message, a first terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface;

sending by the distributed block the first terminal identifier to the terminal; and

sending by the distributed unit the first terminal ID and/or cell ID to the centralized unit.

In an exemplary embodiment, the first terminal identifier is allocated in a distributed block.

Optionally, the method further includes:

the distributed unit sending a first request message to the centralized unit, where the first request message is used to request the centralized unit to allocate a set of terminal identifiers; and

receiving by the distributed unit the terminal ID set sent by the centralized unit, where the terminal ID set includes the first terminal ID.

A fourth aspect of the present application provides a connection control method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and the method includes:

receiving, by the distributed unit, an access request message sent by the terminal;

the distributed unit sending a second request message to the centralized unit based on the access request message, where the second request message is used to request the centralized unit to allocate a first terminal identifier for the terminal;

receiving by the distributed unit the first terminal ID sent by the centralized unit; and

sending by the distributed block the first terminal identifier to the terminal.

Optionally, the second request message includes a cell identifier corresponding to the cell being accessed by the terminal.

Optionally, the first terminal identifier is a unique wireless network identifier.

A fifth aspect of the present application provides a wireless connection management method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and way includes:

receiving by the centralized unit a first message sent by the distributed unit, where the first message is used to request an air interface control plane connection establishment for the terminal; and

sending, by the centralized unit, a second message to the distributed unit, where the second message is used to instruct to establish an air interface control plane connection between the terminal and the distributed unit.

In an exemplary embodiment, the first message is included in a third message for transmission, and the third message is transmitted over a control plane connection between the distributed unit and the centralized unit; and the third message further includes at least one of the following information:

the first terminal identifier corresponding to the terminal, the identifier of the cell accessed by the terminal, and the second terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface, and the second terminal identifier is an identifier allocated by the allocated block for the terminal over the plane interface control between the distributed unit and the centralized unit.

Optionally, the second message is sent over a control plane connection; respectively, wherein the second message includes a third terminal identifier; and the third terminal ID is an ID allocated by the centralized unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

Optionally, the method further includes:

sending, by the centralized unit, the first signaling bearer configuration information to the distributed unit.

Optionally, the first signaling bearer configuration information includes at least one of the following information:

the first signaling bearer identifier, the media access control layer configuration parameter used by the distributed unit to establish the first signaling bearer, the physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, the logical channel configuration parameter used by the distributed unit to establishing a first signaling bearer, and first information about establishing a signaling bearer user plane transmission path on the centralized unit side.

In an exemplary embodiment, the centralized unit sends the first signaling bearer configuration information via a second message.

Optionally, the method further includes:

receiving, by the centralized unit, first signaling bearer user plane transmission path establishment information which is on the side of the distributed unit and which is sent by the distributed unit.

In an exemplary embodiment, the reception by the centralized unit of the first signaling bearer user plane transmission path establishment information that is on the side of the distributed unit and that is sent by the distributed unit includes:

receiving, by the centralized unit, first information about the establishment of a transmission path of the user plane of the signaling bearer on the side of the distributed unit through the third message.

In another possible embodiment, before the centralized unit receives the first message sent by the distributed unit, the method further includes:

the centralized unit sending a fourth message to the distributed unit, where the fourth message includes at least one of the following information: a cell ID, second signaling bearer configuration information, and second signaling bearer user plane transmission path establishment information on the centralized unit side; and

reception by the centralized unit of the fifth message sent by the distributed unit, where the fifth message includes at least one of the following information: a cell identifier, a second signaling bearer identifier, and a second signaling bearer user plane transmission path establishment information on the distributed unit side.

In an exemplary embodiment, the reception by the centralized unit of the first message sent by the distributed unit includes:

receiving, by the centralized unit, a first message on a user plane transmission path corresponding to the second information about the establishment of a user plane transmission path of the signaling bearer on the centralized unit side.

In a possible embodiment, sending a second message to the distributed unit by the centralized unit includes:

sending, by the centralized unit, a second message to the distributed unit via a user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the distributed unit side.

In another possible embodiment, before the centralized unit receives the first message sent by the distributed unit, the method further includes:

the centralized unit receiving a sixth message sent by the distributed unit, where the sixth message is used to request to establish, for the terminal, a user plane transmission path that is between the distributed unit and the centralized unit and which is a second signaling bearer, and the sixth message includes at least one of the following information: a first terminal ID corresponding to the terminal, a second terminal ID corresponding to the terminal, and a cell ID to which the terminal has access; and

sending, by the centralized unit, a seventh message to the distributed unit, wherein the seventh message includes the third terminal identifier and the second signaling bearer user plane transmission path establishment information on the centralized unit side.

Optionally, the method further includes:

receiving, by the centralized unit, second signaling bearer user plane transmission path establishment information which is on the side of the distributed unit and which is sent by the distributed unit.

In an exemplary embodiment, the second signaling bearer user plane transmission path establishment information on the distributed block side is carried in the sixth message for transmission.

In an exemplary embodiment, the reception by the centralized unit of the first message sent by the distributed unit includes:

receiving, by the centralized unit, a first message on a user plane transmission path corresponding to the second information about the establishment of a user plane transmission path of the signaling bearer on the centralized unit side.

In a possible embodiment, sending a second message to the distributed unit by the centralized unit includes:

sending, by the centralized unit, a second message to the distributed unit via a user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the distributed unit side.

A sixth aspect of the present application provides a method for managing a wireless connection, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and way includes:

receiving, by the centralized unit, a ninth message sent by the distributed unit, wherein the ninth message includes a connection parameter used to establish an air interface control plane connection; and

executing, by the centralized processing unit, a connection control based on the connection parameter used to establish an air interface control plane connection.

In an exemplary embodiment, the connection parameter used to establish a radio interface control plane connection includes at least one of the following information: a fourth terminal identifier corresponding to the terminal and a reason for establishing a terminal control plane connection, where the fourth terminal identifier is a terminal identifier allocated core network, or the fourth terminal ID is a random number.

For the fifth aspect and the sixth aspect, the method further includes:

reception by the centralized unit of information about the establishment of the user plane transmission path on the side of the distributed unit through the control plane connection between the distributed unit and the centralized unit, where

the user plane transmission path establishment information on the distributed block side includes at least one of the following information: first signaling bearer user plane transmission path establishment information on the distributed block side, and third signaling bearer user plane transmission path establishment information on the distributed block side. side of the distributed block.

Optionally, the method further includes:

sending, by the centralized unit, first signaling bearer configuration information and/or third signaling bearer configuration information to the distributed unit via a control plane connection between the distributed unit and the centralized unit, where

the first signaling bearer configuration information includes at least one of the following information: a first signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish the first signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the first signaling bearer, and the first signaling bearer user plane transmission path establishment information on the centralized unit side; and

the third signaling bearer configuration information includes at least one of the following information: a third signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the third signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the third signaling bearer, and third signaling bearer user plane transmission path establishment information on the centralized unit side.

Optionally, the method further includes:

sending, by the centralized unit, information about the configuration of the data bearer to the distributed unit; and

reception by the centralized unit information about the establishment of the transmission path of the user plane of the bearer data channel, which is on the side of the distributed unit and which is sent by the distributed unit, where

the bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

A seventh aspect of the present application provides a connection control method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and the method includes:

receiving by the centralized unit a first terminal ID and/or cell ID that are sent by the distributed unit, where the first terminal ID is used to identify the terminal over the air interface; and

execution by the centralized processing unit of the connection control based on the first terminal ID.

In an exemplary embodiment, the first terminal identifier is allocated in a distributed block.

Optionally, the method further includes:

receiving, by the centralized unit, a first request message sent by the distributed unit, where the first request message is used to request the centralized unit to allocate a set of terminal identifiers;

allocation by the centralized unit of a set of terminal identifiers; and

sending, by the centralized unit, the terminal ID set to the distributed unit, where the terminal ID set includes the first terminal ID.

An eighth aspect of the present application provides a connection control method, wherein the method relates to a base station system, wherein the base station system includes a centralized unit and a distributed unit, the centralized unit communicates with the distributed unit, the distributed unit communicates with a terminal via an air interface, and the method includes:

receiving, by the centralized unit, a second request message sent by the distributed unit, where the second request message is used to request the centralized unit to allocate a first terminal identifier to the terminal;

allocation by the centralized unit of the first identifier of the terminal for the terminal; and

sending, by the centralized unit, the first terminal ID to the distributed unit.

Optionally, the second request message includes a cell identifier corresponding to the cell being accessed by the terminal.

Optionally, the first terminal identifier is a unique wireless network identifier.

The ninth aspect of the present application provides a distributed block, where the distributed block has the functions of implementing the distributed block in the first aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, a distributed unit may include a receive module, a processing module, and a send module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive the first message sent by the terminal; the processing module is configured to process the first message; and the sending module is configured to send the first message to the centralized unit.

The tenth aspect of the present application provides a distributed block, where the distributed block has the functions of implementing the distributed block in the second aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, a distributed unit may include a receive module, a processing module, and a send module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive the first message sent by the terminal; the processing module is configured to send an eighth message to the terminal based on the first message, where the eighth message is used to instruct to establish an air interface control plane connection for the terminal; and the sending module is configured to send the ninth message to the centralized unit, where the ninth message includes a connection parameter used to establish a radio interface control plane connection.

The eleventh aspect of the present application provides a distributed block, where the distributed block has the functions of implementing the distributed block in the third aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, a distributed unit may include a receive module, a processing module, and a send module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive an access request message sent by the terminal; the processing module is configured to obtain, based on the access request message, the first terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface; and the sending module is configured to send the first terminal ID to the centralized unit and the terminal.

The twelfth aspect of the present application provides a distributed block, where the distributed block has the functions of implementing the distributed block in the fourth aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, a distributed unit may include a receive module, a processing module, and a send module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive an access request message sent by the terminal; the processing module is configured to send a second request message to the centralized unit based on the access request message; and the sending module is configured to send the first terminal ID to the terminal.

The thirteenth aspect of the present application provides a centralized unit, where the centralized unit has the functions of implementing the centralized unit in the fifth aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, the centralized unit may include a receiving module, a processing module, and a sending module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive the first message sent by the distributed unit; the processing module is configured to generate a second message based on the first message; and the sending module is configured to send a second message to the distributed unit, where the second message is used to instruct to establish an air interface control plane connection between the terminal and the distributed unit.

The fourteenth aspect of the present application provides a centralized unit, where the centralized unit has the functions of implementing the centralized unit in the sixth aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, the centralized unit may include a receiving module and a processing module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive a ninth message sent by a distributed unit, where the ninth message includes a connection parameter used to establish an air interface control plane connection; and the processing module is configured to process the connection control based on the connection parameter used to establish the radio interface control plane connection.

The fifteenth aspect of the present application provides a centralized unit, where the centralized unit has the functions of implementing the centralized unit in the seventh aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, the centralized unit may include a receiving module and a processing module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive the first terminal ID sent by the distributed block, where the first terminal ID is used to identify the terminal over the air interface; and the processing module is configured to process the connection control based on the first terminal ID.

The sixteenth aspect of the present application provides a centralized unit, where the centralized unit has the functions of implementing the centralized unit in the eighth aspect. These functions may be implemented in hardware or may be implemented in hardware by executing appropriate software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, the centralized unit may include a receiving module, a processing module, and a sending module. These modules can perform the corresponding functions in the above method. For example, the receiving module is configured to receive a second request message sent by the distributed unit; the processing module is configured to allocate the first terminal identifier for the terminal; and the sending module is configured to send the first terminal ID to the distributed unit.

The seventeenth aspect of the present application provides a distributed unit, where the distributed unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the first aspect and implementations of the first aspect.

An eighteenth aspect of the present application provides a distributed unit, where the distributed unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the second aspect and implementations of the second aspect.

The nineteenth aspect of the present application provides a distributed unit, where the distributed unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the third aspect and implementations of the third aspect.

The twentieth aspect of the present application provides a distributed unit, where the distributed unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the fourth aspect and implementations of the fourth aspect.

The twenty-first aspect of the present application provides a centralized unit, where the centralized unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the fifth aspect and implementations fifth aspect.

The twenty-second aspect of the present application provides a centralized unit, where the centralized unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the sixth aspect and implementations sixth aspect.

The twenty-third aspect of the present application provides a centralized unit, where the centralized unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the seventh aspect and implementations seventh aspect.

The twenty-fourth aspect of the present application provides a centralized unit, where the centralized unit includes a memory and a processor, wherein the memory is configured to store a program instruction, and the processor is configured to recall the program instruction from the memory so as to implement the method according to the eighth aspect and implementations eighth aspect.

The twenty-fifth aspect of the present application provides a base station system including any distributed unit from the ninth aspect to the twelfth aspect and any centralized unit from the thirteenth aspect to the sixteenth aspect.

Brief description of the drawings

Fig. 1 is a CU-DU separation scheme;

Fig.2 is a simplified block diagram of the protocol layers of the base station of the 5G system;

3 is a schematic flowchart of establishing an RRC connection by a terminal through random access in an LTE system;

Fig. 4 is a schematic flowchart of Embodiment 1 of the connection control method according to the present application;

Fig. 5 is a schematic flowchart of Embodiment 2 of the connection control method according to the present application;

Fig. 6 is a schematic flowchart of Embodiment 3 of the connection control method according to the present application;

Fig. 7 is a schematic flowchart of Embodiment 4 of the connection control method according to the present application;

Fig. 8 is a schematic flowchart of Embodiment 5 of the connection control method according to the present application;

Fig. 9 is a schematic flowchart of Embodiment 6 of the connection control method according to the present application;

Fig. 10 is a schematic flowchart of Embodiment 7 of the connection control method according to the present application;

11 is a modular block diagram of an embodiment of a distributed unit according to the present application;

12 is a modular block diagram of an embodiment of another distributed unit according to the present application;

13 is a modular block diagram of an embodiment of yet another distributed unit according to the present application;

14 is a modular block diagram of an embodiment of yet another distributed unit according to the present application;

15 is a modular block diagram of an embodiment of a centralized unit according to the present application;

16 is a modular block diagram of an embodiment according to the present application;

17 is a modular block diagram of an embodiment according to the present application;

18 is a modular block diagram of an embodiment according to the present application;

Fig. 19 is a block diagram of an object of an embodiment of a distributed block according to the present application;

Fig. 20 is a block diagram of an object of an embodiment of another distributed block according to the present application;

Fig. 21 is a block diagram of an object of an embodiment of yet another distributed block according to the present application;

Fig. 22 is a block diagram of an object of an embodiment of yet another distributed block according to the present application;

Fig. 23 is a block diagram of an object of an embodiment of a centralized unit according to the present application;

Fig. 24 is a block diagram of an object of an embodiment according to the present application;

Fig. 25 is a block diagram of an object of an embodiment according to the present application; and

26 is a block diagram of an object of an embodiment according to the present application.

Detailed description of the invention

With the rapid development of technologies for terminals and the increasing requirements for terminals, a 5G system or New radio (NR) access technology will soon appear. A 5G system or an NR system can provide a higher transmission rate than a Long Term Evolution (LTE) network. The maximum theoretical data transfer rate of a 5G system or NR system can reach tens of gigabytes (Gigabyte, Gb) per second.

The architecture of the access network in the existing 2/3/4G network mainly includes a core network and an access network. However, there is basically no service layer interconnection between access networks. For example, the Iur interface in 3G is used for signaling and communication between RNCs, and the base station X2 interface in 4G is mainly used for resource preparation signaling for UE handover between base stations or is used for signaling and communication between eNodeBs. Thus, it is difficult to perform dynamic (or semi-dynamic) joint adaptation in various aspects such as resource coordination, processing load balancing, and interference suppression. In terms of equipment room layout, not only the physical base station but also the logical base station are versatile. The base stations are separated from each other and do not have significant communication with each other.

In the current 5G technology, when a base station (gNB) includes a centralized unit (CU) and a distributed unit (Distributed Unit, DU), the CU is usually responsible for the centralized radio resource and connection management, and the DU usually includes includes functions for realizing distributed user plane processing, mainly a physical layer processing function and a layer 2 function, which has relatively high real-time requirements.

The CU device includes the function of processing the wireless upper layer protocol stack, such as the Radio Resource Control (RRC) layer or the Packet Data Convergence Protocol (PDCP) layer, and can even support the movement of some functions of the core network up to to the access network, forming an edge computing network that can meet higher network latency requirements for emerging services such as video, online shopping, and virtual/augmented reality in the future communication network. Due to the change in the structure of the communication network element, the protocol stack is adjusted and changed accordingly. Therefore, the name of the next generation network, NR (new radio) 5G, also vividly reflects the radical changes in many aspects of the future 5G network.

The CU covers the upper layer protocol stack of the wireless access network and some core network functions, and the DU covers the physical baseband processing layer and some layer 2 functions. The CU can be deployed in a centralized manner. Deployment of DU depends on the actual network environment. The DU may also be deployed in a centralized manner in a central urban area or in an area such as a college or large event area with relatively high traffic density, relatively short distance between sites, and limited equipment room resources. A DU may be deployed in a distributed manner in an area, such as a suburban or mountainous area, which has a relatively low traffic density, a relatively large distance between sites, and the like.

In the existing LTE system, when a terminal initially accesses a network, or transitions from an idle state to an active state, or is transferred to a new cell, or a radio link fails, or the like, a wireless connection must be established or reacquired. In this case, a process such as establishing an RRC connection or reestablishing an RRC connection may be started. In the existing cellular wireless system, a base station used as a stand-alone base station of a device supports all protocol layer processing. Both the establishment of a wireless connection and the processing of protocol layer messages such as the associated MAC message and the RRC message are directly completed by the base station.

In a 5G system, the gNB may use the CU-DU architecture. Many possibilities can be provided for separating the functions of the CU-DU. Figure 1 shows a CU-DU separation scheme. As shown in FIG. 1, the CU-DU architecture includes RRC, PDCP, high layer RLC, low layer RLC, high layer MAC, low layer MAC, high physical layer (Physical Layer, PHY), low PHY, and radio frequency (Radio frequency, RF). Option 1 may be a split between RRC and PDCP. Option 2 - separation between PDCP and RLC. Option 3 - split the RLC into two parts. The real-time low demand function is placed in the high-level RLC, the real-time high demand function is placed in the low-level RLC, and separation is performed between the high-level RLC and the low-level RLC. Option 4 - separation between RLC and MAC. Option 5 - separation between high level MAC and low level MAC. Option 6 - separation between low level MAC and high PHY. Option 7 - separation between high PHY and low PHY. Option 8 - separation between low PHY and RF. For example, in option 2, for the downlink RRC message and data processing, the CU generates an RRC message or data, and after processing the PDCP layer, transmits a PDCP (Protocol Data Unit, PDU) (namely, an RLC (Service Data Unit) , SDU)) to the DU via the interface between the CU and the DU. After appropriate RLC, MAC and PHY processing, the DU further sends the result with the processed PHY to the wireless channel via RF for transmission. For the uplink RRC message and data processing, after receiving the DU, the data packet through the RF device, the data packet undergoes PHY, MAC, and RLC processing in sequence, and then the DU transmits the RLC SDU (namely, the PDCP PDU) to the CU through the interface between CU and DU. The CU further obtains the RRC message or data through the processing of the PDCP layer, and accordingly sends the RRC message or data to the RRC layer or the application layer. It should be especially noted that with the development of communication technologies, the function of the protocol layer, and the method of naming the base station, and the content of the message and its name may be different from the above in LTE. For example, the original RLC layer reordering function may be moved to the PDCP layer. In another example, the original RRC connection request message may have a different name. In the present application, no restrictions are imposed on the protocol layer, protocol layer function, protocol layer name, and protocol layer message name of a particular CU or DU. For ease of description, the protocol layer name and the corresponding message name in LTE are used as examples to describe the corresponding solution.

With reference to the options shown in FIG. 1, FIG. 2 shows a simplified block diagram of the protocol layers of a base station of a 5G system. As shown in FIG. 2, a CU includes an RRC layer and a PDCP layer, and a DU includes an RLC layer, a MAC layer, and a PHY layer.

The terms "first", "second" and the like, mentioned in this application, are not intended to indicate any order, quantity or importance, but are simply used to distinguish between components. Likewise, the singular forms of nouns are not intended to indicate the limitation of any number, but are intended to indicate the presence of at least one. The terms "connection", "communication line", and the like are not limited to a physical or mechanical connection, but may include an electrical connection, direct or indirect.

Used in this application, the term "module" usually refers to a program or instruction that is stored in memory and can implement some functionality. Used in this description, the term "block" usually refers to a functional structure, divided on the basis of a logical scheme. A "block" may be implemented in hardware alone, or implemented in a combination of software and hardware.

As used in this application, the term "set" refers to two or more than two elements. The term "and/or" describes an association relationship for describing associated objects and represents that three relationships can exist. For example, A and/or B can represent the following three cases: only A exists, both A and B exist, and only B exists. The sign "/" usually indicates an "or" relationship between associated objects.

The technologies described in this application can be applied in various communication systems, for example, in existing 2G and 3G communication systems and a new radio access network, for example, in the Global System of Mobile Communication (GSM), a multiple access system with Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wideband Code Division Multiple Access Wireless (WCDMA), Multiple Access System Frequency Division Multiple Addressing (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single Carrier FDMA (SC-FDMA), General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Development System (Lon g Term Evolution, LTE), UMTS networks and other communication system. The new radio access network allows for a higher transmission speed than the LTE network. The new radio access network is also referred to as 5G network, next generation network, and the like.

In this specification, various aspects are described with respect to a terminal and/or a base station and/or a controller and/or a base station controller.

The Terminal Device may be a wireless terminal or a wired terminal. The wireless terminal may be a device that enables the terminal to transmit voice messages and/or data, a portable device with a wireless connection function, or other processing device connected to the wireless modem. A wireless terminal may communicate with one or more core networks via a radio access network (eg, Radio Access Network, RAN). A wireless terminal may be a mobile terminal such as a mobile phone (also referred to as a "cellular" phone) and a computer with a mobile terminal, for example, may be a handheld, handheld, laptop, embedded computer, or mobile device. installed on a vehicle that exchanges voice messages and/or data with a radio access network. For example, a wireless terminal may be a device such as a Personal Communication Service (PCS) telephone, a cordless telephone, a Session Initiation Protocol (SIP) telephone, a Wireless Local Loop (WLL) ) or a personal digital assistant (Personal Digital Assistant, PDA). A wireless terminal may also be referred to as a system, Subscriber Unit, Subscriber Station, Mobile Station, Mobile Console, Remote Station, Access Point, Remote terminal (Remote Terminal), access terminal (Access Terminal), user terminal (User Terminal), user equipment (User Equipment) or user agent (User Agent).

A base station (namely, a node) may be a device that communicates with a wireless terminal over an air interface in an access network via one or more sectors. The base station may be configured to interconvert the received wireless frame and IP packet and may serve as a router between the wireless terminal and the remainder of the access network, where the remainder of the access network may include an Internet Protocol (IP) based network. The base station may further coordinate the control of the radio interface attributes. For example, a base station may be a Base Transceiver Station (BTS) in a GSM or CDMA system, or may be a Node B (NodeB) in a WCDMA system, or may be an evolved Node B (eNodeB, eNB, or e-NodeB). ) in the LTE system. In the present application, this is not a limitation. The new radio access network device is also referred to as gNB (gNB), NR node or new radio (NR) base station (Base Station, BS), new RAN node (node), or new RAN BS (base station), and is not limited to in this document. However, in this specification, for ease of description, the access network device is generically referred to as a gNB.

The base station controller (namely, the control node) may be a base station controller (Base Station Controller, BSC) in GSM or CDMA, or may be a radio network controller (Radio Network Controller, RNC) in WCDMA. The present application is not limited to this.

FIG. 3 is a schematic flowchart of establishing an RRC connection by a terminal through random access in an LTE system. As shown in FIG. 3, the process of establishing an RRC connection by a terminal through random access in the LTE system is as follows.

S301. The terminal sends a random access preamble to the base station.

The terminal sends a random access preamble to the base station on a Physical Random Access Channel (PRACH) to notify the base station of the presence of a random access request and allow the base station to estimate the transmission delay between the base station and the terminal and calibrate the uplink timing. based on transmission delay.

S302. The base station sends a Random Access Response (RAR) to the terminal.

After sending the random access preamble, the terminal controls the Physical Downlink Control Channel (PDCCH) in the RAR time window. If the RAR returned by the base station is not received within the RAR time window, this random access process is considered to have failed.

The Protocol Data Unit MAC RAR (Protocol Data Unit, PDU) carries the Cell Radio Network Temporary Identifier (C-RNTI). If the terminal does not have a unique C-RNTI used for cell access, the C-RNTI in the MAC RAR PDU of the terminal is used as the Temporary C-RNTI (TC-RNTI). TC-RNTI is used for subsequent transmission between a terminal and a base station. After conflict resolution, the value can be changed to C-RNTI.

S303. The terminal sends an RRC connection request to the base station.

The RRC connection request includes a unique terminal identifier. This identifier is used for conflict resolution in step S304. For a terminal in the RRC_CONNECTED state (RRC connection established), the terminal's unique identifier is C-RNTI. For a terminal in the non-RRC_CONNECTED state (RRC connection not established), a unique terminal identifier (S-TMSI or random number) is used as the terminal identifier from the core network side.

When the terminal sends an RRC connection request during the random access process, if the terminal does not have a C-RNTI, the terminal may use the terminal identifier (S-TMSI or random number) of the core network.

S304. The base station sends an RRC connection establishment message to the terminal.

In the contention resolution mechanism, the base station carries the unique terminal identifier corresponding to the RRC connection request in the contention resolution ID MAC control message of the UE in order to pinpoint the winning terminal. The winning terminal confirms based on the terminal's unique identifier that the terminal wins and then uses the TC-RNTI as the C-RNTI.

S305. The terminal sends an RRC connection establishment completion message to the base station.

From the above steps, it can be learned that in an LTE system, a base station used as a stand-alone device performs processing in an RRC connection establishment process. However, with the development of the system, after the base station is divided into two independent functional entities, namely DU and CU, based on the protocol stack, the existing processing method cannot be used directly.

The wireless connection management method provided in the present application is intended to solve the aforementioned problem of the prior art.

When a terminal accesses a wireless network, the access network device needs to allocate an identifier (which is referred to as the first terminal identifier) to the terminal in order to identify the terminal over the air interface between the access network device and the terminal. The first terminal identifier may be, for example, C-RNTI. In the system architecture to which the present application applies, the first terminal identifier is allocated by the base station system, and in particular, may be allocated by a distributed unit, or may be allocated by a centralized unit, or may be jointly allocated by a distributed unit and a centralized unit. The following specifically describes implementations in which the base station system allocates the above identifier.

In order to help those skilled in the art understand the solution presented in this application, the following embodiment of allocating the first terminal ID for the example description in this application uses a procedure in which the terminal initiates a random access request in the base station system and then initiates a request for RRC connection. However, it should be noted that the process of allocating the first terminal ID in the following embodiment can also be applied to another process in which it is necessary to allocate the first terminal ID. For example, in the following embodiment, the random access request may also be another access request message. For another example, in the following embodiment, an RRC connection request may also be an RRC restore request, or the like.

Fig. 4 is a schematic flowchart of Embodiment 1 of the connection control method according to the present application. In this process, the distributed control unit allocates the first terminal ID. As shown in figure 4, the process includes the following steps.

S401. The terminal sends a random access request to the allocated block.

S402. The allocated block allocates the first terminal identifier for the terminal.

The first terminal identifier is allocated by the base station system and is used to identify the terminal over the air interface between the access network device and the terminal. In particular, the first terminal identifier may be C-RNTI.

Optionally, the first terminal identifier may be a unique wireless network identifier in a cell, or may be a unique wireless network identifier in a distributed unit, or may be a unique wireless network identifier in a centralized unit connected to a distributed unit.

In the base station system in the present application, there may be a plurality of cells in each distributed block. If the first terminal ID is a unique wireless network ID in a cell, this indicates that the first terminal ID is unique in the coverage area of one of the plurality of cells in the distributed block, and the first terminal IDs in the plurality of cells in the same distributed block may be the same. If the first terminal ID is a unique wireless network ID in a distributed block, this indicates that the first terminal ID is unique in the coverage area of the distributed block, and the first terminal IDs in different cells are different. If the first terminal ID is a unique wireless network ID in the centralized unit connected to the distributed unit, this indicates that the first terminal ID is unique in the coverage area of the centralized unit, and the first terminal IDs in different distributed units or different cells may be different.

S403. The allocated unit sends a random access response to the terminal, where the random access response includes the allocated first terminal identifier.

S404. The terminal sends an RRC connection request to the allocated block.

The RRC connection request includes a fourth terminal identifier corresponding to the terminal. In an exemplary method, the fourth terminal identifier is a terminal identifier (eg, S-Temporary Mobile Subscriber Identity (S-TMSI)) allocated by the core network entity. Alternatively, in another possible manner, the fourth terminal identifier may be a random number generated by the terminal. The fourth terminal identifier is used to identify the terminal in the control range of the core network entity.

After sending the RRC connection request, the terminal initiates timer T1.

S405. The allocated unit uses the MAC message to indicate UE contention resolution.

After receiving the RRC connection request and identifying the terminal, the distributed unit uses the MAC message to indicate the resolution of the UE contention. In particular, the MAC message carries the aforementioned fourth terminal identifier. If necessary, the aforementioned fourth terminal identifier may be carried in a MAC (Control Element, CE) control element for sending. After receiving the MAC CE, the terminal determines whether the terminal ID carried in the MAC CE matches the fourth terminal ID carried in the RRC connection request sent by the terminal. If the terminal ID carried in the MAC CE matches the fourth terminal ID carried in the RRC connection request sent by the terminal, this indicates that the terminal's random access succeeds, and then the terminal stops timer T1; or if the terminal ID carried in the MAC CE is different from the fourth terminal ID carried in the RRC connection request sent by the terminal, this indicates that the terminal's random access fails, and then the terminal stops timer T1 and may initiate a new random access request. access.

S406. The distributed unit sends an RRC connection establishment request to the centralized unit, where the RRC connection establishment request includes the first terminal identifier.

After receiving the RRC connection establishment request, the distributed unit sends an RRC connection establishment request to the centralized unit via an interface between the distributed unit and the centralized unit. If necessary, the distributed unit may transmit the above request via a control plane connection between the distributed unit and the centralized unit. In addition, in this case, an RRC connection request is sent, if necessary, in an RRC container (container). Alternatively, the distributed unit may transmit the above request via a user plane transmission path between the distributed unit and the centralized unit. The specific transmission method will be described in detail in the next embodiment of the present application.

In addition, if the aforementioned first terminal ID is a unique ID of a wireless network in a cell, the sent RRC connection request further carries the cell ID so that the centralized unit can identify the terminal after receiving the RRC connection request.

S407. The distributed block sends the first terminal ID to the centralized block.

This step is an optional step. When the distributed unit does not carry the first terminal ID in the RRC connection setup request at the time of sending the RRC connection setup request in step S406, a separate message can be used to send the first terminal ID at this step.

When the RRC connection establishment request sent in step S406 already includes the first terminal ID, this step need not be performed.

Accordingly, the cell ID processing method is also the same. This document does not re-describe the details.

S408. The centralized unit sends an RRC connection establishment message to the distributed unit.

S409. The distributed unit sends an RRC connection establishment message to the terminal.

S410. The terminal sends an RRC connection establishment completion message to the allocated block.

S411. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In the above procedure, steps S406-S408 and step S405 may be performed in reverse order. In other words, steps S406-S408 may be performed before step S405.

In the above procedure, if it is necessary to perform step S407, that is, the first terminal ID is not carried in the RRC connection establishment request, when the RRC connection establishment request is sent in step S406, steps S406 and S407 may be performed in reverse order. In other words, the distributed unit may first send the first terminal ID to the centralized unit and then send an RRC connection request to the centralized unit.

In the above procedure, the messages corresponding to steps S405 and S409 may be sent with the same physical layer message in order to save radio interface transmission resources.

In addition, after obtaining the first terminal ID, the centralized unit may perform connection control processing based on the first terminal ID. For example, after the terminal moves from the current cell to another cell, the centralized unit may obtain, based on the first terminal ID, information and the like. cells before handover of the terminal.

In this embodiment, after receiving the access request from the terminal, the distributed unit allocates the first terminal ID to the terminal, and separately sends the first terminal ID to the terminal and the centralized unit, so that in the base station system to which the present application applies, the terminal and the distributed unit and the centralized units that are in the base station system can collectively obtain the first terminal ID, ensuring the normal wireless connection of the terminal in the base station system.

It should be especially noted that the RRC connection establishment message sent by the centralized unit to the distributed unit may indicate that the centralized unit decides whether to accept the connection establishment request of the terminal or to reject the radio interface control plane connection establishment for the terminal. In this case, if the RRC connection establishment message indicates that the centralized unit rejects the radio interface control plane connection establishment for the terminal, after the distributed unit sends the RRC connection establishment message to the terminal, the distributed unit deletes all resources used and reserved for terminal, and configuration information corresponding to the terminal. Thus, in the present application, for the description of the subsequent steps, only the case where the RRC connection establishment message indicates that a wireless connection establishment request of the terminal has been received has been taken as an example. Processing in the following other implementations is similar to processing in this implementation.

In a further implementation in the above step S404, when sending an RRC connection establishment request to the distributed unit, the terminal may carry the fourth terminal ID in the MAC layer message, and after receiving the MAC layer message, the distributed unit can obtain a specific value of the fourth terminal ID. Accordingly, in step S405, when the allocated unit uses the MAC message to indicate the UE's contention resolution, the MAC message may accurately carry the fourth terminal identifier.

Specifically, in the base station system of the present application, the distributed unit cannot parse the contents of the RRC layer message, and the RRC connection establishment request sent by the terminal in step S404 is an RRC layer message. If the fourth terminal ID is directly carried in the RRC layer message, the allocated entity cannot know the specific value of the fourth terminal ID included in the RRC layer message. When the distributed block instructs the terminal to resolve collisions in step S405, the distributed block may send only the fixed bit data of the message received in step S404 to the terminal. If the fourth terminal identifier occupies a small number of bits, but the allocated block creates a copy based on the fixed bits, there may be a loss of radio interface transmission resources.

In this embodiment, the terminal carries the fourth terminal identifier in a MAC layer message used to send an RRC connection establishment request. For example, the terminal may carry a fourth terminal identifier in the MAC CE. After receiving the MAC layer message, the distributed unit can obtain the specific content of the fourth terminal identifier. In addition, when the allocated block indicates to the terminal to resolve collisions, the distributed block can carry the specific content of the fourth terminal ID in the corresponding MAC layer message without carrying redundant information. Thus, the loss of radio interface transmission resources can be avoided.

It should be noted that the method in this embodiment can be applied to all of the following embodiments of the present application. In the present application, its details are not re-described below.

FIG. 5 is a schematic flowchart of Embodiment 2 of the connection control method according to the present application. In this process, the distributed unit allocates the first terminal ID for the terminal based on the set of terminal IDs previously allocated by the centralized unit. As shown in figure 5, the process includes the following steps.

S501. The centralized block sends a set of terminal identifiers to the distributed block.

In particular, the set of terminal identifiers is the set of available first terminal identifiers in the distributed module.

Optionally, the distributed unit may send a first request message to the centralized unit to request the centralized unit to allocate a set of terminal identifiers. Alternatively, the centralized unit may actively allocate a set of terminal identifiers to the distributed unit and send the set of terminal identifiers to the distributed unit.

In the base station system of the present application, one centralized unit may be connected to a plurality of distributed units, and each distributed unit may request the centralized unit to allocate a set of terminal IDs to the distributed unit. Each first terminal identifier allocated by the distributed block for the terminal accessed by the distributed block is selected from the set of terminal identifiers.

If necessary, the terminal identifiers in the set of terminal identifiers allocated by the centralized unit to different distributed units may be the same or different. More specifically, the first terminal identifier may be unique within the coverage area of the centralized unit or unique within the coverage area of the distributed unit. The centralized unit may allocate a set of terminal identifiers based on network configuration requirements.

S502. The terminal sends a random access request to the allocated block.

S503. The distributed unit selects a terminal ID from the set of terminal IDs as the first terminal ID corresponding to the terminal.

In other words, the above set of terminal IDs includes the first terminal ID corresponding to the terminal.

After obtaining the set of terminal identifiers, the distributed entity may allocate the first terminal identifier for the terminal being accessed based on the cases in which the first terminal identifier is unique in the cell or is unique in the distributed entity.

In particular, if the first terminal identifier is a unique identifier of the wireless network in the cell, when the allocated entity selects the first terminal identifier from the set of terminal identifiers for the terminal being accessed, the distributed entity must select a terminal identifier that has not been used in the cell in which the terminal , which is being accessed, is located as the first identifier of the terminal being accessed. If the first terminal ID is a unique wireless network ID in the distributed block, when the distributed block selects the first terminal ID from the set of terminal IDs for the terminal being accessed, the distributed block must select a terminal ID that was not used in the set of terminal IDs as the first identifier. terminal to be accessed.

S504. The allocated unit sends a random access response to the terminal, where the random access response includes the allocated first terminal identifier.

S505. The terminal sends an RRC connection request to the allocated block.

When it comes to a specific process, the aforementioned step S404 should be referred to. In this document, its details are not re-described.

S506. The allocated unit uses the MAC message to indicate UE contention resolution.

When it comes to a specific process, the above-mentioned step S405 should be referred to. In this document, its details are not re-described.

S507. The distributed unit sends an RRC connection establishment request to the centralized unit, where the RRC connection establishment request includes the first terminal identifier.

When it comes to a specific process, the above-mentioned step S406 should be referred to. This document does not re-describe the details.

S508. The distributed block sends the first terminal ID to the centralized block.

This step is an optional step. When the allocated block does not carry the first terminal ID in the RRC connection establishment request in step S509, a separate message can be used to send the first terminal ID in this step.

When the RRC connection establishment request sent in step S509 already includes the first terminal ID, there is no need to perform this step.

Accordingly, the processing methods of the cell ID and the distributed block ID are also the same. This document does not re-describe the details.

S509. The centralized unit sends an RRC connection establishment message to the distributed unit.

S510. The distributed unit sends an RRC connection establishment message to the terminal.

S511. The terminal sends an RRC connection establishment completion message to the allocated block.

S512. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In the above procedure, step S506 and step S507 may be performed in reverse order. In other words, step S507 may be performed before step S506.

In the above procedure, step S501 and step S502 may be performed in reverse order. In other words, step S502 may be performed before step S501.

In the above procedure, if it is necessary to perform step S508, that is, the first terminal ID is not carried in the RRC connection establishment request, when the RRC connection establishment request is sent in step S507, steps S507 and S508 may be performed in reverse order. In other words, the distributed unit may first send the first terminal ID to the centralized unit and then send an RRC connection request to the centralized unit.

In the above procedure, the messages corresponding to steps S506 and S510 may be sent with the same physical layer message in order to save radio interface transmission resources.

In this embodiment, the first terminal ID allocated by the distributed block to the terminal is selected from a set of terminal IDs sent in advance by the centralized block. In other words, the centralized unit performs division of the first terminal ID for the entire plurality of distributed units connected to the centralized unit. Thus, the flexibility of the network configuration is increased.

FIG. 6 is a schematic flowchart of Embodiment 3 of the connection control method according to the present application. In this process, the centralized unit allocates the first terminal identifier for the terminal. As shown in Fig.6, the process includes the following steps.

S601. The terminal sends a random access request to the allocated block.

S602. The distributed unit sends a second request message to the centralized unit, where the second request message is used to request the centralized unit to allocate a first terminal identifier for the terminal.

S603. The centralized unit allocates the first terminal identifier for the terminal.

The first terminal identifier may be unique within the coverage area of a cell, or may be unique within the coverage area of a distributed unit, or may be unique within the coverage area of a centralized unit.

Specifically, if the first terminal ID is unique within the coverage area of the cell, when the distributed unit sends the second request message to the centralized unit, the second request message must carry the terminal's cell ID. Then, after receiving the second request message, the centralized unit allocates, to the terminal based on the cell ID, the first terminal ID that has not been used in the cell corresponding to the cell ID.

If the first terminal identifier is unique within the coverage area of the distributed unit, the centralized unit determines, based on the interface through which the second request message is received, the distributed unit which sends the second request message, that is, determines the distributed unit to which the terminal belongs, and then allocates for a terminal, the first terminal identifier that was not used in the allocated block.

If the first terminal ID is unique within the coverage area of the centralized unit, the centralized unit allocates to the terminal the first terminal ID that has not been used in the centralized unit.

S604. The centralized block sends the first terminal ID to the distributed block.

S605. The allocated unit sends a random access response to the terminal, where the random access response includes the allocated first terminal identifier.

S606. The terminal sends an RRC connection request to the allocated block.

When it comes to a specific process, the aforementioned step S404 should be referred to. This document does not re-describe the details.

S607. The allocated block indicates the UE's contention resolution via the MAC message.

When it comes to a specific process, the above-mentioned step S405 should be referred to. This document does not re-describe the details.

S608. The distributed block sends an RRC connection request to the centralized block.

After receiving the RRC connection establishment request, the distributed unit sends an RRC connection establishment request to the centralized unit via an interface between the distributed unit and the centralized unit. If necessary, the distributed unit may transmit the aforementioned request through a control plane connection between the distributed unit and the centralized unit, or transmit the aforementioned request through a user plane transmission path between the distributed unit and the centralized unit. The specific transmission method will be described in detail in the next embodiment of the present application.

It should be noted that in this embodiment, since the first terminal ID is directly allocated by the centralized unit, the distributed unit does not need to send the first terminal ID to the centralized unit.

S609. The centralized unit sends an RRC connection establishment message to the distributed unit.

S610. The distributed unit sends an RRC connection establishment message to the terminal.

S611. The terminal sends an RRC connection establishment completion message to the allocated block.

S612. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In the above procedure, step S607 and step S608 may be performed in reverse order. In other words, step S608 may be performed before step S607.

In the above procedure, messages corresponding to steps S607 and S610 may be sent with the same physical layer message in order to save radio interface transmission resources.

In another embodiment, the first terminal identifier allocated by the distributed block to the terminal may be selected from a set of terminal identifiers sent in advance by the centralized block. In other words, the centralized unit performs division of the first terminal ID for the entire plurality of distributed units connected to the centralized unit. Thus, the flexibility of the network configuration is increased.

After receiving the first terminal identifier, the terminal may initiate an air interface control plane connection request. For example, the terminal may initiate an RRC connection request, or the terminal may initiate an RRC re-establishment request. If necessary, the terminal may obtain the first terminal identifier based on any of the various methods by which the base station system allocates the first terminal identifier in the above implementation cases, or the terminal may obtain the first terminal identifier in another manner. For example, in a handover scenario, a terminal obtains, in a source cell through an air interface control plane reconfiguration message (eg, an RRC connection reconfiguration message in LTE), the first terminal identifier allocated by the target base station to the terminal, and after handover to the new cell in the target base station, the terminal initiates an air interface control plane connection request via the first terminal identifier. In a further embodiment of the present application, a procedure for handling interaction between a distributed unit and a centralized unit after a terminal initiates a control plane connection request is described, and mainly relates to a method for transmitting a message corresponding to a control plane connection request.

For ease of description, the following embodiment of the present application describes the technical solution of the present application by way of an example in which a terminal initiates an RRC connection request. However, it is clear that the method described in the following embodiment of the present application can also be applied to another radio interface control plane connection processing procedure.

After the terminal initiates an RRC connection request, the distributed unit receives the RRC connection request, and then the distributed unit sends the RRC connection request to the centralized unit. The following are at least a few specific ways to send an RRC connection request:

(1) transmission over a control plane connection between a distributed unit and a centralized unit;

(2) transmission on a dedicated user plane transmission path set for the cell accessed by the terminal; and

(3) transmission via a dedicated user plane transmission path established for the terminal.

Next, the specific processes for implementing the above transmission methods in cases of different methods for allocating the first terminal ID are described separately.

FIG. 7 is a schematic flowchart of Embodiment 4 of the wireless connection control method according to the present application. In this process, an RRC connection message is transmitted over a control plane connection between a distributed unit and a centralized unit. As shown in Fig.7, the process includes the following steps.

S700. Establish a control plane interface between the distributed unit and the centralized unit.

S701. The terminal receives the first terminal identifier.

If necessary, the terminal may obtain the first terminal identifier based on any of the various methods by which the base station system allocates the first terminal identifier in the above implementation cases, or the terminal may obtain the first terminal identifier in another manner. For example, in a handover scenario, the terminal obtains in the source cell through an air interface control plane reconfiguration message (e.g., an RRC connection reconfiguration message in the LTE system) the first terminal identifier assigned by the target base station to the terminal, and after the handover, the new cell in the target base station, the terminal initiates a radio interface control plane connection request using the first terminal identifier.

S702. The terminal sends an RRC connection request (first message) to the allocated block.

The first message is used to request the establishment of an air interface control plane connection for the terminal.

When it comes to a specific process, the aforementioned step S404 should be referred to. This document does not re-describe the details.

S703. The distributed unit sends an RRC connection request (first message) to the centralized unit via the control plane connection.

If necessary, before step S703, the distributed unit establishes a control plane connection between the distributed unit and the centralized unit in advance. Accordingly, at this stage, the distributed unit sends an RRC connection request to the centralized unit via the pre-established control plane connection.

Specifically, the distributed unit sends a control plane message (referred to as the third message) to the centralized unit, where the third message includes an RRC connection request. If necessary, the RRC connection request may be carried in a container, and then the container is carried in a third message to be sent.

In addition, the third message may further include at least one of the following information:

a first terminal ID corresponding to the terminal, an ID of a cell accessed by the terminal, and a second terminal ID corresponding to the terminal.

The first terminal ID is used to identify the terminal over the air interface, and the second terminal ID is an ID assigned by the distributed unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

If necessary, all of the above three pieces of information may be sent in a third message, or some of the above three pieces of information may be sent in a third message and the remaining pieces of information may be sent in another control plane message, or all of the above three pieces of information may be sent via another control plane message.

S704. The centralized unit sends an RRC connection establishment message (second message) to the distributed unit.

The second message is used to instruct to establish an air interface control plane connection between the terminal and the distributed unit.

According to step S703, at this step, the centralized unit may send the second message through the pre-established control plane connection. Accordingly, the distributed unit receives the second control plane connection message. In other words, the second message is a control plane message, and the second message may carry an RRC connection establishment message. Optionally, an RRC connection request can be added to the container and the container is then carried in a second message to be sent.

In addition, the second message may further include a third terminal identifier.

The third terminal ID is an ID assigned by the centralized unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

If necessary, the aforementioned third terminal identifier may be sent via another control plane message.

S705. The distributed unit sends an RRC connection establishment message to the terminal.

S706. The terminal sends an RRC connection establishment completion message to the allocated block.

S707. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In the above procedure, the sequence in which steps S700 and S701 are performed is not limited. In other words, step S701 may be performed before step S700.

In this embodiment, the distributed unit sends a control plane connection request through the control plane connection between the distributed unit and the centralized unit, and receives an RRC connection establishment message through the control plane between the distributed unit and the centralized unit, so that the message in the RRC connection process is sent based on the control plane message, thereby improving the efficiency of sending and receiving the RRC connection message.

In addition, in the above process, the distributed unit may further configure the first signaling bearer. More specifically, the distributed unit may receive the first signaling bearer configuration information sent by the centralized unit.

In this embodiment of the present application, the first signaling bearer is the bearer used to transmit the radio interface control plane connection message, and the relationship between the first signaling bearer, and the next second signaling bearer and the third signaling bearer is as follows: control plane connection messages radio interfaces are classified into many types. For example, three types are presented in the present application. The second signaling bearer is used to transmit the initial radio interface control plane connection message (eg, RRC connection request and RRC connection establishment message). The first signaling bearer is used to transmit the next radio interface control plane connection message (eg, an RRC Connection Establishment Complete message). The third signaling bearer is used to send another air interface control plane connection message and a non-access stratum message. In addition, if necessary, the processing priority of the second signaling bearer is higher than that of the first signaling bearer, and the processing priority of the first signaling bearer is higher than that of the third signaling bearer.

The first signaling bearer configuration information includes at least one of the following information:

the first signaling bearer identifier, the media access control layer configuration parameter used by the distributed unit to establish the first signaling bearer, the physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, the logical channel configuration parameter used by the distributed unit to establishing a first signaling bearer, and first information about establishing a signaling bearer user plane transmission path on the centralized unit side.

In a further implementation, the first signaling bearer configuration information may be carried in the aforementioned second message to be sent. More specifically, when sending the second message to the distributed unit, the centralized unit includes the first signaling bearer configuration information in the second message and sends the second message to the distributed unit.

In another additional implementation, the first signaling bearer configuration information may be sent via another control plane message. For example, before sending the second message or after sending the second message, the centralized unit sends a control plane message to the distributed unit, where the control plane message carries the first signaling bearer configuration information.

Accordingly, in the above process, the distributed unit may further send the first signaling bearer user plane transmission path establishment information on the distributed unit side to the centralized unit.

In a further implementation, the first signaling bearer user plane transmission path establishment information on the distributed block side may be carried in the aforementioned third message to be sent. More specifically, the distributed unit carries the first signaling bearer user plane transmission path establishment information on the distributed unit side into a third message, and sends the third message to the centralized unit.

In another further implementation, the first signaling bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message. For example, before sending the third message or after sending the third message, the distributed unit sends a control plane message to the centralized unit, where the control plane message carries the first signaling bearer user plane transmission path establishment information on the distributed unit side.

Accordingly, in the above process, the distributed unit may further configure a third signaling bearer.

Specifically, the distributed unit may send the user plane transmission path establishment information on the distributed unit side to the centralized unit via a control plane connection between the distributed unit and the centralized unit.

The distributed unit side user plane transmission path establishment information includes at least one of the following information: third distributed unit side signaling bearer user plane transmission path establishment information.

Accordingly, the distributed unit receives, via the control plane connection between the distributed unit and the centralized unit, the third signaling bearer configuration information sent by the centralized unit.

The third signaling bearer configuration information includes at least one of the following information: a media access control layer configuration parameter used by the distributed unit to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish a third signaling bearer a signaling channel, a logical channel configuration parameter used by the distributed unit to establish a third signaling bearer, and second signaling bearer user plane transmission path establishment information on the centralized unit side.

In a further implementation, the user plane transmission path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may be sent along with the user plane transmission path establishment information which is on the distributed block side and which corresponds to the first signaling bearer. . The specific sending method is given in the above embodiment.

In another further implementation, the user plane path establishment information that is on the distributed block side and which corresponds to the third signaling bearer may also be sent via another control plane message, for example, sent before or after the user plane path establishment information is sent, which is on the distributed block side and which corresponds to the first signaling bearer.

Accordingly, the third signaling bearer configuration information may be sent together with the first signaling bearer configuration information, or may be sent via another control plane message.

Accordingly, in the above process, the distributed unit may further configure a bearer.

Specifically, the centralized unit sends the configuration information of the bearer to the distributed unit. Accordingly, the distributed unit sends at least one of the following information to the centralized unit: the bearer ID and the bearer user plane transmission path establishment information on the side of the distributed unit.

The bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

In a further implementation, the data bearer configuration information may be sent along with the third signaling bearer configuration information.

In another additional implementation, the data bearer configuration information may also be sent via another control plane message.

In a further implementation, the data bearer user plane path establishment information on the distributed block side may be sent along with the data bearer user plane path establishment information on the distributed block side that corresponds to the third signaling bearer.

In another further implementation, the data bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message.

In the above embodiment, the user plane transmission path may be, in particular, a user plane tunnel. Accordingly, the user plane transmission path establishment information may be specifically user plane tunnel establishment information. The user plane tunnel establishment information includes one or a combination of the following information: tunnel ID, tunnel port number, tunnel IP address, and tunnel MAC address. For example, the user plane tunnel is established based on the GTP-U protocol. In order to establish a user plane tunnel between a distributed unit and a centralized unit, the centralized unit must notify the distributed unit of the tunnel identifier allocated for the tunnel on the side of the centralized unit. After obtaining the IP address (this address can be used for all user plane tunnels between the centralized unit and the distributed unit) of the centralized unit and the tunnel ID allocated by the centralized unit for the tunnel, the distributed unit can send the corresponding user plane message to the centralized unit through the tunnel. Similarly, when sending a user plane message to a distributed unit via a user plane tunnel, the centralized unit must obtain in advance the address of the distributed unit and the tunnel ID allocated by the distributed unit for the tunnel.

FIG. 8 is a schematic flowchart of Embodiment 5 of the method for managing a wireless connection according to the present application. In this process, the RRC connection message is transmitted through a dedicated user plane transmission path for the cell accessed by the terminal. As shown in Fig. 8, the process includes the following steps.

S800. Establish a control plane interface between the distributed unit and the centralized unit.

S801. The centralized block sends the fourth message to the distributed block.

In particular, the fourth message is a control plane message and the fourth message includes at least one of the following information:

a cell ID, second signaling bearer configuration information, and second signaling bearer user plane transmission path establishment information on the centralized unit side.

The second signaling bearer configuration information includes a second signaling bearer identifier. If necessary, the second signaling bearer configuration information may further include a corresponding physical layer configuration parameter, a media access control layer configuration parameter, or the like.

S802. The distributed block sends the fifth message to the centralized block.

In particular, the fifth message is also a control plane message, and the fifth message includes at least one of the following information:

a cell ID, a second signaling bearer ID, and second signaling bearer user plane transmission path establishment information on the distributed unit side.

After steps S801 and S802 are executed, a dedicated user plane transmission path is established for the cell in the allocated block.

In particular, the dedicated user plane transmission path may be a user plane tunnel. For example, the tunnel may be established based on the GTP-U protocol or established based on another similar protocol.

S803. The terminal receives the first terminal identifier.

If necessary, the terminal may obtain the first terminal identifier based on any of the various methods by which the base station system allocates the first terminal identifier in the above implementation cases, or the terminal may obtain the first terminal identifier in another manner. For example, in a handover scenario, a terminal obtains, in a source cell through an air interface control plane reconfiguration message (eg, an RRC connection reconfiguration message in LTE), the first terminal identifier allocated by the target base station to the terminal, and after handover to the new cell in the target base station, the terminal initiates an air interface control plane connection request via the first terminal identifier.

S804. The terminal sends an RRC connection request to the allocated block.

When it comes to a specific process, the aforementioned step S404 should be referred to. This document does not re-describe the details.

S805. The distributed block sends an RRC connection request (first message) to the centralized block.

Specifically, since the second signaling bearer user plane transmission path corresponding to the cell accessed by the terminal was established in steps S801 and S802, in this step, the distributed unit directly sends the first message to the centralized unit via the user plane transmission path corresponding to second signaling bearer user plane transmission path establishment information on the centralized unit side.

The distributed unit carries the cell ID and/or the second terminal ID in the first message when sending the first message to the centralized unit.

S806. The centralized unit sends an RRC connection establishment message (second message) to the distributed unit.

Specifically, the distributed unit receives, via the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the distributed unit side, the second message sent by the centralized unit.

The second message, which is sent by the centralized unit and received by the distributed unit, includes a cell ID and/or a third terminal ID.

S807. The distributed unit sends an RRC connection establishment message to the terminal.

S808. The terminal sends an RRC connection establishment completion message to the allocated block.

S809. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In addition, in the above process, the distributed unit may further configure the first signaling bearer. More specifically, the distributed unit may receive the first signaling bearer configuration information sent by the centralized unit.

In a further implementation, the first signaling bearer configuration information may be carried in the aforementioned fourth message to be sent. More specifically, when sending the fourth message to the distributed unit, the centralized unit carries the first signaling bearer configuration information in the fourth message and sends the fourth message to the distributed unit.

In another additional implementation, the first signaling bearer configuration information may be sent via another control plane message. For example, before sending the fourth message or after sending the fourth message, the centralized unit sends a control plane message to the distributed unit, where the control plane message carries the first signaling bearer configuration information.

Accordingly, in the above process, the distributed unit may further send the first signaling bearer user plane transmission path establishment information on the distributed unit side to the centralized unit.

In a further implementation, the first signaling bearer user plane transmission path establishment information on the distributed block side may be carried in the aforementioned fifth message to be sent. More specifically, the distributed unit carries the first signaling bearer user plane transmission path establishment information on the distributed unit side into a fifth message, and sends the fifth message to the centralized unit.

In another further implementation, the first signaling bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message. For example, before sending the fifth message or after sending the fifth message, the distributed unit sends a control plane message to the centralized unit, where the control plane message carries the first signaling bearer user plane transmission path establishment information on the distributed unit side.

If necessary in the above process, the distributed unit may further configure a third signaling bearer.

Specifically, the distributed unit may send the user plane transmission path establishment information on the distributed unit side to the centralized unit via a control plane connection between the distributed unit and the centralized unit.

The distributed unit side user plane transmission path establishment information includes at least one of a third signaling bearer identifier and third distributed unit side signaling bearer user plane transmission path establishment information.

Accordingly, the distributed unit receives, via the control plane connection between the distributed unit and the centralized unit, the third signaling bearer configuration information sent by the centralized unit.

The third signaling bearer configuration information includes at least one of the following information: a third signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the third signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the third signaling bearer, and third signaling bearer user plane transmission path establishment information on the centralized unit side.

In a further implementation, the user plane transmission path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may be sent along with the user plane transmission path establishment information which is on the distributed block side and which corresponds to the first signaling bearer. . The specific sending method is given in the above embodiment.

In another further implementation, the user plane path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may also be sent via another control plane message, for example, sent before or after the user plane path establishment information is sent, which is on the distributed block side and which corresponds to the first signaling bearer.

Accordingly, the third signaling bearer configuration information may be sent together with the first signaling bearer configuration information, or may be sent via another control plane message.

If necessary, in the above process, the distributed unit may further configure a data bearer.

Specifically, the centralized unit sends the configuration information of the bearer to the distributed unit. Accordingly, the distributed unit sends at least one of the following information to the centralized unit: the bearer ID and the bearer user plane transmission path establishment information on the side of the distributed unit.

The bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

In a further implementation, the data bearer configuration information may be sent along with the third signaling bearer configuration information.

In another additional implementation, the data bearer configuration information may also be sent via another control plane message.

In a further implementation, the data bearer user plane path establishment information on the distributed block side may be sent along with the data bearer user plane path establishment information on the distributed block side that corresponds to the third signaling bearer.

In another further implementation, the data bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message.

FIG. 9 is a schematic flowchart of Embodiment 6 of the method for managing a wireless connection according to the present application. In this process, the RRC connection message is transmitted through a dedicated user plane transmission path for the terminal. As shown in Fig.9, the process includes the following steps.

S900. Establish a control plane interface between the distributed unit and the centralized unit.

S901. The terminal receives the first terminal identifier.

If necessary, the terminal may obtain the first terminal identifier based on any of the various methods by which the base station system allocates the first terminal identifier in the above implementation cases, or the terminal may obtain the first terminal identifier in another manner. For example, in a handover scenario, a terminal obtains, in a source cell through an air interface control plane reconfiguration message (eg, an RRC connection reconfiguration message in LTE), the first terminal identifier allocated by the target base station to the terminal, and after handover to the new cell in the target base station, the terminal initiates an air interface control plane connection request via the first terminal identifier.

S902. The terminal sends an RRC connection request to the allocated block.

When it comes to a specific process, the aforementioned step S404 should be referred to. This document does not re-describe the details.

S903. The distributed block sends the sixth message to the centralized block.

The sixth message is a control plane message and is used to request the establishment, for the terminal, of the user plane transmission path that is between the distributed unit and the centralized unit and which is the second signaling bearer.

The sixth message includes at least one of the following information:

a first terminal ID corresponding to the terminal, a second terminal ID corresponding to the terminal, and a cell ID to which the terminal has access.

In a further implementation, the distributed unit may directly use the sixth message to indicate second signaling bearer user plane transmission path establishment information on the distributed unit side.

In another further implementation, the distributed block may carry second signaling bearer user plane transmission path establishment information in a sixth message.

In another further implementation, the distributed entity may also send second signaling bearer user plane transmission path establishment information via another control plane message.

S904. The centralized block sends the seventh message to the distributed block.

The seventh message is a control plane message.

The seventh message includes the third terminal identifier and the second signaling bearer user plane transmission path establishment information on the centralized unit side.

After steps S903 and S904 are completed, the second signaling bearer user plane transmission path for the terminal is established.

S905. The distributed unit sends an RRC connection request (first message) to the centralized unit.

Specifically, in the above step, the second signaling bearer user plane transmission path for the terminal has been established. Thus, in this step, the distributed unit directly sends the first message to the centralized unit via the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the centralized unit side.

S906. The centralized unit sends an RRC connection establishment message (second message) to the distributed unit.

The distributed unit receives the second message on the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the distributed unit side.

S907. The distributed unit sends an RRC connection establishment message to the terminal.

S908. The terminal sends an RRC connection establishment completion message to the allocated block.

S909. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

If necessary in the above process, the distributed unit may further configure the first signaling bearer. More specifically, the distributed unit may receive the first signaling bearer configuration information sent by the centralized unit.

The first signaling bearer configuration information includes at least one of the following information: a first signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish the first signaling bearer, a physical layer configuration parameter used the distributed unit to establish the first signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the first signaling bearer, and the first signaling bearer user plane transmission path establishment information on the centralized unit side.

In a further implementation, the first signaling bearer configuration information may be carried in the aforementioned sixth message to be sent. More specifically, when sending the sixth message to the distributed unit, the centralized unit transfers the first signaling bearer configuration information to the sixth message and sends the sixth message to the distributed unit.

In another additional implementation, the first signaling bearer configuration information may be sent via another control plane message. For example, before sending the sixth message or after sending the sixth message, the centralized unit sends a control plane message to the distributed unit, where the control plane message carries the first signaling bearer configuration information.

Accordingly, in the above process, the distributed unit may further send the user plane transmission path establishment information on the distributed unit side to the centralized unit.

The distributed unit side user plane transmission path establishment information includes at least one of the first signaling bearer identifier and the first distributed block side signaling bearer user plane transmission path establishment information.

In a further implementation, the first signaling bearer user plane transmission path establishment information on the distributed block side may be carried in the aforementioned seventh message to be sent. More specifically, the distributed unit carries the first signaling bearer user plane transmission path establishment information on the distributed unit side into a seventh message, and sends the seventh message to the centralized unit.

In another further implementation, the first signaling bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message. For example, before sending the seventh message or after sending the seventh message, the distributed unit sends a control plane message to the centralized unit, where the control plane message carries the first signaling bearer user plane transmission path establishment information on the distributed unit side.

If necessary in the above process, the distributed unit may further configure a third signaling bearer.

Specifically, the distributed unit may send the user plane transmission path establishment information on the distributed unit side to the centralized unit via a control plane connection between the distributed unit and the centralized unit.

The distributed unit side user plane transmission path establishment information includes at least one of a third signaling bearer identifier and third distributed unit side signaling bearer user plane transmission path establishment information.

Accordingly, the distributed unit receives, via the control plane connection between the distributed unit and the centralized unit, the third signaling bearer configuration information sent by the centralized unit.

The third signaling bearer configuration information includes at least one of the following information: a third signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the third signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the third signaling bearer, and third signaling bearer user plane transmission path establishment information on the centralized unit side.

In a further implementation, the user plane transmission path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may be sent along with the user plane transmission path establishment information which is on the distributed block side and which corresponds to the first signaling bearer. . The specific sending method is given in the above embodiment.

In another further implementation, the user plane path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may also be sent via another control plane message, for example, sent before or after the user plane path establishment information is sent, which is on the distributed block side and which corresponds to the first signaling bearer.

Accordingly, the third signaling bearer configuration information may be sent together with the first signaling bearer configuration information, or may be sent via another control plane message.

If necessary, in the above process, the distributed unit may further configure a data bearer.

Specifically, the centralized unit sends the configuration information of the bearer to the distributed unit. Accordingly, the distributed unit sends the data bearer user plane transmission path establishment information on the side of the distributed unit to the centralized unit.

The bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

In a further implementation, the data bearer configuration information may be sent along with the third signaling bearer configuration information.

In another additional implementation, the data bearer configuration information may also be sent via another control plane message.

In a further implementation, the data bearer user plane path establishment information on the distributed block side may be sent along with the data bearer user plane path establishment information on the distributed block side that corresponds to the third signaling bearer.

In another further implementation, the data bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message.

In the embodiments corresponding to FIGS. 7-9, the distributed unit cannot process the RRC layer message. Therefore, the distributed unit sends the first message to the centralized unit, and the centralized unit performs processing. However, in another optional implementation, the distributed unit may process the RRC layer message, and the distributed unit may send only the identifier corresponding to the terminal to the centralized unit and does not need to send the first message. Details are described below.

FIG. 10 is a schematic flowchart of Embodiment 7 of the method for managing a wireless connection according to the present application. In this process, the distributed unit may process the RRC layer message. As shown in Fig. 10, the process includes the following steps.

S1000. Establish a control plane interface between the distributed unit and the centralized unit.

S1001. The terminal receives the first terminal identifier.

If necessary, the terminal may obtain the first terminal identifier based on any of the various methods by which the base station system allocates the first terminal identifier in the above implementation cases, or the terminal may obtain the first terminal identifier in another manner. For example, in a handover scenario, a terminal obtains, in a source cell through an air interface control plane reconfiguration message (eg, an RRC connection reconfiguration message in LTE), the first terminal identifier allocated by the target base station to the terminal, and after handover to the new cell in the target base station, the terminal initiates an air interface control plane connection request via the first terminal identifier.

S1002. The terminal sends an RRC connection request to the allocated block.

S1003. Optionally, the allocated block uses the MAC message to indicate the terminal's contention resolution.

S1004. The distributed unit sends an RRC connection establishment message to the terminal.

S1005. The distributed block sends the ninth message to the centralized block.

The ninth message includes a connection parameter used to establish an air interface control plane connection.

Optionally, the connection parameter used to establish a radio interface control plane connection includes at least one of the following information: a fourth terminal identifier corresponding to the terminal and a reason for establishing a terminal control plane connection, where the fourth terminal identifier is a terminal identifier allocated by the base network, or the fourth terminal ID is a random number.

S1006. The terminal sends an RRC connection establishment completion message to the allocated block.

S1007. The distributed unit sends an RRC connection establishment completion message to the centralized unit.

In addition, in the above process, the distributed unit may further configure the first signaling bearer. More specifically, the distributed unit may receive the first signaling bearer configuration information sent by the centralized unit.

In a further implementation, the first signaling bearer configuration information may be carried in the aforementioned ninth message to be sent. More specifically, when sending the ninth message to the distributed unit, the centralized unit transfers the first signaling bearer configuration information to the ninth message and sends the ninth message to the distributed unit.

In another additional implementation, the first signaling bearer configuration information may be sent via another control plane message. For example, before sending the ninth message or after sending the ninth message, the centralized unit sends a control plane message to the distributed unit, where the control plane message carries the first signaling bearer configuration information.

Accordingly, in the above process, the distributed unit may further send the first signaling bearer user plane transmission path establishment information on the distributed unit side to the centralized unit.

The first signaling bearer user plane transmission path establishment information on the distributed unit side may be sent via a control plane message. For example, before sending the ninth message or after sending the ninth message, the distributed unit sends a control plane message to the centralized unit, where the control plane message carries the first signaling bearer user plane transmission path establishment information on the distributed unit side.

If necessary in the above process, the distributed unit may further configure a third signaling bearer.

Specifically, the distributed unit may send the user plane transmission path establishment information on the distributed unit side to the centralized unit via a control plane connection between the distributed unit and the centralized unit.

The distributed unit side user plane transmission path establishment information includes at least one of a third signaling bearer identifier and third distributed unit side signaling bearer user plane transmission path establishment information.

Accordingly, the distributed unit receives, via the control plane connection between the distributed unit and the centralized unit, the third signaling bearer configuration information sent by the centralized unit.

The third signaling bearer configuration information includes at least one of the following information: a third signaling bearer identifier, a media access control layer configuration parameter used by the distributed entity to establish a third signaling bearer, a physical layer configuration parameter used by the distributed unit to establish the third signaling bearer, a logical channel configuration parameter used by the distributed unit to establish the third signaling bearer, and third signaling bearer user plane transmission path establishment information on the centralized unit side.

In a further implementation, the user plane transmission path establishment information which is on the distributed block side and which corresponds to the third signaling bearer may be sent along with the user plane transmission path establishment information which is on the distributed block side and which corresponds to the first signaling bearer. . The specific sending method is given in the above embodiment.

In another further implementation, the user plane path establishment information that is on the distributed block side and which corresponds to the third signaling bearer may also be sent via another control plane message, for example, sent before or after the user plane path establishment information is sent, which is on the distributed block side and which corresponds to the first signaling bearer.

Accordingly, the third signaling bearer configuration information may be sent together with the first signaling bearer configuration information, or may be sent via another control plane message.

If necessary, in the above process, the distributed unit may further configure a data bearer.

Specifically, the centralized unit sends the configuration information of the bearer to the distributed unit. Accordingly, the distributed unit sends the data bearer user plane transmission path establishment information on the side of the distributed unit to the centralized unit.

The bearer configuration information includes at least one of the following information: a bearer identifier, a media access control layer configuration parameter used by the distributed unit to establish a bearer, a physical layer configuration parameter used by the distributed unit to establishing a data bearer, a logical channel configuration parameter used by the distributed unit to establish a data bearer, service information used by the distributed unit to process the data bearer, and information about establishing a data bearer user plane transmission path on the side of the centralized unit.

In a further implementation, the data bearer configuration information may be sent along with the third signaling bearer configuration information.

In another additional implementation, the data bearer configuration information may also be sent via another control plane message.

In a further implementation, the data bearer user plane path establishment information on the distributed block side may be sent along with the data bearer user plane path establishment information on the distributed block side that corresponds to the third signaling bearer.

In another further implementation, the data bearer user plane transmission path establishment information on the distributed unit side may also be sent via another control plane message.

Figure 11 shows a modular block diagram of an embodiment of a distributed unit according to the present application. As shown in FIG. 11, the distributed unit includes a receiving module 1101, a processing module 1102, and a sending module 1103.

The receiving module 1101 is configured to receive a first message sent by the terminal, where the first message is used to request the establishment of an air interface control plane connection for the terminal.

The processing module 1102 is configured to process the first message.

The sending module 1103 is configured to send the first message to the centralized unit.

The receiving module 1101 is further configured to receive a second message sent by the centralized unit, where the second message is used to instruct to establish an air interface control plane connection between the terminal and the distributed unit.

The distributed unit is configured to implement the above method embodiments. The implementation principles and technical effects are similar, and their details will not be re-described in this document.

In addition, the processing module is further configured to establish a control plane connection between the distributed unit and the centralized unit.

Accordingly, the sending module 1103 is specifically configured to:

sending a third message to the centralized unit via a control plane connection, where the third message includes the first message, and the third message further includes at least one of the following information:

the first terminal identifier corresponding to the terminal, the identifier of the cell accessed by the terminal, and the second terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface, and the second terminal identifier is an identifier allocated by the allocated block for the terminal over the plane interface control between the distributed unit and the centralized unit.

In addition, the second message is sent over the control plane connection; the second message includes a third terminal identifier; and the third terminal ID is an ID assigned by the centralized unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

In addition, the receiving unit 1101 is further configured to receive the first signaling bearer configuration information sent by the centralized unit.

In addition, the first signaling bearer configuration information includes at least one of the following information:

the first signaling bearer identifier, the media access control layer configuration parameter used by the distributed unit to establish the first signaling bearer, the physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, the logical channel configuration parameter used by the distributed unit to establishing a first signaling bearer, and first information about establishing a signaling bearer user plane transmission path on the centralized unit side.

In addition, the receiving module 1101 is specifically configured to:

receiving, via the second message, the first signaling bearer configuration information sent by the centralized unit.

In addition, the sending module 1103 is further configured to:

sending the first signaling bearer user plane transmission path establishment information on the side of the distributed unit to the centralized unit.

In addition, the sending module 1103 is specifically configured to:

including the first signaling bearer user plane transmission path establishment information on the side of the distributed unit in a third message, and sending the third message to the centralized unit.

In addition, the receiving module 1101 is further configured to:

receiving a fourth message sent by the centralized unit, where the fourth message includes at least one of the following information: cell ID, second signaling bearer configuration information, and second signaling bearer user plane transmission path establishment information on the centralized unit side.

Send module 1103 is further configured to:

sending the fifth message to the centralized unit, where the fifth message includes at least one of the following information: a cell ID, a second signaling bearer ID, and a second signaling bearer user plane transmission path establishment information on the distributed unit side.

In addition, the sending module 1103 is specifically configured to:

sending the first message to the centralized unit via the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the centralized unit side.

The sending module 1103 transfers the cell ID and/or the second terminal ID to the first message when sending the first message to the centralized unit.

In addition, the receiving module 1101 is specifically configured to:

receiving, via the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the side of the distributed unit, of the second message sent by the centralized unit.

The receiving unit 1101 receives the cell ID and/or the third terminal ID that are included in the second message sent by the centralized unit.

12 shows a modular block diagram of an embodiment of another distributed unit according to the present application. As shown in FIG. 11, the distributed unit includes a receiving module 1201, a processing module 1202, and a sending module 1203.

The receiving module 1201 is configured to receive a first message sent by the terminal, where the first message is used to request the establishment of an air interface control plane connection for the terminal.

The processing module 1202 is configured to send an eighth message to the terminal based on the first message, where the eighth message is used to instruct to establish an air interface control plane connection for the terminal.

The sending module 1203 is configured to send a ninth message to the centralized unit, where the ninth message includes a connection parameter used to establish an air interface control plane connection.

The distributed unit is configured to implement the above embodiments of the method. The implementation principles and technical effects are similar, and their details are not repeated in this document.

In addition, the connection parameter used to establish a control plane connection of the air interface includes at least one of the following information: a fourth terminal identifier corresponding to the terminal and a reason for establishing a control plane connection of the terminal, where the fourth terminal identifier is a terminal identifier allocated core network, or the fourth terminal ID is a random number.

13 shows a modular block diagram of an embodiment of another distributed unit according to the present application. As shown in FIG. 13, the distributed unit includes a receiving unit 1301, a processing unit 1302, and a sending unit 1303. As shown in FIG.

The receiving module 1301 is configured to receive an access request message sent by the terminal.

The processing unit 1302 is configured to obtain, based on the access request message, a first terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface.

The send module 1303 is configured to send the first terminal identifier to the terminal.

The sending module 1303 is further configured to send the first terminal ID and/or cell ID to the centralized unit.

In addition, the first terminal ID is allocated with a distributed block.

In addition, the sending module 1303 is further configured to:

sending a first request message to the centralized unit, where the first request message is used to request the centralized unit to allocate a set of terminal identifiers.

The receiving module 1301 is further configured to:

receiving the terminal ID set sent by the centralized unit, where the terminal ID set includes the first terminal ID.

14 shows a modular block diagram of an embodiment of yet another distributed unit according to the present application. As shown in FIG. 14, the distributed unit includes a receiving module 1401, a processing module 1402, and a sending module 1403.

The receiving module 1401 is configured to receive an access request message sent by the terminal.

The processing unit 1402 is configured to send a second request message to the centralized unit based on the access request message, where the second request message is used to request the centralized unit to allocate a first terminal identifier for the terminal.

The receiving unit 1401 is further configured to receive the first terminal ID sent by the centralized unit.

The sending module 1403 is configured to send the first terminal identifier to the terminal.

In addition, the second request message includes a cell ID corresponding to the cell being accessed by the terminal.

In addition, the first terminal identifier is a unique identifier of the wireless network.

15 shows a modular block diagram of an embodiment of a centralized unit according to the present application. As shown in FIG. 15, the centralized unit includes a receiving module 1501, a processing module 1502, and a sending module 1503.

The receiving module 1501 is configured to receive a first message sent by the distributed unit, where the first message is used to request the establishment of an air interface control plane connection for the terminal.

The processing module 1502 is configured to generate a second message based on the first message.

The sending module 1503 is configured to send a second message to the distributed unit, where the second message is used to instruct to establish an air interface control plane connection between the terminal and the distributed unit.

In addition, the first message is included in the third message for transmission, and the third message is transmitted through the control plane connection between the distributed unit and the centralized unit; and the third message further includes at least one of the following information:

the first terminal identifier corresponding to the terminal, the identifier of the cell accessed by the terminal, and the second terminal identifier corresponding to the terminal, where the first terminal identifier is used to identify the terminal over the air interface, and the second terminal identifier is an identifier allocated by the allocated block for the terminal over the plane interface control between the distributed unit and the centralized unit.

In addition, the second message is sent over the control plane connection; accordingly, the second message includes a third terminal identifier; and the third terminal ID is an ID allocated by the centralized unit to the terminal over the control plane interface between the distributed unit and the centralized unit.

In addition, the sending module 1503 is further configured to:

sending the first signaling bearer configuration information to the distributed unit.

In addition, the first signaling bearer configuration information includes at least one of the following information:

the first signaling bearer identifier, the media access control layer configuration parameter used by the distributed unit to establish the first signaling bearer, the physical layer configuration parameter used by the distributed unit to establish the first signaling bearer, the logical channel configuration parameter used by the distributed unit to establishing a first signaling bearer, and first information about establishing a signaling bearer user plane transmission path on the centralized unit side.

In addition, the sending module 1503 sends the first signaling bearer configuration information via the second message.

In addition, the receiving unit 1501 is further configured to receive the first signaling bearer user plane transmission path establishment information which is on the distributed block side and which is sent by the distributed block.

In addition, the receiving module 1501 is specifically configured to:

receiving first signaling bearer user plane transmission path establishment information on the distributed unit side via a third message.

In addition, the sending module 1503 is further configured to:

sending a fourth message to the distributed unit, where the fourth message includes at least one of the following information: cell ID, second signaling bearer configuration information, and second signaling bearer user plane transmission path establishment information on the centralized unit side.

The receiving module 1501 is further configured to:

receiving a fifth message sent by the distributed unit, where the fifth message includes at least one of the following information: a cell ID, a second signaling bearer identifier, and second signaling bearer user plane transmission path establishment information on the distributed unit side.

In addition, the receiving module 1501 is specifically configured to:

receiving the first message on the user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the centralized unit side.

In addition, the sending module 1503 is specifically configured to:

sending a second message to the distributed unit via a user plane transmission path corresponding to the second signaling bearer user plane transmission path establishment information on the distributed unit side.

16 shows a modular block diagram of an embodiment according to the present application. As shown in FIG. 16, the centralized unit includes a receiving unit 1601 and a processing unit 1602.

The receiving module 1601 is configured to receive a ninth message sent by the distributed unit, where the ninth message includes a connection parameter used to establish an air interface control plane connection.

The processing module 1602 is configured to process the connection control based on the connection parameter used to establish the radio interface control plane connection.

In addition, the connection parameter used to establish a control plane connection of the air interface includes at least one of the following information: a fourth terminal identifier corresponding to the terminal and a reason for establishing a control plane connection of the terminal, where the fourth terminal identifier is a terminal identifier allocated core network, or the fourth terminal ID is a random number.

17 shows a modular block diagram of an embodiment according to the present application. As shown in FIG. 17, the centralized unit includes a receiving module 1701 and a processing module 1702.

The receiving module 1701 is configured to receive a first terminal ID and/or cell ID that are sent in a distributed block, where the first terminal ID is used to identify the terminal over the air interface.

The processing module 1702 is configured to process the connection control based on the first terminal ID.

In addition, the first terminal ID is allocated with a distributed block.

In addition, the receiving module 1701 is further configured to:

receiving a first request message sent by the distributed unit, where the first request message is used to request the centralized unit to allocate a set of terminal identifiers.

The processing module 1702 is further configured to:

allocating a set of terminal identifiers.

The centralized unit additionally includes:

a sending module 1703, configured to send the terminal ID set to an allocated block, where the terminal ID set includes a first terminal ID.

18 shows a modular block diagram of an embodiment according to the present application. As shown in FIG. 18, the centralized unit includes a receiving module 1801, a processing module 1802, and a sending module 1803.

The receiving unit 1801 is configured to receive a second request message sent by the distributed unit, where the second request message is used to request the centralized unit to allocate a first terminal identifier for the terminal.

The processing module 1802 is configured to allocate a first terminal identifier for the terminal.

The sending module 1803 is configured to send the first terminal identifier to the allocated block.

In addition, the second request message includes a cell ID corresponding to the cell being accessed by the terminal.

In addition, the first terminal identifier is a unique identifier of the wireless network.

19 is a block diagram of an object of an embodiment of a distributed block according to the present application. As shown in Fig. 19, the distributed unit includes:

memory 1901 and processor 1902.

The memory 1901 is configured to store the program instruction, and the processor 1902 is configured to call the program instruction from the memory 1901 to perform the distributed block function in the above embodiments 4, 5, and 6 of the method.

FIG. 20 is a block diagram of an object of an embodiment of another distributed block according to the present application. As shown in FIG. 20, the distributed unit includes:

2001 memory and 2002 processor.

The memory 2001 is configured to store a program instruction, and the processor 2002 is configured to call the program instruction from the memory 2001 to perform a distributed block function in the above embodiment 7 of the method.

FIG. 21 is a block diagram of an object of an embodiment of yet another distributed unit according to the present application. As shown in Fig. 21, the distributed unit includes:

memory 2101 and processor 2102.

The memory 2101 is configured to store the program instruction, and the processor 2102 is configured to call the program instruction from the memory 2101 to perform the distributed block function in the above embodiments 1 and 2 of the method.

FIG. 22 is a block diagram of an object of an embodiment of yet another distributed unit according to the present application. As shown in Fig. 22, the distributed unit includes:

memory 2201 and processor 2202.

The memory 2201 is configured to store the program instruction, and the processor 2202 is configured to call the program instruction from the memory 2201 to perform the distributed block function in the above embodiment 3 of the method.

FIG. 23 is a block diagram of an object of an embodiment of a centralized unit according to the present application. As shown in Fig.23, the centralized unit includes:

memory 2301 and processor 2302.

The memory 2301 is configured to store the program instruction, and the processor 2302 is configured to call the program instruction from the memory 2301 to perform the function of the centralized unit in the above embodiments 4, 5, and 6 of the method.

Fig. 24 is a block diagram of an object of an embodiment according to the present application. As shown in Fig.24, the centralized unit includes:

memory 2401 and processor 2402.

The memory 2401 is configured to store the program instruction, and the processor 2402 is configured to call the program instruction from the memory 2401 to perform the function of the centralized unit in the above embodiment 7 of the method.

Fig. 25 is a block diagram of an object of an embodiment according to the present application. As shown in Fig.25, the centralized unit includes:

memory 2501 and processor 2502.

The memory 2501 is configured to store the program instruction, and the processor 2502 is configured to call the program instruction from the memory 2501 to perform the function of the centralized unit in the above embodiments 1 and 2 of the method.

Fig. 26 is a block diagram of an object of an embodiment according to the present application. As shown in Fig.26, the centralized unit includes:

memory 2601 and processor 2602.

The memory 2601 is configured to store the program instruction, and the processor 2602 is configured to call the program instruction from the memory 2601 to perform the function of the centralized unit in the above embodiment 3 of the method.

All or some of the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the instructions of the computer program are downloaded and executed on the computer, the procedure or functions according to the embodiments of the present invention are generated in whole or in part. The computer may be a general purpose computer, a specialized computer, a computer network, or other programmable device. The computer instructions may be stored on a computer-readable medium or may be transferred from one computer-readable medium to another computer-readable medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (for example, via infrared, radio or microwave signals) method. A computer-readable medium can be any usable medium accessible to a computer, or a data storage device such as a server or data center that combines one or more usable media. The medium used may be a magnetic medium (eg floppy disk, hard disk or magnetic tape), an optical medium (eg DVD), a semiconductor medium (eg solid state disk (Solid State Disk, SSD)) or the like.

Those skilled in the art will appreciate that embodiments of the present application may be provided as a method, system, or computer program product. Therefore, the present application may take the form of hardware-only embodiments, software-only embodiments, or combination of software and hardware embodiments. In addition, the present application may use a form of computer program product that is embodied in one or more computer storage media (including, but not limited to, disk memory, CD-ROM, optical memory, and the like) that includes computer program the code.

The present application has been described with reference to flowcharts and/or flowcharts of a method, apparatus (system), and computer program product according to embodiments of the present application. It should be understood that computer program instructions may be used to implement each process and/or each step in the flowcharts and/or block in the flowcharts and the combination of the process and/or step in the flowcharts and/or block on block diagrams. These computer program instructions may be intended for a general purpose computer, a specialized computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, so that instructions executed by a computer or processor of another programmable data processing device generate a device to implement a particular function in one or more processes in flowcharts and/or in one or more blocks in flowcharts.

These computer program instructions may be stored in computer readable memory, which may instruct the computer or other programmable processing device to operate in a certain way, such that the instructions stored in computer readable memory produce an artifact that includes the command device. The command device implements a specific function in one or more processes in flowcharts and/or in one or more blocks in flowcharts.

These computer program instructions may be downloaded to a computer or other programmable processing device such that a series of operations and steps are performed on the computer or other programmable device, thereby generating computer-implemented processing. Thus, instructions executable on a computer or other programmable device provide steps for implementing a particular function in one or more processes in flowcharts and/or in one or more blocks in flowcharts.

Although some preferred embodiments of the present application have been described above, changes and modifications to these embodiments may be made by those skilled in the art once they have learned the basic concept of the invention. Thus, the following claims are intended to be construed as covering the preferred embodiments and all changes and modifications falling within the scope of this application.

It is obvious that specialists in the art can make various modifications and changes in this application without departing from the essence and scope of this application. The present application is intended to cover these modifications and variations of the present application provided that they fall within the scope defined by the claims of the present application and their equivalent technologies.

Claims (44)

1. A method for managing a wireless connection, comprising: receiving, by the distributed unit, a radio resource control (RRC) connection request sent by the terminal; the distributed unit sending a control plane message containing an RRC connection request to the centralized unit via a control plane connection between the distributed unit and the centralized unit, the control plane message containing the RRC connection request further comprising a first terminal identifier, a cell identifier, to accessed by the terminal, and a second terminal identifier, the first terminal identifier identifies the terminal over the air interface, and the second terminal identifier is an identifier allocated by the allocated block to the terminal over the control plane interface; receiving, by the distributed unit via the control plane connection, a control plane message which is sent by the centralized unit and which contains an RRC connection establishment message; sending by the distributed unit an RRC connection establishment message to the terminal; receiving by the distributed unit an RRC connection establishment completion message sent by the terminal; and sending by the distributed unit an RRC connection establishment completion message sent to the centralized unit. 2. The method of claim 1, wherein the control plane message containing the RRC connection establishment message further comprises a third terminal identifier, and the third terminal identifier is an identifier assigned by the centralized unit to the terminal over the control plane connection between the distributed unit and the centralized unit . 3. The method of claim 1, wherein the method further comprises: Establishment by a distributed unit of a control plane connection. 4. The method of claim 1, wherein the method further comprises: receiving, by the distributed module, a random access request from the terminal; sending, by the distributed module, a random access response to the terminal, the random access response containing the first terminal identifier. 5. The method of claim 1, wherein the first terminal identifier is allocated in a distributed block. 6. The method of claim 1, wherein the first terminal identifier is a Radio Network Cell Temporary Identifier (C-RNTI). 7. The method according to p. 1, in which the distributed unit and the centralized unit are in the base station; the distributed unit is configured to use a radio link control (RLC) layer function of the base station, a media access control (MAC) layer function of the base station, and a physical layer function of the base station; and the centralized unit is configured to use the RRC layer function of the base station and the Packet Data Convergence Protocol (PDCP) layer function of the base station. 8. A method for managing a wireless connection, comprising: receiving, by the centralized unit via a control plane connection between the distributed unit and the centralized unit, a control plane message which contains a request for a radio resource control (RRC) connection and which is sent by the distributed unit, wherein the control plane message containing a request for an RRC connection further comprises a first a terminal ID, an ID of a cell accessed by the terminal, and a second terminal ID, the first terminal ID identifies the terminal over the air interface, and the second terminal ID is an ID allocated by a allocated block to the terminal over a control plane connection; sending, by the centralized unit, a control plane message containing an RRC connection establishment message to the distributed unit via the control plane interface; and receiving, by the centralized unit, an RRC connection establishment completion message sent by the distributed unit. 9. The method of claim 6, wherein the control plane message containing the RRC connection establishment message further comprises a third terminal identifier, and the third terminal identifier is an identifier assigned by the centralized unit to the terminal over the control plane connection. 10. The method of claim 8, wherein the first terminal identifier is a radio network cell temporary identifier (C-RNTI). 11. The method according to p. 8, in which the distributed unit and the centralized unit are in the base station; the distributed unit is configured to use a radio link control (RLC) layer function of the base station, a media access control (MAC) layer function of the base station, and a physical layer function of the base station; and the centralized unit is configured to use the RRC layer function of the base station and the Packet Data Convergence Protocol (PDCP) layer function of the base station. 12. A communication device comprising a memory and a processor, in which the memory is configured to store a program instruction, and when the program instruction is called by the processor, the communication device is configured to implement the method according to any one of paragraphs. 1-7. 13. A communication device comprising a memory and a processor, in which the memory is configured to store a program instruction, and when the program instruction is called by the processor, the communication device is configured to perform the method according to any one of paragraphs. 8-11. 14. A computer-readable storage medium, in which the computer-readable storage medium contains a program instruction, and when the program instruction is executed, the method according to any one of paragraphs is performed. 1-7. 15. A computer-readable storage medium, on which the computer-readable storage medium contains a program instruction, and when the program instruction is executed, the method according to any one of paragraphs is performed. 8-11. 16. The base station system, comprising: a distributed unit configured to perform the method according to any one of paragraphs. 1-7; and centralized unit, configured to perform the method according to any one of paragraphs. 8-11. 17. Distribution block containing: a receiving module, configured to receive a radio resource control (RRC) connection request sent by the terminal; and a sending module configured to send a control plane message containing an RRC connection request to the centralized unit via a control plane connection between the distributed unit and the centralized unit, wherein the control plane message containing the RRC connection request further comprises a first terminal identifier, a cell identifier accessed by the terminal and a second terminal identifier, the first terminal identifier identifies the terminal over the air interface, and the second terminal identifier is an identifier assigned by a allocated block to the terminal over the control plane interface, in which the receiving module is further configured to receive, via the control plane connection, a control plane message that is sent by the centralized unit and that contains an RRC connection establishment message; the sending module is further configured to send an RRC connection establishment message to the terminal; the receiving module is further configured to receive an RRC connection establishment completion message sent by the terminal; and the sending module is further configured to send an RRC connection establishment completion message sent to the centralized unit. 18. Centralized unit containing: a receiving module configured to receive, over a control plane connection between the distributed unit and the centralized unit, a control plane message that contains a request for a radio resource control (RRC) connection and is sent by the distributed unit, wherein the control plane message containing the request for an RRC connection is further contains a first terminal identifier, an identifier of a cell accessed by the terminal, and a second terminal identifier, the first terminal identifier identifies the terminal over the air interface, and the second terminal identifier is an identifier allocated by a distributed block to the terminal over a control plane connection; and a sending module, configured to send a control plane message containing an RRC connection establishment message to a distributed unit via a control plane interface, in which the receiving module is further configured to receive the RRC connection establishment completion message sent by the distributed unit.

Images