WO2018054336A1

WO2018054336A1 - Method and device for transmitting message

Info

Publication number: WO2018054336A1
Application number: PCT/CN2017/102777
Authority: WO
Inventors: 贾晓倩; 罗海燕
Original assignee: 华为技术有限公司
Priority date: 2016-09-23
Filing date: 2017-09-21
Publication date: 2018-03-29

Abstract

Provided in the embodiments of the present application are a method and a device for transmitting a message. The method comprises: a distributed unit (DU) receiving a radio resource control (RRC) message and instruction information transmitted by a central unit (CU), the DU transmitting the RRC message according to the instruction information. The method and the device for transmitting an RRC message provided in the embodiments of the present application can enable a CU to correctly transmit RRC signaling to a DU.

Description

Message sending method and device

This application is required to be submitted to the China Patent Office on September 23, 2016, the application number is 201610849000.8, and the application name is “Send Method and Device for Radio Resource Control RRC Message”, and submitted to the Chinese Patent Office on March 24, 2017, and apply. The priority of the Chinese Patent Application No. 201710182054.8, entitled "Sending Method and Apparatus for Sending Messages", the entire contents of which is incorporated herein by reference.

Technical field

The embodiments of the present invention relate to computer technologies, and in particular, to a method and an apparatus for sending a message.

Background technique

The cloud radio access network (CRAN) has a built-in baseband processing unit (BBU) to reduce the gain of the shared BBU resource pool, and can better support between different operators. The residential access network (Resident Access Network; RAN) shares and saves power. Therefore, CRAN has been deeply studied in the 5th Generation mobile communication technology (5G).

The CRAN includes a central unit (Central unit; CU for short) and a distributed unit (DU), wherein one CU can be connected to one or more DUs at the same time. FIG. 1 is a schematic diagram of partitioning of CU-DUs at each protocol layer. As shown in FIG. 1 , the current 3rd Generation Partnership Project (3GPP) standard proposes different ones as shown in FIG. 1 in the CRAN architecture. The CU-DU function partitioning scheme, in which the

options

1, 2, 4, 6, and 8 respectively set the CU and the DU in the radio resource control (Radio Resource Control; RRC) layer, packet data on the basis of the current protocol stack. a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical Layer (Physical Layer; The abbreviation: PHY) layer is divided. The switching schemes of

Option

3, 5, and 7 respectively divide the functions of the RLC part and the RLC layer or the functions of the MAC part and the MAC layer or more, or the functions of the PHY layer part and the PHY layer or more into the CU.

In each of the above division methods, the function of the RRC layer is located in the CU. How to send RRC messages has become a technical problem that needs to be solved.

Summary of the invention

An embodiment of the present application provides a method and an apparatus for sending a message, which can be used to send an RRC message. In addition, the scheme of the present application can also be applied to messages of other layers.

In a first aspect, the embodiment of the present application provides a method for sending a message, including:

The distributed node (DU) receives the first message and the indication information from the centralized node (CU);

The DU sends the first message based on the indication information.

Optionally, the indication information includes a first message type of the first message, the first message type is a main information block message, or a system information block type one message, or a paging message, or a minimum system information message, or a system An information message, or other system information message, the first message type being associated with the first scheduling information; The DU sends the first message based on the indication information: the DU sends the first message based on the first message type and the first scheduling information. Optionally, the first scheduling information may be sent by the CU to the DU, or may be specified by a communication standard.

Optionally, the indication information includes first scheduling information of the first message and a first message type of the first message, where the first message type is a system information message or other system information message; and the DU is sent according to the indication information. The first message is: the DU sends the first message based on the first message type and the first scheduling information; the method further includes: the DU receiving the second message and the second message type of the second message from the CU The second message type is a system information block type one message or a minimum system information message, the second message includes the first scheduling information, and the second message is based on the second message type and the second scheduling information associated with the second message type. Send the second message.

Optionally, the method further includes: the DU receiving a first request message from one or more terminals, where the first request message includes the first message type; the DU sends a second request message to the CU, the second request The message includes the first message type.

Optionally, the number of the first request message meets a threshold condition.

Optionally, the method further includes: the DU receiving the threshold condition from the CU.

Optionally, the indication information further includes: a cell identifier, or a network standard, where the DU sends the first message based on the first message type and the first scheduling information: the DU is based on the first message type and the first The scheduling information is sent by the first message in the cell corresponding to the cell identifier; or the DU sends the first message by using the wireless technology corresponding to the network standard based on the first message type and the first scheduling information.

Optionally, the first scheduling information includes: validity information, or a scheduling period, or a scheduling window.

Optionally, the indication information includes a first message type of the first message and a terminal identifier, where the first message type is a signaling radio bearer type message, or a signaling radio bearer message, or a system information message, or other The system information message is sent by the DU based on the indication information: the DU sends the first message based on the first message type and the terminal identifier.

Optionally, the method further includes: the DU sending a tunnel establishment request message to the CU, where the setup request message includes a first message type and a terminal identifier of the first message; the indication information includes an identifier of the tunnel; the DU Sending the first message based on the indication information is: the DU sends the first message based on the first message type and the terminal identifier.

Optionally, the method further includes: the DU sending a tunnel establishment request message to the CU, where the setup request message includes a terminal identifier; the indication information includes an identifier of the tunnel and a first message type of the first message; Sending the first message based on the indication information is: the DU sends the first message based on the first message type and the terminal identifier.

Optionally, the indication information further includes: a cell identifier, or a network standard; the DU sends the first message based on the first message type and the terminal identifier, where the DU is based on the first message type and the terminal identifier The first message is sent in the cell corresponding to the cell identifier; or the first message is sent by the DU based on the first message type and the terminal identifier by using a wireless technology corresponding to the network standard.

In a second aspect, the embodiment of the present application further provides a method for sending a message, including: a centralized node CU acquiring indication information associated with a first message, where the indication information is used to send the first message; and the CU is to a distributed node The DU sends the first message and the indication information.

Optionally, the indication information includes a first message type of the first message, the first message type is a main information block message, or a system information block type one message, or a paging message, or a minimum system information message, or a system An information message, or other system information message, the first message type being associated with the first scheduling information of the first message.

Optionally, the method further includes: the CU sending the first scheduling information to the DU.

Optionally, the indication information includes first scheduling information of the first message and a first message type of the first message, where the first message type is a system information message or other system information message; the method further includes: the CU Sending a second message and a second message type of the second message to the DU, the second message type is a system information block type one message or a minimum system information message, and the second message includes the first scheduling information.

Optionally, the method further includes: the CU receiving a second request message from the DU, where the second request message includes the first message type.

Optionally, the method further includes: the CU sending a threshold condition associated with the second request message to the DU.

Optionally, the first scheduling information includes: validity information, or scheduling information, or a scheduling window.

Optionally, the indication information includes a first message type of the first message and a terminal identifier, where the first message type is a signaling radio bearer type message, or a signaling radio bearer message, or a system information message, or other System information message.

Optionally, the method further includes: the CU receiving a tunnel establishment request message from the DU, where the setup request message includes a first message type and a terminal identifier of the first message, where the indication information includes an identifier of the tunnel.

Optionally, the method further includes: the CU receiving a tunnel establishment request message from the DU, where the setup request message includes a terminal identifier, where the indication information includes an identifier of the tunnel and a first message type of the first message.

Optionally, the indication information further includes: a cell identifier, or a network standard.

In a third aspect, an embodiment of the present application further provides a node. The node is for implementing a method of transmitting a message such as the first aspect. Optionally, the node can be a DU.

As an alternative design, the node includes a processor, a transceiver, and communication circuitry. The processor is configured to receive the first message and the indication information from the centralized node CU through the communication circuit, and send the first message based on the indication information.

As another alternative design, the node includes a processor and a memory. The memory is for storing a program implementing the method of the first aspect, the processor being operative to run the above program to implement the method of the first aspect.

The method of how the node implements the first aspect can refer to the content of the first aspect.

In a fourth aspect, the embodiment of the present application further provides another node. The node is for implementing a method of transmitting a message, for example, of the second aspect. Optionally, the node can be a CU.

As an alternative design, the node includes a processor and communication circuitry. The processor is configured to obtain indication information associated with the first message, where the indication information is used to send the first message; and the processor sends the first message and the indication information to the distributed node DU through the communication circuit.

As another alternative design, the node includes a processor and a memory. The memory is for storing a program implementing the method of the second aspect, the processor being operative to run the above program to implement the method of the second aspect.

The method of how the node implements the second aspect can refer to the content of the second aspect.

In a fifth aspect, the embodiment of the present application further provides a communication system, including the node of the third aspect and the node of the fourth aspect.

In a sixth aspect, the embodiment of the present application further provides a computer program product, where the program product includes a program for implementing the method of the first aspect.

In a seventh aspect, the embodiment of the present application further provides a computer readable storage medium, where the medium stores the program of the sixth aspect.

In an eighth aspect, the embodiment of the present application further provides a computer program product, where the program product includes a program for implementing the method of the second aspect.

In a ninth aspect, the embodiment of the present application further provides a computer readable storage medium, where the medium stores the program of the eighth aspect.

The following is a description of other embodiments provided by the present application.

In a first aspect, the embodiment of the present application provides a method for sending a radio resource control RRC message, including:

The distributed node DU receives the radio resource control RRC message and the indication information sent by the centralized node CU;

The DU sends the RRC message according to the indication information.

In the method for transmitting a RRC message, the RRC message is sent by the CU, and the RRC message is sent according to the indication information. After receiving the RRC message and the indication information, the DU may send an RRC message according to the indication information, so that the DU can correctly send the RRC control signaling to the UE.

In a possible design, the indication information includes a message type; the message type is used to indicate a message type of the RRC message;

The DU sends the RRC message according to the indication information, including:

The DU broadcasts the RRC message according to the message type.

In this aspect, the DU can know the timing of transmitting the RRC message according to the message type, so the RRC message is correctly broadcast, and the terminal can correctly receive the RRC message.

In a possible design, the indication information may further include a cell identifier, and after receiving the indication information, the DU may broadcast the RRC message in a cell corresponding to the cell identifier. In this design, the DU can correspond to multiple cells.

In a possible design, the indication information further includes network standard indication information, where the network standard indication information is used to indicate a type of a radio access network that sends the RRC message, and after receiving the indication information, the DU may The system type of the radio access network broadcasts the RRC message. In this design, the DU can support multiple access technologies, such as CDMA technology, UMTS technology, LTE technology, 5G access technology, and the like.

The radio resource control RRC message sending method provided by each of the foregoing possible designs, after receiving the message type sent by the CU, the DU may broadcast the cell level RRC message to the UE in the cell according to the scheduling period corresponding to the message type, and the solution is solved. The DU does not recognize the message sent by the CU and does not know how to handle the message, so that the DU can correctly transmit the RRC control to the UE.

In a possible design, the indication information includes the identifier information of the signaling radio bearer SRB and the identifier information of the terminal device. The identifier information of the SRB can also be understood as the type information of the SRB, such as SRB0, SRB1, SRB2, SRB3. some type of. The SRB identification information can also be extended to the SRB identifier in the 5G new standard, such as SRB1S, SRB2S, and the like.

The DU sends the RRC message to the corresponding terminal according to the identifier information of the SRB and the identifier information of the terminal device. For example, according to the identifier information of the SRB and the identifier information of the terminal device, the DU may find that the corresponding PDCP entity/RLC entity processes the RRC message (that is, the processing corresponding to the RRC message is performed at the PDCP layer/RLC layer), and can pass The corresponding logical channel transmits the RRC message to the terminal device. It can be understood that the terminal device identifier may be an interface UE identifier between the CU and the DU, and is used by the CU and the DU to identify the UE on the interface. The DU maintains the relationship between the interface UE identifier and the DU internal UE identifier, such as a C-RNTI, and the DU finds the corresponding UE according to the identifier information of the terminal device. Then, according to the identifier information of the SRB, the RLC entity corresponding to the UE is found. The RRC message is forwarded to the RLC entity for processing, and then sent to the MAC/PHY layer for processing, and finally the RRC message is sent to the terminal through the air interface. In addition, for the CU-DU, there is a PDCP-RLC division mode, that is, the CU includes an RRC, PDCP layer, and the DU includes an RLC, a MAC, and a PHY layer. The DU finds an RLC entity corresponding to the UE for processing according to the identifier information of the terminal device and the identifier information of the SRB. The PDCP entity (processing of the PDCP layer), the RLC entity (processing of the RCL layer), how the logical channel is mapped to the transport channel, and how the transport channel maps to the physical channel can be found, for example, in the standard TS 36.300 v13.1.0 section 5 of 3GPP and 6 related content.

The method provided by the possible design, after receiving the identification information of the SRB sent by the CU and the identification information of the terminal device, the DU may send the corresponding logical channel to the corresponding terminal according to the identification information of the SRB and the terminal device.

In a second aspect, the embodiment of the present application provides a method for sending a radio resource control RRC message, including:

The distributed node DU receives the radio resource control RRC message sent by the central node CU through the user plane tunnel; wherein the user plane tunnel has an association relationship with the message type and the terminal of the RRC message;

The DU sends the RRC message to the terminal corresponding to the user plane tunnel. For example, the user plane tunnel has an endpoint identifier TEID, and the DU can obtain a corresponding message type (for example, SRB1) and a terminal identifier according to the TEID, and find a corresponding PDCP entity/RLC entity to process the RRC message (that is, at the PDCP layer/RLC). The layer performs the processing corresponding to the RRC message, and can send the RRC message to the terminal through the corresponding logical channel; another expression is that the DU can obtain the corresponding message type (for example, SRB1) and the terminal identifier according to the TEID, and find the corresponding The logical channel is sent to the corresponding terminal.

The method for transmitting a radio resource control RRC message provided by the foregoing second aspect, the RRC message is received by the CU through the user plane tunnel, and the RRC message is obtained according to the association between the message type of the user plane tunnel and the RRC message and the terminal device. The corresponding processing is performed and sent to the corresponding terminal.

In a possible design, before the distributed node DU receives the RRC message sent by the centralized node CU, the method further includes:

The DU receives the bearer setup request message sent by the CU. For example, the tunnel setup request message may include the message type A and the terminal identifier B. In other words, the RRC message sent by the tunnel may be regarded by the DU as the RRC message. The message type is the message type A and is sent to the terminal identified by the terminal identifier B. Therefore, the RRC message can be processed correspondingly and sent to the corresponding terminal.

The DU establishes the user plane tunnel between the DU and the CU according to the bearer setup request message. In other words, the DU sends a response message to the CU, and the response message may include a tunnel endpoint identifier TEID on the DU side.

The method provided by the possible design, the DU sends a bearer setup request message to the CU to establish a user plane tunnel before sending the RRC message, so that the RRC message sent by the user plane tunnel can correctly identify the message type of the RRC message. And the terminal that wants to receive the RRC message ensures the correct transmission of the RRC message.

In a third aspect, the embodiment of the present application provides a distributed node DU, including:

a receiver, configured to receive a radio resource control RRC message and indication information sent by the centralized node CU;

And a transmitter, configured to send the RRC message according to the indication information.

In a possible design, the indication information includes a message type and a cell identifier; the message type is used to indicate a message type of the RRC message;

The transmitter is further configured to broadcast the RRC message in a cell corresponding to the cell identifier according to the cell identifier and the message type.

In a possible design, the indication information further includes network standard indication information, where the network standard indication information is used to indicate a type of a radio access network that sends the RRC message.

In a possible design, the indication information includes identifier information of the signaling radio bearer SRB and identifier information of the terminal device;

The transmitter is further configured to send the RRC message to the terminal device corresponding to the identifier information of the terminal device according to the identifier information of the SRB and the identifier information of the terminal device.

As an optional design, the DU may include a processor, a transceiver, and a communication circuit, where the processor is configured to receive, by using a communication circuit, an RRC message and indication information sent by the CU, and send the RRC message by using the transceiver according to the indication information. . For details of the implementation of the RRC message transmission of the DU, refer to the content of the first aspect of the foregoing other embodiments.

The beneficial effects of the DUs provided by the foregoing third aspect and the possible designs of the third aspect can be referred to the advantages of the first aspect and the possible designs of the first aspect, and are not described herein again.

In a fourth aspect, the embodiment of the present application provides a distributed node DU, including:

a receiver, configured to receive, by using a user plane tunnel, a radio resource control RRC message sent by the centralized node CU;

And a transmitter, configured to send the RRC message to the terminal corresponding to the user plane tunnel.

In a possible design, the receiver is further configured to receive a bearer setup request message sent by the CU;

And a processor, configured to establish the user plane tunnel between the DU and the CU according to the bearer setup request message.

As an alternative design, the DU includes a processor, a transceiver, and communication circuitry. The processor is configured to receive, by using the communication circuit, an RRC message sent by the CU through the user plane tunnel, and send the RRC message to the terminal corresponding to the user plane tunnel by using the transceiver. For details on how the DU sends the RRC message, refer to the content of the second aspect of the other embodiments.

The beneficial effects of the DUs provided by the fourth aspect and the possible designs of the fourth aspect can be referred to the advantages of the second aspect and the possible designs of the second aspect, and are not described herein again.

The above transceivers and communication circuits may be implemented in one physical device, such as a single board, which may be referred to as a transceiver unit, a communication unit, or the like.

DRAWINGS

FIG. 1 is a schematic diagram of division of a CU-DU at each protocol layer;

2 is a schematic flowchart of Embodiment 1 of a method for transmitting a radio resource control RRC message according to the present application;

3 is a schematic flowchart of Embodiment 2 of a method for transmitting a radio resource control RRC message according to the present application;

Figure 4 is a schematic diagram of DSCP and IP priority bits;

FIG. 5 is a schematic structural diagram of Embodiment 1 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of Embodiment 2 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of Embodiment 3 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of Embodiment 1 of a DU according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a second embodiment of a DU according to an embodiment of the present disclosure.

detailed description

The techniques described herein can be used in a variety of communication systems, such as current 3G, 4G communication systems and next generation communication systems, such as Global System for Mobile communications (GSM), Code Division Multiple (Code Division Multiple) Access; referred to as CDMA system, Time Division Multiple Access (TDMA) system, Wideband Code Division Multiple Access Wireless (WCDMA) system, Frequency Division Multiple Access (Frequency Division Multiple) Addressing; abbreviation: FDMA) system, Orthogonal Frequency-Division Multiple Access (OFDMA) system, single carrier FDMA (SC-FDMA) system, General Packet Radio Service (referred to as: General Packet Radio Service; GPRS) system, Long Term Evolution (LTE) system, 5G communication system (such as NR (new radio) system), communication system with multiple communication technologies (such as LTE technology and NR technology integration) Communication systems) and other such communication systems.

In the present application, a terminal may also be referred to as a terminal device or a terminal device.

In the present application, the functions of the protocol layers of the CU and the DU can be divided according to actual needs. In implementation, the CU and the DU can have a complete protocol layer, for example, including the processing functions of the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the physical layer. In the deployment, some base stations can be configured to enable the processing function of the RRC layer. Such a base station can be regarded as a CU, and some base stations are configured to enable processing functions of the PDCP layer and the following layers, and these base stations can be regarded as DUs. CU and DU are a name for a base station with different protocol layer functions, and other titles may exist in the communication field.

In the present application, a base station is an access network device. There are different titles in different networks. For example, in a 5G network, it can be called a TRP (transceiver point), a micro station, a small station, a macro station, a high frequency base station, a low frequency base station, and the like.

In the present application, the messages have different message types. For example, in a classification of messages, the messages may be MIB messages, SIB1 messages, paging messages, minimum SI messages, SI messages, other SI messages, SIB2 messages. The SIB1 message and the SIB2 message may also be collectively referred to as an SIB message. In some cases, SIB1 and SIB2 may also be referred to as identifiers of SIB messages, or "1" and "2" of SIB1 and SIB2 may be referred to as identifiers of SIB messages. As an example, in an LTE system, a system message may be divided into an MIB message, an SIB1 message, and an SI message, where the MIB message includes downlink system bandwidth, PHICH configuration, and SFN information, and the SIB1 message may specify which SI messages, each of which The period of the SI message and which SIBs are included in each SI message, the SI message contains the SIB1 SIBs other than the same scheduling requirement (transmission period). As another example, for a 5G system (NR system), the system message can be divided into a minimum SI message and a other SI message; wherein the minimum SI message can be understood as a message type carrying system information necessary for the communication system, for example The communication system will send messages in a fixed period according to the agreement so that the terminal can discover or access the communication system. The other SI message is relative to the minimum SI message and can be understood as an SI message other than the minimum SI message. Optionally, other SI messages can be further classified into different types, such as other SI 1, other SI2, otherSI3, and the like. As an example, the system message of the LTE system and the system message of the 5G system may coexist in one communication system. As an example, the scheduling information of the MIB message, the SIB1 message, the paging message, the minimum SI message, the SI message, and the other SI message may be agreed in advance, for example, by a communication standard. As another example, the SI message, the scheduling information of the other SI message may be notified to the terminal by the network, for example, the base station notifies the terminal.

In the present application, the MIB message, the SIB1 message, the SIB message, the SI message, the SRB message, etc. may sometimes omit the suffix "message", which is simply referred to as MIB, SIB1, SIB, SI, SRB.

In the present application, the protocol layer is sometimes also referred to as a layer, for example, the RRC protocol layer may be referred to as an RRC layer.

In the present application, the scheduling period may also be referred to as a transmission period.

In the present application, the network standard information may also be referred to as network standard information, or simply as a network standard.

In this application, the identifier of the tunnel may be an endpoint identifier of the tunnel, such as an endpoint identifier of the tunnel on the CU side, or an endpoint identifier of the tunnel on the DU side.

The technical solution of the present application can be applied not only to RRC messages, but also to messages of other protocol layers as the communication protocol layer changes. The following takes the message of the RRC protocol layer as an example for description. The message of the RRC protocol layer may be referred to as an RRC message.

2 is a schematic flowchart of Embodiment 1 of a method for transmitting a radio resource control RRC message according to the present application. The method shown in Figure 2 can also be regarded as a method of transmitting a message. The embodiment of the present application provides a method for transmitting a radio resource control RRC message, which may be performed by any device that performs a radio resource control RRC message sending method, and the device may be implemented by software and/or hardware. In this embodiment, the device can be integrated in the DU. As shown in FIG. 2, the method in this embodiment may include:

Step 201: The DU receives an RRC message and indication information sent by the CU.

In other words, the DU receives the first message and the indication information from the CU.

Step 202: The DU sends an RRC message according to the indication information.

In other words, the DU sends the first message based on the indication information.

In this embodiment, since the interface between the CU-DUs is introduced in the CRAN architecture, how the DU identifies the message sent by the CU and correctly transmits the message to the terminal is a problem to be solved. In this embodiment, after receiving the message sent by the CU, for example, Radio Resource Control (RRC), and the indication information, the DU can learn how to send the message according to the indication information, so the message can be sent. Send it correctly; for example, it is sent to the user equipment (User Equipment; UE for short). As an example of an implementation manner, in a Packet Data Convergence Protocol (PDCP)/Radio Link Control (RLC) division mode, that is, a CU has an RRC+PDCP layer, and a DU has an RLC. / Media Access Control (MAC) / Physical Layer (Physical Layer; PHY). The specific format of the RRC message sent by the CU to the DU should be: PDCP/RRC message (this part is used as the payload transmitted by the CU-DU interface, for example, on the CU-DU interface, and may also be included in the CU-DU. The interface protocol layer may be a CU-DU interface control plane protocol layer or a CU-DU interface user plane protocol layer, that is, SCTP or GTP-U. As an example, the format of the RRC message sent by the CU to the DU may be as follows.

PDCP head

RRC message

It can be understood that the RRC message can be transmitted between the CU and the DU by using a control plane protocol or a user plane protocol between the CU and the DU.

After the DU is received, the CU-DU interface protocol layer is removed and the payload, that is, the PDCP/RRC message is parsed, and then encapsulated into a PHY/MAC/RLC/PDCP/RRC message, and sent to the UE. As an example, the RRC message after the packetization can be as follows.

PHY header

MAC header

RLC head

PDCP head

RRC message

In addition, the indication message sent by the CU to the DU is directly readable by the DU. For example, the cell or domain in the SCTP or GTP-U carries the indication message or serves as the indication information.

It can be understood that the DU receives the RRC message and the indication information sent by the CU, and the specific format of the control plane protocol transmission between the CU and the DU may be as follows.

终端设备的标识信息Terminal device identification information
SRB的标识信息SRB identification information
RRC消息RRC message

As another example, the division mode of the RRC/PDCP layer, that is, the division mode of option 1 in FIG. 1 may be adopted. In this division mode, the CU supports the RRC layer, and the DU supports the PDCP layer and the following protocol layers. The RRC message sent by the CU to the DU is the payload of the PDCP layer for the DU. The RRC message sent by the CU to the DU cannot be correctly sent to the terminal. The CU may carry the indication information in an interface message with the DU, or in an interface data packet.

Optionally, the indication information may include a message type, where the message type is a message type of the first message. The message type can be associated with scheduling information, that is, messages belonging to the message type can be scheduled using the scheduling information. The association relationship between the scheduling information and the message type may be specified by the communication standard, or may be specified by the network device and sent to the terminal. The delivery message type is equal to the scheduling information indicating the message of the DU, so the DU can correctly send the message.

For example, the first message type may be an MIB message, an SIB1 message, an SI message, a paging message, a minimum SI message, or a other SI message. The MIB message, the SIB1 message, the SI message, the paging message, the minimum SI message, and the scheduling information of the other SI message may be agreed in advance, for example, by a communication standard, or may be sent by the CU to the DU. Therefore, when the DU learns the message type of the message, it is equal to the scheduling information corresponding to the message. Here, the message type that can be expressed as the first message is associated with the scheduling information.

For another example, the first message type may be an SI message or a other SI message. The scheduling information corresponding to the SI message or the other SI message may be sent by the base station to the terminal, for example, by using an MIB, SIB1 or minimum SI message.

For another example, the first message type may be an SRB1 message, or an SRB2 message, or an SI message, or another SI message. The above message can be sent to a specific terminal. A signaling bearer can be established between the terminal and the DU. Usually a signaling bearer is associated with a particular terminal and a particular message type. The indication information may also include the identifier of the terminal, so after the DU knows the message type of the message and the identifier of the corresponding terminal, the DU may send the message to the UE on the corresponding signaling bearer. Specifically, the network side establishes a corresponding PDCP entity and an RLC entity for each bearer of a terminal. The message type and the terminal identifier may be sent by the DU to the corresponding PDCP entity or the RLC entity for corresponding processing, and the bearer is performed. A one-to-one correspondence with the logical channel, the DU may send the message on the physical resource corresponding to the logical channel, so that the message can be correctly sent to the corresponding terminal.

As a variant, the message type or the terminal identifier in the indication information may be replaced by other information. For example, after the tunnel is established for the terminal, the message of the terminal is sent through the tunnel, and the identifier of the tunnel may be used to indicate the user terminal. After the tunnel is established, for example, the message type of the terminal is sent, that is, the message of the message type of the user is sent through the tunnel, and the tunnel identifier can be used to indicate the message type and the terminal identifier.

Optionally, the scheduling information is mainly used to indicate the timing of sending the message. For example, the scheduling information may include: a scheduling period or a scheduling window. Optionally, the scheduling information may further include validity information.

The method for sending a message provided by the embodiment of the present application can help the DU to identify how to send the message sent by the CU to the DU correctly by using the indication information. As an example, the method for transmitting a radio resource control RRC message provided by the embodiment of the present application is to receive an RRC message and indication information sent by the CU, and send an RRC message according to the indication information. Since the DU can send the RRC message according to the indication information after receiving the RRC message and the indication information, the CU can enable the CU to correctly transmit the RRC control signaling to the DU.

It should be noted that, in the embodiment and the following embodiments, only the RRC message is used as an example. In an actual application, the DU may also receive other high-level messages sent by the CU. The upper layer here refers to the protocol layer that the CU supports and the DU does not recognize. In addition, with the development of network technology, the protocol layers supported by DU and CU will also change, and the division of the protocol layer will also change. In the new network environment, when the DU receives the high-level message that the DU does not support from the CU, the method provided by the embodiment of the present application may also be used to perform the transmission of the high-level message.

Some discussion of the embodiment shown in Figure 2 is made below.

Generally, messages can be divided into cell level messages and user level messages. A cell-level message refers to a message broadcasted in the cell, which is a message that is not for a specific user, that is, the message is for a terminal device of the cell; the user-level message is a pointer sent to a specific user. Message. For example, the RRC message includes a cell level RRC message and a user level RRC message.

The cell level message is exemplified below.

Specifically, those skilled in the art can understand that, in order to ensure the reliability of the transmission, the cell-level signaling can be transmitted through the transport layer protocol-Stream Control Transmission Protocol (SCTP) of the control plane. Since the CU and the DU in the CRAN are two entities, the indication information needs to be transmitted through the interface. Therefore, the RRC message at the cell level needs to indicate the message type and the cell identifier through the interface between the CU-DUs.

For the RRC message, the RRC message of the cell level includes a master information block (MIB) message and a system information block (SIB) message, and the SIB message can be further divided into an SIB1 message and an SI. Message. As a special case, a paging message is paged for a particular user, but can also be considered a cell level message. As a special case, SI messages such as SIB2, SIB3, ..., SIB23, and other SI messages can be regarded as either a cell-level message or a user-level cancellation. interest. The SIB message can be further divided into SIB1 and SIB2, SIB3, ..., SIB23, etc., and SIB2, SIB3, ..., SIB23 can also be called SI messages, that is, SIB messages can be divided into SIB1 messages and SI messages. The MIB message and the SIB message (the SIB1 message and the SI message) may be referred to as system messages. For example, in the LTE system, the transmission period of the MIB is 40 ms, the transmission period of the SIB1 is 80 ms, and the SIB messages after the SIB2 have different periods. The period of the SIB message after SIB2 can be given in SIB1. For another example, the cell level RRC message may include a minimum SI message, a other SI message, and a paing message. The sending period of the minimum SI message can be agreed in advance, and the sending period of the ohther SI message can be specified by the minimum SI. Exemplarily, the cell level RRC message may indicate the type of the SIB through an interface message between the CU-DUs, so that the DU learns the SIB type.

Since the cell-level message has different scheduling requirements, the CU can send the cell-level message to the DU by:

The first optional mode is that the CU sends a cell-level message and a message type to the DU according to the scheduling information of the cell-level message. The message type can be regarded as an indication information. After receiving the cell-level message, the DU will The cell-level message message is sent on the corresponding channel (the channel is associated with the time-frequency resource) according to the message type. For example, the DU will send the MIB message on the Physical Broadcast Channel (PBCH), and share the channel in the physical downlink. Other messages, etc. are sent on (Physical Downlink Shared Channel; PDSCH). In this mode, the scheduling timing of the cell-level message is triggered by the CU to the DU. The scheduling information of the cell-level message does not need to be configured on the DU. After receiving the message sent by the CU, the cell-level message can be sent immediately or after an agreed time. .

The second optional mode is that the CU sends the cell-level message and the scheduling information corresponding to the cell-level message to the DU. After receiving the cell-level message, the DU sends the cell-level message according to the scheduling information. The CU may not need to send the cell-level message to the DU every time, but only when the cell-level message changes, the CU sends the updated cell-level message to the DU through the interface, which can greatly reduce the CU and the DU. Interaction between. For the Paging message, the CU usually sends the Paging message directly after receiving the Paging message.

As a variation of the second mode, the scheduling information may be replaced with other information associated with the scheduling information. For example, when the correspondence between the message type and the scheduling information is configured on the DU, the message type of the cell-level message can be sent to the DU, and the DU can obtain the scheduling information of the cell-level message. The correspondence between the foregoing message type and the scheduling information may be configured by the CU to the DU, or may be agreed by the communication standard.

In the second mode and its variant, if the scheduling information of the cell-level message is not specified by the communication standard, the terminal cannot know how to receive the cell-level message at this time. Therefore, the network side also needs to notify the terminal of the scheduling information. As an example, the scheduling information may be carried in an SIB1 message or a minimum SI message and sent to the terminal. Since the scheduling information terminal of the SIB message or the minimum SI message is known in advance, the terminal can correctly receive the scheduling information to receive subsequent cell-level messages.

As mentioned above, the scheduling information is mainly used to indicate the timing of sending a message. For example, the scheduling information may include: a scheduling period or a scheduling window. Optionally, the scheduling information may further include validity information. The scheduling period and the scheduling window information are used to determine a subframe in which the cell-level message is read. When the valid information changes, the system message is changed. The scheduling window and the scheduling period may limit the UE to read the system message in the scheduling window. Reduce the energy consumption of the UE. It should be noted that when the CU sends the latest cell-level message to the DU, the DU can learn that the cell-level message has changed when the cell-level message is received. At this time, the CU can directly cancel the cell-level message. The information is replaced with the latest cell level message. In this case, the scheduling information may not include valid information. In addition, if the scheduling information includes the valid information, if the DU finds that the valid information is different from the locally saved valid information, the CU can learn that the cell-level message has changed. At this time, the DU will be based on The valid information sent by the CU performs cell level message update. In addition, when the cell-level message changes, the CU will be able to notify the UE by the paging message that the cell-level message has changed.

In summary, an embodiment of the present application provides a method for sending a message, including:

The CU sends the first message and the indication information to the DU;

The DU transmits the first message based on the indication information.

As a first optional design, the indication information includes a first message type of the first message, and the first message type may be an MIB message, an SIB1 message, an SI message, a paging message, a minimum SI message, a other SI message, The first message type is associated with the first scheduling information, where the DU sends the first message based on the indication information, and the DU sends the first message based on the first message type and the first scheduling information.

For example, if the message type is an MIB message, the MIB message will be sent on the PBCH according to a period of 40 ms. If the message type is an SIB1 message, the SIB1 message will be sent on the PDSCH according to a period of 80 ms.

As a second optional design, the indication information includes first scheduling information of the first message and a first message type of the first message, where the first message type is an SI message or a other SI message; wherein the DU is based on the indication The information sending the first message is that the DU sends the first message based on the first message type and the first scheduling information; wherein the method further includes the second message type, the second message, that the DU receives the second message and the second message from the CU. The type is an SIB1 message or a minimum SI message, and the second message includes the foregoing first scheduling information; the DU sends the second message based on the second message type and the second scheduling information associated with the second message type. The terminal can learn the scheduling information of the first message by sending the second message, so as to correctly receive the first message.

For example, the CU may send the message A and the message type A to the DU, the message type A is the minimum SI message, and the message A includes the scheduling information B of the message B. After the DU receives, the message A is sent according to the scheduling information of the minimum SI message and the message type A. The CU may send a message B and an indication information B to the DU, the indication information B including the scheduling information B and the message type B of the message B. After the DU receives, the message B is sent according to the scheduling information B of the message B and the message type B. Since the scheduling information terminal and the network side of the minimum SI are already known, the terminal can correctly receive the message A and learn the scheduling information B from the message A. By scheduling the information B, the terminal can correctly receive the message B.

Optionally, the SI message may be any one of SIB2, SIB2, ... SIB23 messages. The scheduling information corresponding to different SIB messages may be different.

In the above method, the DU may find a corresponding channel according to the message type to send a corresponding message. For example, the message can be sent on the broadcast channel according to the first message type.

Optionally, the interaction between the CU and the DU may be performed by using a transport layer protocol, a Stream Control Transmission Protocol (SCTP). The information exchange between the CU and the DU through SCTP can improve reliability. Specifically, the CU may use the first message as a payload of the SCTP data packet, place the indication information in a protocol header of the data packet, and send the first message and the indication information to the DU. The processing of the second message can also refer to this mode.

Optionally, if the DU corresponds to multiple cells, the indication information may further include a cell identifier, and the DU receives the small After the area is identified, the corresponding cell can send the message.

Optionally, if the DU supports multiple network standards, for example, when the 2G, 3G, and 4G are supported, the indication information may further include network standard indication information, where the network standard indication information is used to indicate which access technology is used. To send a message. When the DU receives the network standard information, it can send the message by using the corresponding network standard.

Optionally, the information exchange between the CU and the DU may be sent to the DU by using a GPRS Tunneling Protocol for the user plane (GTP-U) or a protocol encapsulation (PoE).

Example 1: A GTP-U tunnel can be established between the CU and the DU for each type of message. That is, the message type and the tunnel are mapped (mapped, or associated). The message sent to the DU through the tunnel can be considered. Has the message type corresponding to the tunnel. Specifically, after receiving the data packet of the GTP-U, the DU may be based on the tunnel identifier carried in the GTP-U (for example, the endpoint identifier, where the endpoint identifier may be an endpoint identifier on the CU side or an endpoint identifier on the DU side, the endpoint identifier The tunnel can be identified to know the corresponding message type. GTP-U is hereinafter referred to as GTP.

Optionally, when the tunnel is established, the scheduling information corresponding to the message type, or the cell identifier, or the network standard information may be sent to the DU. After receiving the message sent by the CU through the tunnel, the DU searches for the message type, scheduling information, cell identifier, or network standard indication information corresponding to the tunnel, so as to correctly send the message delivered through the tunnel.

As an optional implementation manner, when the CU and the DU establish a tunnel, the CU may send the message type to the DU, thereby establishing an association between the message type and the tunnel. Wherein, (1) if the scheduling information is specified by the communication standard, the scheduling information corresponding to the message type may not be sent to the DU when the tunnel is established; (2) if the scheduling information needs to be sent by the CU to the DU, then the establishment is established. The tunnel sends the scheduling information corresponding to the message type to the DU. (3) If the scheduling information needs to be sent by the CU to the DU, the scheduling information is sent to the DU when the subsequent message is sent to the DU. For example, the CU carries the message to be sent in the payload of the GTP packet sent to the DU, and carries the scheduling information corresponding to the message type in the header of the GTP packet.

Optionally, in the case of the foregoing (1), (2), or (3), if the cell identifier or the network standard information is required, the cell identifier or the network standard information may be sent to the DU when the tunnel is established; When the message is sent to the DU, the cell identifier or network standard information does not need to be sent. The DU can obtain the required information through the tunnel endpoint identifier. Optionally, in the case of (1), (2) or (3), if the cell identifier or the network standard information is still needed, the cell identifier or the network standard information may be sent to the DU when the message is sent to the DU; for example The CU carries the message to be sent in the payload of the GTP packet sent to the DU, and carries the cell identifier or the network standard information in the packet header of the GTP data packet.

Optionally, a payload type can be used in the GTP header to carry different information. For example, the GTP header includes one or more payload type fields, wherein different values of one payload type field indicate different message types, and different values of another payload type field indicate different cell identifiers, and different values of a payload type field indicate different values. Network standard.

Optionally, in the second optional design described above, a trigger condition may be set to trigger the sending of the first message. For example, in a second optional design, the method may further include: the DU receiving the first request message from the one or more terminals, the first request message including the first message type. After receiving the first request message, the DU can learn that the terminal requests the first message. For example, the terminal requests an SIB2 message, requests an SIB3 message, and requests another SI. 2 messages, etc.

It can be seen that the trigger condition for the DU to send the first message to the terminal is that the request of the terminal is received. The DU may send the first message to the terminal according to the request of the terminal. If the first message does not exist on the DU, or the first message has expired, or the DU needs to obtain the first message from the CU each time, or the condition set on the DU is met, the DU may request the CU to obtain the first message. For example, the DU sends a second request message to the CU, where the second request message includes the first message type. After receiving the second request, the CU learns that the first message needs to be sent to the DU according to the type of the message carried in the second request.

Optionally, the scheduling information corresponding to the first message suggested by the DU may also be carried in the second request for reference by the CU. If the CU agrees to use, when sending the first request message to the DU, it only needs to send the indication information to tell the DU to agree to adopt the recommended scheduling information, and does not need to repeatedly send the scheduling information to the DU.

Optionally, a threshold may be set on the DU. When the number of times the terminal requests the first message meets the threshold, the DU may send the first message to the terminal, or request the CU to send the first message to the DU, so that the DU sends the first message.

The second optional design described above can be applied to the SI message of the LTE system or the other SI message of the NR system.

Currently, cell-level messages discussed in the NR system include minimum system information (minimum SI), and other system information (other SI) (also called on demand SI), where the scheduling information of the minimum SI can be communicated. The standard stipulates that the scheduling information of other SI can be notified to the terminal by the network side, for example, carrying the scheduling information of other SI in the minimum SI.

For the connected UE, the UE will request the other SI by sending an RRC message, and the base station will directly send the other SI to the UE through the RRC message, or the base station may directly send the other SI to the UE by broadcast. In particular, for the idle state and the third state UE, the UE may request the other SI through a Random Access Channel (RACH) msg1 or msg3, and the base station may directly send the other SI requested by the other party to the UE through RACH msg2 or msg4. You can also send other SI directly to the UE by broadcast.

When the CU sends the minimum SI and the other SI to the DU, the minimum SI and the other SI can be directly sent to the DU, and the preset threshold can be sent to the DU. The number of other SI messages sent by the DU after receiving the UE exceeds the preset. After the threshold, on the one hand, the DU will send an indication message to the CU, where the indication message includes not only the notification message for notifying the CU to send other SI (for example, the notification message contains the SIB type of the other SI, for example, the DU requests the CU. The SIB2+SIB 5) is sent, and the other SI scheduling information recommended by the DU is also included. For example, the notification message sent by the DU to the CU is: SIB2+ period + SI window, SIB5+ period + SI window. On the other hand, the DU may also send a notification message to the UE through msg2/msg4 to inform the UE to acquire other SI by listening to the broadcast. After receiving the indication message, the CU needs to notify the UE of other SI scheduling information. Therefore, the CU will send the updated minimum SI to the DU. Optionally, if the CU accepts the other SI scheduling information suggested by the DU, the CU will not send the other SI scheduling information to the DU. If the CU does not accept the other SI scheduling information suggested by the DU, the CU needs to send the CU to the DU. The SIB type of the other SI and the corresponding scheduling information. Optionally, when the CU sends the other SI to the DU for the first time, the CU needs to send the changed other SI to the DU.

The number of the request messages sent by the UE to the UE exceeds the preset threshold may include the following situations: when the DU receives the total number of request messages sent by the UE for requesting the broadcast RRC message exceeds the first pre- The threshold is set, or the total number of received request messages exceeds a second preset threshold within a preset time period, or the frequency of receiving the request message exceeds a third preset threshold.

It should be noted that when the CU sends the updated minimum SI, the SIB type+ scheduling information of the other SI, and the other SI message itself to the DU, the CU may transmit by using the above-mentioned control plane mode, or may be sent by the above-mentioned user plane mode. For the specific transmission mode, the embodiment is not limited herein.

The method for sending a message provided in this embodiment can enable the DU to correctly send a message sent by the CU to the DU by indicating the scheduling information to the DU. In addition, the correspondence between the scheduling information and the message type is established in advance, which is advantageous for reducing the interaction burden between the CU and the DU.

The user level message is exemplified below.

For example, the user-level message may be an SRB message, and the SRB message may be classified into a signaling radio bearer (SRB) 0 (such as an RRC connection setup request, an RRC connection setup, an RRC connection setup, etc.), SRB1 ( Such as RRC reconfiguration message, RRC reconfiguration complete message, etc.), SRB2 (security related RRC message) three categories. Among them, SRB0 is currently a transparent transmission mode (TM), and there is no corresponding PDCP/RLC entity. As an example, the PDCP/RLC entity is configured by the RRC message of the base station after establishing the RRC connection. Therefore, there is no corresponding PDCP/RLC entity in the SRB0 message before the RRC connection is established. SRB1 and SRB2 have corresponding PDCP and RLC entities. As an example, after the RRC connection is established, the base station configures the PDCP/RLC entity corresponding to the SRB1 through the RRC message. After the security authentication process, the base station further configures the PDCP/RLC entity corresponding to the SRB2 through the RRC message. Here, SRB0, SRB1, and SRB2 can be considered as different message types. Sometimes, SRB0, SRB1, and SRB2 may also be referred to as identification information of the SRB. For SRB1 and SRB2, the DU will find the corresponding PDCP/RLC entity according to the message type of the SRB and the identification information of the terminal device (currently, in the LTE protocol, the PDCP/RLC entity is each SRB/DRB of each UE), after PDCP The processing of the /RLC entity is then sent to the MAC/PHY layer and finally sent to the corresponding terminal. For SRB0, it is sent directly to the MAC/PHY layer without being passed through the PDCP/RLC entity and finally sent to the corresponding terminal. As an example, the DU directly sends the SRB0 to the MAC/PHY layer for processing according to the SRB identification information, that is, SRB0, and finally sends the terminal corresponding to the identification information of the terminal through the air interface. As an example, the DU directly sends the SRB0 to the MAC/PHY layer for processing according to the SRB identification information, that is, SRB0, and finally sends the terminal corresponding to the identification information of the terminal through the air interface.

For user level messages, in this application, it can be sent in the following manner. As a first alternative design, a control plane protocol between the CU and the DU can be used to deliver the message. As an example, the user plane message is delivered using a control plane protocol of the interface between the CU and the DU.

In this design, a method for sending a message provided by the implementation of the present application includes:

The CU sends the first message and the indication information to the DU;

Optionally, the indication information includes a first message type of the first message and a terminal identifier, where the first message type is an SRB0 message, an SRB1 message, an SRB2 message, an SI message, or a other SI message. At this time, the first message type may also be referred to as an SRB identifier or identifier information of the SRB.

The DU sends the first message based on the first message type and the terminal identity.

Optionally, if the first message type is SRB0, the DU is allocated according to the terminal identifier and SRB0. Sending a first message to the physical resource corresponding to the SRB0 of the terminal.

Optionally, if the first message type is SRB1 or SRB2, the DU finds the PDCP/RLC entity corresponding to the terminal identifier and the SRB type, and sends the first message to the corresponding PDCP/RLC entity for corresponding processing, where The first message is sent on the physical resource corresponding to SRB1 or SRB2 allocated to the terminal.

Optionally, if the first message type is an SI message or a other SI message, the DU may process the SI message or the other SI message as an SRB0 message, an SRB1 message or an SRB2 message.

As an implementation manner, the interaction between the CU and the DU may adopt the SCTP protocol. The CU may carry the first message in the payload of the SCTP data packet, and carry the indication information and the terminal identifier in the packet header of the SCTP data packet, so as to send the first message, the indication information, and the terminal identifier to the DU.

Optionally, the indication information may further include a cell identifier or a network standard. For example, the sending of the first message by the DU based on the indication information may be that the DU sends the first message in the cell corresponding to the cell identifier based on the first message type and the terminal identifier, or the DU sends the first message based on the indication information, which may be a DU-based A message type and a terminal identifier are sent by using a wireless technology corresponding to the network standard.

As a second optional design, a user plane tunnel between the CU and the DU can be used for message delivery. For related content, reference may be made to the above-mentioned content that uses GTP-U to deliver cell-level messages.

As a first optional implementation manner, a user plane tunnel, such as a GTP-U tunnel, may be established between the CU and the DU for each SRB of each terminal.

Example 1: A DU sends a tunnel establishment request to a CU, where the setup request includes a first message type of the first message and a terminal identifier.

Example 2: The CU sends a tunnel establishment request to the DU, where the setup request includes the first message type of the first message and the terminal identifier.

Through the above two examples, the association between the tunnel and the first message type and the terminal identifier may be established. In other words, the association between the endpoint identifier of the tunnel and the first message type and the terminal identifier may be established. The message received from the tunnel, the DU can know the corresponding message type and terminal identifier. The endpoint identifier of the tunnel may be the endpoint identifier of the tunnel on the CU side, and may be the endpoint identifier of the tunnel on the DU side.

In this embodiment, the method for sending a message provided by the implementation of the present application includes:

The CU sends the indication information and the first message to the DU; wherein the indication information is an endpoint identifier of the tunnel;

The DU sends a first message based on the first message type and the terminal identifier corresponding to the tunnel.

Optionally, the payload part of the GTP data packet sent by the CU to the DU may carry the first message, where the indication information of the GTP data packet may carry the indication information, for example, the endpoint identifier of the tunnel.

Optionally, the indication information may further include a cell identifier or network standard information, so that the DU sends the first message in the corresponding cell or sends the first message by using a corresponding network technology.

The above solution is to establish a tunnel for each SRB of each terminal, and the CU does not need to send the message type and the terminal identifier to the DU every time, thereby saving the interaction resources between the CU and the DU.

As a second optional implementation manner, a user plane tunnel may be established between the CU and the DU for each terminal.

Example 1: A DU sends a tunnel establishment request to a CU, where the setup request includes a terminal identifier.

Example 2: The CU sends a tunnel establishment request to the DU, where the setup request includes the terminal identifier.

Through the above two examples, the association between the tunnel and the terminal identifier can be established. In other words, the tunnel can be established. The association between the endpoint identifier of the track and the terminal identifier. The message received from the tunnel, the DU can know the corresponding terminal identifier. The endpoint identifier of the tunnel may be the endpoint identifier of the tunnel on the CU side, and may be the endpoint identifier of the tunnel on the DU side.

The CU sends the indication information and the first message to the DU, where the indication information includes an endpoint identifier of the tunnel and a first message type of the first message;

The DU sends a first message based on the terminal identifier corresponding to the tunnel and the first message type.

Optionally, the payload part of the GTP data packet sent by the CU to the DU may carry the first message, where the indication information of the GTP data packet may be carried, for example, the endpoint identifier of the tunnel and the first message type of the first message.

The above solution is to establish a tunnel for each SRB of each terminal, and the CU does not need to send the terminal identifier corresponding to the message to the DU every time, thereby saving the interaction resource between the CU and the DU.

As an example, a payload type can be used in a GTP header to carry different information. For example, the GTP header includes one or more payload type fields, wherein different values of one payload type field indicate different message types, and different values of another payload type field indicate different cell identifiers, and different values of a payload type field indicate different values. Network standard.

A person skilled in the art should know that the user plane tunnel is bidirectional. Therefore, in addition to the CU needs to give the CU side tunnel endpoint, so that the DU knows which DRB or SRB message is sent to which tunnel endpoint, the DU also needs to give the DU side. The endpoint of the tunnel is used to let the CU know which tunnel endpoints the SRB or DRB messages are sent to. Therefore, the CU and the DU will learn the mapping relationship between the indication information and the tunnel endpoint through the interaction of the message.

The method for sending a message provided by the embodiment, after receiving the message type of the SRB and the identifier information of the terminal device, the DU may correspond to the identifier information of the terminal device according to the message type of the SRB and the identifier information of the terminal device. The terminal device sends a message.

FIG. 3 is a schematic flowchart of Embodiment 2 of a method for transmitting a radio resource control RRC message according to the present application. The embodiment of the present application provides a method for transmitting a radio resource control RRC message, which may be performed by any device that performs a radio resource control RRC message sending method, and the device may be implemented by software and/or hardware. In this embodiment, the device can be integrated in the DU. As shown in FIG. 3, the method in this embodiment may include:

Step 301: The DU receives the RRC message sent by the CU through the user plane tunnel.

Step 302: The DU sends an RRC message to the terminal corresponding to the user plane tunnel.

In this application, the signaling transmission at the UE level uses the SCTP control plane protocol, and the CU needs to specify the identification information of the SRB and the identification information of the terminal device to the DU. As another alternative implementation manner, in this embodiment, the user data protocol (User Data Protocol; UDP) and the tunneling protocol user plane (GPRS Tunnelling Protocol for the user plane; GTP-U) performs signaling transmission. The CU can send the RRC message to the DU through the GTP-U tunnel. Since the GTP-U carries the Tunnel Endpoint ID (TEID), the CU does not need to additionally indicate the SRB identification information and the terminal device to the DU. The identification information, the DU can correctly forward the RRC message to the UE according to the TEID.

The RRC message is sent by the CU through the user plane tunnel, and the RRC message is sent. The GTP carries the TEID, and the DU can perform RRC according to the TEID. The message is sent so that the DU can correctly forward the signaling.

Optionally, before the receiving the RRC message sent by the CU, the method further includes: the DU receiving the bearer setup request message sent by the CU, where the DU establishes a user plane tunnel between the DU and the CU according to the bearer setup request message.

Specifically, before the CU sends an RRC message to the DU, the user plane tunnel between the CU and the DU needs to be established. In a specific implementation process, different user plane tunnels may be established according to different types of SRBs. After the user plane tunnel is established, the CU will send an RRC message to the DU through the user plane tunnel.

In addition, when the user plane tunnel is established, the RRC message and the data are distinguished. In a specific implementation process, the CU sends a bearer setup request message to the DU, and the DU can distinguish the SRB of the RRC message by using the TEID. Type and data. The SRB type may be, for example, SRB1, SRB2, or the like. After distinguishing between the SRB type and the data, the priority of the signaling is guaranteed in different ways. Those skilled in the art can understand that the priority of the data is guaranteed by the Quality of Service (QoS) parameter. In this embodiment, the priority of the RRC message may be defined by multiplexing the defined transmission priority in the differentiated service code point (DSCP) or by redefining the unused in the DSCP. The priority of the field, Figure 4 is a schematic diagram of the DSCP and IP priority bits. As shown in Figure 4, the first six bits of the Type Of Service (TOS) are defined as DSCP, and the last two bits are reserved. Thus, DSCP There are 64 levels that can be defined, and only twenty levels are currently used. Undefined fields can be used to define the transmission priority of RRC messages.

Among them, DSCP value has two expressions, digital form and keyword form. In digital form, DSCP uses 6 bits, and the decimal interval is 0-63, so 64 levels (priority) can be defined. For example, binary DSCP value 000000 is equal to decimal DSCP value 0, binary DSCP value 010010 is equal to decimal DSCP value 18, etc. Wait. In addition, the DSCP value in the form of a keyword is called Per-Hop Behavior (PHB). Currently, there are three types of defined PHBs, namely Best Effort Service (BE Service) and Assured (Assured). Forwarding (AF) and Expedited Forwarding (EF). Since DSCP and IP precedence are coexistent, there is a problem of compatibility, and DSCP is poorly readable. Therefore, DSCP is further classified, and DSCP is divided into four categories: Class Selector (CS) Aaa 000, EF 101 110, AF aaa bb0, default 000 000. In addition, CS6 and CS7 are used by default for protocol packets. Because if these messages cannot be received, it will cause protocol interruption, and it is the highest priority message in most vendors' hardware queues; EF is used to carry voice traffic because voice requires low latency, low jitter, and low packet loss rate. It is the most important message after the protocol packet; AF4 is used to carry the signaling traffic of the voice; AF3 can be used to carry the live traffic of the Internet Protocol TV (IPTV), and the live broadcast is very real-time. Continuity and large throughput guarantees are required; AF2 can be used to carry video on demand (VOD) traffic. Compared with live VOD, real-time performance is not very strong, allowing for delay or buffering; AF1 can bear not Very important private line service, because the private line service is relative to IPTV and voice, IPTV and voice are the most critical services of operators, and need to be given the highest priority.

One of ordinary skill in the art will appreciate that all or part of the steps to implement the various method embodiments described above may be accomplished by hardware associated with the program instructions. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

FIG. 5 is a schematic structural diagram of Embodiment 1 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure. The sending device may be a separate DU, and may also be a device integrated in the DU, and the device may be implemented by software, hardware or a combination of software and hardware. As shown in FIG. 5, the transmitting device includes:

The receiving module 11 is configured to receive a radio resource control RRC message and indication information sent by the centralized node CU;

The sending module 12 is configured to send the RRC message according to the indication information.

Optionally, the receiving module 11 may be a receiver in the receiving device, and the sending module 12 may be a transmitter in the receiving device.

The apparatus for transmitting a radio resource control RRC message provided by the embodiment of the present application receives the RRC message and the indication information sent by the CU, and sends an RRC message according to the indication information. After receiving the RRC message and the indication information, the sending device of the RRC message may send an RRC message according to the indication information, so that the device can perform correct forwarding of the signaling.

Optionally, the indication information includes a message type and a cell identifier, where the message type is used to indicate a message type of the RRC message.

The sending module 12 is further configured to broadcast the RRC message in a cell corresponding to the cell identifier according to the cell identifier and the message type.

Optionally, the indication information further includes network standard indication information, where the network standard indication information is used to indicate a type of a radio access network that sends the RRC message.

Optionally, the indication information includes identifier information of the signaling radio bearer SRB and identifier information of the terminal device;

The sending module 12 is further configured to send the RRC message to the terminal device corresponding to the identifier information of the terminal device according to the identifier information of the SRB and the identifier information of the terminal device.

The apparatus for transmitting the radio resource control RRC message provided by the embodiment of the present application may perform the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

FIG. 6 is a schematic structural diagram of Embodiment 2 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure. The sending device may be a separate DU, and may also be a device integrated in the DU, and the device may be implemented by software, hardware or a combination of software and hardware. As shown in FIG. 6, the apparatus for transmitting the radio resource control RRC message includes:

The receiving module 21 is configured to receive, by using a user plane tunnel, a radio resource control RRC message sent by the centralized node CU;

The sending module 22 is configured to send the RRC message to the terminal corresponding to the user plane tunnel.

The apparatus for transmitting the radio resource control RRC message provided by the embodiment of the present application, the DU can receive the RRC message sent by the CU through the user plane tunnel, and send the RRC message, because the GTP carries the TEID, the DU can perform the RRC according to the TEID. The message is sent so that the DU can correctly forward the signaling.

FIG. 7 is a schematic structural diagram of Embodiment 3 of a device for sending a radio resource control RRC message according to an embodiment of the present disclosure. On the basis of the above embodiment, as shown in FIG. 7, further, the device further includes an establishing module 23;

The receiving module 21 is further configured to receive a bearer setup request message sent by the CU;

The establishing module 23 is configured to establish, between the DU and the CU, according to the bearer setup request message. The user plane tunnel.

FIG. 8 is a schematic structural diagram of Embodiment 1 of a DU according to an embodiment of the present disclosure. As shown in FIG. 8, the DU may include a transmitter 20, a processor 21, a memory 22, and at least one communication bus 23. The communication bus 23 is used to implement a communication connection between components. The memory 22 may include a high speed RAM memory 22, and may also include a non-volatile memory NVM, such as at least one disk memory 22, in which various programs may be stored for performing various processing functions and implementing the method of the present embodiment. step. In addition, the DU may further include a receiver 24. The receiver 24 in this embodiment may be a corresponding input interface having a communication function and a function of receiving information, and may also be a radio frequency module or a baseband module on the DU. The transmitter 20 can be a corresponding output interface having a communication function and a function of transmitting information, and can also be a radio frequency module or a baseband module on the DU. Optionally, the transmitter 20 and the receiver 24 may be integrated in one communication interface, or may be two independent communication interfaces.

In this embodiment, the receiver 24 is configured to receive a radio resource control RRC message and indication information sent by the centralized node CU.

The transmitter 20 is configured to send the RRC message according to the indication information.

The transmitter 20 is further configured to broadcast the RRC message in a cell corresponding to the cell identifier according to the cell identifier and the message type.

The transmitter 20 is further configured to send the RRC message to the terminal device corresponding to the identifier information of the terminal device according to the identifier information of the SRB and the identifier information of the terminal device.

The DUs provided in the embodiments of the present application may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.

FIG. 9 is a schematic structural diagram of a second embodiment of a DU according to an embodiment of the present disclosure. As shown in FIG. 9, the DU may include a transmitter 30, a processor 31, a memory 32, and at least one communication bus 33. The communication bus 33 is used to implement a communication connection between components. The memory 32 may include a high speed RAM memory 32, and may also include a non-volatile memory NVM, such as at least one disk memory 32, in which various programs may be stored for performing various processing functions and implementing the method of the present embodiment. step. In addition, the DU may further include a receiver 34. The receiver 34 in this embodiment may be a corresponding input interface having a communication function and a function for receiving information, and may also be a radio frequency module or a baseband module on the DU. The transmitter 30 can be a corresponding output interface having a communication function and a function of transmitting information, and can also be a radio frequency module or a baseband module on the DU. Optionally, the transmitter 30 and the receiver 34 may be integrated in one communication interface, or may be two independent communication interfaces.

In this embodiment, the receiver 34 is configured to receive, by using a user plane tunnel, a radio resource control RRC message sent by the centralized node CU.

The transmitter 30 is configured to send the RRC message to a terminal corresponding to the user plane tunnel.

Optionally, the receiver 34 is further configured to receive a bearer setup request message sent by the CU;

The processor 31 is configured to establish the user plane tunnel between the DU and the CU according to the bearer setup request message.

The embodiment of the present application further provides a node. This node is used to implement a method of transmitting a message such as described above. Optionally, the node can be a DU.

As another alternative design, the node includes a processor and a memory. The memory is for storing a program for implementing a method of transmitting a message such as the one described above, and a processor for executing the above program to implement a method of transmitting a message such as the above.

How the node implements a message transmission may refer to, for example, the content of a method for transmitting a message as described above.

In a fourth aspect, the embodiment of the present application further provides another node. This node is used to implement a method of transmitting a message such as described above. Optionally, the node can be a CU.

As another alternative design, the node includes a processor and a memory. The memory is used to store a program for implementing the above-described method for transmitting a message, and the processor is configured to run the above program to implement the above-described method for transmitting a message.

How to implement the sending of a message by the node can refer to the content of the sending method of the above message.

The embodiment of the present application further provides a communication system, including the foregoing two types of nodes.

The embodiment of the present application further provides a computer program product, where the program product includes a program for implementing a method for transmitting a message as described above.

The embodiment of the present application further provides a computer readable storage medium, where the medium stores the above program.

The application also provides the following examples. It should be noted that the numbers of the following embodiments do not necessarily need to follow the numbering sequence of the previous embodiment:

Embodiment 1, a method for sending a message, comprising:

The distributed node DU receives the first message and the indication information from the centralized node CU;

The DU sends the first message based on the indication information.

Embodiment 2, the method as described in Embodiment 1,

The indication information includes a first message type of the first message, the first message type is a main information block MIB message, or a system information block type-SIB1 message, or a paging paging message, or a minimum system information minimum SI a message, or a system information SI message, or other system information other SI message, the first message type being associated with the first scheduling information;

Sending, by the DU, the first message according to the indication information:

The DU sends the first message based on the first message type and the first scheduling information.

Embodiment 3, the method as described in Embodiment 1,

The indication information includes first scheduling information of the first message and a first message type of the first message, where the first message type is a system information SI message or other system information other SI message;

Sending, by the DU, the first message according to the indication information:

Sending, by the DU, the first message according to the first message type and the first scheduling information;

The method further includes:

Receiving, by the CU, a second message type of the second message and the second message, where the second message type is a system information block type-SIB1 message or a minimum system information minimum SI message, the second message Include the first scheduling information;

The DU sends the second message based on the second message type and the second scheduling information associated with the second message type.

The method of embodiment 4, further comprising:

Receiving, by the DU, a first request message from one or more terminals, where the first request message includes the first message type;

The DU sends a second request message to the CU, where the second request message includes the first message type.

Embodiment 5, the method as described in Embodiment 4,

The number of the first request messages meets a threshold condition.

The method of embodiment 5, further comprising:

The DU receives the threshold condition from the CU.

Embodiment 7. The method of any of embodiments 2-6,

The indication information further includes: a cell identifier, or a network standard;

Sending, by the DU, the first message based on the first message type and the first scheduling information:

Sending, by the DU, the first message in a cell corresponding to the cell identifier, based on the first message type and the first scheduling information; or

The DU sends the first message by using a wireless technology corresponding to the network standard, based on the first message type and the first scheduling information.

Embodiment 8. The method of any of embodiments 2-7,

The first scheduling information includes: validity information, or a scheduling period, or a scheduling window.

Embodiment 9, the method as described in Embodiment 1,

The indication information includes a first message type of the first message and a terminal identifier, where the first message type is a signaling radio bearer type 1 SRB1 message, or a signaling radio bearer 2 SRB2 message, or a system information SI message, Or other system information other SI message;

Sending, by the DU, the first message according to the indication information:

The DU sends the first message based on the first message type and the terminal identifier.

Embodiment 10, the method as described in Embodiment 1,

The method further includes: the DU sending a tunnel establishment request message to the CU, where the setup request message includes a first message type and a terminal identifier of the first message;

The indication information includes an identifier of the tunnel;

Sending, by the DU, the first message according to the indication information:

Embodiment 11, the method as described in Embodiment 1,

The method further includes: the DU sending a tunnel establishment request message to the CU, where the setup request message includes a terminal identifier;

The indication information includes an identifier of the tunnel and a first message type of the first message;

Sending, by the DU, the first message according to the indication information:

Embodiment 12. The method of any of Embodiments 9-11,

Sending, by the DU, the first message based on the first message type and the terminal identifier is:

Sending, by the DU, the first message in a cell corresponding to the cell identifier, based on the first message type and the terminal identifier; or

The DU sends the first message according to the first message type and the terminal identifier by using a wireless technology corresponding to the network standard.

Embodiment 13, a method for sending a message, comprising:

The centralized node CU acquires indication information associated with the first message, where the indication information is used to send the first message;

The CU sends the first message and the indication information to a distributed node DU.

Embodiment 14, the method as described in Embodiment 13,

The indication information includes a first message type of the first message, the first message type is a main information block MIB message, or a system information block type-SIB1 message, or a paging paging message, or a minimum system information minimum SI The message, or the system information SI message, or other system information other SI message, the first message type being associated with the first scheduling information of the first message.

The method of embodiment 14, further comprising:

The CU sends the first scheduling information to the DU.

Embodiment 16. The method of Embodiment 14 or 15,

The method further includes:

Sending, by the CU, a second message and a second message type of the second message to the DU, where the second message type is a system information block type-SIB1 message or a minimum system information minimum SI message, the second message The first scheduling information is included.

The method of embodiment 16, further comprising:

The CU receives a second request message from the DU, the second request message including the first message type.

The method of embodiment 18, further comprising:

The CU sends a threshold condition associated with the second request message to the DU.

Embodiment 19. The method of any of embodiments 14-18,

The first scheduling information includes: validity information, or scheduling information, or a scheduling window.

Embodiment 20, the method as described in Embodiment 13,

The indication information includes a first message type of the first message and a terminal identifier, where the first message type is a signaling radio bearer type 1 SRB1 message, or a signaling radio bearer 2 SRB2 message, or a system information SI message, Or other system information other SI message.

Embodiment 21, the method as described in Embodiment 13,

The method further includes:

Receiving, by the CU, a tunnel establishment request message, where the setup request message includes a first message type and a terminal identifier of the first message;

The indication information includes an identifier of the tunnel.

Embodiment 22, the method as described in Embodiment 13,

The method further includes:

Receiving, by the CU, a tunnel establishment request message from the DU, where the setup request message includes a terminal identifier;

The indication information includes an identifier of the tunnel and a first message type of the first message.

Embodiment 23. The method of any of embodiments 20-22,

The indication information further includes: a cell identifier, or a network standard.

Embodiment 24, a node, including a processor, a communication circuit, and a transceiver;

The processor is configured to receive, by the communication circuit, a first message and indication information from a centralized node CU, and send the first message according to the indication information.

Embodiment 25, the node as described in Embodiment 24,

The processor is configured to send the first message by using the first message according to the first message type and the first scheduling information.

Embodiment 26, the node as described in Embodiment 24,

The processor is configured to send the first message by using the first message according to the first message type and the first scheduling information;

The processor is further configured to receive, by the communication circuit, a second message type of the second message and the second message from the CU, where the second message type is a system information block type-SIB1 message or minimum system information. a minimum SI message, the second message including the first scheduling information;

The processor is further configured to send the second message by using the second message type and the second scheduling information associated with the second message type.

Embodiment 27, the node as described in Embodiment 26,

The processor is further configured to receive, by the transceiver, a first request message from one or more terminals, where the A request message includes the first message type;

The processor is further configured to send, by the communication circuit, a second request message to the CU, where the second request message includes the first message type.

Embodiment 28, the node as described in Embodiment 27,

The number of the first request messages meets a threshold condition.

Embodiment 29, the node as described in Embodiment 28,

The processor is further configured to receive the threshold condition from the CU through the communication circuit.

Embodiment 30, the node of any of embodiments 25-29,

The processor is configured to send the first message in a cell corresponding to the cell identifier by using the first message type and the first scheduling information, or based on the first message type and location The first scheduling information is sent by the transceiver by using a wireless technology corresponding to the network standard.

Embodiment 31, the node according to any one of embodiments 25-30,

Embodiment 32, the node as described in Embodiment 24,

The processor is configured to send the first message by using the transceiver according to the first message type and the terminal identifier.

Embodiment 33, the node as described in Embodiment 24,

The processor is further configured to send, by using the communications circuit, a tunnel establishment request message to the CU, where the setup request message includes a first message type and a terminal identifier of the first message;

The indication information includes an identifier of the tunnel;

Embodiment 34, the node as described in Embodiment 24,

The indication information includes an identifier of the tunnel;

Embodiment 35. The node of any of embodiments 32-34,

The processor is configured to send the first message in a cell corresponding to the cell identifier by using the first message type and the terminal identifier, or based on the first message type and the terminal And identifying, by the transceiver, the first message by using a wireless technology corresponding to the network standard.

Embodiment 36, a node, comprising: a processor and a communication circuit;

The processor is configured to acquire indication information associated with the first message, where the indication information is used to send the a message;

The processor sends the first message and the indication information to the distributed node DU through the communication circuit.

Embodiment 37, the node as described in Embodiment 36,

Embodiment 38, the node as described in Embodiment 37,

The processor is further configured to send the first scheduling information to the DU by using the communication circuit.

Embodiment 39. The node as described in Embodiment 36 or 37,

The processor is further configured to send, by the communication circuit, a second message type of the second message and the second message to the DU, where the second message type is a system information block type-SIB1 message or a minimum system information A minimum SI message, the second message including the first scheduling information.

Embodiment 40, the node as described in Embodiment 39,

The processor is further configured to receive, by the communication circuit, a second request message from the DU, the second request message including the first message type.

Embodiment 41, the node as described in Embodiment 40,

The processor is further configured to send, by the communication circuit, a threshold condition associated with the second request message to the DU.

Embodiment 42. The node of any of embodiments 37-41,

Embodiment 43, the node as described in Embodiment 36,

Embodiment 44, the node as described in Embodiment 36,

The processor is further configured to receive, by using the communications circuit, a tunnel establishment request message from the DU, where the setup request message includes a first message type and a terminal identifier of the first message;

The indication information includes an identifier of the tunnel.

Embodiment 45, the node as described in Embodiment 36,

The processor is further configured to receive, by the communication circuit, a setup request message of a tunnel from the Du, where the setup request message includes a terminal identifier;

Embodiment 46. The node of any of embodiments 43-45,

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method can be Other ways to achieve. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit described above is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods described in various embodiments of the present application. Part of the steps. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

A person skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of each functional module described above is exemplified. In practical applications, the above function assignment can be completed by different functional modules as needed, that is, the device is installed. The internal structure is divided into different functional modules to perform all or part of the functions described above. For the specific working process of the device described above, refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

It will be understood by those skilled in the art that the various numbers of the first, second, etc., which are referred to herein, are merely for convenience of description and are not intended to limit the scope of the embodiments of the present application.

It will be understood by those skilled in the art that in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, without The implementation process of the embodiments of the present application should be constituting any limitation.

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

Claims

A method for sending a message, comprising:

The distributed node DU receives the first message and the indication information from the centralized node CU, where the indication information includes the signaling radio bearer SRB identifier and the terminal identifier corresponding to the first message;

The DU sends the first message based on the SRB identifier and the terminal identifier.
The method of claim 1 wherein

The SRB is identified as SRB0, SRB1, SRB2, or SRB3.
The method according to claim 1 or 2, wherein the distributed node DU receives the first message and the indication information from the centralized node CU:

The DU receives the first message and the indication information from the CU through a control plane protocol between the CU and the DU.
The method according to any one of claims 1-3, wherein the first message is a radio resource control RRC message.
A method for sending a message, comprising:

The centralized node CU obtains the indication information associated with the first message, where the indication information is used to send the first message, where the indication information includes a signaling radio bearer SRB identifier and a terminal identifier corresponding to the first message. ;

The CU sends the first message and the indication information to a distributed node DU.
The method of claim 5 wherein:

The SRB is identified as SRB0, SRB1, SRB2, or SRB3.
A method according to claim 5 or claim 6 wherein:

The sending, by the CU, the first message and the indication information to the distributed node DU includes:

The CU sends the first message and the indication information to the DU by using a control plane protocol between the CU and the DU.
A method according to any of claims 5-7, wherein

The first message is a radio resource control RRC message.
A node, comprising: a processor, a communication circuit, and a transceiver; wherein the processor is configured to:

Receiving, by the communication circuit, a first message and indication information from a centralized node CU, where the indication information includes a signaling radio bearer SRB identifier and a terminal identifier of the first message;

Sending the first message based on the SRB identifier and the terminal identifier.
The node of claim 9 wherein:

The SRB is identified as SRB0, SRB1, SRB2, or SRB3.
The node of claim 9 or 10, wherein the processor is configured to:

The first message and the indication information are received from the CU by the communication circuit through a control plane protocol between the CU and the DU.
The node according to any one of claims 9-11, wherein the first message is a radio resource control RRC message.
A node, comprising: a processor and a communication circuit;

The processor is used to:

Acquiring the indication information associated with the first message, where the indication information is used to send the first message, where the indication information includes a signaling radio bearer SRB identifier and a terminal identifier corresponding to the first message;

The first message and the indication information are sent to the distributed node DU through the communication circuit.
The node of claim 13 wherein:

The SRB is identified as SRB0, SRB1, SRB2, or SRB3.
A node according to claim 13 or 14, wherein:

The processor is configured to use the communication circuit to send the first message and the indication information to the DU by using a control plane protocol between a CU and a DU.
A node according to any of claims 13-15, characterized in that

The first message is a radio resource control RRC message.