Flexible quality of service framework for different networks

Abstract

This disclosure provides a method and apparatus in a wireless communication system. A method of operating a user equipment (UE) includes generating an indicator indicating that the UE is capable of supporting an adjusted Quality of Service (QoS), wherein the adjusted QoS corresponds to a scaling of QoS parameters associated with an existing QoS indicator. The method further includes generating a capability message including the indicator. The method further includes sending the capability message including the indicator to a base station (BS). The method further includes receiving a message from the BS including an adjusted QoS value based on a scaling of QoS parameters associated with an existing QoS indicator.

Description

Technical Field

[0001] This disclosure generally relates to diverse networks, and more specifically, to flexible quality of service control for diverse networks, including non-terrestrial networks and high-capacity networks. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-Long Term Evolution (LTE) systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed for 5G communication systems. Furthermore, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid frequency shift keying (FSK), Feher orthogonal amplitude modulation (FQAM), and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The internet, a human-centric network of connections where humans generate and consume information, is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), combining IoT technology with cloud server connectivity and big data processing technologies, has emerged. As essential technological elements for realizing IoT, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied. Such an IoT environment can provide intelligent internet technology services, creating new value for human life by collecting and analyzing data generated between interconnected things. Through the convergence and integration of existing information technology (IT) and various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN, as a big data processing technology, can also be seen as an example of the convergence between 5G and IoT technologies.

[0005] As mentioned above, with the development of wireless communication systems, various services can be provided, thus requiring a method for easily providing such services. Summary of the Invention

[0006] Technical solution

[0007] This disclosure relates to a method of operating a user equipment (UE). The method includes generating an indicator indicating that the UE is capable of supporting an adjusted Quality of Service (QoS), wherein the adjusted QoS corresponds to a scaling of QoS parameters associated with an existing QoS indicator. The method also includes generating a capability message including the indicator. The method further includes sending the capability message including the indicator to a base station (BS). The method also includes receiving a message from the BS including an adjusted QoS value based on a scaling of the QoS parameters associated with an existing QoS indicator. Attached Figure Description

[0008] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0009] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0010] Figure 2 An example gNB according to an embodiment of this disclosure is shown;

[0011] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0012] Figure 4 An example of overall management for supporting self-organizing networks and minimizing drive test measurements and reporting for non-terrestrial networks, according to embodiments of this disclosure, is shown;

[0013] Figure 5 Example management of measurement and reporting for self-organizing networks supporting non-terrestrial networks and minimizing road tests, according to embodiments of this disclosure;

[0014] Figure 6An example signaling flow for measurement and reporting of self-organizing networks supporting non-terrestrial networks and minimizing drive tests, according to embodiments of this disclosure, is illustrated.

[0015] Figure 7 An example general mechanism of a flexible quality of service framework according to embodiments of this disclosure is shown;

[0016] Figure 8 An example process for flexible quality of service according to an embodiment of this disclosure is shown;

[0017] Figure 9 Example signaling for a UE network procedure for a flexible QoS framework according to embodiments of this disclosure is shown;

[0018] Figure 10 Example signaling of the overall UE-network procedure for a flexible QoS framework in a 5G network according to embodiments of this disclosure is shown;

[0019] Figure 11 A base station (BS) according to an embodiment of this disclosure is shown; and

[0020] Figure 12 A user equipment (UE) according to an embodiment of this disclosure is shown. Detailed Implementation

[0021] This disclosure generally relates to different networks, and more specifically, it relates to flexible quality of service control for different networks, including non-terrestrial networks (NTNs) and high-capacity networks.

[0022] According to embodiments of this disclosure, a UE in a wireless communication system is provided. The UE includes a processor configured to generate an indicator indicating that the UE can support an adjusted quality of service (QoS), wherein the adjusted QoS corresponds to a scaling of QoS parameters associated with an existing QoS indicator; and to generate a capability message including the indicator. The UE also includes a transceiver operatively connected to the processor, configured to transmit the capability message including the indicator to a base station (BS); and to receive a message from the BS including an adjusted QoS value based on a scaling of QoS parameters associated with an existing QoS indicator.

[0023] In one embodiment, the adjusted QoS includes a QoS scaling factor for the QoS parameters associated with an existing QoS indicator.

[0024] In one embodiment, the QoS scaling factor is configured to indicate one of the following: a more lenient QoS parameter compared to a fixed set of QoS parameters associated with existing QoS indicators; and a more stringent QoS parameter compared to a fixed set of QoS parameters associated with existing QoS indicators.

[0025] In one embodiment, the QoS scaling factor is configured as an adjusted value of either the QoS parameter that defines the packet delay budget or the QoS parameter that defines the packet loss error rate.

[0026] In one embodiment, the QoS scaling factor includes: a first value corresponding to a geosynchronous equatorial orbit (GEO) network; a second value corresponding to a low earth orbit (LEO) network; and a third value corresponding to a high-performance network.

[0027] In one embodiment, the QoS scaling factor corresponds to one of the following: regular voice service; or lenient QoS voice service.

[0028] In one embodiment, the QoS scaling factor corresponds to one of the following: a first value for a first type of frame; a second value for a second type of frame.

[0029] According to another embodiment of this disclosure, a base station (BS) in a wireless communication system is provided. The BS includes a transceiver configured to receive from a user equipment (UE) a capability message including an indicator configured to indicate that the UE can support an adjusted Quality of Service (QoS), wherein the adjusted QoS corresponds to a scaling of QoS parameters associated with an existing QoS indicator. The BS also includes a processor operatively connected to the transceiver. The processor is configured to: identify the indicator; transmit a variable QoS capability to a network entity; receive an adjusted QoS value from the network entity, the adjusted QoS value being based on a scaling of QoS parameters associated with an existing QoS indicator; and transmit the adjusted QoS value to the UE.

[0030] In one embodiment, the adjusted QoS includes a QoS scaling factor for the QoS parameters associated with an existing QoS indicator.

[0031] In one embodiment, the QoS scaling factor is configured to indicate one of the following: a more lenient QoS parameter compared to a fixed set of QoS parameters associated with existing QoS indicators; or a more stringent QoS parameter compared to a fixed set of QoS parameters associated with existing QoS indicators.

[0032] In one embodiment, the QoS scaling factor is configured as an adjusted value of either the QoS parameter that defines the packet delay budget or the QoS parameter that defines the packet loss error rate.

[0033] In one embodiment, the QoS scaling factor includes: a first value corresponding to a geostationary equatorial orbit (GEO) network; a second value corresponding to a low Earth orbit (LEO) network; or a third value corresponding to a high-performance network.

[0034] In one embodiment, the QoS scaling factor corresponds to one of the following: regular voice service; or lenient QoS voice service.

[0035] In one embodiment, the QoS scaling factor corresponds to one of the following: a first value for a first type of frame; a second value for a second type of frame.

[0036] According to another embodiment of this disclosure, a method for providing a user equipment (UE) in a wireless communication system is provided. The method includes generating an indicator indicating that the UE is capable of supporting an adjusted Quality of Service (QoS), wherein the adjusted QoS corresponds to a scaling of QoS parameters associated with an existing QoS indicator. The method also includes generating a capability message including the indicator. The method further includes sending the capability message including the indicator to a base station (BS). The method also includes receiving a message from the BS including an adjusted QoS value based on a scaling of QoS parameters associated with an existing QoS indicator.

[0037] In one embodiment, the adjusted QoS includes a QoS scaling factor for QoS parameters associated with an existing QoS indicator. The method also includes an indicator indicating one of: a more lenient QoS parameter compared to a fixed set of QoS parameters associated with an existing QoS indicator; or a more stringent QoS parameter compared to a fixed set of QoS parameters associated with an existing QoS indicator.

[0038] In one embodiment, the QoS scaling factor is configured as an adjusted value of either the QoS parameter that defines the packet delay budget or the QoS parameter that defines the packet loss error rate.

[0039] In one embodiment, the QoS scaling factor includes: a first value corresponding to a geostationary equatorial orbit (GEO) network; a second value corresponding to a low Earth orbit (LEO) network; or a third value corresponding to a high-performance network.

[0040] In one embodiment, the QoS scaling factor corresponds to one of the following: regular voice service; or lenient QoS voice service.

[0041] In one embodiment, the QoS scaling factor corresponds to one of the following: a first value for a first type of frame; a second value for a second type of frame.

[0042] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.

[0043] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used in this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “include” and “comprising,” and their derivatives, mean unrestricted inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with” and its derivatives refer to including, being included, interconnected with, containing, being contained, connected to or connected with, coupled to or coupled with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, combined with or combined with, having, having attributes, having a relationship, or having a relationship with, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. When used with a list of items, the phrase "at least one" means that different combinations of one or more of the listed items may be used, and it may be necessary to use only one item from the list. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0044] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and be rewritten later, such as rewritable optical discs or erasable storage devices.

[0045] Definitions of other specific words and phrases are also provided in this patent document. Those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of the words and phrases defined in this way.

[0046] Wireless communication is one of the most successful innovations in modern history. Recently, the number of users of wireless communication services exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (such as tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and businesses. To meet the rapid growth of mobile data services and support new applications and deployments, improving the efficiency, coverage, and quality of service of radio interfaces is crucial.

[0047] The following discussion Figures 1 to 10 The various embodiments used to describe the principles of this disclosure in this patent document are merely exemplary and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0048] The following Figures 1-3 Various embodiments of communication technologies, such as orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), are described in wireless communication systems. Figures 1-3 The description does not imply any physical or architectural limitation on the ways in which different embodiments may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0049] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0050] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. In some embodiments, gNB 103 is a non-terrestrial BS. For example, gNB 103 may be a satellite located in geostationary equatorial orbit (GEO) or low Earth orbit (LEO).

[0051] gNB 102 provides wireless broadband access to network 130 to a first plurality of UEs within its coverage area 120. The first plurality of UEs includes UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The coverage area 125 provided by gNB 103 may be part of a non-terrestrial network (NTN). The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi or other wireless communication technologies.

[0052] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting-receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wireless-enabled equipment. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user equipment." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device for wireless access to a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine).

[0053] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles, the coverage areas associated with the gNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0054] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for flexible quality of service control across different networks. In some embodiments, one or more gNBs 101-103 include circuitry, programming, or a combination thereof for flexible quality of service control across different networks.

[0055] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0056] Figure 2 An example gNB 103 according to an embodiment of this disclosure is shown. Figure 2 The embodiment of gNB 103 shown is for illustrative purposes only. Figure 1 gNBs 101 and 102 can have the same or similar configurations. However, gNBs come in a wide variety of configurations, and Figure 2 This disclosure is not intended to limit the scope to any particular implementation of gNB.

[0057] like Figure 2 As shown, gNB 103 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 103 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0058] RF transceivers 210a-210n receive input RF signals, such as signals transmitted by a UE in network 100, from antennas 205a-205n. RF transceivers 210a-210n down-convert the input RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 220 sends the processed baseband signal to controller / processor 225 for further processing.

[0059] The TX processing circuit 215 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. RF transceivers 210a-210n receive the processed baseband or IF signal from the TX processing circuit 215 and up-convert the baseband or IF signal into an RF signal, which is then transmitted via antennas 205a-205n.

[0060] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 103. For example, the controller / processor 225 may control the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 to receive forward channel signals and transmit reverse channel signals, based on well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations, where the output / input signals from / to multiple antennas 205a-205n are weighted differently to effectively direct the output signals in a desired direction. The controller / processor 225 may support any of a variety of other functions within the gNB 103.

[0061] The controller / processor 225 is also capable of executing programs and other processes, such as an operating system, residing in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as needed during execution.

[0062] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows gNB 103 to communicate with other devices or systems via a backhaul connection or network. Interface 235 can support communication via any suitable wireless connection. When deployed as part of a terrestrial network (such as gNB 101 and gNB 102), interface 235 can support communication via any suitable wired or wireless connection. For example, when gNB 103 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 can allow gNB 103 to communicate with other gNBs via a wireless backhaul connection, while gNB 101 and gNB 102 can communicate with other gNBs via a wired or wireless backhaul connection. When one of gNBs 101-103 is implemented as an access point, interface 235 can allow gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless LAN or via a wired or wireless connection. Interface 235 includes any suitable structure that supports communication via wired or wireless connections, such as Ethernet or RF transceivers.

[0063] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, while another portion of memory 230 may include flash memory or other ROM.

[0064] although Figure 2 An example of gNB 103 is shown, but more can be found on... Figure 2Various changes can be made. For example, gNB 103, as part of the terrestrial network (TN), and the corresponding gNBs 101 and 102 may include... Figure 2 Each component can be any number shown. As a specific example, an access point may include multiple interfaces 235, and the controller / processor 225 may support routing functionality to route data between different network addresses. As another specific example, although shown as a single instance including TX processing circuitry 215 and a single instance including RX processing circuitry 220, the gNB 102 may include multiple instances of each (such as one per RF transceiver). Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0065] Figure 3 An example UE 116 according to an embodiment of this disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0066] like Figure 3 As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and an RX processing circuit 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0067] RF transceiver 310 receives an input RF signal transmitted by a gNB of network 100 from antenna 305. RF transceiver 310 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (e.g., for web browsing data).

[0068] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or other output baseband data (such as network data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal, which is then transmitted via the antenna 305.

[0069] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, based on well-known principles, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0070] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as processes for beam management. Processor 340 can move data into or out of memory 360 as needed for the execution process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0071] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website).

[0072] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0073] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0074] To meet the increased demand for wireless data services since the deployment of 4G communication systems and to enable various vertical applications, efforts have been made to develop and deploy improved 5G / NR or pre-5G / NR communication systems. Therefore, 5G / NR or pre-5G / NR communication systems are also referred to as "beyond 4G networks" or "post-LTE systems." 5G / NR communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. The aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even later versions that can utilize terahertz (THz) bands. Beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems to reduce radio wave propagation loss and increase transmission distance.

[0075] In addition, in 5G / NR communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.

[0076] A communication system includes a downlink (DL) and an uplink (UL). The downlink refers to the transmission from a base station or one or more transmission points to the UE, while the uplink refers to the transmission from the UE to a base station or one or more receiving points.

[0077] The time unit used for DL ​​signaling or UL signaling on a cell is called a time slot, and it can include one or more symbols. Symbols can also be used as additional time units. Frequency (or bandwidth (BW)) units are called resource blocks (RBs). An RB includes multiple subcarriers (SCs). For example, a time slot can have a duration of 0.5 milliseconds or 1 millisecond, include 14 symbols, and an RB can include 12 SCs with an inter-SC spacing of 15 kHz or 30 kHz, and so on.

[0078] DL signals include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). PDSCH or PDCCH can be transmitted over a variable number of time slot symbols, each comprising one time slot symbol. For simplicity, the DCI format used to schedule PDSCH reception from the UE is referred to as the DL DCI format, while the DCI format used to schedule transmissions from the Physical Uplink Shared Channel (PUSCH) of the UE is referred to as the UL DCI format.

[0079] The gNB transmits one or more of various RSs, including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily used by the UE to perform measurements and provide Channel State Information (CSI) to the gNB. For channel measurements, the Non-Zero Power CSI-RS (NZP CSI-RS) resource is used. For Interference Measurement Reporting (IMR), the CSI Interference Measurement (CSI-IM) resource associated with the Zero Power CSI-RS (ZP CSI-RS) configuration is used. The CSI process includes both NZP CSI-RS and CSI-IM resources.

[0080] The UE can determine CSI-RS transmission parameters via DL control signaling or higher-layer signaling (such as Radio Resource Control (RRC) signaling) from the gNB. The transmission instance of CSI-RS can be indicated by DL control signaling or configured by higher-layer signaling. DMRS is transmitted only in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0081] Traditional eNBs and gNBs support hundreds or thousands of active RRC connections. To effectively support a large number of low-rate and latency-tolerant services, as well as traditional smartphones, a paradigm shift is needed; each associated cell requires significant processing power. With the virtualization of wireless networks, cloud-based computing and storage resources will facilitate the development of eNBs / gNBs capable of supporting hundreds of thousands of active connections.

[0082] In this disclosure, one or more methods described below can be implemented to realize the concept of flexible Quality of Service (QoS) for various networks, including non-terrestrial networks (NTNs) and high-capacity networks. Geostationary equatorial orbit (GEO) satellites and high-altitude platform stations (HAPS), as well as fixed cells on Earth, are good candidates to support a large number of latency-tolerant devices and applications.

[0083] For non-terrestrial network (NTN) architectures, several embodiments are available. In one embodiment, a transparent GEO satellite payload can be used, where all radio protocol stack processing is performed at a terrestrial-based eNB or gNB. Such an eNB or gNB can leverage high-performance monolithic resources or cloud-based processing and memory resources (e.g., the computing and storage resources of a cloud network).

[0084] In some embodiments, for an NTN architecture, gNB 103 includes a gNB distributed unit (gNB-DU) deployed on a satellite and a gNB centralized unit (gNB-CU) deployed on the ground. In this case, the gNB-CU can control the amount of data sent to the gNB-DU based on the storage capacity of the gNB-DU. In an implementation-specific manner, the gNB-CU can handle most of the storage (e.g., at the Packet Data Convergence Protocol (PDCP) layer) to alleviate any significant memory requirements on the gNB-DU.

[0085] In some embodiments, new quantities such as ephemeris data and satellite elevation angles are introduced for NTN architectures, as well as new capabilities such as support for Terrestrial Network (TN) and NTN, TN-NTN service continuity, pre-compensation for timing and frequency synchronization, and device types (e.g., smartphones with very small aperture terminals (VSAT)). Embodiments of this disclosure introduce signaling mechanisms to leverage these quantities and capabilities to support SON and MDT. Embodiments of this disclosure introduce signaling support for Self-Organizing Network (SON) and Minimized Drive Test (MDT) for NTNs. Specifically, embodiments of this disclosure enable networks and UEs to leverage SON / MDT features by supporting NTN-specific capabilities and NTN-specific measurements. Embodiments of this disclosure provide capabilities to facilitate cell selection / reselection and various SON algorithms, such as Automatic Neighborhood Relationship (ANR) optimization, Physical Cell ID (PCI) configuration, RACH optimization, Capacity and Coverage Optimization (CCO), and Mobility Load Balancing (MLB) / Mobility Robustness Optimization (MRO).

[0086] Figure 4 An example of overall management of SON and MDT measurement and reporting supported by NTN is shown according to an embodiment of this disclosure. Figure 4 The embodiment of the entire mechanism 400 shown is for illustrative purposes only. Figure 4 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0087] exist Figure 4In the example shown, the SON / MDT management processor 405 receives the NTN capabilities, standards, and procedures 410 from UE 116 and gNB 103. This procedure defines the steps and processing for idle mode, inactive mode, connected mode, and MDT mode, as well as SON / MDT functions and algorithms. The SON / MDT management processor 405 configures the output of measurements and reports for SON / MDT 415.

[0088] Figure 5 An example of NTN-supported SON and MDT measurement and reporting management is shown according to an embodiment of this disclosure. Figure 5 The embodiments of all steps 500 shown are for illustrative purposes only. Figure 5 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0089] In operation 505, UE 116 and the network exchange NTN-centric capabilities. In operation 510, gNB 103 configures UE 116 with logged mode and instant mode measurements and reports to support NTN SON / MDT. In operation 515, UE 116 performs measurements according to the configuration established in operation 510. Based on the measurements performed in operation 515, in operation 520, UE 116 notifies the network of the availability of logged, idle, and inactive measurements. In response, in operation 525, the network requests UE 116 to provide logged, idle, and inactive measurements. In operation 530, UE 116 provides gNB 103 with logged, idle, and inactive mode measurements or instant mode measurements. In operation 535, the appropriate SON / MDT function or algorithm uses the NTN-centric measurements obtained by UE 116 and gNB 103.

[0090] Figure 6 Signaling flows for managing measurements and reporting to support NTN's SON and MDT, according to embodiments of this disclosure, are illustrated. Figure 6 The embodiment of the signaling flow 600 for UE-radio network interaction shown is for illustrative purposes only. Figure 6 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0091] like Figure 6As shown, in some embodiments, UE 116 sends a dedicated RRC signaling message 605 containing a Dedicated Non-Access Stratum (NAS) message. For example, RRC signaling message 605 may be an RRC establishment completion message, and the embedded NAS message may be a registration request. UE 116 may indicate its NTN-centric capabilities in RRC signaling message 605. UE 116 may provide early indication of one or more NTN-centric capabilities in RRC signaling message 605, or UE 116 may indicate some or all of these NTN-related capabilities in capability request signal 610.

[0092] Several methods are possible for UE 116 to indicate its capabilities related to NTN operation. In some embodiments, UE 116 may indicate that it supports only NTN or both NTN and TN. In some embodiments, UE 116 may indicate its Global Navigation Satellite System (GNSS) capabilities. In some embodiments, UE 116 may indicate that it supports NTN types for data transmission, such as LEO, GEO, and HAPS. For example, UE 116 may only support GEO to receive GNSS data; but may not support GEO used for actual data transmission, such as transmitting less power in the uplink and saving battery power. In some embodiments, UE 116 may indicate its time and frequency compensation capabilities. Specifically, regarding measurements supporting SON / MDT, in one or more embodiments, UE 116 indicates its support for measurement reports such as: (A) ephemeris data (e.g., position (x, y, z) and velocity (vx, vy, vz)); (B) reference point coordinates (e.g., cell center) provided by the network and / or estimated by UE 116; (C) measured elevation angles of one or more cells (e.g., serving cell and / or neighboring cells); (D) time since the last cell reselection; (E) time since the last handover; (F) timing advance (absolute, relative to a value provided by the gNB or relative to a specific reference point, such as the cell center); and (G) new NTN events.

[0093] In some embodiments, support for one or more (including all) of these measurements is mandatory for UE 116. In some embodiments, UE 116 also reports multiple instances of such measurements and the times associated with the measurements. For example, in the case of ephemeris data, UE 116 may report a set of historical measurements including ephemeris data at time t1 (e.g., provided by the network) and ephemeris data at time t2 (estimated by the UE).

[0094] In some embodiments, for new NTN events in idle / inactive modes or recorded measurement modes, UE 116 may support a new event, "Cell Selection / Reselection," where UE 116 stores and reports parameters and related measurements (e.g., RSRP, elevation angle, and / or timing advance of the serving cell and suitable neighboring cells). In some embodiments, for new NTN events in idle / inactive modes or recorded measurement modes, UE 116 may support a new event, "State Transition," where when UE 116 exits one mode (e.g., idle or inactive) and enters another mode (e.g., connected mode), the UE stores and reports measurements (e.g., RSRP, elevation angle, and / or timing advance of the serving cell and suitable neighboring cells). As a result of additional measurements performed at a past moment, such events can help identify whether the transition failed due to excessive NTN latency.

[0095] In some embodiments, for NTN events in connected mode, UE 116 may support new measurement reporting events to support handovers with specific trigger combinations. For example, UE 116 may indicate that it supports (i) a combination of "RSRP" and "elevation angle," and (ii) a combination of "RSRP" and "time since last handover." In some embodiments, UE 116 may need to support some or all of the triggers for NTN handover.

[0096] In capability request signal 610, gNB 103 sends a UE capability query message to query the UE's NTN-related capabilities mentioned in RRC signaling message 605. gNB 103 can query UE 116 for the selected NTN capabilities based on its own capabilities and the preferences in capability request signal 610. UE 116 replies with UE capability information and specifies its NTN-related capabilities mentioned in RRC signaling message 605.

[0097] gNB 103 sends a LoggedMeasurementConfiguration message 615 to configure the UE to perform measurements. This LoggedMeasurementConfiguration message 615 can be sent by gNB 103 to support UE-specific reporting (e.g., reporting associated with signaling tracing methods) or non-UE-specific reporting (e.g., reporting associated with management-based tracing methods). In some embodiments, gNB 103 can specify new NTN events, such as cell selection / reselection. Additionally, gNB 103 can specify an "areaConfiguration," which specifies the geographic area where the UE should perform MDT measurements. Traditionally supported areas include PLMN, NR CGI, TAC, and TAI. In some embodiments, gNB 103 can specify a new NTN measurement mentioned in RRC signaling message 605 to UE 116. In some embodiments, such measurements may be mandatory for UE 116 to perform and report.

[0098] In some embodiments, the gNB 103 does not include the cellGlobalList in the areaConfiguration when the NTN cell moves across the Earth. For fixed Earth cells or beams, the cellGlobalList may be relevant or useful. Note that for non-fixed Earth beams, the cellGlobalList is irrelevant.

[0099] In some embodiments, gNB 103 includes one or more Virtual Tracking Area (VTA) identifiers in the areaConfiguration, instead of typical broadcast TAC / TAI.

[0100] In operation 620, UE 116 begins to perform appropriate measurements based on the explicit configuration and / or implicit / forced configuration from the LoggedMeasurementConfiguration message 615. In some embodiments, for each TAC / TAI included in the areaConfiguration, when the NTN cell broadcasts multiple TACs / TAIs, UE 116 performs measurements and performs area-specific recording when a TAC / TAI matches any TAC broadcast by the cell. Even if the TAC / TAI broadcast by the NTN cell changes, UE 116 continues to perform measurements and perform area-specific recording as long as the TAC / TAI specified in the areaConfiguration matches any TAC broadcast by the cell.

[0101] In some embodiments, when the NTN cell is moving, UE 116 ignores any received cellGlobalList and does not perform area-based measurements and recording. Furthermore, in the example method, in this case, UE 116 records the reception of cellGlobalList as an error condition.

[0102] In RRC signaling 625, UE 116 indicates the availability of measurements in RRC messages such as RRCSetupComplete and RRCResumeComplete. Existing IElogMeasAvailable (measuring measurement available) can be enhanced, or a new IE logMeasAvailableNTN (measuring measurement available NTN) can be defined.

[0103] In UE Information Request 630, gNB 103 sends a UE Information Request message to request UE 116 to provide one or more reports (e.g., idle mode measurement, logMeasReport, ConnEstFail, RA report, RLF report, and mobilityHistoryReport). These traditional reports for terrestrial networks are enhanced to include NTN-specific measurements and events mentioned in RRC signaling message 605.

[0104] In some embodiments, the mobilityHistoryReport is modified when a non-fixed earth beam is used for the NTN. In some embodiments, a list of VTAs or TAC / TAIs is used instead of NR CGIs because NR CGIs remain variable for a given non-mobile UE, and these CGIs do not provide any information about the mobility of UE 116.

[0105] In UE Information Response 635, UE 116 sends a UE Information Response message to gNB 103 containing one or more reports requested by gNB 103 in UE Information Request 630. In some embodiments, as part of MeasQuantityResults, in addition to the typical RSRP, RSRQ, and SINR, new NTN-specific measurements are also included. For example, UE 116 reports one or more of the following information for the serving / failed cell and neighboring cells: such as ephemeris data (e.g., position (x, y, z) and velocity (vx, vy, vz)), reference point coordinates, measured elevation angle, time since the last cell reselection, timing advance (absolute, relative to values ​​provided by gNB or relative to a specific reference point such as the cell center), distance to the serving and neighboring cells, and new NTN event-specific parameters and measurements. In some embodiments, UE 116 may explicitly indicate the NTN type (e.g., TN to NTN, GEO to non-GEO, Earth-fixed to Earth-moving beam) in UE Information Response 635.

[0106] In some embodiments, in UE Information Response 635, UE 116 reports relevant system configurations, such as the period of NTN-related SIBs and cell selection and reselection parameters, to optimize cell selection / reselection. In some embodiments, in UE Information Response 635, to enhance the random access procedure, UE 116 reports the transmit power level of the last RA preamble for each attempt in the RA (Random Access) report. In another approach, UE 116 also reports open-loop power control parameters obtained from system information, such as the target received power at gNB 103, the power step size, and the maximum transmit power limit specified by gNB 103. In some embodiments, UE 116 also reports its power level to gNB 103.

[0107] To support the immediate mode of MDT, perform RRC configuration (or RRC reconfiguration) 640 and measurement report 645.

[0108] In RRC configuration 640, gNB 103 configures UE 116 with specific measurement and reporting events, and can select periodic reporting or event-based reporting. In some embodiments, gNB 103 specifies new NTN events with certain trigger combinations, such as (i) a combination of “RSRP” and “elevation”, and (ii) a combination of “RSRP” and “time since last handover”. In the example approach, gNB 103 requests UE 116 to report the following new NTN measurements (in addition to typical TN measurements) of the serving and / or neighboring cells: ephemeris data estimated by UE 116 and associated time, reference point coordinates estimated by UE 116 and associated time, elevation and associated time, timing advance (absolute and relative), and distance to the serving and neighboring cells. Where appropriate, when multiple measurements are associated with the same time, the time can be specified as a common time; in one example embodiment, only different times are specified individually.

[0109] In some embodiments, gNB 103 requires UE 116 to report "time since the last handover" from the UE's perspective.

[0110] In Measurement Report 645, UE 116 transmits measurements in the Measurement Report message based on the configuration specified by gNB in ​​RRC Configuration 640.

[0111] In operation 650, gNB 103 provides the SON / MDT function with reports from UE 116 as well as its own measurements. In some embodiments, in operation 650, gNB 103 reports these static or semi-static measurements to the SON / MDT function: NTN GW coordinates, platform (i.e., satellite or HAPS) processing latency, NTN GW processing latency, gNB 103 processing latency, and NTN GW-gNB transmission latency.

[0112] In some embodiments, during operation 650, gNB 103 may explicitly indicate the NTN type (e.g., TN to NTN, GEO to non-GEO, Earth-fixed to Earth-moving beam).

[0113] From a latency perspective, the most lenient 5G QoS Indicators (5QIs) are 5QI = 76 (500ms one-way packet latency budget and 10⁻⁴ packet error rate between UE 116 and User Plane Function (UPF)) and 5QI = 8 or 9 (300ms one-way packet latency budget and 10⁻⁶ packet error rate between UE and UPF). GEO cannot meet these QoS requirements. Furthermore, some NTN types can meet certain 5QIs (such as LEO). However, the long propagation latency imposes more limitations on gNB 103. For example, with a 300ms latency between the UE and P-GW, a 20ms latency between the UPF and gNB 103, and gNB 103 getting approximately 280ms to send packets with a target PER to UE 116. However, the longer satellite-to-ground latency reduces the available time for gNB 103. Therefore, for NTN, a more relaxed QoS standard should be considered.

[0114] Some embodiments provide systems and methods for enhancing the QoS framework of NTN. Embodiments of this disclosure enable service providers to meet QoS requirements delivered to subscribers. Service providers can appropriately allocate suitable resources within the network to meet the target QoS requirements of the NTN. Furthermore, future high-performance terrestrial networks (TNs) may be able to support enhanced QoS compared to existing TNs. Therefore, flexible and easy-to-use mechanisms are attractive for both NTNs and high-performance TNs.

[0115] Figure 7 An example general mechanism 700 of a flexible QoS framework according to an embodiment of this disclosure is shown. Figure 7 The embodiment of the entire mechanism 700 shown is for illustrative purposes only. Figure 7 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0116] exist Figure 7 In the example shown, the flexible QoS framework processor 705 receives NTN type, latency, error rate, legacy QoS, UE 116 capabilities, and network capabilities 710. The QoS framework processor 705 outputs adjusted QoS (new or modified), Quality Control Indicator (QCI), 5G QoS Indicator (5QI), scaling factor, and new or modified QoS features 715.

[0117] Figure 8 An example process for flexible QoS according to an embodiment of this disclosure is shown. Figure 8 The embodiments of all steps 800 shown are for illustrative purposes only. Figure 8One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0118] In operation 805, UE 116 and / or gNB 103 transmit network type and / or any QoS adjustment requests for one or more cells to the core network. In operation 810, UE 116 explicitly and / or implicitly indicates support for QoS adjustments to the core network via gNB 102 or gNB 103. In operation 815, EPS bearer / QoS flow establishment is initiated by UE 116 or the network. In operation 820, the core network determines the adjusted QoS for the EPS bearer / QoS flow. In operation 825, the core network transmits the adjusted QoS to gNB 102 or gNB 103. In operation 830, gNB 103 establishes an appropriate data radio bearer to reflect the adjusted QoS. In operation 835, the adjusted QoS is transmitted between source and destination during mobility within a RAT, between RATs, and between networks, such as between TN and NTN.

[0119] Figure 9 Example signaling for a UE network procedure for a flexible QoS framework according to embodiments of this disclosure is shown. Figure 9 The embodiment of signaling flow 900 for UE-radio network interaction shown is for illustrative purposes only. Figure 9 The one or more components shown can be implemented in a dedicated circuit configured to perform the function, or the one or more components can be implemented by one or more processors that execute instructions to perform the function. Figure 9 In the example shown, the operation and signaling between UE 116, gNB 103, NAS signaling anchor 905, Home Subscriber Server (HSS) / Policy and Charging Rules Function (PCRF) 910, and S Gateway (S-GW) and P-GW 915.

[0120] exist Figure 9 In the example shown, the HSS / PCRF 910 maintains a record of the user's QoS subscriptions for adjusted QoS, where the adjusted QoS is either more stringent or less stringent than typical QoS parameters. For example, the HSS / PCRF 910 may include providing longer or shorter latency compared to a target normalized latency based on the user's subscription and network capabilities. In the example approach, network capabilities depend on the network type. In one example, the network type may be differentiated between a regular terrestrial network (i.e., a network with typical QoS), a high-performance terrestrial network (i.e., a network with typical QoS), and a non-terrestrial network. The user experiences adjusted QoS based on their own capabilities and the type of network they access.

[0121] exist Figure 9 In the example shown, gNB 103 and NAS anchor 905 exchange S1-MME establishment signaling 920. In S1-MME establishment signaling 920, gNB 103 and NAS anchor 905 (i.e., the MME in the Evolved Packet Core (EPC)) exchange S1-MME establishment messages containing an S1 establishment request (SETUPREQUEST) and an S1 establishment response (SETUP RESPONSE). In some embodiments, gNB 103 transmits the network type of its each cell to the MME in the S1 establishment request message. In some embodiments, gNB 103 explicitly mentions the minimum and / or maximum round-trip delay between UE 116 and gNB 103 to the Mobility Management Entity (MME). In some embodiments, gNB 103 mentions support for QoS scaling of one or more QoS parameters. QoS scaling can provide stricter or more lenient QoS in the gNB 103 network compared to normalized QoS. Examples of these QoS parameters include QCI (QoS Category Identifier), packet delay budget (i.e., the delay between the UE and the P-GW), and packet loss error rate. In some embodiments, to support S1-MME establishment signaling 920, gNB 103 can manage some cells belonging to one network type (e.g., TN) and some cells belonging to other network types (e.g., NTN). For example, in the case of extended reality (XR) applications, QoS scaling can be applied to XR frames, such as one QoS scaling for one type of XR frame and another QoS scaling for other types of XR frames. Note that the same 5QI value can be used for different types of frames, but different QoS scaling factors can be applied to different types of XR frames.

[0122] UE 116 and gNB 103 exchange capability messages 925. That is, UE 116 and gNB 103 exchange UE capability query and UE capability information messages. In some embodiments, gNB 103 may explicitly request UE 116 to specify its support for adjusted QoS. In some embodiments, UE 116 either responds to a request from gNB 106 or specifies its support for adjusted QoS autonomously.

[0123] In some embodiments, support for the adjusted QoS is implicit in capability message 925, and it is not necessary to explicitly mention QoS in the UE capability query and UE capability information messages.

[0124] UE 116 sends capability signaling 930 to NAS anchor 905 via gNB 103. In capability signaling 930, UE 116 explicitly conveys its support for adjusted QoS to the MME in NAS messages such as attach request, TAU request, and service request. In some embodiments, UE 116 specifies the network type, and the MME infers the UE's support for adjusted QoS. In some embodiments, the MME infers the UE 116's support for adjusted QoS using the network type determined based on (i) the gNB configuration received in S1-MME establishment signaling 920 and (ii) the presence of ECGI in an S1AP message (e.g., an initial UE message) containing the UE's NAS message (and potential timestamps).

[0125] In Capability Signalling 930, when gNB 103 receives an RRC message containing a NAS message from UE 116, gNB 103 selects an MME by considering the network type of the cell in which gNB 103 has already received messages from UE 116. Some MMEs can be optimized for one network type, while others can be optimized for another.

[0126] In UE subscription signaling 935 between NAS anchor 905 and HSS / PCRF 910, the MME transmits the network type to HSS / PCRF 910 in an Update Location Request message. In the example method, the MME may also transmit a QoS adjustment indication. HSS / PCRF 910 responds with an Update Location Reply message, specifying QoS adjustment support as part of the subscription data. In some embodiments, HSS / PCRF 910 may also specify specific QoS parameters, such as the QCI of the default EPS bearer reflecting QoS adjustment. In some embodiments, HSS / PCRF 910 may also specify an appropriate scaling factor and associated QoS parameters (e.g., a scaling factor of 1.25 for a packet delay budget of QCI=8 or 9). Compared to the normalized QoS characteristics associated with QCI, the scaling factor enables the network to implement stricter or more lenient QoS. For example, in the case of XR applications, one set of scaling factors may be applied to one type of XR frame, while another set of scaling factors may be applied to another type of XR frame. Note that the same QCI / 5QI value can be used for different types of frames, but different QoS scaling factors can be applied to different types of XR frames.

[0127] The exact intranet message in the bearer establishment signaling 940 depends on the type of EPS bearer that the MME establishes for UE 116, such as a default EPS bearer and a dedicated EPS bearer. For example, in the case of a default EPS bearer, the MME sends a create bearer request message to S-GW 915-1, and S-GW 915-1 sends a create bearer request message to P-GW 915-2. These create bearer request messages contain adjusted QoS parameters. P-GW 915-2 sends a create bearer response message to S-GW 915-1, and S-GW 915-1 sends a create bearer response message to the MME.

[0128] To support bearer establishment signaling 940, the MME can select S-GW915-1 and P-GW915-2 based on network type. For example, some S-GW 915-1 and P-GW 915-2 units can be optimized for one network type or QoS, while others can be optimized for another network type or QoS.

[0129] The MME sends an Initial Context Setup Request (INITIAL CONTEXT SETUP REQUEST) or an E-RAN SETUP Request (E-RAN SETUP REQUEST) to request the eNB to facilitate the establishment of an E-UTRAN Radio Access Bearer (E-RAB) 945. These S1AP messages contain adjusted QoS parameters, enabling the gNB 103 to manage radio resources and establish a suitable Data Radio Bearer (DRB) 950. The DRB 950 reflects the adjusted QoS parameters. For example, in the case of XR applications, one set of adjusted QoS parameters is applied to one type of XR frame, while another set is applied to another type of XR frame. Note that the same QCI / 5QI value can be used for different types of frames, but different adjusted QoS scaling factors can be applied to different types of XR frames.

[0130] In some embodiments, the MME transmits adjusted QoS parameters to the UE via NAS signaling 955, such as activating the default EPS bearer context request or activating a dedicated EPS bearer context request.

[0131] In Operation 960, when UE 116 experiences mobility within a network or between two networks, adjusted QoS parameters are transmitted from a source entity (e.g., a source gNB or source MME) to a target entity (e.g., a target gNB or target MME) so that the target entity can facilitate appropriate admission control and radio resource management in the target network and can translate or adapt the adjusted QoS parameters to the target network's capabilities.

[0132] exist Figure 9 In the examples shown, the adjusted QoS parameters can take different forms. In some embodiments, an existing QCI is used, and specific parameters such as packet delay budget and packet loss error rate are scaled using scaling factors. The scaling factor can increase or decrease the value of the QoS parameter; for example, a scaling factor of 1.25 for the packet delay budget increases the packet delay budget from 300ms to (300 * 1.25 = 375ms), while a scaling factor of 0.75 decreases the packet delay budget from 300ms to (300 * 0.75 = 225)ms. In such embodiments, the QCI can remain unchanged, or the QCI can be transformed to something such as QCI' or QCI prime (e.g., QCI = 8' or 9' or 5 or 9 primes instead of QCI = 8 or 9, to indicate an adjustment to the default values ​​of one or more QoS parameters associated with the QCI). In some embodiments, a new QCI is defined for the adjusted QoS, and the adjustment is applied directly to the existing QoS parameter settings. For example, in the case of XR applications, one set of scaled packet delay budget and packet loss error rate is applied to one type of XR frame, while another set of scaled packet delay budget and packet loss error rate is applied to another type of XR frame. Note that the same QCI / 5QI value can be used for different types of frames, but different adjusted QoS scaling factors can be applied to different types of XR frames.

[0133] In some embodiments, for a given adjusted QCI, the selected adjusted QoS characteristics can be represented by Table 1 shown below for LTE networks.

[0134] Table 1

[0135]

[0136] Table 1. Adjusted QoS Features Selected for LTE

[0137] In Table 1, in the example method, L can be a scaling factor less than or greater than 1, M can be an integer (e.g., from 1 to 9), and N can be an integer (e.g., from 1 to 10).

[0138] For example, for GNSS NTN, L can take values ​​from the set {4, 5, 6, 7, 8, 9, 10, 11, 12, 13, ... 30}, M can be 1, and N can be values ​​from the set {2, 3, and 4}.

[0139] Figure 10 Example signaling of the entire UE-network process for a flexible QoS framework in a 5G network according to embodiments of this disclosure is shown. Figure 10The embodiment of the signaling flow 1000 for UE-radio network interaction shown is for illustrative purposes only. Figure 10 One or more components shown may be implemented in a dedicated circuit configured to perform the function, or one or more components may be implemented by one or more processors that execute instructions to perform the function. Figure 10 The example shown illustrates the operation and signaling between UE 116, gNB 103, NAS anchor 905, 5G Session Management Function (SMF) / Unified Data Management (UDM) and Policy Control Function (PCF) 1005, and User Plane Function (UPF) 1010.

[0140] exist Figure 10 In the example shown, Unified Data Management (UDM) and Policy Control Function (PCF) 1005 maintain a user's QoS subscription record for adjusted QoS, where the adjusted QoS is either more stringent or less stringent than typical QoS parameters. For example, UDM and PCF may include providing longer or shorter latency than the target normalized latency based on the user's subscription and network capabilities. In some embodiments, network capabilities depend on the network type. In one example, the network type may be distinguished between a regular terrestrial network (i.e., a network with typical QoS), a high-performance terrestrial network (i.e., a network with typical QoS), and a non-terrestrial network. User equipment experiences adjusted QoS based on its own capabilities and the type of network it accesses.

[0141] In some embodiments, gNB 103 and NAS signaling anchor 905 exchange NG setup signaling 1015. That is, gNB 103 and NAS signaling anchor 905, i.e., the AMF in the 5G core (5GC) or next-generation core (NGC), exchange NG setup messages containing NG setup request and NG setup response. In some embodiments, gNB 103 transmits the network type of each of its cells to the AMF in the NG setup request message. In some embodiments, gNB 103 explicitly mentions the minimum and / or maximum round-trip delay between UE 116 and gNB 103 to the AMF. In some embodiments, gNB 103 mentions support for QoS scaling of one or more QoS parameters. QoS scaling (L) can provide a more stringent or more lenient QoS in the gNB 103 network compared to standardized QoS. Examples of these QoS parameters include 5QI, packet delay budget (i.e., the delay between the UE and the UPF), and packet loss error rate.

[0142] In some embodiments, in order to support NG establishment signaling 1015, gNB 103 can manage some cells belonging to one network type (e.g., TN) and some cells belonging to another network type (e.g., NTN).

[0143] In some embodiments, UE 116 sends capability signaling 1020 to gNB 103. In capability signaling 1020, UE 116 and gNB 103 exchange UE capability query and UE capability information messages. In some embodiments, gNB 103 may explicitly request UE 116 to specify its support for adjusted QoS. In some embodiments, UE 116 specifies its support for adjusted QoS either in response to a request from gNB 103 or independently. In some embodiments, support for adjusted QoS is implicit and does not need to be explicitly mentioned in the UE capability query and UE capability information messages.

[0144] In some embodiments, UE 116 sends a NAS message 1025 for UE capability signaling to NAS signaling anchor 905 via gNB 103. In the NAS message 1025, UE 116 explicitly conveys its support for adjusted QoS to the AMF (in NAS signaling anchor 905) in a NAS message 1025 (such as a UL NAS transport (encapsulated in an RRC message such as a UL NAS transport)) carrying an N1 SM payload such as a PDU session establishment request. In some embodiments, UE 116 specifies the network type, and the AMF infers UE 116's support for adjusted QoS. In some embodiments, the AMF uses the network type to infer UE 116's support for adjusted QoS. When gNB 103 receives an RRC message containing NAS message 1025 from UE 116, gNB 103 selects the AMF by considering the network type of the cell in which it has already received UE messages. Some AMFs can be optimized for one type of network, while others can be optimized for another type of network and NCGI.

[0145] In the Nsmf_PDUSession_CreateSMContextRequest (SM context creation) message 1030, the AMF transmits the network type to the SMF. In some embodiments, the AMF uses the network type to indicate to the SMF (within SMF / UDM / PCF 1005) the UE 116's support for the adjusted QoS. The SMF obtains QoS parameters from the UDM, including the adjusted QoS parameters, specifically the default 5QI for the default QoS flow. The SMF establishes an SM policy association with the PCF. The PCF provides the authorized QoS, including the adjusted QoS parameters. In some embodiments, the adjusted QoS parameters provided by the UDM may be updated by the PCRF.

[0146] In some embodiments, the UDM / PCF (within SMF / UDM / PCF 1005) also specifies specific QoS parameters, such as the QCI of the QoS flow reflecting QoS adjustments. In some embodiments, the UDM / PCF may also specify appropriate scaling factors and associated QoS parameters (e.g., a scaling factor of 1.25 for a packet delay budget of 5QI = 8 or 9). Compared to the normalized QoS features associated with 5QI, the scaling factor enables the network to implement either stricter or more lenient QoS.

[0147] In N3 setup signaling 1035, the SMF configures UPF 1010 for a QoS flow (with adjusted QoS parameters) via an S4 session setup. To support N3 setup signaling 1035, the SMF can select UPF 1010 by considering the network type. For example, some UPFs can be optimized for one network type or QoS, while others can be optimized for another.

[0148] In N3 establishment signaling 1035, SMF sends Namf_Communication_N1N2MessageTransfer message 1040 to AMF, which contains adjusted QoS parameters, having (i) N2 SM information for gNB and (ii) N1 SM container for UE.

[0149] The AMF sends a PDU session resource establishment request 1045 containing adjusted QoS parameters to request gNB 103 to facilitate the establishment of a QoS flow. This NGAP message also contains NAS messages for UE 116, such as a DL NAS transport message containing N1 SM information messages (such as PDU session establishment acceptance).

[0150] Subsequently, gNB 103 establishes a suitable DRB 1050 that reflects the adjusted QoS parameters.

[0151] In some embodiments, UE 116 receives adjusted QoS parameters from AMF via NAS signaling 1055, such as DL NAS transmission messages containing PDU session establishment acceptance.

[0152] In operation 1060, when UE 116 experiences mobility within a network or between two networks, adjusted QoS parameters are transmitted from a source entity (e.g., a source gNB or source AMF) to a target entity (e.g., a target gNB or target AMF) so that the target entity can facilitate appropriate access control and radio resource management in the target network and can adapt or convert the adjusted QoS parameters to the target network.

[0153] exist Figure 10 In the examples shown, the adjusted QoS parameters can take different forms. In some embodiments, the existing 5QI is used, and specific parameters, such as packet delay budget and packet loss error rate, are scaled using scaling factors. The scaling factor can increase or decrease the value of the QoS parameter; for example, a scaling factor of 1.25 for the packet delay budget increases the packet delay budget from 300ms to (300 * 1.25 = 375ms), while a scaling factor of 0.75 decreases the packet delay budget from 300ms to (300 * 0.75 = 225)ms. In such embodiments, the 5QI can remain unchanged, or the 5QI can be transformed into something such as 5QI' or 5QI minus sign (e.g., 5QI = 8' or 9' or 5 minus sign or 9 minus sign, instead of 5QI = 8 or 9, to indicate an adjustment to the default values ​​of one or more QoS parameters associated with the 5QI). In some embodiments, a new 5QI is defined for the adjusted QoS, where the adjustment is applied directly to existing QoS parameter settings.

[0154] In some embodiments, for a given adjusted QCI, the selected adjusted QoS characteristics can be represented by Table 2 shown below for 5G networks.

[0155] Table 2

[0156]

[0157] Table 2. QoS Features Selected and Adjusted for 5G

[0158] In Table 2, L can be a scaling factor less than or greater than 1, M can be an integer (e.g., from 1 to 9), and N can be an integer (e.g., from 1 to 8).

[0159] For example, for GNSS NTN, L can take values ​​from the set {4, 5, 6, 7, 8, 9, 10, 11, 12, 13, ... 30}, M can be 1, and N can be values ​​from the set {2, 3, and 4}. As a specific example, L can be set based on whether the network is GEO, LEO, or a high-performance network. That is, when the network is GEO, L can be set to 10; when the network is LEO, L can be set to 2; and when the network is a high-performance network, L can be set to 0.5. Furthermore, M and N can be set based on the requirements of regular voice service or lenient QoS voice service. For example, when regular voice service is desired, M can be set to 1, and N can be set to 1. Or, when lenient QoS voice service is required, M can be set to 2, and N can be set to 2.

[0160] In some embodiments, to support adjusted QoS (i.e., more lenient or stricter QoS) for networks such as NTN, scaling factors for defined normalized QoS parameters such as Packet Delay Budget (PDB) and Packet Error Rate (PER) are functions of network or RAT type (e.g., NR-GEO, NR-MEO, NR-LEO, NR-HAPS, and air-to-ground or ATG). In some embodiments, scaling factors for defined normalized QoS parameters are functions of 5QI or QCI. In some embodiments, scaling factors for defined normalized QoS parameters are functions of both network / RAT type and 5QI / QCI.

[0161] In some embodiments, the scaling factor is a function of the delay. Such a delay may reflect only the propagation delay, or both the propagation and processing delays.

[0162] In some embodiments, for a given 5QI defined for TN (e.g., 5QI / QCI defined in version 16 and earlier versions), QoS adjustments are made only for PDB, only for PER, or both for PDB and PER, with either a more lenient or stricter approach.

[0163] In some embodiments, the QoS characteristics (e.g., PDB, PER, and priority) associated with a given 5QI / QCI are modified individually by a separate scaling factor.

[0164] In some embodiments, the scaling factors for the QoS features defined in version 16 are integers (e.g., 1, 2, 3, etc.). In one approach, these scaling factors are floating-point numbers (e.g., 1.2, 2.5, 3.5, etc.). In floating-point representation, L = P * (Q / R), where P, Q, and R are integers. The set of possible values ​​includes {1, 1 1 / 8, 1 2 / 8, ...}, where the increment is 1 / 8. Another set of possible values ​​includes {1, 1 1 / 2, 2, 2 1 / 2, ...}, where the increment is 1 / 2. That is, different fractions can be chosen as increments when determining the effective scaling factor.

[0165] For example, for the standardized 5QI=8 or 9 in version 16, the PDB is 300ms and the PER is 10. -6 For NR-GEO NTN / RAT type, a relaxed QoS can be represented by PDB = SF1 * 300ms, and PER can be represented by PER = SF2 * 10 -6 Let SF1 and SF2 be scale factors (<1, =1, or >1) that reflect the NTN / RAT type (or equivalently, the expected latency of such a network) and / or 5QI value (i.e., 5QI = 8 or 9).

[0166] In another example, for the normalized 5QI=1 in version 16, PDB is 100ms and PER is 10. -2 For NR-GEO NTN / RAT type, a relaxed QoS can be represented by PDB = SF3 * 100ms, and PER can be represented by PER = SF4 * 100ms. -2 This indicates that SF3 and SF4 are scaling factors (<1, =1, or >1) that reflect the NTN / RAT type (or equivalently, the expected latency of such a network) and / or 5QI value (i.e., 5QI = 19).

[0167] The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps can be omitted or replaced by other steps.

[0168] Figure 11 A base station according to an embodiment of the present disclosure is illustrated schematically.

[0169] Reference Figure 11 Base station 1100 may include processor 1110, transceiver 1120, and memory 1130. However, not all of the components shown are required. Base station 1100 may be composed of... Figure 11 It can be implemented with more or fewer components as shown. Furthermore, according to another embodiment, the processor 1110, transceiver 1120, and memory 1130 can be implemented as a single chip.

[0170] In an exemplary embodiment, base station 1100 may be a gNodeB (gNB). In an exemplary embodiment, the above... Figure 1 The gNB 101, gNB 102 and gNB 103 described herein can correspond to base station 1100.

[0171] The aforementioned components will now be described in detail.

[0172] Processor 1110 may include one or more processors or other processing devices that control the proposed functions, processes, and / or methods. Operation of base station 1100 may be implemented by processor 1110.

[0173] Transceiver 1120 may include an RF transmitter for up-converting and amplifying the transmitted signal and an RF receiver for down-converting the received signal. However, according to another embodiment, transceiver 1120 may be implemented with more or fewer components than shown in the components.

[0174] Transceiver 1120 can be connected to processor 1110 and transmit and / or receive signals. These signals may include control information and data. Furthermore, transceiver 1120 can receive signals via a wireless channel and output signals to processor 1110. Transceiver 1120 can also transmit signals output from processor 1110 via a wireless channel.

[0175] The memory 1130 may store control information or data included in signals obtained by the base station 1100. The memory 1130 may be connected to the processor 1110 and store at least one instruction, protocol, or parameter for the proposed function, process, and / or method. The memory 1130 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0176] Figure 12 A user equipment (UE) according to an embodiment of this disclosure is shown.

[0177] refer to Figure 12 UE 1200 may include a processor 1210, a transceiver 1220, and a memory 1230. However, not all of the components shown are required. UE 1200 may be composed of components such as processor 1210, transceiver 1220, and memory 1230. Figure 12 It can be implemented with more or fewer components as shown. Furthermore, according to another embodiment, the processor 1210, transceiver 1220, and memory 1230 can be implemented as a single chip.

[0178] In an exemplary embodiment, Figure 1 The UEs 111-116 shown can correspond to UE 1200.

[0179] The aforementioned components will now be described in detail.

[0180] Processor 1210 may include one or more processors or other processing devices that control the proposed functions, processes and / or methods. Operation of UE 1200 may be implemented by processor 1210.

[0181] Transceiver 1220 may include an RF transmitter for up-converting and amplifying the transmitted signal and an RF receiver for down-converting the received signal. However, according to another embodiment, transceiver 1220 may be implemented with more or fewer components than shown in the components.

[0182] Transceiver 1220 can be connected to processor 1210 and transmit and / or receive signals. These signals may include control information and data. Furthermore, transceiver 1220 can receive signals via a wireless channel and output signals to processor 1210. Transceiver 1220 can also transmit signals output from processor 1210 via a wireless channel.

[0183] The memory 1230 may store control information or data included in signals obtained by the UE 1200. The memory 1230 may be connected to the processor 1210 and store at least one instruction or protocol or parameters for the proposed function, process, and / or method. The memory 1230 may include read-only memory (ROM) and / or random access memory (RAM) and / or hard disk and / or CD-ROM and / or DVD and / or other storage devices.

[0184] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Nothing described herein should be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and The processor is operatively connected to the transceiver. The processor is configured as follows: Generate an indicator that shows the UE can support adjusted Quality of Service (QoS). Generate capability messages including indicators. Send a capability message including an indicator to the base station (BS), and A message is received from the BS, the message including at least one adjusted QoS parameter, the at least one adjusted QoS parameter being scaled based on a QoS scaling factor in response to a capability message. The QoS scaling factor is configured to define the value of the at least one adjusted QoS parameter, which includes either packet delay budget or packet loss error rate.

2. The UE according to claim 1, wherein, The QoS scaling factor is configured to indicate one of the following: More lenient QoS parameters compared to a fixed set of QoS parameters; and More stringent QoS parameters compared to a fixed set of QoS parameters.

3. The UE according to claim 1, wherein, The QoS scaling factor includes at least one of a first value corresponding to a geostationary equatorial orbit (GEO) network, a second value corresponding to a low Earth orbit (LEO) network, and a third value corresponding to a high-performance network.

4. The UE according to claim 1, wherein, The QoS scaling factor corresponds to one of the following: Regular voice services; and Flexible QoS voice service.

5. The UE according to claim 1, wherein, The QoS scaling factor corresponds to one of the following: The first value of the first type of frame; and The second value of the second type of frame.

6. A base station (BS) in a wireless communication system, the BS comprising: transceiver; The processor is operatively connected to the transceiver. The processor is configured as follows: Receive a capability message including an indicator from the user equipment (UE), wherein the indicator indicates that the UE can support an adjusted Quality of Service (QoS). Send capability messages to network entities. Receive at least one adjusted QoS parameter from the network entity, said adjusted QoS parameter being scaled based on a QoS scaling factor in response to a capability message, and Send a message to the UE including at least one adjusted QoS parameter. The QoS scaling factor is configured to define the value of the at least one adjusted QoS parameter, which includes either packet delay budget or packet loss error rate.

7. The BS according to claim 6, wherein, The QoS scaling factor is configured to indicate one of the following: More lenient QoS parameters compared to a fixed set of QoS parameters; and More stringent QoS parameters compared to a fixed set of QoS parameters.

8. The BS according to claim 6, wherein, The QoS scaling factor includes at least one of a first value corresponding to a geostationary equatorial orbit (GEO) network, a second value corresponding to a low Earth orbit (LEO) network, and a third value corresponding to a high-performance network.

9. The BS according to claim 6, wherein, The QoS scaling factor corresponds to one of the following: Regular voice services; and Flexible QoS voice service.

10. The BS according to claim 6, wherein, The QoS scaling factor corresponds to one of the following: The first value of the first type of frame; and The second value of the second type of frame.

11. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Generate an indicator that shows the UE can support the adjusted Quality of Service (QoS); Generate capability messages including indicators; Send a capability message including an indicator to the base station (BS); and A message is received from the BS, the message including at least one adjusted QoS parameter, the at least one adjusted QoS parameter being scaled based on a QoS scaling factor in response to a capability message. The QoS scaling factor is configured to define the value of the QoS parameter used for the at least one adjustment, the QoS parameter including packet delay budget or packet loss error rate.

Images