TW202337184A - 5g qos provisioning for an end-to-end connection including non-5g networks - Google Patents

Abstract

Various embodiments may include methods and systems for improving Quality of Service (QoS) in an end-to-end network connection including a first communication network and a second communication network. A method may include determining, by a network element within the end-to-end network connection, a QoS requirement of the end-to-end network connection, obtaining, by the network element, QoS information of the second communication network from a reporting entity within the second communication network, and adjusting, by the network element, a QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information.

Description

5G QoS preparation including end-to-end connections for non-5G networks

This patent application claims priority rights to U.S. Provisional Patent Application No. 63/263,465 titled "5G QoS Provisioning For An End-to-End Connection Including Non-5G Networks" filed on November 3, 2021 , the entire contents of which are incorporated herein by reference for all purposes.

The present invention relates to 5G QoS provisioning of end-to-end connections including non-5G networks.

Communications networks can be configured to provide Quality of Service (QoS) for applications, services or data flows. There is a resource cost when provisioning the network to provide a specific QoS. Therefore, in order to meet the specific QoS requirements of the network, service providers usually try to provide sufficient network resources without over or under using network resources. Providing QoS for applications, services or data flows that involve communication across two or more different types of networks is even more complex.

Various aspects include systems and methods performed by network elements of a communications network for managing end-to-end quality of service (QoS) in an end-to-end network connection including a first communications network and a second communications network. Some aspects may include: the network element in the end-to-end network connection determines the QoS requirements of the end-to-end network connection; the network element obtains the QoS information of the second communication network from the reporting entity in the second communication network ; and the network element adjusts the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information. In some aspects, the first communication network may be a 5G network, and the second communication network may not be a 5G network (ie, the second communication network may be a non-5G network).

In some aspects, the reporting entity may be a device within the second communications network, and the network element may be a device within the first communications network. Such aspects may further include: measuring QoS information by the reporting entity; obtaining QoS information of the second communication network by the network element from the reporting entity in the second communication network; and receiving QoS information by the network element from the reporting entity.

In some aspects, the QoS information may include at least one of the following: round-trip delay of the end-to-end network connection, one-way delay of the end-to-end network connection, or packet error rate provided to the reporting entity. In some aspects, the QoS information may include the classification of the second communication network. In some aspects, the QoS information may include a request message indicating the round-trip delay of the end-to-end network connection, the one-way delay of the end-to-end network connection, or the packet error rate provided to the reporting entity. Change. In some aspects, the QoS information may include at least one of application information or traffic information.

In some aspects, obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network may include measuring the delay between the first communication network and the endpoint server in the second communication network. .

In some aspects, the network element may be located in the second communication network, and obtaining the QoS information of the second communication network from the reporting entity in the second communication network by the network element may include measuring a relationship between the reporting entity and the network element. delay between.

In some aspects, a network element may be located within a third communications network that is communicatively connected to a second communications network via the first communications network, and the network element receives the request from a reporting entity within the second communications network Obtaining QoS information of the second communication network may include measuring delays between the reporting entity and network elements.

In some aspects, the network element may be located in the first communication network, and obtaining the QoS information of the second communication network from the reporting entity in the second communication network by the network element may include measuring the relationship between the reporting entity and the network element. delay between.

In some aspects, determining the QoS requirements of the end-to-end network connection by the network elements within the end-to-end network connection may include determining the QoS requirements of the end-to-end network connection by the network element based on the service agreement, application type, or user request. The QoS requirements of the road connection, and the network element adjusting the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information may include adjusting the 5G QoS parameters of the first communication network by the network element.

Other aspects include a network element having a processor configured to perform one or more operations of any of the methods described above. Other aspects include processing equipment for use within a network element configured with processor-executable instructions to perform the operations of any of the methods described above. Other aspects include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause a processor of the network element to Perform any of the above methods. Other aspects include network elements having components for performing the functionality of any of the above methods. Other aspects include a system-on-chip for a network element and including a processor configured to perform one or more operations of any of the methods described above.

Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for purposes of illustration and are not intended to limit the scope of the claims.

Various embodiments include systems and methods for improving quality of service (QoS) in end-to-end network connections including a first communications network (eg, a 5G network) and a second communications network (eg, a non-5G network) . Network elements within the 5G network may be provisioned with QoS requirements for endpoint devices or endpoint user equipment (UE) within the non-5G network that are connected to the 5G network. Network elements can provide QoS to endpoint devices based on the QoS requirements. However, network elements may not know, observe, or otherwise be able to measure the actual conditions and status of QoS provided to endpoint devices within non-5G networks. In various embodiments, network elements may obtain QoS information for non-5G networks from reporting entities within the non-5G network (eg, AR glasses, head-mounted displays (HMDs), 5G mobile phones). Network elements can use this QoS information to adjust the QoS parameters of the 5G network (i.e., if it is necessary to improve the QoS experienced by endpoint devices or to free up over-provisioned 5G network resources).

The term "network element" is used herein to refer to any or all of the computing devices that are part of or communicate with a communications network, such as servers, routers, gateways, hub devices, switching devices, bridge devices , a repeater device, or another electronic device that includes memory, communications components, and a programmable processor. Wireless devices that communicate with a network can be considered the network elements of such a network.

As used herein, the terms "network", "communications network" and "system" may interchangeably refer to part or all of a communications network or interconnection network. A network can include multiple network elements. The network may include a wireless network, and/or may support one or more features or services of the wireless network.

As used herein, "wireless network," "cellular network," and "wireless communications network" may interchangeably refer to part or all of a service provider's wireless network associated with a wireless device and/or a subscription on a wireless device. The technology described in this article can be used in various wireless communication networks, such as code division multiple access (CDMA), time division multiple access (TDMA), FDMA, orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA) ) and other networks. Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support at least one radio access technology, which can operate on one or more frequencies or frequency ranges. For example, a CDMA network may implement Universal Terrestrial Radio Access (UTRA) (including the Wideband Code Division Multiple Access (WCDMA) standard), CDMA2000 (including the IS-2000, IS-95 and/or IS-856 standards), etc. In another example, TDMA networks can implement GSM Evolution GSM Enhanced Data Rates (EDGE). In another example, the OFDMA network may implement Evolved UTRA (E-UTRA) (including the LTE standard), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDM etc. Reference may be made to wireless networks using the LTE standard, and therefore the terms "Evolved Universal Terrestrial Radio Access", "E-UTRAN" and "eNodeB" are also used interchangeably herein to refer to wireless networks. However, these references are provided as examples only and are not intended to exclude wireless networks using other communication standards. For example, although this article discusses various third-generation (3G) systems, fourth-generation (4G) systems, and fifth-generation (5G) systems, such systems are cited as examples only, and future-generation systems (e.g., 6th-generation systems) are generation (6G or higher systems) can be replaced in various instances.

The term "wireless device" as used herein refers to any or all of the following: wireless router device, wireless appliance, cellular phone, smartphone, portable computing device, personal or mobile multimedia player, laptop computer, tablet computer , smart computers, ultrabooks, handheld computers, wireless email receivers, multimedia Internet cellular phones, medical equipment and equipment, biometric sensors/devices, wearable devices (including smart watches, smart clothing, smart Glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets)), entertainment devices (e.g., wireless game controllers, music and video players, satellite radios, etc.), wireless network-enabled IoT networks ( IoT) devices (including smart instruments/sensors), industrial manufacturing equipment, large and small machinery and appliances used in homes or businesses, wireless communication components in autonomous and semi-autonomous vehicles, attached to or incorporated into various mobile devices Platform wireless devices, GPS devices, and similar electronic devices including memory, wireless communication components, and programmable processors.

The term "system on a chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip that contains multiple resources or processors integrated on a single substrate. A single SOC can contain circuitry for digital, analog, mixed-signal and RF functions. A single SOC can also include any number of general or special purpose processors (digital signal processors, modem processors, video processors, etc.), memory blocks (such as ROM, RAM, flash memory, etc.) and resources (such as timing regulator, voltage regulator, oscillator, etc.). The SOC may also include software for controlling integrated resources and processors and for controlling peripheral devices.

The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores, or processors on two or more IC dies, substrates, or SOCs. For example, a SIP may include a single substrate on which multiple IC dies or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SOCs coupled together via high-speed communication circuits and packaged in close proximity, such as on a single motherboard or in a single wireless device. The proximity of SOCs facilitates high-speed communication and sharing of memory and resources.

The term "QoS information" may be used herein to refer to data or information related to the quality of service (QoS) of an end-to-end connection. The QoS information may be obtained by the network element for use in adjusting one or more QoS parameters (e.g., 5G QoS identifier ( 5QI)), this end-to-end network connection includes telecommunications networks and other types of network connections (e.g., Bluetooth Low Energy (BLE), Wi-Fi, sidelinks). QoS information may be reported to the network element from devices within the end-to-end network connection that includes the network element, or may be measured or otherwise determined by the network element. QoS information may include QoS-related information for non-5G networks (e.g., Wi-Fi, BLE, sidelinks), including characteristics or metrics such as round-trip time delay, one-way delay, or packet error rate. Packet error rate may also be referred to as packet loss rate. The QoS information may further include a classification of non-5G networks that are part of the end-to-end connection. For example, the classification of network connections may determine whether the non-5G network is a Wi-Fi network (eg, IEEE802.11ad, 802.11ac), BLE, or a wired connection (eg, USB). As another example, the classification of networks may include QoS configurations for non-5G networks (e.g., Wi-Fi), which may be determined by specific access classes under Enhanced Distributed Channel Access (EDCA) (e.g., best effort or video) definition. QoS information may also include required changes to the QoS provided from a telecommunications network to user equipment (UE) located within different types of networks including end-to-end network connections of the telecommunications network. For example, the UE may report required changes to a 5G network that prepares the UE with a certain level of QoS, and the required changes may include an amount that reduces latency (e.g., round trip latency, one-way latency) or packet error rate , and/or the amount of delay (e.g., round trip delay, one-way delay) or packet error rate that is allowed to be increased without violating the UE's quality of experience (QoE). QoS information may also include measurements between the telecommunications network and the application or endpoint server, including one-way latency from the telecommunications network to the application server, one-way latency from the application server to the telecommunications network, and/or Or the round-trip delay between the telecommunications network and the application server. QoS information may further include information about applications executing on the UE, such as video codec, audio codec, bit rate, frame rate, latency (e.g., for rendering, for detecting gesture changes) ,QoS requirements (for example, regarding transmission volume and/or latency). QoS information may further include information about network traffic, such as whether traffic is symmetrical between uplink and downlink, whether uplink traffic is dominated by light commands and gestures but has strict latency requirements, and whether downlink traffic is Whether the traffic is mainly multimedia content but the delay requirements are not strict. The QoS information may further include the time delay between the remote UE or endpoint UE and the device hosting the renderer function for augmented reality (AR) applications or mixed reality (MR) applications.

Preparing for QoS for applications, services or data flows that involve communication across two or more different types of networks is complex. A communications network is able to determine information about its own network elements and configure its operations, including devices that communicate with or to those network elements (e.g., devices connected to the communications network). However, communication networks may not be able to obtain information about the operations of other communication networks. For example, an application client of a wireless device may communicate with another device (eg, an application server or another wireless device) via a communication path. The communication path between two endpoint devices (the "end-to-end" communication path) may span multiple networks.

As an example, to provide augmented reality applications, wireless smart glasses may communicate with an application server (ie, send signals to and receive signals from the application server) via communication paths spanning multiple communication networks. For example, smart glasses can communicate with a smartphone via a Wi-Fi network; the smartphone can communicate with a 5G network base station via a cellular communication link; the 5G network can communicate with an interconnection network (e.g., the Internet); and the Internet Networks can use Ethernet and wired network communications including application servers. In this example, the communication path between the smart glasses and the application server spans the Wi-Fi network, the 5G network, the Internet network, and the wired Ethernet network. Augmented reality applications of smart glasses may require specific QoS to meet one or more application requirements. A network (for example, a 5G network) can configure its individual network elements according to the QoS requirements of the application. However, 5G networks generally cannot control the configuration and operation of network elements that are not 5G networks, such as Wi-Fi networks, Internet networks, or wired Ethernet networks. The QoS of non-5G networks can be improved by allocating more resources to the 5G network connected to endpoint devices, but overprovisioning 5G core network resources is costly and inefficient.

Various embodiments include methods and network devices configured to perform methods of improving QoS in an end-to-end network connection that includes a first communication network (eg, a 5G network) and a second communication network (e.g., non-5G networks) and other types of communication networks. In various embodiments, the QoS requirements of the end-to-end network connection may be determined by network elements within the end-to-end network connection, and the QoS requirements are typically provided by endpoint devices within the second communications network. For example, an application, service or data flow may request QoS requirements, or may be associated with QoS requirements. The network element of the first communication network may obtain the QoS information of the second communication network from the reporting entity (eg, endpoint UE, intermediary UE, such as 5G phone, endpoint server) in the second communication network. The network element can then adjust the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information to provide sufficient QoS to support the end-to-end connection including the second communication network.

In some embodiments, network elements within the end-to-end network connection may determine the QoS requirements of the end-to-end network connection. The QoS requirements for an end-to-end network connection may be based in part on the UE's QoS requirements (eg, bandwidth, bit rate, packet error rate, etc.) or data requirements. When establishing a connection between a UE located within a non-5G network with an end-to-end network connection and a telecommunications network such as a 5G core network, the UE may provide basic information outlining the UE to network elements within the telecommunications network. Required QoS requirements. For example, the UE may notify the network element that the UE implements a data streaming video application, and the network element may configure the telecommunications network to provide QoS common in data streaming video services. In some embodiments, the network element may detect the UE's device or application type and may configure the 5G network. Network elements can configure the 5G network based on the UE's QoS requirements to provide universal QoS to endpoint UEs. However, outside the 5G network, within the non-5G network where the endpoint UE is located, the 5G network may not know the actual endpoint QoS. The 5G network may not have visibility and direct control over the non-5G network, and therefore may not be able to optimize the QoS provided to endpoint UEs over the 5G network. For example, a 5G network (configured by network elements) may over-provision QoS to the UE based solely on the QoS requirements received from the UE, thereby providing the UE with excessive resources (e.g., too much bandwidth, bit rate; low packet rate, etc. ), thus wasting 5G network resources. As another example, the 5G network (configured by the network elements) may not be able to prepare sufficient QoS for the UE. In this case, users of the endpoint UE may experience poor QoE, but the network elements of the 5G network will not be aware of the poor QoS experienced within the non-5G network.

Various embodiments allow network elements of a 5G network to manage the speed and quality of end-to-end network connections, where end-to-end QoE is not entirely affected by 5G QoS, but also by the QoS of non-5G networks.

1A is a system block diagram illustrating an exemplary communications system 100 suitable for implementing any of the various embodiments. The communication system 100 may be a 5G New Radio (NR) network or any other suitable network, such as a Long Term Evolution (LTE) network. Although Figure 1 illustrates a 5G network, next-generation networks may contain the same or similar elements. Accordingly, references to 5G networks and 5G network elements in the following description are for illustrative purposes and are not intended to be limiting.

Communication system 100 may include a heterogeneous network architecture including a core network 140 and various wireless devices (shown in Figure 1 as user equipment (UE) 120a-120e). Communication system 100 may also include a number of base stations (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station is an entity that communicates with wireless devices and may also be called a Node B, LTE evolved Node B (eNodeB or eNB), Access Point (AP), Radio Head, Transceiver Point (TRP), New Radio Base Station (NR BS), 5G NodeB (NB), next-generation NodeB (gNodeB or gNB), etc. Each base station can provide communications coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell service area" can refer to the coverage area of a base station, the base station subsystem serving that coverage area, or a combination thereof, depending on the context in which the term is used. The core network 140 may be any type of core network, such as an LTE core network (eg, EPC network), a 5G core network, etc.

The base stations 110a-110d may provide communication coverage for a macro cell service area, a pico cell service area, a femto cell service area, another cell service area, or a combination thereof. A macrocell service area can cover a relatively large geographic area (eg, a radius of several kilometers) and can allow unlimited access by wireless devices with a service subscription. A pico cell service area can cover a relatively small geographic area and can allow unlimited access by wireless devices with a service subscription. A femtocell service area may cover a relatively small geographic area (e.g., a home) and may allow wireless devices associated with the femtocell service area (e.g., wireless devices in a Closed Subscriber Group (CSG)) to have restricted access access. The base station used in the macro cell service area may be called a macro BS. The base station used in the pico cell service area may be called a pico BS. The base station used in the femto cell service area may be called a femto BS or a home BS. In the example shown in Figure 1, base station 110a may be a macro BS for macro cell service area 102a, base station 110b may be a pico BS for pico cell service area 102b, and base station 110c may be Femto BS for femto cell service area 102c. Base stations 110a-110d may support one or more (eg, three) cell service areas. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB" and "cell service area" may be used interchangeably in this article.

In some examples, the cell service area may not be static, and the geographic area of the cell service area may move based on the location of the mobile base station. In some examples, base stations 110a - 110d may be interconnected to each other and to communication system 100 via various types of backhaul interfaces, such as a direct physical connection, a virtual network, or a combination thereof using any suitable transport network. one or more other base stations or network nodes (not shown).

Base stations 110a-110d may communicate with core network 140 via wired or wireless communication links 126. Wireless devices 120a-120e may communicate with base stations 110a-110d via wireless communication link 122.

Wired communication link 126 may use a variety of wired networks (such as Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections), which may use one or more wired communication protocols, such as Ethernet , point-to-point communication protocol, High Level Data Link Control (HDLC), Advanced Data Communication Control Protocol (ADCCP) and Transmission Control Protocol/Internet Protocol (TCP/IP).

Communication system 100 may also include relay stations (such as relay BS 110d). A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a base station or wireless device) and sending data transmissions to a downstream station (e.g., a wireless device or base station). A relay station may also be a wireless device capable of relaying transmissions from other wireless devices. In the example shown in FIG. 1, relay station 110d may communicate with macro base station 110a and wireless device 120d to facilitate communication between base station 110a and wireless device 120d. A relay station may also be called a relay base station, a relay base station, a relay, etc.

The communication system 100 may be a heterogeneous network including different types of base stations, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations may have different transmit power levels, different coverage areas, and different effects of interference on the communication system 100 . For example, macro base stations may have high transmit power levels (eg, 5 to 40 watts), while pico, femto, and relay base stations may have lower transmit power levels (eg, 0.1 to 40 watts). 2 watts).

Network controller 130 may be coupled to a collection of base stations and may provide coordination and control for such base stations. Network controller 130 may communicate with the base station via backhaul. Base stations may also communicate with each other, for example directly or indirectly via wireless or wired backhaul.

Wireless devices 120a, 120b, 120c may be dispersed throughout wireless system 100, and each wireless device may be stationary or mobile. A wireless device may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, user equipment (UE), etc.

The macro base station 110a may communicate with the communication network 140 via a wired or wireless communication link 126. Wireless devices 120a, 120b, 120c may communicate with base stations 110a-110d via wireless communication link 122.

Wireless communication links 122 and 124 may include a plurality of carrier signals, frequencies, or frequency bands, and each carrier signal, frequency, or frequency band may include a plurality of logical channels. Wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that can be used in wireless communication links include 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global Interoperable Microwave Access (WiMAX), Time Division Multiple Access (TDMA) and other mobile phone communications technologies cellular RAT. Other examples of RATs that may be used in one or more of the various wireless communication links within communication system 100 include mid-range protocols such as Wi-Fi, LTE-U, LTE Direct, LAA, MuLTEfire, and relatively short-range RATs. , such as ZigBee, Bluetooth and Bluetooth Low Energy (LE).

Some wireless networks (eg, LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal sub-carriers. These sub-carriers are also usually called tones, frequency bands (bins), etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are sent with OFDM in the frequency domain and with SC-FDM in the time domain. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing between subcarriers may be 15 kHz, and the minimum resource allocation (called a "resource block") may be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast file transfer (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into sub-bands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

Although descriptions of some embodiments may use terminology and examples associated with LTE technology, some embodiments may be applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR can utilize OFDM with cyclic prefix (CP) on both the uplink (UL) and downlink (DL) and includes support for half-duplex operation using time division duplex (TDD). Single component carrier bandwidth of 100 MHz can be supported. The NR resource block can span 12 subcarriers, with a subcarrier bandwidth of 75 kHz and a duration of 0.1 milliseconds (ms). Each radio frame can be composed of 50 sub-frames with a length of 10 ms. Therefore, each subframe can have a length of 0.2 ms. Each sub-frame can indicate the link direction of data transmission (i.e. DL or UL), and the link direction of each sub-frame can be dynamically switched. Each subframe may include DL/UL data and DL/UL control data. Beamforming can be supported, and beam directions can be configured dynamically. Multiple-input multiple-output (MIMO) transmission using precoding can also be supported. MIMO configurations in DL can support up to eight transmit antennas, with multi-layer DL transmitting up to eight streams and up to two streams per wireless device. Can support multi-layer transmission of up to 2 streams per wireless device. Aggregation of multiple cell service areas can be supported with up to eight service cell areas. Alternatively, NR could support a different air interface than one based on OFDM.

Some wireless devices may be considered Machine Type Communications (MTC), or evolved or enhanced Machine Type Communications (eMTC) wireless devices. MTC and eMTC wireless devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (eg, a remote device), or some other entity Communication. For example, a wireless computing platform may provide connectivity to a network (eg, a wide area network, such as the Internet or a cellular network) via wired or wireless communication links. Some wireless devices may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Wireless devices 120a-120e may be included within a housing that houses elements of wireless devices 120a-120e, such as processor elements, memory elements, similar elements, or combinations thereof.

In general, any number of communication systems and any number of wireless networks can be deployed in a given geographical area. Each communications system and wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be called radio technology, air interface, etc. Frequency may also be called a carrier, a channel, etc. To avoid interference between communication systems of different RATs, each frequency can support a single RAT within a given geographical area. In some cases, 4G/LTE and/or 5G/NR RAT networks can be deployed. For example, a 5G non-standalone (NSA) network can simultaneously use 4G/LTE RAT on the 4G/LTE RAN side of the 5G NSA network and 5G/NR RAT on the 5G/NR RAN side of the 5G NSA network. 4G/LTE RAN and 5G/NR RAN can be connected to each other and to the 4G/LTE core network (e.g., Evolved Packet Core (EPC) network) in the 5G NSA network. Other example network configurations may include a 5G standalone (SA) network, where the 5G/NR RAN is connected to the 5G core network.

In some implementations, two or more wireless devices 120a-120e (eg, shown as wireless device 120a and wireless device 120e) may communicate directly using one or more sidelink channels 124 (eg, not communicating with each other using base stations 110a-110d as intermediaries). For example, wireless devices 120a-120e may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocol or similar protocol), mesh network or similar network, or a combination thereof. In this case, wireless devices 120a-120e may perform scheduling operations, resource selection operations, and other operations performed by base stations 110a-110d as described elsewhere herein.

1B-1D are system block diagrams illustrating example communications systems 150, 160, 170, and 180 suitable for implementing any of the various embodiments. Referring to Figures 1A-1D, communication systems 150, 160, 170, and 180 illustrate exemplary end-to-end communication paths between two endpoint devices spanning multiple communication networks. It should be understood that the examples shown in communication systems 150, 160, 170, and 180 are non-limiting and other implementations of end-to-end communication paths between two endpoint devices spanning multiple communication networks are possible. of.

Referring to Figure IB, application clients executing on UE 152a (eg, wireless devices 120a-120e) may communicate with application clients executing on UE 158 (eg, wireless devices 120a-120e). The communication path between UE 152a and UE 158 may span two networks, for example, 5G network 151a and non-5G network 151b. In some embodiments, the 5G network 151a may include a UE 152a that may communicate with the gNB 152b via a cellular communication link 153, a 5G core network 152c, and a UE that may implement communication between the 5G network 151a and the non-5G network 151b. User plane function 152d. Non-5G network 151b may include an interconnection network such as the Internet 154, a Wi-Fi access point 156, and a wireless device 158 that may communicate with the Wi-Fi access point 156 via a Wi-Fi wireless communication link 157 .

Referring to Figure 1C, application clients executing on UE 162a (eg, wireless devices 120a-120e) may communicate with application clients executing on UE 168 (eg, wireless devices 120a-120e). The communication path between UE 162a and UE 168 may span two networks, for example, 5G network 161a and non-5G network 161. In some embodiments, the 5G network 161a may include a UE 162a that may communicate with the gNB 152b via a cellular communication link 163, a 5G core network 162c, and a network that may enable communication between the 5G network 161a and the non-5G network 161b. User plane function 162d. Non-5G network 161b may include an interconnection network (such as the Internet 164), a 4G network 166a, a 4G base station (such as an eNB 166b), and a wireless device 168 that may communicate with the eNB 166b via a 4G wireless communication link 167.

Referring to Figure ID, communication system 170 may include three networks. An application client in the first non-5G network 171b executing on the wireless device 174 (shown as smart glasses) may communicate with the application server 176 in the second non-5G network 171c via the 5G network 171a. In this way, the communication path between the wireless device 174 and the application server 176 can span three communication networks. In some embodiments, the first non-5G network 171b may include a wireless device 174 that may communicate with a wireless device (UE) 172a via a Wi-Fi communication link 173. The 5G network 171a may include a UE 172a that can communicate with the gNB 172b via the cellular communication link 175, a 5G core network 172c, and user plane functions that can implement communication between the 5G network 171a and the second non-5G network 171b. 172d. The second non-5G network 171c may include an application server 176 that may communicate with the 5G network via a wired communication link 177.

Referring to Figure IE, communication system 180 may include three networks. Application clients in the first non-5G network 181b executing on the wireless device 184 (shown as smart glasses) may communicate with the application server 188 in the second non-5G network 181c via the 5G network 181a. In this way, the communication path between the wireless device 184 and the application server 188 can span three communication networks. In some embodiments, the first non-5G network 181b may include a wireless device 184 that may communicate with a wireless device (UE) 182a via a Wi-Fi communication link 181. The 5G network 181a may include a UE 182a that can communicate with the gNB 182b via the cellular communication link 185, a 5G core network 182c, and user plane functions that can implement communication between the 5G network 181a and the second non-5G network 181c. 182d. The second non-5G network 181 c may include an interconnection network (such as the Internet) 186 that may communicate with the 5G network via a cellular communication link 185 and an application server 188 that may communicate with the interconnection network 186 via a wired communication link 187 .

Figure 2 is a block diagram illustrating elements of an exemplary computing and wireless modem system 200 suitable for implementing any of various embodiments. Various embodiments may be implemented on multiple single-processor and multi-processor computer systems, including systems on a chip (SOC) or system-in-package (SIP).

Referring to FIGS. 1 and 2 , an exemplary computing system 200 (which may be a SIP in some embodiments) is shown including two SOCs 202 , 204 coupled to a clock 206 , a voltage regulator 208 , and a wireless transceiver 266 , the wireless transceiver is configured to send and receive wireless communications to/from wireless devices (eg, 120a-120e) or base stations (eg, 110a-110d) via antennas (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the wireless device by performing arithmetic, logical, control, and input/output (I/O) operations specified by the instructions. to execute the instructions of the software application. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high capacity, high speed (such as 5 Gbps, etc.), and/or very high frequency short wavelengths (such as the 28 GHz millimeter wave spectrum, etc.) Communication.

The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an applications processor 216, one or more auxiliary processors 218 connected to the one or more processors (such as vector auxiliary processor), memory 220, custom circuitry 222, system components and resources 224, interconnect/bus module 226, one or more temperature sensors 230, thermal management unit 232, and thermal power envelope (TPE) ) element 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect/bus module 264, a plurality of millimeter wave (mmWave) transceivers 256, memory 258, and various additional processors 260 (such as application processor, packet processor, etc.).

Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor/core may perform operations independently of the other processors/cores. For example, the first SOC 202 may include a processor executing a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor executing a second type of operating system (such as MICROSOFT WINDOWS 10). Additionally, any or all of processors 210, 212, 214, 216, 218, 252, 260 may be included as a processor cluster architecture (such as a synchronous processor cluster architecture, a non-synchronous or heterogeneous processor cluster architecture, etc.) a part of.

The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and for performing other specialized operations, such as data packetization. Decode and process encoded audio and video signals for rendering in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timing and other similar components used to support processors and software clients executing on wireless devices. System components and resources 224 and/or custom circuitry 222 may also include circuitry that interfaces with peripheral devices (such as cameras, electronic displays, wireless communication devices, external memory chips, etc.).

The first SOC 202 and the second SOC 204 may communicate via the interconnect/bus module 250 . The various processors 210 , 212 , 214 , 216 , 218 may be interconnected via an interconnect/bus module 226 to one or more memory elements 220 , system elements and resources 224 , as well as custom circuitry 222 and thermal management unit 232 . Similarly, processor 252 may be interconnected to power management unit 254, mmWave transceiver 256, memory 258, and various additional processors 260 via interconnect/bus module 264. Interconnect/bus modules 226, 250, 264 may include reconfigurable logic gate arrays and/or implement bus architectures (such as CoreConnect, AMBA, etc.). Communication can be provided by advanced interconnects, such as high-performance Network-on-Chip (NoC).

The first SOC 202 and the second SOC 204 may further include input/output modules (not shown) for communicating with resources external to the SOC, such as the clock 206 and the voltage regulator 208 . Resources external to the SOC (such as clock 206, voltage regulator 208) may be shared by two or more internal SOC processors/cores.

In addition to the example SIP 200 discussed above, some implementations may be implemented in a variety of computing systems, which may include a single processor, multiple processors, multi-core processors, or any combination thereof.

3 is a block diagram of components illustrating a software architecture 300 suitable for implementing any of the various embodiments, including a radio protocol stack for a user plane and a control plane in wireless communications. Referring to FIGS. 1-3 , wireless device 320 may implement software architecture 300 to facilitate wireless device 320 (eg, wireless devices 120a - 120e, 200 ) and base station 350 (eg, base station 110a ) of a communication system (eg, 100 ) -110d). In various embodiments, layers in software architecture 300 may form logical connections with corresponding layers in the software of base station 350. Software architecture 300 may be distributed among one or more processors (eg, processors 212, 214, 216, 218, 252, 260). Although illustrated with respect to one radio protocol stack, in a multi-SIM (Subscriber Identity Module) wireless device, the software architecture 300 may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., in In a dual-SIM wireless communication device, two protocol stacks are associated with two SIMs respectively). Although described below with reference to the LTE communication layer, the software architecture 300 may support any of the various standards and protocols for wireless communications, and/or may include support for any of the various standards and protocols for wireless communications. Additional protocols stack.

Software architecture 300 may include a non-access layer (NAS) 302 and an access layer (AS) 304. NAS 302 may include functionality and protocols that support packet filtering, security management, mobility control, session management, and messaging and signaling between a wireless device's SIM (such as SIM 204) and its core network 140. AS 304 may include functions and protocols that support communication between SIMs, such as SIM 204, and entities that support access to the network, such as base stations. In particular, AS 304 may include at least three layers (layer 1, layer 2, and layer 3), and each layer may include multiple sub-layers.

In the user plane and control plane, the layer 1 (L1) of the AS 304 may be the physical layer (PHY) 306, which may oversee transmission and/or reception via the wireless transceiver (e.g., 266) over the air interface. Function. Examples of such physical layer 306 functions may include cyclic redundancy check (CRC) appending, encoding blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The physical layer may include multiple logical channels, including the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH).

In the user plane and control plane, the layer 2 (L2) of the AS 304 may be responsible for the link between the wireless device 320 and the base station 350 on the physical layer 306. In some embodiments, Layer 2 may include a Media Access Control (MAC) sublayer 308, a Radio Link Control (RLC) sublayer 310, a Packet Data Convergence Protocol (PDCP) 312 sublayer, and a Service Data Adaptation Protocol ( SDAP) 317 sublayers, each of which forms a logical connection terminating at the base station 350.

In the control plane, Layer 3 (L3) of AS 304 may include Radio Resource Control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional layer 3 sub-layers, as well as multiple upper layers above layer 3. In some embodiments, the RRC sublayer 313 may provide functions including broadcasting system information, paging, and establishing and releasing RRC signaling connections between the wireless device 320 and the base station 350 .

In various embodiments, SDAP sublayer 317 may provide mapping between quality of service (QoS) flows and data radio bearers (DRBs). In some embodiments, the PDCP sublayer 312 may provide uplink functionality including multiplexing between different radio bearers and logical channels, sequence number addition, handover processing, integrity protection, encryption, and header compression. In the downlink, the PDCP sublayer 312 may provide functions including sequential delivery of data packets, detection of duplicate data packets, integrity verification, decryption, and header decompression.

In the uplink, the RLC sublayer 310 may provide segmentation and concatenation of upper layer data packets, retransmission of lost data packets, and automatic repeat request (ARQ). In the downlink, although the functions of the RLC sublayer 310 may include reordering of data packets to compensate for out-of-order reception, reassembly of upper layer data packets and ARQ.

In the uplink, the MAC sublayer 308 may provide functionality including multiplexing between logical and transport channels, random access procedures, logical channel prioritization, and hybrid ARQ (HARQ) operation. In the downlink, MAC layer functions may include channel mapping, demultiplexing, discontinuous reception (DRX) and HARQ operations within the cell service area.

Although the software architecture 300 may provide functionality for transmitting data via physical media, the software architecture 300 may further include at least one host layer 314 to provide data transmission services to various applications in the wireless device 320 . In some implementations, application-specific functionality provided by at least one host layer 314 may provide an interface between the software architecture and the general-purpose processor 206 .

In other embodiments, software architecture 300 may include one or more higher logic layers (such as transport, communications, rendering, applications, etc.) for providing host layer functionality. For example, in some implementations, software architecture 300 may include a network layer (such as an Internet Protocol (IP) layer), with logical connections terminating at a Packet Data Network (PDN) gateway (PGW). In some implementations, software architecture 300 may include an application layer where the logical connection terminates at another device (such as an end user device, a server, etc.). In some embodiments, the software architecture 300 may further include a hardware interface 316 in the AS 304 between the physical layer 306 and communications hardware, such as one or more radio frequency (RF) transceivers.

4 is a block diagram illustrating components of a system 400 configured to improve QoS in an end-to-end network connection including a first communications network and a second communications network, in accordance with various embodiments. Referring to Figures 1-4, system 400 may include network elements 402 of a 5G network, such as wireless devices (eg, 110a-110d, 200, 320), base stations (eg, 120a-120e, 200, 350), or Another network element of the 5G network includes the core network 140 or any network element of the 5G network 151a, 161a, 171a and 181a.

Network element 402 may include one or more processors 428 coupled to electronic storage 426 and transceiver 427 (which may be a wired transceiver and/or a wireless transceiver, eg, 266). Within network element 402, transceiver 427 may be configured to receive the message sent in transmission and pass the message to processor(s) 428 for processing. Similarly, processor 428 may be configured to send messages for transmission to transceiver 427 for transmission. Network element 402 may send messages to and receive messages from communications network 424 via wired and/or wireless communications links.

Referring to network element 402 , processor(s) 428 may be configured by machine-readable instructions 406 . Machine-readable instructions 406 may include one or more instruction modules. Instruction modules may include computer program modules. The instruction module may include one or more of the end-to-end QoS module 408, the QoS acquisition module 410, the QoS adjustment module 412, or other instruction modules.

The end-to-end QoS module 408 may be configured to determine QoS requirements for the end-to-end network connection used to deliver packets from a packet source (e.g., an endpoint UE) to a packet destination (e.g., an endpoint server) and vice versa. Likewise. The end-to-end QoS module can be configured to determine the QoS requirements for an end-to-end network connection based on service agreement, application type or user request.

The QoS obtaining module 410 may be configured to obtain QoS information of the second communication network from a reporting entity (eg, endpoint UE, intermediary UE, endpoint server) within the second communication network. The QoS acquisition module 410 may be configured to receive QoS information from the reporting entity by the network element. The QoS acquisition module 410 may be configured to measure delays between endpoint servers in the first communication network and the second communication network. The QoS acquisition module 410 may be configured to measure delays between reporting entities and network elements.

The QoS adjustment module 412 may be configured to adjust the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information. The QoS adjustment module 412 may be configured to adjust 5G QoS parameters of the first communication network.

Electronic storage device 426 may include non-transitory storage media that stores information electronically. Electronic storage media for electronic storage 426 may include one or both of the following: system storage provided integrally with network element 402 (i.e., substantially non-removable) and/or available via, for example, a port (e.g., USB A removable storage device that is removably connected to the network element 402 (e.g., a USB port, a FireWire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage devices 426 may include one or more of the following: optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tapes, magnetic hard disks, floppy disk drives, etc.), charge-based storage media (e.g., optical disks, etc.) For example, EEPROM, RAM, etc.), solid-state storage media (e.g., flash memory drive, etc.), and/or other electrically readable storage media. Electronic storage 426 may include one or more virtual storage resources (eg, cloud storage, virtual private network, and/or other virtual storage resources). Electronic storage device 426 may store software algorithms, information determined by processor(s) 428, information received from network element 402, or other information that enables network element 402 to function as described herein.

Processor(s) 428 may be configured to provide information processing capabilities in network element 402 . As such, processor(s) 428 may include digital processors, analog processors, digital circuits designed to process information, analog circuits designed to process information, state machines, and/or other mechanisms for processing information electronically. one or more of them. Although processor(s) 428 are shown as a single entity, this is for illustrative purposes only. In some embodiments, processor(s) 428 may include multiple processing units and/or processor cores. The processing units may be physically located within the same device, or the processor(s) 428 may represent the processing functionality of a plurality of devices operating in conjunction. Processor(s) 428 may be configured to execute modules 408-412 and/or other modules via: software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or or other mechanism for configuring processing capabilities on processor(s) 428 . As used herein, the term "module" may refer to any element or collection of elements that performs the functions attributed to the module. This may include one or more physical processors, processor-readable instructions, circuitry, hardware, storage media, or any other element during execution of the processor-readable instructions.

The descriptions of functionality provided by the various modules 408-412 described below are for illustrative purposes and are not intended to be limiting, as any of the modules 408-412 may provide more or less than what is described. Function. For example, one or more of modules 408-412 may be eliminated and some or all of its functionality may be provided by other modules 408-412. As another example, processor 428 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one of modules 408-412 Function.

Figure 5A is a block diagram illustrating components of a relay system 500 for improving QoS in end-to-end network connections, in accordance with various embodiments. Referring to FIGS. 1-5 , relay system 500 may include: 5G relay wireless tethered AR (WLAR) UE 506 that includes 5G WLAR 502 (i.e., includes endpoint UEs (e.g., wireless devices 174, 184)) and intermediary UEs 504 (e.g., UEs 172a, 182a); cloud/edge network 508 communicatively connected to the 5G relay WLAR UE 506 via the 5G network (e.g., 5G core network 172c, 182c); and endpoint servers 510 (eg, application servers 176, 188) that provide AR/MR/XR applications. Endpoint UEs (not shown) may be mapped to 5G WLAR 502, and intermediary UEs 504 may be mapped to 5G relay WLAR UEs 506 along with 5G WLAR 502. Relay system 500 may make decisions regarding non-5G networks such as wireless connections 501 (eg, Wi-Fi communication links 173, 183) and endpoint server network connections 507 (eg, wired communication links 177, 189). QoS information, which can be reported to a network element (for example, network element 402) of the 5G network, measured by the network element, or otherwise determined by the network element for use based on The QoS requirements provided by the 5G network to the 5G WLAR 502 adjust one or more QoS parameters.

The 5G WLAR 502 may be a head-mounted display (HMD) or other types of AR/MR/XR glasses or equipment used to implement AR/MR/XR applications to provide a certain QoE to the user. The 5G WLAR 502 may include the following functional blocks: AR runtime 502a, featherweight scene manager 502b, media client 502c and basic AR/MR/XR application 502d. AR execution 502a may receive sensor information and camera information from various sensors mapped to endpoint devices (eg, wireless devices 174, 184) of 5G WLAR 502. AR execution time 502a may include the following functional blocks: vision engine/SLAM, pose correction, and sound field mapping to generate AR/MR/XR experiences based on AR data received from base AR/MR/XR application 502d and Output this to the 5G WLAR 502's display and speakers. The featherweight scene manager 502b may include the following functional blocks: a basic scene graph handler and a compositor to help the AR execution time 502a generate AR based on the AR data received from the basic AR/MR/XR application 502d /MR/XR experience. The basic AR/MR/XR application 502d can receive user input for selecting various AR/MR/XR applications, features, and options, and the basic AR/MR/XR application 502d can be based on input from the endpoint server 510 User input to request and receive AR/MR/XR data via end-to-end network connections. Media client 502c may include the following functional blocks: scene description delivery, content delivery, and basic codecs. Media client 502c may support media access functionality to support delivery of media content components over end-to-end network connections including 5G network connection 505 and wireless connection 501. In some embodiments, wireless connection 501 may be a Wi-Fi BLE or sidelink connection. Media access capabilities may include 5GMS (5G Media Streaming) capabilities, MTSI (Multimedia Telephony over IMS) capabilities, web connectivity or edge-related client capabilities, and other media access capabilities. For example, the media client 502c can request and receive AR/MR/XR application content information from the media AS 508a-2 of the cloud/edge network 508, and can communicate the AR/MR/XR application content information and related information with the AR execution time 502a. Contact request.

The intermediary UE 504 may act as a relay device to relay IP packets between the 5G WLAR 502 and the cloud/edge network 508 and the endpoint server 510 to allow the 5G WLAR 502 to Execute AR/MR/XR applications. The intermediary UE 504 may include media communication session processing routines 504a that include supporting QoS control on the 5G system (i.e., adjusting QoS parameters to effect changes in QoS provided to the 5G relay WLAR UE 506 ) edge functions. In order to support appropriate QoS for the end-to-end network connection of the relay system 500 , the media communication process 504 a may consider the constraints of the tethered link (i.e., the wireless connection 501 ) to provide over the 5G network connection 505 Sufficient QoS to provide adequate QoS to end users.

The cloud/edge network 508 may include the following functional blocks: media delivery function 508a and AR/MR/XR application 508b. Media delivery function 508a may include the following functional blocks: media application function (AF) 508a-1 and media application server (AS) 508a-2, which may include functional blocks: content delivery, scene description, decoder and encoding device. Media AF 508a-1 may communicate with media communication process 504a of intermediary UE 504 via 5G network connection 505 to establish end-to-end network connectivity of relay system 500, such as pose-to-render to photon (pose- to-render-to-photon) loop 503. Media AS 508a-2 may relay AR/MR/XR content to media client 502c of 5G WLAR 502 via intermediary UE 504. The AR/MR/XR application 508b may include the following functional blocks: AR functionality, semantic perception, social integration, media asset storage, and AR scene manager 508b-1. The AR scene manager 508b-1 may include the following functional blocks: scene graph generator), immersive visual renderer, and immersive audio renderer. Endpoint server 510 may be communicatively coupled to cloud/edge network 508 via endpoint server network connection 507 and may provide updates to the application files to AR/MR/XR application 508b.

The pose-to-render-to-photon loop 503 may be established via the end-to-end network connection shown in Figure 5A. For example, media client 502c, media communication handler 504a, and media delivery function 508a may communicate via wireless connection 501 and 5G network connection 505 to establish a stable and constant communication path as a gesture to render to photon loop 503 . Therefore, gesture-to-render-to-photonic loop 503 may include four wireless links (i.e., two between 5G WLAR 502 and intermediary UE 504, and two between intermediary UE 504 and cloud/edge network 508) for Communicate AR/MR/XR information via end-to-end network connection. For example, the intermediary UE 504 may relay requests for AR/MR/XR information for AR/MR/XR applications from the 5G WLAR 502 to the cloud/edge network 508 via the gesture-to-render to photonic loop 503 . The AR/MR/XR application 508b (i.e., the AR scene manager 508b-1) may receive, process, and Respond to the request.

In some embodiments, network elements within the end-to-end network connection may determine the QoS requirements of the end-to-end network connection. The QoS requirements for an end-to-end network connection may be based in part on the UE's QoS requirements (eg, bandwidth, bit rate, packet error rate, etc.) or data requirements. When a connection is established between a UE located within a non-5G network (e.g., 5G WLAR 502) with an end-to-end network connection and a telecommunications network such as a 5G core network, the UE may be a network within the telecommunications network Element provides QoS requirements outlining the basic profile requirements of the UE. For example, the UE may notify the network element that the UE implements a data streaming video application, and the network element may configure the telecommunications network to provide QoS common in data streaming video services. In some embodiments, the network element may detect the UE's device or application type and may configure the 5G network. Network elements can configure the 5G network based on the UE's QoS requirements to provide universal QoS to endpoint UEs. However, outside the 5G network, within the non-5G network where the endpoint UE is located, the 5G network may not know the actual endpoint QoS. The 5G network may not have visibility and direct control over the non-5G network, and therefore may not be able to optimize the QoS provided to endpoint UEs over the 5G network. For example, a 5G network (configured by a network element) may over-provision QoS to a UE based solely on the QoS requirements received from the UE, thereby providing the UE with excessive resources (e.g., too much bandwidth, bit rate; low packet rate, etc.), thus wasting 5G network resources. As another example, the 5G network (configured by the network elements) may not be able to prepare sufficient QoS for the UE. In this case, users of the endpoint UE may experience poor QoE, but the network elements of the 5G network will not be aware of the poor QoS experienced within the non-5G network. Various embodiments allow network elements of a 5G network to indirectly optimize the QoS experienced by endpoint UEs of the non-5G network based on QoS information provided to the network element from devices or reporting entities within the non-5G network. .

Figure 5B is a message flow diagram illustrating the dialing process that may occur in the relay system architecture shown in Figure 5A. Referring to FIGS. 1A-5B , in this architecture, the intermediary UE 504 is not involved in the processing of media because it acts as a relay between the network and the AR glasses 502 . To ensure the desired end-to-end QoS, the UE 504 monitors and estimates the QoS of the link (eg, Wi-Fi link) with the AR glasses 502, determines the QoS requirements on the 5G system, and issues QoS to the PDU communication period establishment process request. Specifically, launch of an AR application executing AR glasses 502 may begin with the application launching a device discovery message exchange 1 to detect and establish a wireless connection with the intermediary UE 504 . Once a wireless connection is established with the intermediary UE 504, the AR application executing in the AR glasses 502 can initiate an edge exploration request via the media communication period handler 504a ("MSH" in Figure 5B) executed in the intermediary UE 504. Message 2. The intermediary UE 504 may initiate edge discovery and connection message exchange 3 with the edge application server 508 via the user plane function 510 (UPF) of the 5G network via the media communication process 504a.

When a communication connection is established with the edge application server 508, the application executed in the AR glasses 502 can send the media capability message 4 to the edge application server 508 via the connection. Upon receiving notification of the media capabilities of the AR glasses 502 , the edge application server 508 and the AR glasses 502 may exchange split-screen rendering configuration messages 5 for implementation at the edge application server 508 (and possibly the intermediary UE 504 ) The rendering processing tasks are divided among the AR glasses 502 . With this configuration established, applications executing in AR glasses 502 can launch AR applications and messages 6.

To begin supporting AR applications, in operation 7, the intermediary UE 504 may estimate the Wi-Fi link to the AR glasses via the wireless connection to the AR glasses 502 and the connection of the media communication period handler 504a with the user plane function 510 Quality of Service (QoS). Through the connection of the media communication session handler 504a with the user plane function 510, the intermediary UE 504 may communicate in operation 8 a request for QoS levels required to support the AR application and establish protocol data unit (PDU) communication sessions. Thereafter, the AR application executing in the AR glasses 502 can send the camera feed, audio data, and posture information in the data stream 9 to the edge application server 508 , which can use such uploaded data to generate audio. and video AR media, which are downloaded to the AR glasses 502 in the video/audio/scene graph data stream 10 .

6A-6C are component block diagrams illustrating system architectures 600a-600c for improving QoS in end-to-end network connections, according to various embodiments. Referring to Figures 1-6C, the system architecture 600a-600c shown in Figure 6A may include endpoint UEs 602 (eg, wireless devices 174, 184), intermediary UEs 604 (eg, UEs 172a, 182a, intermediary UE 504), gNB 606 (e.g., gNB 172b, 182b), Non-3GPP Interworking Function (N3IWF) 608, User Plane Function (UPF) 610 (e.g., 172d, 182d), and endpoint server 612 (e.g., application server 176, 188 , endpoint server 510). In some embodiments implementing the elements of Figure 5A, endpoint UE 602 can be mapped to 5G WLAR 502, intermediary UE 604 can be mapped to intermediary UE 504, and endpoint UE 602 and intermediary UE 604 can be mapped into 5G Following WLAR UE 506.

System architectures 600a-600c may represent various end-to-end telecommunications network architectures, in which QoS information may be measured and/or recorded by endpoint devices (e.g., endpoint UE 602, endpoint server 612) within the non-5G network and Subsequent reporting from the endpoint device to a network element (e.g., network element 402) within the 5G network (e.g., 5G core network 172c, 182c) for The QoS requirements of the 5G network and the reported QoS information are used to adjust the QoS parameters of the 5G network. Referring to FIGS. 6A to 6C , the network elements may be gNB 606, N3IWF 608, UPF 610, or devices, components, functional blocks or any other entities within the 5G network including gNB 606, N3IWF 608 and UPF 610.

Referring to Figure 6A, endpoint UE 602 may be managed in part by 3GPP (ie, the 3GPP management higher layers) via N3IWF 608. N3IWF 608 may manage endpoint UE 602 in part using interface Y1 between endpoint UE 602 and intermediary UE 604 and interface Y2 between intermediary UE 604 and N3IWF 608. In a system architecture 600a in which endpoint UE 602 is partially managed by 3GPP, endpoint UE 602, intermediary UE 604, or both endpoint UE 602 and intermediary UE 604 may measure, log, or otherwise obtain descriptions of non-5G QoS information about the network's QoS status and attributes. For example, endpoint UE 602 and/or intermediary UE 604 (e.g., via media communication routine 504a) may collect non-5G network (e.g., Wi-Fi) Bluetooth connections between endpoint UE 602 and intermediary UE 604. ) of the QoS information (such as round-trip delay, one-way delay and/or packet error rate) and report the obtained QoS information to the network element of the 5G network (e.g., N3IWF 608).

Referring to Figure 6B, endpoint UE 602 may not be managed by 3GPP, but may be managed independently of 3GPP. In a system architecture 600b in which endpoint UEs 602 are managed independently of 3GPP, intermediary UEs 604 may measure, log, or otherwise obtain QoS information describing the status and attributes of QoS for non-5G networks. For example, intermediary UE 604 (eg, via media communication routine 504a) may notify the 3GPP network of the presence of endpoint UE 602 via a non-3GPP network (eg, Wi-Fi, Bluetooth). Subsequently, the intermediary UE 604 can collect QoS information of non-5G networks (eg, Wi-Fi, Bluetooth connection between the endpoint UE 602 and the intermediary UE 604), and report the obtained QoS information to the network of the 5G network. Path elements such as Media AF 508a-1, Access and Mobility Management Function (AMF) or Policy and Charging Function (PCF). The PCF can control the service agreement and can decide which 5G QoS to provide to the 5G network. The PCF (not shown) can be connected to the AMF (not shown), which in turn can be connected to the media AF 508a-1.

Referring to Figure 6C, endpoint UE 602 may be fully managed by 3GPP. In a system architecture 600a where the endpoint UE 602 is fully managed by 3GPP (eg, via PC5 interface, sidelink), the endpoint UE 602, the intermediary UE 604, or both the endpoint UE 602 and the intermediary UE 604 can measure , record or otherwise obtain QoS information describing the status and attributes of QoS of non-5G networks. For example, endpoint UE 602 and/or intermediary UE 604 (e.g., via media communication routine 504a) may collect non-5G network (e.g., Wi-Fi) Bluetooth connections between endpoint UE 602 and intermediary UE 604. ) of the QoS information, and report the obtained QoS information to the network element of the 5G network (for example, media AF 508a-1, AMF or PCF).

System architectures 600a-600c describe methods for obtaining QoS information of non-5G networks and reporting the obtained QoS information to network elements in the 5G network via reporting entities (e.g., endpoint UE 602, intermediary UE 604). various methods for further processing. In some embodiments, QoS information may include QoS-related information for non-5G networks (e.g., Wi-Fi, BLE, sidelinks), including characteristics such as round-trip time or latency, one-way latency, or packet error rate, or measure. The QoS information may further include a classification of non-5G networks that are part of the end-to-end connection. For example, the classification of network connections may determine whether the non-5G network is a Wi-Fi network (eg, IEEE802.11ad, 802.11ac), BLE, or a wired connection (eg, USB). As another example, the classification of networks may include QoS configurations for non-5G networks (e.g., Wi-Fi), which may be determined by specific access classes under Enhanced Distributed Channel Access (EDCA) (e.g., best effort or video) definition. The QoS information may further include required changes to the QoS provided to the endpoint UE 602 from the 5G telecommunications network. For example, endpoint UE 602 may report required changes to a network element of a 5G network that prepares endpoint UE 602 with a certain level of QoS, and the required changes may include reducing latency (e.g., round trip latency, the amount of delay (e.g., round trip delay, one-way delay) or packet error rate that is allowed without violating the quality of experience (QoE) of the endpoint UE 602 quantity.

QoS information may further include metrics measured between the telecommunications network and the application or endpoint server, including one-way latency from the telecommunications network to the application server, one-way latency from the application server to the telecommunications network, The round trip delay between the telecommunications network and the application server, the packet error rate from the telecommunications network to the application server, and/or the packet error rate from the application server to the telecommunications network. For example, network elements within a 5G core network may measure time delay metrics to and from endpoint servers (eg, endpoint servers 510, 612). Measurements performed by the network element may be active, in which the network element may send probe packets (such as round-trip delay ping messages between the network element and the endpoint server 612) and/or timestamp messages to determine Round trip delay and/or one way delay. For example, network elements within the 5G core network may generate timestamp messages with a timestamp indicating the starting time (To).

In response to receiving a timestamp message from the network element indicating To, endpoint server 612 may generate a timestamp reply message having a timestamp for the time of receipt (Tr). The timestamp reply message may also include a timestamp indicating To and a timestamp for the sending time (Tt) of the timestamp reply message. The endpoint server 612 may then send the timestamp reply message to the network element within the 5G core network that originally sent the timestamp message including To.

In response to receiving the timestamp reply message from the endpoint server 612, the network element may generate a timestamp indicating the receipt or final time (Tf). The network element can then calculate either: (i) the one-way delay from the network element within the 5G core network to the endpoint server 612 (i.e., one-way delay = Tr – To); (i) 2) The one-way delay from the endpoint server 612 to the network element (i.e., one-way delay = Tf – Tt); (3) The round-trip delay between the network element and the endpoint server 612 (i.e., Round trip delay = Tf – To, or Tf – Tt + Tr – To). In some embodiments, measurement of round-trip latency and/or one-way latency may be performed passively by recording local timestamps of delivery packets and corresponding return packets. In some embodiments, measurement of the time delay between network elements and endpoint server 612 may be performed by network entities such as media AF 508a-1, media AS 508a-2, and/or UPF 610.

QoS information may further include information about applications executing on endpoint UE 602, such as video codecs, audio codecs, bit rates, frame rates, latency (e.g., for rendering, for detection posture changes), or QoS requirements (e.g., regarding transmission volume and/or latency). QoS information may further include information about network traffic, such as whether traffic is symmetrical between uplink and downlink, whether uplink traffic is dominated by light commands and gestures but has strict latency requirements, and whether downlink traffic is Whether the traffic is mainly multimedia content but the delay requirements are not strict. For example, QoS information including application information and/or traffic information may be obtained via various system architectures 600a-600c (eg, 5G relay WLAR UE 506), and may subsequently be obtained via media communication routine 504a and/or media Client 502c is reported to network elements within the 5G network.

QoS information may further include endpoint UE 602 and renderer functions hosted for augmented reality (AR), mixed reality (MR), or extended reality (XR) applications (eg, intermediary UE 604, endpoint server 612) time delay between devices.

Figure 7A is a block diagram illustrating components of a split-screen rendering system 700 for improving QoS in end-to-end network connections, in accordance with various embodiments. In a split-screen rendering architecture, non-5G network QoS information (such as the time delay between multiple devices performing rendering operations for the same output) can be used by network elements to better optimize the QoS parameters of the 5G network. Optimize the QoS experienced by non-5G networks within end-to-end connections.

Referring to Figures 1-7A, a split-screen rendering system 700 may include a 5G split-screen rendering wireless tethered AR (WLAR) UE 706 that includes an endpoint UE 702 (eg, wireless devices 174, 184, endpoint UE 602), Intermediary UE 704 (e.g., UE 172a, 182a, intermediary UE 504, 604); 5G system 708 communicatively connected to 5G split-screen rendering WLAR UE 706 via a 5G network (e.g., 5G core network 172c, 182c); and endpoint servers 710 (eg, application servers 176, 188, endpoint servers 510, 612) that provide AR/MR/XR applications. The endpoint UE 702 and the intermediary UE 704 can be mapped together to the 5G split screen rendering WLAR UE 706. System 700 may make decisions regarding non-5G networks, such as wireless connections 701 (e.g., Wi-Fi communication links 173, 183, wireless connections 501) and endpoint server network connections 707 (e.g., wired communication links 177, 189 , endpoint server network connection 507)), the QoS information may be reported to, measured by, a network element of the 5G network (e.g., network element 402), or measured by the network element. The path elements are otherwise determined for adjusting one or more QoS parameters based on the QoS requirements provided to the endpoint UE 702 by the 5G network.

The endpoint UE 702 may be an HMD or other type of AR/MR/XR glasses or a device used to implement AR/MR/XR applications to provide a certain QoE to the user. Endpoint UE 702 may include the following functional blocks: basic AR execution time 702a, featherweight scene manager 702b, and tethering functionality 702c. The basic AR execution time 702a may receive sensor information and camera information from various sensors of the endpoint UE 702. Basic AR execution 702a may include the following functional blocks: Vision engine/SLAM and pose correction to generate AR/MR/ XR experience and output it to the endpoint UE 702’s display and speakers. Featherweight scene manager 702b may include the following functional blocks: basic applications and compositors to help AR execution 702a generate AR/MR/XR experiences based on AR data received from another rendering device via tethering function 702c. Tethered function 702c may receive user input for selecting various AR/MR/XR applications, features and options, and base AR execution 702a may receive user input from an endpoint server via a peer-to-peer network connection based on the user input. 710 and/or another rendering device requests and receives AR/MR/XR data. Tethering functionality 702c may include the following functional blocks: content delivery and basic codecs. Tethering function 702c may support wireless communication functions to support delivery of media content components over end-to-end network connections including 5G network connection 705 and wireless connection 701. For example, the tethering function 702c may request and receive rendered AR/MR/XR application content information from the AR scene manager 704c of the intermediary UE 704 (i.e., the intermediary UE is performing rendering processing to be used in a split-screen rendering application) , and can communicate AR/MR/XR application content information and associated requests with the AR execution time 702a.

Intermediary UE 704 may act as a device that hosts a renderer application to render data that may be used in conjunction with application data rendered by endpoint UE 702. Intermediary UE 704 may include the following functional blocks: tethering function 704a, AR execution time 704b, AR scene manager 704c, media access function 704d, and AR/MR/XR application 705e. Tethering function 704a may include the functional blocks of content delivery, decoders and encoders to relay AR/MR/XR information to tethering function 702c of endpoint UE 702 via wireless connection 701 . The AR execution time 704b may include the following functional blocks: visual engine/SLAM, visual mapping, and sound field mapping to render AR/MR/XR content that can be used by the endpoint UE 702 to generate and output an AR/MR/XR experience. Display and speakers to endpoint UE 702. The AR scene manager 704c may include the following functional blocks: scene graph processing routines, compositors, immersive visual renderers, and immersive audio renderers to facilitate the AR execution 704b based on the input received from the AR/MR/XR application 702e AR data to generate split-screen rendered AR/MR/XR content experiences. AR/MR/XR application 702e can receive user input for selecting various AR/MR/XR applications, features and options, and AR/MR/XR application 702e can connect via a peer-to-peer network based on the user input Request and receive AR/MR/XR data from endpoint server 710. Media access function 704d may include the following functional blocks: media communication process routine 704d-1 and media access function 704d-2. Media client 704d-2 may include the following functional blocks: 2D codec, scene description delivery, immersive media decoder, and content delivery. Media access functionality 704d may support media access functionality to enable requesting and delivering media content components via end-to-end network connections including 5G network connections 705. For example, media communication handler 704d-1 and media client 704d-2 may include functionality to support establishing a 5G network connection with 5G system 708 (ie, with media AF 708a and media AS 708b of 5G system 708).

The 5G system 708 may include the following functional blocks: media AF 708a and media AS 708b. The media AF 708a and the media AS 708b can communicate AR/MR/XR application information from the endpoint server 710 to the intermediary UE 704 and/or the endpoint UE 702 to perform the split-screen rendering process.

Endpoint server 710 may be communicatively coupled to 5G system 708 via endpoint server network connection 707 and may provide updates to AR/MR/XR applications 704e to application files that may be distributed to various elements of intermediary UE 704. In some embodiments, the endpoint server 710 can host a renderer application and can perform a split-screen rendering process to generate AR/MR/XR content that can be combined with the AR/MR/XR content rendered by the endpoint UE 702 Apply content combinations to output a complete AR/MR/XR experience. For example, endpoint server 710 may include the following functional blocks: AR function 710a and AR scene 710b, which may perform basic AR execution 702a and featherweight scene manager 702b with endpoint UE 702 and intermediary UE 704 The AR execution time 704b and the AR scene manager 704c have similar AR/MR/XR rendering functions.

The pose-to-render-to-photon loop 703 may be established via the end-to-end network connection shown in Figure 7A. For example, tether function 702c may communicate via wireless connection 701 to establish a stable and constant communication path as a gesture to render to photon loop 703. Thus, gesture-to-render-to-photon loop 703 may include two wireless links (ie, two between endpoint UE 702 and intermediary UE 704 ) for communicating split-screen rendering AR/MR/XR via wireless connection 701 information. For example, endpoint UE 702 may send gesture information (eg, 3D orientation, accelerometer information, additional sensor information) to intermediary UE 704 via gesture-to-render-to-photon loop 703 . The AR scene manager 704c receives the gesture information and, in response, generates split-screen rendered AR/MR/XR data corresponding to the gesture information and sends it to the endpoint UE 702 via the gesture-to-render-to-photon loop 703 for development. Complete AR/MR/XR experience. In some embodiments where the endpoint server 710 may host split-screen rendering functionality, the pose-to-render-to-photon loop 703 may extend through the 5G network connection 705 to allow for Split-screen rendering requests (ie, from endpoint UE 702) and content (ie, from intermediary UE 704 and/or endpoint server 710) are transmitted.

In some embodiments, obtaining, calculating, or otherwise determining the relationship between an endpoint UE 702 (eg, a rendering device such as glasses, HMD, etc.) and a device hosting renderer functionality (i.e., an intermediary UE 704, an endpoint server 710) can be used by network elements of the 5G network to improve the QoS of the non-5G network within the end-to-end connection (ie, from the endpoint UE 702 to the endpoint server 710). Based on the QoS information including the latency between the endpoint UE 702 and the device hosting the renderer function, the network element can adjust the QoS parameters of the 5G network to achieve optimal changes within the 5G network, thereby indirectly providing 5G networks provide improved or adequate QoS.

In some embodiments, transmission latency may be measured by the endpoint UE 702 based on round-trip time measurements between the endpoint UE 702 and the device hosting the renderer (i.e., intermediary UE 704, endpoint server 710), Or it can be based on one-way delay measurements with the help of timestamps. In some embodiments, transmission delay may be measured by network elements located in or processing with the 5G network and closest to the endpoint UE 702 (eg, as an intermediary UE 704 operating as a 5G phone). In some embodiments, a device measuring latency (eg, endpoint UE 702 or intermediary UE 704) may report the measured latency to network elements within the 5G core network and/or to host split screens. Rendering-capable devices. Delay ("D") can be used by the device hosting the renderer function to predict the time corresponding to the rendered content (e.g., video, audio), so that any content rendered by the split-screen rendering device can be processed in time. The rendered content is sent to the endpoint UE 702 so that the endpoint UE 702 can produce a complete AR/MR/ by combining the received rendered content with the corresponding content rendered locally by the endpoint UE 702 XR experience. For example, a device hosting a renderer function can predict a pose "x" seconds into the future and render content in preparation for that pose, where x = rendering latency (i.e., time to render content) + D + display latency (i.e., endpoint UE 702 display delay). In some embodiments, delays may be relayed or reported to network elements of the 5G network to determine whether the QoS parameters of the 5G network can be adjusted to facilitate reduced delays "D" or where longer delays can be tolerated "D ” reallocating 5G network resources without affecting the QoE observed by the user of the endpoint UE 702.

In some embodiments implementing a system 700 that includes a 5G split-screen rendering wireless tethered AR (WLAR) UE 706, in order to determine the latency between the endpoint device and the device hosting the renderer, the endpoint device may be mapped to the endpoint device. Point UE 702, and the device hosting the renderer can be mapped to an intermediary UE 704 (eg, a 5G phone). Accordingly, the intermediary UE 704 can receive delay information from the endpoint UE 702 and can relay the delay information to network elements within the 5G network, as described with reference to Figures 6A-6C. For example, latency may be reported to network elements in a system implementing system architecture 600a, where endpoint UE 602 (eg, 702) is partially managed by 3GPP via N3IWF 608. As another example, latency may be reported to network elements in a system implementing system architecture 600b, where endpoint UE 602 (eg, 702) is managed independently of 3GPP. As yet another example, latency may be reported to network elements in a system implementing system architecture 600c, where endpoint UE 602 (eg, 702) is managed entirely by 3GPP via PC5 sidelinks.

In some embodiments implementing a relay system 500 that includes a 5G relay wireless tethered AR (WLAR) UE 506, in order to determine the latency between the endpoint device and the device hosting the renderer, the endpoint device may be mapped to 5G WLAR 502, and the device hosting the renderer can be mapped to the cloud/edge (eg, cloud/edge network 508, endpoint server 510). Accordingly, the cloud/edge hosting the renderer can receive latency information from the 5G WLAR 502 and can relay the latency information to network elements within the 5G network, as described with reference to Figures 6A-6C. For example, latency may be reported to network elements in a system implementing system architecture 600a where endpoint UE 602 (eg, 502) is managed in part by 3GPP via N3IWF 608. As another example, latency may be reported to network elements in a system implementing system architecture 600b, where endpoint UE 602 (eg, 502) is managed independently of 3GPP. As yet another example, latency may be reported to network elements in a system implementing system architecture 600c, where endpoint UE 602 (eg, 502) is managed entirely by 3GPP via PC5 sidelinks.

In various embodiments, network elements within the telecommunications network may be based on the QoS requirements of the endpoint UE (eg, 5G WLAR 502, endpoint UE 602, endpoint UE 702) and from the same end-to-end endpoint as the telecommunications network. The QoS information obtained by the non-5G network within the network connection is used to adjust the QoS parameters of the telecommunications network communication network. Adjusting QoS parameters may include configuring the 5G network to: affect the QoS observed within the non-5G network; improve the QoS of the non-5G network based on received QoS information and QoS requirements, or decide on fewer 5G resources Less resources will be allocated to the endpoint UE after it will be sufficient and the QoE observed at the endpoint UE will not be negatively affected by resource reallocation. In some embodiments, adjusting QoS parameters may include adjusting the 5QI of the 5G network.

7B is a message flow diagram illustrating the dialing process that may occur in the relay system architecture shown in FIG. 7A. Referring to Figures 1A-7B, in this architecture, media session processing (MSH) 704 executed in the intermediary UE 704 handles edge exploration. The link between the AR glasses 702 and the intermediary UE 704 may be a Wi-Fi link as shown in the figure, but may also be a 3GPP side link via the PC5 interface. The 5G system represented by User Plane Function (UPF) 708 is involved at the beginning of the dialing process in message exchanges 2 to 4. The edge discovery process is shown as being application driven, but it could be network driven (in which case edge discovery request message 2 could be omitted). After the media software has been downloaded in message exchange 4, all processing and communication can take place between the AR glasses 702 and the intermediary UE 704.

Specifically, launch of an AR application executing mediating UE 704 may begin with a device discovery message exchange 1 between tethering function 704a executing in UE 714 and AR glasses 702 to establish a wireless connection between the two devices. Once a wireless connection is established with the AR glasses 702, the AR application 704b executing in the intermediary UE 704 can initiate an edge exploration request to the media communication period handler 704d ("MSH" in Figure 7B) executing in the intermediary UE 704. 2. The intermediary UE 704 may initiate edge discovery and connection message exchange 3 with the edge application server 710 via the user plane function 708 (UPF) of the 5G network via the media communication process 704a.

When a communication connection is established with the edge application server 710, the application 704b executing in the intermediary UE 704 downloads media software from the edge application server 710 via the user plane function 708 in message exchange 4.

At this time, the AR glasses 702 may send the media capability message 5 to the application 704b executing in the intermediary UE 704. With the AR glasses informed of the media capabilities, the application 704b executing in the intermediary UE 704 and the AR glasses 702 may exchange functional split-screen negotiation messages 6 to communicate between the AR glasses 702 and the application 704b executing in the intermediary UE 704. Realize the division of rendering processing tasks. As an example of functional split-screening, intermediary UE 704 may request use of the display of AR glasses 702 .

With a split-screen configuration established, application 704b executing in intermediary UE 704 can initiate AR application message 7. Thereafter, AR glasses 702 can send camera feeds, audio data, and gesture information in data stream 8 to application 704b executing in intermediary UE 704, which application 704b can use such uploaded data to generate audio and video AR media, The media is downloaded to the AR glasses 702 in the video/audio/scene image data stream 9 .

8 is a process flow diagram illustrating an embodiment method 800 for improving QoS in an end-to-end network connection including a first communications network and a second communications network, in accordance with various embodiments. Referring to Figures 1-8, method 800 may be implemented in a processor (eg, processor 212, 214, 216, 218, 252, 260, 428) configured to perform the operations of the method. In various embodiments, a processor (eg, processors 212 , 214 , 216 , 218 , 252 , 260 , 428 ) may be configured to store data on a non-transitory processor-readable medium (eg, memory device 220 , 258, the processor in the electronic storage device 426) can execute instructions to perform operations. The component for performing each operation of method 800 may be a processor of wireless modem system 200 and/or network element 402, such as processors 212, 214, 216, 218, 252, 260, 428, etc.

In block 802, network elements within the end-to-end network connection may determine QoS requirements for the end-to-end network connection. In various embodiments, network elements (eg, network element 402) may be based on endpoint UEs (eg, wireless devices 174, 184, endpoint UE 602) located within a second network (eg, a non-5G network) , 702) to determine the QoS requirements for end-to-end network connections. In some embodiments, determining the QoS requirements of the end-to-end network connection by the network elements within the end-to-end network connection may include: determining the end-to-end network element based on the service agreement, application type, or user request. QoS requirements for network connections. In some embodiments, the first communication network may be a 5G network (eg, 5G core networks 172c, 182c), and the second communication network may not be a 5G network (ie, a non-5G network). Means for performing the operations of each of block 802 may include processors of wireless modem system 200 and/or network element 404, such as processors 212, 214, 216, 218, 252, 260, 428, etc.

In block 804, the network element may obtain QoS information of the second communication network from a reporting entity within the second communication network. In various embodiments, a network element (eg, network element 402) may obtain information from a reporting entity (eg, wireless device 174, 184, endpoint UE 602, 702) within a second communications network (eg, a non-5G network) , UE 172a, 182a, intermediary UE 504, 604, 704, application server 176, 188, endpoint server 510, 612, 710) receive, determine or otherwise obtain QoS information.

In some embodiments, the QoS information may include at least one of the following: round-trip delay of the end-to-end network connection, one-way delay of the end-to-end network connection, or packet error rate provided to the reporting entity. In some embodiments, the QoS information may include the classification of the second communication network. In some embodiments, the QoS information may include a request message indicating a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or a requested change in packet error rate provided to the reporting entity . In some embodiments, the QoS information may include at least one of application information or traffic information.

In some embodiments, obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network may include: measuring the first communication network (for example, 5G core network 172c, 182c) and the second communication network. Latency between endpoint servers within the communications network (e.g., application servers 176, 188, endpoint servers 510, 612, 710). In some embodiments, the network element may be located in the second communication network, and obtaining the QoS information of the second communication network from the reporting entity in the second communication network by the network element may include: measuring the reporting entity and the network element delay between. In some embodiments, the network element may be located within a third communication network (eg, a non-5G network) that is communicatively connected to the second communication network via the first communication network, and the network element may access data from within the second communication network by the network element. The reporting entity obtaining the QoS information of the second communication network may include: measuring the delay between the reporting entity and the network element. In some embodiments, the network element may be located in the first communication network, and obtaining the QoS information of the second communication network from the reporting entity in the second communication network by the network element may include measuring the relationship between the reporting entity and the network element. delay between.

Means for performing the operations of each of blocks 804 may include processors of wireless modem system 200 and/or network element 404, such as processors 212, 214, 216, 218, 252, 260, 428, etc.

In block 806, the network element may adjust QoS parameters of the first communications network based on the determined QoS requirements and the obtained QoS information. In various embodiments, a network element (eg, network element 402) may adjust the first communications network (eg, 5G core network 172c) based on the QoS requirements determined in block 802 and the QoS information obtained in block 804. , 182c) QoS parameters. In some embodiments, the network element adjusting the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information may include: adjusting the 5G QoS parameters of the first communication network by the network element (for example, 5QI). Means for performing the operations of each of blocks 806 may include processors of wireless modem system 200 and/or network element 404, such as processors 212, 214, 216, 218, 252, 260, 428, etc.

The order of the operations performed in blocks 802-806 is illustrative only, and in some embodiments, the operations of blocks 802-806 may be performed in any order and partially concurrently. In some embodiments, method 800 may be performed by a processor of the device independent of, but in conjunction with, an external memory device. For example, method 800 may be implemented as a software module executing within a processor of the SoC or in dedicated hardware within the SoC that issues commands to establish a secure memory channel and access memory of an external memory device. body and otherwise configured to act and store data as generally described.

9 is a process flow diagram illustrating an embodiment method 900 for improving QoS in an end-to-end network connection including a first communication network and a second communication network, which method may be used as a component of the method 800, according to some embodiments. part to implement. Referring to Figures 1-9, method 900 may be implemented in a processor (eg, processor 212, 214, 216, 218, 252, 260, 428) configured to perform the operations of the method. In various embodiments, a processor (eg, processors 212 , 214 , 216 , 218 , 252 , 260 , 428 ) may be configured to store data on a non-transitory processor-readable medium (eg, memory device 220 , 258, the processor in the electronic storage device 426) can execute instructions to perform operations. The components used to perform each operation of method 800 may be wireless modem system 200, network element 402, or reporting entity (e.g., wireless device 174, 184, endpoint UE 602, 702, UE 172a, 182a, intermediary UE 504 , 604, 704, application servers 176, 188, endpoint servers 510, 612, 710) processors, such as processors 212, 214, 216, 218, 252, 260, 428, etc.

In block 902, the reporting entity may measure QoS information. In particular, reporting entities (e.g., wireless devices 174, 184, endpoint UEs 602, 702, UEs 172a, 182a, intermediary UEs 504, 604, 704, application servers 176, 188, endpoint servers 510, 612, 710 ) may measure, record and/or otherwise determine QoS information for end-to-end network connections including non-5G networks. The reporting entity may then send the QoS information from the second communication network (eg, non-5G network) to the network element (eg, network element 402) within the first communication network (eg, 5G core network 172c, 182c) ). The components used to perform the operations in block 902 may be the wireless modem system 200, network element 402, or reporting entity (e.g., wireless device 174, 184, endpoint UE 602, 702, UE 172a, 182a, intermediary UE 504, 604, 704, application servers 176, 188, endpoint servers 510, 612, 710), such as processors 212, 214, 216, 218, 252, 260, 428, etc.

After performing the operations in block 902, the system may perform the operations in block 802 of the method 800 (FIG. 8).

Figure 10 is a block diagram of components of a network element device suitable for use with various embodiments. Network elements (e.g., 402) of such network element equipment (e.g., core network 140 or 5G networks 151a, 161a, 171a, and 181a, base station equipment (such as base stations 110a-110d, 200, 350), etc. ) may include at least the elements shown in Figure 10. Referring to FIGS. 1-10 , a network element device 1000 may generally include a processor 1001 coupled to volatile memory 1002 and a large-capacity non-volatile memory such as a disk drive 1008 . Network element device 1000 may also include a peripheral memory access device 1006 such as a floppy disk, compact disc (CD) or digital video disc (DVD) drive coupled to processor 1001 . Network element device 1000 may also include a network access port 1004 (or interface) coupled to processor 1001 for establishing connections with a network (such as the Internet or a local area network coupled to other system computers and servers). data connection. Network element device 1000 may include one or more antennas 1007 for transmitting and receiving electromagnetic radiation that may be coupled to a wireless communication link. Network element device 1000 may include additional access ports such as USB, Firewire, Thunderbolt, etc. for coupling to peripherals, external memory, or other devices.

Figure 11 is a block diagram of components of a wireless device 1100 suitable for use with various embodiments. In some embodiments, wireless device 1100 may operate as a network element. Referring to Figures 1-11, various embodiments may be implemented on various wireless devices 1100 (eg, wireless devices 120a-120e, 200, 320, 404), an example of which is illustrated in Figure 11 in the form of a smartphone. Wireless device 1100 may include a first SOC 202 (eg, SOC-CPU) coupled to a second SOC 204 (eg, a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to internal memory 1116, display 1112, and speakers 1114. Additionally, wireless device 1100 may include an antenna 1104 for transmitting and receiving electromagnetic radiation, which may be connected to a transceiver 427 coupled to one or more processors in first SOC 202 and/or second SOC 204 . Wireless device 1100 may include a menu selection button or rocker switch 1120 for receiving user input.

Wireless device 1100 Wireless device 1100 may include voice encoding/decoding (CODEC) circuitry 1110 that digitizes voice received from a microphone into data packets suitable for wireless transmission, and decodes the received voice data packets to generate analog signal, this analog signal is provided to the speaker to produce sound. One or more processors in first SOC 202 and second SOC 204, wireless transceiver 266, and CODEC 1110 may include digital signal processor (DSP) circuitry (not separately shown).

The processor of network element device 1000 and wireless device 1100 may be any programmable microprocessor, microcomputer, or multi-processor chip that may be configured by software instructions (applications) to perform various functions, including some of the embodiments described below function). In some wireless devices, multiple processors may be provided, such as one processor within SOC 204 dedicated to wireless communication functions and one processor within SoC 202 dedicated to executing other applications. Software applications may be stored in memory 1002, 1116 before being accessed and loaded into the processor. The processor may include internal memory sufficient to store application software instructions.

The various embodiments shown and described are provided by way of example only to illustrate the various features of the claims. However, features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. Furthermore, the claims are not intended to be limited to any one exemplary embodiment. For example, one or more of the operations of methods 800 and 900 may replace or be combined with one or more of the operations of methods 800 and 900.

Example implementations are described in the following paragraphs. Although some of the following implementation examples are described in terms of example methods, other example implementations may include: the example methods discussed in the following paragraphs implemented by a base station including a processor configured with A processor executable with instructions to perform operations of the methods of the following embodiment examples; an exemplary method implemented by a base station, discussed in the following paragraphs, the base station including means for performing the functions of the methods of the following embodiment examples; and the exemplary methods discussed in the following paragraphs that may be implemented as a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being The processor of the base station is configured to perform operations of the methods of the following implementation examples.

Example 1. A method for improving quality of service (QoS) in an end-to-end network connection including a first communication network and a second communication network, the method comprising: connecting a network within the end-to-end network connection The element determines the QoS requirements of the end-to-end network connection; the network element obtains the QoS information of the second communication network from the reporting entity in the second communication network; and the network element based on the determined QoS requirements and the obtained QoS information to adjust the QoS parameters of the first communication network.

Example 2. The method of Example 1, wherein the first communication network is a 5G network, and the second communication network is not a 5G network.

Example 3. The method of any one of examples 1 or 2, wherein the reporting entity is a device within the second communication network, and the network element is a device within the first communication network, the method further comprising measuring via the reporting entity The QoS information, wherein the network element obtains the QoS information of the second communication network from the reporting entity in the second communication network includes the network element receiving the QoS information from the reporting entity.

Example 4. The method of any one of examples 1 or 2, wherein the QoS information includes at least one of the following: round-trip delay of the end-to-end network connection, one-way delay of the end-to-end network connection, or provided for reporting The entity's packet error rate.

Example 5. The method of any one of Examples 1 or 2, wherein the QoS information includes a classification of the second communication network.

Example 6. The method of any one of examples 1 or 2, wherein the QoS information includes a request message indicating a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or providing Requested changes to the reporting entity's packet error rate.

Example 7. The method of any one of Examples 1 or 2, wherein the QoS information includes at least one of application information or service information.

Example 8. The method of any one of examples 1 or 2, wherein obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes measuring the first communication network and the second communication network. Delay between endpoint servers within.

Example 9. The method of any one of Examples 1 to 8, wherein the network element is located in the second communication network, and the QoS information of the second communication network is obtained by the network element from the reporting entity in the second communication network, including Measure the latency between reporting entities and network elements.

Example 10. The method of any one of examples 1 to 8, wherein the network element is located within a third communication network communicatively connected to the second communication network via the first communication network, and by the network The element obtains the QoS information of the second communication network from the reporting entity in the second communication network including measuring the delay between the reporting entity and the network element.

Example 11. The method of any one of Examples 1 to 8, wherein the network element is located in the first communication network, and the network element obtains the QoS information of the second communication network from the reporting entity in the second communication network including Measure the latency between reporting entities and network elements.

Example 12. The method of any one of examples 1 to 8, wherein determining the QoS requirements of the end-to-end network connection by a network element within the end-to-end network connection includes determining the QoS requirements of the end-to-end network connection by the network element based on the service agreement, application type Or the user requests to determine the QoS requirements of the end-to-end network connection, and the network element adjusts the QoS parameters of the first communication network based on the determined QoS requirements and the obtained QoS information, including adjusting the first communication network by the network element 5G QoS parameters of the road.

As used in this context, the terms "component," "module," "system" and the like are intended to include computer-related entities such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software executing , which is configured to perform a specific operation or function. For example, an element may be, but is not limited to, a process executing on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of example, both the application executing on the wireless device and the wireless device may be referred to as elements. One or more elements may reside within a program or thread of execution, and an element may be localized on one processor or core or distributed between two or more processors or cores. Additionally, such elements may execute from a variety of non-transitory computer-readable media having various instructions or data structures stored thereon. Components may communicate via local or remote processes, function or procedure calls, electronic signals, data packets, memory reads/writes, and other known network, computer, processor, or process-related communication methods.

A variety of different cellular and mobile communications services and standards are available or anticipated in the future, all of which may implement and benefit from various embodiments. Such services and standards include: for example, the 3rd Generation Partnership Project (3GPP), the Long Term Evolution (LTE) system, the 3rd generation wireless mobile communication technology (3G), the 4th generation wireless mobile communication technology (4G), the 5th generation wireless mobile communication technology The first generation wireless mobile communication technology (5G) and the subsequent generation 3GPP technology, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, Universal Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) system (e.g., cdmaOne, CDMA1020TM), Enhanced Data Rates for GSM Evolution (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136/TDMA), Evolved Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Worldwide Interoperability for Microwave Access (WiMAX), Wireless Local Area Network (WLAN), Wi-Fi Protected Access I&II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). Each of these technologies involves the sending and receiving of, for example, voice, data, signaling and/or content messages. It should be understood that any reference to terminology and/or technical details related to a single telecommunications standard or technology is for illustrative purposes only and is not intended to limit the scope of the claim to a particular communications system or technology, except in the claim language. stated in detail.

The foregoing method descriptions and process flow diagrams are provided as illustrative examples only, and are not intended to require or imply that the operations of the various embodiments must be performed in the order presented. As those skilled in the art will appreciate, the sequence of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter," "thereafter," "next" and the like are not intended to limit the order of operations; such words are used to guide the reader through the description of the method. Furthermore, any reference to a claim element in the singular, such as by use of the articles "a", "an" or "the" shall not be construed as limiting that element to the singular.

The various illustrative logical blocks, modules, components, circuits, and algorithm operations described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Skilled artisans may implement the described functionality in various ways for each particular application, but such embodiment decisions should not be interpreted as causing a departure from the scope of the claims.

Hardware for implementing the various illustrative logic, logic blocks, modules and circuits described in connection with the embodiments disclosed herein may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC) ), field programmable gate array (FPGA) or other programmable logic devices, individual gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative the processor may be any general processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of receiver smart objects, such as a combination of a DSP and a microprocessor, a combination of a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such Class configuration. Alternatively, some operations or methods may be performed by circuitry specific to a given function.

In one or more embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. The operations of the methods or algorithms disclosed herein may be embodied in processor-executable software modules or processor-executable instructions, which may reside on a non-transitory computer. or processor-readable storage medium. Non-transitory computer-readable or processor-readable storage media can be any storage media that can be accessed by a computer or processor. By way of example, and not limitation, such non-transitory computer-readable or processor-readable storage media may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage devices, magnetic storage devices, or Other magnetic storage smart objects, or any other media that can be used to store the required program code in the form of instructions or data structures that can be accessed by a computer. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs typically reproduce data magnetically. Lasers reproduce data optically. Combinations of the above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operations of a method or algorithm may reside on a non-transitory processor-readable storage medium and/or a computer-readable storage medium as one or any combination or set of code and/or instructions, which may be combined into computer program products.

The foregoing description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the claimed claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the claims. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.

100:Communication system 102a: Macrocell service area 102b: Pico Cell Service Area 102c: Femtocell service area 110a: Macro BS 110b: Weiwei BS 110c: femto BS 110d: Relay BS 120a: Wireless equipment 120b: Wireless equipment 120c: Wireless equipment 120d: Wireless equipment 120e: Wireless equipment 122: Wireless communication link 124:Wireless communication link 126: Wired or wireless communication link 130:Network controller 140:Communication network 150:Communication system 151a:5G network 151b: Non-5G network 152a:UE 152b:gNB 152c:5G core network 152d:User plane function 153: Cellular communication link 154:Internet 156:Wi-Fi access point 157:Wi-Fi wireless communication link 158:Wireless equipment 160:Communication system 161a:5G network 161b: Non-5G network 162a:UE 162c:5G core network 162d:User plane function 163: Cellular communication link 164:Internet 166a:4G network 166b:eNB 167:4G wireless communication link 168:Wireless devices 170:Communication system 171a:5G network 171b: First non-5G network 171c: Second non-5G network 172a: Wireless equipment (UE) 172b:gNB 172c:5G core network 172d:User plane function 173:Wi-Fi communication link 174:Wireless equipment 175: Cellular Communication Link 176:Application Server 177:Wired communication link 180:Communication system 181a:5G network 181b: The first non-5G network 181c: Second non-5G network 182a: Wireless equipment (UE) 182b:gNB 182c:5G core network 182d:User plane function 183:Wi-Fi communication link 184:Wireless equipment 185: Cellular communication link 186:Internet 187:Wired communication link 188:Application Server 189:Wired communication link 200:Wireless modem system 202:First SOC 204:Second SOC 206:Clock 208:Voltage regulator 210:Digital signal processor (DSP) 212: Modem processor 214: Graphics processor 216:Application processor 218: Auxiliary processor 220:Memory 222:Customized circuit 224: System components and resources 230:Temperature sensor 232:Thermal Management Unit 234:Thermal Power Envelope (TPE) Element 250:Interconnect/Bus Module 252: Processor 254:Power management unit 256: Millimeter Wave (mmWave) transceiver 258:Memory 260:Additional processor 264:Interconnect/Bus Module 266:Wireless transceiver 300:Software Architecture 302: Non-access layer (NAS) 304: Access layer (AS) 306:Physical layer (PHY) 308:MAC sublayer 310: Radio Link Control (RLC) sublayer 312: Packet Data Convergence Protocol (PDCP) sublayer 313:RRC sublayer 314: Host layer 317: Service Data Adaptation Protocol (SDAP) 320:Wireless equipment 350:Base station 400:System 402:Network elements 406: Machine-readable instructions 408: End-to-end QoS module 410:QoS acquisition module 412:QoS adjustment module 424:Communication network 426: Electronic storage device 428: Processor 500:Relay system 501: Wireless connection 502:5GWLAR 502a: AR execution time 502b: Featherweight Scenario Manager 502c: Media client 503: Pose to Render to Photon Loop 504: Intermediary UE 504a: Media communication period processing routines 505:5G network connection 506:5G Relay WLARUE 507: Endpoint server network connection 508:Cloud/edge network 508a:Media AS 508a-1: Media Application Function (AF) 508a-2: Media Application Server (AS) 508b:AR/MR/XR applications 508b-1:AR scene manager 510:Endpoint server 600a: System Architecture 600b: System Architecture 600c: System Architecture 602: Endpoint UE 604: Intermediary UE 606:gNB 608:N3IWF 610:UPF 612:Endpoint server 700: Split screen rendering system 701:Wireless connection 702: Endpoint UE 702a: Basic AR execution time 702b: Featherweight scene manager 702c: Tethering function 703: Pose to Render to Photon Loop 704: Intermediary UE 704a: Media communication period processing routine 704b: Application 704c:AR scene manager 704d:Media access function 704d-1: Media Communication Period Processing Routines 704d-2:Media access function 704e: AR/MR/XR applications 705:5G network connection 706: 5G split-screen rendering wireless tethered AR (WLAR) UE 707: Endpoint server network connection 708:5G system 708a:Media AF 708b:Media AS 710: Endpoint Server 800:Method 802: Operation 804: Operation 806: Operation 900:Method 902: Operation 1000:Network element device 1001: Processor 1002:Memory 1004:Network access port 1006: Peripheral memory access device 1007:Antenna 1008: Disk drive 1100:Wireless devices 1104:antenna 1110: Sound encoding/decoding (CODEC) circuit 1112:Display 1114: Speaker 1116: Internal memory 1120: Menu selection button/rocker switch L1: Layer 1 L2: Layer 2 L3: Layer 3 Y1:Interface Y2:Interface

1A is a system block diagram illustrating an exemplary communications system 100 suitable for implementing any of the various embodiments.

1B-1E are system block diagrams illustrating exemplary communications systems suitable for implementing any of the various embodiments.

2 is a block diagram illustrating elements of an exemplary computing and wireless modem system suitable for implementing any of the various embodiments.

3 is a block diagram of components illustrating a software architecture suitable for implementing any of the various embodiments, including a radio protocol stack for a user plane and a control plane in wireless communications.

4 is a block diagram of components illustrating a system configured to improve quality of service (QoS) in an end-to-end network connection including a first communications network and a second communications network, in accordance with various embodiments.

Figure 5A is a block diagram of components of a relay system for improving QoS in end-to-end network connections, in accordance with various embodiments.

Figure 5B is a message flow diagram illustrating the dialing process that may occur in the relay system architecture shown in Figure 5A.

6A-6C are component block diagrams illustrating system architecture for improving QoS in end-to-end network connections, according to various embodiments.

7A is a block diagram illustrating components of a split-screen rendering system for improving QoS in end-to-end network connections, in accordance with various embodiments.

7B is a message flow diagram illustrating the dialing process that may occur in the relay system architecture shown in FIG. 7A.

8 is a process flow diagram illustrating an embodiment method for improving QoS in an end-to-end network connection including a first communications network and a second communications network, in accordance with various embodiments.

9 is a process flow diagram illustrating a method for improving QoS in an end-to-end network connection including a first communication network and a second communication network according to some embodiments. The method may be used as the method shown in FIG. 8 part to implement.

Figure 10 is a block diagram of components of a network element device suitable for use with various embodiments.

Figure 11 is a block diagram of components of a wireless device suitable for use with various embodiments.

Domestic storage information (please note in order of storage institution, date and number) without Overseas storage information (please note in order of storage country, institution, date, and number) without

800:Method

802: Operation

804: Operation

806: Operation

Claims (30)

A method for improving quality of service (QoS) in an end-to-end network connection including a first communication network and a second communication network, including the following steps: A QoS requirement for the end-to-end network connection is determined by a network element within the end-to-end network connection; QoS information for the second communications network is obtained by the network element from a reporting entity within the second communications network; and The network element adjusts a QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information. The method of claim 1, wherein the first communication network is a 5G network, and the second communication network is not a 5G network. The method of claim 1, wherein the reporting entity is a device in the second communication network, and the network element is a device in the first communication network, The method further includes the steps of: measuring the QoS information by the reporting entity, The step of obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes receiving the QoS information by the network element from the reporting entity. The method of claim 1, wherein the QoS information includes at least one of the following: a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or provided to the reporting entity The error rate of a packet. The method of claim 1, wherein the QoS information includes a classification of the second communication network. The method of claim 1, wherein the QoS information includes a request message indicating a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or provided to A requested change in the packet error rate for this reporting entity. The method of claim 1, wherein the QoS information includes at least one of application information or traffic information. The method of claim 1, wherein obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes measuring the first communication network and the second communication network. A delay between an endpoint server. The method as described in request item 1, wherein: the network element is located within the second communications network; and The step of obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes measuring a delay between the reporting entity and the network element. The method as described in request item 1, wherein: the network element is located within a third communications network communicatively connected to the second communications network via the first communications network; and The step of obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes measuring a delay between the reporting entity and the network element. The method as described in request item 1, wherein: the network element is located within the first communications network; and The step of obtaining the QoS information of the second communication network by the network element from the reporting entity in the second communication network includes measuring a delay between the reporting entity and the network element. The method as described in request item 1, wherein: The step of determining the QoS requirements of the end-to-end network connection by the network element within the end-to-end network connection includes determining, by the network element, the end-to-end based on a service agreement, application type or user request. a QoS requirement for the network connection; and The step of adjusting, by the network element, the QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information includes adjusting, by the network element, a 5G QoS parameter of the first communication network. A network element that includes: A processor configured with processor-executable instructions for: Determining a QoS requirement for an end-to-end network connection including a first communications network and a second communications network; Obtain the QoS information of the second communications network from a reporting entity within the second communications network; and Adjusting a QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information. The network element of claim 13, wherein the first communication network is a 5G network, and the second communication network is not a 5G network. A network element as described in request 13, wherein: The reporting entity is a device within the second communications network, and the network element is configured for use within the first communications network; and The processor is further configured with processor-executable instructions for: The QoS information is measured by the reporting entity; and QoS information for the second communication network is obtained from the reporting entity within the second communication network by receiving the QoS information from the reporting entity via the network element. The network element of claim 13, wherein the QoS information includes at least one of the following: a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or a round-trip delay provided to the end-to-end network connection. Reports the entity's packet error rate. The network element of claim 13, wherein the QoS information includes a classification of the second communication network. The network element of claim 13, wherein the QoS information includes a request message indicating a round-trip delay of the end-to-end network connection, a one-way delay of the end-to-end network connection, or A requested change in the packet error rate provided to this reporting entity. The network element of claim 13, wherein the QoS information includes at least one of application information or traffic information. The network element of claim 13, wherein the processor is further configured with processor-executable instructions for measuring the communication between the first communication network and an endpoint server within the second communication network. A delay is provided to obtain the QoS information of the second communication network from the reporting entity within the second communication network. A network element as described in request 13, wherein: the network element is located within the second communications network; and QoS information of the second communication network is obtained from the reporting entity in the second communication network by measuring a delay between the reporting entity and the network element. A network element as described in request 13, wherein: the network element is located within a third communications network communicatively connected to the second communications network via the first communications network; and QoS information of the second communication network is obtained from the reporting entity in the second communication network by measuring a delay between the reporting entity and the network element. A network element as described in request 13, wherein: the network element is located within the first communications network; and QoS information of the second communication network is obtained from the reporting entity in the second communication network by measuring a delay between the reporting entity and the network element. A network element as described in request 13, wherein: Determining the QoS requirements for the end-to-end network connection by determining a QoS requirement for the end-to-end network connection based on a service agreement, application type, or user request; and The QoS parameter of the first communication network is adjusted based on the determined QoS requirement and the obtained QoS information by adjusting a 5G QoS parameter of the first communication network. A network element that includes: means for determining a QoS requirement for an end-to-end network connection including a first communications network and a second communications network; means for obtaining QoS information of the second communications network from a reporting entity within the second communications network; and Means for adjusting a QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information. The network element of request 25, wherein the reporting entity is a device within the second communications network, and the network element is a device within the first communications network, The network element further includes components for measuring the QoS information by the reporting entity, The means for obtaining the QoS information of the second communication network from the reporting entity in the second communication network includes means for receiving the QoS information from the reporting entity by the network element. A network element as described in request 25, wherein: the network element is located within the second communications network; and The means for obtaining the QoS information of the second communication network from the reporting entity within the second communication network includes means for measuring a delay between the reporting entity and the network element. A network element as described in request 25, wherein: the network element is located within a third communications network communicatively connected to the second communications network via the first communications network; and The means for obtaining the QoS information of the second communication network from the reporting entity within the second communication network includes means for measuring a delay between the reporting entity and the network element. A network element as described in request 25, wherein: the network element is located within the first communications network; and The means for obtaining the QoS information of the second communication network from the reporting entity within the second communication network includes means for measuring a delay between the reporting entity and the network element. A non-transitory processor-readable medium having stored thereon processor-executable instructions configured to cause a processor of a network element to perform operations including: Determining a QoS requirement for an end-to-end network connection including a first communications network and a second communications network; Obtain the QoS information of the second communications network from a reporting entity within the second communications network; and Adjusting a QoS parameter of the first communication network based on the determined QoS requirement and the obtained QoS information.