Multicast and broadcast service broadcasts in decomposition and sharing radio access network deployments

Abstract

A method may include receiving a first broadcast setup request message. The method may also include receiving a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. The first broadcast session setup request message and the second broadcast session setup request message may correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. The first configuration and the second configuration may be different. It may be determined whether a feedback message is to be sent to the second centralized unit network, and whether the second centralized unit network element is capable of accepting at least one of the configurations sent in the feedback message. A final response message indicating successful or failed establishment is sent to the second centralized unit network element.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to IN Provisional Application No. 202341006508, filed on February 1, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) New Radio (NR) access technologies, or above 5G, or other communication systems. For example, certain example embodiments may relate to apparatus, systems, and / or methods for decomposing and sharing multicast and broadcast service (MBS) broadcasts in a radio access network (RAN) deployment. Background Art

[0004] Examples of mobile or wireless telecommunication systems may include: Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro, and / or fifth generation (5G) radio access technology, or NR access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G network technology is mostly based on New Radio (NR) technology, but 5G (or NG) networks can also be built on E-UTRAN radios. It is estimated that NR will provide bit rates of approximately 10-20 Gbit / s or higher and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC), as well as massive machine type communications (mMTC). NR is expected to provide extreme broadband and ultra-robust low latency connectivity and large-scale networks to support IoT. Summary of the Invention

[0005] Some example embodiments may be directed to a method. The method may include, in a distributed radio access node shared by two or more public land mobile networks, receiving a first broadcast session establishment request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast session establishment request message includes a first configuration of the first centralized unit network element. The method may also include, in the distributed radio access node, receiving a second broadcast session establishment request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast session establishment request message includes a second configuration of the second centralized unit network element. The method may also include determining that the first broadcast session establishment request message and the second broadcast session establishment request message correspond to the same broadcast service shared by the two public land mobile networks in the public land mobile networks sharing the shared distributed radio access. Furthermore, the method may include determining that the first configuration and the second configuration are different. Furthermore, the method may include determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. The method further includes determining, based on a response of the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The method further includes sending, based on the determination based on the response of the second centralized cell network element to the feedback message, a final response message indicating successful or failed establishment to the second centralized cell network element.

[0006] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus to at least: receive, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. The apparatus may also be caused to: receive, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message may include a second configuration of the second centralized unit network element. The apparatus may also be caused to: determine that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may be caused to: determine that the first configuration and the second configuration are different. Furthermore, the apparatus may be configured to determine whether to send a feedback message to the second centralized cell network element, the feedback message including a configuration list including at least the first configuration or the current operating configuration. The apparatus may also be configured to determine, based on a response from the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The apparatus may also be configured to send, based on the determination based on the response from the second centralized cell network element to the feedback message, a final response message indicating a successful or failed setup to the second centralized cell network element.

[0007] Other example embodiments may be directed to an apparatus. The apparatus may include means for receiving, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. The apparatus may also include means for receiving, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message includes a second configuration of the second centralized unit network element. The apparatus may also include means for determining that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. The apparatus may also include means for determining that the first configuration and the second configuration are different. The apparatus may also include means for determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list including at least the first configuration or a current operating configuration. The apparatus may further include: means for determining, based on a response of the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The apparatus may further include: means for sending, to the second centralized cell network element, a final response message indicating successful or failed establishment, based on the determination based on the response of the second centralized cell network element to the feedback message.

[0008] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include: receiving, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message includes a first configuration of the first centralized unit network element. The method may also include: receiving, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message includes a second configuration of the second centralized unit network element. The method may also include: determining that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by the two public land mobile networks in the public land mobile networks sharing the distributed radio access. Furthermore, the method may include: determining that the first configuration and the second configuration are different. Furthermore, the method may include determining whether to send a feedback message to the second centralized cell network element, the feedback message including a configuration list including at least the first configuration or the current operating configuration. The method may also include determining, based on a response from the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The method may also include sending a final response message to the second centralized cell network element indicating a successful or failed setup, based on the determination based on the response from the second centralized cell network element to the feedback message.

[0009] Other example embodiments may be directed to a computer program product for performing a method. The method may include: receiving, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast session establishment request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast session establishment request message includes a first configuration of the first centralized unit network element. The method may also include: receiving, in the distributed radio access node, a second broadcast session establishment request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast session establishment request message includes a second configuration of the second centralized unit network element. The method may also include: determining that the first broadcast session establishment request message and the second broadcast session establishment request message correspond to the same broadcast service shared by the two public land mobile networks in the public land mobile networks sharing the shared distributed radio access. The method may also include: determining that the first configuration and the second configuration are different. The method may also include: determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. The method further includes determining, based on a response of the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The method further includes sending, based on the determination based on the response of the second centralized cell network element to the feedback message, a final response message indicating successful or failed establishment to the second centralized cell network element.

[0010] Other example embodiments may be directed to an apparatus that may include circuitry configured to receive, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. The apparatus may also include circuitry configured to receive, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message may include a second configuration of the second centralized unit network element. The apparatus may also include circuitry configured to determine that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may include circuitry configured to determine that the first configuration and the second configuration are different. Additionally, the apparatus may include circuitry configured to determine whether to send a feedback message to the second centralized cell network element, the feedback message including a configuration list including at least the first configuration or the current operating configuration. The apparatus may also include circuitry configured to determine, based on a response from the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The apparatus may also include circuitry configured to send a final response message to the second centralized cell network element indicating a successful or failed setup based on the determination based on the response from the second centralized cell network element to the feedback message.

[0011] Certain example embodiments may be directed to a method. The method may include sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The method may also include sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The method may also include, at the second centralized unit network element, receiving a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the method may include, at the second centralized unit network element, sending an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the method may include receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0012] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus to at least: send a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The apparatus may also be caused to: send a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The apparatus may also be caused to: receive, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the apparatus may be caused to: at the second centralized cell network element, in response to the feedback message, send to the distributed radio access node an indication of whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the apparatus may be caused to: at the second centralized cell network element, based on a response to the feedback message, receive from the distributed radio access node a final response message indicating a successful or failed establishment.

[0013] Other example embodiments may be directed to an apparatus. The apparatus may include means for sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized cell network element managed by one of the shared public land mobile networks. The apparatus may also include means for sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized cell network element managed by another of the shared public land mobile networks. The apparatus may also include means for receiving, at the second centralized cell network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the apparatus may include means for sending, at the second centralized cell network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the apparatus may include means for receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0014] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized cell network element managed by one of the shared public land mobile networks. The method may also include sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized cell network element managed by another of the shared public land mobile networks. The method may also include receiving, at the second centralized cell network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the method may include, at the second centralized cell network element, sending, in response to the feedback message, an indication to the distributed radio access node as to whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the method may include receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0015] Other example embodiments may be directed to a computer program product for performing a method. The method may include sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized cell network element managed by one of the shared public land mobile networks. The method may also include sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized cell network element managed by another of the shared public land mobile networks. The method may also include, at the second centralized cell network element, receiving a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. The method may also include, at the second centralized cell network element, sending an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the method may include receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0016] Other example embodiments may be directed to an apparatus that may include circuitry configured to send a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized cell network element managed by one of the shared public land mobile networks. The apparatus may also include circuitry configured to send a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized cell network element managed by another of the shared public land mobile networks. The apparatus may also include circuitry configured to receive, at the second centralized cell network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least a first configuration or a currently operating configuration. Furthermore, the apparatus may include circuitry configured to send, at the second centralized cell network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the apparatus may include circuitry configured to receive, at the centralized unit network element, a final response message from the shared distributed radio access node indicating a successful or failed establishment based on a response to the feedback message. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:

[0018] Figure 1 Diagram illustrates an example deployment scenario.

[0019] Figure 2 An example broadcast context establishment process is illustrated.

[0020] Figure 3 An example signal flow diagram is illustrated in accordance with certain example embodiments.

[0021] Figure 4 Another example signal flow diagram is illustrated in accordance with certain example embodiments.

[0022] Figure 5 Another example signal flow diagram is illustrated in accordance with certain example embodiments.

[0023] Figure 6 Another example signal flow diagram is illustrated in accordance with certain example embodiments.

[0024] Figure 7 An example flow diagram of a method according to certain example embodiments is illustrated.

[0025] Figure 8 An example flow diagram of another method according to certain example embodiments is illustrated.

[0026] Figure 9 A set of apparatuses according to certain example embodiments is illustrated. DETAILED DESCRIPTION

[0027] It will be readily understood that the components of certain example embodiments, as generally described and illustrated herein and in the accompanying figures, may be arranged and designed in a variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for disaggregated and shared (Multicast and Broadcast Service) MBS broadcasts in RAN deployments. For example, certain example embodiments may be directed to disaggregated and shared MBS broadcasts in RAN deployments.

[0028] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "a particular embodiment," "an example embodiment," or "some embodiments" throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with one embodiment may be included in at least one embodiment. Thus, the appearance of the phrases "in some embodiments," "an example embodiment," "in some embodiments," or other similar language throughout this specification does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Furthermore, the terms "cell," "node," "gNB," "network," or other similar language may be used interchangeably throughout this specification. Furthermore, the terms "distributed unit (DU)" and "gNB-DU," as well as "centralized unit (CU)" and "gNB-CU," may be used interchangeably throughout this specification.

[0029] As used herein, “at least one of: ” and “at least one of <a list of two or more elements]” and similar expressions (where a list of two or more elements is connected by “and” or “or”) mean at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0030] The technical specifications of the 3rd Generation Partnership Project (3GPP) describe enhancements related to identifying and evaluating the 5GS architecture for providing MBS. Various solutions have been provided, including, for example, the possibility of providing a common temporary mobile group identity (TMGI) for different public land mobile networks (PLMNs) (e.g., PLMN-A and PLMN-B can use the same common TMGI for the same service). This solution can be coordinated via an application function (AF). In another solution, each PLMN can create a separate local TMGI for the same service. However, additional information can be sent to the NG-RAN node so that the shared NG-RAN node understands that the two TMGIs refer to the same service and the data is sent only once in the radio interface. According to another solution, the shared NG-RAN node may already be configured with the PLMN ID of each sharing partner and may be configured with specific corresponding service IDs (e.g., 6 digits) of the TMGIs of the two PLMNs corresponding to the same content or service ID range.

[0031] In the first solution, the 5G core network (CN) can send a common identifier (e.g., a source-specific multicast (SSM) address) and a TMGI created separately for the same service at each 5G CN (for each PLMN). When the NG-RAN node receives a request to create a broadcast session from different core networks via different TMGIs and common identifier SSM addresses, the NG-RAN node can understand that these different TMGIs belong to the same service. Therefore, the RAN node can send the same data only once in the radio interface using the same G-Radio Network Temporary Identifier (G-RNTI). In addition, user equipment (UE) sharing a PLMN (e.g., UEs belonging to PLMN A, PLMN B, and PLMN C that share a common NG-RAN node) can only receive data scrambled via the same G-RNTI (and the corresponding physical downlink control channel (PDCCH) for the same service) once.

[0032] In the second solution described above, the shared NG-RAN node can be configured with information so that the TMGIs can belong to the same broadcast session created by different 5G CNs. By doing so, the NG-RAN can understand that the TMGIs from different PLMNs belong to the same service and can therefore send the same data only once in the radio interface.

[0033] Various deployment options are possible for converged and decomposed NG-RAN types in MBS broadcast. For example, some deployment options may include, but are not limited to, converged gNB, decomposed gNB, and sharing only some cells within a gNB. For decomposed gNBs, both centralized units (CUs) and distributed units (DUs) can be shared. Furthermore, for decomposed gNBs, only DU sharing and CU non-sharing options may be available. The agreed-upon solution may have a direct impact on the procedures and functionality of the specific deployment type being considered.

[0034] For deployments where only the DU is shared across multiple PLMNs, but the CU is different (not shared), it can be assumed that multiple CNs can create the same MBS broadcast service. Assuming the first solution (different local TMI per PLMN), each CN can send a separate broadcast establishment request to the shared gNB-DU. Figure 1 The diagram shows an example deployment scenario. Figure 1 In the example above, to configure shared radio resources, the gNB-DU may need to know that different TMGIs belong to the same MBS session. The gNB-DU can then allocate the same radio resources to different TMGIs (e.g., the discontinuous reception (DRX) configurations for different TMGIs can be configured with the same value, and data can be sent only once). Figure 1 The deployment shown can be achieved by the CU forwarding the same common information (ie, SSM address) to the DU for each TMGI.

[0035] It can be determined whether each CN can have more than one Next Generation Unit (NG-U) tunnel, and whether multiple F1-U tunnels can exist between different non-shared CUs and shared DUs. In some cases, one or more CUs may already be delivering the same service to another non-shared DU, and therefore, may already have an F1-U tunnel established with them, as well as an NG-U established with the CN.

[0036] Figure 2 An example broadcast context establishment process is shown. For example, Figure 2 The figure illustrates a decomposed architecture setup, where the gNB-CU can initiate the setup procedure by sending a Broadcast Context Setup Request message to the gNB-DU at 200. After the gNB-CU receives the Broadcast Context Setup Request for MBS services from the CN, the Broadcast Context Setup Request message can be sent to the gNB-DU. If the gNB-DU successfully establishes the broadcast context, it can reply to the gNB-CU with a Broadcast Context Setup Response at 205.

[0037] In a "non-shared CU and shared DU" deployment, a shared gNB-DU may receive a broadcast context establishment request (with TMGI-A) from a non-shared CU (gNB-CU-A) from a 5G CN (CN-A), along with other required configurations (e.g., multicast radio bearers (MRBs), packet data convergence protocol (PDCP) configuration, etc.) created by gNB-CU-A. The shared gNB-DU may configure this information for broadcast to UEs. Furthermore, a short time later or simultaneously, the shared gNB-DU may receive another broadcast establishment request for the same MBS broadcast service from another non-shared CU (gNB-CU-B) on another 5G CN (CN-B) with a different configuration (e.g., a different TMGI, but with identity assistance for the first solution). CN-B's gNB-CU-B may be unaware of the configuration already made for the same service on CN-A (by gNB-CU-A).

[0038] Because different non-shared gNB-CUs may require different configurations, a shared gNB-DU may not be able to take advantage of shared NG-RAN optimizations. That is, a shared gNB-DU may not be able to transmit a single, unified configuration and data over the air, which will be received by UEs in different shared PLMNs. This will result in multiple, redundant broadcasts of the Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) (MBS data). Furthermore, this may lead to even greater resource waste when a larger number of PLMNs / CNs share a common NG-RAN. Therefore, certain example embodiments described herein may provide a means for coordination between shared gNB-DUs and non-shared gNB-CUs to enable the desired MBS RAN sharing features to be applied in such deployment scenarios.

[0039] As described herein, certain example embodiments may involve a shared gNB-DU and multiple non-shared gNB-CUs to coordinate and optimize MBS-specific radio resources in accordance with the RAN sharing objectives of Rel-18 in 3GPP TR 23.700-47. For example, in some example embodiments, after a shared gNB-DU receives an MBS Broadcast Context Setup Request from gNB-CU-A along with TMGI-A (local TMGI + IP SSM for identification) and other configuration details (e.g., MRB configuration, PDCP SN length, Robust Header Compression (ROHC) parameters, t_reordering, etc.), the shared gNB-DU may use this information to configure the System Information Block 20 (SIB20) and Multicast Control Channel (MCCH) and may broadcast using the G-RNTI (for UEs in PLMN A). When the shared gNB-DU receives another subsequent Broadcast Context Setup Request from, for example, gNB-CU-B, the shared gNB-DU may have several options for proceeding.

[0040] For example, in some example embodiments, if the shared gNB-DU receives a Broadcast Context Setup Request message from gNB-CU-B with a CU-B configuration that is compatible or identical to that of CU-A, the shared gNB-DU may reply to gNB-CU-B with a Broadcast Context Setup Response message to indicate a successful setup. On the other hand, if the CU-B configuration differs from that of CU-A, the shared gNB-DU may send an F1 Broadcast Context Setup Failure message. Furthermore, the shared gNB-DU may include an Available MRB Configuration Information Element (IE) (including all configurations sent by CU-A for the service) containing the CU-A configuration. In other example embodiments, the gNB-CU B may attempt a subsequent F1AP Broadcast Setup Request that includes the CU-A configuration, if necessary.

[0041] According to another example embodiment, a new Type 1 F1 Application Protocol (F1AP) MRB Configuration Update procedure may be introduced. Following the F1AP Broadcast Context Request, the shared gNB-DU may trigger the F1AP MRB Configuration Update procedure to the gNB-CU-B. In some example embodiments, the F1AP MRB Configuration Update procedure may include an Update Request message and CU-A's configuration details in the F1AP MRB configuration. If the gNB-CU-B can accept CU-A's configuration, the gNB-CU-B may successfully reply with a F1AP MRB Configuration Update Response message. Furthermore, after receiving the F1AP MRB Configuration Update Response message, the shared gNB-DU may reply with a Broadcast Context Establishment Response message that may include the CU-A configuration.

[0042] In certain example embodiments, a new Type 1 F1AP MRB Configuration Update procedure may be provided. In some example embodiments, upon receiving a F1AP Broadcast Context Establishment Request, the shared gNB-DU may trigger a F1AP MRB Configuration Update procedure toward the gNB-CU-B. The F1AP MRB Configuration Update procedure may include the CU-A configuration in the F1AP MRB Configuration Update Request message. If the gNB-CU-B does not accept the shared gNB-DU's proposal to update / change its configuration to the gNB-CU-A configuration, the gNB-CU-B may reply to the shared gNB-DU with a F1AP MRB Configuration Failure message. Upon receiving the F1AP MRB Configuration Update Failure message from the shared gNB-CU-B, the gNB-DU may use both configurations separately, thereby transmitting two different data (i.e., the shared gNB-DU may reply to the gNB-CU-B with a Broadcast Establishment Response message including the originally requested CU-B configuration). This means that MBS broadcast data may be broadcast twice for two different TMIs.

[0043] Alternatively, in other example embodiments, after receiving the F1AP MRB Configuration Update Failure message from the gNB-CU-B, the shared gNB-DU may proceed with a single configuration that is transparent to the gNB-CU. For example, the shared gNB-DU may reply with a Broadcast Setup Failure message in the Broadcast Setup Request message to the originally requested CU-B configuration. This means that the shared gNB-DU may continue broadcasting using only the configuration of CU-A. In certain example embodiments, each time the shared gNB-DU sends a Successful Broadcast Setup Response to the gNB-CU control plane, the shared gNB-DU may indicate whether it requests F1-U tunnel establishment with the corresponding gNB-CU user plane by including a new indication (i.e., "Ignore DU DL Tunnel Endpoint Identifier (TEID)") when the shared gNB-DU does not request establishment.

[0044] According to other example embodiments, in the Broadcast Context Setup Request, the gNB-CU may also send a new DU Non-Shared Status parameter to the shared gNB-DU, indicating whether the gNB-CU is already providing service to one or more non-shared gNB-DUs. The receiving shared gNB-DU may consider this new parameter when determining which F1-U tunnel to establish (i.e., determining a new "Ignore DU DL TEID" setting). For example, in some example embodiments, upon receiving a parameter indicating that the gNB-CU is already providing service to one or more non-shared DUs, the shared gNB-DU may prefer to establish the F1-U tunnel using a specific gNB-CU UP. This may be because the gNB-CU already has an NG-U interface established with its CN to provide service to those non-shared gNB-DUs.

[0045] In certain example embodiments, a shared gNB-DU can receive the first broadcast context from any of the gNB-CUs and immediately share the configuration details with all connected gNB-CUs (without waiting for their individual requests). In this example embodiment, if the shared gNB-DU receives different configurations from different gNB-CUs that are incompatible with each other, the shared gNB-DU may not enable MBS RAN sharing optimization. Instead, the shared gNB-DU can treat services to UEs in different PLMNs as if they were different services from different PLMNs.

[0046] According to some example embodiments, if a pre-configured option is used to identify the MBS shared service across PLMNs (i.e., by Service ID or Service ID range), all gNB-CUs may be pre-configured with a TMGI mapping in addition to the shared gNB-DU. According to other example embodiments, if a "Correlation ID" is used to identify the MBS shared service across PLMNs, the Association ID may also be shared by immediately receiving the shared gNB-DU along with the configuration details for all gNB-CUs.

[0047] In certain example embodiments, the shared gNB-DU may receive the first broadcast context establishment request and wait until it receives a subsequent broadcast contention establishment request from other gNB-CUs (which share the same gNB-DU). Furthermore, the shared gNB-DU may then randomly select one (e.g., any one) of the configurations and update the same configuration with the remaining gNB-CUs.

[0048] According to certain example embodiments, operations and maintenance (O&M) can configure a TMGI configuration set for a gNB-CU to enable identification of the same broadcast service (i.e., broadcast sessions for sharing the same broadcast service). This can mean that O&M can pre-configure certain configurations for each non-shared gNB-CU with a shared gNB-DU within the service area of ​​the broadcast session. For example, the O&M platform can configure rules for mapping Quality of Service (QoS) flows to MRBs. For example, all QoS flows for a particular broadcast service can be mapped to the same MRB, or each flow can be mapped to a different MRB. This can ensure that the same MRB mapping from different non-shared gNB-CUs reaches the shared gNB-DU. In other example embodiments, the O&M platform can also configure PDCP configurations, including reordering timers and PDCP SN lengths. In addition, the O&M platform can configure ROHC configurations.

[0049] Figure 3An example signal flow diagram according to certain example embodiments is illustrated. At 300, an application management function (AMF) may initiate a Next Generation Application Protocol (NGAP) broadcast setup to gNB-CU-A. At 305, a shared gNB-DU may receive an F1 broadcast setup request from gNB-CU-A. According to some example embodiments, CU-A's configuration may include: MRB ID, PDCP SN length, and ROHC. According to other example embodiments, the F1 broadcast setup request message may include a "DU non-shared status" parameter indicating whether gNB-CU-A is already providing the same MBS broadcast service to one or more other non-shared gNB-DUs. At 310, the AMF may initiate an NGAP broadcast setup to gNB-CU-B.

[0050] At 315, the shared gNB-DU may receive an F1 Broadcast Setup Request from gNB-CU-B with the MRB configuration of CU-B. CU-B's configuration may include the MRB ID, PDCP SN length, and ROHC. In some example embodiments, the F1 Broadcast Setup Request message from gNB-CU-B may also include a "DU Non-Shared Status" parameter, which indicates whether gNB-CU-B is already providing service to one or more other non-shared DUs. At 320, the shared gNB-DU may determine that CU-B's configuration is the same as CU-A's configuration. Therefore, the shared gNB-DU may accept the F1 Setup Context and send an F1 Broadcast Setup Response message back to gNB-CU-B. In other example embodiments, if the shared gNB-DU determines that CU-B's configuration is different from CU-A's configuration, then at 325, the shared gNB-DU sends the gNB-CU configuration to gNB-CU-B in an F1AP Broadcast Setup Response. In certain example embodiments, the shared gNB-DU may be configured to be aware that gNB-CU-B is ready to accept any other running configuration from gNB-CU-A, or to accept a configuration run by gNB-CU-A that complies with a given policy.

[0051] According to certain example embodiments, in both operations 320 and 325, the shared gNB-DU may also include a new indication "Ignore DU DL TEID" in the F1 Broadcast Setup Response message, which indicates whether an F1-U tunnel should be established between the shared gNB-DU and gNB-CU-B. Given that the DU DL TEID is currently mandatory in the response message, it may include an indication indicating whether the DU DL TEID should be ignored (i.e., only the F1-U between the shared gNB-DU and gNB-CU-A will deliver data) or not ignored (i.e., the F1-U between the shared gNB-DU and gNB-CU-B is an additional establishment for redundancy).

[0052] Figure 4 Another example signal flow diagram is illustrated in accordance with certain example embodiments. Figure 4 As shown in FIG, operations 400 to 415 may be similar to Figure 3 Operations 300 to 315 in

[15] . At 420, the shared gNB-DU may determine that the configuration of CU-B is different from and / or incompatible with the configuration of CU-A. Accordingly, at 420, the shared gNB-DU may send an F1 Broadcast Failure message, which may include an Available MRB Configuration Information Element (IE), and the Available MRB Configuration IE may include the current operating CU-A configuration from gNB-CU-A. At 425, if operation according to CU-A's configuration is acceptable to gNB-CU-B, gNB-CU-B may decide to resend the F1 Broadcast Setup Request message including the CU-A configuration. In some example embodiments, the F1 Broadcast Setup Request message may also include a "DU Non-Shared Status" parameter, which indicates whether the gNB-CU-B is already providing service to one or more other non-shared DUs.

[0053] At 430, the shared gNB-DU may receive a broadcast setup request from the gNB-CU-B containing an MRB configuration that matches the configuration of the current CU-A it received from the shared gNB-DU. At 435, the shared gNB-DU may accept the F1 broadcast setup request and send an F1 broadcast setup response message to the gNB-CU-B. In some example embodiments, the F1 broadcast setup request message sent at 430 may include a "DU non-shared status" parameter that indicates whether the gNB-CU-B is already providing service to one or more other non-shared DUs. In addition, as described above with respect to Figure 3 Similar to the example embodiments described above, in some example embodiments, the shared gNB-DU may include a new indicator "Ignore DU DL TEID" at 435 to indicate whether an additional F1-U tunnel is to be used between the shared gNB-DU and gNB-CU-B. Since the DU DL TEID may be mandatory in the Broadcast Setup Response message, the DU DL TEID may include an indicator to indicate whether the DU DL TEID should be ignored (i.e., only the F1-U between the shared gNB-DU and gNB-CU-A will deliver data) or not ignored (i.e., the F1-U between the shared gNB-DU and gNB-CU-B UP is an additional setup for redundancy).

[0054] Figure 5 Another example signal flow diagram is illustrated in accordance with certain example embodiments. Figure 5 As shown in FIG, operations 500 to 515 may be similar to Figure 3Operations 300 to 315 in the above example may be performed. At 520, the shared gNB-DU may determine that the configuration of CU-B is different from and / or incompatible with the configuration of CU-A. Therefore, at 520, the shared gNB-DU may trigger a new MRB configuration update request procedure in the form of a F1AP MRB Configuration Update Request message to gNB-CU-B. In some example embodiments, the F1AP MRB Configuration Update Request message may include the current operating CU-A configuration from gNB-CU-A.

[0055] At 525, the gNB-CU-B may accept to operate according to the CU-A configuration and may signal its acceptance to the shared gNB-DU by sending an F1 MRB Configuration Response message at 530. At 535, upon receiving the F1 MRB Configuration Response message from the gNB-CU-B, the shared gNB-DU may understand that the gNB-CU-B accepts to operate according to the CU-A configuration and may respond to the gNB-CU-B with an F1 Broadcast Setup Response message (which includes the CU-A configuration). According to certain example embodiments, the F1 Broadcast Setup Response message sent from the shared gNB-DU may include the CU-A configuration instead of the initially requested CU-B configuration. In some example embodiments, including the CU-A configuration in the F1 Broadcast Setup Response message at 535 may be optional. In other words, at 530, the gNB-CU-B may have assumed, based on the transmission of the response message, that the received Broadcast Setup Response corresponds to the CU-A configuration.

[0056] Figure 6 Another example signal flow diagram is illustrated in accordance with certain example embodiments. Figure 6 As shown in FIG, operations 600 to 615 can be performed with Figure 3 Similar to operations 300 to 315 in FIG. , operation 620 can be performed with Figure 5 Similar to operation 520 in FIG. 6 . At 625 , gNB-CU-B may determine that the configuration suggestion of the shared gNB-DU for the CU-A configuration is not accepted. At 630 , gNB-CU-B may respond to the shared gNB-DU by sending a rejection response message. At 635 , the shared gNB-DU may determine to use both the configurations of CU-A and CU-B, respectively. By using both the configurations of CU-A and CU-B, respectively, multiple data transmissions may be performed by the shared gNB-DU. For example, Figure 6As shown in FIG6 , at 635, the shared gNB-DU may send a reply to the gNB-CU-B with a broadcast setup response that includes the originally requested CU-B configuration. This indicates that the shared gNB-DU may operate so that data may be broadcast twice for two different TMGIs. Furthermore, in certain example embodiments, the shared gNB-DU may add an additional indication that the broadcast may be inefficient because two different broadcast data transmissions may use separate radio resources, but this may be optional as the gNB-CU-B may understand this from operation 630.

[0057] Alternatively, in other example embodiments, the shared gNB-DU may continue to use a single configuration that is transparent to the gNB-CU at 640. For example, at 640, the shared gNB-DU may reply to gNB-CU-B with a broadcast setup failure message, initially requesting the CU-B configuration. This means that the shared gNB-DU may continue to broadcast using only the configuration of CU-A.

[0058] Figure 7 An example flow chart of a method according to certain example embodiments is illustrated. In an example embodiment, Figure 7 The method may be performed by a network entity or a group of multiple network elements in a 3GPP system such as LTE or 5G-NR. For example, in some example embodiments, Figure 7 The method can be performed by the network, cell, gNB, gNB-DU, gNB-CU, or similar Figure 9 Any other device of one of the devices 10 or 20 shown is implemented.

[0059] According to certain example embodiments, Figure 7The method may include, at 700, receiving, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. The method may also include, at 705, receiving, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message may include a second configuration of the second centralized unit network element. The method may also include, at 710, determining that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. Furthermore, the method may include, at 715, determining that the first configuration and the second configuration are different. In addition, the method may include, at 720, determining whether to send a feedback message to the second centralized cell network element, the feedback message including a configuration list, the configuration list including at least the first configuration or the current operating configuration. The method may also include, at 725, determining whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message based on a response of the second centralized cell network element to the feedback message. The method may also include, at 730, sending a final response message to the second centralized cell network element indicating a successful or failed setup based on the determination based on the response of the second centralized cell network element to the feedback message.

[0060] According to certain example embodiments, the feedback message to the second centralized unit network element may be a broadcast setup failure message, the broadcast setup failure message including a list of available configurations proposed by the distributed radio access node, the list of available configurations including at least a currently operating configuration or a first configuration. According to some example embodiments, the response to the feedback message may be a new broadcast setup request message sent by the second centralized unit network element, the new broadcast setup request message including one of the configurations in the list of available configurations proposed by the distributed radio access node, the list of available configurations including at least a currently operating configuration or the first configuration, or another configuration proposed by the second centralized unit network element. According to other example embodiments, the feedback message may be a multicast radio bearer configuration update request message triggered by the distributed radio access node, the multicast radio bearer configuration update request message including a list of available configurations proposed by the distributed radio access node, the list of available configurations including at least the currently operating configuration or the first configuration.

[0061] In certain example embodiments, the response to the feedback message may be a multicast radio bearer configuration update success response, indicating that one of the available configurations is acceptable to the second centralized unit network element and may include one or more of the accepted configurations, or a multicast radio bearer configuration failure unsuccessful message, indicating that none of the proposed available configurations is acceptable to the second centralized unit network element and may also include another configuration proposed by the second centralized unit network element. In some example embodiments, sending the final response message may include sending a broadcast setup response message to the second centralized unit network element if the configuration received from the second centralized unit network element in response to the feedback message is acceptable to the distributed radio access node. In other example embodiments, the final response message sent to the second centralized unit network element may include at least one of the following: the current operating configuration of the first centralized unit network element or any of the configurations included in the feedback message.

[0062] According to certain example embodiments, if the acceptable configuration received from the second centralized unit network element in response to the feedback message corresponds to the current operational configuration of the second centralized unit network element, the distributed radio access node does not initiate additional broadcasts. According to some example embodiments, if the acceptable configuration received from the second centralized unit network element in response to the feedback message does not correspond to the current operational configuration of the second centralized unit network element, the distributed radio access node initiates additional broadcasts. According to other example embodiments, sending the final response message includes sending a broadcast setup failure message to the second centralized unit distributed unit if the configuration received from the second centralized unit distributed unit in response to the feedback message is unacceptable to the distributed radio access node.

[0063] In certain example embodiments, the broadcast setup response message may include an indication of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element. In other example embodiments, the first broadcast setup request message may include a first parameter indicating whether the first centralized network element provides broadcast services to at least one non-shared distributed radio access node. In some example embodiments, the second broadcast setup request message may include a second parameter indicating whether the second centralized network element provides broadcast services to at least one non-shared distributed radio access node. In further example embodiments, the indication in the broadcast setup response message of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element may be based on at least one of: a parameter received from the first centralized network element and the second centralized network element, the parameter indicating whether the first centralized network element and the second centralized network element provide services to the non-shared distributed radio access node; or a centralized network element from which the final configuration has been accepted.

[0064] Figure 8 An example of a flow chart of another method according to certain example embodiments is illustrated. In an example embodiment, Figure 8 The method may be performed by a network entity or a group of multiple network elements in a 3GPP system such as LTE or 5G-NR. For example, in an example embodiment, Figure 8 The method can be performed by the network, cell, gNB, gNB-DU, gNB-CU, or similar Figure 9 Any other device of one of the devices 10 or 20 shown is implemented.

[0065] According to certain example embodiments, Figure 8The method may include, at 800, sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The method may also include, at 805, sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The method may also include, at 810, receiving, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the method may include, at 815, sending, at the second centralized unit network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the method may include, at 820, receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0066] According to certain example embodiments, the feedback message may be a broadcast setup failure message, the broadcast setup failure message including a list of available configurations proposed by the distributed radio access node, the list of available configurations including at least a current operating configuration or a first configuration. According to some example embodiments, the indication in the response to the feedback message may include a new broadcast setup request message, the new broadcast setup request message including one of the available configurations in the list of available configurations proposed by the distributed radio access node, the list of available configurations including at least a currently ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element. According to other example embodiments, the feedback message may be a multicast radio bearer configuration update request message triggered by the distributed radio access node, the multicast radio bearer configuration update request message including a list of available configurations proposed by the distributed radio access node, the list of available configurations including at least the current operating configuration or the first configuration.

[0067] In certain example embodiments, the indication in the response to the feedback message may be a multicast radio bearer configuration update success indication indicating that one of the available configurations is acceptable to the second centralized unit network element and may include one or more of the accepted configurations, or a multicast radio bearer configuration failure unsuccessful message indicating that none of the proposed available configurations is acceptable to the second centralized unit network element and may include another configuration proposed by the second centralized unit network element. In some example embodiments, receiving the final response message may include receiving a broadcast setup response message at the second centralized unit network element if the configuration sent in the response to the feedback message is acceptable to the distributed radio access node. In other example embodiments, the final response message may include at least one of the following: the current operating configuration of the first centralized unit network element or any of the configurations included in the feedback message.

[0068] According to certain example embodiments, receiving the final response message may include receiving a broadcast setup failure message at the second centralized unit network element if the configuration sent in the response to the feedback message is unacceptable to the distributed radio access node. According to some example embodiments, the broadcast setup response message may include an indication of whether a user plane tunnel should be established between the distributed radio network node and the second centralized unit network element. According to other example embodiments, the first broadcast setup request message may include a first parameter indicating whether the first centralized network element is to provide broadcast services to the at least one non-shared distributed unit network element.

[0069] In certain example embodiments, the second broadcast setup request message may include a second parameter indicating whether the second centralized network element provides broadcast services to the at least one non-shared distributed unit network element. In certain example embodiments, the indication in the broadcast setup response message of whether a user plane tunnel should be established between the distributed radio access node and the second centralized network element may be based on at least one of: a parameter received from the first centralized network element and the second centralized network element, the parameter indicating whether the first centralized network element and the second centralized network element provide broadcast services to the at least one non-shared distributed unit network element; or a centralized network element from which a final configuration has been accepted.

[0070] Figure 9A set of apparatuses 10 and 20 according to certain example embodiments are illustrated. In certain example embodiments, the apparatus 10 may be an element in a communication network or associated with such a network, such as a UE, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. It should be noted that a person skilled in the art will understand that the apparatus 10 may include Figure 9 Components or features not shown.

[0071] In some example embodiments, the apparatus 10 may include: one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some example embodiments, the apparatus 10 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that persons of ordinary skill in the art will understand that the apparatus 10 may include Figure 9 Components or features not shown.

[0072] like Figure 9 As shown in the example of , the device 10 may include or be coupled to a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general-purpose or special-purpose processor. In fact, as an example, the processor 12 may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 9 A single processor 12 is shown in FIG. 1 , but according to other example embodiments, multiple processors may be used. For example, it should be understood that in some example embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case processor 12 may represent a multiprocessor). According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0073] Processor 12 may perform functions associated with the operation of apparatus 10, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of apparatus 10, including Figure 3-Figure 8 The process and examples shown.

[0074] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that can be executed by the processor 12. The memory 14 may be one or more memories and of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer-readable medium. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enable the device 10 to perform the tasks described herein.

[0075] In certain example embodiments, the apparatus 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disc, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the apparatus 10 to perform a program or operation. Figure 3-Figure 8 Any methods and examples shown.

[0076] In some example embodiments, the apparatus 10 may further include or be coupled to one or more antennas 15 for receiving downlink signals and for transmitting from the apparatus 10 via the UL. The apparatus 10 may further include a transceiver 18 configured to send and receive information. The transceiver 18 may further include a radio interface (e.g., a modem) coupled to the antenna 15. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or UL, such as OFDMA symbols.

[0077] For example, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15, and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other example embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 10 may include input and / or output devices (I / O devices). In certain example embodiments, the apparatus 10 may also include a user interface, such as a graphical user interface or a touch screen.

[0078] In certain example embodiments, memory 14 stores software modules that provide functionality when executed by processor 12. These modules may include, for example, an operating system that provides operating system functionality for device 10. Memory may also store one or more functional modules, such as applications or programs, that provide additional functionality for device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, device 10 may optionally be configured to communicate with device 20 via a wireless or wired communication link 70 according to any radio access technology, such as NR.

[0079] According to certain example embodiments, processor 12 and memory 14 may be included in, or may form part of, processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 18 may be included in, or may form part of, transceiver circuitry.

[0080] like Figure 9 As shown in the example of , the device 20 may be a network, a core network element, or an element in a communication network, or associated with such a network, such as a gNB, a cell, or a NW. It should be noted that a person skilled in the art will understand that the device 20 may include Figure 9 Components or features not shown.

[0081] like Figure 9 As shown in the example of , the device 20 may include a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general-purpose or special-purpose processor. For example, as an example, the processor 22 may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 9A single processor 22 is shown in FIG. 1 , but according to other example embodiments, multiple processors may be used. For example, it should be understood that in some example embodiments, apparatus 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case processor 22 may represent a multiprocessor). In some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0082] According to certain example embodiments, processor 22 may perform functions related to the operation of apparatus 20, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of apparatus 20, including Figure 3-Figure 8 The process and examples shown.

[0083] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that can be executed by the processor 22. The memory 24 may be one or more memories and of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer-readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enable the device 20 to perform the tasks described herein.

[0084] In certain example embodiments, the apparatus 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 22 and / or the apparatus 20 to perform a program or operation. Figure 3-Figure 8 Methods and examples shown.

[0085] In certain example embodiments, apparatus 20 may further include or be coupled to one or more antennas 25 for transmitting signals and / or data to apparatus 20 and for receiving signals and / or data from apparatus 20. Apparatus 20 may further include or be coupled to a transceiver 28 configured to transmit and receive information. Transceiver 28 may include, for example, a plurality of radio interfaces that may be coupled to antenna(s) 25. The radio interfaces may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, and the like. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, and the like to generate symbols for transmission via one or more downlinks and to receive symbols (e.g., via the UL).

[0086] Thus, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 25, and to demodulate information received via the antenna(s) 25 for further processing by other elements of the apparatus 20. In other example embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 20 may include input and / or output devices (I / O devices).

[0087] In certain example embodiments, memory 24 may store software modules that provide functionality when executed by processor 22. These modules may include, for example, an operating system that provides operating system functionality for device 20. Memory may also store one or more functional modules, such as applications or programs, that provide additional functionality for device 20. The components of device 20 may be implemented in hardware, or as any suitable combination of hardware and software.

[0088] According to some example embodiments, the processor 22 and the memory 24 may be included in the processing circuit system or the control circuit system, or may form part of the processing circuit system or the controller circuit system. In addition, in some example embodiments, the transceiver 28 may be included in the transceiver circuit system, or may form part of the transceiver circuit system.

[0089] As used herein, the term "circuitry" may refer to a pure hardware circuit implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of a hardware processor(s) (including a digital signal processor) with software that works together to enable a device (e.g., devices 10 and 20) to perform various functions, and / or hardware circuit(s) and / or processor(s) or portions thereof that operate using software but which may not be present when not required for operation. As another example, as used herein, the term "circuitry" may also encompass an implementation of only a hardware circuit or processor (or multiple processors), or portions of a hardware circuit or processor, and their accompanying software and / or firmware. The term circuitry may also encompass, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0090] For example, in certain example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to receive, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. Apparatus 20 may also be controlled by memory 24 and processor 22 to receive, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message may include a second configuration of the second centralized unit network element. Apparatus 20 may also be controlled by memory 24 and processor 22 to determine that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks in the public land mobile networks sharing the distributed radio access node. Furthermore, apparatus 20 may be controlled by memory 24 and processor 22 to determine that the first configuration and the second configuration are different. Furthermore, the apparatus 20 may be controlled by the memory 24 and the processor 22 to determine whether to send a feedback message to the second centralized cell network element, the feedback message including a configuration list including at least the first configuration or the current operating configuration. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to determine, based on a response of the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to send a final response message to the second centralized cell network element indicating a successful or failed setup, based on the determination based on the response of the second centralized cell network element to the feedback message.

[0091] In other example embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to send a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to send a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to receive a feedback message from the distributed radio access node at the second centralized unit network element, the feedback message including a configuration list including at least the first configuration or a current operating configuration. Furthermore, the apparatus 20 may be controlled by the memory 24 and the processor 22 to send, at the second centralized cell network element, an indication to the distributed radio access node in response to the feedback message as to whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the apparatus 20 may be controlled by the memory 24 and the processor 22 to receive, at the second centralized cell network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0092] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing a method, process, or any variants discussed herein. Examples of such components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for causing the execution of operations.

[0093] Certain example embodiments may also be directed to an apparatus comprising: means for receiving, in a distributed radio access node shared by two or more public land mobile networks, a first broadcast setup request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of the first centralized unit network element. The apparatus may also include means for receiving, in the distributed radio access node, a second broadcast setup request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain example embodiments, the second broadcast setup request message may include a second configuration of the second centralized unit network element. The apparatus may also include means for determining that the first broadcast session setup request message and the second broadcast session setup request message correspond to the same broadcast service shared by two of the public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may include means for determining that the first configuration and the second configuration are different. Furthermore, the apparatus may include means for determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list including at least the first configuration or a current operating configuration. The apparatus may further include: means for determining, based on a response of the second centralized cell network element to the feedback message, whether the second centralized cell network element can accept at least one of the configurations sent in the feedback message. The apparatus may further include: means for sending, to the second centralized cell network element, a final response message indicating successful or failed establishment, based on the determination based on the response of the second centralized cell network element to the feedback message.

[0094] Certain example embodiments may also be directed to an apparatus comprising: means for sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to certain example embodiments, the first broadcast setup request message may include a first configuration of a first centralized cell network element managed by one of the shared public land mobile networks. The apparatus may also include: means for sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node. According to certain example embodiments, the second broadcast setup request message may include a second configuration of a second centralized cell network element managed by another of the shared public land mobile networks. The apparatus may also include: means for receiving, at the second centralized cell network element, a feedback message from the distributed radio access node, the feedback message including a configuration list including at least the first configuration or a currently operating configuration. Furthermore, the apparatus may include: means for sending, at the second centralized cell network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed. Furthermore, the apparatus may include means for receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating a successful or failed establishment based on a response to the feedback message.

[0095] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages in avoiding having multiple configurations and, therefore, multiple broadcasts of the same data (multiple radio resource usages). For example, in some example embodiments, means may be provided between a shared gNB-DU and a non-shared gNB-CU so that desirable MBS RAN sharing features can be applied to such deployment scenarios.

[0096] A computer program product may include one or more computer executable components that, when executed, are configured to perform certain exemplary embodiments. The one or more computer executable components may be at least one software code or portion thereof. Modifications and configurations required to implement the functionality of certain exemplary embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). The software routine(s) may be downloaded to the device.

[0097] For example, the software or computer program code or part thereof may be in source code form, object code form or some intermediate form and may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, such carriers may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0098] In other example embodiments, the functions may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functions may be implemented as signals, non-tangible components that may be carried by electromagnetic signals downloaded from the Internet or other networks.

[0099] According to certain example embodiments, an apparatus (such as a node, device, or corresponding component) may be configured as a circuit system, a computer, or a microprocessor (such as a single-chip computer element), or a chipset, which includes at least a memory for providing storage capacity for arithmetic operations and an operation processor for performing arithmetic operations.

[0100] It will be readily understood by those skilled in the art that the above disclosure may be practiced with procedures in a different order, and / or with hardware elements in configurations different from those disclosed. Therefore, although the present disclosure has been described based on these example embodiments, certain modifications, variations, and alternative configurations will be readily apparent to those skilled in the art while remaining within the spirit and scope of the example embodiments. Although the above embodiments relate to 5G NR and LTE technologies, the above embodiments may also be applied to any other current or future 3GPP technologies, such as Advanced LTE, and / or fourth generation (4G) technologies.

[0101] Partial glossary:

[0102] 3GPP: Third Generation Partnership Project

[0103] 5G: Fifth Generation

[0104] 5GCN: 5G Core Network

[0105] 5GS: 5G system

[0106] BS: Base Station

[0107] CHO: Conditional Switch

[0108] eNB: Enhanced Node B

[0109] E-UTRAN: Evolved UTRAN

[0110] gNB: 5G or next generation NodeB

[0111] LTE: Long Term Evolution

[0112] NR: New Radio

[0113] NTN: Non-Terrestrial Network

[0114] NW: Network

[0115] RACH: Random Access Channel process

[0116] RE: Resource Element

[0117] RRC: Radio Resource Control

[0118] SSB: Synchronous Signal Block

[0119] UE: User Equipment

[0120] UL: Uplink

[0121] UPF: User Plane Function

Claims

1. A method comprising: In a distributed radio access node shared by two or more public land mobile networks, receiving a first broadcast setup request message from a first centralized cell network element managed by one of the shared public land mobile networks, wherein the first broadcast setup request message includes: a first configuration of the first centralized cell network element; receiving, in the distributed radio access node, a second broadcast setup request message from a second centralized cell network element managed by another one of the shared public land mobile networks, wherein the second broadcast setup request message includes: a second configuration of the second centralized cell network element; determining that the first broadcast session establishment request message and the second broadcast session establishment request message correspond to a same broadcast service shared by two of the public land mobile networks that share the distributed radio access node; determining that the first configuration and the second configuration are different; determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list, the configuration list including at least: the first configuration or a current operating configuration; determining, based on a response of the second centralized unit network element to the feedback message, whether the second centralized unit network element can accept at least one of the configurations sent in the feedback message; and Based on the determination according to the response of the second centralized unit network element to the feedback message, a final response message is sent to the second centralized unit network element indicating a successful or failed establishment.

2. The method according to claim 1, wherein the feedback message to the second centralized unit network element is a broadcast setup failure message, the broadcast setup failure message comprising: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

3. The method according to claim 1 or 2, wherein the response to the feedback message is a new broadcast setup request message sent by the second centralized unit network element, the new broadcast setup request message comprising: One configuration in the available configuration list proposed by the distributed radio access node, the available configuration list comprising at least: a currently ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element.

4. The method according to any one of claims 1 to 3, wherein the feedback message is a multicast radio bearer configuration update request message triggered by the distributed radio access node, the multicast radio bearer configuration update request message comprising: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

5. The method according to any one of claims 1 to 4, wherein the response to the feedback message is a multicast radio bearer configuration update success response or a multicast radio bearer configuration failure unsuccessful message, wherein the multicast radio bearer configuration update success response indicates that one of the available configurations can be accepted by the second centralized unit network element and can include one or more of the accepted configurations, and the multicast radio bearer configuration failure unsuccessful message indicates that none of the proposed available configurations can be accepted by the second centralized unit network element and can also include another configuration proposed by the second centralized unit network element.

6. The method according to any one of claims 1 to 5, wherein sending the final response message comprises: If the configuration received from a second centralized unit network element in the response to the feedback message is acceptable to the distributed radio access node, a broadcast setup response message is sent to the second centralized unit network element.

7. The method according to claim 6, wherein the final response message sent to the second centralized unit network element includes at least one of the following: the current operational configuration of the first centralized unit network element, or Any of the configurations included in the feedback message.

8. The method according to claim 6 or 7, wherein the distributed radio access node does not start additional broadcasts if the acceptable configuration received from the second centralized cell network element in the response to the feedback message corresponds to a current operational configuration of the second centralized cell network element, and wherein the distributed radio access node starts additional broadcasts if the acceptable configuration received from the second centralized unit network element in the response to the feedback message does not correspond to a current operational configuration of the second centralized unit network element.

9. The method according to any one of claims 1 to 8, wherein sending the final response message comprises: If the configuration received from the second centralized unit distributed unit in the response to the feedback message is not acceptable to the distributed radio access node, sending a broadcast setup failure message to the second centralized unit distributed unit.

10. The method according to any one of claims 1 to 9, wherein the broadcast setup response message comprises: An indication of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element.

11. The method according to any one of claims 1 to 10, wherein the first broadcast establishment request message comprises: A first parameter indicating whether the first centralized network element provides the broadcast service to at least one non-shared distributed radio access node.

12. The method according to any one of claims 1 to 11, wherein the second broadcast establishment request message comprises: A second parameter indicating whether the second centralized network element provides the broadcast service to at least one non-shared distributed radio access node.

13. The method according to any one of claims 1 to 12, wherein the indication in the broadcast setup response message of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element is based on at least one of the following: a parameter received from the first centralized network element and the second centralized network element, the parameter indicating whether the first centralized network element and the second centralized network element provide services to a non-shared distributed radio access node, or A centralized network element from which said final configuration has been accepted.

14. A method comprising: sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks, wherein the first broadcast setup request message includes: a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks; sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node, wherein the second broadcast setup request message includes: a second configuration of a second centralized unit network element managed by another one of the shared public land mobile networks; receiving, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message comprising a configuration list, the configuration list comprising at least: the first configuration or a current operating configuration; sending, at the second centralized unit network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed; and At the second centralized unit network element, a final response message is received from the distributed radio access node indicating a successful or failed establishment based on the response to the feedback message.

15. The method according to claim 14, wherein the feedback message is a broadcast setup failure message, and the broadcast setup failure message includes: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

16. The method according to claim 14 or 15, wherein the indication in the response to the feedback message comprises a new broadcast setup request message, the new broadcast setup request message comprising: One available configuration in the available configuration list proposed by the distributed radio access node, the available configuration list comprising at least: a currently ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element.

17. The method according to any one of claims 14 to 16, wherein the feedback message is a multicast radio bearer configuration update request message triggered by the distributed radio access node, the multicast radio bearer configuration update request message comprising: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

18. The method according to any one of claims 14 to 17, wherein the indication in the response to the feedback message is a multicast radio bearer configuration update success indication or a multicast radio bearer configuration failure unsuccessful message, the multicast radio bearer configuration update success indication indicates that: one of the available configurations can be accepted by the second centralized unit network element and can include one or more of the accepted configurations, and the multicast radio bearer configuration failure unsuccessful message indicates that: none of the proposed available configurations can be accepted by the second centralized unit network element and can include another configuration proposed by the second centralized unit network element.

19. The method according to any one of claims 14 to 18, wherein receiving the final response message comprises: If the configuration sent in the response to the feedback message is acceptable to the distributed radio access node, a broadcast setup response message is received at the second centralized unit network element.

20. The method according to any one of claims 14 to 19, wherein the final response message includes at least one of the following: the current operational configuration of the first centralized unit network element, or Any of the configurations included in the feedback message.

21. The method according to any one of claims 14 to 20, Receiving the final response message includes: A broadcast setup failure message is received at the second centralized unit network element if the configuration sent in the response to the feedback message is unacceptable to the distributed radio access node.

22. The method according to any one of claims 14 to 21, wherein the broadcast setup response message comprises: An indication of whether a user plane tunnel should be established between the distributed radio network node and the second centralized unit network element.

23. The method according to any one of claims 14 to 22, wherein the first broadcast setup request message comprises: A first parameter indicating whether the first centralized network element provides the broadcast service to at least one non-shared distributed unit network element.

24. The method according to any one of claims 14 to 23, wherein the second broadcast setup request message comprises: A second parameter indicating whether the second centralized network element provides the broadcast service to at least one non-shared distributed unit network element.

25. The method according to any one of claims 14 to 24, wherein the indication in the broadcast setup response message of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element is based on at least one of the following: parameters received from the first centralized network element and the second centralized network element, the parameters indicating whether the first centralized network element and the second centralized network element provide the broadcast service to at least one non-shared distributed element network element, or A centralized network element from which said final configuration has been accepted.

26. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, in the case of storing instructions, when the instructions are executed by the at least one processor, cause the apparatus to at least: In the apparatus being a distributed radio access node shared by two or more public land mobile networks, receiving a first broadcast setup request message from a first centralized cell network element managed by one of the shared public land mobile networks, wherein the first broadcast setup request message includes: a first configuration of the first centralized cell network element; In the apparatus, a second broadcast setup request message is received from a second centralized cell network element managed by another one of the shared public land mobile networks, wherein the second broadcast setup request message includes: a second configuration of the second centralized cell network element; determining that the first broadcast session establishment request message and the second broadcast session establishment request message correspond to a same broadcast service shared by two of the public land mobile networks that share the apparatus; determining that the first configuration and the second configuration are different; determining whether to send a feedback message to the second centralized unit network element, the feedback message including a configuration list, the configuration list including at least: the first configuration or a current operating configuration; determining, based on a response of the second centralized unit network element to the feedback message, whether the second centralized unit network element can accept at least one of the configurations sent in the feedback message; and Based on the determination according to the response of the second centralized unit network element to the feedback message, a final response message is sent to the second centralized unit network element indicating a successful or failed establishment.

27. The apparatus of claim 26, wherein the feedback message to the second centralized unit network element is a broadcast setup failure message, the broadcast setup failure message comprising: A list of available configurations proposed by the apparatus, the list of available configurations comprising at least: the current operating configuration or the first configuration.

28. The apparatus according to claim 26 or 27, wherein the response to the feedback message is a new broadcast setup request message sent by the second centralized unit network element, the new broadcast setup request message comprising: A configuration in the available configuration list proposed by the apparatus, the available configuration list including at least: a currently ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element.

29. The apparatus according to any one of claims 26 to 28, wherein the feedback message is a multicast radio bearer configuration update request message triggered by the apparatus, the multicast radio bearer configuration update request message comprising: A list of available configurations proposed by the apparatus, the list of available configurations comprising at least: the current operating configuration or the first configuration.

30. The apparatus according to any one of claims 26 to 29, wherein the response to the feedback message is a multicast radio bearer configuration update success response or a multicast radio bearer configuration failure unsuccessful message, wherein the multicast radio bearer configuration update success response indicates that one of the available configurations can be accepted by the second centralized unit network element and can include one or more of the accepted configurations, and the multicast radio bearer configuration failure unsuccessful message indicates that none of the proposed available configurations can be accepted by the second centralized unit network element and can also include another configuration proposed by the second centralized unit network element.

31. The apparatus according to any one of claims 26 to 30, wherein sending the final response message comprises: If the configuration received from a second centralized unit network element in the response to the feedback message is acceptable to the device, a broadcast setup response message is sent to the second centralized unit network element.

32. The apparatus of claim 31 , wherein the final response message sent to the second centralized unit network element comprises at least one of the following: the current operational configuration of the first centralized unit network element, or Any of the configurations included in the feedback message.

33. The device according to claim 31 or 32, wherein if the acceptable configuration received from the second centralized unit network element in the response to the feedback message corresponds to the current operational configuration of the second centralized unit network element, the apparatus does not initiate additional broadcasts, and Wherein if the acceptable configuration received from the second centralized unit network element in the response to the feedback message does not correspond to a current operational configuration of the second centralized unit network element, the apparatus initiates an additional broadcast.

34. The apparatus according to any one of claims 26 to 33, wherein sending the final response message comprises: If the configuration received from the second centralized unit distributed unit in the response to the feedback message is not acceptable for the device, a broadcast setup failure message is sent to the second centralized unit distributed unit.

35. The apparatus according to any one of claims 26 to 34, wherein the broadcast setup response message comprises: An indication of whether a user plane tunnel should be established between the device and the second centralized unit network element.

36. The apparatus according to any one of claims 26 to 35, wherein the first broadcast setup request message comprises: A first parameter indicating whether the first centralized network element provides the broadcast service to at least one non-shared distributed radio access node.

37. The apparatus according to any one of claims 26 to 36, wherein the second broadcast setup request message comprises: A second parameter indicating whether the second centralized network element provides the broadcast service to at least one non-shared distributed radio access node.

38. The apparatus of any one of claims 26 to 38, wherein the indication in the broadcast setup response message of whether a user plane tunnel should be established between the apparatus and the second centralized unit network element is based on at least one of the following: a parameter received from the first centralized network element and the second centralized network element, the parameter indicating whether the first centralized network element and the second centralized network element provide services to a non-shared distributed radio access node, or A centralized network element from which said final configuration has been accepted.

39. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, in the case of storing instructions, when the instructions are executed by the at least one processor, cause the apparatus to at least: sending a first broadcast setup request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks, wherein the first broadcast setup request message includes: a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks; sending a second broadcast setup request message corresponding to the broadcast service to the distributed radio access node, wherein the second broadcast setup request message includes: a second configuration of a second centralized unit network element managed by another one of the shared public land mobile networks; receiving, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message comprising a configuration list, the configuration list comprising at least: the first configuration or a current operating configuration; sending, at the second centralized unit network element, an indication to the distributed radio access node in response to the feedback message: whether at least one of the configurations sent in the feedback message is acceptable or whether another configuration is proposed; and At the second centralized unit network element, a final response message is received from the distributed radio access node indicating a successful or failed establishment based on the response to the feedback message.

40. The apparatus according to claim 39, wherein the feedback message is a broadcast setup failure message, and the broadcast setup failure message comprises: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

41. The apparatus of claim 39 or 40, wherein the indication in the response to the feedback message comprises a new broadcast setup request message, the new broadcast setup request message comprising: One available configuration in the available configuration list proposed by the distributed radio access node, the available configuration list comprising at least: a currently ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element.

42. The apparatus according to any one of claims 39 to 41, wherein the feedback message is a multicast radio bearer configuration update request message triggered by the distributed radio access node, the multicast radio bearer configuration update request message comprising: A list of available configurations proposed by the distributed radio access node, the list of available configurations comprising at least: the current operating configuration or the first configuration.

43. An apparatus according to any one of claims 39 to 42, wherein the indication in the response to the feedback message is a multicast radio bearer configuration update success indication or a multicast radio bearer configuration failure unsuccessful message, the multicast radio bearer configuration update success indication indicates that: one of the available configurations can be accepted by the second centralized unit network element and can include one or more of the accepted configurations, and the multicast radio bearer configuration failure unsuccessful message indicates: none of the proposed available configurations can be accepted by the second centralized unit network element and can include another configuration proposed by the second centralized unit network element.

44. The apparatus of any one of claims 39 to 43, wherein receiving the final response message comprises: If the configuration sent in the response to the feedback message is acceptable to the distributed radio access node, a broadcast setup response message is received at the second centralized unit network element.

45. The apparatus according to any one of claims 39 to 44, wherein the final response message comprises at least one of the following: the current operational configuration of the first centralized unit network element, or Any of the configurations included in the feedback message.

46. ​​The device according to any one of claims 39 to 45, Receiving the final response message includes: A broadcast setup failure message is received at the second centralized unit network element if the configuration sent in the response to the feedback message is unacceptable to the distributed radio access node.

47. The apparatus according to any one of claims 39 to 46, wherein the broadcast setup response message comprises: An indication of whether a user plane tunnel should be established between the distributed radio network node and the second centralized unit network element.

48. The apparatus according to any one of claims 39 to 47, wherein the first broadcast setup request message comprises: A first parameter indicating whether the first centralized network element provides the broadcast service to at least one non-shared distributed unit network element.

49. The apparatus according to any one of claims 39 to 48, wherein the second broadcast setup request message comprises: A second parameter indicating whether the second centralized network element provides the broadcast service to at least one non-shared distributed unit network element.

50. The apparatus of any one of claims 39 to 49, wherein the indication in the broadcast setup response message of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element is based on at least one of: parameters received from the first centralized network element and the second centralized network element, the parameters indicating whether the first centralized network element and the second centralized network element provide the broadcast service to at least one non-shared distributed element network element, or A centralized network element from which said final configuration has been accepted.

51. A non-transitory computer-readable medium comprising program instructions stored thereon, the program instructions being for executing the method according to any one of claims 1 to 25.

52. An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any one of claims 1 to 25.

Images