Techniques for managing multicast and broadcast services

Abstract

Techniques for a radio access network (RAN) system to obtain and manage priority information indicating a priority of a multicast and broadcast service (MBS) are described. An example wireless communication method includes receiving, by a first network node, priority information indicating a priority of a multicast and broadcast service (MBS) from a second network node, and determining, by the first network node, a reception priority of the MBS based on the priority indicated by the priority information.

Description

[Technical field]

[0001] TECHNICAL FIELD This disclosure is directed generally to digital wireless communications. [Background technology]

[0002] Mobile telecommunications technologies are moving the world towards an increasingly connected and networked society. Compared to existing wireless networks, next generation systems and wireless communication techniques will need to support a much broader range of use case characteristics and provide a more complex and sophisticated range of access requirements and flexibility.

[0003] Long Term Evolution (LTE) is a standard for wireless communications for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP®). LTE Advanced (LTE-A) is a wireless communications standard that enhances the LTE standard. The fifth generation of wireless systems, known as 5G, advances the LTE and LTE-A wireless standards and is committed to supporting higher data rates, multiple connections, ultra-low latency, high reliability, and other emerging business demands. Summary of the Invention [Means for solving the problem]

[0004] A cell may transmit several multicast and broadcast services (MBS). MBS may include a technique for a mobile network data source node to transmit data to multiple target nodes, which can realize sharing and effective use of network resources, especially air interface resources. Different MBS services may have different priorities that can be received by a UE. The priority of the MBS service can be known by the base station to enable the base station to make appropriate scheduling decisions. This patent application describes a technique to solve the technical problem of how a radio access network (RAN) system obtains and handles information regarding the priority of the MBS service.

[0005] A first exemplary wireless method includes receiving, by a first network node, priority information from a second network node indicating a priority of a Multicast and Broadcast Service (MBS) and determining, by the first network node, a reception priority of the MBS based on the priority indicated by the priority information. In some embodiments, the priority information includes a priority of an identifier associated with the MBS. In some embodiments, the identifier includes an MBS service identifier, an MBS session identifier, a Temporary Mobile Group Identifier (TMGI), a portion of a Quality of Service (QoS) flow in the MBS session, a Multicast Radio Bearer (MRB) identifier, or a unique identification of an interface over which the MBS service or MBS session is established between the first network node and the second network node.

[0006] In some embodiments, the priority information includes an indication of whether one or more user equipments connected to the first network node prioritize reception of multiple Multimedia Broadcast Multicast Services (MBMS) over reception of any one unicast service. In some embodiments, the priority information includes a list of MBS services that one or more user equipments are receiving (or are interested in receiving). In some embodiments, the list of MBS services includes one or more identifiers arranged in an order indicating a priority of the one or more identifiers. In some embodiments, the priority information is associated with an identifier of a user equipment, or the priority information is associated with multiple user equipments receiving (or are interested in receiving) the MBS.

[0007] In some embodiments, the priority information is received via a Next Generation Application Protocol (NGAP) message using MBS session association signaling. In some embodiments, the priority information is received via a Next Generation Application Protocol (NGAP) message using user equipment association signaling. In some embodiments, the priority information is received via an F1 Application Protocol (F1AP) message using MBS session association signaling. In some embodiments, the priority information is received via an F1 Application Protocol (F1AP) message using user equipment association signaling. In some embodiments, the priority information is received via a Radio Resource Control (RRC) message or a user equipment dedicated Medium Access Control-Control Element (MAC CE).

[0008] In some embodiments, the priority information is received via a radio resource control (RRC) message over a broadcast channel. In some embodiments, the priority information is received via system information or a medium access control-control element (MAC CE) broadcast within a cell. In some embodiments, the first network node includes a base station and the second network node includes a core network. In some embodiments, the first network node includes a distributed unit and the second network node includes a central unit. In some embodiments, the first network node includes a user equipment and the second network node includes a base station. In some embodiments, the first network node includes a base station and the second network node includes a user equipment.

[0009] A second example wireless communication method includes determining, by a user equipment, that a number of multiple transmissions scheduled for the user equipment over a shared channel exceeds a capability of the user equipment, and effecting reception of one or more of the multiple transmissions based on a priority of a multicast and broadcast service (MBS), the priority of the MBS being indicated by a higher layer or by a medium access control element (MAC CE).

[0010] A third exemplary method of wireless communication includes determining, by a medium access control (MAC) entity of a user equipment, that a received downlink assignment for an MBS-associated Radio Network Temporary Identifier (RNTI) and associated Hybrid Automatic Repeat Request (HARQ) information is indicated to a HARQ entity, the HARQ entity being an MBS HARQ entity for the MBS service and managing an MBS process, and for the downlink assignment, the MBS HARQ entity directs a transport block (TB) to the MBS process indicated in the associated HARQ information. In some embodiments, the MAC entity is configured to receive the downlink assignment associated with the MBS-associated RNTI by a higher layer.

[0011] A fourth exemplary method of wireless communication includes determining, by a medium access control (MAC) entity of a user equipment, that a received downlink assignment for an MBS-associated radio network temporary identifier (RNTI) and associated hybrid automatic repeat request (HARQ) information are indicated to a HARQ entity, the HARQ entity being an MBS HARQ entity for an MBS service and managing an MBS process, and for the downlink assignment, the MBS HARQ entity allocates one or more received transport blocks and associated HARQ information to an unoccupied MBS process, and associating the MBS process with the MBS-associated RNTI for the downlink assignment. In some embodiments, the method further includes, upon receiving a new transport block, the MBS HARQ entity making a determination that the MBS HARQ entity does not include an unoccupied MBS process, and in response to making the determination, regarding an occupied MBS process corresponding to an MBS service with the lowest priority as an unoccupied MBS process. In some embodiments, the occupied MBS process is selected or randomly selected from a plurality of MBS processes having the lowest priority.

[0012] A fifth exemplary method of wireless communication includes operating, by a medium access control (MAC) entity of a user equipment, a hybrid automatic repeat request (HARQ) entity and a number of multicast and broadcast service (MBS) processes, where the HARQ entity is an MBS HARQ entity for the MBS service, and the MBS process corresponds to the MBS HARQ entity; receiving a transport block (TB) and associated HARQ information from the MBS HARQ entity for each duration on the shared channel during which transmission is made for the MBS process; and upon determining that HARQ feedback is enabled by downlink control information (DCI), instructing a physical layer to generate an acknowledgment for data in the transport block in response to the HARQ feedback being configured for separate HARQ resources or instructing the physical layer to generate an acknowledgment for data in the transport block in response to the HARQ feedback being configured for shared HARQ resources.

[0013] A sixth exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; making, by the user equipment, a first determination that a downlink assignment has been received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; making a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of a Medium Access Control (MAC) entity; making a third determination that a previous downlink assignment indicated to a HARQ entity of the HARQ process is associated with an MBS-Associated Radio Network Temporary Identifier (RNTI) of the MAC entity, the previous downlink assignment having been received prior to the downlink assignment; and determining, based on the third determination, that a new data indicator (NDI) value has been toggled.

[0014] A seventh exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; making, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; making a second determination that the downlink assignment is associated with an MBS associated radio network temporary identifier (RNTI) of a medium access control (MAC) entity; and performing a HARQ process. making a third determination that the previous downlink allocation indicated to the ARQ entity is associated with another MBS-related RNTI of the MAC entity, or a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) of the MAC entity, or a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity, or a third determination that the previous downlink allocation indicated to the HARQ entity of the HARQ process is a configured downlink allocation, where the previous downlink allocation was received prior to the downlink allocation; and determining based on the third determination that a new data indicator (NDI) value is toggled.

[0015] An eighth exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process, making, by the user equipment, a first determination that a downlink assignment has been received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected, making a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI), making a third determination that a previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with an MBS service having a lower priority than that of a unicast service, the previous downlink assignment having been received prior to the downlink assignment, and determining, based on the third determination, that a new data indicator (NDI) value has been toggled. In some embodiments, the priority of the MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). In some embodiments, the method further includes, in response to the third determination, providing HARQ information associated with the data in the downlink assignment to a HARQ entity.

[0016] A ninth exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process; making, by the user equipment, a first determination that a downlink assignment has been received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; making a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI); making a third determination that a previous downlink assignment indicated to a HARQ entity of the HARQ process is associated with an MBS service having a priority greater than or equal to that of a unicast service, the previous downlink assignment having been received prior to the downlink assignment; and determining that the downlink assignment should be ignored.

[0017] A tenth exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process; making, by the user equipment, a first determination that a downlink assignment has been received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; making a second determination that the downlink assignment is associated with an MBS-related Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity; making a third determination that a previous downlink assignment indicated to a HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a lower priority than that of the MBS-related RNTI, the previous downlink assignment having been received prior to the downlink assignment; and determining, based on the third determination, that a new data indicator (NDI) value has been toggled. In some embodiments, the priority of the another MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). In some embodiments, the method further includes providing, to a HARQ entity, HARQ information associated with the data in the downlink assignment in response to the third determination.

[0018] An eleventh exemplary method of wireless communication includes operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; making, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; making a second determination that the downlink assignment is associated with an MBS-related Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity; making a third determination that a previous downlink assignment indicated to a HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a priority higher than or equal to that of the MBS-related RNTI, the previous downlink assignment being received prior to the downlink assignment; and determining that the downlink assignment should be ignored.

[0019] In yet another exemplary aspect, the methods described above are embodied in the form of processor executable code and stored in a non-transitory computer readable storage medium, the code contained on the computer readable storage medium, when executed by a processor, causes the processor to implement the methods described in this patent document.

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

[0021] These and other aspects and their implementations are described in detail in the drawings, description, and claims. The present invention provides, for example, the following: (Item 1) 1. A wireless communication method, the method comprising: receiving, by a first network node, priority information from a second network node, the priority information indicating a priority of a multicast and broadcast service (MBS); determining, by the first network, a reception priority of the MBS based on the priority indicated by the priority information; A method comprising: (Item 2) 2. The method of claim 1, wherein the priority information includes the priority of an identifier associated with the MBS. (Item 3) Item 2. The method of item 1, wherein the identifier comprises an MBS service identifier, an MBS session identifier, a Temporary Mobile Group Identifier (TMGI), a part of a Quality of Service (QoS) flow in an MBS session, a Multicast Radio Bearer (MRB) identifier, or a unique identification of an interface through which the MBS service or MBS session is established between the first network node and the second network node. (Item 4) 2. The method of claim 1, wherein the priority information includes an indication of whether one or more user equipment connected to the first network node prioritizes reception of multiple Multimedia Broadcast Multicast Services (MBMS) over reception of any one unicast service. (Item 5) 2. The method according to claim 1, wherein the priority information includes a list of MBS services that one or more user equipments are receiving or are interested in receiving. (Item 6) 6. The method of claim 5, wherein the list of MBS services includes one or more identifiers arranged in an order indicating the priority of the one or more identifiers. (Item 7) 2. The method of claim 1, wherein the priority information is associated with an identifier of a user equipment, or the priority information is associated with a plurality of user equipments receiving the MBS or a plurality of user equipments interested in receiving the MBS. (Item 8) 2. The method according to item 1, wherein the priority information is received via a Next Generation Application Protocol (NGAP) message using MBS session association signaling. (Item 9) 2. The method according to claim 1, wherein the priority information is received via a Next Generation Application Protocol (NGAP) message using user equipment association signaling. (Item 10) 2. The method according to item 1, wherein the priority information is received via an F1 Application Protocol (F1AP) message using MBS session association signaling. (Item 11) 2. The method according to claim 1, wherein the priority information is received via an F1 Application Protocol (F1AP) message using user equipment association signaling. (Item 12) 2. The method according to claim 1, wherein the priority information is received via a radio resource control (RRC) message or a user equipment dedicated medium access control-control element (MAC CE). (Item 13) 2. The method of claim 1, wherein the priority information is received via a radio resource control (RRC) message over a broadcast channel. (Item 14) 2. The method according to claim 1, wherein the priority information is received via system information or a medium access control-control element (MAC CE) broadcast in a cell. (Item 15) Item 2. The method of item 1, wherein the first network node includes a base station and the second network node includes a core network. (Item 16) Item 1. The method of item 1, wherein the first network node includes a distributed unit and the second network node includes a central unit. (Item 17) Item 2. The method of item 1, wherein the first network node includes a user equipment and the second network node includes a base station. (Item 18) 2. The method of claim 1, wherein the first network node includes a base station and the second network node includes a user equipment. (Item 19) 1. A wireless communication method, the method comprising: determining, by a user equipment, that a number of transmissions scheduled for the user equipment over a shared channel exceeds a capability of the user equipment; and effecting reception of one or more of the plurality of transmissions based on a priority of a multicast and broadcast service (MBS). Including, The method, wherein the priority of the MBS is indicated by a higher layer or by a medium access control element (MAC CE). (Item 20) 1. A wireless communication method, the method comprising: determining, by a medium access control (MAC) entity of the user equipment, that a received downlink assignment for an MBS-associated radio network temporary identifier (RNTI) and associated hybrid automatic repeat request (HARQ) information is indicated to a HARQ entity; The HARQ entity is an MBS HARQ entity for an MBS service, managing an MBS process; With respect to the downlink allocation, the MBS HARQ entity directs a transport block (TB) to an MBS process indicated in the associated HARQ information. (Item 21) 21. The method of claim 20, wherein the MAC entity is configured to receive the downlink allocation associated with the MBS-related RNTI by a higher layer. (Item 22) 1. A wireless communication method, the method comprising: determining, by a medium access control (MAC) entity of the user equipment, that a received downlink assignment for an MBS-associated radio network temporary identifier (RNTI) and associated hybrid automatic repeat request (HARQ) information is indicated to a HARQ entity; The HARQ entity is an MBS HARQ entity for an MBS service, managing an MBS process; With respect to the downlink assignment, the MBS HARQ entity allocates one or more received transport blocks and associated HARQ information to an unoccupied MBS process; and associating the MBS process with the MBS-related RNTI for the downlink assignment; A method comprising: (Item 23) Upon receiving a new transport block, the MBS HARQ entity performs a determination that it does not include an unoccupied MBS process; in response to implementing the determination, considering the occupied MBS process corresponding to the MBS service with the lowest priority as an unoccupied MBS process; 23. The method of claim 22, further comprising: (Item 24) 24. The method of claim 23, wherein the occupied MBS process is selected or randomly selected from the plurality of MBS processes having the lowest priority. (Item 25) 1. A wireless communication method, the method comprising: operating a Hybrid Automatic Repeat Request (HARQ) entity and a number of Multicast and Broadcast Service (MBS) processes by a Medium Access Control (MAC) entity of the user equipment; the HARQ entity is an MBS HARQ entity for an MBS service; The MBS process corresponds to the MBS HARQ entity; and receiving, for each duration on the shared channel during which transmission is performed for an MBS process, a transport block (TB) and associated HARQ information from the MBS HARQ entity; Upon determining that HARQ feedback is enabled by downlink control information (DCI), instructing a physical layer to generate an acknowledgement for data in the transport block in response to the HARQ feedback being configured for a separate HARQ resource; or instructing the physical layer to generate the acknowledgment for data in the transport block in response to the HARQ feedback being configured for a shared HARQ resource; A method comprising: (Item 26) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of a Medium Access Control (MAC) entity; and performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS Associated Radio Network Temporary Identifier (RNTI) of the MAC entity, the previous downlink allocation having been received prior to the downlink allocation; and determining that a new data indicator (NDI) value has been toggled based on the third determination; A method comprising: (Item 27) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with an MBS Associated Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity; performing a third determination that the previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with another MBS-related RNTI of the MAC entity, or a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) of the MAC entity, or a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity, or a third determination that the previous downlink allocation indicated to the HARQ entity of the HARQ process is a configured downlink allocation, the previous downlink assignment having been received prior to the downlink assignment. And, determining that a new data indicator (NDI) value has been toggled based on the third determination; A method comprising: (Item 28) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI); and performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service having a lower priority than that of a unicast service, the previous downlink allocation having been received prior to the downlink allocation; determining that a new data indicator (NDI) value has been toggled based on the third determination; A method comprising: (Item 29) 29. The method according to claim 28, wherein the priority of the MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). (Item 30) 30. The method of claim 28, further comprising providing HARQ information associated with data in the downlink assignment to the HARQ entity in response to the third determination. (Item 31) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI); and performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service having a priority higher than or equal to that of a unicast service, the previous downlink allocation having been received prior to the downlink allocation; determining that the downlink assignment should be ignored; A method comprising: (Item 32) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with an MBS Associated Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity; performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a lower priority than that of the MBS-related RNTI, the previous downlink allocation having been received prior to the downlink allocation; determining that a new data indicator (NDI) value has been toggled based on the third determination; A method comprising: (Item 33) Item 33. The method according to item 32, wherein the priority of the other MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). (Item 34) 33. The method of claim 32, further comprising providing HARQ information associated with data in the downlink assignment to the HARQ entity in response to the third determination. (Item 35) 1. A wireless communication method, the method comprising: operating, by a user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service; performing, by a user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment for an occasion on the control channel and for a serving cell to which the user equipment is connected; performing a second determination that the downlink assignment is associated with an MBS Associated Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity; performing a third determination that a previous downlink allocation indicated to a HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a priority higher than or equal to that of the MBS-related RNTI, the previous downlink allocation having been received prior to the downlink allocation; determining that the downlink assignment should be ignored; A method comprising: (Item 36) 36. An apparatus for wireless communication comprising a processor configured to implement the methods described in one or more of items 1-35. (Item 37) A non-transitory computer readable program storage medium storing code that, when executed by a processor, causes the processor to implement a method according to one or more of items 1-35. [Brief description of the drawings]

[0022] [Figure 1] FIG. 1 shows an exemplary flowchart for managing priority information indicating the priority of a multicast and broadcast service (MBS).

[0023] [Diagram 2] FIG. 2 illustrates an example flowchart for managing Multicast and Broadcast Service (MBS) Associated Radio Network Temporary Identifiers (RNTIs) or MBS priorities when the number of transmissions exceeds the capabilities of a UE.

[0024] [Diagram 3] FIG. 3 shows an exemplary flow chart for operating a MAC entity of a UE.

[0025] [Figure 4]FIG. 4 shows an exemplary flow chart for operating a MAC entity of a UE.

[0026] [Diagram 5] FIG. 5 shows an exemplary flow chart for operating a MAC entity of a UE.

[0027] [Figure 6] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0028] [Figure 7] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0029] [Figure 8] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0030] [Figure 9] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0031] [Figure 10A] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0032] [Figure 10B] FIG. 6-10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE.

[0033] [Figure 11] FIG. 11 illustrates an example block diagram of a hardware platform that may be part of a network node.

[0034] [Figure 12] FIG. 12 shows an example block diagram of the relationship between a medium access control (MAC) entity and one or more hybrid automatic repeat request (HARQ) entities. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] This patent application describes, among other things, techniques that enable a Radio Access Network (RAN) system to obtain and handle information regarding the priority of MBS services. In this patent document, the term Group Radio Network Temporary Identifier (G-RNTI) may include Radio Network Temporary Identifiers (RNTIs) (also known as MBS-related RNTIs) used for multicast and broadcast services / sessions. The term G-RNTI may be referred to by other names related to MBS services or sessions. The example headings for the various sections below are used to facilitate understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Thus, one or more features of one example section may be combined with one or more features of another example section. Furthermore, although 5G terminology is used for clarity of explanation, the techniques disclosed herein are not limited to only 5G technology and may be used in wireless systems implementing other protocols.

[0036] (Example 1. (MBS priority information can be transmitted from the CN to the RAN by MBS session association signaling)

[0037] The MBS priority information may be included in a message sent from the core network (e.g., 5G Core Access and Mobility Management Function (AMF)) to the base station (e.g., RAN node). The procedure may use MBS session association signaling. The message may be an MBS SESSION RESOURCE SETUP REQUEST message or an MBS SESSION RESOURCE MODIFY REQUEST message. The MBS SESSION RESOURCE SETUP REQUEST message is used to allocate resources over the air interface (Uu) and / or the next generation user plane interface (NG-U) for one or several MBS services and corresponding quality of service (QoS) flows, and to configure corresponding multicast radio bearers (MRBs). The MBS SESSION RESOURCE MODIFY REQUEST message is used to enable configuration modification of already established MBS sessions. The MBS SESSION RESOURCE MODIFY REQUEST message is also used to enable the setup, modification, and release of QoS flows for already established MBS sessions.

[0038] The MBS priority information may be associated with each UE ID, or with all UEs receiving (or interested in receiving) the MBS session. The UE ID may be an AMF UE NGAP ID, or a RAN UE NGAP ID.

[0039] The content of the MBS priority information can be designed as follows.

[0040] In one example, MBS priority information may be included for each MBS ID. The MBS ID may be an MBS service ID, an MBS session ID, a Temporary Mobile Group Identifier (TMGI), a part of a QoS flow in an MBS session, an AMF MBS NGAP ID that uniquely identifies an MBS service / session association over an NG interface, or a RAN MBS NGAP ID that uniquely identifies an MBS service / session association over an NG interface in a RAN node. The MBS priority information may include a priority of the MBS ID. For example, the MBS priority information may be an integer ranging from 1 to a fixed value (e.g., 256).

[0041] In another example, the MBS priority information is implicitly indicated in a message sent from the core network to the base station, the message including a list of MBS services that the UE is receiving (or is interested in receiving), and the MBS priority information for each MBS ID is implicitly indicated by the ranking order of the MBS ID in the list.

[0042] In another example, the MBS priority information may include an indication of whether the associated UE prioritizes reception of all MBMS services over reception of any of the unicast services.

[0043] If the MBS priority information is included in a message sent from the core network to the base station, the base station may use it to determine a priority for scheduling MBS services for an associated UE, or the base station may take UE priority into account with respect to receiving MBS services and unicast services.

[0044] (Example 2. (MBS priority information can be transmitted from CN to RAN by UE association signaling))

[0045] The MBS priority information may be included in a message sent from a core network (e.g., AMF) to a base station (e.g., RAN node). The procedure may use UE association signaling. The message may be a PDU SESSION RESOURCE SETUP REQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

[0046] The content of the MBS priority information can be designed as follows.

[0047] In one example, MBS priority information may be included for each MBS ID. The MBS ID may be an MBS service ID, an MBS session ID, a TMGI, a part of the QoS flows in the MBS session, an AMF MBS NGAP ID, or a RAN MBS NGAP ID. The MBS priority information may include a priority of the MBS ID. The MBS priority information may be an integer ranging from 1 to a fixed value (e.g., 256). The MBS priority information is associated with the MBS ID. The MBS ID may be an MBS service ID, an MBS session ID, a TMGI, a part of the QoS flows in the MBS session.

[0048] In another example, the MBS priority information is implicitly indicated in a message sent from the core network to the base station, the message including a list of MBS services that the UE is receiving (or is interested in receiving), and the MBS priority information for each MBS ID is implicitly indicated by the ranking order of the MBS ID in the list.

[0049] In another example, the MBS priority information may include an indication of whether the UE prioritizes reception of all MBMS services over reception of any of the unicast services.

[0050] If the MBS priority information is included in a message sent from the core network to the base station, the base station may use it to determine a priority for scheduling the MBS ID for the associated UE, or the base station may take the UE priority into account with respect to receiving MBS services and unicast services.

[0051] (Example 3. (MBS priority information can be transmitted from gNB-CU to gNB-DU by MBS association F1AP signaling)

[0052] Example 3 describes how priority information for each MBS ID is transmitted from the gNB-CU to the gNB-DU. The MBS priority information may be included in a message sent from a central unit (e.g., gNB-CU) to a distributed unit (e.g., gNB-DU). The procedure may use MBS session association signaling. The message may be an MBS CONTEXT SETUP REQUEST message or an MBS CONTEXT MODIFY REQUEST message. The MBS CONTEXT SETUP REQUEST message is used to establish an MBS context, including, among other things, the MRB configuration. The MBS CONTEXT MODIFY REQUEST message is used to modify an established MBS context, e.g., to establish, modify, and release radio resources.

[0053] MBS priority information may be associated with each UE ID, or with all UEs receiving (or interested in receiving) the MBS session.

[0054] The content of the MBS priority information can be designed as follows.

[0055] In one example, MBS priority information may be included for each MBS ID. The MBS ID may be an MRB ID, an MBS service ID, an MBS session ID, a TMGI, a gNB-CU MBS F1AP ID, or a gNB-DU MBS F1AP ID. The gNB-CU MBS F1AP ID identifies an MBS session / service association over an F1 interface in a gNB-CU. The gNB-DU MBS F1AP ID identifies an MBS session / service association over an F1 interface in a gNB-DU. The MBS priority information may include a priority of the MBS ID for an associated UE. For example, the MBS priority information may be an integer ranging from 1 to a fixed value (e.g., 256).

[0056] In another example, the MBS priority information is implicitly indicated in a message sent from the CU to the DU, the message containing a list of MBD IDs that the UE is receiving (or is interested in receiving), and the MBS priority information for each MBS ID is implicitly indicated by the ranking order of the MBS ID in the list.

[0057] In another example, the MBS priority information may include an indication of whether the associated UE prioritizes reception of all MBMS services over reception of any of the unicast services.

[0058] If the MBS priority information is included in the message sent from the central unit to the distributed units, the distributed units may use it to determine the priority for scheduling the MBS ID for the associated UE, or the base station may take the UE priority into account with respect to receiving MBS services and unicast services.

[0059] (Example 4. (MBS priority information can be transmitted from gNB-CU to gNB-DU by UE associated F1AP signaling))

[0060] Example 4 describes how priority information for each MBS ID is transmitted from the gNB-CU to the gNB-DU. The MBS priority information may be included in a message sent from a central unit (e.g., gNB-CU) to a distributed unit (e.g., gNB-DU). The procedure may use UE association signaling. The message may be a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0061] The content of the MBS priority information can be designed as follows.

[0062] In one example, MBS priority information may be included for each MBS ID. The MBS ID may be an MRB ID, an MBS service ID, an MBS session ID, a TMGI, a G-RNTI, a gNB-CU UE F1AP ID, or a gNB-DU UE F1AP ID. The MBS priority information may include a priority of the MBS ID for the UE. For example, the MBS priority information may be an integer ranging from 1 to a fixed value (e.g., 256).

[0063] In another example, the MBS priority information is implicitly indicated in a message sent from the core network to the base station, the message including a list of MBS IDs that the UE is receiving (or is interested in receiving), and the MBS priority information for each MBS ID is implicitly indicated by the ranking order of the MBS ID in the list.

[0064] In another example, the MBS priority information may include an indication of whether the UE prioritizes reception of all MBMS services over reception of any of the unicast services.

[0065] If the MBS priority information is included in the message sent from the central unit to the distributed units, the distributed units may use it to determine the priority for scheduling the MBS ID for the UE, or the base station may take the UE priority into account with respect to receiving MBS services and unicast services.

[0066] (Example 5. (MBS priority information can be transmitted between UE and RAN by RRC / system information / MAC CE))

[0067] Example 5 describes how the priority information for each MBS ID is transmitted between the UE and the RAN. The MBS priority information can be transmitted from the UE to the base station, or the MBS priority information can be transmitted from the base station to the UE.

[0068] The procedure may be initiated upon at least one of the following conditions: upon change of interest, upon change of bearer mode, upon change of priority of the MBS service, upon change of priority between MBS reception and unicast reception.

[0069] The MBS priority information may be included in an RRC message or system information or MAC CE.

[0070] The content of the MBS priority information can be designed as follows.

[0071] In one example, MBS priority information may be included for each MBS ID. The MBS ID may be an MBS service ID, an MBS session ID, a TMGI, a G-RNTI, or part of a QoS flow in an MBS session that is of interest (or has been received) by the UE. The MBS priority information may include a priority of the MBS ID. The MBS priority information may be an integer ranging from 1 to a fixed value (e.g., 256). The MBS priority information is associated with an MBS service ID. The MBS ID may be an MBS service ID, an MBS session ID, a TMGI, or part of a QoS flow in an MBS session.

[0072] In another example, the MBS priority information is implicitly indicated in a message sent from the UE to the base station, the message including a list of MBS services that the UE is receiving (or is interested in receiving), and the MBS priority information for each MBS ID is implicitly indicated by the ranking order of the MBS ID in the list.

[0073] In another example, the MBS priority information may include an indication of whether the UE prioritizes reception of all MBMS services over reception of any of the unicast services.

[0074] In another example, the MBS priority information may include a priority threshold for unicast services and / or a priority threshold for multicast services.

[0075] In another example, for an example scenario in which the UE transmits MBS priority information to the RAN, the UE may set a value of the MBS priority information for each MBS ID according to information related to service priority from an application layer.

[0076] In another example, for an example scenario in which the RAN transmits MBS priority information to the UE, the base station may set a value of the MBS priority information for each MBS ID according to at least one of the following information: priority information of the QoS flow (e.g., ARP), MBS priority information received from the core network.

[0077] In another example, for an example scenario in which the RAN transmits MBS priority information to the UE, the distributed unit may set a value of the MBS priority information for each MBS ID according to at least one of the following information: priority information of the QoS flow (e.g., ARP), MBS priority information received from the central unit, priority information of the DRB / MRB.

[0078] If the MBS priority information is received by the base station, the base station may use it to determine a priority for scheduling the MBS ID for the UE, or the base station may take the UE priority into consideration with respect to receiving MBS services and unicast services.

[0079] FIG. 1 illustrates an exemplary flow chart for managing priority information indicating a priority of a multicast and broadcast service (MBS). Operation 102 includes receiving, by a first network node, priority information from a second network node indicating a priority of the multicast and broadcast service (MBS). Operation 104 includes determining, by the first network node, a reception priority of the MBS based on the priority indicated by the priority information. In some embodiments, the priority information includes a priority of an identifier associated with the MBS. In some embodiments, the identifier includes an MBS service identifier, an MBS session identifier, a Temporary Mobile Group Identifier (TMGI), a portion of a Quality of Service (QoS) flow in the MBS session, a Multicast Radio Bearer (MRB) identifier, or a unique identification of an interface over which the MBS service or MBS session is established between the first network node and the second network node.

[0080] In some embodiments, the priority information includes an indication of whether one or more user equipments connected to the first network node prioritize reception of multiple Multimedia Broadcast Multicast Services (MBMS) over reception of any one unicast service. In some embodiments, the priority information includes a list of MBS services that one or more user equipments are receiving (or are interested in receiving). In some embodiments, the list of MBS services includes one or more identifiers arranged in an order indicating a priority of the one or more identifiers. In some embodiments, the priority information is associated with an identifier of a user equipment or the priority information is associated with multiple user equipments receiving (or are interested in receiving) the MBS.

[0081] In some embodiments, the priority information is received via a Next Generation Application Protocol (NGAP) message using MBS session association signaling. In some embodiments, the priority information is received via a Next Generation Application Protocol (NGAP) message using user equipment association signaling. In some embodiments, the priority information is received via an F1 Application Protocol (F1AP) message using MBS session association signaling. In some embodiments, the priority information is received via an F1 Application Protocol (F1AP) message using user equipment association signaling. In some embodiments, the priority information is received via a Radio Resource Control (RRC) message or a user equipment dedicated Medium Access Control-Control Element (MAC CE).

[0082] In some embodiments, the priority information is received via a radio resource control (RRC) message over a broadcast channel. In some embodiments, the priority information is received via system information or a medium access control-control element (MAC CE) broadcast within a cell. In some embodiments, the first network node includes a base station and the second network node includes a core network. In some embodiments, the first network node includes a distributed unit and the second network node includes a central unit. In some embodiments, the first network node includes a user equipment and the second network node includes a base station. In some embodiments, the first network node includes a base station and the second network node includes a user equipment.

[0083] Example 6. UE behavior can be influenced by priority information through the following methods:

[0084] Example 6 describes possible ways in which priority information can affect MAC behavior: If a UE is scheduled with PDSCH transmissions that exceed its processing capabilities, the MAC entity prioritizes the reception of these PDSCH transmissions according to the priority of each G-RNTI / MBS service, where the priority is indicated / configured by higher layers or indicated by the MAC CE.

[0085] The number of G-RNTI / MBS services for parallel reception is limited according to the processing capability of the UE.

[0086] The G-RNTI / MBS service with the higher priority is prioritized to be received.

[0087] In another example, the priority of PDSCH transmissions or downlink allocations for multicast / broadcast / unicast services is included in the DCI, and the MAC entity of the UE prioritizes these PDSCH transmissions according to the priority information indicated on the DCI.

[0088] In another example, information regarding a priority threshold for unicast services and / or a priority threshold for multicast services may be configured in the UE by the base station via an RRC message or MAC CE, and the UE prioritizes transmissions for MBSs or unicast services with a priority indicated on the DCI higher than the threshold configured by the higher layer or MAC CE.

[0089] 2 shows an example flowchart for managing MBS-related radio network temporary identifiers (RNTIs) or priorities of multicast and broadcast services (MBS) when the number of transmissions exceeds the capabilities of the UE. Operation 202 includes determining, by the user equipment, that the number of multiple transmissions scheduled for the user equipment over a shared channel exceeds the capabilities of the user equipment. Operation 204 includes effecting reception of one or more of the multiple transmissions based on the priority of the multicast and broadcast services (MBS), where the priority of the MBS is indicated by a higher layer or by a medium access control element (MAC CE).

[0090] Example 7. UE and RAN behavior can be influenced by priority information through the following methods:

[0091] Examples of RAN behavior are as follows:

[0092] Example 7-1. The RAN may make scheduling decisions based on MBS priority information, for example, when a HARQ process is shared between unicast and multicast services. The RAN may determine downlink allocations based on the MBS priority information.

[0093] Examples of UE behavior are as follows:

[0094] According to the downlink allocation received on the PDCCH, the MAC entity of the UE has the following actions:

[0095] Example 7-1 describes an example of UE behavior when HARQ processes are not shared between unicast and multicast services. Details of Example 7-1 are as follows:

[0096] Example 7-1. In one example, for each serving cell, there is at most one MBS HARQ entity in the MAC entity for multicast / broadcast reception, which maintains several parallel MBS processes. In another example, the MBS HARQ entity is a HARQ entity, which maintains several parallel HARQ processes for unicast services and several parallel MBS processes for multicast services. Each MBS process is associated with a G-RNTI or MBS service of downlink allocation. This interest is indicated by higher layers. The MBS HARQ entity directs the MBS transmission information and associated TBs received on the DL-SCH to the corresponding MBS process. The number of receiving MBS processes associated with the MBS HARQ entity is defined as a constant.

[0097] Examples of MAC entity behavior include at least one of the following:

[0098] When the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI or a G-RNTI, the MAC entity may perform the following operations for each PDCCH occasion for which it monitors a PDCCH and for each serving cell: 1> If a downlink allocation for this PDCCH occasion is received on the PDCCH for G-RNTI, 2> Indicate the presence of a downlink allocation and deliver the associated HARQ information and G-RNTI to the MBS HARQ entity.

[0099] Examples of HARQ entity behavior include at least one of the following:

[0100] The MBS HARQ entity may perform the following operations: 1>For each downlink allocation indicated to the MBS HARQ entity: 2> If NDI has been toggled compared to the value of the previous received transmission corresponding to this TB, or if this is the very first received transmission for this TB: 3> Allocate the TB and associated HARQ information received from the physical layer to an unoccupied MBS process, associate the MBS process with this G-RNTI or the corresponding MBS service, and consider this transmission to be a new transmission.

[0101] NOTE 1: If there are no unoccupied MBS processes in the MBS HARQ entity when a new TB arrives, it is up to the UE implementation how to manage the receiving MBS processes.

[0102] NOTE 2: When a new TB arrives, if there is no unoccupied MBS process in the MBS HARQ entity, the occupied MBS process with the lowest priority is allocated to the unoccupied MBS process. If there are several MBS processes with the lowest priority, any one of these several MBS processes can be allocated to this TB.

[0103] 1>For each MBS process: 2> If the NDI has not been toggled according to its associated SCI compared to the value of the previous received transmission corresponding to this TB for the MBS process; 3> Allocate the TB received from the physical layer to the MBS process and consider this transmission as a retransmission. 2> Else, if the HARQ buffer of the MBS process is not empty, 3> Flush the HARQ buffer.

[0104] Examples of MBS process behavior include at least one of the following actions:

[0105] For each PDSCH duration during which transmission occurs for an MBS process, one TB and associated HARQ information is received from the MBS HARQ entity.

[0106] For each received TB and associated MBS transmission information, the MBS process may perform the following operations: 1> If this is a new transmission: 2> Attempt to decode the received data. 1> Otherwise, if this is a retransmission: 2> If the data about this TB has not yet been successfully decoded, 3> Instruct the physical layer to combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data. 1> If the data that the MAC entity attempted to decode was successfully decoded for this TB: or 1> If the data about this TB was previously successfully decoded: 2> Deliver the decoded MAC PDU to the disassembly and demultiplexing entity; 2> Consider the MBS process as unoccupied. 1> Otherwise, 2> Instruct the physical layer to replace the data in the soft buffer for this TB with the data that the MAC entity attempted to decode. 1> If HARQ feedback is enabled by DCI or higher layers: 2> if the HARQ feedback corresponding to this TB is configured in [separate resource]; or 2> If the HARQ feedback corresponding to this TB is configured in [Shared Resources]; 3> Command the physical layer to generate an acknowledgment for the data in this TB.

[0107] In another example, information indicating whether HARQ feedback is enabled or disabled is transmitted to the UE via a DCI or MAC CE or RRC message.

[0108] Example 7-2 describes an example of UE behavior when HARQ processes are shared between unicast and multicast services. The HARQ entity manages several HARQ processes for both unicast and multicast services. Details of Example 7-2 are as follows.

[0109] In one example, the UE receives the latest instructions (eg, DCI) and acts accordingly. The behavior of the UE's MAC entity includes at least one of the following actions:

[0110] When the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI or a G-RNTI, the MAC entity may perform the following operations for each PDCCH occasion on which it monitors a PDCCH and for each serving cell. 1> if a downlink allocation for this PDCCH occasion and this serving cell is received on the PDCCH for the C-RNTI or temporary C-RNTI of the MAC entity, 2> if this is the first downlink allocation for this temporary C-RNTI; 3>NDI is considered to be toggled. 2> if the downlink allocation relates to the C-RNTI of the MAC entity and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the G-RNTI of the MAC entity; 3> NDI is considered to be toggled regardless of the value of NDI. 2> Indicate the presence of a downlink allocation and deliver the associated HARQ information to the HARQ entity. 1> If a downlink allocation for this PDCCH occasion and this serving cell is received on the PDCCH for the G-RNTI of the MAC entity: 2> if the downlink allocation relates to the C-RNTI of the MAC entity and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was either a downlink allocation received for the CS-RNTI or C-RNTI of the MAC entity or another G-RNTI, or a configured downlink allocation; 3> NDI is considered to be toggled regardless of the value of NDI. 2> Indicate the presence of a downlink allocation and deliver the associated HARQ information to the HARQ entity.

[0111] In another example, the UE behavior is influenced by the priority information and the received instruction (e.g., DCI). The HPN (HARQ process number) indicated in the HARQ information is used for the associated downlink allocation for the G-RNTI. The behavior of the UE MAC entity includes at least one of the following actions:

[0112] When the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI or a G-RNTI, the MAC entity may perform the following operations for each PDCCH occasion on which it monitors a PDCCH and for each serving cell. 1> if a downlink allocation for this PDCCH occasion and this serving cell is received on the PDCCH for the C-RNTI or G-RNTI of the MAC entity, 2> if the downlink allocation is for the C-RNTI of the MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the G-RNTI of the MAC entity with a lower priority than the C-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE, 3> NDI is considered to be toggled regardless of the value of NDI. 3> Indicate the presence of a downlink allocation for this serving cell and deliver the associated HARQ information to the HARQ entity. 2> if the downlink allocation is for the C-RNTI of the MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the G-RNTI of the MAC entity with a priority higher than or equal to the C-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE, 3> Ignore downlink allocations. 2> if the downlink allocation is for a G-RNTI of a MAC entity, and if a previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for a C-RNTI of the MAC entity or another G-RNTI with a lower priority than this G-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE, 3> NDI is considered to be toggled regardless of the value of NDI. 3> Indicate the presence of a downlink allocation for this serving cell and deliver the associated HARQ information to the HARQ entity. 2> if the downlink allocation is for the G-RNTI of the MAC entity, and if a previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the C-RNTI of the MAC entity or another G-RNTI with a priority higher than or equal to this G-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE, 3> Ignore downlink allocations.

[0113] In another example, the UE behavior is influenced by the priority information and the received instruction (e.g., DCI). The occupied HPN (HARQ process number) can be used for the associated downlink allocation for the G-RNTI. The behavior of the UE MAC entity includes at least one of the following actions:

[0114] When the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI or a G-RNTI, the MAC entity may perform the following operations for each PDCCH occasion on which it monitors a PDCCH and for each serving cell. 1> If a downlink allocation for this PDCCH occasion and this serving cell is received on the PDCCH for the C-RNTI or G-RNTI of the MAC entity: 2> if the downlink allocation relates to the C-RNTI of the MAC entity and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the G-RNTI of the MAC entity with a lower priority than the C-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE; 3> NDI is considered to be toggled regardless of the value of NDI. 3> Indicate the presence of a downlink allocation for this serving cell and deliver the associated HARQ information to the HARQ entity. 2> if the downlink allocation is for the C-RNTI of the MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the G-RNTI of the MAC entity with a priority higher than or equal to the C-RNTI, the priority is indicated / configured by higher layers or indicated by the MAC CE, 3> Ignore downlink allocations. 2> if the downlink allocation concerns the G-RNTI of the MAC entity; 3> Indicate the presence of a downlink allocation for this serving cell and deliver the associated HARQ information to the HARQ entity. The HARQ entity may perform the following operations: 1>For each downlink allocation associated with a G-RNTI and indicated to the HARQ entity: 2>If NDI is toggled compared to the value of the previous received transmission corresponding to this TB, or if this is the very first received transmission relating to this TB; 3> Allocate the TB and associated HARQ information received from the physical layer to an unoccupied MBS process, associate the HARQ process with this G-RNTI, and consider this transmission as a new transmission. Note: When a new TB arrives, if there are no unoccupied HARQ processes in the HARQ entity, the occupied HARQ process with the lowest priority is allocated to the unoccupied MBS process. If there are several HARQ processes with the lowest priority, any one of these several HARQ processes can be allocated to this TB.

[0115] Figure 12 shows an example block diagram of the relationship between a MAC entity and one or more HARQ entities. The left side of Figure 12 shows the relationship between the MAC entity 1202, the HARQ entities, and processes, where the HARQ processes and the MBS processes are not shared between unicast and MBS services. The right side of Figure 12 shows the relationship between the MAC entity 1204, the HARQ entities, and the HARQ processes, where the HARQ processes are shared by unicast and MBS services.

[0116] 3 shows an example flowchart for operating a MAC entity of a UE. Operation 302 includes determining, by a Medium Access Control (MAC) entity of the user equipment, that a received downlink allocation for an MBS-related Radio Network Temporary Identifier (RNTI) and associated Hybrid Automatic Repeat Request (HARQ) information are indicated to a HARQ entity, the HARQ entity being an MBS HARQ entity for an MBS service, managing an MBS process, and for a downlink allocation, the MBS HARQ entity directs a transport block (TB) to the MBS process indicated in the associated HARQ information. In some embodiments, the MAC entity is configured by a higher layer to receive a downlink allocation associated with the MBS-related RNTI.

[0117] 4 shows an example flowchart for operating a MAC entity of a UE. Operation 402 includes determining by a Medium Access Control (MAC) entity of the user equipment that a received downlink allocation for an MBS-related Radio Network Temporary Identifier (RNTI) and associated Hybrid Automatic Repeat Request (HARQ) information are indicated to a HARQ entity, the HARQ entity being an MBS HARQ entity for an MBS service, managing an MBS process, and for the downlink allocation, the MBS HARQ entity allocates one or more received transport blocks and associated HARQ information to an unoccupied MBS process. Operation 404 includes associating the MBS process with the MBS-related RNTI for the downlink allocation.

[0118] In some embodiments, the method further includes, upon receiving the new transport block, making a determination that the MBS HARQ entity does not include an unoccupied MBS process, and in response to making the determination, considering an occupied MBS process corresponding to an MBS service with the lowest priority as an unoccupied MBS process. In some embodiments, the occupied MBS process is selected or randomly selected from the multiple MBS processes having the lowest priority.

[0119] 5 shows an example flowchart for operating a MAC entity of a UE. Operation 502 includes operating a Hybrid Automatic Repeat Request (HARQ) entity and several Multicast and Broadcast Service (MBS) processes by a Medium Access Control (MAC) entity of the user equipment, where the HARQ entity is an MBS HARQ entity for the MBS service, and the MBS process corresponds to the MBS HARQ entity. Operation 504 includes receiving a transport block (TB) and associated HARQ information from the MBS HARQ entity for each duration on the shared channel during which transmission is made for the MBS process. Operation 506 includes, upon determining that HARQ feedback is enabled by the downlink control information (DCI), instructing the physical layer to generate an acknowledgment for the data in the transport block in response to the HARQ feedback being configured for separate HARQ resources, or instructing the physical layer to generate an acknowledgment for the data in the transport block in response to the HARQ feedback being configured for shared HARQ resources.

[0120] FIG. 6 illustrates an exemplary flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 602 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service. Operation 604 includes performing, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 606 includes performing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of a Medium Access Control (MAC) entity. Operation 608 includes performing a third determination that a previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with an MBS-associated Radio Network Temporary Identifier (RNTI) of the MAC entity, the previous downlink assignment being received prior to the downlink assignment. Operation 610 includes determining, based on the third determination, that a new data indicator (NDI) value has been toggled.

[0121] 7 shows an example flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 702 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service. Operation 704 includes performing, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 706 includes performing a second determination that the downlink assignment is associated with an MBS-associated radio network temporary identifier (RNTI) of a medium access control (MAC) entity. Operation 708 includes making a third determination that the previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with another MBS-related RNTI of the MAC entity, or a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) of the MAC entity, or a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity, or a third determination that it is a configured downlink allocation, where the previous downlink allocation was received prior to the downlink allocation. Operation 710 includes determining that a new data indicator (NDI) value has been toggled based on the third determination.

[0122] FIG. 8 illustrates an example flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 802 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process. Operation 804 includes implementing, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 806 includes implementing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI). Operation 808 includes implementing a third determination that a previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with an MBS service having a lower priority than that of a unicast service, the previous downlink assignment being received prior to the downlink assignment. Operation 810 includes determining, based on the third determination, that a new data indicator (NDI) value is toggled. Operation 810 includes determining, based on the third determination, that a new data indicator (NDI) value is toggled. In some embodiments, the priority of the MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). In some embodiments, the method further includes providing, in response to the third determination, HARQ information associated with the data in the downlink allocation to a HARQ entity.

[0123] FIG. 9 illustrates an example flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 902 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process. Operation 904 includes performing, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 906 includes performing a second determination that the downlink assignment is associated with a Cell Radio Network Temporary Identifier (C-RNTI). Operation 908 includes performing a third determination that a previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with an MBS service having a priority higher than or equal to that of a unicast service, the previous downlink assignment being received prior to the downlink assignment. Operation 910 includes determining that the downlink assignment should be ignored.

[0124] FIG. 10A shows an example flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 1002 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process. Operation 1004 includes performing, by the user equipment, a first determination that a downlink assignment has been received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 1006 includes performing a second determination that the downlink assignment is associated with an MBS-related Radio Network Temporary Identifier (RNTI) of a Medium Access Control (MAC) entity. Operation 1008 includes performing a third determination that a previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a lower priority than that of the MBS-related RNTI, the previous downlink assignment being received prior to the downlink assignment. Operation 1010 includes determining, based on the third determination, that a new data indicator (NDI) value is toggled. In some embodiments, the priority of the other MBS-related RNTI and the C-RNTI is indicated by a higher layer or by a medium access control-control element (MAC CE). In some embodiments, the method further includes providing, in response to the third determination, HARQ information associated with the data in the downlink allocation to a HARQ entity.

[0125] 10B shows an example flowchart for operating a HARQ entity and a HARQ process by a UE. Operation 1052 includes operating, by the user equipment, a hybrid automatic repeat request (HARQ) entity and a HARQ process shared by a multicast and broadcast service (MBS) and a unicast service. Operation 1054 includes performing, by the user equipment, a first determination that a downlink assignment is received on a control channel, the downlink assignment relating to an occasion on the control channel and a serving cell to which the user equipment is connected. Operation 1056 includes performing a second determination that the downlink assignment is associated with an MBS-associated radio network temporary identifier (RNTI) of a medium access control (MAC) entity. Operation 1058 includes performing a third determination that the previous downlink assignment indicated to the HARQ entity of the HARQ process is associated with a Cell Radio Network Temporary Identifier (C-RNTI) of the MAC entity or another MBS-related RNTI having a priority higher than or equal to that of the MBS-related RNTI, the previous downlink assignment being received prior to the downlink assignment. Operation 1060 includes determining that the downlink assignment should be ignored.

[0126] FIG. 11 shows an example block diagram of a hardware platform 1100 that may be part of a network node (e.g., user equipment or CU or DU or RAN node). The hardware platform 1100 includes at least one processor 1110 and a memory 1105 storing instructions. The instructions, when executed by the processor 1110, configure the hardware platform 1100 to perform the operations described in FIGS. 1-10B and various embodiments described in this patent document. The transmitter 1115 transmits or transmits information or data to another node. The receiver 1120 receives information or data transmitted or transmitted by another node.

[0127] The term "exemplary" is used herein to mean "an example of," and does not imply an ideal or preferred embodiment, unless otherwise stated.

[0128] Some of the embodiments described herein are described in the general context of a method or process that may be implemented by a computer program product embodied in a computer-readable medium, which in one embodiment includes computer-executable instructions, such as program code, 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), compact disks (CDs), digital versatile disks (DVDs), and the like. Thus, the computer-readable medium may include non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0129] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuits, software, or a combination thereof. For example, a hardware circuit implementation can include separate analog and / or digital components integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as application specific integrated circuits (ASICs) and / or as field programmable gate array (FPGA) devices. Some implementations can additionally or alternatively include digital signal processors (DSPs), which are specialized microprocessors with architectures optimized for the operational needs of digital signal processing associated with the disclosed functionality of the present application. Similarly, various components or subcomponents within each module can be implemented in software, hardware, or firmware. Connectivity between modules and / or components within a module can be provided using any one of the connectivity methods and mediums known in the art, including, but not limited to, communication via the Internet, wired, or wireless networks using appropriate protocols.

[0130] Although this document contains many details, these should not be construed as limitations on the scope of the claimed invention or the subject matter that may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Also, although features may be described above as working in a combination and even initially claimed as such, one or more features from the claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination. Similarly, although operations are depicted in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or in a sequential order, or that all of the illustrated operations be performed, to achieve desired results.

[0131] Only some implementations and examples have been described; other implementations, enhancements, and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. 1. A method of wireless communication, the method comprising: A base station receives priority information indicating a priority of a multicast and broadcast service (MBS) from a core network; The base station determines a reception priority of the MBS based on the priority indicated by the priority information; A method comprising:

2. The method of claim 1 , wherein the priority information includes a priority of an identifier associated with the MBS.

3. 3. The method of claim 2, wherein the identifier comprises an MBS service identifier, an MBS session identifier, a Temporary Mobile Group Identifier (TMGI), a part of a Quality of Service (QoS) flow in an MBS session, a Multicast Radio Bearer (MRB) identifier, or a unique identification of an interface over which an MBS service or an MBS session is established between the base station and the core network.

4. 2. The method of claim 1, wherein the priority information includes information indicating whether one or more user equipments connected to the base station prioritize reception of multiple Multimedia Broadcast Multicast Services (MBMS) over reception of any one unicast service.

5. The method of claim 1 , wherein the priority information comprises a list of MBS services that one or more user equipments are receiving or are interested in receiving.

6. The method of claim 5 , wherein the list of MBS services includes one or more identifiers arranged in an order indicating a priority of the one or more identifiers.

7. The method of claim 1, wherein the priority information is associated with an identifier of a user equipment, or the priority information is associated with a plurality of user equipments receiving the MBS or a plurality of user equipments interested in receiving the MBS.

8. The method of claim 1 , wherein the priority information is received via a Next Generation Application Protocol (NGAP) message using MBS session association signaling.

9. The method of claim 1 , wherein the priority information is received via a Next Generation Application Protocol (NGAP) message using user equipment association signaling.

10. The method of claim 1 , wherein the priority information is received via an F1 Application Protocol (F1AP) message using MBS session association signaling.

11. The method of claim 1 , wherein the priority information is received via an F1 Application Protocol (F1AP) message using user equipment association signaling.

12. The method of claim 1, wherein the priority information is received via a Radio Resource Control (RRC) message or a user equipment dedicated Medium Access Control - Control Element (MAC CE).

13. The method of claim 1 , wherein the priority information is received via a radio resource control (RRC) message over a broadcast channel.

14. The method of claim 1 , wherein the priority information is received via system information or a medium access control-control element (MAC CE) broadcast in a cell.

15. The method of claim 1, wherein the base station includes a distributed unit and the core network includes a central unit.

Images