WO2023115260A1

WO2023115260A1 - Method and apparatus of supporting user equipment (ue) status prediction

Info

Publication number: WO2023115260A1
Application number: PCT/CN2021/139680
Authority: WO
Inventors: Congchi ZHANG; Mingzeng Dai; Le Yan
Original assignee: Lenovo (Beijing) Limited
Priority date: 2021-12-20
Filing date: 2021-12-20
Publication date: 2023-06-29
Also published as: CN118369956A; GB202409532D0; GB2629091A

Abstract

Embodiments of the present application relate to a method and apparatus of supporting user equipment (UE) status prediction. An exemplary method may include: transmitting, by a first radio access network (RAN) node, a first message indicating a request for information related to UE status prediction; and receiving, by the first RAN node, a second message from a second RAN node, indicating a response to the request indicated in the first message.

Description

METHOD AND APPARATUS OF SUPPORTING USER EQUIPMENT (UE) STATUS PREDICTION

TECHNICAL FIELD

Embodiments of the present application are related to wireless communication technology, especially, related to artificial intelligence (AI) application in wireless communication, e.g., a method and apparatus of supporting UE status prediction.

BACKGROUND OF THE INVENTION

AI, at least including machine learning (ML) is used to learn and perform certain tasks via training neural networks (NNs) with vast amounts of data, which is successfully applied in computer vison (CV) and nature language processing (NLP) areas. Deep learning (DL) , which is a subordinate concept of ML, utilizes multi-layered NNs as an “AI model” to learn how to solve problems and/or optimize performance from vast amounts of data.

By leveraging the advantage of AI, the performance of radio access network (RAN) network can be further optimized in at least the following use cases: energy saving, load balancing, traffic steering and mobility optimization. Thus, 3rd generation partnership program (3GPP) has been considering to introduce AI into 3GPP since 2016, including several study items and work items in SA1, SA2, SA5 and RAN3. For example, a study item has been approved in RP-201620 to look into:

a) Study standardization impacts for the identified use cases including: the data that may be needed by an AI function as input and data that may be produced by an AI function as output, which is interpretable for multi-vendor support;

b) Study standardization impacts on the node or function in current NG-RAN architecture to receive/provide the input/output data; and

c) Study standardization impacts on the network interface (s) to convey the input/output data among network nodes or AI functions.

However, there are still a mass of issues have not been discussed in 3GPP. Taking UE status prediction as an example, the RAN node may need to predict the status of UE, such as trajectory and traffic load of the UE, and use the predicted status of UE for network optimization. To support that, several technical problems need to be solved. For example, mechanisms are needed for the RAN node (also referred to "old RAN node" or "source RAN node" in such scenarios) to understand the actual status of UE when the UE has been switched to another RAN node (also referred to as "new RAN node" or "target RAN node" in such scenarios) , and mechanisms are needed for the new RAN node to determine the prediction accuracy and inform the old RAN node.

Therefore, the industry needs to propose a technical solution at least supporting UE status prediction to achieve and improve AI application in further long-term evolution (LTE) of RAN.

SUMMARY

One objective of the embodiments of the present application is to provide a technical solution for wireless communication, especially for supporting UE status prediction in wireless communication.

Some embodiments of the present application provide a RAN node, which includes: at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one receiving circuitry and the at least one transmitting circuitry. The at least one processor is configured to: transmit, via the at least one transmitting circuitry, a first message indicating a request for information related to UE status prediction; and receive, via the at least one receiving circuitry, a second message from a second RAN node to the RAN node, indicating a response to the request indicated in the first message.

In some embodiments of the present application, the RAN node is a source node and the second RAN node is a target RAN node during a handover procedure for a UE.

According to some embodiments of the present application, the request for information related to UE status prediction may include: requesting the second RAN node to inform the RAN node actual UE status information at least of the UE to be measured at required time point (s) ; or requesting the second RAN node to inform the RAN node average UE status information at least of the UE to be measured every required time interval during a required time window; or requesting the second RAN node to inform the RAN node a required number of actual UE status information at least of the UE to be measured.

According to some embodiments of the present application, the first message is a handover request message during the handover procedure, and the second message is a handover request acknowledge message in response to the handover request message, indicating whether to accept the request. According to some other embodiments of the present application, the first message is a mobility change request message before the handover procedure, and the second message is a mobility change request acknowledge message during the handover procedure, indicating whether to accept the request. According to some yet other embodiments of the present application, the first message is a UE associated Xn message during a UE associated bi-directional procedure after the handover procedure and before context of the UE being released by the second RAN node; and the second message is another UE associated Xn message during the UE associated bi-directional procedure, indicating whether to accept the request. According to some yet other embodiments of the present application, the first message is a non-UE associated Xn message, and the second message is another non-UE associated Xn message indicating whether to accept the request.

According to some embodiments of the present application, the first message further includes: an event identity (ID) for status prediction of the UE to associate UE status prediction information with the information related to UE status prediction requested from the second RAN node.

According to some embodiments of the present application, in the case that the second message indicates a response of accepting the request, the at least one processor is configured to: receive the information related to UE status prediction from the second RAN node via a UE associated Xn message or via a non-UE associated Xn message with an event ID for status prediction of the UE provided by the RAN node, wherein the information related to UE status prediction of the UE is actual status information of the UE.

In some embodiments of the present application, the RAN node is a node sending a UE to one of an inactive state and idle state and the second RAN node is a node under which the UE enters a connected state from the one of the inactive state and the idle state, and the information related to UE status prediction is actual status information of the UE.

According to some embodiments of the present application, the first message is a retrieve UE context response message in response to a retrieve UE context request message from the second RAN node, requesting the second RAN node to send actual UE status information logged by the UE during the one of the inactive state and the idle state; and the second message is a UE associated Xn message or a non-UE associated Xn message an event ID for status prediction of the UE provided by the RAN node, for sending the actual UE status information in response to the first message.

According to some embodiments of the present application, the first message is a downlink radio resource control (RRC) signaling for sending the UE to the one of the inactive state and the idle state, requesting the UE to report actual UE status information to the RAN node after entering the connected state, wherein the actual UE status information is logged by the UE during the one of the inactive state and the idle state; and the second message is a retrieve UE context request message with the actual UE status information.

In some embodiments of the present application, the RAN node is a target node, the second RAN node is a source RAN node during a handover procedure for a UE, and the at least one processor of the RAN node is configured to: receive a third message from the second RAN node, indicating UE status prediction information available in the second RAN node before transmitting the first message; and transmit the first message in response to the third message indicating whether the UE status prediction information is demanded.

According to some embodiments of the present application, in the case that the first message indicates the UE status prediction information is demanded, the first message requests at least part of the UE status prediction information available in the second RAN node; and the second message indicates the at least part of the UE status prediction information requested by the RAN node. For example, both the first message and the third message may be UE associated Xn messages before the handover procedure is executed. The second message may be a handover request message during the handover procedure or a non-UE associated Xn message indicating an event ID for status prediction of the UE. In another example, the third message may be a handover request message during the handover procedure, and the first message is a handover request acknowledge message in response to the handover request message. The second message is a UE associated Xn message before the RAN node releases context of the UE, or is a non-UE associated Xn message indicating an event ID for status prediction of the UE.

According to some embodiments of the present application, the second message or the third message further requests at least one of the following feedback from the RAN node: accuracy of the at least part of the UE status prediction information determined by the RAN node; confidence level of the at least part of the UE status prediction information determined by the RAN node; standard deviations of the at least part of the UE status prediction information determined by the RAN node; or actual UE status information measured by the RAN node. In the case that the RAN node is unable to provide the feedback requested in the third message, the at least one processor is configured to: transmit a non-UE Xn message with an event for status prediction of the UE provided by the second RAN node.

According to some embodiments of the present application, the first message requests at least part of the UE status prediction information by indicating one of the following: only UE status prediction information at required time point (s) is interested; only average UE status prediction information every required time interval during a required time window is interested; only a required number of UE status prediction information to be measured is interested; and only UE status prediction information under coverage of the RAN node is interested.

Some other embodiments of the present application provide a RAN node, which includes: at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one receiving circuitry and the at least one transmitting circuitry. The at least one processor is configured to: receive, via the at least one receiving circuitry, a first message indicating a request for information related to UE status prediction; and transmit, via the at least one transmitting circuitry, a second message from the RAN node to a second RAN node, indicating a response to the request indicated in the first message.

In some embodiments of the present application, the second RAN node is a source node and the RAN node is a target RAN node during a handover procedure for a UE.

According to some embodiments of the present application, the at least one processor is configured to: in the case of transmitting the second message indicates a response of accepting the request, transmit the information related to UE status prediction to the second RAN node via a UE associated Xn message or a non-UE associated Xn message with an event ID for status prediction of the UE provided by the second RAN node, wherein the information related to UE status prediction of the UE is actual UE status information of the UE. For example, the information related to UE status prediction is transmitted in response to at least one of the following: the UE is handover to a third RAN node in a connected state; the UE is sent to an inactive state or an idle state by the RAN node; the UE connects to the RAN node or a third RAN node in a connected state after being sent to an inactive or an idle state by the RAN node, and the RAN node receives logged actual UE status information from the UE; or logged actual UE status information has fulfilled requirement (s) as indicated by the second RAN node.

In some embodiments of the present application, the second RAN node is a node sending a UE to one of an inactive state and an idle state and the RAN node is a node under which the UE enters a connected state from the one of the inactive state and the idle state, and the information related to UE status prediction is actual status information of the UE.

According to some embodiments of the present application, the first message is a retrieve UE context response message in response to a retrieve UE context request message from the RAN node, requesting the RAN node to send actual UE status information logged by the UE during the one of the inactive state and the idle state; and the second message is a UE associated Xn message or a non-UE associated Xn message an event ID for status prediction of the UE provided by the second RAN node, for sending the actual UE status information in response to the first message.

According to some embodiments of the present application, the first message is a message from the UE entering the connected state, indicating the RAN node to send actual status information logged by the UE during the one of the inactive state and the idle state to the second RAN node; and the second message is a UE associated Xn message or a non-UE associated Xn message with an event ID for status prediction of the UE provided by the second RAN node for sending the actual UE status information.

In some embodiments of the present application, the RAN node is a source node, the second RAN node is a target RAN node during a handover procedure for a UE, and the at least one processor of the RAN node is configured to: transmit a third message to the RAN node, indicating UE status prediction information available in the RAN node; and receive the first message in response to the third message indicating whether the UE status prediction information is demanded.

According to some embodiments of the present application, in the case that the first message indicates the UE status prediction information is demanded, the first message requests at least part of the UE status prediction information available in the RAN node; and the second message indicates the at least part of the UE status prediction information requested by the second RAN node. For example, the first message requests at least part of the UE status prediction information by indicating one of the following: only UE status prediction information at required time point (s) is interested; only average UE status prediction information every required time interval during a required time window is interested; only a required number of UE status prediction information to be measured is interested; and only UE status prediction information under coverage of the RAN node is interested.

Some yet other embodiments of the present application proposes a method, which includes: transmitting, by a first RAN node, a first message indicating a request for information related to UE status prediction; and receiving, by the first RAN node, a second message from a second RAN node, indicating a response to the request indicated in the first message.

Given the above, embodiments of the present application propose a technical solution of supporting UE status prediction, and will facilitate the implementation of AI-based RAN.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which advantages and features of the present application can be obtained, a description of the present application is rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. These drawings depict only exemplary embodiments of the present application and are not therefore intended to limit the scope of the present application.

FIG. 1 is a schematic diagram illustrating an exemplary wireless communication system according to some embodiments of the present application.

FIG. 2 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction according to some embodiments of the present application.

FIG. 3 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction according to some other embodiments of the present application.

FIG. 4 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction in Case 1 according to some embodiments of the present application.

FIG. 5 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction in Case 5 according to some embodiments of the present application.

FIG. 6 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction in Case 3 according to some embodiments of the present application.

FIG. 7 illustrates a block diagram of a wireless communication apparatus of supporting AI according to some embodiments of the present application.

FIG. 8 illustrates a block diagram of a wireless communication apparatus of supporting AI according to some other embodiments of the present application.

DETAILED DESCRIPTION

The detailed description of the appended drawings is intended as a description of the currently preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.

Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architecture and new service scenarios, such as 3GPP 5G, 3GPP long-term evolution (LTE) , and so on. It is contemplated that along with the developments of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems. Moreover, the terminologies recited in the present application may change, which should not affect the principle of the present application.

FIG. 1 illustrates a schematic diagram of an exemplary wireless communication system 100 according to some embodiments of the present application.

As shown in FIG. 1, the wireless communication system 100 includes at least one BS 101 and at least one UE 102. In particular, the wireless communication system 100 includes one BS 101 and two UE 102 (e.g., a first UE 102a and a second UE 102b) for illustrative purpose. Although a specific number of BSs and UEs are illustrated in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or less BSs and UEs in some other embodiments of the present application.

The wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.

The BS 101 may communicate with a core network (CN) node (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , a mobility management function (AMF) or a user plane function (UPF) etc. via an interface. A BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art. In 5G NR, a BS may also refer to as a RAN node or network apparatus. Each BS may serve a number of UE (s) within a serving area, for example, a cell or a cell sector via a wireless communication link. Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.

The UE 102, e.g., the first UE 102a and second UE 102b should be understood as any type terminal device, which may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like. According to an embodiment of the present application, the UE may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network. In some embodiments, the UE may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the UE may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.

If the status of UE, such as trajectory and traffic load of UE can be predicted, the performance of RAN network can be further optimized at least in energy saving, load balancing, traffic steering and mobility optimization. Considering whether the predicted UE status information will be transferred, there are two scenarios. One scenario (hereafter, Scenario#1) is: the UE status is predicted by the local RAN node (or anchored RAN node) of the UE, stored in the local RAN node, and will not be transferred to neighbor RAN node (s) . The other scenario (hereafter, Scenario#2) is: the UE status is predicted by the local RAN node of the UE, and will be transferred to the neighbor RAN node (s) and used by the neighbor RAN node.

However, there are only rough discussions on network optimization in the above two scenarios, and there are still several issues needed to be solved in 3GPP. For example, in any scenario, if the UE is switched to a new RAN node (or target RAN node) , the old RAN node (e.g., source RAN node) which previously predicted the status of the UE will not be able to know the actual status of the UE and will not be able to know if the prediction is accurate or not. Thus, mechanisms are needed for the old RAN node to understand the actual status of the UE. In addition, the size of the predicted UE status information is variable, which may be very large. Thus, when and how to transfer the predicted UE status information is appropriate should be solved. Moreover, for the predicted UE status information received from the old RAN node, the new RAN node is able to determine whether the UE status prediction made by the old RAN node is accurate or not. Thus, mechanisms are needed for the new RAN node to determine the prediction accuracy and feed back to the old RAN node.

At least to solve the above technical problem, embodiments of the present application propose a technical solution of supporting UE status prediction.

FIG. 2 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction according to some embodiments of the present application. The method can be implemented in a RAN node requesting information related to UE status prediction. In different cases, the RAN node and the requested information related to UE status prediction may be different. For example, a RAN node requesting information related to UE status prediction is a source RAN node of a UE, which previously predicted the status of the UE, requests the actual status information of the UE (i.e., information related to UE status prediction) from a target RAN node to which the UE is switched.

Referring to FIG. 2, in step 201, a RAN node, e.g., a first gNB may transmit a first message indicating a request for information related to UE status prediction, which may be transmitted to a UE or another RAN node, e.g., a second gNB. Herein, wording like "first" or "second" etc., is only used for clear expression, and should not be deemed as the sequence limitation. Considering different cases, the first message is various. For example, the first message may be transmitted from a source RAN node of a UE to a target RAN node of the UE to request actual UE status information of the UE in some embodiments of the present application. In some other embodiments of the present application, the first message may be a downlink signaling transmitted from a RAN node to a UE to send the UE to an inactive state or an idle state, which also requests the UE to report actual UE status information to the RAN node after re-entering a connected state. For example, the first message is a downlink RRC signaling for sending the UE to a RRC inactive state or a RRC idle state. In some yet other embodiments of the present application, the first message may be transmitted from a target RAN node of a UE to a source RAN node of the UE, indicating at least part of the UE status prediction information available in the source RAN node is demanded. Before that, the target RAN node may receive a message from the source RAN node, indicating the UE status prediction information available in the source RAN node.

In step 203, the RAN node, e.g., the first gNB may receive a second message from another RAN node, e.g., the second gNB, indicating a response to the request indicated in the first message. Similarly, considering different cases, the second message may be different. For example, in the case that the first message is a message transmitted from the source RAN node to the target RAN node to request actual UE status information of the UE, the second message may be a message indicating whether to accept the request. In the case that the first message is a downlink signaling for sending the UE to an inactive state or an idle state, the second message may be a message from a new RAN node of the UE for sending (or transferring, or forwarding) actual UE status information logged by the UE during the inactive state or the idle state, wherein the new RAN node is a node under which the UE enters a connected state from the inactive state or the idle state. In the case that the first message is a message indicating at least part of the UE status prediction information available in the source RAN node is demanded, the second message may be a message for sending (or transferring or forwarding) the at least part of the UE status prediction information requested by the target RAN node.

FIG. 3 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction according to some other embodiments of the present application. The method can be implemented in a RAN node responding to a request of information related to UE status prediction, e.g., receiving a first message as illustrated in FIG. 2 or the like and transmitting a second message in response to the first message.

Referring to FIG. 3, in step 301, a RAN node, e.g., the second gNB as recited above, may receive a first message indicating a request for information related to UE status prediction, which may be from another RAN node, e.g., the first gNB as recited above or from a UE. For example, as illustrated above, the first message may be received by the target RAN node of a UE from the source RAN node of the UE to request actual UE status information of the UE in some embodiments of the present application. In some other embodiments of the present application, the RAN node is a new RAN node of the UE under which the UE enters a connected state from the inactive state or idle state, and the first message is received from the UE, considering that the UE is required by an old RAN node which sent the UE to the inactive state or idle state to report actual status information of the UE to the old RAN node after entering the connected state. In some yet other embodiments of the present application, the first message may be received from a target RAN node of a UE by a source RAN node of the UE, indicating at least part of the UE status prediction information available in the source RAN node is demanded. Before that, the source RAN node may transmit a message to the target RAN node, indicating the UE status prediction information available in the source RAN node.

In step 303, the RAN node, e.g., the second gNB may transmit a second message to another RAN node, e.g., the first gNB indicating a response to the request indicated in the first message. Similarly, considering different cases, the second message may be different. For example, in the case that the first message is a message transmitted from the source RAN node to the target RAN node to request actual UE status information of the UE, the second message may be a message indicating whether to accept the request. In the case that the first message is received from a UE entering a connected state from an inactive state or idle state, the second message may be a message from the new RAN node to the old RAN node which sent the UE to the inactive state or idle state, forwarding actual UE status information logged by the UE during the inactive state or idle state. In the case that the first message is a message from a target RAN node, indicating at least part of the UE status prediction information available in a source RAN node is demanded, the second message may be a message for sending the at least part of the UE status prediction information requested by the target RAN node.

Based on the above general description, various exemplary embodiments of the present application are illustrated in view of different cases as follows.

Case 1

In Case 1, a RAN node, e.g., RAN node#1 which is a source node of a UE during a handover procedure requests information related to UE status prediction from a target RAN node, e.g., RAN node#2 during the handover procedure. For example, RAN node#1 may inform RAN node#2 via a first message whether and how RAN node#2 to transmit actual status information of the UE to RAN node#1, so that RAN node#1 is able to determine whether the UE status prediction is accurate or not by comparing the predicted UE status information with the actual UE status information. Herein, the handover procedure may be a traditional handover procedure (non-conditional handover procedure) , or a conditional handover (CHO) procedure which is executed by the UE when one or more handover execution conditions are met.

The request for information related to UE status prediction may be in various manners. For example, RAN node#1 may request RAN node#2 to inform RAN node#1 actual UE status information at least of the UE to be measured at required time point (s) . In another example, RAN node#1 may request RAN node#2 to inform RAN node#1 average UE status information at least of the UE to be measured every required time interval during a required time window, e.g., the average traffic load every 10mins in the next 1 hour. In another example, RAN node#1 may request RAN node#2 to inform RAN node#1 a required number of actual UE status information at least of the UE to be measured, e.g., the next N (N>=1) serving cells and the corresponding dwelling time.

The first message may be transmitted in various manners. For example, the first message is a handover request message during the handover procedure, or is a mobility change request message before the handover procedure; or is a UE associated Xn message during a UE associated bi-directional procedure after the handover procedure and before the context of the UE being released by RAN node#2; or is a non-UE associated Xn message. The mobility change request message and non-UE associated Xn message can be used for all handovers between two cells indicated in the corresponding message. In some embodiments of the present applicant, the first message may further include an event ID (or index) for status prediction of the UE to associate the information related to UE status prediction requested from RAN node#2 with the UE status information predicated by RAN node#1. The event ID for status prediction of the UE is different from the ID of the UE. Thereby, the received information related to UE status prediction can be mapped to the predicated status information of a specific UE. For example, during a non-UE associated bi-directional procedure, the first message is a non-UE associated Xn message with an event ID for status information of the UE to map the received actual UE status from RAN node#2 to the predicted UE status information at RAN node#1. In another example, the first message is a handover request message with an event ID, considering that the actual UE status from RAN node#2 may be transmitted by RAN node#2 after releasing the context of the UE.

After receiving the first message, RAN node#2 may transmit a second message, indicating whether the request is accepted. For example, in response to the first message being a handover request message during the handover procedure, the second message may be a handover request acknowledge message during the handover procedure, indicating whether to accept the request. In another example, in response to the first message being a mobility change request message before the handover procedure, the second message is a mobility change request acknowledge message during the handover procedure, indicating whether to accept the request. In another example, in response to the first message being a UE associated Xn message during a UE associated bi-directional procedure after the handover procedure and before the context of the UE being released by RAN node#2, the second message is another UE associated Xn message during the UE associated bi-directional procedure, indicating whether to accept the request. In yet another example, in response to the first message being a non-UE associated Xn message during a non-UE associated bi-directional procedure, the second message is another non-UE associated Xn message during the non-UE associated bi-directional procedure, indicating whether to accept the request.

In the case that RAN node#2 accepts the request, RAN node#2 will transmit the second message indicating a response of accepting the request. Accordingly, RAN node#2 will log the required actual measured UE status information when the UE is connected with RAN node#2 to transfer to RAN node#1. RAN node#2 may transfer the logged actual UE status information to RAN node#1 in response to at least one of the following: the UE is handover to a further RAN node, e.g., RAN node#3 in a connected state; the UE is sent to an inactive state or an idle state by RAN node#2; the UE connects to RAN node#2 or a further RAN node in a connected state after being sent to an inactive or an idle state by RAN node#2, and RAN node#2 receives logged actual UE status information from the UE; or logged actual UE status information has fulfilled requirement (s) as indicated by RAN node#1.

The information related to UE status prediction, e.g., actual status information of the UE may be transmitted from RAN node#2 to RAN node#1 via a UE associated Xn message or via a non-UE associated Xn message. When the non-UE associated Xn message is used, an event ID for status prediction of the UE provided by RAN node#1 will also be included in the non-UE associated Xn message, so that RAN node#1 can map the received actual status information of the UE to the predicted status information of the UE.

Referring to FIG. 4, RAN node#1 is a source node of a UE during a handover procedure and RAN node#2 is a target RAN node during the handover procedure. RAN node#1 transmits a handover request message to RAN node#2 in step 401, which includes a request of actual UE status information from RAN node#2 besides a handover request. In some embodiments of the present application, considering that RAN node#2 may transmit the actual UE status information after releasing the context of the UE, the handover request message also includes an event ID different from the ID of the UE for associating the actual UE status information with the UE's status prediction information in the future.

In step 403, RAN node#2 may transmit a handover request acknowledge message, which includes a response indicating whether to accept the request besides the handover request acknowledge information. For example, the handover request acknowledge message indicates the handover request is acknowledged and also includes a response indicating that the request of actual UE status information is accepted by RAN node#2, that is, RAN node#2 will provide the actual UE status information with the UE as required.

Then, in step 405 and step 407, RAN node#2 respectively transmits a handover success message and UE context release message to RAN node#1. After receiving the UE context release message, RAN node#1 will release the context related to the UE and store the predicted UE status information of the UE by associating with the event ID. In the case that RAN node#2 transfers the actual UE status information to RAN node#1 after releasing the context of the UE in step 409, it will not indicate any UE context. Instead, RAN node#2 will transmit the actual UE status information via a non-UE associated message with the event ID provided by RAN node#1 in step 401. After receiving the actual UE status information from RAN node#2, RAN node#1 will be able to map the actual UE status information to the predicted UE status information stored before by the event ID even if the context of the UE is wiped.

Case 2

In Case 2, the UE is connected to a RAN node, e.g., RAN node#1, and then enters an inactive state or idle state. The UE may enter the inactive state or idle state by itself or is sent to the inactive state or idle state by RAN node#1. The UE may perform cell reselection and camp on different cells in the inactive state or idle state. After re-entering the connected state, the UE will report the actual UE status information logged by the UE during the inactive state or idle state to a RAN node under which the UE enters the connected state from the inactive state or idle state. In addition, when the UE re-enters the connected state, it may still connect to RAN node#1 or connect to another RAN node, e.g., RAN node#2. In the case that the UE connects to RAN node#2 rather than RAN node#1 after re-entering the connected state, RAN node#2 may be requested to transmit the received actual UE status information logged by the UE to RAN node#1, e.g., directly by RAN node#1 or indirectly via the UE.

For example, in response to the UE connecting to RAN node#2 after re-entering the connected state, RAN node#2 will send a retrieve UE context request message to RAN node#1. RAN node#1 may transmit a retrieve UE context response message in response to the retrieve UE context request message. In some embodiments of the present application, RAN node#1 may also include a request in the retrieve UE context response message, requesting RAN node#2 to send the actual UE status information logged by the UE during the inactive state or idle state. RAN node#1 may also indicate an event ID for status prediction of the UE different from the ID of the UE to further map the actual UE status information to the predicated status information of the UE.

In another example, RAN node#1 may send a UE to a RRC inactive state or RRC idle state by transmitting a RRC signaling to the UE. The RRC signaling also requests the UE to report actual UE status information to RAN node#1 after entering the connected state, which will be logged by the UE during the RRC inactive state or RRC idle state. Similarly, an event ID different from the ID of the UE may also be provided by RAN node #1 for associating the actual UE status information with status prediction information of the UE. When the UE re-enters a connected state, the UE may connect to another RAN node, e.g., RAN node#2. Then, the UE will report the actual UE status information logged by the UE during the RRC inactive state or RRC idle state to RAN node#2, e.g., via a RRC resume message. The UE will also indicate RAN node#2 that RAN node#2 shall send the actual UE status information logged by the UE to RAN node#1.

In response to the request from RAN node#1 or the UE, RAN node#2 will transmit (or forward, or transfer) to RAN node#1 the actual UE status information logged by the UE during the RRC inactive state or RRC idle state via a UE associated Xn message or a non-UE associated Xn message. When a non-UE associated Xn message is used, the event ID for status prediction of the UE provided by RAN node#1 will be transmitted with the actual UE status information.

FIG. 5 is a flow chart illustrating an exemplary procedure of a method of supporting UE status prediction in Case 2 according to some embodiments of the present application.

Referring to FIG. 5, the UE is connected to a RAN node, e.g., RAN node#1. In step 501, RAN node#1 may send a UE to a RRC idle state by a RRC signaling to the UE. The UE may perform cell reselection and camp on different cells in the RRC idle state in step 502.

When re-entering the connected state in step 503, the UE will report the actual UE status information logged by the UE during the RRC idle state to RAN node#2 under which the UE enters the connected state from the RRC idle state, e.g., via a RRC resume message.

In response to the UE's connection request, RAN node#2 will send a retrieve UE context request message to RAN node#1 in step 505. RAN node#1 may transmit a retrieve UE context response message in response to the retrieve UE context request message in step 507, including a request requesting RAN node#2 to send the actual UE status information logged by the UE during the RRC idle state. RAN node#1 may also indicate an event ID for status prediction of the UE different from the ID of the UE to further map the actual UE status information to the predicated status information of the UE.

In response to the request from RAN node#1 or the UE, RAN node#2 will transmit (or forward, or transfer) to RAN node#1 the actual UE status information logged by the UE during the RRC idle state via a UE associated Xn message or a non-UE associated Xn message in 509. For example, RAN node#2 may transmit the actual UE status information via a UE associated Xn message before releasing the context of the UE. In another example, RAN node#2 may transmit the actual UE status information via a non-UE associated Xn message with the event ID for status prediction of the UE provided by RAN node#1.

Case 3

In Case 3, a RAN node, e.g., RAN node#1 is a source node of a UE during a handover procedure, and another RAN node, e.g., RAN node#2 is a target node during the handover procedure. RAN node#2 may request information related to UE status prediction, e.g., at least part of the UE status prediction information of the UE available in RAN node#1.

RAN node#1 may first indicate RAN node#2 the available UE status prediction information, and then RAN node#2 will indicate RAN node#1 that at least part of the UE status prediction information is demanded or not. For example, RAN node#2 may request at least part of the UE status prediction information by indicating one of the following: only UE status prediction information at required time point (s) is interested; only average UE status prediction information every required time interval during a required time window is interested, e.g., the average traffic load every 10mins in the next 1 hour; only a required number of UE status prediction information to be measured is interested; and only UE status prediction information under coverage of RAN node#1 is interested, e.g., next N serving cells under RAN node#2.

In some embodiments of the present application, RAN node#1 may indicate RAN node#2 the available UE status prediction information via a UE associated Xn messages before the handover procedure is executed, and RAN node#2 may also request at least part of the available UE status prediction information via another UE associated Xn messages before the handover procedure. After receiving the request from RAN node#2, RAN node#1 may transmit the required UE status prediction information via a handover request message during the handover procedure or via a non-UE associated Xn message. Similarly, the non-UE associated Xn message includes an event ID provided by RAN node#1 for associating the required UE status prediction information with the predicted status information of the UE.

In some embodiments of the present application, RAN node#1 may indicate RAN node#2 the available UE status prediction information via a handover request message during the handover procedure, and RAN node#2 may request at least part of the available UE status prediction information via a handover request acknowledge message in response to the handover request message. After receiving the request from RAN node#2, RAN node#1 may transmit the required UE status prediction information via a UE associated Xn message before RAN node#2 releases (or trigger releasing) the context of the UE, or via a non-UE associated Xn message with an event ID for status prediction of the UE.

In some embodiments of the present application, RAN node#1 may request feedback on the UE status prediction from RAN node#2, e.g., in the message indicting the available UE status prediction information or in the message sending the UE status prediction information required by RAN node#2. The feedback includes but is not limited to at least one of the following: accuracy of the at least part of the UE status prediction information determined by RAN node#2; confidence level of the at least part of the UE status prediction information determined by RAN node#2; standard deviations of the at least part of the UE status prediction information determined by RAN node#2; and actual UE status information measured by RAN node#2. RAN node#2 may transmit the feedback in response to one or more events or conditions. For example, in some embodiments of the present application, RAN node#2 may transmit the feedback in response to one of the following: the UE is handover to another RAN node#3 in RRC connected state; the UE is sent to an inactive state or idle state by RAN node#2; the UE connects to a new RAN node#3 in a connected state after being sent to an inactive state or idle state by RAN node#2, and RAN node#2 receives the logged actual UE status; and the logged actual UE status information has fulfilled the requirement as indicated by RAN node#1, e.g., average traffic load every 10mins in 1 hour, or next N serving cells.

In some situations, RAN node#2 may not be able to determine the accuracy or confidence etc., of the UE status prediction information due to lack of measurements or the UE being handover to a new RAN node, e.g., RAN node#3 soon after the UE is handover to RAN node#2. Accordingly, RAN node#2 is unable to provide the feedback. RAN node#2 will indicate RAN node#1 this situation, e.g., via a non-UE Xn message with an event ID provided by RAN node#1. RAN node#2 may also indicate the cause resulting in this situation in the same message.

Referring to FIG. 6, RAN node#1 is a source node of a UE during a handover procedure and RAN node#2 is a target RAN node during the handover procedure. RAN node#1 transmits a handover request message to RAN node#2 in step 601, which also indicates UE status prediction information available in RAN node#1 and includes a request of feedback, e.g., accuracy of the UE status prediction information from RAN node#2 besides a handover request. Considering that RAN node#2 may transmit the feedback after releasing context of the UE, the handover request message also includes an event ID for status prediction of the UE different from the ID of the UE for associating the feedback with the UE status prediction information in the future.

In step 603, RAN node#2 may transmit a handover request acknowledge message, which includes a request of at least part of the UE status prediction information interested by RAN node#2 besides the handover request acknowledge information. For example, the handover request acknowledge message indicates that the handover request is acknowledged and also includes a request of all UE status prediction information available in RAN node#1.

Then, in step 605, RAN node#2 will transmit a handover success message to RAN node#1. RAN node#1 will transfer the UE status prediction information to RAN node#2 in step 607. After receiving the UE status prediction information, RAN node#2 will transmit a UE context release message to RAN node#1 in step 609. After receiving the UE context release message, RAN node#1 will releases the context related to the UE and store the predicted UE status information associated with the event ID.

In step 611, RAN node#2 will transmit the feedback of the UE status prediction information (if any or indicate unable to provide) to RAN node#1 after releasing the context of the UE, it will not indicate any UE context. Instead, RAN node#2 will transmit the feedback via a non-UE associated message with the event ID provided by RAN node#1. After receiving the feedback from RAN node#2, RAN node#1 will be able to map the feedback to the predicted UE status information stored before even if the UE context is wiped.

Some embodiments of the present application also provide an apparatus of supporting UE status prediction. For example, FIG. 7 illustrates a block diagram of an apparatus of supporting UE status prediction 700 according to some embodiments of the present application.

As shown in FIG. 7, the apparatus 700 may include at least one non-transitory computer-readable medium 701, at least one receiving circuitry 702, at least one transmitting circuitry 704, and at least one processor 706 coupled to the non-transitory computer-readable medium 701, the receiving circuitry 702 and the transmitting circuitry 704. The at least one processor 706 may be a CPU, a DSP, a microprocessor etc. The apparatus 700 may be a RAN node configured to perform a method illustrated in the above or the like.

Although in this figure, elements such as the at least one processor 706, transmitting circuitry 704, and receiving circuitry 702 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated. In some embodiments of the present application, the receiving circuitry 702 and the transmitting circuitry 704 can be combined into a single device, such as a transceiver. In certain embodiments of the present application, the apparatus 700 may further include an input device, a memory, and/or other components.

In some embodiments of the present application, the non-transitory computer-readable medium 701 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to a RAN node, e.g., a gNB as described above. For example, the computer-executable instructions, when executed, cause the processor 706 interacting with receiving circuitry 702 and transmitting circuitry 704, so as to perform the steps with respect to a RAN node as depicted above, e.g., shown in FIG. 2 or FIG. 3.

FIG. 8 is a block diagram of an apparatus of supporting UE status prediction 800 according to some other embodiments of the present application.

Referring to FIG. 8, the apparatus 900, for example a gNB may include at least one processor 802 and at least one transceiver 804 coupled to the at least one processor 802. The transceiver 804 may include at least one separate receiving circuitry 806 and transmitting circuitry 808, or at least one integrated receiving circuitry 806 and transmitting circuitry 808. The at least one processor 802 may be a CPU, a DSP, a microprocessor etc.

According to some embodiments of the present application, when the apparatus 800 is a RAN node, e.g., a gNB, the processor is configured to: transmit a first message indicating a request for information related to UE status prediction; and receive a second message from a second RAN node to the RAN node, indicating a response to the request indicated in the first message.

According to some other embodiments of the present application, when the apparatus 800 is a RAN node, e.g., a gNB, the processor may be configured to: receive a first message indicating a request for information related to UE status prediction; and transmit a second message from the RAN node to a second RAN node, indicating a response to the request indicated in the first message.

The method according to embodiments of the present application can also be implemented on a programmed processor. However, the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like. In general, any device capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application. For example, an embodiment of the present application provides an apparatus, including a processor and a memory. Computer programmable instructions for implementing a method are stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method. The method may be a method as stated above or other method according to an embodiment of the present application.

An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions. The instructions are preferably executed by computer-executable components preferably integrated with a network security system. The non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical storage devices (CD or DVD) , hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device. For example, an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein. The computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment of the present application.

In addition, in this disclosure, the terms "includes, " "including, " or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a, " "an, " or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term "another" is defined as at least a second or more. The terms "having, " and the like, as used herein, are defined as "including. "

Claims

A radio access network (RAN) node, comprising:

at least one receiving circuitry;

at least one transmitting circuitry; and

at least one processor coupled to the at least one receiving circuitry and the at least one transmitting circuitry,

wherein the at least one processor is configured to:

transmit, via the at least one transmitting circuitry, a first message indicating a request for information related to user equipment (UE) status prediction; and

receive, via the at least one receiving circuitry, a second message from a second RAN node to the RAN node, indicating a response to the request indicated in the first message.
The RAN node of claim 1, wherein, the RAN node is a source node and the second RAN node is a target RAN node during a handover procedure for a UE.
The RAN node of claim 2, wherein, the request for information related to UE status prediction comprises:

requesting the second RAN node to inform the RAN node actual UE status information at least of the UE to be measured at required time point (s) ; or

requesting the second RAN node to inform the RAN node average UE status information at least of the UE to be measured every required time interval during a required time window; or

requesting the second RAN node to inform the RAN node a required number of actual UE status information at least of the UE to be measured.
The RAN node of claim 2, wherein, in the case that the second message indicates a response of accepting the request, the at least one processor is configured to:

receive the information related to UE status prediction from the second RAN node via a UE associated Xn message or via a non-UE associated Xn message with an event ID for status prediction of the UE provided by the RAN node, wherein the information related to UE status prediction of the UE is actual status information of the UE.
The RAN node of claim 1, wherein, the RAN node is a node sending a UE to one of an inactive state and idle state and the second RAN node is a node under which the UE enters a connected state from the one of the inactive state and the idle state, and the information related to UE status prediction is actual status information of the UE.
The RAN node of claim 5, wherein,

the first message is a retrieve UE context response message in response to a retrieve UE context request message from the second RAN node, requesting the second RAN node to send actual UE status information logged by the UE during the one of the inactive state and the idle state; and

the second message is a UE associated Xn message or a non-UE associated Xn message with an event identity (ID) for status prediction of the UE provided by the RAN node, for sending the actual UE status information in response to the first message.
The RAN node of claim 1 wherein, the RAN node is a target node, the second RAN node is a source RAN node during a handover procedure for a UE, and the at least one processor of the RAN node is configured to:

receive a third message from the second RAN node, indicating UE status prediction information available in the second RAN node before transmitting the first message; and

transmit the first message in response to the third message indicating whether the UE status prediction information is demanded.
The RAN node of claim 7, wherein, both the first message and the third message are UE associated Xn messages before the handover procedure is executed.
The RAN node of claim 7, wherein, the third message is a handover request message during the handover procedure, and the first message is a handover request acknowledge message in response to the handover request message.
The RAN node of claim 8 or 9, wherein, the second message is a non-UE associated Xn message indicating an event ID for status prediction of the UE.
The RAN node of claim 7, wherein, the second message or the third message further requests at least one of the following feedback from the RAN node:

accuracy of the at least part of the UE status prediction information determined by the RAN node;

confidence level of the at least part of the UE status prediction information determined by the RAN node;

standard deviations of the at least part of the UE status prediction information determined by the RAN node; or

actual UE status information measured by the RAN node.
A radio access network (RAN) node, comprising:

at least one receiving circuitry;

at least one transmitting circuitry; and

at least one processor coupled to the at least one receiving circuitry and the at least one transmitting circuitry,

wherein the at least one processor is configured to:

receive, via the at least one receiving circuitry, a first message indicating a request for information related to user equipment (UE) status prediction; and

transmit, via the at least one transmitting circuitry, a second message from the RAN node to a second RAN node, indicating a response to the request indicated in the first message.
The RAN node of claim 12, wherein, the second RAN node is a source node and the RAN node is a target RAN node during a handover procedure for a UE.
The RAN node of claim 13, wherein, the at least one processor is configured to:

in the case of transmitting the second message indicates a response of accepting the request, transmit the information related to UE status prediction to the second RAN node via a UE associated Xn message or a non-UE associated Xn message with an event ID for status prediction of the UE provided by the second RAN node, wherein the information related to UE status prediction of the UE is actual status information of the UE.
The RAN node of claim 14, wherein, the information related to UE status prediction is transmitted in response to at least one of the following:

the UE is handover to a third RAN node in a connected state;

the UE is sent to an inactive state or an idle state by the RAN node;

the UE connects to the RAN node or a third RAN node in a connected state after being sent to an inactive or an idle state by the RAN node, and the RAN node receives logged actual UE status information from the UE; or

logged actual UE status information has fulfilled requirement (s) as indicated by the second RAN node.