WO2022164358A1 - Managing handover execution - Google Patents
Managing handover execution Download PDFInfo
- Publication number
- WO2022164358A1 WO2022164358A1 PCT/SE2021/050052 SE2021050052W WO2022164358A1 WO 2022164358 A1 WO2022164358 A1 WO 2022164358A1 SE 2021050052 W SE2021050052 W SE 2021050052W WO 2022164358 A1 WO2022164358 A1 WO 2022164358A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- base station
- information
- target cell
- cell
- handover
- Prior art date
Links
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000012545 processing Methods 0.000 claims abstract description 37
- 238000011156 evaluation Methods 0.000 claims abstract description 11
- 238000009877 rendering Methods 0.000 claims description 43
- 238000005259 measurement Methods 0.000 claims description 27
- 238000004590 computer program Methods 0.000 claims description 9
- 235000008694 Humulus lupulus Nutrition 0.000 claims description 3
- 230000003287 optical effect Effects 0.000 claims description 3
- 230000001413 cellular effect Effects 0.000 description 18
- 230000006870 function Effects 0.000 description 13
- 238000004891 communication Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000010801 machine learning Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 229920002635 polyurethane Polymers 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000001934 delay Effects 0.000 description 3
- 239000000872 buffer Substances 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013135 deep learning Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 229920002803 thermoplastic polyurethane Polymers 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/00835—Determination of neighbour cell lists
- H04W36/008357—Determination of target cell based on access point [AP] properties, e.g. AP service capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/00835—Determination of neighbour cell lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
Definitions
- This disclosure relates to methods, devices, computer programs and carriers related to managing handover execution.
- GPUs Graphic Processing Units
- Cloud Gaming
- the GPU has become an important type of computing technology, both for personal and business computing. GPUs are used in a wide range of applications, including graphics and video rendering. For example, GPUs are becoming popular for use in gaming (e.g., cloud gaming), remote rendering, extended reality (XR) (e.g., virtual reality (VR), augmented reality (AR), etc.), and artificial intelligence (Al).
- gaming e.g., cloud gaming
- remote rendering e.g., extended reality (XR) (e.g., virtual reality (VR), augmented reality (AR), etc.), and artificial intelligence (Al).
- XR extended reality
- VR virtual reality
- AR augmented reality
- Al artificial intelligence
- Cloud gaming and remote rendering involve employing a GPU (or a group of
- GPUs that is remote from the user’s user equipment (UE) to render high-fidelity images (e.g., video frames) of a game.
- the images are then transmitted from the GPU to the user’s UE, which then displays the images to the user.
- the UE may also receive input from the user and transmit this user input to the GPU.
- An advantage of cloud gaming is that the GPUs that are “in the cloud” typically have much more rendering power than the user’s UE (e.g. mobile phone, computer, XR device, tablet, etc.).
- the remote GPUs are owned by the company that sells the game or by an online gaming service provider (e.g., Google LLC, which provides an on-line gaming service known as Stadia). Accordingly, the remote GPUs are located outside of the user’s premises (e.g., home or office) and sometimes not even in the same city or country as the user. In other instances, the remote GPU may be owned by the user.
- a home streaming solution known as Steam allows a user to construct a system where a games is rendered on one of the user’s devices, but the user plays the game on another one of the user’s devices.
- one of the user’s device is a remote GPU that is accessible by UEs with the same user login on the same or different network.
- Gaming consoles in every living room, the workstation at the office, and even high-end tablets have a medium range GPU nowadays. Even cars, surveillance cameras and other non-computer devices are getting equipped with GPUs or TPUs for performing machine learning inferencing efficiently. There will likely be hundreds of available rendering devices in each parking lot in the future, being able to supply both storage and compute power for a multitude of thin UEs used by people in the vicinity (e.g., at sporting events).
- GPU processing units may be in an edge-cloud environment where one or more GPUs may be located at a base station or in some logical topology associated with a base station. Also, it is expected that a cellular connected XR user device may be located in a location where the XR user device could be served by more than one base station. Accordingly, handover between these base stations is also expected. Hence, depending on network topology, user mobility that causes handover between different base stations may also imply that different edge cloud processing nodes (e.g. in terms of provided delay, frame renderings, etc.) will become accessible for the XR user device.
- edge cloud processing nodes e.g. in terms of provided delay, frame renderings, etc.
- the purpose of the ANR function is to relieve the operator from the burden of manually managing Neighbor Cell Relations (NCRs).
- the ANR function resides in a base station (e.g., an eNB or a gNB) and manages the Neighbor Cell Relation Table (NCRT).
- the ANR function includes a Neighbor Detection Function (NDF) that functions to identify new neighbors of the base station and add these new neighbors to the NCRT.
- NDF Neighbor Detection Function
- the ANR function also includes a Neighbor Removal Function (NRF) which removes outdated NRs.
- the serving cell’s relation to said new cell is updated (controlled) by an Operation & Maintenance (O&M) server, typically with entries according to no remove (i.e., eNB must not remove this cell from the NCRT), no handover (i.e., no handover shall be initiated into this cell), or no X2 (excludes the establishment of the logical X2 interface to this identified cell and its serving eNB).
- O&M Operation & Maintenance
- An object of this disclosure is to enable reduced latency .
- XR services using remote rendering i.e., rendering of video elements by a device that is remote from the XR user device that functions to display the video elements to a user
- remote rendering i.e., rendering of video elements by a device that is remote from the XR user device that functions to display the video elements to a user
- connections points e.g., cells
- This service re-establishments may cause latency spikes and potentially also degradation in the XR services.
- the target BS in the negotiation procedure following a handover between the serving base station (BS) (a.k.a., source base station) and target BS, the target BS is responding to the handover notification with an ACK/NACK if the target BS determines whether it can support the UE being handed over.
- the target BS determines whether it can support the incoming UE by only looking at certain internal processing resources and/or air interface resources. That is, the target BS does not consider other resources, such as, for example, processing resources for producing application layer data for the UE (e.g., processing resources for rendering video elements for an XR user device).
- a method performed by a base station, for managing handover execution.
- the method includes storing first neighbor cell relation (NCR) information for a first target cell, wherein the first NCR information comprises: i) a first cell identifier for identifying the first target cell and ii) processing unit (PU) information indicating whether or not the target cell has at least one PU available.
- the method further includes evaluating whether or not to initiate a handover of a user equipment (UE) from the source cell to the target cell, wherein the evaluation is based at least in part on the PU information for the target cell.
- UE user equipment
- a computer program comprising instructions which when executed by processing circuitry of a base station causes the base station to perform the method.
- a carrier containing the computer program wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.
- the base station is adapted to perform the method of any embodiments disclosed herein.
- the base station includes processing circuitry; and a memory containing instructions executable by the processing circuitry, whereby the base station is operative to perform the methods disclosed herein.
- An advantage of the embodiments disclosed herein is that the target base station can consider additional resources when determining whether the target base station is capable of serving the incoming UE and this can lead to that latency can be reduced, which will lead to higher Quality of Experience for the user as well as potentially increasing the battery life of the user’s UE.
- FIG 1 illustrates a communication system according to an embodiment.
- FIG. 2 illustrates a gaming system according to an embodiment.
- FIG. 3 is a flowchart illustrating a process according to an embodiment.
- FIG. 4 is a block diagram of a base station according to an embodiment.
- FIG . 1 illustrates a communication system 100 according to an embodiment.
- communication system communicates with a UE 102 and includes a set of base stations (base station 104 and base station 106), and a set of “remote” PUs (PU 111, PU 112, PU 113) (the PUs are “remote” from the UE’s perspective).
- base station 104 and base station 106 a set of “remote” PUs
- PU 111, PU 112, PU 113 the PUs are “remote” from the UE’s perspective.
- FIG. 1 is illustrative only and that communication system 100 may communicate with any number of UEs and include any number of base stations, PUs, and PU selection functions.
- a user equipment (UE) is any device capable of communicating with a remote PU directly or indirectly via an access network.
- Examples of a UE include: a smartphone, a home computer, a head-mounted display (HMD), a gaming console, a streaming device, a tablet, an appliance, a sensor, a vehicle, a gateway, a router, etc.).
- HMD head-mounted display
- UE 102 is mobile and can move from the coverage area of base station 104 to the coverage area of base station 106 (these coverage areas may partially or fully overlap).
- a “base station” is any access point that provides network connectivity to a UE.
- Such access points include, but are not limited to: 3GPP LTE base stations (usually denoted “eNB”); 3GPP NR base stations (usually denoted “gNB”); and non-3GPP base stations (e.g., wireless local area network (WLAN) access points).
- eNB 3GPP LTE base stations
- gNB 3GPP NR base stations
- WLAN wireless local area network
- Future access points like base stations for a future 6 th generation (6G) wireless communication network, are also envisioned as applicable.
- 6G 6 th generation
- UE 102 is running a gaming application that is operable to be served by a remote PU.
- the gaming application is operable to 1) provide to the remote PU user input information (UII) specifying one or more actions the user of the UE has performed and 2) receive video frames rendered by the remote PU, which video frames may be rendered based on the UII.
- the gaming application can be served by any one or more of remote PU 111, remote PU 112, or remote PU 113.
- UE 102 may contain a local PU 103 that can serve the gaming application (e.g., the local PU can perform all the video rendering).
- FIG. 2 illustrates UE 102 communicating with a system 200 (e.g., a gaming system, an XR system, etc.).
- UE 102 includes a display unit 202 and a control unit 204.
- System 200 includes server 230 and a PU 220 that comprises a GPU 222. Any one of remote PUs 111, 112, 113 may implement PU 220.
- GPU 222 functions to render video frames, which are then transmitted to UE 102 and processed by display unit 202 (e.g., display unit 202 receives the video frames and displays corresponding images on a display device of the UE).
- Control unit 204 functions to detect user actions (e.g., movements of the user or the user activating a control) and to provide to PU 220 user input information (UII) specifying one or more actions the user of the UE has performed.
- This user input information may be used by GPU 222 to render the video frames and it may be forwarded to server 230. Additionally, server 230 may forward to PU 220 state information (SI) (which may include UII related to other users), and GPU 222 may also use this state information to render the video frames.
- SI PU 220 state information
- FIG. 2 illustrates, information that is needed to render the video frames can be provided to the PU 220. Accordingly, the rendering can be moved completely to the PU 220 (which may be in or near a base station), thereby allowing the UE 102 to be used only for controls and as the display.
- edge cloud connected XR glasses such as transmission delay and jitter
- other non-access related resource metrics should be considered in a decision process related to mobility.
- relevant and/or accessible XR processing resources may be associated with different base stations.
- the extended NRCT indicates whether a neighbor cell has any PU (e.g., GPU) resources available.
- the extended NCRT may also comprises information further describing measures associated with PU processing frame rate, data transfer delays, or similar. Another PU-related NRT entry may consider if said processing is available on-node, or if not within how many steps (with associated delays).
- UE 102 has some requirements that can be separated into radio requirements associated with the cellular connectivity and GPU requirements for, for example, video rendering. Cellular resources and GPU resources may or may not be located at one specific base station.
- both a first eNB and a second eNB may provide sufficient cellular connectivity (in terms of uplink or downlink throughput, latency, etc.), but that, for example, only the second eNB may provide enough GPU processing capabilities.
- UE 102 may benefit from having means to initiate a handover from one eNB, which is able to provide good radio connectivity but poor (or even no) associated GPU processing, to another eNB that has sufficiently good radio conditions and also the required GPU rendering capabilities. Accordingly, handover management may be motivated not only from a cellular connectivity aspect, but also from a GPU performance aspect.
- One approach to facilitate PU (e.g., GPU) based device mobility is to extend the UE reporting mechanism used for handover purposes to consider also PU rendering information so that handover between cells (e.g., between base stations) can be invoked both with respect to ordinary radio resource handling and the UE’s PU requirements.
- PU e.g., GPU
- the existing Radio Resource Control (RRC) Measurement Report framework is extended to consider, for example, GPU-rendering metric entities such as frame rate, rendering delay (total, within N node steps, etc.), rendering processing memory (total, consecutive, etc.), etc.
- RRC Radio Resource Control
- GPU-rendering metric entities such as frame rate, rendering delay (total, within N node steps, etc.), rendering processing memory (total, consecutive, etc.), etc.
- PU-related condition may trigger UE 102 to transmit to its serving base station an RRC Measurement Report indicating that UE 102 has detected event Pi (e.g., UE 102 has detected a PU-related condition that should be addressed).
- KPI key performance indicator
- a new message is defined (e.g., a PUQualityMeasurementReport Event Pi) so that when UE 102 detects fulfilment of certain metric-constraints may trigger transmission of said report to its currently serving base station, where the events may, for example, relate to aspects of rendering frame rate, aspects of rendering delay, aspects of PU rendering node processing memory, etc.
- the Pi events may, for example, relate to: Pl: Aspects of rendering frame rate
- P4 Aspects ofPU platform characteristics (driver version, Nvidia/ AMD platform) etc.
- the UE’s serving base station may decide to initiate a UE handover in the cellular domain so that the device is to be managed by a base station that has sufficient PU resources available (or associated).
- a devicemeasure that triggers an Event Pi report may be e.g. related to e.g. current PU-provided rendering frame rate, rendering delay, for example:
- P2c - PU measure X at source base station > threshold, and been so during TimerPU.
- the UE’s serving (source) base station may start preparing for a cellular handover of the UE to a target (from radio perspective accessible) base station.
- the base station may evaluate if the intended target cell as being indicated in any of the received reports are valid for a PU-related mobility event, and act accordingly.
- One of first steps of said evaluation includes the base station determining whether the intended target cell (e.g., the cell for which the UE reports a beneficial KPI) is valid for intended handover action; this information is may be obtained from the NCRT.
- a GPU frames-per-second (FPS) metric has either been benchmarked on the node itself or taken from a publicly available database. For gaming, this should be a score that is calculated on several scenes, preferably from very different games or benchmark suites. In one embodiment this FPS-metric could be binned for different resolutions ( ⁇ UHD: 14fps, 1080p: 38fps, 720p: 70 fps ⁇ etc). For 90+ fps, this can also be CPU bound so the precision of the performance estimate for the whole rendering setup can be enhanced if the benchmark is run on the exact hardware. The benchmark number can both be based on average fps on these scenes or (probably better), the lowest 5% percentile. This way it describes the capabilities you can count on in 95% of the cases.
- FPS GPU frames-per-second
- the serving base station assuming the serving base station decides to prepare for a handover of the UE to the target cell, the serving base station provides to the target base station information related to the UE’s “cellular connectivity” resource requirements and PU resource requirements. In one embodiment, the serving base station provides this information to the target base station in an X2AP message (e.g., X2AP Resource Status Request message). Upon receiving the information from the serving base station, the target base station will decide whether it is able to satisfy the UE’s requirements (cellular and PU) and transmit to the serving base station either a positive acknowledgement (ACK) indicating that the target base station and meet the requirement or a negative acknowledgement (NACK) indicating the opposite.
- ACK positive acknowledgement
- NACK negative acknowledgement
- the target base station responds to the X2AP Resource Status Request message by transmitting to the serving base station an X2AP Resource Status Response message that includes the ACK/NACK.
- the source base station decides whether to continue the handover procedure.
- the serving base station locally stores information on neighboring base stations available (local or associated) PU resources. Accordingly, in this embodiment the serving base station need not send to the target base station the status request message, but rather the serving base station decides whether to continue the handover procedure based on the information that it has locally stored. That is, based on the information that the serving base station has about the target base stations available PU resources, the serving base station evaluates if the UE’s ongoing PU resource requirements may be fulfilled by PU resources available to the target base station.
- the serving base station transmits a handover request to the target base station, and, assuming the target responds with an ACK, the serving base station instructs the UE to commence with change of its serving base station to the target.
- the serving base station so instructs the UE by transmitting to the UE an RRC Connection Reconfiguration Request.
- the serving base station after initiating the handover, provides to the target base station: PU-related buffer content for the target base station to consider for starting PU rendering and information of what future position (frame) in data the data flow to the device should be swapped.
- the serving base station may obtain PU resource information for the target base station from either a locally stored database (e.g., an NCRT) or from the target base station itself (e.g., over the X2 interface), and provide to the UE the obtained PU resource information using, for example, dedicated (RRC) signaling.
- a locally stored database e.g., an NCRT
- RRC dedicated
- This “other than serving base station PU information” in combination with already existing radio measurement information may be used by the UE to conduct a more detailed and joint “signal strength and PU-resource availability” evaluation, and based on that, trigger a joint “RRM+PU”-MeasurementReport Event that may be subject to a tradeoff between quality of the cellular connectivity available with source/target base station and whatever PU resource respective source/target base station may provide.
- radio measurement information e.g., Reference Signal Received Power (RSPR) and/or Reference Signal Received Quality (RSRQ) as is used for legacy mobility evaluations
- RSPR Reference Signal Received Power
- RSRQ Reference Signal Received Quality
- the UE itself decides whether to initiate a handover from the serving to the target based not only on the radio signal conditions at the serving and target base stations, but also based on the PU conditions at the serving and target base stations. Accordingly, the UE may consider if it is worth moving from serving to target given an achievable improvement of a PU-related metric of x% (e.g. reduced latency, higher resolution, higher frame rate, etc.) in comparison to a potential reduction of y dB RSRP/RSRQ where the latter would impairing the cellular connectivity. For instance, if x% is greater than a first threshold and y dB is less than a second threshold, then UE will decide to initiate the handover from the serving to the target.
- a PU-related metric of x% e.g. reduced latency, higher resolution, higher frame rate, etc.
- the NCRT is extended with respect to PU processing availability.
- a GPU-extended NCRT may hold entries that block and/or admit handover to a target cell with respect to the cell (directly or in association) having any (or deemed sufficient) GPU processing capabilities.
- a source base station is provided with a means to manage handover execution to a target base station depending on GPU metrics; either a complete handover may be admitted given that both cellular and GPU resource handling at target base station are determined “OK,” or that any partial handover (e.g., cellular metric not OK, but GPU metric OK) may be evaluated but non-continued with given that the cellular demand is found not OK. Or the other way around (e.g., cellular metric OK, but GPU metric not OK).
- a corresponding PU NRT entry may comprise a PU-resource availability column, where “yes” or similar is associated with any PU processing capabilities, and “no” otherwise. See e.g. Table 1 below.
- Table 1 Extended Neighbor Relation Table including PU availability entries I
- the above illustrated table is “target-cell centric” where Target Cell Identifier (TCI) identifies the target cell and NR (Neighbor Relations) as any originating source cell that UE may arrive from.
- TCI Target Cell Identifier
- NR Neighbor Relations
- the “No remove” column if checked, indicates that the base station shall not remove the Neighbour Cell Relation from the NCRT
- the “No HO” column if checked, indicates that the Neighbour Cell Relation shall not be used by the base station for handover reasons.
- the “No X2” column if checked, indicates that the Neighbour Relation shall not use an X2 interface in order to initiate procedures towards the base station serving the target cell.
- an extended NCRT may also comprise entries further describing PU frame rate, data transfer delays, or similar.
- Table 2 such an extended NCRT is illustrated.
- each entry in an extended NCRT may contain the following data fields: PU available, Delay metric, and FPS metric, in addition to the conventional fields of No remove, No HO, and No X2.
- the PU available field may contain a Boolean value indicating whether or not PU processing capabilities are available at the base station or within some predefined reach (e.g., a predefined number of steps) of the base station.
- the Delay metric field contains a delay metric that is a threshold value that processing resource could respond with (provide) at x% probability.
- the delay metrics (Di) may be considered reflecting perceived delay from the processing node.
- the value of the Delay metric may be set under the assumption that a typical value (e.g., X ms) to render a default resolution.
- the FPS metric field contains a measure on frame rendering capability.
- the value of the FPS metric may specify that the available PU could respond with (provide) at y% probability.
- the base station may determine the device’s frame rendering requirement.
- Table 3 below illustrates yet another possible embodiment of an NCRT table, which may be used by a source base station to determine whether or not a given detected base station should be selected for a handover.
- requested PU processing capabilities are not located on the same node as the base station, but still associated and potentially accessible to the base station within a number of steps (i.e., ‘GPU node steps’) in the network.
- the Delay metric can be set based on the PU node steps value as it is plausible that processing resources further steps away from the base station node may be associated with a delay figure representative for the characteristics for said communications links. That is, there may be a direct correlation between the PU nodes steps value and a delay value, which delay value can be added to the Delay metric.
- Table 4 illustrates yet another possible embodiment.
- aggregated high-level table entries are defined. More specifically, as illustrated in Table 4, two classes of PU requirements are defined: “Low” and “High.” Each such requirement has the following corresponding fields: No remove, No HO and No X2. Accordingly, each entry (row) of the table includes the following fields: NR; TCI; No remove, No HO, and No X2 for PU requirement Low; and No remove, No HO, and No X2 for PU requirement High.
- the base station may classify the UE has requiring “High” or “Low” PU resources. That is, based on, for example, a delay value and a FPS value, the base station can map this value pair to either category High or category Low. And then, depending on the mapping, use the appropriate fields from the extended NCRT.
- the serving base station may consider to follow cell relation rules as outlined in the extended neighbor relation table for the entry GPU requirement “High.”
- a UE in the context of a handover event that is reporting GPU attributes associated with a less demanding GPU rendering may be associated with the GPU requirement “Low” and potentially comply with other cell relation rules.
- a UE GPU-related measurement report may, according to Table 4, aggregate GPU requirements and provide the serving base station with an aggregated GPU measure according to “high”, “low”, etc.
- additional or alternative PU attributes may be added to the NCRT, such as, for example, RAM availability, inferencing machine learning (ML) model availability, green processing capabilities, etc.
- FPS is typically dependent on resolution and scene complexity, and, therefore, floating operations per second (Flops) could be used instead with separate numbers per bit depth (Single precision, double etc.).
- platform support can be important. Docker, Tensorflow, torch, python version capabilities, etc. should be handshaked between model server and edge rendering device, screening some edge rendering devices for the ongoing session, both for inferencing and model training.
- FIG. 3 is a flowchart illustrating a process 300, according to an embodiment, for managing handover execution.
- Process 300 may be performed by base station 104 and may begin in step s302.
- Step s302 comprises storing first neighbor cell relation (NCR) information for a first target cell, wherein the first NCR information comprises: i) a first cell identifier for identifying the first target cell and ii) processing unit (PU) information indicating whether or not the target cell has at least one PU available.
- Step s304 comprises evaluating whether or not to initiate a handover of a UE (e.g., UE 102) from the source cell to the target cell, wherein the evaluation is based at least in part on the PU information for the target cell.
- a UE e.g., UE 102
- the PU information comprises PU performance information for at least a first PU, and, in some embodiments, the PU performance information for the first PU comprises video frame rendering capability information and/or a delay metric.
- the video frame rendering capability information comprises a time value indicating an estimated amount of time that it will take the first PU to produce a result (e.g., rendering a video frame or producing an inference). Accordingly, in some embodiments the time value indicates an estimated amount of time to render a video frame having a particular resolution and/or a particular set of fidelity settings, or the time value indicates an estimated amount of time to produce an inference.
- the PU performance information further comprises information specifying distance (e.g., a number of steps or hops) between an available PU and the base station.
- fidelity settings include: an anti-aliasing setting (e.g. off, on, fast approximate anti-aliasing (FXAA), ...); a shadow quality setting (e.g., low, medium, or high); a texture quality setting (e.g., low, medium, high); a tessellation setting (e.g., on or off); a deep learning super sampling (DLSS) setting (e.g., on or off); and a ray tracing setting (e.g., on or off).
- an anti-aliasing setting e.g. off, on, fast approximate anti-aliasing (FXAA), ...
- a shadow quality setting e.g., low, medium, or high
- a texture quality setting e.g., low, medium, high
- a tessellation setting e.g., on or off
- process 300 further includes obtaining for the UE a threshold time value indicating a threshold amount of time, wherein the evaluation as to whether or not to initiate the handover of the UE from the source cell to the target cell is further based on the PU performance information and the threshold time value.
- the threshold time value is based on a video frame rate. In some embodiments the threshold is equal to the reciprocal of the video frame rate.
- process 300 also includes receiving an event report message transmitted by the UE, wherein the step of evaluating whether or not to initiate the handover of the UE from the source cell to the target cell is performed as a result of receiving the event report message.
- the event report message includes the threshold time value.
- the event report message further includes reference signal measurement information for the target cell.
- the event report message is a PU quality measurement report, wherein the PU quality measurement report indicates that the UE has detected a PU related event.
- the PU quality measurement report comprises information indicating that a key performance indicator, KPI, for a PU currently serving the UE has met a criterion (e.g., the KPI exceeds a threshold or has fallen below a threshold).
- receiving the PU quality measurement report comprises receiving a Radio Resource Control (RRC) Measurement Report message comprising the PU quality measurement report.
- RRC Radio Resource Control
- FIG. 4 is a block diagram of base station 104, according to some embodiments.
- base station 104 may comprise: processing circuitry (PC) 402, which may include one or more processors (P) 455 (e.g., one or more general purpose microprocessors and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., base station 104 may be a distributed computing apparatus); a network interface 468 comprising a transmitter (Tx) 465 and a receiver (Rx) 467 for enabling base station 104 to transmit data to and receive data from other nodes connected to a network 40 (e.g., an Internet Protocol (IP) network) to which network interface 468 is connected; communication circuitry 448, which is coupled to an antenna arrangement 449 comprising one or more antennas and which comprises
- IP Internet Protocol
- a computer program product (CPP) 441 may be provided.
- CPP 441 may be or includes a computer readable storage medium (CRSM) 442 storing a computer program (CP) 443 comprising computer readable instructions (CRI) 444.
- CRSM 442 may be a non-transitory computer readable storage medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like.
- the CRI 444 of computer program 443 is configured such that when executed by PC 402, the CRI causes base station 104 to perform steps described herein (e.g., steps described herein with reference to the flow charts).
- base station 104 may be configured to perform steps described herein without the need for code. That is, for example, PC 402 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP21923485.3A EP4285640A4 (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
PCT/SE2021/050052 WO2022164358A1 (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
CN202180092020.4A CN116783935A (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
US18/274,256 US20240107395A1 (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/SE2021/050052 WO2022164358A1 (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022164358A1 true WO2022164358A1 (en) | 2022-08-04 |
Family
ID=82653741
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2021/050052 WO2022164358A1 (en) | 2021-01-27 | 2021-01-27 | Managing handover execution |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240107395A1 (en) |
EP (1) | EP4285640A4 (en) |
CN (1) | CN116783935A (en) |
WO (1) | WO2022164358A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120176892A1 (en) * | 2011-01-12 | 2012-07-12 | Kddi Corporation | Handover Parameter Control Apparatus and Method, and Computer Program |
WO2012112087A1 (en) * | 2011-02-14 | 2012-08-23 | Telefonaktiebolaget L M Ericsson (Publ) | Method and arrangement for automated handling of neighbour cell relations |
US20200221521A1 (en) * | 2019-01-07 | 2020-07-09 | At&T Intellectual Property I, L.P. | Facilitating automatic neighbor relationships for 5g or other next generation network |
WO2020229445A1 (en) * | 2019-05-15 | 2020-11-19 | Nokia Technologies Oy | Proactive triggering of handovers in telecommunication networks |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2472792A (en) * | 2009-08-17 | 2011-02-23 | Nec Corp | Measurement reporting in a mobile communications system |
CN110115063B (en) * | 2017-01-05 | 2020-12-22 | 华为技术有限公司 | Network apparatus and method for handover |
US10694439B2 (en) * | 2018-11-13 | 2020-06-23 | Verizon Patent And Licensing Inc. | Systems and methods for assignment of multi-access edge computing resources based on network performance indicators |
-
2021
- 2021-01-27 CN CN202180092020.4A patent/CN116783935A/en active Pending
- 2021-01-27 WO PCT/SE2021/050052 patent/WO2022164358A1/en active Application Filing
- 2021-01-27 EP EP21923485.3A patent/EP4285640A4/en active Pending
- 2021-01-27 US US18/274,256 patent/US20240107395A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120176892A1 (en) * | 2011-01-12 | 2012-07-12 | Kddi Corporation | Handover Parameter Control Apparatus and Method, and Computer Program |
WO2012112087A1 (en) * | 2011-02-14 | 2012-08-23 | Telefonaktiebolaget L M Ericsson (Publ) | Method and arrangement for automated handling of neighbour cell relations |
US20200221521A1 (en) * | 2019-01-07 | 2020-07-09 | At&T Intellectual Property I, L.P. | Facilitating automatic neighbor relationships for 5g or other next generation network |
WO2020229445A1 (en) * | 2019-05-15 | 2020-11-19 | Nokia Technologies Oy | Proactive triggering of handovers in telecommunication networks |
Non-Patent Citations (1)
Title |
---|
See also references of EP4285640A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP4285640A1 (en) | 2023-12-06 |
EP4285640A4 (en) | 2024-03-27 |
CN116783935A (en) | 2023-09-19 |
US20240107395A1 (en) | 2024-03-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11109252B2 (en) | Method and apparatus for adjusting network configuration based on channel busy ratio in wireless communication system | |
WO2021077267A1 (en) | Cell reselection method and apparatus, and communication device | |
EP3993320A1 (en) | Training method, device, and system using mos model | |
US20180376380A1 (en) | Exposure of capabilities of central units and distributed units in base station entities for admission control | |
US20230103163A1 (en) | Method and apparatus for modifying configuration related to conditional mobility in wireless communication system | |
US20240056917A1 (en) | Method and apparatus for mobility in dual connectivity in wireless communication system | |
US20220345932A1 (en) | Reporting Information Sending Method, Apparatus, and System | |
CN105792290A (en) | Method and device for controlling intelligent terminal to perform wireless roaming | |
Coronado et al. | Joint mobility management and multicast rate adaptation in software–defined enterprise WLANs | |
US20210022056A1 (en) | Method and apparatus for deprioritizing access on unlicensed band based on ue preference in wireless communication system | |
JP2021503251A (en) | Methods and equipment for managing Pcell or PScell | |
US20210385646A1 (en) | End to end troubleshooting of mobility services | |
US11877195B2 (en) | Method and apparatus for cell reselection in wireless communication system | |
US20230038430A1 (en) | Network-based adaptive streaming media parameter adjustment method and an apparatus | |
US20220150784A1 (en) | Handover method and apparatus | |
US11889568B2 (en) | Systems and methods for paging over WiFi for mobile terminating calls | |
US20220225128A1 (en) | Information Update Method, Device, and System | |
US12089094B2 (en) | Communication after mobility in wireless communication system | |
US20230403713A1 (en) | Native computing power service implementation method and apparatus, network device, and terminal | |
JP2023529445A (en) | How to improve the functionality of the NWDAF so that SMF can effectively duplicate transmissions | |
CN113973390B (en) | Communication method and device | |
US11882496B2 (en) | Method and apparatus for mobility in wireless communication system | |
WO2021142662A1 (en) | Resource configuration method and apparatus, communication device and storage medium | |
WO2020063171A1 (en) | Data transmission method, terminal, server and storage medium | |
US20240107395A1 (en) | Managing handover execution |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21923485 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112023014434 Country of ref document: BR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18274256 Country of ref document: US Ref document number: 202180092020.4 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021923485 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021923485 Country of ref document: EP Effective date: 20230828 |