Multicast and Broadcast Services in Disaggregated Shared Wireless Access Network Deployments

Abstract

The method may include receiving a first broadcast configuration request message. The method may further include receiving a second broadcast configuration request message from a second centralized unit network element managed by another sharing public land mobile network. The first broadcast session configuration request message and the second broadcast session configuration request message correspond to the same broadcast service shared by the two public land mobile networks that share a distributed radio access node. The first configuration and the second configuration may be different. Determine whether to send a feedback message to the second centralized unit network element and whether the second centralized unit network element can accept at least one of the configurations sent in the feedback message. A final response message indicating success or failure of the configuration is sent to the second centralized unit network element.

Description

[Technical Field]

[0001] This application claims priority to Indian Provisional Application No. 202341006508 filed on February 1, 2023, the contents of which are incorporated herein by reference in their entirety.

[0002] Some exemplary embodiments relate generally to mobile or wireless communication systems, such as Long Term Evolution (LTE) or fifth generation (5G) New Radio (NR) access technologies, 5G and beyond, or other communication systems. For example, certain exemplary embodiments may relate to apparatus, systems, and / or methods for multicast and broadcast services (MBS) in disaggregated shared radio access network (RAN) deployments. [Background technology]

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

[0004] Some exemplary embodiments relate to a method, including receiving, at a distributed radio access node shared by two or more public land mobile networks, a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message includes a first configuration for the first centralized unit network element. The method also includes receiving, at the distributed radio access node, a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message includes a second configuration for the second centralized unit network element. The method further includes determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the shared distributed radio access. Furthermore, the method may include determining that the first and second configurations 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 list of configurations, the list including at least the first configuration or a current operating configuration. The method includes determining whether the second centralization unit network element can accept at least one of the configurations sent in the feedback message based on a response to the feedback message from the second centralization unit network element, and further includes sending a final response message to the second centralization unit network element notifying success or failure of the configuration based on the determination based on the response to the feedback message from the second centralization unit network element.

[0005] Another exemplary embodiment relates to an apparatus. The apparatus may include at least one processor and at least one memory containing computer program code. When executed by the at least one processor, the at least one memory and the computer program code may configure the apparatus, at least in an apparatus that is a distributed radio access node shared by two or more public land mobile networks, to receive a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration of the first centralized unit network element. The apparatus may also be configured to receive a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks at the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration request message may include a second configuration of the second centralized unit network element. The apparatus may be further configured to determine that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks that share the shared distributed radio access. Further, the apparatus may be configured to determine that the first setting and the second setting differ. Further, the apparatus may be configured to determine whether to send a feedback message to the second concentrator network element including a list of settings, the list including at least the first setting or a current operating setting. The apparatus may be configured to determine whether the second concentrator network element can accept at least one of the settings sent in the feedback message based on a response of the second concentrator network element to the feedback message.The apparatus may be further configured to send a final response message to the second concentrating unit network element notifying success or failure of the configuration based on a determination based on the second concentrating unit network element's response to the feedback message.

[0006] Another exemplary embodiment relates to an apparatus. The apparatus may comprise means for receiving, at a distributed radio access node shared by two or more public land mobile networks, a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration of the first centralized unit network element. The apparatus may also comprise means for receiving, at the distributed radio access node, a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message includes a second configuration of the second centralized unit network element. The apparatus may further comprise means for determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may comprise means for determining that the first and second configurations are different. The apparatus may further comprise means for determining whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, the list including the first setting or the current operating setting. The apparatus may comprise means for determining whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element. The apparatus may further comprise means for sending a final response message to the second centralization unit network element, indicating success or failure of the setting, based on the determination based on the response to the feedback message from the second centralization unit network element.

[0007] According to another exemplary embodiment, a non-transitory computer-readable medium may be encoded with instructions that, when executed on hardware, perform a method. The method may include receiving, at a distributed radio access node shared by two or more public land mobile networks, a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to a particular exemplary embodiment, the first broadcast configuration request message includes a first configuration for the first centralized unit network element. The method may also include receiving, at the distributed radio access node, a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to a particular exemplary embodiment, the second broadcast configuration request message includes a second configuration for the second centralized unit network element. The method may further include determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the distributed radio access node. Furthermore, the method may include determining that the first configuration and the second configuration are different. The method may further include determining whether to send a feedback message to the second centralization unit network element including a list of settings, including the first setting or the current operating setting. The method includes determining whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element. The method further includes sending a final response message to the second centralization unit network element notifying success or failure of the setting based on the determination based on the response to the feedback message from the second centralization unit network element.

[0008] Another exemplary embodiment relates to a computer program product for performing the method. The method includes receiving, at a distributed radio access node shared by two or more public land mobile networks, a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message includes a first configuration of the first centralized unit network element. The method may also include receiving, at the distributed radio access node, a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message includes a second configuration of the second centralized unit network element. The method may further include determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two 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. The method may further include determining whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings including at least the first setting or the current operating setting. The method includes determining whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element. The method further includes sending a final response message to the second centralization unit network element notifying success or failure of the setting based on the determination based on the response to the feedback message from the second centralization unit network element.

[0009] Another exemplary embodiment relates to an apparatus, in a distributed radio access node shared by two or more public land mobile networks, including circuitry configured to receive a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration for the first centralized unit network element. The apparatus may also include circuitry configured to receive a second broadcast configuration request message to the distributed radio access node from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message may include a second configuration for the second centralized unit network element. The apparatus may further include circuitry configured to determine that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may include circuitry configured to determine that the first and second configurations are different. Further, the apparatus may include circuitry configured to determine whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, including the first setting or the current operating setting. The apparatus may also include circuitry configured to determine whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element. The apparatus may include circuitry configured to send a final response message to the second centralization unit network element, indicating success or failure of the setting based on the response to the feedback message from the second centralization unit network element.

[0010] Certain exemplary embodiments relate to a method. The method includes transmitting a first broadcast configuration 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 exemplary embodiments, the first broadcast configuration request message includes a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The method also includes transmitting a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration 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 further include receiving, at the second centralized unit network element, a feedback message from the distributed radio access node including a list of configurations including at least the first configuration or a current operating configuration. Furthermore, the method may include, in response to the feedback message, transmitting, at the second centralized unit network element, a notification to the distributed radio access node indicating whether at least one of the configurations transmitted in the feedback message is acceptable or whether another configuration is proposed. Further, the method may include receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on a response to the feedback message.

[0011] Another exemplary embodiment relates to an apparatus. The apparatus may include at least one processor and at least one memory containing computer program code. When executed by the at least one processor, the at least one memory and the computer program code may be configured to cause the apparatus to transmit a first broadcast configuration request message corresponding to a broadcast service to at least a distributed radio access node shared by two or more public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration 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 configured to transmit a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. Furthermore, the apparatus may be configured to receive, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a list of configurations including at least the first configuration or a current operating configuration. The apparatus is further configured, in the second centralized unit network element, to respond to the feedback message by sending a notification to the distributed radio access node whether at least one of the settings sent in the feedback message is acceptable or not, or to suggest another setting. The apparatus is further configured, in the second centralized unit network element, to receive, from the distributed radio access node, a final response message notifying success or failure of the setting based on the response to the feedback message.

[0012] Another exemplary embodiment relates to an apparatus. The apparatus may include means for transmitting a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to a specific exemplary embodiment, the first broadcast configuration 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 include means for transmitting a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to a specific exemplary embodiment, the second broadcast configuration 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 further include means, at the second centralized unit network element, for receiving from the distributed radio access node a feedback message including a list of configurations including at least the first configuration or a current operational configuration. The apparatus may further include means, at the second centralized unit network element, for, in response to the feedback message, transmitting a notification to the distributed radio access node regarding whether at least one of the configurations transmitted in the feedback message is acceptable or not, or for suggesting another configuration. Furthermore, the apparatus may comprise means for receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on a response to the feedback message.

[0013] According to another exemplary embodiment, a non-transitory computer-readable medium may have encoded thereon instructions that, when executed on hardware, perform a method. The method may include sending a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to a particular exemplary embodiment, the first broadcast configuration 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 configuration request message corresponding to the broadcast service to the distributed radio access node. According to a particular exemplary embodiment, the second broadcast configuration 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 further include receiving, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a list of configurations including at least the first configuration or a current operating configuration. Further, the method may include, in the second centralized unit network element, in response to the feedback message, sending a notification to the distributed radio access node whether at least one of the configurations sent in the feedback message is acceptable or not, or proposing another configuration. Further, the method may include, in the second centralized unit network element, receiving from the distributed radio access node a final response message notifying success or failure of the configuration based on the response to the feedback message.

[0014] Another exemplary embodiment relates to a computer program product for performing a method. The method may include transmitting a first broadcast configuration 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 exemplary embodiments, the first broadcast configuration 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 transmitting a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration 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 further include receiving, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a list of configurations including at least the first configuration or a current operating configuration. Furthermore, the method may include, in response to the feedback message, transmitting, at the second centralized unit network element, a notification to the distributed radio access node indicating whether at least one of the configurations transmitted in the feedback message is acceptable or whether another configuration is proposed. Further, the method may include receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on a response to the feedback message.

[0015] Another exemplary embodiment relates to an apparatus including circuitry configured to transmit a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to a particular exemplary embodiment, the first broadcast configuration 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 include circuitry configured to transmit a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to a particular exemplary embodiment, the second broadcast configuration request message includes a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The apparatus may further include circuitry configured to receive, at the second centralized unit network element, a feedback message from the distributed radio access node, the feedback message including a list of configurations including at least the first configuration or a current operational configuration. The apparatus may further include circuitry at the second centralized unit network element for, in response to the feedback message, transmitting a notification to the distributed radio access node regarding whether at least one of the configurations transmitted in the feedback message is acceptable or not, or for suggesting another configuration. Further, the apparatus may include a circuit for receiving, at the second centralization unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on a response to the feedback message. [Brief explanation of the drawings]

[0016] For an appreciation of the exemplary embodiments, please refer to the accompanying drawings. [Figure 1] Figure 1 shows an example deployment scenario. [Figure 2] FIG. 2 shows an example of a broadcast context setup procedure. [Figure 3] FIG. 3 illustrates an example of a signal flow diagram in accordance with certain illustrative embodiments. [Figure 4] FIG. 4 illustrates another exemplary signal flow diagram in accordance with certain exemplary embodiments. [Figure 5] FIG. 5 illustrates another exemplary signal flow diagram in accordance with certain exemplary embodiments. [Figure 6] FIG. 6 illustrates yet another signal flow diagram in accordance with certain exemplary embodiments. [Figure 7] FIG. 7 illustrates an exemplary flow chart of a method according to certain exemplary embodiments. [Figure 8] FIG. 8 illustrates an exemplary flowchart of another method in accordance with certain exemplary embodiments. [Figure 9] FIG. 9 illustrates a series of devices in accordance with certain exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0017] It will be readily understood that the components of the specific exemplary embodiments, as generally described and illustrated in the Figures herein, could be arranged and designed in a wide variety of different configurations. Following are detailed descriptions of several exemplary embodiments of systems, methods, apparatuses, and computer program products for MBS broadcast (multicast and broadcast services) in a disaggregated shared RAN deployment. For example, certain exemplary embodiments may be directed to MBS broadcast in a disaggregated shared RAN deployment.

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

[0019] As used herein, "at least one of: " and "at least one " and similar expressions, when a list of two or more elements is connected by "and" or "or", mean at least any element, or at least two or more elements, or at least all elements.

[0020] The 3rd Generation Partnership Project (3GPP®) technical specifications describe improvements to the identification and evaluation of 5GS architectures for providing MBS. Various solutions have been proposed, including providing a common temporary mobile group identifier (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 by an application function (AF). In another solution, each PLMN creates its own native TMGI for the same service. However, additional information may be sent to the shared NG-RAN node so that the NG-RAN node understands that both TMGIs refer to the same service and transmits data only once over the air interface. In another solution, the shared NG-RAN node may be configured with specific service IDs (e.g., six-digit numbers) for the TMGIs of the two PLMNs already configured with each of the shared partners' PLMN-IDs, corresponding to the same content or range of service IDs.

[0021] In a first solution, a 5G core network (CN) may send a common identifier (e.g., a source-specific multicast (SSM) address) along with a TMGI created individually by each 5G CN (for each PLMN) for the same service. When an NG-RAN node receives a common identifier SSM address along with a broadcast session creation request sent via different TMGIs from different core networks, the NG-RAN node understands that the different TMGIs belong to the same service. This allows the RAN node to transmit the same data only once on the air interface using the same G-Radio Network Temporary Identifier (G-RNTI). Furthermore, user equipment (UE) in a shared PLMN (e.g., UEs belonging to PLMN A, PLMN B, and PLMN C sharing a common NG-RAN node) receives data (and the corresponding physical downlink control channel (PDCCH)) corresponding to the same service only once, scrambled via the same G-RNTI.

[0022] In the second solution described above, the shared NG-RAN node may be configured such that TMGIs belong to the same broadcast session created by different 5G CNs, so that the NG-RAN understands that TMGIs sent from different PLMNs belong to the same service and may therefore send the same data only once on the air interface.

[0023] Various deployment options exist for aggregated and disaggregated NG-RAN types in MBS broadcast. Examples include, but are not limited to, aggregated gNBs, disaggregated gNBs, and options for sharing only specific cells within a gNB. In disaggregated gNBs, both the centralized unit (CU) and distributed unit (DU) may be shared. Additionally, for disaggregated gNBs, there may be an option to share only the DU but not the CU. The agreed-upon solution may directly impact the procedures and functionality of the specific deployment type under consideration.

[0024] In a deployment where only DUs are shared among multiple PLMNs and CUs are not, it can be assumed that the same MBS broadcast service is created by multiple CNs. Assuming the first solution (different native TMGIs per PLMN), each CN can send a separate broadcast configuration request to the shared gNB-DU. Figure 1 shows an example deployment scenario. In the example of Figure 1, 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 allocate the same radio resources to the different TMGIs (e.g., set the discontinuous reception (DRX) settings for the different TMGIs to the same value and transmit data only once). The deployment shown in Figure 1 can be achieved by the CU forwarding the same common information (i.e., SSM address) to the DU for each TMGI.

[0025] It is possible to determine whether there are multiple Next Generation Unit (NG-U) tunnels for each CN and whether there are multiple F1-U tunnels between different non-shared CUs and shared DUs. In some scenarios, one or more CUs may already be communicating the same service to other non-shared DUs, and therefore may already have F1-U tunnels created between them and NG-Us established with the CN.

[0026] 2 shows an example of a broadcast context setup procedure. For example, FIG. 2 shows a setup example of a disaggregated architecture in which the gNB-CU initiates the setup procedure by sending a broadcast context setup request (BROADCAST CONTEXT SETUP REQUEST) message to the gNB-DU at 200. The broadcast context setup request message is sent to the gNB-DU after the gNB-CU receives a broadcast setup request for an MBS service from the CN. If the gNB-DU successfully establishes the broadcast context, it returns a broadcast context setup response (BROADCAST CONTEXT SETUP RESPONSE) to the gNB-CU at 205.

[0027] In a "non-shared CU and shared DU" type deployment, the shared gNB-DU receives a broadcast context setup request from the 5G CN from gNB-CU-A, a non-shared CU, and a broadcast context setup request from CN-A containing the TMGI-A and other required configurations created by gNB-CU-A (e.g., multicast radio bearer (MRB), packet data convergence protocol (PDCP) configuration, etc.). The shared gNB-DU configures the information to broadcast to the UE. Furthermore, a short time later or simultaneously, the shared gNB-DU may receive another broadcast setup request for the same MBS broadcast service (e.g., a different MGI but with identification assistance for the first solution) from another non-shared CU (another 5G CN, gNB-CU-B in CN-B). The gNB-CU-B in CN-B may not be aware of the configuration (configured by gNB-CU-A) already configured for the same service for CN-A.

[0028] Because different non-shared gNB-CUs require different configurations, the shared gNB-DU may not be able to utilize shared NG-RAN optimizations. That is, the shared gNB-DU may not be able to transmit a single, unified configuration and data over the air for UEs in different shared PLMNs to receive, which may result in multiple redundant physical downlink control channels (PDCCHs) / physical downlink shared channels (PDSCHs) (MBS data). Furthermore, when more PLMNs / CNs share a common NG-RAN, more serious resource waste may occur. Therefore, certain exemplary embodiments described herein may provide a means of coordination between the shared gNB-DU and non-shared gNB-CUs, enabling the desired MBS RAN sharing functionality to be applied to this deployment scenario.

[0029] As described herein, certain exemplary embodiments may relate to a shared gNB-DU and multiple non-shared gNB-CUs for coordinating and optimizing MBS-specific radio resources in keeping with the RAN sharing objectives of 3GPP TR23.700-47 Rel-18. For example, in some exemplary embodiments, after a shared gNB-DU receives an MBS broadcast context setup request with TMGI-A (native TMGI+IPSSM for identification) from gNB-CU-A, along with other configuration details (e.g., MRB configuration, PDCP SN length, robust header compression (ROHC) parameters, t_reordering, etc.), the shared gNB-DU can use that information to configure a system information block 20 (SIB20) and a multicast control channel (MCCH) for broadcast using the G-RNTI (for UEs in the PLMNA). If the shared gNB-DU receives another subsequent broadcast context setup request, for example from gNB-CU-B, the shared gNB-DU has several options for continuing processing.

[0030] For example, in some exemplary 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 with or identical to that of CU-A, the shared gNB-DU can return a Broadcast Context Setup Response message to gNB-CU-B indicating successful setup. On the other hand, if the CU-B configuration differs from that of CU-A, the shared gNB-DU can send an F1 Broadcast Context Setup Failed message. Additionally, the shared gNB-DU can include an Available MRB Configuration Information Element (IE) containing the CU-A configuration (including all configurations sent by CU-A for this service). In other exemplary embodiments, the gNB-CU-B can attempt subsequent F1 AP Broadcast Setup Requests containing the CU-A configuration, if necessary.

[0031] According to other exemplary embodiments, a new Class 1 F1 Application Protocol (F1AP) MRB Configuration Update procedure can be introduced. In response to an F1AP Broadcast Context Request, the shared gNB-DU can trigger an F1AP MRB Configuration Update procedure to the gNB-CU-B. In some exemplary embodiments, the F1AP MRB Configuration Update procedure may include the F1AP MRB Configuration Update Request message, details of the CU-A's configuration. If the gNB-CU-B accepts the CU-A's configuration, the gNB-CU-B replies with an F1AP MRB Configuration Update Response message indicating success. Furthermore, upon receiving the F1AP MRB Configuration Update Response message, the shared gNB-DU replies with a Broadcast Context Setup Response message including the CU-A's configuration.

[0032] In certain exemplary embodiments, a new Class 1 F1AP MRB configuration update procedure may be provided. In some exemplary embodiments, upon receiving an F1AP broadcast context setup request, the shared gNB-DU may trigger an F1AP MRB configuration update procedure to 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 proposal to update / change the shared gNB-DU's configuration to the gNB-CU-A's configuration, the gNB-CU-B replies with an F1AP MRB configuration failure message to the shared gNB-DU. If the F1AP MRB configuration update failure message is received from the shared gNB-CU-B, the gNB-DU may use both configurations independently, which may result in two different data transmissions (i.e., the shared gNB-DU may replies with a broadcast configuration response message to the gNB-CU-B, including the originally requested CU-B configuration). This means that MBS broadcast data may be broadcast twice for two different TMGIs.

[0033] Alternatively, in other exemplary embodiments, upon receiving an F1AP MRB Configuration Update Failure message from the gNB-CU-B, the shared gNB-DU can continue to proceed with a single configuration that is transparent to the gNB-CU. For example, the shared gNB-DU replies with a Broadcast Configuration Failure message for the original requested CU-B configuration in the Broadcast Configuration Request message. This means that the shared gNB-DU continues broadcasting using only CU-A's configuration. In certain exemplary embodiments, each time the shared gNB-DU sends a successful broadcast configuration response to the gNB-CU control plane, the shared gNB-DU can include a new notification (i.e., "ignore DU DL Tunnel Endpoint Identifier (TEID)") to indicate whether to request an F1-U tunnel configuration with the corresponding gNB-CU user plane if the configuration is not requested.

[0034] According to other exemplary embodiments, in the broadcast context setup request, the gNB-CU may also send a new DU non-shared state parameter to the shared gNB-DU indicating whether the gNB-CU is already serving one or more non-shared gNB-DUs. The receiving shared gNB-DU then takes this new parameter into account when deciding which F1-U tunnel to set up (i.e., determining the new "ignore DU DL TEID" setting). For example, in some exemplary embodiments, if the shared gNB-DU receives a parameter indicating that the gNB-CU is already serving one or more non-shared DUs, it may prioritize setting up an F1-U tunnel with a specific gNB-CU UP because an NG-U interface has already been established between this gNB-CU and its CN to serve these non-shared gNB-DUs.

[0035] In a particular exemplary embodiment, the shared gNB-DU receives a first broadcast context from any gNB-CU and immediately shares its configuration details with all connected gNB-CUs (without waiting for individual requests). If the shared gNB-DU in this embodiment receives different, incompatible configurations from different gNB-CUs, it does not enable MBS RAN sharing optimization. Instead, the shared gNB-DU treats services for UEs in different PLMNs as if they were different services from different PLMNs.

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

[0037] In certain exemplary embodiments, the shared gNB-DU receives an initial broadcast context setup request and waits until it receives subsequent broadcast context setup requests from other gNB-CUs (that share the same gNB-DU). Further, the shared gNB-DU may randomly select one of the configurations (e.g., any one) and update the same configuration for the remaining gNB-CUs.

[0038] According to certain exemplary embodiments, an operation and maintenance (O&M) platform can configure a gNB-CU with a set of settings for TMGI that enable identification of identical broadcast services (i.e., broadcast sessions sharing the same broadcast service). This means that the O&M pre-configures some settings in each non-shared gNB-CU with a shared gNB-DU within the coverage area of ​​the broadcast session. For example, the O&M platform can configure rules for quality of service (QoS) flows to MRBs. For example, all QoS flows of a particular broadcast service can be mapped to the same MRB, or each can be mapped to a different MRB. This ensures that MRB mappings sent from different non-shared gNB-CUs to shared gNB-DUs are identical. In other exemplary embodiments, the O&M platform can also configure PDCP settings, including reordering timers and PDCP SN lengths. Additionally, the O&M platform can configure ROHC settings.

[0039] 3 illustrates an example of a signal flow diagram according to certain exemplary embodiments. At 300, an Application Management Function (AMF) may initiate Next Generation Application Protocol (NGAP) broadcast configuration for gNB-CU-A. At 305, a shared gNB-DU may receive an F1 broadcast configuration request from gNB-CU-A. According to some exemplary embodiments, the CU-A configuration may include an MRB ID, a PDCP SN length, and a ROHC. According to other exemplary embodiments, the F1 broadcast configuration request message may include a "DU non-shared state" parameter that indicates 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 initiates NGAP broadcast configuration for gNB-CU-B.

[0040] At 315, the shared gNB-DU receives an F1 broadcast configuration request from gNB-CU-B, including CU-B's MRB configuration. CU-B's configuration includes an MRB ID, PDCP SN length, and ROHC. In some exemplary embodiments, the F1 broadcast configuration request message from gNB-CU-B may also include a "DU non-shared state" parameter indicating whether gNB-CU-B is already serving one or more other non-shared DUs. At 320, the shared gNB-DU determines that CU-B's configuration is identical to CU-A's configuration. Therefore, the shared gNB-DU accepts the F1 configuration context and sends an F1 broadcast configuration response message to gNB-CU-B. In other exemplary embodiments, if the shared gNB-DU determines that CU-B's configuration is not identical to CU-A's configuration, then at 325, the shared gNB-DU sends gNB-CU's configuration to gNB-CU-B in an F1 AP broadcast configuration response. In certain exemplary embodiments, the shared gNB-DU may be configured to recognize that the gNB-CU-B is ready to accept either another running configuration from the gNB-CU-A or a configuration executed by the gNB-CU-A that conforms to a predetermined policy.

[0041] According to certain example embodiments, in both operations 320 and 325, the shared gNB-DU may also include in the F1 broadcast configuration response message a new notification "ignore DU DL TEID" indicating whether an F1-U tunnel should be established between the shared gNB-DU and gNB-CU-B. Because the DU DL TEID is now mandatory in the response message, an indicator may be included indicating whether the DU DL TEID should be ignored (i.e., only the F1-U between the shared gNB-DU and gNB-CU-A transmits data) or not (i.e., the F1-U between the shared gNB-DU and gNB-CU-B is an additional configuration for redundancy).

[0042] FIG. 4 illustrates another signal flow diagram according to certain exemplary embodiments. As shown in FIG. 4, operations 400 through 415 are similar to operations 300 through 315 in FIG. 3. At 420, the shared gNB-DU determines that CU-B's configuration is different from or incompatible with CU-A's configuration. Therefore, at 420, the shared gNB-DU transmits an F1 broadcast failure message including an available MRB configuration information element (IE), where the available MRB configuration IE includes the currently operating CU-A configuration obtained from gNB-CU-A. At 425, if gNB-CU-B is acceptable to operate according to CU-A's configuration, gNB-CU-B determines to resend an F1 broadcast configuration request message including CU-A's configuration. In some exemplary embodiments, the F1 broadcast configuration request message may also include a “DU non-sharing state” parameter indicating whether gNB-CU-B is already serving one or more other non-shared DUs.

[0043] At 430, the shared gNB-DU receives a broadcast configuration request from the gNB-CU-B, including an MRB configuration that matches the current CU-A configuration received from the shared gNB-DU. At 435, the shared gNB-DU may accept the F1 broadcast configuration request and send an F1 broadcast configuration response message to the gNB-CU-B. In some exemplary embodiments, the F1 broadcast configuration request message sent at 430 may include a "DU non-shared state" parameter that indicates whether the gNB-CU-B is already serving one or more other non-shared DUs. Additionally, similar to the exemplary embodiment described above with respect to FIG. 3, in some exemplary embodiments, the shared gNB-DU may include a new indicator "ignore DU DL TEID" at 435 that indicates whether additional F1-U tunnels should be used between the shared gNB-DU and the gNB-CU-B. Since the DU DL TEID may be mandatory in the broadcast configuration response message, the DU DL TEID includes an indicator indicating whether the DU DL TEID is ignored (i.e., only the F1-U between the shared gNB-DU and gNB-CU-A transmits data) or not (i.e., the F1-U between the shared gNB-DU and gNB-CU-BUP is an additional configuration for redundancy).

[0044] FIG. 5 illustrates another exemplary signal flow diagram in accordance with certain exemplary embodiments. As shown in FIG. 5, operations 500 through 515 are similar to operations 300 through 315 of FIG. 3. At 520, the shared gNB-DU may determine that the configuration of CU-B is different and / or incompatible with the configuration of CU-A. Thus, at 520, the shared gNB-DU may trigger a new MRB Configuration Update Request procedure to gNB-CU-B in the form of an F1AP MRB Configuration Update Request message. In some exemplary embodiments, the F1AP MRB Configuration Update Request message may include the current operating CU-A configuration from gNB-CU-A.

[0045] At 525, gNB-CU-B accepts to operate according to CU-A's configuration and notifies the shared gNB-DU of this acceptance by transmitting an F1 MRB Configuration Response message at 530. At 535, upon receiving the F1 MRB Configuration Response message from gNB-CU-B, the shared gNB-DU understands that gNB-CU-B will operate according to CU-A's configuration, and the shared gNB-DU provides a final response to gNB-CU-B using an F1 Broadcast Configuration Response message (including the CU-A configuration). According to certain exemplary embodiments, the F1 Broadcast Configuration Response message transmitted from the shared gNB-DU may include the CU-A configuration instead of the originally requested CU-B configuration. In some exemplary embodiments, including the CU-A configuration in the F1 Broadcast Configuration Response message at 535 is optional. In other words, gNB-CU-B may already consider the received broadcast configuration response to correspond to the CU-A configuration based on transmitting the response message at 530.

[0046] FIG. 6 shows another exemplary signal flow diagram according to a particular exemplary embodiment. As shown in FIG. 6, operations 600 to 615 are similar to operations 300 to 315 of FIG. 3, and operation 620 is similar to operation 520 of FIG. 5. In 625, the gNB-CU-B decides not to accept the configuration proposal for the CU-A configuration from the shared gNB-DU. In 630, the gNB-CU-B responds by sending a rejection response message to the shared gNB-DU. In 635, the shared gNB-DU decides to use the CU-A and CU-B configurations separately. By using both the CU-A and CU-B configurations separately, multiple data transmissions can be performed by the shared gNB-DU. For example, as shown in FIG. 6, in 635, the shared gNB-DU can send a broadcast configuration response to the gNB-CU-B that includes the originally requested CU-B configuration. This means that the shared gNB-DU operates to broadcast data twice for two different TMGIs. Additionally, in certain exemplary embodiments, the shared gNB-DU may add an additional notification indicating that the broadcast is inefficient because the two different broadcast data transmissions use separate radio resources, although this is optional as the gNB-CU-B can understand this from operation 630.

[0047] Alternatively, in another exemplary embodiment, the shared gNB-DU can continue with a single configuration that is transparent to the gNB-CU at 640. For example, at 640, the shared gNB-DU can return a broadcast configuration failure message to gNB-CU-B for the originally requested CU-B configuration, meaning that the shared gNB-DU will continue broadcasting using only CU-A's configuration.

[0048] 7 illustrates an example flow diagram of a method according to certain exemplary embodiments. In an exemplary embodiment, the method of FIG. 7 may be performed by a network entity or group of network elements in a 3GPP system, such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 7 may be performed by a network, a cell, a gNB, a gNB-DU, a gNB-CU, or other device similar to either of devices 10 or 20 illustrated in FIG. 9.

[0049] According to certain exemplary embodiments, the method of FIG. 7 includes, at 700, receiving a first broadcast configuration request message at a distributed radio access node shared by two or more public land mobile networks from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration of the first centralized unit network element. The method may also include, at 705, receiving a second broadcast configuration request message at the distributed radio access node from a second centralized unit network element managed by another shared public land mobile network. According to certain exemplary embodiments, the second broadcast configuration request message includes a second configuration of the second centralized unit network element. The method may further include, at 710, determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two 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. The method may further include determining, at 720, whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, the list including at least the first setting or the current operating setting. The method may also include determining, from a response from the second centralization unit network element to the feedback message, whether the second centralization unit network element can accept at least one of the settings sent in the feedback message, at 725. The method may further include, at 730, sending a final response message to the second centralization unit network element indicating success or failure of the configuration, based on the determination based on the response from the second centralization unit network element to the feedback message.

[0050] According to certain exemplary embodiments, the feedback message to the second centralized unit network element may be a broadcast configuration failure message containing a list of available configurations proposed by the distributed radio access node, including at least the current operational configuration or the first configuration. According to some exemplary embodiments, the response to the feedback message may be a new broadcast configuration request message sent by the second centralized unit network element containing one configuration from the list of available configurations proposed by the distributed radio access node, including at least the current ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element. According to other exemplary embodiments, the feedback message is a multicast radio bearer configuration update request message triggered by the distributed radio access node containing a list of available configurations proposed by the distributed radio access node, including at least the current operational configuration or the first configuration.

[0051] In certain exemplary embodiments, the response to the feedback message is 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 includes one or more of the accepted configurations. Alternatively, the response is a multicast radio bearer configuration failure message indicating that none of the available configurations was accepted by the second centralized unit network element and does not include other configurations proposed by the second centralized unit network element. In some exemplary embodiments, 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, sending the final response message may include sending a broadcast configuration response message to the second centralized unit network element. In other exemplary embodiments, the final response message sent to the second centralized unit network element may include at least one of the current operating configuration of the first centralized unit network element or any of the configurations included in the feedback message.

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

[0053] In certain exemplary embodiments, the broadcast configuration 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 exemplary embodiments, the first broadcast configuration request message may include a first parameter indicating whether the first centralized network element provides broadcast service to at least one unshared distributed radio access node. In some exemplary embodiments, the second broadcast configuration request message may include a second parameter indicating whether the second centralized network element provides broadcast service to at least one unshared distributed radio access node. In still other exemplary embodiments, the indication of whether a user plane tunnel should be established between the distributed radio access node and the second centralized unit network element in the broadcast configuration response message may be based on at least one of the parameters indicating whether to provide service to the unshared distributed radio access node received from the first and second centralized network elements or the centralized network element on which the final configuration was accepted.

[0054] 8 illustrates an example flow diagram of another method according to certain exemplary embodiments. In an exemplary embodiment, the method of FIG. 8 is performed by a network entity or group of network elements in a 3GPP system, such as LTE or 5G-NR. For example, in an exemplary embodiment, the method of FIG. 8 may be performed by a network, a cell, a gNB, a gNB-DU, a gNB-CU, or other device similar to either of devices 10 or 20 illustrated in FIG. 9.

[0055] According to certain exemplary embodiments, the method of FIG. 8 includes, at 800, transmitting a first broadcast configuration 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 exemplary embodiments, the first broadcast configuration 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, transmitting a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration 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 further include, at 810, receiving from the distributed radio access node, at the second centralized unit network element, a feedback message including a list of configurations including at least the first configuration or a current operating configuration. Further, the method may include, at the second centralized unit network element, in response to the feedback message, sending a notification to the distributed radio access node whether at least one of the configurations sent in the feedback message is acceptable or suggesting another configuration, at 815. Further, the method may include, at the second centralized unit network element, receiving from the distributed radio access node a final response message notifying success or failure of the configuration based on the response to the feedback message, at 820.

[0056] According to certain exemplary embodiments, the feedback message may be a broadcast configuration failure message containing a list of available configurations proposed by the distributed radio access node, including at least the current operational configuration or the first configuration. According to some exemplary embodiments, the notification to the feedback message may include a new broadcast configuration request message containing one of a list of available configurations proposed by the distributed radio access node, including at least the current ongoing configuration or the first configuration, or another configuration proposed by the second centralized unit network element. According to other exemplary embodiments, the feedback message is a multicast radio bearer configuration update request message triggered by the distributed radio access node, including a list of available configurations proposed by the distributed radio access node, including at least the current operational configuration or the first configuration.

[0057] In certain exemplary embodiments, the notification in response to the feedback message is a multicast radio bearer configuration update success notification indicating that one of the available configurations is acceptable by the second centralized unit network element and includes one or more of the accepted configurations, or a multicast radio bearer configuration failure message indicating that none of the available configurations was accepted by the second centralized unit network element and does not include other configurations proposed by the second centralized unit network element. In some exemplary embodiments, if the configuration sent in response to the feedback message is acceptable to the distributed radio access node, receiving a final response message includes receiving a broadcast configuration response message at the second centralized unit network element. In other exemplary embodiments, the final response message includes at least one of the current operating configuration of the first centralized unit network element or any of the configurations included in the feedback message.

[0058] According to certain exemplary embodiments, if the configuration sent in response to the feedback message is not accepted by the distributed radio access node, receiving the final response message may include receiving a broadcast configuration failure message at the second centralized unit network element. According to some exemplary embodiments, the broadcast configuration response message may include a notification indicating whether or not a user plane tunnel should be established between the distributed radio network node and the second centralized unit network element. According to other exemplary embodiments, the first broadcast configuration request message may include a first parameter indicating whether or not the first centralized network element provides a broadcast service to at least one non-shared distributed unit network element.

[0059] In certain exemplary embodiments, the second broadcast configuration request message may include a second parameter indicating whether the second centralized network element provides a broadcast service to at least one non-shared distributed unit network element. In some exemplary embodiments, the notification in the broadcast configuration response message of whether to set up a user plane tunnel between the distributed radio access node and the second centralized unit network element is based on at least one of the parameters received from the first and second centralized network elements indicating whether to provide a broadcast service to at least one non-shared distributed unit network element, or the centralized network element on which the final configuration was accepted.

[0060] 9 illustrates a set of apparatuses 10 and 20 according to certain exemplary embodiments. In certain exemplary embodiments, apparatus 10 may be an element in a communication network or an element associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, or other device. Note that those skilled in the art will understand that apparatus 10 may include components or functionality not illustrated in FIG. 9.

[0061] In some exemplary embodiments, device 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more wireless access components (e.g., modems, transceivers, etc.), and / or a user interface. In some exemplary embodiments, device 10 may be configured to operate using one or more wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MultiFire, and / or other wireless access technologies. Note that those skilled in the art will understand that device 10 may include components or features not shown in FIG. 9 .

[0062] As shown in the example of FIG. 9, device 10 may include or be connected to processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general-purpose or special-purpose processor. Indeed, processor 12 may be, for example, one or more general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on multi-core processor architectures. While a single processor 12 is shown in FIG. 9, according to other exemplary embodiments, multiple processors may be utilized. For example, it should be understood that in certain exemplary embodiments, device 10 may include two or more processors capable of forming a multiprocessor system capable of supporting multiprocessing (e.g., in this case, processor 12 may represent a multiprocessor). According to certain exemplary embodiments, the multiprocessor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

[0063] Processor 12 may perform functions related to the operation of device 10, including pre-coding antenna gain / phase parameters, encoding and decoding individual bits that make up communication messages, formatting information, and the processes and examples shown in Figures 3-8.

[0064] Device 10 may further include or be connected to memory 14 (internal or external) connected to processor 12 for storing information and instructions executable by processor 12. Memory 14 is one or more memories appropriate to the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, including semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic or optical disks, hard disk drives (HDDs), or other types of non-transitory machine- or computer-readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable device 10 to perform the tasks described herein.

[0065] In certain exemplary embodiments, device 10 may further include or be connected to a drive or port (internal or external) configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or other storage medium. For example, the external computer-readable storage medium may store computer programs or software executed by processor 12 and / or device 10 to perform any of the methods and examples shown in Figures 3-8.

[0066] In some demonstrative embodiments, device 10 may include or be connected to one or more antennas 15 for receiving downlink signals and transmitting from device 10 over the UL. Device 10 may further include a transceiver 18 configured to transmit and receive information. Transceiver 18 may include a radio interface (e.g., a modem) connected to antenna 15. The radio interface supports one or more radio access technologies, such as 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), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., for processing symbols, such as OFDMA symbols, transmitted over the downlink or UL.

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

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

[0069] According to certain exemplary embodiments, the processor 12 and memory 14 may be included in or form part of processing or control circuitry. Further, in some exemplary embodiments, the transceiver 18 may be included in or form part of transmitting and receiving circuitry.

[0070] As shown in the example of Figure 9, the device 20 may be a network, a core network element, or an element within a communications network or an element associated with such a network (e.g., a gNB, a cell, a NW, etc.). Those skilled in the art will understand that the device 20 may include components or functions not shown in Figure 9.

[0071] As shown in the example of FIG. 9, device 20 may include a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. For example, processor 22 may include one or more of 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), a processor based on a multi-core processor architecture, and the like. While a single processor 22 is shown in FIG. 9, multiple processors may be utilized according to other exemplary embodiments. For example, it should be understood that in certain exemplary embodiments, device 20 may include two or more processors capable of forming a multiprocessor system capable of supporting multiprocessing (e.g., in this case, processor 22 may represent a multiprocessor). In certain exemplary embodiments, the multiprocessor system may be tightly coupled (e.g., to form a computer cluster) or loosely coupled.

[0072] According to certain exemplary embodiments, processor 22 may perform functions related to the operation of device 20, including, for example, pre-coding antenna gain / phase parameters, encoding and decoding individual bits that make up communication messages, formatting information, and overall control of device 20, including the processes and examples shown in FIGS. 3-8.

[0073] Device 20 may further include or be connected to memory 24 (internal or external) connected to processor 22 for storing information and instructions executed by processor 22. Memory 24 may be one or more memories appropriate to 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, memory 24 may be comprised of any combination of random access memory (RAM), read-only memory (ROM), static storage such as magnetic or optical disks, hard disk drives (HDDs), or other types of non-transitory machine- or computer-readable media. The instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable device 20 to perform the tasks described herein.

[0074] In certain exemplary embodiments, device 20 may further include or be connected to a drive or port (internal or external) configured to accept and read an external computer-readable storage medium, such as an optical disk, USB drive, Flash drive, or other storage medium. For example, the external computer-readable storage medium may store computer programs or software executed by processor 22 and / or device 20 to perform the methods and embodiments illustrated in Figures 3-8.

[0075] In certain exemplary embodiments, device 20 may include or be connected to one or more antennas 25 for transmitting and receiving signals and / or data to and from device 20. Device 20 may further include or be connected to a transceiver 28 configured to transmit and receive information. Transceiver 28 may comprise, for example, multiple wireless interfaces connectable to antennas 25. The wireless interfaces may correspond to one or more wireless access technologies, such as GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identification (RFID), ultra-wideband (UWB), MulteFire, etc. The wireless interfaces may include components, such as filters, converters (e.g., digital-to-analog converters), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission over one or more downlinks and receive symbols (e.g., over the UL).

[0076] Thus, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna 25 and to demodulate information received by antenna 25 for further processing by other elements of device 20. In other exemplary embodiments, transceiver 18 may transmit and receive signals or data directly. Additionally or alternatively, in some exemplary embodiments, device 20 may include input and / or output devices (I / O devices).

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

[0078] According to some exemplary embodiments, the processor 22 and memory 24 may be included in or form part of processing or control circuitry. Further, in some exemplary embodiments, the transceiver 28 may be included in or form part of transmission and reception circuitry.

[0079] As used herein, the term "circuitry" refers to a hardware-only 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 with software (including a digital signal processor) that work together to cause a device (e.g., devices 10 and 20) to perform various functions, and / or a hardware circuit and / or processor, or portion thereof, that uses software in its operation but is absent if not necessary for operation. Furthermore, as used herein, the term "circuitry" also encompasses a mere hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, and its associated software and / or firmware implementation. The term circuitry also encompasses, for example, baseband integrated circuits in a server, cellular network node or device, or other computing or network device.

[0080] For example, in certain exemplary embodiments, device 20 is controlled by memory 24 and processor 22 to receive, at a distributed radio access node shared by two or more public land mobile networks, a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration of the first centralized unit network element. Device 20 is also controlled by memory 24 and processor 22 to receive, at the distributed radio access node, a second broadcast configuration request message from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message may include a second configuration of the second centralized unit network element. Device 20 is further controlled by memory 24 and processor 22 to determine that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the distributed radio access node. Furthermore, the device 20 is controlled by the memory 24 and the processor 22 to determine that the first setting and the second setting are different. Furthermore, the device 20 is controlled by the memory 24 and the processor 22 to determine whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, the list including at least the first setting or the current operating setting. The device 20 is controlled by the memory 24 and the processor 22 to determine whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element.The device 20 is further controlled by the memory 24 and the processor 22 and can send a final response message to the second centralization unit network element notifying the success or failure of the configuration based on a determination based on the response to the feedback message from the second centralization unit network element.

[0081] In another exemplary embodiment, the device 20, controlled by the memory 24 and the processor 22, can transmit a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks. According to a particular exemplary embodiment, the first broadcast configuration request message can include a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks. The device 20, controlled by the memory 24 and the processor 22, can also transmit a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to a particular example, the second broadcast configuration request message can include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. The device 20, further controlled by the memory 24 and the processor 22, can receive, from the distributed radio access node at the second centralized unit network element, a feedback message including a list of configurations including at least the first configuration or a current operating configuration. Furthermore, the apparatus 20 is controlled by the memory 24 and the processor 22 to instruct the distributed radio access node at the second centralized unit network element whether at least one of the settings transmitted in the feedback message is acceptable or not, or to suggest other settings, in response to the feedback message. Furthermore, the apparatus 20 is controlled by the memory 24 and the processor 22 to receive, at the second centralized unit network element, a final response message from the distributed radio access node notifying success or failure of the setting based on the response to the feedback message.

[0082] In some exemplary embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may comprise means for performing the methods, processes, or any variations thereof described herein, such as one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for performing the operations.

[0083] Certain exemplary embodiments are also directed to an apparatus, at a distributed radio access node shared by two or more public land mobile networks, comprising means for receiving a first broadcast configuration request message from a first centralized unit network element managed by one of the shared public land mobile networks. According to certain exemplary embodiments, the first broadcast configuration request message may include a first configuration of the first centralized unit network element. The apparatus may also comprise means for receiving a second broadcast configuration request message at the distributed radio access node from a second centralized unit network element managed by another of the shared public land mobile networks. According to certain exemplary embodiments, the second broadcast configuration request message includes a second configuration of the second centralized unit network element. The apparatus may further comprise means for determining that the first and second broadcast session configuration request messages correspond to the same broadcast service shared by the two public land mobile networks sharing the distributed radio access node. Furthermore, the apparatus may comprise means for determining that the first and second configurations are different. The apparatus may further comprise means for determining whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, the list including at least the first setting or the current operating setting. The apparatus may comprise means for determining whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element. The apparatus may further comprise means for sending a final response message to the second centralization unit network element notifying success or failure of the setting based on the determination based on the response to the feedback message from the second centralization unit network element.

[0084] Certain exemplary embodiments are also directed to an apparatus comprising means for transmitting a first broadcast configuration 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 exemplary embodiments, the first broadcast configuration 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 comprise means for transmitting a second broadcast configuration request message corresponding to the broadcast service to the distributed radio access node. According to certain exemplary embodiments, the second broadcast configuration request message may include a second configuration of a second centralized unit network element managed by another of the shared public land mobile networks. Furthermore, the apparatus may comprise means at the second centralized unit network element for receiving, from the distributed radio access node, a feedback message including a list of configurations including at least the first configuration or a current operational configuration. Furthermore, the apparatus may comprise means at the second centralized unit network element for, in response to the feedback message, transmitting to the distributed radio access node a notification of whether at least one of the configurations transmitted in the feedback message is acceptable or unacceptable, or for suggesting another configuration. Further, the apparatus may comprise means for receiving, at the second centralized unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on a response to the feedback message.

[0085] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages in terms of avoiding multiple configurations and thus multiple broadcasts of the same data (use of multiple radio resources). For example, in some example embodiments, means may be provided between a shared gNB-DU and a non-shared gNB-CU to enable desired MBS RAN sharing capabilities to be applied in such deployment scenarios.

[0086] The computer program product may include one or more computer-executable components configured to perform some exemplary embodiments when the program is executed. The one or more computer-executable components may be at least one software code or a portion thereof. The modifications and configurations necessary to implement the functionality of certain exemplary embodiments may be performed as routines and may be implemented as additional or updated software routines. The software routines may be downloaded to a device.

[0087] For example, the software or computer program code, or portions thereof, in source code form, object code form, or any intermediate form, may be stored on any carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of conveying a program. Such carriers include recording media, computer memory, read-only memory, optical, electrical, and / or electrical carrier signals, communications signals, and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed across several computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0088] In other exemplary embodiments, the functions may be performed by hardware or circuitry incorporated into a device (e.g., device 10 or device 20), for example, through the use of 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 other exemplary embodiments, the functions may be implemented as signals transmitted by non-tangible means, such as electromagnetic signals downloaded from the internet or other network.

[0089] According to certain exemplary embodiments, an apparatus such as a node, device, or corresponding component may be configured as a circuit, computer, or microprocessor such as a single-chip computer element, or as a chipset that includes a memory that provides storage capacity used for arithmetic operations and an arithmetic processor that performs the arithmetic operations.

[0090] Those of ordinary skill in the art will readily appreciate that the above disclosure can be implemented using procedures in a different order and / or hardware elements in different configurations than those disclosed. Accordingly, while the present disclosure has been described based on these exemplary embodiments, certain modifications, variations, and alternative configurations will be apparent to those skilled in the art while remaining within the scope of the exemplary embodiments. While the above embodiments refer to 5G NR and LTE technologies, the above embodiments may also be applied to other current or future 3GPP technologies, such as LTE-Advanced and / or fourth generation (4G) technologies.

[0091] Partial Glossary 3GPP (registered trademark) 3rd Generation Partnership Project 5G (5th Generation) 5G CN 5G Core Network 5GS 5G System BS base station CHO Conditional Handover eNB Enhanced Node B E-UTRAN Evolved UTRAN gNB 5G or Next Generation Node B LTE Long Term Evolution NR new radio NTN Non-Terrestrial Network NW Network RACH Random Access Channel Procedure RE Resource Element RRC Radio Resource Control SSB sync signal block UE User Equipment UL Uplink UPF User Plane Function

Claims

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

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

3. 3. The method of claim 1, wherein the response to the feedback message is a new broadcast configuration request message sent by the second centralization unit network element, the broadcast configuration request message including at least the current ongoing configuration or the first configuration, or one configuration from the list of available configurations proposed by the distributed radio access node, including other configurations proposed by the second centralization unit network element.

4. 4. The method according to claim 1, 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 including a list of available configurations proposed by the distributed radio access node, the list including at least the current operational configuration or the first configuration.

5. The response to the feedback message: a multicast radio bearer configuration update success response informing that one of the available configurations is acceptable by the second centralization unit network element and including one or more of the accepted configurations; or a multicast radio bearer setup failure message informing that none of the available configurations was accepted by the second centralization unit network element and further not including other configurations proposed by the second centralization unit network element.

5. The method according to any one of claims 1 to 4.

6. 6. The method of claim 1, wherein if the configuration received from the second centralization unit network element in response to the feedback message is acceptable to the distributed radio access node, sending the final response message comprises sending a broadcast configuration response message to the second centralization unit network element.

7. The final response message sent to the second centralization unit network element comprises: the current operational configuration of the first centralization unit network element; or Any of the settings included in the feedback message; The method of claim 6 , comprising at least one of:

8. if the acceptable configuration received from the second centralization unit network element in response to the feedback message corresponds to its current operational configuration, the distributed radio access node does not initiate an additional broadcast; if the acceptable configuration received from the second centralization unit network element in response to the feedback message does not correspond to its current operational configuration, the distributed radio access node initiates an additional broadcast.

8. The method according to claim 6 or 7.

9. 9. The method of claim 1, wherein if the configuration received from the second centralized unit distributed unit in response to the feedback message is not acceptable to the distributed radio access node, sending the final response message comprises sending a broadcast configuration failure message to the second centralized unit distributed unit.

10. The method according to claim 1 , wherein the broadcast configuration response message includes a notification of whether a user plane tunnel should be established between the distributed radio access node and the second centralization unit network element.

11. 11. The method according to claim 1, wherein the first broadcast configuration request message includes a first parameter indicating whether the first centralized network element provides the broadcast service to at least one unshared distributed radio access node.

12. 12. The method according to claim 1, wherein the second broadcast configuration request message includes a second parameter indicating whether the second centralized network element provides the broadcast service to at least one unshared distributed radio access node.

13. In the broadcast configuration response message, the notification of whether to set up a user plane tunnel between the distributed radio access node and the second centralization unit network element is: a parameter received from the first and second centralized network elements indicating whether to provide service to a non-shared distributed radio access node; or a centralized network element to which the final configuration has been accepted; The method according to any one of claims 1 to 12, based on at least one of:

14. sending a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks, the first broadcast configuration request message including a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks; sending, to the distributed radio access node, a second broadcast configuration request message corresponding to the broadcast service, the second broadcast configuration request message including 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 centralization unit network element, from the distributed radio access node, a feedback message including a list of configurations including at least the first configuration or a current operational configuration; in the second centralization unit network element, in response to the feedback message, sending a notification to the distributed radio access node whether at least one of the configurations sent in the feedback message is acceptable or not, or proposing another configuration; receiving, at the second centralization unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on the response to the feedback message; A method comprising:

15. 15. The method of claim 14, wherein the feedback message is a broadcast configuration failure message including a list of available configurations proposed by the distributed radio access node, including at least the current operational configuration or the first configuration.

16. 16. The method according to claim 14 or 15, wherein the notification to the feedback message comprises a new broadcast configuration request message including one of the list of available configurations proposed by the distributed radio access node, including at least the current ongoing configuration or the first configuration, or another configuration proposed by the second centralization unit network element.

17. 17. The method according to claim 14, 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 including a list of available configurations proposed by the distributed radio access node, the list including at least the current operational configuration or the first configuration.

18. The notification in response to the feedback message includes: a multicast radio bearer configuration update success notification informing that one of the available configurations is acceptable by the second centralization unit network element and including one or more of the accepted configurations; or a multicast radio bearer setup failure message informing that none of the available configurations was accepted by the second centralization unit network element and not including other configurations proposed by the second centralization unit network element; 18. The method of any one of claims 14 to 17.

19. 19. The method of claim 14, wherein if the configuration sent in the response to the feedback message is acceptable to the distributed radio access node, receiving the final response message comprises receiving a broadcast configuration response message at the second centralization unit network element.

20. The final response message: the current operational configuration of the first centralization unit network element; or Any of the settings included in the feedback message; 20. The method of claim 14, comprising at least one of:

21. 21. The method of claim 14, wherein if the configuration sent in the response to the feedback message is not accepted by the distributed radio access node, receiving the final response message comprises receiving a broadcast configuration failure message at the second centralization unit network element.

22. 22. The method according to claim 14, wherein the broadcast configuration response message includes a notification of whether to set up a user plane tunnel between the distributed radio network node and the second centralization unit network element.

23. 23. The method of claim 14, wherein the first broadcast configuration request message includes 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. 24. The method of claim 14, wherein the second broadcast configuration request message includes 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. In the broadcast configuration response message, the notification of whether to establish a user plane tunnel between the distributed radio access node and the second centralization unit network element is: a parameter received from the first and second centralized network elements indicating whether to provide the broadcast service to at least one non-shared distributed unit network element; or a centralized network element to which the final configuration has been accepted; 25. The method according to any one of claims 14 to 24, based on at least one of:

26. 1. An apparatus comprising: at least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, when executed by the at least one processor, cause the device to at least: In the device, which is a distributed radio access node shared by two or more public land mobile networks, receiving a first broadcast configuration request message from a first centralization unit network element managed by one of the shared public land mobile networks, the first broadcast configuration request message including a first configuration of the first centralization unit network element; receiving, in the device, a second broadcast configuration request message from a second centralization unit network element managed by another one of the shared public land mobile networks, the second broadcast configuration request message including a second configuration of the second centralization unit network element; determining that the first and second broadcast session setup request messages correspond to the same broadcast service shared by two of the public land mobile networks that share the device; determining that the first setting and the second setting are different; determining whether to send a feedback message to the second centralization unit network element, the feedback message including a list of settings, the list including at least the first setting or a current operating setting; determining whether the second centralization unit network element can accept at least one of the settings sent in the feedback message based on a response to the feedback message from the second centralization unit network element; sending a final response message to the second centralization unit network element indicating success or failure of the configuration based on the determination based on the response to the feedback message from the second centralization unit network element; 20. A device configured to store instructions to cause a

27. 27. The device of claim 26, wherein the feedback message to the second centralization unit network element is a broadcast configuration failure message including a list of available configurations proposed by the device, including at least the current operating configuration or the first configuration.

28. 28. The device according to claim 26 or 27, wherein the response to the feedback message is a new broadcast configuration request message sent by the second centralization unit network element, the broadcast configuration request message including at least the current ongoing configuration or the first configuration, or one configuration from the list of available configurations proposed by the device, including other configurations proposed by the second centralization unit network element.

29. 29. The apparatus of claim 26, 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 including a list of available configurations proposed by the apparatus, the list including at least the current operating configuration or the first configuration.

30. The response to the feedback message: a multicast radio bearer configuration update success response informing that one of the available configurations is acceptable by the second centralization unit network element and including one or more of the accepted configurations; or a multicast radio bearer setup failure message informing that none of the available configurations was accepted by the second centralization unit network element and further not including other configurations proposed by the second centralization unit network element.

30. Apparatus according to any one of claims 26 to 29.

31. 31. The device according to claim 26, wherein if the configuration received from the second centralization unit network element in response to the feedback message is acceptable to the device, sending the final response message comprises sending a broadcast configuration response message to the second centralization unit network element.

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

33. if the acceptable configuration received from the second centralization unit network element in response to the feedback message corresponds to its current operational configuration, the device does not initiate an additional broadcast; if the acceptable configuration received from the second centralization unit network element in response to the feedback message does not correspond to its current operational configuration, the device initiates an additional broadcast.

33. Apparatus according to claim 31 or 32.

34. 34. The device of claim 26, wherein if the configuration received from the second centralized unit distributed unit in response to the feedback message is not acceptable to the device, sending the final response message includes sending a broadcast configuration failure message to the second centralized unit distributed unit.

35. 35. The device according to any one of claims 26 to 34, wherein the broadcast configuration response message includes a notification of whether a user plane tunnel should be established between the device and the second convergence unit network element.

36. 36. The apparatus of claim 26, wherein the first broadcast configuration request message includes a first parameter indicating whether the first centralized network element provides the broadcast service to at least one unshared distributed radio access node.

37. 37. The apparatus according to claim 26, wherein the second broadcast configuration request message includes a second parameter indicating whether the second centralized network element provides the broadcast service to at least one unshared distributed radio access node.

38. In the broadcast configuration response message, the notification of whether to set up a user plane tunnel between the device and the second centralization unit network element is: a parameter received from the first and second centralized network elements indicating whether to provide service to a non-shared distributed radio access node; or a centralized network element to which the final configuration has been accepted; 39. The apparatus of any one of claims 26 to 38, based on at least one of:

39. 1. An apparatus comprising: at least one processor; at least one memory containing computer program code; Equipped with The at least one memory and the computer program code, when executed by the at least one processor, cause the device to at least: sending a first broadcast configuration request message corresponding to a broadcast service to a distributed radio access node shared by two or more public land mobile networks, the first broadcast configuration request message including a first configuration of a first centralized unit network element managed by one of the shared public land mobile networks; sending, to the distributed radio access node, a second broadcast configuration request message corresponding to the broadcast service, the second broadcast configuration request message including 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 centralization unit network element, from the distributed radio access node, a feedback message including a list of configurations including at least the first configuration or a current operational configuration; in the second centralization unit network element, in response to the feedback message, sending a notification to the distributed radio access node whether at least one of the configurations sent in the feedback message is acceptable or not, or proposing another configuration; receiving, at the second centralization unit network element, a final response message from the distributed radio access node indicating success or failure of the configuration based on the response to the feedback message; 20. A device configured to store instructions to cause a

40. 40. The apparatus of claim 39, wherein the feedback message is a broadcast configuration failure message including a list of available configurations proposed by the distributed radio access node, including at least the current operating configuration or the first configuration.

41. 41. The apparatus according to claim 39 or 40, wherein the notification to the feedback message comprises a new broadcast configuration request message including one of the list of available configurations proposed by the distributed radio access node, including at least the current ongoing configuration or the first configuration, or another configuration proposed by the second centralization unit network element.

42. 42. The apparatus according to any 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 including a list of available configurations proposed by the distributed radio access node, the list including at least the current operational configuration or the first configuration.

43. The response to the feedback message: a multicast radio bearer configuration update success notification informing that one of the available configurations is acceptable by the second centralization unit network element and including one or more of the accepted configurations; or a multicast radio bearer setup failure message informing that none of the available configurations was accepted by the second centralization unit network element and not including other configurations proposed by the second centralization unit network element; 43. Apparatus according to any one of claims 39 to 42.

44. 44. The apparatus of claim 39, wherein if the configuration sent in the response to the feedback message is acceptable to the distributed radio access node, receiving the final response message comprises receiving a broadcast configuration response message at the second centralization unit network element.

45. The final response message: the current operational configuration of the first centralization unit network element; or Any of the settings included in the feedback message; 45. Apparatus according to any one of claims 39 to 44, comprising at least one of:

46. 46. ​​The apparatus of claim 39, wherein receiving the final response message comprises receiving a broadcast configuration failure message at the second centralization unit network element if the configuration sent in the response to the feedback message is not accepted by the distributed radio access node.

47. 47. The apparatus of claim 39, wherein the broadcast setup response message includes a notification of whether to set up a user plane tunnel between the distributed radio network node and the second centralization unit network element.

48. 48. The apparatus of claim 39, wherein the first broadcast configuration request message includes 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. 49. The apparatus of claim 39, wherein the second broadcast configuration request message includes 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. In the broadcast configuration response message, the notification of whether to set up a user plane tunnel between the distributed radio access node and the second centralization unit network element is: a parameter received from the first and second centralized network elements indicating whether to provide the broadcast service to at least one non-shared distributed unit network element; or a centralized network element to which the final configuration has been accepted; 50. The apparatus of claim 39, wherein the apparatus is based on at least one of the following:

51. A non-transitory computer readable medium having stored thereon program instructions for carrying out the method of any of claims 1 to 25.

52. 26. An apparatus comprising circuitry configured to cause said apparatus to carry out a process according to a method according to any preceding claim.

Images