Terminal and communication method
AI and machine learning models enhance handover performance in wireless communication systems by predicting and executing handovers, addressing uncertainties in event prediction and improving mobility efficiency.
Patent Information
- Application Number
- PCT/JP2025/017282
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-12
- Publication Date
- 2026-11-19
AI Technical Summary
Existing handover procedures in wireless communication systems, particularly in 5G and beyond, face challenges in optimizing mobility performance due to uncertainties in event prediction, leading to potential handover failures and inefficiencies.
Implementing artificial intelligence and machine learning models to predict handover events, allowing terminals to verify and execute handovers based on predicted events, thereby enhancing mobility performance.
Improves handover performance by reducing handover failures and optimizing mobility through AI-driven event prediction and execution.
Smart Images

Figure JP2025017282_19112026_PF_FP_ABST
Abstract
Description
Terminal and Communication Method
[0001] The present invention relates to a terminal and a communication method in a communication system.
[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), studies on a radio communication scheme called 5G or NR (New Radio) (hereinafter, the radio communication scheme is referred to as "5G" or "NR") are progressing in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction of delay in a radio section, and the like. In 5G, various radio technologies are being studied to satisfy the requirement that the delay in the radio section is 1 ms or less while realizing a throughput of 10 Gbps or more.
[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core) which is a core network in a network architecture of LTE (Long Term Evolution) and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) which is RAN (Radio Access Network) in the network architecture of LTE is being studied (for example, Non-Patent Document 1).
[0004] Furthermore, various requirements are being studied for next-generation 6G. For example, the requirements include Ultra broadband communication, Mission critical communication, Ultra massive connection, Universal coverage, Intelligent connection, Ubiquitous sensing, and the like.
[0005] To meet these requirements, the new concept aims for extensibility (e.g., making it more effective for future use), ease of operation, customizability (e.g., making it easier to operate), and sustainability (e.g., cost reduction, a more robust configuration, and resilience). Furthermore, guaranteed communication, ensuring a minimum level of performance at all times, is being considered.
[0006] Furthermore, the use of artificial intelligence / machine learning models (AI (Artificial Intelligence) / ML (Machine Learning) models) to perform various controls such as network management or automation is being considered (for example, Non-Patent Document 2).
[0007] 3GPP TS 23.501 V18.7.0 (2024-09)3GPP TSG-RAN Meeting #105 RP-242393, Melbourne, Australia, 9-12 September 2024
[0008] AIML may be supported for mobility. When the UE performs event prediction, the handover procedure with event reporting can be optimized to further improve performance.
[0009] This invention has been made in view of the above points, and aims to improve handover performance when performing event prediction using artificial intelligence and machine learning models for mobility.
[0010] According to the disclosed technology, a terminal is provided which includes a receiving unit that receives a handover command from a base station, and a control unit that predicts and verifies whether an event will occur during a first period that begins from the time the handover command is received, and if the control unit predicts that the event will occur during the first period, it performs a handover based on the handover command.
[0011] According to the disclosed technology, handover performance can be improved when performing event prediction using artificial intelligence and machine learning models for mobility.
[0012] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating an example of a handover model (1) in an embodiment of the present invention. This is a diagram illustrating an example of a handover model (2) in an embodiment of the present invention. This is a diagram illustrating an example of a handover model (3) in an embodiment of the present invention. This is a diagram illustrating an example of a handover (1) in an embodiment of the present invention. This is a diagram illustrating an example of a handover (2) in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of a terminal 20 in an embodiment of the present invention. This is a diagram illustrating an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention.
[0013] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.
[0014] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced, LTE-Advanced and later technologies (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.
[0015] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters means that predetermined values are pre-configured, or that wireless parameters notified from the network node 30 or terminal 20 are configured.
[0016] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.
[0017] The RAN (Radio Access Network) is a network node 30 having wireless access functionality, which may include a base station 10, and is connected to a UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN (Data Network) and having functions such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, multiple network slices are constructed.
[0018] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
[0019] The SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. The PCF is a network node 30 that has the function of controlling network policies. The AF is a network node 30 that has the function of controlling application servers. The NRF is a network node 30 that has the function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that holds the said data.
[0020] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assigned to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.
[0021] The RAN is a network node 30 having wireless access functionality and is connected to the UE, AMF, and UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN, having functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.
[0022] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.
[0023] SMF is a network node 30 that has functions such as session management, IP address allocation and management for UEs, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining which NSSAIs are allowed, determining which NSSAIs are configured, and determining which AMF set the UE connects to. PCF is a network node 30 that has the function of controlling network policies. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is the SEPP in the visited network, and hSEPP is the SEPP in the home network.
[0024] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the Visited PLMN. The Visited PLMN and Home PLMN are connected via vSEPP and hSEPP. The UE can communicate with the UDM of the Home PLMN, for example, via the AMF of the Visited PLMN.
[0025] Furthermore, in an NG-RAN (Next Generation Radio Access Network), a gNB, which is a RAN node, may have an architecture separated into gNB-CU (Central Unit) and gNB-DU (Distributed Unit). One gNB-CU may accommodate multiple gNB-DUs, and one gNB-DU may accommodate multiple cells.
[0026] The application of AIML to mobility is being considered. It is also anticipated that AIML will be applied to mobility in 6G.
[0027] The application of AIML to enhance mobility in RRC Connected Mode is being considered (see Non-Patent Document 2). For example, the following may be performed on an AIML basis: • RRM (Radio Resource Management) measurement and event prediction • Cell-level measurement prediction including intra and inter-frequency • Cell beam measurement prediction for L3 mobility • Handover failure prediction, RLF (Radio Link Failure) prediction • Measurement event prediction
[0028] Other User Assistance Information (UAI) may be used on the network side. The evaluation of AIML-assisted mobility may take into account the trade-offs between handover performance and complexity. The testability, interoperability, impact on RRM requirements, and performance of AIML-assisted mobility may also be considered.
[0029] Two options for event prediction to enhance mobility procedures are being considered.
[0030] Option 1: Prepare for the handover in advance according to a report based on predicted measurement events, while the handover is performed as usual based on actual or real-world measurement results.
[0031] Option 2: Handover preparations can be made in advance based on reports of predicted measurement events, and the handover can also be performed in advance based on the predicted events.
[0032] Options 1 and 2 offer superior performance compared to the legacy solution, and option 2 outperforms option 1 in terms of handover failure rate.
[0033] Here, it is unclear what the UE's behavior will be after reporting a predicted measurement event, namely whether an additional Measurement Report (MR) is required before receiving a Handover Command (HOC).
[0034] Furthermore, after reporting the predicted measurement events, the UE may provide a measurement report based on the actual / real / predicted measurement results. Handover execution may be postponed even if the target cell is already prepared in advance and the actual or real measurement indicates that the target cell's radio state is ready.
[0035] (Coupling with CHO) After preparing for the handover of the AI trigger, the CHO message (condTargetConfig and condReconfDuration) can be reused by adding AI-related conditions in conditionInfo, and the UE may directly execute the RACH procedure on the target cell, as long as one or more condTargetConfigs are triggered within condReconfDuration. Note that CHO is a necessary capability for AI-based mobility.
[0036] (Decoupling from CHO) A new message is introduced to communicate AI-based HOC, conditions, and durations, and the UE directly executes the RACH procedure on the target cell as long as one or more of the newly introduced conditions are triggered within the duration. Note that AI-based mobility may be a capability independent of the CHO. Messages can be customized for AI functions, such as predictive-based conditions.
[0037] Figure 3 illustrates an example (1) of a handover model in an embodiment of the present invention. As shown in Figure 3, time-domain prediction may be performed to improve HO performance. The network sends a handover command purely based on the actual measurement event, regardless of whether the actual measurement result (time t2) is earlier or later than the predicted measurement event (time t1). Prediction is used only for early HO preparation. Figure 3 shows an example where t2 is earlier than t1.
[0038] Figure 4 is a diagram illustrating an example (2) of the handover model in an embodiment of the present invention. In Figure 4, t2 is later than t1. The network sends a handover command purely based on the actual measurement event, regardless of whether the actual measurement result (time t2) is earlier or later than the predicted measurement event (time t1).
[0039] Figure 5 is a diagram illustrating an example (3) of a handover model in an embodiment of the present invention. As shown in Figure 5, HO preparation is initiated when an event is expected to occur (i.e., t0), and an HO command is sent when the event A3 entry conditions are met based on actual or real-world measurements and the event is expected to be met within the duration of the TTT (Time to Trigger). Both early HO preparation and early HO command are possible, which can reduce the TTT.
[0040] In the handover cases shown in Figures 3, 4, or 5, it was unclear whether additional measurement reports were required before receiving the handover command.
[0041] Furthermore, CHO is defined in NR, which allows UE to decide whether or not to HO based on conditions. In addition to existing conditions, conditions related to prediction can be added to enhance CHO using UE predictions. UE needs to support both CHO and AI-based mobility simultaneously by reusing CHO for AI-based mobility.
[0042] The HO procedure may be extended as follows. The behavior of the UE when the reported prediction is correct may be defined as follows. What the UE should do after reporting the predicted measurement event may be 1) and / or 2) below.
[0043] 1) The UE may report predicted measurement events. The report may include the predicted time to happen (TTH), the predicted or measured measurement result for the corresponding cell, and the cell ID.
[0044] 2) After reporting the predicted event, the UE may evaluate the start, end and trigger condition of the measurement event corresponding to the reported predicted measurement event based on evaluation or measurement, and report the measurement event based on the following.
[0045] Option 1: The UE may report the measurement event when the start condition of the measurement event is satisfied. Option 2: The UE may report the measurement event based on a shortened or different TTT (for example, TTT after prediction). The terminal may determine the value of the post-prediction TTT based on the specification, or receive a configuration or instruction for the value of the post-prediction TTT. Option 3: The UE may report the measurement event if the entry condition of the measurement event is satisfied at TTH.
[0046] The UE may report the measurement event based on the above option 1 / 2 / 3 when one of the following conditions is satisfied. - The same neighboring cell as the predicted measurement event is reported in the measurement event. - The measurement event is entered, and the reporting of the measurement event is triggered at the predicted time instance within the error tolerance gap.
[0047] Under the CHO framework, the HO procedure may be enhanced as follows. What the UE shall do after reporting the predicted measurement event may be as follows.
[0048] 1) The UE may report the predicted measurement event. The report may include the predicted Time to happen (TTH), the predicted or measured measurement result for the corresponding cell, and the cell ID.
[0049] 2) The UE may receive a conditional handover command, and the condition may further include one or more of the following.
[0050] a) The start conditions for a measurement event corresponding to a reported predicted measurement event may be met in a TTH-TTC (Time to Collision) or TTH-TTT or a specified, set or notified time instance. Furthermore, the start of the measurement event may last for a specified, set or notified duration. If the start conditions are met, the corresponding adjacent cell may be the same as the prediction, or it may be in the candidate cell list set or notified to the UE.
[0051] b) If the predicted measurement event is still valid in TTH-TTC or TTH-TTT or in the specified, configured or notified time instance. Valid means one or a combination of the following: • No TTH updates, or updates within the error tolerance period. • No updates to the corresponding adjacent cell ID. • No updates to the predicted measurement result, or updates within the error tolerance. • The probability or confidence of the prediction is still above the threshold.
[0052] The above-mentioned error tolerance range or threshold is specified, set, or notified to the UE. Logical operations (AND, OR, NOT) may be applied between conditions.
[0053] The term "HO command (Handover command)" may refer to a setting or instruction to the UE that commands the UE to change a serving cell, PCell, or SPCell. An HO command may include one or a list of cell IDs as the target cell ID. An HO command may include information about the target cell (e.g., time and / or frequency position). Handover commands can be transmitted to the UE via signaling as described in Note 2 below.
[0054] The terms "execute handover command" or "execute handover command" may refer to one or more of the following UE behaviors.
[0055] 1) The UE detaches from the source cell. 2) The UE applies the settings of the target cell configured or notified to the UE. 3) The UE performs downlink / uplink synchronization with the target cell configured or notified to the UE. 4) The UE performs the RACH procedure on the target cell configured or notified to the UE.
[0056] Further extended UE handover procedures, separate from CHO, may be defined as follows: The UE may verify the following based on the received HO command (as defined above):
[0057] 1) The UE may verify the start, end, and / or trigger of one or more measurement events based on measurements taken within a time window or before the timer expires.
[0058] 2) The UE may verify the start, end, or trigger of one or more measurement events based on the inferred measurement values (i.e., measurement value predictions). Option 1: The UE may verify whether the start, end, or trigger of the measurement event occurs before Timer #1 expires or within Time Window #1. This verification may continue until the end of Time Window #1 or until Timer #1 expires. Option 2: The UE may verify whether the start, end, or trigger of the measurement event occurs before Timer #1 expires or within Time Window #1. This verification may continue until the end of Time Window #2 or until Timer #2 expires.
[0059] 3) The UE may further verify whether the adjacent cell corresponding to the above event is the same as the one set, or whether it is in the list of cells that have been set or notified.
[0060] 4) UE may verify the above combinations using logical operations such as AND, OR, and NOT.
[0061] In addition to the above UE behavior, the following may also be performed: Measurement events (e.g., event A3) and corresponding settings (e.g., offset, hysteresis, TTT) may be specified, set, or notified to the UE. For example, the measurement event and corresponding settings may be notified by an HO command. A time window (#1 / #2) can be started when the UE receives an HO command with a specified, set, or notified offset and duration. The offset and duration of the time window may be notified by an HO command. The UE can start a timer (#1 / #2) when it receives an HO command, and the expiration time of the timer is specified, set, or notified. For example, the expiration time of the timer may be notified by an HO command.
[0062] The UE may execute an HO command (as defined on the glossary page) if one or a combination of the above conditions is met. The UE may stop the corresponding timer if one or a combination of the above conditions is met. The UE may report that no HO command was executed if the conditions are not met until the end of the time window or the timer expires.
[0063] Figure 6 is a diagram illustrating an example (1) of a handover in an embodiment of the present invention. As shown in Figure 6, within Window #1 or before Timer #1 expires, the UE may verify whether the start, end, or trigger of an event specified by the HO command occurs. If the UE anticipates that an event will occur, it may execute the HO procedure. If no event is anticipated, the UE may continue the verification until the end of Window #1 or until Timer #1 expires. Window #1 may start from the time the HO command is received, and Timer #1 may start from the time the HO command is received.
[0064] Figure 7 illustrates an example (2) of a handover in an embodiment of the present invention. As shown in Figure 7, within Window #1 or before Timer #1 expires, the UE may verify whether the start, end, or trigger of an event specified by the HO command occurs. If the UE anticipates that an event will occur, it may execute the HO procedure. If no event is anticipated, the UE may continue verifying until the end of Window #2 or until Timer #2 expires. Window #2 may start from the time the HO command is received, and Timer #2 may start from the time the HO command is received.
[0065] The UE may report the following capabilities to the network: • Capabilities of each operation • Capabilities of the hold timer • Capabilities of each option in each operation, or combinations of options • Capabilities of each choice in each operation, or combinations of choices
[0066] UEs may report the above capabilities for each frequency. Capabilities may also be reported for each UE, each FR1, FR2, FR2-1, FR2-2, each SCS, each bandwidth, each BC, each FC, or each FSPC.
[0067] UEs can report the above capabilities for each cell. Capabilities may also be reported for each UE, each cell, or for each TDD and FDD.
[0068] The following is referred to as Note 1.
[0069] Throughout the entire operation, which operation applies, or / or which option or alternative is used, may be determined as follows: - Set by higher-level parameters; - Determined by relevant higher-level parameters; - Indicated by MAC-CE or DCI; - Determined based on UE capability; - As specified in the specification; - Based on conditions specified in the specification; - Determined by the settings of higher-level parameters / MAC-CE / DCI and reported terminal capability (combination of the above determinations).
[0070] Throughout the entire process, multiple options and alternatives can be combined into a single option / alternative.
[0071] Throughout its operation, the UE may assume that certain behaviors, behavior options, or behavioral alternatives may apply only when the UE reports support for a particular feature or model.
[0072] The following is referred to as Note 2.
[0073] The UE can receive the following types of information from the NW (the NW can be referred to as gNB throughout the proposal): • Information via upper-layer signaling (e.g., RRC messages / LPP messages) • MAC-CE, MAC-CE with a new LCID in the subheader, extensions to existing MAC-CE (e.g., introducing a new octet) • DCI, DCI field: existing DCI field or newly introduced DCI field, RNTI: existing RNTI or DCI with scrambled CRC by newly introduced RNTI, DCI format: existing DCI format or newly introduced DCI format • Combinations of the above information
[0074] The UE may receive information from the NW in the following periodic types: Opt1: Periodic Opt2: Semi-persistent (triggered by UE or gNB instruction) Opt3: Aperiodic (triggered by UE or gNB instruction)
[0075] The following is referred to as Note 3.
[0076] The UE can transmit the following types of information to the NW (where NW can be referred to as gNB throughout the proposal): • Information via upper-layer signaling (e.g., RRC messages / LPP messages) • MAC-CE, MAC-CE with a new LCID in the subheader, extending an existing MAC-CE (e.g., introducing a new octet) • UCI, UCI on PUCCH, UCI on PUSCH • UAI, which may be accompanied by a simple reason for non-applicability • Combinations of the above information
[0077] The UE may report information to the NW in the following periodic types: Opt1: Periodic Opt2: Semi-persistent (triggered by UE or gNB instruction) Opt3: Aperiodic (triggered by UE or gNB instruction)
[0078] The above-described operation allows AI-based mobility to be implemented independently of CHO's capabilities. For example, customized messages for AI functionality can be used, such as prediction-based conditions.
[0079] In other words, it is possible to improve handover performance when performing event prediction using artificial intelligence and machine learning models for mobility.
[0080] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiments.
[0081] <Base Station 10 and Network Node 30> Figure 8 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 8, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 8 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.
[0082] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.
[0083] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.
[0084] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to the operation described in the embodiment.
[0085] The control unit 140 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.
[0086] <Terminal 20> Figure 9 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 9, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 9 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.
[0087] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiving unit 220 also receives setting information, instructions, and notifications related to paging notification information and the low-power wake-up signal from the base station 10. For example, the receiving unit 220 receives the low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to the operation described in the embodiment.
[0088] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.
[0089] (Hardware Configuration) The block diagrams (Figures 8 and 9) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may also be realized by combining the above one device or the above multiple devices with software.
[0090] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0091] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.
[0092] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.
[0093] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit, call processing unit, etc., may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.
[0094] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.
[0095] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).
[0096] The memory 1002 is a computer-readable recording medium and may be composed of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or at least a combination of these. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of the present disclosure.
[0097] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., card, stick, key drive), a floppy® disk, a magnetic strip, or a combination of at least two of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.
[0098] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, a transmit / receive antenna, amplifier section, transmit / receive section, or transmission path interface may be implemented by the communication device 1004. The transmit / receive section may be implemented in a physically or logically separated manner, consisting of a transmit section and a receive section.
[0099] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0100] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.
[0101] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0102] <Configuration relating to this embodiment> (1) A terminal having a receiving unit that receives a handover command from a base station, and a control unit that predicts and verifies whether an event will occur during a first period that begins from the time the handover command is received, wherein the control unit predicts that the event will occur within the first period and performs a handover based on the handover command. (2) The terminal according to paragraph 1, wherein the control unit acquires the event and the settings corresponding to the event based on the handover command. (3) The terminal according to paragraph 1, wherein the control unit does not predict that the event will occur and predicts and verifies whether the event will occur until the end of the first period. (4) The terminal according to paragraph 1, wherein the control unit does not predict that the event will occur and predicts and verifies whether the event will occur until the end of a second period that is shorter than the first period and begins from the time the handover command is received. (5) The terminal according to paragraph 1, wherein the control unit determines the length of the first period based on the handover command. (Clause 6) A communication method in which a terminal performs the following steps: receiving a handover command from a base station; predicting and verifying whether an event will occur during a first period that begins from the time the handover command is received; and, if it is predicted that the event will occur during the first period, performing a handover based on the handover command.
[0103] Any of the above configurations can improve handover performance when performing event prediction using artificial intelligence and machine learning models for mobility. Furthermore, according to paragraphs 2 through 5, AI-based mobility can be implemented independently of CHO's capabilities. For example, customized messages for AI functions can be used, such as prediction-based conditions.
[0104] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.
[0105] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.
[0106] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", "Radio Access Network (RAN)", and "Network" may be used interchangeably.
[0107] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.
[0108] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "Terminal" may be used interchangeably.
[0109] The terminal may be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other appropriate term.
[0110] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0111] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be interpreted as a sidelink channel.
[0112] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).
[0113] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.
[0114] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.
[0115] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.
[0116] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).
[0117] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."
[0118] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during execution.
[0119] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.
[0120] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.
[0121] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.
[0122] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.
[0123] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.
[0124] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.
[0125] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.
[0126] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.
[0127] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.
[0128] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0129] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.
[0130] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device
Claims
1. A terminal comprising: a receiving unit that receives a handover command from a base station; and a control unit that predicts and verifies whether an event will occur during a first period that begins from the time the handover command is received, wherein the control unit predicts that the event will occur during the first period, and performs a handover based on the handover command.
2. The terminal according to claim 1, wherein the control unit acquires the event and the settings corresponding to the event based on the handover command.
3. The terminal according to claim 1, wherein the control unit predicts and verifies whether or not the event will occur until the end of the first period if it does not predict that the event will occur.
4. The terminal according to claim 1, wherein the control unit predicts and verifies whether the event will occur if it does not predict that the event will occur, until the end of a second period which is shorter than the first period and begins from the time the handover command is received.
5. The terminal according to claim 1, wherein the control unit determines the length of the first period based on the handover command.
6. A communication method in which a terminal performs the following steps: receiving a handover command from a base station; predicting and verifying whether an event will occur during a first period starting from the time the handover command is received; and, if it is predicted that the event will occur during the first period, performing a handover based on the handover command.
