Shared cu up address management

Abstract

Embodiments of the present disclosure relate to shared CU UP address management. An apparatus is provided that includes means for receiving, at a multicast / broadcast session management function of a core network, information from a radio access network, RAN, node or an access management function of the core network, the information being about a shared centralized unit user plane, CU UP, for a multicast / broadcast session; means for determining, based on the information, whether to configure a user plane function of the core network to deliver data for the multicast / broadcast session to the shared CU UP or to terminate delivery of data for the multicast / broadcast session to the shared CU UP; and means for configuring the user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate delivery of data for the multicast / broadcast session to the shared CU UP, if so.

Description

Technical Field

[0001] This application relates to a method, apparatus, system, and computer program, and specifically, but not exclusively, to shared centralized unit (CU) user plane (UP) address management. Background Technology

[0002] A communication system can be viewed as a facility that enables a communication session between two or more entities, such as user terminals, base stations, and / or other nodes, by providing carrier waves between various entities involved in the communication path. For example, a communication system can be provided via a communication network and one or more compatible communication devices. The communication session can include, for example, data communication used to carry communications such as voice, video, email, text messages, multimedia, and / or content data. Non-limiting examples of the services provided include two-way or multiplexed calls, data communication or multimedia services, and access to data network systems such as the Internet.

[0003] In wireless communication systems, at least a portion of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems include Public Land Mobile Networks (PLMNs), satellite-based communication systems, and various wireless local area networks (WLANs). Some wireless systems can be divided into cells and are therefore often referred to as cellular systems.

[0004] Users can access the communication system through appropriate communication equipment or terminals. A user's communication equipment may be referred to as User Equipment (UE) or simply user equipment. The communication equipment is equipped with appropriate signal receiving and transmitting means to enable communication, such as enabling access to a communication network or direct communication with other users. The communication equipment can access carriers provided by stations (e.g., base stations in a cell) and transmit and / or receive communication on those carriers.

[0005] Communication systems and associated equipment typically operate according to a given standard or specification that states what is allowed to be done by the various entities associated with the system and how it should be done. Communication protocols and / or parameters used for connectivity are also usually defined. One example of a communication system is UTRAN (3G Radio). Other examples of communication systems are the Long Term Evolution (LTE) of Universal Mobile Telecommunications System (UMTS) radio access technology and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP). Summary of the Invention

[0006] In a first aspect, an apparatus is provided, comprising, at a multicast / broadcast session management function of a core network: components for receiving information from a radio access network (RAN) node or an access management function of the core network, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions; components for determining, based on the information, whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP; and components for configuring the user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP if so.

[0007] Information related to the shared CU UP may include an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0008] The apparatus may include components for configuring user plane functions to deliver data for a multicast / broadcast session to a shared CU UP without receiving an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0009] Information related to the shared CU UP may include indications that the RAN node or AMF no longer participates in the multicast / broadcast session, and indications of whether to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0010] The apparatus may include components for configuring user plane functions to terminate the delivery of data for the multicast / broadcast session to the shared CU UP upon receiving an indication that the RAN node no longer participates in the multicast / broadcast session and without receiving an indication to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0011] This information may include the identifier associated with the RAN node and an indication of whether data delivery is requested or terminated.

[0012] The apparatus may include components for configuring user plane functions to deliver data for a multicast / broadcast session to the shared CU UP upon receiving an indication that data delivery has been requested and in the absence of any other RAN node having previously requested delivery of data for a multicast / broadcast session to the shared CU UP.

[0013] The apparatus may include components for configuring user plane functions to terminate the delivery of data for the multicast / broadcast session to the shared CU UP when an instruction to terminate the delivery of data for the multicast / broadcast session is received and no other RAN node requests the delivery of data for the multicast / broadcast session to the shared CU UP.

[0014] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0015] The apparatus may include components for storing the identifiers of RAN nodes in association with identifiers associated with shared CU UP.

[0016] The identifier associated with a shared CU UP can be a transport layer address.

[0017] The identifier associated with a shared CU UP can be a globally unique logical network node identifier in a public terrestrial mobile network.

[0018] The RAN node may include a centralized cell control plane (CU CP), and components for receiving information from the RAN node may be used to receive information from the CU CP.

[0019] In a second aspect, an apparatus is provided comprising a node at a radio access network (RAN) for providing information to a multicast / broadcast session management function or a core network access management function regarding a shared centralized unit user plane (CU UP) for the multicast / broadcast session, for determining whether to configure user plane functions to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0020] The apparatus may include components for receiving at a RAN node an indication that an identifier associated with the shared CU UP has been provided to another RAN node from a shared CU UP, and components for providing the information based on the indication.

[0021] This information may include indications that an identifier has already been provided that is associated with the shared CU UP.

[0022] The apparatus may include components for instructing a shared CU UP that the apparatus no longer participates in a multicast / broadcast session and, in response to the instruction, receiving whether to continue delivering data for the multicast / broadcast session to an identifier associated with the shared CU UP, and components for providing the information based on the instruction.

[0023] This information may include an indication that the RAN node no longer participates in the multicast / broadcast session, and an indication of whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP.

[0024] This information may include the identifier associated with the RAN node.

[0025] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0026] RAN nodes may include a centralized cell control plane (CU CP).

[0027] The identifier associated with a shared CU UP can be at least one of the following: a transport layer address, or a globally unique identifier for the shared CU UP.

[0028] In a third aspect, a method is provided, comprising: at a multicast / broadcast session management function of a core network, receiving information from a radio access network (RAN) node or an access management function of the core network, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions; based on the information, determining whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP; and if so, configuring the user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0029] Information related to the shared CU UP may include an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0030] The method may include: if no indication has been received that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP, then configuring the user plane function to deliver data for a multicast / broadcast session to the shared CU UP.

[0031] Information related to the shared CU UP may include indications that the RAN node or AMF no longer participates in the multicast / broadcast session, and indications of whether to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0032] The method may include: if an indication is received that the RAN node no longer participates in the multicast / broadcast session and no indication is received to continue delivering data for the multicast / broadcast session to the shared CU UP, then configuring user plane functions to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0033] This information may include the identifier associated with the RAN node and an indication of whether data delivery is requested or terminated.

[0034] The method may include: if an indication to deliver requested data is received and no other RAN node has previously requested to deliver data for a multicast / broadcast session to the shared CU UP, then configuring the user plane function to deliver data for a multicast / broadcast session to the shared CU UP.

[0035] The method may include: if an indication to terminate the delivery of data is received, and no other RAN node still requests the delivery of data for the multicast / broadcast session to the shared CU UP, then configuring the user plane function to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0036] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0037] The apparatus may include components for storing the identifiers of RAN nodes in association with identifiers associated with shared CU UP.

[0038] The identifier associated with a shared CU UP can be a transport layer address.

[0039] The identifier associated with a shared CU UP can be a globally unique logical network node identifier in a public terrestrial mobile network.

[0040] The RAN node may include a centralized cell control plane (CU CP), and components for receiving information from the RAN node may be used to receive information from the CU CP.

[0041] In a fourth aspect, a method is provided that includes providing information at a node in a radio access network (RAN) to a multicast / broadcast session management function or an access management function in a core network, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, for determining whether to configure user plane functions to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0042] The method may include: receiving at the RAN node an indication that an identifier associated with the shared CU UP has been provided to another RAN node, and providing the information based on the indication.

[0043] This information may include indications that an identifier has already been provided that is associated with the shared CU UP.

[0044] The method may include: instructing the shared CU UP that the device no longer participates in a multicast / broadcast session, and receiving, in response to the instruction, whether to continue delivering data for the multicast / broadcast session to an identifier associated with the shared CU UP, and providing the information based on the instruction.

[0045] This information may include an indication that the RAN node no longer participates in the multicast / broadcast session, and an indication of whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP.

[0046] This information may include the identifier associated with the RAN node.

[0047] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0048] RAN nodes may include a centralized cell control plane (CU CP).

[0049] The identifier associated with a shared CU UP can be at least one of the following: a transport layer address, or a globally unique identifier for the shared CU UP.

[0050] In a fifth aspect, an apparatus is provided, comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to utilize the at least one processor to cause the apparatus to receive information from a radio access network RAN ​​node or an access management function of the core network at least at a multicast / broadcast session management function of the core network, the information relating to a shared centralized unit user plane (CUUP) for a multicast / broadcast session.

[0051] Based on this information, determine whether to configure the user plane functions of the core network to deliver data for multicast / broadcast sessions to the shared CU UP or to terminate the delivery of data for multicast / broadcast sessions to the shared CU UP, and if so, configure the user plane functions to deliver data for multicast / broadcast sessions to the shared CU UP or terminate the delivery of data for multicast / broadcast sessions to the shared CU UP.

[0052] Information related to the shared CU UP may include an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0053] The device can be configured to configure the user plane function to deliver data for a multicast / broadcast session to the shared CU UP without receiving an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0054] Information related to the shared CU UP may include indications that the RAN node or AMF no longer participates in the multicast / broadcast session, and indications of whether to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0055] The device can be configured to configure the user plane function to terminate the delivery of data for the multicast / broadcast session to the shared CU UP upon receiving an indication that the RAN node no longer participates in the multicast / broadcast session and without receiving an indication to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0056] This information may include the identifier associated with the RAN node and an indication of whether data delivery is requested or terminated.

[0057] The device can be configured to, if an instruction to deliver requested data is received and no other RAN node has previously requested to deliver data to the shared CU UP for a multicast / broadcast session, configure the user plane function to deliver data to the shared CU UP for a multicast / broadcast session.

[0058] The device can be configured to terminate the delivery of data for multicast / broadcast sessions to the shared CU UP if an instruction to terminate data delivery is received and no other RAN node still requests delivery of data for multicast / broadcast sessions to the shared CU UP.

[0059] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0060] The apparatus may include components for storing the identifiers of RAN nodes in association with identifiers associated with shared CU UP.

[0061] The identifier associated with a shared CU UP can be a transport layer address.

[0062] The identifier associated with a shared CU UP can be a globally unique logical network node identifier in a public terrestrial mobile network.

[0063] The RAN node may include a centralized cell control plane (CU CP), and components for receiving information from the RAN node may be used to receive information from the CU CP.

[0064] In a sixth aspect, an apparatus is provided, comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to utilize the at least one processor to cause the apparatus to provide information, at least at a radio access network (RAN) node, to a multicast / broadcast session management function or an access management function of the core network, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, for determining whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0065] The device can be configured to receive at a RAN node an indication that an identifier associated with the shared CU UP has been provided to another RAN node from a shared CU UP, and to provide the information based on the indication.

[0066] This information may include indications that an identifier has already been provided that is associated with the shared CU UP.

[0067] The device can be configured to indicate to the shared CU UP that the device no longer participates in the multicast / broadcast session, and in response to the indication, receive whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP, and provide the information based on the indication.

[0068] This information may include an indication that the RAN node no longer participates in the multicast / broadcast session, and an indication of whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP.

[0069] This information may include the identifier associated with the RAN node.

[0070] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0071] RAN nodes may include a centralized cell control plane (CU CP).

[0072] The identifier associated with a shared CU UP can be at least one of the following: a transport layer address, or a globally unique identifier for the shared CU UP.

[0073] In a seventh aspect, a computer-readable medium is provided including program instructions for causing an apparatus to perform at least the following: receiving information from a radio access network (RAN) node or an access management function of the core network at a multicast / broadcast session management function of the core network, the information relating to a shared centralized unit user plane (CU UP) for a multicast / broadcast session; based on the information, determining whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP; and if so, configuring the user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0074] Information related to the shared CU UP may include an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0075] If no indication has been received that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP, the device may perform a configuration user plane function to deliver data for the multicast / broadcast session to the shared CU UP.

[0076] Information related to the shared CU UP may include indications that the RAN node or AMF no longer participates in the multicast / broadcast session, and indications of whether to continue delivering data for the multicast / broadcast session to the shared CU UP.

[0077] If an instruction is received that the RAN node is no longer participating in the multicast / broadcast session and no instruction is received to continue delivering data for the multicast / broadcast session to the shared CU UP, the device can perform a configuration user plane function to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0078] This information may include the identifier associated with the RAN node and an indication of whether data delivery is requested or terminated.

[0079] If an instruction to deliver requested data is received and no other RAN node has previously requested to deliver data for a multicast / broadcast session to the shared CU UP, the device may be configured to perform user plane functions to deliver data for a multicast / broadcast session to the shared CU UP.

[0080] If an instruction to terminate data delivery is received and no other RAN node still requests data delivery to the shared CUUP for multicast / broadcast sessions, the device can perform a configuration user plane function to terminate data delivery to the shared CUUP for multicast / broadcast sessions.

[0081] The information may also include at least one of the following: an indication that the CU UP is shared and a global identifier associated with the shared CU UP.

[0082] The device can perform the operation of storing the identifier of the RAN node in association with the identifier associated with the shared CU UP.

[0083] The identifier associated with a shared CU UP can be a transport layer address.

[0084] The identifier associated with a shared CU UP can be a globally unique logical network node identifier in a public terrestrial mobile network.

[0085] The RAN node may include a centralized cell control plane (CU CP), and components for receiving information from the RAN node may be used to receive information from the CU CP.

[0086] In an eighth aspect, a computer-readable medium is provided, comprising program instructions for causing a device at a radio access network (RAN) node to perform at least the following operations: providing information to a multicast / broadcast session management function or an access management function of the core network, the information being associated with a shared centralized unit user plane (CU UP) for the multicast / broadcast session, for determining whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0087] The device may perform the following operations: at the RAN node, receive an indication that the identifier associated with the shared CU UP has been provided to another RAN node from the shared CU UP; and provide the information based on the indication.

[0088] This information may include indications that an identifier has already been provided that is associated with the shared CU UP.

[0089] The device can instruct the shared CU UP to no longer participate in the multicast / broadcast session, and in response to the instruction, receive whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP, and provide the information based on the instruction.

[0090] This information may include an indication that the RAN node no longer participates in the multicast / broadcast session, and an indication of whether to continue delivering data for the multicast / broadcast session to the identifier associated with the shared CU UP.

[0091] This information may include the identifier associated with the RAN node.

[0092] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

[0093] RAN nodes may include a centralized cell control plane (CU CP).

[0094] The identifier associated with a shared CU UP can be at least one of the following: a transport layer address, and a globally unique identifier for the shared CU UP.

[0095] In a ninth aspect, a non-transient computer-readable medium is provided, comprising program instructions for causing a device to execute at least the method according to a third or fourth aspect.

[0096] Many different embodiments have been described above. It should be understood that other embodiments can be provided by any combination of two or more of the above embodiments. Attached Figure Description

[0097] Embodiments will now be described by way of example only with reference to the accompanying drawings, in which:

[0098] Figure 1 A schematic diagram of an example 5GS communication system is shown;

[0099] Figure 2 A schematic diagram of an exemplary mobile communication device is shown;

[0100] Figure 3 A schematic diagram of an example control device is shown;

[0101] Figure 4 A flowchart of a method according to an example embodiment is shown;

[0102] Figure 5 A flowchart of a method according to an example embodiment is shown;

[0103] Figure 6 The signaling flow is shown for an example case where a shared NG-U address is added and managed by a RAN node;

[0104] Figure 7 The signaling flow is shown in an example scenario where the removal of a shared NG-U address is managed by the RAN node;

[0105] Figure 8 The signaling flow is shown for an example case of adding a shared NG-U address managed by the MB-SMF;

[0106] Figure 9 The signaling flow is shown for an example case of the removal of a shared NG-U address managed by the MB-SMF. Detailed Implementation

[0107] Before explaining the examples in detail, refer to Figures 1 to 3 A brief explanation of some general principles of wireless communication systems and mobile communication devices is provided to help understand the underlying technology of the described examples.

[0108] A suitable example of a communication system is the 5G system (5GS). The network architecture in 5GS can be similar to that of advanced LTE. Base stations in NR systems can be referred to as next-generation node Bs (gNBs). Changes in network architecture can depend on the need to support various radio technologies and more granular QoS support, as well as some on-demand requirements, such as QoS levels supporting user perspectives. Furthermore, network-aware services and applications, and service and application-aware networks, can bring about changes to the architecture. These technologies involve information-centric networks (ICNs) and user-centric content delivery networks (UC-CDNs) approaches. NR can use multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites working in conjunction with smaller stations, and may also employ a variety of radio technologies to achieve better coverage and enhanced data rates.

[0109] 5G networks can leverage Network Functions Virtualization (NFV), a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that are operatively connected or linked together to provide services. Virtualized network functions (VNFs) can include one or more virtual machines running computer program code using standard or general-purpose type servers instead of custom hardware. Cloud computing or data storage can also be used. In radio communications, this can mean performing node operations, at least partially, within servers, hosts, or nodes operatively coupled to a remote radio head. Node operations can also be distributed across multiple servers, nodes, or hosts. It should also be understood that the workforce distribution between core network operations and base station operations can differ from, or even not exist at all, the workforce distribution in LTE.

[0110] Figure 1 A schematic diagram of a 5G system (5GS) 100 is shown. The 5GS may include a user equipment (UE) 102 (which may also be referred to as a communication device or terminal), a 5G radio access network (5GRAN) 104, a 5G core network (5GCN) 106, one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0111] An example 5G core network (CN) includes functional entities. 5GCN106 may include one or more Access and Mobility Management Functions (AMF) 112, one or more Session Management Functions (SMF) 114, Authentication Server Function (AUSF) 116, Unified Data Management (UDM) 118, one or more User Plane Functions (UPF) 120, Unified Data Repository (UDR) 122, and / or Network Exposure Function (NEF) 124. The UPF is controlled by the SMF (Session Management Function) that receives policies from the PCF (Policy Control Function).

[0112] The CN is connected to the terminal equipment via the Radio Access Network (RAN). The 5G RAN may include one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. The RAN may include one or more access nodes.

[0113] The UPF (User Plane Function), whose role is called PSA (Protocol Data Unit (PDU) Session Anchor Point), can be responsible for forwarding frames back and forth between the DN (Data Network) and the tunnel established through 5G to (multiple) UEs that exchange services with the DN.

[0114] Now refer to Figure 2 A more detailed description of possible mobile communication devices, Figure 2 A schematic partial cross-sectional view of a communication device 200 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Suitable mobile communication devices can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples include mobile stations (MS) or mobile devices such as mobile phones or so-called "smartphones," computers equipped with wireless interface cards or other wireless interface devices (e.g., USB dongles), personal data assistants (PDAs) or tablet computers equipped with wireless communication capabilities, Voice over IP (VoIP) phones, portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), or any combination of these devices. Mobile communication devices can provide, for example, data communication for carrying communications such as voice, email, text messages, multimedia, etc. Therefore, a variety of services can be provided to the user via the user's communication device. Non-limiting examples of these services include two-way or multiplexed calling, data communications or multimedia services, or simply access to data communications network systems such as the Internet. Broadcast or multicast data may also be provided to users. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms, and other information.

[0115] Mobile devices typically include at least one data processing entity 201, at least one memory 202, and other possible components 203 for software and hardware assistance in performing tasks designed to be performed, including controlling access to and communication with access systems and other communication devices. Data processing, storage, and other related control devices may be located on suitable circuit boards and / or chipsets. This feature is indicated by reference numeral 204. Users can control the operation of the mobile device through suitable user interfaces, such as keyboards 205, voice commands, touch-sensitive screens or keyboards, combinations thereof, etc. A display 208, speakers, and microphone may also be provided. Furthermore, mobile communication devices may include suitable connectors (wired or wireless) for connecting to other devices and / or for attaching external accessories (e.g., hands-free devices).

[0116] Mobile device 200 can receive signals via air or radio interface 207 through appropriate means for receiving, and can transmit signals via appropriate means for transmitting radio signals. Figure 2 In the diagram, the transceiver device is schematically represented by box 206. The transceiver device 206 can be provided, for example, via a radio section and an associated antenna arrangement. The antenna arrangement can be located inside or outside the mobile device.

[0117] Figure 3 An example of a control device 300 for a communication system is shown, which is coupled to and / or used to control access to the system, such as RAN nodes (e.g., base stations, eNBs or gNBs), relay nodes, or core network nodes (e.g., MMEs, S-GWs, or P-GWs), or core network functions (e.g., AMFs / SMFs), or servers or hosts. The method can be implemented in a single control device or in more than one control device. The control device can be integrated with or external to nodes or modules of the core network or RAN. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device can be another network element, such as a radio network controller or a spectrum controller. In some embodiments, each base station can have such a control device as well as control devices provided in the radio network controller. The control device 300 can be arranged to provide control over communications within the service area of ​​the system. The control device 300 includes at least one memory 301, at least one data processing unit 302, 303, and an input / output interface 304. Through this interface, the control device can be coupled to the receiver and transmitter of the base station. The receiver and / or transmitter can be implemented as a radio front end or a remote radio head.

[0118] In 5G Multicast / Broadcast Service (MBS) Release 17, it has been decided to use Packet Data Convergence Protocol (PDCP) Sequence Number (SN) synchronization between multiple cells to minimize data loss in multicast sessions.

[0119] One solution for synchronizing PDCP SNs is to use a host that manages PDCP entities for multiple cells and provides a shared CU UP entity with the same PDCP configuration.

[0120] When a CU CP requests to join the multicast / broadcast distribution tree, according to the current solution, the second and subsequent CU CPs requesting to use the shared CU UP node do not need to trigger an NG distribution establishment request to request MB-SMF / MB-UPF to send multicast traffic to the shared CU UP NG-U TNL address, because the shared CU-UP has already received it.

[0121] However, if those CU CPs do not trigger NG distribution establishment requests, then those CU CPs will not be registered with the AMF and will not be notified of subsequent activation requests by the MB-SMF. In other words, those CU CPs will not be added to the control plane distribution tree to receive subsequent activation (or deactivation) request messages.

[0122] When a CU CP requests to leave the distribution tree, according to the current solution, if the CU CP no longer has UEs involved in the CUUP it controls, the CU CP sends an NGAP distribution release request to the AMF / MB-SMF, which includes the CUUP's NG-U TNL unicast address to request removal.

[0123] However, when using a shared CU UP shared with other CU CPs, a given CU CP should not request the removal of the shared CU UP address unless it is the last CU CP using it. Simultaneously, it should still send an NG distribution release request, which will be deregistered from the AMF for subsequent activation requests; in other words, the NG distribution release request will be removed from the control plane distribution tree for subsequent reception of activation (or deactivation) request messages.

[0124] Figure 4 A flowchart of a method according to an example embodiment is shown. This method can be executed at a core network node, such as a core network session management function, like MB-SMF (Multicast-Session Management Function).

[0125] In S1, the method includes receiving information related to the shared centralized unit user plane (CU UP) from a radio access network RAN ​​node or a core network access management function.

[0126] In S2, the method includes determining, based on the information, whether to configure the core network's user plane function (e.g., MB-UPF (Multicast-Broadcast User Plane Function)) to deliver data for multicast / broadcast sessions to the shared CU UP or to terminate the delivery of data for multicast / broadcast sessions to the shared CU UP.

[0127] If so, in S3, the method includes configuring user plane functions to deliver data for a multicast / broadcast session to a shared CU UP or terminating the delivery of data for a multicast / broadcast session to the shared CU UP.

[0128] Figure 5 A flowchart of a method according to an example embodiment is shown. The method can be performed at a RAN node (e.g., a CU CP of a RAN node such as a gNB).

[0129] In T1, the method includes providing information to the multicast / broadcast session management function or the access management function of the core network, which is associated with the shared centralized unit user plane (CU UP) for the multicast / broadcast session, to determine whether to configure user plane functions to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

[0130] RAN nodes can include CU CP.

[0131] RAN nodes can provide information to MB-SMF via AMF. In other words, RAN nodes (or CU CP) can provide information to AMF, and AMF forwards that information to MB-SMF.

[0132] The identifier associated with a shared CU-UP can be a shared NG-U address, such as the transport layer address of the NG-U interface. The identifier associated with a shared CU-IP can be a globally unique logical network node identifier within the PLMN.

[0133] The method may include storing the identifier of the RAN node associated with the identifier associated with the shared CU UP.

[0134] In the first example embodiment, the addition / removal of shared NG-U addresses is managed by the RAN node.

[0135] This method may include receiving, at the RAN node (or at the CU CP within the RAN node), an indication from the CU UP that the identifier associated with the CU UP has been provided to another RAN node (CU CP). It can be inferred that the identifier associated with the CU UP has therefore been provided to the User Plane Function (MB-UPF) of the core network. Information can then be provided from the RAN node to the SMF (e.g., from the CU CP to the MB-SMF) based on this indication.

[0136] Information related to the shared CU UP may include indications that data for multicast / broadcast sessions has been provided or requested (e.g., to the MB-UPF) to be delivered to the shared CU UP.

[0137] An indication that a request has been made from the shared CU UP to the RAN node to deliver data for a multicast / broadcast session to the shared CU UP can be an indication that the NG-U address is not present in the E1 bearer context setup response, or that the shared NG-U address is available in the E1 bearer context setup response.

[0138] The method may include configuring a User Plane Function (MB-UPF) to deliver data for a multicast / broadcast session to a shared CU UP without receiving an indication that data for a multicast / broadcast session has been requested to be delivered to the shared CU UP.

[0139] For example, when the CU CP configures an MBS session, it detects whether a "shared CU UP" provides an NG-U address and can select that shared CU UP. Optionally, the CU UP informs the CU CP whether the shared NG-U address has already been allocated for the MBS session (and is therefore provided to the MB-UPF). The CU UP can provide an indication that the shared NG-U address has been allocated for the MBS session (in other words, provided to the MB-UPF) by either not including the NG-U address in the E1 bearer context setup response or by including an indicator that the shared NG-U address is already available.

[0140] If the CU CP uses the shared CU UP's NG-U address, the CU CP sends an NGAP distribution request, in which the new shared NG-U address has been delivered by an indicator IE or equivalent IE in the delivery distribution setup transmission request toward the CN (e.g., MB-SMF).

[0141] When the MB-SMF receives an NGAP distribution request transmission with a new shared NG-U address delivered indicator IE, it continues to store the AMF ID for subsequent activation request notifications, but it does not contact the MB-UPF to update the distribution tree for the multicast / broadcast session with the NG-U address. In other words, it determines not to configure the MB-UPF to deliver data for the multicast / broadcast session to the shared CU UP.

[0142] The method may include receiving, at the CU UP, an indication from the RAN node that the device no longer participates in the multicast / broadcast session, and includes receiving, at the RAN node, an indication in response to the indication from the shared CU UP regarding whether to continue delivering data for the multicast / broadcast session to an identifier associated with the shared CU UP. The method may also include providing information from the RAN node to the MB SMF based on this indication.

[0143] Information related to the shared CU UP may include indications that the RAN node no longer participates in multicast / broadcast sessions, and indications of whether to continue delivering data for multicast / broadcast sessions to the shared CU UP.

[0144] This indication may be due to the absence of a removal indicator and / or the non-existence of the NG-U transport address.

[0145] The method may include configuring a User Plane Function (MB-UPF) to terminate the delivery of data for the multicast / broadcast session to the shared CU UP if an indication is received that the RAN node no longer participates in the multicast / broadcast session and no indication is received that data for the multicast / broadcast session will continue to be delivered to the shared CU UP.

[0146] For example, when no more UEs are participating in the gNB, the CU CP contacts the CU UP, which informs the CU CP that it is the last CU CP involved in the shared address of this MBS session. Based on this, the CU CP triggers an NGAP distribution release request message, which in the distribution release request transport IE newly includes no removal indicator and / or does not include the NG-U transport address.

[0147] When the MB SMF receives an NGAP distribution release request transmission that does not have an NG-U transport address and / or has a "no removal indicator", it does not request the MB UPF to remove the delivery of the NG-U address for the distribution tree of the MBS session.

[0148] In the second example embodiment, the addition and / or removal of shared NG-U addresses is managed by the MB SMF.

[0149] This information may include an identifier associated with the RAN node and an indication of whether data delivery is requested or terminated (e.g., an NGAP distribution establishment request or an NGAP distribution release request, respectively).

[0150] This method may include configuring the User Plane Function (MB-UPF) so that if an indication of a request for data delivery is received and no other RAN node has previously requested MB-SMF data delivery for a multicast / broadcast session to the shared CU UP, then data for the multicast / broadcast session will be delivered to the shared CU UP.

[0151] This method may include configuring a User Plane Function (MB-UPF) to terminate the delivery of data for a multicast / broadcast session to the shared CU UP if an instruction to terminate data delivery is received and no other RAN node still requests delivery of data for a multicast / broadcast session to the shared CU UP.

[0152] The information may also include at least one of the following: an indication that the CU UP is shared, and a global identifier associated with the CU UP.

[0153] For example, when the CU CP decides to use “shared CU UP”, the CU CP sends an NGAP distribution establishment request to the MB SMF. The NGAP distribution establishment request includes the MBS session ID, the shared NG-U address and gNB ID (of the CU CP) in the distribution establishment request transmission, as well as an optional sharing indicator (i.e., an indication that the CU UP is shared) and / or an optional globally unique identifier of the CU UP (gNB ID, CU UP ID).

[0154] When the MB-SMF receives an NGAP distribution establishment request transmission including the MBS session ID, NG-U address, and gNB ID, as well as an optional sharing indicator and / or optional (gNB ID, CU UP ID), the MB-SMF continues to store the AMF ID for subsequent notification of the activation request. However, it selectively contacts the MB UPF to add multicast delivery to the NG-U address only if a request from another CU CP (identified by the gNB ID) has not yet been completed, possibly for the same CU UP ID (if indicated by (gNB ID, CU UP)).

[0155] When no more UEs participate in the gNB for the MBS session, the CU CP triggers an NGAP distribution release request message. This message has the MBS session ID, the NG-U address, and in the distribution release request transmission IE, it newly includes the gNB ID (of the CU CP) and an optional sharing indicator, and / or optional (gNB ID, CU UPID) as the global identifier of the CU UP.

[0156] When the MB SMF receives an NGAP distribution release request transmission including the MBS session ID, NG-U address, and new gNB ID, as well as optional sharing indicators and / or optional (gNB ID, CU UP ID), it selectively requests the MB UPF to remove multicast delivery to the NG-U address used for the MBS session only if no other gNB (identified by the gNB ID), i.e., the CU CP is using that NG-U address or that (gNB ID, CU UP ID).

[0157] Figure 6 The signaling flow is shown for an example case where a shared NG-U address is added and managed by a RAN node.

[0158] In step 1, the shared CU UP can instruct it to provide sharing for certain MBS sessions.

[0159] In step 2, the CU CP needs to create a context for the MBS session and decide to use the shared CU UP for E1 bearer context establishment / modification requests.

[0160] In step 2bis, the shared CU UP can indicate to the requesting CU CP that the requested address can be shared by either omitting the NG-U address for multicast delivery or adding an indicator IE that the NG-U address has been delivered in the E1AP bearer context setup / modification response message.

[0161] In step 3, the CU CP determines that it can use the shared NG-U address from the shared CU UP from step 1 or step 2bis, and decides to include an indicator that the NG-U address has been delivered in the NGAP distribution establishment request transmission IE of the NGAP distribution establishment request message.

[0162] In step 4, the AMF relays the NGAP distribution establishment request transmission IE to the MB-SMF, and simultaneously adds the gNB ID to the control plane distribution tree for, for example, to activate subsequent reception and / or transmission of the request. The MB-SMF receiving the NGAP distribution establishment request transmission IE with an indicator that a new NG-U address has been delivered determines not to contact the MB-UPF requesting the delivery of multicast data to that NG-U address.

[0163] Figure 7 The signaling flow is shown for an example case where the removal of a shared NG-U address is managed by a RAN node.

[0164] In step 1, since no more UEs are participating in the MBS session, the CU CP decides to release NG-U delivery from the shared CU UP for multicast delivery. It sends the E1AP bearer context modification to the shared CU UP.

[0165] In step 2, the shared CU UP notifies the CU CP in the E1AP bearer modification response whether it is the last CU CP using the shared CU UP and NG-U address of the MBS session.

[0166] In step 3, if it is not the final CU CP, the CU CP determination notifies the MB SMF by omitting the NG-U address in the NGAP Distribution Release Request Transmission IE of the NGAP Distribution Release Request message and / or including a "no removal indicator" in the NGAP Distribution Release Request Transmission IE of the NGAP Distribution Release Request message. The AMF relays the NGAP Distribution Release Request Transmission IE while removing the CU CP (gNB) from the control plane distribution tree for subsequent reception / transmission, such as activation requests.

[0167] In step 4, the MB SMF determines not to contact the MB UPF to remove the NG-U address from the delivery of multicast data based on receiving a "no removal indicator" or based on not receiving the NG-U address.

[0168] Figure 8 The signaling flow is shown for an example case of adding a shared NG-U address managed by MB-SMF.

[0169] In step 1, the CU CP determines to use the shared CU UP to create the MBS context for the MBS session. The CU CP includes its gNB 2 identifier and may optionally add the shared indicator and / or unique identifier of the CU UP (gNB1, CU UP5) to the NGAP distribution establishment request transport IE of the NGAP distribution establishment request message toward the MB-SMF.

[0170] In step 2, the AMF relays the NGAP distribution establishment request (IE) to the MB SMF, and simultaneously adds gNB 2 to the control plane distribution tree for, for example, subsequent reception / transmission of the activation request. The MB SMF receiving the NGAP distribution establishment request IE determines whether to contact the MB UPF to deliver multicast data to the NG-U address based on whether another CU CP has not yet requested delivery for that NGU address or for that shared CU UP. The MB SMF may also store information gNB 2 and / or (gNB1, CUUP5) for further use.

[0171] Figure 9 The signaling flow is shown for an example case of the removal of a shared NG-U address managed by the MB-SMF.

[0172] In step 1, the CU CP decides to leave multicast delivery for a given MBS session because it no longer has a UE joining for that MBS session. It sends an NGAP distribution release request message, and in the NGAP distribution release request transport IE, in addition to the NG-U address and MBS session ID, it also includes gNB 2 and an optional sharing indicator and / or a global identifier for the shared CU UP such as (gNB1, CU UP5).

[0173] In step 2, the AMF relays the NGAP distribution release request transmission IE and simultaneously removes gNB2 from the control plane distribution tree, i.e., for subsequent reception / transmission, such as activation requests. The MB SMF receiving the NGAP distribution release request transmission IE determines whether to contact the MB UPF to remove multicast data delivery to the NG-U address based on whether the shared NG-U address and / or the shared NG-U address (gNB1, CU UP 5) has not been used to deliver according to a request from another CU CP other than CU CP (gNB2). When the NGAP distribution establishment request transmission IE is received, it can determine gNB IDx and / or (gNBy, CU UP z) from the previous storage device.

[0174] An apparatus may include: a component for receiving information from a radio access network (RAN) node or an access management function of the core network at a multicast / broadcast session management function of the core network, the information relating to a shared centralized unit user plane (CU UP) for a multicast / broadcast session; determining, based on the information, whether to configure the core network's user plane function to deliver data for the multicast / broadcast session to the shared CU UP or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP; and if so, configuring the user plane function to deliver data for the multicast / broadcast session to the shared CU UP or terminating the delivery of data for the multicast / broadcast session to the shared CU UP.

[0175] Alternatively, additionally, an apparatus may include components for providing information at the radio access network (RAN) to the core network for multicast / broadcast session management, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, to determine whether to configure the core network's user plane functions to deliver multicast / broadcast session data to the shared CU UP or to terminate the delivery of multicast / broadcast session data to the shared CU UP.

[0176] It should be understood that the device may include or be coupled to other units or modules, such as radio sections or radio heads used in or for transmission and / or reception. Although the device has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0177] Note that while some embodiments have been described with respect to 5G networks, similar principles can be applied to other networks and communication systems. Therefore, although some embodiments have been described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, these embodiments can be applied to any other suitable form of communication system besides the communication systems shown and described herein.

[0178] It should also be noted that although exemplary embodiments have been described above, several changes and modifications may be made to the disclosed solutions without departing from the scope of the invention.

[0179] Generally, various embodiments can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. Although aspects of this disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that the blocks, apparatuses, systems, techniques, or methods described herein are intended as non-limiting examples implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or combinations thereof.

[0180] As used in this application, the term "circuit system" may refer to one or more or all of the following:

[0181] (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits) and

[0182] (b) A combination of hardware circuitry and software, such as (if applicable):

[0183] (i) A combination of analog and / or digital hardware circuitry with software / firmware, and

[0184] (ii) any part of a hardware processor (including a digital signal processor), software, and memory (a plurality of) having software, which work together to enable a device such as a mobile phone or server to perform various functions; and (c) a plurality of hardware circuits and / or a plurality of processors (e.g., a plurality of microprocessors or a portion thereof) that require software (e.g., firmware) to operate, but which may be absent when no software is required to operate.

[0185] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors in general) or portions thereof and their accompanying software and / or firmware. The term "circuit system" also covers (e.g., and if applicable to elements of a particular claim) baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0186] Embodiments of the present invention may be implemented by computer software executable by a data processor of a mobile device (e.g., in a processor entity), by hardware, or by a combination of software and hardware. Computer software or programs, also known as program products, include software routines, applets, and / or macros, may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components configured to execute the embodiments during program runtime. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0187] Furthermore, it should be noted that any box in the logical flow diagram can represent a program step, or an interconnected logic circuit, a box and function, or a combination of program steps and logic circuits, boxes and functions. Software can be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, and CDs. The physical media are non-transient media.

[0188] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. As a non-limiting example, the data processor can be of any type suitable for the local technical environment and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures.

[0189] Embodiments of the present invention can be practiced in various components, such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on semiconductor substrates.

[0190] The scope of protection sought by the various embodiments of this disclosure is set forth in the independent claims. Embodiments and features (if any) described in this specification that do not fall within the scope of the independent claims are to be interpreted as examples useful for understanding the various embodiments of this disclosure.

[0191] The foregoing description has provided a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, various modifications and adaptations will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of this disclosure will still fall within the scope of the invention as defined by the appended claims. Indeed, other embodiments exist that combine one or more embodiments with any of the other embodiments discussed above.

Claims

1. A device for communication, comprising: Components for receiving information from a radio access network (RAN) node or a core network access management function, the information relating to a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, wherein the information includes an identifier associated with the RAN node and an indication of whether to request or terminate the delivery of data. The component used to determine, based on the information, whether to configure the user plane function of the core network to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP, wherein the component for determination includes: a component for determining to configure the user plane function to deliver data for the multicast / broadcast session to the shared CU UP if an indication of a requested delivery of data is received, and no other RAN node has previously requested the delivery of data for the multicast / broadcast session to the shared CU UP; and A component for configuring the user plane function to deliver the data for the multicast / broadcast session to the shared CU UP, or terminating the delivery of data for the multicast / broadcast session to the shared CU UP, based on the determination.

2. The apparatus of claim 1, wherein the component for determining further comprises: A component for determining to configure the user plane function to terminate the delivery of data for the multicast / broadcast session to the shared CU UP if an indication to terminate the delivery of data is received and no other RAN node still requests the delivery of data for the multicast / broadcast session to the shared CU UP.

3. The apparatus of claim 1, wherein the information further includes at least one of: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

4. The apparatus according to claim 1, further comprising: A component for storing the identifier of the RAN node in association with the identifier associated with the shared CU UP.

5. The apparatus of claim 4, wherein the identifier associated with the shared CU UP is a transport layer address.

6. The apparatus of claim 1, wherein the RAN node includes a centralized cell control plane (CU CP), and the component for receiving information from the RAN node is used to receive information from the CU CP.

7. A method for communication, comprising, at a multicast / broadcast session management function in a core network: Information is received from a radio access network (RAN) node or the access management function of the core network regarding a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, wherein the information includes an identifier associated with the RAN node and an indication of whether to request or terminate the delivery of data. Based on the information, it is determined whether to configure the user plane function of the core network to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP, wherein the determination is made when an indication that the delivery of data for the multicast / broadcast session has been requested is received, and no other RAN node has previously requested the delivery of data for the multicast / broadcast session to the shared CU UP; as well as Based on the determination, the user plane function is configured to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

8. The method of claim 7, further comprising: Upon receiving an indication that the delivery of data for the multicast / broadcast session has been requested, and if no other RAN node still requests the delivery of data for the multicast / broadcast session to the shared CU UP, it is determined that the user plane function be configured to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

9. The method of claim 7, wherein the information further comprises at least one of: an indication that the CU UP is shared, and a global identifier associated with the shared CU UP.

10. The method of claim 7, further comprising: The identifier of the RAN node is stored in association with the identifier associated with the shared CUUP.

11. The method of claim 10, wherein the identifier associated with the shared CU UP is a transport layer address.

12. The method of claim 7, wherein the RAN node includes a centralized cell control plane (CU CP), and receiving information from the RAN node includes receiving information from the CU CP.

13. An apparatus for communication, comprising: At least one processor and at least one memory including computer program code, said at least one memory and computer program code being configured, together with said at least one processor, to cause the apparatus to perform at least: Information is received from the access management function of the radio access network (RAN) node or the core network regarding the shared centralized unit user plane (CU UP) for multicast / broadcast sessions, wherein the information includes an identifier associated with the RAN node and an indication of whether to request or terminate the delivery of data. Based on the information, it is determined whether to configure the user plane function of the core network to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP, wherein the determination is made when an indication that the delivery of data for the multicast / broadcast session has been requested is received, and no other RAN node has previously requested the delivery of data for the multicast / broadcast session to the shared CU UP; as well as Based on the determination, the user plane function is configured to deliver the data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

14. A computer-readable medium comprising program instructions that cause a device to perform at least the following at a multicast / broadcast session management function of a core network: Information is received from a radio access network (RAN) node or the access management function of the core network regarding a shared centralized unit user plane (CU UP) for multicast / broadcast sessions, wherein the information includes an identifier associated with the RAN node and an indication of whether to request or terminate the delivery of data. Based on the information, it is determined whether to configure the user plane function of the core network to deliver data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP, wherein the determination is made when an indication that the delivery of data for the multicast / broadcast session has been requested is received, and no other RAN node has previously requested the delivery of data for the multicast / broadcast session to the shared CU UP; as well as Based on the determination, the user plane function is configured to deliver the data for the multicast / broadcast session to the shared CU UP, or to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

15. The computer-readable medium of claim 14, wherein the program instructions are further configured to cause the apparatus to: upon receiving an indication that the delivery of data for the multicast / broadcast session has been requested, and no other RAN node still requests the delivery of data for the multicast / broadcast session to the shared CU UP, determine to configure the user plane function to terminate the delivery of data for the multicast / broadcast session to the shared CU UP.

Images