End-to-end quality of service via customer premises equipment

Abstract

Methods, systems, and devices for wireless communication are described. For example, the described techniques provide for a first device (e.g., a cellular modem or user equipment (UE)) to map a quality of service flow for a first radio access technology (e.g., cellular) to a service category for a second RAT (e.g., Wi-Fi). The first device may communicate mapping information indicative of the mapping to a second network device (e.g., a router). The first device and the second device may communicate various packets via the quality of service flows and the service categories.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 960,454, filed by HUANG et al. on October 5, 2022, entitled "END-TO-END QUALITY OF SERVICE VIA A CUSTOMER PREMISES EQUIPMENT," which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including end-to-end quality of service via customer premises equipment. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, 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] Some wireless communication systems may support local networks, such as Wi-Fi networks. For example, a cellular device such as a UE may communicate with a network entity using a first radio access technology (RAT) and support communication with other devices via a second RAT such as Wi-Fi. In some examples, communication via the first RAT and / or the second RAT may be associated with quality of service (QoS) requirements. Summary of the invention

[0006] The described techniques relate to methods, systems, devices, and apparatuses that support improved end-to-end quality of service (QoS) via customer premises equipment (CPE). For example, the described techniques provide for a first device (e.g., a cellular modem or user equipment (UE)) to map QoS flows of a first radio access technology (e.g., cellular) to service classes of a second radio access technology (e.g., Wi-Fi). The first device may communicate mapping information indicating the mapping to a second network device (e.g., a router). The first device and the second device may communicate various packets via the QoS flows and the service classes.

[0007] A method for wireless communication at a first network device is described. The method may include: sending mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows; and communicating packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based on the mapping information.

[0008] An apparatus for wireless communication at a first network device 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: send mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows; and communicate packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based on the mapping information.

[0009] Another apparatus for wireless communication at a first network device is described. The apparatus may include: means for sending to a second network device mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows; and means for communicating packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based on the mapping information.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a first network device is described. The code may include instructions executable by a processor to: send mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows; and communicate packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based on the mapping information.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the set of multiple service categories for the second RAT from the second network device, and wherein each QoS flow may be mapped to the one or more service categories based on receiving the indication of the set of multiple service categories.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling via the first RAT indicating the set of QoS parameter values ​​for each QoS flow in the set of multiple QoS flows.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling includes a set of Internet Protocol addresses to be communicated via a QoS flow in the set of multiple QoS flows, and the QoS flow can be mapped to at least one service class in the set of multiple service classes based on the set of Internet Protocol addresses.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of Internet Protocol addresses may be received from a policy control function associated with the first RAT.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information includes an indication of the set of Internet Protocol addresses to be communicated via the QoS flow.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of the set of multiple service categories for the second RAT from the second network device; sending uplink control signaling requesting the set of multiple QoS flows based on receiving the indication of the set of multiple service categories and using a default QoS flow; and receiving control signaling indicating the set of QoS parameter values ​​for each QoS flow in the set of multiple QoS flows via the first RAT based on sending the uplink control signaling.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the uplink control signaling may be sent to a policy control function associated with the first RAT.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating the packet may include operations, features, components, or instructions for: receiving the packet including a service identifier from the second network device; and sending the packet via the first QoS flow based on the service identifier that can be mapped to the first QoS flow.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for removing the traffic identifier from the packet before sending the packet via the first QoS flow based on the traffic identifier corresponding to the Internet Protocol-based QoS flow.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the packet including the traffic identifier may be sent via the first QoS flow based on the first QoS flow being an Ethernet-based QoS flow.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the traffic identifier may be a VLAN tag.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information may be sent via a DHCP message, a serial communication, or a Hypertext Transfer Protocol (HTTP) message.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information may be sent by a DHCP server at the first network device and via a DHCP offer message that may be sent to a DHCP client at the second network device, and the DHCP offer message includes the mapping information and indicates an identifier configured to cause the DHCP client to avoid discarding the DHCP offer message.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: avoiding mapping the Ethernet port of the second network device to the QoS flow.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second network device and the first network device may be included in customer premises equipment (CPE).

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of QoS parameter values ​​for each QoS flow includes a delay budget value, a packet error rate value, a priority value, a bit rate value, a data burst value, a reflective QoS attribute value, a periodicity value, or a combination thereof, and each service class in the set of multiple service classes can be associated with a delay limit value, a packet loss ratio value, a priority value, a minimum throughput value, a maximum throughput value, a burst size value, a priority value, a service interval value, or a combination thereof.

[0027] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for mapping each QoS flow in the set of multiple QoS flows to one or more service categories in the set of multiple service categories based on a QoS identifier of the set of multiple QoS flows and a mapping table including the set of multiple service categories, description information associated with each QoS flow, and packet filter information.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the mapping information may include operations, features, components, or instructions for sending indications of one or more QoS identifiers of service classes in the set that can be mapped to multiple service classes, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the mapping information may include operations, features, components, or instructions for sending descriptive information indicating a maximum flow bit rate for each QoS flow, a guaranteed flow bit rate for each QoS flow, an average window for each QoS flow, a QoS identifier for each QoS flow, or a combination thereof.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first RAT may be a cellular communication technology and the second RAT may be Wi-Fi.

[0031] A method for wireless communication at a first network device is described. The method may include: receiving mapping information from a second network device indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT supported by the first network device; using a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first RAT and a second network address used by the first network device; and communicating the packet between devices associated with the first network device using a first service class in the set of multiple service classes and a first QoS flow in the set of multiple QoS flows based on the conversion of the header.

[0032] An apparatus for wireless communication at a first network device 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 mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT supported by the first network device from a second network device; use a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first RAT and a second network address used by the first network device; and communicate the packet between devices associated with the first network device using a first service class in the set of multiple service classes and a first QoS flow in the set of multiple QoS flows based on the conversion of the header.

[0033] Another apparatus for wireless communication at a first network device is described. The apparatus may include: a component for receiving mapping information from a second network device indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT supported by the first network device; a component for converting a header of a packet between a first network address of the first RAT and a second network address used by the first network device using a conversion rule included in the mapping information; and a component for communicating the packet between devices associated with the first network device using a first service class in the set of multiple service classes and a first QoS flow in the set of multiple QoS flows based on the conversion of the header.

[0034] A non-transitory computer-readable medium storing code for wireless communication at a first network device is described. The code may include instructions that can be executed by a processor to: receive mapping information from a second network device indicating a mapping of each QoS flow in a set of multiple QoS flows of a first RAT to one or more service classes in a set of multiple service classes of a second RAT supported by the first network device; use a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first RAT and a second network address used by the first network device; and communicate the packet between devices associated with the first network device using a first service class in the set of multiple service classes and a first QoS flow in the set of multiple QoS flows based on the conversion of the header.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information includes an indication of a set of Internet Protocol addresses to be communicated to the QoS flow, and the header can be transformed based on the set of Internet Protocol addresses.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the set of multiple service categories to the second network device, and wherein the mapping information may be received based on sending the indication of the set of multiple service categories.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second packet to the second network device that includes a service identifier that can be mapped to a default QoS flow associated with the first RAT, and wherein the mapping information can be received based on sending the second packet.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the second packet from the device via a default service class, and wherein the second packet may be sent to the second network device based on receiving the second packet from the device.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating the packet may include operations, features, components, or instructions for: receiving the packet from the device via the first service category; inserting a service identifier corresponding to the first service category into a header of the packet based on the mapping information; and sending the packet including the service identifier to the second network device.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the traffic identifier may be a VLAN tag.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, converting the header of the packet may include operations, features, components, or instructions for: receiving the packet from the second network device, the packet including the first network address; replacing the first network address with the second network address that can be mapped to the first network address via the mapping information; and wherein the packet can be sent to the device via the first service category.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, converting the header of the packet may include operations, features, components, or instructions for: receiving the packet from the device, the packet including the second network address; replacing the second network address with the first network address that can be mapped to the second network address via the mapping information; and wherein the packet can be sent to the second network device.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for scheduling the communication of a set of multiple packets including the packet based on a corresponding service class associated with each packet in the set of multiple packets, and wherein the packets may be communicated based on the scheduling.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information may be received via a Dynamic Host Configuration Protocol (DHCP) message, or serial communication, or HTTP.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information can be received by a DHCP client at the first network device and via a DHCP offer message that can be sent by a DHCP server at the second network device, and the DHCP offer message includes the mapping information and indicates an identifier configured to cause the DHCP client to avoid discarding the DHCP offer message.

[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the mapping information including an indication of one or more QoS identifiers for service classes in the set that can be mapped to multiple service classes, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the mapping information includes: receiving descriptive information indicating the maximum flow bit rate of each QoS flow, the guaranteed flow bit rate of each QoS flow, the average window of each QoS flow, the QoS identifier of each QoS flow, or a combination thereof.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the mapping information does not include information associated with an Ethernet port of the first network device.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network device and the second network device may be included in customer premises equipment (CPE).

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first RAT may be a cellular communication technology and the second RAT may be Wi-Fi. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 An example of a wireless communication system supporting end-to-end quality of service (QoS) via customer premises equipment (CPE) in accordance with one or more aspects of the present disclosure is illustrated.

[0052] Figure 2 An example of a wireless communication system supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0053] Figure 3 An example of a wireless communication architecture supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0054] Figure 4 An example of a CPE architecture that supports end-to-end QoS via the CPE in accordance with one or more aspects of the present disclosure is illustrated.

[0055] Figure 5A and Figure 5B An example of a process flow for supporting end-to-end QoS via CPE in accordance with one or more aspects of the present disclosure is illustrated.

[0056] Fig. 6A , Figure 6B and Figure 6C An example of a process flow for supporting end-to-end QoS via CPE in accordance with one or more aspects of the present disclosure is illustrated.

[0057] Figure 7 and Figure 8 A block diagram of a device supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0058] Fig. 9 A block diagram of a communication manager that supports end-to-end QoS via CPE is illustrated in accordance with one or more aspects of the present disclosure.

[0059] Fig.10 A diagram illustrating a system including a device supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0060] Fig.11 and Fig.12 A block diagram of a device supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0061] Fig.13 A block diagram of a communication manager that supports end-to-end QoS via CPE is illustrated in accordance with one or more aspects of the present disclosure.

[0062] Fig.14 A diagram illustrating a system including a device supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated.

[0063] Figures 15 to 17 A flow chart illustrating a method of supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0064] Some wireless communication systems may support local networks, such as Wi-Fi networks. For example, a cellular device such as a UE may communicate with a network entity using a first radio access technology (RAT) and support communication with other devices via a second RAT such as Wi-Fi. In some examples, communication via the first RAT and / or the second RAT may be associated with quality of service (QoS) requirements or service classes associated with different QoS. For example, a Wi-Fi network may support Voice over Internet Protocol (VOIP), high definition (HD) video, gaming, etc., each of which may be associated with different QoS requirements and parameters. Additionally, communication via a cellular network (such as a network implementing 5G RAT communication) may be associated with different QoS flows, wherein each QoS flow may be associated with a different value for a set of parameters (such as 5G delay budget, packet error rate, priority, etc.).

[0065] In some examples, 5G customer premises equipment (CPE) can support Wi-Fi access via 5G wireless backhaul, such that the CPE can provide connectivity via 5G communications (e.g., a first RAT) and the CPE can provide connectivity via Wi-Fi communications protocols. The techniques described herein support an end-to-end (e.g., core network via Wi-Fi to user equipment) QoS architecture and QoS coordination via both Wi-Fi and 5G protocols to support consistent QoS services. QoS requirements can be driven by the core 5G network or by the Wi-Fi network. Depending on whether QoS is driven by the core network or by the WIFI network, various signaling techniques are described herein. QoS flows can be used to signal a cellular modem (e.g., user equipment (UE)) using various QoS parameters such as delay budget, error rate, and priority.

[0066] The cellular modem may map 5G QoS parameters to Wi-Fi service classes based on service class parameters (e.g., delay bounds, priorities) and 5G QoS parameters. Depending on the capabilities of the modem and router and whether the modem and router are configured within the same CPE (e.g., the same box), various types of signaling may be used to communicate mapping information to the Wi-Fi router, which may include service class to QoS mapping, IP addresses associated with QoS flows, and other information. The Wi-Fi router is configured to support mapping of local IPs to public IPs based on the received mapping information, traffic indicator tags (e.g., using virtual local area network (VLAN) tags), and packet scheduling to support routing packets in uplinks and downlinks to support QoS flows and Wi-Fi service types.

[0067] For example, a first network device such as a cellular modem may send mapping information to a second network device such as a router, the mapping information indicating a mapping of each of a plurality of QoS flows of a first RAT (e.g., cellular) to one or more service categories of a plurality of service categories of a second RAT (e.g., Wi-Fi). The mapping may be based on a set of QoS parameter values ​​for the plurality of QoS flows. The first network device and the second network device may communicate packets between the first QoS flow and the second QoS flow based on the mapping. By supporting mapping of QoS flows to service categories, the technology may support improved communication efficiency and reliability at a user device. More specifically, because QoS flows and service categories may be associated with minimum reliability and throughput parameter values, and such parameter values ​​may be used to map QoS flows to service types, communication reliability and throughput targets may be maintained for end-to-end (e.g., user device to application server) communications.

[0068] Additionally, QoS flow establishment and mapping can be initiated by a communication facility that can communicate via a first RAT, or by a user device or a second network device that can communicate via a second RAT. For example, the first network device can receive control signaling via the first RAT, and the control signaling can indicate a set of QoS parameter values ​​for each QoS flow in a plurality of QoS flows. The first network device can then dynamically map the QoS flow to one or more service categories of the second RAT. Additionally or alternatively, the first network device can send a request for a change or addition of a QoS flow based on a communication received from the second network device (e.g., via uplink control signaling). More specifically, if the first network device receives an uplink communication for a default QoS flow, the use of the default QoS flow can trigger the dynamic addition of a new QoS flow to support communication. Therefore, QoS flows can be dynamically added based on server (e.g., application server) and / or device needs, which can result in improved communication flexibility, reliability, and throughput. These and other technologies are further described in detail for the accompanying drawings.

[0069] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further described with respect to a wireless communication system, wireless communication architecture diagrams, and process flow diagrams. Aspects of the present disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow diagrams related to end-to-end QoS via CPE.

[0070] Figure 1An example of a wireless communication system 100 supporting end-to-end QoS via CPE 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.

[0071] 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 devices 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, etc. In some examples, the network entities 105 and the UEs 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 UEs 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 UEs 115 may support signal communication according to one or more radio access technologies (RATs).

[0072] 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 both stationary and mobile at different times. The UEs 115 may be devices in different form factors 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.

[0073] 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, 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. 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, 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, and the third node may be a network entity 105. In yet 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, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as a network node. 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 the second node.

[0074] 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 via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the 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 .

[0075] 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).

[0076] 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)).

[0077] The functional split between CU 160, DU 165, and RU 170 is flexible and can 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 can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can 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 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an 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 these communication links.

[0078] 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., a 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.

[0079] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support end-to-end QoS via CPE as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0080] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld 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. 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.

[0081] 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.

[0082] The UE 115 and the network entity 105 can use resources associated with one or more carriers to wirelessly communicate with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined to support 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 communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both frequency division duplex (FDD) component carriers 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 part (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 part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0083] The signal waveform transmitted via the carrier wave may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of a symbol period (e.g., the duration of a modulation symbol) and a 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., within 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.

[0084] 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).

[0085] 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, a 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.

[0086] 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 transmit time interval (TTI). In some examples, the TTI duration (e.g., the amount 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)).

[0087] Physical channels may be multiplexed using carriers for communication according to various techniques. For example, physical control channels and physical data channels may be multiplexed via downlink carriers for signaling using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. 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 group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search spaces, 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 the control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the 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 a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0088] 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 respective coverage areas 110 using the same or different radio access technologies.

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

[0090] 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 by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group may be outside 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.

[0091] 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 transmitted through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for 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.

[0092] 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). Typically, 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) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0093] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt 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 entities 105 and UEs 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in combination with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0094] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels that may 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 geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0095] 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 technology may be referred to as spatial multiplexing. Multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, 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), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0096] 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).

[0097] 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 handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

[0098] As described herein, the wireless communication system 100 may support a CPE 185 that may communicate with the wireless communication system 100 via a UE 115 that communicates with a network entity 105 via a first RAT (e.g., cellular communication) and may also communicate with other devices such as a STA 195 via a second RAT (e.g., Wi-Fi) to support local network communications. For example, the CPE 185 may implement a UE 115 and an AP 190 as a router, the UE may communicate with the network and act as a cellular modem, and the AP may be used to support a wireless local area network (WLAN) (also referred to as a Wi-Fi network). The WLAN may include an AP 190 and a plurality of associated stations (STAs), such as a STA 195, which may represent devices such as mobile stations, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptop computers, display devices (e.g., TVs, computer monitors, etc.), printers, etc. The STA 195 and the AP 190 may communicate according to WLAN radio and baseband protocols for physical and MAC layers from IEEE 802.11 and versions including, but not limited to, 802.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11ax, etc. In other specific implementations, peer-to-peer connections or ad hoc networks may be implemented within the WLAN 100.

[0099] The wireless communication system 100 may support various QoS flows for a first RAT (e.g., cellular communication), each of which may be associated with a different set of parameter values ​​for a set of QoS parameters. The Wi-Fi network of the AP 190 may also support different service types. As described herein, in order to support end-to-end (e.g., core network 130 to STA 195) QoS communication, a first network device (e.g., a cellular modem or a UE 115 of a CPE 185) may receive control signaling indicating a set of QoS parameter values ​​for each of a plurality of QoS flows. The cellular modem may map each QoS flow to a service class in a plurality of QoS classes of a second RAT (e.g., Wi-Fi). The mapping may be based on parameters associated with the QoS flow parameters of the service class. The cellular modem may communicate mapping information indicating the mapping of each QoS flow to the service class, and then communicate packets between the QoS flows and the service class based on the mapping.

[0100] A second network device, such as a router (e.g., AP 190), can receive the mapping information and use the information to communicate packets between the cellular modem and the device (e.g., STA 195) based on the service type. The second network device can convert network addresses (e.g., Internet Protocol (IP) addresses) between public IP addresses and private IP addresses based on the mapping information, and can also add virtual local area network (VLAN) tags (e.g., network identifiers) to support routing of packets to the correct service type and QoS flow. Additionally, the router can implement a scheduler to schedule packets based on the service type. Thus, according to these techniques, the cellular modem, router, and network can work in conjunction to support end-to-end QoS communications.

[0101] Figure 2 An example of a wireless communication system 200 that supports end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a, a UE 115-a, an AP 205, and a STA 210, which may be as described in reference to Figure 1 1 , and the corresponding examples of the network entity 105, UE 115, AP 190, and STA 195 are described. In some examples, the network entity 105-a and the UE 115-a can communicate via link 220 according to RAT 215-a (e.g., 5G), and the AP 205 and the STA 210 can communicate via link 225 according to RAT 215-b (e.g., Wi-Fi). In addition, the wireless communication system 200 may include a CPE 230 that can support mapping of QoS flows (e.g., QoS flows 235) to service categories (e.g., service category 240) and communication based on the mapping between RAT 215-a and RAT 215-b, as described in reference to FIG. Figure 1 Described.

[0102] In some communication systems, UE 115-a can support communication with network entity 105-a and AP 205. That is, UE 115-a can provide connection to RAT 215-a (e.g., cellular communication with network entity 105-a) and can provide connection to RAT 215-b (e.g., Wi-Fi protocol). Such connection can be supported by CPE 230, which can include a modem, a router, or both to facilitate end-to-end QoS coordination between RAT 215-a and RAT 215-b. In some examples, end-to-end coordination can be driven by RAT 215-a (e.g., can be 3GGP driven or core network driven) or can be driven by RAT 215-b (e.g., can be Wi-Fi network driven).

[0103] To support such coordination, the CPE 230 may be operable to map the service classes 240 to the QoS flows 235. The CPE 230 may determine such mapping based on various parameters associated with each of the QoS flows 235 and the service classes. Thus, the CPE 230 may map the QoS flow 235 parameters of the RAT 215-a to a set of service class 240 parameters associated with the RAT 215-b. It should be noted that any amount of mapping may be performed by the CPE 230 and is not limited to the amount illustrated by the wireless communication system 200.

[0104] In some examples, the CPE 230 may operate according to various architectures. For example, the CPE 230 may operate according to an Internet Protocol (IP) Protocol Data Unit (PDU) session-based CPE architecture or an Ethernet PDU session-based architecture. In some cases, such as when the CPE operates according to an IP PDU session-based architecture, the CPE 230 may further use a call flow for end-to-end QoS establishment based on static PCC rules, a call flow for end-to-end QoS establishment based on dynamic PCC rules, or both. In some other cases, such as when the CPE operates according to an Ethernet PDU session-based architecture, the CPE 230 may further use a call flow for end-to-end QoS establishment based on static PCC rules, a call flow for end-to-end QoS establishment based on dynamic PCC rules, or both. Additionally or alternatively, the CPE 230 (e.g., the AP 205) may use a VLAN mapping configuration to route packets according to various mapped QoS and service types.

[0105] As shown below, Table 1 may include various architectural elements end-to-end QoS.

[0106]

[0107]

[0108] Table 1

[0109] The architectural elements of Table 1 may correspond to respective definitions for RAT 215-a and RAT 215-b. For example, according to Table 1, QoS signaling may be initiated by an application server via a PCF of RAT 215-a, which may correspond to QoS signaling initiated by a network via a service type manager of RAT 215-b. In some examples, RAT 215-a and RAT 215-b may have different amounts of mapping operations for architectural elements, such as packet filters (e.g., there is no corresponding uplink packet filter for RAT 215-b).

[0110] In some examples, the QoS parameters of RAT 215-a may be mapped to parameters in QoS parameter RAT 215-b. In some examples, CPE 230 (e.g., UE 115-a) maps parameters or uses a parameter mapping table to perform mapping of QoS flows 235 to service categories 240. An example parameter mapping is shown in Table 2 below:

[0111] RAT 215-a (e.g., cellular) QoS parameters RAT 215-b (e.g., Wi-Fi) QoS parameters Cellular QoS Identifier (5QI) Delay Budget Delay Bound 5QI Packet Error Rate (PER) Packet Loss Ratio 5QI Priorities Transmit Opportunity (TXOP) Scheduling Priority Guaranteed Bit Rate (GBR) Minimum and maximum throughput Maximum Data Burst Volume (MDBV) Burst Size Allocation and Reservation Policy (ARP) Admission Control Priority Periodicity Service Area

[0112] Table 2

[0113] In some cases, a non-access stratum (NAS) PDU session modification command may include a mapping of one or more QoS parameters in the QoS parameters. In one example, the NAS PDU session modification command may include a 5QI delay budget mapping, a 5QIPER mapping, a 5QI priority mapping, a GBR mapping, or any combination thereof. Additionally, the UE 115-a may identify the mapping included in the NAS PDU session modification command based on the network configuration. For example, when a standardized 5QI is used by the network, the mapping included in the NAS PDU session modification command may be able to be identified by the UE 115-a (e.g., it may be indirectly visible to it). Alternatively, the UE 115-a may be signaled to the network entity 105-a based on the mapping to identify the mapping. In addition, when the MDBV mapping is included in the 5QI configuration, the UE 115-a may identify the MDBV mapping. In some examples, the ARP mapping and the periodicity mapping may not be able to be identified by the UE 115-a (e.g., it may not be visible to it). However, in some examples, ARP and periodicity may be available.

[0114] Example service types that may be supported by RAT 215-a and RAT 215-b that may be supported via QoS flow 235 to service class 240 mapping are shown in Table 3 below:

[0115] RAT 215-b Service Category RAT 215-a 5QI Augmented Reality (AR) / Virtual Reality (VR) Services Game Services Real-time gaming, vehicle-to-everything (V2X) Interactive Video Dialogue Video Interactive Audio Conversational Voice Streaming video or video on demand (VOD) services Non-dialogue video Voice over Internet Protocol (VOIP) services Conversational Voice Time-sensitive control services IP Multimedia Subsystem (IMS) signaling Large file transfer or data movement General GBR or non-GBR

[0116] Table 3

[0117] In some cases, the illustrated service mappings included in Table 3 may indicate various applications associated with RAT 215-b and RAT 215-b and service classes (e.g., relative QoS priority) mappings for the applications. For example, a service class associated with an AR or VR service in RAT 215-b (e.g., Wi-Fi) may not have a corresponding mapping to RAT 215-a, which may indicate that no service of RAT 215-a corresponds to a relatively high expected QoS (e.g., service class) for the AR or VR service. As another example, a large file transfer or data movement in RAT 215-a may correspond to a general GBR or non-GBR of RAT 215-b, which may indicate a service associated with a relatively low expected QoS. In some cases, CPE 315 may translate a Wi-Fi IP tuple into a cellular side port number (e.g., associated with UE 115-a), which may be an example of a network address translation (NAT) function. Such mapping and conversion may support end-to-end QoS between applications of RAT 215 - a and RAT 215 - b without dynamically defining service classes for each application.

[0118] Table 4 below includes example CPE 230 QoS flow signaling options between RAT 215-b and RAT 215-a for supporting end-to-end QoS:

[0119]

[0120]

[0121] Table 4

[0122] Figure 3 An example of a wireless communication architecture 300 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The wireless communication architecture 300 can implement one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, the wireless communication architecture can support end-to-end QoS mapping between a first RAT (e.g., cellular communication, 5G) and a second RAT (e.g., Wi-Fi protocol), as described in reference to Figure 2 Additionally, the wireless communication architecture may include a CPE 315, which may be as described in reference Figure 2 An example of CPE 230 is described.

[0123] In some examples, the wireless communication architecture 300 can implement static QoS configuration from the PCF 345. That is, the CPE 315 can request QoS in the first RAT based on static rules (e.g., independent of the application server 350). In one example, the rules can be configured in the first RAT and the QoS establishment can be triggered from the first RAT. Alternatively, the rules can be configured in the fixed wireless access (FWA) UE 115-b or AP 305, and the QoS establishment can be triggered from the first RAT using an existing PDU session modification procedure. In some cases, the PDU session modification procedure can be the same as the QoS signaling procedure initiated by the UE 115-b (as shown in Table 1).

[0124] Static rules (e.g., policies) for QoS can be pre-configured by PCF 345 for various types of application services (e.g., identified by IP address range, port number, or both). PCF 345 can communicate within the first RAT to install one or more packet filters and establish a QoS flow for the first RAT. That is, PCF 345 can provide an uplink packet filter 320 to UE 115-b, a downlink packet filter 335 to UPF 330, or both, which can support aggregation of multiple QoS flows from the second RAT to be mapped to the common QoS flow of the first RAT. For example, static rules (e.g., conversion rules) can limit the amount of QoS flows of the first RAT so that the packet filters of the statically deployed QoS flows can accommodate multiple dynamically established QoS flows of the second RAT. In some examples, the packet filter can be specified to provide a wide coverage of the common portion of the potential QoS flows of the second RAT to be mapped to the QoS flow of the first RAT. In one example, application traffic from a service (e.g., a streaming provider) of a second RAT may share the same set of server-side IP addresses, the same range of port numbers, or both, and such a set may be used as a packet filter for a QoS flow (e.g., a QoS flow carrying application traffic) of a first RAT. Additionally or alternatively, a first application (e.g., a file transfer protocol (FPT) traffic session) of a second RAT and a second application (e.g., a VOIP traffic session) of a second RAT may be associated with different port number ranges on the server side. Thus, the first application and the second application may be split into different QoS flows of the first RAT using the service-side port number ranges, and may be split into QoS flows of the second RAT corresponding to different service classes.

[0125] In some examples, such as when UE 115-b has installed uplink packet filter 320, UE 115-b can perform a NAT function to map the tuple of the second RAT to the transmission port of the first RAT. Additionally, UE 115-b can map the uplink QoS flow of the second RAT to the QoS flow of the first RAT, and AP 305 can map the downlink QoS flow of the first RAT to the QoS flow of the second RAT. In some examples, STA 310 can signal a downlink classification rule or an uplink classification rule (e.g., a conversion rule) to AP 305, which can support self-aware Wi-Fi configuration of the QoS flow of the second RAT.

[0126] In some cases, each packet mapping between the QoS flow of the first RAT and the QoS flow of the second RAT can be determined via a NAT function and a static QoS flow packet filter. The mapping can support a many-to-one configuration for converting one or more service categories of the second RAT to one or more QoS flows of the first RAT. For example, delay bounds, service intervals, and packet loss rates (e.g., corresponding to the service category of the second RAT) can be mapped to a packet delay budget (PDB), a semi-persistent scheduling (SPS) period, and a maximum packet loss rate associated with the QoS flow. In some cases, the mapping can prioritize matching the service category with the following items associated with the 5QI service category: PDB, then SPS period, and then packet loss rate. That is, CPE 315 can map aggregate data from the second RAT to similar parameters of the first RAT so as to combine the aggregate data in a single service category of the first RAT. In some cases, the TID of the second RAT can be determined based on the QoS of the second RAT.

[0127] As shown below, Table 5 may include various functions for implementing end-to-end QoS mapping based on static PCF.

[0128]

[0129] Table 5

[0130] In some other examples, the wireless communication architecture 300 may be an example of a dynamic QoS configuration initiated by an application server 350. For example, the application server 350 may identify end-to-end application traffic (e.g., application traffic communicated by the STA 310 and the application server 350) and may determine a QoS flow for the application traffic. For example, for uplink packets, the application traffic performed by the STA 310 may use a default QoS flow, and the use of the default QoS flow may signal the application server 350 to dynamically cause the generation of one or more QoS flows. The application server 350 may identify an IP address, a port number, or both associated with the application traffic, and may transmit a request to the PCF 345 for applying QoS to the application traffic (using techniques similar to those in the static configuration). In such examples, the QoS mapping may be one-to-one, such that a tuple of the second RAT (e.g., an IP5 tuple) corresponds to a specific tuple of the first RAT (e.g., a 5QI tuple). That is, the QoS mapping may be dynamically generated by the UE 115-b (e.g., according to the uplink packet filter 320) to be applied to the identified application traffic. UE 115-b may then map the QoS flow of the first RAT to the QoS flow (service class) of the second RAT, and may send a signal indicating the application service (e.g., indicating the mapping information) to AP 305. After receiving the signal, AP 305 may perform QoS scheduling for the second RAT (e.g., Wi-Fi downlink and uplink).

[0131] As shown below, Table 6 may include various functions for implementing dynamic application server initiated end-to-end QoS mapping.

[0132]

[0133] Table 6

[0134] In another example, the wireless communication architecture 300 can be an example of dynamic QoS configuration initiated by UE 115-b, AP 305, STA 310, or any combination thereof. That is, the QoS configuration can be triggered by UE 115-b sending a request for end-to-end application services to the PCF to apply QoS rules (e.g., conversion rules). In some cases, AP 305 can receive an indication of the end-to-end application from STA 310 and can forward the indication to UE 115-b to trigger the request to the PCF. Additionally, AP 305 can perform mapping between QoS flows of the second RAT (e.g., WLAN service category) to QoS flows of the first RAT (e.g., 5QI) and can signal the mapping to UE 115-b.

[0135] As shown below, Table 7 may include various functions for implementing dynamic UE or AP based end-to-end QoS mapping.

[0136]

[0137]

[0138] Table 7

[0139] Figure 4 An example of a CPE architecture 400 that supports end-to-end QoS via a CPE according to one or more aspects of the present disclosure is illustrated. The CPE architecture 400 may be implemented by one or more aspects of the wireless communication system 200 and the wireless communication architecture 300. For example, the CPE architecture 400 may include a fixed wireless access (FWA) CPE 405, which may be as described in detail in the respective references to Figure 2 and Figure 3 The CPE 315 and the example of CPE 315 described in the embodiment of the present invention are shown in FIG. 4 . Additionally, the CPE architecture 400 may include a UPF 330, which may be as described in reference Figure 3 An example of UPF 330 is described. In some cases, CPE architecture 400 may be an example of an architecture based on IP PDU sessions. In some other cases, CPE architecture 400 may be an example of an architecture based on Ethernet PDU sessions.

[0140] In some cases, the FWA CPE 405 may include a Wi-Fi router 410 (e.g., an AP or a network device) and a cellular modem 415 (e.g., a UE 115 or a network device), which may facilitate mapping of QoS flows between a first RAT (e.g., 5G NR, a different cellular protocol) associated with the cellular modem 415 and a second RAT (e.g., a Wi-Fi protocol) associated with the Wi-Fi router 410. Additionally, the Wi-Fi router 410 and the cellular modem 415 may include a mapping communicator 420 (e.g., a Dynamic Host Configuration Protocol (DHCP) client, a Hypertext Transfer Protocol (HTTP) client, a serial port, etc.) and a mapping communicator 425 (e.g., a DHCP server, an HTTP server, a serial port, etc.), respectively, which may transmit mapping information between the Wi-Fi router 410 and the cellular modem 415. The Wi-Fi router 410 may include a NAT 430 (e.g., corresponding to a function for supporting establishment of a network), which may also include an AP 435. In some cases, Wi-Fi router 410 may facilitate scheduling of application traffic within service class 440 of the second RAT and the second category via scheduler 490. That is, one or more STAs 480 (e.g., STA 480-a, STA 480-b, STA 480-c, and STA 480-d) may communicate (e.g., receive or transmit) data (e.g., application data) via the second RAT, and the data may be communicated by scheduler 490 via one or more service classes (e.g., according to parameters associated with the service classes). For example, communications by STA 480-a may be classified into each of service class 440-a, service class 440-b, and service class 440-c (e.g., transmitting application data with various QoS expectations), communications by STA 480-b may be classified into service class 440-b, and communications by STA 480-c may be classified into service class 440-c. In some cases, STA 480-d may communicate within the second RAT via an Ethernet connection and may therefore not be classified into a service class or QoS flow. In addition, NAT 430 may additionally support one or more translations for QoS rules. For example, NAT 430 may provide translation from a public IP or port number of a cellular network to a private IP or port number of a Wi-Fi network based on a translation rule. A mapping of port numbers (e.g., an IP packet filter) may be an example of mapping information communicated between modem 415 and router 410 and may be used to configure a translation rule.

[0141] In some examples, the AP 435 can manage VLAN tags associated with application data via the VLAN handler 445-a. The operation of the VLAN handler 445-a can be associated with the communication direction of the application data. That is, the VLAN handler 445-a can insert a VLAN tag for uplink application data (e.g., to be mapped to a QoS flow of the first RAT), or can remove a VLAN tag for downlink application data (e.g., to be mapped to a QoS flow of the second RAT). In some cases, the VLAN handler 445-a can manage VLAN tags for uplink Ethernet frames (e.g., one STA 480 associated with one service class and one IP PDU session). Additionally or alternatively, the mapping between the STA 480 and the VLAN tag can be pre-configured, or can be dynamically determined (e.g., can be dynamically learned). In some examples, the mapping of the DNN type and the VLAN tag used by the STA is an example of mapping information communicated between the modem 415 and the router 410.

[0142] In order to map QoS parameters between the Wi-Fi router 410 and the cellular modem 415, the mapping communicator 420 may coordinate mapping information with the mapping communicator 425. In the case where the FWA CPE 405 operates according to an IP PDU session-based architecture, the mapping communicator 420 may be an example of a DHCP client. Alternatively, in the case of the FWA CPE 405 operating according to an Ethernet PDU session-based architecture, the mapping communicator 420 may be an example of a DHCP client or an HTTP client.

[0143] The scheduler 490 may use the mapping information for end-to-end QoS processing. For example, the scheduler 490 may use the mapped QoS flow description received from the cellular modem 415 to establish a QoS flow for the second RAT. In some cases, the scheduler 490 may provide for the implementation of translation rules (e.g., a set of IP packet filters provided by the NAT 430) when scheduling communications for one or more STAs 480. Additionally, transmissions from the STA 480 may be associated with multiple service classes, which may be associated with the same PDU session. In another example, transmissions from the STA 480 may be associated with multiple service classes, which may be associated with different PDU sessions. In such an example, the Wi-Fi AP 435 may perform deep packet inspection (DPI) to map different applications of the STA 480 to different PDU sessions (e.g., applications associated with different VLAN tags).

[0144] In some cases, NAT 430 may communicate with cellular modem 415 via Ethernet network interface controller (NIC) 450-a and Ethernet NIC 450-b. For example, VLAN handler 445-a may output one or more QoS flows with corresponding VLAN tags to Ethernet NIC 450-a, which may communicate with Ethernet NIC 450-b (e.g., included in cellular modem 415).

[0145] The cellular modem 415 may facilitate QoS flow mapping via a mapping function. For example, the cellular modem 415 may include an Internet Packet Accelerator (IPA) 455 to support reception of QoS flows with corresponding VLAN tags (e.g., received via the Ethernet NIC 450-b) and the IPA 455 may include a VLAN handler 460. In some examples, the VLAN handler 460 may map the VLAN tag to a PDU session, such as a PDU session 465-a, a PDU session 465-b, or a PDU session 470, via the mapping function and based on mapping information received from the modem 415. In some examples, the mapping function may use a pre-configured mapping table (e.g., mapping information) that provides mapping between QoS flows of the first RAT and the second RAT. In some other cases, the mapping function of the cellular modem 415 may use information of the PDU session 465-a corresponding to an aggregated set of multiple QoS flows of the first RAT to map the PDU session 465-a into a single service class flow. Additionally or alternatively, the mapping function may be implemented as a QoS flow description mapping (e.g., GBR, modified bit rate (MBR), averaging window, 5QI parameters, or any combination thereof) between the first RAT and the second RAT. The flow description of each QoS flow may include examples of parameter values ​​for a set of QoS parameters for the QoS flow. For example, a QoS flow may be associated with a value for each of a set of GBR, MBR, averaging window, and 5QI parameters.

[0146] The mapping function may also correspond to the application of QoS conversion rules (e.g., IP packet filter sets). In some examples, the cellular modem 415 may provide a mapping from VLAN tags to PDU sessions by mapping uplink VLAN tagged Ethernet frames to associated IP PDU sessions. In some cases, the uplink VLAN tag may be removed after the mapping is performed. In some cases, a separate IP PDU session may be implemented for an end device connected to an Ethernet NIC 450-a (e.g., included in a Wi-Fi router 410). In such cases, the mapping function may not map the Ethernet NIC 450-a to a QoS flow. The QoS flow may be mapped to be communicated via PDU sessions 645 or PDU sessions 470 to be communicated via UPF 475.

[0147] In the case where the FWA CPE 405 operates according to an IP PDU session-based architecture, the mapping communicator 425 may be an example of a DHCP server. Alternatively, in the case of the FWA CPE 405 operating according to an Ethernet PDU session-based architecture, the mapping communicator 425 may be an example of a DHCP server or an HTTP server.

[0148] In the case where DHCP is used to send the mapping information, such as when the cellular modem 415 and the Wi-Fi router 410 are in separate physical boxes and connected via an Ethernet cable, the mapping communicator 425 of the cellular modem 415 (e.g., the first network device) can be an example of a DHCP server, and the mapping communicator 420 of the Wi-Fi router 410 can be an example of a DHCP client. The DHCP server can send a DHCP OFFER message to the DHCP client. The DHCP OFFER message can include an identifier, such as a field code (e.g., field code 43), which can cause the DHCP OFFER message to be retained by the DHCP client (e.g., not discarded by it). That is, in some examples, the DHCP OFFER message is sent in response to a DHCP request made by a client. However, the use of a field code known to the DHCP client may cause the client to retain the message. The DHCPOFFER message can include QoS mapping information to provide information to the Wi-Fi router 410.

[0149] In other cases, CPE 405 is an all-in-one box CPE, such that Wi-Fi router 410 and cellular modem 415 are integrated into a single physical device. In such cases, Wi-Fi router 410 and cellular modem 415 can be configured to communicate via a software stack, via serial communication, or a combination thereof.

[0150] As described herein, router 410 may support VLAN mapping for end-to-end QoS establishment. In some cases, VLAN mapping may be performed based on a user's preferred DNN selection or dynamically. In either case, router 410 may be configured with a DNN type (e.g., service type) to VLAN mapping table (with a default DNN). The DNN type to VLAN type mapping table may be an example of mapping information communicated to router 410 via modem 415. For example, router 410 (e.g., Wi-Fi AP) may be configured with a list of supported DNN types, such as augmented reality, virtual reality, Internet, TV. More specifically, router 410 may be configured with a DNN type to VLAN tag mapping table including a default DNN. A user may log in to (or connect to) a Wi-Fi AP via a STA that may be identified by a media access control (MAC) address, select a DNN type from a configured list (e.g., select or open an application associated with the DNN). In response to selecting a DNN type, router 410 may associate a VLAN tag with a MAC address of a STA (e.g., STA 480) according to the DNN type and VLAN tag mapping table. Router 410 (eg, a VLAN handler) may receive the uplink packet and insert a corresponding VLAN tag based on the MAC address and the mapping.

[0151] In some cases, VLAN mapping can be performed dynamically by the router 410. For example, the router 410 (e.g., a Wi-Fi AP) can be configured with a list of supported DNN types, such as augmented reality, virtual reality, Internet, TV. More specifically, the router 410 can be configured with a DNN type to VLAN tag mapping table including a default DNN. The router 410 can receive an uplink packet from the STA 480, and the router (e.g., the VLAN handler 445-a) can associate the default VLAN tag with the STA MAC address according to the DNN type to VLAN tag mapping table. The router 410 can then perform VLAN mapping dynamic learning (SCI), deep packet inspection (DPI), and / or machine learning with flow classification services. Deep packet inspection and mapping can be based on the destination IP address, source / destination port number (e.g., port number range), and / or a domain name via a DNS monitor. The router 410 can determine a new mapping of VLAN tags for STAs, and VLAN tags can be mapped by STA or by an application executed on the STA.

[0152] Figure 5A and Figure 5BAn example of a process flow 500 for supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The process flow 500 includes a STA 505, a router 510, a modem 515 (e.g., a UE), a core network 520, a PCF 525, and a data network name (DNN) 530, which may be as described for Figures 1 to 4 Examples of corresponding devices described. Router 510 can be an example of a Wi-Fi router and can include the functionality of an AP and a NAT. In some examples, router 510 and modem 515 are part of a CPE. Router 510 and modem 515 can be housed in the same box as the CPE, or in a different box but configured to be used as a CPE. Router 510 can be configured to support a set of service classes with corresponding QoS features and VLAN tag mapping (per STA or per STA application). Modem 515 can be configured with information for QoS flow (e.g., 5QI) to service class mapping, such as a 5QI to service class mapping table and a VLN tag to IP PDU session mapping table. PCF 525 can be configured with PCC rule configuration for CPE with a known destination IP / port number (e.g., range) or a UE local port number or a port number range after NAT.

[0153] Process flow 500 illustrates example operations for end-to-end QoS establishment based on static PCC rules. To implement static PCC rules (e.g., conversion rules), an IP address / port number, a reserved UE local port number, or a local port number range (after NAT) is configured at the PCF for packet filter configuration. Additionally, using static PCC rules, both non-GBR and GBR QoS flows can be established before the STA initiates application communication. In the following description of process flow 500, operations between devices may be sent in an order different from the example order shown, or the operations performed may be performed in a different order and at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0154] At 531, the CPE including the modem 515 and the router 510 is activated. In response to the activation, at 532, the modem 515 and the PCF 525 may communicate (e.g., via the core network 520) to perform cellular registration (e.g., 5GS registration). After the cellular registration, at 534, the modem 515 may send a PDU setup request to the core network 520. In response, the PCF 525 may send a PDU setup accept message at 535 and may communicate a set of QoS parameter values ​​for each QoS flow in a plurality of QoS flows at 536. For example, the PCF 525 may communicate a QoS flow description, a QoS rule, an IP packet filter set, etc. to the modem 515. The flow description may indicate whether each QoS flow is a GBR QoS or a non-GBR QoS, and may include information such as a maximum flow bit rate (MFBR) for each QoS flow, a GBR for each QoS flow, an average window for each QoS flow, a QoS identifier (5QI) for each QoS flow, or a combination thereof. The QoS parameter values ​​may be communicated via control signaling.

[0155] At 538, the modem 515 maps each of the plurality of QoS flows to one or more service classes of the plurality of service classes based at least in part on the set of QoS parameter values ​​for the plurality of QoS flows. The mapping may be further based on the QoS identifiers of the plurality of QoS flows and a mapping table including a plurality of service classes, description information associated with each QoS flow, packet filter information, or a combination thereof. In some examples, the QoS mapping may aggregate one or more QoS identifiers (e.g., 5QIs) into service classes based on the mapping table, map flow descriptions to service class flow descriptions, and map QoS flow rules to service class rules. Mapping the flow descriptions may include mapping parameter values ​​of a first RAT (e.g., cellular QoS flow parameter values) to parameter values ​​of a second RAT (e.g., Wi-Fi service class parameter values). The rule mapping may include mapping network addresses (e.g., public IP addresses to private IP addresses). In some examples, the mapping may include aggregation of one or more service classes to QoS flows. The operations at 535 to 538 may be repeated for each PDU session. Information of the mapping table associated with the service class (eg, service class description, parameter values, etc.) may be communicated by the router 510 to the modem 515 .

[0156] At 540, the modem 515 can send mapping information, and the router 510 can receive mapping information, indicating a mapping of each of a plurality of QoS flows of a first radio access technology (e.g., cellular) to one or more of a plurality of service classes of a second radio access technology (e.g., Wi-Fi). The mapping information can be sent via an internal software stack of the CPE, via serial communication, via HTTP, or via DHCP, as described herein. At 542, the router 510 can configure QoS conversion rules based on the provided mapping information.

[0157] At 544 , the router 510 may receive a service class request (eg, Wi-Fi QoS) from the STA 505 , and at 546 , the router 510 may send a response to the STA 505 .

[0158] exist Figure 5B , at 548, STA 505 may send application traffic and router 510 may receive the application traffic. At 550, STA 505 may map the corresponding GBR or non-GBR service class to the application traffic based on the QoS / service class information received from router 510 (e.g., via the QoS response at 546).

[0159] At 552, the router 510 may perform NAT for packets of the application service. For example, the router 510 may receive a packet from the STA 505 (e.g., a device) via a first service class of the router 510. The router 510 may replace a first network address (e.g., a private IP address) of a header of the packet with a second network address (e.g., a public IP address) based on mapping information received from the modem 515. At 554, the router 510 may insert a service identifier (e.g., a VLAN tag) into one or more packets of the application service, into a header of the packet. The inserted VLAN tag may be based on mapping information received from the modem 515, for example, the VLAN tag may correspond to a PDU session for a QoS flow, which is mapped to a service class for communicating packets from the STA 505 to the router 510.

[0160] At 556, the converted packets (e.g., packets with the converted network address and the included network identifier) ​​are communicated to the modem 515 as application signaling. At 558, the modem 515 can map the packets to the PDU session based on the VLAN tag inserted by the router 510. At 560, the modem 515 can map the packets to the QoS flow of the second RAT (e.g., cellular communication) according to the network configuration. In some examples, the mapping of the packets can be based on the VLAN tag and the converted IP address. At 561, the application packets are sent to the DNN 530 via the core network 520 using the corresponding QoS flow.

[0161] At 562, one or more downlink packets are sent to the modem 515 via the core network 520 and the QoS flow. The modem 515 may communicate the packet to the router 510. At 564, the router 510 performs NAT for the one or more downlink packets. For example, the router may replace a first network address (e.g., a public IP address) in a header of the downlink packet with a second network address (e.g., a private IP address). At 566, the router 510 may map the one or more downlink packets to a service class (e.g., GBR or non-GBR) based on the QoS flow for receiving the one or more downlink packets and the mapping information received from the router 510. At 568, the one or more downlink packets are communicated to the STA 505 using the service class. In some examples, the router 510 may schedule one or more downlink packets based on the service class corresponding to each packet.

[0162] Fig. 6A , Figure 6B and Figure 6C An example of a process flow 600 for supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The process flow 600 includes a STA 605, a router 610, a modem 615 (e.g., a UE), a core network 620, a PCF 625, and a DNN 630, which may be as described for Figure 1 5 . Router 610 may be an example of a Wi-Fi router and may include AP and NAT functionality. In some examples, router 610 and modem 615 are part of a CPE. Router 610 and modem 615 may be housed in the same box as the CPE, or in a different box configured to function as a CPE. Router 610 may be configured to support a set of service classes with corresponding QoS features and VLAN tag mapping (per STA or per STA application).

[0163] Process flow 600 illustrates example operations for end-to-end QoS establishment based on dynamic PCC rules. When the CPE is powered on, a default QoS (e.g., non-GBR) QoS is established during PDU session establishment. When STA 605 utilizes application functions (e.g., Figure 3 The PCF 625 may establish other QoS such as GBR QoS after initiating application layer signaling by the application server 350 of the UE (which may trigger the PCF 625 to establish at least one dedicated QoS (e.g., GBR QoS). In this example, there may not be a pre-configured or known destination IP address or port number (e.g., or IP address / port number range), a reserved UE local port number, and / or a local port number range for packet filter configuration at the PCF 625.

[0164] At 632, the STA 605 may send application signaling (e.g., one or more uplink packets) using the default QoS flow. That is, the one or more packets may be sent to the router 610 using the default service class. Based on the fact that the dynamic QoS flow and the service class have not been configured, the router 610 may perform NAT at 634 and insert a network identifier (e.g., a VLAN tag) at 636 to correspond to the default QoS flow on the cellular network side. That is, the router 610 may convert the network address of the packet (e.g., a private IP address to a public IP address) and insert a VLAN tag into the header of the packet so that the packet is sent by the modem 615 via the default QoS flow. At 638, the converted packet is sent to the modem 615 via application signaling.

[0165] At 640, the modem 615 maps the received uplink packet to an IP PDU session using the network identifier (e.g., VLAN tag) inserted by the router 610. The modem 615 may remove the network identifier because the tag is to be sent via the IP PDU session. At 642, the modem 615 may map one or more uplink packets to a default QoS flow, and at 643, the modem 615 may send the uplink packet to the DNN 630 via the default QoS flow via the core network 620. At 644, the DNN 630 may send a downlink packet to the STA 605 via the default QoS flow.

[0166] In response to receiving an uplink packet via the default QoS flow, the application function of the DNN 630 may request a dedicated QoS requirement from the cellular system. The application function may provide the PCF 625 with the STA 605 application source and destination IP address / port number for a dedicated QoS flow (e.g., a dedicated GBR QoS flow). That is, at 646, the DNN 630 may send the QoS requirements to the PCF 625, and the requirements may include an indication of the IP address / port number. The PCF 625 relays these requirements to the core network 620, which may trigger a PDU session modification command to the modem 615 at 648, and the PDU session modification command may include parameters of the QoS flow to be established and mapped to the service class. For example, the PDU session modification command may include a QoS flow description (e.g., GBR, MFBR, averaging window, QoS identifier).

[0167] At 650, the modem 615 may update the QoS mapping. That is, the modem 615 may map the new QoS flow to one or more service classes based on the QoS parameters received via the PDU session modification command. The mapping may include aggregating one or more 5Qi into one or more Wi-Fi service classes, mapping QoS flow descriptions Wi-Fi service class descriptions (e.g., mapping to service class identifiers), and QoS rules to service class mappings. Information of the mapping table associated with the service class (e.g., service class descriptions, parameter values, etc.) may be communicated by the router 610 to the modem 615.

[0168] exist Figure 6B At 654, the modem 615 may indicate to the core network 620 that the PDU session modification is complete, and accordingly, establish a new (e.g., GBR) QoS flow at 656. At 658, the modem 615 may send mapping information to the router 610 indicating each of the plurality of QoS flows of the first radio access technology (e.g., cellular) to one or more service classes of the plurality of service classes of the second radio access technology (e.g., Wi-Fi) supported by the first network device (e.g., router 610).

[0169] At 660, the router 610 may initiate a QoS rule conversion process, and at 662, the router 610 may update the QoS information. At 664, the STA 605 may send a service class request, and the router 610 may send a service class QoS response. In response, at 666, the application service of the STA 605 is mapped to the service class. At 668, the application service (e.g., one or more uplink packets) is sent to the router via the service class. At 670, the router 610 may perform NAT for the application service. That is, the router 610 may convert a network address (e.g., a private IP address to a public IP address conversion) for the packet. At 672, the router 610 may send a service identifier (e.g., a VLAN tag) based on the mapping information and insert it into the packet. More specifically, the router 610 may insert a VLAN tag for a new PDU session corresponding to the new QoS flow.

[0170] exist Figure 6C At 674, the router 610 may send application traffic (e.g., uplink packets) to the modem 615. At 676, the modem 615 may map a traffic identifier (e.g., a VLAN tag) to a PDU session corresponding to a QoS flow. At 678, the modem 615 may map the application traffic to a cellular QoS flow (e.g., a GBR QoS flow). At 680, uplink traffic is communicated via the dynamically established QoS flow, and downlink application traffic may be received via the dynamically established QoS flow. Downlink traffic may be communicated to the router 610 based on the packet filter and mapping information. At 682, the router 610 performs NAT (e.g., translation of an IP address) for the downlink traffic, and at 684, the router 610 may map the application traffic to a corresponding service class (e.g., a Wi-Fi service class). At 686, the application traffic is communicated to the STA 605 via the service class.

[0171] Figure 7 A block diagram 700 of a device 705 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 705 may be an example of aspects of the UE 115 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).

[0172] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0173] 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 associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. 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.

[0174] 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 end-to-end QoS via CPE 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.

[0175] 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 herein. In some examples, a 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).

[0176] 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.

[0177] 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 be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0178] Additionally or alternatively, the communication manager 720 may support wireless communications at a first network device according to examples as disclosed herein. For example, the communication manager 720 may be configured to or otherwise support components for sending mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. The communication manager 720 may be configured to or otherwise support components for communicating packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based at least in part on the mapping information.

[0179] By including or configuring the 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) can support techniques for more efficiently utilizing communication resources. Using the techniques and processes described herein, end-to-end QoS can be established between a first RAT (e.g., a cellular network) and a second RAT (e.g., Wi-Fi) to provide efficient and reliable communications via CPE.

[0180] Figure 8A block diagram 800 of a device 805 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 805 may be an example of aspects of the device 905 or UE 115 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).

[0181] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. The information may be passed to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0182] 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 associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. 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.

[0183] Devices 805 or their various components may be examples of components for performing various aspects of end-to-end QoS via CPE as described herein. For example, communications manager 820 may include mapping information communications component 825, packet communications interface 830, or any combination thereof. Communications manager 820 may be an example of various aspects of communications manager 920 as described herein. In some examples, communications manager 820 or their various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 810, transmitter 815, or both. For example, communications manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated with receiver 810, transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0184] The communication manager 820 may support wireless communication at a first network device according to examples as disclosed herein. The mapping information communication component 825 may be configured to or otherwise support means for sending, to a second network device, mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. The packet communication interface 830 may be configured to or otherwise support means for communicating packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based on the mapping information.

[0185] Fig. 9 A block diagram 900 of a communication manager 920 supporting end-to-end QoS via CPE is illustrated in accordance with one or more aspects of the present disclosure. The communication manager 920 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of end-to-end QoS via CPE as described herein. For example, the communication manager 920 may include a mapping information communication component 925, a packet communication interface 930, a service class interface 935, a control signaling interface 940, a default QoS component 945, a QoS configuration component 950, an uplink QoS component 955, a DHCP server 960, a mapping component 965, a service identifier component 970, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0186] Additionally or alternatively, the communication manager 920 may support wireless communications at a first network device according to examples as disclosed herein. The mapping information communication component 925 may be configured to or otherwise support means for sending, to a second network device, mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. The packet communication interface 930 may be configured to or otherwise support means for communicating packets between a first QoS flow in a set of multiple QoS flows and a first service class in a set of multiple service classes based on the mapping information.

[0187] In some examples, the service class interface 935 can be configured or otherwise support components for receiving an indication of a set of multiple service classes for the second radio access technology from the second network device. In some examples, the service class interface 935 can be configured or otherwise support components for mapping each QoS flow to one or more service classes based on receiving the indication of the set of multiple service classes.

[0188] In some examples, control signaling interface 940 may be configured or otherwise support components for receiving control signaling indicating a set of QoS parameter values ​​for each QoS flow in a set of multiple QoS flows via a first radio access technology.

[0189] In some examples, the control signaling includes a set of Internet Protocol addresses to be communicated via a QoS flow in a set of multiple QoS flows. In some examples, the QoS flow is mapped to at least one service class in a set of multiple service classes based on the set of Internet Protocol addresses.

[0190] In some examples, the set of Internet Protocol addresses is received from a policy control function associated with the first radio access technology.

[0191] In some examples, the mapping information includes an indication of a set of Internet Protocol addresses to be communicated via the QoS flow.

[0192] In some examples, the service class interface 935 can be configured as or otherwise support means for receiving an indication of a set of multiple service classes for a second radio access technology from a second network device. In some examples, the default QoS component 945 can be configured as or otherwise support means for sending uplink control signaling requesting a set of multiple QoS flows based on receiving an indication of a set of multiple service classes and using a default QoS flow. In some examples, the QoS configuration component 950 can be configured as or otherwise support means for receiving control signaling indicating a set of QoS parameter values ​​for each QoS flow in the set of multiple QoS flows via the first radio access technology based on sending uplink control signaling.

[0193] In some examples, the uplink control signaling is sent to a policy control function associated with the first radio access technology.

[0194] In some examples, to support communicating packets, packet communication interface 930 may be configured or otherwise support components for receiving packets including a service identifier from a second network device. In some examples, to support communicating packets, uplink QoS component 955 may be configured or otherwise support components for sending packets via a first QoS flow based on a service identifier mapped to the first QoS flow.

[0195] In some examples, traffic identifier component 970 may be configured or otherwise support means for removing a traffic identifier from a packet prior to sending the packet via a first QoS flow based on a traffic identifier corresponding to an Internet Protocol-based QoS flow.

[0196] In some examples, the packet including the traffic identifier is sent via the first QoS flow based on the first QoS flow being an Ethernet-based QoS flow.

[0197] In some examples, the service identifier is a virtual local area network tag.

[0198] In some examples, the mapping information is sent via Dynamic Host Configuration Protocol messages, serial communications, or HTTP.

[0199] In some examples, the mapping information is sent by a Dynamic Host Configuration Protocol (DHCP) server at the first network device and via a DHCP offer message sent to a DHCP client at the second network device. In some examples, the DHCP offer message includes the mapping information and indicates an identifier configured to cause the DHCP client to avoid discarding the DHCP offer message.

[0200] In some examples, mapping component 965 can be configured to or otherwise support components for avoiding mapping an Ethernet port of the second network device to a QoS flow.

[0201] In some examples, the second network device and the first network device are included in a CPE.

[0202] In some examples, the set of QoS parameter values ​​for each QoS flow includes a delay budget value, a packet error rate value, a priority value, a bit rate value, a data burst value, a reflective QoS attribute value, a periodicity value, or a combination thereof. In some examples, each service class in the set of multiple service classes is associated with a delay bound value, a packet loss ratio value, a priority value, a minimum throughput value, a maximum throughput value, a burst size value, a priority value, a service interval value, or a combination thereof.

[0203] In some examples, mapping component 965 can be configured as or otherwise support components for mapping each QoS flow in a set of multiple QoS flows to one or more service categories in a set of multiple service categories based on a QoS identifier for the set of multiple QoS flows and a mapping table comprising a set of multiple service categories, descriptive information associated with each QoS flow, and packet filter information.

[0204] In some examples, to support sending mapping information, the mapping information communication component 925 can be configured as or otherwise support components for sending indications of one or more QoS identifiers mapped to service classes in a set of multiple service classes, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0205] In some examples, to support sending mapping information, the mapping information communication component 925 can be configured as or otherwise support components for sending descriptive information indicating the maximum flow bit rate for each QoS flow, the guaranteed flow bit rate for each QoS flow, the average window for each QoS flow, the QoS identifier for each QoS flow, or a combination thereof.

[0206] In some examples, the first radio access technology is a cellular communication technology and the second radio access technology is Wi-Fi.

[0207] Fig.10 A diagram of a system 1000 including a device 1005 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 1005 may be an example of a device 905, a device 1005, or a UE 115 as described herein or include components of these devices. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

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

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

[0210] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 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 1035 may not be directly executable by the processor 1040, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, among other things, the memory 1030 may contain a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0211] Processor 1040 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, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks that support end-to-end QoS via CPE). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform the various functions described herein.

[0212] Additionally or alternatively, the communication manager 1020 may support wireless communication at a first network device according to an example as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a component for sending mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. The communication manager 1020 may be configured to or otherwise support a component for communicating packets between a first QoS flow in the set of multiple QoS flows and a first service class in the set of multiple service classes based at least in part on the mapping information.

[0213] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 can support techniques for improved communication reliability. Using the techniques and processes described herein, end-to-end QoS can be established between a first RAT (e.g., a cellular network) and a second RAT (e.g., Wi-Fi) to provide efficient and reliable communication via the CPE, which can enhance the user experience at the STA.

[0214] In some examples, the communication manager 1020 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, 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 can be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 can include instructions that can be executed by the processor 1040 to cause the device 1005 to perform various aspects of end-to-end QoS via CPE as described herein, or the processor 1040 and the memory 1030 can be otherwise configured to perform or support such operations.

[0215] Fig.11 A block diagram 1100 of a device 1105 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 1105 may be an example of aspects of an AP as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0216] The receiver 1110 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0217] The transmitter 1115 may provide means for transmitting signals generated by the other components of the device 1105. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0218] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of end-to-end QoS via CPE as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0219] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0220] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, 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 1120, the receiver 1110, the transmitter 1115, 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.

[0221] In some examples, communication manager 1120 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 can receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0222] Additionally or alternatively, the communication manager 1120 may support wireless communications at a first network device according to an example as disclosed herein. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology supported by the first network device from a second network device. The communication manager 1120 may be configured to or otherwise support a component for converting a header of a packet between a first network address of the first radio access technology and a second network address used by the first network device using a conversion rule included in the mapping information. The communication manager 1120 may be configured to or otherwise support a component for communicating packets between devices associated with the first network device using a first service class in a set of multiple service classes and a first QoS flow in a set of multiple QoS flows based on conversion of the header.

[0223] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor controlling or otherwise coupled to the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof) can support techniques for more efficiently utilizing communication resources. Using the techniques and processes described herein, end-to-end QoS can be established between a first RAT (e.g., a cellular network) and a second RAT (e.g., Wi-Fi) to provide efficient and reliable communications via CPE.

[0224] Fig.12 A block diagram 1200 of a device 1205 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 1205 may be an example of aspects of the device 1305 or AP as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0225] The receiver 1210 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to end-to-end QoS via CPE), user data, control information, or any combination thereof. The information may be passed to other components of the device 1205. The receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0226] The transmitter 1215 may provide means for transmitting signals generated by the other components of the device 1205. The transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0227] Devices 1205 or their various components may be examples of components for performing various aspects of end-to-end QoS via CPE as described herein. For example, communications manager 1220 may include mapping information communications component 1225, packet conversion component 1230, packet communications interface 1235, or any combination thereof. Communications manager 1220 may be an example of various aspects of communications manager 1320 as described herein. In some examples, communications manager 1220 or their various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communications manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0228] The communication manager 1220 may support wireless communication at a first network device according to an example as disclosed herein. The mapping information communication component 1225 may be configured to or otherwise support a component for receiving mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology supported by the first network device from a second network device. The packet conversion component 1230 may be configured to or otherwise support a component for converting a header of a packet between a first network address of a first radio access technology and a second network address used by the first network device using a conversion rule included in the mapping information. The packet communication interface 1235 may be configured to or otherwise support a component for communicating packets between devices associated with the first network device using a first service class in a set of multiple service classes and a first QoS flow in a set of multiple QoS flows based on conversion of the header.

[0229] Fig.13A block diagram 1300 of a communication manager 1320 supporting end-to-end QoS via CPE is illustrated in accordance with one or more aspects of the present disclosure. The communication manager 1320 may be an example of aspects of the communication manager 1320, the communication manager 1420, or both as described herein. The communication manager 1320 or various components thereof may be examples of components for performing various aspects of end-to-end QoS via CPE as described herein. For example, the communication manager 1320 may include a mapping information communication component 1325, a packet conversion component 1330, a packet communication interface 1335, a service class communication component 1340, a traffic identifier component 1345, a device interface 1350, a packet scheduler 1355, a DHCP client 1360, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0230] Additionally or alternatively, the communication manager 1320 may support wireless communications at a first network device according to an example as disclosed herein. The mapping information communication component 1325 may be configured to or otherwise support a component for receiving mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology supported by the first network device from a second network device. The packet conversion component 1330 may be configured to or otherwise support a component for converting a header of a packet between a first network address of a first radio access technology and a second network address used by the first network device using a conversion rule included in the mapping information. The packet communication interface 1335 may be configured to or otherwise support a component for communicating packets between devices associated with the first network device using a first service class in a set of multiple service classes and a first QoS flow in a set of multiple QoS flows based on conversion of the header.

[0231] In some examples, the mapping information includes an indication of a set of Internet Protocol addresses to be communicated to the QoS flow. In some examples, the header is converted based on the set of Internet Protocol addresses.

[0232] In some examples, class of service communicating component 1340 can be configured or otherwise support means for sending an indication of a set of multiple classes of service to a second network device. In some examples, mapping information communicating component 1325 can be configured or otherwise support means for receiving mapping information based on sending an indication of a set of multiple classes of service.

[0233] In some examples, traffic identifier component 1345 can be configured or otherwise support means for sending, to a second network device, a second packet including a traffic identifier mapped to a default QoS flow associated with the first radio access technology. In some examples, mapping information communication component 1325 can be configured or otherwise support means for receiving mapping information based on sending the second packet.

[0234] In some examples, device interface 1350 may be configured or otherwise support components for receiving a second packet from a device via a default service class. In some examples, packet communication interface 1335 may be configured or otherwise support components for wherein the second packet is sent to a second network device based on receiving the second packet from the device.

[0235] In some examples, to support communicating packets, device interface 1350 may be configured or otherwise support components for receiving packets from a device via a first class of service. In some examples, to support communicating packets, service identifier component 1345 may be configured or otherwise support components for inserting a service identifier corresponding to the first class of service into a header of the packet based on mapping information. In some examples, to support communicating packets, packet communication interface 1335 may be configured or otherwise support components for sending a packet including a service identifier to a second network device.

[0236] In some examples, the service identifier is a virtual local area network tag.

[0237] In some examples, to support converting a header of a packet, the packet communication interface 1335 may be configured or otherwise support a component for receiving a packet from a second network device, the packet including a first network address. In some examples, to support converting a header of a packet, the packet conversion component 1330 may be configured or otherwise support a component for replacing the first network address with a second network address mapped to the first network address via mapping information. In some examples, to support converting a header of a packet, the packet communication interface 1335 may be configured or otherwise support a component for wherein the packet is sent to the device via a first service class.

[0238] In some examples, to support converting the header of the packet, the device interface 1350 may be configured or otherwise support a component for receiving a packet from the device, the packet including the second network address. In some examples, to support converting the header of the packet, the packet conversion component 1330 may be configured or otherwise support a component for replacing the second network address with a first network address mapped to the second network address via mapping information. In some examples, to support converting the header of the packet, the packet communication interface 1335 may be configured or otherwise support a component for sending the packet to the second network device.

[0239] In some examples, the packet scheduler 1355 may be configured or otherwise support components for scheduling the communication of a set of multiple packets including a packet based on a respective service class associated with each packet in the set of multiple packets. In some examples, the packet communication interface 1335 may be configured or otherwise support components for wherein the packets are communicated based on scheduling.

[0240] In some examples, the mapping information is received via Dynamic Host Configuration Protocol messages, serial communications, or HTTP.

[0241] In some examples, the mapping information is received by a Dynamic Host Configuration Protocol (DHCP) client at the first network device and via a DHCP offer message sent by a DHCP server at the second network device. In some examples, the DHCP offer message includes the mapping information and indicates an identifier configured to cause the DHCP client to avoid discarding the DHCP offer message.

[0242] In some examples, receiving mapping information includes an indication of one or more QoS identifiers mapped to service classes in a set of multiple service classes, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0243] In some examples, receiving mapping information includes receiving description information indicating a maximum flow bit rate for each QoS flow, a guaranteed flow bit rate for each QoS flow, an averaging window for each QoS flow, a QoS identifier for each QoS flow, or a combination thereof.

[0244] In some examples, the mapping information does not include information associated with an Ethernet port of the first network device.

[0245] In some examples, the first network device and the second network device are included in a CPE.

[0246] In some examples, the first radio access technology is fifth generation and the second radio access technology is Wi-Fi.

[0247] Fig.14 A diagram of a system 1400 including a device 1405 supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The device 1405 may be an example of a device 1305, a device 1405, or an AP as described herein, or include components of these devices. The device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1420, a network communication manager 1410, a transceiver 1415, an antenna 1425, a memory 1430, a code 1435, a processor 1440, and an inter-AP communication manager 1445. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1450).

[0248] The network communication manager 1410 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communication manager 1410 may manage the transmission of data communications for client devices (such as one or more STAs).

[0249] In some cases, the device 1405 may include a single antenna 1425. However, in some other cases, the device 1405 may have more than one antenna 1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1415 may communicate bidirectionally via one or more antennas 1425, a wired or wireless link, as described herein. For example, the transceiver 1415 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1415 may also include a modem for: modulating packets; and providing the modulated packets to one or more antennas 1425 for transmission; and demodulating packets received from one or more antennas 1425. The transceiver 1415, or the transceiver 1415 and one or more antennas 1425 may be examples of transmitters 1315, transmitters 1415, receivers 1310, receivers 1110, or any combination thereof or components thereof as described herein.

[0250] Memory 1430 may include RAM and ROM. Memory 1430 may store computer-readable, computer-executable code 1435 including instructions that, when executed by processor 1440, cause device 1405 to perform various functions described herein. In some cases, memory 1430 may contain BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0251] Processor 1440 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, processor 1440 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks that support end-to-end QoS via CPE). For example, device 1405 or a component of device 1405 may include processor 1440 and memory 1430 coupled to or coupled to processor 1440, the processor 1440 and memory 1430 being configured to perform the various functions described herein.

[0252] The inter-AP communication manager 1445 may manage communications with other APs and may include a controller or scheduler for controlling communications with STAs in coordination with other APs. For example, the inter-AP communication manager 1445 may coordinate the scheduling of transmissions to the APs for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-AP communication manager 1445 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between APs.

[0253] Additionally or alternatively, the communication manager 1420 may support wireless communication at the first network device according to the examples disclosed herein. For example, the communication manager 1420 may be configured to or otherwise support a component for receiving mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of a first radio access technology to one or more service classes in a set of multiple service classes of a second radio access technology supported by the first network device from a second network device. The communication manager 1420 may be configured to or otherwise support a component for converting a header of a packet between a first network address of the first radio access technology and a second network address used by the first network device using a conversion rule included in the mapping information. The communication manager 1420 may be configured to or otherwise support a component for communicating packets between devices associated with the first network device using a first service class in a set of multiple service classes and a first QoS flow in a set of multiple QoS flows based on conversion of the header.

[0254] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 can support techniques for improved communication reliability. Using the techniques and processes described herein, end-to-end QoS can be established between a first RAT (e.g., a cellular network) and a second RAT (e.g., Wi-Fi) to provide efficient and reliable communication via the CPE, which can enhance the user experience at the STA.

[0255] Fig.15 A flowchart illustrating a method 1500 for supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 3 to 12 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0256] At 1505, the method may include: sending mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of the first radio access technology to one or more service classes in a set of multiple service classes of the second radio access technology to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. 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.11 The described mapping information communication component 1125 is executed.

[0257] At 1510, the method may include communicating packets between a first QoS flow in a set of multiple QoS flows and a first service class in a set of multiple service classes based on the mapping information. 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.11 The packet communication interface 1130 described above is executed.

[0258] Fig.16 A flowchart illustrating a method 1600 for supporting end-to-end QoS via CPE according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 3 to 12 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0259] At 1605, the method may include receiving, via a first radio access technology, control signaling indicating a set of QoS parameter values ​​for each QoS flow in a set of multiple QoS flows. 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.11 The control signaling interface 1140 described above is implemented.

[0260] At 1610, the method may include: sending mapping information indicating a mapping of each QoS flow in a set of multiple QoS flows of the first radio access technology to one or more service classes in a set of multiple service classes of the second radio access technology to a second network device, wherein the mapping is based on a set of QoS parameter values ​​for the set of multiple QoS flows. 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.11 The described mapping information communication component 1125 is executed.

[0261] At 1615, the method may include: communicating packets between a first QoS flow in a set of multiple QoS flows and a first service class in a set of multiple service classes based on the mapping information. 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.11 The packet communication interface 1130 described above is executed.

[0262] Fig.17 A flowchart illustrating a method 1700 for supporting end-to-end QoS via a CPE according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by an AP or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by an AP or a component thereof as described in reference to Figure 1 To Figure 6c and Figures 11 to 14 The AP described herein performs. In some examples, the AP may execute an instruction set to control the functional elements of the AP to perform the described functions. Additionally or alternatively, the AP may use dedicated hardware to perform various aspects of the described functions.

[0263] At 1705, the method may include: receiving mapping information from a second network device indicating a mapping of each QoS flow in a set of a plurality of QoS flows of a first radio access technology to one or more service classes in a set of a plurality of service classes of a second radio access technology supported by the first network device. 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.15 The described mapping information communication component 1525 is executed.

[0264] At 1710, the method may include: using the conversion rules included in the mapping information to convert the header of the packet between the first network address of the first radio access technology and the second network address used by the first network device. 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.15 The described packet conversion component 1530 performs.

[0265] At 1715, the method may include: communicating packets between devices associated with the first network device using a first service class in a set of multiple service classes and a first QoS flow in a set of multiple QoS flows based on the conversion of the header. 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.15 The packet communication interface 1535 described above is executed.

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

[0267] Aspect 1: A method for wireless communication at a first network device, comprising: sending mapping information to a second network device indicating a mapping of each QoS flow in a plurality of QoS flows of a first RAT to one or more service categories in a plurality of service categories of a second RAT, wherein the mapping is based at least in part on a set of QoS parameter values ​​for the plurality of QoS flows; and communicating packets between a first QoS flow in the plurality of QoS flows and a first service category in the plurality of service categories based at least in part on the mapping information.

[0268] Aspect 2: The method according to Aspect 1 also includes: receiving an indication of the multiple service categories of the second RAT from the second network device; and wherein each QoS flow is mapped to the one or more service categories at least in part based on receiving the indication of the multiple service categories.

[0269] Aspect 3: The method according to any one of aspects 1 to 2 further includes: receiving control signaling indicating the set of QoS parameter values ​​for each QoS flow in the multiple QoS flows via the first RAT.

[0270] Aspect 4: A method according to Aspect 3, wherein the control signaling includes a set of Internet Protocol addresses to be communicated via a QoS flow in the multiple QoS flows; and the QoS flow is mapped to at least one service category in the multiple service categories based at least in part on the set of Internet Protocol addresses.

[0271] Aspect 5: The method of aspect 4, wherein the set of Internet Protocol addresses is received from a policy control function associated with the first RAT.

[0272] Aspect 6: The method according to any one of aspects 4 to 5, wherein the mapping information includes an indication of the set of Internet Protocol addresses to be communicated via the QoS flow.

[0273] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: receiving an indication of the multiple service categories of the second RAT from the second network device; sending uplink control signaling requesting the multiple QoS flows based at least in part on the indication of the multiple service categories and using a default QoS flow; and receiving control signaling indicating the set of QoS parameter values ​​for each QoS flow in the multiple QoS flows via the first RAT based at least in part on the uplink control signaling.

[0274] Aspect 8: The method according to aspect 7, wherein the uplink control signaling is sent to a policy control function associated with the first RAT.

[0275] Aspect 9: A method according to any one of Aspects 1 to 8, wherein communicating the packet comprises: receiving the packet including a service identifier from the second network device; and sending the packet via the first QoS flow based at least in part on the service identifier mapped to the first QoS flow.

[0276] Aspect 10: The method according to aspect 9 also includes: removing the service identifier from the packet before sending the packet via the first QoS flow based at least in part on the service identifier corresponding to the Internet Protocol-based QoS flow.

[0277] Aspect 11: The method according to any one of aspects 9 to 10, wherein the packet including the traffic identifier is sent via the first QoS flow based at least in part on the first QoS flow being an Ethernet-based QoS flow.

[0278] Aspect 12: The method according to any one of aspects 9 to 10, wherein the service identifier is a virtual local area network tag.

[0279] Aspect 13: The method according to any one of aspects 1 to 12, wherein the mapping information is sent via a dynamic host configuration protocol message, serial communication or HTTP message.

[0280] Aspect 14: A method according to any one of Aspects 1 to 12, wherein the mapping information is sent by a Dynamic Host Configuration Protocol (DHCP) server at the first network device and via a DHCP offer message sent to a DHCP client at the second network device; and the DHCP offer message includes the mapping information and indicates an identifier configured to enable the DHCP client to avoid discarding the DHCP offer message.

[0281] Aspect 15: The method according to any one of Aspects 1 to 14, further comprising: avoiding mapping the Ethernet port of the second network device to a QoS flow.

[0282] Aspect 16: The method according to any one of aspects 1 to 15, wherein the second network device and the first network device are included in customer premises equipment (CPE).

[0283] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the set of QoS parameter values ​​for each QoS flow includes a delay budget value, a packet error rate value, a priority value, a bit rate value, a data burst value, a reflective QoS attribute value, a periodic value, or a combination thereof; and each service category in the multiple service categories is associated with a delay limit value, a packet loss ratio value, a priority value, a minimum throughput value, a maximum throughput value, a burst size value, a priority value, a service interval value, or a combination thereof.

[0284] Aspect 18: The method according to any one of Aspects 1 to 17 further includes: mapping each of the multiple QoS flows to one or more service categories among the multiple service categories based at least in part on QoS identifiers of the multiple QoS flows and a mapping table including the multiple service categories, description information associated with each QoS flow, and packet filter information.

[0285] Aspect 19: A method according to any one of Aspects 1 to 18, wherein sending the mapping information includes: sending an indication of one or more QoS identifiers mapped to service categories in the multiple service categories, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0286] Aspect 20: A method according to Aspect 19, wherein sending the mapping information includes: sending descriptive information indicating the maximum stream bit rate of each QoS stream, the guaranteed stream bit rate of each QoS stream, the average window of each QoS stream, the QoS identifier of each QoS stream, or a combination thereof.

[0287] Aspect 21: The method according to any one of aspects 1 to 20, wherein the first RAT is a cellular communication technology and the second RAT is Wi-Fi.

[0288] Aspect 22: A method for wireless communication at a first network device, comprising: receiving mapping information from a second network device indicating a mapping of each of a plurality of QoS flows of a first RAT to one or more service categories of a plurality of service categories of a second RAT supported by the first network device; using a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first RAT and a second network address used by the first network device; and communicating the packet between devices associated with the first network device using a first service category of the plurality of service categories and a first QoS flow of the plurality of QoS flows based at least in part on the conversion of the header.

[0289] Aspect 23: The method of aspect 22, wherein the mapping information comprises an indication of a set of Internet Protocol addresses to be communicated to the QoS flow; and the header is converted based at least in part on the set of Internet Protocol addresses.

[0290] Aspect 24: The method according to any one of Aspects 22 to 23 further includes: sending an indication of the multiple service categories to the second network device; and wherein the mapping information is received at least in part based on sending the indication of the multiple service categories.

[0291] Aspect 25: The method according to any one of Aspects 22 to 24 further includes: sending a second packet including a service identifier mapped to a default QoS flow associated with the first RAT to the second network device; and wherein the mapping information is received at least in part based on sending the second packet.

[0292] Aspect 26: The method according to aspect 25 further includes: receiving the second packet from the device via a default service class; and wherein the second packet is sent to the second network device based at least in part on receiving the second packet from the device.

[0293] Aspect 27: A method according to any one of Aspects 22 to 26, wherein communicating the packet includes: receiving the packet from the device via the first service category; inserting a service identifier corresponding to the first service category into the header of the packet based at least in part on the mapping information; and sending the packet including the service identifier to the second network device.

[0294] Aspect 28: The method according to aspect 27, wherein the service identifier is a virtual local area network tag.

[0295] Aspect 29: A method according to any one of Aspects 22 to 28, wherein converting the header of the packet includes: receiving the packet from the second network device, the packet including the first network address; replacing the first network address with the second network address mapped to the first network address via the mapping information; and wherein the packet is sent to the device via the first service category.

[0296] Aspect 30: A method according to any one of Aspects 22 to 29, wherein converting the header of the packet includes: receiving the packet from the device, the packet including the second network address; replacing the second network address with the first network address mapped to the second network address via the mapping information; and wherein the packet is sent to the second network device.

[0297] Aspect 31: The method according to any one of Aspects 22 to 30 further includes: scheduling the communication of multiple packets including the packet based at least in part on a corresponding service class associated with each packet in the multiple packets; and wherein the packets are communicated at least in part based on the scheduling.

[0298] Aspect 32: The method according to any one of Aspects 22 to 31, wherein the mapping information is received via DHCP, or serial communication, or HTTP.

[0299] Aspect 33: A method according to any one of Aspects 22 to 32, wherein the mapping information is received by a DHCP client at the first network device and via a DHCP offer message sent by a DHCP server at the second network device; and the DHCP offer message includes the mapping information and indicates an identifier configured to enable the DHCP client to avoid discarding the DHCP offer message.

[0300] Aspect 34: A method according to any one of Aspects 22 to 33, wherein the receiving device comprises an indication of one or more QoS identifiers mapped to service categories in the multiple service categories, descriptive information associated with each QoS flow, a set of packet filters for each QoS flow, or any combination thereof.

[0301] Aspect 35: A method according to Aspect 34, wherein receiving the mapping information includes: receiving descriptive information indicating the maximum flow bit rate of each QoS flow, the guaranteed flow bit rate of each QoS flow, the average window of each QoS flow, the QoS identifier of each QoS flow, or a combination thereof.

[0302] Aspect 36: The method according to any one of Aspects 22 to 35, wherein the mapping information does not include information associated with an Ethernet port of the first network device.

[0303] Aspect 37: A method according to any one of Aspects 22 to 36, wherein the first network device and the second network device are included in a CPE.

[0304] Aspect 38: The method of any one of Aspects 22 to 37, wherein the first RAT is a cellular communication technology and the second RAT is Wi-Fi.

[0305] Aspect 39: An apparatus for performing wireless communication at a first network device, 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 21.

[0306] Aspect 40: An apparatus for wireless communication at a first network device, comprising: at least one component for performing the method according to any one of aspects 1 to 21.

[0307] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication at a first network device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 21.

[0308] Aspect 42: An apparatus for performing wireless communications at a first network device, 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 22 to 38.

[0309] Aspect 43: An apparatus for wireless communication at a first network device, comprising: at least one component for performing a method according to any one of aspects 22 to 38.

[0310] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication at a first network device, the code comprising instructions executable by a processor to perform the method according to any one of aspects 22 to 38.

[0311] 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 other implementations are possible. In addition, aspects from two or more methods may be combined in a method.

[0312] 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 techniques described 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.

[0313] The information and signals described herein may be represented using any of a variety of different technologies 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.

[0314] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0315] 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.

[0316] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transmission of computer program from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose 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 parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical 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.

[0317] 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). Moreover, 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."

[0318] 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, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0319] 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 the similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0320] 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 "having advantages 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.

[0321] 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. Therefore, 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. An apparatus for wireless communication at a first network device, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending, to a second network device, mapping information indicating a mapping of each of a plurality of quality of service flows of the first radio access technology to one or more of a plurality of service classes of the second radio access technology, wherein the mapping is based at least in part on a set of quality of service parameter values ​​for the plurality of quality of service flows; as well as Packets are communicated between a first quality of service flow of the plurality of quality of service flows and a first class of service of the plurality of classes of service based at least in part on the mapping information.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving, from the second network device, an indication of the plurality of service classes for the second radio access technology, Wherein each quality of service flow is mapped to the one or more service classes based at least in part on receiving the indication of the plurality of service classes.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicative of the set of quality of service parameter values ​​for each of the plurality of quality of service flows is received via the first radio access technology.

4. The device according to claim 3, wherein: The control signaling comprises a set of Internet Protocol addresses to be communicated via a quality of service flow of the plurality of quality of service flows; and The quality of service flow is mapped to at least one class of service of the plurality of classes of service based at least in part on the set of Internet Protocol addresses.

5. The apparatus of claim 4, wherein the set of Internet Protocol addresses is received from a policy control function associated with the first radio access technology.

6. The apparatus of claim 4, wherein the mapping information comprises an indication of the set of Internet Protocol addresses to be communicated via the quality of service flow.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, from the second network device, an indication of the plurality of service classes for the second radio access technology; sending uplink control signaling requesting the plurality of quality of service flows based at least in part on the indication of the plurality of service classes and using a default quality of service flow; as well as Control signaling is received via the first radio access technology based at least in part on the uplink control signaling indicating a set of quality of service parameter values ​​for each of a plurality of quality of service flows for a first radio access technology.

8. The apparatus of claim 1, wherein the instructions for communicating the packet are executable by the processor to cause the apparatus to: receiving the packet including the service identifier from the second network device; and The packet is sent via the first quality of service flow based at least in part on the traffic identifier mapped to the first quality of service flow.

9. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to: The traffic identifier is removed from the packet prior to transmitting the packet via the first quality of service flow based at least in part on the traffic identifier corresponding to an Internet Protocol based quality of service flow.

10. The apparatus of claim 8, wherein the packet including the traffic identifier is sent via the first quality of service flow based at least in part on the first quality of service flow being an Ethernet-based quality of service flow.

11. The apparatus of claim 1, wherein the mapping information is sent via a dynamic host configuration protocol message, a serial communication, or a hypertext transfer protocol message.

12. The device according to claim 1, wherein: The mapping information is sent by a Dynamic Host Configuration Protocol (DHCP) server at the first network device and via a DHCP offer message sent to a DHCP client at the second network device; and The DHCP offer message includes the mapping information and indicates an identifier configured to enable the DHCP client to avoid discarding the DHCP offer message.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Avoid mapping the Ethernet port of the second network device to the quality of service flow.

14. The device according to claim 1, wherein: The set of quality of service parameter values ​​for each quality of service flow includes a delay budget value, a packet error rate value, a priority value, a bit rate value, a data burst value, a reflective quality of service attribute value, a periodicity value, or a combination thereof; and Each service class of the plurality of service classes is associated with a delay bound value, a packet loss ratio value, a priority value, a minimum throughput value, a maximum throughput value, a burst size value, a priority value, a service interval value, or a combination thereof.

15. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Each of the plurality of quality of service flows is mapped to one or more of the plurality of service classes based at least in part on quality of service identifiers of the plurality of quality of service flows and a mapping table comprising the plurality of service classes, descriptive information associated with each quality of service flow, and packet filter information.

16. The apparatus of claim 1, wherein the instructions for sending the mapping information are executable by the processor to cause the apparatus to: An indication of one or more quality of service identifiers mapped to a class of service in the plurality of classes of service, descriptive information associated with each quality of service flow, a set of packet filters for each quality of service flow, or any combination thereof is sent.

17. The apparatus of claim 1, wherein the instructions for sending the mapping information are executable by the processor to cause the apparatus to: Descriptive information indicating a maximum stream bit rate for each quality of service flow, a guaranteed stream bit rate for each quality of service flow, an averaging window for each quality of service flow, the quality of service identifier for each quality of service flow, or a combination thereof is sent.

18. An apparatus for wireless communication at a first network device, 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 second network device, mapping information indicating a mapping of each of a plurality of quality of service flows of a first radio access technology to one or more of a plurality of service classes of a second radio access technology supported by the first network device; using a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first radio access technology and a second network address used by the first network device; as well as The packet is communicated between devices associated with the first network device using a first class of service of the plurality of classes of service and a first quality of service flow of the plurality of quality of service flows based at least in part on the transformation of the header.

19. The device according to claim 18, wherein: The mapping information includes an indication of a set of Internet Protocol addresses to be communicated to the quality of service flow; and The header is transformed based at least in part on the set of Internet Protocol addresses.

20. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: sending an indication of the plurality of service classes to the second network device, Wherein the mapping information is received based at least in part on sending the indication of the plurality of service classes.

21. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: sending, to the second network device, a second packet including a traffic identifier mapped to a default quality of service flow associated with the first radio access technology, Wherein the mapping information is received based at least in part on sending the second packet.

22. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: receiving the second packet from the device via a default class of service, Wherein the second packet is sent to the second network device based at least in part on receiving the second packet from the device.

23. The apparatus of claim 18, wherein the instructions for communicating the packet are executable by the processor to cause the apparatus to: receiving the packet from the device via the first class of service; inserting a traffic identifier corresponding to the first class of service into a header of the packet based at least in part on the mapping information; as well as The packet including the service identifier is sent to the second network device.

24. The apparatus of claim 18, wherein the instructions for converting the header of the packet are executable by the processor to cause the apparatus to: receiving the packet from the second network device, the packet including the first network address; and replacing the first network address with the second network address mapped to the first network address via the mapping information, The packets are sent to the device via the first service class.

25. The apparatus of claim 18, wherein the instructions for converting the header of the packet are executable by the processor to cause the apparatus to: receiving the packet from the device, the packet including the second network address; and replacing the second network address with the first network address mapped to the second network address via the mapping information, The packet is sent to the second network device.

26. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: scheduling communication of a plurality of packets including the packet based at least in part on a respective class of service associated with each packet in the plurality of packets, Wherein the packets are communicated based at least in part on the schedule.

27. The apparatus of claim 18, wherein the mapping information is received via a dynamic host configuration protocol message, a serial communication, or a hypertext transfer protocol message.

28. The apparatus of claim 18, wherein: The mapping information is received by a Dynamic Host Configuration Protocol (DHCP) client at the first network device and via a DHCP offer message sent by a DHCP server at the second network device; and The DHCP offer message includes the mapping information and indicates an identifier configured to enable the DHCP client to avoid discarding the DHCP offer message.

29. A method for wireless communication at a first network device, comprising: sending, to a second network device, mapping information indicating a mapping of each of a plurality of quality of service flows of the first radio access technology to one or more of a plurality of service classes of the second radio access technology, wherein the mapping is based at least in part on a set of quality of service parameter values ​​for the plurality of quality of service flows; as well as Packets are communicated between a first quality of service flow of the plurality of quality of service flows and a first class of service of the plurality of classes of service based at least in part on the mapping information.

30. A method for wireless communication at a first network device, comprising: receiving, from a second network device, mapping information indicating a mapping of each of a plurality of quality of service flows of a first radio access technology to one or more of a plurality of service classes of a second radio access technology supported by the first network device; using a conversion rule included in the mapping information to convert a header of a packet between a first network address of the first radio access technology and a second network address used by the first network device; as well as The packet is communicated between devices associated with the first network device using a first class of service of the plurality of classes of service and a first quality of service flow of the plurality of quality of service flows based at least in part on the transformation of the header.

Images