Broadcast service recovery for multicast / broadcast services upon radio access node failure or restart

Abstract

Embodiments of the present disclosure relate to broadcast service recovery for multicast / broadcast services upon radio access node failure or restart. Systems, methods, apparatuses, and computer program products for broadcast service recovery for multicast / broadcast services upon radio access node failure or restart are provided. For example, a method can include storing last multicast / broadcast service session information corresponding to a multicast / broadcast service session received from a multicast / broadcast session management function. The method can also include detecting that a radio access node associated with the multicast / broadcast service session has restarted or is unreachable. The method can also include taking a further action to adjust delivery of the multicast / broadcast service session based on the detection.

Description

Technical Field

[0001] Some example embodiments may typically relate to communications including mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or 5G radio access technologies or New Radio (NR) or Beyond 5G, or other communication systems. For example, some example embodiments may typically relate to systems and / or methods for providing broadcast service recovery for multicast / broadcast services in the event of a radio access node failure or restart. Background Technology

[0002] Examples of mobile or wireless telecommunications systems can include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), UTRAN evolved from LTE (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-APro, and / or fifth-generation (5G) radio access technologies or new radio (NR) access technologies. 5G radio systems refer to next-generation (NG) radio systems and network architectures. 5G systems are primarily built on 5G New Radio (NR), but 5G (or NG) networks can also be built on E-UTRA radio. NR is estimated to provide bit rates 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) and massive machine-type communications (mMTC). NR is expected to provide ultra-wideband and ultra-robust, low-latency connectivity and massive networks to support the Internet of Things (IoT). With the increasing prevalence of IoT and machine-to-machine (M2M) communication, the demand for networks that meet the requirements of low power consumption, low data rates, and long battery life will continue to grow. Next-Generation Radio Access Network (NG-RAN) represents the RAN for 5G, which can provide NR and LTE (and LTE-Advanced) radio access. It's important to 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 named Next-Generation NB (gNB) when established on NR radio, and Next-Generation eNB (NG-eNB) when established on E-UTRA radio. Summary of the Invention

[0003] One embodiment may relate to an apparatus. The apparatus may include at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code may be configured, together with the at least one processor, to cause the apparatus to at least perform the following actions: storing information about the last multicast / broadcast service session received from a multicast / broadcast session management function corresponding to a multicast / broadcast service session. The at least one memory and the computer program code may also be configured, together with the at least one processor, to cause the apparatus to at least perform the following actions: detecting that a radio access node associated with the multicast / broadcast service session has been restarted or is unreachable. The at least one memory and the computer program code may also be configured, together with the at least one processor, to cause the apparatus to at least perform the following actions: based on this detection, taking further action to adjust the delivery of the multicast / broadcast service session.

[0004] One embodiment may relate to an apparatus. The apparatus may include at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code may be configured, together with the at least one processor, to cause the apparatus to at least perform a request to receive data transmissions for a multicast / broadcast session to a radio access node with a fully qualified tunneling endpoint identifier, the request including the radio access node's identifier. The at least one memory and the computer program code may also be configured, together with the at least one processor, to cause the apparatus to at least perform a request to send a request to a multicast / broadcast user plane function, the request including the fully qualified tunneling endpoint identifier of the radio access node received from the radio access node, and to request the multicast / broadcast user plane function to commence. The at least one memory and the computer program code may also be configured, together with the at least one processor, to cause the apparatus to at least perform a request to store the radio access node's identifier and context to control the transmission of the fully qualified tunneling endpoint identifier to the radio access node. The at least one memory and the computer program code may further be configured, together with the at least one processor, to cause the apparatus to at least perform a request to receive a request to redirect data transmissions for a multicast / broadcast session to a new fully qualified tunneling endpoint identifier of the radio access node, or a request to terminate data transmissions for a multicast / broadcast session to the radio access node. At least one memory and computer program code may also be configured, together with at least one processor, to cause the apparatus to at least perform: when a request is made to redirect data transmission, sending a request to a multicast / broadcast user plane function, the request including a first complete tunnel endpoint identifier of a radio access node corresponding to a complete tunnel endpoint identifier received from a radio access node, and requesting the multicast / broadcast user plane function to begin sending multicast / broadcast session data to the first complete tunnel endpoint identifier of the radio access node, and the request including a second complete tunnel endpoint identifier of the radio access node, and requesting the multicast / broadcast user plane function to stop sending multicast / broadcast session data to the second complete tunnel endpoint identifier of the radio access node, the second complete tunnel endpoint identifier being set to the complete tunnel endpoint identifier previously used for the multicast / broadcast session. At least one memory and computer program code may also be configured, together with at least one processor, to cause the apparatus to at least perform: sending a request to the multicast / broadcast user plane function when a request is made to terminate data transmission, the request including a complete tunnel endpoint identifier of a radio access node that is set as a complete tunnel endpoint identifier previously used for a multicast / broadcast session, and requesting the multicast / broadcast user plane function to stop sending multicast / broadcast session data to the complete tunnel endpoint identifier of the radio access node.

[0005] One embodiment may relate to a method. The method may include storing information about the last multicast / broadcast service session corresponding to a multicast / broadcast service session, received from a multicast / broadcast session management function. The method may also include detecting that the radio access node associated with the multicast / broadcast service session has been restarted or is unreachable. The method may further include taking additional actions based on this detection to adjust the delivery of the multicast / broadcast service session.

[0006] One embodiment may relate to a method. The method may include receiving a request for a data transfer of a complete tunnel endpoint identifier for a multicast / broadcast session to a radio access node, the request including the radio access node's identifier. The method may also include sending a request to a multicast / broadcast user plane function, the request including the radio access node's complete tunnel endpoint identifier received from the radio access node, and requesting the multicast / broadcast user plane function to commence. The method may further include storing the radio access node's identifier and context to control the transmission of the complete tunnel endpoint identifier to the radio access node. The method may additionally include receiving a request to redirect data transfer of the multicast / broadcast session to a new complete tunnel endpoint identifier for the radio access node, or terminating data transfer of the multicast / broadcast session to the radio access node. The method may further include sending a request to the multicast / broadcast user plane function when a request is made to redirect data transmission. The request includes a first complete tunnel endpoint identifier of the radio access node corresponding to a complete tunnel endpoint identifier received from the radio access node, and requests the multicast / broadcast user plane function to begin transmitting multicast / broadcast session data to the first complete tunnel endpoint identifier of the radio access node. The request also includes a second complete tunnel endpoint identifier of the radio access node, and requests the multicast / broadcast user plane function to stop transmitting multicast / broadcast session data to the second complete tunnel endpoint identifier of the radio access node, which is set to the complete tunnel endpoint identifier previously used for the multicast / broadcast session. The method may also include sending a request to the multicast / broadcast user plane function when a request is made to terminate data transmission. The request includes a complete tunnel endpoint identifier of the radio access node set to the complete tunnel endpoint identifier previously used for the multicast / broadcast session, and requests the multicast / broadcast user plane function to stop transmitting multicast / broadcast session data to the complete tunnel endpoint identifier of the radio access node.

[0007] One embodiment may be directed to an apparatus. The apparatus may include components for storing information about the last multicast / broadcast service session corresponding to a multicast / broadcast service session, received from a multicast / broadcast session management function. The apparatus may also include components for detecting that a radio access node associated with the multicast / broadcast service session has been restarted or is unreachable. The apparatus may further include components for taking additional action based on the detection to adjust the delivery of the multicast / broadcast service session.

[0008] An apparatus may be provided for receiving a request for data transmission of a complete tunnel endpoint identifier for a multicast / broadcast session to a radio access node, the request including the identifier of the radio access node. The apparatus may further include components for sending a request to a multicast / broadcast user plane function, the request including the complete tunnel endpoint identifier of the radio access node received from the radio access node, and requesting the multicast / broadcast user plane function to commence. The apparatus may also include components for storing the identifier of the radio access node and context to control the transmission of the complete tunnel endpoint identifier to the radio access node. The apparatus may additionally include components for receiving a request to redirect data transmission of a multicast / broadcast session to a new complete tunnel endpoint identifier of the radio access node, or a request to terminate data transmission of a multicast / broadcast session to the radio access node. The apparatus may further include components for sending a request to a multicast / broadcast user plane function when a request is made for redirecting data transmission. The request includes a first complete tunnel endpoint identifier of the radio access node corresponding to a complete tunnel endpoint identifier received from the radio access node, and requests the multicast / broadcast user plane function to begin transmitting multicast / broadcast session data to the first complete tunnel endpoint identifier of the radio access node. The request also includes a second complete tunnel endpoint identifier of the radio access node, and requests the multicast / broadcast user plane function to stop transmitting multicast / broadcast session data to the second complete tunnel endpoint identifier of the radio access node, which is set to a previously used complete tunnel endpoint identifier for the multicast / broadcast session. The apparatus may also include components for sending a request to the multicast / broadcast user plane function when a request is made for terminating data transmission. The request includes a complete tunnel endpoint identifier of the radio access node set to a previously used complete tunnel endpoint identifier for the multicast / broadcast session, and requests the multicast / broadcast user plane function to stop transmitting multicast / broadcast session data to the complete tunnel endpoint identifier of the radio access node. Attached Figure Description

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

[0010] Figure 1 The system architecture is shown;

[0011] Figure 2 A method according to certain embodiments is shown;

[0012] Figure 3 A signal flow diagram is shown for resuming a broadcast multicast / broadcast service (MBS) session when a radio access node fails and restarts, according to certain embodiments.

[0013] Figure 4 Methods according to certain embodiments are shown; and

[0014] Figure 5 An example block diagram of a system according to an embodiment is shown. Detailed Implementation

[0015] 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 providing broadcast service restoration for multicast / broadcast services (MBS) in the event of a radio access node failure or restart is not intended to limit the scope of any particular embodiment, but rather represents selected example embodiments.

[0016] The features, structures, or characteristics of the exemplary embodiments described throughout this specification can be combined in any suitable manner in one or more exemplary embodiments. For example, the use of phrases such as "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 can be included in at least one embodiment. Therefore, the appearance of phrases such as "some embodiments," "some examples," "other examples," or other similar language throughout this specification does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments.

[0017] Some embodiments may have various aspects and features. These aspects and features may be applied individually or in any desired combination with each other. Other features, processes, and elements may also be applied in combination with some or all of the aspects and features disclosed herein.

[0018] Additionally, if necessary, the different functions or processes discussed below may be executed in different orders and / or concurrently with each other. Furthermore, if necessary, one or more of the described functions or processes may be optional or may be combined. Therefore, the following description should be regarded as an illustration of the principles and teachings of certain example embodiments, and not as a limitation thereof.

[0019] Release 17 (Rel-17) of the 3rd Generation Partnership Project (3GPP) describes architectural enhancements for fifth-generation (5G) multicast and broadcast services. For example, 3GPP Technical Specification (TS) 23.247 describes a system architecture. Figure 1 An example of the system architecture is shown. Figure 1 Based on 3GPP TS 23.247 Figure 5 .1-1, “5G system architecture for multicast and broadcast services”.

[0020] like Figure 1 As shown, N4mb and N4 can respectively serve as reference point services used between Session Management Function (SMF) and User Plane Function (UPF), and between Multicast / Broadcast (MB) SMF (MB) and MB-UPF. The Packet Forwarding Control Protocol (PFCP) can be a protocol used on N4mb and N4. PFCP is specified, for example, in 3GPP TS 29.244.

[0021] MB service (MBS) sessions can correspond to broadcast MBS sessions, in which case the SMF and UPF may not be involved in the delivery of services. MBS sessions can alternatively correspond to multicast MBS sessions, in which case the SMF and UPF may participate in the delivery of MBS data, as explained in more detail in 3GPP TS 23.247.

[0022] For both broadcast and multicast MBS sessions, unicast or multicast transmission can be used on the N3mb, applicable to both broadcast and multicast MBS sessions, and on the N19mb, applicable only to multicast MBS sessions. Unicast transmission can send packets in a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (GTP-U) tunnel, as described in 3GPP TS 29.281. Packets can be sent to a Downlink (DL) Complete Tunnel Endpoint Identifier (F-TEID), which may include an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID). Multicast transmission can send packets using a Low Layer Source Specific Multicast (LLSSM) address and a Public GTP TEID (C-TEID). The LLSSM address may include a multicast address, which can be used as the destination address in the transmitted packets; the LLSSM address may also include a source IP address, which may correspond to the IP address of the MB-UPF. 3GPP TS 29.281 includes further discussion on IP multicast distribution of user plane data for MBMS and MBS.

[0023] MBS service recovery refers to the end-to-end process of restoring an MBS session when a failure (with or without a restart) affects any entity involved in the delivery of the MBS session. Potentially affected entities may include, for example, the MB-SMF, SMF, Access and Mobility Management Function (AMF), MB-UPF, UPF, and Radio Access Network (RAN). Figure 1 The RAN element shown is connected to the next-generation (NG) RAN (NG-RAN) via the Uu interface of the user equipment (UE).

[0024] The MB-SMF can store the identifier of the AMF that handles multicast or broadcast sessions. The AMF may know the RAN nodes involved in the multicast or broadcast MBS sessions and may store their identifiers.

[0025] When a failure, with or without a restart, affects the MB-UPF, all PFCP sessions and contexts created for the MBS session in the MB-UPF may be lost, in some implementations. Furthermore, in some implementations, MBS data may fail to reach the end user.

[0026] Furthermore, without certain embodiments, if an NG-RAN node is reconfigured with a new Tracking Area Identifier (TAI) that is part of the MBS service area of ​​an existing MBS session, it may be unable to initiate the broadcast of an existing broadcast MBS session in the RAN node.

[0027] In some embodiments, the AMF can manage the recovery of broadcast MBS sessions itself for restarted RAN nodes.

[0028] Figure 2 Example methods according to certain embodiments are shown. For example... Figure 2 As shown in 210, the AMF can be stored in the last N2 MBS session management container received from the MB-SMF during the establishment of a broadcast MBS session or during a broadcast MBS session update. In this method, the approach may rely on an N2 MBS session management container that always contains all relevant information, such as Quality of Service (QoS) flow information, transport layer addresses, etc.

[0029] At 220, the AMF can detect a RAN node restart (using existing NG procedures), and at 230, the AMF can check if the RAN node serves any region within an existing MBS service area, such as a TAI or cell. If so, at 240, the AMF can trigger a Next Generation Application Protocol (NGAP) broadcast session setup procedure to re-establish the MBS session in the RAN node. In the case of location-related content, the AMF can include the relevant region session ID and may include the associated N2 container for storage.

[0030] At point 225, the AMF can detect that the RAN node is no longer reachable. Such detection can be performed using any required NG procedure. After performing this detection at point 225, the AMF can check at point 235 whether the RAN node is processing any multicast or broadcast MBS sessions. If so, at point 245, the AMF can request the MB-SMF to interrupt or otherwise terminate the delivery of data related to that MBS session to the RAN node. If unicast delivery is used on N3mb, the MB-SMF can configure the MB-UPF to terminate the delivery of data for that MBS session to the RAN node's GTP endpoint and IP address. Figure 2 (Not shown in the image).

[0031] Additionally, if unicast transmission is used on N3mb, the RAN node can return its DL GTP-U F-TEID, such as its IP address and tunnel endpoint identifier, in its response to the AMF at position 250. The AMF can then initiate an MBS broadcast context state notification request at position 260 to the MB-SMF, including the DLGTP-U F-TEID. Although Figure 2 As not shown, the MB-SMF can modify the PFCP session of the MBS session in the MB-UPF to begin distributing MBS data to the DL GTP-U F-TEID and stop doing so for the earlier DL GTP-U F-TEID used before the RAN node was restarted.

[0032] In order for the MB-SMF to modify or terminate the transmission of MBS data to the RAN node, the RAN node can ( Figure 2 (Not shown) The RAN node ID, along with the DL GTP-U F-TEID, is transmitted to the MB-SMF via the AMF, and the MB-SMF can store this information. This transmission can occur during the establishment of a broadcast session and in MBS broadcast context state notification requests. For multicast, this transmission may occur when a RAN node requests to establish a shared delivery to itself.

[0033] Figure 2This is provided as an example embodiment of a method or process. However, some embodiments are not limited to this example, and other examples, as discussed elsewhere herein, are possible. Figure 2 The method can be implemented by the access and mobility management functions.

[0034] Figure 3 An example signal flow diagram is shown for resuming a broadcast multicast / broadcast service (MBS) session in the event of a failed radio access node that has been restarted, according to certain embodiments.

[0035] like Figure 3 As shown, at point 0, a broadcast MBS session can be created, as described in 3GPP TS23.247. Then, at point 1, the AMF can be stored in the last N2MBS session management container received from the MB-SMF during the establishment or subsequent update of the broadcast MBS session for the MBS session. For location-dependent MBS sessions, the AMF can store the last N2MBS session management container received from the MB-SMF for both the MBS session and the MBS service area.

[0036] MBS data can flow from the Application Function (AF) to the UE in the source of the MBS session.

[0037] At point 2a, the NG-RAN node restarts, which may cause an interruption of broadcast MBS services. AMF can detect NG-RAN node restarts at point 3, for example, via the NGAP reset process at point 2b.

[0038] At point 3, the AMF can detect that the RAN has been restarted and that the RAN serves at least one TAI or a cell that is part of the MBS service area of ​​an existing MBS session, or, in the case of location-related content, one MBS service area that serves the MBS session.

[0039] AMF can re-establish a broadcast MBS session in the RAN node by sending an NGAP broadcast session establishment request at point 4a. The NGAP broadcast session establishment request contains the N2 (NGAP) MBS session information establishment request transmission information element (IE) of the last stored N2 MBS session management container. For example, the last N2 MBS session management container may include an N2 (NGAP) MBS session information establishment request transmission or an MBS session information modification request transmission.

[0040] NG-RAN nodes can establish broadcast MBS sessions and can return a response to the AMF at 4b. If unicast transmission is used on N3mb, the RAN response can include a new DL F-TEID assigned by the RAN node to receive MBS data from the MB-UPF within the IE container of the N2 (NGAP) MBS session information response message established from the NGAP broadcast session.

[0041] At point 5, the AMF can send a broadcast context state notification request to the MB-SMF, including an N2(NGAP)MBS session information response delivery IE container, which may contain the RAN node DL GTP-U F-TEID assigned by the NG-RAN node at point 4.

[0042] At point 6, the MB-SMF can modify the PFCP session of the MBS session in the MB-UPF to begin distributing MBS data to the DL GTP-U F-TEID and stop doing so for an earlier DL GTP-U F-TEID used before the RAN node was restarted.

[0043] Therefore, MBS service can be restored from AF to UE. If multicast transmission is used on N3mb, signaling from AMF to MB-SMF may not be required. However, such a feature... Figure 3 The middle is shown to make Figure 3 It is possible to describe multiple options without having to describe every feature in each option.

[0044] Figure 4 Methods according to certain embodiments are shown. For example... Figure 4 As shown, one method may include, at 410, receiving a request for data transmission of a complete tunnel endpoint identifier for a multicast / broadcast session to a radio access node, the request including the identifier of the radio access node. The method may further include, at 420, sending a request to a multicast / broadcast user plane function, the request including the complete tunnel endpoint identifier of the radio access node received from the radio access node, and requesting the multicast / broadcast user plane function to begin transmitting multicast / broadcast session data to the complete tunnel endpoint identifier of the radio access node.

[0045] The method may further include, at 430, storing the identifier and context of the radio access node to control the transmission of a complete tunnel endpoint identifier to the radio access node. The method may also include, at 440, receiving a request to redirect data delivery for a multicast / broadcast session to a new complete tunnel endpoint identifier for the radio access node, or at 450, a request to terminate the delivery of multicast / broadcast session data to the radio access node;

[0046] When a request is used to redirect data transmission, the method may include sending a request at 445 to a multicast / broadcast user plane function, the request including a first complete tunnel endpoint identifier of the radio access node corresponding to a complete tunnel endpoint identifier received from the radio access node, and requesting the multicast / broadcast user plane function to begin transmitting multicast / broadcast session data to the first complete tunnel endpoint identifier of the radio access node, and the request including a second complete tunnel endpoint identifier of the radio access node, and requesting the multicast / broadcast user plane function to stop transmitting multicast / broadcast session data to the second complete tunnel endpoint identifier of the radio access node, the second complete tunnel endpoint identifier being set to the complete tunnel endpoint identifier previously used for the multicast / broadcast session; and

[0047] When a request is used to terminate data transmission, the method may include, at 455, sending a request to the multicast / broadcast user plane function, the request including a complete tunnel endpoint identifier of the radio access node that has been set as a complete tunnel endpoint identifier previously used for the multicast / broadcast session, and requesting the multicast / broadcast user plane function to stop sending multicast / broadcast session data to the complete tunnel endpoint identifier of the radio access node.

[0048] A complete tunnel endpoint identifier can correspond to the Internet Protocol address and tunnel endpoint identifier of the user plane tunnel to which the radio access node expects to receive data from the multicast / broadcast session.

[0049] The method may also include, at 460, receiving a request for data transmission to a multicast / broadcast session of a radio access node using multicast transmission, the request including an identifier of the radio access node. The branches from start to 460 are shown separately from the branches from start to 410 because these processes can be performed independently or in parallel with each other at different times.

[0050] The method may also include, at 465, in response to a request for multicast data delivery, sending a source-specific multicast address and a complete tunnel endpoint identifier assigned to the multicast / broadcast session by the multicast / broadcast user plane function.

[0051] The method may also include, at 470, storing an identifier of the radio access node and storing an indication to use multicast transmission to the radio access node.

[0052] The method may also include, at 475, receiving a request to redirect data transmission of a multicast / broadcast session to a new complete tunnel endpoint identifier for the radio access, or a request to terminate data transmission of the multicast / broadcast session to the radio access node.

[0053] The method may also include, at 480, sending, in response to a request to redirect multicast data delivery, a source-specific multicast address and a complete tunnel endpoint identifier assigned to the multicast / broadcast session by the multicast / broadcast user plane function.

[0054] Figure 4 This is provided as an example embodiment of a method or process. However, some embodiments are not limited to this example, and other examples, as discussed elsewhere herein, are possible. Figure 4 The method can be implemented by the multicast / broadcast session management function.

[0055] Figure 5 An example of a system including device 10 according to an embodiment is shown. In one embodiment, device 10 may be a node, host, or server in or serving such a communication network. For example, device 10 may be a network node, satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next-generation Node B (NG-NB or gNB), TRP, 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 some example embodiments, device 10 may be, for example, a gNB or other similar radio node.

[0056] 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 including 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 (multiple) DUs via a midrange interface (referred to as the F1 interface), and (multiple) DUs may have one or more radio units (RUs) connected to (multiple) DUs via a frontend interface. Depending on the function splitting option, the DU may be a logical node including a subset of gNB functions. It should be noted that those skilled in the art will understand that device 10 may include Figure 5 Components or features not shown in the diagram.

[0057] like Figure 5As shown in the example, device 10 may include a 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, as an example, processor 12 may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor or any other processing unit based on a multi-core processor architecture. Although Figure 5 A single processor 12 is shown, but multiple processors may be used according to other 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).

[0058] 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 or communication resources.

[0059] 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 random access memory (RAM), read-only memory (ROM), static memory (such as a disk or optical disk), hard disk drive (HDD), 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.

[0060] 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 executed by processor 12 and / or device 10.

[0061] 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 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. The radio interfaces may correspond to a variety of radio access technologies, including one or more of the following: Global System for Mobile Communications (GSM), Narrowband Internet of Things (NB-IoT), LTE, 5G, WLAN, Bluetooth (BT), Bluetooth Low Energy (BT-LE), Near Field Communication (NFC), Radio Frequency Identifier (RFID), Ultra Wideband (UWB), MulteFire, etc. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters), mappers, Fast Fourier Transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and to receive symbols (e.g., via an uplink).

[0062] 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 embodiments, transceiver 18 is capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, device 10 may include input and / or output devices (I / O devices), or input / output components.

[0063] 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.

[0064] According to some embodiments, the processor 12 and memory 14 may be included in, or may be part of, a processing circuit system / component or a control circuit system / component. Additionally, in some embodiments, the transceiver 18 may be included in or may be part of a transceiver circuit system / component.

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

[0066] As described above, in some embodiments, device 10 may be a network element or RAN node, or may be part of a network element or RAN node, such as a base station, access point, node B, eNB, gNB, TRP, HAPS, IAB node, relay node, WLAN access point, satellite, etc. In one example embodiment, device 10 may be a gNB or other radio node, or may be the CU and / or DU of a gNB. According to some embodiments, device 10 may be controlled by memory 14 and processor 12 to perform functions associated with any embodiment described herein. For example, in some embodiments, device 10 may be configured to perform one or more processes described in any flowchart or signaling diagram described herein, such as Figures 2 to 4 Those shown, or any other methods described herein. In some embodiments, as discussed herein, apparatus 10 may be configured to perform, for example, procedures relating to the restoration of broadcast services for multicast / broadcast services in the event of a radio access node failure or restart.

[0067] Figure 5An example of device 20 according to an embodiment is also shown. In one embodiment, device 20 may be a node or element in or associated with such a network, such as a UE, communication node, mobile device (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, mobile device, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet computer, smartphone, IoT device, sensor or NB-IoT device, watch or other wearable device, head-mounted display (HMD), vehicle, drone, medical device and its applications (e.g., remote surgery), industrial device and its applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. As an example, device 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0068] In some example embodiments, device 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, 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 5 Components or features not shown in the diagram.

[0069] like Figure 5 As illustrated in the example, device 20 may include or be coupled to processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. In fact, as an example, 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 5 A single processor 22 is shown, but multiple processors may be used according to other embodiments. For example, it should be understood that in some embodiments, device 20 may include two or more processors, which may 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).

[0070] 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.

[0071] 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 memory (such as a disk or optical disk), hard disk drive (HDD), 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.

[0072] 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 executed by processor 22 and / or device 20.

[0073] In some embodiments, device 20 may further include or be coupled to one or more antennas 25 for receiving downlink signals from device 20 and for transmitting via 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 a variety of radio access technologies, including one or more of the following: 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, etc.), 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.

[0074] 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 capable of directly transmitting and receiving 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.

[0075] 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 one example embodiment, device 20 may optionally be configured to communicate with device 10 via wireless or wired communication link 70 according to any radio access technology, such as NR.

[0076] According to some embodiments, the processor 22 and memory 24 may be included in a processing circuit system or a control circuit system, or may be part of a processing circuit system or a control circuit system. Additionally, in some embodiments, the transceiver 28 may be included in a transceiver circuit system or may be part of a transceiver circuit system.

[0077] As described above, according to some embodiments, device 20 may be, for example, a UE, SL UE, relay UE, mobile device, mobile station, ME, IoT device, and / or NB-IoT device, etc. According to some embodiments, device 20 may be controlled by memory 24 and processor 22 to perform functions associated with any of the embodiments described herein, such as... Figures 2 to 4 The image shown or about Figures 2 to 4 One or more operations described herein, or any other method described herein. For example, in one embodiment, apparatus 20 may be controlled to perform processes related to restoring broadcast service for multicast / broadcast services in the event of a radio access node failure or restart, as described in detail elsewhere herein.

[0078] In some embodiments, the apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing methods, processes, or any variations discussed herein. Examples of such components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for causing the execution of any of the operations discussed herein.

[0079] In view of the foregoing, certain exemplary embodiments provide several technical improvements, enhancements, and / or advantages relative to prior art processes, and constitute improvements at least in the technical field of wireless network control and / or management. Certain embodiments may have various benefits and / or advantages. For example, in some embodiments, NG-RAN node restarts may be completely hidden from the MB-SMF when using multicast transmission over N3mb. Furthermore, for example, in some embodiments, the AMF can handle NG-RAN restarts locally without involving the MB-SMF, except for notifying the DL F-TEID address change when using unicast transmission over N3mb. Additionally, some embodiments may also allow the initiation of broadcasts of existing broadcast MBS sessions in NG-RAN nodes that are reconfigured using a new TAI that is part of the MBS service area of ​​the existing MBS session.

[0080] In some exemplary embodiments, the functionality of any method, process, signal diagram, algorithm, or flowchart described herein may be implemented by software and / or computer program code or portions thereof stored in memory or other computer-readable or tangible media and may be executed by a processor.

[0081] 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 configured as a program or part of a program (including added or updated software routines), which may be executed by at least one processing processor or controller. The program (also referred to as a program product or computer program) includes software routines, applets, and macros, and may be stored in any device-readable data storage medium and may include program instructions for performing a specific task. A 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 a portion of 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.

[0082] As an example, software or computer program code, or part of it, can be in the form of source code, object code, or some intermediate form, and can be stored on some carrier, distribution medium, or computer-readable medium, which can be any entity or device capable of carrying the program. Such a carrier can include, for example, 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 can be executed in a single electronic digital computer or distributed across multiple computers. The computer-readable medium or computer-readable storage medium can be a non-transitory medium.

[0083] 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 component, which may be carried by an electromagnetic signal downloaded from the Internet or another network.

[0084] According to example embodiments, an apparatus (such as a node, device, or corresponding component) may be configured as a circuit system, a computer, or a microprocessor, such as a monolithic computer element, or configured as a chipset that may include at least a memory for providing storage capacity for arithmetic operations(s) and / or an arithmetic processor for performing arithmetic operations(s).

[0085] The exemplary embodiments described herein can be applied to both singular and plural implementations, regardless of whether 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 exemplary embodiments that include multiple instances of network nodes, and vice versa.

[0086] It will be readily understood by those skilled in the art that the exemplary embodiments described above can be practiced with a different sequence of processes and / or with hardware elements in a different configuration than 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.

[0087] Partial vocabulary list:

[0088] AC access

[0089] Automatic Gain Control (AGC)

[0090] CSI-RS Channel State Information Reference Signal

[0091] DL downlink

[0092] DMRS demodulation reference signal

[0093] gNB Next Generation Node B

[0094] MPE Maximum Permissible Exposure

[0095] NR 5G New Radio

[0096] PA power amplifier

[0097] PDCCH (Physical Downlink Control Channel)

[0098] PDCP (Packet Data Convergence Protocol)

[0099] PDSCH (Physical Downlink Shared Channel)

[0100] RA Random Access

[0101] RACH Random Access Channel

[0102] RO random access timing

[0103] RRC Radio Resource Control

[0104] RSRP reference signal received power

[0105] SRS Detection Reference Signal

[0106] SSB Synchronization Signal Block

[0107] SSBRI SSB Resource Block Indicator

[0108] SSS auxiliary synchronization signal

[0109] TDD (Time Division Duplex)

[0110] UE User Equipment

[0111] UL uplink

[0112] WB wide beam

Claims

1. An apparatus for a communication network, comprising: Access and mobility management functions, which are configured to perform: Stores the last multicast / broadcast service session information received from the multicast / broadcast session management function, corresponding to the multicast / broadcast service session; The radio access node associated with the multicast / broadcast service session has been restarted; as well as Based on the stored last multicast / broadcast service session information, a multicast / broadcast session establishment process is triggered to establish the multicast / broadcast service session in the radio access node.

2. The apparatus of claim 1, wherein the detection comprises: Check whether the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session. as well as If the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session, then the radio access node is determined to be associated with the multicast / broadcast service.

3. The apparatus according to claim 1 or claim 2, wherein the access and mobility management function is further configured to perform: In response to the trigger, a complete tunnel endpoint identifier is received from the radio access node, wherein when Internet Protocol unicast transmission is used to deliver data of the multicast / broadcast service session to the radio access node, the complete tunnel endpoint identifier corresponds to the Internet Protocol address and tunnel endpoint identifier of the user plane tunnel to which the radio access node expects to receive the data.

4. The apparatus of claim 3, wherein the access and mobility management function is further configured to perform: When Internet Protocol unicast transmission is used to deliver the data to the radio access node, a request is sent to the multicast / broadcast session management function with the complete tunnel endpoint identifier of the radio access node to update the multicast / broadcast session management function with respect to the new complete tunnel endpoint identifier of the radio access node.

5. The apparatus according to any one of claims 1 to 4, wherein the multicast / broadcast service session information includes all the information required to establish the multicast / broadcast service session in the radio access node.

6. The apparatus according to any one of claims 1 to 5, wherein for location-dependent multicast / broadcast sessions, the storage, detection, and triggering are performed per multicast / broadcast service region associated with the region session identifier of the multicast / broadcast service session.

7. A method for access and mobility management functions in a communication network, the method comprising: Stores the last multicast / broadcast service session information received from the multicast / broadcast session management function, corresponding to the multicast / broadcast service session; The radio access node associated with the multicast / broadcast service session has been restarted; as well as Based on the stored last multicast / broadcast service session information, a multicast / broadcast session establishment process is triggered to establish the multicast / broadcast service session in the radio access node.

8. The method of claim 7, wherein the detection comprises: Check whether the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session. as well as If the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session, then the radio access node is determined to be associated with the multicast / broadcast service.

9. The method according to claim 7 or claim 8, further comprising: In response to the trigger, a complete tunnel endpoint identifier is received from the radio access node, wherein when Internet Protocol unicast transmission is used to deliver data of the multicast / broadcast service session to the radio access node, the complete tunnel endpoint identifier corresponds to the Internet Protocol address and tunnel endpoint identifier of the user plane tunnel to which the radio access node expects to receive the data.

10. The method of claim 9, further comprising: When Internet Protocol unicast transmission is used to deliver the data to the radio access node, a request is sent to the multicast / broadcast session management function with the complete tunnel endpoint identifier of the radio access node to update the multicast / broadcast session management function with respect to the new complete tunnel endpoint identifier of the radio access node.

11. The method according to any one of claims 7 to 10, wherein the multicast / broadcast service session information includes all the information required to establish the multicast / broadcast service session in the radio access node.

12. The method according to any one of claims 7 to 11, wherein for location-dependent multicast / broadcast sessions, the storage, detection, and triggering are performed per multicast / broadcast service region associated with the region session identifier of the multicast / broadcast service session.

13. An access and mobility management function for a communication network, comprising: A component for storing the last multicast / broadcast service session information received from the multicast / broadcast session management function, corresponding to the multicast / broadcast service session; Components used to detect that the radio access node associated with the multicast / broadcast service session has been restarted; as well as A component for triggering a multicast / broadcast session establishment process based on the stored last multicast / broadcast service session information, so as to establish the multicast / broadcast service session in the radio access node.

14. The access and mobility management function of claim 13, wherein the detection includes: Check whether the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session. as well as If the radio access node serves any area within the multicast / broadcast service area of ​​the multicast / broadcast service session, then the radio access node is determined to be associated with the multicast / broadcast service.

15. The access and mobility management function according to claim 13 or claim 14, further comprising: The component is used to receive a complete tunnel endpoint identifier from the radio access node in response to the trigger, wherein when Internet Protocol unicast transmission is used to deliver data of the multicast / broadcast service session to the radio access node, the complete tunnel endpoint identifier corresponds to the Internet Protocol address and tunnel endpoint identifier of the user plane tunnel to which the radio access node expects to receive the data.

16. The access and mobility management function according to claim 15, further comprising: A component for sending a request to the multicast / broadcast session management function with the complete tunnel endpoint identifier of the radio access node when Internet Protocol unicast transmission is used to deliver the data to the radio access node, so as to update the multicast / broadcast session management function with respect to the new complete tunnel endpoint identifier of the radio access node.

17. The access and mobility management function according to any one of claims 13 to 16, wherein the multicast / broadcast service session information includes all the information required to establish the multicast / broadcast service session in the radio access node.

18. The access and mobility management function according to any one of claims 13 to 17, wherein for location-related multicast / broadcast sessions, the storage, detection, and triggering are performed per multicast / broadcast service area associated with the area session identifier of the multicast / broadcast service session.

19. A non-transient computer-readable medium comprising program instructions stored thereon, the program instructions being executed by a processor to perform the method according to any one of claims 7 to 12.

Images