Restoring multicast / broadcast services upon multicast / broadcast failure and restart

Abstract

Embodiments of the present disclosure relate to resuming multicast / broadcast services upon multicast / broadcast failure and restart. Systems, methods, apparatuses, and computer program products for resuming multicast / broadcast services upon multicast / broadcast failure and restart are provided. For example, a method can include detecting a restart of a multicast / broadcast user plane function that is supporting a packet forwarding control protocol session for a multicast / broadcast session. The method can also include recreating the packet forwarding control protocol session for the multicast / broadcast session. The method can also include providing addressing information for data delivery for the broadcast / multicast session to the multicast / broadcast user plane function and instructing the multicast / broadcast user plane function to use the addressing information for the broadcast / multicast session if possible.

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 communication systems other than 5G or other communication systems. For example, some example embodiments may generally relate to systems and / or methods for providing recovery of multicast / broadcast services by utilizing restart in the event of a multicast / broadcast failure. 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) wireless 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 approximately 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 deliver extremely wide bandwidth and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT). As machine-to-machine (M2M) communication becomes increasingly prevalent, the demand for networks that meet lower power, lower data rates, and longer battery life will continue to grow. Next-Generation Radio Access Network (NG-RAN) refers to the RAN for 5G, which can provide NR and LTE (and LTE Advanced) radio access. Note that in 5G, nodes that can provide radio access to user equipment (i.e., similar to BNBs in UTRAN or evolved NBs / eNBs in LTE) can be called Next-Generation NBs (gNBs) when built on NR radios, and Next-Generation eNBs (NG-eNBs) when built on E-UTRA radios. Summary of the Invention

[0003] The embodiments may relate to an apparatus. The apparatus 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 may be configured, together with the at least one processor, to cause the apparatus to at least perform the following actions: detect a restart of a multicast / broadcast user plane function that supports a packet forwarding control protocol session for a multicast / broadcast 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: recreate the packet forwarding control protocol session for the multicast / broadcast 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: provide addressing information for data delivery in a broadcast / multicast session to the multicast / broadcast user plane function, and, if possible, instruct the multicast / broadcast user plane function to use the addressing information for the broadcast / multicast session.

[0004] The embodiments may relate to an apparatus. The apparatus 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 may be configured, together with the at least one processor, to cause the apparatus to at least perform the following operations: receive a request from a multicast / broadcast session management function for establishing a Packet Forwarding Control Protocol (CTP) session for a multicast / broadcast 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 receiving addressing information, the addressing information including an address within an address range for data delivery of the broadcast / multicast 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, if possible, at least use the addressing information to perform the broadcast / multicast session.

[0005] Implementations may relate to a method. The method may include detecting a restart of a multicast / broadcast user plane function that is supporting a packet forwarding control protocol session for a multicast / broadcast session. The method may also include recreating the packet forwarding control protocol session for the multicast / broadcast session. The method may further include providing the multicast / broadcast user plane function with addressing information for data delivery in the broadcast / multicast session, and, if possible, instructing the multicast / broadcast user plane function to use the addressing information for the broadcast / multicast session.

[0006] The embodiments may relate to a method. This method may include receiving a request from a multicast / broadcast session management function for establishing a Packet Forwarding Control Protocol (PaCP) session for the multicast / broadcast session. The method may also include receiving addressing information including an address within an address range for means of data delivery for the broadcast / multicast session. If possible, the method may further include using the addressing information for the broadcast / multicast session.

[0007] The embodiments may relate to an apparatus. The apparatus may include components for detecting the restart of a multicast / broadcast user plane function that is supporting a packet forwarding control protocol session of a multicast / broadcast session. The apparatus may also include components for recreating the packet forwarding control protocol session for the multicast / broadcast session. The apparatus may further include components for providing the multicast / broadcast user plane function with addressing information for data delivery in the broadcast / multicast session, and, if possible, instructing the multicast / broadcast user plane function to use the addressing information for the broadcast / multicast session.

[0008] The embodiments may relate to an apparatus. The apparatus may include components for receiving from a multicast / broadcast session management function a request to establish a Packet Forwarding Control Protocol (CTP) session for the multicast / broadcast session. The apparatus may also include components for receiving addressing information, which includes an address within an address range for means of data delivery for the broadcast / multicast session. If possible, the apparatus may further include components for using the addressing information for the broadcast / multicast session. 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 a method of resuming a packet forwarding control protocol session for a multicast / broadcast service session in a restarted multicast / broadcast user plane function, according to certain embodiments.

[0013] Figure 4 Another method according to certain embodiments is shown;

[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 exemplary 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 exemplary embodiments of systems, methods, apparatuses, and computer program products for providing broadcast service recovery 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 exemplary embodiments.

[0016] 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 phrases such as "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact 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 phrases such as "in some embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification does not necessarily refer to all of 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.

[0017] Some embodiments may have various aspects and features. These aspects and features may be applied individually or in any desired combination of 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 desired, the different functions or processes discussed below can be performed in different orders and / or simultaneously with each other. Furthermore, if desired, one or more of the described functions or processes can be optional or can be combined. Therefore, the following description should be considered 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 the system architecture. Figure 1 The system architecture is shown. Figure 1 Based on 3GPP TS 23.247 Figure 5 .1-1. "5G System architecture for Multicast andBroadcast Service".

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

[0021] MB Service (MBS) sessions can correspond to broadcast MBS sessions, in which case SMF and UPF may not be involved in service delivery. Alternatively, MBS sessions can correspond to multicast MBS sessions, in which case SMF and UPF can be included 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 also 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 with a downlink (DL) fully qualified Tunnel Endpoint Identifier (F-TEID), which may include an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID). Multicast transmission can use a low-layer source-specific multicast (LL SSM) address and a public GTP TEID (C-TEID) to send packets. The LL SSM address may include a multicast address, which can be used as the destination address in the transmitted packets, and the LL SSM 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 restoration can refer 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. Entities that may be affected can 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 unit shown is connected to the next-generation (NG) RAN (NG-RAN) via the user equipment (UE) through the Uu interface.

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

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

[0026] Furthermore, in some embodiments that do not have a restart, if the 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 impossible to start broadcasting an existing broadcast MBS session in the RAN node.

[0027] At 210, the MB-SMF can detect an MB-UPF restart. When an MB-UPF restart is detected, at 215, the MB-SMF can recreate the PFCP session for the affected MBS session in the MB-UPF by applying any suitable method, such as the method for establishing an N4mbPFCP session for the MBS as defined in Clause 5.34.2 of 3GPP TS 29.244, but with at least some differences, as described below.

[0028] When multicast transmission is used on N3mb and / or N19mb, at 220, the MB-SMF can provide the MB-UPF with the new LL SSM and GTP-U C-TEID used before the MB-UPF restart, and, if possible, instruct the MB-UPF to allocate that address and C-TEID. The MB-UPF response at 230 can indicate the LL SSM and GTP-U C-TEID allocated by the MB-UPF. The MB-UPF can only provide a different address if the previous address cannot be reused, for example, if the reset is a partial restart.

[0029] When using unicast transmission on N6mb / Nmb9, at 225, the MB-SMF can provide a new N6mb / Nmb9 unicast tunnel address used before the MB-UPF restart, and, if possible, instruct the MB-UPF to allocate that address. The MB-UPF response at 230 can indicate the N6mb / Nmb9 address allocated by the MB-UPF. The MB-UPF can only provide a different address if the previous address cannot be reused, for example, due to a partial reboot.

[0030] If multicast transmission is used for N6mb or N9mb, MB-UPF can join the delivery from the multicast address received in the request from MB-SMF.

[0031] After an MB-UPF reboot, it may not immediately reuse N3mb / N19mb and N6mb / Nmb9 addresses to avoid inconsistent address allocations across the network, and it is able to restore Packet Forwarding Control Protocol (PFCP) sessions of MBS sessions affected by the failure. How this is accomplished can be implementation-specific.

[0032] Some embodiments can support all cases in which addressing information for MBS data delivery can be retained / recovered in the MB-UPF.

[0033] At 240, the method may include receiving a new unicast ingress tunnel address in a response from a multicast / broadcast user plane function. The method may also include, at 250, redirecting the multicast / broadcast service session to the new unicast ingress tunnel address. The response including the new address may be the response received at 230.

[0034] At 245, the method may include: receiving a new low-layer source-specific multicast address and a Public Packet Radio Service Tunneling Protocol (PPP) user plane tunnel endpoint identifier in a response from the multicast / broadcast user plane function. The method may also include: at 255, providing each access-side destination with the new low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier assigned by the multicast / broadcast user plane function. The response including the new address may be the response received at 230.

[0035] Figure 2 This is provided as an example embodiment of a method or process. However, some embodiments are not limited to this example, and other examples are possible as discussed elsewhere herein.

[0036] Figure 3 A signal flow diagram is shown for a method of resuming a packet forwarding control protocol session for a multicast / broadcast service session in a restarted multicast / broadcast user plane function, according to certain embodiments.

[0037] like Figure 3 As shown, at point 0, MB-UPF can be used to create broadcast or multicast MBS sessions, as described in 3GPP TS 23.247. Therefore, MBS data can be distributed.

[0038] At point 1, the MB-UPF may fail and restart. The MB-UPF will no longer forward / distribute MBS data. At point 2, the MB-SMF can use any desired mechanism to detect the MB-UPF restart, such as restoring the timestamp of the signal sent in the PFCP signaling.

[0039] At 3a, MB-SMF can re-establish the PFCP session for the MBS session in MB-UPF by applying any desired techniques used to establish the N4mb PFCP session for MBS (such as the methods set forth in Clause 5.34.2 of 3GPP TS 29.244), but with the following differences.

[0040] When using multicast transmission on N3mb and / or N19mb, at point 3a, the MB-SMF can provide the MB-UPF with the new LL SSM and GTP-UC-TEID used before the MB-UPF reboot, and, if possible, instruct the MB-UPF to allocate that address and C-TEID. The MB-UPF response at point 3b can indicate the allocated LL SSM and GTP-UC-TEID. The MB-UPF can only provide a different address if the previous address cannot be reused, such as in the case of a partial reboot. If a different address is allocated, the MB-SMF can continue as in the case of an MB-UPF failure without rebooting.

[0041] When using unicast transmission on N6mb / Nmb9, at point 3a, the MB-SMF can provide a new N6mb / Nmb9 tunnel address used before the MB-UPF restart, and, if possible, instruct the MB-UPF to allocate that address. At point 3b, the MB-UPF can only provide a different address if the previous address cannot be reused, such as in the case of a partial restart. If a different address is allocated, the MB-SMF can continue without restarting, as it would in the case of an MB-UPF failure.

[0042] If multicast transmission is used for N6mb or N9mb, MB-UPF can join the delivery from the multicast address received in the request from MB-SMF.

[0043] The PFCP session establishment request may include a recovery indication flag to inform MB-UPF that the PFCP session will resume the PFCP session of the existing MBS session.

[0044] After the MB-UPF restarts, the N3mb / N19mb and N6mb / Nmb9 addresses cannot be immediately reused by the MB-UPF to avoid address allocation inconsistencies across the network and to enable PFCP session recovery should an MBS session be affected by a failure. How this is accomplished can be implementation-specific.

[0045] At the end of the process, MBS data delivery can be resumed toward the RAN node and / or UPF, seamlessly connecting to the rest of the system and NEF / AF / MBSF.

[0046] Figure 4 Another method according to certain embodiments is shown. For example... Figure 4As shown, the method may include: at 410, receiving a request from a multicast / broadcast session management function for establishing a Packet Forwarding Control Protocol (CTP) session for the multicast / broadcast session. The method may further include: at 420, receiving addressing information including an address within an address range for means of data delivery for the broadcast / multicast session. The method may further include: at 430, using the addressing information for the broadcast / multicast session, if possible.

[0047] The method may also include sending a response at 440 to the multicast / broadcast session management function indicating whether the addressing information is being used.

[0048] Addressing information can be a low-layer source-specific multicast address and a Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier, which is used to transmit data.

[0049] For each destination endpoint, the addressing information can be the destination address and the GPRS Tunneling Protocol User Plane Tunnel Endpoint Identifier, which is used to send data to that destination endpoint.

[0050] When unicast transmission is used to receive data, the addressing information can be the unicast ingress tunnel address.

[0051] When multicast transmission is used to receive data, the addressing information may include a multicast address. The method may also include, at 450, incorporating the reception of data from the multicast address.

[0052] A Packet Forwarding Control Protocol (CTP) session establishment request may include a recovery flag configured to indicate that the establishment request will restore an existing CTP session for multicast / broadcast service.

[0053] At 460, the method may include: determining whether the received unicast ingress tunnel address has been allocated or is no longer available for allocation. At 462, the method may include: if the determination is positive, i.e., when it is determined that the received unicast ingress tunnel address is now unavailable for any reason, such as the received unicast ingress tunnel address having been allocated or no longer available for allocation, then allocating a new unicast ingress tunnel address. The method may further include: at 464, if the determination is positive, for example, at any time when the allocation of the new unicast ingress tunnel address is performed in 462, providing the new unicast ingress tunnel address to the multicast / broadcast session management function.

[0054] The method may further include: at 470, determining whether the received low-layer source-specific multicast address and PPP Tunneling Protocol user plane tunnel endpoint identifier have been assigned or are no longer available for assignment. The method may further include: at 472, if the determination is yes, assigning a new low-layer source-specific multicast address and PPP Tunneling Protocol user plane tunnel endpoint identifier. The method may further include: at 474, if the determination is yes, providing the new low-layer source-specific multicast address and PPP Tunneling Protocol user plane tunnel endpoint identifier to the multicast / broadcast session management function.

[0055] Regarding the described process or explanation Figure 4 Various modifications to the method are also possible. For example, the procedure at 430 can be combined with procedures at 460 and 470. For example, a device implementing the method shown can check whether the provided LLSSM, ingress tunnel address, or both have been assigned, are no longer available, or are unavailable. If not, i.e., if they are available, the address can be used, and the response at 440 can indicate this. On the other hand, if there is any reason why the address(s) or other identifier(s) cannot be used, the device implementing the method can assign a new address or other identifier, and the new address can be provided in the response at 440.

[0056] 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 are possible as discussed elsewhere herein.

[0057] 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 a communications network, or provide services for such a 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 LTE, 5G, or NR. In some example embodiments, device 10 may be, for example, a gNB or other similar radio node.

[0058] 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. The CU may control the operation of the DU(s) via a midrange interface known as the F1 interface, and the DU(s) may have one or more radio units (RUs) connected to the DU(s) 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.

[0059] like Figure 5 As 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 practice, as an example, processor 12 may include one or more of 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 device based on a multi-core processor architecture. Although in 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, apparatus 10 may include two or more processors that can form a multiprocessor system (e.g., in this case, processor 12 may represent a multiprocessor), which can support multiprocessing. In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

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

[0061] 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 any type of memory 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-transient machine or computer-readable medium, or any other suitable storage device. 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.

[0062] In one embodiment, device 10 may further include or be coupled to (internal or external) a 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.

[0063] In some embodiments, device 10 may further include or be coupled to one or more antennas 15 for transmitting 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 device. The radio interfaces may correspond to one or more of various radio access technologies, including 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 Identification (RFID), Ultra Wideband (UWB), Multiband (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 uplinks).

[0064] Thus, 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 apparatuses.

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

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

[0067] As used herein, the term "circuit system" can refer to a hardware circuit system implementation only (e.g., analog and / or digital circuitry), 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(s) (including digital signal processors) having software, which work together to enable a device (e.g., device 10) to perform various functions, and / or a hardware circuitry and / or a processor(s), or a portion thereof, which uses software for operation, but may be absent when software is not required for operation. As another example, as used herein, the term "circuit system" can also cover a hardware circuitry or processor(s), or a portion thereof, and its accompanying software and / or firmware implementation. The term "circuit system" can also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or networking device.

[0068] As described above, in some embodiments, device 10 may be 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 depicted in any flowchart or signaling diagram described herein, such as in Figure 2 and 3 Those illustrated in the figures, or any other methods described herein. In some embodiments, as discussed herein, apparatus 10 may be configured to perform processes, for example, relating to the recovery of multicast / broadcast services in the event of multicast / broadcast failure and restart.

[0069] Figure 5 Further examples of apparatus 20 according to embodiments are shown. In one embodiment, apparatus 20 may be a node or element in or associated with a communication network, such as a UE, communication node, mobile device (ME), mobile station, mobile device, fixed device, mobile device, or other device. As described herein, a UE may also be referred to as, for example, a mobile station, mobile device, mobile unit, mobile device, user equipment, subscriber station, wireless terminal, tablet computer, smartphone, wireless device, sensor or NB-IoT device, watch or other wearable device, head-mounted display (HMD), vehicle, target, 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, apparatus 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0070] 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 wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, Wi-Fi, NB-IoT, Bluetooth, NFC, multi-antenna, and / or any other wireless 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.

[0071] like Figure 5 As shown 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 practice, as an example, processor 22 may include one or more of 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 based on a multi-core processor architecture. Although in 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 that can form a multiprocessor system (e.g., in this case, processor 22 may represent a multiprocessor), which can support multiprocessing. In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0072] 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 communication resource management.

[0073] 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 any type of memory 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 consist of any combination of 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-transient machine or computer-readable medium. 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.

[0074] In one embodiment, device 20 may further include or be coupled to (internal or external) a 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.

[0075] 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 one or more of a variety of 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, 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.

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

[0077] 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 via wireless or wired communication link 70 according to any wireless access technology (e.g., NR).

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

[0079] As described above, according to some embodiments, device 20 may be, for example, a UE, SLUE, relay UE, mobile device, mobile station, ME, IoT device, and / or NB-IoT device. 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... Figure 2 and Figure 3 The image shown or about Figure 2 and Figure 3 One or more of the operations described herein, or any other method described herein. For example, in one embodiment, the control device 20 may perform procedures relating to the recovery and restart of multicast / broadcast services in the event of multicast / broadcast failure, as described in detail elsewhere herein.

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

[0081] In view of the foregoing, certain exemplary embodiments provide several technical improvements, enhancements, and / or advantages over prior art processes, and at least constitute an improvement in the technical field of wireless network control and / or management. Certain embodiments may have various benefits and / or advantages. For example, certain embodiments may allow seamless recovery of MBS data delivery to the RAN node and / or UPF, to the rest of the system, and to the NEF / AF / MBSF.

[0082] The embodiments can be further described using the following examples:

[0083] Example 1. An apparatus comprising: components for detecting a restart of a multicast / broadcast user plane function, the multicast / broadcast user plane function supporting a Packet Forwarding Control Protocol (PTCP) session for a multicast / broadcast session; components for recreating a PTCP session for the multicast / broadcast session; and components for providing the multicast / broadcast user plane function with addressing information for data delivery of the broadcast / multicast session, and instructing the multicast / broadcast user plane function to use the addressing information for the broadcast / multicast session if possible.

[0084] Example 2. The apparatus according to Example 1 further includes: a component for receiving a response from the multicast / broadcast user plane function, the response indicating whether the addressing information is used.

[0085] Example 3. The apparatus according to Example 1 or 2, wherein when the multicast / broadcast user plane function is to use multicast transmission for sending data, the addressing information includes a low-layer source-specific multicast address and a Public Packet Radio Service Tunneling Protocol (PPP) user plane tunnel endpoint identifier, and the low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier are provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

[0086] Example 4. An apparatus according to any one of Examples 1 to 3, wherein, for each destination endpoint, when data is to be sent to the destination endpoint using unicast transmission by the multicast / broadcast user plane function, the addressing information includes a destination address and a Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier.

[0087] Example 5. An apparatus according to any one of Examples 1 to 4, wherein when the multicast / broadcast user plane function uses unicast transmission for receiving data, the addressing information includes a unicast ingress tunnel address, which is provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

[0088] Example 6. The apparatus according to any one of Examples 1 to 4, wherein the addressing information includes a multicast address when the multicast / broadcast user plane function uses multicast transmission for receiving data.

[0089] Example 7. An apparatus according to any one of Examples 1 to 6, wherein providing the addressing information and instructing the multicast / broadcast user plane function comprises: sending the information and the instruction in a Packet Forwarding Control Protocol session establishment request.

[0090] Example 8. The apparatus according to Example 7, wherein the Packet Forwarding Control Protocol (CTP) session establishment request includes a recovery flag configured to indicate that the establishment request is to restore a CTP session with an existing multicast / broadcast service session.

[0091] Example 9. The apparatus according to any one of Examples 2 to 8 further includes: means for receiving a new unicast ingress tunnel address from the response of the multicast / broadcast user plane function; and means for redirecting the multicast / broadcast service session to the new unicast ingress tunnel address.

[0092] Example 10. The apparatus according to any one of Examples 2 to 9 further includes: components for receiving a new low-layer source-specific multicast address and a Public Packet Radio Service Tunneling Protocol (PPP) user plane tunnel endpoint identifier from the response of the multicast / broadcast user plane function; and components for providing the new low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier assigned by the multicast / broadcast user plane function to each access-side destination.

[0093] Example 11. An apparatus comprising: components for receiving a request from a multicast / broadcast session management function, the request being for establishing a Packet Forwarding Control Protocol session for the multicast / broadcast session; components for receiving addressing information, the addressing information including an address within an address range of the apparatus for data delivery of the broadcast / broadcast session; and components for using the addressing information for the broadcast / broadcast session, if possible.

[0094] Example 12. The apparatus according to Example 11 further includes: a component for sending a response to the multicast / broadcast session management function, the response indicating whether the addressing information is used.

[0095] Example 13. The apparatus according to Example 11 or 12, wherein the addressing information includes a low-layer source-specific multicast address to be used for transmitting data and a Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier.

[0096] Example 14. The apparatus according to Example 11 or 12, wherein for each destination endpoint, the addressing information includes a destination address to which data will be sent to the destination endpoint and a Public General Packet Radio Service Tunneling Protocol User Plane Tunnel Endpoint Identifier.

[0097] Example 15. The apparatus according to any one of Examples 11 to 14, wherein when a unicast transmission is to be used to receive data, the addressing information includes a unicast ingress tunnel address.

[0098] Example 16. The apparatus according to any one of Examples 11 to 14, wherein when a multicast transmission is to be used to receive data, the addressing information includes a multicast address.

[0099] Example 17. The apparatus according to Example 16 further includes: a component for incorporating the reception of data from the multicast address.

[0100] Example 18. An apparatus according to any one of Examples 11 to 17, wherein the Packet Forwarding Control Protocol (CTP) session establishment request includes a recovery flag configured to indicate that the establishment request is to restore a CTP session with an existing multicast / broadcast service session.

[0101] Example 19. The apparatus according to any one of Examples 11 to 18 further includes: components for determining whether the received unicast ingress tunnel address has been allocated or is no longer available for allocation; components for allocating a new unicast ingress tunnel address if the determination is affirmative; and components for providing the new unicast ingress tunnel address to the multicast / broadcast session management function if the determination is affirmative.

[0102] Example 10. The apparatus according to any one of Examples 11 to 19 further includes: components for determining whether the received low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier have been allocated or are no longer available for allocation; if the determination is affirmative, allocating a new low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier; and if the determination is affirmative, providing the new low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier to the multicast / broadcast session management function.

[0103] In some exemplary 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 may be executed by a processor.

[0104] In some exemplary 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) executable by at least one operating processor or controller. A program, also known as a program product or computer program, includes software routines, applets, and macros, may be stored in any device-readable data storage medium, and may include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components configured to perform some of the exemplary embodiments when the program is run. 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 exemplary embodiments may be executed as routines, which may be implemented as added or updated software routines. In one example, software routines may be downloaded to the apparatus.

[0105] As an 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 in some type of carrier, distribution medium, or computer-readable medium, which can be any entity or device capable of carrying the program. Such a carrier may include, for example, recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and / or software distribution packages. Depending on the required processing power, the computer program may be executed in a single electronic digital computer or may be distributed across multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transient medium.

[0106] In other example embodiments, the functionality of the example embodiments may be performed by hardware or circuitry included in the device, for example, 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, which may be carried by an electromagnetic signal downloaded from the Internet or other networks.

[0107] According to an exemplary embodiment, an apparatus such as a node, device, or corresponding component may be configured as a circuit, a computer, or a microprocessor such as a single-chip computer element, or a chipset, which may include at least a memory for providing storage capacity for arithmetic operations and / or an arithmetic processor for performing arithmetic operations.

[0108] The example 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 example embodiments that include multiple instances of network nodes, and vice versa.

[0109] Those skilled in the art will readily understand that the exemplary embodiments described above can be practiced with different sequences of processes and / or with hardware components in configurations different from the disclosed configuration. Therefore, while 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. An apparatus (10) for restoring multicast / broadcast services, comprising: Components for detecting restarts of multicast / broadcast user plane functions that support packet forwarding control protocol sessions for multicast / broadcast sessions; as well as The component for recreating the packet forwarding control protocol session for the multicast / broadcast session includes: Components for providing addressing information used prior to the restart of the multicast / broadcast user plane function for delivering data of the multicast / broadcast session to the multicast / broadcast user plane function, and for instructing the multicast / broadcast user plane function to use the addressing information for the multicast / broadcast session. The addressing information is provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

2. The apparatus (10) of claim 1, wherein when the multicast / broadcast user plane function uses multicast transmission to send the data, the addressing information includes a low-layer source-specific multicast address and a Public Packet Radio Service Tunneling Protocol (PPP) user plane tunnel endpoint identifier, and the low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier are provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

3. The apparatus (10) according to any one of claims 1 to 2, wherein, for each respective destination endpoint, when the data is to be transmitted to the respective destination endpoint using unicast transmission by the multicast / broadcast user plane function, the addressing information includes a destination address and a General Packet Radio Services Tunneling Protocol user plane tunnel endpoint identifier.

4. The apparatus (10) according to any one of claims 1 to 3, wherein when the data is to be received by the multicast / broadcast user plane function using unicast transmission, the addressing information includes a unicast ingress tunnel address, which is provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function; or When the multicast / broadcast user plane function uses multicast transmission to receive the data, the addressing information includes a multicast address.

5. The apparatus (10) according to any one of claims 1 to 4, wherein the components for providing addressing information and indicating the multicast / broadcast user plane functions include: A component used to send the information and the indication in a Packet Forwarding Control Protocol session establishment request.

6. The apparatus (10) of claim 5, wherein the Packet Forwarding Control Protocol (PTP) session establishment request includes a recovery flag configured to indicate that the PTP session establishment request is to restore an existing PTP session of multicast / broadcast service.

7. The apparatus (10) according to any one of claims 2 to 5, further comprising: Components for receiving new unicast ingress tunnel addresses in responses from the multicast / broadcast user plane functions; as well as A component for redirecting the multicast / broadcast service session to the new unicast ingress tunnel address.

8. An apparatus for restoring multicast / broadcast services, comprising: Components used to restart multicast / broadcast user plane functions; as well as A component for receiving a request from a multicast / broadcast session management function, the request being for establishing a packet forwarding control protocol session for a multicast / broadcast session, the component for receiving the request comprising: A component for receiving addressing information, the addressing information including an address in the address range of the device for data delivery of the multicast / broadcast session, wherein the addressing information was used prior to the restart of the multicast / broadcast user plane function and was received prior to the restart of the multicast / broadcast user plane function; as well as A component for using the addressing information in the broadcast / multicast session.

9. The apparatus according to claim 8, further comprising: A component for sending a response to the multicast / broadcast session management function indicating whether the addressing information is being used.

10. The apparatus according to any one of claims 8 to 9, wherein the addressing information includes a unicast ingress tunnel address when the unicast transmission should be used to receive data.

11. The apparatus of any one of claims 8 to 10, wherein the request includes a Packet Forwarding Control Protocol (CTP) session establishment request, the CTP session establishment request including a recovery flag configured to indicate that the CTP session establishment request is to restore a CTP session of an existing multicast / broadcast service session.

12. The apparatus according to any one of claims 8 to 11, wherein the addressing information includes a unicast ingress tunnel address, and the apparatus further comprises: A component used to determine whether the unicast ingress tunnel address has been assigned or is no longer available for assignment; A component for allocating a new unicast ingress tunnel address if the unicast ingress tunnel address has already been allocated or is no longer available for allocation; as well as A component for providing the new unicast ingress tunnel address to the multicast / broadcast session management function if the unicast ingress tunnel address has already been allocated or is no longer available for allocation.

13. The apparatus of any one of claims 8 to 12, wherein the addressing information includes a low-layer source-specific multicast address and a Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier, the apparatus further comprising: Components used to determine whether the low-layer source-specific multicast address and the Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier have been assigned or are no longer available for assignment; If the lower-layer source-specific multicast address and the public general packet radio service tunneling protocol user plane tunnel endpoint identifier have been allocated or are no longer available for allocation, then allocate a new lower-layer source-specific multicast address and a public general packet radio service tunneling protocol user plane tunnel endpoint identifier. as well as If the low-layer source-specific multicast address and the PPP Tunneling Protocol user plane tunnel endpoint identifier have already been assigned or are no longer available for assignment, then the new low-layer source-specific multicast address and PPP Tunneling Protocol user plane tunnel endpoint identifier are provided to the multicast / broadcast session management function.

14. A method for restoring multicast / broadcast service, comprising: Detect (210) the restart of the multicast / broadcast user plane function, which supports packet forwarding control protocol sessions for multicast / broadcast sessions; as well as Re-create (215) the packet forwarding control protocol session for the multicast / broadcast session, the re-creation including: Addressing information is provided that is used prior to the restart of the multicast / broadcast user plane function for delivering data of the multicast / broadcast session to the multicast / broadcast user plane function, and instructs the multicast / broadcast user plane function to use the addressing information for the multicast / broadcast session. The addressing information is provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

15. The method of claim 14, wherein when the multicast / broadcast user plane function uses multicast transmission to send the data, the addressing information includes a low-layer source-specific multicast address and a Public Packet Radio Service Tunneling Protocol (PPP) user plane tunnel endpoint identifier, and the low-layer source-specific multicast address and PPP user plane tunnel endpoint identifier are provided by the multicast / broadcast session prior to the restart of the multicast / broadcast user plane function.

16. The method of any one of claims 14 to 15, wherein, for each respective destination endpoint, when the data is to be transmitted to the respective destination endpoint using unicast transmission by the multicast / broadcast user plane function, the addressing information includes a destination address and a General Packet Radio Services Tunneling Protocol user plane tunnel endpoint identifier (220).

17. The method according to any one of claims 14 to 16, wherein when the multicast / broadcast user plane function uses unicast transmission to receive the data, the addressing information includes a unicast ingress tunnel address, which is provided by the multicast / broadcast session (225) prior to the restart of the multicast / broadcast user plane function; or When the multicast / broadcast user plane function uses multicast transmission to receive the data, the addressing information includes a multicast address.

18. The method according to any one of claims 14 to 17, wherein providing the addressing information and instructing the multicast / broadcast user plane function comprises: The addressing information and indication are sent in the Packet Forwarding Control Protocol session establishment request.

19. The method of claim 18, wherein the Packet Forwarding Control Protocol (CTP) session establishment request includes a recovery flag configured to indicate that the CTP session establishment request is to restore an existing CTP session of multicast / broadcast service.

20. The method according to any one of claims 15 to 19, further comprising: Receive the new unicast ingress tunnel address from the response of the multicast / broadcast user plane function; as well as The multicast / broadcast service session is redirected to the new unicast ingress tunnel address.

21. The method according to any one of claims 15 to 20, further comprising: Receive a new low-layer source-specific multicast address and a Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier in the response from the multicast / broadcast user plane function; as well as Provide each access-side destination with the new low-layer source-specific multicast address and the Public General Packet Radio Service Tunneling Protocol user plane tunnel endpoint identifier received from the multicast / broadcast user plane function.

22. A method for restoring multicast / broadcast services, comprising: Restart the multicast / broadcast user plane functionality; as well as Receive a request from the multicast / broadcast session management function, the request being used to establish a packet forwarding control protocol session for the multicast / broadcast session, the receiving including: Receive addressing information, the addressing information including an address in the address range of the means for data delivery of the multicast / broadcast session, wherein the addressing information was used and received prior to the restart of the multicast / broadcast user plane function; as well as The addressing information is used for the broadcast / multicast session.

23. The method of claim 22, further comprising: Send a response to the multicast / broadcast session management function, the response indicating whether the addressing information is used.

24. The method of any one of claims 22 to 23, wherein the request includes a Packet Forwarding Control Protocol (CTP) session establishment request, the CTP session establishment request including a recovery flag configured to indicate that the CTP session establishment request is to restore a CTP session of an existing multicast / broadcast service session.

Images