Techniques for managing multicast and broadcast services

Abstract

Techniques for a radio access network (RAN) system to acquire 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 from a second network node, priority information indicating a priority of a multicast and broadcast service (MBS), and determining, by the first network, a reception priority of the MBS based on the priority indicated by the priority information.

Description

Technical Field

[0001] This disclosure is generally used for digital wireless communications. Background Technology

[0002] Mobile communication technologies are propelling the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide more complex and granular access requirements and flexibility.

[0003] Long-Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE-Advanced (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system, 5G, advances the LTE and LTE-A wireless standards and aims to support higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging service requirements. Summary of the Invention

[0004] A cell can transmit multicast and broadcast services (MBS). MBS may include techniques for transmitting data from a mobile network data source node to multiple target nodes, enabling the sharing and efficient use of network resources, particularly air interface resources. Different MBS services may have different priorities received by the UE. To enable the base station to make appropriate scheduling decisions, the priorities of MBS services can be known to the base station. This patent application describes techniques for solving the technical problem of how a radio access network (RAN) system acquires and processes information about the priorities of MBS services.

[0005] A first example of the wireless method includes a first network node receiving priority information from a second network node indicating the priority of a multicast and broadcast service (MBS); and the first network determining a reception priority for the MBS based on the priority indicated by the priority information. In some embodiments, the priority information includes the 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 subset of quality of service (QoS) flows in an MBS session, a multicast radio bearer (MRB) identifier, a multicast radio bearer (MBS) identifier, or a unique identifier of the interface through which the first and second network nodes establish the MBS service or MBS session.

[0006] In some embodiments, priority information includes an indication of whether one or more user equipments connected to the first network node prioritize the reception of multiple Multimedia Broadcast Multicast Services (MBMS) over the reception of any single unicast service. In some embodiments, 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 order of priority indicating one or more identifiers. In some embodiments, priority information is associated with identifiers of user equipments, or priority information is associated with multiple user equipments that are receiving or are interested in receiving MBS services.

[0007] In some embodiments, priority information is received via Next Generation Application Protocol (NGAP) messages using signaling associated with the MBS session. In some embodiments, priority information is received via NGAP messages using signaling associated with the User Equipment (UE). In some embodiments, priority information is received via F1 Application Protocol (F1AP) messages using signaling associated with the MBS session. In some embodiments, priority information is received via F1AP messages using signaling associated with the UE. In some embodiments, priority information is received via Radio Resource Control (RRC) messages or via a Medium Access Control-Control Element (MAC CE) dedicated to the UE.

[0008] In some embodiments, priority information is received via a broadcast channel through a Radio Resource Control (RRC) message. In some embodiments, priority information is received via system information or a Media Access Control-Control Element (MAC CE) broadcast in the 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 centralized 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] The second example wireless communication method includes a user equipment determining that the number of multiple transmissions scheduled for the user equipment on a shared channel exceeds the user equipment's capacity; and performing reception of one or more of the multiple transmissions based on the priority of multicast and broadcast services (MBS), wherein the priority of MBS is indicated by an upper layer or by a media access control element (MAC CE).

[0010] A third example method for wireless communication includes a Media Access Control (MAC) entity of a user equipment determining that a received downlink allocation for a Network Radio Temporary Identifier (RNTI) associated with the MBS and that associated Hybrid Automatic Repeat Request (HARQ) information is indicated to a HARQ entity, wherein the HARQ entity is an MBS HARQ entity for MBS service and manages MBS processes, and wherein, for downlink allocation, the MBS HARQ entity points 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 allocation associated with the MBS-related RNTI from an upper layer.

[0011] A fourth example method for wireless communication includes a Media Access Control (MAC) entity of a user equipment determining that received downlink allocation for MBS-related Radio Network Temporary Identifiers (RNTIs) and associated Hybrid Automatic Repeat Request (HARQ) information are indicated to a HARQ entity, wherein the HARQ entity is an MBS HARQ entity for MBS services and manages MBS processes, and wherein, for downlink allocation, the MBS HARQ entity assigns one or more received transport blocks and associated HARQ information to unoccupied MBS processes; and associates the MBS processes with the MBS-related RNTI for downlink allocation. In some embodiments, the method further includes determining, upon receiving a new transport block, that the MBS HARQ entity does not include unoccupied MBS processes; and, in response to the determination, treating an occupied MBS process corresponding to the MBS service with the lowest priority as an unoccupied MBS process. In some embodiments, occupied MBS processes are selected or randomly selected from a plurality of MBS processes with the lowest priority.

[0012] A fifth example method for wireless communication includes a Media Access Control (MAC) entity of a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and multiple Multicast and Broadcast Service (MBS) processes, wherein the HARQ entity is an MBS HARQ entity for MBS services, and wherein the MBS processes correspond to the MBS HARQ entities; for each duration on a shared channel in which the MBS processes transmit, receiving a transport block (TB) and associated HARQ information from the MBS HARQ entity; and upon determining that HARQ feedback is enabled via downlink control information (DCI): instructing the physical layer to generate acknowledgments for data in the transport block in response to HARQ feedback being configured for individual HARQ resources, or instructing the physical layer to generate acknowledgments for data in the transport block in response to HARQ feedback being configured for shared HARQ resources.

[0013] A sixth example method for wireless communication includes a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process shared by multicast and broadcast services (MBS) and unicast services; the user equipment performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is for timing on the control channel and for the serving cell to which the user equipment is connected; performing a second determination that the downlink allocation is associated with a cell radio network temporary identifier (C-RNTI) of a media access control (MAC) entity; performing a third determination that a previous downlink allocation indicated to the HARQ process by the HARQ entity is associated with a radio network temporary identifier (RNTI) associated with an MBS of the MAC entity, wherein 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 switched.

[0014] A seventh example method for wireless communication includes a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process shared by multicast and broadcast services (MBS) and unicast services; the user equipment performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the user equipment is connected; performing a second determination that the downlink allocation is associated with a Radio Network Temporary Identifier (RNTI) associated with an MBS of a Media Access Control (MAC) entity; performing a third determination that a previous downlink allocation indicated to the HARQ process by the HARQ entity is associated with an RNTI associated with another MBS 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 configured downlink allocation, wherein 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 switched.

[0015] An eighth example method for wireless communication includes a user equipment (UE) operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process; the UE performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the UE is connected; performing a second determination that the downlink allocation is associated with a Cell Radio Network Temporary Identifier (C-RNTI); performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service with a lower priority than the unicast service, wherein 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 switched. In some embodiments, the priority of the MBS-related RNTI and the priority of the C-RNTI are indicated by an upper layer or by a Media Access Control-Control Element (MAC CE). In some embodiments, the method further includes providing HARQ information associated with data in the downlink allocation to the HARQ entity in response to the third determination.

[0016] A ninth example method for wireless communication includes a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process; the user equipment performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the user equipment is connected; performing a second determination that the downlink allocation is associated with a Cell Radio Network Temporary Identifier (C-RNTI); performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service with a priority greater than or equal to that of a unicast service, wherein the previous downlink allocation was received prior to the downlink allocation; and determining that the downlink allocation will be ignored.

[0017] A tenth example method for wireless communication includes a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process; the user equipment performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the user equipment is connected; performing a second determination that the downlink allocation is associated with a Network Radio Temporary Identifier (RNTI) associated with the MBS of a Media Access Control (MAC) entity; performing a third determination that a previous downlink allocation indicated to the HARQ entity for the HARQ process is associated with another MBS-related RNTI of a MAC entity whose priority is lower than that of the cell-related RNTI, wherein 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 switched. In some embodiments, the priorities of the other MBS-related RNTI and C-RNTI are indicated by an upper layer or by a Media Access Control-Control Element (MAC CE). In some embodiments, the method further includes providing HARQ information associated with data in the downlink allocation to the HARQ entity and in response to the third determination.

[0018] An eleventh example method for wireless communication includes a user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and a HARQ process shared by multicast and broadcast services (MBS) and unicast services; the user equipment performing a first determination that a downlink allocation is received on a control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the user equipment is connected; performing a second determination that the downlink allocation is associated with a Radio Network Temporary Identifier (RNTI) associated with an MBS of a Media Access Control (MAC) entity; performing a third determination that a previous downlink allocation indicated to the HARQ process by the HARQ entity is associated with another MBS-related RNTI of a MAC entity with a Cell Radio Network Temporary Identifier (C-RNTI) or a priority greater than or equal to the priority of the MBS-related RNTI, wherein the previous downlink allocation was received prior to the downlink allocation; and determining that the downlink allocation will be ignored.

[0019] In another exemplary aspect, the above-described method is embodied in processor-executable code and stored in a non-transitory computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the method described in this patent document.

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

[0021] The foregoing and other aspects, and their embodiments, will be described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0022] Figure 1 An example flowchart is shown for managing priority information that indicates the priority of multicast and broadcast services (MBS).

[0023] Figure 2 An example flowchart is shown for managing the priority of Radio Network Temporary Identifiers (RNTIs) or MBS associated with Multicast and Broadcast Services (MBS) when the number of transmissions exceeds the UE's capacity.

[0024] Figure 3 An example flowchart of the MAC entity used to operate the UE is shown.

[0025] Figure 4 An example flowchart of the MAC entity used to operate the UE is shown.

[0026] Figure 5 An example flowchart of the MAC entity used to operate the UE is shown.

[0027] Figures 6 to 10B An example flowchart is shown for the operation of HARQ entities and HARQ processes by the UE.

[0028] Figure 11 An exemplary block diagram of a hardware platform that can be part of a network node is shown.

[0029] Figure 12 An example block diagram illustrating the relationship between a Media Access Control (MAC) entity and one or more Hybrid Automatic Repeat Request (HARQ) entities is shown. Detailed Implementation

[0030] This patent application describes, among other things, techniques that enable a Radio Access Network (RAN) system to acquire and process information about MBS service priority. In this patent document, the term Group of Radio Network Temporary Identifiers (G-RNTI) can include Radio Network Temporary Identifiers (RNTIs) for multicast and broadcast services / sessions (also referred to as MBS-related RNTIs). The term G-RNTI may be referred to by another name for the MBS service or session. The example headings of the following subsections are used to facilitate understanding of the disclosed subject matter and do not in any way limit the scope of the claimed subject matter. Thus, one or more features of one example subsection may be combined with one or more features of another example subsection. Furthermore, for clarity, the term 5G is used; however, the techniques disclosed in this document are not limited to 5G technology and can be used in wireless systems implementing other protocols.

[0031] Example 1. (MBS priority information can be sent from CN to RAN via signaling associated with the MBS session.)

[0032] MBS priority information can be included in messages sent from the core network (e.g., the 5G Core Access and Mobility Management Function (AMF)) to the base station (e.g., the RAN node). This procedure can utilize signaling associated with the MBS session. The message can 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 for one or more MBS services and corresponding Quality of Service (QoS) flows via the Radio Interface (Uu) and / or the Next Generation User Plane Interface (NG-U), and to set up the corresponding Multicast Radio Bearer (MRB). The MBS SESSION RESOURCE MODIFY REQUEST message is used to enable configuration modifications for established MBS sessions. The MBS SESSION RESOURCE MODIFY REQUEST message is also used to enable the setting, modification, and release of QoS flows for established MBS sessions.

[0033] MBS priority information can be associated with each UE ID or all UEs that are receiving or interested in receiving MBS sessions. The UE ID can be the AMF UE NGAP ID or the RAN UE NGAP ID.

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

[0035] In one example, MBS priority information may be included for each MBS ID. The MBS ID can be an MBS service ID, an MBS session ID, a temporary mobile group identifier (TMGI), a subset of QoS flows in an MBS session, an AMF MBS NGAP ID uniquely identifying the MBS service / session associated on an NG interface, or a RAN MBS NGAP ID uniquely identifying the MBS service / session associated on an NG interface within a RAN node. The MBS priority information may include the priority of the MBS ID. For example, the MBS priority information can be an integer from 1 to a constant value (e.g., 256).

[0036] In another example, MBS priority information is implicitly indicated in a message sent from the core network to the base station. This message contains a list of MBS services that one or more UEs are receiving or are interested in receiving, and the MBS priority information for each MBS ID is implicitly indicated by the order in which the MBS IDs are listed.

[0037] In another example, MBS priority information may include an indication of whether one or more associated UEs prioritize receiving all MBMS services over receiving any unicast services.

[0038] If MBS priority information is included in a message sent from the core network to the base station, the base station can use it to determine the priority of MBS services for scheduling one or more associated UEs, or the base station can consider the priority of UEs for receiving MBS services and unicast services.

[0039] Example 2. (MBS priority information can be sent from CN to RAN via UE-associated signaling)

[0040] MBS priority information can be included in a message sent from the core network (e.g., AMF) to the base station (e.g., RAN node). This procedure can utilize UE-associated signaling. The message can be a PDU SESSION RESOURCE SETUPREQUEST message or a PDU SESSION RESOURCE MODIFY REQUEST message.

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

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

[0043] In another example, MBS priority information is implicitly indicated in a message sent from the core network to the base station. This message contains 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 order in which the MBS IDs are listed.

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

[0045] If MBS priority information is included in a message sent from the core network to the base station, the base station can use it to determine the priority of the MBS ID for scheduling one or more associated UEs, or the base station can consider the priority of UEs for receiving MBS services and unicast services.

[0046] Example 3. (MBS priority information can be sent from gNB-CU to gNB-CU via the F1AP signaling associated with the MBS.) DU)

[0047] Example 3 describes how priority information for each MBS ID is transmitted from the gNB-CU to the gNB-DU. MBS priority information can be included in a message sent from a centralized unit (e.g., gNB-CU) to a distributed unit (e.g., gNB-DU). This procedure can utilize signaling associated with the MBS session. The message can be an MBS CONTEXT SETUP REQUEST message or an MBS CONTEXT MODIFY REQUEST message. The MBS CONTEXT SETUP REQUEST message is used to establish the MBS context, including MRB configuration. The MBS CONTEXT MODIFY REQUEST message is used to modify the established MBS context, such as establishing, modifying, and releasing radio resources.

[0048] MBS priority information can be associated with each UE ID or all UEs that are receiving or interested in receiving MBS sessions.

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

[0050] In one example, MBS priority information can be included for each MBS ID. The MBS ID can be an MRB ID, MBS service ID, MBS session ID, TMGI, gNB-CU MBS F1AP ID, or gNB-DU MBS F1AP ID. The gNB-CU MBS F1AP ID identifies the MBS session / service association on the F1 interface within the gNB-CU. The gNB-DU MBS F1AP ID identifies the MBS session / service association on the F1 interface within the gNB-DU. The MBS priority information can contain the priority of the MBS IDs of one or more associated UEs. For example, the MBS priority information can be an integer from 1 to a constant value (e.g., 256).

[0051] In another example, MBS priority information is implicitly indicated in a message sent from the CU to the DU. This message contains a list of one or more 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 order in which the MBS IDs are listed.

[0052] In another example, MBS priority information may include an indication of whether one or more associated UEs prioritize receiving all MBMS services over receiving any unicast services.

[0053] If MBS priority information is included in a message sent from a centralized unit to a distributed unit, the distributed unit can use it to determine the priority of the MBS ID for scheduling one or more associated UEs, or the base station can consider the priority of UEs for receiving MBS services and unicast services.

[0054] Example 4. (MBS priority information can be sent from gNB-CU to gNB-DU via F1AP signaling associated with the UE.)

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

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

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

[0058] In another example, MBS priority information is implicitly indicated in a message sent from the core network to the base station. This message contains 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 order in which the MBS IDs are listed.

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

[0060] If MBS priority information is included in a message sent from a centralized unit to a distributed unit, the distributed unit can use it to determine the priority of the MBS ID used for scheduling the UE, or the base station can consider the priority of the UE used to receive MBS services and unicast services.

[0061] Example 5. (MBS priority information can be exchanged between the UE and RAN via RRC / System Information / MAC) CE was sent)

[0062] Example 5 illustrates how priority information for each MBS ID is transmitted between the UE and the RAN. MBS priority information can be sent from the UE to the base station, or vice versa.

[0063] The program can be started under at least one of the following conditions: when the interest changes, when the bearer mode changes, when the priority of the MBS service changes, and when the priority between MBS reception and unicast reception changes.

[0064] MBS priority information can be included in RRC messages, system messages, or MAC CE.

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

[0066] In one example, MBS priority information can be included for each MBS ID. The MBS ID can be an MBS service ID, MBS session ID, TMGI, G-RNTI, or a subset of QoS flows in an MBS session that the UE is interested in or is receiving. The MBS priority information can contain the priority of the MBS ID. The MBS priority information can be an integer from 1 to a constant value (e.g., 256). The MBS priority information is associated with the MBS service ID. The MBS ID can also be an MBS service ID, MBS session ID, TMGI, or a subset of QoS flows in an MBS session.

[0067] In another example, MBS priority information is implicitly indicated in a message sent from the UE to the base station. This message contains 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 order in which the MBS IDs are arranged in the list.

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

[0069] In another example, MBS priority information may include indications of priority thresholds for unicast services and / or priority thresholds for multicast services.

[0070] In another example, for a scenario where the UE sends MBS priority information to the RAN, the UE can set the MBS priority value for each MBS ID based on service priority information from the application layer.

[0071] In another example, for a scenario where the RAN sends MBS priority to the UE, the base station can set the value of the MBS priority information for each MBS ID based on at least one of the following: priority information of the QoS flow (e.g., ARP), and MBS priority information received from the core network.

[0072] In another example, for a scenario where the RAN sends MBS priority information to the UE, the distributed unit can set the value of the MBS priority information for each MBS ID based on at least one of the following: priority information of the QoS flow (e.g., ARP), MBS priority information received from the centralized unit, and priority information of the DRB / MRB.

[0073] If the MBS priority information is received by the base station, the base station can use it to determine the priority for scheduling MBS IDs for the UE, or the base station can consider the priority of the UE for receiving MBS services and unicast services.

[0074] Figure 1 An example flowchart is shown for managing priority information indicating the priority of a Multicast and Broadcast Service (MBS). Operation 102 includes a first network node receiving priority information indicating the priority of the MBS from a second network node. Operation 104 includes the first network determining a reception priority for the MBS based on the priority indicated by the priority information. In some embodiments, the priority information includes the 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 subset of Quality of Service (QoS) flows in an MBS session, a Multicast Radio Bearer (MRB) identifier, or a unique identifier of the interface through which the first and second network nodes establish the MBS service or MBS session.

[0075] In some embodiments, priority information includes an indication of whether one or more user equipments connected to the first network node prioritize the reception of multiple Multimedia Broadcast Multicast Services (MBMS) over the reception of any single unicast service. In some embodiments, 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 order of priority indicating one or more identifiers. In some embodiments, priority information is associated with identifiers of user equipments, or priority information is associated with multiple user equipments that are receiving or are interested in receiving MBS services.

[0076] In some embodiments, priority information is received via Next Generation Application Protocol (NGAP) messages using signaling associated with the MBS session. In some embodiments, priority information is received via Next Generation Application Protocol (NGAP) messages using signaling associated with the user equipment. In some embodiments, priority information is received via F1 Application Protocol (F1AP) messages using signaling associated with the MBS session. In some embodiments, priority information is received via F1 Application Protocol (F1AP) messages using signaling associated with the user equipment. In some embodiments, priority information is received via Radio Resource Control (RRC) messages or a Media Access Control-Control Element (MAC CE) dedicated to the user equipment.

[0077] In some embodiments, priority information is received via a broadcast channel through Radio Resource Control (RRC) messages. In some embodiments, priority information is received via system information or a Media Access Control-Control Element (MAC CE) broadcast in the 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 centralized 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.

[0078] Example 6. (UE behavior can be influenced by priority information in the following ways.)

[0079] Example 6 illustrates a possible way in which priority information affects MAC behavior. If a UE is scheduled to receive more PDSCH transmissions than it can handle, the MAC entity prioritizes these PDSCH transmissions based on the priority of each G-RNTI / MBS service, where the priority is indicated / configured by the upper layer or by the MAC CE.

[0080] The number of G-RNTI / MBS services available for parallel reception is limited by the UE's processing capacity.

[0081] G-RNTI / MBS services with higher priority are received first.

[0082] In another example, the priority of PDSCH transmissions or downlink allocations for multicast / broadcast / unicast services is included in the DCI. The UE's MAC entity prioritizes these PDSCH transmissions based on the priority information indicated on the DCI.

[0083] In another example, information regarding priority thresholds for unicast services and / or multicast services can be configured by the base station to the UE via RRC messages or MAC CE. The UE prioritizes transmissions of MBS or unicast services whose priority indicated on the DCI is higher than the thresholds configured by the upper layer or MAC CE.

[0084] Figure 2 An example flowchart is shown for managing the priority of MBS-related Radio Network Temporary Identifier (RNTI) or Multicast and Broadcast Service (MBS) when the number of transmissions exceeds the UE's capacity. Operation 202 includes the UE determining that the number of multiple transmissions scheduled for the UE on the shared channel exceeds the UE's capacity. Operation 204 includes performing reception of one or more of the multiple transmissions based on the priority of the Multicast and Broadcast Service (MBS), wherein the MBS priority is indicated by an upper layer or by a Media Access Control Element (MAC CE).

[0085] Example 7. (The behavior of the UE and RAN can be affected by priority information in the following ways.)

[0086] Examples of RAN behavior are as follows:

[0087] Example 7-1: The RAN can make scheduling decisions based on MBS priority information. For example, when HARQ processes are shared between unicast and multicast services, the RAN can determine downlink allocation based on MBS priority information.

[0088] Examples of UE behavior are as follows:

[0089] Based on the downlink allocation received on the PDCCH, the UE's MAC entity performs the following actions.

[0090] Example 7-1 describes an example of UE behavior when the HARQ process is not shared between unicast and multicast services. Details of Example 7-1 are as follows.

[0091] Example 7-1. In one example, at most one MBS HARQ entity is located at the MAC entity for multicast / broadcast reception per serving cell, maintaining multiple parallel MBS processes. In another example, the MBS HARQ entity is a HARQ entity that maintains multiple parallel HARQ processes for unicast services and multiple parallel MBS processes for multicast services. Each MBS process is associated with a downlink-assigned G-RNTI or MBS service. This interest is indicated by the upper layer. The MBS HARQ entity directs the MBS transmission information and associated TB 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.

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

[0093] When a MAC entity has a C-RNTI, temporary C-RNTI, CS-RNTI, or G-RNTI, the MAC entity can perform the following operations for each PDCCH it is listening to and for each serving cell:

[0094] 1> If a downlink allocation for this PDCCH timing has already been received on the PDCCH used for G-RNTI:

[0095] 2> indicates the existence of downlink allocation and delivers the associated HARQ information and G-RNTI to the MBS HARQ entity.

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

[0097] MBS HARQ entities can perform the following operations:

[0098] 1> For each downlink allocation indicated to the MBS HARQ entity:

[0099] 2> If NDI has switched compared to the value of a previously received transmission corresponding to that TB, or if this is the first received transmission for that TB:

[0100] 3> The one or more TBs and associated HARQ information received from the physical layer will be assigned to an unoccupied MBS process, the MBS process will be associated with the G-RNTI or the corresponding MBS service, and the transmission will be treated as a new transmission.

[0101] Note 1: When a new TB arrives, if there are no unoccupied MBS processes in the MBS HARQ entity, how to manage the receiving MBS process depends on the UE implementation method.

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

[0103] 1> For each MBS process:

[0104] 2> If, according to the SCI associated with NDI, the NDI has not yet switched compared to the value of the previously received transmissions for that TB corresponding to the MBS process:

[0105] 3> The TB received from the physical layer will be dispatched to the MBS process, and this transmission will be regarded as a retransmission.

[0106] 2> Otherwise, if the HARQ buffer of the MBS process is not empty:

[0107] 3> then refresh the HARQ buffer.

[0108] Examples of MBS process behavior include at least one of the following operations:

[0109] For each PDSCH duration during which the MBS process transmits data, a TB and associated HARQ information are received from the MBS HARQ entity.

[0110] For each received TB and associated MBS transmission information, the MBS process can perform the following operations:

[0111] 1> If this is a new transmission:

[0112] 2> Then attempt to decode the received data.

[0113] 1> Otherwise, if this is a retransmission:

[0114] 2> If the TB of data has not yet been successfully decoded:

[0115] 3> then instructs the physical layer to merge the received data with the data currently in the soft buffer of that TB, and attempt to decode the merged data.

[0116] 1> If the data that the MAC entity attempted to decode for that TB was successfully decoded; or

[0117] 1> If this TB of data is successfully decoded before the following operations:

[0118] 2> Deliver the decoded MAC PDU to the disassembler and demultiplexer entity;

[0119] 2> It is assumed that the MBS process is not occupied.

[0120] 1> Otherwise:

[0121] 2> Instruct the physical layer to replace the data in the soft buffer of the TB with the data that the MAC entity attempts to decode.

[0122] 1> If HARQ feedback is enabled by DCI or the upper layer:

[0123] 2> If the HARQ feedback corresponding to this TB is configured with [a separate resource]; or

[0124] 2> If the HARQ feedback corresponding to this TB is configured with [shared resources]:

[0125] 3> This instructs the physical layer to generate one or more acknowledgments for the data in that TB.

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

[0127] Example 7-2 illustrates an example of UE behavior when a HARQ process is shared between unicast and multicast services. The HARQ entity manages multiple HARQ processes for both unicast and multicast services. Details of Example 7-2 are as follows.

[0128] In one example, the UE receives the latest instruction (e.g., DCI) and acts accordingly. The behavior of the UE's MAC entity includes at least one of the following operations.

[0129] When a MAC entity has a C-RNTI, a temporary C-RNTI, a CS-RNTI, or a G-RNTI, the MAC entity can perform the following operations for each PDCCH it listens to and for each serving cell:

[0130] 1> If the PDCCH timing and downlink allocation for the serving cell have already been received on the PDCCH for a C-RNTI or temporary C RNTI used for a MAC entity:

[0131] 2> If this is the first downlink allocation for this temporary C-RNTI:

[0132] If 3>, then it is assumed that NDI has been switched.

[0133] 2> If the downlink allocation is a C-RNTI for a MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a G-RNTI for a MAC entity, then the received downlink allocation is:

[0134] 3> Regardless of the value of NDI, it is assumed that NDI has been switched.

[0135] 2> indicates the existence of downlink allocation and delivers the associated HARQ information to the HARQ entity.

[0136] 1> If the PDCCH timing and downlink allocation for the serving cell have already been received on the PDCCH of the MAC entity's G-RNTI:

[0137] 2> If the downlink allocation is a G-RNTI for a MAC entity, and the downlink allocation received is a CS-RNTI, C-RNTI, or another G-RNTI for a MAC entity, or is a configured downlink allocation:

[0138] 3> Regardless of the value of NDI, it is assumed that NDI has been switched.

[0139] 2> indicates the existence of downlink allocation and delivers the associated HARQ information to the HARQ entity.

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

[0141] When a MAC entity has a C-RNTI, a temporary C-RNTI, a CS-RNTI, or a G-RNTI, the MAC entity can perform the following operations for each PDCCH it listens to and for each serving cell:

[0142] 1> If the PDCCH timing and downlink allocation for the serving cell have already been received on the PDCCH of the MAC entity's C-RNTI or G-RNTI:

[0143] 2> If the downlink allocation is a C-RNTI for a MAC entity, and if the previous downlink allocation indicated to a HARQ entity in the same HARQ process was a G-RNTI for a MAC entity with a lower priority than the C-RNTI, and the priority is indicated / configured by the upper layer or by the MAC CE:

[0144] 3> Regardless of the value of NDI, it is assumed that NDI has been switched.

[0145] 3> indicates the existence of downlink allocation for the serving cell and delivers the associated HARQ information to the HARQ entity.

[0146] 2> If the downlink allocation is for a MAC entity's C-RNTI, and if the previous downlink allocation indicated to a HARQ entity in the same HARQ process was a downlink allocation received for a MAC entity with a priority higher than or equal to the C-RNTI, where the priority is indicated / configured by the upper layer or by the MAC CE:

[0147] 3> Then the downlink allocation is ignored.

[0148] 2> If the downlink allocation is a G-RNTI for a MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a C-RNTI for a MAC entity or a downlink allocation received with a lower priority than that G-RNTI, where the priority is indicated / configured by the upper layer or by the MAC CE:

[0149] 3> Regardless of the value of NDI, it is assumed that NDI has been switched.

[0150] 3> indicates the existence of downlink allocation for the serving cell and delivers the associated HARQ information to the HARQ entity.

[0151] 2> If the downlink allocation is for a G-RNTI of a MAC entity, and if the previous downlink allocation indicated to a HARQ entity in the same HARQ process was for a C-RNTI of a MAC entity or another G-RNTI with a priority higher than or equal to that G-RNTI, where the priority is indicated / configured by the upper layer or by the MAC CE:

[0152] 3> Then the downlink allocation is ignored.

[0153] In another example, the UE's behavior is influenced by priority information and received instructions (e.g., DCI). A reserved HPN (HARQ process number) can be used for relevant downlink allocation in G-RNTI. The UE's MAC entity behavior includes at least one of the following operations.

[0154] When a MAC entity has a C-RNTI, a temporary C-RNTI, a CS-RNTI, or a G-RNTI, the MAC entity can perform the following operations for each PDCCH it listens to and for each serving cell:

[0155] 1> If the PDCCH timing and downlink allocation for the serving cell have already been received on the PDCCH of the MAC entity's C-RNTI or G-RNTI:

[0156] 2> If the downlink allocation is a C-RNTI for a MAC entity, and if the previous downlink allocation indicated to a HARQ entity in the same HARQ process was a G-RNTI for a MAC entity with a lower priority than the C-RNTI, and the priority is indicated / configured by the upper layer or by the MAC CE:

[0157] 3> Regardless of the value of NDI, it is assumed that NDI has been switched.

[0158] 3> indicates the existence of downlink allocation for the serving cell and delivers the associated HARQ information to the HARQ entity.

[0159] 2> If the downlink allocation is for a MAC entity's C-RNTI, and the downlink allocation is received if the previous downlink allocation to a HARQ entity in the same HARQ process was for a MAC entity with a G-RNTI that has a priority higher than or equal to the C-RNTI, where the priority is indicated / configured by the upper layer or by the MAC CE:

[0160] 3> Then the downlink allocation is ignored.

[0161] 2> If the downlink allocation is a G-RNTI for a MAC entity,

[0162] 3> indicates the existence of downlink allocation for the serving cell and delivers the associated HARQ information to the HARQ entity.

[0163] HARQ entities are able to perform the following operations:

[0164] 1> For each downlink assignment associated with G-RNTI and indicated to the HARQ entity:

[0165] 2> If NDI has been switched compared to the value of a previously received transmission corresponding to this TB, or if this is the first received transmission for this TB:

[0166] 3> Then, one or more TBs and associated HARQ information received from the physical layer are assigned to an unoccupied HARQ process, the HARQ process is associated with the G-RNTI, and the transmission is treated as a new transmission.

[0167] 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 will be assigned to an unoccupied MBS process. If there are several HARQ processes with the lowest priority, any one of these HARQ processes can be assigned to the TB.

[0168] Figure 12An example block diagram illustrating the relationship between a MAC entity and one or more HARQ entities is shown. Figure 12 The left side shows the relationship between MAC entity 1202, HARQ entity and process, where the HARQ process and MBS process are not shared between unicast and MBS services. Figure 12 The right side shows the relationship between MAC entity 1204, HARQ entity, and HARQ process, where the HARQ process is shared by unicast and MBS services.

[0169] Figure 3 An example flowchart for a MAC entity used to operate a UE is shown. Operation 302 includes the UE's Media Access Control (MAC) entity determining that a received downlink allocation for an MBS-related Radio Network Temporary Identifier (RNTI) and the associated Hybrid Automatic Repeat Request (HARQ) information are indicated to a HARQ entity, wherein the HARQ entity is the MBS HARQ entity for MBS service and manages the MBS process, and wherein, for the 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 an upper layer to receive the downlink allocation associated with the MBS-related RNTI.

[0170] Figure 4 An example flowchart for the MAC entity used to operate the UE is shown. Operation 402 includes the UE's Media Access Control (MAC) entity determining that a received downlink allocation for an MBS-related Radio Network Temporary Identifier (RNTI) and associated Hybrid Automatic Repeat Request (HARQ) message are indicated to a HARQ entity, which is the MBS HARQ entity for MBS service and manages MBS processes. For downlink allocation, the MBS HARQ entity dispatches one or more received transport blocks and associated HARQ messages to an unoccupied MBS process. Operation 404 includes associating the MBS process with the MBS-related RNTI for downlink allocation.

[0171] In some embodiments, the method further includes performing a determination upon receiving a new transport block, namely, that the MBS HARQ entity does not include unoccupied MBS processes; and in response to performing the determination, treating an occupied MBS process corresponding to the MBS service with the lowest priority as an unoccupied MBS process. In some embodiments, the occupied MBS processes are selected or randomly selected from a plurality of MBS processes with the lowest priority.

[0172] Figure 5An example flowchart for a MAC entity used to operate a UE is shown. Operation 502 includes the user equipment's Media Access Control (MAC) entity operating a Hybrid Automatic Repeat Request (HARQ) entity and multiple Multicast and Broadcast Service (MBS) processes, wherein the HARQ entity is an MBS HARQ entity for MBS services, and wherein the MBS processes correspond to the MBS HARQ entities. Operation 504 includes receiving a transport block (TB) and associated HARQ information from the MBS HARQ entity for each duration on the shared channel for which transmissions occur for the MBS processes. Operation 506 includes, upon determining that HARQ feedback is enabled by Downlink Control Information (DCI): instructing the physical layer to generate an acknowledgment 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 an acknowledgment for data in the transport block in response to the HARQ feedback being configured for shared HARQ resources.

[0173] Figure 6 An example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 602 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process shared by multicast and broadcast services (MBS) and unicast services. Operation 604 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-specific on the control channel and for the serving cell to which the user equipment is connected. Operation 606 includes performing a second determination that the downlink allocation is associated with the Cell Radio Network Temporary Identifier (C-RNTI) of the Media Access Control (MAC) entity. Operation 608 includes performing a third determination that a previous downlink allocation of the HARQ entity indicated to the HARQ process is associated with the MBS-related Radio Network Temporary Identifier (RNTI) of the MAC entity, wherein the previous downlink allocation was received prior to the downlink allocation. Operation 610 includes determining, based on the third determination, that a new Data Indicator (NDI) value is switched.

[0174] Figure 7An example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 702 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process shared by multicast and broadcast services (MBS) and unicast services. Operation 704 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-dependent on the control channel and for the serving cell to which the user equipment is connected. Operation 706 includes performing a second determination that the downlink allocation is associated with the Radio Network Temporary Identifier (RNTI) associated with the MBS of the Media Access Control (MAC) entity. Operation 708 includes performing a third determination that a previous downlink allocation of the HARQ entity indicated to the HARQ process is associated with an RNTI associated with another MBS of the MAC entity, or a configured Scheduled 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 configured downlink allocation, wherein the previous downlink allocation was received prior to said downlink allocation. Operation 710 includes determining, based on a third determination, that a new Data Indicator (NDI) value has been switched.

[0175] Figure 8 An example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 802 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process. Operation 804 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-specific on the control channel and for the serving cell to which the user equipment is connected; operation 806 includes performing a second determination that the downlink allocation is associated with a Cell Radio Network Temporary Identifier (C-RNTI); operation 808 includes performing a third determination that the previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service with a lower priority than the unicast service, wherein the previous downlink allocation was received prior to the downlink allocation. Operation 810 includes determining, based on the third determination, that a new Data Indicator (NDI) value is switched. Operation 810 includes determining, based on the third determination, that a new Data Indicator (NDI) value is switched. In some embodiments, the priorities of the MBS-related RNTI and C-RNTI are indicated by an upper layer or by a Media Access Control-Control Element (MAC CE). In some embodiments, the method further includes providing HARQ information associated with data in the downlink allocation to the HARQ entity and in response to a third determination.

[0176] Figure 9An example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 902 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process. Operation 904 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-specific on the control channel and for the serving cell to which the user equipment is connected. Operation 906 includes performing a second determination that the downlink allocation is associated with a Cell Radio Network Temporary Identifier (C-RNTI). Operation 908 includes performing a third determination that a previous downlink allocation indicated to the HARQ entity of the HARQ process is associated with an MBS service with a priority greater than or equal to that of the unicast service, wherein the previous downlink allocation was received prior to said downlink allocation. Operation 910 includes determining that the downlink allocation will be ignored.

[0177] Figure 10A An example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 1002 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process. Operation 1004 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-specific on the control channel and for the serving cell to which the user equipment is connected. Operation 1006 includes performing a second determination that the downlink allocation is associated with the MBS-related Radio Network Temporary Identifier (RNTI) of the Media Access Control (MAC) entity. Operation 1008 includes performing a third determination that a previous downlink allocation indicated to the HARQ entity for the HARQ process is associated with another MBS-related RNTI of the MAC entity with a priority lower than that of the MBS-related RNTI, wherein the previous downlink allocation was received prior to said downlink allocation. Operation 1010 includes determining, based on the third determination, that a new Data Indicator (NDI) value is switched. In some embodiments, the priority of another MBS-related RNTI and C-RNTI is indicated by an upper layer or by a Media Access Control-Control Element (MAC CE). In some embodiments, the method further includes providing HARQ information associated with data in the downlink allocation to the HARQ entity and in response to a third determination.

[0178] Figure 10BAn example flowchart for UE operation of a HARQ entity and HARQ process is shown. Operation 1052 includes the user equipment operating a Hybrid Automatic Repeat Request (HARQ) entity and HARQ process shared by multicast and broadcast services (MBS) and unicast services. Operation 1054 includes the user equipment performing a first determination that a downlink allocation is received on the control channel, wherein the downlink allocation is timing-specific on the control channel and for the serving cell to which the user equipment is connected. Operation 1056 includes performing a second determination that the downlink allocation is associated with the MBS-related Radio Network Temporary Identifier (RNTI) of the Media Access Control (MAC) entity. Operation 1058 includes performing a third determination that a previous downlink allocation of the HARQ entity indicated to the HARQ process is associated with another MBS-related RNTI of the MAC entity whose cell radio network temporary identifier (C-RNTI) or priority is greater than or equal to the priority of the MBS-related RNTI, wherein the previous downlink allocation was received prior to said downlink allocation. Operation 1060 includes determining that the downlink allocation will be ignored.

[0179] Figure 11 An exemplary block diagram of a hardware platform 1100, which may be part of a network node (e.g., a user equipment, CU, DU, or RAN node), is shown. The hardware platform 1100 includes at least one processor 1110 and a memory 1105 storing instructions. The instructions configure the hardware platform 1100 to execute when executed by the processor 1110. Figure 1-10B The operation of the transmitter 1115 and the operation of the various embodiments described in this patent document. The transmitter 1115 transmits or sends information or data to another node. The receiver 1120 receives information or data transmitted or sent by another node.

[0180] In this document, the term “exemplary” is used to mean “an example of…” and, unless otherwise stated, does not imply an ideal or preferred embodiment.

[0181] 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, including computer-executable instructions, such as program code, that are executed by a computer in a networked environment. Computer-readable media 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 optical disc (DVD), etc. Therefore, computer-readable media may include non-transitory storage media. Generally, 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 behaviors for implementing the functions described in these steps or processes.

[0182] Some of the disclosed embodiments may use hardware circuitry, software, or a combination thereof to implement the device or module. For example, hardware circuitry implementations may include discrete analog and / or digital components, such as those integrated 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 additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor whose architecture is optimized for the operational requirements of digital signal processing related to the functions disclosed herein. Similarly, the 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 of the connection methods and media known in the art, including but not limited to communication via the Internet, wired, or wireless networks using appropriate protocols.

[0183] Although this document contains numerous details, these details should not be construed as limiting the scope of the claimed invention or the content that may be claimed, but rather as descriptions of specific features of particular embodiments. Certain features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as operating in a particular combination, and even initially claimed to be so, in certain circumstances one or more features from the claimed combination may be removed from the claimed combination, and the claimed combination may be for sub-combinations or variations thereof. 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 sequence shown, or requiring all illustrated operations to achieve the desired result.

[0184] This document describes only some implementation methods and examples. Other implementation methods, improvements and variations can be made based on the content described and illustrated in this disclosure.

Claims

1. A wireless communication method, comprising: The base station receives priority information from the core network indicating the priority of multicast and broadcast services MBS, wherein the priority information includes at least one of the following: an indication of whether one or more user equipments connected to the base station receive MBS with priority over receiving unicast services, and a list of MBS services that the one or more user equipments are receiving or are interested in receiving. as well as The base station determines the priority of the MBS used to schedule the one or more user equipments on the shared channel based on the priority indicated by the priority information.

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

3. The method according to claim 2, wherein, The identifiers include MBS service identifiers, MBS session identifiers, Temporary Mobile Group identifiers (TMGI), subsets of Quality of Service (QoS) flows in an MBS session, Multicast Radio Bearer (MRB) identifiers, or unique identifiers of the interfaces used to establish MBS services or MBS sessions between the base station and the core network.

4. The method according to claim 1, wherein, The priority information includes an indication of whether the reception of multiple multimedia broadcast multicast services (MBMS) by one or more user equipments connected to the base station takes precedence over the reception of any single unicast service.

5. The method according to claim 1, wherein, The list of MBS services includes the one or more identifiers arranged in order of priority indicating the one or more identifiers.

6. The method according to claim 1, wherein, The priority information is associated with the identifier of the user equipment.

7. The method according to claim 1, wherein, The priority information is received via Next Generation Application Protocol (NGAP) messages using signaling associated with the MBS session.

8. The method according to claim 1, wherein, The priority information is received via Next Generation Application Protocol (NGAP) messages using signaling associated with the user equipment.

9. The method according to claim 1, wherein, The priority information is received via F1 Application Protocol (F1AP) messages using signaling associated with the MBS session.

10. The method according to claim 1, wherein, The priority information is received via F1 Application Protocol (F1AP) messages using signaling associated with the user equipment.

11. The method according to claim 1, wherein, The priority information is received via Radio Resource Control (RRC) messages or Media Access Control (MAC) CEs dedicated to user equipment.

12. The method according to claim 1, wherein, The priority information is received via a Radio Resource Control (RRC) message through a broadcast channel.

13. The method according to claim 1, wherein, The priority information is received via system information or via a Media Access Control-Control Element (MAC CE) broadcast in the cell.

14. An apparatus for wireless communication, comprising a processor configured to implement the method according to any one of claims 1 to 13.

15. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 13.

Images