Node of a wireless communication system and a method performed by it

Abstract

The present disclosure relates to a 5G or 6G communication system that supports faster data transmission speeds. The present disclosure provides a node of a wireless communication system and methods performed by said node. A method performed by a first node in a wireless communication system comprises: receiving a first message from a second node comprising at least one of mobility information or L3 measurement results associated with a terminal; determining a first timing advance (TA) value based on at least one of said mobility information, L1 measurement results, or said L3 measurement results associated with the terminal; transmitting a second message to the terminal comprising a first TA value used to access a target cell when the terminal performs a handover; and receiving a third message from the second node comprising a second TA value used to evaluate whether the first TA value is appropriate.

Description

Technology Field

[0001] The present disclosure relates to the technical field of wireless communication, in particular to a node of a wireless communication system and a method performed by the same. Background Technology

[0002] Mobile communication technology defines wide frequency bands to enable fast transmission speeds and new services, and can be implemented not only in "Sub 6 GHz" bands such as 3.5 GHz, but also in "Above 6 GHz" bands, referred to as ultra-high frequency (millimeter wave, mmWave), including 28 GHz and 39 GHz. In addition, the implementation of 6G mobile communication technology (referred to as a Beyond 5G system) in the terahertz band (e.g., 95 GHz to 3 THz band) has been considered to achieve transmission speeds 50 times faster than 5G mobile communication technology and ultra-low latency at one-tenth the level of 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to support services and satisfy performance requirements for Enhanced Mobile Broadband (eMBB), Ultra Reliable & Low Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), technologies included beamforming and massive MIMO to mitigate propagation path loss and increase transmission distance in ultra-high frequency bands; dynamic operation of numerology (e.g., operation of multiple subcarrier spacing) and slot formats for the efficient utilization of ultra-high frequency resources; initial access techniques to support multi-beam transmission and broadband; the definition and operation of Bandwidth Part (BWP); new channel coding methods such as Low Density Parity Check (LDPC) codes for high-volume data transmission and polar codes for the reliable transmission of control information; L2 pre-processing; and dedicated networks specialized for specific services. Standardization of network slicing and other features provided has been carried out.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology in consideration of the services that the 5G mobile communication technology was intended to support. Additionally, physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything), which aims to assist autonomous vehicles in making driving decisions and increase user convenience based on information regarding their location and status transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims to operate systems that meet various regulatory requirements in unlicensed bands; NR terminal power saving (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand network service areas by integrally supporting wireless backhaul links and access links, mobility enhancement technologies including conditional handover and Dual Active Protocol Stack (DAPS) handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G basic architectures (e.g., service-based architecture or service-based interface) to incorporate Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] With the commercialization of such 5G mobile communication systems, an exponentially increasing number of connected devices will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the advancement of these 5G mobile communication systems can serve as a foundation for the development of new waveforms for ensuring coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterial-based lenses and antennas to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) technology, as well as full-duplex technology for improving frequency efficiency and system networks of 6G mobile communication technology, AI-based communication technology that utilizes satellites and AI from the design stage and internalizes end-to-end AI support functions to achieve system optimization, and next-generation distributed computing technology that realizes services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] Efforts to develop improved 5G or pre-5G communication systems have continued to meet the increasing demand for wireless data communication services following the establishment of 4G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post LTE systems."

[0009] Wireless communication is one of the most successful innovations in modern history. Recently, the number of wireless communication service subscribers has exceeded 5 billion and continues to grow rapidly. With the increasing penetration of smartphones and other mobile data devices (e.g., tablet computers, laptops, netbooks, e-book readers, and mechanical devices) among consumers and businesses, the demand for wireless data services is surging. To respond to the rapid growth of mobile data services and support new applications and deployments, it is crucial to improve the efficiency and coverage of wireless interfaces. The problem to be solved

[0010] The present disclosure relates to a method and apparatus for solving problems such as delay, resource usage, or signal interference that may occur in connection with mobility management or decision-making during handover in a wireless communication system. means of solving the problem

[0011] Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, the method comprising: receiving a first message from a second node comprising at least one of mobility information or an L3 measurement result associated with a terminal; determining a first timing advance (TA) value based on at least one of the mobility information, the L1 measurement result, or the L3 measurement result associated with the terminal; transmitting a second message to the terminal comprising a first TA value used to access a target cell when the terminal performs a handover; and receiving a third message from the second node comprising a second TA value used to evaluate whether the first TA value is appropriate.

[0012] Embodiments of the present disclosure provide a method performed by a second node in a wireless communication system, the method comprising: transmitting to a first node a first message comprising at least one of mobility information or an L3 measurement result associated with a terminal, wherein at least one of the mobility information associated with the terminal, the L3 measurement result, or the L1 measurement result is used by the first node to determine a first timing advance (TA) value; and transmitting to the first node a third message comprising a second TA value used to evaluate whether the first TA value is appropriate, wherein the first TA value is used to access a target cell when the terminal performs a handover.

[0013] Embodiments of the present disclosure provide a method performed by a terminal in a wireless communication system, the method comprising: transmitting a 28 message including an L1 measurement result associated with the terminal to a first node; receiving a 27 message including a first timing advance (TA) value from the first node; and accessing a target cell based on the first TA value, wherein the first TA value is determined by the first node based on at least one of mobility information associated with the terminal, an L1 measurement result, and an L3 measurement result.

[0014] According to embodiments of the present disclosure, the step of accessing a target cell based on the first TA value includes the step of accessing the target cell based on the first TA value within an effective time corresponding to the first TA value.

[0015] According to embodiments of the present disclosure, the method further comprises: obtaining a third TA value through random access when the first TA value and / or the valid time corresponding to the first TA value is not applicable; and accessing the target cell based on the third TA value.

[0016] Embodiments of the present disclosure provide a first node device of a wireless communication system, which comprises a transceiver configured to transmit and receive a signal and a processor connected to the transceiver, wherein the processor is configured to perform methods performed by the first node in the wireless communication system according to embodiments of the present disclosure.

[0017] Embodiments of the present disclosure provide a second node device of a wireless communication system, which comprises a transceiver configured to transmit and receive a signal and a processor connected to the transceiver, said processor configured to perform methods performed by the second node in the wireless communication system according to embodiments of the present disclosure.

[0018] Embodiments of the present disclosure provide a terminal of a wireless communication system, comprising a transceiver configured to transmit and receive a signal and a processor connected to the transceiver, wherein the processor is configured to perform methods performed by the terminal in the wireless communication system according to embodiments of the present disclosure.

[0019] Embodiments of the present disclosure provide a computer-readable medium storing a computer-readable instruction, which, when executed by a processor, performs methods performed by a first node and / or a second node and / or a terminal in a wireless communication system according to the embodiments of the present disclosure. Effects of the invention

[0020] Methods performed by a first node and / or a second node in a wireless communication system provided by the present disclosure can effectively support the nodes and / or terminals in performing mobility management or decision-making through the exchange of information between the nodes and / or terminals. Brief explanation of the drawing

[0021] The foregoing and other aspects, features, and advantages of specific embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings. Figure 1 illustrates an exemplary system architecture of System Architecture Evolution (SAE). FIG. 2 illustrates an exemplary system architecture according to various embodiments of the present disclosure. FIG. 3a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3d illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3e illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3f illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3g illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3h illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3i illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3j illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3k illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3la illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3lb illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3m illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3n illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3o illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3p illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3q illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3ra illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 3rb illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 4a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 4b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 4c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 4d illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 4e illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 5a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 5b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 5c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 6a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 6b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 6c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 7 illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 8 illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 9 illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10d illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10e illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 10f illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11d illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11e illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11f illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11g illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11h illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11i illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 11j illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 12a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 12b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 12c illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 12d illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 13a illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 13b illustrates a schematic diagram of one aspect of a mobility management support method according to embodiments of the present disclosure. FIG. 14 illustrates a flowchart of a method performed by a first node in a wireless communication system according to embodiments of the present disclosure. FIG. 15 illustrates a flowchart of a method performed by a second node in a wireless communication system according to embodiments of the present disclosure. FIG. 16 illustrates a schematic diagram of a node according to embodiments of the present disclosure. FIG. 17 illustrates a schematic diagram of a terminal according to an embodiment of the present disclosure. Specific details for implementing the invention

[0022] The following description, with reference to the attached drawings, is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these should be considered merely illustrative. Accordingly, those skilled in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Additionally, descriptions of known functions and structures may be omitted for clarity and brevity.

[0023] The terms and expressions used in the following specification and claims are not limited to their dictionary meanings but are used by the inventors merely to enable a clear and consistent understanding of the present disclosure. Accordingly, it will be obvious to a person skilled in the art that the following description of various embodiments of the present disclosure is provided merely for illustrative purposes and is not intended to limit the present disclosure as defined by the appended claims and their equivalents.

[0024] The singular form should be understood to include the plural form unless otherwise specified in the context. For example, the reference to "component surfaces" includes a reference to one or more of such surfaces.

[0025] The terms “comprising” or “may comprising” mean that the relevant function, operation, or component may be used in various embodiments of the present disclosure and do not limit the existence of one or more additional functions, operations, or components. Additionally, the terms “comprising” or “having” may be interpreted as indicating a specific feature, number, step, operation, component, element, or combination thereof, but are not interpreted as excluding the possibility of the existence of one or more other features, numbers, steps, operations, components, elements, or combinations thereof.

[0026] The term “or” as used in the various embodiments of the present disclosure includes any of the listed items and all combinations thereof. For example, “A or B” may include A, may include B, or may include both A and B.

[0027] Unless otherwise defined, all terms used in this disclosure, including technical or scientific terms, have the same meaning as understood by a person skilled in the art to which this disclosure pertains. Terms defined in commonly used dictionaries are to be interpreted as having the same meaning as their contextual meaning in the relevant art and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0028] The drawings and various embodiments described below to illustrate the principles of the present disclosure are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure in any way. A person skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably configured system or device.

[0029] FIG. 1 illustrates an exemplary system architecture (100) of system architecture evolution (SAE). A terminal (UE: user equipment) (101) is a terminal device that receives data. An evolved universal terrestrial radio access network (E-UTRAN) (102) is a radio access network that includes a macro base station (eNodeB / NodeB) that provides the terminal with an interface to access the radio network. A mobility management entity (MME) (103) is responsible for managing the terminal's mobility context, session context, and security information. A serving gateway (SGW) (104) primarily provides functions of the user plane, and the MME (103) and SGW (104) may be on the same physical entity. A packet data network gateway (PGW) (105) is responsible for functions such as billing and legal intervention, and may be on the same physical entity as the SGW (104). The policy and charging rules function entity (PCRF) (106) provides quality of service (QoS) policies and charging criteria. The serving general packet radio service support node (SGSN) (108) is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS).The home subscriber server (HSS) (109) is a home subsystem of the terminal and serves to protect user information including the terminal's current location, the address of the serving node, user security information, and the terminal's packet data context.

[0030] FIG. 2 illustrates an exemplary system architecture (200) according to various embodiments of the present disclosure. Other embodiments of the system architecture (200) may also be used without departing from the scope of the present disclosure.

[0031] A terminal (201) is a terminal device that receives data. A next-generation radio access network (NG-RAN) (202) is a radio access network that includes a base station (a gNB or eNB connected to a 5G core network (5GC), and an eNB connected to the 5GC is also called an ng-gNB) that provides the terminal with an interface to access the radio network. An access control and mobility management function entity (AMF) (203) is responsible for managing the terminal's mobility context and security information. A user plane function entity (UPF) (204) primarily provides user plane functions. A session management function entity (SMF) (205) is responsible for session management. A data network (DN) (206) includes, for example, services from telecommunications operators, internet access, and third-party services.

[0032] The nodes mentioned in the present disclosure may include a gNB, a gNB Central Unit (gNB-CU), a gNB Distributed Unit (gNB-DU), a gNB Central Unit Control Plane (gNB-CU-CP), a gNB Central Unit User Plane (gNB CU-UP), an en-gNB, an eNB, an ng-eNB, a terminal (UE), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Mobility Management Entity (MME), a User Plane Function (UPF), a Network Data Analytics Function (NWDAF), a Management Data Analytics Function (MDAF), and other network entities or network logic units and cells and / or beams managed by them.

[0033] The fields and / or information described in this disclosure may include, but are not limited to, average values, instantaneous values, maximum values, minimum values, etc.

[0034] The fields and / or information mentioned in this disclosure may include, but are not limited to, uplinks, downlinks, uplinks and downlinks, uplinks or downlinks, etc.

[0035] The measurement reports and / or measurement results and / or signal strength and / or signal quality described in the present disclosure may include a Received Signal Strength Indicator (RSSI), Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), etc.

[0036] In the present disclosure, failure types and / or problem types may be referred to as reporting types.

[0037] In the present disclosure, reports related to a Self-Optimization Network (SON) may include one or more of a Connection Establishment Failure (CEF) report, a Random Access report, a Successful Handover report, a Radio Link Failure (RLF) report, a measurement report, or other reports related to radio connectivity.

[0038] In the present disclosure, wireless link failure refers to two cases: wireless link failure and handover failure.

[0039] In the present disclosure, mobility determination may include one or more of the generation of a Timing Advance (TA), the generation of a Handover Decision, etc.

[0040] In the present disclosure, the handover decision may include one or more of the following: selecting a target node and / or target cell, determining the handover time, determining the handover type, etc.

[0041] In the present disclosure, handover types may include one or more of Layer 3 (L3) handover, Layer 1 / Layer 2 (L1 / L2) Triggered Mobility handover, conditional handover, L1 / L2 Triggered Mobility conditional handover, Dual Active Protocol Stack (DAPS) handover, etc.

[0042] In this disclosure, "actually used" and "measured" may be used interchangeably.

[0043] In this disclosure, "actual use" and "measurement" may be used interchangeably.

[0044] In this disclosure, "actual measurement" and "actual use" may be used interchangeably.

[0045] Network self-optimization decisions mentioned in the present disclosure may include network energy saving, load balancing, coverage optimization, mobility (robustness) optimization and / or management, configuration creation and / or updating, etc.

[0046] In this disclosure, results and reports may be used interchangeably.

[0047] In the present disclosure, time may be represented by one or more of a timestamp, time point, time interval, timer, period of time, time length, time period / periodicity, and time spacing. Here, the time length may be the length of time from a specific point in time, and the specific point in time may be the current time. Time may be relative time or absolute time. In some embodiments, the period may be represented by distinct fields, for example, by a combination of a start time and an end time, or by a combination of a start time and a time period.

[0048] The times mentioned in this disclosure (e.g., start time, end time, expected start time, expected end time, etc.) may be relative time or absolute time.

[0049] In the present disclosure, a previously obtained TA value and a TA value within an LTM cell switching command may be used interchangeably.

[0050] In the present disclosure, load, load status, load information, etc., and resource status may be used interchangeably.

[0051] In the present disclosure, a source node may include one or more of a source master node, a source secondary node, a source serving node, etc.

[0052] In the present disclosure, a target node may include one or more of a target serving node, a target master node, a target secondary node, a candidate target serving node, a candidate target node, a candidate target master node, a candidate target secondary node, etc.

[0053] In the present disclosure, the term "user equipment" (UE) may refer to a user, a terminal, etc.

[0054] In the present disclosure, events and conditions may be used interchangeably. Trigger events and trigger conditions may be used interchangeably.

[0055] In the present disclosure, measurement may mean actual measurement, predicted measurement, etc.

[0056] In the present disclosure, a parameter may mean an actual measured parameter, a predicted parameter, or a generated parameter.

[0057] In the present disclosure, an event type may mean an identification representing an event. When a message receiving node receives an event type, it can determine what the event is.

[0058] In the present disclosure, a change in the RRC state may mean a transition from an RRC Inactive state or an RRC Idle state to an RRC Connected state, a transition from an RRC Connected state to an RRC Inactive state or an RRC Idle state, or any transition between an RRC Connected state, an RRC Inactive state, and an RRC Idle state.

[0059] In the present disclosure, the actual TA value used refers to the TA value used and / or applied when the terminal accesses the target cell.

[0060] In the present disclosure, predicted beam information may also be referred to as reference beam information.

[0061] In the present disclosure, the beam may also be referred to as a reference beam.

[0062] In the present disclosure, if a registration request within a request message is Start, this means that the request is to start a new report. If a registration request within a request message is End and / or Cancel, this means that the request is to end and / or cancel an existing report and / or request. If a registration request within a request message is Addition and / or Update and / or Modification, this means that the request is to add and / or update and / or modify some of the requested settings within an existing report and / or request, and accordingly, updates and reports are performed according to the added and / or updated and / or modified settings within the original report message.

[0063] In the present disclosure, a registration request may be used to direct reporting and / or measurement and / or prediction.

[0064] In the present disclosure, after the requesting node transmits an event and / or condition that triggers a report and / or measurement, if the situation satisfies the event and / or condition that triggers the report, the requested node performs the report and / or measurement.

[0065] In the present disclosure, where a report and / or measurement performed by a node is due to an event and / or condition that triggers the measurement and / or report, the event and / or condition that triggers the report and / or measurement may be included in the report message.

[0066] In the present disclosure, an event and / or condition that triggers a report, an event and / or condition that triggers a measurement, an event and / or condition that triggers a report corresponding to a report that can be performed, an event and / or condition that triggers a report corresponding to a measurement that can be performed, an event and / or condition that triggers a report corresponding to a report that cannot be performed, or an event and / or condition that triggers a report corresponding to a measurement that cannot be performed may include one or more of the following:

[0067] The measurement result of the serving cell is greater than and / or equal to and / or less than a predetermined threshold, and / or the measurement result of the serving cell is within and / or outside a predetermined interval. The serving cell may also be the serving cell beam, the serving cell component carrier, the serving cell carrier, the serving cell bandwidth part, the serving cell channel (e.g., licensed channel or unlicensed channel), etc. The event and / or condition triggering the report must include one or more of the following configurations: event type, event, predetermined threshold, predetermined interval, cell identifier, beam identifier, component carrier information, carrier information, bandwidth identifier, channel identifier, etc. The component carrier information may include one or more of the following: component carrier frequency, component carrier identifier, component carrier center frequency, component carrier start frequency, component carrier end frequency, component carrier frequency interval, etc. Carrier information may include one or more of the following: carrier frequency, carrier identifier, carrier center frequency, carrier start frequency, carrier end frequency, carrier frequency range, etc.

[0068] The measurement result of an adjacent cell is greater than and / or equal to and / or less than a predetermined threshold, and / or the measurement result of an adjacent cell is within and / or outside a predetermined interval. An adjacent cell may also be an adjacent cell beam, an adjacent cell component carrier, an adjacent cell carrier, an adjacent cell partial bandwidth, an adjacent cell channel (e.g., a licensed channel or an unlicensed channel), etc. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, predetermined interval, cell identifier, beam identifier, component carrier information, carrier information, partial bandwidth identifier, channel identifier, etc. Component carrier information may include one or more of the following: component carrier frequency, component carrier identifier, component carrier center frequency, component carrier start frequency, component carrier end frequency, component carrier frequency interval, etc. Carrier information may include one or more of the following: carrier frequency, carrier identifier, carrier center frequency, carrier start frequency, carrier end frequency, carrier frequency interval, etc.

[0069] The difference between the measurement result of an adjacent cell and the measurement result of a serving cell is greater than and / or equal to and / or less than a predetermined threshold, and / or the difference between the measurement result of an adjacent cell and the measurement result of a serving cell is within and / or outside a predetermined interval. A cell may also be a cell beam, a cell component carrier, a cell carrier, a cell partial bandwidth, a cell channel (e.g., a licensed channel or an unlicensed channel), etc. Events and / or conditions that trigger reporting must include one or more of the following settings: event type, event, predetermined threshold, predetermined interval, cell identifier, beam identifier, component carrier information, carrier information, partial bandwidth identifier, channel identifier, etc. Component carrier information may include one or more of the following: component carrier frequency, component carrier identifier, component carrier center frequency, component carrier start frequency, component carrier end frequency, component carrier frequency interval, etc. Carrier information may include one or more of the following: carrier frequency, carrier identifier, carrier center frequency, carrier start frequency, carrier end frequency, carrier frequency interval, etc. Here, the difference between the measurement result of an adjacent cell and the measurement result of a serving cell may be the value obtained by subtracting the measurement result of the serving cell from the measurement result of the adjacent cell, or the value obtained by subtracting the measurement result of the adjacent cell from the measurement result of the serving cell, etc.

[0070] The measurement result of an adjacent cell is better than the measurement result of a serving cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0071] The movement speed is greater than and / or equal to a specified threshold. The event and / or condition triggering the report must include one or more of the following settings: event type, event, specified threshold, etc.

[0072] The location of the terminal is within a specified range, and / or the distance between the terminal and the node is greater than and / or equal to and / or less than a specified threshold. The event and / or condition triggering the report must include one or more of the following settings: event type, event, specified threshold, specified interval, etc. The location may be location coordinates, an identifier of the accessed beam, an identifier of the serving cell, an identifier of the visited cell, etc.

[0073] The terminal RRC status changes. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0074] The event type can be an identifier representing an event. When a message receiving node receives the event type, it can determine what the corresponding event is.

[0075] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0076] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0077] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0078] In the present disclosure, candidate cells, handover candidate cells, and candidate target cells, etc., may be used interchangeably.

[0079] In the present disclosure, the load expected to be too large or the acceptable load may be one or more of the following: PRB utilization, number of available PRBs, number of allocated PRBs, scheduling PDCCH CCE usage, Transport Network Layer (TNL) capacity indication, radio resource status, total available capacity group, total available resource group, number of active user terminals, number of Radio Resource Control (RRC) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, Almost Blank Subframe (ABS) status, Reference Signal Received Power (RSRP) measurement report list, Reference Signal Receiving Quality (RSRQ) measurement report, Signal to Interference plus Noise Ratio (SINR) measurement report, Channel State Information (CSI) report, cell report indication, Channel Occupancy time ratio, Energy Detection threshold, signal strength and / or signal Quality, channel busy ratio, data capacity, and jitter of various content parameters, etc. Additionally, these can be expressed as proportions. For example, in some implementations, the acceptable load may be a proportion of the current load, a proportion of the current instantaneous input rate, or a proportion of the total load.In some embodiments, for example, the load amount at the time of overload may be a ratio of the current load amount, a ratio of the instantaneous input speed, or a ratio of the total load amount, and the overloaded load amount may be a ratio of the current load amount, a ratio of the instantaneous input speed, or a ratio of the total load amount.

[0080] In the present disclosure, regarding the scope requested to be reported, the scope requested to be predicted, the scope that can be measured and / or reported, the scope that cannot be measured and / or reported, the scope corresponding to the requested content, and the scope corresponding to the reported content, such scope may be one or more of the following identifiers (IDs) and / or lists of identifiers: slice, service, scenario, node, terminal (UE), cell, beam, channel, Protocol Data Unit (PRU) session, Data Radio Bearer (DRB), QoS flow, QoS level, etc. The service may be a service type, Quality of Service (QoS), scenario, etc. The service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. The quality of service may include one or more of the following: delay, throughput, reliability, packet loss rate, data transmission rate, etc. This may be identified by a 5G QoS Identifier (5QI), a QoS Class Identifier (QCI), etc. The scenario may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc.

[0081] In the present disclosure, each of the messages, such as the first to 27th messages, etc., may be a MAC CE, L1 signaling, RRC message, Xn message, X2 message, F1 message, E1 message, NG message, RRC container, and / or user plane frame, etc.

[0082] In embodiments of the present disclosure, in the case of a handover under the same base station (gNB) CU, the source gNB CU and the target gNB CU may be considered as a single gNB CU node.

[0083] In L1 / L2 Triggered Mobility (LTM), current methods or processes need to be optimized.

[0084] Example 1

[0085] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a first node transmits a first message to a second node, which includes a request for user mobility information and / or measurement results, and requests the second node to report user mobility information and / or measurement results (e.g., L3 measurement results). The first node may make mobility decisions based on the acquired user mobility information and / or measurement results, which may include, for example, generating and / or predicting a Timing Advance (TA), generating a handover decision, generating and / or predicting access beam information, etc. Handover decisions include the selection of a target node and / or target cell, the determination of a handover time, the determination of a handover type, etc. Handover types include L3 handover, L1 / L2 triggered mobility (LTM) handover, conditional handover, L1 / L2 triggered mobility (LTM) conditional handover, Dual Active Protocol Stack (DAPS) handover, etc. The generation and / or prediction of TA can be implemented by an artificial intelligence machine learning model. The generation and / or prediction of beam information can be implemented by an artificial intelligence machine learning model. The user can directly access the target cell using the TA generated and / or predicted by the first node without performing a random access procedure. To transmit the random access preamble to the target node, the target node transmits the TA value back to the source node, or the user acquires the TA through random access. The TA that can be generated and / or predicted by the source node and / or target node will effectively reduce the signaling overhead required for TA acquisition. User mobility information and / or measurement result information may be measured information or predicted information.

[0086] In some embodiments, the first message may include one or more of the following information and / or fields:

[0087] Terminal (UE) Identifier (ID: identification): Identifies the user corresponding to the requested user mobility information and / or measurement results. This may be a terminal ID or a list of terminal IDs.

[0088] Transmission Node ID: Used to identify the node transmitting the message.

[0089] Receiving Node ID: Used to identify the node receiving the message.

[0090] Identifier for Request to Report User Mobility Information and / or Measurement Results: This information is used to indicate that a request for reporting user mobility information and / or measurement results is made. This field may be represented by a single bit. For example, if the bit is 1, it indicates that a request for reporting user mobility information and / or measurement results is made; if the bit is 0, it indicates that a request for reporting user mobility information and / or measurement results is not made. Or, if the bit is 0, it indicates that a request for reporting user mobility information and / or measurement results is made; if the bit is 1, it indicates that a request for reporting user mobility information and / or measurement results is not made.

[0091] Requested content: Used to indicate requested content, which may include one or more of the following:

[0092] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, resident cell, visited cell, time of stay, time of visit, time information, etc.

[0093] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0094] Registration Request: Used to indicate the type of request. For example, this may include start, end, add, update, modify, cancel, etc.

[0095] Report Registration Request: Used to indicate the type of report request. For example, this may include start, end, add, update, modify, cancel, etc.

[0096] Reporting mode of requested content: Used to specify the reporting mode of the requested content. This may include single reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0097] Events and / or conditions triggering a report: If the events and / or conditions triggering a report are met, a report must be performed.

[0098] Reporting Periodicity: Used to indicate the interval of reporting. This may also be the time interval between two adjacent reports. This time interval may be a maximum time interval or a minimum time interval. The reporting periodicity may also be the predicted time and / or measurement time of the reported information. In one embodiment, for example, if there is no content in this field, a one-time report is indicated, and the reporting time of the one-time report is the measurement time and / or reporting time. In some embodiments, for example, the reporting periodicity may be the reporting interval of a periodic reporting mode.

[0099] Reporting Time of Requested Content: Used to indicate the time and / or time interval for which content is requested to be reported. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0100] Start time: Used to indicate the start time of the report time.

[0101] End time: Used to indicate the end time of the report time.

[0102] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0103] Requested content measurement mode: Used to specify the requested content measurement mode. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0104] Events and / or conditions triggering the measurement: If the events and / or conditions triggering the measurement are met, the measurement must be performed.

[0105] Measurement period: Used to indicate the interval of periodic measurements.

[0106] Measurement time of the requested content: Used to indicate the measurement time and / or time interval of the requested content. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0107] Start time: Used to indicate the start time of the measurement time.

[0108] End time: Used to indicate the end time of the measurement time.

[0109] Requested Prediction Time: Used to indicate the time and / or time interval for the prediction. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0110] Prediction start time: Used to indicate the start time of the prediction.

[0111] Prediction end time: Used to indicate the end time of the prediction.

[0112] Applicable / Valid Time for Requested Prediction: Used to indicate the time and / or time interval corresponding to the prediction. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0113] Start Time: Used to indicate the start time of an applicable / valid time.

[0114] End Time: Used to indicate the end time of an applicable / valid time.

[0115] Request Information: Used to indicate request information regarding user mobility information and / or measurement results. This may include one or more of the following:

[0116] Number of slices: The number of slices corresponding to user mobility information and / or measurement results requested to be reported.

[0117] Slice ID and / or ID list: A range of slices corresponding to the requested user mobility information and / or measurement results. For example, the slices corresponding to the user mobility information and / or measurement results requested to be reported must be one or more of the slice ID and / or ID list.

[0118] Cell count: The number of cells corresponding to user mobility information and / or measurement results requested to be reported.

[0119] Cell ID and / or ID list: A range of cells corresponding to the requested user mobility information and / or measurement results. For example, the cells corresponding to the user mobility information and / or measurement results requested to be reported must be one or more of the cell ID and / or ID list.

[0120] Beam count: The number of beams corresponding to user mobility information and / or measurement results requested to be reported.

[0121] Beam ID and / or ID list: A range of beams corresponding to the requested user mobility information and / or measurement results. For example, the beams corresponding to the user mobility information and / or measurement results requested to be reported must be one or more of the beam ID and / or ID list.

[0122] Number of nodes: The number of nodes corresponding to user mobility information and / or measurement results requested to be reported.

[0123] Node ID and / or list of IDs: A range of nodes corresponding to the requested user mobility information and / or measurement results. For example, the nodes corresponding to the user mobility information and / or measurement results requested to be reported must be one or more of the node ID and / or list of IDs.

[0124] Measurement and / or Prediction ID: Used to identify measurements and / or predictions.

[0125] Request ID: Used to identify the request.

[0126] In some embodiments, the second node may transmit a second message to the first node containing a response regarding user mobility information and / or measurement results to inform the first node whether the second node can report user mobility information and / or measurement results, thereby allowing the first node to know whether it can subsequently receive the requested content from the second node. In some embodiments, for example, if the second message received by the first node indicates that the second node can report user mobility information and / or measurement results, the first node may subsequently receive user mobility information and / or measurement results reported by the second node, for example, through a subsequent third message. In some other embodiments, for example, the first node may transmit a message to the second node to stop (and / or cancel) reporting based on information indicated in the received second message, for example, to stop (and / or cancel) reporting via the first message.

[0127] In some embodiments, the second message may include one or more of the following information and / or fields:

[0128] Transmission Node ID: Used to identify the node transmitting the message.

[0129] Receiving Node ID: Used to identify the node receiving the message.

[0130] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID within the first message.

[0131] Request ID: Used to identify the request corresponding to the response. In some implementations, to associate a report with a request and / or response, this ID may match the request ID in the first message.

[0132] Acknowledge for User Mobility Information and / or Measurement Results Request: Used to indicate whether user mobility information and / or measurement results can be measured and / or reported. The acknowledgment for a request for user mobility information and / or measurement results may be a bit indicating whether the request can be measured and / or reported.

[0133] Terminal ID for which reporting may be performed: ID(s) of the user(s) for whom user mobility information and / or measurement results may be measured and / or reported. This may be an ID or a list of IDs.

[0134] Cell IDs where reporting can be performed: ID(s) of the cell(s) where user mobility information and / or measurement results can be measured and / or reported. This may be an ID or a list of IDs.

[0135] Beam IDs where reporting can be performed: ID(s) of beam(s) where user mobility information and / or measurement results can be measured and / or reported. This may be an ID or a list of IDs.

[0136] Slice IDs where reporting can be performed: ID(s) of slice(s) where user mobility information and / or measurement results can be measured and / or reported. This may be an ID or a list of IDs.

[0137] Reportable content: Used to indicate content that may be reported, which may include one or more of the following:

[0138] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, cell of residence, cell visited, time of stay, time of visit, time information, etc.

[0139] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0140] Predictable content: Used to indicate content that can be predicted, and may include one or more of the following:

[0141] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, cell of residence, cell visited, time of stay, time of visit, time information, etc.

[0142] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0143] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0144] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0145] Reportable Time: Indicates the time and / or time interval during which the content can be reported. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0146] Start time: Used to indicate the start time of the reportable time.

[0147] End time: Used to indicate the end time of the reportable time.

[0148] Available Measurement Modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0149] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0150] Available Measurement Time: Used to indicate the measurement time and / or time interval during which a measurement can be performed. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0151] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0152] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0153] Predictable Time: Used to indicate the time and / or time interval during which a prediction can be performed. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0154] Prediction start time: Used to indicate the start time at which the prediction can be performed.

[0155] Prediction end time: Used to indicate the end time at which the prediction can be performed.

[0156] Applicable / Valid Time for Predictable Correspondence: Used to indicate the applicable / valid time and / or time interval for predictable correspondence. Time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0157] Start time: Used to indicate the start time of the valid time available for forecasting.

[0158] End Time: Used to indicate the end time of the valid time available for the forecast.

[0159] Reportable Response Information: Used to indicate information corresponding to user mobility information and / or measurement results that may be reported. This may include one or more of the following:

[0160] Number of slices: The number of slices corresponding to user mobility information and / or measurement results that can be reported.

[0161] Slice ID and / or ID list: A range of slices corresponding to user mobility information and / or measurement results that may be reported. For example, the slices corresponding to user mobility information and / or measurement results that may be reported are one or more of the slice ID and / or ID list.

[0162] Cell count: The number of cells corresponding to user mobility information and / or measurement results that can be reported.

[0163] Cell ID and / or ID list: A range of cells corresponding to user mobility information and / or measurement results that may be reported. For example, the cells corresponding to user mobility information and / or measurement results that may be reported are one or more of the cell ID and / or ID list.

[0164] Beam count: The number of beams corresponding to user mobility information and / or measurement results that can be reported.

[0165] Beam ID and / or ID list: A range of beams corresponding to user mobility information and / or measurement results that may be reported. For example, the beams corresponding to user mobility information and / or measurement results that may be reported are one or more of the beam ID and / or ID list.

[0166] Number of nodes: The number of nodes corresponding to user mobility information and / or measurement results that can be reported.

[0167] Node ID and / or list of IDs: A range of nodes corresponding to user mobility information and / or measurement results that may be reported. For example, the nodes corresponding to user mobility information and / or measurement results that may be reported are one or more of the node ID and / or list of IDs.

[0168] Events and / or conditions that trigger a report that can be performed: Indicates trigger events and / or conditions that trigger a report that can be performed. If the events and / or conditions that trigger a report are met, the report may be performed.

[0169] Events and / or conditions that trigger a measure that can be performed: Indicates trigger events and / or conditions that trigger a measure that can be performed. If the events and / or conditions that trigger a measure are met, the measure can be performed.

[0170] Terminal IDs for which measurement and / or reporting cannot be performed: ID(s) of user(s) for whom user mobility information and / or measurement results cannot be measured and / or reported. This may be an ID or a list of IDs.

[0171] Cell IDs where measurement and / or reporting cannot be performed: ID(s) of cell(s) where user mobility information and / or measurement results cannot be measured and / or reported. This may be an ID or a list of IDs.

[0172] Beam IDs for which measurement and / or reporting cannot be performed: ID(s) of beam(s) for which user mobility information and / or measurement results cannot be measured and / or reported. This may be an ID or a list of IDs.

[0173] Slice IDs for which measurement and / or reporting cannot be performed: ID(s) of slice(s) for which user mobility information and / or measurement results cannot be measured and / or reported. This may be an ID or a list of IDs.

[0174] Non-reportable content: Used to indicate content that cannot be reported, which may include one or more of the following:

[0175] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, cell of residence, cell visited, time of stay, time of visit, time information, etc.

[0176] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0177] Unpredictable content: Used to indicate unpredictable content, which may include one or more of the following:

[0178] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, cell of residence, cell visited, time of stay, time of visit, time information, etc.

[0179] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0180] Unavailable Report Mode: Used to indicate an unavailable reporting mode. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0181] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0182] Non-reportable Time: Indicates a time and / or time interval during which content cannot be reported. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0183] Start time: Used to indicate the start time of an unreportable time.

[0184] End time: Used to indicate the end time of the time when reporting is not possible.

[0185] Unavailable Measurement Mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0186] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0187] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0188] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0189] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0190] Unpredictable Time: Used to indicate a time and / or time interval where prediction cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0191] Prediction start time: Used to indicate the start time at which a prediction cannot be performed.

[0192] Prediction end time: Used to indicate the end time at which a prediction cannot be performed.

[0193] Applicable / Valid Time for Unpredictable Response Predictions: Used to indicate the applicable / valid time and / or time interval for unpredictable response predictions. Time can be relative or absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0194] Start Time: Used to indicate the start time of a valid time that is unavailable for forecasting.

[0195] End Time: Used to indicate the end time of a valid period that is unavailable for prediction.

[0196] Non-reportable corresponding information: Used to indicate information corresponding to user mobility information and / or measurement results that cannot be reported. This may include one or more of the following:

[0197] Number of slices: The number of slices corresponding to user mobility information and / or measurement results that cannot be reported.

[0198] Slice ID and / or ID list: A range of slices corresponding to user mobility information and / or measurement results that cannot be reported. For example, the slices corresponding to user mobility information and / or measurement results that cannot be reported are one or more of the slice ID and / or ID list.

[0199] Cell count: The number of cells corresponding to user mobility information and / or measurement results that cannot be reported.

[0200] Cell ID and / or ID list: A range of cells corresponding to user mobility information and / or measurement results that cannot be reported. For example, the cells corresponding to user mobility information and / or measurement results that cannot be reported are one or more of the cell ID and / or ID list.

[0201] Beam count: The number of beams corresponding to user mobility information and / or measurement results that cannot be reported.

[0202] Beam ID and / or ID list: A range of beams corresponding to user mobility information and / or measurement results that cannot be reported. For example, the beams corresponding to user mobility information and / or measurement results that cannot be reported are one or more of the beam ID and / or ID list.

[0203] Number of nodes: The number of nodes corresponding to user mobility information and / or measurement results that cannot be reported.

[0204] Node ID and / or ID list: A range of nodes corresponding to user mobility information and / or measurement results that cannot be reported. For example, the nodes corresponding to user mobility information and / or measurement results that cannot be reported are one or more of the node ID and / or ID list.

[0205] Events and / or conditions that trigger an unexecutable report: Indicates trigger events and / or conditions that trigger a report that cannot be executed. If the events and / or conditions triggering this report are met, the report cannot be executed.

[0206] Events and / or conditions that trigger an unpermissible measurement: Indicates trigger events and / or conditions that trigger a measurement that cannot be performed. If the events and / or conditions triggering this measurement are met, the measurement cannot be performed.

[0207] Cause / reason: Indicates the reason why measurement and / or reporting cannot be performed.

[0208] In some embodiments, the second node may transmit a third message containing user mobility information and / or measurement results to the first node according to its own circumstances and / or a first message containing a request for user mobility information and / or measurement results received from the first node. In some embodiments, for example, the first node may make mobility decisions based on the acquired user mobility information and / or measurement results, which may be, for example, generating and / or predicting Timing Advance (TA), generating handover decisions, generating and / or predicting access beam information, etc. Handover decisions include the selection of a target node and / or target cell, the determination of a handover time, the determination of a handover type, etc. Handover types include L3 handover, L1 / L2 Triggered Mobility (LTM) handover, conditional handover, LTM conditional handover, Dual Active Protocol Stack (DAPS) handover, etc. The generation and / or prediction of TA can be implemented by an artificial intelligence machine learning model. The generation and / or prediction of beam information can be implemented by an artificial intelligence machine learning model. The first node can acquire a TA for a user to access a target cell based on acquired user mobility information and / or measurement results. The first node can transmit the TA to the user to enable the user to access the target cell during the handover process, or the first node can transmit it to other nodes, and the other nodes can transmit it to the user to enable the user to access the target cell during the handover process. This can effectively reduce the signaling overhead required for TA acquisition. The user can directly access the target cell using the TA generated and / or predicted by the first node without performing a random access procedure.To transmit a random access preamble to a target node, the target node transmits the TA value back to the source node, or the user acquires the TA through random access. The TA that can be generated and / or predicted by the source node and / or target node will effectively reduce the signaling overhead required for TA acquisition. User mobility information and / or measurement result information may be measured information or predicted information.

[0209] In some implementations, the third message may include one or more of the following information and / or fields:

[0210] Terminal (UE) ID: Indicates the user corresponding to user mobility information and / or measurement results. This may be a terminal ID or a list of terminal IDs.

[0211] Transmission Node ID: Used to identify the node transmitting the message.

[0212] Receiving Node ID: Used to identify the node receiving the message.

[0213] User Mobility Information: Indicates user mobility information and / or a list of mobility information. User mobility information may include one or more of the following: speed, direction of movement, location information, location coordinates, cell of residence, cell visited, time of stay, time of visit, time information, etc.

[0214] Measurement Result: Indicates the user's measurement result. The measurement result may include RSRP, RSRQ, SINR, target cell identifier, beam identifier, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0215] Event and / or condition that triggered the report: Indicates the event and / or condition that triggered the report.

[0216] Event and / or condition that triggered the measurement: Indicates the event and / or condition that triggered the measurement.

[0217] Applicable / Valid Time Corresponding to Prediction Information: Used to indicate the time and / or time interval corresponding to the prediction content. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0218] Start Time: Used to indicate the start time of an applicable / valid time.

[0219] End Time: Used to indicate the end time of an applicable / valid time.

[0220] Measurement and / or Prediction ID: Used to identify measurements and / or predictions. In some implementations, to associate a report with a request and / or response, this ID may match a measurement and / or prediction ID within a first message and / or a second message.

[0221] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID in the first message and / or second message.

[0222] Example 2

[0223] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a third node transmits a fourth message to a fourth node containing a request to report a TA value, thereby requesting the fourth node to report a TA value. The TA value may be a TA value calculated by a mathematical method and / or a TA value obtained by an artificial intelligence machine learning model. In some embodiments, for example, the third node may transmit the TA value obtained from the fourth node to the terminal when the terminal needs to be handed over, and the terminal may perform direct access using the TA value, thereby preventing interruption due to the handover and effectively reducing the signaling required to obtain the TA.

[0224] In some embodiments, the fourth message may include one or more of the following information and / or fields:

[0225] Transmission Node ID: Used to identify the node transmitting the message.

[0226] Receiving Node ID: Used to identify the node receiving the message.

[0227] Measurement and / or Prediction ID: Used to identify measurements and / or predictions.

[0228] Request ID: Used to identify the request.

[0229] Terminal ID: Indicates the user corresponding to the TA value requested to be reported. This may be a terminal ID or a list of terminal IDs.

[0230] Cell ID: Indicates the cell corresponding to the TA value requested to be reported. This can be a cell ID or a list of cell IDs.

[0231] TA value request identifier for candidate cell: Instructs the message receiving node to request the TA value for the candidate cell.

[0232] Beam ID: Indicates the beam corresponding to the TA value requested to be reported. This can be a beam ID or a list of beam IDs.

[0233] TA value request identifier corresponding to the beam within the candidate cell: Instructs the message receiving node to request the reporting of the TA value corresponding to the beam within the candidate cell.

[0234] Slice ID: Indicates the slice corresponding to the TA value requested to be reported. This can be a slice ID or a list of slice IDs.

[0235] Request identifier for the TA value corresponding to the slice within the candidate cell: Instructs the message receiving node to request the TA value corresponding to the slice within the candidate cell.

[0236] TA Value Request Identifier: Used to indicate that this information is intended to request the reporting of a TA value. This field may be represented by a single bit. For example, if the bit is 1, it indicates that a TA value is requested to be reported; if the bit is 0, it indicates that a TA value is not requested to be reported. Or, if the bit is 0, it indicates that a TA value is requested to be reported; if the bit is 1, it indicates that a TA value is not requested to be reported.

[0237] Registration Request: Used to indicate the type of request. For example, it may include start, end, add, update, modify, cancel, etc.

[0238] Report Registration Request: Used to indicate the type of report request. For example, it may include start, end, add, update, modify, cancel, etc.

[0239] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0240] Events and / or conditions triggering a report: If the events and / or conditions triggering a report are met, a report must be performed.

[0241] Reporting Period: Used to indicate the interval for periodic reporting. The reporting period may also be the estimated time and / or measurement time of the reported information. In one embodiment, for example, if there is no content in this field, a one-time report is indicated, and the reporting time of the one-time report is the measurement time and / or reporting time.

[0242] Reporting Time of Requested Content: Used to indicate the time and / or time interval for which content is requested to be reported. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0243] Start time: Used to indicate the start time of the report time.

[0244] End time: Used to indicate the end time of the report time.

[0245] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0246] Requested content measurement mode: Used to specify the requested content measurement mode. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0247] Events and / or conditions triggering the measurement: If the events and / or conditions triggering the measurement are met, the measurement must be performed.

[0248] Measurement period: Used to indicate the interval of periodic measurements.

[0249] Measurement Time for Requested Content: Used to indicate the time and / or time interval for measuring the requested content. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0250] Start time: Used to indicate the start time of the measurement time.

[0251] End time: Used to indicate the end time of the measurement time.

[0252] Applicable / Valid Time of Requested Content: Used to indicate the valid time and / or time interval of the requested content. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0253] Start Time: Used to indicate the start time of an applicable / valid time.

[0254] End Time: Used to indicate the end time of an applicable / valid time.

[0255] Requested Prediction Time Interval: Used to indicate the time and / or time interval for the prediction. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0256] Prediction start time: Used to indicate the start time of the prediction.

[0257] Prediction end time: Used to indicate the end time of the prediction.

[0258] Applicable / Valid Time for Requested Prediction: Used to indicate the time and / or time interval corresponding to the prediction. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0259] Start Time: Used to indicate the start time of an applicable / valid time.

[0260] End Time: Used to indicate the end time of an applicable / valid time.

[0261] Request Information: Used to indicate request information for reporting TA values. This may include one or more of the following:

[0262] Cell Count: The number of cells corresponding to the TA values ​​requested to be reported.

[0263] Cell ID and / or ID list: Cells corresponding to the requested TA value. For example, the cells corresponding to the TA value requested to be reported must be one or more of the cell ID and / or ID list.

[0264] Node Count: The number of nodes corresponding to the TA value requested to be reported.

[0265] Node ID and / or list of IDs: Nodes corresponding to the requested TA value. For example, the nodes corresponding to the TA value requested to be reported must be one or more of the node ID and / or list of IDs.

[0266] Beam Count: The number of beams corresponding to the TA value requested to be reported. The beams may be SSB beams or other beams.

[0267] Beam ID and / or ID list: Beams corresponding to the requested TA value. For example, beams corresponding to the TA value requested to be reported must be one or more of the beam ID and / or ID list.

[0268] Slice Count: The number of slices corresponding to the TA values ​​requested to be reported.

[0269] Slice ID and / or ID list: Slices corresponding to the requested TA value. For example, slices corresponding to the TA value requested to be reported must be one or more of the slice ID and / or ID list.

[0270] Number of TA values: The number of TA values ​​requested to be reported. This may also be the maximum and / or minimum number of TA values ​​requested to be reported.

[0271] The fourth node may transmit a fifth message containing a response regarding a TA value report to the third node to inform the third node whether the fourth node can measure and / or report and / or predict the TA value, thereby allowing the third node to know whether the requested content to be reported can subsequently be received from the fourth node. In some embodiments, for example, if the fifth message received by the third node indicates that the fourth node can measure and / or report and / or predict the TA value, the third node may subsequently receive the TA value reported by the fourth node, for example, through a subsequent sixth message. In some other embodiments, for example, the third node may transmit a message to the fourth node to stop (and / or cancel) reporting based on the information indicated in the received fifth message, for example, to stop (and / or cancel) reporting through the fourth message.

[0272] In some embodiments, the fifth message may include one or more of the following information and / or fields:

[0273] Transmission Node ID: Used to identify the node transmitting the message.

[0274] Receiving Node ID: Used to identify the node receiving the message.

[0275] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID within the fourth message.

[0276] Request ID: Used to identify the request corresponding to the response. In some implementations, to associate the report with the request and / or response, this ID may match the request ID in the fourth message.

[0277] Acknowledge for TA value request: Used to indicate whether a TA value can be measured and / or reported and / or predicted. The acknowledgment for a TA value request may be a bit indicating whether the request can be measured and / or reported and / or predicted.

[0278] Terminal ID where reporting can be performed: ID(s) of the user(s) where the TA value can be measured and / or reported. This may be an ID or a list of IDs.

[0279] Cell IDs where reporting can be performed: ID(s) of the cell(s) where TA values ​​can be measured and / or reported. This can be an ID or a list of IDs.

[0280] Beam IDs where reporting can be performed: ID(s) of beam(s) where TA values ​​can be measured and / or reported. This may be an ID or a list of IDs.

[0281] Slice IDs where reporting can be performed: ID(s) of slice(s) where TA values ​​can be measured and / or reported. This can be an ID or a list of IDs.

[0282] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0283] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0284] Reportable Time: Indicates the time and / or time interval during which the content can be reported. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it may be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0285] Start time: Used to indicate the start time of the reportable time.

[0286] End time: Used to indicate the end time of the reportable time.

[0287] Available Measurement Modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0288] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0289] Available Measurement Time: Used to indicate the measurement time and / or time interval during which a measurement can be performed. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0290] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0291] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0292] Predictable Time: Used to indicate the time and / or time interval during which a prediction can be performed. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0293] Prediction start time: Used to indicate the start time at which the prediction can be performed.

[0294] Prediction end time: Used to indicate the end time at which the prediction can be performed.

[0295] Applicable / Valid Time for Predictable Correspondence: Used to indicate the applicable / valid time and / or time interval for predictable correspondence. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it may be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0296] Start time: Used to indicate the start time of the valid time available for forecasting.

[0297] End Time: Used to indicate the end time of the valid time available for the forecast.

[0298] Reporting and / or Measuring and / or Predictable Response Information: Used to indicate information corresponding to a reporting and / or measuring and / or predictable TA value. This may include one or more of the following:

[0299] Number of slices: The number of slices corresponding to reported and / or measured and / or predicted TA values.

[0300] Slice ID and / or ID list: A range of slices corresponding to a reported and / or measured and / or predicted TA value. For example, the slices corresponding to a reported and / or measured and / or predicted TA value are one or more of the slice ID and / or ID list.

[0301] Cell count: The number of cells corresponding to TA values ​​that can be reported and / or measured and / or predicted.

[0302] Cell ID and / or ID list: A range of cells corresponding to a reported and / or measured and / or predicted TA value. For example, the cells corresponding to a reported and / or measured and / or predicted TA value are one or more of the cell ID and / or ID list.

[0303] Number of Beams: The number of beams corresponding to the reported and / or measured and / or predicted TA values.

[0304] Beam ID and / or ID list: A range of beams corresponding to reported and / or measured and / or predicted TA values. For example, the beams corresponding to reported and / or measured and / or predicted TA values ​​are one or more of the beam ID and / or ID list.

[0305] Number of nodes: The number of nodes corresponding to the reported and / or measured and / or predicted TA values.

[0306] Node ID and / or ID list: A range of nodes corresponding to a reported and / or measured and / or predicted TA value. For example, the nodes corresponding to a reported and / or measured and / or predicted TA value are one or more of the node ID and / or ID list.

[0307] Number of TA values: The number of TA values ​​that can be reported and / or measured and / or predicted. This may also be the maximum and / or minimum number of TA values ​​that can be reported and / or measured and / or predicted.

[0308] Events and / or conditions that trigger a report that can be performed: Indicates the trigger events and / or conditions that trigger a report that can be performed. If the events and / or conditions that trigger this report are met, the report may be performed.

[0309] Events and / or conditions that trigger a measure that can be performed: Indicates trigger events and / or conditions that trigger a measure that can be performed. If the events and / or conditions that trigger this measure are met, the measurement can be performed.

[0310] Unavailable Report Modes: Used to indicate unavailable reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0311] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0312] Non-reportable Time: Indicates a time and / or time interval during which content cannot be reported. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0313] Start time: Used to indicate the start time of an unreportable time.

[0314] End time: Used to indicate the end time of the time when reporting is not possible.

[0315] Unavailable Measurement Mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0316] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0317] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0318] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0319] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0320] Unpredictable Time: Used to indicate a time and / or time interval where prediction cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0321] Prediction start time: Used to indicate the start time at which a prediction cannot be performed.

[0322] Prediction end time: Used to indicate the end time at which a prediction cannot be performed.

[0323] Applicable / Valid Time for Unpredictable Response Predictions: Used to indicate the applicable / valid time and / or time interval for unpredictable response predictions. Time can be relative or absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0324] Start Time: Used to indicate the start time of a valid time that is unavailable for forecasting.

[0325] End Time: Used to indicate the end time of a valid period that is unavailable for prediction.

[0326] Reporting and / or Measuring and / or Unpredictable Response Information: Used to indicate information corresponding to reporting and / or measuring and / or unpredictable TA values. This may include one or more of the following:

[0327] Number of slices: The number of slices corresponding to reported and / or measured and / or unpredictable TA values.

[0328] Slice ID and / or ID list: A range of slices corresponding to reported and / or measured and / or unpredictable TA values. For example, slices corresponding to reported and / or measured and / or unpredictable TA values ​​are one or more of the slice ID and / or ID list.

[0329] Cell count: The number of cells corresponding to TA values ​​that cannot be reported and / or measured and / or predicted.

[0330] Cell ID and / or ID list: A range of cells corresponding to reported and / or measured and / or unpredictable TA values. For example, the cells corresponding to reported and / or measured and / or unpredictable TA values ​​are one or more of the cell ID and / or ID list.

[0331] Number of beams: The number of beams corresponding to reported and / or measured and / or unpredictable TA values.

[0332] Beam ID and / or ID list: A range of beams corresponding to reported and / or measured and / or unpredictable TA values. For example, beams corresponding to reported and / or measured and / or unpredictable TA values ​​are one or more of the beam ID and / or ID list.

[0333] Number of nodes: The number of nodes corresponding to reported and / or measured and / or unpredictable TA values.

[0334] Node ID and / or ID list: A range of nodes corresponding to reported and / or measured and / or unpredictable TA values. For example, nodes corresponding to reported and / or measured and / or unpredictable TA values ​​are one or more of the node ID and / or ID list.

[0335] Number of TA values: The number of TA values ​​that cannot be reported and / or measured and / or predicted. This may also be the maximum and / or minimum number of TA values ​​that cannot be reported and / or measured and / or predicted.

[0336] Events and / or conditions that trigger an unexecutable report: Indicates trigger events and / or conditions that trigger a report that cannot be executed. If the events and / or conditions triggering this report are met, the report cannot be executed.

[0337] Events and / or conditions that trigger an unpermissible measurement: Indicates trigger events and / or conditions that trigger a measurement that cannot be performed. If the events and / or conditions triggering this measurement are met, the measurement cannot be performed.

[0338] Cause / reason: Indicates the reason why measurement and / or reporting and / or prediction cannot be performed.

[0339] The fourth node reports to the third node a sixth message containing a TA value obtained and / or generated by the fourth node, in accordance with its own situation and / or a fourth message containing a request to report a TA value received from the third node. In some embodiments, for example, the third node may transmit the TA value obtained from the fourth node to the terminal when the terminal needs to be handed over, and the terminal may prevent interruption due to the handover and effectively reduce the signaling required to obtain the TA by performing direct access using the TA value. The generation and / or prediction of the TA may be implemented by an artificial intelligence machine learning model. The user may directly access the target cell using the generated and / or predicted TA obtained by the third node and / or the fourth node without performing a random access procedure. For the user to transmit a random access preamble to the target node, the target node transmits the TA value back to the source node, or the user obtains the TA through random access. TAs that can be generated and / or predicted by source nodes and / or target nodes will effectively reduce the signaling overhead required for TA acquisition.

[0340] In some implementations, the sixth message may include one or more of the following information and / or fields:

[0341] Transmission Node ID: Used to identify the node transmitting the message.

[0342] Receiving Node ID: Used to identify the node receiving the message.

[0343] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID in the fourth message and / or fifth message.

[0344] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID in the fourth message and / or fifth message.

[0345] Terminal ID: Indicates the user corresponding to the reported TA value. This may be a terminal ID or a list of terminal IDs.

[0346] Cell ID: Indicates the cell corresponding to the reported TA value. This can be a cell ID or a list of cell IDs.

[0347] Beam ID: Indicates the beam corresponding to the reported TA value. This may be a beam ID or a list of beam IDs.

[0348] Slice ID: Indicates the slice corresponding to the reported TA value. This can be a slice ID or a list of slice IDs.

[0349] TA value: Indicates the reported TA value.

[0350] Applicable / Valid Time Corresponding to the TA Value: Used to indicate the valid time and / or time interval corresponding to the TA value. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0351] Start Time: Used to indicate the start time of an applicable / valid time.

[0352] End Time: Used to indicate the end time of an applicable / valid time.

[0353] Event and / or condition that triggered this report: Indicates the event and / or condition that triggered this report.

[0354] Event and / or condition that triggered this measurement: Indicates the event and / or condition that triggered this measurement.

[0355] Applicable / Valid Time Corresponding to Predicted TA Value: Used to indicate a valid time and / or time interval corresponding to the predicted TA value. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0356] Start Time: Used to indicate the start time of an applicable / valid time.

[0357] End Time: Used to indicate the end time of an applicable / valid time.

[0358] If the receiving node of the sixth message is a terminal, the terminal may access the target cell based on the TA value within a valid time corresponding to the (predicted) TA value. If the terminal discovers that the acquired TA value and / or the valid time is inapplicable when accessing the target node, the terminal acquires a TA for accessing the target cell through random access. In one embodiment, the method may be applied to a conditional handover, wherein the node may transmit the (predicted) TA value (or a list of TA values) and / or the corresponding valid time (or a list of valid times) to the terminal. When an execution condition and / or event for a conditional handover corresponding to the target cell is satisfied, the terminal may access the target cell based on the TA value corresponding to the target cell, or access the target cell based on the TA value corresponding to the target cell within a valid time corresponding to the (predicted) TA value.

[0359] Example 3

[0360] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a fifth node sending a seventh message to a sixth node, which includes a request to report the TA value actually used, thereby requesting the sixth node to report the TA value actually used. In some embodiments, for example, the fifth node may evaluate whether the generated and / or predicted TA value is appropriate using the TA value actually used. For example, if the TA value actually used does not match the generated and / or predicted TA value and / or the difference between the TA value actually used and the generated and / or predicted TA value is greater than and / or equal to a predetermined threshold, this implies that the generated and / or predicted TA value is inappropriate. Or, if the TA value actually used matches the generated and / or predicted TA value and / or the difference between the TA value actually used and the generated and / or predicted TA value is less than and / or equal to a predetermined threshold, this implies that the generated and / or predicted TA value is appropriate. In another embodiment, for example, the fifth node may use the TA value actually used to support artificial intelligence machine learning functions, for example, as an input parameter to train an artificial intelligence machine learning model, such as a model for generating and / or predicting TA values ​​or a model for generating handover decisions. Alternatively, the TA value actually used may be used to evaluate the artificial intelligence machine learning model, for example, to evaluate whether the model can be continued to be used, whether the model needs to be trained and / or adjusted, etc.

[0361] In some implementations, the seventh message may include one or more of the following information and / or fields:

[0362] Transmission Node ID: Used to identify the node transmitting the message.

[0363] Receiving Node ID: Used to identify the node receiving the message.

[0364] Measurement ID: Used to identify the measurement.

[0365] Request ID: Used to identify the request.

[0366] Terminal ID: Indicates the user corresponding to the TA value actually used that is requested to be reported. This may be a terminal ID or a list of terminal IDs.

[0367] Cell ID: Indicates the cell corresponding to the TA value actually used that is requested to be reported. This can be a cell ID or a list of cell IDs.

[0368] Beam ID: Indicates the beam corresponding to the TA value actually used that is requested to be reported. This can be a beam ID or a list of beam IDs.

[0369] Slice ID: Indicates the slice corresponding to the TA value actually used that is requested to be reported. This can be a slice ID or a list of slice IDs.

[0370] Identifier for request to report the TA value actually used: Instructs the message receiving node to request the TA value actually used to be reported.

[0371] Identifier for the request for the TA value actually used: Indicates that the message is intended to request a report of the TA value actually used. This field can be represented by a single bit. For example, if the bit is 1, it indicates that a request is made to report the TA value actually used, and if the bit is 0, it indicates that a request is not made to report the TA value actually used. Or, if the bit is 0, it indicates that a request is made to report the TA value actually used, and if the bit is 1, it indicates that a request is not made to report the TA value actually used.

[0372] Identifier for request to report whether access is performed based on the TA value in the LTM cell switching command: Used to indicate that the message is intended to request a report on whether access is performed based on the TA value in the LTM cell switching command. This field may be represented by a single bit. For example, if the bit is 1, it indicates that a request is made to report whether access is performed based on the TA value in the LTM cell switching command; if the bit is 0, it indicates that a request is not made to report whether access is performed based on the TA value in the LTM cell switching command. Or, if the bit is 0, it indicates that a request is made to report whether access is performed based on the TA value in the LTM cell switching command; if the bit is 1, it indicates that a request is not made to report whether access is performed based on the TA value in the LTM cell switching command.

[0373] Instruction to request a report on whether the TA value actually used matches the TA value received: The message is used to indicate that it is to request a report on whether the TA value actually used matches the TA value received.

[0374] Registration Request: Used to indicate the type of request. For example, this may include start, end, add, update, modify, cancel, etc.

[0375] Report Registration Request: Used to indicate the type of report request. For example, it may include start, end, add, update, modify, cancel, etc.

[0376] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0377] Events and / or conditions triggering a report: If the events and / or conditions triggering a report are met, a report must be performed. The events and / or conditions triggering a report include one or more of the following:

[0378] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0379] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be executed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0380] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0381] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0382] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0383] Reporting Period: Used to indicate the interval of reporting. This may also be the time interval between two adjacent reports. This time interval may be a maximum time interval or a minimum time interval. The reporting period may also be the predicted time and / or measurement time of the reported information. In one embodiment, for example, if there is no content in this field, a one-time report is indicated, and the reporting time of the one-time report is the measurement time and / or reporting time. In some embodiments, the reporting period is used to indicate the time interval of periodic reporting.

[0384] Reporting Time of Requested Content: Used to indicate the time and / or time interval for which content is requested to be reported. Time can be relative or absolute. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0385] Start time: Used to indicate the start time of the report time.

[0386] End time: Used to indicate the end time of the report time.

[0387] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0388] Requested content measurement mode: Used to specify the requested content measurement mode. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0389] Events and / or conditions triggering a measurement: If the events and / or conditions triggering a measurement are met, a measurement must be performed. The events and / or conditions triggering a measurement include one or more of the following:

[0390] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0391] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0392] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0393] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0394] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0395] Measurement Period: Used to indicate the interval for measurement. This may also be the time interval between two adjacent measurements. This time interval may be a maximum time interval or a minimum time interval. The measurement period may also be the measurement time of the measurement information. In one embodiment, for example, if there is no content in this field, a one-time measurement is indicated, and the time of the one-time measurement is the measurement time and / or reporting time. In some embodiments, the measurement period is used to indicate the time interval of periodic measurements.

[0396] Measurement time for the requested content: Used to indicate the time and / or time interval for measuring the requested content. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers the measurement in Message 7, or an event and / or condition that triggers the report. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0397] Start time: Used to indicate the start time of the measurement time.

[0398] End time: Used to indicate the end time of the measurement time.

[0399] Applicable / Valid Time of Requested Content: Used to indicate the valid time and / or time interval of the requested content. Time can be relative or absolute time. Time can also be a time or period prior to or after an event. The event can be an event and / or condition that triggers a measurement in Message 7, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0400] Start Time: Used to indicate the start time of an applicable / valid time.

[0401] End Time: Used to indicate the end time of an applicable / valid time.

[0402] Request Information: Used to indicate request information for reporting the TA values ​​actually used. This may include one or more of the following:

[0403] Cell count: The number of cells corresponding to the actually measured TA values ​​requested to be reported.

[0404] Cell ID and / or ID list: Cells corresponding to the requested actually measured TA values. For example, the cells corresponding to the actually measured TA values ​​requested to be reported must be one or more of the cell ID and / or ID list.

[0405] Node Count: The number of nodes corresponding to the actually measured TA values ​​requested to be reported.

[0406] Node ID and / or list of IDs: Nodes corresponding to the requested actually measured TA values. For example, the nodes corresponding to the actually measured TA values ​​requested to be reported must be one or more of the node ID and / or list of IDs.

[0407] Beam count: The number of beams corresponding to the actually measured TA values ​​requested to be reported. The beams may be SSB beams or other beams.

[0408] Beam ID and / or ID list: The beam corresponding to the requested actually measured TA value. For example, the beams corresponding to the actually measured TA value requested to be reported must be one or more of the beam ID and / or ID list. The beam may be an SSB beam or other beams.

[0409] Number of slices: The number of slices corresponding to the actually measured TA values ​​requested to be reported.

[0410] Slice ID and / or list of IDs: Slices corresponding to the requested actually measured TA values. For example, slices corresponding to the actually measured TA values ​​requested to be reported must be one or more of the slice ID and / or list of IDs.

[0411] Number of TA values: The number of actually measured TA values ​​requested to be reported, or the maximum and / or minimum number of actually measured TA values ​​requested to be reported.

[0412] The sixth node transmits an eighth message to the fifth node containing a report response of the actually measured TA value, thereby informing the fifth node whether the sixth node can report the actually measured TA value, and accordingly, the fifth node can determine whether the requested content to be reported can subsequently be received from the sixth node. In some embodiments, for example, if the eighth message received by the fifth node indicates that the sixth node can report the actually measured TA value, the fifth node may subsequently receive the actually measured TA value reported by the sixth node, for example, through a subsequent ninth message. In some other embodiments, for example, the fifth node may transmit a message to the sixth node to stop (and / or cancel) reporting based on the information indicated in the received eighth message, for example, to stop (and / or cancel) reporting through the seventh message.

[0413] In some implementations, the eighth message may include one or more of the following information and / or fields:

[0414] Transmission Node ID: Used to identify the node transmitting the message.

[0415] Receiving Node ID: Used to identify the node receiving the message.

[0416] Measurement ID: Used to identify a measurement. In some implementations, to associate a report with a request and / or response, this ID may match the measurement ID in the seventh message.

[0417] Request ID: Used to identify the request corresponding to the response. In some implementations, to associate the report with the request and / or response, this ID may match the request ID in the seventh message.

[0418] Acknowledgment for the actually measured TA value: Used to indicate whether the TA value can be measured and / or reported. The acknowledgment for the actually measured TA value may be a bit indicating whether the request can be measured and / or reported.

[0419] Terminal ID where reporting can be performed: ID(s) of the user(s) to whom the actually measured TA value can be measured and / or reported. This may be an ID or a list of IDs.

[0420] Cell ID where reporting can be performed: The ID(s) of the cell(s) where the actually measured TA value can be measured and / or reported. This can be an ID or a list of IDs.

[0421] Beam IDs where reporting can be performed: ID(s) of the beam(s) where the actually measured TA values ​​can be measured and / or reported. This may be an ID or a list of IDs.

[0422] Slice IDs where reporting can be performed: ID(s) of slice(s) where the actually measured TA values ​​can be measured and / or reported. This can be an ID or a list of IDs.

[0423] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0424] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0425] Time available for reporting: Indicates the time and / or time interval during which the content can be reported. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 7, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0426] Start Time: Used to indicate the start time of the time available for reporting.

[0427] End Time: Used to indicate the end time of the time available for reporting.

[0428] Available Measurement Modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0429] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0430] Available Measurement Time: Used to indicate the measurement time and / or time interval during which a measurement may be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 7, or an event and / or condition that triggers a report. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0431] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0432] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0433] Corresponding information that can be reported and / or measured: Used to indicate information corresponding to an actually measured TA value that can be reported and / or measured. This may include one or more of the following:

[0434] Number of slices: The number of slices corresponding to the actually measured TA values ​​that can be reported and / or measured.

[0435] Slice ID and / or ID list: A range of slices corresponding to the actually measured TA values ​​that can be reported and / or measured. For example, the slices corresponding to the actually measured TA values ​​that can be reported and / or measured are one or more of the slice ID and / or ID list.

[0436] Cell count: The number of cells corresponding to the actually measured TA values ​​that can be reported and / or measured.

[0437] Cell ID and / or ID list: A range of cells corresponding to the actually measured TA values ​​that can be reported and / or measured. For example, the cells corresponding to the actually measured TA values ​​that can be reported and / or measured are one or more of the cell ID and / or ID list.

[0438] Beam count: The number of beams corresponding to the actually measured TA values ​​that can be reported and / or measured.

[0439] Beam ID and / or ID list: A range of beams corresponding to the actually measured TA values ​​that can be reported and / or measured. For example, the beams corresponding to the actually measured TA values ​​that can be reported and / or measured are one or more of the beam ID and / or ID list.

[0440] Number of nodes: The number of nodes corresponding to the actually measured TA values ​​that can be reported and / or measured.

[0441] Node ID and / or ID list: A range of nodes corresponding to the actually measured TA values ​​that can be reported and / or measured. For example, the nodes corresponding to the actually measured TA values ​​that can be reported and / or measured are one or more of the node ID and / or ID list.

[0442] Number of TA values: The number of actually measured TA values ​​that can be reported and / or measured, or the maximum and / or minimum number of actually measured TA values ​​that can be reported and / or measured.

[0443] Trigger events and / or conditions corresponding to report and / or measurement that can be performed: Indicate trigger events and / or conditions corresponding to report and / or measurement that can be performed. If the event and / or condition triggering this report and / or measurement is satisfied, the report and / or measurement may be performed. The event and / or condition triggering the report includes one or more of the following:

[0444] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0445] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0446] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0447] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0448] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0449] Unavailable Report Modes: Used to indicate unavailable reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0450] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0451] Time Unavailable for Reporting: Indicates a time and / or time interval during which the content cannot be reported. Time may be relative or absolute. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 7, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0452] Start time: Used to indicate the start time of an unreportable time.

[0453] End time: Used to indicate the end time of the time when reporting is not possible.

[0454] Unavailable Measurement Mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0455] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0456] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 7, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0457] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0458] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0459] Corresponding information that cannot be reported and / or measured: Used to indicate information corresponding to an actually measured TA value that cannot be reported and / or measured. This may include one or more of the following:

[0460] Number of slices: The number of slices corresponding to the actually measured TA values ​​that cannot be reported and / or measured.

[0461] Slice ID and / or ID list: A range of slices corresponding to the actually measured TA values ​​that cannot be reported and / or measured. For example, the slices corresponding to the actually measured TA values ​​that cannot be reported and / or measured are one or more of the slice ID and / or ID list.

[0462] Cell count: The number of cells corresponding to actually measured TA values ​​that cannot be reported and / or measured.

[0463] Cell ID and / or ID list: A range of cells corresponding to the actually measured TA values ​​that cannot be reported and / or measured. For example, the cells corresponding to the actually measured TA values ​​that cannot be reported and / or measured are one or more of the cell ID and / or ID list.

[0464] Beam count: The number of beams corresponding to the actually measured TA values ​​that cannot be reported and / or measured.

[0465] Beam ID and / or ID list: A range of beams corresponding to the actually measured TA values ​​that cannot be reported and / or measured. For example, the beams corresponding to the actually measured TA values ​​that cannot be reported and / or measured are one or more of the beam ID and / or ID list.

[0466] Number of nodes: The number of nodes corresponding to the actually measured TA values ​​that cannot be reported and / or measured.

[0467] Node ID and / or ID list: A range of nodes corresponding to the reported and / or actually measured TA values ​​that cannot be reported and / or measured. For example, the nodes corresponding to the reported and / or actually measured TA values ​​that cannot be reported are one or more of the node ID and / or ID list.

[0468] Number of TA values: The number of actually measured TA values ​​that cannot be reported and / or measured, or the maximum and / or minimum number of actually measured TA values ​​that cannot be reported and / or measured.

[0469] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering this report and / or measurement are satisfied, the report and / or measurement cannot be performed. The events and / or conditions triggering the report include one or more of the following:

[0470] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0471] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0472] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0473] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0474] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0475] Cause / reason: Indicates the reason why measurement and / or reporting cannot be performed.

[0476] The 6th node reports to the 5th node a 9th message containing the TA value actually used obtained by the 6th node, in accordance with a 7th message received from the 5th node, including a request to report the TA value actually used according to its situation and / or. In some embodiments, for example, the 5th node may evaluate whether the generated TA value is appropriate using the TA value actually used. For example, if the TA value actually used does not match the generated TA value and / or the difference between the TA value actually used and the generated TA value is greater than and / or equal to a predetermined threshold, this means the generated TA value is inappropriate. If the TA value actually used matches the generated TA value and / or the difference between the TA value actually used and the generated TA value is less than and / or equal to a predetermined threshold, this means the generated TA value is appropriate. In other embodiments, for example, the 5th node may use the TA value actually used to support artificial intelligence machine learning functions, for example, it may be used as an input parameter to train an artificial intelligence machine learning model, such as a model for generating TA values ​​or a model for generating handover decisions. Alternatively, the TA value actually used can also be used to evaluate the artificial intelligence machine learning model, for example, to evaluate whether the model can be continued to be used, whether the model needs to be trained and / or adjusted, etc.

[0477] In some implementations, the ninth message may include one or more of the following information and / or fields:

[0478] Transmission Node ID: Used to identify the node transmitting the message.

[0479] Receiving Node ID: Used to identify the node receiving the message.

[0480] Measurement ID: Used to identify a measurement. In some implementations, to associate a report with a request and / or response, this ID may match a measurement ID in the seventh message and / or the eighth message.

[0481] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID in the seventh message and / or the eighth message.

[0482] Terminal ID: Indicates the user corresponding to the reported TA value actually used. This may be a terminal ID or a list of terminal IDs.

[0483] Cell ID: Indicates the cell corresponding to the reported TA value actually used. This can be a cell ID or a list of cell IDs.

[0484] Beam ID: Indicates the beam corresponding to the reported TA value actually used. This can be a beam ID or a list of beam IDs.

[0485] Slice ID: Indicates the slice corresponding to the reported TA value actually used. This can be a slice ID or a list of slice IDs.

[0486] TA value: Indicates the reported TA value actually used.

[0487] Applicable / Valid Time Corresponding to the TA Value Actually Used: Used to indicate the valid time and / or time interval corresponding to the TA value actually used. Time can be relative or absolute time. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0488] Start Time: Used to indicate the start time of an applicable / valid time.

[0489] End Time: Used to indicate the end time of an applicable / valid time.

[0490] Events and / or conditions that triggered this report: Indicates the events and / or conditions that triggered this report. The events and / or conditions that triggered this report include one or more of the following:

[0491] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0492] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0493] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0494] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0495] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0496] Event and / or condition that triggered this measurement: Indicates the event and / or condition that triggered this measurement. The event and / or condition that triggered this measurement includes one or more of the following:

[0497] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0498] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0499] The TA value actually used at access does not match the TA value within the LTM cell switching command, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the LTM cell switching command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0500] The TA value actually used at access does not match the TA value within the handover command, and / or the difference between the TA value actually used at access and the TA value within the handover command is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the TA value within the handover command is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0501] The TA value actually used at access does not match the received TA value, and / or the difference between the TA value actually used at access and the received TA value is greater than, and / or equal to, and / or less than a predetermined threshold, and / or the difference between the TA value actually used at access and the received TA value is within a predetermined range. The event and / or condition triggering the report must include one or more of the following settings: event type, event, predetermined threshold, and predetermined range.

[0502] Indication of whether the target cell is accessible based on the TA value in the LTM cell switching command: Used to indicate whether the target cell is accessible based on the TA value in the LTM cell switching command. This field can be represented by a single bit. For example, if the bit is 1, it indicates access based on the TA value in the LTM cell switching command; if the bit is 0, it indicates that access is not accessed based on the TA value in the LTM cell switching command. Or, if the bit is 0, it indicates access based on the TA value in the LTM cell switching command; if the bit is 1, it indicates that access is not accessed based on the TA value in the LTM cell switching command.

[0503] Indicator for whether the TA value actually used matches the TA value received: Used to indicate whether the TA value actually used matches the TA value received. If the receiving node of the message discovers that the TA value used as the basis for the actual access does not match the TA value received, the receiving node of the message reports this information.

[0504] The TA value actually used is the TA value used when the terminal accesses the cell and / or target cell.

[0505] Example 2 can be combined with Example 3. For example, the source node may transmit a first TA value to the target node via the sixth message. The first TA value may be a generated and / or predicted TA value, or a TA value within an LTM cell switching command and / or handover command. When a user accesses the target cell, the target node obtains the TA actually used from the terminal side using the methods of Example 3, and the target node compares the TA actually used value with the received first TA value. If the TA actually used value does not match the received first TA value, the target node may notify the source node of the discrepancy between the TA actually used value and the received first TA value via the ninth message of Example 3.

[0506] Example 4

[0507] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a seventh node transmits a tenth message to an eighth node containing a request for a neighboring cell load condition, thereby requesting the eighth node to report the neighboring cell load condition (or neighboring cell load information). The neighboring cell load condition may include a measured neighboring cell load condition or a predicted neighboring cell load condition. After obtaining the neighboring cell load condition, the seventh node may make relevant decisions, e.g., decisions related to a Self-Optimization Network (SON) and / or mobility decisions, based on the load condition of the neighboring cell, thereby preventing frequent handovers, local overloads, overloads, and degradation of service performance. Herein, the mobility decision may include a handover decision, e.g., an LTM handover decision. The source node can select an appropriate target cell for handover based on the load status of candidate cells, thereby preventing frequent handovers and service performance degradation caused by the terminal having to be handed over again due to the high load of adjacent cells and the possibility of local overload occurring after the terminal is handed over to the adjacent cell.

[0508] In some embodiments, the 10th message may include one or more of the following information and / or fields:

[0509] Transmission Node ID: Used to identify the node transmitting the message.

[0510] Receiving Node ID: Used to identify the node receiving the message.

[0511] Measurement and / or Prediction ID: Used to identify measurements and / or predictions.

[0512] Request ID: Used to identify the request.

[0513] Registration Request: Used to identify the type of request. This may include start, end, add, update, modify, cancel, etc.

[0514] Request Identifier for Adjacent Cell Load Status: Used to indicate request information regarding the adjacent cell load status. This request may be for the measured adjacent cell load status or the predicted adjacent cell load status.

[0515] Cell ID corresponding to adjacent cell load status: Used to indicate which adjacent cells' load status is being requested. This can be a cell ID or a list of cell IDs.

[0516] Request identifier for the load status of the handover candidate cell: Used to indicate a request for the load status of the handover candidate cell. Here, the handover candidate cell may be a candidate cell for any type of handover. Any type of handover may include one or more of the following: handover, conditional handover, Dual Active Protocol Stack (DAPS) handover, LTM handover, etc.

[0517] Handover Candidate Cell ID: Used to indicate which handover candidate cells' load status is being requested. This can be a cell ID or a list of cell IDs.

[0518] Requested range to be reported: Used to indicate the requested range to be reported.

[0519] Reporting period for requested adjacent cell load status: Used to indicate the reporting interval for the requested adjacent cell load status, or it may be the time interval between two adjacent reports. The time interval may also be a maximum time interval or a minimum time interval. The reporting period may also be the reporting time of the reported data. In some implementations, for example, if this field is empty, a one-time report is indicated, and the reporting time of the one-time report is from the report start time to the report end time. In some implementations, the reporting period indicates the time interval for periodic reporting.

[0520] Reporting mode for requested adjacent cell load status: Used to specify the reporting mode for the requested adjacent cell load status. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0521] Adjacent Cell Load Status Reporting Time: Used to indicate the time and / or time interval at which the adjacent cell load status is reported. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0522] Start time: Used to indicate the start time of the report time.

[0523] End time: Used to indicate the end time of the report time.

[0524] Prediction ID: Used to identify prediction requests.

[0525] Identifier for prediction request for adjacent cell load status: Used to direct a request for prediction information on adjacent cell load.

[0526] Cell ID corresponding to the request for prediction of adjacent cell load status: Used to indicate which adjacent cells' predicted load status is being requested.

[0527] Predicted request identifier for the load state of a handover candidate cell: Used to indicate a request for the predicted load state of a handover candidate cell. Here, the handover candidate cell may be a candidate cell for any type of handover. Any type of handover may include one or more of the following: handover, conditional handover, DAPS handover, LTM handover.

[0528] Handover candidate cell ID corresponding to the request for the predicted load state of the handover candidate cell: Used to indicate which handover candidate cells' predicted load state is being requested. This can be a cell ID or a list of cell IDs.

[0529] Requested range to be predicted: Used to indicate the requested range to be predicted.

[0530] Reporting period of adjacent cell load status requested to be predicted: Used to indicate the reporting interval of adjacent cell load status requested to be predicted, or may be the time interval between two adjacent reports. The time interval may be a minimum time interval or a maximum time interval. In some implementations, the reporting period may also be the predicted time of the reported data. If this field is empty, a one-time report is indicated, and the reporting time of the one-time report is from the prediction start time to the prediction end time. In some implementations, the time interval may be the time interval for periodic reporting.

[0531] Reporting mode for requested adjacent cell load status to be predicted: Used to specify the reporting mode for the requested predicted adjacent cell load status. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0532] Reporting Time for Predicted Adjacent Cell Load Status: Used to indicate the time and / or time interval for reporting the predicted adjacent cell load status. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0533] Start time: Used to indicate the start time of the report time.

[0534] End time: Used to indicate the end time of the report time.

[0535] Predicted time of predicted adjacent cell load state: Used to indicate the predicted time and / or time interval corresponding to the predicted adjacent cell load state. The time can be relative or absolute. The time interval can be represented by a timer, a combination of start and end times, a combination of start and duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0536] Start time: Used to indicate the start time of the predicted time.

[0537] End time: Used to indicate the end time of the predicted time.

[0538] Effective / valid time of predicted adjacent cell load state: Used to indicate the effective time and / or time interval corresponding to the predicted adjacent cell load state. The time can be relative or absolute. The time interval can be represented by a timer, a combination of start and end times, a combination of start and duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0539] Start time: Used to indicate the start time of the valid time.

[0540] End time: Used to indicate the end time of the valid time.

[0541] Trigger conditions and / or events for reporting adjacent cell load status: This means that adjacent cell load information (or information related to adjacent cell load status) needs to be reported when trigger events and / or conditions for reporting are met. The adjacent cell load information may include currently measured adjacent cell load information or may also include predicted adjacent cell load information. Events and / or conditions that trigger reporting include one or more of the following:

[0542] The adjacent cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0543] The adjacent cell load is predicted to be greater than and / or equal to and / or less than a predetermined threshold. The events and / or conditions triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0544] Overload will occur. Events and / or conditions that trigger reporting may include one or more of the following settings: event type, event, etc.

[0545] Overload is predicted to occur. Events and / or conditions triggering reporting may include one or more of the following settings: event type, event, etc.

[0546] Adjacent cell load status requested to be reported: Used to specify the specific parameters of the adjacent cell load status requested to be reported.

[0547] In some embodiments, the eighth node may transmit a first message containing a response regarding the adjacent cell load status to the seventh node to inform the seventh node whether the eighth node can report the adjacent cell load status, thereby allowing the seventh node to know whether the requested content can be received later. In some embodiments, for example, if the first message received by the seventh node indicates that the eighth node can report the adjacent cell load status, the seventh node may subsequently receive the adjacent cell load status reported by the eighth node, for example, by receiving a subsequent first message. In some other embodiments, for example, the seventh node may transmit a message to the eighth node to stop (and / or cancel) reporting based on the information indicated in the received first message, for example, to stop (and / or cancel) reporting via the first message.

[0548] In some embodiments, the 11th message may include one or more of the following information and / or fields:

[0549] Transmission Node ID: Used to identify the node transmitting the message.

[0550] Receiving Node ID: Used to identify the node receiving the message.

[0551] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, for example, to associate a response message with a request message, the measurement and / or prediction ID may match the measurement and / or prediction ID of the 10th message.

[0552] Request ID: Used to identify the request corresponding to the response. In some implementations, for example, to associate the response message with the request message, the request ID may match the request ID of the 10th message.

[0553] Acknowledge for Adjacent Cell Load Status Request: Used to indicate whether the adjacent cell load status can be measured and / or reported. The acknowledgment for the adjacent cell load status may be a bit indicating whether measurement and / or reporting can be performed.

[0554] Acknowledgment for predicted adjacent cell load status: Used to indicate whether the adjacent cell load status can be predicted and / or reported. The acknowledgment for the adjacent cell load status may be a bit indicating whether measurement and / or reporting can be performed.

[0555] Acknowledgment of the load status of the handover candidate cell: Used to indicate whether the load status of the handover candidate cell can be predicted and / or reported. Here, the handover candidate cell may be a candidate cell for any type of handover. Any type of handover may include one or more of the following: handover, conditional handover, DAPS handover, LTM handover, etc. The acknowledgment of the load status of the handover candidate cell may be a bit indicating whether measurement and / or reporting can be performed.

[0556] Handover candidate cell ID corresponding to a load state that can be measured and / or reported: Used to indicate a candidate cell ID corresponding to a load state that can be measured and / or reported. This may be a cell ID or a list of cell IDs.

[0557] Range of measurement and / or reporting: Used to indicate the range of measurement and / or prediction and / or reporting.

[0558] Adjacent cell load status that can be measured and / or reported: Used to indicate specific parameters of the adjacent cell load status that can be measured and / or reported.

[0559] Trigger events and / or conditions corresponding to reports and / or measurements that may be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that may be performed. If the events and / or conditions triggering the reports and / or measurements are satisfied, the reports and / or measurements may be performed. The events and / or conditions triggering the reports include one or more of the following:

[0560] The adjacent cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0561] The adjacent cell load is predicted to be greater than and / or equal to and / or less than a predetermined threshold. The events and / or conditions triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0562] Overload will occur. Events and / or conditions that trigger reporting may include one or more of the following settings: event type, event, etc.

[0563] Overload is predicted to occur. Events and / or conditions triggering reporting may include one or more of the following settings: event type, event, etc.

[0564] Handover candidate cell ID corresponding to a load condition that cannot be measured and / or reported: Used to indicate a candidate cell ID corresponding to a load condition that cannot be measured and / or reported. This may be a cell ID or a list of cell IDs.

[0565] Range that cannot be measured and / or reported: Used to indicate a range that cannot be measured and / or predicted and / or reported.

[0566] Adjacent cell load status that cannot be measured and / or reported: Used to indicate specific parameters of adjacent cell load status that cannot be measured and / or reported.

[0567] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering the reports and / or measurements are satisfied, the reports and / or measurements cannot be performed. The events and / or conditions triggering the reports include one or more of the following:

[0568] The adjacent cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0569] The adjacent cell load is predicted to be greater than and / or equal to and / or less than a predetermined threshold. The events and / or conditions triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0570] Overload will occur. Events and / or conditions that trigger reporting may include one or more of the following settings: event type, event, etc.

[0571] Overload is predicted to occur. Events and / or conditions triggering reporting may include one or more of the following settings: event type, event, etc.

[0572] Cause / Reason: Indicates the reason why measurement and / or reporting cannot be performed. The reason may include one or more of the following: adjacent cell unavailable, measurement unavailable, adjacent cell load measurement unavailable, adjacent cell temporarily unavailable, measurement temporarily unavailable, adjacent cell measurement temporarily unavailable, reporting time unavailable, reporting cycle unavailable, adjacent cell corresponding to the forecast unavailable, forecast unavailable, forecast of adjacent cell load status unavailable, forecast temporarily unavailable, adjacent cell forecast temporarily unavailable, forecast time unavailable, forecast reporting time unavailable, forecast information validity time unavailable, forecast information reporting cycle unavailable, adjacent cell not supported, measurement not supported, adjacent cell temporarily not supported, measurement temporarily not supported, adjacent cell measurement temporarily not supported, reporting time not supported, reporting cycle not supported, adjacent cell corresponding to the forecast not supported, forecast not supported, forecast temporarily not supported, adjacent cell forecast temporarily not supported, forecast time not supported, forecast reporting time not supported, forecast information validity time not supported Not available, forecast information reporting cycle not supported, etc.

[0573] In some embodiments, the eighth node transmits a 12th message containing an adjacent cell load state or an update of the adjacent cell load state to the seventh node to notify the seventh node of the adjacent cell load state measured (or obtained) by the eighth node, in accordance with its own circumstances and / or in accordance with a 10th message containing an adjacent cell load state request received from the seventh node. In some embodiments, after the eighth node receives a 10th message containing an adjacent cell load state request from the seventh node, and after the eighth node reports to the seventh node via a 11th message that it can perform some and / or all of the requested adjacent cell load state, the eighth node transmits the adjacent cell load state to the seventh node in accordance with the 10th message containing the adjacent cell load state request. After obtaining the adjacent cell load state, the seventh node may make relevant decisions, e.g., SON-related decisions, based on the adjacent cell load state, thereby preventing frequent handovers, local overloads, overloads, and service performance degradation. The seventh node can also evaluate decisions made based on adjacent cell load conditions. In some implementations, for example, if a local overload occurs after a decision, this indicates that the decision was inappropriate.

[0574] In some embodiments, the 12th message may include one or more of the following information and / or fields:

[0575] Transmission Node ID: Used to identify the node transmitting the message.

[0576] Receiving Node ID: Used to identify the node receiving the message.

[0577] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID in the 10th message and / or the 11th message.

[0578] Request ID: Used to identify the request. In some implementations, to associate a report with a request and / or response, this ID may match the request ID in the 10th message and / or the 11th message.

[0579] Measured adjacent cell load status: Used to indicate the measured adjacent cell load status.

[0580] Applicable / Valid Time of Measured Adjacent Cell Load State: Used to indicate the time and / or time interval corresponding to the measured adjacent cell load state. The time can be relative or absolute. The time interval can be represented by a timer, a combination of start and end times, a combination of start and duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0581] Start Time: Used to indicate the start time of the applicable / valid time.

[0582] End Time: Used to indicate the end time of the applicable / valid time.

[0583] Predicted adjacent cell load status: Used to indicate the predicted adjacent cell load status.

[0584] Applicable / Valid Time of Predicted Adjacent Cell Load State: Used to indicate the time and / or time interval corresponding to the predicted adjacent cell load state. The time can be relative or absolute. The time interval can be represented by a timer, a combination of start and end times, a combination of start and duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0585] Start Time: Used to indicate the start time of the applicable / valid time.

[0586] End Time: Used to indicate the end time of the applicable / valid time.

[0587] Conditions and / or events that triggered the reporting and / or measurement of adjacent cell load status: Indicates the events and / or conditions that triggered the reporting and / or measurement of adjacent cell load status. Adjacent cell load status includes currently measured adjacent cell load information and may also include predicted adjacent cell load information. The events and / or conditions that trigger the reporting include one or more of the following:

[0588] The adjacent cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0589] The adjacent cell load is predicted to be greater than and / or equal to and / or less than a predetermined threshold. The events and / or conditions triggering the report may include one or more of the following settings: event type, event, predetermined threshold, etc.

[0590] Overload will occur. Events and / or conditions that trigger reporting may include one or more of the following settings: event type, event, etc.

[0591] Overload is predicted to occur. Events and / or conditions triggering reporting may include one or more of the following settings: event type, event, etc.

[0592] The fields within the above 10th, 11th, and 12th messages may be used for measured load information or for predicted load information. Here, the adjacent cell (or nearby cell) may be a handover candidate cell or may include it.

[0593] In some implementations, for example, the seventh node may be a gNB DU and the eighth node may be a gNB CU. In LTM handover, the LTM handover decision is determined by the gNB DU, but since the gNB DU does not know the load status of the candidate cells, there is a high probability that the terminal will be handed over to a high-load cell, causing local overload, which necessitates frequent handovers of the terminal and leads to a degradation of service performance. The gNB DU may request the load status of adjacent cells and / or target candidate cells from the gNB CU. The gNB CU may transmit the acquired load status of adjacent cells and / or target candidate cells to the gNB DU. In this way, the gNB DU can make an LTM handover decision based on the load status of adjacent cells and / or target candidate cells, for example, by selecting an appropriate handover target cell.

[0594] Example 5

[0595] Node 9 transmits a message 13 containing information about a situation where the load of an adjacent cell is too high to Node 10, so that Node 10 can be aware of the situation where the load of an adjacent cell is too high, and Node 10 can refer to this information when making a mobility decision. Here, the situation where the load of an adjacent cell is too high may be a situation where the current load of the adjacent cell is too high or a situation where the predicted load of the adjacent cell is too high. Here, the adjacent cell may refer to an adjacent cell, or a candidate target cell and / or target cell for handover, etc. The mobility decision may be a handover-related decision, for example, an LTM handover decision. For example, the gNB CU obtains information that the load of an adjacent cell is too high based on the acquired adjacent cell load information, and the gNB CU can transmit this information to the gNB DU. The gNB DU can refer to this information when making an LTM handover decision, and, for example, by not selecting an adjacent cell with too much load as the target cell for LTM handover, it can prevent frequent handovers caused by excessive load and prevent terminal performance degradation caused by this.

[0596] In some embodiments, the 13th message may include one or more of the following information and / or fields:

[0597] Transmission Node ID: Used to identify the node transmitting the message.

[0598] Receiving Node ID: Used to identify the node receiving the message.

[0599] Cell ID corresponding to predicted excessive load: Used to identify the cell corresponding to a situation where the load is predicted to be too large.

[0600] Beam ID corresponding to predicted excessive load: Used to identify the beam corresponding to a situation where the load is predicted to be too large.

[0601] Predicted amount of excessive load.

[0602] Time information for responding to predicted excessive load: Used to indicate when the predicted excessive load occurs.

[0603] Accuracy and / or confidence in the prediction.

[0604] Action: Used to indicate the action that the message receiving node must apply. An action may include one or more of the following: for example, deny RRC establishment, deny non-emergency RRC establishment, deny RRC establishment for signaling, allow only urgent session establishment, allow only mobile terminated services, allow only high-priority sessions, etc. In some implementations, this action may be a configured action, meaning the message receiving node must perform the action. In some other implementations, this action may be a suggested action, and the message receiving node may or may not perform the suggested action depending on its circumstances.

[0605] Example 6

[0606] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a ninth node transmits a 14th message containing receivable load information (e.g., information of an adjacent cell) to a tenth node, thereby enabling the tenth node to know the receivable load. The tenth node may refer to this information when making a subsequent mobility decision. Here, the adjacent cell may mean an adjacent cell, or a candidate target cell and / or a target cell for handover, etc. The mobility decision may be a handover-related decision, e.g., an LTM handover decision. In some embodiments, for example, a gNB CU may obtain the adjacent cell load status, and the gNB CU may transmit receivable load information to a gNB DU, and the gNB DU may refer to this information when making an LTM handover decision, thereby preventing frequent handovers and service interruptions due to excessive load by handing over a terminal to a cell with too large a load.

[0607] In some embodiments, the 14th message may include one or more of the following information and / or fields:

[0608] Transmission Node ID: Used to identify the node transmitting the message.

[0609] Receiving Node ID: Used to identify the node receiving the message.

[0610] Acceptable load information: Information indicating the acceptable load.

[0611] Capacity to accommodate load.

[0612] Beam ID corresponding to the load capacity that can be accommodated.

[0613] Cell ID corresponding to the load capacity that can be accommodated.

[0614] Actions corresponding to acceptable load: Used to indicate the actions that the message receiving node must apply. Actions may include one or more of the following: e.g., deny RRC establishment, deny non-urgent RRC establishment, deny RRC establishment for signaling, allow only urgent session establishment, allow only mobile termination services, allow only high-priority sessions, etc. In some implementations, these actions may be configured actions, meaning the message receiving node must perform the corresponding actions. In some other implementations, these actions may be proposed actions, and the message receiving node may or may not perform the proposed actions depending on its circumstances.

[0615] Time corresponding to acceptable load: Used to indicate when the acceptable load can be accommodated.

[0616] Accuracy and / or confidence in the prediction.

[0617] Example 7

[0618] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a ninth node transmits a 15th message containing information on the activation and / or deactivation of a candidate cell to a tenth node, thereby enabling the tenth node to know which candidate cell may be selected as the handover target cell when performing a handover. For example, only a cell that is in an active state may be selected as the handover target cell, a cell that is not in a deactivated state may be selected as the handover target cell, or a cell that is in a deactivated state may not be selected as the handover target cell. The ninth node may decide to activate and / or deactivate the candidate cell based on the acquired and / or received load state of the candidate cell. For example, if the load state of the candidate cell is too large / high, the candidate cell may be deactivated to prevent frequent handovers due to the large / high load after the terminal is handed over to that cell. For example, if the load state of the candidate cell is low, the candidate cell may be activated to ensure the performance of the terminal when the terminal is handed over to that candidate cell. And / or, Node 9 may decide to enable and / or disable a candidate cell based on performance information obtained and / or received from other terminals within the candidate cell. For example, if the performance of other terminals within the candidate cell is poor, the candidate cell may be disabled to prevent performance degradation of the terminal after the terminal is handed over to a cell where QoS performance and / or QoE performance cannot be guaranteed. Or, if the performance of other terminals within the candidate cell is good, the candidate cell may be enabled to guarantee the performance of the terminal after the terminal is handed over to that cell.

[0619] In some embodiments, the 15th message may include one or more of the following information and / or fields:

[0620] Transmission Node ID: Used to identify the node transmitting the message.

[0621] Receiving Node ID: Used to identify the node receiving the message.

[0622] Terminal ID: Indicates the user corresponding to the activation and / or deactivation of the candidate cell.

[0623] ID of active cell: Indicates the ID of the active cell, or may be a list of IDs of active cells. The cell may be a handover candidate cell. The active cell may also be a cell where activation can be performed and / or a cell where activation is permitted.

[0624] Activation Time: Used to indicate the activation time and / or time interval corresponding to the activated cell. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0625] Start time: Used to indicate the start time of the activation time.

[0626] End time: Used to indicate the end time of the activation time.

[0627] Available and / or Allowed Activation Time: Used to indicate the available and / or allowed activation time and / or time interval corresponding to the activated cell. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0628] Start time: Used to indicate the start time of the activation time.

[0629] End time: Used to indicate the end time of the activation time.

[0630] ID of disabled cell: Indicates the ID of the disabled cell, or may be a list of IDs of disabled cells. The cell may be a handover candidate cell. The disabled cell may also be a cell where disabled can be performed and / or a cell where disabled is permitted.

[0631] Inactive Time: Used to indicate the inactive time and / or time interval corresponding to the inactive cell. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0632] Start time: Used to indicate the start time of the inactivity time.

[0633] End time: Used to indicate the end time of the inactivity time.

[0634] Available and / or Allowed Disable Time: Used to indicate the available and / or allowed disabled time and / or time interval corresponding to the disabled cell. The time can be relative or absolute. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0635] Start time: Used to indicate the start time of the inactivity time.

[0636] End time: Used to indicate the end time of the inactivity time.

[0637] Accuracy and / or confidence of the prediction: In some implementations, this information may be included in the case of a predicted activation and / or deactivation decision.

[0638] The candidate cell activation and / or deactivation information within the 15th message may be predictive information applicable at the current time or applicable at a future time.

[0639] Example 8

[0640] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a 11th node transmits a 16th message containing a user performance request to a 12th node to request the 12th node to report the requested user performance. In some embodiments, the user performance may be the user performance corresponding to an LTM handover. In some embodiments, for example, the 11th node may use the user performance to evaluate relevant decisions, for example, decisions related to an LTM handover. For example, good user performance (e.g., better than one or more predetermined criteria or performance levels) may indicate that the relevant decision is appropriate, and bad user performance (e.g., worse than one or more predetermined criteria or performance levels) may indicate that the relevant decision is inappropriate and requires optimization and updating. In some other embodiments, for example, the 11th node may also use the user performance to evaluate an artificial intelligence machine learning model, for example, whether the model can be continued to be used, whether training and / or tuning of the model is required, etc. In other embodiments, for example, the 11th node may make a decision based on user performance. For example, if user performance meets the requirements for users and / or services, the subsequent user may be handed over to the cell where the user is located. In other embodiments, for example, after acquiring user performance, the 11th node accepts and / or rejects a handover request based on the acquired user performance. For example, if the performance of a terminal handed over from source node A and / or source cell A to the 11th node is poor, the 11th node may subsequently reject a handover request sent by source node A and / or source cell A.For example, if the performance of the terminal handed over from source node A and / or source cell A to the 11th node is good, the 11th node may subsequently accept a handover request transmitted by source node A and / or source cell A.

[0641] In some embodiments, the 16th message may include one or more of the following information and / or fields:

[0642] Transmission Node ID: Used to identify the node transmitting the message.

[0643] Receiving Node ID: Used to identify the node receiving the message.

[0644] Request ID: Used to identify the request.

[0645] Measurement ID: Used to identify this measurement.

[0646] User Performance Request Instruction: Used to direct user performance report requests.

[0647] Requested Content: Used to indicate the content requested to be reported. The content may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0648] The range corresponding to the requested content.

[0649] Events and / or conditions triggering reporting and / or measurements: This means that reporting and / or measurements need to be performed when the events and / or conditions triggering reporting and / or measurements are met. Events and / or conditions triggering reporting and / or measurements include one or more of the following:

[0650] The terminal RRC status changes. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0651] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0652] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0653] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0654] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0655] Reporting Period of Requested Content: Used to indicate the interval for periodic reporting of requested content, or the time interval between two adjacent reports. The reporting period may also be the measurement time of the reported data. If this field is empty, a one-time report is indicated, and the reporting time for a one-time report is from the measurement start time to the measurement end time. In some implementations, for example, the reporting period may be the reporting period for periodic reporting.

[0656] Requested Measurement Time: Used to indicate the time and / or time interval of the measurement. The time can be relative or absolute. The time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0657] Measurement start time: Used to indicate the start time of the measurement.

[0658] Measurement end time: Used to indicate the end time of the measurement.

[0659] Requested Reporting Time: Used to indicate the time and / or time interval for reporting. The time can be relative or absolute. The time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0660] Start time: Used to indicate the start time for the report.

[0661] End time: Used to indicate the end time for reporting.

[0662] Applicable / Valid Time Corresponding to the Content Requested to be Reported: Used to indicate the valid time and / or time interval corresponding to the content requested to be reported. Time can be relative or absolute time. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0663] Start Time: Used to indicate the start time of the applicable / valid time.

[0664] End Time: Used to indicate the end time of the applicable / valid time.

[0665] Partial Reporting Indicator: Used to indicate whether the message receiving node can perform partial reporting, that is, whether the message receiving node can report a portion of the information requested to be reported. If it is indicated that partial reporting can be performed, the message receiving node may report only a portion of the information requested to be reported. If it is indicated that partial reporting cannot be performed, the message receiving node must report all the information requested to be reported, and if one or more of the information requested to be reported cannot be reported, the message receiving node sends a request failure message to the message sending node. The information requested to be reported may include one or more of the aforementioned request contents and may also be one or more of the scopes corresponding to the aforementioned request contents. This instruction allows the message receiving node to report partial information according to its circumstances, thereby preventing a situation where the message receiving node must send a request failure message if one or more of the information requested to be reported cannot be reported, which prevents the result of the message sending node having to make a new request due to a request failure. Otherwise, the message sending node does not know which message the message receiving node can send, so it must continuously attempt requests, which results in a signaling burden.

[0666] Mandatory reporting of information requested to be reported: Used to indicate whether information requested to be reported must be reported. If information is indicated to be mandatory, the message receiving node must report said information and / or the load status corresponding to the information. The information requested to be reported may include one or more of the aforementioned requests and may also be one or more of the scopes corresponding to the aforementioned requests. The message receiving node may decide which parameters to report based on the instructions and / or its own circumstances.

[0667] Priority of information requested to be reported: Used to indicate the priority of information requested to be reported. In some implementations, the message receiving node must report high-priority information. The message receiving node may report or not report low-priority information depending on its circumstances. The information requested to be reported may include one or more of the aforementioned requests and may also be one or more of the ranges corresponding to the aforementioned requests. The message receiving node may decide which parameters to report based on priority and its circumstances.

[0668] Indicator for whether user performance needs to be collected in subsequent LTM handover: Used to inform the message receiving node whether it is necessary to collect the terminal's performance in subsequent LTM handover. This can be represented by a single bit. For example, if the bit is 1, it indicates that it is necessary to collect the terminal's performance in subsequent LTM handover; if the bit is 0, it indicates that it is not necessary to collect the terminal's performance in subsequent LTM handover.

[0669] User performance request information: Request information related to user performance. This may include one or more of the following:

[0670] Slice count: The number of slices corresponding to user performance that can be reported.

[0671] Slice ID and / or list of IDs: A range of slices corresponding to user performance that can be reported. For example, the slices corresponding to user performance that can be reported are one or more of the slice ID and / or list of IDs.

[0672] Cell count: The number of cells corresponding to user performance that can be reported.

[0673] Cell ID and / or ID list: A range of cells corresponding to user performance that can be reported. For example, the cells corresponding to user performance that can be reported are one or more of the cell ID and / or ID list.

[0674] Beam Count: The number of beams corresponding to user performance that can be reported.

[0675] Beam ID and / or ID list: A range of beams corresponding to user performance that can be reported. For example, the beams corresponding to user performance that can be reported are one or more of the beam ID and / or ID list.

[0676] Node count: The number of nodes corresponding to the user performance that can be reported.

[0677] Node ID and / or list of IDs: A range of nodes corresponding to user performance that can be reported. For example, the nodes corresponding to user performance that can be reported are one or more of the node ID and / or list of IDs.

[0678] In some embodiments, the 12th node may transmit a 17th message containing a user performance response to the 11th node to indicate whether the 11th node can perform reporting, thereby allowing the 11th node to know whether it can subsequently receive from the 12th node the content requested to be reported. In some embodiments, for example, if the 17th message received by the 11th node indicates that the 12th node can report all and / or part of the requested user performance information, the 11th node may subsequently receive the user performance information reported by the 12th node, for example, through a subsequent 18th message. In some other embodiments, for example, the 11th node may transmit a message to the 12th node to stop (and / or cancel) reporting based on the information indicated in the received 17th message, for example, to stop (and / or cancel) reporting through the 16th message.

[0679] In some embodiments, the 17th message may include one or more of the following information and / or fields:

[0680] Transmission Node ID: Used to identify the node transmitting the message.

[0681] Receiving Node ID: Used to identify the node receiving the message.

[0682] Measurement ID: Used to identify a measurement. In some implementations, to associate a report with a request and / or response, this ID may match the measurement ID of the 16th message.

[0683] Request ID: Used to identify the request. In some implementations, this ID may match the request ID of message 16 to associate the report with the request and / or response.

[0684] User Performance Request Acknowledge: Used to indicate whether user performance can be measured and / or reported. The user performance request acknowledgment can be represented in bits.

[0685] Terminal ID on which reporting can be performed: ID(s) of the user(s) corresponding to the user performance to be measured and / or reported. This may be an ID or a list of IDs.

[0686] Cell IDs where reporting can be performed: ID(s) of the cell(s) corresponding to the user performance to be measured and / or reported. This may be an ID or a list of IDs.

[0687] Beam IDs for which reporting can be performed: ID(s) of the beam(s) corresponding to the user performance to be measured and / or reported. This may be an ID or a list of IDs.

[0688] Slice IDs for which reporting can be performed: ID(s) of slice(s) corresponding to user performance that can be measured and / or reported. This may be an ID or a list of IDs.

[0689] Reportable content: Used to indicate what can be reported, which may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0690] Predictable content: Used to indicate predictable content, which may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0691] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0692] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0693] Reportable Time: Indicates the time and / or time interval during which the content can be reported. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0694] Start Time: Used to indicate the start time of the time available for reporting.

[0695] End Time: Used to indicate the end time of the time available for reporting.

[0696] Available Measurement Modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0697] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0698] Available Measurement Time: Used to indicate the measurement time and / or time interval during which a measurement may be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0699] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0700] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0701] Predictable Time: Used to indicate the time and / or time interval during which a prediction can be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0702] Prediction start time: Used to indicate the start time at which the prediction can be performed.

[0703] Prediction end time: Used to indicate the end time at which the prediction can be performed.

[0704] Applicable / Valid Time of Predictable Response Predictions: Used to indicate the applicable / valid time and / or time interval of predictable corresponding predictions. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0705] Start Time: Used to indicate the start time of the valid time available for forecasting.

[0706] End Time: Used to indicate the end time of the valid time available for forecasting.

[0707] Reportable Response Information: Used to indicate information corresponding to user performance that can be reported. This may include one or more of the following:

[0708] Slice count: The number of slices corresponding to user performance that can be reported.

[0709] Slice ID and / or list of IDs: A range of slices corresponding to user performance that can be reported. For example, the slices corresponding to user performance that can be reported are one or more of the slice ID and / or list of IDs.

[0710] Cell count: The number of cells corresponding to user performance that can be reported.

[0711] Cell ID and / or ID list: A range of cells corresponding to user performance that can be reported. For example, the cells corresponding to user performance that can be reported are one or more of the cell ID and / or ID list.

[0712] Beam Count: The number of beams corresponding to user performance that can be reported.

[0713] Beam ID and / or ID list: A range of beams corresponding to user performance that can be reported. For example, the beams corresponding to user performance that can be reported are one or more of the beam ID and / or ID list.

[0714] Node count: The number of nodes corresponding to the user performance that can be reported.

[0715] Node ID and / or list of IDs: A range of nodes corresponding to user performance that can be reported. For example, the nodes corresponding to user performance that can be reported are one or more of the node ID and / or list of IDs.

[0716] Trigger events and / or conditions corresponding to report and / or measurement that can be performed: Indicate trigger events and / or conditions corresponding to report and / or measurement that can be performed. If the event and / or condition triggering the report and / or measurement is satisfied, the report and / or measurement may be performed. The event and / or condition triggering the report and / or measurement includes one or more of the following:

[0717] The terminal RRC status changes. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0718] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0719] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0720] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0721] Terminal IDs for which measurement and / or reporting cannot be performed: ID(s) of user(s) for whom user performance measurement and / or reporting cannot be performed. This may be an ID or a list of IDs.

[0722] Cell IDs for which measurement and / or reporting cannot be performed: ID(s) of cell(s) for which user performance measurement and / or reporting cannot be performed. This may be an ID or a list of IDs.

[0723] Beam IDs for which measurement and / or reporting cannot be performed: ID(s) of beam(s) for which user performance measurement and / or reporting cannot be performed. This may be an ID or a list of IDs.

[0724] Slice IDs for which measurement and / or reporting cannot be performed: ID(s) of slice(s) for which user performance measurement and / or reporting cannot be performed. This may be an ID or a list of IDs.

[0725] Non-reportable content: Used to indicate non-reportable content, which may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0726] Unpredictable content: Used to indicate unpredictable content, which may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0727] Unavailable Report Modes: Used to indicate unavailable reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0728] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0729] Non-reportable time: Indicates a time and / or time interval during which content cannot be reported. Time may be relative or absolute. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0730] Start Time: Used to indicate the start time of a time that is unavailable for reporting.

[0731] End Time: Used to indicate the end time of a period when it is unavailable for reporting.

[0732] Unavailable measurement mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0733] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0734] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0735] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0736] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0737] Unpredictable time: Used to indicate a time and / or time interval for which prediction cannot be performed. Time can be relative or absolute time. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0738] Prediction start time: Used to indicate the start time at which a prediction cannot be performed.

[0739] Prediction end time: Used to indicate the end time at which a prediction cannot be performed.

[0740] Applicable / Valid Time for Unpredictable Response Predictions: Used to indicate the applicable / valid time and / or time interval for unpredictable response predictions. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement in Message 16, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0741] Start Time: Used to indicate the start time of the valid time that is unavailable for forecasting.

[0742] End Time: Used to indicate the end time of the valid time that is unavailable for forecasting.

[0743] Non-reportable response information: Used to indicate information corresponding to user performance that cannot be reported. This may include one or more of the following:

[0744] Slice count: The number of slices corresponding to user performance that cannot be reported.

[0745] Slice ID and / or list of IDs: A range of slices corresponding to user performance that cannot be reported. For example, the slices corresponding to user performance that cannot be reported are one or more of the slice ID and / or list of IDs.

[0746] Cell count: The number of cells corresponding to user performance that cannot be reported.

[0747] Cell ID and / or ID list: A range of cells corresponding to user performance that cannot be reported. For example, the cells corresponding to user performance that cannot be reported are one or more of the cell ID and / or ID list.

[0748] Beam Count: The number of beams corresponding to user performance that cannot be reported.

[0749] Beam ID and / or ID list: A range of beams corresponding to user performance that cannot be reported. For example, the beams corresponding to user performance that cannot be reported are one or more of the beam ID and / or ID list.

[0750] Node count: The number of nodes corresponding to user performance that cannot be reported.

[0751] Node ID and / or list of IDs: A range of nodes corresponding to user performance that cannot be reported. For example, the nodes corresponding to user performance that cannot be reported are one or more of the node ID and / or list of IDs.

[0752] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering this report and / or measurement are satisfied, the report and / or measurement cannot be performed. The events and / or conditions triggering this report and / or measurement include one or more of the following:

[0753] The terminal RRC status changes. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0754] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0755] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0756] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0757] Cause / Reason: Indicates the reason why measurement and / or reporting cannot be performed.

[0758] Indicates whether user performance can be collected in a subsequent LTM handover: Used to inform the message receiving node whether the terminal's performance can be collected in a subsequent LTM handover. This can be represented by a single bit. For example, if the bit is 1, it indicates that the terminal's performance can be collected in a subsequent LTM handover; if the bit is 0, it indicates that the terminal's performance cannot be collected in a subsequent LTM handover.

[0759] Node 12 may notify Node 11 of the requested user performance by transmitting a message 18 containing user performance to Node 11, depending on its own circumstances and / or in accordance with a message 16 containing a user performance request received from Node 11. In some embodiments, the user performance may be the user performance corresponding to an LTM handover. In some embodiments, for example, Node 11 may use the user performance to evaluate relevant decisions, for example, decisions related to an LTM handover. For example, good user performance (e.g., better than one or more predetermined criteria or performance levels) may indicate that the relevant decision is appropriate, and bad user performance (e.g., worse than one or more predetermined criteria or performance levels) may indicate that the relevant decision is inappropriate and requires optimization and updates. In some other embodiments, for example, Node 11 may also use the user performance to evaluate an artificial intelligence machine learning model, for example, whether the model can be continued to be used, whether training and / or tuning of the model is required, etc. In other implementations, for example, the 11th node may make a decision based on user performance. For example, if user performance meets the requirements for users and / or services, the subsequent user may be handed over to the cell where the user is located.

[0760] In some embodiments, the 18th message may include one or more of the following information and / or fields:

[0761] Transmission Node ID: Used to identify the node transmitting the message.

[0762] Receiving Node ID: Used to identify the node receiving the message.

[0763] Measurement ID: Used to identify a measurement. In some implementations, to associate a report with a request and / or response, this ID may match the measurement ID of the 16th message and / or the 17th message.

[0764] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID of the 16th message and / or the 17th message.

[0765] Reported Content: Used to indicate reported content. Content may include one or more of the following: QoS parameters, QoE parameters, TA information used for successful access, TA information used for access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value within an LTM cell switching command, access time, successful access time, etc.

[0766] Scope corresponding to the reported content: A scope may be one or more of the following IDs and / or a list of IDs: cell, beam, slice, terminal (UE), terminal not to be measured, terminal service to be measured, scenario, node, channel, Protocol Data Unit Session, Data Radio Bearers (DRB), QoS flow, QoS level, etc. A service may be a service type, Quality of Service (QoS), scenario, etc. A service type may include one or more of the following: voice service, video service, virtual reality service, augmented reality service, call service, etc. A quality of service may include one or more of the following: delay, throughput, reliability, packet loss rate, data transmission rate, etc. This may be identified by a 5G QoS Identifier (5QI), QoS Class Identifier (QCI), etc. The scenario may include one or more of the following: Ultra-reliable and Low Latency Communications (URLLC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), etc. The above range may also indicate performance for users excluding one or more terminals, for example, other users within a slice and / or cell excluding handover users, or other users within a slice and / or cell excluding users corresponding to slice remapping.

[0767] Applicable / Valid Time Corresponding to Reported Content: Used to indicate the valid time and / or time interval corresponding to the reported content. Time can be relative or absolute time. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0768] Start Time: Used to indicate the start time of the applicable / valid time.

[0769] End Time: Used to indicate the end time of the applicable / valid time.

[0770] Trigger event and / or condition that triggered this report and / or measurement: Indicates the trigger event and / or condition that triggered this report and / or measurement. The event and / or condition triggering the report and / or measurement includes one or more of the following:

[0771] The terminal RRC status changes. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0772] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0773] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0774] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0775] Example 9

[0776] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a 13th node transmits a 19th message to a 14th node, which includes a request to report predicted beam information, thereby requesting the 14th node to report predicted beam information. The beam information may be information about a beam that a user intends to access. The predicted beam information may be obtained by mathematical method calculation and / or an artificial intelligence machine learning model. In some embodiments, for example, the 13th node may transmit the predicted beam information in advance to a handover target node, and the target node may reserve resources for the predicted beam, thereby ensuring terminal performance and preventing service interruption due to a lack of resources for the selected beam by ensuring that there are sufficient resources when the terminal needs to access the beam. In other embodiments, a gNB CU may transmit the predicted beam information to a gNB DU, and the gNB DU may reserve resources to ensure the terminal's performance.

[0777] In some embodiments, the 19th message may include one or more of the following information and / or fields:

[0778] Transmission Node ID: Used to identify the node transmitting the message.

[0779] Receiving Node ID: Used to identify the node receiving the message.

[0780] Measurement and / or Prediction ID: Used to identify measurements and / or predictions.

[0781] Request ID: Used to identify the request.

[0782] Terminal ID: Indicates the user corresponding to the predicted beam information requested to be reported. This may be a terminal ID or a list of terminal IDs.

[0783] Cell ID: Indicates the cell corresponding to the forecast beam information requested to be reported. This can be a cell ID or a list of cell IDs.

[0784] Candidate Cell Predicted Beam Information Request Identifier: Instructs the message receiving node to report the candidate cell's predicted beam information.

[0785] Slice ID: Indicates the slice corresponding to the requested prediction beam information. This can be a slice ID or a list of slice IDs.

[0786] Predicted beam information request identifier corresponding to a slice within a candidate cell: Instructs the message receiving node to report predicted beam information corresponding to a slice within a candidate cell.

[0787] Predicted Beam Information Request Identifier: This information is used to indicate that a report of predicted beam information is to be requested. This field may be represented by a single bit. For example, if the bit is 1, it indicates that a report of predicted beam information is requested; if the bit is 0, it indicates that a report of predicted beam information is not requested. Alternatively, if the bit is 0, it may indicate that a report of predicted beam information is requested; and if the bit is 1, it may indicate that a report of predicted beam information is not requested.

[0788] Registration Request: Used to indicate the type of request. For example, this may include start, end, add, update, cancel, etc.

[0789] Report Registration Request: Used to indicate the type of report request. For example, this may include start, end, add, update, cancel, etc.

[0790] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0791] Events and / or conditions triggering a report: If the events and / or conditions triggering a report are met, a report must be performed.

[0792] Reporting Period: Used to indicate the interval for periodic reporting. The reporting period may also be the estimated time and / or measurement time of the reported information. In one embodiment, for example, if there is no content in this field, a one-time report is indicated, and the reporting time of the one-time report is the measurement time and / or reporting time.

[0793] Reporting Time of Requested Content: Used to indicate the time and / or time interval for which content is requested to be reported. Time can be relative or absolute. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0794] Start time: Used to indicate the start time of the report time.

[0795] End time: Used to indicate the end time of the report time.

[0796] Reporting Mode of Requested Content: Used to specify the reporting mode of the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0797] Measurement mode of the requested content: Used to specify the measurement mode of the requested content. This may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0798] Events and / or conditions triggering measurement: When events and / or conditions triggering measurement are met, a measurement must be performed.

[0799] Measurement period: Used to indicate the interval of periodic measurements.

[0800] Measurement Time for Request: Used to indicate the time and / or time interval for measuring the requested content. The time can be relative or absolute. The time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0801] Start time: Used to indicate the start time of the measurement time.

[0802] End time: Used to indicate the end time of the measurement time.

[0803] Applicable / Valid Time of Request: Used to indicate the valid time and / or time interval of the requested content. Time can be relative or absolute. Time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0804] Start Time: Used to indicate the start time of the applicable / valid time.

[0805] End Time: Used to indicate the end time of the applicable / valid time.

[0806] Requested Prediction Time Interval: Used to indicate the time and / or time interval for the prediction. The time can be relative or absolute. The time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0807] Prediction start time: Used to indicate the start time of the prediction.

[0808] Prediction end time: Used to indicate the end time of the prediction.

[0809] Applicable / Valid Time of Requested Prediction: Used to indicate the time and / or time interval corresponding to the prediction. Time can be relative or absolute. Time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0810] Start Time: Used to indicate the start time of the applicable / valid time.

[0811] End Time: Used to indicate the end time of the applicable / valid time.

[0812] Request Information: Used to indicate request information for reporting predicted beam information. This may include one or more of the following:

[0813] Cell count: The number of cells corresponding to the prediction beam information requested to be reported.

[0814] Cell ID and / or ID list: Cells corresponding to the requested forecast beam information. For example, the cells corresponding to the forecast beam information requested to be reported must be one or more of the cell ID and / or ID list.

[0815] Number of nodes: The number of nodes corresponding to the prediction beam information requested to be reported.

[0816] Node ID and / or ID list: Nodes corresponding to the requested forecast beam information. For example, the nodes corresponding to the forecast beam information requested to be reported must be one or more of the node ID and / or ID list.

[0817] Beam Count: The number of beams corresponding to the predicted beam information requested to be reported. The beams may be SSB beams or other beams.

[0818] Beam ID and / or ID list: Beams corresponding to the requested predicted beam information. For example, the beams corresponding to the predicted beam information requested to be reported must be one or more of the beam ID and / or ID list. The beams may be SSB beams or other beams.

[0819] Number of slices: The number of slices corresponding to the prediction beam information requested to be reported.

[0820] Slice ID and / or ID list: Slices corresponding to the requested forecast beam information. For example, the slices corresponding to the forecast beam information requested to be reported must be one or more of the slice ID and / or ID list.

[0821] In some embodiments, the 14th node may transmit a 20th message containing a report response of predicted beam information to the 13th node to inform the 13th node whether the 14th node can measure and / or report and / or predict beam information, and accordingly, the 13th node may know whether the requested content to be reported can subsequently be received from the 14th node. In some embodiments, for example, if the 20th message received by the 13th node indicates that the 14th node can measure and / or report and / or predict beam information, the 13th node may subsequently receive the predicted beam information reported by the 14th node, for example, through a subsequent 21st message. In some other embodiments, for example, the 13th node may transmit a message to the 14th node to stop (and / or cancel) reporting based on the information indicated in the received 20th message, for example, to stop (and / or cancel) reporting through the 19th message.

[0822] In some embodiments, the 20th message may include one or more of the following information and / or fields:

[0823] Transmission Node ID: Used to identify the node transmitting the message.

[0824] Receiving Node ID: Used to identify the node receiving the message.

[0825] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID of the 19th message.

[0826] Request ID: Used to identify the request corresponding to the response. In some implementations, to associate a report with a request and / or response, this ID may match the request ID of message 19.

[0827] Acknowledgment for Predicted Beam Information Request: Used to indicate whether predicted beam information can be measured and / or reported and / or predicted. The acknowledgment for a predicted beam information request may be a bit indicating whether the request can be measured and / or reported and / or predicted.

[0828] Terminal ID for which reporting can be performed: ID(s) of the user(s) corresponding to the predicted beam information to be measured and / or reported. This may be an ID or a list of IDs.

[0829] Cell IDs for which reporting can be performed: ID(s) of the cell(s) corresponding to the predicted beam information to be measured and / or reported. This may be an ID or a list of IDs.

[0830] Beam IDs for which reporting may be performed: ID(s) of beam(s) corresponding to predicted beam information that may be measured and / or reported. This may be an ID or a list of IDs.

[0831] Slice IDs for which reporting may be performed: ID(s) of slice(s) corresponding to predicted beam information to be measured and / or reported. This may be an ID or a list of IDs.

[0832] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0833] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0834] Time available for reporting: Indicates the time and / or time interval during which the content can be reported. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 19, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0835] Start Time: Used to indicate the start time of the time available for reporting.

[0836] End Time: Used to indicate the end time of the time available for reporting.

[0837] Available Measurement Modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0838] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0839] Available measurement time: Used to indicate the measurement time and / or time interval during which a measurement may be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 19, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0840] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0841] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0842] Predictable Time: Used to indicate the time and / or time interval during which a prediction can be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 19, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0843] Prediction start time: Used to indicate the start time at which the prediction can be performed.

[0844] Prediction end time: Used to indicate the end time at which the prediction can be performed.

[0845] Applicable / Valid Time of Predictable Corresponding Predictions: Used to indicate the applicable / valid time and / or time interval of predictable corresponding predictions. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 19, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0846] Start Time: Used to indicate the start time of the valid time available for forecasting.

[0847] End Time: Used to indicate the end time of the valid time available for forecasting.

[0848] Reportable and / or measurable and / or predictable corresponding information: Used to indicate information corresponding to reported and / or measurable and / or predictable beam information. This may include one or more of the following:

[0849] Number of slices: The number of slices corresponding to beam information that can be reported and / or measured and / or predicted.

[0850] Slice ID and / or ID list: A range of slices corresponding to beam information that can be reported and / or measured and / or predicted. For example, the slices corresponding to beam information that can be reported and / or measured and / or predicted are one or more of the slice ID and / or ID list.

[0851] Cell count: The number of cells corresponding to beam information that can be reported and / or measured and / or predicted.

[0852] Cell ID and / or ID list: A range of cells corresponding to beam information that can be reported and / or measured and / or predicted. For example, the cells corresponding to beam information that can be reported and / or measured and / or predicted are one or more of the cell ID and / or ID list.

[0853] Beam count: The number of beams corresponding to beam information that can be reported and / or measured and / or predicted.

[0854] Beam ID and / or ID List: A range of beams corresponding to reported and / or measured and / or predictable beam information. For example, the beams corresponding to reported and / or measured and / or predictable beam information are one or more of the Beam ID and / or ID List.

[0855] Number of nodes: The number of nodes corresponding to beam information that can be reported and / or measured and / or predicted.

[0856] Node ID and / or ID list: A range of nodes corresponding to reporting and / or measuring and / or predictable beam information. For example, the nodes corresponding to reporting and / or measuring and / or predictable beam information are one or more of the node ID and / or ID list.

[0857] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering the report and / or measurement are met, the measurement and / or report cannot be performed.

[0858] Unavailable Report Modes: Used to indicate unavailable reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0859] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0860] Non-reportable Time: Indicates a time and / or time interval during which content cannot be reported. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0861] Start time: Used to indicate the start time of an unreportable time.

[0862] End time: Used to indicate the end time of the time when reporting is not possible.

[0863] Unavailable Measurement Mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0864] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0865] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, where the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0866] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0867] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0868] Unpredictable Time: Used to indicate a time and / or time interval where prediction cannot be performed. The time can be relative or absolute. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the prediction start time and the last n bits indicate the prediction end time. It can also be represented by separate fields including one or more of the following:

[0869] Prediction start time: Used to indicate the start time at which a prediction cannot be performed.

[0870] Prediction end time: Used to indicate the end time at which a prediction cannot be performed.

[0871] Applicable / Valid Time for Unpredictable Response Predictions: Used to indicate the applicable / valid time and / or time interval for unpredictable response predictions. Time can be relative or absolute time. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. In the case of a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0872] Start Time: Used to indicate the start time of a valid time that is unavailable for forecasting.

[0873] End Time: Used to indicate the end time of a valid period that is unavailable for prediction.

[0874] Report and / or measurement and / or unpredictable response information: Used to indicate information corresponding to report and / or measurement and / or unpredictable beam information. This may include one or more of the following:

[0875] Number of slices: The number of slices corresponding to reported and / or measured and / or unpredictable beam information.

[0876] Slice ID and / or ID list: A range of slices corresponding to reported and / or measured and / or unpredictable beam information. For example, slices corresponding to reported and / or measured and / or unpredictable beam information are one or more of the slice ID and / or ID list.

[0877] Cell count: The number of cells corresponding to reported and / or measured and / or unpredictable beam information.

[0878] Cell ID and / or ID list: A range of cells corresponding to reporting and / or measuring and / or unpredictable beam information. For example, the cells corresponding to reporting and / or measuring and / or unpredictable beam information are one or more of the cell ID and / or ID list.

[0879] Beam count: The number of beams corresponding to reported and / or measured and / or unpredictable beam information.

[0880] Beam ID and / or ID List: A range of beams corresponding to reported and / or measured and / or unpredictable beam information. For example, the beams corresponding to reported and / or measured and / or unpredictable beam information are one or more of the Beam ID and / or ID List.

[0881] Number of nodes: The number of nodes corresponding to reported and / or measured and / or unpredictable beam information.

[0882] Node ID and / or ID list: A range of nodes corresponding to reporting and / or measuring and / or unpredictable beam information. For example, the nodes corresponding to reporting and / or measuring and / or unpredictable beam information are one or more of the node ID and / or ID list.

[0883] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering this measurement and / or report are met, the measurement and / or report cannot be performed.

[0884] Cause / Reason: Indicates the reason why measurement and / or reporting and / or prediction cannot be performed.

[0885] In some embodiments, the 14th node may report to the 13th node a 21st message containing predicted beam information obtained and / or generated by the 14th node, in accordance with a 19th message containing a request to report predicted beam information received from the 13th node and its own situation. The beam information may be information about a beam that a user intends to access. The predicted beam information may be obtained by mathematical method calculation and / or an artificial intelligence machine learning model. In some embodiments, for example, the 13th node may transmit the predicted beam information in advance to a handover target node, and the target node may reserve resources for the predicted beam, thereby ensuring that there are sufficient resources to guarantee the performance of the terminal when the terminal needs to access the beam. In other embodiments, the gNB CU may transmit the predicted beam information to the gNB DU, and the gNB DU may reserve resources to guarantee the performance of the terminal.

[0886] In some embodiments, the 21st message may include one or more of the following information and / or fields:

[0887] Transmission Node ID: Used to identify the node transmitting the message.

[0888] Receiving Node ID: Used to identify the node receiving the message.

[0889] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement ID of the 19th message and / or the 20th message.

[0890] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID of the 19th message and / or the 20th message.

[0891] Terminal ID: Indicates the user corresponding to the reported prediction beam information. This may be a terminal ID or a list of terminal IDs.

[0892] Cell ID: Indicates the cell corresponding to the reported forecast beam information. This can be a cell ID or a list of cell IDs.

[0893] Beam ID: Indicates the beam corresponding to the reported predicted beam information. This can be a beam ID or a list of beam IDs.

[0894] Slice ID: Indicates the slice corresponding to the reported prediction beam information. This can be a slice ID or a list of slice IDs.

[0895] Predicted Beam Information: Indicates reported predicted beam information. Predicted beam information may include one or more of the following: beam ID, time to access the beam, time to leave the beam, residence time in the beam, etc.

[0896] Applicable / Valid Time Corresponding to Predicted Beam Information: Used to indicate a valid time and / or time interval corresponding to the predicted beam information. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 19, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0897] Start Time: Used to indicate the start time of the applicable / valid time.

[0898] End Time: Used to indicate the end time of the applicable / valid time.

[0899] Event and / or condition that triggered this report: Indicates the event and / or condition that triggered this report.

[0900] Event and / or condition that triggered this measurement: Indicates the event and / or condition that triggered this measurement.

[0901] Example 10

[0902] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a 15 node sending a 22 message to a 16 node that includes a request to report actual accessed beam information, thereby requesting the 16 node to report the requested actual accessed beam information. In some embodiments, for example, the 15 node may use the actual accessed beam information to evaluate whether the predicted beam information is appropriate. For example, if the actual accessed beam information does not match the predicted beam information, this implies that the predicted beam information is inappropriate; and if the actual accessed beam information matches the predicted beam information, this implies that the predicted beam information is appropriate. In other embodiments, for example, the 15 node may use the actual accessed beam information to support artificial intelligence machine learning functions. For example, the actual accessed beam information may be used as input parameters to train an artificial intelligence machine learning model, which may be a model for predicting beam information or a model for generating handover decisions. Alternatively, the actual accessed beam information can be used to evaluate artificial intelligence machine learning models, for example, to assess whether the model can be continued to be used, whether the model needs to be trained and / or adjusted, etc.

[0903] In some embodiments, the 22nd message may include one or more of the following information and / or fields:

[0904] Transmission Node ID: Used to identify the node transmitting the message.

[0905] Receiving Node ID: Used to identify the node receiving the message.

[0906] Measurement and / or Prediction ID: Used to identify measurements and / or predictions.

[0907] Request ID: Used to identify the request.

[0908] Terminal ID: Indicates the user corresponding to the actual accessed beam information requested to be reported. This may be a terminal ID or a list of terminal IDs.

[0909] Cell ID: Indicates the cell corresponding to the actual accessed beam information requested to be reported. This can be a cell ID or a list of cell IDs.

[0910] Beam ID: Indicates the beam corresponding to the actual accessed beam information requested to be reported. This can be a beam ID or a list of beam IDs.

[0911] Slice ID: Indicates the slice corresponding to the actual accessed beam information requested to be reported. This can be a slice ID or a list of slice IDs.

[0912] Identifier for request to report actual accessed beam information: Instructs the message receiving node to report the actual accessed beam information.

[0913] Actual Accessed Beam Information Request Identifier: Indicates that the message is intended to request a report of actual accessed beam information. This field can be represented by a single bit. For example, if the bit is 1, it indicates that a report of actual accessed beam information is requested; if the bit is 0, it indicates that a report of actual accessed beam information is not requested. Or, if the bit is 0, it indicates that a report of actual accessed beam information is requested; if the bit is 1, it indicates that a report of actual accessed beam information is not requested.

[0914] Instruction to request a report on whether the actual accessed beam matches the received beam information: Used to instruct a request to report information on whether the actual accessed beam matches the received beam information.

[0915] Registration Request: Used to indicate the type of request. For example, this may include start, end, add, update, modify, cancel, etc.

[0916] Report Registration Request: Used to indicate the type of report request. For example, this may include start, end, add, update, modify, cancel, etc.

[0917] Reporting Mode for Requested Content: Used to specify the reporting mode for the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0918] Events and / or conditions triggering a report: If the events and / or conditions triggering a report are met, a report must be performed. The events and / or conditions triggering a report include one or more of the following:

[0919] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0920] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0921] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information, or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0922] Reporting Period: Used to indicate the interval of reporting. This may also be the time interval between two adjacent reports. This time interval may be a maximum time interval or a minimum time interval. The reporting period may also be the predicted time and / or measurement time of the reported information. In one embodiment, for example, if there is no content in this field, a one-time report is indicated, and the reporting time of the one-time report is the measurement time and / or reporting time. In some embodiments, the reporting period is used to indicate the time interval of periodic reporting.

[0923] Reporting Time of Requested Content: Used to indicate the time and / or time interval for which content is requested to be reported. Time can be relative or absolute. Time can also be a time or period prior to or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0924] Start time: Used to indicate the start time of the report time.

[0925] End time: Used to indicate the end time of the report time.

[0926] Reporting mode of requested content: Used to specify the reporting mode of the requested content. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0927] Measurement mode of the requested content: Used to specify the measurement mode of the requested content. This may include one-time measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0928] Events and / or conditions triggering a measurement: If the events and / or conditions triggering a measurement are met, a measurement must be performed. The events and / or conditions triggering a measurement include one or more of the following:

[0929] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0930] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0931] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information, or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0932] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0933] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0934] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0935] Measurement Period: Used to indicate the interval for measurement. This may also be the time interval between two adjacent measurements. This time interval may be a maximum time interval or a minimum time interval. The measurement period may also be the measurement time of the measurement information. In one embodiment, for example, if there is no content in this field, a one-time measurement is indicated, and the time of the one-time measurement is the measurement time and / or reporting time. In some embodiments, the measurement period is used to indicate the time interval of periodic measurements.

[0936] Measurement Time for Requested Content: Used to indicate the time and / or time interval for measuring the requested content. The time can be relative or absolute. The time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. The time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0937] Start time: Used to indicate the start time of the measurement time.

[0938] End time: Used to indicate the end time of the measurement time.

[0939] Applicable / Valid Time of Request: Used to indicate the valid time and / or time interval of the requested content. Time can be relative or absolute. Time can also be a time or period before or after an event. An event can be an event and / or condition that triggers a measurement, or an event and / or condition that triggers a report. A time interval can be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it can be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It can also be represented by separate fields including one or more of the following:

[0940] Start Time: Used to indicate the start time of the applicable / valid time.

[0941] End Time: Used to indicate the end time of the applicable / valid time.

[0942] Request Information: Used to indicate request information for reporting actual accessed beam information. This may include one or more of the following:

[0943] Cell count: The number of cells corresponding to the actual accessed beam information requested to be reported.

[0944] Cell ID and / or ID list: Cells corresponding to the requested actual accessed beam information. For example, the cells corresponding to the actual accessed beam information requested to be reported must be one or more of the cell ID and / or ID list.

[0945] Node count: The number of nodes corresponding to the actual accessed beam information requested to be reported.

[0946] Node ID and / or list of IDs: Nodes corresponding to the requested actual accessed beam information. For example, the nodes corresponding to the actual accessed beam information requested to be reported must be one or more of the node ID and / or list of IDs.

[0947] Beam Count: The number of beams corresponding to the actual accessed beam information requested to be reported. The beams may be SSB beams or other beams.

[0948] Beam ID and / or ID list: Beams corresponding to the requested actual accessed beam information. For example, the beams corresponding to the actual accessed beam information requested to be reported must be one or more of the Beam ID and / or ID list. The beams may be SSB beams or other beams.

[0949] Slice count: The number of slices corresponding to the actual accessed beam information requested to be reported.

[0950] Slice ID and / or ID list: Slices corresponding to the requested actual accessed beam information. For example, the slices corresponding to the actual accessed beam information requested to be reported must be one or more of the slice ID and / or ID list.

[0951] In some embodiments, the 16th node transmits a 23rd message containing a report response of actual accessed beam information to the 15th node to inform the 15th node whether the 16th node can report the actual accessed beam information, and accordingly, the 15th node can know whether the requested content to be reported can subsequently be received from the 16th node. In some embodiments, for example, if the 23rd message received by the 15th node indicates that the 16th node can report the actual accessed beam information, the 15th node may subsequently receive the actual accessed beam information reported by the 16th node, for example, via a 24th message. In some other embodiments, for example, the 15th node may transmit a message to the 16th node to stop (and / or cancel) reporting based on the information indicated in the received 23rd message, for example, to stop (and / or cancel) reporting via a 22nd message.

[0952] In some embodiments, the 23rd message may include one or more of the following information and / or fields:

[0953] Transmission Node ID: Used to identify the node transmitting the message.

[0954] Receiving Node ID: Used to identify the node receiving the message.

[0955] Measurement ID: Used to identify a measurement. In some implementations, to associate a response with a request, this ID may match the measurement ID in message 22.

[0956] Request ID: Used to identify the request corresponding to the response. In some implementations, to associate the response with the request, this ID may match the request ID in message 22.

[0957] Acknowledgment for actual accessed beam information request: Used to indicate whether accessed beam information can be measured and / or reported. The acknowledgment for actual accessed beam information request may be a bit indicating whether the request can be measured and / or reported.

[0958] Terminal ID for which reporting can be performed: ID(s) of the user(s) corresponding to the actual accessed beam information to be measured and / or reported. This may be an ID or a list of IDs.

[0959] Cell IDs where reporting can be performed: ID(s) of the cell(s) corresponding to the actual accessed beam information that can be measured and / or reported. This may be an ID or a list of IDs.

[0960] Beam IDs for which reporting can be performed: ID(s) of the beam(s) corresponding to the actual accessed beam information that can be measured and / or reported. This may be an ID or a list of IDs.

[0961] Slice IDs for which reporting can be performed: ID(s) of slice(s) corresponding to the actual accessed beam information to be measured and / or reported. This may be an ID or a list of IDs.

[0962] Available Reporting Modes: Used to indicate available reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0963] Available Reporting Period: Used to indicate the interval available for reporting. This may also be the time interval between two adjacent reports that can be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of a periodic reporting mode.

[0964] Time available for reporting: Indicates the time and / or time interval during which the content can be reported. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 22, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0965] Start Time: Used to indicate the start time of the time available for reporting.

[0966] End Time: Used to indicate the end time of the time available for reporting.

[0967] Available measurement modes: Used to indicate the modes available for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0968] Measurable measurement period: Used to indicate the measurement period available for measurement.

[0969] Available Measurement Time: Used to indicate the measurement time and / or time interval during which a measurement may be performed. The time may be relative or absolute time. The time may also be a time or period prior to or after an event. The event may be an event and / or condition that triggers a measurement in Message 22, or an event and / or condition that triggers a report. The time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0970] Start time: Used to indicate the start time of the measurement period during which the measurement can be performed.

[0971] End time: Used to indicate the end time of the measurement period during which the measurement can be performed.

[0972] Corresponding information that can be reported and / or measured: Used to indicate information corresponding to actual measured access beam information that can be reported and / or measured. This may include one or more of the following:

[0973] Slice count: The number of slices corresponding to the actual accessed beam information that can be reported and / or measured.

[0974] Slice ID and / or ID list: A range of slices corresponding to actual accessed beam information that can be reported and / or measured. For example, the slices corresponding to actual accessed beam information that can be reported and / or measured are one or more of the slice ID and / or ID list.

[0975] Cell count: The number of cells corresponding to the actual accessed beam information that can be reported and / or measured.

[0976] Cell ID and / or ID list: A range of cells corresponding to actual accessed beam information that can be reported and / or measured. For example, the cells corresponding to actual accessed beam information that can be reported and / or measured are one or more of the cell ID and / or ID list.

[0977] Beam Count: The number of beams corresponding to the actual accessed beam information that can be reported and / or measured.

[0978] Beam ID and / or ID List: A range of beams corresponding to actual accessed beam information that can be reported and / or measured. For example, the beams corresponding to actual accessed beam information that can be reported and / or measured are one or more of the Beam ID and / or ID List.

[0979] Number of nodes: The number of nodes corresponding to the actual accessed beam information that can be reported and / or measured.

[0980] Node ID and / or ID list: A range of nodes corresponding to actual accessed beam information that can be reported and / or measured. For example, the nodes corresponding to actual accessed beam information that can be reported and / or measured are one or more of the node ID and / or ID list.

[0981] Trigger events and / or conditions corresponding to report and / or measurement that can be performed: Indicate trigger events and / or conditions corresponding to report and / or measurement that can be performed. If the event and / or condition triggering this report and / or measurement is satisfied, the report and / or measurement may be performed. The event and / or condition triggering the report includes one or more of the following:

[0982] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0983] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0984] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0985] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0986] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0987] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[0988] Unavailable Report Modes: Used to indicate unavailable reporting modes. This may include one-time reporting, periodic reporting, on-demand reporting, and event-triggered reporting.

[0989] Unavailable Reporting Period: Used to indicate an interval that is unavailable for reporting. This may also be the time interval between two adjacent reports that cannot be used for reporting. This time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting period may be the reporting interval of the periodic reporting mode.

[0990] Time Unavailable for Reporting: Indicates a time and / or time interval during which the content cannot be reported. Time may be relative or absolute. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 22, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0991] Start time: Used to indicate the start time of an unreportable time.

[0992] End time: Used to indicate the end time of the time when reporting is not possible.

[0993] Unavailable measurement mode: Used to indicate a mode that is unavailable for measurement. This may include one-time measurements, periodic measurements, on-demand measurements, event-triggered measurements, etc.

[0994] Unmeasurable measurement period: Used to indicate a measurement period that is unavailable for measurement.

[0995] Unavailable Measurement Time: Used to indicate a measurement time and / or time interval where a measurement cannot be performed. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 22, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[0996] Start time: Used to indicate the start time of a measurement time when a measurement cannot be performed.

[0997] End time: Used to indicate the end time of a measurement period when a measurement cannot be performed.

[0998] Corresponding information that cannot be reported and / or measured: Used to indicate information corresponding to actual accessed beam information that cannot be reported and / or measured. This may include one or more of the following:

[0999] Slice count: The number of slices corresponding to actual accessed beam information that cannot be reported and / or measured.

[1000] Slice ID and / or ID list: A range of slices corresponding to actual accessed beam information that cannot be reported and / or measured. For example, slices corresponding to actual accessed beam information that cannot be reported and / or measured are one or more of the slice ID and / or ID list.

[1001] Cell count: The number of cells corresponding to actual accessed beam information that cannot be reported and / or measured.

[1002] Cell ID and / or ID list: A range of cells corresponding to actual accessed beam information that cannot be reported and / or measured. For example, the cells corresponding to actual accessed beam information that cannot be reported and / or measured are one or more of the cell ID and / or ID list.

[1003] Beam Count: The number of beams corresponding to actual accessed beam information that cannot be reported and / or measured.

[1004] Beam ID and / or ID List: A range of beams corresponding to actual accessed beam information that cannot be reported and / or measured. For example, the beams corresponding to actual accessed beam information that cannot be reported and / or measured are one or more of the Beam ID and / or ID List.

[1005] Number of nodes: The number of nodes corresponding to actual accessed beam information that cannot be reported and / or measured.

[1006] Node ID and / or list of IDs: A range of nodes corresponding to actual accessed beam information that cannot be reported and / or measured. For example, the nodes corresponding to actual accessed beam information that cannot be reported and / or measured are one or more of the node ID and / or list of IDs.

[1007] Trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed: Indicate trigger events and / or conditions corresponding to reports and / or measurements that cannot be performed. If the events and / or conditions triggering this report and / or measurement are satisfied, the report and / or measurement cannot be performed. The events and / or conditions triggering the report include one or more of the following:

[1008] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1009] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1010] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1011] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1012] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1013] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1014] Cause / Reason: Indicates the reason why measurement and / or reporting cannot be performed.

[1015] In some embodiments, the 16th node may report to the 15th node a 24th message containing actual accessed beam information obtained by the 16th node, depending on its circumstances and / or in accordance with a 22nd message containing a request to report actual accessed beam information received from the 15th node. In some embodiments, for example, the 15th node may evaluate whether the predicted beam information is appropriate using the actual accessed beam information. For example, if the actual accessed beam information does not match the predicted beam information, this means that the predicted beam information is inappropriate; if the actual accessed beam information matches the predicted beam information, this means that the predicted beam information is appropriate. In other embodiments, for example, the 15th node may use the actual accessed beam information to support artificial intelligence machine learning functions. For example, the actual accessed beam information may be used as input parameters to train an artificial intelligence machine learning model, which may be a model for predicting beam information or a model for generating handover decisions; Alternatively, the actual accessed beam information can be used to evaluate artificial intelligence machine learning models, for example, to assess whether the model can be continued to be used, whether the model needs to be trained and / or adjusted, etc.

[1016] In some embodiments, the 24th message may include one or more of the following information and / or fields:

[1017] Transmission Node ID: Used to identify the node transmitting the message.

[1018] Receiving Node ID: Used to identify the node receiving the message.

[1019] Measurement and / or Prediction ID: Used to identify the measurement and / or prediction. In some implementations, to associate the report with the request and / or response, this ID may match the measurement and / or prediction ID within the 22nd message and / or the 23rd message.

[1020] Request ID: Used to identify the request corresponding to the report. In some implementations, to associate the report with a request and / or response, this ID may match the request ID in message 22 and / or message 23.

[1021] Terminal ID: Indicates the user corresponding to the reported actual accessed beam information. This may be a terminal ID or a list of terminal IDs.

[1022] Cell ID: Indicates the cell corresponding to the reported actual accessed beam information. This can be a cell ID or a list of cell IDs.

[1023] Beam ID: Indicates the beam corresponding to the reported actual accessed beam information. This can be a beam ID or a list of beam IDs.

[1024] Slice ID: Indicates the slice corresponding to the reported actual accessed beam information. This can be a slice ID or a list of slice IDs.

[1025] Actual accessed beam information: Indicates the reported actual accessed beam information. The actual accessed beam information may include one or more of the following: beam ID, beam access time, beam exit time, in-beam dwell time, etc.

[1026] Applicable / Valid Time Corresponding to Actual Accessed Beam Information: Used to indicate a valid time and / or time interval corresponding to the actual accessed beam information. Time may be relative or absolute time. Time may also be a time or period prior to or after an event. An event may be an event and / or condition that triggers a measurement within Message 22, or an event and / or condition that triggers a report. A time interval may be represented by a timer, a combination of a start time and an end time, a combination of a start time and a duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits indicate the start time and the last n bits indicate the end time. It may also be represented by separate fields including one or more of the following:

[1027] Start Time: Used to indicate the start time of the applicable / valid time.

[1028] End Time: Used to indicate the end time of the applicable / valid time.

[1029] Events and / or conditions triggering this report: Indicates the events and / or conditions triggering this report. The events and / or conditions triggering this report include one or more of the following:

[1030] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1031] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1032] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information, or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1033] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1034] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1035] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1036] Events and / or conditions that trigger this measurement: Indicates the events and / or conditions that trigger this measurement. The events and / or conditions that trigger this measurement include one or more of the following:

[1037] The terminal accesses the target cell. When the terminal accesses the target cell, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1038] A cell switch notification is received. If a message receiving node receives a cell switch notification message, a report may be performed. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1039] The actual accessed beam does not match the received beam information. The received beam information may be generated and / or predicted beam information, or other received beam information. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1040] The terminal accesses the target cell. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1041] The terminal receives a handover command and / or an LTM cell switching command. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1042] A handover occurs. The event and / or condition triggering the report must include one or more of the following settings: event type and event.

[1043] Indicator of whether the actual accessed beam matches the received beam information: Used to indicate whether the actual accessed beam matches the received beam information.

[1044] Example 11

[1045] One aspect of the present disclosure proposes a method for supporting mobility management, which may include: a 17 node transmits a 25 message to a 18 node, which includes a request for the ability to generate and / or predict for 1 information, thereby requesting the 18 node to report the ability to generate and / or predict for 1 information. The 1 information may include one or more of the following: a TA value, a beam, etc.

[1046] In some embodiments, the 25th message may include one or more of t...

Claims

Claim 1 A method performed by a first node in a wireless communication system, comprising: receiving a first message from a second node containing at least one of mobility information or an L3 measurement result associated with a terminal; determining a first timing advance (TA) value based on at least one of the mobility information, the L1 measurement result, or the L3 measurement result associated with the terminal; transmitting a second message to the terminal containing a first TA value used to access a target cell when the terminal performs a handover; and receiving a third message from the second node containing a second TA value used to evaluate whether the first TA value is appropriate. Claim 2 A method according to claim 1, wherein the second TA value is received by the second node from the target node over which the terminal is handed over. Claim 3 A method according to claim 1, further comprising the step of receiving load-related information of an adjacent cell from the second node, wherein the adjacent cell includes a candidate target cell; and the step of making a mobility decision based on the load-related information of the adjacent cell. Claim 4 A method according to paragraph 3, wherein the load-related information of the adjacent cell comprises: load information of the adjacent cell; information indicating a situation in which the load of the adjacent cell is too large; or at least one of information related to the load amount that can be accommodated by the adjacent cell. Claim 5 A method performed by a second node in a wireless communication system, comprising: a step of transmitting to a first node a first message containing at least one of mobility information or an L3 measurement result associated with a terminal, wherein at least one of the mobility information associated with the terminal, the L3 measurement result, or the L1 measurement result is used by the first node to determine a first timing advance (TA) value; and a step of transmitting to the first node a third message containing a second TA value used to evaluate whether the first TA value is appropriate; wherein the first TA value is used to access a target cell when the terminal performs a handover. Claim 6 A method characterized by further including, in claim 5, the step of receiving the second TA value from the target node over which the terminal is handed over. Claim 7 A method according to claim 5, further comprising the step of transmitting to the first node at least one of a fourth message containing load information of an adjacent cell, a fifth message containing information indicating a situation in which the load of the adjacent cell is too large, or a sixth message containing information on the amount of load that can be accommodated by the adjacent cell, wherein the adjacent cell includes a candidate target cell; wherein at least one of the load information of the adjacent cell, the information indicating a situation in which the load of the adjacent cell is too large, or the information on the amount of load that can be accommodated by the adjacent cell is used by the first node to make a mobility decision. Claim 8 A method according to claim 5, further comprising the step of transmitting a seventh message containing information instructing the first node to activate or deactivate a candidate target cell; wherein the information instructing the first node to activate or deactivate the candidate target cell is used by the first node to make a mobility decision. Claim 9 A first node comprising: a transceiver as a first node of a wireless communication system; and a processor connected to the transceiver; wherein the processor is configured to perform a method comprising: receiving a first message from a second node comprising at least one of mobility information or an L3 measurement result associated with a terminal; determining a first timing advance (TA) value based on at least one of the mobility information, an L1 measurement result, or an L3 measurement result associated with the terminal; transmitting a second message to the terminal comprising a first TA value used to access a target cell when the terminal performs a handover; and receiving a third message from the second node comprising a second TA value used to evaluate whether the first TA value is appropriate. Claim 10 In claim 9, the first node is characterized in that the second TA value is received by the second node from the target node over which the terminal is handed over. Claim 11 In claim 9, the method further comprises: receiving load-related information of an adjacent cell from the second node, wherein the adjacent cell includes a candidate target cell; and making a mobility decision based on the load-related information of the adjacent cell; characterized in that the first node further comprises Claim 12 A first node characterized in that, in paragraph 11, the load-related information of the adjacent cell comprises: load information of the adjacent cell; information indicating a situation where the load of the adjacent cell is too large; or information related to the amount of load that can be accommodated by the adjacent cell. Claim 13 A second node of a wireless communication system comprising: a transceiver; and a processor connected to the transceiver; wherein the processor comprises: a step of transmitting to a first node a first message comprising at least one of mobility information or an L3 measurement result associated with a terminal, wherein at least one of the mobility information associated with the terminal, the L3 measurement result, or the L1 measurement result associated with the terminal is used by the first node to determine a first timing advance (TA) value; and a step of transmitting to the first node a third message comprising a second TA value used to evaluate whether the first TA value is appropriate; wherein the first TA value is configured to perform a method in which the terminal is used to access a target cell when performing a handover. Claim 14 In claim 13, the method further comprises the step of receiving the second TA value from the target node over which the terminal is handed over; a second node. Claim 15 In paragraph 13, the method further comprises: transmitting to the first node at least one of a fourth message containing load information of an adjacent cell, a fifth message containing information indicating a situation in which the load of the adjacent cell is too large, or a sixth message containing information on a load amount acceptable by the adjacent cell, wherein the adjacent cell includes a candidate target cell; and a second node characterized in that at least one of the load information of the adjacent cell, the information indicating a situation in which the load of the adjacent cell is too large, or the information on a load amount acceptable by the adjacent cell is used by the first node to make a mobility decision.

Images