WO2021136655A1 - Procédés de sensibilisation de noeud de réseau à un service de multidiffusion ou de diffusion dans un réseau de télécommunication, et appareil associé - Google Patents

Procédés de sensibilisation de noeud de réseau à un service de multidiffusion ou de diffusion dans un réseau de télécommunication, et appareil associé Download PDF

Info

Publication number
WO2021136655A1
WO2021136655A1 PCT/EP2020/086292 EP2020086292W WO2021136655A1 WO 2021136655 A1 WO2021136655 A1 WO 2021136655A1 EP 2020086292 W EP2020086292 W EP 2020086292W WO 2021136655 A1 WO2021136655 A1 WO 2021136655A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
network node
communication device
multicast
notification
Prior art date
Application number
PCT/EP2020/086292
Other languages
English (en)
Inventor
Jie LING
Joakim ÅKESSON
Erik Stare
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2021136655A1 publication Critical patent/WO2021136655A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present disclosure relates generally to methods and apparatus for network node awareness of multicast or broadcast service (MBS) in a telecommunication network, including a radio access network and/or a core network.
  • MMS multicast or broadcast service
  • Evolved multimedia broadcast multicast service was initially specified for Long Term
  • LTE Long Term Evolution
  • SAI Service Area Identifier
  • GCSE Group Communication System Enablers
  • multicast/broadcast for fifth generation mobile system may be specified.
  • Mission Critical Services MCS may be one of the use cases driving the solution.
  • a method performed by a network node in a telecommunication network for adaptively tracking multicast session information.
  • the network node can perform operations receiving a notification from a network entity including session information for a multicast service identified by a multicast service identifier.
  • the network node can perform further operations tracking the network entity and the multicast service identifier.
  • the network node can perform further operations creating a service context when other network entities have not previously communicated interest in the multicast service.
  • the network node can perform further operations sending a notification to an uplink network node including an indication that the network node is interested in the multicast service.
  • the network node can perform further operations receiving a session start request from the uplink network node.
  • the session start request includes the multicast service identifier and at least one of a lower layer IP multicast address; a UDP port; a quality of service,
  • the network node can perform further operations sending a notification to the uplink network node including a notification that the network node is interested in the multicast service.
  • the notification to the uplink network node is sent when a notification to the uplink network node was not previously sent.
  • the network node can perform further operations receiving a session start request from the uplink network node.
  • the session start request is based on the tracking of the network node and the multicast service identifier and includes at least one of a lower layer IP multicast address; a UDP port; a quality of service, QoS information; a session start time; and a broadcast area.
  • the network node can perform further operations determining to handover the communication device to a target cell of the telecommunication network.
  • the network node can perform further operations including the service context associated with one or more communication device in the handover.
  • the network node can perform further operations copying the service context associated with the one or more communication device to the target cell.
  • the network node can perform further operations deleting the service context for the communication device in the source cell of the telecommunication network when the communication device is a last served communication device in the source cell.
  • the network node can perform further operations sending a notification to the uplink network node including a notification that the network node is not interested in the multicast service.
  • the notification to the uplink network node is sent based on the last communication device tracked by the network node reporting to the network node that the communication device is not interested in the multicast service.
  • the network node can perform further operations removing the communication device from the service context.
  • the network node can perform further operations deleting the service context when the communication device is the last served communication device by the network node.
  • the network node can perform further operations receiving, based on the session information including the interest of the base station or the multicast scheduling entity in the multicast service and the multicast service identifier, a notification from the uplink network node informing the network node of a session stop request.
  • the network node can perform further operations sending, based on the interest of the communication device in the multicast service identified and the multicast service identifier, a notification informing the communication device that multicast service session with the communication device is being stopped.
  • the network node can perform further operations deleting the service context for the communication device.
  • the network node can perform further operations receiving an indication of a disconnection of the communication device to the multicast service.
  • the network node can perform further operations reconnecting the communication device to the multicast service (1) when an amount of time set for a timer of the communication device has not expired, or (2) when an amount of time set for a timer of the network node has not expired.
  • the network node can perform further operations deleting the service context for the communication device when an amount of time set for a timer of the network node has expired.
  • the network node can perform further operations receiving a new notification from the communication device after the reconnecting including interest of the communication device in the multicast service identified by the multicast service identifier.
  • the network node can perform further operations renewing tracking of the communication device and the multicast service identifier.
  • the network node can be a first network node.
  • the first network node can perform operations where receiving the notification from a network entity includes a notification from the base station or the multicast scheduling entity, before a multicast session is established and when the notification was not previously received from the base station or the multicast scheduling entity, that the network entity is interested in the multicast service identified by the multicast service identifier.
  • the first network node can perform further operations sending, to the base station or the multicast scheduling entity, a session start request based on the tracking of the network entity and the multicast service identifier.
  • the network node can be a second network node.
  • the second network node can perform operations where the receiving a notification from a network entity includes receiving the notification from the first network node before a multicast session is established.
  • the second network node can perform further operations sending, to the first network node, a session start request based on the tracking of the network entity and the multicast service identifier.
  • the second network node can perform further operations sending a notification to the first network node, based on the session information including the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • the second network node can perform further operations sending a notification to the first network node, based on the session information including the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • a method performed by a communication device in a telecommunication network is provided for adaptively tracking multicast session information. The communication device can perform operations initiating a notification to a network node including session information for a multicast service identified by a multicast service identifier.
  • the communication device can perform further operations receiving packets from the network node based on the notification to the network node including the session information.
  • the communication device can perform further operations receiving a notification from the network node, based on the session information including the communication device having an interest in the multicast service identified by the multicast service identifier, informing the communication device that the multicast service session with the communication device is being stopped.
  • the communication device can perform further operations sending an indication to the network node of a disconnection of the communication device to the multicast service.
  • the communication device can perform further operations reconnecting to the multicast service (1 ) when an amount of time set for a timer of the communication device has not expired, or (2) when an amount of time set for a timer of the network node has not expired.
  • the communication device can perform further operations sending a new notification to the network node after the reconnecting including interest of the communication device in the multicast service identified by the multicast service identifier.
  • the communication device can perform further operations sending a new notification to the network node after the reconnecting including interest of the communication device in the multicast service identified by the multicast service identifier.
  • Some approaches for eMBMS may be dependent on an application client determining if coverage is poor, which may be challenging. Additionally, some approaches for eMBMS may perform signaling on an application level to an application server, independent of actual lower level mobility decisions, which may result in session interruptions. [0032] Some approaches for eMBMS may include service areas that are statically defined at the start of an eMBMS service. Transmissions, therefore, may become inefficient when the service is transmitted in cells where no, or very few, users are present.
  • One or more embodiments of the present disclosure may include methods for enabling uplink nodes to be aware of the MBS interests (also referred to herein as service or session interests) from downlink nodes in a telecommunication network.
  • Uplink nodes may track the involved downlink nodes.
  • Operations advantages that may be provided by one or more embodiments include an uplink node uplink node sending session start, update and/or stop requests concerning a MBS to relevant downlink nodes based on received information from the relevant downlink nodes.
  • one or more embodiments may improve adaptively tracking interested downlink nodes and an associated operation for controlling a MBS.
  • Figure 1 illustrates a 5G MBS architecture including control plane and user plane separation and service-based architecture principles in 5G Core (5GC);
  • Figure 2 illustrates a sequence flow of operations about how a user equipment (UE) may join the session before a multimedia broadcast multicast service (MBMS) session has been established according to some embodiments of the present disclosure;
  • UE user equipment
  • MBMS multimedia broadcast multicast service
  • Figure 3 illustrates exemplary interactions in the network as well as the UE side when a multicast server (MC Server) decides to start a MBMS service according to some embodiments of the present disclosure
  • Figure 4 illustrates a user plane stack according to some embodiments of the present disclosure
  • Figure 5 illustrates a sequence flow of operations when a UE joins a session after a MBMS session has been established according to some embodiments of the present disclosure
  • Figure 6 illustrates a sequence flow of operations when a UE leaves a MBMS session according to some embodiments of the present disclosure
  • Figure 7 illustrates a sequence flow of operations when a MC Server decides to stop a MBMS session according to some embodiments of the present disclosure
  • Figure 8 is a block diagram and data flow diagram of a neural network circuit that can be used in the network computing device according to some embodiments of the present disclosure
  • Figure 7 is a block diagram illustrating a client computing device according to some embodiments of the present disclosure.
  • Figure 8 is a block diagram illustrating a communication device according to some embodiments of the present disclosure.
  • Figure 9 is a block diagram illustrating a network node according to some embodiments of the present disclosure.
  • Figure 10 is a block diagram illustrating a network entity according to some embodiments of the present disclosure.
  • FIGS 11-14 are flowcharts illustrating operations that may be performed by a network node in accordance with some embodiments of the present disclosure.
  • FIG. 15 is a flowchart illustrating operations that may be performed by a communication device in accordance with some embodiments of the present disclosure.
  • a communication device refers to any device intended for accessing services via an access network and configured to communicate over the access network.
  • the communication device may be, but is not limited to, a user equipment (UE), user device, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, television, radio, tablet computer, laptop, or PC.
  • the communication device may be a portable, pocket-storable, hand-held, computer-comprises, or vehicle-mounted mobile device, enabled to communicate voice and/or data, via wireless or wireline connection.
  • a network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a communication device and/or with other network nodes, network entities, or equipment in the telecommunication network to enable and/or provide wireless access to the communication device and/or to perform other functions (e.g., administration) in the telecommunication network.
  • network nodes include, but are not limited to, base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), gNode Bs, etc.), access points (APs) (e.g., radio access points), etc.
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multistandard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a user device with access to the telecommunication network or to provide some service to a communication device that has accessed the telecommunication network.
  • a network entity refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with network nodes, network entities, or equipment in the telecommunication network to enable to perform other functions (e.g., administration) in the telecommunication network.
  • network entities include, but are not limited to, base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), gNode Bs, etc.), access points (APs) (e.g., radio access points), access and mobility management function (AMF) nodes, communication devices, etc.
  • BSs base stations
  • APs access points
  • AMF access and mobility management function
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network entity may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network entities include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes
  • SON nodes e.g., SON nodes
  • positioning nodes e.g., E-SMLCs
  • MDTs
  • potential problems with some approaches for MBMS may be dependent on an application client determining if coverage is poor.
  • procedures for seamless transition between unicast and broadcast transmission is specified in TS 23.468, section 5.3.3.2.
  • the procedure is dependent on the application client determining if coverage is poor (to take proactive make-before-break measures).
  • the client shall signal to the application server that it instead wants to be served via unicast.
  • it may be challenging to reliably detect such poor conditions that require a transition to unicast.
  • a UE handover or cell reselection to a cell not providing the eMBMS service may occur.
  • Another potential problem may be that service areas used for eMBMS may be statically defined at the start of an eMBMS service (although there are procedures that allows for some level of modifications). Transmissions therefore may become inefficient because the service may be transmitted in cells where no (or very few) users are present.
  • a broadcast service may be started in a service area identified by a service area identifier (SAI). It could also be started in a larger broadcast area, identified by a list of SAIs. Another option is to start the service in an area identified by a cell(s) or a list of cell(s).
  • SAI service area identifier
  • the service (or bearer) itself may be identified with a temporary mobile group identity (TMGI).
  • TMGI temporary mobile group identity
  • This bearer may be statically coupled to the broadcast area, regardless of where the receiving UEs may be located (although it is possible to request modifications of the bearer, including the covered area).
  • EPS Evolved Packet Core
  • EPS Evolved Packet Core
  • a UE in RRC Idle may monitor the Tracking Area (TA) it is camping on when doing cell reselections from one cell to another. If it is changing TA, a UE may need to report this (Tracking Area Update - TAU) to the mobility management entity (MME) in the EPC.
  • MME mobility management entity
  • the network When the network needs to establish a bearer for mobile terminated traffic it may use this TA information to page/locate the UE and then an end-to-end (E2E) bearer can be (initially) established through the currently serving cell (then following the UE as described above).
  • E2E end-to-end
  • a user that is affiliated to a GCSE service may need to report its SAI location but in this case to the application layer - to the group communication service application server (GCS AS) (e.g. a Mission Critical Push To Talk server, MCPTT).
  • GCS AS group communication service application server
  • MCPTT Mission Critical Push To Talk server
  • the GCS AS may use this location information to establish unicast and/or broadcast bearers where the group members are currently located (e.g., one broadcast bearer may target user 1-5, another broadcast bearer may target users 6-8 while users 9-10 may get individual unicast bearers, depending on reported UE locations). If a UE moves out of a broadcast area, the GCS client should preferably proactively report this to perform the make-before-break procedure specified in TS 23.468, section 5.3.3.2. As described above, this may be challenging and often may not be possible.
  • At least the client should report when it has moved out of the area, moved into a cell that does not belong to the broadcast area where the UE was listening to the broadcast bearer, identified by a TMGI. This would trigger the break-before-make procedure, TS 23.468, 5.3.3.3, resulting in a service interruption.
  • an eMBMS architecture may rely on the SAI information to trigger the session from the application layer. If the application server cannot measure the UE location precisely and in a timely manner, and if the relationships between SAI and downlink nodes are incorrect, it may be possible: (1) The broadcast starts to a certain area, but no UEs are interested in receiving it, which may be a kind of inefficiency; and/or (2) There may be UEs interested in the service, but the broadcast is not started to this area, which also means the broadcast may not be started effectively.
  • Figure 1 illustrates a 5G MBS architecture including control plane and user plane separation and service-based architecture principles in 5G Core (5GC).
  • the architecture may include a NR 101 (also referred to herein as a base station or a multicast scheduling entity (MCE) 101 or gNB/MCE 101 ) communicatively connected via a user plane (shown by the dashed line of Figure 1 ) to a UE 109, a multicast/broadcast user plane function node 115 (MB-UPF 115), and an application server 117 (also referred to herein as App Service 117, multicast server, MC Server, or MC Server 117).
  • MCE multicast scheduling entity
  • NR 101 may also be communicatively connected via a control plane to Access and Mobility management Function 103 (AMF 103), multicast/broadcast session management function 105 (MB-SMF 105), and App Server 117.
  • AMF 103 Access and Mobility management Function 103
  • MB-SMF 105 multicast/broadcast session management function 105
  • App Server 117 may include a MBMS client/modem 111 and an application client 113 (App Client 113).
  • App Client 113 may be communicatively connected to App Server 117 via a GC1 107 interface.
  • gNB/MCE 101 may be, for example, a base station (e.g., a gNB in a 5G network) or a multicast scheduling entity (MCE) residing in a base station or shared among multiple base stations for coordination purposes (e.g., a MCE in a 4G network).
  • MCE multicast scheduling entity
  • MB-SMF 105 may be responsible for a control plane in 5G MBS.
  • MB-SMF 105 may receive the session management from the application server 117 and further establish MBMS bearers towards AMF 103.
  • AMF 103 may further establish MBMS bearers to RAN (e.g., gNB/MCE 101).
  • MB-UPF 115 may be responsible for the user plane function in 5G MBS. MB-UPF 115 may receive the content delivered from the application server 117 and may further transmit to RAN (e.g., gNB/MCE 101).
  • RAN e.g., gNB/MCE 101
  • AMF 103 of Figure 1 is shown as an AMF that is a non-dedicated multicast/broadcast node
  • MB-SMF 105 of Figure 1 is shown as a dedicated MB-SMF
  • AMF 103 and MB-SMF 105 are shown as examples that have been provided for ease of illustration and explanation of one embodiment.
  • Other embodiments may include uplink nodes that are either non-dedicated MB-nodes or dedicated MB- nodes, or any combination of non-dedicated and dedicated uplink MB-nodes.
  • Dedicated MB-uplink nodes may handle functionalities for telecommunication network MBS (e.g., 5G MBS).
  • AMF may be kept and reused for a 5MBS solution.
  • a new dedicated function MB-AMF may be used to handle the functionalities for 5G MBS.
  • a single UE 109 and a single NR 101 are shown as examples in Figure 1 and have been provided for ease of illustration and explanation of one embodiment. Other embodiments may include any non-zero number of each of UE 109 and NR 101. Additionally, a 5G MBS architecture is shown as an example in Figure 1 and has been provided for ease of illustration and explanation of one embodiment. Other embodiments may include any telecommunication network (RAN). [0056] Still referring to Figure 1 , in various embodiments of the present disclosure, a network node may include, but is not limited to, a base station, a gNB, a MCE, an AMF, an SMF, etc.
  • a network entity may include, but are not limited to, a base station, a gNB, a MCE, an AMF, a communication device, etc.
  • the terms “communication device”, “user equipment”, and “UE” are used interchangeably herein.
  • the terms “gNB”, “base station”, “MCE”, and NR are used interchangeably herein.
  • methods may be provided for enabling uplink nodes to be aware of service interests from downlink nodes.
  • the uplink nodes may keep track of the involved downlink nodes, so that the session start/update/stop procedures may be optimized or improved in a precise way.
  • various embodiments may provide feasibility to have a seamless switch for mission critical services achieved in the network layer, instead of the application layer. This seamless switch may even be performed in the RAN.
  • a communication device may inform a network node (e.g., gNB/MCE 101) about a service that the communication device is interested in.
  • the network node may inform a first uplink node (e.g., AMF 103) about the interested service when it is the first communication device under its coverage that informed the network node of its interest in the service.
  • the first uplink node e.g., AMF 103
  • the communication device decides to leave a service.
  • the communication device informs a network node (e.g., a gNB 101) that it is no longer interested in the service.
  • the network node informs a first uplink node (e.g., AMF 103) that it is no longer interested in the service, when there are no communication devices under its coverage that are interested in the service.
  • the first uplink node informs a second uplink node (e.g., MB-SMF 105) that it is no longer interested in the service, when there are no communication devices under its coverage are interested in the service.
  • the uplink nodes in a network layer (e.g., in a 5G MBS control plane), the uplink nodes (e.g., the first and second uplink nodes) keep track of the interested downlink nodes, so that the session can be established and terminated in a precise way (e.g., an uplink node may only send session start/update/stop requests to the relevant downlink nodes based on the received information from the downlink nodes).
  • Presently disclosed embodiments may provide potential advantages.
  • One potential advantage may provide optimization or improvement of a session start/update/stop procedure to be delivered to the relevant nodes, which is more effective and accurate.
  • Further potential advantages of various presently disclosed embodiments may include starting the broadcast in cells to enable a UE(s), e.g., to have seamless switching for mission critical services due to mobility. Methods of presently disclosed embodiments may avoid the situation that UEs need to receive the contents over broadcast, but broadcast is not yet started in that area.
  • Further potential advantages of various presently disclosed embodiments may include that a broadcast may not be started in irrelevant cells to improve the radio efficiency. Methods of presently disclosed embodiments may further avoid a situation that a broadcast session has been started in a certain area but no UEs are listening in that area.
  • seamless switching implemented in a network layer may include in the RAN, instead of an application layer.
  • seamless switching implemented in the network layer may be provided for mission critical services.
  • a 5G MBS architecture is illustrated in Figure 1.
  • a first uplink node 103 e.g., AMF
  • a second uplink node 105 MB-SMF
  • MB-SMF 105 may be responsible for control plane in 5G MBS.
  • MB-SMF 105 may receive the session management from the application server 117 and further establish MBMS bearers towards AMF 103.
  • AMF 103 may further establish MBMS bearers to RAN 101 (e.g., gNB/MCE).
  • Multicast/Broadcast User Plane Function (MB-UPF) 115 may be responsible for the user plane function in 5G MBS.
  • MB-UPF 115 may receive the content delivered from the application server 117 and further transmitted to RAN 101 (e.g., gNB).
  • RAN 101 e.g., gNB
  • Figure 2 illustrates a sequence flow of operations about how a UE may join the session before the MBMS session has been established.
  • Figure 2 illustrates, at operation 200, multicast client (MC Client) hosted by a UE 109 that wants to initiate a new group call sends a session establish request to MC Server 117.
  • MC Client multicast client
  • MC Server 117 sends a created service request to MB-SMF 105 to allocate service identifier.
  • service identifier In 5G MBS, it is possible to reuse TMGI as the service identifier, which was used in eMBMS.
  • MC Server 117 allocates resources for the bearer for the group communication, which may include higher layer IP multicast address and UDP port (operation 204).
  • MC Server 117 performs MBMS Bearer Announcement to all MC Clients affiliated to the group and hosted by the UE 109, which includes the MC service identifier, as well as the high layer IP multicast address and UDP port to be used in the inner IP multicast packets (operation 206).
  • the MBMS Bearer Announcement can be performed via GC1 interface 107 or via a dedicated MBMS signalling bearer.
  • MC Client gets the service identifier
  • MC Client informs gNB/MCE 101 that it is interested in the service (identified by the service identifier) via MBMS Client and Modem on UE 109.
  • gNB/MCE 101 may keep track of UE 109 and interested service identifier by storing the UE 109 to a service context, including the service identifier and all UEs 109 served that has shown an interest in the service.
  • the message sent from UE 109 could be an extended MBMSInterestlndication (specified in TS 36.331 for LTE), including a (list of) service identifiers (such as TMGI). If the service context does not already exist (other served UEs 109 have expressed interest) the service context is created. If interest for multiple service identifiers is expressed there may be one service context per service.
  • gNB/MCE 101 also informs AMF 103 that the gNB/MCE 101 is interested in the MC service, if it has not informed AMF 103 before.
  • AMF 103 keeps track of the gNB/MCE 101 and interested MC service identifier.
  • AMF 103 informs MB-SMF 105 that it is interested in the MC service, if it has not informed MB-SMF 105 before.
  • MB-SMF 105 keeps track of the AMF 103 and the interested MC service identifier.
  • MB-SMF 105 keeps track of AMF 103 and the interested MC service identifier.
  • AMF 103 keeps track of gNB/MCE 101 and the interested MC service identifier.
  • gNB/MCE 101 keeps track of UE 109 and the interested MC service identifier.
  • the MC service identifier and resources may only need to be allocated once. Operations 202 and 204 may be performed once per service, but not per MC Client.
  • Operations 202 and 204 may take place prior to operation 200. Once MC Server 117 sees the needs, it can allocate the service identifier and resources in advance. [0078] For those receiving MC Clients, they may receive MBMS Bearer Announcement without a session establishment request, especially when the announcement is performed over a signaling MBMS bearer.
  • Figure 3 illustrates exemplary interactions in the network as well as the UE 109 side when MC Server 117 decides to start the MBMS service (operation 300).
  • FIG. 3 illustrates, at operation 302, MC Server 117 sends a session start request to MB- SMF 105 to start the session with the MC service identifier, together with the quality of service (QoS) information (e.g. including guaranteed bit rate (GBR)), optional start time, and optional the broadcast area.
  • QoS quality of service
  • GRR guaranteed bit rate
  • MB-SMF 105 allocates resources for the MBMS bearer in the network, which includes the lower layer IP multicast address, UDP port and GTP-U identifier (operation 304).
  • MB-SMF 105 sends a session start request to the interested AMF 103 together with MC service identifier, lower layer IP multicast (LL IP-MC), user datagram protocol
  • UDP User Datagram
  • QoS information e.g. including GBR
  • GBR GBR
  • AMF 103 sends a session start request to the interested gNB/MCE 101 together with MC service identifier, LL IP-MC, UDP port, QoS information (including GBR), as well as the optional start time and optional broadcast area.
  • MB-SMF 105 sends a session start request to MB-UPF 115 to establish the user plane with the service identifier, lower layer IP multicast address, UDP port, QoS information (e.g. including GBR) as well as optional start time.
  • MB-UPF 115 allocates the receiving IP/port and responds such information in session start response to MB-SMF 105 (operation 312).
  • MB-SMF 105 responds the receiving IP/port to MC Server 117 for user plane content ingestion via session start response (operation 314).
  • the broadcast area can still be used for control plane message routing. That is, for some use cases (e.g., TV delivery), the receiving UEs 109 may not have uplink connection.
  • the uplink nodes cannot keep track of downlink nodes based on the expressed interests.
  • the broadcast area can be used in such scenario, so that the uplink nodes can send the session start request to the downlink nodes based on the broadcast area.
  • gNB/MCE 101 may join the multicast group via routers (e.g., internet group management protocol/multicast listener discovery (IGMP/MLD) Join). In other words, operation 318 may not be a direct message from gNB/MCE 101 to MB-UPF 115.
  • MB-UPF 115 receives packets from MC Server 117.
  • MC Server 117 encapsulates the higher layer IP multicast packets into a UDP tunnel and delivers to the Receiving Address.
  • MB-UPF 115 encapsulates higher layer (HL) IP packets in GPRS tunnelling protocol for the user plane (GTP-U) and optionally appends SYNC headers (for single frequency network delivery), and then encapsulate them into LL IP multicast address and multicast the IP packets out.
  • HL higher layer
  • GTP-U GPRS tunnelling protocol for the user plane
  • SYNC headers for single frequency network delivery
  • Figure 4 illustrates, for example, a user plane stack.
  • operation 322 may be performed by MB-UPF 115 receiving packets from UDP tunnel between MC Server 117 and MB- UPF 115, and adding SYNC, GTP-U headers, outer UDP header and LL IP-MC header.
  • the interested gNBs 101 receive packets from the lower layer IP multicast group of MB-UPF 115.
  • the gNBs 101 extract the outer lower layer IP multicast group, decapsulate from SYNC and GTP-U, then get the higher layer IP multicast packets. In other words, the gNBs 101 receive IP multicast packets (e.g., LL IP-MC) and receives a payload (e.g., without LL UDP/IP headers). [0095] At operation 328, the gNBs 101 deliver those higher layer IP multicast packets over the air.
  • IP multicast packets e.g., LL IP-MC
  • a payload e.g., without LL UDP/IP headers
  • MC Client 113 receives them via MBMS Client and Modem 111 on UE 109.
  • Figure 5 illustrates a sequence flow of operations when a UE joins a session after the MBMS session has been established.
  • Figure 5 illustrates, at operation 500, a UE 109 joined a session while the session is established.
  • MC Client 113 on UE 109 sends a session establishment request to MC Server 117 (operation 502).
  • MC Server 117 performs MBMS Bearer Announcement to MC Client 113, which may include the service identifier, as well as the high layer IP multicast address and UDP port to be used in the inner IP multicast packets.
  • MC Server 117 can perform the announcement immediately without further need for resource allocation in MC Server 117 and to MB-SMF 105.
  • the MBMS Bearer Announcement can be performed via GC1 interface 107 or via a dedicated MBMS signaling bearer.
  • MC Client 113 gets the service identifier, MC Client 113 informs gNB/MCE 101 that it is interested in the service (identified by the service identifier) via MBMS Client and Modem 111 on UE 109. gNB/MCE 101 keeps track of the UE 109 and interested service identifier, storing it to an existing service context or creating a new service context.
  • gNB/MCE 101 also informs AMF 103 the gNB/MCE 101 is interested in the service, if it has not informed AMF 103 before.
  • AMF 103 keeps track of the gNB 101 and interested service identifier. Otherwise, gNB/MCE 101 should have received Session Start Request from AMF 103 before, and operations 508 to 514 can be skipped.
  • AMF 103 informs MB-SMF 105 that it is interested in the service, if it has not informed MB-SMF 105 before.
  • MB-SMF 105 keeps track of the AMF 103 and the interested service identifier. Otherwise, AMF 103 should have received a Session Start Request from MB-SMF 105 before, and operations 510 and 512 can be skipped.
  • MB-SMF 105 sends a session start request to AMF 103 together with service identifier, LL IP-MC, UDP port, QoS information (including GBR), as well as the optional start time and optional broadcast area.
  • AMF 103 sends a session start request to the interested gNB/MCE 101 together with service identifier, LL IP-MC, UDP port, QoS information (including GBR), as well as the optional start time and optional broadcast area.
  • operation 518 those interested gNBs 101 join the LL IP multicast group while the specific source is MB-UPF 115.
  • gNB/MCE 101 may join the multicast group via routers (e.g., IGMP/MLD Join).
  • operation 518 may not be a direct message from gNB/MCE 101 to MB-UPF 115.
  • MB-UPF 115 receives packets from MC Server 117.
  • MC Server 117 encapsulates the higher layer IP multicast packets into a UDP tunnel and delivers to the Receiving Address.
  • MB-UPF 115 encapsulates HL IP packets in GTP-U and optional append SYNC headers (for single frequency network delivery), and then encapsulate them into lower layer IP multicast address and multicast the IP packets out.
  • Figure 4 illustrates a user plane stack. Referring to Figure 4, operation 522 may be performed by MB-UPF 115 receiving packets from UDP tunnel between MC Server 117 and MB-UPF 115, and adding SYNC, GTP-U headers, outer UDP header and LL IP-MC header.
  • the interested gNBs 101 receive packets from the lower layer IP multicast group.
  • the gNBs 101 extract the outer LL IP multicast group, decapsulate from SYNC and GTP-U, then get the higher layer IP multicast packets.
  • the gNBs 101 receive IP multicast packets (e.g., LL IP-MC) and receives a payload (e.g., without LL UDP/IP headers).
  • the gNBs 101 deliver those higher layer IP multicast packets over the air.
  • MC Client 113 may get them via MBMS Client and Modem 111 on UE 109.
  • a UE 109 moving to another serving gNB 101 will now be described. [00113] In some embodiments of the present disclosure, a UE 109 moves to another serving gNB 101.
  • Serving gNB 101 determines that the UE 109 should be handed over to another target cell. As part of the normal handover process (as defined in TS 38.300, 9.2.3 and TS 38.331,) the UE 109 context is transferred. In addition to this all service contexts associated with the UE 109 (one context per service) is copied to the target cell. In case the UE 109 is the last served UE in the source cell, the service context is instead transferred (in other words, deleted in the source cell).
  • the service contexts can be copied/transferred by expanding a HandoverPreparationlnformation message to include a (list of) service context(s).
  • Figure 6 illustrates a sequence flow of operations when a UE leaves the session.
  • Figure 6 illustrates, at operation 600, a MC Client 113 of a UE 109 leaves the session as in the following exemplary operations.
  • MC Client 113 on UE 109 sends release session request to MC Server 117 (operation 602).
  • MC Client 113 informs gNB/MCE 101 that it is not interested in the service
  • gNB/MCE 101 keeps track of the UE 109 and interested service identifier. The UE 109 is removed from the service context. If this is the last UE 109 served by the gNB 101 , the context is deleted.
  • gNB/MCE 101 also informs AMF 103 the gNB/MCE 101 is not interested in the service, if the UE 109 is the last interested one in gNB/MCE 101. AMF 103 keeps track of the UE 109, gNB/MCE 101 and interested service identifier. Otherwise, operations 606 to 612 can be skipped. [00120] At operation 608, AMF 103 informs MB-SMF 105 that it is not interested in the service, if the gNB/MCE 101 is the last interested one in AMF 103. MB-SMF 105 keeps track of the AMF 103 and the interested service identifier.
  • gNB 101 leaves the lower layer IP multicast group, so that it will no longer receive packets for the service. [00123] UE mobility handling will now be described.
  • the gNB/MCE 101 is responsible for the mobility handling.
  • UE 109 moves across gNB/MCE 101, UE 109 will leave the original gNB/MCE 101 (inform original gNB/MCE 101 that it is not interested in the service) and join the session in the new gNB/MCE 101 (the new gNB/MCE 101 is informed that the UE 109 is interested in the service.
  • This can be achieved by the source cell sharing a service context to the target cell; or, in another example, by the UE 109 signaling the interest.
  • Figure 7 illustrates a sequence flow of operations when MC Server 117 decides to stop the MBMS session.
  • Figure 7 illustrates, at operation 700, a MC Server 117 decides to stop the session as in the following exemplary operations.
  • MC Server 117 sends session stop request to MB-SMF105 to stop the session with the service identifier (operation 702).
  • MB- SMF 105 sends a session stop request to the interested AMF 103 together with the service identifier.
  • AMF 103 sends a session stop request to the interested gNB/MCE 101 together with service identifier.
  • gNB/MCE 101 informs the interested UEs 109 the session is going to be stopped. The interested UE 109 also deletes the associated service context.
  • MB-SMF 105 sends a session stop request to MB-UPF 115 to teardown the user plane with the service identifier.
  • both MC Client 113 and gNB/MCE 101 can keep timers after UE 109 disconnection.
  • a timer T 1 is set for UE 109
  • a timer T2 is set for gNB/MCE 101
  • UE 109 reconnects before T1, there is no need for MC Client 113 to inform gNB/MCE 101 about its interested services.
  • MC Client 113 informs gNB/MCE 101 about its interested service again.
  • a first scenario if UE 109 reconnects before T2, gNB/MCE 101 receives the interests, but does nothing because gNB/MCE 101 has not deleted the UE 109 interests so far.
  • gNB/MCE 101 deletes the UE 109 interests. For a service, if there are no UEs 109 interested in the service in the gNB/MCE 101, gNB/MCE 101 may further inform AMF 103 that it is no longer interested in the service and leave the multicast group. If in AMF 103, there are no gNBs 101 interested in the service, AMF 103 informs MB-SMF 105 that it is no longer interested in the service as well.
  • MC Client 113 informs gNB 101 of its interested services again, and gNB 101 keeps track of the UE 109 and the interested services. For a service, if gNB/MCE 101 informed AMF 103 that it was no longer interested in the service before, gNB/MCE 101 informs AMF 103 again that it is interested in the service , receives a session start request from AMF 103, and joins multicast group to deliver packets over the air again. If AMF 103 informed MB-SMF 105 that it was no longer interested in the service before, AMF 103 informs MB-SMF 105 again that it is interested in the service again and receives a session start request from MB-SMF 105.
  • a method may be provided in a telecommunication network (e.g., 5G MBS) to enable the uplink nodes to be aware of the service interests from the downlink nodes.
  • the uplink nodes will keep track of the involved downlink nodes, so that the session start/update/stop procedures can be optimized or improved in a precise way.
  • the method may provide the feasibility to have a seamless switch for mission critical services achieved in the network layer, including RAN, instead of the application layer.
  • a UE 109 informs a gNB 101 about its interested service.
  • the gNB 101 informs AMF 103 about its interested service, when there are UEs 109 which have informed AMF 103.
  • AMF 103 informs MB-SMF 105 about its interested service, when there are gNBs 101 which have informed AMF 103.
  • a UE 109 decides to leave a service.
  • UE 109 informs gNB 101 that it is no longer interested in the service.
  • gNB 101 informs AMF 103 that it is no longer interested in the service, when there are no UEs 109 under its coverage that are interested in the service.
  • AMF 103 informs MB-SMF 105 that AMF 103 is no longer interested in the service, when there are no UEs 109 under its coverage that are interested in the service.
  • a method may ensure that the broadcast starts to all the necessary cells to enable UEs 109 to have seamless switching for mission critical services due to mobility.
  • a method may be provided that can avoid the situation that UEs 109 need to receive the contents over broadcast, but broadcast is not started in that area.
  • a method may be provided that may ensure that the broadcast will not be started to irrelevant cells to improve the radio efficiency.
  • the method may further avoid a situation that a broadcast session has been started to a certain area but no UEs 109 are listening in that area.
  • a method may be provided that may provide seamless switching implemented in the network layer, instead of the application layer, e.g. for mission critical services.
  • An example communication device will now be described.
  • FIG 8 is a block diagram illustrating a communication device 800, which may correspond to UE 109 in Figures 1 and 4 and/or the MC Client and MBMS Client/Modem in Figures 2, 3, and 5-7, that is configured according to some embodiments.
  • the communication device includes at least one processor 803 (also referred to as processor), at least one memory 805 (also referred to as memory), and at least one transceiver circuit 801 (also referred to as transceiver) including a transmitter and a receiver configured to provide radio communications through at least one antenna 807, e.g., one or more arrays of MIMO antennas, with a radio access networks (RANs) of a radio communications network.
  • RANs radio access networks
  • the processor 803 is operatively connected to the transceiver 801 which is connected to the antenna 807 for transmitting and receiving signals.
  • the processor 803 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks.
  • the processor 803 may be defined to include memory so that a separate memory is not required.
  • the communication device 800 may also include a user output interface, e.g., display device and/or speaker interface, and/or a user input interface, e.g., touch screen, keyboard, etc. [00147] An example network node will now be described.
  • Figure 9 is a block diagram illustrating a network node 900, which may correspond to NR 101 (gNB/MCE 101 ), AMF 103, or MB-SMF 105 in Figures 1 -7, that is configured according to some embodiments having components that are configured according to some embodiments.
  • the network node includes at least one network interface 907, at least one processor 903 (also referred to as processor), at least one memory 905 (also referred to as memory) containing program code.
  • the network node may optionally include at least one transceiver circuit 901 (also referred to as transceiver) including a transmitter and a receiver configured to provide radio communications through at least one antenna, e.g., one or more arrays of MIMO antennas, with a wireless communication device of a telecommunication network.
  • the processor 903 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks.
  • the memory 905, described below as a computer readable medium, stores computer readable program code that when executed by the processor 903 causes the processor 903 to perform operations according to embodiments disclosed herein. According to other embodiments, the processor 903 may be defined to include memory so that a separate memory is not required.
  • Figure 10 is a block diagram illustrating a network entity 1000, which may correspond to NR 101 (e.g., gNB/MCE 101), AMF 103, or a communication device (e.g., UE 109, MC Client, orMBMS Client/Modem)) in Figures 1-7, that is configured according to some embodiments having components that are configured according to some embodiments.
  • the network node includes at least one network interface 1007, at least one processor 1003 (also referred to as processor), at least one memory 1005 (also referred to as memory) containing program code.
  • the network node may optionally include at least one transceiver circuit 1001 (also referred to as transceiver) including a transmitter and a receiver configured to provide radio communications through at least one antenna, e.g., one or more arrays of MIMO antennas, with a wireless communication device of a telecommunication network.
  • the processor 1003 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor) that may be collocated or distributed across one or more networks.
  • Figure 11 shows operations that may be performed by a network node 900 (e.g., gNB/MCE 101 , AMF 103, MB-SMF 105 of Figures 1 -7) according to various embodiments of inventive concepts.
  • Figure 12 shows operations that may be performed by a network node 900 (e.g., gNB/MCE 101 of Figures 1-7) according to various embodiments of inventive concepts.
  • Figure 13 shows operations that may be performed by a first network node 900 (e.g., AMF 103 of Figures 1-7) according to various embodiments of inventive concepts.
  • Figure 14 shows operations that may be performed by a second network node 900 (e.g., MB-SMF 105 of Figures 1-7) according to various embodiments of inventive concepts.
  • Figure 15 shows operations that may be performed by a network entity 800 (e.g., UE 109 or MB Client, MBMS Client/Modem of Figures 1 -7) according to various embodiments of inventive concepts.
  • a network entity 800 e.g., UE 109 or MB Client, MBMS Client/Modem of Figures 1 -7)
  • Each of the operations described in Figures 11-15 can be combined and/or omitted in any combination with each other, and it is contemplated that all such combinations fall within the spirit and scope of this disclosure.
  • some of operations of Figure 12 may be optional or omitted.
  • some operations in operations 1200-1206 may be omitted (e.g.
  • operations 1200-1202 occur, operations 1204-1206 may be omitted); and/or when there is no handover, operations 1210-1214 may be omitted; and/or when operations 1216-1220 are omitted, operations 1222-1226 may occur.
  • some operations of Figure 15 may be optional, omitted, or in a different order than shown in Figure 15. For example, operations 1506-1510 may occur before operation 1504; and if a session is stopped in operation 1504, there is no need to report the UE’s interest in the service in operation 1510 after reconnecting.
  • operations can be performed by a network node (e.g., 900 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • the operations of network node 900 include receiving (1100) a notification from a network entity (e.g., 101, 103, 109, 1000) including session information for a multicast service identified by a multicast service identifier.
  • the operations of the network node further include tracking (1102) the network entity and the multicast service identifier.
  • the session information includes at least one of an interest in the multicast service identified by the multicast service identifier; a session start request for the multicast service identified by the multicast service identifier; a disinterest in the multicast service identified by the multicast service identifier; and a session stop request for the multicast service identified by the multicast service identifier.
  • the tracking includes storing the network entity to a service context including the multicast service identifier and other network entities that have communicated session information including an interest in the multicast service.
  • further operations that can be performed by the network node 900 may include creating (1104) the service context when other network entities have not previously communicated interest in the multicast service.
  • the service context includes at least one service context per multicast service associated with the communication device, and the creating (1104) the service context includes creating the service context to associate each of at least one multicast service with each of at least one network entity.
  • the notification from the network entity includes a multimedia broadcast multicast service message including at least one multicast service identifier.
  • the multicast service identifier includes a Temporary Mobile Group Identity, TMGI.
  • the network entity is a communication device (e.g., 109, 800), the network node is a base station or multicast scheduling entity (e.g., 101, 900), and the receiving a notification from a network entity includes receiving the notification from the communication device before a multicast session is established.
  • Figure 12 illustrates that operations can be performed by a network node 900 (e.g., gNB/MCE 101 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • the operations of network node 900 include sending (1200) a notification to an uplink network node (e.g., 103, 900) including an indication that the network node is interested in the multicast service.
  • an uplink network node e.g., 103, 900
  • the tracking includes the network node tracking the communication device and the multicast service identifier.
  • further operations that can be performed by the network node 900 may include receiving (1202) a session start request from the uplink network node (e.g., 103, 900).
  • the session start request includes the multicast service identifier and at least one of: a lower layer IP multicast address, a UDP port, a quality of service, QoS information, a session start time, and a broadcast area.
  • the receiving the session start request includes receiving the session start request based on the tracking of the network entity and the multicast service identifier.
  • further operations that can be performed by the network node 900 may include sending (1204) a notification to the uplink network node including a notification that the network node is interested in the multicast service.
  • the notification to the uplink network node is sent when a notification to the uplink network node was not previously sent.
  • the tracking includes the network node tracking the communication device and the multicast service identifier.
  • further operations that can be performed by the network node 900 may include receiving (1206) a session start request from the uplink network node.
  • the session start request is based on the tracking of the network node and the multicast service identifier and includes at least one of a lower layer IP multicast address; a UDP port; a quality of service, QoS information; a session start time; and a broadcast area.
  • Further operations that can be performed by the network node 900 may include determining (1208) to handover the communication device to a target cell of the telecommunication network. Further operations that can be performed may include including (1210) the service context associated with one or more communication device in the handover; and copying (1212) the service context associated with the one or more communication device to the target cell.
  • Further operations that can be performed by the network node 900 may include deleting (1214) the service context for the communication device in the source cell of the telecommunication network when the communication device is a last served communication device in the source cell.
  • the notification from a network entity includes a notification from the communication device including a disinterest in the multicast service identified by the multicast service identifier.
  • Further operations that can be performed by the network node 900 may include sending (1216) a notification to the uplink network node (103, 900) including a notification that the network node is not interested in the multicast service.
  • the notification to the uplink network node is sent based on the last communication device tracked by the network node reporting to the network node that the communication device is not interested in the multicast service.
  • the tracking includes the network node tracking the communication device and the multicast service identifier.
  • Further operations that can be performed by the network node 900 may include removing (1218) the communication device from the service context; and deleting (1220) the service context when the communication device is the last served communication device by the network node.
  • Further operations that can be performed by the network node 900 may include receiving (1222), based on the session information including the interest of the base station or the multicast scheduling entity in the multicast service and the multicast service identifier, a notification from the uplink network node informing the network node of a session stop request. Further operations that can be performed may include sending (1224), based on the interest of the communication device in the multicast service identified and the multicast service identifier, a notification informing the communication device that multicast service session with the communication device is being stopped; and deleting (1226) the service context for the communication device.
  • Further operations that can be performed by the network node 900 may include receiving (1228) an indication of a disconnection of the communication device to the multicast service. Further operations that can be performed may include reconnecting (1230) the communication device to the multicast service (1 ) when an amount of time set for a timer of the communication device has not expired, or (2) when an amount of time set for a timer of the network node has not expired; and deleting (1232) the service context for the communication device when an amount of time set for a timer of the network node has expired.
  • Further operations that can be performed by the network node 900 may include receiving (1234) a new notification from the communication device after the reconnecting including interest of the communication device in the multicast service identified by the multicast service identifier; and renewing (1236) tracking of the communication device and the multicast service identifier.
  • Figure 13 illustrates that operations can be performed by a network node 900 that is a first network node (e.g., AMF 103 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • a network node 900 that is a first network node (e.g., AMF 103 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • AMF 103 of Figures 1-7 implemented using the structure of the block diagram of Figure 9
  • the notification from a network entity includes a notification from the base station or the multicast scheduling entity, before a multicast session is established and when the notification was not previously received from the base station or the multicast scheduling entity, that the network entity is interested in the multicast service identified by the multicast service identifier.
  • Further operations that can be performed by the first network node 900 may include sending (1300), to the base station or the multicast scheduling entity, a session start request based on the tracking of the network entity and the multicast service identifier.
  • the session start request is based on the tracking of the network entity and the multicast service identifier and further includes at least one of a lower layer IP multicast address; a UDP port; a quality of service, QoS information; a session start time; and a broadcast area.
  • the notification from a network entity includes a notification from the base station or the multicast scheduling entity, after a multicast session is established and when the notification was not previously received from the base station or the multicast scheduling entity, that the network entity is interested in the multicast service identified by the multicast service identifier.
  • the tracking includes the first network node tracking the base station or the multicast scheduling entity and the multicast service identifier.
  • the notification from a network entity includes a notification from the base station or the multicast scheduling entity including a disinterest in the multicast service identified by the multicast service identifier when the communication device is a last communication device tracked by the base station or the multicast scheduling entity that had an interest in the multicast service identified by the multicast service identifier.
  • the tracking includes the first network node tracking the base station or the multicast scheduling entity and the multicast service identifier.
  • Further operations that can be performed by the first network node 900 may include sending (1302) a notification to the base station or multicast scheduling entity (101, 900), based on the session information including the base station or multicast scheduling entity having an interest in the multicast service identified by the multicast service identifier, informing the base station or multicast scheduling entity that the multicast service session with the communication device is being stopped.
  • Figure 14 illustrates that operations can be performed by a network node 900 that is a second network node (e.g., MB-SMF 105 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • a network node 900 that is a second network node (e.g., MB-SMF 105 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • a network node 900 that is a second network node (e.g., MB-SMF 105 of Figures 1-7 implemented using the structure of the block diagram of Figure 9) in a telecommunication network for adaptively tracking multicast session information.
  • MB-SMF 105 of Figures 1-7 implemented using the structure of the block diagram of Figure 9
  • the network entity includes a first network node (103, 900), and the receiving a notification from a network entity includes receiving the notification from the first network node (103) before a multicast session is established.
  • the tracking before the multicast session is established, includes the second network node (105, 900) tracking the first network node (103, 900) and the multicast service identifier.
  • the notification from a network entity includes a notification from the first network node (103, 900), before a multicast session is established and when the notification was not previously received from the first network node, that the first network node is interested in the multicast service identified by the multicast service identifier.
  • Further operations that can be performed by the second network node 900 may include sending (1400), to the first network node (103, 900), the session start request based on the tracking of the network entity and the multicast service identifier.
  • the session start request further includes at least one of a lower layer IP multicast address; a UDP port; a quality of service, QoS information; a session start time; and a broadcast area.
  • the sending the session start request includes sending the session start request based on the tracking of the network entity and the multicast service identifier.
  • the notification from a network entity includes a notification from the first network node (103, 900) to a second network node (105, 900), after a multicast session is established and when the notification was not previously received from the first network node, that the first network node is interested in the multicast service identified by the multicast service identifier.
  • the tracking includes the second network node tracking the first network node and the multicast service identifier.
  • the notification from a network entity includes a notification that the first network node is not interested in the multicast service. The notification is sent based on a last network entity tracked by the first network node reporting to the first network node that the network entity is not interested in the multicast service.
  • the tracking includes the second network node (105) tracking the first network node (103) and the multicast service identifier.
  • Further operations that can be performed by the second network node 900 may include sending (1402) a notification to the first network node (103, 900), based on the session information including the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • a computer program can be provided that includes instructions which, when executed on at least one processor, cause the at least one processor to carry out methods performed by the network node.
  • a computer program product includes a non-transitory computer readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to carry out methods performed by the network node.
  • Figure 15 illustrates that operations can be performed by a communication device (e.g., UE 109 of Figures 1-7 implemented using the structure of the block diagram of communication device 800 of Figure 8) in a telecommunication network for adaptively tracking multicast session information.
  • the operations of communication device 800 may include initiating (1500) a notification to a network node (101, 1000) including session information for a multicast service identified by a multicast service identifier.
  • the session information includes at least one of an interest in the multicast service identified by the multicast service identifier; and a disinterest in the multicast service identified by the multicast service identifier.
  • Further operations that can be performed by the communication device 800 may include sending (1506) an indication to the network node of a disconnection of the communication device to the multicast service. Further operations that can be performed can include reconnecting (1508) to the multicast service (1 ) when an amount of time set for a timer of the communication device has not expired, or (2) when an amount of time set for a timer of the network node has not expired.
  • Further operations that can be performed by the communication device 800 may include sending (1510) a new notification to the network node after the reconnecting including interest of the communication device in the multicast service identified by the multicast service identifier.
  • a computer program can be provided that includes instructions which, when executed on at least one processor, cause the at least one processor to carry out methods performed by the communication device.
  • a computer program product can be provided that includes a non-transitory computer readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to carry out methods performed by the communication device.
  • These computer program instructions may be provided to a processor of a computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • a method performed by a network node (101 , 103, 105, 900) in a telecommunication network for adaptively tracking multicast session information comprising: receiving (1100) a notification from a network entity (101, 103, 109, 1000) comprising session information for a multicast service identified by a multicast service identifier; and tracking (1102) the network entity and the multicast service identifier.
  • the session information comprises at least one of: an interest in the multicast service identified by the multicast service identifier; a session start request for the multicast service identified by the multicast service identifier; a disinterest in the multicast service identified by the multicast service identifier; and a session stop request for the multicast service identified by the multicast service identifier.
  • the network entity comprises a communication device (109, 800), wherein the network node comprises a base station or a multicast scheduling entity (101, 900), and wherein the receiving a notification from a network entity comprises receiving the notification from the communication device before a multicast session is established.
  • receiving the session start request comprises receiving the session start request based on the tracking of the network entity and the multicast service identifier.
  • the tracking comprises the network node tracking the communication device and the multicast service identifier.
  • the notification from a network entity comprises a notification from the communication device comprising a disinterest in the multicast service identified by the multicast service identifier.
  • the method of embodiment 18, further comprising: sending (1216) a notification to the uplink network node (103, 900) comprising a notification that the network node is not interested in the multicast service, wherein the notification to the uplink network node is sent based on the last communication device tracked by the network node reporting to the network node that the communication device is not interested in the multicast service.
  • the notification from a network entity comprises a notification from the base station or the multicast scheduling entity, before a multicast session is established and when the notification was not previously received from the base station or the multicast scheduling entity, that the network entity is interested in the multicast service identified by the multicast service identifier.
  • the notification from a network entity comprises a notification from the base station or the multicast scheduling entity, after a multicast session is established and when the notification was not previously received from the base station or the multicast scheduling entity, that the network entity is interested in the multicast service identified by the multicast service identifier.
  • the notification from a network entity comprises a notification from the base station or the multicast scheduling entity comprising a disinterest in the multicast service identified by the multicast service identifier when the communication device is a last communication device tracked by the base station or the multicast scheduling entity that had an interest in the multicast service identified by the multicast service identifier.
  • the tracking comprises the first network node tracking the base station or the multicast scheduling entity and the multicast service identifier.
  • the network entity comprises a first network node (103, 900), wherein the network node comprises a second network node (105, 900), and wherein the receiving a notification from a network entity comprises receiving the notification from the first network node (103) before a multicast session is established.
  • the tracking comprises the second network node (105, 900) tracking the first network node (103, 900) and the multicast service identifier. 35.
  • the notification from a network entity comprises a notification from the first network node (103, 900), before a multicast session is established and when the notification was not previously received from the first network node, that the first network node is interested in the multicast service identified by the multicast service identifier.
  • 36. The method of any of embodiment 33 and 35, further comprising: sending (1400), to the first network node (103, 900), the session start request based on the tracking of the network entity and the multicast service identifier.
  • the session start request further comprises at least one of: a lower layer IP multicast address; a UDP port; a quality of service, QoS information; a session start time; and a broadcast area.
  • sending the session start request comprises sending the session start request based on the tracking of the network entity and the multicast service identifier.
  • the notification from a network entity comprises a notification from the first network node (103, 900) to a second network node (105, 900), after a multicast session is established and when the notification was not previously received from the first network node, that the first network node is interested in the multicast service identified by the multicast service identifier.
  • the tracking comprises the second network node tracking the first network node and the multicast service identifier.
  • the notification from a network entity comprises a notification that the first network node is not interested in the multicast service, wherein the notification is sent based on a last network entity tracked by the first network node reporting to the first network node that the network entity is not interested in the multicast service.
  • a network node (101, 103, 107, 900) comprising: processing circuitry (903); and memory (905) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to perform operations comprising: receiving (1100) a notification from a network entity (101, 103, 109, 1000) comprising session information for a multicast service identified by a multicast service identifier; and tracking (1102) the network entity and the multicast service identifier.
  • a computer program comprising program code to be executed by processing circuitry (903) of a network node (101 , 103, 105, 900), whereby execution of the program code causes the network node to perform operations comprising: receiving (1100) a notification from a network entity (101, 103, 109, 1000) comprising session information for a multicast service identified by a multicast service identifier; and tracking (1102) the network entity and the multicast service identifier.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (903) of a network node (101 , 103, 105, 900), whereby execution of the program code causes the network node to perform operations comprising: receiving (1100) a notification from a network entity (101, 103, 109, 1000) comprising session information for a multicast service identified by a multicast service identifier; and tracking (1102) the network entity and the multicast service identifier.
  • a method performed by a communication device (109, 800) in a telecommunication network for adaptively handling a multicast service comprising: initiating (1500) a notification to a network node (101, 1000) comprising session information for a multicast service identified by a multicast service identifier.
  • session information comprises at least one of: an interest in the multicast service identified by the multicast service identifier; and a disinterest in the multicast service identified by the multicast service identifier.
  • a communication device comprising: processing circuitry (803); and memory (805) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to perform operations comprising: sending (1402) a notification to the first network node (103, 900), based on the session information comprising the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • a communication device (109, 800) adapted to perform operations comprising: sending (1402) a notification to the first network node (103, 900), based on the session information comprising the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • a computer program comprising program code to be executed by processing circuitry (803) of a communication device (109, 800), whereby execution of the program code causes the communication device to perform operations comprising: sending (1402) a notification to the first network node (103, 900), based on the session information comprising the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (803) of a communication device (109, 800), whereby execution of the program code causes the communication device to perform operations comprising: sending (1402) a notification to the first network node (103, 900), based on the session information comprising the first network node having an interest in the multicast service identified by the multicast service identifier, informing the first network node that the multicast service session with the communication device is being stopped.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé mis en oeuvre par un noeud de réseau dans un réseau de télécommunication pour le suivi adaptatif d'informations de session de multidiffusion. Le noeud de réseau peut mettre en oeuvre des opérations de réception d'une notification provenant d'une entité de réseau, comprenant des informations de session relatives à un service de multidiffusion identifié par un identifiant de service de multidiffusion. Le noeud de réseau peut mettre en oeuvre d'autres opérations de suivi de l'entité de réseau et de l'identifiant de service de multidiffusion. L'invention concerne également un procédé mis en oeuvre par un dispositif de communication dans un réseau de télécommunication pour le suivi adaptatif d'informations de session de multidiffusion. Le dispositif de communication peut mettre en oeuvre des opérations d'envoi d'une notification à un noeud de réseau, comprenant des informations de session relatives à un service de multidiffusion identifié par un identifiant de service de multidiffusion.
PCT/EP2020/086292 2020-01-03 2020-12-15 Procédés de sensibilisation de noeud de réseau à un service de multidiffusion ou de diffusion dans un réseau de télécommunication, et appareil associé WO2021136655A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2020/070316 2020-01-03
CN2020070316 2020-01-03

Publications (1)

Publication Number Publication Date
WO2021136655A1 true WO2021136655A1 (fr) 2021-07-08

Family

ID=74106010

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/086292 WO2021136655A1 (fr) 2020-01-03 2020-12-15 Procédés de sensibilisation de noeud de réseau à un service de multidiffusion ou de diffusion dans un réseau de télécommunication, et appareil associé

Country Status (1)

Country Link
WO (1) WO2021136655A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023191696A1 (fr) * 2022-03-29 2023-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau, deuxième nœud de réseau radio, troisième nœud de réseau et procédés exécutés par ceux-ci pour gérer un plan utilisateur commun

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180199163A1 (en) * 2017-01-12 2018-07-12 Asustek Computer Inc. Method and apparatus of handling interest indication in a wireless communication system
WO2019114939A1 (fr) * 2017-12-12 2019-06-20 Nokia Solutions And Networks Oy Procédé, système et appareil de gestion de session de multidiffusion dans un réseau de communication 5g

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180199163A1 (en) * 2017-01-12 2018-07-12 Asustek Computer Inc. Method and apparatus of handling interest indication in a wireless communication system
WO2019114939A1 (fr) * 2017-12-12 2019-06-20 Nokia Solutions And Networks Oy Procédé, système et appareil de gestion de session de multidiffusion dans un réseau de communication 5g

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023191696A1 (fr) * 2022-03-29 2023-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau, deuxième nœud de réseau radio, troisième nœud de réseau et procédés exécutés par ceux-ci pour gérer un plan utilisateur commun

Similar Documents

Publication Publication Date Title
US10687179B2 (en) Service continuity for group communication over LTE eMBMS
KR101514425B1 (ko) Mbms 서비스 송신 방식의 전환 방법, 장치 및 사용자 장비
US7969938B2 (en) Method and apparatus for providing multimedia broadcast/multicast service according to mobility of user equipment
US8068843B2 (en) Method for increasing system capacity by transmitting control Signal for MBMS data by combining RLC and PDCP messages
KR100770876B1 (ko) 멀티미디어 방송/멀티캐스트 서비스 시스템에서 서비스세션의 시작시 주파수 선택 방법 및 장치
EP3409035B1 (fr) Commutation dynamique de service de transmission en continu entre une distribution en mode diffusion et en mode unidiffusion
EP2737734B1 (fr) Identification de résultats de comptage d'ue dans un EMBMS
EP2987381B1 (fr) Mise a jour de session de diffusion generale multimedia/service multimedia
KR20150048618A (ko) 이동성에 강인한 그룹 통신을 위한 방법 및 장치
CA2593845A1 (fr) Utilisation de ressources amelioree pour des services de diffusion selective multimedia (mbms)
KR100927985B1 (ko) 무선통신 시스템에서 일대다 ｍｂｍｓ 정보를 획득하는방법 및 장치
US20160150590A1 (en) Method and system for indicating a multicast session to user equipment (ue) in an idle mode
KR20230004776A (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
EP4079002B1 (fr) Zones de service adaptatives destinées à une continuité de session de multidiffusion
EP2843977A1 (fr) Procédé d'allocation de ressources pour service de diffusion, centre de gestion de ressources et mme
WO2021136655A1 (fr) Procédés de sensibilisation de noeud de réseau à un service de multidiffusion ou de diffusion dans un réseau de télécommunication, et appareil associé
WO2023083096A1 (fr) Procédé et appareil permettant de transmettre un service de diffusion en multidiffusion et nœud de communication
Nguyen et al. LTE Broadcast for Public Safety
CN118104257A (zh) 用户设备、源基站、目标基站和用于无缝ue mbs移动性的切换方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20833776

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20833776

Country of ref document: EP

Kind code of ref document: A1