Method and apparatus for multicast broadcast service (MBS) activation and deactivation

Abstract

Systems, methods, apparatuses, and computer program products for multicast broadcast service (MBS) deactivation and / or activation are provided. A method can include receiving, at a multicast broadcast session management entity, a multicast broadcast service (MBS) session setup message from at least one management entity, the MBS session setup message including at least one of an identifier of at least one network node requesting setup of a multicast broadcast service (MBS) session and an identifier of the at least one management entity. The method can also include storing, at the multicast broadcast management entity, at least one of the identifier of the at least one network node, the identifier of the at least one management entity, or an identifier of a region of the at least one management entity.

Description

Technical Field

[0001] Some example embodiments may generally relate to communications, including mobile or wireless telecommunication systems such as Long Term Evolution (LTE) or 5G radio access technologies or New Radio (NR) access technologies, or other communication systems. For example, some example embodiments may generally relate to systems and / or methods for activating and / or deactivating Multicast Broadcast Service (MBS). Background Technology

[0002] Examples of mobile or wireless telecommunications systems can include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN) for Long Term Evolution (LTE), LTE-A Advanced, MulteFire, LTE-APro, and / or 5G or New Radio (NR) access technologies. 5G wireless systems refer to next-generation (NG) radio systems and network architectures. 5G systems are primarily built on top of 5G New Radio (NR), but 5G (or NG) networks can also be built on top of E-UTRA radio. NR is estimated to provide bit rates on the order of 10-20 Gbit / s or higher and can support at least service categories such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communications (URLLC), as well as massive machine-type communications (mMTC). NR promises to enable extremely wide bandwidth and ultra-robust low-latency connectivity and massive networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communication become increasingly prevalent, there will be a growing demand for networks that meet the requirements of lower power consumption, lower data rates, and longer battery life. Next-Generation Radio Access Network (NG-RAN) refers to the RAN used for 5G, which can provide both NR and LTE (and Advanced LTE) radio access. Note that in 5G, nodes that can provide radio access to user equipment (i.e., similar to Node B (NB) in UTRAN, or Evolved NB (eNB) in LTE) can be designated as Next-Generation NB (gNB) when built on top of NR radio, and as Next-Generation eNB (NG-eNB) when built on top of E-UTRA radio. Summary of the Invention

[0003] One embodiment relates to a method that may include: a network node sending a multicast broadcast service (MBS) session establishment message including at least one of a network node identifier and a management entity identifier, the multicast broadcast service (MBS) session establishment message being sent through the management entity. The method may further include: receiving a message for deactivating a multicast broadcast service (MBS) session, and in response to receiving the message for deactivating a multicast broadcast service (MBS) session, transitioning the context of the multicast broadcast service (MBS) session to a deactivated state.

[0004] Another embodiment relates to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to at least: transmit a multicast broadcast service (MBS) session establishment message including at least one of an identifier of the apparatus and an identifier of a management entity, the multicast broadcast service (MBS) session establishment message being transmitted through the management entity; receive a message for deactivating a multicast broadcast service (MBS) session; and, in response to receiving the message for deactivating a multicast broadcast service (MBS) session, transition the context of the multicast broadcast service (MBS) session to a deactivated state.

[0005] Another embodiment relates to an apparatus that may include: components for sending a multicast broadcast service (MBS) session establishment message including at least one of an identifier of a network node and an identifier of a management entity, the multicast broadcast service (MBS) session establishment message being sent through the management entity. The apparatus may further include: components for receiving a message for deactivating a multicast broadcast service (MBS) session; and components for transitioning the context of the multicast broadcast service (MBS) session to a deactivated state in response to receiving the message for deactivating the multicast broadcast service (MBS) session.

[0006] Another embodiment relates to a method that may include: receiving from a multicast broadcast session management entity a message for deactivating a multicast broadcast service (MBS) session, the message including at least identifiers of one or more network nodes involved in the multicast broadcast service (MBS) session, and sending a deactivation message for deactivating the multicast broadcast service (MBS) session toward one or more network nodes indicated in the received deactivation message.

[0007] Another embodiment relates to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to at least: receive from a multicast broadcast session management entity a message for deactivating a multicast broadcast service (MBS) session, the message including at least identifiers of one or more network nodes involved in the multicast broadcast service (MBS) session; and send a deactivation message for deactivating the multicast broadcast service (MBS) session toward one or more network nodes indicated in the received deactivation message.

[0008] Another embodiment relates to an apparatus that may include: components for receiving from a multicast broadcast session management entity a message for deactivating a multicast broadcast service (MBS) session, the message including at least identifiers of one or more network nodes involved in the multicast broadcast service (MBS) session; and components for sending a deactivation message for deactivating the multicast broadcast service (MBS) session toward one or more network nodes indicated in the received deactivation message.

[0009] Another embodiment relates to a method that may include: receiving a multicast broadcast service (MBS) session establishment message from at least one management entity at a multicast broadcast session management entity, the multicast broadcast service (MBS) session establishment message including at least one of the following: an identifier of at least one network node requesting the establishment of a multicast broadcast service (MS) session, and an identifier of at least one management entity; and storing at least one of the following at the multicast broadcast session management entity: an identifier of at least one network node, an identifier of at least one management entity, or an identifier of a region of at least one management entity.

[0010] Another embodiment relates to an apparatus including at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to at least: receive a multicast broadcast service (MBS) session establishment message from at least one management entity, the MBS session establishment message including at least one of: an identifier of at least one network node requesting the establishment of a multicast broadcast service (MBS) session, and an identifier of at least one management entity; and store at least one of: the identifier of at least one network node, the identifier of at least one management entity, or an identifier of a region of at least one management entity.

[0011] Another embodiment relates to an apparatus that may include: a component for receiving a multicast broadcast service (MBS) session establishment message from at least one management entity, the MBS session establishment message including at least one of: an identifier of at least one network node requesting the establishment of a multicast broadcast service (MBS) session, and an identifier of at least one management entity. The apparatus may further include a component for storing at least one of: the identifier of at least one network node, the identifier of at least one management entity, or the identifier of a region of at least one management entity. Attached Figure Description

[0012] To correctly understand the exemplary embodiments, reference should be made to the accompanying drawings, in which:

[0013] Figure 1 An example block diagram of an MBS architecture based on an example is shown;

[0014] Figure 2 An example signaling diagram depicting information storage at the MB-SMF is shown according to one embodiment;

[0015] Figure 3 An example signaling diagram depicting the deactivation of an MBS session according to one embodiment is shown;

[0016] Figure 4 An example signaling diagram depicting the activation of an MBS session according to one embodiment is shown;

[0017] Figure 5A An example flowchart of a method according to one embodiment is shown;

[0018] Figure 5B An example flowchart of a method according to one embodiment is shown;

[0019] Figure 5C An example flowchart of a method according to one embodiment is shown;

[0020] Figure 6A An example block diagram of a device according to one embodiment is shown;

[0021] Figure 6B An example block diagram of a device according to one embodiment is shown; and

[0022] Figure 6C An example block diagram of an apparatus according to one embodiment is shown. Detailed Implementation

[0023] It will be readily understood that components of certain example embodiments, as generally described and illustrated in the accompanying drawings, can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for activating and / or deactivating Multicast Broadcast Service (MBS) is not intended to limit the scope of any particular embodiment, but rather represents selected example embodiments.

[0024] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the use of the phrases "some embodiments," "some examples," or other similar language throughout this specification means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Therefore, the appearance of the phrases "some embodiments," "some examples," "other examples," or other similar language throughout this specification does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

[0025] Furthermore, if necessary, the different functions or processes discussed below may be performed in different orders and / or simultaneously with each other. Additionally, if necessary, one or more of the described functions or processes may be optional or may be combined. Therefore, the following description should be considered as illustrating the principles and teachings of certain exemplary embodiments, and not as limiting them.

[0026] Figure 1 An example block diagram of MBS architecture 100 is shown. 5G MBS service information can be delivered from the application / service layer to the 5G core network (5GC) 110. Multiple UEs 120 can request to join an MBS session, MBS streaming can be established, and MBS data can be delivered to the multiple UEs 120. MBS sessions can be deactivated and / or activated. For example, upon detection of a multicast data pause or activity resumption, the MBS session can be deactivated / activated by an application function (AF) (e.g., via the Network Open Function (NEF)) or by a multicast user plane function (MB-UPF). During the period when the MBS session is deactivated, it has been agreed that the Next Generation Radio Access Network (NG-RAN) node 130 can transition one or more UEs to Radio Resource Control (RRC) idle mode.

[0027] Therefore, an MBS session can be stopped upon AF request, and (multiple) UEs already in the multicast session can become "idle". Furthermore, when the MB-UPF does not detect multicast data within a configurable time period, the MBS session can be deactivated, and similarly, (multiple) UEs already in the multicast session can become "idle".

[0028] Therefore, a method is needed for handling MBS contexts in NG-RAN nodes when MBS sessions are deactivated and when they are reactivated. For example, a solution might be needed in different scenarios where the NG-RAN node can decide to maintain UE connectivity, transition the UE to an RRC inactive state, or transition them to an RRC idle state. Furthermore, it may be desirable to avoid signaling spikes in the network used to manage these contexts during both deactivation and activation times.

[0029] Currently, when deactivation is triggered, it is anticipated that the MBS context will be held in the 5GC and removed from the NG-RAN node. Specifically, when an MBS session is deactivated by the 5GC, the MBS session context is held in the 5GC, but the AN resources with the context and the N3 tunnel used for the 5GC to share the MBS delivery method are released.

[0030] When an MBS session needs to be activated, the MB-UPF can send a message to the Multicast Session Management Function (MB-SMF). When the MB-SMF initiates MBS session activation to establish transport resources, the MB-SMF can notify the NG-RAN of session activation via the Session Management Function (SMF) and / or Access and Mobility Management Function (AMF) serving the UE within the multicast session.

[0031] MBS sessions can be activated / initiated via AF requests. When an MBS session needs to be activated / initiated, the NEF or MBSF can send a message to the MB-SMF to establish transport resources. The MB-SMF can obtain relevant multicast QoS flow information from the Policy Control Function (PCF). When the MB-SMF restarts the MBS session, it can notify the NG-RAN of session activation via the SMF / AMF serving the UE within the multicast session.

[0032] However, a precise notification mechanism is currently undefined. Furthermore, the release of all MBS context information could be signaling-intensive. It is also unclear how the MBS context for a UE used for RRC connection or an RRC-inactive UE will be recreated if it is removed during deactivation. Further unclear is how this notification can work for UEs that have already been transitioned to RRC idle, and how they can be re-established if all MBS contexts in the RAN are removed.

[0033] As will be discussed in detail below, certain example embodiments may provide solutions for at least the problems discussed above, as well as other problems that may benefit from the methods described herein.

[0034] Some example embodiments provide mechanisms for signaling deactivation when the MB-SMF receives a deactivation trigger from the MB-UPF and / or from the AF. As will be discussed in more detail below, according to some example embodiments, the process for deactivation or activation may rely on some information storage in, for example, the MB-SMF.

[0035] Figure 2 An example signaling diagram depicting information storage at the MB-SMF is shown according to one embodiment. Figure 2 As shown in the example, at 205, when an NG-RAN node establishes user plane (UP) resources with an MB-UPF via an MB-SMF, the NG-RAN node may include its NG-RAN node ID in the NGAP message and may also include an AMF ID (e.g., the AMF ID of the AMF through which the establishment message is sent to the MB-SMF). Upon receiving the MBS UP establishment message, at 210, the MB-SMF may store the NG-RAN node ID, and / or the associated AMF ID, and / or the area ID of the AMF through which the message is being delivered. For example, in some embodiments, the MB-SMF may build and store a list of NG-RAN node IDs for each AMF or a list of NG-RAN node IDs for each area. In one embodiment, at 215, the NG-RAN node may receive an MBS UP establishment response from the AMF.

[0036] Figure 3 An example signaling diagram depicting the deactivation of an MBS session according to one embodiment is shown. In one embodiment, at any point in time when the MB-SMF wants to trigger the deactivation of the MBS session, it can retrieve a list of all NG-RAN nodes involved in the MBS session from storage at 210. Then, at 320, the MB-SMF can send a deactivation message to one or more AMFs.

[0037] For example, in one embodiment, the MB-SMF can send deactivation messages to the involved NG-RAN nodes(s) via the associated AMF stored at location 210. In this embodiment, the deactivation message(s) may include at least the IDs of the NG-RAN nodes(s) involved in the MBS session, so that the AMF routes the deactivation message to the correct NG-RAN nodes(s).

[0038] According to another embodiment, the MB-SMF can send a deactivation message to the associated AMF(s) stored at location 210. In this embodiment, the deactivation message may include a list of NG-RAN node IDs involved in the MBS session associated with the AMF at location 210. The AMF may replicate the message toward the involved NG-RAN node(s) identified in the received deactivation message, or may construct and send an individual message for each NG-RAN node, containing the target NG-RAN node ID. In other embodiments, the MB-SMF may send an activation message to any AMF in the stored region to which the list of target NG-RAN node(s) belongs.

[0039] In another embodiment, the MB-SMF can send a deactivation message to an AMF for each region stored at 210. In this embodiment, the deactivation message may include a list of NG-RAN node IDs involved in the MBS session for that region. The AMF (e.g., an AMF for that region) may replicate the message toward the involved NG-RAN nodes(s), or may construct an individual message for each NG-RAN node, containing the target NG-RAN node ID.

[0040] According to some embodiments, upon receiving a deactivation message at 330, the NG-RAN node can transition the MBS context to a "deactivated state." As long as the MBS context state remains "deactivated," as shown at 340, the NG-RAN node can maintain the UE MBS context information in the UE context of a UE remaining in an RRC connection, as shown at 345. The NG-RAN node can maintain the UE MBS context information in the UE context of a UE remaining in an RRC inactive state, as shown at 347. The NG-RAN node can remove UE contexts including the UE MBS context information of a UE that has decided to transition to an RRC idle state. Furthermore, as long as at least one UE in the NG-RAN node is in an RRC connected state or an RRC inactive state, the NG-RAN node can maintain the N3 shared tunnel. The NG-RAN node can also maintain the MBS context used for the MBS session as long as at least one UE in the NG-RAN node is in an RRC connected state or an RRC inactive state. Otherwise, in one embodiment, when the MBS context no longer exists, at 350, the NG-RAN node can remove the N3 shared tunnel.

[0041] Figure 4 An example signaling diagram depicting the activation of an MBS session according to one embodiment is shown. For example, Figure 4The example illustrates the following procedure, which is used to signal activation when the MB-SMF receives an activation trigger from the MB-UPF at 402 (recovery of multicast service), and / or receives an activation trigger from the AF at 404. For example... Figure 4 As shown in the example, at any point in time when the MB-SMF wants to trigger the activation of an MBS session, the MB-SMF can retrieve a list of the (multiple) NG-RAN nodes involved in that MBS session from the storage at 210. Then, at 415, the MB-SMF can send an activation message.

[0042] For example, in one embodiment, the MB-SMF may send an activation message to each involved NG-RAN node via an associated AMF stored at 210 locations. In this embodiment, the activation message may include the ID(s) of the NG-RAN node(s) involved in the MBS session so that the AMF routes the activation message to the correct NG-RAN node.

[0043] In another embodiment, the MB-SMF can send activation messages to the associated AMF(s) stored at location 210. According to this embodiment, the activation message may include a list of NG-RAN node IDs involved in the MBS session associated with the AMF at location 210. The AMF may replicate the activation message toward each involved NG-RAN node, and / or construct and send an individual activation message for each NG-RAN node, the activation message containing the target NG-RAN node ID.

[0044] According to another embodiment, the MB-SMF can send an activation message to an AMF for each of the 210 stored regions. In this embodiment, the activation message may include a list of (multiple) NG-RAN node IDs involved in the MBS session for that region. The AMF may replicate the activation message toward each involved NG-RAN node and / or construct an individual activation message for each NG-RAN node, which contains the target NG-RAN node ID. In other embodiments, the MB-SMF can send the activation message to any AMF in a stored region where the list of (multiple) target NG-RAN node IDs belongs to that stored region.

[0045] In some embodiments, upon receiving an activation message for an MBS session, at 420, the NG-RAN node can avoid transitioning a UE with an RRC connection involved in the MBS session or a UE with RRC inactivity to an RRC idle state.

[0046] Figure 5AAn example flowchart of a method for deactivating and / or activating an MBS session according to one embodiment is shown. In some example embodiments, Figure 5A The flowchart can be executed by network entities or network nodes in a communication system (such as LTE or 5G NR). In some example embodiments, the execution... Figure 5A The network entities in the method may include, or be included in, base stations, access nodes, node Bs, eNBs, gNBs, NG-RAN nodes, etc. In one example embodiment, Figure 5A The method can be executed by NG-RAN nodes, such as Figures 1-4 The example diagram depicts an NG-RAN node.

[0047] like Figure 5A As shown in the example, the method may include: at 500, sending an MBS session establishment message, the MBS session establishment message including at least one of the following: an identifier of the network node (e.g., an NG-RAN node) that sent the MBS session establishment message, and an identifier of the management entity (e.g., an AMF) through which the MBS session establishment message was sent. In one embodiment, the method may further include: at 505, receiving, for example, a message for deactivating the MBS session from the MB-SMF via the management entity (e.g., the AMF). According to some embodiments, in response to receiving the message for deactivating the MBS session, the method may include: at 510, transitioning the context of the MBS session to a deactivated state.

[0048] In some embodiments, when the MBS context is in a deactivated state, the method may include: maintaining UEMBS context information in the user equipment (UE) contexts of one or more user equipments (UEs) still in a Radio Resource Control (RRC) connected state; maintaining UE MBS context information in the user equipment (UE) contexts of one or more user equipments (UEs) still in a Radio Resource Control (RRC) inactive state; and removing user equipment (UE) contexts including UE MBS contexts of one or more user equipments (UEs) that the network node decides to transition to a Radio Resource Control (RRC) idle state. Furthermore, in one embodiment, the method may include: maintaining the N3 shared tunnel when at least one user equipment (UE) in the network node is in a Radio Resource Control (RRC) connected state or an RRC inactive state. Additionally, in some embodiments, the method may include: maintaining the MBS context in the NG-RAN node when at least one user equipment (UE) in the network node is in a Radio Resource Control (RRC) connected state or an RRC inactive state.

[0049] According to certain embodiments, Figure 5AThe method may optionally include: at 515, when the MBS context is deactivated, preventing the transition of a user equipment (UE) involved in a radio resource control (RRC) connection or a user equipment (UE) with inactive radio resource control (RRC) in the MBS session to a radio resource control (RRC) idle state. In one embodiment, the method may include: at 520, when the MBS context is deactivated, receiving a message to activate the MBS session.

[0050] Figure 5B An example flowchart of a method for deactivating and / or activating an MBS session according to one embodiment is shown. In some example embodiments, Figure 5B The flowchart can be executed by network entities or network nodes in a communication system (such as LTE or 5GS). In some example embodiments, the execution... Figure 5B The network entities of the method may include, or be included in, management entities or functions (such as AMF, SMF, and / or AF). In one example embodiment, Figure 5B The methods can be executed by AMF, such as Figures 2-4 The example diagram depicts the AMF.

[0051] like Figure 5B As illustrated in the example, the method may include: at 530, receiving an MBS session establishment message from a network node (e.g., an NG-RAN node). The MBS session establishment message may include at least one of the following: an identifier of the network node and / or optionally, an identifier of a management entity (e.g., an AMF). In one embodiment, the method may include: at 533, forwarding the MBS session establishment message to a multicast session management entity (such as an MB-SMF). According to some embodiments, the method may further include: at 535, receiving a message for deactivating the MBS session from the multicast session management entity (e.g., an MB-SMF). The message for deactivating the MBS session may include at least the identifiers of one or more network nodes involved in the MBS session. In some embodiments, the method may include: at 540, sending a deactivation message for deactivating the MBS session to one or more network nodes involved in the MBS session.

[0052] According to some embodiments, sending a deactivation message 540 may include: copying the deactivation message toward one or more network nodes involved in the MBS session based on the identifier of the network node received from the multicast session management entity in the message used to deactivate the MBS session, or constructing and sending an individual message for each of the one or more network nodes involved in the MBS session.

[0053] In some embodiments, the method may optionally include: at 545, receiving a message from a multicast session management entity to activate an MBS session. The message to activate the MBS session may include at least identifiers of one or more network nodes involved in the MBS session. The method may then include: at 550, routing or sending an activation message to the one or more network nodes identified in the message received from the multicast session management entity to activate the MBS session. In one embodiment, sending the activation message may include: copying the activation message to one or more network nodes involved in the MBS session based on the identifiers of the network nodes received from the multicast session management entity in the message to activate the MBS session, or constructing and sending an individual message for each of the one or more network nodes involved in the MBS session.

[0054] Figure 5C An example flowchart of a method for deactivating and / or activating an MBS session according to one embodiment is shown. In some example embodiments, Figure 5C The flowchart can be executed by network entities or network nodes in a communication system (such as LTE or 5GS). In some example embodiments, the execution... Figure 5C The network entity of the method may include, or be included therein, a multicast session management entity or function (e.g., such as MB-SMF). In one example embodiment, Figure 5C The method can be executed by MB-SMF, such as Figures 2-4 The example diagram depicts the MB-SMF.

[0055] like Figure 5C As illustrated in the example, the method may include: at 560, receiving an MBS session establishment message from at least one management entity (e.g., AMF). The MBS session establishment message may include at least one of the following: an identifier of at least one network node (e.g., an NG-RAN node) requesting the establishment of an MBS session and an identifier of at least one management entity (e.g., AMF). In one embodiment, the method may include: at 565, storing one or more of the following: an identifier of at least one network node (e.g., an NG-RAN node), an identifier of at least one management entity (e.g., AMF), and / or an identifier of a region of at least one management entity (e.g., a region of the AMF). In some embodiments, storing 565 may include: constructing and storing at least one of the following: a list of identifiers of at least one network node for each management entity (e.g., the ID of an NG-RAN node for each AMF), or a list of identifiers of at least one network node for each region (e.g., the ID of a RAN node for each AMF region).

[0056] According to some embodiments, when a multicast broadcast management entity decides to trigger the deactivation of an MBS session, the method may include: at 570, sending a message to at least one management entity to deactivate the MBS session. In this embodiment, the message may include at least the identifier of at least one network node involved in the MBS session. In one embodiment, sending the message to deactivate the multicast broadcast service (MBS) session 570 may include: sending a deactivation message to at least one management entity, the deactivation message including a list of identifiers of at least one network node involved in the MBS session associated with at least one management entity. Alternatively or additionally, sending the message to deactivate the multicast broadcast service (MBS) session 570 may include: sending a deactivation message to a management entity for each stored area, the deactivation message including a list of identifiers of at least one network node involved in the MBS session for that area.

[0057] In some embodiments, when a multicast broadcast management entity decides to trigger the activation of a multicast broadcast service (MBS) session, the method may include: retrieving the identifier of at least one network node involved in the MBS session, and at 575, sending a message to activate the MBS session, the message possibly including at least the identifier of at least one network node involved in the MBS session. According to some embodiments, sending the message to activate the MBS session at 575 may include: sending an activation message to at least one management entity (e.g., AMF) including a list of identifiers of at least one network node involved in the MBS session associated with at least one management entity. Alternatively or additionally, sending the message to activate the MBS session at 575 may include: sending an activation message to a management entity (e.g., AMF) for each stored region, the activation message including a list of identifiers of at least one network node involved in the MBS session for that region.

[0058] Figure 6A An example of apparatus 10 according to an embodiment is shown. In one embodiment, apparatus 10 may be a node, host, or server in or serving such a communication network. For example, apparatus 10 may be a satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next-generation Node B (NG-NB or gNB), transmit-receive point (TRP), high-altitude platform station (HAPS), integrated access and backhaul (IAB) node, and / or WLAN access point associated with a radio access network (such as an LTE network, 5G, or NR). In one example embodiment, apparatus 10 may represent NG-RAN, such as Figures 1-4 The NG-RAN shown.

[0059] It should be understood that in some example embodiments, device 10 may include an edge cloud server as a distributed computing system, wherein the server and radio nodes may be separate devices communicating with each other via a radio path or via a wired connection, or they may reside in the same entity communicating via a wired connection. For example, in some example embodiments where device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides gNB functions. In such an architecture, the CU may be a logical node that includes gNB functions such as user data transmission, mobility control, radio access network sharing, location and / or session management, etc. The CU may control the operation of the DU(s) through a fronthaul interface. The DU may be a logical node that includes a subset of gNB functions, depending on the function splitting options. It should be noted that those skilled in the art will understand that device 10 may include Figure 6A Components or features not shown in the diagram.

[0060] like Figure 6A As shown in the example, device 10 may include processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general-purpose or special-purpose processor. In fact, for example, processor 12 may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and processor based on a multi-core processor architecture, or any other processing unit.

[0061] Although Figure 6A A single processor 12 is shown, but multiple processors may be utilized according to other example embodiments. For example, it should be understood that in some embodiments, device 10 may include two or more processors that can form a multiprocessor system capable of supporting multiple processing (e.g., in this case, processor 12 may represent multiple processors). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0062] The processor 12 can perform functions associated with the operation of the device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the device 10, including processes related to the management of communication resources.

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

[0064] In one embodiment, device 10 may further include or be coupled to an (internal or external) drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software that are executed by processor 12 and / or device 10.

[0065] In some embodiments, device 10 may further include or be coupled to one or more antennas 15 for transmitting and / or receiving signals and / or data to and from device 10. Device 10 may also include or be coupled to a transceiver 18 configured to transmit and / or receive information. Transceiver 18 may include, for example, multiple radio interfaces that may be coupled to antenna(s) 15, or may include any other suitable transceiver components. In some embodiments, the radio interface may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, RFID, UWB, MulteFire, etc. According to example embodiments, the radio interface may include components such as filters, converters (e.g., digital-to-analog converters), mappers, Fast Fourier Transform (FFT) modules, for example, to generate symbols or signals for transmission via one or more downlinks and to receive symbols (e.g., via an uplink).

[0066] Therefore, transceiver 18 can be configured to modulate information onto a carrier waveform for transmission by antenna(s)15 and demodulate information received via antenna(s)15 for further processing by other elements of device 10. In other example embodiments, transceiver 18 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some embodiments, device 10 may include input devices and / or output devices (I / O devices), or input / output components.

[0067] In one embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. These modules may include, for example, an operating system that provides operating system functionality to device 10. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. Components of device 10 may be implemented in hardware or as any suitable combination of hardware and software.

[0068] According to some embodiments, the processor 12 and memory 14 may be included in or form part of a processing circuitry or control circuitry. Furthermore, in some embodiments, the transceiver 18 may be included in or form part of a transceiver circuitry.

[0069] As used herein, the term "circuit system" can refer to a hardware circuit implementation only (e.g., analog and / or digital circuit systems), a combination of hardware circuits and software, a combination of analog and / or digital hardware circuits with software / firmware, any part of a hardware processor(s) (including digital signal processors) having software working together to cause a device (e.g., device 10) to perform various functions, and / or a hardware circuit and / or processor(s) or a portion thereof that operates using software but may be absent when operation is not required. As another example, as used herein, the term "circuit system" can also encompass a hardware circuit or processor (or multiple processors) only, or a portion of a hardware circuit or processor, and its accompanying software and / or firmware implementation. The term "circuit system" can also encompass baseband integrated circuits, for example, in servers, cellular network nodes or devices, or other computing or networking devices.

[0070] As described above, in some embodiments, device 10 may be a network node or RAN node, such as a base station, access point, node B, eNB, gNB, TRP, HAPS, IAB node, WLAN access point, etc. In one example embodiment, device 10 may be a network node in NG-RAN. For example, in some embodiments, device 10 may be configured to perform one or more of the processes shown in any flowchart or signaling diagram described herein, such as Figure 5AThe process is illustrated. In some embodiments, as discussed herein, apparatus 10 may be configured to perform processes, for example, relating to deactivating and / or activating MBS sessions.

[0071] Figure 6B An example of apparatus 20 according to another embodiment is shown. In one embodiment, apparatus 20 may be a node or element in or associated with a communication network, such as a satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next-generation Node B (NG-NB or gNB), and / or WLAN access point associated with a radio access network (such as an LTE network, 5G, or NR). According to one embodiment, apparatus 20 may be a management entity or function, or may be included therein, such as an AMF, SMF, and / or AF, such as Figures 2-4 Those shown in the example diagrams.

[0072] It should be understood that in some example embodiments, device 20 may include an edge cloud server as a distributed computing system, wherein the server and radio nodes may be separate devices communicating with each other via a radio path or via a wired connection, or they may reside in the same entity communicating via a wired connection. For example, in some example embodiments where device 20 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that partitions gNB functions. In such an architecture, the CU may be a logical node that includes gNB functions such as user data transmission, mobility control, radio access network sharing, location and / or session management, etc. The CU may control the operation of the DU(s) through a fronthaul interface. The DU may be a logical node that includes a subset of gNB functions, depending on the function partitioning options. It should be noted that those skilled in the art will understand that device 20 may include Figure 6B Components or features not shown in the diagram.

[0073] In some example embodiments, device 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some embodiments, device 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that those skilled in the art will understand that device 20 may include... Figure 6B Components or features not shown in the diagram.

[0074] like Figure 6BAs shown in the example, device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. In practice, processor 22 may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and processor based on a multi-core processor architecture. Although Figure 6B A single processor 22 is shown, but in other embodiments, multiple processors may be utilized. For example, it should be understood that in some embodiments, device 20 may include two or more processors that can form a multiprocessor system capable of supporting multiple processing (e.g., in this case, processor 22 may represent multiple processors). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0075] The processor 22 can perform functions associated with the operation of the device 20, including, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the device 20, including processes related to the management of communication resources.

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

[0077] In one embodiment, device 20 may further include or be coupled to an (internal or external) drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software that are executed by processor 22 and / or device 20.

[0078] In some embodiments, device 20 may further include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting from device 20 via an uplink. Device 20 may also include a transceiver 28 configured to transmit and receive information. Transceiver 28 may also include a radio interface (e.g., a modem) coupled to antenna 25. The radio interface may correspond to one or more of various radio access technologies, including GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0079] For example, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna(s)25 and demodulate information received via antenna(s)25 for further processing by other elements of device 20. In other embodiments, transceiver 28 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some embodiments, device 20 may include input and / or output devices (I / O devices). In some embodiments, device 20 may also include a user interface, such as a graphical user interface or a touchscreen.

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

[0081] According to some embodiments, processor 22 and memory 24 may be included in, or may form part of, a processing circuit system / component or a control circuit system / component. Furthermore, in some embodiments, transceiver 28 may be included in, or may form part of, a transceiver circuit system or transceiver component.

[0082] As described above, according to some embodiments, device 20 may be a management entity or function, such as AMF, SMF, and / or AF. According to some embodiments, device 20 may be controlled by memory 24 and processor 22 to perform functions associated with the example embodiments described herein. For example, in some embodiments, device 20 may be configured to perform one or more processes shown in any flowchart or signaling diagram described herein. In one embodiment, device 20 may be controlled by memory 24 and processor 22 to perform… Figure 5B The method is illustrated in the example. Therefore, according to one embodiment, the device 20 can be configured to perform processes, for example, related to MBS session activation and / or deactivation.

[0083] Figure 6C An example of apparatus 30 according to another exemplary embodiment is shown. In one exemplary embodiment, apparatus 30 may be a node or element in or associated with a communications network, such as a satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next-generation Node B (NG-NB or gNB), and / or WLAN access point associated with a radio access network (such as an LTE network, 5G, or NR). According to one embodiment, apparatus 30 may be a multicast management entity or function, or may be included therein, such as an MB-SMF.

[0084] In some example embodiments, device 30 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some example embodiments, device 30 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and / or any other radio access technology. It should be noted that those skilled in the art will understand that device 30 may include... Figure 6C Components or features not shown in the diagram.

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

[0086] The processor 32 can perform functions associated with the operation of the device 30, including, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the device 30, including processes related to the management of communication resources.

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

[0088] In one example embodiment, device 30 may also include or be coupled to an (internal or external) drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software that can be executed by processor 32 and / or device 30.

[0089] In some example embodiments, device 30 may further include or be coupled to one or more antennas 35 for receiving downlink signals and for transmitting from device 30 via an uplink. Device 30 may also include a transceiver 38 configured to transmit and receive information. Transceiver 38 may also include a radio interface (e.g., a modem) coupled to antenna 35. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0090] For example, transceiver 38 may be configured to modulate information onto a carrier waveform for transmission by antenna(s)35 and demodulate information received via antenna(s)35 for further processing by other elements of device 30. In other example embodiments, transceiver 38 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some example embodiments, device 30 may include input and / or output devices (I / O devices). In some example embodiments, device 30 may also include a user interface, such as a graphical user interface or a touchscreen.

[0091] In one example embodiment, memory 34 stores software modules that provide functionality when executed by processor 32. These modules may include, for example, an operating system that provides operating system functionality to device 30. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 30. Components of device 30 may be implemented in hardware or as any suitable combination of hardware and software. According to the example embodiment, device 30 may optionally be configured to communicate with device 10 via wireless or wired communication link 71 and / or with device 20 via wireless or wired communication link 72, according to any radio access technology such as NR.

[0092] According to some example embodiments, the processor 32 and the memory 34 may be included in a processing circuitry or a control circuitry, or may be part of it. Furthermore, in some example embodiments, the transceiver 38 may be included in a transceiver circuitry, or may be part of it.

[0093] As described above, according to some example embodiments, device 30 may be a multicast management entity or function, such as MB-SMF. According to some example embodiments, device 30 may be controlled by memory 34 and processor 32 to perform functions associated with the example embodiments described herein. For example, in some example embodiments, device 30 may be configured to perform one or more processes shown in any diagram or signaling flowchart described herein. In one embodiment, device 30 may be controlled by memory 34 and processor 32 to perform functions according to… Figure 5C Examples of methods. According to certain example embodiments, for example, device 30 may be configured to perform processes related to MBS session activation and / or deactivation.

[0094] In some embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20 and / or apparatus 30) may include components for performing the methods or any variations discussed herein, such as references Figure 2 - One or more methods are described in Figure 5. Examples of this component may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the execution of these operations.

[0095] In view of the above, certain example embodiments provide several technical improvements, enhancements, and / or advantages compared to existing processes, and constitute at least an improvement in the field of radio network control and management technology. For example, as described above, in some embodiments, deactivation and / or activation utilize the MB-SMF storage of the NG-RAN node ID. Therefore, information storage in the AMF is unnecessary, as the AMF only acts as a routing proxy when delivering deactivation and / or activation messages. Furthermore, according to some embodiments, deactivation and / or activation do not involve the (UE's) SMF, such as... Figures 2-4 As illustrated in the examples. Furthermore, in some embodiments, the MBS context, the MBS portion of the UE context, and the N3 shared tunnel are not all removed, but only for UEs for which the NG-RAN node will decide to transition them to RRC idle. Therefore, the use of certain example embodiments improves the functionality of the communication network and its nodes (such as base stations, eNBs, gNBs, and / or IoT devices, UEs, or mobile stations).

[0096] In some example embodiments, the functionality of any methods, processes, signaling diagrams, algorithms, or flowcharts described herein may be implemented by software and / or computer program code or code portions stored in memory or other computer-readable or tangible media and executable by a processor.

[0097] In some example embodiments, an apparatus may include, or be associated with, at least one software application, module, unit, or entity configured to perform arithmetic operations, or to be a program or program portion (including added or updated software routines) executed by at least one operating processor or controller. The program (also referred to as a program product or computer program, including software routines, applets, and macros) may be stored in any device-readable data storage medium and may include program instructions for performing a specific task. The computer program product may include one or more computer-executable components configured to perform some example embodiments when the program is run. The one or more computer-executable components may be at least one piece of software code or code. Modifications and configurations required to implement the functionality of the example embodiments may be executed as routines, which may be implemented as added or updated software routines. In one example, the software routines may be downloaded to the apparatus.

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

[0099] In other example embodiments, the functionality of the example embodiments may be performed by hardware or circuitry systems included in the device, such as by using an application-specific integrated circuit (ASIC), a programmable gate array (PGA), a field-programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality of the example embodiments may be implemented as a signal, such as an intangible means that can be carried by an electromagnetic signal downloaded from the Internet or other networks.

[0100] According to example embodiments, devices such as nodes, equipment, or corresponding components may be configured as circuit systems, computers, or microprocessors, such as monolithic computer elements, or configured as chipsets that may include at least a memory for providing storage capacity for arithmetic operations(s) and / or an operation processor for performing arithmetic operations(s).

[0101] The exemplary embodiments described herein can be applied to both singular and plural implementations, regardless of whether a singular or plural language is used in conjunction with the description of certain embodiments. For example, an embodiment describing the operation of a single network node can also be applied to embodiments that include multiple instances of network nodes, and vice versa.

[0102] It will be readily understood by those skilled in the art that the exemplary embodiments discussed above can be practiced with a different sequence of processes and / or with different configurations of hardware elements compared to those disclosed. Therefore, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be readily apparent while remaining within the spirit and scope of the exemplary embodiments.

Claims

1. A method for communication, comprising: A multicast broadcast service (MBS) session establishment message is sent by an access network node, including at least one of the identifier of the access network node and the identifier of a first management entity, the multicast broadcast service (MBS) session establishment message being sent through the first management entity; Receive a message to deactivate the Multicast Broadcast Service (MBS) session; as well as In response to receiving the message for deactivating a Multicast Broadcast Service (MBS) session, the context of the Multicast Broadcast Service (MBS) session is changed to a deactivated state; Wherein, when the context of the multicast broadcast service (MBS) session is in the deactivated state, the method includes at least one of the following: Information about the context of the multicast broadcast service (MBS) session in the context of one or more user equipments (UEs) that are still in the radio resource control (RRC) connection state; Information about the context of the multicast broadcast service (MBS) session in the context of one or more user equipment (UEs) that are still in a radio resource control (RRC) inactive state; When at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state, the multicast broadcast service (MBS) session context information in the access network node is maintained. or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

2. The method according to claim 1, further comprising: Receive a message to activate the Multicast Broadcast Service (MBS) session; as well as Avoid transitioning user equipment (UE) with radio resource control (RRC) connections involved in the multicast broadcast service (MBS) session or user equipment (UE) with inactive radio resource control (RRC) to a radio resource control (RRC) idle state.

3. A communication apparatus for accessing a network node, comprising: At least one processor; as well as At least one memory, including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: A multicast broadcast service (MBS) session establishment message is sent, which includes at least one of the identifier of the device and the identifier of the first management entity, the multicast broadcast service (MBS) session establishment message being sent through the first management entity; Receive a message to deactivate the Multicast Broadcast Service (MBS) session; as well as In response to receiving the message for deactivating a Multicast Broadcast Service (MBS) session, the context of the Multicast Broadcast Service (MBS) session is changed to a deactivated state; Wherein, when the context of the Multicast Broadcast Service (MBS) session is in the deactivated state, the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to at least: Information about the context of the multicast broadcast service (MBS) session in the context of one or more user equipments (UEs) that are still in the radio resource control (RRC) connection state; Information about the context of the multicast broadcast service (MBS) session in the context of one or more user equipment (UEs) that are still in a radio resource control (RRC) inactive state; When at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state, the multicast broadcast service (MBS) session context information in the access network node is maintained. or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

4. A method for communication, comprising: At the first management entity, a message for deactivating a multicast broadcast service (MBS) session is received from the multicast broadcast session management entity, the message including at least the identifiers of one or more access network nodes involved in the multicast broadcast service (MBS) session; as well as Send a deactivation message to the one or more access network nodes indicated in the received message to deactivate the multicast broadcast service (MBS) session, so as to change the context of the multicast broadcast service (MBS) session to a deactivated state. Specifically, when the context of the Multicast Broadcast Service (MBS) session is in the deactivated state: The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments (UEs) that are still in the Radio Resource Control (RRC) connection state; The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments that are still in a radio resource control (RRC) inactive state; When at least one User Equipment (UE) in the access network node is in a Radio Resource Control (RRC) connected state or a Radio Resource Control (RRC) inactive state, the Multicast Broadcast Service (MBS) session context information is maintained in the access network node; or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

5. The method of claim 4, further comprising, before receiving the message for deactivation: At the first management entity, a multicast broadcast service (MBS) session establishment message is received from the access network node, the multicast broadcast service (MBS) session establishment message including at least one of the identifier of the access network node and the identifier of the first management entity; The first management entity forwards the multicast broadcast service (MBS) session establishment message to the multicast broadcast session management entity.

6. The method of claim 4, wherein the sending of the deactivation message comprises at least one of the following: The deactivation message is copied toward the one or more access network nodes indicated in the message received from the multicast session management entity; or For each of the one or more access network nodes indicated in the message received from the multicast broadcast session management entity, an individual message is constructed and sent to deactivate the multicast broadcast service (MBS) session.

7. The method according to claim 6, further comprising: Receive a message from the multicast broadcast session management entity to activate the multicast broadcast service (MBS) session, the message including at least the identifiers of one or more access network nodes involved in the multicast broadcast service (MBS) session; as well as An activation message is sent to one or more access network nodes identified in the message received from the multicast broadcast session management entity to activate the multicast broadcast service (MBS) session.

8. The method of claim 7, wherein sending the activation message comprises: The activation message is copied toward the one or more access network nodes identified in the activation message received from the multicast session management entity; or For each of the one or more access network nodes identified in the activation message received from the multicast broadcast session management entity, an individual message is constructed and sent to activate the multicast broadcast service (MBS) session.

9. A communication apparatus for a first management entity, comprising: At least one processor; as well as At least one memory, including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: Receive a message from the multicast broadcast session management entity to deactivate a multicast broadcast service (MBS) session, the message including at least the identifiers of one or more access network nodes involved in the multicast broadcast service (MBS) session; as well as Send a deactivation message to the one or more access network nodes indicated in the received message to deactivate the multicast broadcast service (MBS) session, so as to change the context of the multicast broadcast service (MBS) session to a deactivated state. Specifically, when the context of the Multicast Broadcast Service (MBS) session is in the deactivated state: The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments (UEs) that are still in the Radio Resource Control (RRC) connection state; The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments that are still in a radio resource control (RRC) inactive state; When at least one User Equipment (UE) in the access network node is in a Radio Resource Control (RRC) connected state or a Radio Resource Control (RRC) inactive state, the Multicast Broadcast Service (MBS) session context information is maintained in the access network node; or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

10. A method for communication, comprising: At the multicast broadcast session management entity, a multicast broadcast service (MBS) session establishment message is received from at least one first management entity. The multicast broadcast service (MBS) session establishment message includes at least one of the following: an identifier of at least one access network node requesting the establishment of the multicast broadcast service (MBS) session, and an identifier of the at least one first management entity; and At the multicast session management entity, at least one of the following is stored: the identifier of the at least one access network node, the identifier of the at least one first management entity, or the identifier of the region of the at least one first management entity; Wherein, when the multicast broadcast session management entity decides to trigger the deactivation of the multicast broadcast service (MBS) session, the method includes: Send a message to a first management entity to deactivate the multicast broadcast service (MBS) session for changing the context of the multicast broadcast service (MBS) session to a deactivated state, wherein the message includes at least an identifier of at least one access network node involved in the multicast broadcast service (MBS) session. Specifically, when the context of the Multicast Broadcast Service (MBS) session is in the deactivated state: The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments (UEs) that are still in the Radio Resource Control (RRC) connection state; The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments that are still in a radio resource control (RRC) inactive state; When at least one User Equipment (UE) in the access network node is in a Radio Resource Control (RRC) connected state or a Radio Resource Control (RRC) inactive state, the Multicast Broadcast Service (MBS) session context information is maintained in the access network node; or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

11. The method of claim 10, wherein the storage comprises constructing and storing at least one of: a list of identifiers for the at least one access network node for each first management entity, or a list of identifiers for the at least one access network node for each region.

12. The method of claim 10, wherein the first management entity comprises: The first management entity having the stored identifier, or the first management entity associated with the region having the stored identifier.

13. The method of claim 10, wherein the transmission of the message used to deactivate the multicast broadcast service (MBS) session comprises at least one of the following: Send a deactivation message to the at least one first management entity, wherein the deactivation message includes: A list of identifiers of at least one access network node involved in the multicast broadcast service (MBS) session associated with the at least one first management entity; or For each stored region, a deactivation message is sent to a first management entity, wherein the deactivation message includes a list of identifiers of at least one access network node involved in the multicast broadcast service (MBS) session for the region.

14. The method of claim 10, wherein, When the multicast broadcast session management entity decides to trigger the activation of the multicast broadcast service (MBS) session, the method includes: Retrieve the identifier of at least one access network node involved in the Multicast Broadcast Service (MBS) session; and A message is sent to a first management entity to activate the multicast broadcast service (MBS) session, wherein the message includes at least an identifier of at least one access network node involved in the multicast broadcast service (MBS) session.

15. The method of claim 14, wherein the first management entity comprises: The first management entity having the stored identifier, or the first management entity associated with the region having the stored identifier.

16. The method of claim 14, wherein sending the message for activating the multicast broadcast service (MBS) session comprises: Send an activation message to the at least one first management entity, wherein the activation message includes: a list of identifiers of at least one access network node involved in the multicast broadcast service (MBS) session associated with the at least one first management entity; or For each stored region, an activation message is sent to a first management entity, wherein the activation message includes a list of identifiers of at least one access network node involved in the multicast broadcast service (MBS) session for the region.

17. An apparatus for communication, comprising: At least one processor; as well as At least one memory, including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: Receive a multicast broadcast service (MBS) session establishment message from at least one first management entity, the multicast broadcast service (MBS) session establishment message including at least one of the following: an identifier of at least one access network node requesting the establishment of the multicast broadcast service (MBS) session, and an identifier of the at least one first management entity; as well as Store at least one of the following: the identifier of the at least one access network node, the identifier of the at least one first management entity, or the identifier of the region of the at least one first management entity; Wherein, when the device decides to trigger the deactivation of the Multicast Broadcast Service (MBS) session, the at least one memory and the computer program code are configured, together with the at least one processor, such that the device at least: Send a message to a first management entity to deactivate the multicast broadcast service (MBS) session for changing the context of the multicast broadcast service (MBS) session to a deactivated state, wherein the message includes at least an identifier of at least one access network node involved in the multicast broadcast service (MBS) session. Specifically, when the context of the Multicast Broadcast Service (MBS) session is in the deactivated state: The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments (UEs) that are still in the Radio Resource Control (RRC) connection state; The context information of the Multicast Broadcast Service (MBS) session is maintained in the user equipment (UE) context of one or more user equipments that are still in a radio resource control (RRC) inactive state; When at least one User Equipment (UE) in the access network node is in a Radio Resource Control (RRC) connected state or a Radio Resource Control (RRC) inactive state, the Multicast Broadcast Service (MBS) session context information is maintained in the access network node; or The N3 shared tunnel is maintained when at least one user equipment (UE) in the access network node is in a radio resource control (RRC) connected state or a radio resource control (RRC) inactive state.

18. A non-transitory computer-readable medium comprising program instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to claim 1.

19. A non-transitory computer-readable medium comprising program instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to claim 4.

20. A non-transitory computer-readable medium comprising program instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to claim 10.

Images