Patent Application
20250234284
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. A wireless network may include one or more network nodes that support communication for wireless communication devices.
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
When a UE is configured for dual connectivity, such as Fifth Generation (5G) New Radio (NR) and NR dual connectivity, the UE may be simultaneously connected to both a first frequency range and a second frequency range, which may improve a data rate for the UE. The first frequency range may be associated with a C-band (e.g., FR1). The second frequency range may be associated with an mmWave band (e.g., FR2). The UE may initially be connected to a single frequency range, and then the UE may be triggered to connect to both the first frequency range and the second frequency range using dual connectivity. Dual connectivity may be triggered by a signal strength associated with the UE and/or a status of a data buffer of the UE. For example, when the signal strength satisfies a threshold and/or an amount of data in the data buffer exceeds a certain amount, dual connectivity may be triggered for the UE.
However, a relatively limited set of criteria for enabling dual connectivity (e.g., signal strength and/or data buffer status) may cause the UE to enter dual connectivity even when dual connectivity is disadvantageous for the UE, which may reduce battery life for the UE and/or cause overheating of the UE. For example, when the UE is traveling from a starting location to an ending location, the UE may have a sufficient signal strength at the starting location so that dual connectivity may be triggered. As the UE travels to the ending location, the signal strength may deteriorate, such that dual connectivity may no longer be suitable for the UE. However, the UE may attempt to maintain the dual connectivity, which may drain the battery and/or overheat the UE. Thus, the limited set of criteria for dual connectivity may cause the UE to unnecessarily remain in a dual connectivity state, which may degrade an overall performance of the UE. Further, maintaining the dual connectivity may potentially add unnecessary airlink control messaging, which may congest a control channel when a wireless network is busy.
In some implementations, dual connectivity may be a physical-properties-assisted, slice-aware standalone NR dual connectivity. Such dual connectivity may be triggered by certain factors in addition to signal strength and data buffer status, such as whether a UE is expected to have a line-of-sight (LOS) to a base station. When the UE is expected to have the LOS to the base station, and based on network slice parameters associated with the UE, dual connectivity may be triggered for the UE. When the UE is not expected to have the LOS to the base station and/or based on the network slice parameters, dual connectivity may not be triggered for the UE, even when the signal strength and the data buffer status would otherwise trigger dual connectivity.
In some implementations, an application function (AF) in a wireless network may determine whether the UE is expected to have the LOS to the base station. The AF may use geographic information system (GIS) three-dimensional (3D) path rendering and information on antenna radiation centers to determine whether the UE is expected to have the LOS to the base station. The AF may determine, for a travel path associated with the UE, a route LOS. The route LOS may indicate a percentage of time that the UE is expected to have the LOS to the base station (or a percentage of time that the UE is expected to have no LOS (e.g., non-line-of-sight (NLOS)) to the base station), while the UE is traveling along a route. The route LOS may be determined using high-resolution terrain data. For example, the AF may determine, for a travel path from a starting location to a destination, that the UE is expected to have an LOS to the base station for approximately 90% of the travel path, which may be determined based on the GIS 3D path rendering and the information on antenna radiation centers.
In some implementations, the AF may transmit, to a radio access network (RAN) intelligent controller (RIC) in the wireless network, an indication of the route LOS. The RIC may use the route LOS and parameters in a network slice as criteria for determining whether dual connectivity is suitable for the UE. For example, such parameters may indicate whether a network slice is for a smart phone, or whether the UE is mounted on a vehicle, which may mitigate concern for saving battery life and provide greater heat dissipation (as opposed to a smartphone being carried by a user or placed in a user's pocket). The RIC may determine when dual connectivity is best served based on radio frequency (RF) and other contributing factors. When the RIC determines that the route LOS and the network slice parameters meet certain criteria, the RIC may provide an indication to the base station to add dual connectivity for the UE. On the other hand, when the RIC determines that the route LOS and/or the network slice parameters do not meet the certain criteria, the RIC may not provide any indication to the base station to add dual connectivity for the UE.
In some implementations, by defining dual connectivity to incorporate LOS and network slice parameters, dual connectivity may not be triggered when the UE does not have LOS to the network node and/or when the UE is associated with certain network slice parameters, even when a signal strength and a data buffer status would otherwise trigger dual connectivity. As a result, in certain situations, the UE may not initiate dual connectivity, thereby saving battery life for the UE and avoiding overheating of the UE. Criteria for triggering dual connectivity may be modified to include LOS and network slice parameters, which may improve an overall performance of the UE. Further, by not triggering dual connectivity in certain situations, unnecessary airlink control messaging may be avoided.
As shown by reference number 112, the UE 102 may transmit, to the base station 104, a measurement report. The measurement report may indicate measurements for a plurality of frequency ranges, which may include FR2. The measurements may include reference signal received power (RSRP) measurements, reference signal received quality (RSRQ) measurements, and/or signal-to-interference-plus-noise ratio (SINR) measurements.
As shown by reference number 114, the base station 104 may transmit, to the RIC 106, an indication that one or more triggers for dual connectivity are satisfied. The one or more triggers may be satisfied based on the measurement report received from the UE. For example, a signal strength of a certain frequency range, as indicated by the measurement report, may satisfy one or more thresholds, which may cause the one or more triggers for dual connectivity to be satisfied.
However, even though the one or more triggers for dual connectivity may be satisfied, dual connectivity may be conditional on a route LOS and network slice parameters, as described herein, and the RIC 106 may make no decision on whether to trigger dual connectivity for the UE 102 until the RIC 106 confirms that the route LOS and the network slice parameters are suitable for dual connectivity.
As shown by reference number 116, the RIC 106 may exchange context and discovery signaling with the AMF 108, which may allow the RIC 106 to be notified of a suitable AF 110. The AF 110 may be responsible for determining the route LOS using GIS 3D path rendering and information on antenna radiation centers.
As shown by reference number 118, the RIC 106 may transmit, to the AF 110, an indication of physical properties associated with the UE 102. The physical properties may include a route associated with the UE, a latitude associated with the UE 102, a longitude associated with the UE 102, a speed associated with the UE 102, a data buffer status associated with the UE 102, or a temperature associated with the UE 102. The physical properties may include positioning information associated with the UE 102. The positioning information may include X, Y, and Z coordinates associated with the UE 102, where X represents a horizontal position of the UE 102, Y represents a vertical position of the UE 102, and Z represents a height and/or elevation of the UE 102. The RIC 106 may receive information regarding the physical properties from the base station 104 and/or the UE 102.
As shown by reference number 120, the AF 110 may determine a metric associated with the LOS of the UE 102 with the base station 104, where the LOS metric is determined while the UE 102 is traveling along the route. The metric may be associated with the path LOS. The metric (or path LOS) may indicate a percentage of time, while the UE 102 is traveling along the route, that the UE 102 is expected to have the LOS with the base station 104. Alternatively, the metric may indicate a percentage of the route during which the UE 102 is expected to have the LOS with the base station 104. The AF 110 may determine the metric using high-resolution terrain data, LOS data, clutter data, and/or information regarding an antenna radiation center associated with the base station 104. The AF 110 may retrieve the high-resolution terrain data and/or other types of data from a GIS.
As shown by reference number 122, the AF 110 may transmit, to the RIC 106, an indication of the metric. For example, the metric may indicate that the UE 102 is expected to have an LOS with the base station 104 for 90% of the route (e.g., there are only certain streets for which the UE 102 may not have LOS to the base station 104). As another example, the metric may indicate, for a route that is estimated to take 30 minutes, the UE 102 is expected to have an LOS with the base station 104 for 25 minutes of the 30 minutes.
As shown by reference number 124, the RIC 106 may identify one or more network slice parameters. The one or more network slice parameters may be associated with single network slice selection assistance information (S-NSSAI). The S-NSSAI may include an indication of whether the UE 102 is a smart phone or a customer premises equipment (CPE). The S-NSSAI may include an indication of whether the UE 102 is configured for connected mode discontinuous reception (C-DRX). The S-NSSAI may include an indication of whether the UE 102 is battery powered or connected to a power source. The S-NSSAI may include an indication of whether the UE 102 is mounted to a surface. The S-NSSAI may include an indication of whether the UE 102 is to optimize latency. The S-NSSAI may include an indication of whether the UE 102 is to optimize throughput. The S-NSSAI may include an indication of whether the UE 102 is to optimize battery life.
As shown by reference number 126, the RIC 106 may transmit, to the base station 104, a message to enable dual connectivity for the UE 102 based on the metric and one or more network slice parameters, in addition to a signal strength and a data buffer status. The dual connectivity may be based on a first frequency range (e.g., a C-band, which may correspond to FR1) and a second frequency range (e.g., a mmWave band, which may correspond to FR2). The RIC 106 may determine to enable or trigger dual connectivity for the UE 102 when the metric satisfies a threshold. For example, the RIC 106 may determine to enable or trigger dual connectivity for the UE 102 when the percentage of time or the percentage of the route associated with having LOS with the base station 104 satisfies a threshold. The RIC 106 may determine to enable or trigger dual connectivity for the UE 102 when certain network slice parameters are set. For example, when the network slice parameters indicate that the UE 102 is connected to a power source (e.g., is not battery operated) and/or the UE 102 is mounted to an exterior surface of a vehicle (which may cause heat dissipation to not be an issue depending on weather), the RIC 106 may determine to enable or trigger dual connectivity for the UE 102.
As shown by reference number 128, the base station 104 may transmit, to the UE 102, a message to enable dual connectivity for the UE 102. The UE 102 may initiate appropriate signaling with the base station 104 for establishing dual connectivity.
As indicated above,
As shown by reference number 202, a base station 104 (e.g., an mmWave node) may be mounted on a relatively tall tower (e.g., a 200-foot-tall tower). A UE 102, when traveling along a route, may have LOS with the base station 104 due to its relatively tall height. The UE 102 may be associated with a vehicle that is traveling along the route (e.g., the UE 102 may be inside the vehicle).
As shown by reference number 204, the UE 102 may be traveling along a route from a starting location to an ending location. A majority of the route may be associated with LOS and a relatively good mmWave signal.
As shown by reference number 206, the base station 104 may transmit a query regarding whether to add NR dual connectivity for the UE 102. In response to the query, an RIC 106 and/or an AF 110 may determine whether NR dual connectivity should be added for the UE 102. The RIC 106 and/or an AF 110 may determine a metric associated with the LOS of the UE 102 with the base station 104, where the LOS metric is determined while the UE 102 is traveling along the route. The metric may indicate a route LOS, which may correspond to a percentage of the route for which the UE 102 has an LOS with the base station 104. The RIC 106 and/or the AF 110 may determine the metric using LOS data, clutter data (e.g., data indicating buildings, relatively large objects, etc., on a portion of land), speed data associated with the UE 102, a data buffer status of the UE 102, a temperature associated with the UE 102, and/or the route taken by the UE 102. The LOS data and the clutter data may be retrieved from a GIS. The RIC 106 and/or an AF 110 may identify S-NSSAI (e.g., smart phone, C-DRX, connected to power source, bias latency, and/or bias throughput). The RIC 106 and/or an AF 110 may indicate, to the network node 104, that NR dual connectivity should be added for the UE 102, which may be based on the metric and the S-NSSAI. For example, the RIC 106 and/or an AF 110 may determine that NR dual connectivity should be added based on the metric indicating that 98% of the route has LOS and a good mmWave signal, which may satisfy a threshold. As a result, the UE 102 may be connected to both a C-band and an mmWave band using NR dual connectivity. The RIC 106 and/or the base station 104 may enable NR dual connectivity by adding the mmWave band to the C-band.
As indicated above,
As shown by reference number 302, a base station 104 (e.g., an mmWave node) may be mounted on a relatively short tower (e.g., a 30-foot-tall tower). A UE 102, when traveling along a route, may have a relatively poor LOS with the base station 104 due to its relatively short height. The UE 102 may be associated with a vehicle that is traveling along the route (e.g., the UE 102 may be inside the vehicle).
As shown by reference number 304, the UE 102 may be traveling along a route from a starting location to an ending location. Portions of the route may be associated with relatively poor LOS and a relatively poor mmWave signal. For example, the starting location may be associated with LOS and a relatively good RF signal, but portions of the route may be associated with NLOS and a relatively poor RF signal. The NLOS may be due to buildings, trees, and/or other objects between the UE 102 and the base station 104.
As shown by reference number 306, the base station 104 may transmit a query regarding whether to add NR dual connectivity for the UE 102. In response to the query, an RIC 106 and/or an AF 110 may determine whether NR dual connectivity should be added for the UE 102. The RIC 106 and/or an AF 110 may determine a metric associated with the LOS of the UE 102 with the base station 104, where the LOS metric is determined while the UE 102 is traveling along the route. The metric may indicate a route LOS, which may correspond to a percentage of the route for which the UE 102 has an LOS with the base station 104. The RIC 106 and/or the AF 110 may determine the metric using LOS data, clutter data (e.g., data indicating buildings, relatively large objects, etc., on a portion of land), speed data associated with the UE 102, a data buffer status of the UE 102, a temperature associated with the UE 102, and/or the route taken by the UE 102. The LOS data and the clutter data may be retrieved from a GIS. The RIC 106 and/or an AF 110 may identify S-NSSAI (e.g., smart phone, C-DRX, battery powered, and/or bias battery life). The RIC 106 and/or an AF 110 may indicate, to the network node 104, that NR dual connectivity should not be added for the UE 102, which may be based on the metric and the S-NSSAI. For example, the RIC 106 and/or an AF 110 may determine that NR dual connectivity should not be added based on the metric indicating that only 15% of the route has LOS (e.g., 85% of the route has NLOS) and a good mmWave signal, which may not satisfy a threshold. As a result, the UE 102 may remain connected to only a C-band using single connectivity. The RIC 106 and/or the base station 104 may not enable NR dual connectivity by not adding the mm Wave band to the C-band.
As indicated above,
The UE 102 may include one or more devices capable of receiving, generating, storing, processing, and/or providing information, such as information described herein. For example, The UE 102 can include a mobile phone (e.g., a smart phone or a radiotelephone), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch or a pair of smart glasses), a mobile hotspot device, a fixed wireless access device, customer premises equipment, an autonomous vehicle, or a similar type of device.
The RAN 402 may support, for example, a cellular radio access technology (RAT). The RAN 402 may include one or more base stations (e.g., base transceiver stations, radio base stations, node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, transmit receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network entities that can support wireless communication for the UE 102. A base station may be a disaggregated base station. The disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more nodes, which may include a radio unit (RU), a distributed unit (DU), and a centralized unit (CU). The RAN 402 may transfer traffic between the UE 102 (e.g., using a cellular RAT), one or more base stations (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and/or the core network 404. The RAN 402 may provide one or more cells that cover geographic areas.
In some implementations, the RAN 402 may perform scheduling and/or resource management for the UE 102 covered by the RAN 402 (e.g., the UE 102 covered by a cell provided by the RAN 402). In some implementations, the RAN 402 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, and/or other operations. The network controller may communicate with the RAN 402 via a wireless or wireline backhaul. In some implementations, the RAN 402 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. In other words, the RAN 402 may perform network control, scheduling, and/or network management functions (e.g., for uplink, downlink, and/or sidelink communications of the UE 102 covered by the RAN 402).
In some implementations, the core network 404 may include an example functional architecture in which systems and/or methods described herein may be implemented. For example, the core network 404 may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system. While the example architecture of the core network 404 shown in
As shown in
The NSSF 406 may include one or more devices that select network slice instances for the UE 102. The NSSF 406 may allow an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In some implementations, each slice may be customized for different services. The NEF 408 may include one or more devices that support exposure of capabilities and/or events in the wireless telecommunications system to help other entities in the wireless telecommunications system discover network services.
The UDR 410 may include one or more devices that provide a converged repository, which may be used by network functions to store data. For example, a converged repository of subscriber information may be used to service a number of network functions. The UDM 412 may include one or more devices to store user data and profiles in the wireless telecommunications system. The UDM 412 may generate authentication vectors, perform user identification handling, perform subscription management, and perform other various functions. The AUSF 414 may include one or more devices that act as an authentication server and support the process of authenticating the UE 102 in the wireless telecommunications system.
The PCF 416 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and/or mobility management, among other examples. The AF 110 may include one or more devices that support application influence on traffic routing, access to the NEF 408, and/or policy control, among other examples. The AMF 108 may include one or more devices that act as a termination point for non-access stratum (NAS) signaling and/or mobility management, among other examples. The SMF 418 may include one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF 418 may configure traffic steering policies at the UPF 420 and/or may enforce UE IP address allocation and policies, among other examples. The UPF 420 may include one or more devices that serve as an anchor point for intra-RAT and/or inter-RAT mobility. The UPF 420 may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples. The message bus 422 may represent a communication structure for communication among the functional elements. In other words, the message bus 422 may permit communication between two or more functional elements.
The data network 424 may include one or more wired and/or wireless data networks. For example, the data network 424 may include an IP multimedia subsystem (IMS), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network such as a corporate intranet, an ad hoc network, the Internet, a fiber optic-based network, a cloud computing network, a third party services network, an operator services network, and/or a combination of these or other types of networks.
The number and arrangement of devices and networks shown in
The bus 510 may include one or more components that enable wired and/or wireless communication among the components of the device 500. The bus 510 may couple together two or more components of
The memory 530 may include volatile and/or nonvolatile memory. For example, the memory 530 may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). The memory 530 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). The memory 530 may be a non-transitory computer-readable medium. The memory 530 may store information, one or more instructions, and/or software (e.g., one or more software applications) related to the operation of the device 500. In some implementations, the memory 530 may include one or more memories that are coupled (e.g., communicatively coupled) to one or more processors (e.g., processor 520), such as via the bus 510. Communicative coupling between a processor 520 and a memory 530 may enable the processor 520 to read and/or process information stored in the memory 530 and/or to store information in the memory 530.
The input component 540 may enable the device 500 to receive input, such as user input and/or sensed input. For example, the input component 540 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, a global navigation satellite system sensor, an accelerometer, a gyroscope, and/or an actuator. The output component 550 may enable the device 500 to provide output, such as via a display, a speaker, and/or a light-emitting diode. The communication component 560 may enable the device 500 to communicate with other devices via a wired connection and/or a wireless connection. For example, the communication component 560 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.
The device 500 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 530) may store a set of instructions (e.g., one or more instructions or code) for execution by the processor 520. The processor 520 may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors 520, causes the one or more processors 520 and/or the device 500 to perform one or more operations or processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, the processor 520 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number and arrangement of components shown in
As shown in
As shown in
As shown in
Although
As used herein, the term “component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/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 are described herein without reference to specific software code—it being understood that software and hardware can be used to implement the systems and/or methods based on the description herein.
As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
To the extent the aforementioned implementations collect, store, or employ personal information of individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage, and use of such information can be subject to consent of the individual to such activity, for example, through well known “opt-in” or “opt-out” processes as can be appropriate for the situation and type of information. Storage and use of personal information can be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various 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 various implementations includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiple of the same item.
When “a processor” or “one or more processors” (or another device or component, such as “a controller” or “one or more controllers”) is described or claimed (within a single claim or across multiple claims) as performing multiple operations or being configured to perform multiple operations, this language is intended to broadly cover a variety of processor architectures and environments. For example, unless explicitly claimed otherwise (e.g., via the use of “first processor” and “second processor” or other language that differentiates processors in the claims), this language is intended to cover a single processor performing or being configured to perform all of the operations, a group of processors collectively performing or being configured to perform all of the operations, a first processor performing or being configured to perform a first operation and a second processor performing or being configured to perform a second operation, or any combination of processors performing or being configured to perform the operations. For example, when a claim has the form “one or more processors configured to: perform X; perform Y; and perform Z,” that claim should be interpreted to mean “one or more processors configured to perform X; one or more (possibly different) processors configured to perform Y; and one or more (also possibly different) processors configured to perform Z.”
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.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only 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. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).
In the preceding specification, various example embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
