CN117202107A

CN117202107A - Information transmission method, device and network element

Info

Publication number: CN117202107A
Application number: CN202210579973.XA
Authority: CN
Inventors: 刘爱娟; 周叶; 周锐
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2022-05-25
Filing date: 2022-05-25
Publication date: 2023-12-08

Abstract

The application provides an information transmission method, an information transmission device and a network element, and relates to the technical field of communication. The information transmission method is executed by a first network element and comprises the following steps: transmitting the first information to a second network element; wherein the first information is used for indicating that the multicast broadcast service MBS supported by the first network element and MBS supported by other network elements except the first network element are allowed to use the same radio resource, and the first network element and other network elements except the first network element share the second network element. According to the scheme, resource sharing of broadcast multicast service under a plurality of PLMNs can be realized under the scene of distributed node sharing.

Description

Information transmission method, device and network element

Technical Field

The present application relates to the field of communications technologies, and in particular, to an information transmission method, an information transmission device, and a network element.

Background

In the deployment of current wireless communication systems, to save costs, sharing of wireless network devices between multiple operators may be considered with a separate deployment of the core network. Each core network node of the Public Land Mobile Network (PLMN) and the shared 5G radio access network (NG-RAN) node establish an NG interface, as shown in fig. 1, which is a schematic diagram of the access network nodes of the shared NG-RAN.

The NG-RAN node may share only the DU or may share both the DU and the CU in a scenario where a Central node (CU, may also be referred to as a Central Unit)/a Distributed node (DU, may also be referred to as a Distributed Unit) is separated, as shown in fig. 2, which is a schematic diagram of sharing only the DU.

At present, for NG-RAN nodes, gNB-CU does not share, and how a gNB-DU sharing scene supports resource sharing of broadcast multicast service under a plurality of PLMNs does not have scheme support yet.

Disclosure of Invention

The embodiment of the application provides an information transmission method, an information transmission device and a network element, which are used for solving the problem of how to support resource sharing of broadcast multicast service under a plurality of PLMNs in a gNB-CU sharing scene.

In order to solve the above technical problem, an embodiment of the present application provides an information transmission method, which is executed by a first network element, including:

transmitting the first information to a second network element;

wherein the first information is used for indicating that the multicast broadcast service MBS supported by the first network element and MBS supported by other network elements except the first network element are allowed to use the same radio resource, and the first network element and other network elements except the first network element share the second network element.

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

a first indication, where the first indication is used to indicate that an MBS supported by the first network element and MBS supported by other network elements except the first network element share radio resources;

a second instruction, configured to instruct the second network element to feed back, to a first network element, determined relevant information of MBS supported by the first network element;

the relevant information of the MBS comprises at least one of the following: configuration information of the bearer, mapping information of quality of service QoS flows to multicast radio bearers MRB, and QoS flow information of the MRB.

Optionally, the sending the first information to the second network element includes:

sending an interface message to a second network element;

the interface message carries the first information and/or a service identifier, and the service identifier is associated with the first information.

Optionally, after the sending the first information to the second network element, the method further includes:

and receiving second information sent by a second network element, wherein the second information is related information of MBS supported by other network elements and acquired by the second network element.

Optionally, the method further comprises:

and sending second information to the user plane network element under the condition that the control plane and the user plane are separated.

The embodiment of the application also provides an information transmission method, which is executed by the second network element and comprises the following steps:

receiving first information sent by a first network element, where the first information is used to indicate that multicast broadcast service MBS supported by the first network element and MBS supported by other network elements except the first network element are allowed to use the same radio resource, and the first network element and other network elements except the first network element share the second network element;

and processing the MBS supported by the first network element according to the first information.

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

Optionally, the receiving the first information sent by the first network element includes:

Receiving an interface message sent by a first network element;

Optionally, the processing, according to the first information, the MBS supported by the first network element includes:

and configuring the acquired relevant information of the MBSs supported by other network elements to the MBSs supported by the first network element, and sending second information to the first network element, wherein the second information is the relevant information of the MBSs supported by other network elements acquired by the second network element.

The embodiment of the application also provides a network element, which is a first network element and comprises a memory, a transceiver and a processor:

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

transmitting the first information to the second network element through the transceiver;

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

Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

transmitting an interface message to the second network element via the transceiver;

Optionally, the processor is configured to read the computer program in the memory and further perform the following operations:

and receiving second information sent by a second network element through a transceiver, wherein the second information is related information of MBS supported by other network elements and acquired by the second network element.

and sending second information to the user plane network element under the condition that the control plane and the user plane are separated through the transceiver.

The embodiment of the application also provides a network element, which is a second network element and comprises a memory, a transceiver and a processor:

receiving, by a transceiver, first information sent by a first network element, where the first information is used to indicate that a multicast broadcast service MBS supported by the first network element is allowed to use the same radio resource as MBS supported by other network elements except the first network element, and the first network element shares the second network element with the other network elements except the first network element;

receiving an interface message sent by a first network element through a transceiver;

Optionally, the processor is configured to read the computer program in the memory to perform the following operations:

and configuring the acquired relevant information of the MBSs supported by other network elements to the MBSs supported by the first network element, and sending second information to the first network element through a transceiver, wherein the second information is the relevant information of the MBSs supported by other network elements acquired by the second network element.

The embodiment of the application also provides an information transmission device, which is applied to the first network element and comprises:

a first sending unit, configured to send first information to a second network element;

The embodiment of the application also provides an information transmission device, which is applied to a second network element and comprises:

a first receiving unit, configured to receive first information sent by a first network element, where the first information is used to indicate that a multicast broadcast service MBS supported by the first network element is allowed to use the same radio resource as MBS supported by other network elements except the first network element, and the first network element shares the second network element with other network elements except the first network element;

And the processing unit is used for processing the MBS supported by the first network element according to the first information.

The embodiment of the application also provides a processor-readable storage medium, which stores a computer program for causing the processor to execute the method.

The beneficial effects of the application are as follows:

according to the scheme, the first information indicating that the multicast and broadcast service MBS supported by the first network element and MBS supported by other network elements except the first network element are allowed to use the same wireless resources is sent to the distribution node, so that resource sharing of the broadcast and multicast service under a plurality of PLMNs in a scene of sharing of the distribution node is realized.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.

Figure 1 shows a schematic diagram of an access network node sharing an NG-RAN;

Fig. 2 shows a schematic diagram of sharing only DUs;

FIG. 3 is a schematic flow chart of an information transmission method according to an embodiment of the application;

FIG. 4 is a flow chart of the first application case;

FIG. 5 is a flow chart of the second application case;

FIG. 6 shows a schematic flow diagram of application case three;

FIG. 7 is a flow chart of the fourth application case;

fig. 8 shows one of unit diagrams of an information transmission device according to an embodiment of the present application;

fig. 9 shows a block diagram of a network element according to an embodiment of the present application;

FIG. 10 is a second flow chart of an information transmission method according to an embodiment of the application;

fig. 11 shows a second unit diagram of an information transmission device according to an embodiment of the application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to implement embodiments of the application described herein, such as in a sequence other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the embodiment of the application, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.

In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Embodiments of the present application are described below with reference to the accompanying drawings. The information transmission method, the information transmission device and the network element provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a system employing a fifth generation (5th Generation,5G) mobile communication technology (hereinafter, simply referred to as a 5G system), and it will be understood by those skilled in the art that the 5G NR system is only an example and not a limitation.

Firstly, based on the technical scheme provided by the application, partial technical terms possibly related to the technical scheme are introduced.

In the 5G network architecture, the parts closely related to the air interface are as follows (taking 5G/NR as an example):

in NR and similar systems, a logical radio access network node (RAN node) may be further divided into a Control Plane center node (CU-CP), one or more User Plane center nodes (CU-UP), and one or more Distributed Units (DU), which is called "CU-CP/UP split (CU-CP/UP split)". The CU-CP and DU are connected by F1-C or the like, and the CU-CP and CU-UP are connected by E1 or the like. The control plane connection of the RAN node with the core network/other NG-RAN nodes ends at CU-CP, the user plane connection ends at CU-UP, and the air interface connection of the RAN node with the mobile terminal ends at DU.

The gNB-CU-CP refers to the Control Plane part of the Central node (Central Unit) in the gNB, which is the most Central module in the gNB, and is connected to the access and mobility management function AMF via an N2 interface (also called NG-C interface for this case, i.e. the Control Plane part in the NG interface). Two adjacent gNBs are connected through an Xn interface. Each UE may be connected to multiple gNB-CU-CPs at the same time, but only one of them is the primary gNB-CU-CP, with an N2 context associated with the UE between itself and the AMF. Different gNB-CU-CPs are connected through an Xn-C interface. The gNB-CU-CP maps one or more quality of service (QoS) flows in each session to one radio bearer for air interface transmission according to its own policy. The gNB-CU-CP is also responsible for sending RRC (radio resource control ) messages to the UE to indicate how it configures the air interface link. These RRC messages are sent and received through the PDCP (packet data convergence protocol) layer Protocol Data Unit.

gNB-CU-UP refers to the User Plane (User Plane) section among Central Unit among gNB. The gNB-CU-CP manages the gNB-CU-UP through an E1 interface, for example, requests the gNB-CU-UP to establish, modify and release a transmission channel of service data. In principle, gNB-CU-UP interacts traffic data with UPF via N3 interface north and gNB-DU via F1-U interface south.

gNB-DU refers to Distributed nodes (Distributed units) among gNB. gNB-CU-CP manages gNB-DU through F1-C interface, for example, requests gNB-DU to build, modify and release air interface resource. The gNB-DU mainly includes RLC (Radio Link control ), MAC (Medium Access control, media Access Control), PHY (Physical) and RF (Radio Frequency) layers.

Based on analysis, the embodiment of the application provides an information transmission method, an information transmission device and a network element, which are used for solving the problem of how to support resource sharing of broadcast multicast service under a plurality of PLMNs in a gNB-CU sharing scene.

The method and the device are based on the same application, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.

As shown in fig. 3, an embodiment of the present application provides an information transmission method, which is executed by a first network element, and includes:

step S301, first information is sent to a second network element;

wherein the first information is used for indicating that Multicast Broadcast Service (MBS) supported by a first network element is allowed to use the same radio resource as MBS supported by other network elements except the first network element, and the first network element shares the second network element with other network elements except the first network element.

It should be noted that the Public Land Mobile Network (PLMN) to which the first network element is connected is different from the Public Land Mobile Network (PLMN) to which the other network elements are connected, that is, services issued by different PLMNs may be transmitted by using the same radio resource in the second network element.

Optionally, in at least one embodiment of the present application, the first information includes at least one of:

a11, a first instruction, wherein the first instruction is used for instructing the MBS supported by the first network element to share wireless resources with the MBS supported by other network elements except the first network element;

wherein, the MBS supported by the first network element and the MBS supported by other network elements may be the same MBS or different MBS.

In this case, the first network element indicates to the second network element that the MBS supported by the first network element allows radio resource sharing with MBS supported by other network elements, so that the second network element can realize resource sharing of broadcast or multicast service under multiple PLMNs.

A12, a second instruction, wherein the second instruction is used for instructing the second network element to feed back the determined relevant information of the MBS supported by the first network element to the first network element;

it should be noted that, in the embodiment of the present application, the relevant information of the MBS includes at least one of the following: configuration information of bearers, mapping information of quality of service (QoS) flows to Multicast Radio Bearers (MRBs), and QoS flow information of the MRBs.

The situation can be understood that the relevant information of the MBS supported by the first network element may be updated, for example, when the relevant information of the MBS includes the configuration information of the bearer, that is, the configuration information of the bearer of the MBS supported by the first network element may be updated; for example, when the relevant information of the MBS includes mapping information of QoS flows to MRBs, that is, the mapping information of QoS flows to MRBs of the MBS supported by the first network element may be updated; for example, when the related information of the MBS includes QoS flow information of the MRB, that is, the QoS flow information of the MRB of the MBS supported by the first network element may be updated.

Optionally, the configuration information of the bearer may include at least one of:

packet Data Convergence Protocol (PDCP) configuration information;

service Data Adaptation Protocol (SDAP) configuration information.

In this case, the first network element indicates to the second network element that the second network element is allowed to feed back the related information of the MBS supported by the first network element to the first network element, that is, the related information of the MBS transmitted by other network elements can be used to update the related information of the MBS of the first network element, so that the second network element can also realize resource sharing of broadcast or multicast service under multiple PLMNs.

It should be noted that, the first network element may send a11 only to the second network element, in which case, the second network element does not need to inform the first network element of at least one of configuration information of a bearer used by the first network element when actually transmitting, mapping information of QoS flow to MRB, and QoS flow information of MRB; the first network element may only send a12 to the second network element, in which case, the second network element knows that the MBS supported by the first network element needs to share resources with MBS supported by other network elements after receiving the first information sent by the first network element, and at the same time, the first network element also needs to know at least one of configuration information of a bearer used by the first network element when actually transmitting, mapping information of QoS flow to MRB, and QoS flow information of MRB; the first network element may also send a11 and a12 to the second network element at the same time, in which case the second network element also needs to inform the first network element of at least one of configuration information of bearers used by the first network element when actually transmitting, mapping information of QoS flows to MRB, and QoS flow information of MRB.

It should be noted that, in the embodiment of the present application, the second network element refers to a distribution node (DU) at the access network side, for example, a gNB-DU. Because the control plane and the user plane of the central node at the access network side can be separated or not, when the control plane and the user plane of the central node at the access network side are not separated, the first network element is the central node at the access network side, and when the control plane and the user plane of the central node at the access network side are separated, the first network element is the central node of the control plane.

Optionally, in at least one embodiment of the present application, an optional implementation manner of this step S301 is:

sending an interface message to a second network element;

It should be noted that, the interface message sent by the first network element may directly carry the first information, or the interface message may not carry the first information, but may carry a service identifier associated with the first information, and when the second network element knows the service identifier, the content of the first information may be inferred according to the service identifier. For example, when the first information indicates a11, and when the identifier carried in the interface message received by the second network element is the identifier of the service a, the second network element may determine, based on the service a, that the service supported by the first network element may perform radio resource sharing with the service a. For example, when the first information indicates a12, when the identifier carried in the interface message received by the second network element is the identifier of the service B, the second network element may determine, based on the service B, that the second network element needs to feed back the relevant information of the service B to the first network element.

Optionally, in at least one embodiment of the present application, after the sending the first information to the second network element, the method further includes:

That is, in the case that the first network element indicates that the second network element needs to feed back the related information of the MBS supported by the first network element to the first network element, the second network element may configure the acquired related information of MBS supported by other network elements to the MBS supported by the first network element, and send the related information to the first network element. For example, the second network element may send the relevant information to the first network element in case the relevant information of the MBS is updated. For example, if the first network element indicates that the second network element needs to feed back the configuration information of the MBS supported by the first network element to the first network element, the second network element sends PDCP configuration information and/or SDAP configuration information of the MBS to the first network element under the condition that the configuration information of the MBS supported by the first network element changes; for example, if the first network element indicates that the second network element needs to feed back the mapping information of the QoS flow of the MBS supported by the first network element to the MRB to the first network element, the second network element sends the mapping information of the QoS flow of the MBS to the MRB to the first network element under the condition that the mapping information of the QoS flow of the MBS to the MRB changes; for example, if the first network element indicates that the second network element needs to feed back the QoS flow information of the MRB of the MBS supported by the first network element to the first network element, the second network element sends the QoS flow information of the MRB of the MBS to the first network element in the case that the QoS flow information of the MRB of the MBS changes. It should be further noted that, if the first information sent by the first network element only indicates that the MBS supported by the first network element is allowed to share radio resources with MBS supported by other network elements except the first network element, in general, the second network element does not send the MBS related information to the first network element even if the MBS related information is updated.

Optionally, in at least one embodiment of the present application, the method further includes:

The situation is generally applicable to the situation that the control plane and the user plane of the central node at the access network side are separated, namely, the first network element is the control plane central node, and the user plane network element is the user plane central node; when the control plane and the user plane are separated, the channel for actually carrying out data transmission should be maintained by the user plane central node, and the control plane central node needs to send the information to the user plane central node again after acquiring the relevant information of the MBS.

It should be further noted that, before the second network element sends the second information to the first network element, the second network element should generally acquire relevant information of the MBS, where the relevant information of the service MBS is generally sent by other network elements, and optionally, in at least one embodiment of the present application, the second network element receives third information sent by a third network element;

determining the second information according to the third information;

wherein the third information includes:

d11, carrying PDCP configuration information;

d12, carrying SDAP configuration information;

D13, mapping information of QoS flow to MRB;

d14, qoS information of MRB.

It should be noted that the third network element is different from the PLMN to which the first network element belongs. When the control plane and the user plane of the central node at the access network side are not separated, the third network element is the central node at the access network side, and when the control plane and the user plane of the central node at the access network side are separated, the third network element is the central node of the control plane.

Embodiments of the present application are illustrated below in specific applications.

Firstly, the central node of the access network side is denoted as gNB-CU, the central node of the control plane of the access network side is denoted as gNB-CU-CP, the central node of the user plane of the access network side is denoted as gNB-CU-UP, and the distribution node of the access network side is denoted as gNB-DU.

Application one, PLMN1 and PLMN2 share gNB-DU, gNB-CU does not share, PLMN1 and PLMN2 both support the same broadcast service.

The specific implementation flow is shown in fig. 4, and mainly comprises:

step S101, the gNB-CU1 sends a broadcast context setup request (broadcast Context Setup Request) message to the shared gNB-DU requesting to set up a context for the broadcast service identified as TMGI 1.

In the broadcast context setup request message, the CU informs that the service identified as TMGI1 and the service identified as TMGI2 under DU PLMN1 are the same service under different PLMNs, and can use the same radio resource. The message may carry the configuration of the SDAP layer.

Step S102, after receiving the broadcast context establishment request message, the gNB-DU finds that the DU has not saved the context of the broadcast service corresponding to TMGI1, saves the configuration information sent by the gNB-CU1, and replies a broadcast context establishment response (broadcast Context Setup Response) message to the CU to indicate that the broadcast-related context establishment is successful.

Step S103, gNB-DU broadcasts the broadcast service which is supported by itself and identified as TMGI1 through the system message, and UE under PLMN1 monitors the broadcast service under the cell.

Step S104, the gNB-CU2-CP sends a broadcast bearer context establishment request (broadcast bear context setup Request) message to the gNB-CU2-UP, wherein the broadcast bearer context establishment request is used for requesting the gNB-CU2-UP to establish the context of a broadcast service MRB;

step S105, gNB-CU2-UP sends a broadcast bearer context setup response (broadcast bear context setup Response) message to gNB-CU 2-CP.

Step S106, the gNB-CU2-CP sends broadcast Context Setup Request a message to the shared gNB-DU requesting to establish a context for the broadcast service identified as TMGI 2. In this message, the CU informs that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and the same radio resource can be used. The message may carry the configuration of the SDAP layer.

After receiving the message, the gNB-DU discovers that the context of the broadcast service identified as TMGI1 is already saved, and does not need to establish a new context for the broadcast service of TMGI 2. The gNB-DU further checks configuration information (such as SDAP configuration and PDCP configuration) sent by the gNB-CU2-CP, mapping information of QoS flow to MRB and the like, and if the configuration information is inconsistent with the current DU, the gNB-DU carries the configuration information of the service stored by the DU in a broadcast Context Setup response message sent to the gNB-CU 2-CP.

Step S108, the gNB-CU2-CP sends configuration information (e.g., SDAP configuration, PDCP configuration) of the MRB received from the gNB-DU to the gNB-CU2-UP, the mapping of QoS flows to the MRB, qoS information of the MRB, etc., e.g., the configuration information (e.g., SDAP configuration, PDCP configuration) of the MRB from the update of gNB-DU may be carried by the broadcast bearer context update request (broadcast Bear context modification Request), the mapping of QoS flows to the MRB, qoS information of the MRB, etc.

Step S109, gNB-CU2-UP replies a response message to gNB-CU 2-CP.

Step S110, gNB-DU broadcasts the broadcast service which supports the TMGI1 and the TMGI2 through the system message and corresponds to the same MCCH and the MTCH. The UEs under PLMN1 and PLMN2 monitor the broadcast service on the same resource block.

Application two, PLMN1 and PLMN2 share gNB-DU, gNB-CU does not share, PLMN1 and PLMN2 both support the same multicast service.

The specific implementation flow is shown in fig. 5, and mainly comprises:

step S201, the gNB-CU1 sends a multicast context setup request (multicast Context Setup Request) message to the shared gNB-DU requesting to set up a context for the multicast service identified as TMGI 1.

In the multicast context establishment request message, the CU informs that the service identified as TMGI1 and the service identified as TMGI2 under the DU PLMN1 are the same service under different PLMNs, and can use the same radio resource. The message may carry the configuration of the SDAP layer

Step S202, after receiving the multicast context establishment request message, the gNB-DU finds that the DU has not saved the context of the multicast service corresponding to TMGI1, saves the configuration information sent by the gNB-CU1, and replies a multicast context establishment response (multicast Context Setup Response) message to the CU.

Step S203, the gNB-DU provides the multicast service for the UE under PLMN1 on the radio resource corresponding to the TMGI1 multicast service.

Step S204, the gNB-CU2-CP sends a multicast bearer context establishment request (multicast bear context setup Request) message to the gNB-CU2-UP, wherein the multicast bearer context establishment request is used for requesting the gNB-CU2-UP to establish the context of the multicast service MRB;

Step S205, gNB-CU2-UP sends a multicast bearer context setup response (multicast bear context setup Response) message to gNB-CU 2-CP.

Step S206, the gNB-CU2-CP sends multicast Context Setup Request a message to the shared gNB-DU requesting to establish a context for the multicast service identified as TMGI 2. In this message, the CU informs that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and the same radio resource can be used. The message may carry the configuration of the SDAP layer.

After receiving the message, the gNB-DU discovers that the context of the multicast service identified as TMGI1 is already saved, and does not need to establish a new context for the multicast service of TMGI 2. The gNB-DU further checks configuration information (such as SDAP configuration and PDCP configuration) sent by the gNB-CU2-CP, mapping information of QoS flow to MRB and the like, and if the configuration information is inconsistent with the current DU, the gNB-DU carries the configuration information of the service stored by the DU in a multicast Context Setup response message sent to the gNB-CU 2-CP.

Step S208, the gNB-CU2-CP sends configuration information (e.g., SDAP configuration, PDCP configuration) of the MRB received from the gNB-DU to the gNB-CU2-UP, the mapping of QoS flows to the MRB, and QoS information of the MRB, etc., which may be carried with the updated configuration information (e.g., SDAP configuration, PDCP configuration) of the MRB from the gNB-DU by broadcasting a bearer context update request (broadcast Bear context modification Request).

Step S209, gNB-CU2-UP replies a response message to gNB-CU 2-CP.

Step S210, the gNB-DU sends the same multicast service (TMGI 1 in PLMN1 and TMGI2 in PLMN 2) on the same resource for the UEs of PLMN1 and PLMN 2.

Application case three, PLMN1 and PLMN2 share gNB-DU, gNB-CU does not share, PLMN1 and PLMN2 support the same broadcast service.

The specific implementation flow is shown in fig. 6, and mainly comprises the following steps:

step S301, the gNB-CU1 sends a broadcast context setup request (broadcast Context Setup Request) message to the shared gNB-DU requesting to set up a context for the broadcast service identified as TMGI 1.

In the broadcast context establishment request message, the CU informs that the service identified as TMGI1 and the service identified as TMGI2 under DU PLMN1 are the same service under different PLMNs, and the configuration information of the service under gNB-CU1 is updatable. The message may carry the configuration of the SDAP layer.

Step S302-step S305, step S102-step S105 in the same application case.

Step S306, the gNB-CU2-CP sends broadcast Context Setup Request a message to the shared gNB-DU requesting to establish a context for the broadcast service identified as TMGI 2. In this message, the CU informs that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and that the configuration information of the service under the gNB-CU2 can be updated. The message may carry the configuration of the SDAP layer.

Step S307 to step S310, and step S107 to step S110 in the same application case.

Application case four, PLMN1 and PLMN2 share gNB-DU, gNB-CU is not shared, and PLMN1 and PLMN2 support the same multicast service.

The specific implementation flow is shown in fig. 7, and mainly comprises:

step S401, gNB-CU1 sends a multicast context setup request (multicast Context Setup Request) message to the shared gNB-DU requesting to set up a context for the multicast service identified as TMGI 1.

In the multicast context establishment request message, the CU informs the DU PLMN1 whether the service identified as TMGI1 and the service identified as TMGI2 are the same service under different PLMNs, and whether the configuration information of the service under the gNB-CU1 can be updated. The message may carry the configuration of the SDAP layer.

Step S402 to step S405, step S202 to step S205 in the same application case two.

Step S406, the gNB-CU2-CP sends multicast Context Setup Request a message to the shared gNB-DU requesting to establish a context for the multicast service identified as TMGI 2. In this message, the CU informs that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and that the configuration information of the service under the gNB-CU2 can be updated. The message may carry the configuration of the SDAP layer.

Step S407 to step S410, and step S207 to step S210 in the same application case two.

Application case five, PLMN1 and PLMN2 share gNB-DU, gNB-CU does not share, PLMN1 and PLMN2 support the same broadcast service.

The main difference between the application case and the application case three is that in step S301 and step S306, the gNB-CU1 and the gNB-CU2 inform that the mapping information of the QoS flow of the service under the gNB-DU to the MRB can be updated. The other steps are the same as the third application case.

Application case six, sharing gNB-DU by PLMN1 and PLMN2, sharing not gNB-CU, and supporting the same multicast service by PLMN1 and PLMN2

The main difference between the application case and the application case four is that in step S401 and step S406, the gNB-CU1 and the gNB-CU2 inform that the mapping information of the QoS flow of the service under the gNB-DU to the MRB can be updated. The other steps are the same as the application case four.

At least one embodiment of the present application decides by the gNB-CU whether to share radio resources of the same broadcast/multicast service with other PLMNs, whether to allow DUs to update at least one of mapping information of QoS flows to MRBs, whether to allow modification of configuration information of bearers, whether to allow updating of QoS flow information of MRBs, and informs the gNB-DUs in case that the NG-RAN is a CU/DU split architecture and the gNB-CU does not share gNB-DU sharing; after receiving the notification of the gNB-CU, the gNB-DU can feed back at least one of updated configuration information, mapping information from QoS flow to MRB and QoS flow information of MRB to the gNB-CU-CP which allows sharing radio resources of broadcast/multicast service with other PLMNs; the gNB-CU-CP further provides at least one of mapping information of updated configuration information QoS flows to MRB and QoS flow information of MRB to the gNB-CU-UP; therefore, the implementation can support the same service of different PLMNs in the RAN sharing scene to use the same wireless resource, thereby optimizing the system efficiency.

The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G system. For example, suitable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (general packet Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR), and the like. Terminal devices and network devices are included in these various systems. Core network parts such as evolved packet system (Evolved Packet System, EPS), 5G system (5 GS) etc. may also be included in the system.

As shown in fig. 8, an embodiment of the present application provides an information transmission apparatus 800, which is applied to a first network element, and includes:

A first sending unit 801, configured to send first information to a second network element;

The first information includes one or more of the following:

Optionally, the first sending unit 801 is configured to:

sending an interface message to a second network element;

Optionally, after the first sending unit 801 sends the first information to the second network element, the method further includes:

and the second receiving unit is used for receiving second information sent by a second network element, wherein the second information is related information of MBS supported by other network elements and acquired by the second network element.

Optionally, the apparatus further comprises:

and the second sending unit is used for sending second information to the user plane network element under the condition that the control plane and the user plane are separated.

It should be noted that, the embodiment of the device is a device corresponding to the embodiment of the method, and all the implementation manners in the embodiment of the method are applicable to the embodiment of the device, so that the same technical effects can be achieved.

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

As shown in fig. 9, the embodiment of the present application further provides a network element, where the network element is a first network element, and includes a processor 900, a transceiver 910, a memory 920, and a program stored in the memory 920 and executable on the processor 900; the transceiver 910 is connected to the processor 900 and the memory 920 through a bus interface, where the processor 900 is configured to read a program in the memory, and perform the following procedures:

Transmitting the first information to the second network element through the transceiver 910;

A transceiver 910 for receiving and transmitting data under the control of the processor 900.

Wherein in fig. 9, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 900 and various circuits of memory represented by memory 920, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 910 may be a number of elements, i.e., include a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, etc.

The processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 900 in performing operations.

Alternatively, the processor 900 may be a CPU (central processing unit), ASIC (Application Specific Integrated Circuit ), FPGA (Field-Programmable Gate Array, field programmable gate array) or CPLD (Complex Programmable Logic Device ), and the processor may also employ a multi-core architecture.

The processor is operable to perform any of the methods provided by embodiments of the present application in accordance with the obtained executable instructions by invoking a computer program stored in a memory. The processor and the memory may also be physically separate.

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

transmitting an interface message to the second network element via the transceiver 910;

and receiving, by the transceiver 910, second information sent by a second network element, where the second information is related information of MBS supported by other network elements acquired by the second network element.

the second information is sent to the user plane network element by the transceiver 910 with the control plane and the user plane separated.

At least one embodiment of the present application further provides a network element, where the network element is a first network element, and includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements each process in the information transmission method embodiment applied to the first network element when executing the program, and the process can achieve the same technical effect, so that repetition is avoided and no further description is given here.

At least one embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the program when executed by a processor implements each process in the embodiment of the information transmission method applied to the first network element as described above, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

Corresponding to the implementation of the first network element side, as shown in fig. 10, an embodiment of the present application provides an information transmission method, which is executed by the second network element, and includes:

step S1001, receiving first information sent by a first network element, where the first information is used to indicate that a multicast broadcast service MBS supported by the first network element is allowed to use the same radio resource as MBS supported by other network elements except the first network element, and the first network element shares the second network element with other network elements except the first network element;

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

receiving an interface message sent by a first network element;

Optionally, before the sending the second information to the first network element, the method further includes:

receiving third information sent by a third network element;

determining the second information according to the third information;

wherein the third information includes at least one of:

PDCP configuration information carried;

SDAP configuration information carried by the carrier;

mapping information of QoS flows to MRB;

QoS information of MRB.

It should be noted that, all the descriptions in the above embodiments are applicable to the embodiment of the information transmission method applied to the second network element side, and the same technical effects as the above embodiments can be achieved.

As shown in fig. 11, an embodiment of the present application further provides an information transmission apparatus 1100, applied to a first network element, including:

a first receiving unit 1101, configured to receive first information sent by a first network element, where the first information is used to indicate that a multicast broadcast service MBS supported by the first network element is allowed to use the same radio resource as MBS supported by other network elements except the first network element, and the first network element shares the second network element with other network elements except the first network element;

and a processing unit 1102, configured to process an MBS supported by the first network element according to the first information.

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

Optionally, the first receiving unit 1101 is configured to:

receiving an interface message sent by a first network element;

Optionally, the processing unit 1102 is configured to:

It should be noted that, the device provided in the embodiment of the present application is a device capable of executing the above information transmission method, and all embodiments of the above information transmission method are applicable to the device embodiment, and the same or similar beneficial effects can be achieved.

The embodiment of the present application further provides a network element, where the network element is a second network element, specifically, the structure of the second network element is similar to that of the first network element shown in fig. 9, and will not be described herein.

Wherein the processor is configured to read the program in the memory, and execute the following procedure:

Optionally, the first information includes one or more of:

It should be noted that, the network element provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and the parts and beneficial effects that are the same as those of the method embodiment in the embodiment are not described in detail herein.

At least one embodiment of the present application further provides a network element, where the network element is a second network element, and includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements each process in the information transmission method embodiment applied to the second network element when executing the program, and the process can achieve the same technical effect, so that repetition is avoided and no further description is given here.

The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, wherein the computer program, when being executed by a processor, realizes the steps of the information transmission method applied to the second network element. The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), and the like.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. An information transmission method, performed by a first network element, comprising:

transmitting the first information to a second network element;

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

3. The method of claim 1, wherein the sending the first information to the second network element comprises:

sending an interface message to a second network element;

4. The method according to claim 1 or 2, characterized in that the method further comprises:

5. The method as recited in claim 4, further comprising:

6. An information transmission method, performed by a second network element, comprising:

7. The method of claim 6, wherein the first information comprises one or more of:

8. The method of claim 6, wherein the receiving the first information sent by the first network element comprises:

receiving an interface message sent by a first network element;

9. The method according to claim 6 or 7, wherein the processing the MBS supported by the first network element according to the first information comprises:

10. A network element, the network element being a first network element, comprising a memory, a transceiver, and a processor:

11. The network element of claim 10, wherein the first information comprises one or more of:

12. The network element of claim 10, wherein the processor is configured to read the computer program in the memory and perform the following:

13. The network element of claim 10 or 11, wherein the processor is configured to read the computer program in the memory to further perform the following:

14. The network element of claim 13, wherein the processor is configured to read the computer program in the memory to further:

15. A network element, the network element being a second network element, comprising a memory, a transceiver, and a processor:

16. The network element of claim 15, wherein the processor is configured to read the computer program in the memory and perform the following:

17. The network element of claim 15, wherein the processor is configured to read the computer program in the memory to:

18. An information transmission device, applied to a first network element, comprising:

19. An information transmission device, applied to a second network element, comprising:

20. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to perform the method of any one of claims 1 to 9.