Optimizing RAN notification area (RNA) updates and RAN paging using user equipment (UE) mobility history information

Abstract

Embodiments of the present disclosure disclose determining a priority cell list based on mobility history information of a UE. The RIC receives mobility history information of the UE and a subscriber ID from the base station. Further, the RIC stores mobility history information according to the subscriber ID of the UE. Thereafter, the RIC determines a priority cell list based on mobility history information of the UE to optimize RNA updates and RAN paging.

Description

Technical Field

[0001] This disclosure generally relates to communication technologies, and more specifically to using user equipment (UE) mobility history information to optimize radio access network (RAN) notification area (RNA) updates and RAN paging. Background Technology

[0002] In the 3rd Generation Partnership Project (3GPP), since Release 15 (Rel-15), 3GPP has specified the Radio Resource Control (RRC) _INACTIVE state in the UE to allow the UE context to be paused in the RAN and resumed at any time when the UE wants to return to an active state. When the UE is in an inactive state, it can continue to move within a list of cells designated as "RAN Notification Areas". As long as the UE is moving within these cells and has no data to relay, the UE can remain inactive without sending any signals to the RAN. Furthermore, the success of this approach / technology depends on the degree of optimization and fine-tuning of the RNA.

[0003] Based on the above discussion, it is necessary to use the UE's mobility history information to optimize the UE's RNA update in order to reduce the number of paging attempts.

[0004] The information disclosed in the Background section of this disclosure is intended only to enhance the understanding of the general background of this disclosure and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0005] In one embodiment, a Radio Access Network (RAN) Intelligent Controller (RIC) is disclosed. The RIC includes a memory and a processor. The memory is configured to store instructions, thereby causing the RIC to receive mobility history information of a UE and the UE's subscriber identifier (ID) from a base station. The RIC is configured to store the UE's mobility history information based on the UE's subscriber ID. Subsequently, the RIC is configured to determine a priority cell list based on the UE's mobility history information.

[0006] In another embodiment, a method is disclosed. The method includes receiving mobility history information of a UE and a subscriber ID of the UE from a base station via a RIC. The method includes storing the UE's mobility history information by the RIC based on the UE's subscriber ID. The method includes determining a priority cell list by the RIC based on the UE's mobility history information.

[0007] In one embodiment, a base station is disclosed. The base station includes a memory and a processor. The memory is configured to store instructions, thereby causing the base station to receive mobility history information and subscriber identifier (ID) of a UE from a UE. The base station is configured to send the UE's mobility history information and subscriber ID to a RIC. The base station is configured to receive a priority cell list from the RIC. The RIC determines the priority cell list based on the UE's mobility history information. The base station is configured to perform paging based on the priority cell list.

[0008] In another embodiment, a non-transitory computer-readable medium is disclosed. This non-transitory computer-readable medium is configured to receive mobility history information of a UE and a subscriber identifier (ID) of the UE from a base station. The non-transitory computer-readable medium is configured to store the UE's mobility history information based on the UE's subscriber ID. Subsequently, the non-transitory computer-readable medium is configured to determine a priority cell list based on the UE's mobility history information.

[0009] The above description of the invention is illustrative only and is not intended to be limiting in any way. Other aspects, embodiments, and features will become apparent from the accompanying drawings and the following detailed description, in addition to the illustrative aspects, embodiments, and features described above. Attached Figure Description

[0010] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the specification, serve to explain the disclosed principles. The same numerals are used throughout the drawings to refer to similar features and components. Some embodiments of devices and / or methods according to this subject matter will now be described by way of example and with reference to the accompanying drawings, in which:

[0011] Figure 1 The illustration shows a sequence diagram illustrating interaction with the RIC to determine a priority cell list according to an embodiment of the present disclosure;

[0012] Figure 2 A detailed block diagram of a RIC for determining a priority cell list according to an embodiment of the present disclosure is shown;

[0013] Figure 3 The illustration shows a sequence diagram illustrating interaction with a base station to perform paging according to an embodiment of the present disclosure;

[0014] Figure 4 A detailed block diagram of a base station for performing paging according to an embodiment of the present disclosure is shown;

[0015] Figure 5 The illustration shows a flowchart illustrating an exemplary method for determining a priority cell list according to embodiments of the present disclosure; and

[0016] Figure 6 The illustration shows a flowchart of an exemplary method for performing paging according to an embodiment of the present disclosure.

[0017] Those skilled in the art will understand that any block diagram herein represents a conceptual diagram of an illustrative system embodying the principles of the subject matter. Similarly, it will be understood that any flowchart, diagrammatic flowchart, state transition diagram, pseudocode, etc., represents various processes that can be substantially represented in a computer-readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown. Detailed Implementation

[0018] In this document, the word "exemplary" is used to mean "as an example, instance, or illustration." Any embodiment or implementation of the subject matter described herein as "exemplary" is not necessarily to be construed as more preferred or advantageous than other embodiments.

[0019] While this disclosure is readily available in various modifications and alternatives, specific embodiments thereof have been illustrated by way of example in the accompanying drawings and will be described in detail below. However, it should be understood that this is not intended to limit this disclosure to the specific forms disclosed; rather, this disclosure is intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.

[0020] The terms “comprises,” “comprising,” or any other variations thereof are intended to cover non-exclusive inclusion, such that an arrangement, apparatus, or method that includes a list of components or steps may include not only those listed components or steps, but also other components or steps not expressly listed or inherent to such an arrangement, apparatus, or method. In other words, without further constraints, one or more elements in an apparatus, system, or device that begins with “comprises … a (including a …)” do not exclude the presence of other elements or additional elements in the apparatus, system, or device.

[0021] In the following detailed description of embodiments of the present disclosure, reference is made to the accompanying drawings, which form part of this disclosure, illustrating specific embodiments in which the present disclosure may be practiced by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present disclosure, and it should be understood that other embodiments may be utilized and changes may be made without departing from the scope of the present disclosure. Therefore, the following description should not be considered limiting.

[0022] It should be noted that, for ease of interpretation, this disclosure uses the terms and names defined in the 3GPP RAN standard. More specifically, the terms 'RAN Intelligent Controller (RIC)', 'base station', 'gNodeB', 'cell', 'User Equipment (UE)', 'Near Real-Time RIC', 'RRCSetupComplete', 'VarMobilityHistoryReport', 'mobilityHistoryavail', 'RRCResumeComplete', 'RRC_Inactive', 'RRC_Idle', 'RRC_Connected', 'visitedCellInfoList', 'RIC Subscription Request', 'UEInformationResponse', 'E2 Service Model (E2SM) - RAN Control (RC) Indication Message', 'New Radio (NR) Cell', etc., will be interpreted as those defined by the 3GPP RAN standard and the Open Radio Access Network (ORAN) standard.

[0023] As used herein, the term "RNA update and RAN paging" refers to optimizing RNA update and RAN paging using UE mobility history information. More specifically, the UE's mobility history information and subscriber ID are received from the base station to which the UE is connected. In one embodiment, the mobility history information is stored based on the UE's subscriber ID. In another embodiment, the mobility history information is used to determine a priority cell list to optimize RNA update and RAN paging. The determined priority cell list enables the UE to reduce RNA update signaling between the UE and the base station. Furthermore, the priority cell list helps the base station achieve successful RAN paging with less paging signaling and reduces paging overhead at the base station. In one embodiment, refer to Appendix Figures 1-6 A detailed explanation of how the priority cell list is determined based on mobility history information.

[0024] Figure 1 The illustration shows a sequence diagram illustrating interaction with the RIC to determine a priority cell list according to an embodiment of the present disclosure. Figure 1The diagram illustrates UE 101, cell 1 103, cell 2 105, base station 107, RIC 109, and Access and Mobility Management Function (AMF) 111. In one embodiment, UE 101 may include, but is not limited to, mobile devices, smartphones, tablets, laptops, wireless devices, etc. In one embodiment, cell 1 103 and cell 2 105 are geographical areas covered by base station 107 in a cellular network. In another embodiment, UE 101 is connected to base station 107. In yet another embodiment, RIC 109 is a software-defined component of the Open Radio Access Network (RAN) responsible for controlling and optimizing RAN functions. Initially, an E2 establishment procedure 113 is established between base station 107 and RIC 109. Base station 107 may include, but is not limited to, gNodeB (gNB), next-generation evolved NodeB (ng-eNB), and evolved NodeB (eNB). In one embodiment, the E2 procedure is performed to establish a signaling connection between the E2 node of base station 107 and RIC 109. Specifically, RIC 109 sends an RIC subscription request message 115 to base station 107. For example, RIC 109 sends [RIC event trigger definition type 1 = message event, message type = RRC->NR message ID = UEInformationResponse] to base station 107. After receiving the RIC subscription request message 115, base station 107 sends an RIC subscription response message 117 to RIC 109. In one embodiment, the RIC subscription response message indicates confirmation of a successful subscription process at base station 107 for sending the “UEInformationResponse” RRC message.

[0025] In one embodiment, UE 101 supports the storage of mobility history information, which UE 101 includes in a “VarMobilityHistoryReport”. In one embodiment, the mobility history information includes cells accessed by UE 101 during its inactive, idle, or connected states. In one embodiment, “mobilityHistoryAvail” is included in the RRCSetupComplete message / RRCResumeComplete message. “mobilityHistoryAvail” instructs UE 101 to include the mobility history information. In one embodiment, UE 101 performs an RRC establishment / RRC connection recovery procedure 119 with AMF 111. In one embodiment, Figures 3-4The RRC establishment / RRC connection recovery process is explained in detail. In one embodiment, at 121, base station 107 sends mobility history information to RIC 109. In another embodiment, at 123, RIC 109 receives mobility history information and the subscriber ID of UE 101 from base station 107 connected to UE 101. In one embodiment, RIC 109 receives mobility history information and subscriber ID from base station 107 via the E2 interface using one of a first message and a second message. In one embodiment, the first and second messages are standard ORAN messages. In one embodiment, mobility history information and subscriber ID can be sent as part of the first standard message, i.e., an RIC indication message (action = report, E2SM = [UEID->5G-S-TMSI, E2SM-RC indication message format 1->RRC message->RRC UE information response]). If mobility history information and subscriber ID are not part of the first standard message, they are sent via the E2 interface using a second standard message (i.e., an RIC indication message using a customized E2SM-RC container message). In one embodiment, the subscriber ID may include, but is not limited to, 5G-STMSI, RAN-related identifiers, etc. In one embodiment, the subscriber ID is crucial for maintaining the uniqueness of UE 101's records within RIC 109, as the subscriber ID is unique within the AMF 111 area (5G-S-TMSI{AMFSetId, AMFPointer, TMSI}). In one embodiment, AMFSetID is an IE used to uniquely identify an AMF set within the AMF area. In one embodiment, AMFPointer is an IE used to identify one or more AMFs within the AMF set. In one embodiment, the 5G-TMSI is unique within the AMF to which it has been assigned. In one embodiment, the 5G-STMSI is a temporary mobile subscription identifier (5G-S-TMSI), a temporary UE identity provided by the 5G core (5GC), which uniquely identifies UE 101 within the tracking area.

[0026] In one embodiment, after receiving mobility history information, at 125, RIC 109 stores the mobility history information of UE 101 based on the subscriber ID of UE 101. For example, RIC 109 maps the mobility history information to the subscriber ID of UE 101. In one embodiment, at 127, RIC 109 determines a priority cell list based on the mobility history information of UE 101. In one embodiment, the mobility history information of UE 101 includes information about one or more cells among a plurality of cells accessed by the UE during inactive, idle, or connected states. In one embodiment, RIC 109 determines the priority of each of the one or more cells based on the mobility history information. The mobility history information includes information about the amount of time spent by UE 101 in the one or more cells, the number of times UE 101 accessed the one or more cells, and the traversal pattern of UE 101 between the one or more cells. After determining the priority cell list at 129, RIC 109 transmits the determined priority cell list to base station 107 via the E2 interface. In one embodiment, the priority cell list is a "RAN Notification Area Information Priority List" sent using a standard message; that is, the priority cell list is included in the "RRC Connection Release Control" within the RIC Control Request message and sent to base station 107 via the E2 interface. In another embodiment, the priority cell list is sent to base station 107 via the E2 interface using a first standard message or a second standard message (i.e., an E2SM-RC container message) along with the subscriber ID. For example, when sending the priority cell list and subscriber ID, the message may indicate "RIC Control Request (E2SM-RC [UEID->5G-S-TMSI, RRC Connection Release Control->RAN Notification Area Information Priority List]" or "Custom E2SM containing [5G-S-TMSI, RAN Notification Area Message Priority List [PLMN, NREllIdentity List [Priority, NR CELLIdentity(1..N)]]]". Furthermore, base station 107 stores the priority cell list for paging 131, which... Figures 3-4 The following provides a detailed explanation. In one embodiment, after base station 107 receives the priority cell list at 133, base station 107 sends an RIC control confirmation message to RIC 109.

[0027] In one embodiment, such as Figure 2As shown, RIC 109 may include a processor 201, an I / O interface 203, and a memory 205. In some embodiments, the memory 205 may be communicatively coupled to the processor 201. The memory 205 stores instructions executable by the processor 203, which, when executed, may cause the RIC 109 to determine a priority cell list as disclosed in this disclosure. In one embodiment, the memory 205 may include, for example, Figure 2 One or more modules 207 and data 209 are shown. One or more modules 207 can be configured to use data 209 to perform the processes of this disclosure to determine a priority cell list. In one embodiment, each of the one or more modules 207 may be a hardware unit that may be external to memory 205 and coupled to RIC 109. In one embodiment, RIC 109 may be via an E2 interface (… Figure 1 (Not shown in the image) communicates with base station 107.

[0028] Figure 2 A detailed block diagram of a priority cell list RIC for determining priority cells according to an embodiment of the present disclosure is shown.

[0029] This section describes in detail the data 209 in the memory 205 of the RIC 109 and one or more modules 207.

[0030] In one implementation, one or more modules 207 may include, but are not limited to, a receiving module 211, a storage module 213, a determining module 215, and one or more miscellaneous modules 217 associated with RIC 109.

[0031] In one embodiment, the data 209 in memory 205 may include input data 219 associated with RIC 109, priority cell list data 221, and miscellaneous data 223.

[0032] In one embodiment, data 209 in memory 205 may be processed by one or more modules 207 of RIC 109. In one embodiment, one or more modules 207 may be implemented as dedicated units, and when implemented in this way, the modules may be configured with the functions defined in this disclosure to produce novel hardware. As used herein, the term module may refer to application-specific integrated circuits (ASICs), electronic circuits, field-programmable gate arrays (FPGAs), programmable system-on-chip (PSoCs), combinational logic circuits, and / or other suitable components that provide the functions described above.

[0033] One or more modules 207 of this disclosure are used to determine a priority cell list. One or more modules 207 may also include miscellaneous modules 217 to perform various miscellaneous functions of the RIC 109. It should be understood that such modules can be represented as a single module or a combination of different modules. One or more modules 207 and data 209 can be implemented in any RIC to determine the priority cell list.

[0034] Input data 219 may include mobility history information about UE 101 and subscriber ID information about UE 101.

[0035] The priority cell list data 221 may include details about the priority of each of one or more cells determined based on the mobility history information of UE 101.

[0036] Miscellaneous data 223 can store data generated by the module for performing various functions of RIC 109, including temporary data and temporary files.

[0037] In one embodiment, the receiving module 211 of RIC 109 is configured to receive mobility history information and subscriber ID of UE 101 from base station 107. UE 101 is connected to UE 101. In one embodiment, the mobility history information is included in the information element "VisitedCellInfoList". The mobility history information includes: information on up to 16 recently visited primary cells, or the time spent in any cell selection state and / or camped in any cell state in NR or E-UTRA. In one embodiment, in the case of dual connectivity, the mobility history information maxPSCellHistory of the most recently visited primary and secondary cell groups across all primary cells is included in VisitedCellInfoList. After receiving, the storage module 213 of RIC 109 is configured to store the mobility history information of UE 101 based on the subscriber ID of UE 101. In one embodiment, the storage module 213 maps the mobility history information to the subscriber ID of UE 101. Storage module 213 stores mapped mobility history information for determining a priority cell list. Furthermore, determination module 215 of RIC 109 is configured to determine the priority cell list based on the mobility history information of UE 101. In one embodiment, determination module 215 determines the priority of each cell based on information about the amount of time spent by UE 101 in one or more cells, the number of times UE 101 accesses one or more cells, and the traversal pattern of UE 101 between one or more cells. Additionally, in one embodiment, the determined priority cell list and subscriber ID are sent by RIC 109 to base station 107 via the E2 interface using a first message (i.e., a standard message) or a second message (i.e., a specific message).

[0038] Figure 3 The illustration shows a sequence diagram illustrating interaction with a base station to perform paging according to an embodiment of the present disclosure. Figure 3 The diagram shows UE 101, cell 1 103, cell 2 105, base station 107, RIC 109, and AMF 111. Initially, as described above... Figure 1As shown, an E2 establishment procedure 113 is established between base station 107 and RIC 109. In one embodiment, UE 101 and AMF 111 execute an RRC establishment / RRC connection recovery procedure 119. In one embodiment, the RRC establishment / RRC connection recovery procedure 119 is used to establish / rebuild an RRC connection between UE 101 and base station 107 after a temporary interruption or pause. In one embodiment, triggers for RRC connection recovery are received based on various events, such as cell reselection, handover, or transition from idle to active state. Furthermore, in one embodiment, base station 107 generates an RRC connection recovery request message, which may include relevant information about the RRC connection to be recovered. This relevant information may include, but is not limited to, context information, security information, etc. Furthermore, UE 101 processes the received RRC connection recovery request message to recover the connection. Subsequently, UE 101 confirms the successful recovery of the RRC connection. Furthermore, base station 107 receives confirmation from UE 101 that the RRC connection has been successfully recovered. In one embodiment, during the RRC setup / RRC connection recovery process, at point 301, base station 107 receives an Information Element (IE) from UE 101. For example, consider UE 101 attaching / recovering to a network or AMF 111, and UE 101 supporting the storage of mobility history information. In this case, the UE sends a "mobilityHistoryAvail" IE set to true to base station 107 in an "RRCSetupComplete / RRCResumeComplete" message. Specifically, at point 303, base station 107 uses a "UE Information Request" RRC message to request UE 101 to share mobility history information, where the "mobilityHistoryReportReq" IE is set to true. Then, UE 101 sends a "mobilityHistoryReport-r16" IE to base station 107 in a "UE Information Response" message. That is, at point 305, base station 107 receives a UE Information Response message in response to this request. In addition, base station 107 sends UE 101's mobility history information and subscriber ID to RIC 109 to determine the priority cell list (as above). Figure 1(As shown). At 131, base station 107 stores a priority cell list for RRC release and paging. In one embodiment, at 307 and 309, base station 107 locally stores the priority cell list in the "UE inactivity context" and sends this information (i.e., the priority cell list) as part of the "suspendConfig->RAN-notificationAreaInfo->PLMN-RAN-AreaCellList" IE to UE 101 within the "RRC release" message. Furthermore, at 311, UE 101 utilizes "RNA notification area information" (i.e., the priority cell list) when moving in an inactive state. In one embodiment, if UE 101 moves within these priority cell lists, UE 101 does not need to perform an RNA update process with the RAN. In one embodiment, since these NRCells are priority access cells, UE 101 performs fewer RNA updates. Therefore, less signaling overhead is achieved between UE 101 and base station 107. In another embodiment, if UE 101 is in an inactive state, UE 101 can access multiple NRCells, and UE 101 uses these newly accessed cells in its database to update the "VarMobilityHistoryReport" so that it can be shared with the RAN when UE 101 later moves to a connected state.

[0039] In one embodiment, at 313, base station 107 receives signaling messages from AMF 111 or receives data notifications from base station 107. For example, if base station 107's gNB-CUCP receives a "DL data notification" message from base station 107's gNB-CUUP, or if base station 107 receives any signaling message for UE 101 from AMF 111, base station 107 utilizes a stored priority cell list to first perform RAN paging in one or more of the listed high-priority cells and starts a paging timer. In one embodiment, gNB-CUCP (gNB-CU control plane) is a logical node hosting the control plane portion of the RRC and Packet Data Convergence Protocol (PDCP) of base station 107. In one embodiment, gNB-CUUP (gNB-CU user plane) is a logical node hosting the user plane portion of the PDCP of base station 107. In one embodiment, if UE 101 exists in any of the priority cell lists, UE 101 resumes RRC connection with that cell / NR cell. In another embodiment, UE 101 may share the updated or latest "mobilityHistoryReport-r16" IE with the currently serving base station. In one embodiment, if the paging timer expires, base station 107 performs paging using a secondary priority cell from the priority cell list until paging is successful.

[0040] For example, in Figure 3 In the first embodiment, after receiving a signaling message from AMF 111, at point 315, base station 107 performs a paging request in cell 1 103. At point 317, base station 107 performs a RAN paging request in cell 1 103, which has first priority. If paging is successful in cell 1 103, then at point 319, cell 1 103 performs an RRC paging request for UE 101. Subsequently, at point 321, UE 101 restores its RRC connection with cell 1 103. After successful paging in cell 1 103, at point 323, base station 107 stops the paging timer for UE 101. In another embodiment, at point 325, if paging is unsuccessful and the paging timer expires, base station 107 performs a paging request in cell 2 105 at point 327. At point 329, base station 107 performs a RAN paging request in cell 2 105, which has second priority. If paging in cell 2105 is successful, then at point 331, cell 2105 performs an RRC paging of UE 101. Subsequently, at point 333, UE 101 restores its RRC connection with cell 2105. After successful paging in cell 2105, at point 335, base station 107 stops the paging timer for UE 101.

[0041] In one embodiment, base station 107 may include processor 401, I / O interface 403, and memory 405, such as Figure 4 As shown. In some embodiments, memory 405 may be communicatively coupled to processor 401. Memory 405 stores instructions executable by processor 401, which, when executed, may cause base station 107 to perform paging as disclosed in this disclosure. In one embodiment, memory 405 may include, for example, Figure 4 One or more modules 407 and data 409 are shown. One or more modules 407 can be configured to use data 409 to perform the procedures of this disclosure to perform paging. In one embodiment, each of the one or more modules 407 may be a hardware unit that may be external to memory 405 and coupled to base station 107. In one embodiment, base station 107 may be connected via an E2 interface (… Figure 3 (Not shown in the image) Communicates with UE 101 and RIC 109.

[0042] Figure 4 A detailed block diagram of a base station for performing paging according to an embodiment of the present disclosure is shown.

[0043] This document describes in detail the data 409 in the memory 405 of the base station 107 and one or more modules 407.

[0044] In one implementation, one or more modules 407 may include, but are not limited to, a receiving module 411, a transmitting module 413, an execution module 415, and one or more miscellaneous modules 417 associated with the base station 107.

[0045] In one embodiment, the data 409 in the memory 405 may include input data 419 associated with the base station 107, priority cell list data 421, and miscellaneous data 423.

[0046] In one embodiment, data 409 in memory 405 may be processed by one or more modules 407 of base station 107. In one embodiment, one or more modules 407 may be implemented as dedicated units, and when implemented in this way, the modules may be configured with the functions defined in this disclosure to produce novel hardware. As used herein, the term module may refer to application-specific integrated circuits (ASICs), electronic circuits, field-programmable gate arrays (FPGAs), programmable system-on-chip (PSoCs), combinational logic circuits, and / or other suitable components that provide the functions described above.

[0047] One or more modules 407 of this disclosure are used to perform paging. One or more modules 407 may also include miscellaneous modules 417 to perform various miscellaneous functions of the base station 107. It should be understood that such modules can be represented as a single module or a combination of different modules. One or more modules 407 and data 409 can be implemented in any base station to perform paging.

[0048] Input data 419 may include mobility history information about UE 101 and subscriber ID information about UE 101.

[0049] The priority cell list data 421 may include details about the priority of each of one or more cells determined based on the mobility history information of UE 101.

[0050] Miscellaneous data 423 can store data generated by the module for performing various functions of base station 107, including temporary data and temporary files.

[0051] In one embodiment, the receiving module 411 of base station 107 is configured to receive mobility history information and subscriber ID of UE 101 from UE 101. In one embodiment, the receiving module first receives an information element from UE 101. This information element indicates the availability of mobility history information. Furthermore, the transmitting module 413 of base station 107 is configured to send a request message to UE 101 requesting the sharing of UE 101's mobility history information. In one embodiment, the receiving module 411 receives the UE's mobility history information in response to the request message. In one embodiment, the UE 101's mobility history information includes information about one or more cells among a plurality of cells accessed by UE 101 during inactive, idle, or connected states. After receiving, the transmitting module 413 transmits the UE 101's mobility history information and subscriber ID to RIC 109. In one embodiment, the UE 101's mobility history information and subscriber ID are transmitted from base station 107 to RIC 109 via an E2 interface using a first message or a second message. In addition, RIC 109 determines the priority cell list based on mobility history information, as described above. Figures 1-2As described above. In one embodiment, the receiving module 411 of base station 107 receives a priority cell list from RIC 109. Thereafter, the execution module 415 of base station 107 is configured to perform paging based on the priority cell list. In one embodiment, paging is performed when base station 107 receives at least one of signaling messages or data from UE 101 during an inactive state. In one embodiment, a timer can be set for a predefined time period to perform paging. In one embodiment, the execution module 415 performs paging in one or more cells within a predefined time period based on at least one of the following: successful paging or paging in one or more cells based on the second highest priority of the priority cell list.

[0052] Figure 5 The illustration shows a flowchart of an exemplary method for determining a priority cell list according to an embodiment of the present disclosure.

[0053] like Figure 5 As shown, method 500 may include one or more boxes for performing the procedures in RIC 109. Method 500 may be described in the general context of computer-executable instructions. Typically, computer-executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a particular function or implement a particular abstract data type.

[0054] The order in which method 500 is described is not intended to be construed as limiting, and any number of described method blocks can be combined in any order to implement the method. Furthermore, individual blocks can be removed from the method without departing from the scope of the subject matter herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0055] At box 501, the mobility history information of UE 101 and the subscriber ID of UE 101 are received from the base station 107 connected to UE 101.

[0056] In step 502, the mobility history information of UE 101 is stored based on the subscriber ID of UE 101.

[0057] At box 503, the priority cell list is determined based on the mobility history information of UE 101.

[0058] Figure 6 The illustration shows a flowchart of an exemplary method for performing paging according to an embodiment of the present disclosure.

[0059] like Figure 6As shown, method 600 may include one or more blocks for performing procedures in base station 107. Method 600 may be described in the general context of computer-executable instructions. Typically, computer-executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions that perform a particular function or implement a particular abstract data type.

[0060] The order in which method 600 is described is not intended to be construed as limiting, and any number of described method blocks can be combined in any order to implement the method. Furthermore, individual blocks can be removed from the method without departing from the scope of the subject matter herein. Moreover, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0061] At box 601, receive the mobility history information and subscriber ID of UE 101 from UE 101.

[0062] At box 602, send UE 101's mobility history information and subscriber ID to RIC 109.

[0063] At box 603, a priority cell list is received from RIC 109. RIC 109 determines the priority cell list based on the mobility history information of UE 101.

[0064] At box 604, an RRC release (inactive) is performed based on the priority cell list.

[0065] At frame 605, data notifications are received from base station 107 or signaling messages are received from AMF 111.

[0066] At box 606, paging is performed based on the priority cell list.

[0067] refer to Figures 5-6 The publicly available methods, or references Figures 1-4 The operations of RIC 109 and base station 107 described herein can be implemented using software that includes computer-executable instructions stored on one or more computer-readable media (e.g., non-transitory computer-readable media, such as one or more optical discs, volatile memory components (e.g., DRAM or SRAM), or non-volatile memory or storage components (e.g., hard disk drives or solid-state non-volatile memory components, such as flash memory components), and executed on a computer (e.g., any suitable computer, such as a laptop, netbook, webbook, tablet computing device, smartphone, or other mobile computing device). For example, such software can be executed on a single local computer.

[0068] Furthermore, one or more computer-readable storage media can be used to implement embodiments consistent with this disclosure. A computer-readable storage medium refers to any type of physical memory on which processor-readable information or data can be stored. Therefore, a computer-readable storage medium can store instructions executable by one or more processors, including instructions for causing the processor to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible articles but exclude carrier waves and transient signals, i.e., non-transient signals. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard disk drives, CD (optical disc) ROMs, DVDs, flash drives, magnetic disks, and any other known physical storage media.

[0069] The various embodiments of this disclosure offer numerous advantages. Embodiments of this disclosure enable the UE to utilize an updated cell list obtained from the RIC to reduce RNA update signaling between the UE and the base station. Furthermore, the priority cell list helps the base station achieve successful RAN paging with less paging signaling. Therefore, this disclosure reduces paging overhead at the base station. Additionally, this disclosure enables the RIC to use the UE's mobility history information to determine the priority cell list. Furthermore, this disclosure provides better utilization of radio frequency (RF) network resources. This disclosure provides better UE battery performance.

[0070] Those skilled in the art will understand that, generally, the terms used herein are “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “comprising” should be interpreted as “including but not limited to,” etc.). For example, to aid understanding, the specific implementation may include the use of the introductory phrases “at least one” and “one or more” to introduce an enumeration. However, the use of such phrases should not be construed as implying that an enumeration introduced by the indefinite article “a” or “an” limits any particular portion of the description containing such an enumeration to containing only one such enumeration, even when the enumeration includes the introductory phrases “one or more” or “at least one” and indefinite articles (such as “a” and “an”) (e.g., “a” and / or “an” should generally be interpreted as meaning “at least one” or “one or more”); the same applies to the use of definite articles used to introduce such enumerations. Furthermore, even when specific portions of the introduced description are explicitly listed, those skilled in the art will recognize that such listing should generally be interpreted as indicating at least the number of listings (e.g., listing only “two listings” without any other modifiers generally indicates at least two listings or two or more listings).

[0071] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and implementations disclosed herein are for illustrative purposes only and are not intended to be limiting; the true scope and spirit are indicated by the following detailed description (claims).

Claims

1. A Radio Access Network (RAN) Intelligent Controller (RIC) (109), comprising: The memory (205) is configured to store instructions executable by the processor (201); as well as The processor (201) is configured to execute the instructions stored in the memory (205), and thereby cause the RIC (109): Receive mobility history information of user equipment (UE) and subscriber identifier (ID) of the UE from a base station, wherein the base station is the location where the UE connects; The UE's mobility history information is stored based on the UE's subscriber ID; as well as The priority cell list is determined based on the UE's mobility history information.

2. The RIC (109) according to claim 1, wherein the processor (201) is configured to: Map the mobility history information to the subscriber ID of the UE; and The mapped mobility history information is stored to determine the priority cell list.

3. The RIC (109) according to claim 1, wherein the processor (201) is configured to: The priority cell list is determined based on the mobility history information, wherein the UE's mobility history information includes information about one or more cells from a plurality of cells accessed by the UE during inactive, idle, or connected states; and The priority cell list is sent to the base station.

4. The RIC (109) according to claim 1, wherein the processor (201) is configured to: The priority of each cell in one or more cells is determined based on the mobility history information, wherein the mobility history information includes information about: the amount of time spent by the UE in the one or more cells, the number of times the UE accesses the one or more cells, and the traversal pattern of the UE among the one or more cells.

5. The RIC (109) according to claim 1, wherein the mobility history information and the subscriber ID are received by the RIC from the base station via the E2 interface using one of a first message and a second message.

6. The RIC (109) according to claim 1, wherein the priority cell list and the subscriber ID are sent to the base station via the E2 interface using a first message.

7. The RIC (109) according to claim 1, wherein the priority cell list and the subscriber ID are sent to the base station via the E2 interface using a second message.

8. A method comprising: The Radio Access Network (RAN) Intelligent Controller (RIC) (109) receives mobility history information of the User Equipment (UE) and the subscriber identifier (ID) of the UE from the base station, wherein the base station is the place where the UE is connected; The RIC (109) stores the mobility history information of the UE based on the subscriber ID of the UE; as well as The RIC (109) determines the priority cell list based on the mobility history information of the UE.

9. The method of claim 8, comprising: The mobility history information is mapped to the subscriber ID of the UE by the RIC (109); as well as The mapped mobility history information is stored by the RIC (109) for determining the priority cell list.

10. The method of claim 8, comprising: The priority cell list is determined by the RIC (109) based on the mobility history information, wherein the mobility history information of the UE includes information about one or more cells among a plurality of cells accessed by the UE during an inactive state, an idle state, or a connected state; as well as The priority cell list is sent to the base station by the RIC (109).

11. The method of claim 8, wherein determining the priority cell list comprises: The RIC (109) determines the priority of each cell in one or more cells based on the mobility history information, wherein the mobility history information includes information about: the amount of time the UE spends in the one or more cells, the number of times the UE accesses the one or more cells, and the traversal pattern of the UE between the one or more cells.

12. The method of claim 8, wherein the mobility history information and the subscriber ID are received by the RIC from the base station via an E2 interface using one of a first message and a second message.

13. The method of claim 8, wherein the priority cell list and the subscriber ID are sent to the base station via an E2 interface using a first message.

14. The method of claim 8, wherein the priority cell list and the subscriber ID are sent to the base station via an E2 interface using a second message.

15. A base station (107), comprising: The memory (405) is configured to store instructions executable by the processor (401); as well as The processor (401) is configured to execute the instructions stored in the memory (405), thereby enabling the user equipment (UE) to connect to the base station: Receive the UE's mobility history information and the UE's subscriber identifier (ID) from the UE. Send the UE's mobility history information and subscriber ID to the Radio Access Network (RAN) Intelligent Controller (RIC); The priority cell list is received from the RIC, wherein the RIC determines the priority cell list based on the mobility history information of the UE; as well as Paging is performed based on the priority cell list.

16. The base station (107) according to claim 15, wherein the processor (401) is configured to: The UE receives an information element (IE), wherein the IE indicates the availability of the mobility history information; Send a request message to the UE for sharing the UE's mobility history information; and In response to the request message, the mobility history information of the UE is received.

17. The base station (107) of claim 15, wherein the paging is performed when the base station receives at least one of a signaling message or data for the UE during an inactive state.

18. The base station (107) of claim 15, wherein the mobility history information of the UE includes information about one or more cells among a plurality of cells accessed by the UE during an inactive state, an idle state, or a connected state.

19. The base station (107) according to claim 15, wherein the processor (401) is configured to: Set a timer for a predefined time period; and During the predefined time period, paging is performed in one or more cells based on at least one of the following: successful paging or paging in one or more cells based on the second highest priority of the priority cell list.

20. A non-transitory computer-readable medium comprising instructions for performing operations, the operations including: Receive mobility history information of user equipment (UE) and subscriber identifier (ID) of the UE from a base station, wherein the base station is the location where the UE connects; The UE's mobility history information is stored based on the UE's subscriber ID; as well as The priority cell list is determined based on the UE's mobility history information.

Images