Tunnel reuse for multicast and broadcast services

Abstract

Methods, apparatuses, and systems are described for efficient reuse of multicast or shared tunnels for implementing multicast and broadcast services. In one example aspect, a method of wireless communication includes receiving, by a network node in a core network, information from a first access node requesting a multicast tunnel associated with a multicast and broadcast service, and sending, by the network node, information to the first access node about a shared tunnel associated with the multicast and broadcast service that has been established for a second access node.

Description

Technical Field

[0001] This patent application is generally directed to wireless communications. Background Art

[0002] Mobile communications technology is driving the world toward an increasingly interconnected and networked society. Rapid growth in mobile communications and technological advancements are driving greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectrum efficiency, and latency, are also crucial to meeting the demands of various communication scenarios. Various technologies are being explored, including new approaches to providing higher quality of service, longer battery life, and improved performance. Summary of the Invention

[0003] This patent application describes, inter alia, techniques related to efficiently reusing existing multicast or shared tunnels created for access nodes sharing the same user plane resources, thereby conserving network resources and reducing signaling overhead.

[0004] In one example aspect, a wireless communication method is disclosed. The method includes: receiving, by a network node in a core network, information requesting a multicast tunnel associated with a multicast and broadcast service from a first access node; and sending, by the network node, to the first access node information regarding a shared tunnel associated with the multicast and broadcast service that has been established for a second access node.

[0005] In another example aspect, a wireless communication method is disclosed. The method includes: sending, by an access node, information requesting a multicast tunnel associated with a multicast and broadcast service to a network node in a core network. The method includes: receiving, by the access node, information regarding a shared tunnel associated with the multicast and broadcast service that has been established for a neighboring access node. The method also includes: sending, by the access node, a response to the network node indicating whether the shared tunnel can be used by the access node for the multicast and broadcast service.

[0006] In another example aspect, a wireless communication method is disclosed. The method includes: sending, by an access node, information requesting a shared tunnel associated with a multicast and broadcast service to a network node in a core network. The method includes: receiving, by the access node, an indicator from the network node indicating establishment of the shared tunnel associated with the multicast and broadcast service. The method also includes: sending, by the access node, information regarding the shared tunnel associated with the multicast and broadcast service to a neighboring access node.

[0007] In another exemplary aspect, a communication device is disclosed, wherein the device includes a processor configured to implement the above method.

[0008] In yet another exemplary aspect, a computer program storage medium is disclosed. The computer program storage medium includes code stored thereon. When executed by a processor, the code causes the processor to implement the described method.

[0009] These and other aspects are described throughout this application. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 An example architecture of a fifth generation (5G) system is shown.

[0011] Figure 2 An example architecture for providing multicast and broadcast services is shown.

[0012] Figure 3 An example deployment of a 5G system according to the present technology is shown.

[0013] Figure 4A A conventional 5G network deployment for multicast and broadcast service (MBS) is shown.

[0014] Figure 4B An example 5G network deployment for MBS according to the present technology is shown.

[0015] Figure 5 is a flowchart representation of a wireless communication method according to the present technology.

[0016] Figure 6 is a flowchart representation of a wireless communication method according to the present technology.

[0017] Figure 7 is a flowchart representation of a wireless communication method according to the present technology.

[0018] Figure 8 An example of a wireless communication system is shown in which the technology according to one or more embodiments of the present technology can be applied.

[0019] Figure 9 is a block diagram representation of a portion of a wireless station in accordance with one or more embodiments of the present technology. DETAILED DESCRIPTION

[0020] Section headings are used in this application only to improve readability and do not limit the scope of the embodiments and techniques disclosed in each section to that section. Certain features are described using examples of fifth-generation (5G) wireless protocols. However, the applicability of the disclosed techniques is not limited to only 5G wireless systems.

[0021] In telecommunications, 5G is the fifth-generation technology standard for cellular networks that provide connectivity for wireless communication devices. 5G communication systems offer many network capabilities. Figure 1An example architecture 100 of a 5G system is shown. The illustrated architecture 100 includes the following network functions:

[0022] 1. Access and Mobility Management Function (AMF) 101. AMF 101 is responsible for user equipment (UE) mobility management, reachability management, and / or connection management. The AMF terminates the Radio Access Network (RAN) Control Plane (CP) N2 interface and the Non-Access Stratum (NAS) N1 interface. It also assigns the Session Manager (SM) NAS to the appropriate Session Management Function (SMF) via the N11 interface.

[0023] 2. Session Management Function (SMF) 103. SMF 103 is responsible for UE Internet Protocol (IP) address allocation and management, selection and control of User Plane (UP) functions, and / or Protocol Data Unit (PDU) connection management.

[0024] 3. User Plane Function (UPF) 105. The UPF 105 is the anchor point for intra-RAT / inter-RAT mobility and the external PDU session point for interconnection with the data network. The UPF also routes and forwards data packets as instructed by the SMF. When the anchor point is in idle mode, the UPF 105 buffers downlink data.

[0025] 4. Unified Data Management (UDM) 107. The UDM 107 manages the UE's subscription profile. Subscription data includes data for mobility management (e.g., restricted areas) and session management (e.g., quality of service profile for each slice per data network name). Subscription data also includes slice selection parameters, which are used by the AMF to select the appropriate SMF 103. The AMF 101 and SMF 103 obtain subscription data from the UDM 107. The subscription data is stored in a unified data repository (UDR) (not shown). The UDM 107 uses this data upon receiving a request from the AMF 101 or SMF 103.

[0026] 5. Policy Control Function (PCF) 109. PCF 109 generates policies for managing network behavior based on subscriptions and instructions from Application Function (AF) 111. It also provides policy rules to CP functions (e.g., AMF 101 and / or SMF 103) for execution. PCF can access UDR to retrieve policy data.

[0027] 6. Network Open Function (NEF) (not shown). NEF is optionally deployed to exchange information between the 5G core network (also known as 5GC) and external third parties. In this case, AF 111 can store application information in UDR via NEF.

[0028] With the development of 5G technology, 5G communication systems can provide multicast broadcast services for different businesses related to public safety, autonomous driving and / or the Internet of Things (IoT). Figure 2 An example architecture for providing multicast and broadcast services is shown. The illustrated architecture 200 includes network functions such as a multicast / broadcast SMF (MB-SMF) 203 and / or a multicast / broadcast UPF (MB-UPF) 205, which are enhanced to support multicast / broadcast services. The architecture 200 also includes the following network functions:

[0029] 1. Multicast / Broadcast Service Function (MBSF) 207. MBSF 207 is a new network function used to manage the signaling of service layer capabilities and provides an interface to application servers or content providers.

[0030] 2. Multicast / Broadcast Service User Plane (MBSU) 209. MBSU 209 is a new entity used to manage payload data of service layer capabilities. MBSU 209 can be an independent entity or collocated with MBSF or MB-UPF.

[0031] In addition, new architectures and features of base stations (also known as gNBs) have been introduced into 5G communication systems. For example, compared to the X2 interface between base stations (also known as eNBs) in LTE communication systems, the interface between different gNBs is called the Xn interface. Furthermore, the gNB can be divided into two parts: the centralized unit (CU) and the distributed unit (DU). The gNB-CU can be further divided into two parts: the control plane (CP) CU and the user plane (UP) CU. The interface between the gNB-CU and the gNB-DU is called the F1 interface, while the interface between the gNB-CU-CP and the gNB-CU-UP is called the E1 interface.

[0032] The introduction of CU / DU splitting and CP-UP separation allows for different variations in deployment scenarios in 5G systems. Figure 3 An example deployment of a 5G system according to the present technology is shown. In some embodiments, when the CU-CP entities 303a, 303b, 303c are physically distributed, the pool of logical CU-UP entities can be physically located in the same centralized location 301. With such a deployment, handover can be performed with the source and target logical UP entities within the same physical centralized UP entity 301. This provides the possibility of optimizing the inter-node handover process by: (1) avoiding the need to change the NG-U tunnel towards the core network, and (2) avoiding the need for data forwarding from the source UP entity to the target UP entity.

[0033] For example, Figure 3As shown in FIG, the UE can perform handover from the source gNB (311a and 311b) to the target gNB (313a and 313b), where the source CU-UP (311a) and the target CU-UP (313a) are within the same physical centralized UP entity 301. The physical centralized UP 301 does not require changes to the DL UP termination of the NG interface, and data forwarding can be classified within the physical centralized UP entity 301.

[0034] Figure 4A FIG4 shows a conventional 5G network deployment 400 for multicast and broadcast service (MBS). An MBS includes one or more MBS quality of service (QoS) flows. Figure 4A As shown, the 5GC (e.g., UPF) establishes an N3 tunnel with each new generation radio access network (NG-RAN) node. When the network allows the UE to join an MBS service that includes one or more MBS QoS flows, the UE can reside on a cell belonging to NG-RAN1. If the MBS service has been established for the NG-RAN1 node, the NG-RAN1 node already has a multicast / shared N3 tunnel for transmitting user data for the MBS service. The 5GC does not need to establish the N3 tunnel for the UE again. However, if the multicast / shared N3 tunnel has not been established for the NG-RAN1 node, the 5GC establishes a tunnel so that user data for the MBS service can be sent from the network node (e.g., UPF) to the UE. In this deployment, the 5GC needs to establish a separate N3 tunnel for each NG-RAN node that provides MBS services. Note that one N3 tunnel can serve one or more MBSs.

[0035] Figure 4B An example 5G network deployment 450 for MBS according to the present technology is shown. In this deployment, CU / DU splitting and CP / UP separation are adopted so that NG-RAN nodes share user plane resources (e.g., Figure 3 Only one N3 tunnel is required between the 5GC (e.g., UPF) and the NG-RAN node. If a multicast / shared N3 tunnel has already been established for one NG-RAN node (e.g., NG-RAN 1), there is no need to re-establish additional N3 tunnels for other NR-RAN nodes.

[0036] use Figure 4BThe example deployment shown requires fewer N3 tunnels to be established. However, currently, the 5GC does not know which NG-RAN nodes share the same user plane resources. Therefore, the 5GC can redundantly establish N3 tunnels even when unnecessary. This patent application discloses techniques that can be implemented in various embodiments to allow NG-RAN nodes sharing the same user plane resources to reuse existing N3 tunnels (if any), thereby reducing signaling consumption and saving network resources. Some examples of the disclosed techniques are further described in the following example embodiments.

[0037] Example 1

[0038] In some embodiments, a UE may reside on a cell belonging to a first access node (e.g., NG-RAN1). The UE is allowed to join a specific multicast and broadcast service (MBS) that includes one or more MBS QoS flows. A network node (e.g., UPF) within the 5GC receives a request from the first access node and decides whether a shared channel needs to be established in the first access node for one or more QoS flows of the UE.

[0039] If a shared tunnel for one or more QoS flows of MBS has already been established for the first access node, the network node may inform the first access node (e.g., NG-RAN1) to use the existing shared tunnel. However, if a shared tunnel has not yet been established for the first access node, but there is another shared tunnel established for the second access node (e.g., NG-RAN2), the network node may send such information to the first access node.

[0040] Subsequently, the network node may receive information from the first access node that allows the network node to decide whether it is necessary to establish a new multicast / shared channel. For example, the information may indicate whether an existing shared tunnel for the second access node (e.g., NG-RAN2) can be used by the first access node (e.g., NG-RAN1). The information may be a simple indicator with a binary value indicating whether the existing tunnel is available. The information may also indicate whether the first and second access nodes share the same user plane resources for one or more QoS flows. If the two access nodes share the same user plane resources, the existing tunnel established for the second access node can be reused by the first access node. The network node can decide whether to establish a new shared channel for the first access node based on this information.

[0041] Figure 55 is a flowchart representation of a wireless communication method 500 according to the present technology. The method 500 includes, at operation 510, receiving, by a network node (e.g., UPF) in a core network (e.g., 5GC), information requesting a multicast tunnel associated with a multicast and broadcast service from a first access node. The method 500 also includes, at operation 520, sending, by the network node, to the first access node information regarding a shared tunnel associated with the multicast and broadcast service that has been established for a second access node (e.g., NG-RAN2).

[0042] In some embodiments, the shared tunnel is associated with at least one other multicast and broadcast service (i.e., the shared tunnel can serve one or more MBSs). In some embodiments, the multicast tunnel is used for one or more quality of service (QoS) flows of the multicast and broadcast service. In some embodiments, the method includes: determining, by the network node, whether to establish a multicast tunnel associated with the multicast and broadcast service for the first access node.

[0043] In some embodiments, the method also includes receiving, by the network node, a response from the first access node, indicating whether a shared tunnel associated with the multicast and broadcast service or a QoS flow of the multicast and broadcast service can be used by the first access node, and establishing, by the network node, a separate tunnel for the first access node when determining, based on the response, that the shared tunnel cannot be used by the first access node.

[0044] In some embodiments, whether the shared tunnel can be used by the first access node is determined based on whether the first access node and the second access node share the same user plane resources for multicast and broadcast services or a QoS flow for multicast multicast and broadcast services.

[0045] Example 2

[0046] In some embodiments, a UE may reside on a cell belonging to a first access node (e.g., NG-RAN1). The UE is allowed to join a specific multicast and broadcast service that includes one or more MBS QoS flows. The first access node sends a request to a network node (e.g., UPF) within the 5GC to request a multicast / shared channel for one or more MBS QoS flows.

[0047] If a shared tunnel for one or more QoS flows of MBS has already been established for the first access node, the network node may notify the first access node (e.g., NG-RAN1) to use the existing shared tunnel. However, if a shared tunnel has not yet been established for the first access node, but there is another shared tunnel established for the second access node (e.g., NG-RAN2), the first access node may receive information from the network node instructing it to do so.

[0048] For example, the network node may send information about the established shared tunnel information (such as the MBS service identifier, the tunnel endpoint identifier (TEID) of the tunnel, and / or the node identity of the second access node (e.g., NG-RAN2)) to the first access node (e.g., NG-RAN1). After receiving this information, the first access node determines whether the second access node shares the same user plane resources for this particular MBS. If the same user plane resources are used, the first access node may determine that the existing shared channel can be reused. The first access node then notifies the network node in the 5GC whether it can reuse the established shared tunnel.

[0049] If the established shared tunnel cannot be reused by the first access node, the network node in the core network may establish a new shared tunnel for one or more QoS flows of the MBS of the first access node.

[0050] Figure 6 6 is a flowchart representation of a wireless communication method 600 according to the present technology. The method 600 includes, at operation 610, sending information by an access node (e.g., NG-RAN1) to a network node (e.g., UPF) in a core network (e.g., 5GC) requesting a multicast tunnel associated with a multicast and broadcast service. The method 600 includes, at operation 620, receiving information by the access node about a shared tunnel associated with the multicast and broadcast service that has been established for a neighboring access node (e.g., NG-RAN2). The method 600 also includes, at operation 630, sending a response by the access node to the network node indicating whether the shared tunnel can be used by the access node for the multicast and broadcast service.

[0051] In some embodiments, the shared tunnel is associated with at least one other multicast and broadcast service (i.e., the shared tunnel can serve one or more MBSs). In some embodiments, the multicast tunnel is used for one or more quality of service (QoS) flows of the multicast and broadcast service. In some embodiments, the method includes determining whether the shared tunnel can be used by the access node based on whether the access node and a neighboring access node share the same user plane resources for the multicast and broadcast service or one or more QoS flows of the multicast and broadcast service.

[0052] In some embodiments, the information about a shared tunnel associated with a multicast and broadcast service includes a tunnel endpoint identifier for the shared tunnel. In some embodiments, the information about a shared tunnel associated with a multicast and broadcast service includes an identifier for at least one of one or more quality of service (QoS) flows associated with the multicast and broadcast service. In some embodiments, the information about a shared tunnel for a multicast and broadcast service includes an identifier identifying an access node for which the tunnel was established.

[0053] Example 3

[0054] In some embodiments, a UE may reside on a cell belonging to a first access node (e.g., NG-RAN1). The UE is allowed to join a specific multicast and broadcast service (MBS) that includes one or more MBS QoS flows. A network node (e.g., UPF) within the 5GC receives a request from the first access node and decides to establish a shared channel for the one or more QoS flows of the UE in the first access node.

[0055] When no existing tunnel is established for any access node, the network node in the 5GC can establish a multicast / shared tunnel for one or more QoS flows of the MBS service. The network node can then notify the first access network that the multicast / shared channel has been established.

[0056] In some embodiments, upon receiving the notification from the network node, the first access network may send information about the newly established multicast / shared tunnel (e.g., the TEID of the shared tunnel, the node ID of the first access node, and / or the MBS QoS flow ID) to one or more neighboring access nodes that share the same user plane resources. In this way, the neighboring access nodes are aware of the existence of this multicast / shared tunnel. When other UEs residing in the neighboring access nodes are allowed to join the same MBS and request an additional tunnel, the neighboring access nodes can reuse this existing tunnel without any signaling exchange with the network, thereby reducing or eliminating any signaling delay and overhead when enabling MBS.

[0057] Figure 7 7 is a flowchart representation of a wireless communication method 700 according to the present technology. The method 700 includes, at operation 710, sending, by an access node, information requesting a shared tunnel associated with a multicast and broadcast service to a network node in a core network. The method 700 includes, at operation 720, receiving, by the access node, an indicator from the network node indicating establishment of a shared tunnel associated with the multicast and broadcast service. The method 700 also includes, at operation 730, sending, by the access node, information regarding the shared tunnel associated with the multicast and broadcast service to a neighboring access node.

[0058] In some embodiments, the shared tunnel is associated with at least one other multicast and broadcast service (i.e., the shared tunnel can serve one or more MBSs). In some embodiments, the tunnel is used for one or more quality of service (QoS) flows of the multicast and broadcast service. In some embodiments, the method includes: receiving, by the access node, a notification from a neighboring access node indicating whether the tunnel can be used by the neighboring access node.

[0059] In some embodiments, the information about a shared tunnel associated with a multicast and broadcast service includes a tunnel endpoint identifier for the tunnel. In some embodiments, the information about a shared tunnel associated with a multicast and broadcast service includes an identifier for a Quality of Service (QoS) flow associated with the multicast and broadcast service. In some embodiments, the information about a shared tunnel for a multicast and broadcast service includes an identifier identifying an access node for which the tunnel was established.

[0060] Example 4

[0061] In some embodiments, when a UE resides in a cell belonging to a first access node (e.g., NG-RAN1), the UE joins a specific multicast and broadcast service (MBS). The UE receives user data for the MBS via a multicast / shared tunnel established by the core network. When the UE moves to another cell belonging to a second access node (e.g., NG-RAN2), a handover occurs. Return to Reference Figure 4B When NG-RAN1 and NG-RAN2 share the same user plane resources (e.g., CU-UP), there is no need to establish a new tunnel for one or more QoS flows of MBS during handover. The UE can simply reuse the same tunnel after handover without incurring signaling overhead.

[0062] Figure 8 An example of a wireless communication system 800 in which techniques according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 800 may include one or more base stations (BSs) 805a, 805b, one or more wireless devices 810a, 810b, 810c, 810d, and a core network 825. The base stations 805a, 805b may provide wireless services to the wireless devices 810a, 810b, 810c, and 810d in one or more wireless sectors. In some embodiments, the base stations 805a, 805b include directional antennas that generate two or more directional beams to provide wireless coverage in different sectors.

[0063] The core network 825 can communicate with one or more base stations 805a and 805b. The core network 825 provides connectivity to other wireless communication systems and wired communication systems. The core network can include one or more service subscription databases to store information related to subscribed wireless devices 810a, 810b, 810c, and 810d. The first base station 805a can provide wireless services based on a first radio access technology, while the second base station 805b can provide wireless services based on a second radio access technology. Depending on the deployment scenario, base stations 805a and 805b can be quasi-co-located or installed separately on-site. The wireless devices 810a, 810b, 810c, and 810d can support a variety of different radio access technologies. The techniques and embodiments described herein can be implemented by a base station of the wireless devices described herein.

[0064] Figure 9 is a block diagram representation of a portion of a wireless site according to one or more embodiments of the present technology. A wireless site 905, such as a base station or a wireless device (or UE), may include processor electronics 910, such as a microprocessor that implements one or more wireless technologies presented in this application. The wireless site 905 may include transceiver electronics 915 for sending and / or receiving wireless signals via one or more communication interfaces (e.g., antenna 920). The wireless site 905 may include other communication interfaces for sending and receiving data. The wireless site 905 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, the processor electronics 910 may include at least a portion of the transceiver electronics 915. In some embodiments, the wireless site 905 is used to implement at least some of the disclosed techniques, modules, or functions. In some embodiments, the wireless site 905 may be configured to perform the methods described herein.

[0065] It should be understood that the present application discloses techniques that can be embodied in various embodiments to achieve efficient reuse of existing multicast / shared tunnels when access nodes share the same user plane resources. The disclosed embodiments and other embodiments, modules, and functional operations described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware (including the structures disclosed in this application and their equivalents), or in a combination of one or more thereof. The disclosed embodiments and other embodiments can be implemented as one or more computer program products (i.e., one or more modules of computer program instructions encoded on a computer-readable medium) for execution by a data processing apparatus or for controlling the operation of the data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition that effects a machine-readable propagated signal, or a combination of one or more thereof. The term "data processing apparatus" encompasses all apparatuses, devices, and machines for processing data, such as a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more thereof. A propagated signal is an artificially generated signal, eg, a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

[0066] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files that store one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on one computer or on multiple computers that are located at one location or distributed across multiple locations and interconnected by a communications network.

[0067] The processes and logic flows described herein can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0068] By way of example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. Typically, a processor will receive instructions and data from read-only memory or random access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operatively coupled to one or more mass storage devices (e.g., magnetic, magneto-optical, or optical disks) for storing data, to receive data from or transmit data to the mass storage devices, or both. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include various forms of nonvolatile memory, media, and storage devices, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory can be supplemented by, or incorporated into, special-purpose logic circuitry.

[0069] Although this patent application contains many details, these should not be interpreted as limitations on the scope of any invention or the scope of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features described in this patent application in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable subcombination. Furthermore, although the features described above may be described as working in certain combinations, and even initially claimed as such, in some cases one or more features from the combination may be deleted from the combination, and the combination may involve subcombinations or variations of subcombinations.

[0070] Similarly, while operations are described in a particular order in the drawings, this should not be understood as requiring that these operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, in order to achieve the desired results. Furthermore, the separation of various system components in the embodiments described in this patent application should not be understood as requiring such separation in all embodiments.

[0071] Only a few implementations and examples are described, and other implementations, enhancements, and variations can be made based on what is described and illustrated in this patent application.

Claims

1. A wireless communication method, comprising: Receiving, by a network node in the core network, information requesting a multicast tunnel associated with a multicast and broadcast service from a first access node in a first radio access network RAN; as well as sending, by the network node to the first access node, information about a shared tunnel associated with the multicast and broadcast service that has been established for a neighboring second access node in a second RAN, The first access node and the adjacent second access node share the same user plane resources for the multicast and broadcast services.

2. The method according to claim 1, wherein The shared tunnel is associated with at least one other multicast and broadcast service.

3. The method according to claim 1, wherein The multicast tunnel is used for one or more Quality of Service (QoS) flows of the multicast and broadcast services.

4. The method according to claim 1, comprising: The network node determines whether to establish the multicast tunnel associated with the multicast and broadcast service for the first access node.

5. The method according to claim 3, comprising: receiving, by the network node, a response from the first access node, the response indicating whether the shared tunnel associated with the multicast and broadcast service or the one or more QoS flows of the multicast and broadcast service can be used by the first access node; as well as When it is determined based on the response that the shared tunnel cannot be used by the first access node, a separate tunnel is established by the network node for the first access node.

6. The method according to claim 5, wherein: Whether the shared tunnel can be used by the first access node is determined based on whether the first access node and the neighboring second access node share the same user plane resources for the multicast and broadcast service or the one or more QoS flows for the multicast and broadcast service.

7. The method according to claim 3, wherein: The information about the shared tunnel associated with the multicast and broadcast service includes an identifier of at least one of the one or more QoS flows associated with the multicast and broadcast service.

8. The method according to claim 1, wherein The information about the shared tunnel for the multicast and broadcast service includes a tunnel endpoint identifier or an identifier identifying an access node for which the tunnel is established.

9. A wireless communication method, comprising: A first access node in a first radio access network RAN ​​sends information requesting a multicast tunnel associated with a multicast and broadcast service to a network node in a core network; receiving, by the first access node, information about a shared tunnel associated with the multicast and broadcast service that has been established for a neighboring second access node in a second RAN, wherein the first access node and the neighboring second access node share the same user plane resources for the multicast and broadcast service; as well as A response is sent by the first access node to the network node, the response indicating whether the shared tunnel can be used by the first access node for the multicast and broadcast service.

10. The method according to claim 9, wherein: The shared tunnel is associated with at least one other multicast and broadcast service.

11. The method according to claim 9, wherein The multicast tunnel is used for one or more Quality of Service (QoS) flows of the multicast and broadcast services.

12. The method according to claim 11, further comprising: Whether the shared tunnel can be used by the first access node is determined based on whether the first access node and the neighboring second access node share the same user plane resources for the multicast and broadcast service or the one or more QoS flows for the multicast and broadcast service.

13. The method according to claim 11, wherein The information about the shared tunnel associated with the multicast and broadcast service includes an identifier of at least one of the one or more QoS flows associated with the multicast and broadcast service.

14. The method according to claim 9, wherein The information about the shared tunnel for the multicast and broadcast service includes a tunnel endpoint identifier or an identifier identifying an access node for which the tunnel is established.

15. A wireless communication method, comprising: Sending, by a second access node in the second radio access network RAN, to a network node in the core network, information requesting a shared tunnel associated with the multicast and broadcast service; receiving, by the second access node from the network node, an indicator indicating establishment of the shared tunnel associated with the multicast and broadcast service; as well as Information about the shared tunnel associated with the multicast and broadcast service is sent by the second access node to a neighboring first access node in the first RAN, wherein the neighboring first access node and the second access node share the same user plane resources for the multicast and broadcast service.

16. The method according to claim 15, wherein The shared tunnel is associated with at least one other multicast and broadcast service.

17. The method according to claim 15, wherein: The shared tunnel is used for one or more Quality of Service (QoS) flows of the multicast and broadcast services.

18. The method according to claim 15, comprising: A notification is received by the second access node from the neighboring first access node indicating whether the tunnel can be used by the neighboring first access node.

19. The method according to claim 17, wherein The information about the shared tunnel associated with the multicast and broadcast service includes an identifier of at least one of the one or more QoS flows associated with the multicast and broadcast service.

20. The method according to claim 15, wherein The information about the shared tunnel for the multicast and broadcast service includes a tunnel endpoint identifier or an identifier identifying an access node for which the tunnel is established.

21. A wireless communication device comprising a processor and non-transitory memory having instructions thereon, wherein: When the instructions are executed by the processor, the processor is caused to implement the method according to any one of claims 1 to 20.

22. A computer readable medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method of any one of claims 1 to 20.

Images