Signaling for multicast broadcast services

Abstract

Methods, systems, and apparatus for implementing multicast broadcast services in a wireless network are described. An example method includes: communicating messages at an interface between a network node's control plane (CP) function and a network node's user plane (UP) function, the network node providing data connectivity to one or more wireless devices in the wireless network, and configuring the network node based on the messages to provide services carrying multicast or broadcast data for sessions of the one or more wireless devices.

Description

Technical Field

[0001] This application is generally directed to wireless communication. Background Technology

[0002] Wireless communication technology is propelling the world towards an increasingly interconnected and networked society. The rapid growth and technological advancements in wireless communication have led to 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. Compared to existing wireless networks, next-generation systems and wireless communication technologies will support greater functionality and more flexible network operation. Summary of the Invention

[0003] This application relates to methods, systems, and apparatus for providing multicast and broadcast services (MBS) in mobile communication technologies, including fifth-generation (5G) and new radio (NR) communication systems.

[0004] In one exemplary aspect, a method for wireless communication is disclosed. The method includes: transmitting a message on an interface between a control plane (CP) function and a user plane (UP) function of a network node, the network node providing data connectivity to one or more wireless devices in a wireless network, and configuring the network node based on the message to provide services carrying multicast or broadcast data for sessions of the one or more wireless devices.

[0005] In yet another exemplary aspect, the above-described method is embodied in the form of processor-executable code and stored in a computer-readable process medium.

[0006] In yet another exemplary embodiment, a device configured or operable to perform the methods described above is disclosed.

[0007] The foregoing and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0008] Figure 1 An example of a wireless system that supports multicast and broadcast services (MBS) is shown.

[0009] Figure 2 An example implementation of a network node that provides MBS services to wireless devices is shown.

[0010] Figure 3 An example of a protocol stack implementation for handling MBS services is shown.

[0011] Figure 4 An example of another method for wireless communication is shown.

[0012] Figure 5 It is a block diagram representation of an apparatus that can be used to implement the methods and techniques disclosed herein. Detailed Implementation

[0013] The chapter headings used in this application are for readability purposes only and are not intended to limit the scope of the embodiments and techniques disclosed in each chapter to that chapter only. Examples of fifth-generation (5G) wireless protocols are used to describe certain features. However, the applicability of the disclosed techniques is not limited to 5G wireless systems.

[0014] With the continuous development of 5G (fifth-generation mobile network, fifth-generation mobile communication technology), 5G solutions for various application scenarios are rapidly converging. Multicast broadcast service (MBS) scenarios are traditional service scenarios designed to meet the needs of most users for the same service. Currently, the 5G-related technologies that have been discussed and standardized in the industry mainly concern unicast service scenarios, namely the PTP (point-to-point) service mode. Discussions on the standardization of the PTM (point-to-multipoint) service mode have not yet begun. Furthermore, with the rapid growth in the number of users and the diversification of application scenarios, the point-to-multipoint service mode will inevitably become one of the indispensable service modes.

[0015] For the future development of wireless communication (and especially multicast services), it will be beneficial to solve how to rationally and effectively implement multicast services within the 5G-NR (New Radio, New NR) technical framework. Currently, 5G base stations support CU / DU separation and CU CP / UP separation, where CU-CP and CU-UP communicate via the E1 interface. In this case, how to perform broadcast / multicast service bearer establishment through the E1 interface, particularly the configuration information exchanged via the E1 interface, remains unknown.

[0016] The technology disclosed in this application allows embodiments to support schemes for introducing broadcast / multicast services into NR. The disclosed embodiments can be used for network-side establishment supporting broadcast / multicast services. Specifically, this application discloses flexible configuration information that can be exchanged between control plane (CP) functions and user plane (UP) functions at network devices. This information can be exchanged through a suitable interface, such as an E1 interface.

[0017] This application uses examples from the 3GPP New Radio (NR) network architecture and 5G protocols for the purpose of facilitating understanding only, and the disclosed technologies and embodiments can be practiced in other wireless systems using communication protocols different from 3GPP protocols.

[0018] The following abbreviations are used in this application.

[0019] AMBR - Aggregated Maximum Bit Rate

[0020] AMF - Access and Mobility Functions

[0021] AP - Application Protocol

[0022] CP-Control Surface

[0023] CU - Centralized Unit

[0024] DU - Distributed Unit

[0025] GBR - Guaranteed Bit Rate

[0026] gNB-gNodeB

[0027] GTP - General Packet Radio Services Tunneling Protocol

[0028] ID - Identifier

[0029] MBS - Multicast Broadcast Service

[0030] NG - Next Generation

[0031] NR - New Radio

[0032] PDCP - Packet Data Convergence Protocol

[0033] PDU - Protocol Data Unit

[0034] PTM - Point-to-Multipoint

[0035] PTP - Point-to-Point

[0036] QoS - Quality of Service

[0037] RAN - Radio Access Network

[0038] RLC - Wireless Link Control

[0039] SDAP - Service Data Adaptation Protocol

[0040] SDU - Service Data Unit

[0041] TEID - Tunnel Endpoint Identifier

[0042] TMGI - Temporary Movement Group Identifier

[0043] TNL - Transport Network Layer

[0044] UE - User Equipment

[0045] UP - User Interface

[0046] Figure 1An example network 100 is shown in which MBS services can be provided to one or more wireless devices 102. The wireless device 102 can be, for example, a mobile phone, a tablet computer, or other UE capable of wireless or cellular communication.

[0047] Wireless device 102 can be coupled to network node 104 via radio access network RAN ​​106. Network node 104 can be, for example, a base station or another network-side device operating in the network to provide data connectivity to wireless device 102.

[0048] Figure 2 This illustrates an example of a network node 104 with a control plane CP 202 and a user plane UP 204, configured to implement control plane functions (e.g., related to device and connectivity control) and user plane functions (e.g., related to user data or application layer data traffic). These two functions 202 and 204 can be configured to communicate with each other using an interface such as an E1 interface.

[0049] Network node 104 can be configured to implement various scenarios related to the use of MBS services by wireless device 102 in RAN 106. For example, the network node can be a centralized unit (CU) that provides services by... Figure 1 The RAN and core network serving each distributed unit (DU) not explicitly shown in the text Figure 1 Connections between (not explicitly shown in the text). For example, during operation, network node 104 can establish a bearer to carry data traffic for services to one or more wireless devices 302, add or remove wireless devices 302 from their ongoing service subscriptions, or change the mode of service reception for wireless devices from unicast to multicast / broadcast, and vice versa.

[0050] Example 1

[0051] The CU-CP requests the CU-UP to establish an MBS bearer to support MBS traffic transmission. Specifically, the CU-CP requests the CU-UP to establish the MBS bearer through the MBS bearer establishment / modification process. The CU-CP can send the following information to the CU-UP:

[0052] -MBS Session ID,

[0053] -MBS session type.

[0054] In some embodiments, the CU-CP may send a group member list that includes the identifiers of all UEs interested in the MBS service. The UE ID may be a RAN UE ID or an E1AP UE ID.

[0055] In various embodiments, the UE may support PTP mode or PTM mode, or both. Accordingly, a network node may wirelessly deliver a single copy (PTM) of MBS data packets to a group of UEs, or wirelessly deliver individual copies (PTP) of MBS data packets to each UE.

[0056] In some embodiments, CU-CP can send TMGI.

[0057] In some embodiments, the CU-CP may send the MBS service identifier.

[0058] In some embodiments, the CU-CP can send the MBS session AMBR. This information can be sent for non-GBR QoS flows.

[0059] In some embodiments, the CU-CP may send TNL information, including the IP multicast address and / or DL ​​TEID, to the CU-UP.

[0060] In some embodiments, the CU-CP may send alternative TNL information, including the IP multicast address and / or DL ​​TEID, to the CU-UP.

[0061] In some embodiments, CU-CP may send the following MBS bearer-related information to CU-UP:

[0062] (1) MBS bearer indexes used by CU-UP to identify different MBS bearers.

[0063] (2) MBS bearer type, which is used to indicate whether the supported mode is PTP or PTM or both.

[0064] (3) QoS flow information, including 5QI, allocation and reservation priority, and GBR QoS flow information. For GBR QoS flow information, CU-CP can provide CU-UP with a list of alternative QoS parameter sets via the E1 interface. This list of QoS parameter sets may include an index of alternative QoS parameter sets, downlink guaranteed flow bit rate, packet delay budget, packet error rate, etc.

[0065] In some embodiments, the CU-CP can send service area information. This information may include a service area identifier or a list of cells.

[0066] UEs operating in PTM mode may need to report their DL data reception status to the gNB. To achieve this, when establishing an MBS bearer, the CU-UP can establish an additional GTP tunnel for the MBS bearer. Through this tunnel, the UE can send DL delivery status (e.g., PDCP status report) to the CU-UP. Furthermore, the CU-UP can use the additional tunnel for DL ​​data retransmission. Each additional tunnel can correspond to an RLC entity. Specifically, the information associated with the MBS bearer may also include one or more of the following:

[0067] 1. Several additional tunnels will be built.

[0068] 2. The identifier of the additional tunnel, and the identifier of the UE optionally associated with the additional tunnel.

[0069] 3. UE ID list, in which CU-CP includes all identifiers of UEs that require feedback.

[0070] 4. Additional Tunnel Establishment Instruction. Upon receiving this instruction, CU-UP can establish an additional GTP tunnel when establishing the MBS bearer.

[0071] - The UE ID or group member list associated with each MBS bearer.

[0072] In some embodiments, the CU-UP may feed back to the CU-CP the UL UP transport layer information associated with each additional tunnel and the identifier of each additional tunnel, as well as the UE ID optionally associated with each additional tunnel.

[0073] Example Scenario 1 - UE Joins MBS Service

[0074] Assume the UE joins the MBS service. If the CU-UP has already established an MBS bearer, the CU-CP can send the following information to the CU-UP via an MBS bearer modification request message:

[0075] -MBS Session ID.

[0076] -MBS Session Type

[0077] -TMGI,

[0078] -MBS service identifier,

[0079] -MBS Session AMBR. This information can be used for non-GBR QoS flows.

[0080] -Includes TNL information including IP multicast address + DL TEID,

[0081] - Includes optional TNL information such as IP multicast address + DL TEID.

[0082] - The new UE's UE ID,

[0083] -Indication regarding whether the UE supports PTP, PTM, or both.

[0084] -MBS carries the information for establishing the system.

[0085] Since CU-UP receives the session and bearer configuration corresponding to the MBS session ID, it can perform bearer establishment based on the previously received session and bearer configuration when it receives another MBS session. In this case, CU-CP does not need to send the session and bearer configuration to CU-UP again, thus saving signaling overhead.

[0086] Example Scenario 2 - UE Leaves MBS Service

[0087] Suppose the UE leaves MBS service. In this case, the CU-CP can perform an MBS bearer release / modification procedure. Established MBS bearers can be released. Furthermore, the CU-CP can send one or more of the following information items to the CU-UP:

[0088] - Instructions to release additional tunnels associated with the UE.

[0089] - An updated group member list that removes identifiers of UEs that are not interested in MBS services.

[0090] - Remove the ID list, which includes identifiers of UEs that are not interested in MBS services.

[0091] Example Scenario 3 - UE switches from PTP to PTM mode

[0092] Assuming the UE switches from PTP to PTM, the CU-CP can notify the CU-UP of this event. To allow the UE to begin receiving service on the bearer, the CU-CP can send one or more of the following information items to the CU-UP:

[0093] -UE ID

[0094] -UE now supports PTM information.

[0095] - Instruction to release all MBS bearers associated only with the UE.

[0096] - An updated list of group members associated with each MBS bearer used for PTM.

[0097] - Multiple additional tunnels to be established, which are used only by the UE performing the handover.

[0098] Example Scenario 4 - UE switches from PTM mode to PTP mode

[0099] Assuming the UE switches from PTM to PTP, regarding the information provided by CU-CP to CU-UP, the following solutions can be considered:

[0100] Solution 1:

[0101] In this solution, the CU-CP performs the MBS bearer modification procedure. In this scenario, the CU-UP can release all additional tunnels associated with the UE. The CU-CP sends a bearer context establishment / modification request message to the CU-UP to establish an MBS bearer for the UE.

[0102] Solution 2:

[0103] In this scenario, the CU-CP uses the MBS bearer modification procedure to implement the UE's mode switch. Specifically, the CU-CP can send one or more of the following information items to the CU-UP:

[0104] -UE ID,

[0105] -UE now supports PTP information.

[0106] - Instructions to release additional tunnels associated with the UE.

[0107] - An updated list of group members associated with each MBS bearer used for PTM.

[0108] -MBS carries the information for establishing the system.

[0109] Example 2

[0110] In some cases, the CU-CP can request the CU-UP to establish an MBS bearer to support MBS traffic transmission. Specifically, the CU-CP requests the CU-UP to establish the MBS bearer through a bearer context establishment / modification procedure, which is a UE-related message. The CU-CP can send one or more of the following information items to the CU-UP:

[0111] -MBS Session ID,

[0112] -MBS session type,

[0113] -UE supports PTP or PTM or both.

[0114] -TMGI,

[0115] -MBS service identifier,

[0116] -MBS session AMBR. This rate can be used for non-GBR QoS flows.

[0117] - TNL information including IP multicast address and / or DL ​​TEID,

[0118] - Optional TNL information including IP multicast address and / or DL ​​TEID.

[0119] In some embodiments, CU-CP may send the following MBS bearer-related information to CU-UP:

[0120] QoS flow information includes 5QI, allocation and reservation priorities, and GBR QoS flow information. For GBR QoS flow information, CU-CP can provide CU-UP with a list of alternative QoS parameter sets via the E1 interface. This list of alternative QoS parameter sets may include an index of alternative QoS parameter sets, downlink guaranteed flow bit rate, packet delay budget, packet error rate, etc.

[0121] Optionally, service area information may include a service area identifier or a list of supported cells.

[0122] Example Scenario 5

[0123] Suppose the UE leaves MBS service. In this case, CU-CP can execute the BEARER CONTEXT RELEASE procedure.

[0124] Example Scenario 6

[0125] Suppose the UE switches from PTP to PTM. In this case, the CU-CP can execute the BEARER CONTEXT RELEASE procedure.

[0126] Example 3

[0127] In order to enable data streams from MBS sessions to be delivered to the UE in different delivery modes (i.e., PTP, PTM, or both), for the same UE or different UEs, such as Figure 3 As shown, from the user plane (UP) perspective, there are several different options. The air interface protocols include SDAP, PDCP, RLC, MAC, and PHY layers. Different UP options use different protocol layers as anchor layers for mode switching, and in all options, different RLC entities are used for different delivery modes, either simultaneously for the same UE or simultaneously for different UEs.

[0128] in particular, Figure 3Option 3, as described, can be as follows: Two different service deliveries can share the same SDAP entity, but different PDCP entities, GTP tunnels, and RLC entities. In this option, the anchor layer is the SDAP layer. QoS flows or data flows from the core network are submitted to the shared SDAP entity. QoS flows are mapped to a set of MBS bearers, while the same QoS flows are mapped to another set of MBS bearers with the same or different mapping rules. The MBS bearers are then processed by different PDCP entities using separate ordering operations. Therefore, PDCP PDUs from the aforementioned different PDCP entities are sent to different DUs in different GTP tunnels and delivered by different RLC entities.

[0129] In some embodiments of option 3, the CU-CP may send an MBS bearer establishment / modification request message to the CU-UP. Furthermore, this message may include information associated with the MBS bearer.

[0130] In some embodiments, SDAP copy instruction and copy activation instruction.

[0131] In some embodiments, CU-CP includes replica information in the message for generating one or more replicas of the service packet:

[0132] -Number of copies

[0133] - Information regarding whether PTP mode and / or PTM mode are supported by each of one or more replicas.

[0134] - The UE ID or group member list associated with each of one or more copies.

[0135] The various embodiments described above can be used to provide the following technical solutions, which are preferably implemented by some of the embodiments.

[0136] 1. A method for wireless communication (e.g., Figure 4 The method 400 described herein includes: transmitting (402) a message on an interface between the control plane (CP) function and the user plane (UP) function of a network node, the network node providing data connectivity to one or more wireless devices in a wireless network; and configuring (404) the network node based on the message to provide services carrying multicast or broadcast data for sessions of one or more wireless devices.

[0137] 2. The method according to Solution 1, wherein the message includes a request to establish a new bearer to carry the service, wherein the request is sent during the bearer establishment process or the bearer modification process.

[0138] 3. The method according to Solution 1, wherein the message includes a request to establish a new bearer to carry the service, wherein the request is sent during a bearer context establishment process or a bearer context modification process.

[0139] 4. The method according to solutions 2-3, wherein the message includes a session identifier carrying the session of the service.

[0140] 5. The method described in solutions 2-4, wherein the message includes the session type of the session.

[0141] 6. The method according to any one of solutions 1-5, wherein the message includes one or more of the following: a group member list identifying all wireless devices interested in receiving the service, a Temporary Mobile Group Identifier (TMGI), an identifier of the service, an aggregated maximum bit rate associated with the session; and one or more transport network layer (TNL) information including an Internet Protocol (IP) multicast address and / or a downlink tunnel endpoint identifier (TEID).

[0142] 7. The method according to Solution 6, wherein the list of group members uses a radio access network identifier or an E1APUE identifier to identify all wireless devices.

[0143] 8. The method according to any one of solutions 1-7, wherein the message includes a carried identifier.

[0144] 9. The method according to any one of solutions 1-7, wherein the message includes quality of service (QoS) information associated with the bearer.

[0145] 10. The method according to any one of solutions 1-9, wherein the message includes service area information associated with the wireless device, including a list or identifier of one or more service areas. For example, a service area may represent all cells where wireless devices subscribing to the service are located.

[0146] 11. The method according to any one of solutions 1-10, wherein the message further includes a field indicating associated information for the bearer. Various possible examples of such associated information are described in this application.

[0147] 12. The method according to solution 11, wherein the associated information includes: the number of additional tunnels to be established, the identifier of the radio device associated with each tunnel, the identifier of the UE associated with one or more additional tunnels, or a list of radio devices as group members of each group associated with each bearer established with the UP function.

[0148] 13. The method according to solution 12, wherein the additional tunnel is used to send downlink data delivery status for each wireless device using PTM mode.

[0149] 14. The method according to any one of solutions 1-13, comprising: receiving uplink transport layer information associated with an additional tunnel, an identifier of the additional tunnel, and a UE ID associated with each tunnel from the UP function by the CP function.

[0150] 15. The method according to solution 1 or 3, wherein a message is sent in the event that the wireless device goes out of service, wherein the message includes one or more of the following: an instruction to release the existing bearer, an instruction to release an additional tunnel established for the wireless device, an updated group membership list, or a list of removed identifiers including the identifier of the wireless device.

[0151] 16. The method according to any one of solutions 1-15, comprising: transmitting a packet replication instruction and / or a replication function activation instruction from the CP function to the UP function at the Service Data Adaptation Protocol (SDAP) layer.

[0152] 17. The method according to any one of solutions 1 to 16, comprising: transmitting copy information of one or more copies of a group for generating a service from the CP function to the UP function.

[0153] 18. The method according to solution 17, wherein the copy information includes the number of copies.

[0154] 19. The method according to any one of solutions 17-18, wherein the copy information includes information about whether PTP mode and / or PTM mode are supported by each of one or more copies.

[0155] 20. The method according to any one of solutions 17-19, wherein the copy information includes a UE ID or a list of group members associated with each of the one or more copies.

[0156] 21. The method according to Solution 11, wherein the associated information includes Quality of Service (QoS) information associated with a bearer, the bearer including Guaranteed Bit Rate (GBR) flow information, the Guaranteed Bit Rate flow information including one or more of the following: a list of alternative QoS parameter sets including an index of alternative QoS parameter sets, the guaranteed flow bit rate in the downlink direction, packet delay budget, or packet error rate.

[0157] 22. The method according to solution 11, wherein the associated information includes one or more of the following: a list of UE IDs identifying the UEs that need feedback.

[0158] 23. The method according to solution 11, 12 or 22, wherein the associated information includes one or more of the following: additional tunnel establishment instructions for the UP function to establish an additional GTP tunnel when establishing the bearer.

[0159] 24. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any one of solutions 1 to 23.

[0160] 25. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of solutions 1 to 23.

[0161] In the above solutions, multicast or broadcast data or services can be, for example, MBS streams and services described in 3GPP documents 3GPP TS22.246, 23.246, or 26.946. For example, using MBS streams, wireless devices will be able to receive the same content using unicast, multicast, or broadcast transmissions, depending on network conditions.

[0162] Figure 5 This is a block diagram representation of a portion of an apparatus according to some embodiments of the present disclosure. Apparatus 505, such as a base station or network node or wireless device (or UE), may include processor electronics 510, such as a microprocessor implementing one or more technologies proposed in this application. Apparatus 505 may include transceiver electronics 515 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as one or more antennas 520. Apparatus 505 may include other communication interfaces for transmitting and receiving data. For example, a network node may include a wired connection on the core network side. Apparatus 505 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, processor electronics 510 may include at least a portion of transceiver electronics 515. In some embodiments, apparatus 505 is used to implement at least some of the disclosed technologies, modules, or functions. In some embodiments, apparatus 505 may be used to implement the CP or UP functions described herein.

[0163] It should be understood that several examples of messages transmitted between the control plane and user plane of a network device are disclosed to facilitate the establishment, ongoing maintenance, and cancellation of MBS services to or allocation of bearers to MBS services to radio devices. In one example aspect, the disclosed techniques can be used to reduce the amount of control signaling performed on the E1 interface in a centralized unit. In another example aspect, the disclosed techniques can be used to provide seamless changes to MBS delivery, including allowing a UE to join a new multicast service or change the mode in which a UE is receiving an existing multicast service.

[0164] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, the computer program product including computer-executable instructions such as program code that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding actions for implementing the functionality described in these steps or processes.

[0165] Some disclosed embodiments may be implemented as devices or modules using hardware circuitry, software, or a combination thereof. For example, a hardware circuitry implementation may include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed herein. Similarly, various components or sub-components within each module may be implemented in software, hardware, or firmware. Interconnectivity between modules and / or components within modules may be provided using any connection methods and media known in the art, including but not limited to communication over the Internet, wired, or wireless networks using appropriate protocols.

[0166] While this application contains numerous details, these details should not be construed as limiting the scope of the claimed invention or any potentially claimed content, but rather as descriptions of specific features of particular embodiments. Certain features described herein may also be implemented in combination in a single embodiment within the context of individual embodiments. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. 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 from said combination may be removed from the combination, and the claimed combination may refer to a sub-combination or a variation of a sub-combination. Similarly, although operations are described in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific order or sequential sequence shown, or requiring all of the shown operations to obtain the desired result.

[0167] Only some implementation methods and examples have been described. Other implementation methods, enhancements and variations can be made based on the content described and illustrated in this disclosure.

Claims

1. A method for wireless communication, comprising: sending, by a control plane (CP) function of a network node, one or more messages to a user plane (UP) function of the network node on an interface between the CP function and the UP function, wherein the network node provides data connectivity to one or more wireless devices in a wireless network, wherein the one or more messages comprise a request to establish a bearer to carry a service, wherein the request is sent during a bearer context establishment procedure or a bearer context modification procedure, wherein the request comprises a session identifier of a session carrying the service, wherein the one or more messages comprise one or more of a group member list identifying all wireless devices interested in receiving the service, a temporary mobile group identifier (TMGI), an identifier of the service, an aggregate maximum bit rate associated with the session, and one or more transport network layer (TNL) information comprising an Internet Protocol (IP) multicast address or a downlink tunnel endpoint identifier (TEID); and configuring the network node to provide the service carrying multicast or broadcast data for the session of the one or more wireless devices based on the messages.

2. The method of claim 1, wherein, the request comprises a session type of the session.

3. The method of claim 1, wherein, the group member list identifies the all wireless devices using a wireless access network (WAN) identifier or an El AP UE identifier.

4. The method of any one of claims 1-3, wherein, the request comprises an identifier of the bearer.

5. The method of any one of claims 1-3, wherein, the request comprises quality of service (QoS) information associated with the bearer.

6. The method of any one of claims 1-3, wherein, the one or more messages comprise service area information associated with the wireless devices, the associated service area information comprising a list or an identification of one or more service areas.

7. The method of any one of claims 1-3, wherein, the request further comprises a field indicating associated information of the bearer.

8. The method of claim 7, wherein, the associated information comprises a number of additional tunnels to be established, an identification of UEs associated with the one or more additional tunnels, or a list of wireless devices that are group members of each group associated with each bearer established with the UP function.

9. The method of any of claims 1-3, comprising: receiving, by the CP function from the UP function, uplink transport layer information associated with additional tunnels, an identifier of additional tunnels, a UE ID associated with each tunnel.

10. The method of claim 1, wherein, the request is sent in case a wireless device exits the service, wherein the messages comprise one or more of an instruction to release an existing bearer, an instruction to release additional tunnels established for the wireless device, an updated group member list, or a removal identifier list comprising an identifier of the wireless device.

11. The method of any of claims 1-3, comprising: communicating, by the CP function to the UP function, an indication of packet duplication at a service data adaptation protocol (SDAP) layer and / or an indication of activation of a duplication function.

12. The method of claim 7, wherein, The associated information includes Quality of Service, QoS, information associated with the bearer, the bearer including Guaranteed Bit Rate, GBR, flow information, the Guaranteed Bit Rate, GBR, flow information including one or more of: a list of alternative QoS parameter sets including an alternative QoS parameter set index, a Guaranteed Bit Rate, GBR, flow in a downlink direction, a packet delay budget, or a packet error rate.

13. The method of claim 7, wherein, The associated information includes a UE ID list identifying UEs that need feedback.

14. The method of claim 7, wherein, The associated information includes an additional tunnel establishment indication for UP functions to establish an additional GTP tunnel when establishing the bearer.

15. A wireless communication device comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method of any of claims 1 to 14.

16. A computer program product comprising computer readable program medium code stored thereon, which when executed by a processor, causes the processor to implement the method of any of claims 1 to 14.

Images