Information transmission method, apparatus and network element

By facilitating information exchange between the first and second network elements in a scenario where gNB-CU is not shared but gNB-DU is shared, the problem of sharing broadcast and multicast service resources under multiple PLMNs is solved, achieving efficient resource utilization and improved system efficiency.

CN117202107BActive Publication Date: 2026-07-03DATANG MOBILE COMM EQUIP CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
DATANG MOBILE COMM EQUIP CO LTD
Filing Date
2022-05-25
Publication Date
2026-07-03

Smart Images

  • Figure CN117202107B_ABST
    Figure CN117202107B_ABST
Patent Text Reader

Abstract

This application provides an information transmission method, apparatus, and network element, relating to the field of communication technology. The information transmission method, executed by a first network element, includes: sending first information to a second network element; wherein the first information is used to instruct that multicast broadcast services (MBS) supported by the first network element are allowed to use the same radio resources as MBS supported by other network elements besides the first network element, and the first network element shares the second network element with the other network elements besides the first network element. This solution enables resource sharing for broadcast multicast services under multiple PLMNs in a distributed node sharing scenario.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an information transmission method, apparatus and network element. Background Technology

[0002] In current wireless communication system deployments, to save costs, multiple operators consider sharing wireless network equipment even with separate core network deployments. Each Public Land Mobile Network (PLMN) core network node and the shared 5G Radio Access Network (NG-RAN) node establish an NG interface, such as... Figure 1 The diagram shows a shared NG-RAN access network node.

[0003] In NG-RAN scenarios where the Central Unit (CU) and Distributed Unit (DU) are separate, nodes can share only the DU, or they can share both the DU and the CU. Figure 2 The diagram shown is for a shared DU only.

[0004] Currently, there is no solution to support resource sharing for broadcast multicast services under multiple PLMNs in scenarios where gNB-CU is not shared but gNB-DU is shared in NG-RAN nodes. Summary of the Invention

[0005] This application provides an information transmission method, apparatus, and network element to address the problem of resource sharing for broadcast multicast services under multiple PLMNs in scenarios where gNB-CUs are not shared but gNB-DUs are shared.

[0006] To address the aforementioned technical problems, embodiments of this application provide an information transmission method, executed by a first network element, comprising:

[0007] Send the first message to the second network element;

[0008] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

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

[0010] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0011] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0012] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0014] Send interface messages to the second network element;

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

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

[0017] The second information is received from the second network element, which is the relevant information of MBS supported by other network elements obtained by the second network element.

[0018] Optionally, the method further includes:

[0019] In the case of separation between the control plane and the user plane, a second message is sent to the user plane network element.

[0020] This application embodiment also provides an information transmission method, executed by a second network element, including:

[0021] The first information sent by the first network element is received, the first information being used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element, and the first network element shares the second network element with other network elements other than the first network element.

[0022] Based on the first information, the MBS supported by the first network element is processed.

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

[0024] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0025] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0026] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0028] Receive interface messages sent by the first network element;

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

[0030] Optionally, processing the MBS supported by the first network element based on the first information includes:

[0031] Configure the relevant information of MBS supported by other network elements to the MBS supported by the first network element, and send the second information to the first network element. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

[0032] This application embodiment also provides a network element, which is a first network element, including a memory, a transceiver, and a processor:

[0033] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0034] The first information is sent to the second network element via the transceiver;

[0035] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

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

[0037] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0038] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0039] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0041] Send interface messages to the second network element via transceiver;

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

[0043] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0044] The transceiver receives second information sent by the second network element, which is information about MBS supported by other network elements obtained by the second network element.

[0045] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0046] The second information is sent to the user plane network element through the transceiver when the control plane and user plane are separated.

[0047] This application embodiment also provides a network element, which is a second network element, including a memory, a transceiver, and a processor:

[0048] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0049] The transceiver receives first information sent by the first network element. The first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element. The first network element shares the second network element with other network elements other than the first network element.

[0050] Based on the first information, the MBS supported by the first network element is processed.

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

[0052] Receive interface messages sent by the first network element through the transceiver;

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

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

[0055] The relevant information of MBS supported by other network elements is configured to the MBS supported by the first network element, and the second information is sent to the first network element through the transceiver. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

[0056] This application embodiment also provides an information transmission device applied to a first network element, including:

[0057] The first transmitting unit is used to transmit the first information to the second network element;

[0058] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

[0059] This application embodiment also provides an information transmission device applied to a second network element, including:

[0060] The first receiving unit is configured to receive first information sent by the first network element. The first information is configured to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element. The first network element shares the second network element with other network elements other than the first network element.

[0061] The processing unit is used to process the MBS supported by the first network element according to the first information.

[0062] This application also provides a processor-readable storage medium storing a computer program for causing the processor to perform the above-described method.

[0063] The beneficial effects of this application are:

[0064] The above scheme achieves resource sharing for broadcast multicast services under multiple PLMNs in a scenario where distributed nodes share resources by sending first information to the distributed nodes indicating that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements besides the first network element. Attached Figure Description

[0065] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0066] Figure 1 A schematic diagram showing access network nodes sharing NG-RAN;

[0067] Figure 2 A diagram illustrating that only DU is shared;

[0068] Figure 3 One of the flowcharts illustrating an embodiment of the information transmission method of this application;

[0069] Figure 4 A flowchart illustrating application scenario one;

[0070] Figure 5 A flowchart illustrating application scenario two;

[0071] Figure 6 A flowchart illustrating application scenario three;

[0072] Figure 7 A flowchart illustrating application scenario four;

[0073] Figure 8 One of the unit schematic diagrams of the information transmission device according to an embodiment of this application;

[0074] Figure 9 This is a structural diagram of a network element in an embodiment of this application;

[0075] Figure 10 A second flowchart illustrating the information transmission method according to an embodiment of this application;

[0076] Figure 11 This is a second schematic diagram of an information transmission device according to an embodiment of this application. Detailed Implementation

[0077] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0078] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the application described herein may be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0079] In this application's embodiments, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. In this application's embodiments, the term "multiple" refers to two or more, and other quantifiers are similar.

[0080] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0081] The embodiments of this application are described below with reference to the accompanying drawings. The information transmission method, apparatus, and network element provided in the embodiments of this application can be applied to wireless communication systems. The wireless communication system can be a system using fifth-generation (5G) mobile communication technology (hereinafter referred to as a 5G system). Those skilled in the art will understand that the 5G NR system is merely an example and not a limitation.

[0082] First, based on the technical solution provided in this application, some technical terms that may be involved will be introduced.

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

[0084] In NR and similar systems, a logical Radio Access Network (RAN) node can be further divided into a Central Unit-Control Plane (CU-CP), one or more Central Unit-User Planes (CU-UP), and one or more Distributed Units (DU). This structure is called "CU-CP / UP split". The CU-CP and DU are connected via an F1-C or similar interface, while the CU-CP and CU-UP are connected via an E1 or similar interface. The control plane connection between the RAN node and the core network / other NG-RAN nodes terminates at the CU-CP, the user plane connection terminates at the CU-UP, and the air interface connection between the RAN node and the mobile terminal terminates at the DU.

[0085] gNB-CU-CP refers to the control plane portion of the central unit within a gNB, and is the core module of the gNB. It connects to the Access and Mobility Management Function (AMF) via the N2 interface (also known as the NG-C interface, i.e., the control plane portion of the NG interface). Two adjacent gNBs are connected via the Xn interface. Each UE can connect to multiple gNB-CU-CPs simultaneously, but only one is the primary gNB-CU-CP, which maintains an N2 context related to that UE with the AMF. Different gNB-CU-CPs are connected via the Xn-C interface. Based on its own policies, the gNB-CU-CP maps one or more Quality of Service (QoS) streams in each session to a radio bearer for air interface transmission. The gNB-CU-CP is also responsible for sending RRC (Radio Resource Control) messages to the UE to instruct it on how to configure the air interface link. These RRC messages are sent and received through the PDCP (Protocol Data Unit) layer.

[0086] gNB-CU-UP refers to the User Plane portion of the Central Unit within a gNB. gNB-CU-CP manages gNB-CU-UP through the E1 interface, for example, requesting gNB-CU-UP to establish, modify, and release transmission channels for service data. In principle, gNB-CU-UP interacts with the UPF northbound via the N3 interface and with the gNB-DU southbound via the F1-U interface.

[0087] gNB-DU refers to the distributed unit within a gNB. The gNB-CU-CP manages the gNB-DU through the F1-C interface, for example, requesting the establishment, modification, and release of air interface resources. The gNB-DU mainly comprises the RLC (Radio Link Control), MAC (Media Access Control), PHY (Physical), and RF (Radio Frequency) layers.

[0088] Based on the analysis, this application provides an information transmission method, apparatus, and network element to solve the problem of how to support resource sharing of broadcast multicast services under multiple PLMNs in a scenario where gNB-CUs are not shared but gNB-DUs are shared.

[0089] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0090] like Figure 3 As shown, this application embodiment provides an information transmission method, executed by a first network element, including:

[0091] Step S301: Send the first information to the second network element;

[0092] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

[0093] It should be noted that the first network element is connected to a different Public Land Mobile Network (PLMN) than the other network elements. In other words, services issued by different PLMNs can be transmitted by the second network element using the same radio resources.

[0094] Optionally, in at least one embodiment of this application, the first information includes at least one of the following:

[0095] A11. First instruction, the first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements other than the first network element;

[0096] Among them, the MBS supported by the first network element can be the same MBS or different MBS supported by other network elements.

[0097] In this case, the first network element instructs the second network element that the MBS it supports allows wireless resource sharing with MBS supported by other network elements, thereby enabling the second network element to achieve resource sharing for broadcast or multicast services under multiple PLMNs.

[0098] A12. Second instruction, the second instruction is used to instruct the second network element to feed back to the first network element the relevant information of the MBS supported by the first network element;

[0099] It should be noted that the MBS related information mentioned in the embodiments of this application includes at least one of the following: bearer configuration information, quality of service (QoS) flow mapping information to multicast radio bearer (MRB), and MRB QoS flow information.

[0100] This situation can be understood as the MBS-related information supported by the first network element being able to be updated. For example, when the MBS-related information includes bearer configuration information, the bearer configuration information of the MBS supported by the first network element can be updated; when the MBS-related information includes QoS flow to MRB mapping information, the QoS flow to MRB mapping information of the MBS supported by the first network element can be updated; when the MBS-related information includes MRB QoS flow information, the MRB QoS flow information of the MBS supported by the first network element can be updated.

[0101] Optionally, the configuration information of the bearer may include at least one of the following:

[0102] Packet Data Convergence Protocol (PDCP) configuration information;

[0103] Service Data Adaptation Protocol (SDAP) configuration information.

[0104] In this case, the first network element instructs the second network element to allow the second network element to feed back the relevant information of the MBS supported by the first network element to the first network element. That is, the relevant information of the MBS transmitted by other network elements can be used to update the relevant information of the first network element's MBS. This also enables the second network element to realize resource sharing of broadcast or multicast services under multiple PLMNs.

[0105] It should be noted that the first network element may send A11 only to the second network element. In this case, the second network element does not need to inform the first network element of at least one of the following: the bearer configuration information, the QoS flow mapping information to the MRB, and the MRB QoS flow information used during actual transmission. Alternatively, the first network element may send A12 only to the second network element. In this case, after receiving the first information sent by the first network element, the second network element knows that the MBS supported by the first network element needs to share resources with the MBS supported by other network elements. At the same time, the first network element also needs to know at least one of the following: the bearer configuration information, the QoS flow mapping information to the MRB, and the MRB QoS flow information used during actual transmission. Alternatively, the first network element may send both A11 and A12 to the second network element simultaneously. In this case, the second network element also needs to inform the first network element of at least one of the following: the bearer configuration information, the QoS flow mapping information to the MRB, and the MRB QoS flow information used during actual transmission.

[0106] It should be noted that, in the embodiments of this application, the second network element refers to the distributed node (DU) on the access network side, such as a gNB-DU. Since the control plane and user plane of the central node on the access network side can be separated or not, when the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side; when the control plane and user plane of the central node on the access network side are separated, the first network element is the control plane central node.

[0107] Optionally, in at least one embodiment of this application, step S301 may be implemented as follows:

[0108] Send interface messages to the second network element;

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

[0110] It should be noted that the interface message sent by the first network element can directly carry the first information. Alternatively, the interface message can omit the first information and instead carry a service identifier associated with it. When the second network element learns of this service identifier, it can infer the content of the first information based on it. For example, if the first information indicates A11, and the interface message received by the second network element carries the identifier of service A, the second network element can determine, based on service A, that the services supported by the first network element can share radio resources with service A. Similarly, if the first information indicates A12, and the interface message received by the second network element carries the identifier of service B, the second network element can determine, based on service B, that it needs to send relevant information about service B back to the first network element.

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

[0112] The second information is received from the second network element, which is the relevant information of MBS supported by other network elements obtained by the second network element.

[0113] In other words, when the first network element instructs the second network element to provide feedback to the first network element regarding the MBS supported by the first network element, the second network element can configure the relevant information of MBS supported by other network elements to the MBS supported by the first network element and send the relevant information to the first network element. For example, the second network element can send the relevant information to the first network element if the MBS's relevant information is updated. For example, if the first network element instructs the second network element to provide feedback to the first network element regarding the configuration information of the MBS bearer supported by the first network element, then if the configuration information of the MBS bearer changes, the second network element will send the PDCP configuration information and / or SDAP configuration information of the MBS bearer to the first network element; or if the first network element instructs the second network element to provide feedback to the first network element regarding the mapping information of the QoS flow from the first network element to the MRB of the MBS supported by the first network element, then if the mapping information of the QoS flow from the MBS to the MRB changes, the second network element will send the mapping information of the QoS flow from the MBS to the MRB to the first network element; or if the first network element instructs the second network element to provide feedback to the first network element regarding the QoS flow information of the MRB of the MBS supported by the first network element, then if the QoS flow information of the MRB of the MBS changes, the second network element will send the QoS flow information of the MRB of the MBS to the first network element. It should also be 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 the MBS supported by other network elements besides the first network element, then under normal circumstances, even if the relevant information of the MBS is updated, the second network element will not send the relevant information of the MBS to the first network element.

[0114] Optionally, in at least one embodiment of this application, the method further includes:

[0115] In the case of separation between the control plane and the user plane, a second message is sent to the user plane network element.

[0116] This situation typically applies when the control plane and user plane of the central node on the access network side are separated. That is, the first network element is the control plane central node, and the user plane network element refers to the user plane central node. When the control plane and user plane are separated, the channel for actual data transmission should be maintained by the user plane central node. Therefore, after obtaining the relevant information of MBS, the control plane central node needs to send the information to the user plane central node.

[0117] It should also be noted that the second network element should usually obtain the relevant information of MBS before sending the second information to the first network element. The relevant information of the service MBS is usually sent by other network elements. Optionally, in at least one embodiment of this application, the second network element receives the third information sent by the third network element.

[0118] The second information is determined based on the third information;

[0119] The third information includes:

[0120] D11, PDCP configuration information carried;

[0121] D12, SDAP configuration information carried;

[0122] D13, QoS flow mapping information to MRB;

[0123] QoS information for D14 and MRB.

[0124] It should be noted that the third network element belongs to a different PLMN than the first network element. When the control plane and user plane of the central node on the access network side are not separated, the third network element is the central node on the access network side. When the control plane and user plane of the central node on the access network side are separated, the third network element is the control plane central node.

[0125] The embodiments of this application are illustrated below in specific applications.

[0126] First, it should be noted that the central node on the access network side is represented as gNB-CU, the control plane central node on the access network side is represented as gNB-CU-CP, the user plane central node on the access network side is represented as gNB-CU-UP, and the distributed node on the access network side is represented as gNB-DU.

[0127] Application Scenario 1: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same broadcast service.

[0128] The specific implementation process is as follows: Figure 4 As shown, it mainly includes:

[0129] In step S101, gNB-CU1 sends a broadcast context setup request message to the shared gNB-DU to request the establishment of a context for the broadcast service identified as TMGI1.

[0130] In this Broadcast Context Establishment Request message, the CU informs the DU that the service identified as TMGI1 and the service identified as TMGI2 under PLMN1 are the same service under different PLMNs and can use the same radio resources. This message can carry SDAP layer configuration.

[0131] In step S102, after receiving the broadcast context setup request message, gNB-DU finds that DU has not yet saved the context of the broadcast service corresponding to TMGI1, saves the configuration information sent by gNB-CU1, and then replies to CU with a broadcast context setup response message to indicate that the broadcast-related context setup was successful.

[0132] In step S103, the gNB-DU broadcasts its support for broadcast services identified as TMGI1 via system messages, and the UE under PLMN1 listens for the broadcast services in this cell.

[0133] Step S104: gNB-CU2-CP sends a broadcastbear context setup request message to gNB-CU2-UP to request gNB-CU2-UP to establish the context of the broadcast service MRB;

[0134] Step S105: gNB-CU2-UP sends a broadcastbear context setup response message to gNB-CU2-CP.

[0135] Step S106: The gNB-CU2-CP sends a Broadcast Context Setup Request message to the shared gNB-DU to request the establishment of a context for the broadcast service identified as TMGI2. In this message, the CU informs the DU that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs and can use the same radio resources. This message may carry SDAP layer configuration.

[0136] In step S107, after receiving the message, the gNB-DU finds that the context of the broadcast service identified as TMGI1 has already been saved, and there is no need to create a new context for the broadcast service of TMGI2. The gNB-DU further checks the configuration information (such as SDAP configuration, PDCP configuration), QoS flow to MRB mapping information, etc. sent by the gNB-CU2-CP. If it is inconsistent with the information currently saved by the DU, the gNB-DU carries the configuration information for this service saved by the DU in the broadcast context setup response message sent to the gNB-CU2-CP.

[0137] In step S108, gNB-CU2-CP sends the configuration information of MRB (such as SDAP configuration, PDCP configuration), the mapping of QoS flow to MRB, and the QoS information of MRB to gNB-CU2-UP received from gNB-DU. For example, updated MRB configuration information (such as SDAP configuration, PDCP configuration), the mapping of QoS flow to MRB, and the QoS information of MRB can be carried through a broadcast bear context modification request.

[0138] Step S109: gNB-CU2-UP replies with a response message to gNB-CU2-CP.

[0139] In step S110, the gNB-DU broadcasts via system messages the broadcast services it supports, identified as TMGI1 and TMGI2, which correspond to the same MCCH and MTCH. UEs under PLMN1 and PLMN2 listen for this broadcast service on the same resource block.

[0140] Application Scenario 2: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same multicast service.

[0141] The specific implementation process is as follows: Figure 5 As shown, it mainly includes:

[0142] In step S201, gNB-CU1 sends a multicast context setup request message to the shared gNB-DU to request the establishment of a context for the multicast service identified as TMGI1.

[0143] In this multicast context establishment request message, the CU notifies the DU that the service identified as TMGI1 and the service identified as TMGI2 under PLMN1 are the same service under different PLMNs and can use the same radio resources. This message may carry SDAP layer configuration.

[0144] In step S202, after receiving the multicast context setup request message, gNB-DU finds that DU has not yet saved the context of the multicast service corresponding to TMGI1, saves the configuration information sent by gNB-CU1, and then replies to CU with a multicast context setup response message.

[0145] Step S203: gNB-DU provides multicast services to UEs under PLMN1 on the radio resources corresponding to the TMGI1 multicast service.

[0146] Step S204: gNB-CU2-CP sends a multicastbear context setup request message to gNB-CU2-UP to request gNB-CU2-UP to establish the context of the multicast service MRB;

[0147] In step S205, gNB-CU2-UP sends a multicastbear context setup response message to gNB-CU2-CP.

[0148] In step S206, the gNB-CU2-CP sends a multicast Context Setup Request message to the shared gNB-DU to request the establishment of a context for the multicast service identified as TMGI2. In this message, the CU informs the DU that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs and can use the same radio resources. This message may carry SDAP layer configuration.

[0149] In step S207, after receiving the message, the gNB-DU finds that the context of the multicast service identified as TMGI1 has already been saved, and there is no need to create a new context for the multicast service of TMGI2. The gNB-DU further checks the configuration information (such as SDAP configuration, PDCP configuration), QoS flow to MRB mapping information, etc., sent by the gNB-CU2-CP. If it is inconsistent with the information currently saved by the DU, the gNB-DU carries the configuration information for this service saved by the DU in the multicast Context Setup response message sent to the gNB-CU2-CP.

[0150] In step S208, gNB-CU2-CP sends the configuration information of MRB (such as SDAP configuration, PDCP configuration), the mapping of QoS flow to MRB, and the QoS information of MRB received from gNB-DU to gNB-CU2-UP. For example, updated MRB configuration information (such as SDAP configuration, PDCP configuration), the mapping of QoS flow to MRB, and the QoS information of MRB can be carried from Gnb-du through a broadcast bear context modification request.

[0151] Step S209: gNB-CU2-UP replies with a response message to gNB-CU2-CP.

[0152] In step S210, gNB-DU sends the same multicast service for UEs in PLMN1 and PLMN2 on the same resources (identified as TMGI1 in PLMN1 and TMGI2 in PLMN2).

[0153] Application Scenario 3: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same broadcast service.

[0154] The specific implementation process is as follows: Figure 6 As shown, it mainly includes:

[0155] In step S301, gNB-CU1 sends a broadcast context setup request message to the shared gNB-DU to request the establishment of a context for the broadcast service identified as TMGI1.

[0156] In this broadcast context establishment request message, the CU notifies that the service identified as TMGI1 and the service identified as TMGI2 under DU PLMN1 are the same service under different PLMNs, and that the configuration information of this service under gNB-CU1 can be updated. This message can carry the configuration of the SDAP layer.

[0157] Steps S302-S305 are the same as steps S102-S105 in application case one.

[0158] Step S306: The gNB-CU2-CP sends a Broadcast Context Setup Request message to the shared gNB-DU to request the establishment of a context for the broadcast service identified as TMGI2. In this message, the CU informs the DU that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and the configuration information of this service under gNB-CU2 can be updated. This message can carry the SDAP layer configuration.

[0159] Steps S307-S310 are the same as steps S107-S110 in application case one.

[0160] Application Scenario 4: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same multicast service.

[0161] The specific implementation process is as follows: Figure 7 As shown, it mainly includes:

[0162] In step S401, gNB-CU1 sends a multicast context setup request message to the shared gNB-DU to request the establishment of a context for the multicast service identified as TMGI1.

[0163] In this multicast context establishment request message, the CU notifies the DU that the service identified as TMGI1 and the service identified as TMGI2 under DU PLMN1 are the same service under different PLMNs, and whether the configuration information of this service under gNB-CU1 can be updated. This message can carry the configuration of the SDAP layer.

[0164] Steps S402-S405 are the same as steps S202-S205 in application scenario two.

[0165] Step S406: The gNB-CU2-CP sends a multicast Context Setup Request message to the shared gNB-DU to request the establishment of a context for the multicast service identified as TMGI2. In this message, the CU informs the DU that the service identified as TMGI2 and the service identified as TMGI1 are the same service under different PLMNs, and the configuration information of this service under gNB-CU2 can be updated. This message can carry the SDAP layer configuration.

[0166] Steps S407-S410 are the same as steps S207-S210 in application scenario two.

[0167] Application scenario 5: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same broadcast service.

[0168] The main difference between this application scenario and application scenario three is that in steps S301 and S306, gNB-CU1 and gNB-CU2 notify gNB-DU that the QoS flow mapping information of this service to the MRB can be updated. The other steps are the same as in application scenario three.

[0169] Application Scenario 6: PLMN1 and PLMN2 share the gNB-DU, but do not share the gNB-CU. Both PLMN1 and PLMN2 support the same multicast service.

[0170] The main difference between this application scenario and application scenario four is that in steps S401 and S406, gNB-CU1 and gNB-CU2 notify gNB-DU that the QoS flow mapping information of this service to the MRB can be updated. The other steps are the same as in application scenario four.

[0171] In at least one embodiment of this application, when the NG-RAN is a CU / DU separated architecture and the gNB-CU does not share gNB-DU sharing, the gNB-CU decides whether to share radio resources for the same broadcast / multicast service with other PLMNs, whether to allow the DU to update the QoS flow mapping information to the MRB, whether to allow modification of the bearer configuration information, and whether to allow updating the MRB QoS flow information, and notifies the gNB-DU. After receiving the notification from the gNB-CU, the gNB-DU can feed back at least one of the updated configuration information, QoS flow mapping information to the MRB, and MRB QoS flow information to the gNB-CU-CP that is allowed to share radio resources for broadcast / multicast services with other PLMNs. The gNB-CU-CP further provides at least one of the updated configuration information, QoS flow mapping information to the MRB, and MRB QoS flow information to the gNB-CU-UP. This enables the same service in different PLMNs to use the same radio resources in RAN sharing scenarios, thereby optimizing system efficiency.

[0172] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0173] like Figure 8 As shown, this application embodiment provides an information transmission device 800, applied to a first network element, including:

[0174] The first transmitting unit 801 is used to transmit first information to the second network element;

[0175] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

[0176] The first information includes one or more of the following:

[0177] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0178] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0179] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

[0180] Optionally, the first transmitting unit 801 is configured to:

[0181] Send interface messages to the second network element;

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

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

[0184] The second receiving unit is used to receive second information sent by the second network element. The second information is related information of MBS supported by other network elements obtained by the second network element.

[0185] Optionally, the device further includes:

[0186] The second transmitting unit is used to transmit second information to user plane network elements when the control plane and user plane are separated.

[0187] It should be noted that this device embodiment corresponds one-to-one with the above method embodiments. All implementation methods in the above method embodiments are applicable to this device embodiment and can achieve the same technical effect.

[0188] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0189] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0190] like Figure 9 As shown in the illustration, this application embodiment also provides a network element, which is a first network element, including a processor 900, a transceiver 910, a memory 920, and a program stored in the memory 920 and executable on the processor 900; wherein, the transceiver 910 is connected to the processor 900 and the memory 920 via a bus interface, and the processor 900 is used to read the program in the memory and execute the following processes:

[0191] The first information is sent to the second network element via transceiver 910;

[0192] The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element, and the first network element shares the second network element with other network elements besides the first network element.

[0193] Transceiver 910 is used to receive and send data under the control of processor 900.

[0194] Among them, Figure 9 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 910 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0195] The processor 900 is responsible for managing the bus architecture and general processing, while the memory 920 can store the data used by the processor 900 during operation.

[0196] Optionally, the processor 900 can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0197] The processor executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling a computer program stored in memory. The processor and memory may also be physically separated.

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

[0199] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0200] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0201] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0203] The transceiver 910 sends interface messages to the second network element.

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

[0205] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0206] The transceiver 910 receives the second information sent by the second network element, which is the relevant information of MBS supported by other network elements obtained by the second network element.

[0207] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0208] The transceiver 910 sends the second information to the user plane network element when the control plane and user plane are separated.

[0209] At least one embodiment of this application also provides a network element, which is a first network element, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the various processes in the information transmission method embodiment applied to the first network element and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0210] At least one embodiment of this application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the program implements the various processes described above in the information transmission method embodiment applied to the first network element, and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0211] Corresponding to the implementation on the first network element side, such as Figure 10 As shown, this application embodiment provides an information transmission method, executed by a second network element, including:

[0212] Step S1001: Receive first information sent by the first network element. The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements other than the first network element. The first network element shares the second network element with other network elements other than the first network element.

[0213] Based on the first information, the MBS supported by the first network element is processed.

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

[0215] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0216] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0217] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0219] Receive interface messages sent by the first network element;

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

[0221] Optionally, processing the MBS supported by the first network element based on the first information includes:

[0222] Configure the relevant information of MBS supported by other network elements to the MBS supported by the first network element, and send the second information to the first network element. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

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

[0224] Receive third information sent by a third network element;

[0225] The second information is determined based on the third information;

[0226] The third information includes at least one of the following:

[0227] The PDCP configuration information carried;

[0228] The SDAP configuration information carried;

[0229] Mapping information from QoS flows to MRB;

[0230] QoS information for MRB.

[0231] It should be noted that all descriptions in the above embodiments are applicable to the embodiments of the information transmission method applied to the second network element side, and can achieve the same technical effect.

[0232] like Figure 11 As shown, this application embodiment also provides an information transmission device 1100, applied to a first network element, including:

[0233] The first receiving unit 1101 is used to receive first information sent by the first network element. The first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element. The first network element shares the second network element with other network elements other than the first network element.

[0234] The processing unit 1102 is used to process the MBS supported by the first network element according to the first information.

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

[0236] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0237] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0238] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

[0239] Optionally, the first receiving unit 1101 is configured to:

[0240] Receive interface messages sent by the first network element;

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

[0242] Optionally, the processing unit 1102 is used for:

[0243] Configure the relevant information of MBS supported by other network elements to the MBS supported by the first network element, and send the second information to the first network element. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

[0244] It should be noted that the device provided in this application embodiment is a device capable of performing the above information transmission method. Therefore, all embodiments of the above information transmission method are applicable to this device embodiment and can achieve the same or similar beneficial effects.

[0245] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0246] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0247] This application embodiment also provides a network element, which is a second network element. Specifically, the structure of the second network element is similar to... Figure 9 The structure of the first network element shown is similar and will not be described again here.

[0248] The processor is used to read the program from the memory and execute the following processes:

[0249] The transceiver receives first information sent by the first network element. The first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element. The first network element shares the second network element with other network elements other than the first network element.

[0250] Based on the first information, the MBS supported by the first network element is processed.

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

[0252] The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element.

[0253] The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element.

[0254] The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

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

[0256] Receive interface messages sent by the first network element through the transceiver;

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

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

[0259] The relevant information of MBS supported by other network elements is configured to the MBS supported by the first network element, and the second information is sent to the first network element through the transceiver. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

[0260] It should be noted that the network element provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0261] At least one embodiment of this application also provides a network element, which is a second network element, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the various processes in the information transmission method embodiment applied to the second network element and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0262] This application also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of an information transmission method applied to a second network element. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs), etc.).

[0263] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0264] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can 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, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0265] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0266] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0267] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. An information transmission method, characterized in that, Executed by the first network element, when the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side; when the control plane and user plane of the central node on the network input side are separated, the first network element is the central node on the control plane, including: Send the first information to the second network element, which is a distributed node on the access network side; Wherein, the first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element, and the first network element shares the second network element with other network elements other than the first network element; The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

2. The method according to claim 1, characterized in that, Sending the first information to the second network element includes: Send interface messages to the 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.

3. The method according to claim 1, characterized in that, The method further includes: The second information is received from the second network element, which is the relevant information of MBS supported by other network elements obtained by the second network element.

4. The method according to claim 3, characterized in that, Also includes: In the case of separation between the control plane and the user plane, a second message is sent to the user plane network element.

5. An information transmission method, characterized in that, This is executed by a second network element, which is a distributed node on the access network side, including: The system receives first information sent by a first network element. The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements besides the first network element. The first network element shares the second network element with other network elements besides the first network element. When the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side. When the control plane and user plane of the central node on the network access side are separated, the first network element is the central node on the control plane. Based on the first information, the MBS supported by the first network element is processed; The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

6. The method according to claim 5, characterized in that, The first information received from the first network element includes: Receive interface messages sent by the first network element; The interface message carries the first information and / or a service identifier, and the service identifier is associated with the first information.

7. The method according to claim 5, characterized in that, The step of processing the MBS supported by the first network element based on the first information includes: Configure the relevant information of MBS supported by other network elements to the MBS supported by the first network element, and send the second information to the first network element. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

8. A network element, wherein the network element is a first network element, wherein when the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side; and when the control plane and user plane of the central node on the network access side are separated, the first network element is the central node on the control plane, characterized in that... Includes memory, transceiver, and processor: Memory, used to store computer programs; The transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: The first information is sent to the second network element through the transceiver, and the second network element is a distributed node on the access network side; Wherein, the first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element, and the first network element shares the second network element with other network elements other than the first network element; The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

9. The network element according to claim 8, characterized in that, The processor is configured to read the computer program in the memory and perform the following operations: Send interface messages to the second network element via transceiver; The interface message carries the first information and / or a service identifier, and the service identifier is associated with the first information.

10. The network element according to claim 8, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: The transceiver receives second information sent by the second network element, which is information about MBS supported by other network elements obtained by the second network element.

11. The network element according to claim 10, characterized in that, The processor, for reading the computer program in the memory, also performs the following operations: The second information is sent to the user plane network element through the transceiver when the control plane and user plane are separated.

12. A network element, wherein the network element is a second network element, and the second network element is a distributed node on the access network side, characterized in that, Includes memory, transceiver, and processor: Memory, used to store computer programs; The transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: The transceiver receives first information sent by the first network element. The first information is used to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element. The first network element shares the second network element with other network elements besides the first network element. When the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side. When the control plane and user plane of the central node on the network access side are separated, the first network element is the central node on the control plane. Based on the first information, the MBS supported by the first network element is processed; The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

13. The network element according to claim 12, characterized in that, The processor is configured to read the computer program in the memory and perform the following operations: Receive interface messages sent by the first network element through the transceiver; The interface message carries the first information and / or a service identifier, and the service identifier is associated with the first information.

14. The network element according to claim 12, characterized in that, The processor is configured to read the computer program in the memory and perform the following operations: The relevant information of MBS supported by other network elements is configured to the MBS supported by the first network element, and the second information is sent to the first network element through the transceiver. The second information is the relevant information of MBS supported by other network elements obtained by the second network element.

15. An information transmission device, characterized in that, Applied to the first network element, when the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side; when the control plane and user plane of the central node on the network input side are separated, the first network element is the central node on the control plane, including: The first sending unit is used to send first information to the second network element, which is a distributed node on the access network side; Wherein, the first information is used to indicate that the multicast broadcast service MBS supported by the first network element is allowed to use the same radio resources as MBS supported by other network elements other than the first network element, and the first network element shares the second network element with other network elements other than the first network element; The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

16. An information transmission device, characterized in that, Applied to the second network element, which is a distributed node on the access network side, including: The first receiving unit is configured to receive first information sent by the first network element. The first information is configured to indicate that the multicast broadcast service (MBS) supported by the first network element is allowed to use the same radio resources as the MBS supported by other network elements besides the first network element. The first network element shares the second network element with other network elements besides the first network element. When the control plane and user plane of the central node on the access network side are not separated, the first network element is the central node on the access network side. When the control plane and user plane of the central node on the network access side are separated, the first network element is the central node on the control plane. The processing unit is configured to process the MBS supported by the first network element according to the first information. The first information includes one or more of the following: The first instruction is used to instruct the MBS supported by the first network element to share radio resources with MBS supported by other network elements besides the first network element. The second instruction is used to instruct the second network element to feed back relevant information about the MBS supported by the first network element to the first network element. The relevant information of the MBS includes at least one of the following: bearer configuration information, QoS flow mapping information to the MRB multicast radio bearer, and MRB QoS flow information.

17. 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 according to any one of claims 1 to 7.