Method and system for multicast service and broadcast service establishment in a wireless communication network

Abstract

The present disclosure describes methods and systems for establishing multicast services and broadcast services. In one example aspect, the method includes adding a first identifier to user data of a data service flow and transmitting the data service flow with the first identifier over a unicast tunnel upon determining that flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier, or adding a second identifier to the user data of the data service flow and transmitting the data service flow with the second identifier over a multicast shared tunnel upon determining that the flow establishment configuration information includes the multicast broadcast service (MBS) flow identifier and a corresponding multicast shared tunnel.

Description

Technical Field

[0001] This patent document generally relates to wireless communication. Background Technology

[0002] Mobile communication technology is leading the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in mobile communications have resulted in greater demands for capacity and connectivity. Other factors, such as energy consumption, equipment cost, spectrum efficiency, and latency, are also important for meeting the needs of various communication scenarios. Various technologies are currently under discussion, including new ways to provide higher service quality, longer battery life, and improved performance. Summary of the Invention

[0003] Among other things, this patent document describes techniques for establishing multicast and broadcast services.

[0004] In one aspect, a data communication method includes: a first communication node determining whether to set up one or more data service flows for a mobile device; when determining to set up the one or more data service flows, transmitting flow establishment configuration information including a unicast flow identifier and a corresponding unicast tunnel to a second communication node; when determining that the flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier and a corresponding multicast shared tunnel, adding a first identifier to the user data of the data service flow, and the first communication node transmitting the data service flow having the first identifier to the second communication node through the corresponding unicast tunnel; and when determining that the flow establishment configuration information includes the multicast broadcast service (MBS) flow identifier and the corresponding multicast shared tunnel, adding a second identifier to the user data of the data service flow, and the first communication node transmitting the data service flow having the second identifier to the second communication node through the corresponding multicast shared tunnel.

[0005] In another aspect, a data communication method includes: a second communication node receiving stream establishment configuration information from a first communication node for transmitting a data service stream to a mobile device; the second communication node determining, based on the stream establishment configuration information, whether to receive user data of the data service stream via a unicast tunnel or a multicast tunnel; and the second communication node receiving the user data of the data service stream via the unicast tunnel or the multicast tunnel based on the determination.

[0006] In another aspect, a data communication method includes: a core network determining whether at least one multicast stream has been established in an existing unicast protocol data unit session or a new unicast protocol data unit session; and the core network performing data communication based on the determination using an existing unicast tunnel corresponding to the existing unicast protocol data unit session or a new unicast tunnel corresponding to the new unicast protocol data unit session.

[0007] This document describes these and other aspects. Attached Figure Description

[0008] Figure 1 The architecture of a 5G system based on some example embodiments of the technology disclosed herein is described.

[0009] Figure 2 An enhanced 5G system architecture for providing broadcast / multicast services to user equipment is described based on some example embodiments of the technology disclosed herein.

[0010] Figure 3 Various stages in the process of providing multicast services are described based on some example embodiments of the technology disclosed herein.

[0011] Figure 4 The present disclosure describes a process for establishing a shared tunnel in a 5G system to transmit multicast services, based on some example embodiments of the technology disclosed herein.

[0012] Figure 5 The present disclosure describes a process for transmitting multicast service data from a core network (CN) to a radio access network (NG-RAN) based on some example embodiments of the technology disclosed herein.

[0013] Figure 6 Some example embodiments based on the technology disclosed herein are described, including unicast tunnels and shared tunnels established between a first communication node and a second communication node.

[0014] Figure 7 Examples of processes for wireless communication based on some exemplary embodiments of the technology disclosed herein are described.

[0015] Figure 8 Another example of a process for wireless communication based on some example embodiments of the technology disclosed herein is described.

[0016] Figure 9 Another example of a process for wireless communication based on some example embodiments of the technology disclosed herein is described.

[0017] Figure 10 Wireless communication systems based on some example embodiments of the technology disclosed herein are described.

[0018] Figure 11 A block diagram depicts a portion of a radio system based on some example embodiments of the technology disclosed herein. Detailed Implementation

[0019] Examples using fifth-generation (5G) wireless protocols describe certain characteristics. However, the applicability of the techniques disclosed herein is not limited to 5G wireless systems only.

[0020] 5G systems (5GS) include multicast and broadcast services. One aspect of these services is multicast discovery, as well as the initiation and termination of multicast services. User equipment (UE) can operate simultaneously using unicast (also known as unicast) and multicast services. When a UE moves from one radio access network (RAN) node to another RAN node, service continuity for both broadcast and multicast services is required. This document discloses techniques for providing service continuity for both broadcast and multicast services.

[0021] In some example embodiments, a multicast service is a communication service in which the same service and the same content data are simultaneously provided to a group of authorized UEs (i.e., not all UEs in the multicast coverage are authorized to receive data). A broadcast service is a communication service in which the same service and the same content data are simultaneously provided to all UEs in a geographic area (i.e., all UEs in the broadcast coverage area are authorized to receive data).

[0022] Figure 1 An example architecture 100 for a 5G system is depicted. The 5G system architecture consists of network functions (NF) and other functions described below.

[0023] The Access and Mobility Management Function (AMF) 125 performs functions including UE mobility management, reachability management, connection management, and other functions. The AMF terminates the Radio Access Network Control Plane (RAN CP) interface (also known as the N2 interface 142) and the Non-Access Stratum (NAS) (also known as the N1 interface 137), as well as NAS encryption and integrity protection. The AMF also assigns the Session Management (SM) NAS to the appropriate Session Management Function (SMF) via the N11 interface 127.

[0024] Session Management Function (SMF) 130 includes user equipment (UE) Internet Protocol (IP) address allocation and management, UP function selection and control, PDU connection management, etc.

[0025] The User Plane Function (UPF) 145 is an anchor point for intra / inter-Radio Access Technology (RAT) mobility and an External Protocol Data Unit (PDU) session point for interconnection with data networks. The UPF also routes and forwards packets according to the instructions of the SMF, and buffers downlink (DL) data when the UE is in idle mode.

[0026] The Unified Data Management (UDM) 110 manages the UE's subscription profiles. Subscriptions include data for mobility management (e.g., restricted areas) and session management (e.g., Quality of Service (QoS) profiles per Data Network Name (DNN) per slice). Subscription data also includes slice selection parameters used by the AMF to select the SMF. The AMF and SMF obtain subscriptions from the UDM, and subscription data is stored in the Unified Data Repository (UDR). The UDM uses the data when it receives requests from the AMF or SMF.

[0027] The Policy Control Function (PCF) 115 manages network behavior based on subscriptions and instructions from the Application Function (AF) 120. The PCF provides policy rules enforced by control plane (CP) functions such as the AMF and / or SMF. The PCF accesses the UDR to retrieve policy data.

[0028] Network Open Function (NEF) (not shown) may be included in systems used for exchanging information between the core network (5GC) and external third parties. For example, AF 120 may use NEF to store application information in the UDR.

[0029] Multicast Broadcast Multimedia Service (MBMS) was developed for video broadcasting and streaming services. Since its initial development, the MBMS system has been updated to support new services such as public safety, consumer IoT (CIoT), and vehicle-to-everything (V2X). With the development and maturation of 5GS, 5GS can provide multicast broadcast services for vertical businesses.

[0030] Figure 2 An example of an enhanced 5G system architecture 200 that provides broadcast / multicast services to user equipment 230 is depicted.

[0031] Multicast / Broadcast Service Function (MBSF) 235 is a network function (NF) that handles the signaling portion of service layer capabilities and provides an interface with application server 245. It can be a standalone entity or located in the same location as the MB-SMF.

[0032] The Multicast / Broadcast Service User Plane (MBSU) 240 handles the payload portion of the service layer capabilities and can be a standalone entity or located in the same location as the MBSF or MB-UPF.

[0033] The SMF and UPF can be enhanced to support multicast / broadcast services. The AMF can also be enhanced to make multicast / broadcast service signaling between the RAN / UE and the multicast / broadcast SMF (MB-SMF)225 transparent.

[0034] Figure 3 Examples of the various stages in the process of providing multicast services are depicted.

[0035] In the service subscription phase 310, a subscription is an agreement by which a user agrees to receive (multiple) services provided by the operator. The relationship between the user and the service provider is established during the subscription period. This relationship can be stored statically in a unified data repository (UDR) or dynamically pushed from the MBS server to the relevant PCF.

[0036] During the multicast service initiation phase 320, the MBS server triggers the MBSF to start a session to send multicast data. The MBSF triggers MBS session establishment in 5GS. Session initiation occurs independently of user activation of the service (i.e., a given user can activate the service before or after session initiation). Session initiation is a trigger for establishing bearer resources for MBMS data delivery.

[0037] In PDU session establishment phase 330, the UE can initiate unicast PDU session establishment to retrieve multicast service configuration or set association with MBSF. This can occur before phase 310. The UE can dynamically subscribe to the multicast service via the established PDU session. This phase can also occur after phase 340 if the multicast service begins before the UE joins the multicast service.

[0038] During the multicast service announcement phase 340, the multicast service announcement / discovery mechanism allows users to request or be informed of the range of available multicast services. This announcement is also used to distribute information to users about service parameters required for service activation (e.g., multiple IP multicast addresses) and possibly other service-related parameters (e.g., service start time).

[0039] During the multicast join phase 350, the UE initiates the join process to become a member of the multicast group.

[0040] During the data transmission phase 360, the data is transmitted to the UE.

[0041] Figure 4 An example of a process for establishing a shared tunnel in a 5G system to deliver multicast services is described. In some example embodiments, this process occurs after the UE has already established a PDU session.

[0042] At 410, the UE initiates a unicast PDU session establishment procedure. During this procedure, the UE selects an MBS-SMF that supports both unicast and multicast based on a specific DNN and single network slice selection assistance information (S-NSSAI). Upon completion of the establishment procedure, the UE can retrieve the multicast service configuration.

[0043] At 420, the UE initiates a join request via UP data or NAS message to join the multicast communication service.

[0044] At 430, when the MB-SMF detects a request, it requests the MBSF to authorize the UE. The MBSF checks if the UE is allowed to access the service. If so, the MBSF checks if a multicast context for the multicast group exists (i.e., whether the UE has already joined the multicast group). If no multicast context for the multicast group exists, the SMF creates the multicast context when the first UE joins the multicast group. This check may involve the MBS server, PCF, and / or UDM. The MBS server may store group membership in the UDM or send it to the PCF before 430. The MBSF or MB-SMF can then retrieve the information during the association establishment between the MBSF / MB-SMF and the PCF / UDM. If there is no interaction between the MBSF and the PCF / UDM, the MBSF can retrieve the information from the MB-SMF.

[0045] Figure 5 The present disclosure describes a process for transmitting multicast service data from a core network (e.g., 5GC) to a radio access network (NG-RAN) based on some example embodiments of the technology disclosed herein.

[0046] After a user equipment (e.g., UE) has successfully joined one or more multicast broadcast multimedia service (MBMS) quality of service (QoS) streams (MBMS QoS streams) for MBMS services, the core network (e.g., 5GC) can trigger a stream establishment procedure to establish one or more MBMS QoS streams for that user equipment (e.g., UE).

[0047] In the context of this patent document, the term “Multicast Broadcast Multimedia Service (MBMS)” can be used to refer to “Multicast Broadcast Service (MBS)”, and the two terms are used interchangeably.

[0048] In some embodiments of the present disclosure, the Multicast / Broadcast Service Function (MBSF) can initiate a flow establishment procedure for multicast streams. For each user equipment (UE) that has joined one or more Multicast Broadcast Multimedia Services (MBMS), the MBSF triggers the Multicast / Broadcast Session Management Function (MB-SMF) to establish one or more MBMS QoS streams (i.e., multicast QoS streams) in an existing Protocol Data Unit (PDU) session via a PDU session modification procedure initiated by the core network (e.g., a procedure for modifying a PDU session initiated by the 5GC) or in a new PDU session via a PDU session setup procedure initiated by the core network. These MBMS QoS streams are bound to a unicast tunnel associated with the UE. For example, user data in these QoS streams can be transmitted from the core network (e.g., the 5GC) to the UE via the unicast tunnel.

[0049] When multiple user equipments (UEs) have joined one or more MBMS QoS flows (the same), the core network (e.g., 5GC) can establish unicast tunnels associated with the user equipments to transmit the one or more MBMS QoS flows for each user equipment (e.g., UE).

[0050] In some embodiments of this disclosure, when user data of the one or more MBMS QoS flows is transmitted in multicast mode (via a shared / multicast tunnel), the MBSF also triggers the MB-SMF to establish a shared tunnel for all user equipment (UEs) joining the (same) one or more MBMS QoS flows under the same radio access network (NG-RAN) node. The one or more MBMS QoS flows discussed above will be established in a shared tunnel (i.e., a multicast tunnel associated with the MBMS). When the one or more MBMS QoS flows are configured with a shared tunnel, an MBMS identifier (e.g., TMGI, session ID, special QoS flow ID) different from that of the unicast QoS flows is also configured.

[0051] In some implementations, when user data of one or more MBMS QoS streams is transmitted in multicast mode via a shared tunnel, the one or more QoS streams may be configured with both an MBMS identifier and a shared tunnel.

[0052] In some implementations, when user data of the one or more MBMS QoS streams is transmitted in unicast mode via a unicast tunnel (configured as described above), the one or more QoS streams may not be configured with an MBMS identifier.

[0053] In some embodiments of this disclosure, the one or more MBMS QoS streams bind both a unicast tunnel and a multicast tunnel to each user equipment (UE) that has joined the one or more Multicast Broadcast Multimedia Services (MBMS). When the one or more MBMS QoS streams are established, the one or more MBMS QoS streams bind to a unicast tunnel associated with the UE, and may also bind to a multicast shared tunnel associated with the MBMS. If only the unicast tunnel associated with the UE is available, the user data of the one or more MBMS QoS streams will be transmitted through the unicast tunnel associated with the UE. If both the unicast tunnel associated with the UE and the multicast shared tunnel are available, the user data of the one or more MBMS QoS streams can be transmitted through the shared tunnel instead of the unicast tunnel. In this case, the unicast tunnel may be referred to as a "dummy tunnel" (i.e., no user data is transmitted through this tunnel).

[0054] In some embodiments of the present disclosure, for one or more MBMS QoS flows belonging to a certain MBMS service, if user data of the one or more MBMS QoS flows is transmitted in unicast mode via a unicast tunnel, a QFI (QoS Flow Identifier) ​​can be added to the encapsulation header of each user data packet. If user data is transmitted in multicast mode via a shared tunnel, an MBMS identifier can be added to the encapsulation header of each user data packet.

[0055] In some embodiments of this disclosure, for one or more MBMS QoS flows belonging to a certain MBMS service, their corresponding unicast tunnels (for transmitting user data of the MBMS QoS flows in unicast mode) and QFIs (QoS flow identifiers) are always configured. Only in multicast mode can the MBMS identifier and a shared tunnel (for transmitting user data of the MBMS QoS flows in multicast mode) be configured.

[0056] When the core network (e.g., 5GC) transmits user data for MBMS QoS flows in unicast mode, the core network 5GC will not configure the MBMS identifier and shared tunnel. If the core network 5GC switches from unicast mode to multicast mode and transmits user data for MBMS QoS flows in multicast mode, the core network 5GC additionally configures the MBMS identifier and shared tunnel for the one or more MBMS QoS flows. Conversely, if the MBMS identifier and shared tunnel are removed from the MBMS QoS flow configuration, the MBMS QoS user data is transmitted in unicast mode.

[0057] Figure 6 Some example embodiments based on the technology disclosed herein are described, including unicast tunnels and shared tunnels established between a first communication node and a second communication node.

[0058] The first user equipment UEa has established a unicast PDU session, which includes one or more unicast QoS streams. For example, a first QoS stream identifier QF1 and a second QoS stream identifier QF2 are established in the first unicast PDU session (e.g., PDU session 1), and a first unicast tunnel is included for transmitting user data of the first and second QoS stream identifiers QF1 and QF2.

[0059] After the first user equipment (UEa) has successfully joined the MBMS service, the core network (e.g., 5GC) triggers a flow establishment procedure to establish one or more MBMS QoS flows. Here, the one or more MBMS QoS flows are mapped to the MBMS service. In this example, a third QoS flow identifier, QF3, different from the first and second QoS flow identifiers QF1 and QF2, is assigned to the one or more MBMS QoS flows.

[0060] If the one or more MBMS QoS flows are established in an existing unicast PDU session (e.g., PDU session 1), the identifiers of the one or more MBMS QoS flows are different from the first and second QoS flow identifiers QF1 and QF2. The one or more MBMS QoS flows have the same unicast tunnel as another of the first and second QoS flow identifiers QF1 and QF2. The existing unicast PDU session is already configured in a unicast tunnel (e.g., unicast tunnel 1), and the unicast tunnel can be used for all its QoS flows. In other words, the one or more MBMS QoS flows can be unicast transmitted using the existing unicast tunnel.

[0061] If the one or more MBMS QoS flows are established in a new unicast PDU session (e.g., PDU session 2), the identifier of the new PDU session is different from that of the existing PDU session. The new unicast PDU session is also configured with a new unicast tunnel (e.g., unicast tunnel 2), and the one or more MBMS QoS flows can be unicast transmitted using the new unicast tunnel.

[0062] If the core network (5GC) transmits one or more MBMS QoS flows belonging to a certain MBMS service in multicast mode, the core network can additionally configure a shared (multicast) tunnel for the one or more MBMS QoS flows. The one or more MBMS QoS flows are configured with two tunnels (one unicast tunnel and one multicast tunnel), and the core network (5GC) sends the user data of the one or more MBMS QoS flows to the radio access network (NG-RAN) through the multicast tunnel. In this case, the user data of the one or more MBMS QoS flows is not transmitted through the unicast tunnel; therefore, the unicast tunnel can be referred to as a "dummy tunnel" in this situation. Here, the one or more MBMS QoS flows can also be configured with one or more MBMS identifiers (e.g., MBMS TMGI, TMGI, MBMS session ID, session ID, special QF ID) indicating that the user data of the one or more MBMS QoS flows can be transmitted in multicast mode through the shared / multicast tunnel.

[0063] When an NG-RAN node is authorized to establish one or more MBMS QoS flows belonging to a certain MBMS service, if the one or more MBMS QoS flows are not configured with the one or more MBMS identifiers and / or do not have corresponding shared / multicast tunnels configured, the NG-RAN receives the user data of the one or more MBMS QoS flows through unicast tunnels. If the one or more MBMS QoS flows are configured with the one or more MBMS identifiers and corresponding shared / multicast tunnels, the NG-RAN receives the user data of the one or more MBMS QoS flows through shared / multicast tunnels.

[0064] When a radio access network (NG-RAN) node receives multicast data through a shared / multicast tunnel, the NG-RAN can decide whether to deliver the multicast stream in PTM (point-to-multipoint) or PTP (point-to-point) mode on the radio interface. If unicast mode is used, the MBMS QoS stream within the unicast PDU session is used to transmit the multicast (MBMS) QoS stream over a dedicated data radio bearer (DRB) on the radio interface. If broadcast mode is used, UEs in the same group as the multicast service receive the multicast data over a shared data radio bearer (DRB) on the radio interface.

[0065] In some embodiments of the present disclosure, one or more User Equipment (UE) devices successfully join an MBMS service in a given area (e.g., within NG-RAN). When the core network 5GC decides to transmit user data for one or more MBMS QoS flows through a shared tunnel for the one or more UE devices that have joined the MBMS service, the core network 5GC can configure a shared tunnel and an MBMS identifier for each UE device for the one or more MBMS QoS flows.

[0066] When the radio access network (NG-RAN) receives MBMS QoS flow configuration information, if the radio access network (NG-RAN) establishes one or more MBMS QoS flows, the radio access network (NG-RAN) can receive user data of the one or more MBMS QoS flows through a shared tunnel, and the radio access network (NG-RAN) decides whether to transmit the multicast flow in PTM mode or PTP mode on the radio interface.

[0067] Figure 7Examples of a process 700 for wireless communication based on some example embodiments of the present disclosure are described. At 710, method 700 includes: a first communication node (e.g., 5GC) determining whether to set up one or more data service flows for a mobile device. At 720, the method includes: when it is determined that the one or more data service flows will be set up, transmitting flow establishment configuration information (e.g., MBS QoS flow configuration information) including a unicast flow identifier (e.g., QFI), a corresponding unicast tunnel, and a corresponding Quality of Service (QoS) profile to a second communication node (e.g., NG-RAN). At 730, the method includes: when it is determined that the flow establishment configuration information does not further include a Multicast Broadcast Service (MBS) flow identifier, a corresponding multicast shared tunnel, and a corresponding multicast Quality of Service (QoS) profile, adding a first identifier to the user data of the data service flow, and the first communication node transmitting the data service flow with the first identifier to the second communication node through the corresponding unicast tunnel. At 740, the method includes: when determining that the flow establishment configuration information further includes the multicast broadcast service (MBS) flow identifier, the corresponding multicast shared tunnel, and the corresponding multicast quality of service (QoS) profile, adding a second identifier to the user data of the data service flow, and the first communication node transmitting the data service flow with the second identifier to the second communication node through the corresponding multicast shared tunnel.

[0068] Figure 8 Another example of a process 800 for wireless communication based on some example embodiments of the present disclosure is shown. At 810, method 800 includes: a second communication node (e.g., NG-RAN) receiving flow establishment configuration information (e.g., MBS QoS flow configuration information) from a first communication node (e.g., 5GC) for transmitting a data service flow for a mobile device. At 820, the method includes: the second communication node determining, based on the flow establishment configuration information, whether to receive user data of the data service flow via a unicast tunnel or a multicast tunnel. At 830, the method includes: the second communication node receiving the user data of the data service flow via the unicast tunnel or the multicast tunnel based on the determination.

[0069] Figure 9Another example of a process 900 for wireless communication based on some example embodiments of the present disclosure is shown. At 910, the method includes: a core network determining whether at least one multicast stream has been established in an existing unicast protocol data unit session or a new unicast protocol data unit session. At 920, the method includes: the core network performing data communication based on the determination using an existing unicast tunnel corresponding to the existing unicast protocol data unit session or a new unicast tunnel corresponding to the new unicast protocol data unit session.

[0070] Figure 10 An example of a wireless communication system 1000 is shown, in which techniques according to one or more embodiments of the present invention can be applied. The wireless communication system 1000 may include one or more base stations (BS) 1005a, 1005b, one or more wireless devices 1010a, 1010b, 1010c, 1010d, and a core network 1025. Base stations 1005a and 1005b may provide wireless services to wireless devices 1010a, 1010b, 1010c, and 1010d in one or more wireless sectors. In some implementations, base stations 1005a and 1005b include directional antennas for generating two or more directional beams to provide wireless coverage in different sectors.

[0071] The core network 1025 can communicate with one or more base stations 1005a and 1005b. The core network 1025 provides connectivity with other wireless and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1010a, 1010b, 1010c, and 1010d. The first base station 1005a can provide wireless services based on a first radio access technology, while the second base station 1005b can provide wireless services based on a second radio access technology. Depending on the deployment scenario, base stations 1005a and 1005b can be located in the same location or installed separately in the field. Wireless devices 1010a, 1010b, 1010c, and 1010d can support multiple different radio access technologies. The technologies and embodiments described in this document can be implemented by base stations of the wireless devices described in this document.

[0072] Figure 11This is a block diagram representation of a portion of a radio station to which one or more embodiments of the present invention may be applied. The radio station 1105, such as a base station or wireless device (or UE), may include processor electronics 1110, such as a microprocessor implementing one or more wireless technologies described herein. The radio station 1105 may include transceiver electronics 1115 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as antenna 1120. The radio station 1105 may include other communication interfaces for transmitting and receiving data. The radio station 1105 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, processor electronics 1110 may include at least a portion of transceiver electronics 1115. In some embodiments, the radio station 1105 is used to implement at least some of the technologies, modules, or functions disclosed herein. In some embodiments, the radio station 1105 may be configured to perform the methods described herein.

[0073] It will be understood that this document discloses techniques that can be implemented in various embodiments to establish and manage multicast sessions in various scenarios. The disclosed embodiments and other embodiments, the modules and functional operations described in this document, can be implemented in digital electronic circuits or in computer software, firmware, or hardware (including the structures disclosed in this document and their structural equivalents), or combinations 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 a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of substances influencing machine-readable propagation signals, or combinations thereof. The term "data processing apparatus" encompasses means, devices, and machines for processing data, including, for example, a programmable processor, a computer, or a plurality of processors or computers. In addition to hardware, the means may include code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or combinations thereof. A propagation signal is an artificially generated signal, such as an electrical, optical, or electromagnetic signal produced by a machine, which is generated to encode information for transmission to a suitable receiver device.

[0074] Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any programming language, including compiled or interpreted languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units suited to a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), as a single file dedicated to the program in question, or as multiple coordinating files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program can be deployed to execute on a single computer or on multiple computers located at one site or distributed across multiple sites and interconnected via a communication network.

[0075] The processes and logic described in this document can be implemented by one or more programmable processors, which execute one or more computer programs to perform functions by manipulating input data and generating outputs. The processes and logic can also be implemented by devices, and these devices can be implemented as special-purpose logic circuit systems, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0076] For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, as well as any one or more processors in any type of digital computer. Typically, the processor receives instructions and data from read-only memory or random access memory, or both. The basic components 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 one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operatively coupled to receive data from or transfer data to mass storage devices, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory 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 may be supplemented or integrated therein by dedicated logic circuitry.

[0077] Some embodiments may preferably implement one or more of the following schemes listed in the terms format. The above examples and this document support and further describe the following terms. As used in the following terms and claims, a wireless terminal may be a user equipment, a mobile station, or any other wireless terminal including a fixed node such as a base station. A network node includes a base station, which includes a next-generation B-node (gNB), an enhanced B-node (eNB), or any other device acting as a base station. Resource range may refer to a range of time-frequency resources or blocks.

[0078] Clause 1. A data communication method, comprising: a first communication node determining whether to set up one or more data service flows for a mobile device; when determining to set up the one or more data service flows, transmitting flow establishment configuration information including a unicast flow identifier and a corresponding unicast tunnel to a second communication node; and when determining that the flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier and a corresponding multicast shared tunnel, adding a first identifier to the user data of the data service flow, and the first communication node transmitting the data service flow with the first identifier to the second communication node through the corresponding unicast tunnel; or when determining that the flow establishment configuration information includes the multicast broadcast service (MBS) flow identifier and the corresponding multicast shared tunnel, adding a second identifier to the user data of the data service flow, and the first communication node transmitting the data service flow with the second identifier to the second communication node through the corresponding multicast shared tunnel.

[0079] Clause 2. The method described in Clause 1, wherein the corresponding unicast tunnel includes an existing unicast tunnel or a new unicast tunnel.

[0080] Clause 3. The method according to Clause 1, wherein the flow establishment configuration information is included in an existing Protocol Data Unit (PDU) session.

[0081] Clause 4. The method according to Clause 3, wherein the corresponding unicast tunnel is an existing unicast tunnel being used by the existing PDU session.

[0082] Clause 5. The method described in Clause 3, wherein the corresponding unicast tunnel is a new unicast tunnel being used by the new PDU session.

[0083] Clause 6. The method according to Clause 1, wherein the flow establishment configuration information is included in the new Protocol Data Unit (PDU) session.

[0084] Clause 7. The method according to Clause 1, wherein the data service stream is a multicast stream, and the user data of the data service stream is multicast broadcast service (MBS) user data.

[0085] Clause 8. The method according to Clause 1, wherein the first identifier includes a Quality of Service (QoS) Flow Identifier (QFI).

[0086] Clause 9. The method described in Clause 1, wherein the second identifier includes a multicast broadcast service (MBS) identifier.

[0087] Clause 10. The method according to Clause 9, wherein the MBS identifier includes at least one of the following: Multicast Broadcast Service (MBS) group identifier, or Multicast Broadcast Multimedia Service (MBMS) service identifier, MBMS session identifier, Multicast Broadcast Service Quality Stream Identifier (MBS QFI), or Temporary Mobile Group Identifier (TMGI).

[0088] Clause 11. The method according to Clause 1, wherein each of the first identifier and the second identifier is added to the encapsulation header of each data packet of the data service flow.

[0089] Clause 12. The method according to Clause 1, wherein the shared tunnel is established by a multicast broadcast session triggered by the Multicast Broadcast Service Function (MBSF).

[0090] Clause 13. A data communication method comprising: a second communication node receiving flow establishment configuration information from a first communication node for transmitting a data service flow to a mobile device; the second communication node determining, based on the flow establishment configuration information, whether to receive user data of the data service flow via a unicast tunnel or a multicast tunnel; and the second communication node receiving the user data of the data service flow via the unicast tunnel or the multicast tunnel based on the determination.

[0091] Clause 14. The method according to Clause 13, wherein the flow establishment configuration information is included in an existing Protocol Data Unit (PDU) session.

[0092] Clause 15. The method according to Clause 14, wherein the unicast tunnel is an existing unicast tunnel being used by the existing PDU session.

[0093] Clause 16. The method according to Clause 13, wherein the flow establishment configuration information is included in the new Protocol Data Unit (PDU) session.

[0094] Clause 17. The method according to Clause 16, wherein the unicast tunnel is a new unicast tunnel being used by the new PDU session.

[0095] Clause 18. The method according to Clause 13, wherein the first communication node is configured to determine which transmission mode to use between unicast mode and multicast mode.

[0096] Clause 19. The method according to Clause 18, wherein the unicast mode is configured to use the unicast tunnel, and the multicast mode is configured to use the multicast tunnel.

[0097] Clause 20. The method according to any one of Clauses 18-19, wherein the multicast mode is used when it is determined that the flow establishment configuration information indicates that both the multicast tunnel and the unicast tunnel are configured.

[0098] Clause 21. The method according to any one of Clauses 18-19, wherein the unicast mode is used when it is determined that the flow establishment configuration information indicates that the unicast tunnel is configured while the multicast tunnel is not configured.

[0099] Clause 22. The method according to any one of Clauses 1-21, wherein the first communication node comprises a core network and the second communication node comprises a radio access network.

[0100] Clause 23. A data communication method comprising: a core network determining whether at least one multicast stream has been established in an existing unicast protocol data unit session or a new unicast protocol data unit session; and the core network performing data communication based on the determination using an existing unicast tunnel corresponding to the existing unicast protocol data unit session or a new unicast tunnel corresponding to the new unicast protocol data unit session.

[0101] Clause 24. The method according to Clause 23 further includes: the core network establishing at least one of a unicast stream or a multicast stream between the core network and the radio access network.

[0102] Clause 25. The method according to Clause 24, wherein establishing at least one of a unicast stream or a multicast stream comprises: the core network establishing the multicast stream in the existing Protocol Data Unit (PDU) session, the PDU session including a first unicast tunnel configured to carry data services between the core network and each mobile device.

[0103] Clause 26. The method according to Clause 25, wherein the identifier of the multicast stream is different from the identifier of the unicast stream established in the same existing protocol data unit session.

[0104] Clause 27. The method according to Clause 25, wherein the multicast stream is carried by the first unicast tunnel.

[0105] Clause 28. The method according to Clause 24, wherein establishing at least one of a unicast stream or a multicast stream comprises: the core network establishing the multicast stream in the new protocol data unit session, the new protocol data unit session including a second unicast tunnel configured to carry data services between the core network and each mobile device.

[0106] Clause 29. The method according to Clause 28, wherein the identifier of the new protocol data unit session is different from the identifier of the existing protocol data unit session.

[0107] Clause 30. The method according to Clause 28, wherein the multicast stream is carried by the second unicast tunnel.

[0108] Clause 31. The method according to Clause 24, wherein establishing at least one of a unicast stream or a multicast stream comprises: the core network establishing the multicast stream in a shared tunnel, the shared tunnel being configured to carry data services between the core network and a plurality of mobile devices.

[0109] Clause 32. The method according to Clause 31 further includes: transmitting user data of the multicast stream to the radio access network via the shared tunnel.

[0110] Clause 33. The method according to Clause 32 further comprises: transmitting user data of the multicast stream to the radio access network via the first unicast tunnel or the second unicast tunnel when it is determined that the radio access network is authorized not to receive any identifier of the multicast stream in establishing the multicast stream.

[0111] Clause 34. The method according to Clause 23, wherein the multicast stream is configured with at least one of Multicast Broadcast Multimedia Service (MBMS) Temporary Mobile Group Identifier (TMGI), TMGI, MBMS Session ID, Session ID, or QoS Stream ID (QFI).

[0112] Clause 35. The method according to Clause 24, wherein the radio access network is configured to transmit the multicast stream on the radio interface using a broadcast data radio bearer when transmitting the multicast stream on a point-to-multipoint basis.

[0113] Clause 36. The method according to Clause 24, wherein the radio access network is configured to transmit the multicast stream on a radio interface using a dedicated data radio bearer when transmitting the multicast stream on a point-to-point basis.

[0114] Clause 37. An apparatus for wireless communication, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method as described in any one of Clauses 1 to 36.

[0115] Clause 38. A computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method as described in any one of Clauses 1 to 36.

[0116] Although this patent document contains numerous specific details, these details should not be construed as limiting the scope of any invention or what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of a particular invention. Certain features described in the context of various embodiments in this patent document 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 separately in multiple embodiments, or in any suitable sub-combination. Furthermore, although features may be described above as functioning in certain combinations, and even initially claimed in this way, in some cases, one or more features in a claimed combination may be removed from that combination, and a claimed combination may refer to a sub-combination or a variation of a sub-combination.

[0117] Similarly, although operations are described in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order or sequence shown, or requiring all of the operations shown, in order to obtain the desired results. Furthermore, the separation of various system components in the embodiments described in this patent document should not be construed as requiring such separation in all embodiments.

[0118] Only some implementation methods and examples are described. Other implementation methods, improvements and changes can be made based on the description and explanation in this patent document.

Claims

1. A data communication method, comprising: The first communication node determines whether to set up one or more data service flows for the mobile device; When determining to set up one or more data service flows, the flow establishment configuration information, including unicast flow identifiers and corresponding unicast tunnels, is transmitted to the second communication node; as well as When it is determined that the flow establishment configuration information does not include the Multicast Broadcast Service (MBS) flow identifier and the corresponding multicast shared tunnel, a Quality of Service (QoS) flow identifier (QFI) is added to the encapsulation header of the user data of the data service flow, and the first communication node transmits the user data of the data service flow with the added QFI to the second communication node through the corresponding unicast tunnel. or When it is determined that the flow establishment configuration information includes the multicast broadcast service MBS flow identifier and the corresponding multicast shared tunnel, a unicast tunnel is configured in parallel with the multicast shared tunnel as a dummy tunnel in which no user data of MBS is transmitted. The MBS identifier is added to the encapsulation header of the user data of the data service flow, and the first communication node transmits the user data of the data service flow with the MBS identifier added to it to the second communication node through the corresponding multicast shared tunnel.

2. The method according to claim 1, wherein, The corresponding unicast tunnel includes existing unicast tunnels or new unicast tunnels.

3. The method according to claim 1, wherein, The flow establishment configuration information is included in the existing Protocol Data Unit (PDU) session.

4. The method according to claim 3, wherein, The corresponding unicast tunnel is the existing unicast tunnel that the existing PDU session is currently using.

5. The method according to claim 1, wherein, The stream establishment configuration information is included in the new protocol data unit (PDU) session.

6. The method according to claim 5, wherein, The corresponding unicast tunnel is the new unicast tunnel that the new PDU session is using.

7. The method according to claim 1, wherein, The data service stream is a multicast stream, and the user data in the data service stream is Multicast Broadcast Service (MBS) user data.

8. The method according to claim 1, wherein, The MBS identifier includes at least one of the following: Multicast Broadcast Service MBS Group Identifier, Multicast Broadcast Multimedia Service MBMS Service Identifier, MBMS Session Identifier, Multicast Broadcast Service Quality Stream Identifier MBS QFI, or Temporary Mobile Group Identifier TMGI.

9. The method according to claim 1, wherein, The shared tunnel is established by a multicast broadcast session triggered by the Multicast Broadcast Service (MBSF) function.

10. The method according to any one of claims 1 to 9, wherein, The first communication node includes a core network, and the second communication node includes a radio access network.

11. A data communication method, comprising: The second communication node receives stream setup configuration information from the first communication node in order to transmit data service streams for mobile devices; The second communication node determines, based on the flow configuration information, whether to receive user data from the data service flow via a unicast tunnel or a multicast tunnel; as well as When it is determined that the flow establishment configuration information includes the Multicast Broadcast Service (MBS) flow identifier and the corresponding multicast shared tunnel, the second communication node receives the user data of the data service flow through the multicast tunnel, and maintains the unicast tunnel in parallel as a dummy tunnel in which no MBS user data is transmitted. or When it is determined that the flow establishment configuration information does not include the Multicast Broadcast Service (MBS) flow identifier and the corresponding multicast shared tunnel, the second communication node receives the user data of the data service flow through the unicast tunnel, wherein the unicast tunnel carries data packets, and the Quality of Service (QoS) flow identifier (QFI) is included in the encapsulation header of the data packets.

12. The method according to claim 11, wherein, The flow establishment configuration information is included in the existing Protocol Data Unit (PDU) session.

13. The method according to claim 12, wherein, The unicast tunnel is an existing unicast tunnel that is currently in use by the existing PDU session.

14. The method according to claim 11, wherein, The stream establishment configuration information is included in the new protocol data unit (PDU) session.

15. The method according to claim 14, wherein, The unicast tunnel is a new unicast tunnel that the new PDU session is using.

16. The method according to claim 11, wherein, The first communication node is configured to determine which transmission mode to use between unicast and multicast modes.

17. The method according to claim 16, wherein, The unicast mode is configured to use the unicast tunnel, and the multicast mode is configured to use the multicast tunnel.

18. The method according to any one of claims 11 to 17, wherein, The first communication node includes a core network, and the second communication node includes a radio access network.

19. A data communication method, comprising: The core network determines whether at least one multicast stream was established in an existing unicast protocol data unit session or a new unicast protocol data unit session; as well as The core network performs data communication based on the determination to use either an existing unicast tunnel corresponding to the existing unicast protocol data unit session or a new unicast tunnel corresponding to the new unicast protocol data unit session. When it is determined that the at least one multicast stream is configured with a Multicast Broadcast Service (MBS) stream identifier and a corresponding multicast shared tunnel, a unicast tunnel is maintained in parallel with the multicast shared tunnel as a dummy tunnel in which no user data of MBS is transmitted, and the user data of the multicast stream is transmitted through the multicast shared tunnel. or When it is determined that at least one multicast stream is not configured with a Multicast Broadcast Service (MBS) stream identifier and a corresponding multicast shared tunnel, the user data of the multicast stream is transmitted through the unicast tunnel, wherein the Quality of Service (QoS) stream identifier (QFI) is added to the encapsulation header of each user data packet.

20. The method of claim 19, further comprising: The core network establishes at least one of a unicast stream or a multicast stream between the core network and the radio access network.

21. The method according to claim 20, wherein, The establishment of at least one of a unicast stream or a multicast stream includes: the core network establishing the multicast stream in the existing unicast protocol data unit session, the existing unicast protocol data unit session including a first unicast tunnel configured to carry data services between the core network and each mobile device.

22. The method according to claim 21, wherein, The identifier of the multicast stream is different from the identifier of the unicast stream established in the same existing unicast protocol data unit session.

23. The method according to claim 21, wherein, The multicast stream is carried by the first unicast tunnel.

24. The method of claim 20, wherein, The establishment of at least one of the unicast stream or the multicast stream includes: the core network establishing the multicast stream in the new unicast protocol data unit session, the new unicast protocol data unit session including a second unicast tunnel configured to carry data services between the core network and each mobile device.

25. The method according to claim 24, wherein, The identifier of the new unicast protocol data unit session is different from the identifier of the existing unicast protocol data unit session.

26. The method of claim 24, wherein, The multicast stream is carried by the second unicast tunnel.

27. The method of claim 20, wherein, The establishment of at least one of a unicast stream or a multicast stream includes: the core network establishing the multicast stream in a shared tunnel, the shared tunnel being configured to carry data services between the core network and multiple mobile devices.

28. The method of claim 27, further comprising: User data of the multicast stream is transmitted to the radio access network through the shared tunnel.

29. The method of claim 28, further comprising: When it is determined that the radio access network is authorized not to receive any identifier of the multicast stream before establishing the multicast stream, the user data of the multicast stream is transmitted to the radio access network through a first unicast tunnel included in the existing unicast protocol data unit session or a second unicast tunnel included in the new unicast protocol data unit session.

30. The method according to claim 19, wherein, The multicast stream is configured with at least one of the following: Multicast Broadcast Multimedia Service (MBMS) Temporary Mobile Group Identifier (TMGI), TMGI, MBMS Session ID, Session ID, or QoS Stream ID.

31. The method according to claim 20, wherein, The radio access network is configured to transmit the multicast stream on the radio interface using a broadcast data radio bearer when transmitting the multicast stream on a point-to-multipoint basis.

32. The method according to claim 20, wherein, The radio access network is configured to transmit the multicast stream on a radio interface using a dedicated data radio bearer when transmitting the stream on a point-to-point basis.

33. An apparatus for wireless communication, comprising a memory and a processor, wherein, The processor reads code from the memory and implements the method as described in any one of claims 1 to 32.

34. A computer-readable program storage medium having code stored thereon, said code causing the processor to perform the method as described in any one of claims 1 to 32 when executed by a processor.

Images