Patent Application
20240040603
The disclosure relates to a system, method and device for traffic flow adjustment in a network environment.
A network environment may include a long term evolution (LTE) base station and a new radio (NR) base station (e.g., a 5th generation (5G) base station). In a non-standalone (NSA) network model of 5G deployment, 5G services are provided without an end-to-end 5G network, but instead use an LTE core network for control functions (such as signaling). That is, the 5G Radio Access Network (RAN) and its NR base station are used in conjunction with the LTE core network. In this context, user equipment (UE) that supports Evolved Universal Terrestrial Radio Access Network (E-UTRAN) New Radio Dual Connectivity (ENDC) can connect simultaneously to (or camp on) both an LTE cell and an NR cell. However, as the UE moves throughout the network environment, the conditions for transmitting uplink data and receiving downlink data may change. Thus, processes that adapt to the changing conditions are desired.
According to an aspect of the disclosure, a method may include determining that a user equipment (UE) is camped on a new radio (NR) cell and on a long term evolution (LTE) cell, determining a reference signal received power (RSRP) of the LTE cell, determining an RSRP of the NR cell, and assigning an uplink data flow configuration for the UE based on the RSRP of the LTE cell and the RSRP of the NR cell.
According to an aspect of the disclosure, a system may include a memory configured to store instructions and one or more processors configured to execute the instructions to determine that a UE is camped on a NR cell and to an LTE cell, determine an RSRP of the LTE cell, determine an RSRP of the NR cell, and assign an uplink data flow configuration for the UE based on the RSRP of the LTE cell and the RSRP of the NR cell.
According to an aspect of the disclosure, a non-transitory computer-readable medium may store instructions, and the instructions may include one or more instructions that, when executed by one or more processors of a wireless communication system, cause the one or more processors to determine that a UE is camped on a NR cell and to an LTE cell, determine an RSRP of the LTE cell, determine an RSRP of the NR cell, and assign an uplink data flow configuration for the UE based on the RSRP of the LTE cell and the RSRP of the NR cell.
Additional aspects will be set forth in part in the description that follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments of the disclosure.
The above and other aspects, features, and aspects of embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
The following detailed description of example embodiments refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
When the system determines that the UE is camped on both the LTE cell and the NR cell, in operation 306, the system determines whether an LTE RSRP is greater than or equal to an LTE RSRP threshold (LTh). When the system determines that the LTE RSRP is not greater than or equal to the LTE RSRP threshold, in operation 308, the system determines whether an NR RSRP is less than an NR RSRP threshold (nTh). When the system determines that the NR RSRP is less than the NR RSRP threshold, in operation 310, the system assigns an uplink data flow configuration such that uplink data is allowed on the LTE cell and is blocked on the NR cell. When the system determines that the NR RSRP is not less than the NR RSRP threshold, in operation 312, the system assigns an uplink data flow configuration such that uplink data is allowed on the NR cell and is blocked on the LTE cell.
Referring back to operation 306, when the system determines that the LTE RSRP is greater than or equal to the LTE RSRP threshold, in operation 314, the system determines whether an NR RSRP is greater than or equal to the NR RSRP threshold. When the system determines that the NR RSRP is greater than or equal to the NR RSRP threshold, in operation 316, the system assigns an uplink data flow configuration such that uplink data is allowed on the NR cell and on the LTE cell. When the system determines that the NR RSRP is not greater than or equal to the NR RSRP threshold, in operation 318, the system assigns an uplink data flow configuration such that uplink data is allowed on the LTE cell and is blocked on the NR cell.
Table 1 shows an example of uplink data flow configurations.
The order of the operations shown in
As various parameters of the UE operation within the network environment change while the UE is camped on the LTE cell and the NR cell, it may be desirable to adjust the LTE RSRP threshold and the NR RSRP threshold. That is, as the UE moves around the coverage area and gets closer or farther to the NR or LTE base stations, channel quality or block error rate (BLER) may change. In such cases, the RSRP thresholds should reflect these changes. For example, if the UE experiences high BLER over the NR uplink connection, then a higher RSRP is required to reduce transmission errors. According to various embodiments, the system may implement a method, such as a machine learning (ML) method, for dynamically adjusting the RSRP thresholds based on channel quality, as is described in
Referring to
In operation 404, the system determines whether the LTE uplink BLER for the UE is greater than an error threshold percentage X. The system may obtain the BLER from the LTE base station. The threshold percentage X may be a predefined input threshold set by a user (e.g., network operator). When the system determines that the LTE uplink BLER is greater than the threshold percentage X, in operation 406, the system determines whether the LTE RSRP threshold increased by a predetermined value (e.g., 2 decibels (dB)) is greater than an LTE RSRP threshold maximum (LThmax). The LTE RSRP threshold maximum may be a predefined input threshold set by a user (e.g., network operator). The value of 2 dB is an example iteration value, and other appropriate values will be understood by those of skill in the art from the disclosure herein. When the system determines that the LTE RSRP threshold plus 2 dB (or any other iteration value) is not greater than the LTE RSRP threshold maximum, in operation 408, the system sets the LTE RSRP threshold to be the previous value of the LTE RSRP threshold plus 2 dB (or any other iteration value). When the system determines that the LTE RSRP threshold plus 2 dB is greater than the LTE RSRP threshold maximum, in operation 416, the system maintains the existing LTE RSRP threshold.
Referring back to operation 404, when the system determines that the LTE uplink BLER is not greater than the threshold percentage X, in operation 410, the system determines whether the LTE uplink BLER is less than the threshold percentage X. When the system determines that the LTE uplink BLER is not less than the threshold percentage X (i.e., the system determines that the LTE uplink BLER is equal to the threshold percentage X), in operation 416, the system determines to maintain the existing LTE RSRP threshold. When the system determines that the LTE uplink BLER threshold is less than the threshold percentage X, in operation 412, the system determines whether the LTE RSRP threshold minus a predetermined value (e.g., 2 dB) is less than an LTE RSRP threshold minimum (LThmin). The value of 2 dB is an example iteration value, and other appropriate values will be understood by those of skill in the art from the disclosure herein. The LTE RSRP threshold minimum may be a predefined input threshold set by a user (e.g., network operator). When the system determines that the LTE RSRP threshold minus 2 dB (or any other iteration value) is less than the LTE RSRP threshold minimum, in operation 416, the system determines to maintain the existing LTE RSRP threshold. When the system determines that the LTE RSRP threshold minus 2 dB (or any other iteration value) is not less than the LTE RSRP threshold minimum, in operation 414, the system sets the LTE RSRP threshold to be the previous value of the LTE RSRP threshold minus 2 dB (or any other iteration value). Thus, the LTE RSRP threshold may be dynamically adjusted according to system conditions.
The method of
Referring back to operation 504, when the system determines that the NR uplink BLER is not greater than the threshold percentage Y, in operation 510, the system determines whether the NR uplink BLER is less than the threshold percentage Y. When the system determines that the NR uplink BLER is not less than the threshold percentage Y (i.e., the system determines that the NR uplink BLER is equal to the threshold percentage Y), in operation 516, the system determines to maintain the existing NR RSRP threshold. When the system determines that the NR uplink BLER threshold is less than the threshold percentage Y, in operation 512, the system determines whether the NR RSRP threshold minus a predetermined value (e.g., 2 dB) is less than an NR RSRP threshold minimum (nThmin). The value of 2 dB is an example iteration value, and other appropriate values will be understood by those of skill in the art from the disclosure herein. The NR RSRP threshold minimum may be a predefined input threshold set by a user (e.g., network operator). Further, the NR RSRP threshold minimum may be the same as or different from (e.g., less than or greater than) the LTE RSRP threshold minimum. When the system determines that the NR RSRP threshold minus 2 dB (or any other iteration value) is less than the NR RSRP threshold minimum, in operation 516, the system determines to maintain the existing NR RSRP threshold. When the system determines that the NR RSRP threshold minus 2 dB (or any other iteration value) is not less than the NR RSRP threshold minimum, in operation 514, the system sets the NR RSRP threshold to be the previous value of the NR RSRP threshold minus 2 dB (or any other iteration value). Thus, the NR RSRP threshold may be dynamically adjusted according to system conditions.
The method of
The user device 710 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server device, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a camera device, a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device.
The server device 720 includes one or more devices. For example, the server device 720 may be a server device, a computing device, or the like.
The network 730 includes one or more wired and/or wireless networks. For example, network 730 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.
In accordance with an embodiment, the client device 710 may correspond to a UE, the network 730 may correspond to an LTE RAN and a 5G RAN, and the server device 720 may correspond to the systems described above.
The number and arrangement of devices and networks shown in
As shown in
The bus 810 includes a component that permits communication among the components of the device 800. The processor 820 is implemented in hardware, firmware, or a combination of hardware and software. The processor 820 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. The process 820 includes one or more processors capable of being programmed to perform a function.
The memory 830 includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by the processor 820.
The storage component 840 stores information and/or software related to the operation and use of the device 800. For example, the storage component 840 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.
The input component 850 includes a component that permits the device 800 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). The input component 850 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator).
The output component 860 includes a component that provides output information from the device 800 (e.g., a display, a speaker, and/or one or more light-emitting diodes (LEDs)).
The communication interface 870 includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables the device 800 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 870 may permit device 800 to receive information from another device and/or provide information to another device. For example, the communication interface 870 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
The device 800 may perform one or more processes described herein. The device 800 may perform operations based on the processor 820 executing software instructions stored by a non-transitory computer-readable medium, such as the memory 830 and/or the storage component 840. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into the memory 830 and/or the storage component 840 from another computer-readable medium or from another device via the communication interface 870. When executed, software instructions stored in the memory 830 and/or storage component 840 may cause the processor 820 to perform one or more processes described herein.
Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments described herein are not limited to any specific combination of hardware circuitry and software.
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
Some embodiments may relate to a system, a method, and/or a computer readable medium at any possible technical detail level of integration. The computer readable medium may include a computer-readable non-transitory storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out operations.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program code/instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, and computer readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware may be designed to implement the systems and/or methods based on the description herein.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
The descriptions of the various aspects and embodiments have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Even though combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2021/065281 | 12/28/2021 | WO |
