Multicast traffic scheduling across multiple radio access technologies

Abstract

Methods, systems, and devices for wireless communication are described that provide for multicast communication at a wide area network (WAN) using a first RAT to be provided to a local area network (LAN) using a second RAT for completing the multicast communication to a user equipment (UE). A scheduler of the second RAT may prioritize transmission of the multicast data to one or more UEs using one or more parameters associated with the multicast communication. The scheduler of the second RAT may, based on a number of served clients, a quality of service (QoS) or bandwidth of the multicast communication, capabilities of the UE, one or more other data streams, or the like. A feedback scheme associated with the multicast communication, or one or more of any combination thereof, prioritizes the multicast communication with other communications of the second RAT.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 942,973, entitled “MULTICASTTRAFFIC SCHEDULING ACROSS MULTIPLE RADIO ACCESS TECHNOLOGIES,” filed by Babbellapati et al. on September 12, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including multicast traffic scheduling across multiple radio access technologies. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE).

[0005] In some deployments, a UE may be capable of using two or more radio access technologies (RATs) for radio communications. For example, a UE may be capable of wireless communications using a wide area network (WAN) such as a 4G or 5G wireless communication system and a wireless local area network (WLAN) such as a Wi-Fi (i.e., Institute of Electrical and Electronics Engineers (IEEE) 802.11) network. In some cases, multiple networks may be used to send communications, such as communications originating from a WAN and contending using a WLAN. Efficient techniques for communicating across multiple RATs may help improve throughput, reliability, and user experience. Summary of the invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting multicast traffic scheduling across multiple radio access technologies (RATs). In various aspects, the described techniques provide multicast communications originating from a wide area network (such as a fifth generation (5G) wireless communication network) using a first RAT, which will be provided to a local area network (such as a Wi-Fi network) using a second RAT, which is used to complete the multicast communication to one user equipment (UE) or multiple UEs. In some aspects, a device (such as customer premises equipment (CPE)) receiving the multicast communication via the first RAT can decode the multicast data from the multicast communication and provide the multicast data to a scheduler of the second RAT together with one or more parameters associated with the multicast data.

[0007] The scheduler of the second RAT may use one or more parameters to prioritize the transmission of multicast data to one or more UEs. In some cases, the scheduler of the second RAT may prioritize the multicast communication over other communications of the second RAT based on one or more of the following: the number of clients to receive the multicast communication, the quality of service (QoS) associated with the multicast communication, the bandwidth of the multicast communication, the capabilities of the clients using the second RAT for multiple access, one or more other data streams provided using the second RAT, a feedback scheme associated with the multicast communication, or any combination thereof.

[0008] A method for wireless communication is described. The method may include receiving multicast data associated with a multicast service via a first wireless network using a first radio access technology, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network; and sending the multicast data to the scheduler for transmission via the second wireless network.

[0009] An apparatus for wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive multicast data associated with a multicast service via a first wireless network using a first radio access technology, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; send an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network; and send the multicast data to the scheduler for transmission via the second wireless network.

[0010] Another apparatus for wireless communication is described. The apparatus may include means for receiving multicast data associated with a multicast service via a first wireless network using a first radio access technology, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; means for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network; and means for sending the multicast data to the scheduler for transmission via the second wireless network.

[0011] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive multicast data associated with a multicast service via a first wireless network using a first radio access technology, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; send an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network; and send the multicast data to the scheduler for transmission via the second wireless network.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving an indication from a scheduler to allow multicast service or deny multicast service, and wherein sending multicast data may be performed in response to the indication of allowing multicast service. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the multicast service parameter set includes one or more of the number of clients associated with the multicast service, one or more quality of service parameters, a data rate target for the multicast data, the number of non-multicast data streams to be communicated concurrently with the multicast service, or a feedback scheme associated with the multicast service. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the number of clients indicates the number of endpoint devices to be supported using the multicast service.

[0013] In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more quality of service parameters indicate an amount of delay tolerance for multicast data. In some examples of the methods, devices, and non-transitory computer-readable media described herein, a feedback scheme associated with a multicast service indicates a no feedback scheme, a negative acknowledgement-only feedback scheme, or an acknowledgement / negative acknowledgement feedback scheme. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first wireless network may be a fifth generation (5G) or sixth generation (6G) radio access network, and the second wireless network may be a wireless local area network (WLAN).

[0014] A method for wireless communication is described. The method may include receiving from a wireless modem an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; receiving from the wireless modem at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second radio access technology; and sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0015] An apparatus for wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive from a wireless modem an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; receive from the wireless modem at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second radio access technology; and send the first multicast data communication to at least a first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0016] Another apparatus for wireless communication is described. The apparatus may include means for receiving from a wireless modem an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; means for receiving from the wireless modem at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second radio access technology; and means for sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0017] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive from a wireless modem an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; receive from the wireless modem at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second radio access technology; and send the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining to grant or deny a multicast service based on one or more multicast service parameters. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more multicast service parameters include one or more of a number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining to grant or deny a multicast service based on the capabilities of each of the clients associated with the multicast service. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capabilities of each of the clients include orthogonal frequency division multiple access (OFDMA) capabilities or multi-user multiple input multiple output (MU-MIMO) capabilities.

[0020] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: mapping data communications associated with a multicast service to a separate access category (AC) queue of a second wireless network, and scheduling data transmission from the separate AC queue to one or more clients based on a higher priority of the separate AC queue than one or more other AC queues. In some examples of the methods, devices, and non-transitory computer-readable media described herein, mapping data communications associated with a multicast service to a separate AC queue may be based on one or more quality of service (QoS) thresholds associated with the separate AC queue and one or more other AC queues, and a QoS associated with the multicast service indicating a delay tolerance amount for the multicast service. In some examples of the methods, devices, and non-transitory computer-readable media described herein, mapping data communications associated with a multicast service to a separate AC queue may be based on a feedback scheme for the multicast service, and wherein a no feedback scheme or a negative acknowledgement feedback scheme may be mapped to a lower priority AC queue, and an acknowledgement / negative acknowledgement feedback scheme may be mapped to a separate AC queue having a higher priority than one or more other AC queues.

[0021] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: determining whether to grant or deny a multicast service based on the number of one or more clients to receive the multicast service. Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: scheduling data transmission associated with the multicast service using OFDMA or MU-MIMO based on the associated capabilities of each of the one or more clients and the data rate associated with the multicast service being higher than a data rate threshold. In some examples of the methods, devices, and non-transitory computer-readable media described herein, one or more thresholds associated with one or more multicast service parameters may be adjusted based on the number of other multicast service streams and other non-multicast service streams. In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first wireless network may be a 5G or 6G radio access network, and the second wireless network may be a WLAN. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example of a wireless communication system supporting multicast traffic scheduling across multiple radio access technologies (RATs) according to one or more aspects of the present disclosure is illustrated.

[0023] Figure 2 An example of multicast and broadcast service (MBS) traffic delivery via a wireless communication system supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated.

[0024] Figure 3 An example of a wireless communication system with customer premises equipment (CPE) supporting multicast traffic scheduling across multiple RATs in accordance with one or more aspects of the present disclosure is illustrated.

[0025] Figure 4 An example of a process flow for supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated.

[0026] Figure 5 An example of a flow chart illustrating multicast traffic scheduling across multiple RATs in accordance with one or more aspects of the present disclosure is illustrated.

[0027] Figure 6 An example of access category queues supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated.

[0028] Figure 7 and Figure 8 A block diagram of a device supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is shown.

[0029] Fig. 9 A block diagram of a communication manager supporting multicast traffic scheduling across multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0030] Fig.10 A diagram of a system including a UE supporting multicast traffic scheduling across multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0031] Fig.11 A diagram of a system including network entities supporting multicast traffic scheduling across multiple RATs is shown in accordance with one or more aspects of the present disclosure.

[0032] Figures 12 to 18 A flow chart illustrating a method of supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0033] In some wireless communication systems, a fixed wireless access (FWA) deployment may be used, where a wireless device (e.g., a Wi-Fi access point (AP)) of a wireless local area network may carry the last leg of traffic between a wide area network (e.g., a fifth generation (5G) or sixth generation (6G) wireless communication system) and one or more endpoint devices (e.g., user equipment (UE) or end-user devices). In some cases, a wide area network (WAN) may send multicast and broadcast service (MBS) traffic to multiple users, some of which may receive the MBS traffic via a wireless local area network (WLAN) that receives the traffic from the WAN and provides it to associated users. For example, a Wi-Fi AP may communicate with a 5G modem (e.g., in a customer premises equipment (CPE) that includes both a 5G modem and a WLAN AP), where the 5G modem receives the MBS traffic via a 5G network (e.g., a first radio access network (RAN) using a first RAT), and the AP completes the link to the multiple users using a Wi-Fi connection (e.g., a second RAN using a second RAT). In some cases, the 5G modem may have relatively good channel conditions and radio connectivity to the 5G network, and the network may operate based on such conditions (e.g., data rates are based on relatively good channel conditions between the 5G modem and the 5G serving cell).

[0034] However, in some cases, the WLAN may serve multiple different flows, which may result in a bottleneck for the MBS traffic, which may result in delays for the MBS traffic and a poor user experience in situations where the MBS traffic is delay sensitive. For example, such a bottleneck may occur because a scheduler at the WLAN (e.g., a scheduler of a Wi-Fi AP) is unaware that the MBS traffic is delay sensitive and serves other services that are more delay tolerant (e.g., enhanced mobile broadband (eMBB) traffic, or other background (BK) or best effort (BE) traffic) before the MBS traffic. In situations where the MBS traffic experiences such delays, it may result in the MBS traffic not meeting quality of service (QoS) targets even if the 5G network has information indicating relatively good channel conditions at the 5G modem. Therefore, an enhanced technique that allows the LAN to use a second RAN (e.g., a Wi-Fi network) to provide appropriate prioritization of connectivity for the "last mile" between the first RAN and the UE for the MBS traffic of the first RAN (e.g., a 5G network) may help enhance the user experience, maintain the MBS QoS targets, and enhance reliability and network efficiency.

[0035] According to various aspects discussed herein, a WAN modem (e.g., a 5G modem providing connectivity to a 5G network) may provide MBS information related to MBS traffic carried to one or more end users via the WAN and the LAN to a LAN scheduler (e.g., a Wi-Fi scheduler of a Wi-Fi AP). Information related to the MBS traffic may be passed from the WAN modem to the LAN scheduler together with or separately from the MBS data. In some cases, the MBS information may be used to provide prioritization at the LAN scheduler. In some cases, the LAN scheduler may prioritize traffic communications via the LAN based on any combination of: the number of clients, QoS parameters (e.g., 5QI parameters and associated thresholds provided with some 5G communications), bandwidth of the traffic (e.g., whether the bandwidth is above or below a threshold), LAN client capabilities (e.g., capabilities of Wi-Fi devices such as stations (STAs) or user equipment (UEs) for multiple access communications such as OFDMA / MU-MIMO), the presence of non-MBS streams, feedback techniques for MBS data (e.g., communications not configured for ACK / NACK feedback may have lower QoS targets relative to communications using only NACK or ACK / NACK feedback). The LAN scheduler may receive MBS information and prioritize MBS traffic over other more delay-tolerant traffic (e.g., BK or BE traffic), which may enhance efficiency and provide MBS service with appropriate quality. In some cases, the LAN scheduler may place MBS data in an access category (AC) queue based on the MBS information. Additionally or alternatively, the LAN scheduler may implement a separate AC transmit queue for low-latency traffic based on MBS information.

[0036] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated by and described with reference to process flows, AC queues, device diagrams, system diagrams, and flow charts involving multicast service scheduling across multiple RATs.

[0037] Figure 1 An example of a wireless communication system 100 supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0038] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more RATs.

[0039] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0040] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, an endpoint device, a CPE, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105 or a CPE 185. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105 or a CPE 185, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105 or a CPE 185, and the third node may be a network entity 105 or a CPE 185. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, CPE 185, devices, equipment, computing systems, etc. may include disclosure of UE 115, network entity 105, CPE 185, devices, equipment, computing systems, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0041] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0042] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0043] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0044] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0045] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0046] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0047] The IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay the UE's transmission through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0048] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via the NR Uu interface of the MT to the IAB node 104 via signaling. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0049] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support multicast service scheduling across multiple RATs as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0050] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, and an endpoint device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. In some cases, UE 115 may also act as a CPE. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0051] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0052] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0053] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different RAT) is used to anchor the connection.

[0054] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0055] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0056] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0057] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0058] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0059] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0060] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0061] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different RATs.

[0062] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may allow automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0063] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0064] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0065] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units) using vehicle-to-network (V2N) communication, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0066] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0067] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0068] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz (also known as a centimeter band), or an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0069] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0070] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0071] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0072] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0073] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0074] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0075] In some cases, the communication link 125 may use a first RAT (e.g., 5G or 6G RAT), and may use multiple RATs to provide connectivity for some UEs 115. For example, some UEs 115 located near a CPE 185 may be served using a link 190 of a second RAT (e.g., via a Wi-Fi WLAN in a Wi-Fi coverage area 195 served by the CPE 185), where the CPE 185 communicates with the network entity 105 via the communication link 125 using the first RAT. According to various aspects discussed herein, a scheduler associated with the second RAT may prioritize some communications received via the first RAT based on one or more parameters associated with communications of the first RAT. For example, a scheduler associated with the second RAT may prioritize MBS communications of the first RAT based on MBS information having one or more parameters provided with the MBS communications, where the one or more parameters are associated with communications of the first RAT. Several example references to communications via multiple RATs Figures 2 to 6 Have a discussion.

[0076] Figure 2 An example of MBS service delivery via a wireless communication system 200 supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 includes a first UE 115-a, a second UE 115-b, a third UE 115-c, and a fourth UE 115-d, which may be reference UEs. Figure 1 The wireless communication system 200 in this example includes a core network 210 (e.g., 5GC or reference Figure 1 The core network 130) and a first RAN 225 (e.g., NG-RAN), which includes one or more network entities (e.g., reference Figure 1 The network entity 105 described above provides a radio air interface between the first RAN 225 and the UE 115 or CPE 185-a using the first RAT. In addition, the CPE 185-a can provide wireless communication using a second RAT (e.g., Wi-Fi) to one or more UEs 115.

[0077] exist Figure 2In the example of FIG. 1 , MBS services 205 may be received at a core network 210 and transmitted to a plurality of UEs 115. The MBS services 205 may provide data for one or more of a plurality of use cases, such as real-time streaming of events using a multicast subscription-based model, broadcast services, delay-sensitive signaling, or high-resolution Internet Protocol Television (IPTV), to name a few examples. In some cases, a replication function 215 at the core network 210 may replicate MBS services 205 for a plurality of UEs for transmission via respective MBS service deliveries 220 for respective UEs 115 (e.g., point-to-point (PTP) MBS streams), or for transmission to two or more UEs 115 via a shared MBS service delivery 240 (e.g., point-to-multipoint (PTM) MBS streams). In this example, a first PDU session 230 for respective MBS service deliveries 220 may be established for a first UE 115-a, and a second PDU session 235 for respective MBS service deliveries 220 may be established for a second UE 115-b. In addition, the shared transmission for the shared MBS service delivery 240 is to both the third UE 115-c and the fourth UE 115-d. In this example, the shared MBS service delivery 240 may be transmitted to the CPE 185-a via the first RAN 225, and the CPE 185-a may provide the MBS service 205 to the third UE 115-c, the fourth UE 115-d, one or more other UEs, or any combination thereof. For example, the CPE 185-a may use the first Wi-Fi link 250-a (e.g., reference 1 Figure 1 The link 190 described above) can be used to communicate with the third UE 115-c, and the second Wi-Fi link 250-b (e.g., reference Figure 1 In some cases, the first RAN 225 capable of MBS may dynamically determine whether to perform PTP or PTM for a UE 115 to receive the MBS service 205 based on several factors, such as proximity to the same transmit receive point (TRP) of the first RAN 225, characteristics of the MBS service 205 to be transmitted (e.g., initial transmission or retransmission, delay tolerance of data, etc.), channel conditions observed at the UE 115, etc.

[0078] In some cases, the CPE 185-a may provide "list mile" connectivity between the core network 210 and the third UE 115-c and the fourth UE 115-d, which may help enhance the efficiency and reliability of communications between the core network 210 and the third UE 115-c and the fourth UE 115-d. For example, the third UE 115-c and the fourth UE 115-d may be located in a structure that prevents reliable connectivity with the first RAN 225 using the first RAT, but may be able to reliably connect to the CPE 185-a using the second RAT. The CPE 185-a may then be located at or in a location in the structure that provides a reliable connection with the first RAN 225 using the first RAT, and may thus provide an efficient and reliable end-to-end connection for the third UE 115-c and the fourth UE 115-d using both the first RAT and the second RAT. In some cases, the final portion of providing wireless connectivity using the CPE 185-a may be referred to as fixed wireless access (FWA). CPE 185-a may include, for example, a mobile router, a soft AP CPE, a gateway CPE, or an outdoor unit (ODU) that may have, for example, an associated indoor AP.

[0079] In some cases, the MBS service 205 may be received at the CPE 185-a (via the first RAN 225), where the CPE 185-a has a WAN interface (e.g., a 5G RAN interface) and an Ethernet or Wi-Fi interface (or both) for LAN clients such as the third UE 115-c and the fourth UE 115.d. However, the existing LAN system may place the associated data in a buffer for transmission via the second RAT after receiving the MBS service 205, and the WAN may consider the associated data to be successfully received. As discussed herein, in the case where the MBS service 205 is placed in a traditional buffer for transmission, other services at the CPE may cause the MBS service 205 to be delayed. Such a delay may result in the QoS objectives of the MBS service 205 not being met. In addition, in some cases, a relatively large number of UEs 115 may be served via the CPE 185-a, where multiple instances of the MBS service 205 are placed in a buffer for transmission to the UE 115. In some cases, the second RAT may provide multicast and broadcast modes, but such modes may provide relatively low data rates (eg, because such transmissions are set to the lowest possible decodable rate in order to be received by devices that only support the low rate).

[0080] In some cases, in order to provide a higher effective data delivery rate, the MBS service 205 can be converted to unicast data for each served client, which can be sent at a much higher rate than the rate available in the multicast and broadcast modes, so that even in the case where a large number of clients are to receive the MBS service 205, the transmission of the unicast data improves efficiency. In addition, since the frame is sent as unicast, the transmission rate can be further enhanced based on the client reception capability, and thus such a technique can provide more efficient use of air time. However, as discussed above, in the case where the MBS service 205 is placed in the transmission queue of each served client, even when converted to unicast data for transmission to the served client, the latency caused by other services may result in the QoS target of the MBS service 205 not being met. In some cases, the first RAN 225 can support QoS control per MBS session, where for an MBS session, one or more QoS flows can be guaranteed bit rate (GBR) or non-GBR flows. A QoS flow may have associated QoS parameters (e.g., 5G QoS Identifier (5QI) parameters) based on the data sent via the flow.

[0081] According to various aspects discussed herein, CPE 185-a can provide information to enable MBS service 205 awareness at the WLAN scheduler. Such MBS service 205 awareness can help improve user experience and can also enhance overall network efficiency. In some cases, the WLAN scheduler can use the awareness of MBS service to prioritize MBS service with other WLAN services 205 based on the parameters of the MBS service. Example reference to a wireless communication system with CPE 185 according to various aspects of the present disclosure Figure 3 discuss.

[0082] Figure 3 An example of a wireless communication system 300 with a CPE 185-b supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 includes a first UE 115-e to an nth UE 115-f, which may be reference UEs 115-e to 115-f. Figure 1 and Figure 2 In this example, the wireless communication system 200 includes a network entity 105-b and a CPE 185-b, which may be reference Figure 1 and Figure 21 and 185. In this example, the network entity 105-b can communicate with the CPE 185-b via a first link 335 using a first RAT (e.g., 5G), and the CPE 185-b can communicate with the UEs 115-e to 115-f via a second link 350 to an nth link 355 using a second RAT (e.g., Wi-Fi). In some cases, the network entity 105-b can communicate directly with one or more of the UEs 115 via associated links 340 to 345.

[0083] exist Figure 3 In an example of , CPE 185-b may include a CPE connection manager 305, a WLAN scheduler 310, a WAN modem 315 (e.g., a 5G or 6G modem that communicates in a first RAN according to a first RAT), a WLAN modem 320 (e.g., a Wi-Fi AP that communicates in a second RAN according to a second RAT), a QoS manager 325, and a CPE data path manager 330. The CPE 185-b may include associated hardware and software to perform various techniques as discussed herein, such as a modem and associated chipset for communicating (e.g., via multiple RANs, LANs, WANs, or combinations thereof), antennas for communicating using different RATs, a wired port for accessing a WAN / LAN (e.g., Ethernet, digital subscriber line (DSL), Gigabit Ethernet passive optical network (GPON), etc.), one or more processors or controllers that provide various managers, and one or more memories that can buffer data and store instructions that can be executed to perform one or more of the functions described herein.

[0084] As discussed herein, in some cases, the CPE 185-b may receive MBS traffic (such as multicast data) from a first RAN and send the MBS traffic to two or more served UEs 115-e to 115-f via a second RAN, such that a single packet of the multicast data is sent in a one-to-many manner. In some cases, the CPE connection manager 305 may manage the connections of different networks, the WLAN scheduler 310, the QoS manager 325, and the CPE data path manager 330. The QoS manager 325 may monitor and configure various QoS parameters for different data flows (including MBS data flows provided via the CPE 185-b). The CPE data path manager 330 routes the various flows via different data paths based on information from the WLAN scheduler 310, one or more configured rules (e.g., QoS rules), or any combination thereof. Thus, the WLAN scheduler 310 in conjunction with the data path manager 330 may perform traffic steering, traffic switching, etc. between different data paths for LAN or WAN communications.

[0085] In some cases, the WLAN scheduler 310 may use FWA LAN communications to provide one or more of the UEs 115 for a multicast session over the WAN, and may prioritize data traffic associated with the multicast session based on awareness of the multicast traffic and one or more parameters associated therewith. The WLAN scheduler 310 may use multicast traffic awareness to manage a relatively large number of WLAN clients (e.g., UEs 115-e to 115-f) participating in the multicast session, which may result in a relatively large amount of air time spent in sending multicast traffic and, in some cases, may result in back pressure due to a one-to-many relationship between multicast packets received via the WAN modem 315 and associated multiple multicast packets sent via the WLAN modem 320. In some cases, the CPE 185-b may have a shared buffer between the WLAN modem 320 and the WAN modem 315, and the multicast traffic awareness may allow for appropriate allocation of the shared buffer. One or more parameters associated with the multicast traffic may also indicate relatively high bandwidth versus relatively low bandwidth multicast, which may allow for appropriate resource allocation for different traffic flows (e.g., a multicast data flow and one or more other LAN or WAN flows). Furthermore, one or more parameters associated with the multicast service may indicate whether the multicast service has a relatively high QoS or is latency critical, which may allow WLAN scheduling that provides differentiated services (eg, even within the same AC).

[0086] According to various aspects, the WLAN scheduler 310 may use one or more parameters associated with the multicast stream to perform efficient WLAN scheduling. In some cases, the one or more parameters may include the number of served clients to receive the multicast stream, and the WLAN scheduler 310 may throttle the number of clients associated with the stream to provide enhanced overall system performance and network efficiency (e.g., based on a throttling configuration that is based on the FWA CPE configuration or received from the WAN core network, such as a threshold number of clients that can be served). In some cases, the one or more parameters may include a 5QI parameter (e.g., a multicast stream with 5QI<82 may be less critical and managed as part of a standard AC queue, a multicast stream with 5QI≥82 may be delay-critical and prioritized over other streams, and a multicast stream with 5QI=65 or 69 may be treated as if it were 5QI≥82).

[0087] In some cases, one or more parameters may include the bandwidth of the multicast stream, which may allow for more efficient scheduling based on the expected data rate. In some cases, one or more parameters may include the capabilities of each WLAN client (such as the first UE 115-e to the nth UE 115-f), which may allow for the implementation of multiple access technologies. For example, if the UEs 115-e to 115-f are capable of OFDMA or MU-MIMO, the WLAN scheduler 310 may use OFDMA or MU-MIMO for the multicast stream, and if one or more of the UEs 115-e to 115-f are capable of single-user (SU) operation, the WLAN scheduler may use SU communication for the multicast stream to such UEs 115. In some cases, one or more parameters may include the number of non-multicast MBS streams, which may indicate the resources that may be required for such streams. In some cases, one or more parameters may include a feedback configuration for the multicast stream, which may indicate the QoS or delay criticality of the MBS stream. For example, a relatively low QoS may be indicated if the multicast stream is configured without HARQ ACK / NACK feedback, a higher QoS may be indicated if the multicast stream is configured with only NACK feedback, and the highest QoS may be indicated if the multicast stream is configured with ACK / NACK feedback.

[0088] Figure 4 An example of a process flow 400 for supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The process flow 400 includes a UE 115-g, which may be a reference Figures 1 to 3 The process flow 400 also includes a network entity 105-c and a CPE 185-c including a WLAN scheduler 405 and a 5G modem 410, which may be referenced Figure 1-3 Examples of corresponding devices are described. The process flow 400 can implement aspects of the wireless communication system 100, 200, or 300. For example, the process flow 400 can support multicast traffic scheduling across multiple RATs.

[0089] In the following description of the process flow 400, the signaling exchanged between the UE 115-g, the WLAN scheduler 405, the 5G modem 410, and the network entity 105-c may be exchanged in a different order than the example order shown, or the operations performed by the UE 115-g, the WLAN scheduler 405, the 5G modem 410, and the network entity 105-c may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400. In addition, the WLAN scheduler 405 and the 5G modem 410 are shown for illustration and discussion purposes only, and the techniques discussed herein may be applied to other RAN / RATs.

[0090] At 415, the network entity 105-c may announce the multicast session. In some cases, the multicast session may provide real-time streaming of events using a multicast subscription-based model, critical delay-sensitive signaling, high-resolution IPTV, etc. In some cases, the announcement of the multicast session may provide one or more parameters associated with the session, such as an expected bandwidth or data rate, a periodicity of multicast transmissions, a feedback configuration, a QoS of the multicast stream, or any combination thereof. For example, the announcement of the multicast session may be provided in MBS configuration information provided in a medium access control (MAC) control element (CE) or in other control information or system information. In some cases, the multicast session announcement may be received directly by the UE 115-g via the 5G RAN, or may be received via the CPE 185-c and a WLAN associated with the WLAN scheduler 405 according to the FWA configuration.

[0091] At 420, the UE 115-g may send a multicast session request to the WLAN scheduler 405. In some cases, the UE 115-g may be configured for FWA via a WLAN associated with the CPE 185-c and may send the multicast session request based on the multicast session announcement. At 425, the WLAN scheduler 405 and the 5G modem 410 may exchange information related to the multicast session. For example, the WLAN scheduler 405 and the 5G modem 410 may exchange information related to the multicast session, such as 5QI information, bandwidth of the multicast stream, feedback configuration for the multicast stream, or any combination thereof.

[0092] At 430, the WLAN scheduler 405 may determine to grant a multicast flow. In some cases, the determination may be based on one or more parameters of the multicast session, such as information related to the multicast session exchanged with the 5G modem, the number of clients requesting the multicast session, the capabilities of the clients requesting the multicast session, the number of non-MBS flows served by the CPE 185-c, or any combination thereof. In some cases, a multicast session from the LAN may be served / granted only if the number of clients is below an acceptable limit (e.g., a configured threshold), one or more QoS constraints relative to the 5QI are met, the capabilities of the served UE 115 for OFDMA or MU-MIMO (e.g., flows of UEs with OFDMA / MU-MIMO capabilities are given priority SU flows for scheduling multicast services), a failure rate of clients (e.g., if the number of transmission failures for a particular client exceeds a threshold, the client may be removed from the multicast session), or any combination thereof. Example References to Multicast Service Grants and Associated Prioritization Figure 5In some cases, to avoid competition from other flows, an alternative AC queue for low-latency multicast (e.g., for multicast flows with 5QI>82) may be implemented. An example of such an alternative AC queue is shown in Figure 6 discuss.

[0093] At 435, based on the determination that the multicast flow is permitted, the WLAN scheduler 405 may send a multicast session request to the 5G modem 410. At 440, the 5G modem 410 may send the multicast session request to the network entity 105-c. At 445, the network entity 105-c may send multicast data to the 5G modem 410 based on the multicast session request.

[0094] At 450, the 5G modem may format a multicast indication associated with the multicast stream. In some cases, the multicast indication may provide one or more parameters associated with the multicast stream, or may indicate an ID of a multicast session associated with a previous multicast session request. In some cases, at 455, the multicast indication may be provided to the WLAN scheduler 405 along with the multicast data, or may be provided separately from the multicast data. At 460, in some cases where the multicast stream has a configured NACK or ACK / NACK feedback, the 5G modem 410 may send ACK / NACK feedback to the network entity 105-c.

[0095] At 465, the WLAN scheduler 405 may prioritize the multicast data and other WLAN traffic. In some cases, the multicast data is prioritized based on one or more parameters associated with the multicast session, as discussed herein. At 470, the WLAN scheduler 405 may schedule the multicast data for transmission by a WLAN modem (e.g., a Wi-Fi modem) to the UE 115-g.

[0096] Figure 5 An example of a flowchart 500 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The flowchart 500 may be implemented in a system supporting multicast service scheduling across multiple RATs, such as the system described in the accompanying drawings. Figures 1 to 4 The operations as discussed with reference to flowchart 500 may be performed by one or more components of a CPE, such as a WLAN scheduler, as discussed herein.

[0097] The WLAN scheduler may receive an MBS session initiation request at 505. In some cases, the MBS session initiation request may be received from a UE in a FWA configuration over which a CPE communicates with a first RAN using a first RAT and the CPE communicates with a UE in a second RAN using a second RAT.

[0098] At 510, the WLAN scheduler may determine whether a client limit is exceeded for the MBS session. In some cases, the client limit may be based on a FWA CPE limit, or may be based on configuration information from the first RAN. In some cases, the client limit may be set based on the capacity of multicast communications via the CPE, the number of clients served via the CPE, the type of service associated with the MBS session, or any combination thereof. At 515, if it is determined that the client limit is exceeded, the WLAN scheduler may deny the session request. In some cases, the WLAN scheduler may provide an indication to the UE that the MBS session is denied, and the UE may attempt to directly initiate the MBS session via the first RAN.

[0099] At 520, if it is determined that the client limit is not exceeded, the WLAN scheduler may determine whether the QoS value is less than a first threshold (e.g., a 5QI value is less than 82). At 525, if it is determined that the QoS value is less than the first threshold, the WLAN scheduler may determine whether the QoS value has a specific value corresponding to a higher priority service (e.g., a 5QI value of 65 or 69). At 530, if it is determined that the QoS threshold does not have a specific value, the WLAN scheduler may map packets of the MBS session to the AC queue according to standard WLAN AC mapping, and at 565, the WLAN scheduler may admit the flow for the MBS session.

[0100] At 535, if the QoS value is greater than or equal to the first threshold, or if the QoS value is equal to a specific value, the WLAN scheduler may determine whether the data rate associated with the MBS session is less than the rate threshold. At 540, if it is determined that the data rate is not less than the rate threshold, the WLAN scheduler may determine whether all clients requesting the MBS session have MU-MIMO capabilities. At 545, if it is determined that all clients do not have MU-MIMO capabilities, the WLAN scheduler may map packets of the MBS session to an alternative AC queue associated with low-latency multicast communication, and at 565, the WLAN scheduler may grant a flow for the MBS session. At 560, if it is determined that all clients have MU-MIMO capabilities, the WLAN scheduler may schedule downlink MU-MIMO for the client requesting the MBS session, and at 565, the WLAN scheduler may grant a flow for the MBS session.

[0101] At 550, if it is determined that the data rate is less than the data rate threshold, the WLAN scheduler may determine whether all clients requesting the MBS flow are OFDMA capable. If all clients are not OFDMA capable, at 560, the WLAN scheduler may map packets for the MBS session to an alternative AC queue associated with low-latency multicast communication, and at 565, the WLAN scheduler may grant the flow for the MBS session. At 555, if it is determined that all clients are OFDMA capable, the WLAN scheduler may schedule downlink OFDMA for the clients requesting the MBS session, and at 565, the WLAN scheduler may grant the flow for the MBS session.

[0102] Figure 6 An example of an access category queue 600 supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is illustrated. The access category queue 600 may be used in a system supporting multicast service scheduling across multiple RATs (such as in a system such as a reference system). Figures 1 to 5 The wireless communication system is implemented as described above.

[0103] exist Figure 6In an example of , a WLAN scheduler (such as a WLAN scheduler of a FWA CPE) may have granted a multicast flow as discussed herein (e.g., based on one or more parameters associated with the flow). The WLAN scheduler may receive a MAC service data unit (MSDU) 605, which may be provided to a packet mapping function 610. The packet mapping function 610 may map packets of the MSDU to one of a plurality of ACs 615, including a background (BK) AC 620, a best effort (BE) AC 625, an alternative video (A_VI) AC 630, a video (VI) AC 635, an alternative voice (A_VO) AC 640, and a voice (VO) AC 645. The mapped ACs may then be mapped to one of the plurality of transmit AC queues 650, wherein the BK AC 620 is mapped to the BK transmit queue 655, the BE AC 625 is mapped to the BE transmit queue 660, the A_VI AC 630 and the VI AC 635 are mapped to the VI transmit queue 665, and the A_VO AC 640 and the VO AC 645 are mapped to the VO transmit queue 670. In this example, multicast packets having a QoS value exceeding a QoS threshold (e.g., 5QI>82) or having a pre-specified QoS value (e.g., 5QI=65 or 69) from the VI AC 635 or the VO AC 645 may be mapped to an alternative low latency (LL) transmit queue 675. In such a case, the WLAN scheduler may schedule packets from the alternative LL transmit queue 675 before packets from the other transmit queues 655 to 670. Therefore, a relatively high QoS multicast packet may be provided with a higher transmission priority, and the WLAN scheduler may provide enhanced network efficiency and enhanced user experience for the multicast data.

[0104] Figure 7 A block diagram 700 of a device 705 supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of a UE 115, a CPE 185, or a network entity 105 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0105] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to multicast service scheduling across multiple RATs). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas. In some cases, the receiver 710 may include multiple receivers for different RATs (e.g., wireless modems for different RATs).

[0106] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to multicast service scheduling across multiple RATs). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas. In some cases, the transmitter 715 may include multiple transmitters for different RATs (e.g., wireless modems for different RATs).

[0107] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of multicast traffic scheduling across multiple RATs as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0108] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0109] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0110] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0111] According to examples disclosed herein, the device 705 may support wireless communications. For example, the receiver 710 may be configured to or otherwise support components for receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The communication manager 720 may be configured to or otherwise support components for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network (e.g., which in some aspects may be included within the communication manager). The communication manager 720 may be configured to or otherwise support components for sending the multicast data to the scheduler for transmission via the second wireless network.

[0112] Additionally or alternatively, according to examples disclosed herein, the device 705 may support wireless communications. For example, the communication manager 720 may be configured to or otherwise support components for receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via a wireless modem using a first wireless network utilizing a first RAT. The communication manager 720 may be configured to or otherwise support components for receiving, from the wireless modem, at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second RAT. The transmitter 715 may be configured to or otherwise support components for sending the first multicast data communication to at least a first client via a second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0113] By including or configuring a communication manager 720 according to the examples described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof) may support techniques for prioritizing multicast communications in traffic scheduling across multiple RATs, which provide enhanced reliability for multicast streams sent to UEs across multiple RATs, enhance network efficiency, enable latency-sensitive multicast streams, and provide an enhanced user experience.

[0114] Figure 8 A block diagram 800 of a device 805 supporting multicast traffic scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705, UE 115, CPE 185, or network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0115] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to multicast service scheduling across multiple RATs). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0116] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to multicast service scheduling across multiple RATs). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0117] The device 805 or its various components may be examples of components for performing various aspects of multicast traffic scheduling across multiple RATs as described herein. For example, the communication manager 820 may include a WAN modem manager 825, an MBS communication manager 830, a WLAN scheduler 835, a WLAN modem manager 840, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0118] According to examples disclosed herein, the communication manager 820 may support wireless communications. The WAN modem manager 825 may be configured to or otherwise support components for receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The MBS communication manager 830 may be configured to or otherwise support components for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network. The WAN modem manager 825 may be configured to or otherwise support components for sending the multicast data to the scheduler for transmission via the second wireless network.

[0119] Additionally or alternatively, according to examples disclosed herein, the communication manager 820 may support wireless communications. The WLAN scheduler 835 may be configured to or otherwise support components for receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via a wireless modem using a first wireless network utilizing a first RAT. The WLAN scheduler 835 may be configured to or otherwise support components for receiving, from a wireless modem, at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second RAT. The WLAN modem manager 840 may be configured to or otherwise support components for sending the first multicast data communication to at least a first client via a second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0120] Fig. 9 A block diagram 900 of a communication manager 920 supporting multicast traffic scheduling across multiple RATs in accordance with one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of multicast traffic scheduling across multiple RATs as described herein. For example, the communication manager 920 may include a WAN modem manager 925, an MBS communication manager 930, a WLAN scheduler 935, a WLAN modem manager 940, an AC queue manager 945, a CPE data path manager 950, a QoS manager 955, a WAN feedback manager 960, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0121] According to examples disclosed herein, the communication manager 920 may support wireless communications. The WAN modem manager 925 may be configured to or otherwise support components for receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The MBS communication manager 930 may be configured to or otherwise support components for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network. In some examples, the WAN modem manager 925 may be configured to or otherwise support components for sending the multicast data to the scheduler for transmission via the second wireless network.

[0122] In some examples, the MBS communication manager 930 may be configured to or otherwise support a component for receiving an indication from a scheduler to allow or deny a multicast service, and wherein sending the multicast data is performed in response to the indication of allowing the multicast service. In some examples, the multicast service parameter set includes one or more of the number of clients associated with the multicast service, one or more quality of service parameters, a data rate target for the multicast data, the number of non-multicast data streams to be communicated concurrently with the multicast service, or a feedback scheme associated with the multicast service. In some examples, the number of clients indicates the number of endpoint devices to be supported using the multicast service. In some examples, one or more quality of service parameters indicate the amount of delay tolerance for the multicast data. In some examples, the feedback scheme associated with the multicast service indicates a no feedback scheme, a NACK-only feedback scheme, or an ACK / NACK feedback scheme. In some examples, the first wireless network is a 5G or 6G radio access network, and the second wireless network is a WLAN.

[0123] Additionally or alternatively, according to examples disclosed herein, the communication manager 920 may support wireless communications. The WLAN scheduler 935 may be configured to or otherwise support components for receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via a wireless modem using a first wireless network utilizing a first RAT. In some examples, the WLAN scheduler 935 may be configured to or otherwise support components for receiving at least a first multicast data communication from a wireless modem, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second RAT. The WLAN modem manager 940 may be configured to or otherwise support components for sending the first multicast data communication to at least a first client via a second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0124] In some examples, the WLAN scheduler 935 may be configured to or otherwise support components for determining to grant or deny a multicast service based on one or more multicast service parameters. In some examples, the one or more multicast service parameters include one or more of a number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

[0125] In some examples, the WLAN scheduler 935 may be configured to or otherwise support components for determining whether to grant or deny a multicast service based on the capabilities of each of the clients associated with the multicast service. In some examples, the capabilities of each of the clients include OFDMA capabilities or MU-MIMO capabilities.

[0126] In some examples, the AC queue manager 945 may be configured or otherwise support components for mapping data communications associated with the multicast service to a separate AC transmit queue of the second wireless network. In some examples, the AC queue manager 945 may be configured or otherwise support components for scheduling data transmissions from the separate AC transmit queue to one or more clients based on a higher priority of the separate AC transmit queue than one or more other AC transmit queues. In some examples, mapping the data communications associated with the multicast service to the separate AC transmit queue is based on one or more QoS thresholds associated with the separate AC transmit queue and the one or more other AC queues, and a QoS associated with the multicast service that indicates an amount of delay tolerance for the multicast service.

[0127] In some examples, mapping data communications associated with the multicast service to a separate AC transmit queue is based on a feedback scheme for the multicast service, and wherein a no feedback scheme or a NACK-only feedback scheme is mapped to a lower priority AC transmit queue, and an ACK / NACK feedback scheme is mapped to a separate AC transmit queue having a higher priority than one or more other AC queues. In some examples, the WLAN scheduler 935 may be configured to or otherwise support components for determining to grant or deny a multicast service based on a number of one or more clients to receive the multicast service.

[0128] In some examples, the CPE data path manager 950 may be configured to or otherwise support components for scheduling data transmission associated with a multicast service using OFDMA or MU-MIMO based on the associated capabilities of each of the one or more clients and the data rate associated with the multicast service being above a data rate threshold. In some examples, one or more thresholds associated with one or more multicast service parameters are adjusted based on the number of other multicast service flows and other non-multicast service flows. In some examples, the first wireless network is a 5G or 6G radio access network, and the second wireless network is a WLAN.

[0129] Fig.10 A diagram of a system 1000 including a device 1005 that supports multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, a CPE 185, or a network entity 105 as described herein, or include components thereof. The device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1005 may include components that support output and acquisition of communications, such as a communication manager 1020, a transceiver 1010, an antenna 1015, a memory 1025, a code 1030, and a processor 1035. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1040).

[0130] The transceiver 1010 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1010 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1010 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1005 may include one or more antennas 1015, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1010 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1015, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1015, from a wired receiver); and demodulating a signal. The transceiver 1010 or transceiver 1010 and one or more antennas 1015 or wired interfaces (where applicable) may be examples of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0131] The memory 1025 may include random access memory (RAM) and read-only memory (ROM). The memory 1025 may store computer-readable, computer-executable code 1030 including instructions that, when executed by the processor 1035, cause the device 1005 to perform various functions described herein. The code 1030 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1030 may not be directly executable by the processor 1035, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1025 may also include, among other things, a basic input / output (I / O) system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0132] The processor 1035 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1035 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1035. The processor 1035 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1025) so that the device 1005 performs various functions (e.g., functions or tasks that support multicast service scheduling across multiple RATs). For example, the device 1005 or a component of the device 1005 may include a processor 1035 and a memory 1025 coupled to the processor 1035, and the processor 1035 and the memory 1025 are configured to perform the various functions described herein. Processor 1035 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1005 (e.g., by executing code 1030).

[0133] In some examples, bus 1040 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1040 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1005, or communications performed between different components of device 1005 that may be co-located or may be located in different locations (e.g., where device 1005 may refer to a system in which one or more of communication manager 1020, transceiver 1010, memory 1025, code 1030, and processor 1035 may be located in one of the different components or divided between the different components).

[0134] In some examples, the communication manager 1020 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1020 may manage the delivery of data communications for client devices such as one or more UEs 115. In some examples, the communication manager 1020 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1020 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0135] According to examples disclosed herein, the communication manager 1020 may support wireless communications. For example, the communication manager 1020 may be configured to or otherwise support components for receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The communication manager 1020 may be configured to or otherwise support components for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network. The communication manager 1020 may be configured to or otherwise support components for sending the multicast data to the scheduler for transmission via the second wireless network.

[0136] Additionally or alternatively, according to examples disclosed herein, the communication manager 1020 may support wireless communications. For example, the communication manager 1020 may be configured to or otherwise support components for receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via a wireless modem using a first wireless network utilizing a first RAT. The communication manager 1020 may be configured to or otherwise support components for receiving, from the wireless modem, at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second RAT. The communication manager 1020 may be configured to or otherwise support components for sending the first multicast data communication to at least a first client via a second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0137] By including or configuring a communications manager 1020 according to the examples described herein, the device 1005 may support techniques for prioritizing multicast communications in service scheduling across multiple RATs, which provide enhanced reliability for multicast streams sent to UEs across multiple RATs, enhance network efficiency, enable latency-sensitive multicast streams, and provide an enhanced user experience.

[0138] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1010, one or more antennas 1015 (e.g., where applicable), or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1035, the memory 1025, the code 1030, the transceiver 1010, or any combination thereof. For example, the code 1030 may include instructions that are executable by the processor 1035 to cause the device 1005 to perform various aspects of multicast service scheduling across multiple RATs as described herein, or the processor 1035 and the memory 1025 may be otherwise configured to perform or support such operations.

[0139] Fig.11 A diagram of a system 1100 including a device 1105 that supports multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 705, a device 805, a CPE 185, or a UE 115 as described herein or include components thereof. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an I / O controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

[0140] I / O controller 1110 can manage input signals and output signals of device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor (such as processor 1140). In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0141] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired or wireless link, as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. The transceiver 1115 or the transceiver 1115 and the one or more antennas 1125 may be examples of the transmitter 715, the transmitter 815, the receiver 710, the receiver 810, or any combination thereof or components thereof as described herein.

[0142] Memory 1130 may include RAM and ROM. Memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by processor 1140, cause device 1105 to perform various functions described herein. Code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1135 may not be directly executable by processor 1140, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1130 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0143] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) so that the device 1105 performs various functions (e.g., functions or tasks that support multicast service scheduling across multiple RATs). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or coupled to the processor 1140, and the processor 1140 and the memory 1130 are configured to perform the various functions described herein.

[0144] According to examples disclosed herein, the communication manager 1120 may support wireless communications. For example, the communication manager 1120 may be configured to or otherwise support components for receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The communication manager 1120 may be configured to or otherwise support components for sending an information message indicating one or more multicast service parameters in the set of multicast service parameters to a scheduler of the second wireless network. The communication manager 1120 may be configured to or otherwise support components for sending the multicast data to the scheduler for transmission via the second wireless network.

[0145] Additionally or alternatively, according to examples disclosed herein, the communication manager 1120 may support wireless communications. For example, the communication manager 1120 may be configured to or otherwise support components for receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via a wireless modem using a first wireless network utilizing a first RAT. The communication manager 1120 may be configured to or otherwise support components for receiving, from the wireless modem, at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second RAT. The communication manager 1120 may be configured to or otherwise support components for sending the first multicast data communication to at least a first client via a second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on the one or more multicast service parameters.

[0146] By including or configuring a communications manager 1120 according to the examples described herein, the device 1105 may support techniques for prioritizing multicast communications in service scheduling across multiple RATs, which provide enhanced reliability for multicast streams sent to UEs across multiple RATs, enhance network efficiency, enable latency-sensitive multicast streams, and provide an enhanced user experience.

[0147] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions that are executable by the processor 1140 to cause the device 1105 to perform various aspects of multicast service scheduling across multiple RATs as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0148] Fig.12 A flowchart illustrating a method 1200 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0149] At 1205, the method may include receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Fig. 9 The WAN modem manager 925 is used to execute.

[0150] At 1210, the method may include sending an information message indicating one or more multicast service parameters in a multicast service parameter set to a scheduler of the second wireless network. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Fig. 9 The MBS communication manager 930 is used to execute.

[0151] At 1215, the method may include sending the multicast data to the scheduler for transmission via the second wireless network. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Fig. 9The WAN modem manager 925 is used to execute.

[0152] Fig.13 A flowchart illustrating a method 1300 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0153] At 1305, the method may include receiving multicast data associated with a multicast service via a first wireless network using a first RAT, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second RAT, and wherein the multicast service has a set of multicast service parameters. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig. 9 The WAN modem manager 925 is used to execute.

[0154] At 1310, the method may include sending an information message indicating one or more multicast service parameters in a multicast service parameter set to a scheduler of the second wireless network. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig. 9 The MBS communication manager 930 is used to execute.

[0155] At 1315, the method may include receiving an indication from the scheduler that the multicast service is permitted or denied. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig. 9 The MBS communication manager 930 is used to execute.

[0156] At 1320, the method may include sending the multicast data to the scheduler for transmission via the second wireless network. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Fig. 9 The WAN modem manager 925 is used to execute.

[0157] Fig.14A flowchart illustrating a method 1400 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0158] At 1405, the method may include receiving, from the wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first RAT. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0159] At 1410, the method may include receiving at least a first multicast data communication from a wireless modem, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network using a second RAT. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0160] At 1415, the method may include sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on one or more multicast service parameters. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig. 9 The WLAN modem manager 940 is used to execute.

[0161] Fig.15 A flowchart illustrating a method 1500 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0162] At 1505, the method may include receiving, from the wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first RAT. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0163] At 1510, the method may include determining to grant or deny a multicast service based on one or more multicast service parameters. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The multicast service parameters may be performed by the WLAN scheduler 935. In some cases, the one or more multicast service parameters include one or more of a number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

[0164] At 1515, the method may include receiving at least a first multicast data communication from a wireless modem, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network using a second RAT. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0165] At 1520, the method may include sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on one or more multicast service parameters. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig. 9 The WLAN modem manager 940 is used to execute.

[0166] Fig.16A flowchart illustrating a method 1600 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0167] At 1605, the method may include receiving, from the wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first RAT. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0168] At 1610, the method may include receiving at least a first multicast data communication from a wireless modem, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network using a second RAT. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0169] At 1615, the method may include mapping data communications associated with the multicast service to a separate AC transmit queue of the second wireless network. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The AC queue manager 945 is used for execution.

[0170] At 1620, the method may include means for scheduling data transmission from the separate AC transmit queue to one or more clients based on the separate AC transmit queue having a higher priority than one or more other AC queues. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The AC queue manager 945 is used for execution.

[0171] At 1625, the method may include sending a first multicast data communication to at least a first client via a second wireless network based on the AC queue. The operations of 1625 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig. 9 The WLAN modem manager 940 is used to execute.

[0172] Fig.17 A flowchart illustrating a method 1700 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0173] At 1705, the method may include receiving, from the wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first RAT. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0174] At 1710, the method may include determining to grant or deny the multicast service based on the number of one or more clients to receive the multicast service. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0175] At 1715, the method may include receiving at least a first multicast data communication from the wireless modem in response to the grant of the multicast service, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network using a second RAT. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0176] At 1720, the method may include sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on one or more multicast service parameters. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig. 9 The WLAN modem manager 940 is used to execute.

[0177] Fig.18 A flowchart illustrating a method 1800 for supporting multicast service scheduling across multiple RATs according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a UE or a component thereof as described herein. Figures 1 to 11 The network entity or UE 115 may be used to perform the functions. In some examples, the network entity or UE may execute an instruction set to control the functional elements of the network entity or UE to perform the functions. Additionally or alternatively, the network entity or UE may use dedicated hardware to perform various aspects of the functions.

[0178] At 1805, the method may include receiving, from the wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first RAT. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0179] At 1810, the method may include receiving at least a first multicast data communication from a wireless modem, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network using a second RAT. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig. 9 The WLAN scheduler 935 is used to execute.

[0180] At 1815, the method may include scheduling data transmission associated with the multicast service using OFDMA or MU-MIMO based on the associated capabilities of each of the one or more clients and the data rate associated with the multicast service being above a data rate threshold. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig. 9 The CPE data path manager 950 is used to execute.

[0181] At 1820, the method may include sending the first multicast data communication to at least the first client via the second wireless network based on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based on one or more multicast service parameters. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig. 9The WLAN modem manager 940 is used to execute.

[0182] The following provides an overview of various aspects of the disclosure:

[0183] Aspect 1: A method for wireless communication, the method comprising: receiving multicast data associated with a multicast service via a first wireless network using a first radio access technology, wherein the multicast data will be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a multicast service parameter set; sending an information message indicating one or more multicast service parameters in the multicast service parameter set to a scheduler of the second wireless network; and sending the multicast data to the scheduler for transmission via the second wireless network.

[0184] Aspect 2: The method according to aspect 1, the method further comprising: receiving an indication from the scheduler to allow the multicast service or to deny the multicast service, and wherein sending the multicast data is performed in response to the indication to allow the multicast service.

[0185] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the multicast service parameter set includes one or more of the number of clients associated with the multicast service, one or more quality of service parameters, a data rate target for the multicast data, a number of non-multicast data streams to be communicated concurrently with the multicast service, or a feedback scheme associated with the multicast service.

[0186] Aspect 4: The method according to aspect 3, wherein the number of clients indicates the number of endpoint devices to be supported using the multicast service.

[0187] Aspect 5: The method according to any one of aspects 3 to 4, wherein the one or more quality of service parameters indicate a delay tolerance amount of the multicast data.

[0188] Aspect 6: The method according to any one of aspects 3 to 5, wherein the feedback scheme associated with the multicast service indicates a no feedback scheme, a negative acknowledgement-only feedback scheme, or an acknowledgement / negative acknowledgement feedback scheme.

[0189] Aspect 7: The method according to any one of aspects 1 to 6, wherein the first wireless network is a 5G or 6G radio access network, and the second wireless network is a WLAN.

[0190] Aspect 8: A method for wireless communications, the method comprising: receiving from a wireless modem an information message indicating one or more multicast service parameters associated with a multicast service provided via a first wireless network utilizing a first radio access technology; receiving from the wireless modem at least a first multicast data communication, wherein the first multicast data communication is to be sent to one or more clients via a second wireless network utilizing a second radio access technology; and sending the first multicast data communication to at least a first client via the second wireless network based at least in part on a priority ranking of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the priority ranking is based at least in part on the one or more multicast service parameters.

[0191] Aspect 9: The method according to aspect 8, the method further comprising: determining to grant or deny the multicast service based at least in part on the one or more multicast service parameters.

[0192] Aspect 10: A method according to any one of Aspects 8 to 9, wherein the one or more multicast service parameters include one or more of the number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

[0193] Aspect 11: The method according to aspect 10, further comprising: determining to grant or deny the multicast service based at least in part on the capability of each of the clients associated with the multicast service.

[0194] Aspect 12: The method according to aspect 11, wherein the capability of each of the clients comprises OFDMA capability or MU-MIMO capability.

[0195] Aspect 13: According to the method described in any one of Aspects 8 to 12, the method also includes: mapping data communications associated with the multicast service to a separate AC queue of the second wireless network; and scheduling data transmission from the separate AC queue to the one or more clients based at least in part on the higher priority of the separate AC queue than one or more other AC queues.

[0196] Aspect 14: A method according to Aspect 13, wherein mapping the data communication associated with the multicast service to the separate AC queue is based at least in part on one or more QoS thresholds associated with the separate AC queue and the one or more other AC queues, and the QoS associated with the multicast service indicating a delay tolerance amount for the multicast service.

[0197] Aspect 15: A method according to any one of Aspects 13 to 14, wherein mapping the data communication associated with the multicast service to the separate AC queue is based at least in part on a feedback scheme of the multicast service, and wherein a no feedback scheme or a negative confirmation feedback scheme is mapped to a lower priority AC queue, and a confirmation / negative confirmation feedback scheme is mapped to the separate AC queue having a higher priority than the one or more other AC queues.

[0198] Aspect 16: The method according to any one of aspects 8 to 15, the method further comprising: determining to grant or deny the multicast service based at least in part on the number of the one or more clients to receive the multicast service.

[0199] Aspect 17: According to the method described in any one of Aspects 8 to 16, the method also includes: using OFDMA or MU-MIMO to schedule data transmission associated with the multicast service based at least in part on the associated capabilities of each of the one or more clients and that the data rate associated with the multicast service is higher than a data rate threshold.

[0200] Aspect 18: The method according to any one of aspects 8 to 17, wherein one or more thresholds associated with the one or more multicast service parameters are adjusted at least in part based on the number of other multicast service flows and other non-multicast service flows.

[0201] Aspect 19: The method according to any one of aspects 8 to 18, wherein the first wireless network is a 5G or 6G radio access network, and the second wireless network is a WLAN.

[0202] Aspect 20: An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 7.

[0203] Aspect 21: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 7.

[0204] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 7.

[0205] Aspect 23: An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 8 to 19.

[0206] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to any one of aspects 8 to 19.

[0207] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of aspects 8 to 19.

[0208] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0209] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0210] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0211] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0212] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0213] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, a server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0214] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0215] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0216] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0217] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0218] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, the method comprising: receiving, via a first wireless network using a first radio access technology, multicast data associated with a multicast service, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; sending an information message indicating one or more multicast service parameters in the multicast service parameter set to a scheduler of the second wireless network; as well as The multicast data is sent to the scheduler for transmission via the second wireless network.

2. The method according to claim 1, further comprising: An indication is received from the scheduler to grant the multicast service or to deny the multicast service, and wherein sending the multicast data is performed in response to the indication to grant the multicast service.

3. The method of claim 1 , wherein the set of multicast service parameters comprises one or more of a number of clients associated with the multicast service, one or more quality of service parameters, a data rate target for the multicast data, a number of non-multicast data streams to be communicated concurrently with the multicast service, or a feedback scheme associated with the multicast service. The method of claim 3 , wherein the number of clients indicates a number of endpoint devices to be supported using the multicast service. The method of claim 3 , wherein the one or more quality of service parameters indicate an amount of delay tolerance for the multicast data.

6. The method of claim 3, wherein the feedback scheme associated with the multicast service indicates a no feedback scheme, a negative acknowledgement-only feedback scheme, or an acknowledgement / negative acknowledgement feedback scheme.

7. The method of claim 1, wherein the first wireless network is a fifth generation (5G) or sixth generation (6G) radio access network, and the second wireless network is a wireless local area network (WLAN).

8. A method for wireless communication, the method comprising: receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; receiving at least a first multicast data communication from the wireless modem, wherein the first multicast data communication is to be transmitted to one or more clients via a second wireless network using a second radio access technology; as well as The first multicast data communication is sent to at least a first client via the second wireless network based at least in part on a prioritization of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the prioritization is based at least in part on the one or more multicast service parameters.

9. The method according to claim 8, further comprising: A determination is made to grant or deny the multicast service based at least in part on the one or more multicast service parameters.

10. The method of claim 8, wherein the one or more multicast service parameters include one or more of a number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

11. The method according to claim 10, further comprising: Granting or denying the multicast service is determined based at least in part on the capabilities of each of the clients associated with the multicast service.

12. The method of claim 11, wherein the capability of each of the clients comprises orthogonal frequency division multiple access (OFDMA) capability or multi-user multiple input multiple output (MU-MIMO) capability.

13. The method according to claim 8, further comprising: mapping data communications associated with the multicast service to a separate AC transmit queue of the second wireless network; as well as Data transmission from the individual AC transmit queue to the one or more clients is scheduled based at least in part on a higher priority of the individual AC transmit queue than one or more other AC queues.

14. The method of claim 13, wherein mapping the data communications associated with the multicast service to the separate AC transmit queue is based at least in part on one or more quality of service (QoS) thresholds associated with the separate AC transmit queue and the one or more other AC queues, and a QoS associated with the multicast service that indicates an amount of delay tolerance for the multicast service.

15. The method of claim 13, wherein mapping the data communications associated with the multicast service to the separate AC transmit queue is based at least in part on a feedback scheme of the multicast service, and wherein a no feedback scheme or a negative acknowledgement feedback scheme is mapped to a lower priority AC queue, and an acknowledgement / negative acknowledgement feedback scheme is mapped to the separate AC transmit queue having a higher priority than the one or more other AC queues.

16. The method according to claim 8, further comprising: Granting or denying the multicast service is determined based at least in part on a number of the one or more clients to receive the multicast service.

17. The method according to claim 8, further comprising: Based at least in part on the associated capabilities of each of the one or more clients and that a data rate associated with the multicast service is above a data rate threshold, data transmission associated with the multicast service is scheduled using orthogonal frequency division multiple access (OFDMA) or multi-user multiple input multiple output (MU-MIMO).

18. The method of claim 8, wherein one or more thresholds associated with the one or more multicast service parameters are adjusted based at least in part on a number of other multicast service flows and other non-multicast service flows.

19. The method of claim 8, wherein the first wireless network is a fifth generation (5G) or sixth generation (6G) radio access network, and the second wireless network is a wireless local area network (WLAN).

20. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, via a first wireless network using a first radio access technology, multicast data associated with a multicast service, wherein the multicast data is to be provided to one or more clients via a second wireless network using a second radio access technology, and wherein the multicast service has a set of multicast service parameters; sending an information message indicating one or more multicast service parameters in the multicast service parameter set to a scheduler of the second wireless network; as well as The multicast data is sent to the scheduler for transmission via the second wireless network.

21. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is received from the scheduler to grant the multicast service or to deny the multicast service, and wherein sending the multicast data is performed in response to the indication to grant the multicast service.

22. An apparatus according to claim 20, wherein the set of multicast service parameters includes one or more of the number of clients associated with the multicast service, one or more quality of service parameters, a data rate target for the multicast data, a number of non-multicast data streams to be communicated concurrently with the multicast service, or a feedback scheme associated with the multicast service.

23. The apparatus of claim 20, wherein the first wireless network is a fifth generation (5G) or sixth generation (6G) radio access network, and the second wireless network is a wireless local area network (WLAN).

24. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a wireless modem, an information message indicating one or more multicast service parameters associated with a multicast service provided via the wireless modem using a first wireless network utilizing a first radio access technology; receiving at least a first multicast data communication from the wireless modem, wherein the first multicast data communication is to be transmitted to one or more clients via a second wireless network using a second radio access technology; as well as The first multicast data communication is sent to at least a first client via the second wireless network based at least in part on a prioritization of the first multicast data communication relative to one or more other data communications to be sent via the second wireless network, wherein the prioritization is based at least in part on the one or more multicast service parameters.

25. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: A determination is made to grant or deny the multicast service based at least in part on the one or more multicast service parameters.

26. An apparatus according to claim 24, wherein the one or more multicast service parameters include one or more of the number of clients associated with the multicast service, a quality of service parameter associated with the multicast service, a data rate target for the multicast service, a number of non-multicast data streams to be communicated concurrently with the multicast service, a capability of each of the clients associated with the multicast service, or a feedback scheme associated with the multicast service.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: Granting or denying the multicast service is determined based at least in part on the capabilities of each of the clients associated with the multicast service.

28. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: mapping data communications associated with the multicast service to a separate access category (AC) queue of the second wireless network; and Data transmission from the individual AC transmit queue to the one or more clients is scheduled based at least in part on a higher priority of the individual AC transmit queue than one or more other AC queues.

29. The apparatus of claim 28, wherein mapping the data communications associated with the multicast service to the separate AC transmit queue is based at least in part on one or more quality of service (QoS) thresholds associated with the separate AC transmit queue and the one or more other AC queues, and a QoS associated with the multicast service that indicates an amount of delay tolerance for the multicast service.

30. The apparatus of claim 28, wherein mapping the data communications associated with the multicast service to the separate AC transmit queue is based at least in part on a feedback scheme of the multicast service, and wherein a no feedback scheme or a negative acknowledgement feedback scheme is mapped to a lower priority AC queue, and an acknowledgement / negative acknowledgement feedback scheme is mapped to the separate AC transmit queue having a higher priority than the one or more other AC queues.

Images