NETWORK NODE, SECOND RADIO NETWORK NODE, THIRD NETWORK NODE, AND METHODS PERFORMED THEREBY FOR HANDLING COMMON USER PLANE

TECHNICAL FIELD

The present disclosure relates generally to a network node, and methods performed thereby, for handling common user plane. The present disclosure further relates generally to a second radio network node and methods performed thereby for handling common user plane. The present disclosure additionally relates generally to a third network node and methods performed thereby for handling common user plane. The present disclosure also relates generally to computer programs and computer-readable storage mediums, having stored thereon the computer programs to carry out these methods.

BACKGROUND

Computer systems in a communications network or communications system may comprise one or more nodes. A node may comprise one or more processors which, together with computer program code may perform different functions and actions, a memory, a receiving port, and a sending port. A node may be, for example, a server. Nodes may perform their functions entirely on the cloud.

The communications network may cover a geographical area which may be divided into cell areas, each cell area being served by a type of node, a network node in the Radio Access Network (RAN), radio network node or Transmission Point (TP), for example, an access node such as a Base Station (BS), e.g., a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, or Base Transceiver Station (BTS), depending on the technology and terminology used. The base stations may be of different classes such as e.g., Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations and Home Base Stations, based on transmission power and thereby also cell size. A cell may be understood to be the geographical area where radio coverage may be provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The telecommunications network may also comprise network nodes which may serve receiving nodes, such as user equipments, with serving beams.

The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a New Radio Interface called Next Generation Radio or New Radio (NR) or 5G-Universal Terrestrial Radio Access (UTRA), as well as a Fifth Generation (5G) Packet Core Network, which may be referred to as 5G Core Network (5GC), abbreviated as 5GC.

Broadcast procedure in TS 23.247

In TS 23.247 v17.2.0, Broadcast Session Start procedure is described in clause 7.3.1 :

7.3. 1 MBS Session Start for Broadcast

The Broadcast Session Start may follow the common procedure specified in clause 7.1.1.2 or clause 7.1.1.3, which may consist of Temporary Mobile Group Identity (TMGI) Allocation and Multicast/Broadcast Service (MBS) Session Create. It may be possible for an Application Function (AF) to allocate TMGI once but create the MBS Session for multiple times. A combined procedure to perform both TMGI allocation and MBS Session Create may be available.

The TMGI Allocation may be used by AF to obtain the TMGI as MBS Session Identity (ID), e.g., TMGI, and perform service announcement towards UEs.

The MBS Session Create, with MBS service type set to broadcast service, may be used by the AF to indicate the impending start of the transmission of MBS data, and to provide the session attributes, so that resources for the MBS Session may be set up in the Multicast/Broadcast (MB)- User Plane Function (UPF) and in the Next Generation - Radio Access Network (NG-RAN) for 5G Core (5GC) Shared MBS traffic delivery. The MBS Session Create may be used if TMGI has not been allocated. In this case, MB-Session Management Function (SMF) may allocate a unique TMGI for the AF and then start the MBS Session.

As a first note, NOTE 1 , when the multicast transport between NG-RAN and MB-UPF is described below, source specific multicasting may be assumed.

To receive the data of broadcast communication service, the UE may be either preconfigured with needed configuration, e.g., User Service Description (USD) as defined in TS 26.346 [13], for the UE to receive MBS service, or provisioned with the configuration of broadcast session on application level, e.g., service announcement; the configuration may for instance be performed using Session Initiation Protocol (SIP) signalling, or methods described in TS 26.346 [13], If the needed configuration is pre-configured, the UE may be understood to not need to interact with network.

Figure 1 corresponds to Figure 7.3.1 -1 : MBS Session Establishment for Broadcast, as described next. Each of the following paragraphs numbered 0-15 describe an action having the corresponding number in the flowchart of Figure 1.

0. Based on Operations Administration and Maintenance (OAM) configuration, RAN nodes may announce in System Information Blocks (SIBs) over the radio interface information about the MBS Frequency Selection Area (FSA) I Dentifiers (Ids) and frequencies of neighbouring cells.

1. To establish broadcast MBS session, the AF may perform TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or 7.1.1.3. The MBS service type may indicate to be broadcast service. The MBS FSA ID(s) of a broadcast MBS session may be communicated in the service announcement towards the UE. The UE may compare those MBS FSA IDs(s) with the MBS FSA ID(s) in System Information Blocks (SIBs) for frequency selection.

2. The MB-SMF may use Network Repository Function (NRF) to discover the AMF(s) supporting MBS based on the MBS service area and select the appropriate one(s). Then the MB-SMF may send the Namf_MBSBroadcast_ContextCreate (TMGI, N2 Session Management (SM) information ([Lower Layer Source-Specific Multicast (LL SSM)], 5G Quality of Service (QoS) Profile), MBS service area, [MBS FSA I D(s)]) messages to the selected AMF(s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request.

3. The AMF may transfer the MBS Session Resource Setup Request message, which may contain the N2 SM information in the received Namf_MBSBroadcast_ContextCreate Request to all NG-RANs which may support MBS in the MBS service area. The AMF may include the MBS service area.

4. NG-RAN may create a Broadcast MBS Session Context and store the TMGI and the Quality of Service (QoS) Profile in the MBS Session Context. The LL SSM may be understood to be optional parameters and only provided by MB-SMF to NG-RAN if N3mb multicast transport is configured to be used in the 5GC. If MBS FSA ID(s) were received, the NG-RAN may use those MBS FSA ID(s)s to determine cells/frequencies within the MBS service area to broadcast MBS session data based on QAM configuration about the MBS FSA IDs and related frequencies.

5. If NG-RAN prefers to use N3mb multicast transport, and if LL SSM is available in NG- RAN, the NG-RAN may join the multicast group, that is, the LL SSM.

If NG-RAN prefers to use N3mb point-to-point transport, or if the LL SSM is not available in NG-RAN, between the NG-RAN and MB-UPF, NG-RAN may provide its N3mb DL Tunnel Info.

6. The NG-RAN may report successful establishment of the MBS Session resources, which may include multiple MBS QoS Flows, by sending MBS Session Resource Setup Response, TMGI, N2 SM information ([N3mb DL Tunnel Info])) message(s) to the AMF. N3mb DL Tunnel Info may only be available when point-to-point transport may apply between MB-UPF and NG-RAN. For more details, refer to TS 38.413 [15], 7. The AMF may transfer the Namf_MBSBroadcast_ContextCreate Response () to the MB- SMF. The AMF may need to respond success when it may receive the first success response from the NG-RAN(s). And if all NG-RAN(s) report failure, the AMF may need to respond failure. The MB-SMF may store the AMF(s) which may respond success in the MBS Session Context as the downstream nodes. If the AMF receives the NG-RAN response(s) from all involved NG-RAN(s), the AMF may need to include an indication of completion of the operation in all NG-RANs.

8. If N3mb point-to-point transport is to be used, that is, N3mb DL Tunnel Info is present in the Namf_MBSBroadcast_ContextCreate Response message from AMF, the MB-SMF may send an N4mb Session Modification Request to the MB-LIPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 8 may be skipped.

9. NG-RAN may broadcast the TMGI representing the MBS service over radio interface. Step 9 may take place in parallel with step 6.

10. Another NG-RAN may report successful establishment of the MBS Session resources, which may include multiple MBS QoS Flows, by sending MBS Session Resource Setup Response, TMGI, N2 SM information ([N3mb DL Tunnel Info]), message after the AMF transferred the Namf_MBSBroadcast_ContextCreate Response () to the MB-SMF.

11. The AMF may transfer the Namf_MBSBroadcast_ContextStatusNotify request () to the MB-SMF. When the AMF receives the response from all NG-RAN nodes, the AMF may include an indication of the completion of the operation. If the AMF does not receive responses from all NG-RAN nodes before the maximum response time elapses since the reception of the Namf_MBSBroadcast_ContextCreate Request, then the AMF may need to transfer the Namf_MBSBroadcast_ContextStatusNotify request () which may indicate partial success or failure.

12. If N3mb point-to-point transport is to be used, e.g., N3mb DL Tunnel Info is present in the MBS Session Start Response message from AMF, the MB-SMF may send an N4mb Session Modification Request to the MB-UPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 12 may be skipped.

13. The AF may start transmitting the Downlink (DL) media stream to MB-UPF using the N6mb Tunnel, or optionally un-tunnelled, that is, as an Internet Protocol (IP) multicast stream using the Higher Layer Multicast (HL MC) address.

14. The MB-UPF may transmit the media stream to NG-RAN via N3mb multicast transport or point-to-point transport.

15. The NG-RAN may transmit the received DL media stream using DL Point-to-Multipoint (PTM) resources. As a second note, NOTE 2, step 6-8 and 2-4 are comparable to step 2-5 and 6-7 in clause 7.2.1.4, respectively.

Multicast procedure

In TS 23.247 v17.2.0, the establishment of shared delivery procedure is described in clause 7.2.1.4 as follows.

7.2.1 .4 Establishment of shared delivery toward RAN node

In the following cases, the shared tunnel for shared delivery may be established between the NG-RAN and MB-LIPF:

In a first case, the first UE may be included in the context of the MBS session in the NG- RAN.

As a first note of this section, NOTE 1 , when the multicast MBS session is deactivated, if there is at least one UE joining the multicast MBS session in Radio Resource Control (RRC)- CONNECTED state in the NG-RAN, the shared delivery may not be released.

As a second note of this section, NOTE 2, share delivery establishment procedures may be used when MBS supporting NG-RAN node(s) get involved in the multicast MBS session regardless of the state of the multicast MBS session.

In a second case, handover to the target NG-RAN when the shared delivery tunnel is not established in the target RAN node for this multicast MBS session.

Figure 2 corresponds to Figure 7.2.1.4-1 : Establishment of shared delivery toward NG- RAN node, as described next. Each of the following paragraphs numbered 0-7 describe an action having the corresponding number in the flowchart of Figure 2.

1. An NG-RAN node may decide to establish shared delivery for a multicast MBS session when it may serve at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node may need to establish shared delivery for the location dependent contents of a multicast MBS session if it serves at least one UE assigned to an MBS session ID and area session ID.

2. The NG-RAN may send an N2 MBS Session request message, e.g., MBS Session ID, [Area Session ID], N2 SM information ([unicast DL tunnel Info]) towards the AMF.

If the NG-RAN node is configured to use unicast transport for the shared delivery, it may allocate a GPRS Tunnelling Protocol (GTP) tunnel endpoint and provide the unicast DL tunnel Info in the request, which may include the GTP tunnel endpoint and NG-RAN node address. For location dependent MBS services, the NG-RAN node may also provide the Area Session ID.

3. The AMF may select the MB-SMF serving the multicast MBS session, e.g., using the NRF discovery service or locally stored information. It may invoke Nmbsmf_MBSSession_Contextllpdate request, e.g., MBS Session ID, [Area Session ID], N2 SM information, to the MB-SMF.

The AMF may store the information of the NG-RAN nodes, e.g., NG-RAN node ID, for the subsequent signaling related to the multicast MBS Session.

4. [Conditional] If the MB-SMF received unicast DL tunnel Info in step 3, it may configure the MB-LIPF to send multicast data for the multicast MBS session, or location dependent content of the multicast MBS session if an area session ID was received, towards that GTP tunnel endpoint via unicast transport.

5. The MB-SMF may store the information of the AMF, e.g., AMF ID, in the MBS multicast session context, or location dependent part of the multicast MBS session context if an Area Session ID was received, to enable subsequent signalling towards that AMF.

6. The MB-SMF may send Nmbsmf_MBSSession_ContextUpdate response, e.g., MBS Session ID, [Area Session ID], N2 SM information ([TMGI], multicast QoS flow information, session status indication (active/inactive), [multicast DL tunnel Info], [MBS service areas]), to the AMF. If the MB-SMF did not receive unicast DL tunnel Info in step 3, it may provide the multicast DL tunnel info that may include transport multicast address, e.g., a LL SSM, and a GTP tunnel endpoint for multicast transport of the shared delivery.

7. The AMF may send an N2 MBS Session response message, e.g., MBS Session ID, [Area Session ID], N2 SM information, to the NG-RAN node. If the NG-RAN node receives the multicast DL tunnel Info of the shared delivery, it may use the transport multicast address included in the multicast DL tunnel info to join the multicast transport distribution.

In TS 23.247 v17.2.0, the release of shared delivery procedure is described in clause 7.2.2.4 as follows.

7.2.2.4 Release of shared delivery toward RAN node

In the following cases, the shared delivery tunnel may be released between NG-RAN and MB-UPF.

In a first case, the last UE may be excluded from the context of the multicast MBS session in the NG-RAN node.

In a second case, handover to the target NG-RAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node during handover preparation phase known by the source NG-RAN node.

In a third case, handover to the target E-UTRAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node.

In a fourth case, MBS session deletion. It may be noted that when the multicast MBS session is deactivated, the shared delivery may not be released if there is at least one UE is in Radio Resource Control (RRC)- CONNECTED state for this multicast MBS session.

Figure 3 corresponds to Figure 7.2.2.4-1 : Release of shared delivery toward RAN node, as described next. Each of the following paragraphs numbered 0-7 describe an action having the corresponding number in the flowchart of Figure 3.

1. RAN node may decide to release shared delivery for a multicast MBS session, e.g. because it no longer serves at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node may release shared delivery for the location dependent contents of a multicast MBS session if it no longer serves at least one UE assigned to an MBS session ID and Area Session ID.

2. The NG-RAN node may send N2 MBS Session release request, e.g., MBS Session ID, [Area Session ID], [N2 SM information ([GTP tunnel info], release indication)])], to the AMF. For location dependent services, the NG-RAN node may also provide the Area Session ID. The RAN node may include the unicast DL tunnel info if unicast transport is used for the shared delivery. If the NG-RAN node was configured to use multicast transport for the 5GC Shared MBS traffic delivery, the NG-RAN node may not include the N2 SM information in the message.

3. [Conditional] If the N2 SM information is received or it is the last RAN node controlled by the AMF serving the multicast MBS session, the AMF may invoke Nmbsmf_MBSSession_ContextUpdate request, e.g., MBS Session ID [Area Session ID], [leave indication], [N2 SM information], to the MB-SMF corresponding to the MB-SMF ID stored in the AMF for the MBS Session ID. If it is the last RAN node controlled by the AMF serving the multicast MBS session identified by the MBS Session ID or both the MBS Session ID and Area Session ID, if exists, the leave indication may be included.

4. [Conditional] If unicast transport was used towards the NG-RAN node, the MB-SMF may determine whether the context update is for tunnel release or create based on the release indication in the N2 container. If the MB-SMF determines the context update is for tunnel release, the MB-SMF may send N4mb Session Modification to the MB-UPF to release the N3mb tunnel used for the multicast MBS session, or location dependent content of the multicast MBS session if an Area Session ID was received, towards that RAN node using the received GTP tunnel info.

5. [Conditional] The MB-SMF may respond to the AMF with MBS Session ID and Area Session ID if received. If leave indication is received, the MB-SMF may also remove the information of the AMF from the context of the multicast MBS session. 6. The AMF may remove the information of the RAN node from the context of the multicast MBS session, or location dependent part of the multicast MBS session if an Area Session ID was received.

7. The AMF may send an N2 MBS Session release response, e.g., MBS Session ID, [Area Session ID], to the RAN node. The NG-RAN node may delete the GTP tunnel info, if unicast transport is used for the shared delivery, or sends Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) leave message to leave the multicast distribution tree, if multicast transport is used for the shared delivery. The NG- RAN node may release local resources for the multicast MBS session.

A shared delivery may be understood as, e.g., a "5GC Shared MBS traffic delivery", as defined, for example, in TS 23.247: 5GC Shared MBS traffic delivery. A 5G CN may receive a single copy of MBS data packets and may deliver a single copy of those MBS data packets to a RAN node.

Broadcast MBS Session Setup procedure (BL CR for TS 38.401)

In BL CR for TS 38.401 (R3-222926), Broadcast MBS Session Setup procedure is described as below. Figure 4 corresponds to Figure 8.xx.1.1-1 : Broadcast MBS Session Setup. Figure 8.xx.1.1-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions at Broadcast MBS Session Setup, as described next. Each of the following paragraphs numbered 0-11 describe an action having the corresponding number in the flowchart of Figure 4.

1. The 5GC may start the broadcast session by sending the NGAP Broadcast Session Setup Request message to the gNB containing the TMGI, Single Network Slice Selection Assistance information (S-NSSAI), 5G QoS Profile, area information and transport information, for NG-U multicast transport it may provide the IP multicast address and the IP source specific multicast address, for NG-U unicast transport it may provide an GTP UL Tunnel Endpoint Identifier (TEID), and optionally an alternative set of transport information.

2/3. The gNB-Centralized Unit (CU)-Control Plane (CP) may set up the broadcast bearer context, providing NG-U transport information from the 5GC to the gNB-CU-UP and receiving from the gNB-CU-UP the NG-U GTP DL TEID in case NG-U unicast transport was selected and an F1-U GTP UL TEID per MBS Radio Bearer (MRB).

4. In case of NG-U multicast transport, the gNB-CU-UP may join the NG-U multicast group. 5/6. The gNB-CU-CP may establish the Broadcast MBS Session Context at the Distributed Unit (DU), providing MRB configuration, other relevant session parameters and F1-U GTP UL TEID information, and receiving F1-U GTP DL TEID information.

7/8. The gNB-CU-CP may trigger BC Bearer Context Modification Request towards the gNB-CU-UP to provide the F1-U GTP DL TEID information.

9. The DU may configure broadcast resources and provide broadcast configuration information to the UEs by means of MBS Control Channel (MCCH).

10. The gNB-CU CP may successfully terminate the NGAP broadcast Session Setup procedure. In case the gNB has chosen NG-U unicast transport, NG-U GTP DL TEID information may be provided to the 5GC.

11. The broadcast MBS media stream may be provided to the UEs.

On NG-U, in case of location dependent broadcast MBS Sessions, multiple shared NG- U transport tunnels may need to be setup, one per Area Session ID served by the gNB. In case of shared NG-U termination: a) the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs, and b) at establishment of the BC bearer context in the gNB-CU- UP, the gNB-CU-UP may overwrite the QoS flow mapping indicated by the gNB-CU-CP, if the gNB-CU-CP has provided its consent to do so at BC bearer context setup. As an Editor’s Note, it was noted that providing the consent from the gNB-CU-CP to the gNB-CU-UP needs further discussions.

Multicast MBS Session Setup procedure (BL CR for TS 38.401)

In BL CR for TS 38.401 (R3-222926), Multicast MBS Session Setup procedure is described as below.

8.xx.1.2 Multicast MBS Session Activation

Figure 5 corresponds to Figure 8.xx.1.2-1: Multicast MBS Session Context establishment. Figure 8.xx.1.2-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions at Multicast MBS Session Activation.

1. A multicast session context may be established by the 5GC.

2/3. If not yet existing, the gNB-CU-CP may establish the multicast bearer context at the gNB-CU-UP, in order to retrieve for unicast NG-U transport the GTP DL TEID, a shared resource address, e.g., GTP DL TEID)

4/5. If applicable, the gNB-CU-CP may establish the Multicast Context at the DU, providing MRB configuration. It may contain MBS Area Session ID information. 6. Dependent on e.g., joined UEs, the gNB-Dll may trigger the establishment of an F1-LI tunnel, which may be established either per DU or per cell or per MBS Area Session ID. The receiving gNB-CU-CP may need to fetch a gNB side NG-U Transport Network Layer (TNL) address information for the gNB-CU-UP by means of a E1 AP MC Bearer Context Modification procedure.

7/8. The gNB-CU CP may trigger the NGAP Distribution Setup procedure. For unicast transport, DL/UL GTP TEIDs may be exchanged, for multicast transport, multicast address information may be fetched from the 5GC.

9/10. The gNB-CU-UP side of the F1-U and NG-U UP entity may be established by means of the E1AP MC Bearer Context Modification procedure, providing the DU side F1-U TNL address and the 5GC NG-U TNL address to the gNB-CU-UP, which may provide the gNB-CU-UP side F1-U TNL address in return.

11. The gNB-CU-UP side F1-U TNL address may be provided to the gNB-DU.

12. In case of NG-U multicast transport, the gNB-CU-UP may join the NG-U multicast group.

13. The gNB-CU-CP may RRC-configure each UE which may have joined the multicast group.

14. The gNB may successfully terminate the NGAP procedure for establishing the multicast session context.

15. The multicast MBS media stream may be provided to the UEs.

On NG-U, in case of location dependent multicast MBS Sessions, multiple shared NG-U transport tunnels may need to be setup, one per Area Session ID served by the gNB.

In case of shared NG-U termination: a) the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs, and b) at establishment of the MC bearer context in the gNB-CU-UP, the gNB-CU-UP may overwrite the QoS flow mapping indicated by the gNB-CU- CP, if the gNB-CU-CP has provided its consent to do so at MC bearer context setup. As an Editor’s Note, it was noted that providing the consent from the gNB-CU-CP to the gNB-CU-UP needs further discussions.

SUMMARY

As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

In RAN3 115E, a LS(R3-222867) has been sent from RAN3 to SA2 about providing a solution to enable common NG-U Termination Information in MBS. A common NG-U Termination, e.g., a Shared NG-ll Termination, may be understood to refer as a deployment of a Shared NG-ll Termination at NG-RAN, shared among gNBs, which may comprise a common entity for assignment of Packet Data Convergence Protocol (PDCP) COUNT values. Synchronisation in terms of MBS QoS flow to MRB mapping and PDCP Sequence Number (SN) size of the corresponding MRB among gNBs may be achieved by means of network implementation. RAN3 has informed SA2 that RAN3 has agreed on two schemes to enable neighbouring gNBs allocating the same PDCP SN to MBS user data packets.

A first alternative, alternative 1 , foresees the MB-UPF to associate identical sequence number information on NG-U/N3mb to gNBs allowing them to translate the NG-U/N3mb sequence numbers into PDCP Sequence Numbers which may enable UEs at inter-gNB handover to detect duplicates and, if configured, request retransmissions.

A second alternative, alternative 2, may enable NG-RAN nodes sharing a common User Plane (UP) entity comprising Service Data Adaption Protocol (SDAP)/PDCP protocol entities and a NG-U/N3mb termination at NG-RAN.

RAN3 denotes such entity a “shared NG-U termination”, referenced by a GTP-U tunnel address.

Consequently, UEs receiving MBS user data issued through such a “shared NG-U termination” may be able, at inter-gNB handover to detect duplicates and, if configured, request retransmissions - in the same way as in alternative 1.

As a combination of alternatives 1&2, RAN3 agreed that it may be possible to combine both schemes and apply it for both, broadcast and multicast MBS sessions.

Protocol support for alternative 1 is foreseen in TS 38.415, the NG-U User Plane protocol.

As to protocol support for alternative 2, RAN3 is discussing the possibility to support exchange availability of “shared NG-U terminations” via the NG-C/N2 interface in the following way: a) if the gNB is able to “offer” a “shared NG-U termination”, it may provide a reference to the MB-SMF, b) in turn, the MB-SMF may provide information about “available NG-U termination”, as offered by gNBs, to other gNBs on a per MBS Session(/Area Session ID) basis.

The resulting architectural and protocol impacts may require SA2 feedback. Assumed protocol changes may be as outlined below.

For broadcast, at MBS Session Start for Broadcast and MBS Session Update for Broadcast.

For multicast, at Establishment of shared delivery toward RAN node and Multicast session update.

According to the foregoing, it is an object of embodiments herein to improve the handling of an indication in a communications network. According to a first aspect of embodiments herein, the object is achieved by a method performed by a network node. The method is for handling common user plane. The network node operates in a communications network. The network node receives, directly or indirectly, first information from a first radio network node operating in the communications network. The first information indicates a first NG-ll common DL termination reference to be used by the first radio network node during a multicast procedure. The network node also receives, directly or indirectly, one or more second indications from a second radio network node operating in the communications network. The one or more second indications indicate a change to a shared delivery procedure from a unicast tunnel and a second NG-ll common DL termination information, or the second NG-ll common DL termination information, currently used by the second radio network node to the first NG-U DL termination reference.

According to a second aspect of embodiments herein, the object is achieved by a method performed by the second radio network node. The method is for handling common user plane. The second radio network node operates in the communications network. The second radio network node sends, directly or indirectly, the one or more second indications to the first network node operating in the communications network. The one or more second indications indicate the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information, or the second NG-U common DL termination information, currently used by the second radio network node, to the first NG-U DL termination reference indicated to be used by the first radio network node during the multicast procedure.

According to a third aspect of embodiments herein, the object is achieved by a method performed by a third network node. The method is for handling common user plane. The third network node operates in the communications network. The third network node exchanges one or more third indications with the first network node operating in the communications network. The one or more third indications indicate a modification to a session currently held by the second radio network node operating in the communications network. The modification comprises the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information, or the second NG- U common DL termination information, currently used by the second radio network node, to the first NG-U DL termination reference used by a first radio network node, to be used in the multicast procedure.

According to a fourth aspect of embodiments herein, the object is achieved by the network node, for handling common user plane. The network node is configured to operate in the communications network. The network node is further configured to receive, directly or indirectly, the first information from the first radio network node configured to operate in the communications network. The first information is configured to indicate the first NG-U common DL termination reference to be used by the first radio network node during the multicast procedure. The network node is also configured to receive, directly or indirectly, the one or more second indications from the second radio network node configured to operate in the communications network. The one or more second indications are configured to indicate the change to the shared delivery procedure from the unicast tunnel and the second NG-ll common DL termination information, or the second NG-ll common DL termination information, configured to be currently used by the second radio network node, to the first NG-U common DL termination reference.

According to a fifth aspect of embodiments herein, the object is achieved by the second radio network node, for handling common user plane. The second radio network node is configured to operate in the communications network. The second radio network node is further configured to send, directly or indirectly the one or more second indications to the first network node configured to operate in the communications network. The one or more second indications are configured to indicate the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information, or the second NG-U common DL termination information, being configured to be currently used by the second radio network node, to the first NG-U common DL termination reference configured to be indicated to be used by the first radio network node during the multicast procedure.

According to a sixth aspect of embodiments herein, the object is achieved by the third network node, for handling common user plane. The third network node is to operate in the communications network. The third network node is further configured to exchange the one or more third indications with the first network node configured to operate in the communications network. The one or more third indications are configured to indicate the modification to the session currently held by the second radio network node configured to operate in the communications network. The modification is configured to comprise the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information, or the second NG-U common DL termination information, configured to be currently used by the second radio network node, to the first NG-U DL termination reference configured to be used by the first radio network node, to be used in the multicast procedure.

According to a seventh aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the network node.

According to an eighth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the network node.

According to a ninth aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the second radio network node.

According to a tenth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the second radio network node.

According to an eleventh aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the third network node.

According to a twelfth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the third network node.

Embodiments herein may be understood to update the MBS procedures to enable the shared NG-ll termination for multicast MBS sessions in NG-RAN, which may allow a common NG-U termination, e.g., gNB-CU-UP, for multiple gNB-CU-CPs.

Embodiments herein may be understood to allow UEs to receive MBS user data issued through such a “shared NG-U termination” to be able, at inter-gNB handover to detect duplicates and, if configured, request retransmissions.

Embodiments herein may also enable to reduce the DL tunnel endpoints in NG-RAN to lower the number of the replication of the streams from MB-UPF.

By the network node receiving the first information, e.g., the shared NG-U termination sent from the first radio network node, e.g., in Distribution Setup Request, the network node may be enabled to keep track of the usage of shared NG-U terminations across radio network nodes, e.g., NG-RANs. In another words, the network node may be enabled to know radio network nodes using the same shared NG-U termination. In this way, the network nodes may be enabled to prevent the duplicating of the user plane tunnels towards the same shared NG-U termination, which may be understood to be an error scenario. The network node may be further enabled to then respond to the first radio network node properly.

By the network node receiving the one or more second indications, e.g., the shared NG- U termination sent from the second radio network node, e.g., in Distribution Release Request, the network node may be enabled to keep track of the usage of shared NG-U terminations across radio network nodes, e.g., NG-RANs, together with the first information. In this way, the network node may be enabled to avoid releasing a user plane tunnel which may be in use by some other radio network nodes.

As a summary, network node may be able to establish/release user plane tunnel towards the shared NG-ll termination in a correct way, to enable the shared NG-ll termination across multiple radio network nodes, e.g., NG-RANs.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail with reference to the accompanying drawings, and according to the following description.

Figure 1 is a schematic representation depicting an example of MBS Session Establishment for Broadcast, according to existing methods.

Figure 2 is a schematic representation depicting an example of Establishment of shared delivery toward NG-RAN node, according to existing methods.

Figure 3 is a schematic representation depicting an example of Release of shared delivery toward RAN node, according to existing methods.

Figure 4 is a schematic representation depicting an example of a Broadcast MBS Session Setup, according to existing methods.

Figure 5 is a schematic representation depicting an example of a Multicast MBS Session Context establishment, according to existing methods.

Figure 6 is a schematic diagram illustrating a communications system, according to embodiments herein.

Figure 7 is a flowchart depicting an example of a method in a network node, according to embodiments herein.

Figure 8 is a flowchart depicting an example of a method in a second radio network node, according to embodiments herein.

Figure 9 is a flowchart depicting an example of a method in a third network node, according to embodiments herein.

Figure 10 is a schematic representation depicting a non-limiting example of a method in a communications network, according to embodiments herein.

Figure 11 is a schematic representation depicting another non-limiting example of a method in a communications network, according to embodiments herein.

Figure 12 is a schematic block diagram illustrating two non-limiting examples, a) and b) of a network node, according to embodiments herein.

Figure 13 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a second radio network node, according to embodiments herein. Figure 14 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a third network node, according to embodiments herein.

Figure 15 is a flowchart depicting an example of a first method in a network node, according to examples related to embodiments herein.

Figure 16 is a flowchart depicting an example of a second method in a network node, according to examples related to embodiments herein.

Figure 17 is a flowchart depicting an example of a method in a first radio network node, according to examples related to embodiments herein.

Figure 18 is a flowchart depicting an example of a method in a second radio network node, according to examples related to embodiments herein.

Figure 19 is a flowchart depicting an example of a method in a third network node, according to examples related to embodiments herein.

Figure 20 is a schematic representation depicting a further non-limiting example of a first method in a communications network, according to examples related to embodiments herein.

Figure 21 is a schematic block diagram illustrating four non-limiting examples a), b), c) and d) of a network node, according to examples related to embodiments herein.

Figure 22 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a first radio network node, according to examples related to embodiments herein.

Figure 23 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a second radio network node, according to examples related to embodiments herein.

Figure 24 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a third network node, according to examples related to embodiments herein.

Figure 25 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to embodiments herein.

Figure 26 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to embodiments herein.

Figure 27 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 28 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

Figure 29 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein. Figure 30 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

DETAILED DESCRIPTION

Certain aspects of the present disclosure and their embodiments may provide solutions to this challenge or other challenges. There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

Embodiments and/or the disclosure herein may be understood to be related to methods of NG-RAN Common User Plane in MBS.

Embodiments and/or the disclosure herein may relate to two aspects: Broadcast procedure and Multicast procedure.

Broadcast procedure:

In Broadcast Context Create request towards AMF, MB-SMF may include a list of “IP address of the NG-RAN UP” to allow NG-RAN to use common user plane entity in N2 message of “Broadcast Session Setup Request” to NG-RAN.

NG-RAN may use the list of IP addresses of the NG-RAN UP to select the common user plane entity.

Multicast procedure

In description below, “common DL termination info” may include only IP address of the common NG-RAN UP, or include both the IP address and TEID of the common NG-RAN UP.

In “MBS Distribution Setup Request” from NG-RAN to MB-SMF, “Common DL termination info”, e.g., common DL termination info 1, may be provided by NG-RAN. In MBS Session Context update request, AMF may include NG-RAN ID to MB-SMF. MB-SMF may store the common DL termination info with NG-RAN ID within the multicast MBS session context.

In “MBS Distribution Setup Response” to NG-RAN, MB-SMF may include the “list of common DL termination info” it may store. NG-RAN may determine whether one of the common DL termination info in the list may be used. If it determines to use one of them, e.g., common DL termination info 2, the following options may apply.

According to a first option, Option 1 , it may trigger “release of shared delivery procedure” to MB-SMF to release the downlink tunnel it may have allocated. In this procedure, “Common DL termination info”, e.g., common DL termination info 1 , may be included as well, MB-SMF may remove it from the stored list. Also according to the first option, it may trigger establishment of shared delivery procedure with the selected common DL termination info, e.g., common DL termination info 2, to MB-SMF.

According to a second option, Option 2, combine the “release of shared delivery procedure” and “establishment of shared delivery procedure” into “modify shared delivery procedure”. NG-RAN may include both the common DL tunnel to be released, e.g., common DL termination info 1 , and the common DL tunnel to be established, e.g., common DL termination info 2, in N2 message. The N2 request may be sent from NG-RAN to MB-SMF via AMF. AMF may add NG-RAN ID.

Also according to the second option, after receiving the request, MB-SMF may remove the common DL tunnel to be released, e.g., common DL termination info 1 , with NG-RAN ID from the stored list, and add the common DL tunnel to be established, e.g., common DL termination info 2, with NG-RAN ID in the stored list.

Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

Note that although terminology from LTE/5G has been used in this disclosure to exemplify the embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system. Other wireless systems with similar features may also benefit from exploiting the ideas covered within this disclosure.

Figure 6 depicts four non-limiting examples, in panels “a”, “b”, “c” and “d”, respectively, of a communications network 100, in which embodiments herein may be implemented. In some example implementations, such as that depicted in the non-limiting example of Figure 6a, and Figure 6c, the communications network 100 may be a computer network. In other example implementations, such as that depicted in the non-limiting example of Figure 6b and Figure 6d, the communications network 100 may be implemented in a telecommunications system, sometimes also referred to as a telecommunications network, cellular radio system, cellular network, or wireless communications system. In some examples, the telecommunications system may comprise network nodes which may serve receiving nodes, such as wireless devices, with serving beams. In some examples, the telecommunications system may for example be a network such as a 5G system, or a newer system supporting similar functionality. The telecommunications system may also support other technologies, such as a Long-Term Evolution (LTE) network, e.g., LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE HalfDuplex Frequency Division Duplex (HD-FDD), or LTE operating in an unlicensed band, Wideband Code Division Multiple Access (WCDMA), UTRA TDD, Global System for Mobile communications (GSM) network, GSM/Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising of any combination of Radio Access Technologies (RATs) such as e.g. MultiStandard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network/s (WLAN) or WiFi network/s, Worldwide Interoperability for Microwave Access (WiMax), IEEE 802.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide Area Network (LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

The communications network 100 comprises a network node 101, 102. The network node 101, 102 may be any of a first network node 101, a second network node 102, as depicted in the non-limiting examples of Figure 6. In some embodiments, such as that depicted in panel c) and panel d) of Figure 6, the communications network 100 may comprise a third network node 103. It may be understood that the communications network 100 may comprise more network nodes than those represented on Figure 6.

Any of the first network node 101, the second network node 102 and the third network node 103 may be understood, respectively, as a first computer system, a second computer system, and a third computer system. In some examples, any of the first network node 101, the second network node 102 and the third network node 103 may be implemented as a standalone server in e.g., a host computer in the cloud 105, as depicted in the non-limiting example depicted in panel b) and panel d) of Figure 6. Any of the first network node 101 , the second network node 102 and the third network node 103 may in some examples be a distributed node or distributed server, with some of their respective functions being implemented locally, e.g., by a client manager, and some of its functions implemented in the cloud 105, by e.g., a server manager. Yet in other examples, any of the first network node 101 , the second network node 102 and the third network node 103 may also be implemented as processing resources in a server farm. Any of the first network node 101, the second network node 102 and the third network node 103 may be a core network node in the communications network 100. Any of the first network node 101, the second network node 102 and the third network node 103 may be independent and separate nodes. In some examples, any of the first network node 101 , the second network node 102 and the third network node 103 may be colocalized or be the same node.

In some examples of embodiments herein, the first network node 101 may be understood as a node that may have a capability to support different functionalities, e.g., session establishment, modify and release, and policy related functionalities such as termination of interfaces towards policy control functions. As depicted in the non-limiting example of Figure 6, a non-limiting example of the first network node 101, wherein the communications network 100 may be a 5G network, may be a Session Management Function (SMF).

The second network node 102 may be a node having a capability to handle notifications about group data for a device. As depicted in the non-limiting example of Figure 6, a nonlimiting example of the second network node 102, wherein the communications network 100 may be a 5G network, may be an Access and Mobility Function (AMF).

The third network node 103 may be a node having a capability to enforce policy decisions according to provisioned rules, e.g., Policy and Charging Control (PCC) rules. In some particular examples, such as in those wherein the communications network 100 may be a 5G network, the third network node 103 may be a User Plane function (UPF).

The communications network 100 further comprises a first radio network node 111, and a second radio network node 112, as depicted in the non-limiting examples of Figure 6. It may be understood that the communications network 100 may comprise further radio network nodes than those represented on Figure 6. Any of the first radio network node 111 and the second radio network node 112 may be a radio network node. That is, a transmission point such as a radio base station, for example a gNB, an eNB, or any other network node with similar features capable of serving a wireless device, such as a user equipment or a machine type communication device, in the communications network 100. In other examples, which are not depicted in Figure 6, any of the first radio network node 111 and the second radio network node 112 may be a distributed node, such as a virtual node in the cloud 105, and may perform its functions entirely on the cloud 105, or partially, in collaboration with a radio network node. The first radio network node 111 and the second radio network node 112 may, in some examples, be co-located or be the same network node. In typical examples, such as those depicted in Figure 6, the first radio network node 111 and the second radio network node 112 may be different nodes.

The communications network 100 covers a geographical area which may be divided into cell areas, wherein each cell area may be served by a radio network node, although, one radio network node may serve one or several cells. The communications network 100 may comprise a first cell 121 , which may be served by the first radio network node 111. The communications network 100 may also comprise a second cell 122, which may be served by the second radio network node 112.

Any of the first radio network node 111 and the second radio network node 112 may be of different classes, such as, e.g., macro base station, home base station or pico base station, based on transmission power and thereby also cell size. Any of the first radio network node 111 and the second radio network node 112 may support one or several communication technologies, and its name may depend on the technology and terminology used. In 5G/NR, any of the first radio network node 111 and the second radio network node 112 may be referred to as a gNB and may be directly connected to one or more core networks.

The communication network 100 may comprise a wireless device 130. The wireless device 130 may be a wireless communication device such as a 5G UE, or a UE, which may also be known as e.g., mobile terminal, wireless terminal and/or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. The wireless device 130 comprised in the communications network 100 may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and/or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system. The wireless device 130 may be enabled to communicate wirelessly in the communications network 100. The communication may be performed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the communications network 100. It may be understood that the communications network 100 may comprise further wireless devices such as the wireless device 130.

The first network node 101 may be configured to communicate within the communications network 100 with the second network node 102 over a first link 141 , e.g., a wired link. The second network node 102 may be configured to communicate within the communications network 100 with the first radio network node 111 over a second link 142, e.g., a wired link or a radio link. The second network node 102 may be configured to communicate within the communications network 100 with the second radio network node 112 over a third link 143, e.g., a wired link or a radio link. The first network node 101 may be configured to communicate within the communications network 100 with the third network node 103 over a fourth link 144, e.g., a wired link. The first radio network node 111 may be configured to communicate within the communications network 100 with the wireless device 130 over a fifth link 145, e.g., a radio link. The second radio network node 112 may be configured to communicate within the communications network 100 with the wireless device 130 over a sixth link 146, e.g., a radio link. The first radio network node 111 may be configured to communicate within the communications network 100 with the second radio network node 112 over a seventh link 147, e.g., a wired link or a radio link.

Any of the respective first link 141, the second link 142, the third link 143, the fourth link 144, the fifth link 145, the sixth link 146 and/or the seventh link 147 may be a direct link or it may go via one or more computer systems or one or more core networks in the communications system 100, or it may go via an optional intermediate network. The intermediate network may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network, if any, may be a backbone network or the Internet, which is not shown in Figure 6.

In general, the usage of “first”, “second”, “third”, “fourth”, “fifth”, “sixth” and/or “seventh” herein may be understood to be an arbitrary way to denote different elements or entities and may be understood to not confer a cumulative or chronological character to the nouns these adjectives modify.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

More specifically, the following are embodiments related to a network node, such as the network node 101 , 102, e.g., a core network node, embodiments related to a first radio network node, such as the first radio network node 111, e.g., a first NG-RAN node, embodiments related to a second radio network node, such as the second radio network node 112, e.g., a second NG-RAN node, and embodiments related to a third network node, such as the third network node 103, e.g., another core network node.

Embodiments of a method, performed by the network node 101 , 102, will now be described with reference to the flowchart depicted in Figure 7. The method is for handling common user plane. The method may be understood to be computer-implemented. The network node 101, 102 operates in the communications network 100.

Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, some actions may be optional. In Figure 4, optional actions are indicated with dashed lines. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

Action 701

In this Action 701 , the network node 101 , 102 receives, directly or indirectly, first information from the first radio network node 111 operating in the communications network 100. The first information indicates a first Next Generation (NG)-User Plane (II) common Downlink (DL) termination reference to be used by the first radio network node 111 during a multicast procedure.

The first information may comprise common DL Termination information. The common DL termination information may comprise one or more Internet Protocol (IP) addresses of a common NG-RAN UP, alone or together with a Tunnel Endpoint Identifier (TEID).

Each IP address may correspond to a user plane entity of a radio network node comprised in the area.

In some embodiments, the network node 101 may be the first network node 101 , and the first information may be sent indirectly, via the second network node 102.

The first network node 101 may be a Multicast Broadcast (MB)-Session Management Function (SMF) and the second network node 102 may be an AMF.

The network node 101 may be the first network node 101 and the first information may be received in a distribution setup request.

Action 702

In this Action 702, the network node 101 , 102 may be the first network node 101 , and the network node 101 , 102 may further store the received first information within a session context for a Multicast Broadcast Service (MBS).

Action 703

In some embodiments, in this Action 703, the network node 101 , 102 may send, directly or indirectly, a first indication to the second radio network node 112. The first indication may indicate one or more NG-U common DL termination references to be used during the multicast procedure. The first indication may comprise the received first information.

Action 704

In this Action 704, the network node 101 , 102 receives, directly or indirectly, one or more second indications from a second radio network node 112 operating in the communications network 100. The one or more second indications indicate a change to a shared delivery procedure from a unicast tunnel and a second NG-U common DL termination information, or the second NG-U common DL termination information, currently used by the second radio network node 112 to the first NG-U common DL termination reference. In some embodiments, at least one of the following may apply: a) the first NG-ll common DL termination reference indicated by the one or more second indications may be a selected NG-ll common DL termination reference of the one or more NG-ll common DL termination references indicated by the network node 101 , 102, b) the one or more NG-U common DL termination references may correspond to an area serviced by the network node 101 , 102, c) the first information may comprise common DL Termination information, d) the network node 101 may be the first network node 101, and the first information may be sent indirectly, via the second network node 102, e) the first network node 101 may be an MB-SMF, the second network node 102 may be an AMF, and the second radio network node 112 may be a second NG- RAN node, f) the network node 101 may be a first network node 101 and the first information may be received in a distribution setup request, g) the common DL termination information may comprise one or more Internet Protocol (IP) addresses of the common NG- RAN UP alone or together with a TEID, and h) each IP address may correspond to a user plane entity of a radio network node comprised in the area.

The one or more second indications may comprise a first second indication requesting to release a current shared delivery procedure with tunnel information currently used by the second radio network node 112.

In some embodiments, the network node 101 may be the first network node 101 , the first information may be sent indirectly, via the second network node 102, the first network node 101 may be the MB-SMF, the second network node 102 may be the AMF, the second radio network node 112 may be the second NG-RAN node, the first information may comprise common DL Termination information, and at least one of the following may apply: a) the first information may further comprise unicast DL tunnel information, and b) with the proviso the MB-SMF determines the unicast DL tunnel in the first information exists already, the MB-SMF may refrain from configuring the third network node 103 operating in the communications network 100. In such embodiments, the third network node 103 may be a MB-UPF. In such embodiments, the MB-SMF may further keep track on a number of NG-RAN nodes currently using the unicast DL tunnel and the common DL termination information.

In some embodiments, the network node 101 may be the first network node 101 , the first information may be sent indirectly, via the second network node 102, the first network node 101 may be the MB-SMF, the second network node 102 may be the AMF, the second radio network node 112 may be the second NG-RAN node, the first information may comprise common DL Termination information, the one or more second indications may comprise the first second indication and, with the proviso the MB-SMF may determine a context update indicated by the first second indication is for tunnel release, the MB-SMF may decrease the number of NG-RAN nodes using the common DL Termination indicated by the first second indication. Action 705

In this Action 705, the network node 101, 102 may exchange, in response to the received one or more second indications, one or more third indications with the third network node 103 operating in the communications network 100. The one or more third indications may indicate a modification to a session currently held by the second radio network node 112, the modification being based on the received one or more second indications.

Action 706

In this Action 706, the network node 101, 102 may send, directly or indirectly, in response to the exchanged one or more third indications, a fourth indication to the second radio network node 112. The fourth indication may indicate an update to the shared delivery procedure.

Embodiments of a computer-implemented method, performed by the second radio network node 112, will now be described with reference to the flowchart depicted in Figure 8. The method is for handling common user plane. The second radio network node 112 operates in the communications network 100.

Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, some actions may be optional. In Figure 8, optional actions are indicated with dashed lines. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. For example, in some embodiments, the actuations may comprise an HO actuation.

Action 801

In this Action 801 , the second radio network node 112 may receive, directly or indirectly, the first indication from the first network node 101. The first indication may indicate the one or more NG-ll common termination references to be used during the multicast procedure. The first indication may comprise the first information, that is, the first information as it may have been received by the network node 101, 102. Action 802

In embodiments, in this Action 802, the second radio network node 112 may select at least one of the one or more NG-ll common termination references to be used during the multicast procedure indicated in the received first indication.

Action 803

In this Action 803, the second radio network node 112 sends, directly or indirectly the one or more second indications to the first network node 101 operating in the communications network 100. The one or more second indications indicate the change to the shared delivery procedure from the unicast tunnel and the second NG-ll common DL termination information, or the second NG-ll common DL termination information, currently used by the second radio network node 112, to the first NG-ll common DL termination reference indicated to be used by the first radio network node 111 during the multicast procedure.

In some embodiments, at least one of the following may apply: a) the first NG-U common DL termination reference may be the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, b) the one or more NG-U common DL termination references may correspond to the area serviced by the first network node 101 , c) the first network node 101 may be an MB-SMF, the second network node 102 may be an AMF, and the second radio network node 112 may be a second NG-RAN node, d) the common DL termination information may comprise one or more IP addresses of the common NG-RAN UP alone or together with a TEID, h) each IP address may correspond to a user plane entity of a radio network node comprised in the area, and i) the one or more second indications may be sent indirectly to the first network node 101 via the second network node 102.

The one or more second indications may comprise the first second indication requesting to release the current shared delivery procedure with tunnel information currently used by the second radio network node 112.

Action 804

In this Action 804, the second radio network node 112 may receive, directly or indirectly, in response to the sent one or more second indications, the fourth indication from the network node 101 , 102. The fourth indication indicates the update to the shared delivery procedure, e.g., an updated common NG-U termination list.

Embodiments of a computer-implemented method, performed by the third network node

103, will now be described with reference to the flowchart depicted in Figure 9. The method is for handling common user plane. The third network node 103, operates in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

Action 901

In this Action 901 , the third network node 103 exchanges one or more third indications with the first network node 101 operating in the communications network 100. The one or more third indications indicate a modification to a session currently held by the second radio network node 112 operating in the communications network 100. The modification comprises the change to the shared delivery procedure from the unicast tunnel and the second NG-ll common DL termination information, or the second NG-ll common DL termination information, currently used by the second radio network node 112, to a first NG-ll DL termination reference used by the first radio network node 111 , to be used in the multicast procedure.

In some embodiments, at least one of the following may apply: a) the first network node 101 may be an MB-SMF, and the second radio network node 112 may be a second NG-RAN node, b) the common DL termination information may comprise one or more IP addresses, e.g., an IP address, of the common NG-RAN UP alone or together with a TEID, and c) each IP address may correspond to the user plane entity of the radio network node comprised in the area.

Some embodiments herein will now be further described with some non-limiting examples.

In the following description, any reference to a/the “NG-RAN1”, and/or a/the “first NG- RAN” in the context of Figures 10-11, and/or “NG-RAN” and/or “NG-RAN node” in the context of Figure 12, may be understood to equally refer to any of the first radio network node 111; any reference to a/the “NG-RAN2”, and/or a/the “second NG-RAN”, in the context of Figures 10-11 may be understood to equally refer to any of the second radio network node 112; any reference to a/the “MB-SMF” may be understood to equally refer to the first network node 101; any reference to a/the “AMF” may be understood to equally refer to the second network node 102; any reference to a/the “MB-UPF” may be understood to equally refer to the third network node 103; any reference to a/the UE may be understood to equally refer the wireless device 130. According to embodiments herein, the approach of Common User Plane addresses the following two scenarios: Establishment of shared delivery towards RAN node, and Release of shared delivery towards RAN node. Both scenarios entail updates to clauses in TS 23.247, v. 17.2.0, as follows.

Update to clause 7.2.1.4 Establishment of shared delivery toward RAN node of TS 23.247 V17.2.0 ======== below shows the changes to clause 7.2.1.4========= 7.2.1.4 Establishment of shared delivery toward RAN node

In the following cases, the shared tunnel for shared delivery may be established between the NG-RAN and MB-UPF:

The first UE may be included in the context of the Multicast/Broadcast Service (MBS) session in the NG-RAN

NOTE 1 : When the multicast MBS session is deactivated, if there is at least one UE joining the multicast MBS session in RRC-CONNECTED state in the NG-RAN, the shared delivery may not be released.

NOTE 2: Share delivery establishment procedures may be used when MBS supporting NG-RAN node(s) get involved in the multicast MBS session regardless of the state of the multicast MBS session.

- Handover to the target NG-RAN when the shared delivery tunnel is not established in the target RAN node for this multicast MBS session.

Figure 10 is a schematic representation depicting a non-limiting example of a method in a communications network, according to embodiments herein. The signalling diagram depicted in Figure 10 is based on Figure 7.2.1.4-1: Establishment of shared delivery toward NG-RAN node. In the non-limiting example of Figure 10, the network node 101 is a first network node 111 and is an MB-SMF, the second network node 112 is an AMF, the third network node 103 is an MB-UPF, the first radio network node 111 is a first NG-RAN, NG- RAN1 and the second radio network node 112 is a second NG-RAN. The actions depicted are described below. In the description below, “common DL termination info” may include only IP address of the common NG-RAN UP, or include both the IP address and TEID of the common NG-RAN UP.

1. A NG-RAN, NG-RAN1, node may decide to establish shared delivery for a multicast MBS session when it may serve at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node may need to establish shared delivery for the location dependent contents of a multicast MBS session if it serves at least one UE assigned to an MBS session ID and area session ID.

2. The NG-RAN1 may send an N2 MBS Session request message, e.g., MBS Session ID, [Area Session ID], N2 SM information ([unicast DL tunnel Info], [List of common DL termination info), towards the AMF. The N2 SM information may be understood to correspond to the first information.

If the NG-RAN node is configured to use unicast transport for the shared delivery, it may allocate a GTP tunnel endpoint and provide the unicast DL tunnel Info in the request, which may include the GTP tunnel endpoint and NG-RAN node address. For location dependent MBS services, the NG-RAN node may also provide the Area Session ID.

3. The AMF may select the MB- Session Management Function (SMF) serving the multicast MBS session, e.g. using the NRF discovery service or locally stored information. It may invoke Nmbsmf_MBSSession_ContextUpdate request, e.g., MBS Session ID, [Area Session ID], N2 SM information, to the MB-SMF, in accordance with Action 701.

The AMF may store the information of the NG-RAN nodes, e.g., NG-RAN node ID, for the subsequent signaling related to the multicast MBS Session.

4. [Conditional] If the MB-SMF received unicast DL tunnel Info in step 3, it may configure the MB-UPF to send multicast data for the multicast MBS session, or location dependent content of the multicast MBS session if an area session ID was received, towards that GTP tunnel endpoint via unicast transport. If MB-SMF determines the unicast DL tunnel, also common DL termination info, exist already, it may not configure the MB-UPF and just keep track on the number of NG-RAN nodes currently using the unicast DL tunnel as well as common DL termination info.

5. The MB-SMF, in accordance with Action 702, may store the information of the AMF, e.g, AMF ID, in the MBS multicast session context, or location dependent part of the multicast MBS session context if an Area Session ID was received, to enable subsequent signalling towards that AMF.

6. The MB-SMF may send Nmbsmf_MBSSession_ContextUpdate response, e.g., MBS Session ID, [Area Session ID], N2 SM information ([TMGI], multicast QoS flow information, session status indication (active/inactive), [multicast DL tunnel Info], [List of common DL termination info], [MBS service areas])) to the AMF. If the MB-SMF did not receive unicast DL tunnel Info in step 3, it may provide the multicast DL tunnel info that may include transport multicast address, e.g., a LL SSM, and a GTP tunnel endpoint for multicast transport of the shared delivery.

7. The AMF may send an N2 MBS Session response message, e.g., MBS Session ID, [Area Session ID], N2 SM information, to the NG-RAN node. If the NG-RAN node receives the multicast DL tunnel Info of the shared delivery, it may use the transport multicast address included in the multicast DL tunnel info to join the multicast transport distribution.

8. When the second NG-RAN may decide to establish shared delivery for a multicast MBS session when it may serve at least one UE within the multicast MBS session, steps as in steps 2-5 may be performed. If the unicast DL tunnel Info and common DL termination info from the second NG-RAN are different from that of the first NG-RAN, steps 9-17 may apply.

9. Same as step 6 except that the List of common DL termination info is updated to include the common DL termination info received from the second NG-RAN. Action 9 is in accordance with Action 703 and Action 801 .

10. Same as step 7 except that common DL termination info for the first NG-RAN may be provided in the N2 SM information.

Option-1 : steps 11-12 may be performed

11 . Based on the received common DL termination info, the second NG-RAN may release the shared delivery as specified below. The second NG-RAN may establish the shared delivery as captured in the section entitled ’’Update to clause 7.2.2.4 Release of shared delivery toward RAN node of TS 23.247 v17.2.0” of this document.

12. The second NG-RAN may establish the shared delivery as in steps 2-7 but with the unicast DL tunnel Info and common DL termination info provided by the first NG-RAN.

Option-2: steps 13-17 may be performed.

13-17. The second NG-RAN may send N2 MBS Session Modify Request to replace the unicast DL tunnel Info with the unicast DL tunnel Info provided by the first NG-RAN. MB-SMF may update MB-UPF to replace the DL N3mb Tunnel Info with the unicast DL tunnel Info provided by the first NG-RAN. Action 14 is in accordance with Action 704 and Actions 801 and 803. Action 15 is in accordance with Action 705 and Action 901. Action 16 is in accordance with Action 706 and Action 804.

Jpdate to clause 7.2.2.4 Release of shared delivery toward RAN node of TS 23.247 v17.2.0 ======== below shows the changes to clause 7.2.2.4=========

7.2.2.4 Release of shared delivery toward RAN node

In the following case, the shared delivery tunnel may be released between NG-RAN and MB-UPF:

The last UE may be excluded from the context of the multicast MBS session in the NG- RAN node; - Handover to the target NG-RAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node during handover preparation phase known by the source NG-RAN node;

- Handover to the target E-UTRAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node;

- MBS session deletion.

NOTE: When the multicast MBS session is deactivated, the shared delivery may not be released if there is at least one UE is in RRC-CONNECTED state for this multicast MBS session.

Figure 11 is a schematic representation depicting another non-limiting example of a method in a communications network, according to embodiments herein. Figure 13 is based on Figure 7.2.2.4-1: Release of shared delivery toward RAN node. In the non-limiting example of Figure 11 , the network node 101 is a first network node 111 and is an MB-SMF, the second network node 112 is an AMF, the third network node 103 is an MB-UPF and the first radio network node 111 is an NG-RAN. The actions depicted are described below.

1. A RAN node may decide to release shared delivery for a multicast MBS session, e.g. because it no longer serves at least one UE within the multicast MBS session. For location dependent services, the NG-RAN node may release shared delivery for the location dependent contents of a multicast MBS session if it no longer serves at least one UE assigned to an MBS session ID and Area Session ID.

2. The NG-RAN node may send N2 MBS Session release request, e.g., MBS Session ID, [Area Session ID], [N2 SM information ([GTP tunnel info], release indication, [common DL termination info])])]) to the AMF. For location dependent services, the NG-RAN node also may also provide the Area Session ID. The RAN node may include the unicast DL tunnel info if unicast transport is used for the shared delivery. If the NG-RAN node was configured to use multicast transport for the 5GC Shared MBS traffic delivery, the NG- RAN node may not include the N2 SM information in the message.

3. [Conditional] If the N2 SM information is received or it is the last RAN node controlled by the AMF serving the multicast MBS session, the AMF may invoke Nmbsmf_MBSSession_ContextUpdate request, e.g., MBS Session ID [Area Session ID], [leave indication], [N2 SM information], to the MB-SMF corresponding to the MB-SMF ID stored in the AMF for the MBS Session ID. If it is the last RAN node controlled by the AMF serving the multicast MBS session identified by the MBS Session ID or both the MBS Session ID and Area Session ID, if exists, the leave indication may be included.

4. [Conditional] If unicast transport was used towards the NG-RAN node, the MB-SMF may determine whether the context update is for tunnel release or create based on the release indication in the N2 container. If the MB-SMF determines the context update is for tunnel release, MB-SMF may decrease the number of NG-RAN nodes using the GTP tunnel info. If no NG-RANs are using the GTP tunnel info, the MB-SMF may send N4mb Session Modification to the MB-LIPF to release the N3mb tunnel used for the multicast MBS session, or location dependent content of the multicast MBS session if an Area Session ID was received, towards that RAN node using the received GTP tunnel info. If common DL termination info is provided, MB-SMF may decrease the number of NG- RAN nodes using the common DL termination info. If no NG-RANs are using the common DL termination info, MB-SMF may remove the common DL termination info from the stored list.

5. [Conditional] The MB-SMF may respond to the AMF with MBS Session ID and Area Session ID if received. If leave indication is received, the MB-SMF may also remove the information of the AMF from the context of the multicast MBS session.

6. The AMF may remove the information of the RAN node from the context of the multicast MBS session (or location dependent part of the multicast MBS session if an Area Session ID was received).

7. The AMF may send an N2 MBS Session release response, e.g., MBS Session ID, [Area Session ID]) to the RAN node. The NG-RAN node may delete the GTP tunnel info, if unicast transport is used for the shared delivery, or sends IGMP/MLD leave message to leave the multicast distribution tree, if multicast transport is used for the shared delivery. The NG-RAN node may release local resources for the multicast MBS session.

As a summarized overview of the foregoing, embodiments herein may be understood to Multicast:

In “Distribution Setup Response”, introduce the means for the MB-SMF to provide an ordered list of Common NG-U Termination references to allow the NG-RAN to get aware of available shared Common NG-U Terminations.

NG-RAN nodes may decide to switch to a shared Common NG-U Termination indicated by the MB-SMF by means of issuing a Distribution Setup Request and releasing the previously established NG-U Termination by means of Distribution Release Request, in which ever order, and indicate to the MB-SMF in both procedures how they may be linked to each other by a certain indication, e.g., a Transaction ID or a simple flag. It may also be possible to issue Distribution Modify Request to release the previously established NG-U termination and setup the newly decided one at one time.

Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as follows. Embodiments herein may be understood to update the MBS procedures to enable the shared NG-ll termination for multicast and broadcast MBS sessions in NG-RAN, which may allow a common NG-ll termination, e.g., gNB-CU-UP, for multiple gNB-CU-CPs.

Embodiments herein may be understood to allow UEs to receive MBS user data issued through such a “shared NG-ll termination” to be able, at inter-gNB handover to detect duplicates and, if configured, request retransmissions.

Embodiments herein may also reduce the DL tunnel endpoints in NG-RAN to lower the number of the replication of the streams from MB-LIPF.

Figure 12 depicts two different examples in panels a) and b), respectively, of the arrangement that the network node 101 , 102 may comprise to perform the second method described in Figure 7 and/or Figures 10-11. The network node 101, 102 may be understood to be for handling common user plane. The network node 101, 102 is configured to operate in the communications network 100. In some embodiments, the network node 101, 102 may comprise the following arrangement depicted in Figure 12a.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

In Figure 12, optional units are indicated with dashed boxes.

The network node 101, 102 is configured to perform the receiving of Action 701, e.g., by means of a receiving unit 1201 within the network node 101, 102, configured to receive, directly or indirectly, the first information from the first radio network node 111 configured to operate in the communications network 100. The first information is configured to indicate the first NG-ll common DL termination reference to be used by the first radio network node 111 during the multicast procedure.

The network node 101, 102 is also configured to perform the receiving of Action 704, e.g. by means of the receiving unit 1201 within the network node 101, 102, configured to receive, directly or indirectly, the one or more second indications from the second radio network node 112 configured to operate in the communications network 100. The one or more second indications are configured to indicate the change to the shared delivery procedure from the unicast tunnel and the second NG-ll common DL termination information, or the second NG-U common DL termination information, configured to be currently used by the second radio network node 112, to the first NG-U common DL termination reference.

In some embodiments, at least one of the following may apply: a) the first NG-U common DL termination reference configured to be indicated by the one or more indications may be configured to be the selected NG-ll common DL termination reference of the one or more NG- II common DL termination references configured to be indicated by the network node 101, 102, b) the one or more NG-ll common DL termination references may be configured to correspond to the area serviced by the network node 101 , 102, c) the first information may be configured to comprise common DL Termination information, d) the network node 101 may be configured to be the first network node 101, and the first information may be configured to be sent indirectly, via the second network node 102, e) the first network node 101 may be configured to be the MB-SMF, the second network node 102 may be configured to be the AMF and the second radio network node 112 may be configured to be the second NG-RAN node, f) the network node 101 may be configured to be the first network node 101 and the first information may be configured to be received in the distribution setup request, g) the common DL termination information may be configured to comprise the one or more IP addresses of the common NG-RAN UP, alone or together with the TEID, and h) each IP address may be configured to correspond to the user plane entity of the radio network node comprised in the area.

In some embodiments, the one or more second indications may be configured to comprise the first second indication configured to request to release the current shared delivery procedure with the tunnel information configured to be currently used by the second radio network node 112.

In some embodiments, wherein the network node 101 may be configured to be the first network node 101, the network node 101 , 102 may be further configured to perform the storing of Action 705, e.g., by means of a storing unit 1202 within the network node 101 , 102, configured to store the received first information within the session context for the multicast MBS.

The network node 101, 102 may be configured to perform the sending of Action 703, e.g., by means of a sending unit 1203 within the network node 101, 102, configured to send, directly or indirectly, the first indication to the second radio network node 112. The first indication may be configured to indicate the one or more NG-U common DL termination references to be used during the multicast procedure. The first indication may be configured to comprise the received first information.

The network node 101, 102 may be configured to perform the exchanging of Action 705, e.g. by means of an exchanging unit 1204 within the network node 101 , 102, configured to exchange, in response to the one or more second indications configured to be received, the one or more third indications with the third network node 103 configured to operate in the communications network 100. The one or more third indications may be configured to indicate the modification to the session configured to be currently held by the second radio network node 112. The modification may be configured to be based on the one or more second indications configured to be received.

The network node 101, 102 may be configured to perform the sending of Action 706, e.g., by means of the sending unit 1202, configured to send, directly or indirectly, in response to the one or more third indications configured to be exchanged, the fourth indication to the second radio network node 112. The fourth indication may be configured to indicate the update to the shared delivery procedure.

In some embodiments, the network node 101 may be configured to be the first network node 101, the first information may be configured to be sent indirectly, via the second network node 102, the first network node 101 may be configured to be the MB-SMF, the second network node 102 may be configured to be the AMF, the second radio network node 112 may be configured to be the second NG-RAN node, the first information may be configured to comprise the common DL Termination information, and at least one of the following may apply: a) the first information may be further configured to comprise unicast DL tunnel information, and b) with the proviso the MB-SMF may determine the unicast DL tunnel in the first information exists already, the MB-SMF may be configured to refrain from configuring the third network node 103 configured to operate in the communications network 100. The third network node 103 may be configured to be the MB-UPF, and may be further configured to keep track on the number of NG-RAN nodes configured to be currently using the unicast DL tunnel and the common DL termination information.

In some embodiments, the network node 101 may be configured to be the first network node 101 , the first information may be configured to be sent indirectly, via the second network node 102, the first network node 101 may be configured to be the MB-SMF, the second network node 102 may be configured to be the AMF, the second radio network node 112 may be configured to be the second NG-RAN node, the first information may be configured to comprise the common DL Termination information, the one or more second indications may be configured to comprise the first second indication and, with the proviso the MB-SMF determines the context update configured to be indicated by the first second indication is for tunnel release, the MB-SMF may be configured to decrease the number of NG-RAN nodes configured to be using the common DL Termination configured to be indicated by the first second indication.

Other units 1205 may be comprised in the network node 101, 102.

The embodiments herein in the network node 101, 102 may be implemented through one or more processors, such as a processor 1206 in the network node 101, 102 depicted in Figure 12a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 101, 102. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 101, 102.

The network node 101, 102 may further comprise a memory 1207 comprising one or more memory units. The memory 1207 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the network node 101 , 102.

In some embodiments, the network node 101, 102 may receive information from, e.g., the first network node 101, the second network node 102, the third network node 103, the first radio network node 111, the second radio network node 112, the wireless device 130 and/or another node, through a receiving port 1208. In some embodiments, the receiving port 1208 may be, for example, connected to one or more antennas in network node 101 , 102. In other embodiments, the network node 101, 102 may receive information from another structure in the communications network 100 through the receiving port 1208. Since the receiving port 1208 may be in communication with the processor 1206, the receiving port 1208 may then send the received information to the processor 1206. The receiving port 1208 may also be configured to receive other information.

The processor 1206 in the network node 101 , 102 may be further configured to transmit or send information to e.g., the first network node 101, the second network node 102, the third network node 103, the first radio network node 111, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100, through a sending port 1209, which may be in communication with the processor 1206, and the memory 1207.

Those skilled in the art will also appreciate that the units 1201-1205 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1206, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1201-1205 described above may be implemented as one or more applications running on one or more processors such as the processor 1206.

Thus, the methods according to the embodiments described herein for the network node 101 , 102 may be respectively implemented by means of a computer program 1210 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1206, cause the at least one processor 1206 to carry out the actions described herein, as performed by the network node 101 , 102. The computer program 1210 product may be stored on a computer-readable storage medium 1211. The computer-readable storage medium 1211, having stored thereon the computer program 1210, may comprise instructions which, when executed on at least one processor 1206, cause the at least one processor 1206 to carry out the actions described herein, as performed by the network node 101, 102. In some embodiments, the computer-readable storage medium 1211 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1210 product may be stored on a carrier containing the computer program 1210 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1211 , as described above.

The network node 101, 102 may comprise a communication interface configured to facilitate communications between the network node 101 , 102 and other nodes or devices, e.g., the first network node 101, the second network node 102, the third network node 103, the first radio network node 111 , the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the network node 101 , 102 may comprise the following arrangement depicted in Figure 12b and Figure 12d. The network node 101 , 102 may comprise a processing circuitry 1206, e.g., one or more processors such as the processor 1206, in the network node 101 , 102 and the memory 1207. The network node 101 , 102 may also comprise a radio circuitry 1212, which may comprise e.g., the receiving port 1208 and the sending port 1209. The radio circuitry 1212 may be configured to set up and maintain at least a wireless connection with the first network node 101, the second network node 102, the third network node 103, the first radio network node 111, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the network node 101, 102 operative to operate in the communications network 100. The network node 101, 102 may comprise the processing circuitry 1206 and the memory 1207, said memory 1207 containing instructions executable by said processing circuitry 1206, whereby the network node 101, 102 is further operative to perform the actions described herein in relation to the network node 101, 102, e.g., in Figure 7, Figures 10-11 and/or Figures 26-30. Figure 13 depicts two different examples in panels a) and b), respectively, of the arrangement that the second radio network node 112 may comprise to perform the method described in Figure 8 and/or Figures 10-11. In some embodiments, the second radio network node 112 may comprise the following arrangement depicted in Figure 13a. The second radio network node 112 may be understood to be for handling common user plane. The second radio network node 112 is configured to operate in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

In Figure 13 optional units are indicated with dashed boxes.

The second radio network node 112 is configured to perform the sending of Action 803, e.g. by means of a sending unit 1301 within the second radio network node 112, configured to send, directly or indirectly the one or more second indications to the first network node 101 configured to operate in the communications network 100. The one or more second indications are configured to indicate the change to the shared delivery procedure from the unicast tunnel and the second NG- II common DL termination information, or the second NG- II common DL termination information, being configured to be currently used by the second radio network node 112, to the first NG- II common DL termination reference configured to be indicated to be used by the first radio network node 111 during the multicast procedure.

In some embodiments, at least one of the following may apply: a) the first NG-U common DL termination reference configured to be indicated by the one or more second indications may be configured to be the selected NG-U common DL termination reference of the one or more NG-U common DL termination references configured to be indicated by the network node 101 , 102, b) the one or more NG-U common DL termination references may be configured to correspond to the area serviced by the first network node 101 , c) the first network node 101 may be configured to be the MB-SMF, and the second radio network node 112 may be configured to be the second NG-RAN, node, d) the common DL termination information may be configured to comprise the one or more IP addresses of the common NG- RAN UP, alone or together with the TEID, e) each IP address may be configured to correspond to the user plane entity of the radio network node configured to be comprised in the area, and f) the one or more second indications may be configured to be sent indirectly to the first network node 101 via the second network node 102. In some embodiments, the one or more second indications may be configured to comprise the first second indication configured to request to release the current shared delivery procedure with the tunnel information configured to be currently used by the second radio network node 112.

In some embodiments, the second radio network node 112 may be configured to perform the receiving of Action 801, e.g., by means of a receiving unit 1302 within the second radio network node 112, configured to receive, directly or indirectly, the first indication from the first network node 101. The first indication may be configured to indicate the one or more NG- II common termination references to be used during the multicast procedure. The first indication may be configured to comprise the first information. The first information may be configured to indicate the first NG-ll common DL termination reference indicated to be used by the first radio network node 111 during the multicast procedure.

The second radio network node 112 may be configured to perform the selecting of Action 802, e.g., by means of a selecting unit 1303 within the second radio network node 112, configured to select the at least one of the one or more NG-ll common termination references to be used during the multicast procedure configured to be indicated in the received first indication.

The second radio network node 112 may be configured to perform the receiving of Action 804, e.g. by means of the receiving unit 1301 within the second radio network node 112, configured to receive, directly or indirectly, in response to the one or more second indications configured to be sent, the fourth indication from the network node 101 , 102. The fourth indication may be configured to indicate the update to the shared delivery procedure, e.g., an updated common NG-ll termination list.

Other units 1304 may be comprised in the second radio network node 112.

The embodiments herein in the second radio network node 112 may be implemented through one or more processors, such as a processor 1305 in the second radio network node 112 depicted in Figure 13a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second radio network node 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second radio network node 112.

The second radio network node 112 may further comprise a memory 1306 comprising one or more memory units. The memory 1306 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the second radio network node 112.

In some embodiments, the second radio network node 112 may receive information from, e.g., the network node 101, 102, the first network node 101 , the second network node 102, the third network node 103, the first radio network node 111, the wireless device 130 and/or another node, through a receiving port 1307. In some embodiments, the receiving port 1307 may be, for example, connected to one or more antennas in second radio network node 112. In other embodiments, the second radio network node 112 may receive information from another structure in the communications network 100 through the receiving port 1307. Since the receiving port 1307 may be in communication with the processor 1305, the receiving port 1307 may then send the received information to the processor 1305. The receiving port 1307 may also be configured to receive other information.

The processor 1305 in the second radio network node 112 may be further configured to transmit or send information to e.g., the network node 101, 102, the first network node 101 , the second network node 102, the third network node 103, the first radio network node 111 , the wireless device 130, another node, and/or another structure in the communications network 100, through a sending port 1308, which may be in communication with the processor 1305, and the memory 1306.

Those skilled in the art will also appreciate that the unit 1301-1304 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1305, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application- Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1301-1304 described above may be implemented as one or more applications running on one or more processors such as the processor 1305.

Thus, the methods according to the embodiments described herein for the second radio network node 112 may be respectively implemented by means of a computer program 1309 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1305, cause the at least one processor 1305 to carry out the actions described herein, as performed by the second radio network node 112. The computer program 1309 product may be stored on a computer-readable storage medium 1310. The computer- readable storage medium 1310, having stored thereon the computer program 1309, may comprise instructions which, when executed on at least one processor 1305, cause the at least one processor 1305 to carry out the actions described herein, as performed by the second radio network node 112. In some embodiments, the computer-readable storage medium 1310 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1309 product may be stored on a carrier containing the computer program 1309 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1310, as described above.

The second radio network node 112 may comprise a communication interface configured to facilitate communications between the second radio network node 112 and the network node 101 , 102, the first network node 101 , the second network node 102, the third network node 103, the first radio network node 111 , the wireless device 130, another node, and/or another structure in the communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the second radio network node 112 may comprise the following arrangement depicted in Figure 13b. The second radio network node 112 may comprise a processing circuitry 1305, e.g., one or more processors such as the processor 1305, in the second radio network node 112 and the memory 1306. The second radio network node 112 may also comprise a radio circuitry 1311 , which may comprise e.g., the receiving port 1307 and the sending port 1308. The processing circuitry 1305 may be configured to, or operable to, perform the method actions according to Figure 8, Figures 10-11 and/or Figures 26-30, in a similar manner as that described in relation to Figure 13a. The radio circuitry 1311 may be configured to set up and maintain at least a wireless connection with the network node 101, 102, the first network node 101, the second network node 102, the third network node 103, the first radio network node 111 , the wireless device 130, another node, and/or another structure in the communications network 100. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the second radio network node 112 operative to operate in the communications network 100. The second radio network node 112 may comprise the processing circuitry 1305 and the memory 1306, said memory 1306 containing instructions executable by said processing circuitry 1305, whereby the second radio network node 112 is further operative to perform the actions described herein in relation to the second radio network node 112, e.g., in Figure 8, Figures 10-11 and/or Figures 26-30.

Figure 14 depicts two different examples in panels a) and b), respectively, of the arrangement that the third network node 103 may comprise to perform the method described in Figure 9 and/or Figures 10-11. In some embodiments, the third network node 103 may comprise the following arrangement depicted in Figure 14a. The third network node 103 may be understood to be for handling common user plane. The third network node 103 is configured to operate in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

In Figure 14 optional units are indicated with dashed boxes.

The third network node 103 may be configured to perform the exchanging of Action 901, e.g., by means of an exchanging unit 1401 within the third network node 103, configured to exchange the one or more third indications with the first network node 101 configured to operate in the communications network 100. The one or more third indications are configured to indicate the modification to the session currently held by the second radio network node 112 configured to operate in the communications network 100. The modification is configured to comprise the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information, or the second NG-ll common DL termination information, configured to be currently used by the second radio network node 112, to the first NG-U DL termination reference configured to be used by the first radio network node 111 , to be used in the multicast procedure.

In some embodiments, at least one of the following may apply: a) the first network node 101 may be configured to be the MB-SMF and the second radio network node 112 may be configured to be the second NG-RAN node, b) the common DL termination information may be configured to comprise the one or more IP addresses of the common NG-RAN UP, alone or together with the TEID, and c) each IP address may be configured to correspond to the user plane entity of the radio network node configured to be comprised in the area.

Other units 1402 may be comprised in the third network node 103.

The embodiments herein in the third network node 103 may be implemented through one or more processors, such as a processor 1403 in the third network node 103 depicted in Figure 14a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the third network node 103. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the third network node 103.

The third network node 103 may further comprise a memory 1404 comprising one or more memory units. The memory 1404 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the third network node 103.

In some embodiments, the third network node 103 may receive information from, e.g., the network node 101, 102, the first network node 101 , the second network node 102, the first radio network node 111, the second radio network node 112, the wireless device 130 and/or another node, through a receiving port 1405. In some embodiments, the receiving port 1405 may be, for example, connected to one or more antennas in third network node 103. In other embodiments, the third network node 103 may receive information from another structure in the communications network 100 through the receiving port 1405. Since the receiving port 1405 may be in communication with the processor 1403, the receiving port 1405 may then send the received information to the processor 1403. The receiving port 1405 may also be configured to receive other information.

The processor 1403 in the third network node 103 may be further configured to transmit or send information to e.g., the network node 101 , 102, the first network node 101, the second network node 102, the first radio network node 111, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100, through a sending port 1406, which may be in communication with the processor 1403, and the memory 1404.

Those skilled in the art will also appreciate that the unit 1401-1402 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 1403, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application- Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 1401-1402 described above may be implemented as one or more applications running on one or more processors such as the processor 1403.

Thus, the methods according to the embodiments described herein for the third network node 103 may be respectively implemented by means of a computer program 1407 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 1403, cause the at least one processor 1403 to carry out the actions described herein, as performed by the third network node 103. The computer program 1407 product may be stored on a computer-readable storage medium 1408. The computer-readable storage medium 1408, having stored thereon the computer program 1407, may comprise instructions which, when executed on at least one processor 1403, cause the at least one processor 1403 to carry out the actions described herein, as performed by the third network node 103. In some embodiments, the computer-readable storage medium 1408 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1407 product may be stored on a carrier containing the computer program 1407 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1408, as described above.

The third network node 103 may comprise a communication interface configured to facilitate communications between the third network node 103 and the network node 101, 102, the first network node 101, the second network node 102, the first radio network node 111, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the third network node 103 may comprise the following arrangement depicted in Figure 14b. The third network node 103 may comprise a processing circuitry 1403, e.g., one or more processors such as the processor 1403, in the third network node 103 and the memory 1404. The third network node 103 may also comprise a radio circuitry 1409, which may comprise e.g., the receiving port 1405 and the sending port 1406. The processing circuitry 1403 may be configured to, or operable to, perform the method actions according to Figure 9, Figures 10-11 and/or Figures 26-30, in a similar manner as that described in relation to Figure 14a. The radio circuitry 1409 may be configured to set up and maintain at least a wireless connection with the network node 101, 102, the first network node 101 , the second network node 102, the first radio network node 111 , the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the third network node 103 operative to operate in the communications network 100. The third network node 103 may comprise the processing circuitry 1403 and the memory 1404, said memory 1404 containing instructions executable by said processing circuitry 1403, whereby the third network node 103 is further operative to perform the actions described herein in relation to the third network node 103, e.g., in Figure 9, Figures 10-11 and/or Figures 26-30. As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

When using the word "comprise" or “comprising” it shall be interpreted as non- limiting, i.e. meaning "consist at least of".

A processor may be understood herein as a hardware component.

The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the invention.

Examples related to embodiments herein

According to a first aspect of examples related to embodiments herein, the object is achieved by a first method, performed by a network node. The first method is for handling common user plane, network node operates in a communications network. The network node sends, directly or indirectly, a first indication to a first radio network node. The first radio network node operates in the communications network. The first indication indicates one or more Next Generation (NG)-User Plane (II) common Downlink (DL) termination references to be used during a broadcast procedure. Each of the NG-ll common termination references is an Internet Protocol (IP) address.

According to a second aspect of examples related to embodiments herein, the object is achieved by a first method, performed by a first radio network node. The first method is for handling common user plane. The first radio network node operates in the communications network. The first radio network node receives, directly or indirectly, the first indication from the first network node operating in the communications network. The first indication indicates one or more NG-ll DL common termination references to be used during a broadcast procedure. Each of the NG-ll common termination references is an IP address.

According to a third aspect of examples related to embodiments herein, the object is achieved by a second method performed by the network node. The second method is for handling common user plane. The network node operates in the communications network. The network node receives, directly or indirectly, first information from the first radio network node operating in the communications network. The first information indicates a first NG-ll common DL termination reference to be used by the first radio network node during a multicast procedure. The network node sends, directly or indirectly, a first indication to a second radio network node operating in the communications network. The first indication indicates one or more NG-ll common DL termination references to be used during the multicast procedure. The first indication comprises the received first information. The network node also receives, directly or indirectly, in response to the sent first indication, one or more second indications from the second radio network node. The one or more second indications indicate a change to a shared delivery procedure from a unicast tunnel and a second NG-ll common DL termination information or the second NG-ll common DL termination information currently used by the second radio network node, to a selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., to the first NG-U DL termination reference.

According to a fourth aspect of examples related to embodiments herein, the object is achieved by a method performed by the second radio network node. The method is for handling common user plane. The second radio network node operates in the communications network. The second radio network node receives, directly or indirectly, the first indication from the first network node operating in the communications network. The first indication indicates the one or more NG-U common, DL .termination references to be used during the multicast procedure. The first indication comprises the received first information. The second radio network node sends, directly or indirectly, in response to the received first indication, the one or more second indications to the first network node. The one or more second indications indicate a change to a shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information or the second NG-U common DL termination information currently used by the second radio network node, to the selected NG- U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., to a first NG-U DL termination reference indicated by the first indication.

According to a fifth aspect of examples related to embodiments herein, the object is achieved by a method performed by a third network node. The method is for handling common user plane. The third network node operates in the communications network. The third network node exchanges one or more third indications with the first network node operating in the communications network. The one or more third indications indicate a modification to a session currently held by the second radio network node operating in the communications network. The modification comprises the change to the shared delivery procedure from the unicast tunnel and the second NG-U common DL termination information or the second NG-U common DL termination information currently used by the second radio network node, to a selected NG-U common DL termination reference, e.g., to the first NG-U DL termination reference used by a first radio network node 111 , to be used in a multicast procedure. According to a sixth aspect of examples related to embodiments herein, the object is achieved by the network node, configured to perform the first method.

According to a seventh aspect of examples related to embodiments herein, the object is achieved by the first radio network node, configured to perform the first method.

According to an eighth aspect of examples related to embodiments herein, the object is achieved by the network node, configured to perform the second method.

According to a ninth aspect of examples related to embodiments herein, the object is achieved by the second radio network node, configured to perform the method.

According to a tenth aspect of examples related to embodiments herein, the object is achieved by the third network node, configured to perform the method.

The network node embodiments relate to Figure 15, Figure 20, Figure 21 , panels a) and b), and Figures 26-30.

A first method, performed by a network node, such as the network node 101 , 102, is described herein. The first method may be understood to be for handling common user plane. The network node 101 , 102 may operate in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the first method performed by the network node 101 , 102 is depicted in Figure 15. A further particular example is depicted in Figure 20, where Step 2 corresponds to Action 1501.

In some embodiments, the network node 101 , 102 may be the first network node 101 , e.g., an MB-SMF. In some embodiments, the network node 101, 102 may be the second network node 102, e.g., an AMF. o Sending 1501 a first indication.

The sending may be, directly or indirectly to the first radio network node 111 operating in the communications network 100.

The sending may be performed, e.g., via the first link 141 and/or the second link 142.

The first indication may indicate one or more Next Generation (NG)-User Plane (II) common Downlink (DL) termination references. The one or more NG-ll common DL termination references may be to be used during a broadcast procedure. Each of the NG-ll common termination references may be an Internet Protocol (IP) address.

Any references to the first indication in regards to any of Figure 15 and Figure 17 may be understood to refer to the first indication sent in this Action 1501.

In some examples, at least one of the following may apply: - the one or more NG-ll common DL termination references may correspond to an area serviced by the network node 101, 102,

- each IP address may correspond to a user plane entity, e.g., a different user plane entity, e.g., of radio network node comprised in the area; the user plane entity may be servicing the area,

- the network node 101 may be a first network node 101 and the first indication may be sent indirectly, via the second network node 102,

- the first network node 101 may be a Multicast Broadcast (MB)-Session Management Function (SMF), the second network node 102 may be an Access and Mobility Management Function (AMF), and the first radio network node 111 may be a first NG-Radio Access Network (RAN) node,

- the first indication may comprise an Internet Protocol address of a user plane of an NG-RAN operating in the communications network 100,

- the first indication may indicate a plurality of NG-ll common DL termination references, and

- the plurality may be indicated as a list.

In some examples, at least one of the following may apply:

- the network node 101 may be the first network node 101 , and the first indication may be sent in a Broadcast Session Setup Request or a Broadcast Session Modify Request,

- the network node 101 may be the first network node 101 , and the first indication may be sent in a broadcast context create request towards the second network node 102, and

- the network node 101 may be the second network node 102, and the first indication may be sent in a Broadcast Session Setup Request or a Broadcast Session Modify Request.

The network node 101, 102 may comprise an arrangement as shown in Figure 21, panel a) or b), to enable performance of the first method, as shown in Figure 15, or as shown in Figure 26.

A second method, performed by a network node, such as the network node 101 , 102, is also described herein. The second method may be understood to be for handling common user plane. The network node 101 , 102 may operate in the communications network 100.

A non-limiting example of the second method performed by the network node 101, 102 is depicted in Figure 16.

Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. Some actions may be performed in a different order than that shown in Figure 16. A further particular example is depicted in Figures 10-11. In Figure 10, Step 3a corresponds to Action 1601, step 5 corresponds to Action 1602, Step 9 corresponds to Action 1603, Step 14 corresponds to Action 1604, Step 15 corresponds to Action 1605 and Step 16 corresponds to Action 1606. o Receiving 1601 first information.

The first information may be received, directly or indirectly, from the first radio network node 111 operating in the communications network 100, via the first link 141 and/or the second link 142.

The first information may indicate a first NG-ll common DL termination reference to be used by the first radio network node 111 during a multicast procedure. o Sending 1603 a first indication.

The first indication may be sent, directly or indirectly, to the second radio network node 112 operating in the communications network 100.

The first indication may indicate one or more NG-ll common DL termination references to be used during the multicast procedure.

Any references to the first indication in regards to any of Figure 16 and Figure 18, may be understood to refer to the first indication sent in this Action 1603.

The first indication may comprise the received first information, o Receiving 1604 one or more second indications.

The receiving of the one or more second indications may be, directly or indirectly, from the second radio network node 112, e.g., via the first link 141 and/or the third link 143.

The receiving of the one or more second indications may be in response to the sent first indication.

The one or more second indications may indicate a change to a shared delivery procedure from a unicast tunnel and a second NG-ll common DL termination information, or the second NG-U common DL termination information, currently used by the second radio network node 112, to a selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., to the first NG-U DL termination reference.

In some examples, at least one of the following may apply:

- the one or more NG-U common DL termination references may correspond to an area serviced by the network node 101, 102,

- the first indication may comprise common DL Termination information, - the network node 101 may be the first network node 101 and the first indication may be sent indirectly, via the second network node 102,

- the first network node 101 may be an MB-SMF, the second network node 102 may be an AMF, and the second radio network node 112 may be a second NG- RAN node,

- the network node 101 may be the first network node 101 , and the first indication may be sent in a distribution setup response,

- the first indication may indicate a plurality of NG-ll common DL termination references, and

- the common DL termination information may comprise one or more IP addresses of the common NG-RAN UP, alone or together with a Tunnel Endpoint Identifier (TEID),

- each IP address may correspond to a, e.g., different, user plane entity, e.g., of a radio network node comprised in the area; The user plane entity may be servicing the area, and

- the plurality may be indicated as a list.

In some examples, e.g., according to a first option, the one or more second indications may comprise one of:

- a first second indication requesting to release a current shared delivery procedure with the tunnel information currently used by the second radio network node 112, and a second second indication indicating to establish a new shared delivery procedure with the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., the first NG-U DL termination reference indicated by the first indication sent by the network node 101 , 102, and

- a third second indication indicating to modify the current shared delivery procedure by indicating the tunnel information currently used by the second radio network node 112 to be released and the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references to be established, e.g., the first NG-U DL termination reference to be established.

In some examples, the network node 101 may be the first network node 101 , and the second method may further comprise at least one of the following actions: o Storing 1602 the received first information.

The storing of the received first information may be within a session context for a multicast MBS. The sent first indication may comprise the stored first information. o Exchanging 1605 one or more third indications. Exchanging may be understood as sending and/or receiving.

The exchanging in this Action 1605 may be with the third network node 103 operating in the communications network 100.

The exchanging may be performed, e.g., via the fourth link 144.

The exchanging in this Action 1605 may be in response to the received one or more second indications.

The one or more third indications may indicate a modification to a session currently held by the second radio network node 112. The modification may be based on the received one or more second indications.

In some examples, the second method may further comprise: o Sending 1606 a fourth indication.

The sending in this Action 1606 of the fourth indication may be, directly or indirectly, to the second radio network node 112, e.g., via the first link 141 and/or the third link 143.

The sending in this Action 1606 may be in response to the exchanged one or more third indications.

The fourth indication indicating an update to the shared delivery procedure, e.g., an updated common NG-ll termination list.

In some examples, at least one of the following may apply:

- at least one of the first indication and the one or more second indications may be received indirectly from the first radio network node 111 via the second network node 102 operating in the communications network 100,

- the first indication may be sent indirectly to the second radio network node 112 via the second network node 102 operating in the communications network 100, and

- the fourth indication may be sent indirectly to the second radio network node

112 via the second network node 102 operating in the communications network 100.

The first radio network node embodiments relate to Figure 17, Figure 20, Figure 22 and Figures 26-30.

A first method, performed by a first radio network node, such as the first radio network node 111 , is described herein. The first method may be understood to be for handling common user plane. The first radio network node 111 may operate in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the method performed by the first radio network node 111 is depicted in Figure 17. A further particular example is depicted in Figure 20, where Step 2 corresponds to Action 1701.

In some embodiments, the first radio network node 111 may be a first NG-RAN node. o Receiving 1701 the first indication.

The first indication may be received, directly or indirectly, from the first network node 101 operating in the communications network 100, e.g., via the first link 141 and/or the second link 142.

The first indication may indicate one or more NG-ll DL common termination references to be used during a broadcast procedure.

Each of the NG-ll common termination references may be an IP address.

In some examples, at least one of the following may apply:

- the one or more NG-ll common DL termination references may correspond to an area serviced by the first network node 101 ,

- each IP address may correspond to a, e.g., different, user plane entity, e.g., of a radio network node comprised in the area; The user plane entity may be servicing the area,

- the first indication may comprise common DL Termination information,

- the first indication may be received indirectly, via the second network node 102,

- the first network node 101 may be an MB-SMF, the second network node 102 may be an AMF and the first radio network node 111 may be a first NG-RAN, node,

- the first indication may indicate a plurality of NG-U common DL termination references, and

- the plurality may be indicated as a list.

In some examples, at least one of the following may apply:

- the first indication may be received in a Broadcast Session Setup Request or a Broadcast Session Modify Request,

- the first indication may be received in a broadcast context create request via a second network node 102, and

- the first indication may be received in a Broadcast Session Setup Request or a Broadcast Session Modify Request.

The second radio network node embodiments relate to Figure 18, Figures 10-11, Figure 23 and Figures 26-30. A method, performed by a second radio network node, such as the second radio network node 112, is described herein. The method may be understood to be for handling common user plane. The second radio network node 112 may operate in the communications network 100.

Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. Some actions may be performed in a different order than that shown in Figure 18. A further particular example is depicted in Figures 10-11. In Figure 10, Step 14 corresponds to Action 1801 and 1803 and Step 16 corresponds to Action 1804. o Receiving 1801 the first indication.

The first indication may be received, directly or indirectly, from the first network node 101 operating in the communications network 100, e.g., via the first link 141 and/or the second link 142.

The first indication may indicate one or more NG-ll DL common termination references to be used during a multicast procedure.

The first indication may comprise the received first information. o Sending 1803 the one or more second indications

The one or more second indications may be sent, directly or indirectly, to the first network node 101 , e.g., via the first link 141 and/or the second link 142.

The sending of the one or more second indications may be in response to the received first indication.

The one or more second indications may indicate a change. The change may be to a shared delivery procedure. The change to the shared delivery procedure may be from a unicast tunnel and a second NG-ll common DL termination information, or the second NG-ll common DL termination information, currently used by the second radio network node 112, to a selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., to a first NG-U DL termination reference indicated by the first indication.

In some examples, at least one of the following may apply:

- the one or more NG-U common DL termination references may correspond to an area serviced by the first network node 101 ,

- the first indication may comprise common DL Termination information, - the first indication may be received indirectly, via the second network node 102,

- the first network node 101 may a MB-SMF, the second network node 102 may an AMF, and the second radio network node 112 may a second NG-RAN node,

- the first indication may be received in a distribution setup response,

- the first indication may indicate a plurality of NG-ll common DL termination references,

- the common DL termination information may comprise one or more IP addresses of the common NG-RAN UP, alone or together with a (TEID),

- each IP address may correspond to a, e.g., different, user plane entity, e.g., of radio network node comprised in the area; The user plane entity may be servicing the area,

- the plurality may be indicated as a list, and

- the first indication may be received indirectly from the first network node 101 via the second network node 102 operating in the communications network 100, and

- the second indication may be sent indirectly to the first network node 101 via the second network node 102.

In some examples, the one or more second indications may comprise one of:

- the first second indication requesting to release the current shared delivery procedure with the tunnel information currently used by the second radio network node 112, and the second second indication indicating to establish the new shared delivery procedure with the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., the first NG-U DL termination reference indicated by the first indication sent by the first network node 101 , and

- the third second indication indicating to modify the current shared delivery procedure by indicating the tunnel information currently used by the second radio network node 112 to be released and the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references to be established, e.g., the first NG-U DL termination reference to be established.

In some examples, the method may comprise at least one of the following actions: o Selecting 1802 at least one of the one or more NG-U common termination references.

The selecting of the at least one of the one or more NG-U common termination references may be to be used during the multicast procedure indicated in the received first indication. o Receiving 1804 the fourth indication.

The receiving of the fourth indication may be, directly or indirectly, from the network node 101, 102, e.g., via the first link 141 and/or the third link 143.

The receiving of the fourth indication may be in response to the sent one or more second indications.

The fourth indication may indicate the update to the shared delivery procedure, e.g., the updated common NG-ll termination list.

The third network node embodiments relate to Figure 19, Figures 10-11 , Figure 24 and Figures 26-30.

A method, performed by a third network node, such as the third network node 103, is described herein. The method may be understood to be for handling common user plane. The third network node 103 may operate in the communications network 100.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the method performed by the third network node 103 is depicted in Figure 19. A further particular example is depicted in Figures 10-11. In Figure 10, Step 15 corresponds to Action 1901.

In some embodiments, the third network node 103 may be an MB-LIPF. o Exchanging 1901 the one or more third indications.

Exchanging may be understood as sending and/or receiving.

The exchanging in this Action 1901 may be with the first network node 101 operating in the communications network 100.

The exchanging may be performed, e.g., via the fourth link 144.

The one or more third indications may indicate the modification to the session currently held by the second radio network node 112 operating in the communications network 100. The modification may comprise the change to the shared delivery procedure from the unicast tunnel and the second NG-ll common DL termination information or the second NG-ll common DL termination information currently used by the second radio network node 112 to the selected NG-ll common DL termination reference, e.g., to the first NG-U DL termination reference used by the first radio network node 111 , to be used in a multicast procedure.

In some examples, at least one of the following may apply:

- the first network node 101 may be an MB-SMF and the second radio network node 112 may be a second NG-RAN node, - the common DL termination information may comprise the IP address of the common NG-RAN UP, alone or together with the TEID, and

- each IP address may correspond to a, e.g., different, user plane entity, e.g., of a radio network node comprised in the area; The user plane entity may be servicing the area.

Selected examples related to embodiments herein:

Example 1. A first method performed by a network node (101 , 102), the first method being for handling common user plane, the network node (101, 102) operating in a communications network (100), and the first method comprising:

- sending (701), directly or indirectly, a first indication to a first radio network node (111) operating in the communications network (100), the first indication indicating one or more Next Generation, NG, -User Plane, U, common Downlink, DL, termination references to be used during a broadcast procedure, wherein each of the NG-U common termination references is an Internet Protocol address.

Example 2. The first method according to example 1, wherein at least one of:

- the one or more NG-U common DL termination references correspond to an area serviced by the network node (101 , 102),

- each IP address corresponds to a user plane entity of a radio network node comprised in the area,

- the network node (101) is a first network node (101) and the first indication is sent indirectly, via a second network node (102),

- the first network node (101) is a Multicast Broadcast, MB, -Session Management Function, SMF, the second network node (102) is an Access and Mobility Management Function, AMF, and the first radio network node (111) is a first NG-Radio Access Network, RAN, node,

- the first indication comprises an Internet Protocol, IP, address of a user plane of an NG-RAN, operating in the communications network (100),

- the first indication indicates a plurality of NG-U common DL termination references, and

- the plurality is indicated as a list.

Example 3. The first method according to any of examples 1-2, wherein at least one of: - the network node (101) is a first network node (101), and the first indication is sent in a Broadcast Session Setup Request or a Broadcast Session Modify Request,

- the network node (101) is a first network node (101), and the first indication is sent in a broadcast context create request towards a second network node (102), and

- the network node (101) is a second network node (102), and the first indication is sent in a Broadcast Session Setup Request or a Broadcast Session Modify Request.

Example 4. A first method performed by a first radio network node (111), the first method being for handling common user plane, the first radio network node (111) operating in a communications network (100), and the first method comprising:

- receiving (801), directly or indirectly, a first indication from a first network node (101) operating in the communications network (100), the first indication indicating one or more Next Generation, NG, -User Plane, U, Downlink, DL, common termination references to be used during a broadcast procedure, wherein each of the NG-U common termination references is an Internet Protocol address.

Example 5. The first method according to example 4, wherein at least one of:

- the one or more NG-U common DL termination references correspond to an area serviced by the first network node (101),

- each IP address corresponds to a user plane entity of a radio network node comprised in the area,

- the first indication comprises common Downlink, DL, Termination information,

- the first indication is received indirectly, via a second network node (102),

- the first network node (101) is a Multicast Broadcast, MB, -Session Management Function, SMF, the second network node (102) is an Access and Mobility Management Function, AMF, and the first radio network node (111) is a first NG-Radio Access Network, RAN, node,

- the first indication indicates a plurality of NG-U common DL termination references, and

- the plurality is indicated as a list.

Example 6. The first method according to any of examples 1-5, wherein at least one of: - the first indication is received in a Broadcast Session Setup Request or a Broadcast Session Modify Request,

- the first indication is received in a broadcast context create request via a second network node (102), and

- the first indication is received in a Broadcast Session Setup Request or a Broadcast Session Modify Request.

Example 7. A second method performed by a network node (101 , 102), the second method being for handling common user plane, the network node (101, 102) operating in a communications network (100), and the second method comprising:

- receiving (901), directly or indirectly, first information from a first radio network node (111) operating in the communications network (100), the first information indicating a first Next Generation, NG, -User Plane, U, common Downlink, DL, termination reference to be used by the first radio network node (111) during a multicast procedure,

- sending (903), directly or indirectly, a first indication to a second radio network node (112) operating in the communications network (100), the first indication indicating one or more Next Generation, NG,-U common Downlink, DL, termination references to be used during the multicast procedure, the first indication comprising the received first information, and

- receiving (904), directly or indirectly, in response to the sent first indication, one or more second indications from the second radio network node (112), the one or more second indications indicating a change to a shared delivery procedure from a unicast tunnel and a second NG-U common DL termination information or the second NG-U common DL termination information currently used by the second radio network node (112) to a selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., to the first NG-U DL termination reference.

Example 8. The second method according to example 7, wherein at least one of:

- the one or more NG-U common DL termination references correspond to an area serviced by the network node (101 , 102),

- the first indication comprises common Downlink, DL, Termination information,

- the network node (101) is a first network node (101), and the first indication is sent indirectly, via a second network node (102),

- the first network node (101) is a Multicast Broadcast, MB, -Session Management Function, SMF, the second network node (102) is an Access and Mobility Management Function, AMF, and the second radio network node (112) is a second NG-Radio Access Network, RAN, node,

- the network node (101) is a first network node (101) and the first indication is sent in a distribution setup response,

- the first indication indicates a plurality of NG-ll common DL termination references,

- the common DL termination information comprises one or more Internet Protocol, IP, addresses of the common NG-RAN UP, alone or together with a Tunnel Endpoint Identifier, TEID,

- each IP address corresponds to a user plane entity of a radio network node comprised in the area, and

- the plurality is indicated as a list.

Example 9. The second method according to any of examples 7-8, wherein the one or more second indications comprise one of:

- a first second indication requesting to release a current shared delivery procedure with the tunnel information currently used by the second radio network node (112), and a second second indication indicating to establish a new shared delivery procedure with the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., the first NG-U DL termination reference indicated by the first indication sent by the network node (101 , 102), and

- a third second indication indicating to modify the current shared delivery procedure by indicating the tunnel information currently used by the second radio network node (112) to be released and the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references to be established, e.g., the first NG-U DL termination reference to be established.

Example 10. The second method according to any of examples 7-9, wherein the network node (101) is a first network node (101), and wherein the second method further comprises at least one of:

- storing (902) the received first information within a session context for a Multicast Broadcast Service, MBS, and wherein the sent first indication comprises the stored first information, and

- exchanging (905), in response to the received one or more second indications, one or more third indications with a third network node (103) operating in the communications network (100), the one or more third indications indicating a modification to a session currently held by the second radio network node (112), the modification being based on the received one or more second indications.

Example 11. The second method according to example 10, wherein the second method further comprises:

- sending (906), directly or indirectly, in response to the exchanged one or more third indications, a fourth indication to the second radio network node (112), the fourth indication indicating an update to the shared delivery procedure, e.g., an updated common NG-ll termination list.

Example 12. The second method according to examples 10 and 11, wherein at least one of:

- at least one of the first indication and the one or more second indications is received indirectly from the first radio network node (111) via a second network node (102) operating in the communications network (100),

- the first indication is sent indirectly to the second radio network node (112) via the second network node (102) operating in the communications network (100), and

- the fourth indication is sent indirectly to the second radio network node (112) via the second network node (102) operating in the communications network (100).

Example 13. A method performed by a second radio network node (112), the method being for handling common user plane, the second radio network node (112) operating in a communications network (100), and the method comprising:

- receiving (1901), directly or indirectly, a first indication from a first network node (101) operating in the communications network (100), the first indication indicating one or more Next Generation, NG, -User Plane, U, common termination references to be used during a multicast procedure, the first indication comprising the received first information, and

- sending (1903), directly or indirectly, in response to the received first indication, one or more second indications to the first network node (101), the one or more second indications indicating a change to a shared delivery procedure from a unicast tunnel and a second NG-U common DL termination information or the second NG-U common DL termination information currently used by the second radio network node (112) to a selected NG-U common DL termination reference of the indicated one or more NG-ll common DL termination references, e.g., to a first NG-ll DL termination reference indicated by the first indication.

Example 14. The method according to example 13, wherein at least one of:

- the one or more NG-ll common DL termination references correspond to an area serviced by the first network node (101),

- the first indication comprises common Downlink, DL, Termination information,

- the first indication is received indirectly, via a second network node (102),

- the first network node (101) is a Multicast Broadcast, MB, -Session Management Function, SMF, the second network node (102) is an Access and Mobility Management Function, AMF, and the second radio network node (112) is a second NG-Radio Access Network, RAN, node,

- the first indication is received in a distribution setup response, and

- the first indication indicates a plurality of NG-U common DL termination references,

- the common DL termination information comprises one or more Internet Protocol, IP, addresses of the common NG-RAN UP, alone or together with a Tunnel Endpoint Identifier, TEID,

- each IP address corresponds to a user plane entity of a radio network node comprised in the area,

- the plurality is indicated as a list, and

- the first indication is received indirectly from the first network node (101) via the second network node (102) operating in the communications network (100), and

- the second indication is sent indirectly to the first network node (101) via the second network node (102).

Example 15. The method according to example 14, wherein the one or more second indications comprise one of:

- a first second indication requesting to release a current shared delivery procedure with the tunnel information currently used by the second radio network node (112), and a second second indication indicating to establish a new shared delivery procedure with the selected NG-U common DL termination reference of the indicated one or more NG-U common DL termination references, e.g., the first NG-U DL termination reference indicated by the first indication sent by the first network node (101), and - a third second indication indicating to modify the current shared delivery procedure by indicating the tunnel information currently used by the second radio network node (112) to be released and the selected NG-ll common DL termination reference of the indicated one or more NG-ll common DL termination references to be established, e.g., the first NG-ll DL termination reference to be established.

Example 16. The method according to any of examples 13-15, further comprising at least one of:

- selecting (1902) at least one of the one or more NG-U common termination references to be used during a multicast procedure indicated in the received first indication, and

- receiving (1904), directly or indirectly, in response to the sent one or more second indications, a fourth indication from the network node (101 , 102), the fourth indication indicating an update to the shared delivery procedure, e.g., an updated common NG-U termination list.

Example 17. A method performed by a third network node (103), the method being for handling common user plane, the third network node (103) operating in a communications network (100), and the method comprising:

- exchanging (2001) one or more third indications with a first network node (101) operating in the communications network (100), the one or more third indications indicating a modification to a session currently held by a second radio network node (112) operating in the communications network (100), the modification comprising a change to a shared delivery procedure from a unicast tunnel and a second NG-User Plane, U, common DL termination information or the second NG-U common DL termination information currently used by the second radio network node (112) to a selected NG-U common DL termination reference, e.g., to a first NG-U DL termination reference used by a first radio network node (111), to be used in a multicast procedure.

Example 18. The second method according to example 17, wherein at least one of:

- the first network node (101) is a Multicast Broadcast, MB, -Session Management Function, SMF, and the second radio network node (112) is a second NG-Radio Access Network, RAN, node, - the common DL termination information comprises an Internet Protocol, IP, address of the common NG-RAN UP, alone or together with a Tunnel Endpoint Identifier, TEID, and

- each IP address corresponds to a user plane entity of a radio network node comprised in the area.

Example 19. A network node (101 , 102), for handling common user plane, the network node (101 , 102) being configured to operate in a communications network (100), and the network node (101 , 102) being further configured to perform a first method according to any of examples 1-3.

Example 20. A first radio network node (111), for handling common user plane, the first radio network node (111) being configured to operate in a communications network (100), the first radio network node (111) being configured to perform the first method according to any of examples 4-6.

Example 21. A network node (101, 102), for handling common user plane, the network node (101 , 102) being configured to operate in a communications network (100), the network node (101 , 102) being further configured to perform the second method according to any of examples 7-12.

Example 22. A second radio network node (112), for handling common user plane, the second radio network node (112) being configured to operate in a communications network (100 the second radio network node (112) being further configured to perform the method according to any of examples 13-16.

Example 23. A third network node (103), for handling common user plane, the third network node (103) being configured to operate in a communications network (100), the third network node (103) being further configured to perform the method according to any of examples 17- 18.

Some examples related to embodiments herein will now be further described with some non-limiting examples.

In the following description, any reference to a/the “NG-RAN1” and/or “NG-RAN” and/or “NG-RAN node” in the context of Figure 20, may be understood to equally refer to any of the first radio network node 111; any reference to a/the “MB-SMF” may be understood to equally refer to the first network node 101 ; any reference to a/the “AMF” may be understood to equally refer to the second network node 102; any reference to a/the “MB-LIPF” may be understood to equally refer to the third network node 103; any reference to a/the UE may be understood to equally refer the wireless device 130.

According to examples related to embodiments herein, the approach of network requested broadcast MBS Session may entail updates to clause 7.3.1 in TS 23.247, v. 17.2.0, as follows.

Jpdate to clause 7.3.1 MBS Session Start for Broadcast of TS 23.247 v17.2.0 ======== below shows the changes to clause 7.3.1 ========= 7.3.1 MBS Session Start for Broadcast

The Broadcast Session Start may follow the common procedure specified in clause 7.1.1.2 or clause 7.1.1.3, which consist of TMGI Allocation and MBS Session Create. It is possible for AF to allocate TMGI once but create the MBS Session for multiple times. A combined procedure to perform both TMGI allocation and MBS Session Create may be available.

The TMGI Allocation may be used by AF to obtain the TMGI as MBS Session ID, e.g., TMGI, and perform service announcement towards UEs.

The MBS Session Create, with MBS service type set to broadcast service, may be used by the AF to indicate the impending start of the transmission of MBS data, and to provide the session attributes, so that resources for the MBS Session may be set up in the MB-LIPF and in the NG-RAN for 5GC Shared MBS traffic delivery. The MBS Session Create may be used if TMGI has not been allocated. In this case, MB-SMF may allocate a unique TMGI for the AF and then start the MBS Session.

NOTE 1 : When the multicast transport between NG-RAN and MB-LIPF is described below, source specific multicasting may be assumed.

To receive the data of broadcast communication service, the UE may be either preconfigured with needed configuration, e.g., USD as defined in TS 26.346 [13], for the UE to receive MBS service, or provisioned with the configuration of broadcast session on application level, e.g., service announcement; the configuration may for instance be performed using SIP signalling, or methods described in TS 26.346 [13], If the needed configuration is pre-configured, the UE may be understood to not need to interact with network.

Figure 20 is a schematic representation depicting a further non-limiting example of a first method in a communications network, according to examples related to embodiments herein. Figure 20 is based on Figure 7.3.1-1 : MBS Session Establishment for Broadcast.

0 Based on GAM configuration, RAN nodes may announce in SIBs over the radio interface information about the MBS FSA IDs and frequencies of neighbouring cells. To establish broadcast MBS session, the AF may perform TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or 7.1.1.3. The MBS service type may indicate to be broadcast service. The MBS FSA ID(s) of a broadcast MBS session may be communicated in the service announcement towards the UE. The UE may compare those MBS FSA IDs(s) with the MBS FSA ID(s) in SIBs for frequency selection. The MB-SMF may use NRF to discover the AMF(s) supporting MBS based on the MBS service area and select the appropriate one(s). Then the MB-SMF may send, in accordance with Action 1501 and Action 1701 , the Namf_MBSBroadcast_ContextCreate (TMGI, N2 SM information ([LL SSM], 5G QoS Profile, [List of IP addresses of the NG- RAN IIP]), MBS service area, [MBS FSA ID(s)]) messages to the selected AMF(s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request. If configured, the MB-SMF includes list of IP addresses of the NG-RAN UP to enable use of common user plane entity. The AMF may transfer the MBS Session Resource Setup Request message, which may contain the N2 SM information in the received Namf_MBSBroadcast_ContextCreate Request to all NG-RANs which may support MBS in the MBS service area. The AMF may include the MBS service area. NG-RAN may create a Broadcast MBS Session Context and store the TMGI and the QoS Profile in the MBS Session Context. The LL SSM may be understood to be optional parameters and only provided by MB-SMF to NG-RAN if N3mb multicast transport is configured to be used in the 5GC. If MBS FSA ID(s) were received, the NG-RAN may use those MBS FSA ID(s)s to determine cells/frequencies within the MBS service area to broadcast MBS session data based on QAM configuration about the MBS FSA IDs and related frequencies.

If NG-RAN supports shared NG-U termination in a common user plane entity, the NG- RAN may use the IP address of the NG-RAN UP to select a common user plane entity, if feasible. If NG-RAN prefers to use N3mb multicast transport, and if LL SSM is available in NG- RAN, the NG-RAN may join the multicast group, that is, the LL SSM.

If NG-RAN prefers to use N3mb point-to-point transport, or if the LL SSM is not available in NG-RAN, between the NG-RAN and MB-UPF, NG-RAN may provide its N3mb DL Tunnel Info. The NG-RAN may report successful establishment of the MBS Session resources, which may include multiple MBS QoS Flows, by sending MBS Session Resource Setup Response, TMGI, N2 SM information ([N3mb DL Tunnel Info]), message(s) to the AMF. N3mb DL Tunnel Info may only be available when point-to-point transport may apply between MB-UPF and NG-RAN. For more details, refer to TS 38.413 [15], 7. The AMF may transfer the Namf_MBSBroadcast_ContextCreate Response () to the MB- SMF. The AMF may need to respond success when it may receive the first success response from the NG-RAN(s). And if all NG-RAN(s) report failure, the AMF may need to respond failure. The MB-SMF may store the AMF(s) which may respond success in the MBS Session Context as the downstream nodes. If the AMF receives the NG-RAN response(s) from all involved NG-RAN(s), the AMF may need to include an indication of completion of the operation in all NG-RANs.

8. If N3mb point-to-point transport is to be used, that is, N3mb DL Tunnel Info is present in the Namf_MBSBroadcast_ContextCreate Response message from AMF, the MB-SMF may send an N4mb Session Modification Request to the MB-LIPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 8 may be skipped.

9. NG-RAN may broadcast the TMGI representing the MBS service over radio interface. Step 9 may take place in parallel with step 6.

10. Another NG-RAN may report successful establishment of the MBS Session resources, which may include multiple MBS QoS Flows, by sending MBS Session Resource Setup Response, TMGI, N2 SM information ([N3mb DL Tunnel Info]), message after the AMF transferred the Namf_MBSBroadcast_ContextCreate Response () to the MB-SMF.

11. The AMF may transfer the Namf_MBSBroadcast_ContextStatusNotify request () to the MB-SMF. When the AMF receives the response from all NG-RAN nodes, the AMF may include an indication of the completion of the operation. If the AMF does not receive responses from all NG-RAN nodes before the maximum response time elapses since the reception of the Namf_MBSBroadcast_ContextCreate Request, then the AMF may need to transfer the Namf_MBSBroadcast_ContextStatusNotify request () which indicates partial success or failure.

12. If N3mb point-to-point transport is to be used, e.g., N3mb DL Tunnel Info is present in the MBS Session Start Response message from AMF, the MB-SMF may send an N4mb Session Modification Request to the MB-UPF to allocate the N3mb point-to-point transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 12 may be skipped.

13. The AF may start transmitting the DL media stream to MB-UPF using the N6mb Tunnel, or optionally un-tunnelled, that is, as an IP multicast stream using the HL MC address.

14. The MB-UPF may transmit the media stream to NG-RAN via N3mb multicast transport or point-to-point transport.

15. The NG-RAN may transmit the received DL media stream using DL PTM resources.

NOTE 2: Step 6-8 and 2-4 are comparable to step 2-5 and 6-7 in clause 7.2.1.4, respectively.

As a summarized overview of the foregoing, embodiments herein may be understood to Broadcast:

MB-SMF may provide a list of common NG-RAN UP, e.g., based on MBS service area, and provide it to NG-RAN in broadcast session start request. NG-RAN may determine to common user plane entity to be used from the list, without selecting other user plane entities.

To perform the first method of Figure 15 and/or Figure 20, the network node 101 , 102 may comprise the arrangement of panel a) or panel b).

Figure 21 depicts four different examples in panels a), b), c) and d), respectively, of the arrangement that the network node 101 , 102 may comprise. In some embodiments, the network node 101 , 102 may comprise the following arrangement depicted in Figure 21a.

To perform the first method of Figure 15 and/or Figure 20, the network node 101 , 102 may comprise the arrangement of panel a) or panel b).

To perform the second method of Figure 16 and/or Figures 10-11 , the network node

101 , 102 may comprise the arrangement of panel c) or panel d).

In Figure 21 , optional units are indicated with dashed boxes.

As depicted in panel a), the network node 101 , 102 may be configured to perform the sending of Action 1501 , e.g., by means of a sending unit 2101 within the network node 101 ,

102, configured to perform this action.

Other units 2102 may be comprised in the network node 101 , 102.

The embodiments herein in the network node 101 , 102 may be implemented through one or more processors, such as a processor 2103 in the network node 101 , 102 depicted in Figure 21a and Figure 21c, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 101 , 102. One such carrier may be in the form of a CD ROM disc. It is, however, feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 101 , 102.

The network node 101 , 102 may further comprise a memory 2104 comprising one or more memory units. The memory 2104 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the network node 101 , 102. In some embodiments, the network node 101 , 102 may receive information from, e.g., the first network node 101, the second network node 102, the third network node 103, the first radio network node 111, the second radio network node 112, the wireless device 130 and/or another node, through a receiving port 2105. In some embodiments, the receiving port 2105 may be, for example, connected to one or more antennas in network node 101, 102. In other embodiments, the network node 101 , 102 may receive information from another structure in the communications network 100 through the receiving port 2105. Since the receiving port 2105 may be in communication with the processor 2103, the receiving port 2105 may then send the received information to the processor 2103. The receiving port 2105 may also be configured to receive other information.

The processor 2103 in the network node 101 , 102 may be further configured to transmit or send information to e.g., the first network node 101 , the second network node 102, the third network node 103, the first radio network node 111, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network

100, through a sending port 2106, which may be in communication with the processor 2103, and the memory 2104.

Thus, the methods according to the embodiments described herein for the network node

101 , 102 may be respectively implemented by means of a computer program 2107 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 2103, cause the at least one processor 2103 to carry out the actions described herein, as performed by the network node 101 , 102. The computer program 2107 product may be stored on a computer-readable storage medium 2108. The computer-readable storage medium 2108, having stored thereon the computer program 2107, may comprise instructions which, when executed on at least one processor 2103, cause the at least one processor 2103 to carry out the actions described herein, as performed by the network node 101 , 102. In some embodiments, the computer-readable storage medium 2108 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 2107 product may be stored on a carrier containing the computer program 2107 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 2108, as described above.

The network node 101, 102 may comprise a communication interface configured to facilitate communications between the network node 101, 102 and other nodes or devices, e.g., the first network node 101, the second network node 102, the third network node 103, the first radio network node 111 , the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the network node 101 , 102 may comprise the following arrangement depicted in Figure 21b and Figure 21 d. The network node 101, 102 may comprise a processing circuitry 2103, e.g., one or more processors such as the processor 2103, in the network node 101, 102 and the memory 2104. The network node 101 , 102 may also comprise a radio circuitry 2109, which may comprise e.g., the receiving port 2105 and the sending port 2106. The processing circuitry 2103 may be configured to, or operable to, perform the method actions according to Figure 15, and Figure 20 in panel b), and Figure 16 and Figures 10-11 in panel d), and/or Figures 26-30, in a similar manner as that described in relation to Figure 21a and Figure 21c), respectively. The radio circuitry 2109 may be configured to set up and maintain at least a wireless connection with the first network node 101 , the second network node 102, the third network node 103, the first radio network node 111 , the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the network node 101 , 102 operative to operate in the communications network 100. The network node 101 , 102 may comprise the processing circuitry 2103 and the memory 2104, said memory 2104 containing instructions executable by said processing circuitry 2103, whereby the network node 101, 102 is further operative to perform the actions described herein in relation to the network node 101, 102, e.g., in Figure 15, Figure 20, Figure 16, Figures 10-11 and/or Figures 26-30.

The network node 101, 102 may also be configured to communicate user data with a host application unit in a host computer 2610, e.g., via another link such as 2650.

The network node 101, 102 may comprise an arrangement as shown in Figure 21, panel c) or d), to enable performance of the second method, or as shown in Figure 26.

The network node 101, 102 may be configured to perform the receiving of Action 1601, e.g., by means of a receiving unit 2110 within the network node 101, 102, configured to perform this action.

The network node 101, 102 may be configured to perform the sending of Action 1603, e.g., by means of a sending unit 2111 within the network node 101, 102, configured to perform this action.

The network node 101, 102 may be configured to perform the receiving of Action 1604, e.g., by means of the receiving unit 2110 within the network node 101 , 102, configured to perform this action. The network node 101, 102 may be configured to perform the storing of Action 1605, e.g., by means of a storing unit 2112 within the network node 101, 102, configured to perform this action.

The network node 101, 102 may be configured to perform the exchanging of Action 1605, e.g., by means of an exchanging unit 2113 within the network node 101 , 102, configured to perform this action.

The network node 101, 102 may be configured to perform the sending of Action 1606, e.g. by means of the sending unit 2102, configured to perform this action.

Other units 2114 may be comprised in the network node 101, 102.

Those skilled in the art will also appreciate that the units 2101-2102 and 2110-2114 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 2103, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 2101-2102 and 2110-2114 described above may be implemented as one or more applications running on one or more processors such as the processor 2103.

The description of the remaining components depicted in Figure 21 , panels c) and d) may be understood to correspond to that provided for Figure 21, panels a) and b), respectively.

Figure 22 depicts two different examples in panels a) and b), respectively, of the arrangement that the first radio network node 111 may comprise to perform the method described in Figure 17. In some embodiments, the first radio network node 111 may comprise the following arrangement depicted in Figure 22a.

Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. In Figure 22 optional units are indicated with dashed boxes. The first radio network node 111 may be configured to perform the receiving of Action 1701, e.g., by means of a receiving unit 2201 within the first radio network node 111, configured to perform this action.

Other units 2202 may be comprised in the first radio network node 111.

The embodiments herein in the first radio network node 111 may be implemented through one or more processors, such as a processor 2203 in the first radio network node 111 depicted in Figure 22a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first radio network node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first radio network node 111.

The first radio network node 111 may further comprise a memory 2204 comprising one or more memory units. The memory 2204 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first radio network node 111.

In some embodiments, the first radio network node 111 may receive information from, e.g., the network node 101 , 102, the first network node 101 , the second network node 102, the third network node 103, the second radio network node 112, the wireless device 130 and/or another node, through a receiving port 2205. In some embodiments, the receiving port 2205 may be, for example, connected to one or more antennas in first radio network node 111. In other embodiments, the first radio network node 111 may receive information from another structure in the communications network 100 through the receiving port 2205. Since the receiving port 2205 may be in communication with the processor 2203, the receiving port 2205 may then send the received information to the processor 2203. The receiving port 2205 may also be configured to receive other information.

The processor 2203 in the first radio network node 111 may be further configured to transmit or send information to e.g., the network node 101 , 102, the first network node 101 , the second network node 102, the third network node 103, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100, through a sending port 2206, which may be in communication with the processor 2203, and the memory 2204.

Those skilled in the art will also appreciate that the unit 2201-2202 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 2203, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application- Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

Also, in some embodiments, the different units 2201-2202 described above may be implemented as one or more applications running on one or more processors such as the processor 2203.

Thus, the methods according to the embodiments described herein for the first radio network node 111 may be respectively implemented by means of a computer program 2207 product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor 2203, cause the at least one processor 2203 to carry out the actions described herein, as performed by the first radio network node 111. The computer program 2207 product may be stored on a computer-readable storage medium 2208. The computer-readable storage medium 2208, having stored thereon the computer program 2207, may comprise instructions which, when executed on at least one processor 2203, cause the at least one processor 2203 to carry out the actions described herein, as performed by the first radio network node 111. In some embodiments, the computer-readable storage medium 2208 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 2207 product may be stored on a carrier containing the computer program 2207 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 2208, as described above.

The first radio network node 111 may comprise a communication interface configured to facilitate communications between the first radio network node 111 and the network node 101, 102, the first network node 101, the second network node 102, the third network node 103, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the first radio network node 111 may comprise the following arrangement depicted in Figure 22b. The first radio network node 111 may comprise a processing circuitry 2203, e.g., one or more processors such as the processor 2203, in the first radio network node 111 and the memory 2204. The first radio network node 111 may also comprise a radio circuitry 2209, which may comprise e.g., the receiving port 2205 and the sending port 2206. The processing circuitry 2203 may be configured to, or operable to, perform the method actions according to Figure 17, Figure 20 and/or Figures 26-30, in a similar manner as that described in relation to Figure 22a. The radio circuitry 2209 may be configured to set up and maintain at least a wireless connection with the network node 101, 102, the first network node 101 , the second network node 102, the third network node 103, the second radio network node 112, the wireless device 130, another node, and/or another structure in the communications network 100. Circuitry may be understood herein as a hardware component.

Hence, embodiments herein also relate to the first radio network node 111 operative to operate in the communications network 100. The first radio network node 111 may comprise the processing circuitry 2203 and the memory 2204, said memory 2204 containing instructions executable by said processing circuitry 2203, whereby the first radio network node 111 is further operative to perform the actions described herein in relation to the first radio network node 111, e.g., in Figure 17, Figure 20 and/or Figures 26-30.

The first radio network node 111 may also be configured to communicate user data with a host application unit in a host computer 2610, e.g., via another link such as 2650.

The first radio network node 111 may comprise an arrangement as shown in Figure 22 or in Figure 26.

Figure 23 depicts two different examples in panels a) and b), respectively, of the arrangement that the second radio network node 112 may comprise to perform the method described in Figure 18. In Figure 23 optional units are indicated with dashed boxes.

The description of Figure 23 corresponds to that already provided with regards to Figure 13, with the exception of the units depicted, which are described as follows.

The second radio network node 112 may be configured to perform the receiving action 1801, e.g., by means of a receiving unit 2301 within the second radio network node 112, configured to perform this action.

The second radio network node 112 may be configured to perform the sending of Action 1803, e.g., by means of a sending unit 2302 within the second radio network node 112, configured to perform this action.

The second radio network node 112 may be configured to perform the selecting of Action 1802, e.g., by means of a selecting unit 2303 within the second radio network node 112, configured to perform this action.

The second radio network node 112 may be configured to perform the receiving of Action 1804, e.g., by means of the receiving unit 2301 within the second radio network node 112, configured to perform this action.

Other units 2304 may be comprised in the second radio network node 112. The second radio network node 112 may also be configured to communicate user data with a host application unit in a host computer 2610, e.g., via another link such as 2650.

The second radio network node 112 may comprise an arrangement as shown in Figure 23 or in Figure 26.

Figure 24 depicts two different examples in panels a) and b), respectively, of the arrangement that the third network node 103 may comprise to perform the method described in Figure 19. The description of Figure 24 corresponds to that already provided with regards to Figure 14, with the exception of the units depicted, which are described as follows.

In Figure 24 optional units are indicated with dashed boxes.

The third network node 103 may be configured to perform this exchanging action 1901 , e.g., by means of an exchanging unit 2401 within the third network node 103, configured to perform this action.

Other units 2402 may be comprised in the third network node 103.

The third network node 103 may also be configured to communicate user data with a host application unit in a host computer 2610, e.g., via another link such as 2650.

The third network node 103 may comprise an arrangement as shown in Figure 24 or in Figure 26.

Further Extensions And Variations

Figure 25: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments

With reference to Figure 25, in accordance with an embodiment, a communication system includes telecommunication network 2510 such as the communications network 100, for example, a 3GPP-type cellular network, which comprises access network 2511 , such as a radio access network, and core network 2514. Access network 2511 comprises a plurality of network nodes such as the first radio network node 111 and the second radio network node 112. For example, base stations 2512a, 2512b, 2512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 2513a, 2513b, 2513c. Each base station 2512a, 2512b, 2512c is connectable to core network 2514 over a wired or wireless connection 2515. A plurality of wireless devices, such as the wireless device 130 are comprised in the communications network 100. In Figure 25, a first UE 2591 located in coverage area 2513c is configured to wirelessly connect to, or be paged by, the corresponding base station 2512c. A second UE 2592 in coverage area 2513a is wirelessly connectable to the corresponding base station 2512a. While a plurality of UEs 2591 , 2592 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 2512. Any of the UEs 2591 , 2592 are examples of the wireless device 130.

Telecommunication network 2510 is itself connected to host computer 2530, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 2530 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 2521 and 2522 between telecommunication network 2510 and host computer 2530 may extend directly from core network 2514 to host computer 2530 or may go via an optional intermediate network 2520. Intermediate network 2520 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 2520, if any, may be a backbone network or the Internet; in particular, intermediate network 2520 may comprise two or more sub-networks (not shown).

The communication system of Figure 25 as a whole enables connectivity between the connected UEs 2591 , 2592 and host computer 2530. The connectivity may be described as an over-the-top (OTT) connection 2550. Host computer 2530 and the connected UEs 2591 , 2592 are configured to communicate data and/or signaling via OTT connection 2550, using access network 2511 , core network 2514, any intermediate network 2520 and possible further infrastructure (not shown) as intermediaries. OTT connection 2550 may be transparent in the sense that the participating communication devices through which OTT connection 2550 passes are unaware of routing of uplink and downlink communications. For example, base station 2512 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 2530 to be forwarded (e.g., handed over) to a connected UE 2591. Similarly, base station 2512 need not be aware of the future routing of an outgoing uplink communication originating from the UE 2591 towards the host computer 2530.

In relation to Figures 26, 27, 28, 29, and 30, which are described next, it may be understood that a UE is an example of the wireless device 130, and that any description provided for the UE equally applies to the wireless device 130. It may be also understood that the base station is an example of the first radio network node 111 and the second radio network node 112, and that any description provided for the base station equally applies to the first radio network node 111 and the second radio network node 112.

Figure 26: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments

Example implementations, in accordance with an embodiment, of the wireless device 130, e.g., a UE, the first radio network node 111 and the second radio network node 112, e.g., a base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 26. In communication system 2600, such as the communications network 100, host computer 2610 comprises hardware 2615 including communication interface 2616 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 2600. Host computer 2610 further comprises processing circuitry 2618, which may have storage and/or processing capabilities. In particular, processing circuitry 2618 may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 2610 further comprises software 2611 , which is stored in or accessible by host computer 2610 and executable by processing circuitry 2618. Software 2611 includes host application 2612. Host application 2612 may be operable to provide a service to a remote user, such as UE 2630 connecting via OTT connection 2650 terminating at UE 2630 and host computer 2610. In providing the service to the remote user, host application 2612 may provide user data which is transmitted using OTT connection 2650.

Communication system 2600 further includes the first radio network node 111 and the second radio network node 112, exemplified in Figure 26 as a base station 2620 provided in a telecommunication system and comprising hardware 2625 enabling it to communicate with host computer 2610 and with UE 2630. Hardware 2625 may include communication interface 2626 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2600, as well as radio interface 2627 for setting up and maintaining at least wireless connection 2670 with the wireless device 130, exemplified in Figure 26 as a UE 2630 located in a coverage area (not shown in Figure 26) served by base station 2620. Communication interface 2626 may be configured to facilitate connection 2660 to host computer 2610. Connection 2660 may be direct or it may pass through a core network (not shown in Figure 26) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 2625 of base station 2620 further includes processing circuitry 2628, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 2620 further has software 2621 stored internally or accessible via an external connection.

Communication system 2600 further includes UE 2630 already referred to. Its hardware 2635 may include radio interface 2637 configured to set up and maintain wireless connection 2670 with a base station serving a coverage area in which UE 2630 is currently located. Hardware 2635 of UE 2630 further includes processing circuitry 2638, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 2630 further comprises software 2631 , which is stored in or accessible by UE 2630 and executable by processing circuitry 2638. Software 2631 includes client application 2632. Client application 2632 may be operable to provide a service to a human or non-human user via UE 2630, with the support of host computer 2610. In host computer 2610, an executing host application 2612 may communicate with the executing client application 2632 via OTT connection 2650 terminating at UE 2630 and host computer 2610. In providing the service to the user, client application 2632 may receive request data from host application 2612 and provide user data in response to the request data. OTT connection 2650 may transfer both the request data and the user data. Client application 2632 may interact with the user to generate the user data that it provides.

It is noted that host computer 2610, base station 2620 and UE 2630 illustrated in Figure 26 may be similar or identical to host computer 2530, one of base stations 2512a, 2512b, 2512c and one of UEs 2591 , 2592 of Figure 25, respectively. This is to say, the inner workings of these entities may be as shown in Figure 26 and independently, the surrounding network topology may be that of Figure 25.

In Figure 26, OTT connection 2650 has been drawn abstractly to illustrate the communication between host computer 2610 and UE 2630 via base station 2620, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 2630 or from the service provider operating host computer 2610, or both. While OTT connection 2650 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 2670 between UE 2630 and base station 2620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2630 using OTT connection 2650, in which wireless connection 2670 forms the last segment. More precisely, the teachings of these embodiments may improve the latency, signalling overhead, and service interruption and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 2650 between host computer 2610 and UE 2630, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 2650 may be implemented in software 2611 and hardware 2615 of host computer 2610 or in software 2631 and hardware 2635 of UE 2630, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 2650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 2611 , 2631 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 2650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 2620, and it may be unknown or imperceptible to base station 2620. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 2610’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 2611 and 2631 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2650 while it monitors propagation times, errors etc.

Figure 27: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 27 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 25 and 26. For simplicity of the present disclosure, only drawing references to Figure 27 will be included in this section. In step 2710, the host computer provides user data. In substep 2711 (which may be optional) of step 2710, the host computer provides the user data by executing a host application. In step 2720, the host computer initiates a transmission carrying the user data to the UE. In step 2730 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 28: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 28 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 25 and 26. For simplicity of the present disclosure, only drawing references to Figure 28 will be included in this section. In step 2810 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 2820, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2830 (which may be optional), the UE receives the user data carried in the transmission. Figure 29: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 29 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 25 and 26. For simplicity of the present disclosure, only drawing references to Figure 29 will be included in this section. In step 2910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2920, the UE provides user data. In substep 2921 (which may be optional) of step 2920, the UE provides the user data by executing a client application. In substep 2911 (which may be optional) of step 2910, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 2930 (which may be optional), transmission of the user data to the host computer. In step 2940 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 30: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 30 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 25 and 26. For simplicity of the present disclosure, only drawing references to Figure 30 will be included in this section. In step 3010 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Further numbered embodiments

1 . A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

5. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

6. The communication system of embodiment 5, further including the base station.

7. The communication system of embodiment 6, further including the UE, wherein the UE is configured to communicate with the base station.

8. The communication system of embodiment 7, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

11. A method implemented in a base station, comprising one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

15. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

16. The method of embodiment 15, further comprising: at the base station, transmitting the user data.

17. The method of embodiment 16, wherein the user data is provided at the host computer by executing a host application, the method further comprising: at the UE, executing a client application associated with the host application.

21. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

25. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

26. The communication system of embodiment 25, further including the UE. 27. The communication system of embodiment 26, wherein the cellular network further includes a base station configured to communicate with the UE.

28. The communication system of embodiment 26 or 27, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

31. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the wireless device 130.

35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

36. The method of embodiment 35, further comprising: at the UE, receiving the user data from the base station.

41. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

45. A communication system including a host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to: perform one or more of the actions described herein as performed by the wireless device 130.

46. The communication system of embodiment 45, further including the UE.

47. The communication system of embodiment 46, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

48. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

49. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

51. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the wireless device 130.

52. The method of embodiment 51 , further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

55. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

56. The method of embodiment 55, further comprising: at the UE, providing the user data to the base station.

57. The method of embodiment 56, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

58. The method of embodiment 56, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

61. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

65. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

66. The communication system of embodiment 65, further including the base station.

67. The communication system of embodiment 66, further including the UE, wherein the UE is configured to communicate with the base station.

68. The communication system of embodiment 67, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

71. A method implemented in a base station, comprising one or more of the actions described herein as performed by the first radio network node 111 and the second radio network node 112.

75. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130. 7Q. The method of embodiment 75, further comprising: at the base station, receiving the user data from the UE. 77. The method of embodiment 76, further comprising: at the base station, initiating a transmission of the received user data to the host computer.

REFERENCE LIST 1. TS 23.247 v17.2.0 Architectural enhancements for 5G multicast-broadcast services;

Stage 2 (Release 17)

2. 38.300 Change Request: R3-222925

3. 38.401 Change Request: R3-222926

4. LS from RAN3: R3-222867