Node in wireless communication system and method performed by the same

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure provides a node in a wireless communication system and methods performed by the same. A method performed by a first node in a wireless communication system includes: receiving a first message including at least one of mobility information and an L3 measurement result related to a terminal, from a second node; determining a first timing advance (TA) value based on at least one of the mobility information, an L1 measurement result and the L3 measurement result related to the terminal; transmitting a second message including the first TA value, wherein the first TA value is used for the terminal to access a target cell when performing handover, to the terminal; and receiving a third message including a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate, from the second node.

Description

[Rectified under Rule 91, 31.01.2025]NODE IN WIRELESS COMMUNICATION SYSTEM AND METHOD PERFORMED BY THE SAME

[0001] The present disclosure relates to a technical field of wireless communication, and more specifically, to a node in a wireless communication system and methods performed by the same.

[0002] mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] In order to meet an increasing demand for wireless data communication services since a deployment of 4G communication system, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called “beyond 4G network” or “post LTE system”.

[0009] Wireless communication is one of the most successful innovations in modern history. Recently, a number of subscribers of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, a demand for wireless data services is growing rapidly. In order to meet rapid growth of mobile data services and support new applications and deployments, it is very important to improve efficiency and coverage of wireless interfaces.

[0010] The disclosure relates to a method and an apparatus for solving problems such as delay, resource usage, or signal interference that can occur with regard to mobility management or decision making during handover in a wireless communication system.

[0011] Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, which includes: receiving a third message from a second node, wherein the third message includes mobility information and / or an L3 measurement result related to a user equipment (UE); determining a first timing advance (TA) value based on at least one of the mobility information, an L1 measurement result and the L3 measurement result related to the UE; transmitting a twenty-seventh message to the UE, wherein the twenty-seventh message includes the first TA value, wherein the first TA value is used for the UE to access a target cell when performing handover; and receiving a ninth message from the second node, wherein the ninth message includes a second TA value, wherein the second TA value is used for evaluating 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, which includes: transmitting a third message to a first node, wherein the third message includes mobility information and / or an L3 measurement result related to a user equipment (UE), wherein at least one of the mobility information, the L3 measurement result and an L1 measurement result related to the UE is used for the first node to determine a first timing advance (TA) value; and transmitting a ninth message to the first node, wherein the ninth message includes a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate; wherein the first TA value is used for the UE to access a target cell when performing handover.

[0013] Embodiments of the present disclosure provide a method performed by a user equipment (UE) in a wireless communication system, which includes: transmitting a twenty-eighth message to a first node, wherein the twenty-eighth message includes an L1 measurement result related to the UE; receiving a twenty-seventh message from the first node, wherein the twenty-seventh message includes a first timing advance (TA) value; 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, an L1 measurement result and an L3 measurement result related to the UE.

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

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

[0016] Embodiments of the present disclosure provide a first node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a first node in a wireless communication system according to embodiments of the present disclosure.

[0017] Embodiments of the present disclosure provide a second node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a second node in a wireless communication system according to embodiments of the present disclosure.

[0018] Embodiments of the present disclosure provide a user equipment (UE) in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.

[0019] Embodiments of the present disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, perform methods performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to embodiments of the present disclosure.

[0020] The methods performed by the first node and / or the second node in the wireless communication system provided by the present disclosure can effectively support the nodes and / or the user equipment to perform mobility management or decision making by exchanging information between the nodes and / or the user equipment.

[0021] The above and other aspects, features and advantages of certain embodiments of the present disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0022] FIG. 1 illustrates an exemplary system architecture of System Architecture Evolution (SAE);

[0023] FIG. 2 illustrates an exemplary system architecture according to various embodiments of the present disclosure;

[0024] FIG. 3A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0025] FIG. 3B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0026] FIG. 3C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0027] FIG. 3D illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0028] FIG. 3E illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0029] FIG. 3F illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0030] FIG. 3G illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0031] FIG. 3H illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0032] FIG. 3I illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0033] FIG. 3J illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0034] FIG. 3K illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0035] FIG. 3LA illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0036] FIG. 3LB illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0037] FIG. 3M illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0038] FIG. 3N illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0039] FIG. 3O illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0040] FIG. 3P illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0041] FIG. 3Q illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0042] FIG. 3RA illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0043] FIG. 3RB illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0044] FIG. 4A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0045] FIG. 4B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0046] FIG. 4C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0047] FIG. 4D illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0048] FIG. 4E illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0049] FIG. 5A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0050] FIG. 5B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0051] FIG. 5C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0052] FIG. 6A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0053] FIG. 6B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0054] FIG. 6C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0055] FIG. 7 illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0056] FIG. 8 illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0057] FIG. 9 illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0058] FIG. 10A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0059] FIG. 10B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0060] FIG. 10C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0061] FIG. 10D illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0062] FIG. 10E illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0063] FIG. 10F illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0064] FIG. 11A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0065] FIG. 11B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0066] FIG. 11C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0067] FIG. 11D illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0068] FIG. 11E illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0069] FIG. 11F illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0070] FIG. 11G illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0071] FIG. 11H illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0072] FIG. 11I illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0073] FIG. 11J illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0074] FIG. 12A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0075] FIG. 12B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0076] FIG. 12C illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0077] FIG. 12D illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0078] FIG. 13A illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0079] FIG. 13B illustrates a schematic diagram of an aspect of a method for supporting mobility management according to embodiments of the present disclosure;

[0080] 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;

[0081] 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;

[0082] FIG. 16 illustrates a schematic diagram of a node according to embodiments of the present disclosure; and

[0083] FIG. 17 illustrates a schematic diagram of a user equipment according to embodiments of the present disclosure.

[0084] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0085] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0086] It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

[0087] The term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components. The terms such as “include” and / or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

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

[0089] Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the present disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure.

[0090] Figures discussed below and various embodiments for describing the principles of the present disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0091] FIG. 1 illustrates an exemplary system architecture 100 of system architecture evolution (SAE). User equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides UE with interfaces to access the radio network. A mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE. A serving gateway (SGW) 104 mainly provides functions of user plane, and the MME 103 and the SGW 104 may be in the same physical entity. A packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104. A policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria. A 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). A home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.

[0092] FIG. 2 illustrates an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.

[0093] User equipment (UE) 201 is a terminal device for receiving data. A next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network. An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE. A user plane function entity (UPF) 204 mainly provides functions of user plane. A session management function entity SMF 205 is responsible for session management. A data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.

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

[0095] The fields and / or information described in the present disclosure may be an average value, an instantaneous value, a maximum value, a minimum value, etc., which is not limited herein.

[0096] The fields and / or information mentioned in the present disclosure may refer to uplink, downlink, uplink and downlink, uplink or downlink, etc., which is not limited herein.

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

[0098] In the present disclosure, a failure type and / or problem type may also be referred to as a report type.

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

[0100] In the present disclosure, radio link failure refers to the following two cases: radio link failure and handover failure.

[0101] In the present disclosure, a mobility decision may include one or more of the following: generation of a Timing Advance (TA), generation of a handover decision, and the like.

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

[0103] In the present disclosure, a handover type may include one or more of the following: 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.

[0104] In the present disclosure, “actually used” and “measured” may refer to each other.

[0105] In the present disclosure, “actual use” and “measurement” may refer to each other.

[0106] In the present disclosure, “actual measurement” and “actual use” may refer to each other.

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

[0108] A result and a report may refer to each other in the present disclosure.

[0109] In the present disclosure, a time may be represented by one or more of the following: a timestamp, a time point, a time interval, a timer, a period of time, a time length, a time period / periodicity, a time spacing, etc. Herein, the time length may be a length of time from a certain time point, which may be the current time. A time may be a relative time or an absolute time. In some implementations, a period of time may be represented by separate 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.

[0110] The time involved in the present disclosure, such as start time, end time, predicted start time and predicted end time, etc., may be a relative time or an absolute time.

[0111] In the present disclosure, a TA value obtained in advance and a TA value in an LTM cell switch command may refer to each other.

[0112] In the present disclosure, load, load condition, load information, etc., and Resource Status may refer to each other.

[0113] In the present disclosure, a source node may include one or more of the following: a source master node, a source secondary node, a source serving node, and the like.

[0114] In the present disclosure, a target node may include one or more of the following: 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, and the like.

[0115] In the present disclosure, user equipment (UE) may refer to user, terminal and the like.

[0116] In the present disclosure, event and condition may refer to each other. Trigger event and trigger condition may refer to each other.

[0117] In the present disclosure, measurement may refer to actual measurement, predicted measurement, etc.

[0118] In the present disclosure, parameters may be actually measured parameters, predicted parameters or generated parameters.

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

[0120] In the present disclosure, a change of RRC state may be from an RRC Inactive state or an RRC Idle state to an RRC Connected state, or from an RRC Connected state to an RRC Inactive state or an RRC Idle state, or any transition among an RRC Connected state, an RRC Inactive state and an RRC Idle state.

[0121] In the present disclosure, an actually used TA value means a TA value used and / or applied by the UE when accessing a target cell.

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

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

[0124] In the present disclosure, if a registration request in a request message is Start, it means that the request is to start a new reporting; if the registration request in a request message is End and / or Cancel, it means that the request is to end and / or cancel an existing reporting and / or request; if the registration request in a request message is Addition and / or Update and / or Modification, it means that the request is to add and / or update and / or modify some requested configurations in an existing reporting and / or request, so that updating and reporting are performed according to the added and / or updated and / or modified configurations in the original reporting message.

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

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

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

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

[0129] A measurement result of a serving cell is greater than and / or equal to and / or less than a predetermined threshold, and / or the measurement result of a serving cell is within and / or outside a predetermined interval. The serving cell may also be a beam of the serving cell, a component carrier of the serving cell, a carrier of the serving cell, a Bandwidth Part of the serving cell, a channel of the serving cell (for example, a Licensed channel or an Unlicensed channel), etc. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold, predetermined interval, cell identification, beam identification, component carrier information, carrier information, bandwidth part identification, channel identification, etc. The component carrier information may include one or more of the following: frequency of a component carrier, identification of a component carrier, center frequency of a component carrier, start frequency of a component carrier, end frequency of a component carrier, frequency interval of a component carrier, and the like. The carrier information may include one or more of the following: frequency of a carrier, identification of a carrier, center frequency of a carrier, start frequency of a carrier, end frequency of a carrier, frequency interval of a carrier, etc.

[0130] A measurement result of a neighboring cell is greater than and / or equal to and / or less than a predetermined threshold, and / or the measurement result of a neighboring cell is within and / or outside a predetermined interval. The neighboring cell may also be a beam of the neighboring cell, a component carrier of the neighboring cell, a carrier of the neighboring cell, a Bandwidth Part of the neighboring cell, a channel of the neighboring cell (for example, a Licensed channel or an Unlicensed channel), etc. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold, predetermined interval, cell identification, beam identification, component carrier information, carrier information, bandwidth part identification, channel identification, etc. The component carrier information may include one or more of the following: frequency of a component carrier, identification of a component carrier, center frequency of a component carrier, start frequency of a component carrier, end frequency of a component carrier, frequency interval of a component carrier, and the like. The carrier information may include one or more of the following: frequency of a carrier, identification of a carrier, center frequency of a carrier, start frequency of a carrier, end frequency of a carrier, frequency interval of a carrier, etc.

[0131] A difference between a measurement result of a neighboring cell and a 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 a measurement result of a neighboring cell and a measurement result of a serving cell is within and / or outside a predetermined interval. The cell may also be a beam of the cell, a component carrier of the cell, a carrier of the cell, a Bandwidth Part of the cell, a channel of the cell (for example, a Licensed channel or an Unlicensed channel), etc. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold, predetermined interval, cell identification, beam identification, component carrier information, carrier information, bandwidth part identification, channel identification, etc. The component carrier information may include one or more of the following: frequency of a component carrier, identification of a component carrier, center frequency of a component carrier, start frequency of a component carrier, end frequency of a component carrier, frequency interval of a component carrier, and the like. The carrier information may include one or more of the following: frequency of a carrier, identification of a carrier, center frequency of a carrier, start frequency of a carrier, end frequency of a carrier, frequency interval of a carrier, etc. Herein, the difference between a measurement result of a neighboring cell and a measurement result of a serving cell may be the measurement result of the neighboring cell minus the measurement result of the serving cell, or the measurement result of the serving cell minus the measurement result of the neighboring cell, etc.

[0132] The measurement result of a neighboring cell is better than the measurement result of a serving cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0133] Moving speed is greater than and / or equal to a predetermined threshold. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0134] The location of a UE is within a predetermined scope, and / or the distance between a UE and a node is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold, predetermined interval, etc. The location may be location coordinates, identification of an accessed beam, identification of the serving cell, identification of a visited cell, etc.

[0135] UE RRC state changes. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0136] The event type may be an identification representing an event. When a message receiving node receives an event type, it can know what the event is.

[0137] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0138] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0139] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0140] In the present disclosure, candidate cell, handover candidate cell and candidate target cell, etc., may refer to each other.

[0141] In the present disclosure, a load amount which is predicted to be too large or a load amount that can be received may be one or more of the following: PRB usage ratio, available PRB number, allocated PRB number, scheduling PDCCH CCE usage, Transport Network Layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, Radio Resource Control (RRC) connection number, 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 volume, and Jitter of the various content parameters, etc. They may also be represented by proportion. In some implementations, for example, the load amount that can be received may be a ratio of the current load amount, or the load amount that can be received may be a ratio of a current instantaneous input rate, or the load amount that can be received may be a ratio of a total load amount, etc. In some implementations, for example, the load amount when overload occurs may be a ratio of the current load amount, or the load amount when overload occurs may be a ratio of the instantaneous input rate, or the load amount when overload occurs may be a ratio of a total load amount, or the overloaded load amount may be a ratio of the current load amount, or the overloaded load amount may be a ratio of the instantaneous input rate, or the overloaded load amount may be a ratio of a total load amount.

[0142] In the present disclosure, as for 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, the scope corresponding to the reported content, the scope may be an ID and / or ID list of one or more of the following: slice, service, scenario, node, UE, cell, beam, channel, Protocol Data Unit Session, Data Radio Bearer (DRB), QoS flow, QoS level, etc. The service may be 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 rate, etc., which may be identified by 5QI (5G QoS Identifier), QCI (QoS Class Identifier), etc. The scenarios 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.

[0143] In the present disclosure, messages such as the first message to the twenty-seventh message and the like each may be a MAC CE, an L1 signaling, an RRC message, an Xn message, an X2 message, an F1 message, a E1 message, an NG message, an RRC container, and / or a user plane frame, etc.

[0144] In the embodiments of the present disclosure, in case of handover under the same gNB CU, the source gNB CU and the target gNB CU can be regarded as one gNB CU node.

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

[0146] Example 1

[0147] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a first node transmits a first message containing a user mobility information and / or measurement result request to a second node to request the second node to report user mobility information and / or measurement result (for example, an L3 measurement result). The first node can make mobility decisions based on the obtained user mobility information and / or measurement result, for example, generating and / or predicting a Timing Advance (TA), generating a handover decision, generating and / or predicting access beam information, etc. The handover decision includes: selection of a target node and / or target cell, decision of a handover time, decision of a handover type, etc. The handover type includes: 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 a TA may be implemented by an artificial intelligence machine learning model. The generation and / or prediction of beam information may be implemented by an artificial intelligence machine learning model. The user can directly access a target cell by using the TA generated and / or predicted by the first node without performing a random access procedure. In order 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. The TA that can be generated and / or predicted by the source node and / or the target node will effectively reduce the signaling overhead required for obtaining a TA. The user mobility information and / or measurement result information may be measured information or predicted information.

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

[0149] UE identification (ID): indicates the user corresponding to the requested user mobility information and / or measurement result. It may be a UE ID or a list of UE IDs.

[0150] Transmitting node ID: used to identify the node that transmits the message.

[0151] Receiving node ID: used to identify the node that receives the message.

[0152] Identification of a request for reporting of user mobility information and / or measurement result: used to indicate that the information requests to report the user mobility information and / or measurement result. This field may be represented by a single bit. For example, when the bit is 1, it indicates that the user mobility information and / or measurement result is requested to be reported; and when the bit is 0, it indicates that the user mobility information and / or measurement result is not requested to be reported. Alternatively, when the bit is 0, it indicates that the user mobility information and / or measurement result is requested to be reported; and when the bit is 1, it indicates that the user mobility information and / or measurement result is not requested to be reported.

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

[0154] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0155] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

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

[0157] Reporting registration request: used to indicate the type of a reporting request. For example, it may include start, end, add, update, modify, cancel, etc.

[0158] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0159] Event and / or condition that triggers reporting: when the event and / or condition that triggers reporting is met, reporting is required to be performed.

[0160] Reporting periodicity: used to indicate the interval of a reporting. It may also be a time interval between two adjacent reportings. The time interval may be a maximum time interval or a minimum time interval. The reporting periodicity may also be the prediction time and / or measurement time of the reported information. In an implementation, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is a measurement time and / or a reporting time. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0161] Reporting time of a requested content: used to indicate a time and / or time interval when the content is requested to be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0162] Start time: used to indicate the start time of a reporting time.

[0163] End time: used to indicate the end time of a reporting time.

[0164] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0165] Measurement mode of a requested content: used to indicate a requested content measurement mode. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0166] Event and / or condition that triggers measurement: when the event and / or condition that triggers measurement is met, measurement is required to be performed.

[0167] Measurement period: used to indicate the interval of a periodic measurement.

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

[0169] Start time: used to indicate the start time of a measurement time.

[0170] End time: used to indicate the end time of a measurement time.

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

[0172] Prediction start time: used to indicate a start time of the prediction.

[0173] Prediction end time: used to indicate an end time of the prediction.

[0174] Applicable / valid time of a requested prediction content: used to indicate a time and / or time interval corresponding to a prediction content. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0175] Start time: used to indicate a start time of the applicable / valid time.

[0176] End time: used to indicate an end time of the applicable / valid time.

[0177] Request information: used to indicate the request information for the user mobility information and / or measurement result. It may include one or more of the following:

[0178] Number of slices: the number of slices corresponding to the user mobility information and / or measurement result requested to be reported.

[0179] Slice ID and / or ID list: the scope of slices corresponding to the requested user mobility information and / or measurement result. For example, the slices corresponding to the user mobility information and / or measurement result requested to be reported should be one or more of the slice ID and / or ID list.

[0180] Number of cells: the number of cells corresponding to the user mobility information and / or measurement result requested to be reported.

[0181] Cell ID and / or ID list: the scope of cells corresponding to the requested user mobility information and / or measurement result. For example, the cells corresponding to the user mobility information and / or measurement result requested to be reported should be one or more of the cell ID and / or ID list.

[0182] Number of beams: the number of beams corresponding to the user mobility information and / or measurement result requested to be reported.

[0183] Beam ID and / or ID list: the scope of beams corresponding to the requested user mobility information and / or measurement result. For example, the beams corresponding to user mobility information and / or measurement result requested to be reported should be one or more of the beam ID and / or ID list.

[0184] Number of nodes: the number of nodes corresponding to the user mobility information and / or measurement result requested to be reported.

[0185] Node ID and / or ID list: the scope of nodes corresponding to the requested user mobility information and / or measurement result. For example, the nodes corresponding to the user mobility information and / or measurement result requested to be reported should be one or more of the node ID and / or ID list.

[0186] Measurement and / or prediction ID: used to identify a measurement and / or prediction.

[0187] Request ID: used to identify a request.

[0188] In some implementations, the second node may transmit a second message containing a response for user mobility information and / or measurement result to the first node, so as to inform the first node whether the second node can report user mobility information and / or measurement result, so that the first node can know whether the requested content can be received from the second node subsequently. In some implementations, for example, if the second message received by the first node indicates that the second node can report the user mobility information and / or measurement result, the first node can subsequently receive the user mobility information and / or measurement result reported by the second node, for example, through a subsequent third message. In some other implementations, for example, the first node may also transmit a message for stoping (and / or cancelling) reporting to the second node based on the information indicated in the received second message, for example, to stop (and / or cancel) reporting through the first message.

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

[0190] Transmitting node ID: used to identify the node that transmits the message.

[0191] Receiving node ID: used to identify the node that receives the message.

[0192] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the first message, in order for associating the reporting with the request and / or response.

[0193] Request ID: used to identify a request corresponding to the response. In some implementations, this ID may be consistent with the request ID in the first message, in order for associating the reporting with the request and / or response.

[0194] Acknowledge of a user mobility information and / or measurement result request: used to indicate whether the user mobility information and / or measurement result can be measured and / or reported. The acknowledge of a user mobility information and / or measurement result request may be a bit indicating whether the request can be measured and / or reported.

[0195] UE ID for which reporting can be performed: ID(s) of user(s) for which user mobility information and / or measurement result can be measured and / or reported. It may be an ID or an ID list.

[0196] Cell ID for which reporting can be performed: ID(s) of cell(s) for which user mobility information and / or measurement result can be measured and / or reported. It may be an ID or an ID list.

[0197] Beam ID for which reporting can be performed: ID(s) of beam(s) for which user mobility information and / or measurement result can be measured and / or reported. It may be an ID or an ID list.

[0198] Slice ID for which reporting can be performed: ID(s) of slice(s) for which user mobility information and / or measurement result can be measured and / or reported. It may be an ID or an ID list.

[0199] Content that can be reported: used to indicate the content that can be reported, which may include one or more of the following:

[0200] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0201] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0202] Content that can be predicted: used to indicate the content that can be predicted, which may include one or more of the following:

[0203] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0204] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0205] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0206] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0207] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0208] Start time: used to indicate the start time of the time available for reporting.

[0209] End time: used to indicate the end time of the time available for reporting.

[0210] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0211] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[0212] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0213] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[0214] End time: used to indicate the end time of a measurement time when measurement can be performed.

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

[0216] Prediction start time: used to indicate the start time when prediction can be performed.

[0217] Prediction end time: used to indicate the end time when prediction can be performed.

[0218] Applicable / valid time of corresponding prediction content that can be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that can be predicted. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0219] Start time: used to indicate the start time of a valid time available for prediction.

[0220] End time: used to indicate the end time of a valid time available for prediction.

[0221] Corresponding information that can be reported: used to indicate information corresponding to the user mobility information and / or measurement result that can be reported. It may include one or more of the following:

[0222] Number of slices: the number of slices corresponding to user mobility information and / or measurement result that can be reported.

[0223] Slice ID and / or ID list: the scope of slices corresponding to user mobility information and / or measurement result that can be reported. For example, the slices corresponding to user mobility information and / or measurement result that can be reported are one or more of slice ID and / or ID list.

[0224] Number of cells: the number of cells corresponding to user mobility information and / or measurement result that can be reported.

[0225] Cell ID and / or ID list: the scope of cells corresponding to user mobility information and / or measurement result that can be reported. For example, the cells corresponding to user mobility information and / or measurement result that can be reported are one or more of the cell ID and / or ID list.

[0226] Number of beams: the number of beams corresponding to user mobility information and / or measurement result that can be reported.

[0227] Beam ID and / or ID list: the scope of beams corresponding to user mobility information and / or measurement result that can be reported. For example, the beams corresponding to user mobility information and / or measurement result that can be reported are one or more of the beam ID and / or ID list.

[0228] Number of nodes: the number of nodes corresponding to user mobility information and / or measurement result that can be reported.

[0229] Node ID and / or ID list: the scope of nodes corresponding to user mobility information and / or measurement result that can be reported. For example, the nodes corresponding to user mobility information and / or measurement result that can be reported are one or more of the node ID and / or ID list.

[0230] Event and / or condition that triggers a reporting which can be performed: indicates a trigger event and / or condition that triggers a reporting which can be performed. When the event and / or condition that triggers the reporting is met, the reporting can be performed.

[0231] Event and / or condition that triggers a measurement which can be performed: indicates a trigger event and / or condition that triggers a measurement which can be performed. When the event and / or condition that triggers the measurement is met, the measurement can be performed.

[0232] UE ID for which measurement and / or reporting cannot be performed: ID(s) of user(s) for which user mobility information and / or measurement result cannot be measured and / or reported. It may be an ID or an ID list.

[0233] Cell ID for which measurement and / or reporting cannot be performed: ID(s) of cell(s) for which user mobility information and / or measurement result cannot be measured and / or reported. It may be an ID or an ID list.

[0234] Beam ID for which measurement and / or reporting cannot be performed: ID(s) of beam(s) for which user mobility information and / or measurement result cannot be measured and / or reported. It may be an ID or an ID list.

[0235] Slice ID for which measurement and / or reporting cannot be performed: ID(s) of slice(s) for which user mobility information and / or measurement result cannot be measured and / or reported. It may be an ID or an ID list.

[0236] Content that cannot be reported: used to indicate the content that cannot be reported, which may include one or more of the following:

[0237] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0238] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0239] Content that cannot be predicted: used to indicate the content that cannot be predicted, which may include one or more of the following:

[0240] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0241] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0242] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0243] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0244] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0245] Start time: used to indicate the start time of the time unavailable for reporting.

[0246] End time: used to indicate the end time of the time unavailable for reporting.

[0247] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0248] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[0249] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[0251] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[0252] Time unavailable for prediction: used to indicate a time and / or time interval when prediction can not be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0253] Prediction start time: used to indicate the start time when prediction cannot be performed.

[0254] Prediction end time: used to indicate the end time when prediction cannot be performed.

[0255] Applicable / valid time of corresponding prediction content that cannot be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that cannot be predicted. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0256] Start time: used to indicate the start time of a valid time unavailable prediction.

[0257] End time: used to indicate the end time of a valid time unavailable for prediction.

[0258] Corresponding information that cannot be reported: used to indicate information corresponding to the user mobility information and / or measurement result that cannot be reported. It may include one or more of the following:

[0259] Number of slices: the number of slices corresponding to user mobility information and / or measurement result that cannot be reported.

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

[0261] Number of cells: the number of cells corresponding to user mobility information and / or measurement result that cannot be reported.

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

[0263] Number of beams: the number of beams corresponding to user mobility information and / or measurement result that cannot be reported.

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

[0265] Number of nodes: the number of nodes corresponding to user mobility information and / or measurement result that cannot be reported.

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

[0267] Event and / or condition that triggers a reporting which cannot be performed: indicates a trigger event and / or condition that triggers a reporting which cannot be performed. When the event and / or condition that triggers reporting is met, the report cannot be performed.

[0268] Event and / or condition that trigger a measurement which cannot be performed: indicates a trigger event and / or condition that triggers a measurement which cannot be performed. When the event and / or condition that triggers the measurement is met, the measurement cannot be performed.

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

[0270] In some implementations, the second node may transmit a third message containing user mobility information and / or measurement result to the first node according to its own situation and / or according to the first message containing a user mobility information and / or measurement result request received from the first node. In some implementations, for example, the first node can make mobility decisions based on the obtained user mobility information and / or measurement result, for example, generating and / or predicting a Timing Advance (TA), generating a handover decision, generating and / or predicting access beam information, etc. The handover decision includes: selection of a target node and / or target cell, decision of a handover time, decision of a handover type, etc. The handover type includes: 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 a TA may be implemented by an artificial intelligence machine learning model. The generation and / or prediction of beam information may be implemented by an artificial intelligence machine learning model. The first node can obtain a TA for a user to access a target cell based on the obtained user mobility information and / or measurement result. The first node may transmit the TA to the user for the user to access the target cell in a handover process, or the first node may transmit it to other nodes and other nodes transmit it to the user for the user to access the target cell in a handover process. This can effectively reduce the signaling overhead required for obtaining a TA. The user can directly access a target cell by using the TA generated and / or predicted by the first node without performing a random access procedure. In order 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. The TA that can be generated and / or predicted by the source node and / or the target node will effectively reduce the signaling overhead required for obtaining a TA. The user mobility information and / or measurement result information may be measured information or predicted information.

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

[0272] UE identification (ID): indicates the user corresponding to the user mobility information and / or measurement result. It may be a UE ID or a list of UE IDs.

[0273] Transmitting node ID: used to identify the node that transmits the message.

[0274] Receiving node ID: used to identify the node that receives the message.

[0275] User mobility information: indicates the mobility information and / or mobility information list of a user. The mobility information of a user may include one or more of the following: speed, moving direction, location information, location coordinates, resident cell, Visited Cell, Time of Stay, Time of Visit, time information, etc.

[0276] Measurement result: indicates a measurement result of a user. The measurement results may include RSRP, RSRQ, SINR, target cell identification, beam identification, time information, etc. The measurement result may be an L1 measurement result or an L3 measurement result.

[0277] Event and / or condition that triggered the reporting: indicates the event and / or condition that triggered the reporting.

[0278] Event and / or condition that triggered the measurement: indicates the event and / or condition that triggered the measurement.

[0279] Applicable / valid time corresponding to prediction information: used to indicate a time and / or time interval corresponding to a prediction content. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0280] Start time: used to indicate a start time of the applicable / valid time.

[0281] End time: used to indicate an end time of the applicable / valid time.

[0282] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the first message and / or the second message, in order for associating the reporting with the request and / or response.

[0283] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the first message and / or the second message, in order for associating the reporting with the request and / or response.

[0284] Example 2

[0285] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a third node transmits a fourth message containing a request for reporting a TA value to a fourth node to request the fourth node to report a TA value. The TA value may be a TA value calculated by a mathematical method and / or obtained by an artificial intelligence machine learning model. In some implementations, for example, the third node may transmit the TA value obtained from the fourth node to a UE when the UE needs to be handed over, and the UE may perform accessing directly by using the TA value, so as to avoid an interruption caused by handover and effectively reduce the signaling required for obtaining a TA.

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

[0287] Transmitting node ID: used to identify the node that transmits the message.

[0288] Receiving node ID: used to identify the node that receives the message.

[0289] Measurement and / or prediction ID: used to identify a measurement and / or prediction.

[0290] Request ID: used to identify a request.

[0291] UE identification (ID): indicates the user corresponding to the TA value requested to be reported. It may be a UE ID or a list of UE IDs.

[0292] Cell ID: indicates the cell corresponding to TA value requested to be reported. It may be a cell ID or a list of cell IDs.

[0293] Identification of a request for a TA value for a candidate cell: which indicates a request for a message receiving node to report a TA value for a candidate cell.

[0294] Beam ID: indicates the beam corresponding to the TA value requested to be reported. It may be a beam ID or a list of beam IDs.

[0295] Identification of a request for a TA value corresponding to a beam in a candidate cell: which indicates a request for a message receiving node to report a TA value corresponding to a beam in a candidate cell.

[0296] Slice ID: indicates the slice corresponding to the TA value requested to be reported. It may be a slice ID or a list of slice IDs.

[0297] Identification of a request for a TA value corresponding to a slice in a candidate cell: which indicates a request for a message receiving node to report a TA value corresponding to a slice in a candidate cell.

[0298] Identification of a request for a TA value: used to indicate that this information is to request the reporting of a TA value. This field may be represented by a single bit. For example, when the bit is 1, it indicates that a TA value is requested to be reported; and when the bit is 0, it indicates that a TA value is not requested to be reported. Alternatively, when the bit is 0, it indicates that a TA value is requested to be reported; and when the bit is 1, it indicates that a TA value is not requested to be reported.

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

[0300] Reporting registration request: used to indicate the type of a reporting request. For example, it may include start, end, add, update, modify, cancel, etc.

[0301] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0302] Event and / or condition that triggers reporting: when the event and / or condition that triggers reporting is met, reporting is required to be performed.

[0303] Reporting periodicity: used to indicate the interval of a periodic reporting. The reporting periodicity may also be the prediction time and / or measurement time of the reported information. In an implementation, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is a measurement time and / or a reporting time.

[0304] Reporting time of a requested content: used to indicate a time and / or time interval when the content is requested to be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0305] Start time: used to indicate the start time of a reporting time.

[0306] End time: used to indicate the end time of a reporting time.

[0307] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0308] Measurement mode of a requested content: used to indicate a requested content measurement mode. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0309] Event and / or condition that triggers measurement: when the event and / or condition that triggers measurement is met, measurement is required to be performed.

[0310] Measurement period: used to indicate the interval of a periodic measurement.

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

[0312] Start time: used to indicate the start time of a measurement time.

[0313] End time: used to indicate the end time of a measurement time.

[0314] Applicable / valid time of a requested content: used to indicate a valid time and / or time interval of a requested content. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0315] Start time: used to indicate a start time of the applicable / valid time.

[0316] End time: used to indicate an end time of the applicable / valid time.

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

[0318] Prediction start time: used to indicate a start time of the prediction.

[0319] Prediction end time: used to indicate an end time of the prediction.

[0320] Applicable / valid time of a requested prediction content: used to indicate a time and / or time interval corresponding to a prediction content. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0321] Start time: used to indicate a start time of the applicable / valid time.

[0322] End time: used to indicate an end time of the applicable / valid time.

[0323] Request information: used to indicate the request information for TA value reporting. It may include one or more of the following:

[0324] Number of cells: the number of cells corresponding to the TA value requested to be reported.

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

[0326] Number of nodes: the number of nodes corresponding to the TA value requested to be reported.

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

[0328] Number of beams: the number of beams corresponding to the TA value requested to be reported. The beam may be an SSB beam or other beams.

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

[0330] Number of slices: the number of slices corresponding to the TA value requested to be reported.

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

[0332] Number of TA values: the number of TA values requested to be reported. It may also be a maximum and / or minimum number of TA values requested to be reported.

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

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

[0335] Transmitting node ID: used to identify the node that transmits the message.

[0336] Receiving node ID: used to identify the node that receives the message.

[0337] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the fourth message, in order for associating the reporting with the request and / or response.

[0338] Request ID: used to identify a request corresponding to the response. In some implementations, this ID may be consistent with the request ID in the fourth message, in order for associating the reporting with the request and / or response.

[0339] Acknowledge of a TA value request: used to indicate whether a TA value can be measured and / or reported and / or predicted. The acknowledge of a TA value request may be a bit indicating whether the request can be measured and / or reported and / or predicted.

[0340] UE ID for which reporting can be performed: ID(s) of user(s) for which a TA value can be measured and / or reported. It may be an ID or an ID list.

[0341] Cell ID for which reporting can be performed: ID(s) of cell(s) for which a TA value can be measured and / or reported. It may be an ID or an ID list.

[0342] Beam ID for which reporting can be performed: ID(s) of beam(s) for which a TA value can be measured and / or reported. It may be an ID or an ID list.

[0343] Slice ID for which reporting can be performed: ID(s) of slice(s) for which a TA value can be measured and / or reported. It may be an ID or an ID list.

[0344] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0345] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0346] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0347] Start time: used to indicate the start time of the time available for reporting.

[0348] End time: used to indicate the end time of the time available for reporting.

[0349] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0350] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[0351] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0352] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[0353] End time: used to indicate the end time of a measurement time when measurement can be performed.

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

[0355] Prediction start time: used to indicate the start time when prediction can be performed.

[0356] Prediction end time: used to indicate the end time when prediction can be performed.

[0357] Applicable / valid time of corresponding prediction content that can be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that can be predicted. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0358] Start time: used to indicate the start time of a valid time available for prediction.

[0359] End time: used to indicate the end time of a valid time available for prediction.

[0360] Corresponding information that can be reported and / or measured and / or predicted: used to indicate information corresponding to the TA value that can be reported and / or measured and / or predicted. It may include one or more of the following:

[0361] Number of slices: the number of slices corresponding to the TA value that can be reported and / or measured and / or predicted.

[0362] Slice ID and / or ID list: the scope of slices corresponding to the TA value that can be reported and / or measured and / or predicted. For example, the slices corresponding to the TA value that can be reported and / or measured and / or predicted are one or more of the slice ID and / or ID list.

[0363] Number of cells: the number of cells corresponding to the TA value that can be reported and / or measured and / or predicted.

[0364] Cell ID and / or ID list: the scope of cells corresponding to the TA value that can be reported and / or measured and / or predicted. For example, the cells corresponding to TA value that can be reported and / or measured and / or predicted are one or more of the cell ID and / or ID list.

[0365] Number of beams: the number of beams corresponding to the TA value that can be reported and / or measured and / or predicted.

[0366] Beam ID and / or ID list: the scope of beams corresponding to the TA value that can be reported and / or measured and / or predicted. For example, the beams corresponding to TA value that can be reported and / or measured and / or predicted are one or more of the beam ID and / or ID list.

[0367] Number of nodes: the number of nodes corresponding to the TA value that can be reported and / or measured and / or predicted.

[0368] Node ID and / or ID list: the scope of nodes corresponding to the TA value that can be reported and / or measured and / or predicted. For example, the nodes corresponding to the TA value that can be reported and / or measured and / or predicted are one or more of the node ID and / or ID list.

[0369] Number of TA values: the number of TA values that can be reported and / or measured and / or predicted. It may also be a maximum and / or minimum number of TA values that can be reported and / or measured and / or predicted.

[0370] Event and / or condition that triggers a reporting which can be performed: indicates a trigger event and / or condition that triggers a reporting which can be performed. When the event and / or condition that triggers the reporting is met, the reporting can be performed.

[0371] Event and / or condition that triggers a measurement which can be performed: indicates a trigger event and / or condition that triggers a measurement which can be performed. When the event and / or condition that triggers the measurement is met, the measurement can be performed.

[0372] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0373] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0374] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0375] Start time: used to indicate the start time of the time unavailable for reporting.

[0376] End time: used to indicate the end time of the time unavailable for reporting.

[0377] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0378] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[0379] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[0381] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[0382] Time unavailable for prediction: used to indicate a time and / or time interval when prediction can not be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0383] Prediction start time: used to indicate the start time when prediction cannot be performed.

[0384] Prediction end time: used to indicate the end time when prediction cannot be performed.

[0385] Applicable / valid time of corresponding prediction content that cannot be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that cannot be predicted. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0386] Start time: used to indicate the start time of a valid time unavailable prediction.

[0387] End time: used to indicate the end time of a valid time unavailable for prediction.

[0388] Corresponding information that cannot be reported and / or measured and / or predicted: used to indicate information corresponding to the TA value that cannot be reported and / or measured and / or predicted. It may include one or more of the following:

[0389] Number of slices: the number of slices corresponding to the TA value that cannot be reported and / or measured and / or predicted.

[0390] Slice ID and / or ID list: the scope of slices corresponding to the TA value that cannot be reported and / or measured and / or predicted. For example, the slices corresponding to the TA value that cannot be reported and / or measured and / or predicted are one or more of the slice ID and / or ID list.

[0391] Number of cells: the number of cells corresponding to the TA value that cannot be reported and / or measured and / or predicted.

[0392] Cell ID and / or ID list: the scope of cells corresponding to the TA value that cannot be reported and / or measured and / or predicted. For example, the cells corresponding to TA value that cannot be reported and / or measured and / or predicted are one or more of the cell ID and / or ID list.

[0393] Number of beams: the number of beams corresponding to the TA value that cannot be reported and / or measured and / or predicted.

[0394] Beam ID and / or ID list: the scope of beams corresponding to the TA value that cannot be reported and / or measured and / or predicted. For example, the beams corresponding to TA value that cannot be reported and / or measured and / or predicted are one or more of the beam ID and / or ID list.

[0395] Number of nodes: the number of nodes corresponding to the TA value that cannot be reported and / or measured and / or predicted.

[0396] Node ID and / or ID list: the scope of nodes corresponding to the TA value that cannot be reported and / or measured and / or predicted. For example, the nodes corresponding to the TA value that cannot be reported and / or measured and / or predicted are one or more of the node ID and / or ID list.

[0397] Number of TA values: the number of TA values that cannot be reported and / or measured and / or predicted. It may also be a maximum and / or minimum number of TA values that cannot be reported and / or measured and / or predicted.

[0398] Event and / or condition that triggers a reporting which cannot be performed: indicates a trigger event and / or condition that triggers a reporting which cannot be performed. When the event and / or condition that triggers reporting is met, the report cannot be performed.

[0399] Event and / or condition that trigger a measurement which cannot be performed: indicates a trigger event and / or condition that triggers a measurement which cannot be performed. When the event and / or condition that triggers the measurement is met, the measurement cannot be performed.

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

[0401] The fourth node reports a sixth message containing a TA value obtained and / or generated by the fourth node to the third node according to its own situation and / or according to the fourth message containing the request for reporting a TA value received from the third node. In some implementations, for example, the third node may transmit the TA value obtained from the fourth node to a UE when the UE needs to be handed over, and the UE may perform accessing directly by using the TA value, so as to avoid an interruption caused by handover and effectively reduce the signaling required for obtaining a TA. The generation and / or prediction of a TA may be implemented by an artificial intelligence machine learning model. The user can directly access a target cell by using the generated and / or predicted TA obtained by the third node and / or the fourth node without performing a random access procedure. In order 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. The TA that can be generated and / or predicted by the source node and / or the target node will effectively reduce the signaling overhead required for obtaining a TA.

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

[0403] Transmitting node ID: used to identify the node that transmits the message.

[0404] Receiving node ID: used to identify the node that receives the message.

[0405] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the fourth message and / or the fifth message, in order for associating the reporting with the request and / or response.

[0406] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the fourth message and / or the fifth message, in order for associating the reporting with the request and / or response.

[0407] UE ID: indicates the user corresponding to the reported TA value. It may be a UE ID or a list of UE IDs.

[0408] Cell ID: indicates the cell corresponding to the reported TA value. It may be a cell ID or a list of cell IDs.

[0409] Beam ID: indicates the beam corresponding to the reported TA value. It may be a beam ID or a list of beam IDs.

[0410] Slice ID: indicates the slice corresponding to the reported TA value. It may be a slice ID or a list of slice IDs.

[0411] TA value: indicates the reported TA value.

[0412] Applicable / valid time corresponding to a TA value: used to indicate a valid time and / or time interval corresponding to a TA value. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0413] Start time: used to indicate a start time of the applicable / valid time.

[0414] End time: used to indicate an end time of the applicable / valid time.

[0415] Event and / or condition that triggered this reporting: indicates an event and / or condition that triggered this reporting.

[0416] Event and / or condition that triggered this measurement: indicates an event and / or condition that triggered this measurement.

[0417] Applicable / valid time corresponding to a predicted TA value: used to indicate a valid time and / or time interval corresponding to a predicted TA value. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0418] Start time: used to indicate a start time of the applicable / valid time.

[0419] End time: used to indicate an end time of the applicable / valid time.

[0420] If the receiving node of the sixth message is a UE, the UE can access a target cell based on the corresponding TA value within the valid time corresponding to the (predicted) TA value. If the UE finds that the obtained TA value and / or valid time thereof are not applicable when accessing the target node, it obtains a TA to access the target cell through random access. In an implementation, the method can be applied to conditional handover, where the node may transmit a (predicted) TA value (or a list of TA values) and / or the corresponding valid time (or a list of valid times) to the UE. When an execution condition and / or event for conditional handover corresponding to a target cell is met, the UE can 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 the valid time corresponding to the (predicted) TA value.

[0421] Example 3

[0422] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a fifth node transmits a seventh message containing a request for reporting an actually used TA value to a sixth node, so as to request the sixth node to report the requested actually used TA value. In some implementations, for example, the fifth node can use the actually used TA value to evaluate whether a generated and / or predicted TA value is appropriate. For example, if the actually used TA value is inconsistent with the generated and / or predicted TA value and / or the difference between the actually used TA value and the generated and / or predicted TA value is greater than and / or equal to a predetermined threshold, it means that the generated and / or predicted TA value is inappropriate; or if the actually used TA value is consistent with the generated and / or predicted TA value and / or the difference between the actually used TA value and the generated and / or predicted TA value is less than and / or equal to a predetermined threshold, it means that the generated and / or predicted TA value is appropriate. In another implementation, for example, the fifth node may use the actually used TA value to support an artificial intelligence machine learning function, for example, it may be used as an input parameter to train an artificial intelligence machine learning model, which may be a model for generating and / or predicting a TA value or a model for generating a handover decision. Alternatively, the actually used TA value may also be used to evaluate an artificial intelligence machine learn model, for example, to evaluate whether the model can continue to be used, whether the model needs to be train and / or adjusted, etc.

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

[0424] Transmitting node ID: used to identify the node that transmits the message.

[0425] Receiving node ID: used to identify the node that receives the message.

[0426] Measurement ID: used to identify this measurement.

[0427] Request ID: used to identify a request.

[0428] UE identification (ID): indicates the user corresponding to the actually used TA value requested to be reported. It may be a UE ID or a list of UE IDs.

[0429] Cell ID: indicates the cell corresponding to the actually used TA value requested to be reported. It may be a cell ID or a list of cell IDs.

[0430] Beam ID: indicates the beam corresponding to the actually used TA value requested to be reported. It may be a beam ID or a list of beam IDs.

[0431] Slice ID: indicates the slice corresponding to the actually used TA value requested to be reported. It may be a slice ID or a list of slice IDs.

[0432] Identification of a request for reporting of an actually used TA value: which indicates a request for a message receiving node to report an actually used TA value.

[0433] Identification of a request for an actually used TA value: indicates that the message is to request the reporting of an actually used TA value. This field may be represented by a single bit. For example, when the bit is 1, it indicates that the actually used TA value is requested to be reported; and when the bit is 0, it indicates that the actually used TA value is not requested to be reported. Alternatively, when the bit is 0, it indicates that the actually used TA value is requested to be reported; and when the bit is 1, it indicates that the actually used TA value is not requested to be reported.

[0434] Identification of a request for reporting of whether access is performed based on a TA value in an LTM cell switch command: used to indicate that the message is to request the reporting of whether access is performed based on a TA value in an LTM cell switch command. This field may be represented by a single bit. For example, when the bit is 1, it indicates that whether access is performed based on a TA value in an LTM cell switch command is requested to be reported; and when the bit is 0, it indicates that whether access is performed based on a TA value in an LTM cell switch command is not requested to be reported. Alternatively, when the bit is 0, it it indicates that whether access is performed based on a TA value in an LTM cell switch command is requested to be reported; and when the bit is 1, it indicates that whether access is performed based on a TA value in an LTM cell switch command is not requested to be reported.

[0435] Indication of a request for reporting of whether an actually used TA value is consistent with a received TA value: used to indicate that the message is to request the reporting of information about whether an actually used TA value is consistent with a received TA value.

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

[0437] Reporting registration request: used to indicate the type of a reporting request. For example, it may include start, end, add, update, modify, cancel, etc.

[0438] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0439] Event and / or condition that triggers reporting: when the event and / or condition that triggers reporting is met, reporting is required to be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0440] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0441] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0442] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0443] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0444] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0445] Reporting periodicity: used to indicate the interval of a reporting. It may also be a time interval between two adjacent reportings. The time interval may be a maximum time interval or a minimum time interval. The reporting periodicity may also be the prediction time and / or measurement time of the reported information. In an implementation, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is a measurement time and / or a reporting time. In some implementations, the reporting periodicity is used to indicate a time interval of a periodic reporting.

[0446] Reporting time of a requested content: used to indicate a time and / or time interval when the content is requested to be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0447] Start time: used to indicate the start time of a reporting time.

[0448] End time: used to indicate the end time of a reporting time.

[0449] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0450] Measurement mode of a requested content: used to indicate a requested content measurement mode. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0451] Event and / or condition that triggers measurement: when the event and / or condition that triggers measurement is met, measurement is required to be performed. The event and / or condition that triggers measurement includes one or more of the following:

[0452] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0453] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0454] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0455] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0456] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0457] Measurement period: used to indicate an interval for measurement. It may also be a time interval between two adjacent measurements. The 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 an implementation, for example, if there is no content in this field, a single measurement is indicated, and the time of the single measurement is the measurement time and / or the reporting time. In some implementations, the measurement period is used to indicate a time interval of a periodic measurement.

[0458] Measurement time for a requested content: used to indicate a time and / or time interval for the measurement of a requested content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0459] Start time: used to indicate the start time of a measurement time.

[0460] End time: used to indicate the end time of a measurement time.

[0461] Applicable / valid time of a requested content: used to indicate a valid time and / or time interval of a requested content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0462] Start time: used to indicate a start time of the applicable / valid time.

[0463] End time: used to indicate an end time of the applicable / valid time.

[0464] Request information: used to indicate the request information for reporting of an actually used TA value. It may include one or more of the following:

[0465] Number of cells: the number of cells corresponding to the actually measured TA value requested to be reported.

[0466] Cell ID and / or ID list: the cell corresponding to the actually measured TA value requested. For example, the cells corresponding to the actually measured TA value requested to be reported should be one or more of the cell ID and / or ID list.

[0467] Number of nodes: the number of nodes corresponding to the actually measured TA value requested to be reported.

[0468] Node ID and / or ID list: the node corresponding to the actually measured TA value requested. For example, the nodes corresponding to the actually measured TA value requested to be reported should be one or more of the node ID and / or ID list.

[0469] Number of beams: the number of beams corresponding to the actually measured TA value requested to be reported. The beam may be an SSB beam or other beams.

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

[0471] Number of slices: the number of slices corresponding to the actually measured TA value requested to be reported.

[0472] Slice ID and / or ID list: the slice corresponding to the actually measured TA value requested. For example, the slices corresponding to the actually measured TA value requested to be reported should be one or more of the slice ID and / or ID list.

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

[0474] The sixth node transmits an eighth message containing a reporting response of an actually measured TA value to the fifth node, so as to inform the fifth node whether the sixth node can report the actually measured TA value, so that the fifth node can know whether the content requested to be reported can be received from the sixth node subsequently. In some implementations, 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 can subsequently receive the actually measured TA value reported by the sixth node, for example, through a subsequent ninth message. In some other implementations, for example, the fifth node may also transmit a message for stoping (and / or cancelling) reporting to the sixth node based on the information indicated in the received eighth message, for example, to stop (and / or cancel) reporting through the seventh message.

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

[0476] Transmitting node ID: used to identify the node that transmits the message.

[0477] Receiving node ID: used to identify the node that receives the message.

[0478] Measurement ID: used to identify this measurement. In some implementations, this ID may be consistent with the measurement ID in the seventh message, in order for associating the reporting with the request and / or response.

[0479] Request ID: used to identify a request corresponding to the response. In some implementations, this ID may be consistent with the request ID in the seventh message, in order for associating the reporting with the request and / or response.

[0480] Acknowledge of a request for an actually measured TA value: used to indicate whether a TA value can be measured and / or reported. The acknowledge of a request for an actually measured TA value may be a bit indicating whether the request can be measured and / or reported.

[0481] UE ID for which reporting can be performed: ID(s) of user(s) for which an actually measured TA value can be measured and / or reported. It may be an ID or an ID list.

[0482] Cell ID for which reporting can be performed: ID(s) of cell(s) for which an actually measured TA value can be measured and / or reported. It may be an ID or an ID list.

[0483] Beam ID for which reporting can be performed: ID(s) of beam(s) for which an actually measured TA value can be measured and / or reported. It may be an ID or an ID list.

[0484] Slice ID for which reporting can be performed: ID(s) of slice(s) for which an actually measured TA value can be measured and / or reported. It may be an ID or an ID list.

[0485] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0486] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0487] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0488] Start time: used to indicate the start time of the time available for reporting.

[0489] End time: used to indicate the end time of the time available for reporting.

[0490] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0491] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[0492] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0493] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[0494] End time: used to indicate the end time of a measurement time when measurement can be performed.

[0495] Corresponding information that can be reported and / or measured: used to indicate information corresponding to the actually measured TA value that can be reported and / or measured. It may include one or more of the following:

[0496] Number of slices: the number of slices corresponding to the actually measured TA value that can be reported and / or measured.

[0497] Slice ID and / or ID list: the scope of slices corresponding to the actually measured TA value that can be reported and / or measured. For example, the slices corresponding to the actually measured TA value that can be reported and / or measured are one or more of the slice ID and / or ID list.

[0498] Number of cells: the number of cells corresponding to the actually measured TA value that can be reported and / or measured.

[0499] Cell ID and / or ID list: the scope of cells corresponding to the actually measured TA value that can be reported and / or measured. For example, the cells corresponding to the actually measured TA value that can be reported and / or measured are one or more of the cell ID and / or ID list.

[0500] Number of beams: the number of beams corresponding to the actually measured TA value that can be reported and / or measured.

[0501] Beam ID and / or ID list: the scope of beams corresponding to the actually measured TA value that can be reported and / or measured. For example, the beams corresponding to the actually measured TA value that can be reported and / or measured are one or more of the beam ID and / or ID list.

[0502] Number of nodes: the number of nodes corresponding to the actually measured TA value that can be reported and / or measured.

[0503] Node ID and / or ID list: the scope of nodes corresponding to the actually measured TA value that can be reported and / or measured. For example, the nodes corresponding to the actually measured TA value that can be reported and / or measured are one or more of the node ID and / or ID list.

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

[0505] Trigger event and / or condition corresponding to a reporting and / or measurement that can be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that can be performed. When the event and / or condition that triggers reporting and / or measurement are met, reporting and / or measurement can be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0506] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0507] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0508] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0509] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0510] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0511] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0512] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0513] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0514] Start time: used to indicate the start time of the time unavailable for reporting.

[0515] End time: used to indicate the end time of the time unavailable for reporting.

[0516] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0517] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[0518] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the seventh message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[0520] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[0521] Corresponding information that cannot be reported and / or measured: used to indicate information corresponding to the actually measured TA value that cannot be reported and / or measured. It may include one or more of the following:

[0522] Number of slices: the number of slices corresponding to the actually measured TA value that cannot be reported and / or measured.

[0523] Slice ID and / or ID list: the scope of slices corresponding to the actually measured TA value that cannot be reported and / or measured. For example, the slices corresponding to the actually measured TA value that cannot be reported and / or measured are one or more of the slice ID and / or ID list.

[0524] Number of cells: the number of cells corresponding to the actually measured TA value that cannot be reported and / or measured.

[0525] Cell ID and / or ID list: the scope of cells corresponding to the actually measured TA value that cannot be reported and / or measured. For example, the cells corresponding to the actually measured TA value that cannot be reported and / or measured are one or more of the cell ID and / or ID list.

[0526] Number of beams: the number of beams corresponding to the actually measured TA value that cannot be reported and / or measured.

[0527] Beam ID and / or ID list: the scope of beams corresponding to the actually measured TA value that cannot be reported and / or measured. For example, the beams corresponding to the actually measured TA value that cannot be reported and / or measured are one or more of the beam ID and / or ID list.

[0528] Number of nodes: the number of nodes corresponding to the actually measured TA value that cannot be reported and / or measured.

[0529] Node ID and / or ID list: the scope of nodes corresponding to the actually measured TA value that cannot be reported and / or measured. For example, the nodes corresponding to the actually measured TA value that cannot be reported and / or measured are one or more of the node ID and / or ID list.

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

[0531] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers reporting and / or measurement are met, the reporting and / or measurement cannot be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0532] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0533] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0534] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0535] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0536] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

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

[0538] The sixth node reports a ninth message containing an actually used TA value obtained by the sixth node to the fifth node according to its own situation and / or according to the seventh message received from the fifth node containing a request to report the actually used TA value. In some implementations, for example, the fifth node can use the actually used TA value to evaluate whether a generated TA value is appropriate. For example, if the actually used TA value is inconsistent with the generated TA value and / or the difference between the actually used TA value and the generated TA value is greater than and / or equal to a predetermined threshold, it means that the generated TA value is inappropriate; if the actually used TA value is consistent with the generated TA value and / or the difference between the actually used TA value and the generated TA value is less than and / or equal to a predetermined threshold, it means that the generated TA value is appropriate. In another implementation, for example, the fifth node may use the actually used TA value to support an artificial intelligence machine learning function, for example, it may be used as an input parameter to train an artificial intelligence machine learning model, which may be a model for generating a TA value or a model for generating a handover decision. Alternatively, the actually used TA value may also be used to evaluate an artificial intelligence machine learn model, for example, to evaluate whether the model can continue to be used, whether the model needs to be train and / or adjusted, etc.

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

[0540] Transmitting node ID: used to identify the node that transmits the message.

[0541] Receiving node ID: used to identify the node that receives the message.

[0542] Measurement ID: used to identify this measurement. In some implementations, this ID may be consistent with the measurement ID in the seventh message and / or the eighth message, in order for associating the reporting with the request and / or response.

[0543] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the seventh message and / or the eighth message, in order for associating the reporting with the request and / or response.

[0544] UE identification (ID): indicates the user corresponding to the actually used TA value reported. It may be a UE ID or a list of UE IDs.

[0545] Cell ID: indicates the cell corresponding to the actually used TA value reported. It may be a cell ID or a list of cell IDs.

[0546] Beam ID: indicates the beam corresponding to the actually used TA value reported. It may be a beam ID or a list of beam IDs.

[0547] Slice ID: indicates the slice corresponding to the actually used TA value reported. It may be a slice ID or a list of slice IDs.

[0548] TA value: indicates the actually used TA value reported.

[0549] Applicable / valid time corresponding to an actually used TA value: used to indicate a valid time and / or time interval corresponding to an actually used TA value. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0550] Start time: used to indicate a start time of the applicable / valid time.

[0551] End time: used to indicate an end time of the applicable / valid time.

[0552] Event and / or condition that triggered this reporting: indicates an event and / or condition that triggered this reporting. The event and / or condition that triggered this reporting includes one or more of the following:

[0553] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0554] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0555] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0556] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0557] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

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

[0559] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0560] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0561] A TA value actually used in an access is inconsistent with a TA value in an LTM cell switch command, and / or the difference between the TA value actually used in an access and the TA value in the LTM cell switch 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 in an access and the TA value in the LTM cell switch command is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0562] A TA value actually used in an access is inconsistent with a TA value in a handover command, and / or the difference between the TA value actually used in an access and the TA value in a 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 in an access and the TA value in a handover command is in a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0563] A TA value actually used in an access is inconsistent with a received TA value, and / or the difference between the TA value actually used in an 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 in an access and the received TA value is within a predetermined interval. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type, event, predetermined threshold and predetermined interval.

[0564] Indication of whether a target cell can be accessed based on a TA value in an LTM cell switch command: used to indicate whether a target cell is accessed based on a TA value in an LTM cell switch command. This field may be represented by a single bit. For example, when the bit is 1, it indicates that access is based on a TA value in an LTM cell switch command; and when the bit is 0, it indicates that access is not based on a TA value in an LTM cell switch command. Alternatively, when the bit is 0, it indicates that access is based on a TA value in an LTM cell switch command; and when the bit is 1, it indicates that access is not based on a TA value in an LTM cell switch command.

[0565] Indication of whether an actually used TA value is consistent with a received TA value: used to indicate whether the actually used TA value is consistent with a received TA value. When the receiving node of the message finds that the TA value based on which the actual access is performed is inconsistent with the received TA value, the receiving node of the message reports this information.

[0566] The actually used TA value is a TA value used when the UE accesses a cell and / or a target cell.

[0567] Example 2 may be combined with Example 3. For example, the source node may transmit a first TA value to the target node through a sixth message. The first TA value may be a generated and / or predicted TA value, or a TA value in an LTM cell switch command and / or a handover command. When the user accesses the target cell, the target node obtains the actually used TA from the UE side by using the methods of Example 3, and the target node compares the actually used TA value with the received first TA value. If the actually used TA value is inconsistent with the received first TA value, the target node may inform the source node of that the actually used TA value is inconsistent with the received first TA value through the ninth message of Example 3.

[0568] Example 4

[0569] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a seventh node transmits a tenth message containing a request for a neighboring cell load condition to an eighth node to request the eighth node to report the neighboring cell load condition (or called 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 the seventh node obtains the neighboring cell load condition, it can make a relevant decision based on the load condition of the neighboring cell, for example, a SON-related decision and / or a mobility decision, etc., so as to avoid frequent handover, local overload, overload and service performance deterioration, etc. Herein, the mobility decision may include a handover decision, for example, an LTM handover decision. The source node may select an appropriate target cell for handover according to load conditions of candidate cells, so as to avoid a case in which the load of a neighboring cell is high and local overload may occur after a UE is handed over to the neighboring cell, and then the UE needs to be handed over again due to the high load of the neighboring cell, resulting in frequent handover and service performance deterioration, etc.

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

[0571] Transmitting node ID: used to identify the node that transmits the message.

[0572] Receiving node ID: used to identify the node that receives the message.

[0573] Measurement and / or prediction ID: used to identify a measurement and / or prediction.

[0574] Request ID: used to identify a request.

[0575] Registration request: used to identify the type of a request. It may include start, end, add, update, modify, cancel, etc.

[0576] Identification of a request for a neighboring cell load condition: used to indicate information of a request for a neighboring cell load condition. The request may be to request a measured neighboring cell load condition or a predicted neighboring cell load condition.

[0577] Cell ID corresponding to a neighboring cell load condition: used to indicate the load conditions of which neighboring cells are requested. It may be a cell ID or a list of cell IDs.

[0578] Identification of a request for load condition of a handover candidate cell: used to indicate a request for load condition of a handover candidate cell. Herein, the handover candidate cell may be a candidate cell for handover of any type. The handover of any type may include one or more of the following: handover, conditional handover, Dual Active Protocol Stack (DAPS) handover, LTM handover, etc.

[0579] Handover candidate cell ID: used to indicate the load conditions of which handover candidate cells are requested. It may be a cell ID or a list of cell IDs.

[0580] Scope requested to be reported: used to indicate the scope requested to be reported.

[0581] Reporting periodicity of a requested neighboring cell load condition: used to indicate an interval for reporting of the requested neighboring cell load condition, or it may be a time interval between two adjacent reportings. The time interval may also be a maximum time interval or a minimum time interval. The reporting periodicity may also be the reporting time of the reported data. In some implementations, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is from a reporting start time to a reporting end time. In some implementations, the reporting periodicity indicates a time interval of a periodic reporting.

[0582] Reporting mode of a requested neighboring cell load condition: used to indicate a reporting mode of a requested neighboring cell load condition. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0583] Reporting time of a neighboring cell load condition: used to indicate a time and / or time interval when a neighboring cell load condition is reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0584] Start time: used to indicate the start time of a reporting time.

[0585] End time: used to indicate the end time of a reporting time.

[0586] Prediction ID: used to identify the prediction request.

[0587] Identification of a prediction request for a neighboring cell load condition: used to indicate a request for prediction information of neighboring cell load.

[0588] Cell ID corresponding to the prediction request for a neighboring cell load condition: used to indicate predicted load conditions of which neighboring cells are requested.

[0589] Identification of a prediction request for load condition of a handover candidate cell: used to indicate a request for the predicted load condition of a handover candidate cell. Herein, the handover candidate cell may be a candidate cell for handover of any type. The handover of any type may include one or more of the following: handover, conditional handover, Dual Active Protocol Stack (DAPS) handover, LTM handover, etc.

[0590] Handover candidate cell ID corresponding to the request for predicted load condition of a handover candidate cell: used to indicate the predicted load conditions of which handover candidate cells are requested. It may be a cell ID or a list of cell IDs.

[0591] Scope requested to be predicted: used to indicate a scope requested to be predicted.

[0592] Reporting periodicity of a neighboring cell load condition requested to be predicted: used to indicate an interval for reporting of the neighboring cell load condition requested to be predicted, or it may be a time interval between two adjacent reportings. The time interval may be a minimum time interval or a maximum time interval. In some implementations, the reporting periodicity may also be the predicted time of the reported data. If there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is from a prediction start time to a prediction end time. In some implementations, the time interval may be a time interval for periodic reporting.

[0593] Reporting mode of a neighboring cell load condition requested to be predicted: used to indicate a reporting mode of a predicted neighboring cell load condition requested. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0594] Reporting time of a predicted neighboring cell load condition: used to indicate a time and / or time interval for reporting the predicted neighboring cell load condition. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0595] Start time: used to indicate the start time of a reporting time.

[0596] End time: used to indicate the end time of a reporting time.

[0597] Prediction time of a predicted neighboring cell load condition: used to indicate a prediction time and / or time interval corresponding to the predicted neighboring cell load condition. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0598] Start time: used to indicate the start time of a prediction time.

[0599] End time: used to indicate the end time of a prediction time.

[0600] Effective / valid time of a predicted neighboring cell load condition: used to indicate an effective / valid time and / or time interval corresponding to a predicted neighboring cell load condition. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0601] Start time: used to indicate the start time of an effective / valid time.

[0602] End time: used to indicate the end time of an effective / valid time.

[0603] Trigger condition and / or event for reporting of a neighboring cell load condition: it means that neighboring cell load information (or information related to a neighboring cell load condition) needs to be reported when a trigger event and / or condition for reporting is met. The neighboring cell load information includes a currently measured neighboring cell load information, or may also include a predicted neighboring cell load information. The event and / or condition that triggers reporting includes one or more of the following:

[0604] Neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0605] It is predicted that neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0606] Overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0607] It is predicted that overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0608] Neighboring cell load condition requested to be reported: used to indicate specific parameters of neighboring cell load conditions requested to be reported.

[0609] In some implementations, the eighth node transmits an eleventh message to the seventh node, which contains a response for a neighboring cell load condition, so as to inform the third node whether the fourth node can report a neighboring cell load condition, so that the seventh node can know whether the requested content can be received subsequently. In some implementations, for example, if the eleventh message received by the seventh node indicates that the eighth node can report a neighboring cell load condition, the seventh node can subsequently receive the neighboring cell load condition reported by the eighth node, for example, by receiving a twelfth message subsequently. In some other implementations, for example, the seventh node may also transmit a message for stoping (and / or cancelling) reporting to the eighth node based on the information indicated in the received eleventh message, for example, to stop (and / or cancel) reporting through the tenth message.

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

[0611] Transmitting node ID: used to identify the node that transmits the message.

[0612] Receiving node ID: used to identify the node that receives the message.

[0613] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, for example, the measurement and / or prediction ID may be consistent with the measurement and / or prediction ID in the tenth message, in order for associating the response message with the request message.

[0614] Request ID: used to identify a request corresponding to the response. In some implementations, for example, the request ID may be consistent with the request ID in the tenth message, in order for associating the response message with the request message.

[0615] Acknowledge of a request for a neighboring cell load condition: used to indicate whether a neighboring cell load condition can be measured and / or reported. The acknowledge of a neighboring cell load condition may be a bit indicating whether measurement and / or reporting can be performed.

[0616] Acknowledge of a predicted neighboring cell load condition: used to indicate whether a neighboring cell load condition can be predicted and / or reported. The acknowledge of a neighboring cell load condition may be a bit indicating whether measurement and / or reporting can be performed.

[0617] Acknowledge of a load condition of a handover candidate cell: used to indicate whether a load condition of a handover candidate cell can be predicted and / or reported. Herein, the handover candidate cell may be a candidate cell for handover of any type. The handover of any type may include one or more of the following: handover, conditional handover, Dual Active Protocol Stack (DAPS) handover, LTM handover, etc. The acknowledge of a load condition of a handover candidate cell may be a bit indicating whether measurement and / or reporting can be performed.

[0618] Handover candidate cell ID corresponding to a load condition that can be measured and / or reported: used to indicate a candidate cell ID corresponding to a load condition that can be measured and / or reported. It may be a cell ID or a list of cell IDs.

[0619] Scope that can be measured and / or reported: used to indicate a scope that can be measured and / or predicted and / or reported.

[0620] Neighboring cell load condition that can be measured and / or reported: used to indicate specific parameters of a neighboring cell load condition that can be measured and / or reported.

[0621] Trigger event and / or condition corresponding to a reporting and / or measurement that can be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that can be performed. When the event and / or condition that triggers reporting and / or measurement are met, reporting and / or measurement can be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0622] Neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0623] It is predicted that neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0624] Overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0625] It is predicted that overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0626] 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. It may be a cell ID or a list of cell IDs.

[0627] Scope that cannot be measured and / or reported: used to indicate a scope that cannot be measured and / or predicted and / or reported.

[0628] Neighboring cell load condition that cannot be measured and / or reported: used to indicate specific parameters of a neighboring cell load condition that cannot be measured and / or reported.

[0629] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers reporting and / or measurement are met, the reporting and / or measurement cannot be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0630] Neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0631] It is predicted that neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0632] Overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0633] It is predicted that overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0634] Cause / reason: indicates the reason why measurement and / or reporting cannot be performed. The reasons may include one or more of the following: neighboring cell is unavailable, measurement is unavailable, neighboring cell load measurement is unavailable, neighboring cell is temporarily unavailable, measurement is temporarily unavailable, neighboring cell measurement is temporarily unavailable, reporting time is unavailable, reporting periodicity is unavailable, neighboring cell corresponding to prediction is unavailable, prediction is unavailable, prediction of neighboring cell load condition is unavailable, prediction is temporarily unavailable, neighboring cell prediction is temporarily unavailable, prediction time is unavailable, prediction reporting time is unavailable, effective time of prediction information is unavailable, reporting periodicity of prediction information is unavailable, neighboring cell is not supported, measurement is not supported, neighboring cell is not supported temporarily, measurement is not supported temporarily, neighboring cell measurement is not supported temporarily, reporting time is not supported, reporting periodicity is not supported, neighboring cell corresponding to prediction is not supported, prediction is not supported, prediction is not supported temporarily, neighboring cell prediction is not supported temporarily, prediction time is not supported, prediction reporting time is not supported, effective time of prediction information is not supported, reporting periodicity of prediction information is not supported, etc.

[0635] In some implementations, the eighth node transmits a twelfth message containing a neighboring cell load condition or an update of a neighboring cell load condition to the seventh node according to its own situation and / or according to the tenth message containing a neighboring cell load condition request received from the seventh node, so as to inform the seventh node of the neighboring cell load condition measured (or acquired) by the eighth node. In some implementations, after the eighth node receives the tenth message containing the neighboring cell load condition request from the seventh node, and after the eighth node reports to the seventh node that the eighth node can perform part and / or all of the requested neighboring cell load condition through the eleventh message, the eighth node transmits the neighboring cell load condition to the seventh node according to the tenth message containing the neighboring cell load condition request. After the seventh node obtains the neighboring cell load condition, it can make a relevant decision based on the neighboring cell load condition, for example, a SON-related decision, etc., so as to avoid frequent handover, local overload, overload and service performance deterioration, etc. The seventh node may also evaluate a made decision based on the neighboring cell load condition. In some implementations, for example, when local overload occurs after a decision, it indicates that the decision is inappropriate.

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

[0637] Transmitting node ID: used to identify the node that transmits the message.

[0638] Receiving node ID: used to identify the node that receives the message.

[0639] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the first message and / or the second message, in order for associating the reporting with the request and / or response.

[0640] Request ID: used to identify a request. In some implementations, this ID may be consistent with the request ID in the first message and / or the second message, in order for associating the reporting with the request and / or response.

[0641] Measured neighboring cell load condition: used to indicate a measured neighboring cell load condition.

[0642] Applicable / valid time of a measured neighboring cell load condition: used to indicate a time and / or time interval corresponding to a measured neighboring cell load condition. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0643] Start time: used to indicate a start time of the applicable / valid time.

[0644] End time: used to indicate an end time of the applicable / valid time.

[0645] Predicted neighboring cell load condition: used to indicate a predicted neighboring cell load condition.

[0646] Applicable / valid time of a predicted neighboring cell load condition: used to indicate a time and / or time interval corresponding to a predicted neighboring cell load condition. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0647] Start time: used to indicate a start time of the applicable / valid time.

[0648] End time: used to indicate an end time of the applicable / valid time.

[0649] Condition and / or event that triggerred the reporting and / or measurement of the neighboring cell load condition: indicates an event and / or condition that triggered the reporting and / or measurement of the neighboring cell load condition. The neighboring cell load condition includes a currently measured neighboring cell load information, and may also include a predicted neighboring cell load information. The event and / or condition that triggers reporting includes one or more of the following:

[0650] Neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0651] It is predicted that neighboring cell load is greater than and / or equal to and / or less than a predetermined threshold. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, predetermined threshold, etc.

[0652] Overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0653] It is predicted that overload is to occur. The event and / or condition that triggers reporting may include one or more of the following configurations: event type, event, etc.

[0654] The fields in the above tenth message, eleventh message and twelfth message may be used with respect to measured load information, or may be used with respect to predicted load information. Herein, a neighboring cell (or an adjacent cell) may be or include a handover candidate cell.

[0655] In some implementations, for example, the seventh node may be a gNB DU and the eighth node may be a gNB CU. Since in LTM handover, an LTM handover decision is decided by a gNB DU, but the gNB DU doesn't know the load conditions of candidate cells, thus the UE is likely to be handed over to a cell with high load, which leads to local overload, and frequent handover of the UE is needed, which leads to service performance deterioration. The gNB DU may request the load conditions of neighboring cells and / or target candidate cells from the gNB CU. The gNB CU may transmit the obtained load conditions of neighboring 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 conditions of the neighboring cells and / or target candidate cells, for example, selecting an appropriate handover target cell.

[0656] Example 5

[0657] A ninth node transmits a thirteenth message containing information of a situation that the load of a neighboring cell is too large to a tenth node, so that the tenth node can know the situation that the load of a neighboring cell is too large, and the tenth node may refer to this information when making a mobility decision. Herein, the situation that the load of a neighboring cell is too large may be a situation that the current load of a neighboring cell is too large or a situation that the predicted load of a neighboring cell is too large. Herein, the neighboring cell may refer to a neighboring 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, a gNB CU obtains the information that the load of a neighboring cell is too large based on the obtained neighboring cell load information, and the gNB CU may transmit this information to a gNB DU. When the gNB DU is making an LTM handover decision, it may refer to this information, for example, not selecting a neighboring cell whose load is too large as the target cell for LTM handover, so as to avoid frequent handover due to the too large load, which will cause UE performance deterioration.

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

[0659] Transmitting node ID: used to identify the node that transmits the message.

[0660] Receiving node ID: used to identify the node that receives the message.

[0661] Cell ID corresponding to a predicted too large load: used to identify a cell corresponding to the situation where the predicted load is too large.

[0662] Beam ID corresponding to a predicted too large load: used to identify a beam corresponding to the situation where the predicted load is too large.

[0663] Laod amount of a predicted too large load.

[0664] Time information corresponding to a predicted too large load: used to indicate when the predicted too large load occurs.

[0665] Accuracy and / or confidence for prediction.

[0666] Action: used to indicate an action that the receiving node of the message should apply. The actions may include one or more of the following: for example, rejecting RRC establishment, rejecting non-emergency RRC establishment, rejecting RRC establishment for signaling, allowing only emergency session establishment, allowing only mobile terminated services, allowing only high-priority sessions, etc. In some implementations, the action may be a configured action, that is, the receiving node of the message must implement the action. In some other implementations, the measure may also be a suggested action, and the receiving node of the message may or may not implement the suggested action according to its own situation.

[0667] Example 6

[0668] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a ninth node transmits a fourteenth message containing receivable load amount information (for example, of a neighboring cell) to a tenth node, so that the tenth node can know the receivable load amount. The tenth node may refer to this information when making subsequent mobility decisions. Herein, the neighboring cell may refer to a neighboring 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. In some implementations, for example, the gNB CU can obtain the neighboring cell load condition, and the gNB CU may transmit the receivable load amount information to the gNB DU, and the gNB DU may refer to this information when making an LTM handover decision, so as to avoid handing over the UE to a cell with a too large load, resulting in frequent handover and service interruption due to the too large load, etc.

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

[0670] Transmitting node ID: used to identify the node that transmits the message.

[0671] Receiving node ID: used to identify the node that receives the message.

[0672] Receivable load amount information: information indicating the receivable load amount.

[0673] Load amount that can be received.

[0674] Beam ID corresponding to the load amount that can be received.

[0675] Cell ID corresponding to the load amount that can be received.

[0676] Action corresponding to the load amount that can be received: used to indicate an action that the receiving node of the message should apply. The actions may include one or more of the following: for example, rejecting RRC establishment, rejecting non-emergency RRC establishment, rejecting RRC establishment for signaling, allowing only emergency session establishment, allowing only mobile terminated services, allowing only high-priority sessions, etc. In some implementations, the action may be a configured action, that is, the receiving node of the message must implement the action. In some other implementations, the measure may also be a suggested action, and the receiving node of the message may or may not implement the suggested action according to its own situation.

[0677] Time corresponding to the receivable load amount: used to indicate when the receivable load amount can be received.

[0678] Accuracy and / or confidence for prediction.

[0679] Example 7

[0680] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a ninth node transmits a fifteenth message containing information of activation and / or deactivation of a candidate cell to the tenth node, so that the tenth node may know which candidate cells can be selected as handover target cells when making handover, for example, only a cell in an activated state can be selected as a handover target cell, or a cell which is not in an inactived state can be selected as a handover target cell, or a cell in an inactived state can not be selected as a handover target cell. The ninth node may decide to activate and / or deactivate a candidate cell according to the obtained and / or received load condition of the candidate cell. For example, when the load condition of the candidate cell is too large / high, the candidate cell may be deactivated to avoid frequent handover of a UE after the UE is handed over to the cell due to the large / high load. For example, when the load condition of the candidate cell is low, the candidate cell may be activated to ensure the performance of a UE when the UE is handed over to the candidate cell. And / or, the ninth node may decide to activate and / or deactivate a candidate cell according to the obtained and / or received performance information of other UEs in the candidate cell. For example, when the performance of another UE in the candidate cell is poor, the candidate cell can be deactivated, so as to avoid performance degradation of a UE after the UE is handed over to the cell, where the QoS performance and / or QoE performance cannot be guaranteed, etc. Alternatively, when the performance of another UE in the candidate cell is good, the candidate cell can be activated to ensure the performance of a UE after the UE is handed over to the cell.

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

[0682] Transmitting node ID: used to identify the node that transmits the message.

[0683] Receiving node ID: used to identify the node that receives the message.

[0684] UE identification (ID): indicates the user corresponding to the activation and / or deactivation of a candidate cell.

[0685] ID of an activated cell: indicates the ID of an activated cell, or it may be an ID list of activated cells. The cell may be a handover candidate cell. The activated cell may also be a cell for which activation can be performed and / or a cell for which activation is allowed to be performed.

[0686] Activation time: used to indicate an activation time and / or time interval corresponding to an activated cell. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0687] Start time: used to indicate the start time of an activation time.

[0688] End time: used to indicate the end time of an activation time.

[0689] Available and / or allowed activation time: used to indicate an available and / or allowed activation time and / or time interval corresponding to an activated cell. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0690] Start time: used to indicate the start time of an activation time.

[0691] End time: used to indicate the end time of an activation time.

[0692] ID of a deactivated cell: indicates the ID of a deactivated cell, or it may be an ID list of deactivated cells. The cell may be a handover candidate cell. The deactivated cell may also be a cell for which deactivation can be performed and / or a cell for which deactivation is allowed to be performed.

[0693] Deactivation time: used to indicate a deactivation time and / or time interval corresponding to a deactivated cell. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an 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 a deactivation time.

[0695] End time: used to indicate the end time of a deactivation time.

[0696] Available and / or allowed deactivation time: used to indicate an available and / or allowed deactivation time and / or time interval corresponding to a deactivated cell. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0697] Start time: used to indicate the start time of a deactivation time.

[0698] End time: used to indicate the end time of a deactivation time.

[0699] Accuracy and / or confidence for prediction: In some implementations, if it is a predicted activation and / or deactivation decision, this information can be carried.

[0700] The candidate cell activation and / or deactivation information in the fifteenth message may be applicable to the current time, or may be predicted information which may be applicable to a future time.

[0701] Example 8

[0702] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: an eleventh node transmits a sixteenth message containing a user performance request to a twelfth node to request the twelfth node to report the requested user performance. In some implementations, the user performance may be the performance of a user corresponding to an LTM handover. In some implementations, for example, the eleventh node may use the user performance to evaluate a related decision, for example, an LTM handover related decision. For example, good user performance (for example, better than one or more predetermined standards or performance levels) can indicate that the related decision is appropirate, and poor user performance (for example, worse than one or more predetermined standards or performance levels) can indicate that the related decision is inappropriate and needd to be optimized and updated. In some other implementations, for example, the eleventh section may also use the user performance to evaluate an artificial intelligence machine learning model, for example, to evaluate whether the model can continue to be used, whether the model needs to be trained and / or adjusted, etc. In yet other implementations, for example, the eleventh node may make decisions based on the user performance. For example, if the user performance meets the requirements for users and / or services, a subsequent user may be handed over to the cell where the user is located, etc. In still other implementations, for example, after the eleventh node obtains the user performance, it receives and / or rejects a handover request based on the obtained user performance. For example, if the performance of a UE handed over from a source node A and / or source cell A to the eleventh node is poor, the eleventh node may reject the handover request transmitted by the source node A and / or source cell A subsequently. For example, if the performance of a UE handed over from a source node A and / or source cell A to the eleventh node is good, the eleventh node may receive the handover request transmitted by the source node A and / or source cell A subsequently.

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

[0704] Transmitting node ID: used to identify the node that transmits the message.

[0705] Receiving node ID: used to identify the node that receives the message.

[0706] Request ID: used to identify a request.

[0707] Measurement ID: used to identify this measurement.

[0708] User performance request indication: used to indicate a request to report user performance.

[0709] 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 in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0710] Scope corresponding to the requested content.

[0711] Event and / or condition that triggers reporting and / or measurement: it means that reporting and / or measurement needs to be performed when the event and / or condition that triggers reporting and / or measurement is met. The event and / or condition that triggers reporting and / or measurement includes one or more of the following:

[0712] UE RRC state changes. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0713] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0714] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0715] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0716] Reporting mode of a requested content: used to indicate a reporting mode of a requested content. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0717] Reporting periodicity of a requested content: used to indicate an interval for a periodic reporting of a requested content, or a time interval between two adjacent reportings. The reporting periodicity may also be the measurement time of the reported data. If there is no content in this field, a single reporting is indicated, and the teporting time of the single reporting is from a measurement start time to a measurement end time. In some implementations, for example, the reporting periodicity may be a reporting periodicity for a periodic reporting.

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

[0719] Measurement start time: used to indicate the start time of measurement.

[0720] Measurement end time: used to indicate the end time of measurement.

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

[0722] Start time: used to indicate the start time for reporting.

[0723] End time: used to indicate the end time for reporting.

[0724] Applicable / valid time corresponding to a content requested to be reported: used to indicate a valid time and / or time interval corresponding to a content requested to be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0725] Start time: used to indicate a start time of the applicable / valid time.

[0726] End time: used to indicate an end time of the applicable / valid time.

[0727] Indication of whether partial reporting can be performed: used to indicate whether the message receiving node can perform partial reporting, that is, whether the message receiving node can report part of the information requested to be reported. If it is indicated that partial reporting can be performed, the message receiving node may only report part 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 transmits a request failure message to the message transmitting node. The information requested to be reported may include one or more of the above-mentioned requested contents, and may also be one or more of the scopes corresponding to the above-mentioned requested contents. This indication may allow the message receiving node to report partial information according to its own situation, so as to avoid that the message receiving node has to transmit a request failure message when one or more of the information requested to be reported cannot be reported, which would result in a request failure, so that the message transmitting node needs to make a new request. However, the message transmitting node does not know which messages the message receiving node can transmit, which leads to the need for the message transmitting node to continuously try to make a request, resulting in signaling burden.

[0728] Indication of whether the information requested to be reported must be reported: used to indicate whether the information requested to be reported must be reported. If it is indicated that the information must be reported, the message receiving node must report the information and / or a load condition corresponding to the information. The information requested to be reported may include one or more of the above-mentioned requested contents, and may also be one or more of the scopes corresponding to the above-mentioned requested contents. The message receiving node can determine which parameters to report according to the indication and / or its own situation.

[0729] 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 and / or not report low priority information according to its own situation. The information requested to be reported may include one or more of the above-mentioned requested contents, and may also be one or more of the scopes corresponding to the above-mentioned requested contents. The message receiving node can determine which parameters to report according to the priority and its own situation.

[0730] Indication of whether user performance needs to be collected in subsequent LTM handover: used to inform the message receiving node whether the performance of a UE needs to be collected in the subsequent LTM handover. It may be represented by a single bit. For example, when the bit is 1, it indicates that the performance of the UE in the subsequent LTM handover needs to be collected; and when the bit is 0, it indicates that the performance of the UE in the subsequent LTM handover needs not to be collected.

[0731] Request information of user performance: request information related to user performance. It may include one or more of the following:

[0732] Number of slices: the number of slices corresponding to the user performance that can be reported.

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

[0734] Number of cells: the number of cells corresponding to the user performance that can be reported.

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

[0736] Number of beams: the number of beams corresponding to the user performance that can be reported.

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

[0738] Number of nodes: the number of nodes corresponding to the user performance that can be reported.

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

[0740] In some implementations, the twelfth node may transmit a seventeenth message containing a user performance response to the eleventh node to inform whether the eleventh node can performing reporting, so that the eleventh node can know whether the content requested to be reported can be received from the twelfth node subsequently. In some implementations, for example, if the seventeenth message received by the eleventh node indicates that the second node can report all and / or part of the requested user performance information, the eleventh node can receive the user performance information reported by the twelfth node subsequently, for example, through a subsequent eighteenth message. In some other implementations, for example, the eleventh node may also transmit a message for stoping (and / or cancelling) reporting to the twelfth node based on the information indicated in the received seventeenth message, for example, to stop (and / or cancel) reporting through the sixteenth message.

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

[0742] Transmitting node ID: used to identify the node that transmits the message.

[0743] Receiving node ID: used to identify the node that receives the message.

[0744] Measurement ID: used to identify this measurement. In some implementations, this ID may be consistent with the measurement ID in the seventeenth message, in order for associating the reporting with the request and / or response.

[0745] Request ID: used to identify a request. In some implementations, this ID may be consistent with the request ID in the seventeenth message, in order for associating the reporting with the request and / or response.

[0746] User performance request acknowledge: used to indicate whether user performance can be measured and / or reported. The user performance request acknowledge may be represented by a bit.

[0747] UE ID for which reporting can be performed: ID(s) of user(s) corresponding to user performance that can be measured and / or reported. It may be an ID or an ID list.

[0748] Cell ID for which reporting can be performed: ID(s) of cell(s) corresponding to user performance that can be measured and / or reported. It may be an ID or an ID list.

[0749] Beam ID for which reporting can be performed: ID(s) of beam(s) corresponding to user performance that can be measured and / or reported. It may be an ID or an ID list.

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

[0751] Content that can be reported: used to indicate the content that can be reported, which may include one or more of the following: QoS parameters, QoE parameters, TA information used in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0752] Content that can be predicted: used to indicate the content that can be predicted, which may include one or more of the following: QoS parameters, QoE parameters, TA information used in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0753] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0754] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0755] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0756] Start time: used to indicate the start time of the time available for reporting.

[0757] End time: used to indicate the end time of the time available for reporting.

[0758] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0759] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[0760] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0761] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[0762] End time: used to indicate the end time of a measurement time when measurement can be performed.

[0763] Time available for prediction: used to indicate a time and / or time interval when prediction can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0764] Prediction start time: used to indicate the start time when prediction can be performed.

[0765] Prediction end time: used to indicate the end time when prediction can be performed.

[0766] Applicable / valid time of corresponding prediction content that can be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that can be predicted. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0767] Start time: used to indicate the start time of a valid time available for prediction.

[0768] End time: used to indicate the end time of a valid time available for prediction.

[0769] Corresponding information that can be reported: used to indicate the information corresponding to the user performance that can be reported. It may include one or more of the following:

[0770] Number of slices: the number of slices corresponding to the user performance that can be reported.

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

[0772] Number of cells: the number of cells corresponding to the user performance that can be reported.

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

[0774] Number of beams: the number of beams corresponding to the user performance that can be reported.

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

[0776] Number of nodes: the number of nodes corresponding to the user performance that can be reported.

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

[0778] Trigger event and / or condition corresponding to a reporting and / or measurement that can be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that can be performed. When the event and / or condition that triggers reporting and / or measurement are met, reporting and / or measurement can be performed. The event and / or condition that triggers reporting and / or measurement includes one or more of the following:

[0779] UE RRC state changes. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0780] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0781] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0782] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0783] UE ID for which measurement and / or reporting cannot be performed: ID(s) of user(s) for which user performance measurement and / or reporting cannot be performed. It may be an ID or an ID list.

[0784] Cell ID 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. It may be an ID or an ID list.

[0785] Beam ID 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. It may be an ID or an ID list.

[0786] Slice ID 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. It may be an ID or an ID list.

[0787] Content that cannot be reported: used to indicate the content that cannot be reported, which may include one or more of the following: QoS parameters, QoE parameters, TA information used in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0788] Content that cannot be predicted: used to indicate the content that cannot be predicted, which may include one or more of the following: QoS parameters, QoE parameters, TA information used in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0789] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0790] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0791] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0792] Start time: used to indicate the start time of the time unavailable for reporting.

[0793] End time: used to indicate the end time of the time unavailable for reporting.

[0794] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0795] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[0796] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[0798] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[0799] Time unavailable for prediction: used to indicate a time and / or time interval when prediction can not be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0800] Prediction start time: used to indicate the start time when prediction cannot be performed.

[0801] Prediction end time: used to indicate the end time when prediction cannot be performed.

[0802] Applicable / valid time of corresponding prediction content that cannot be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that cannot be predicted. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0803] Start time: used to indicate the start time of a valid time unavailable prediction.

[0804] End time: used to indicate the end time of a valid time unavailable for prediction.

[0805] Corresponding information that cannot be reported: used to indicate the information corresponding to the user performance that cannot be reported. It may include one or more of the following:

[0806] Number of slices: the number of slices corresponding to the user performance that cannot be reported.

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

[0808] Number of cells: the number of cells corresponding to the user performance that cannot be reported.

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

[0810] Number of beams: the number of beams corresponding to the user performance that cannot be reported.

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

[0812] Number of nodes: the number of nodes corresponding to the user performance that cannot be reported.

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

[0814] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers reporting and / or measurement are met, the reporting and / or measurement cannot be performed. The event and / or condition that triggers reporting and / or measurement includes one or more of the following:

[0815] UE RRC state changes. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0816] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0817] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0818] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

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

[0820] Indication of whether collection of user performance in subsequent LTM handover is acceptable: used to inform the message receiving node whether the performance of a UE in subsequent LTM handover can be collected. It may be represented by a single bit. For example, when the bit is 1, it indicates that the performance of a UE in subsequent LTM handover can be collected; and when the bit is 0, it indicates that the performance of a UE in subsequent LTM handover cannot be collected.

[0821] The twelfth node may transmit an eighteenth message containing user performance to the twelfth node according to its own situation and / or according to the sixteenth message containing a user performance request received from the eleventh node, so as to inform the eleventh node of the requested user performance. In some implementations, the user performance may be the performance of a user corresponding to an LTM handover. In some implementations, for example, the eleventh node may use the user performance to evaluate a related decision, for example, an LTM handover related decision. For example, good user performance (for example, better than one or more predetermined standards or performance levels) can indicate that the related decision is appropirate, and poor user performance (for example, worse than one or more predetermined standards or performance levels) can indicate that the related decision is inappropriate and needd to be optimized and updated. In some other implementations, for example, the eleventh section may also use the user performance to evaluate an artificial intelligence machine learning model, for example, to evaluate whether the model can continue to be used, whether the model needs to be trained and / or adjusted, etc. In yet other implementations, for example, the eleventh node may make decisions based on the user performance. For example, if the user performance meets the requirements for users and / or services, a subsequent user may be handed over to the cell where the user is located, etc.

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

[0823] Transmitting node ID: used to identify the node that transmits the message.

[0824] Receiving node ID: used to identify the node that receives the message.

[0825] Measurement ID: used to identify this measurement. In some implementations, this ID may be consistent with the measurement ID in the sixteenth message and / or the seventeenth message, in order for associating the reporting with the request and / or response.

[0826] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the sixteenth message and / or the seventeenth message, in order for associating the reporting with the request and / or response.

[0827] Reported content: used to indicate a reported content. The content may include one or more of the following: QoS parameters, QoE parameters, TA information used in a successful access, TA information used in an access, whether successful access is performed using a received TA value, whether successful access is performed using a TA value in an LTM cell switch command, access time, time of a successful access, etc.

[0828] Scope corresponding to a reported content: the scope may be an ID and / or ID list of one or more of the following: cell, beam, slice, UE, UE not to be measured, UE service to be measured, scenario, node, channel, Protocol Data Unit Session, Data Radio Bearers (DRB), QoS flow, QoS level, etc. The service may be 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 rate, etc., which may be identified by 5QI (5G QoS Identifier), QCI (QoS Class Identifier), etc. The scenarios 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 scope may also indicate performance of users except one or more UEs, for example, the other users in a slice and / or cell except the handover user, or the other users in a slice and / or cell except the user corresponding to a slice remapping.

[0829] Applicable / valid time corresponding to a reported content: used to indicate a valid time and / or time interval corresponding to a reported content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the sixteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0830] Start time: used to indicate a start time of the applicable / valid time.

[0831] End time: used to indicate an end time of the applicable / valid time.

[0832] Trigger event and / or condition that triggered this reporting and / or measurement: indicates a trigger event and / or condition that triggered this reporting and / or measurement. The event and / or condition that triggers reporting and / or measurement includes one or more of the following:

[0833] UE RRC state changes. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0834] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0835] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0836] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0837] Example 9

[0838] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a thirteenth node transmits a nineteenth message containing a request for reporting predicted beam information to a fourteenth node to request the fourteenth node to report predicted beam information. The beam information may be of the beam that the user is to access. The predicted beam information may be obtained by mathematical method calculation and / or artificial intelligence machine learning model. In some implementations, for example, the thirteenth node may transmit the predicted beam information to a handover target node in advance, and the target node may reserve resources of the predicted beam, thereby when a UE needs to access the beam, it is ensured that there are sufficient resources to guarantee the performance of the UE and avoid service interruption due to the shortage of resources of the selected beam. In still other implementations, a gNB CU may transmit the predicted beam information to a gNB DU, and the gNB DU can reserve resources to ensure the performance of the UE.

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

[0840] Transmitting node ID: used to identify the node that transmits the message.

[0841] Receiving node ID: used to identify the node that receives the message.

[0842] Measurement and / or prediction ID: used to identify a measurement and / or prediction.

[0843] Request ID: used to identify a request.

[0844] UE identification (ID): indicates the user corresponding to the predicted beam information requested to be reported. It may be a UE ID or a list of UE IDs.

[0845] Cell ID: indicates the cell corresponding to the predicted beam information requested to be reported. It may be a cell ID or a list of cell IDs.

[0846] Identification of a request for predicted beam information of a candidate cell: which indicates a request for a message receiving node to report the predicted beam information of a candidate cell.

[0847] Slice ID: indicates the slice corresponding to the requested predicted beam information. It may be a slice ID or a list of slice IDs.

[0848] Identification of a request for predicted beam information corresponding to a slice in a candidate cell: which indicates a request for a message receiving node to report the predicted beam information corresponding to a slice in a candidate cell.

[0849] Identification of a request for predicted beam information: used to indicate that this information is to request the reporting of predicted beam information. This field may be represented by a single bit. For example, when the bit is 1, it indicates that the predicted beam information is requested to be reported; and when the bit is 0, it indicates that the predicted beam information is not requested to be reported. Alternatively, when the bit is 0, it indicates that the predicted beam information is requested to be reported; and when the bit is 1, it indicates that the predicted beam information is not requested to be reported.

[0850] Registration request: used to indicate the type of a request. For example, it may include start, end, add, update, cancel, etc.

[0851] Reporting registration request: used to indicate the type of a reporting request. For example, it may include start, end, add, update, cancel, etc.

[0852] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0853] Event and / or condition that triggers reporting: when the event and / or condition that triggers reporting is met, reporting is required to be performed.

[0854] Reporting periodicity: used to indicate the interval of a periodic reporting. The reporting periodicity may also be the prediction time and / or measurement time of the reported information. In an implementation, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is a measurement time and / or a reporting time.

[0855] Reporting time of a requested content: used to indicate a time and / or time interval when the content is requested to be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0856] Start time: used to indicate the start time of a reporting time.

[0857] End time: used to indicate the end time of a reporting time.

[0858] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0859] Measurement mode of a requested content: used to indicate a requested content measurement mode. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0860] Event and / or condition that triggers measurement: when the event and / or condition that triggers measurement is met, measurement is required to be performed.

[0861] Measurement period: used to indicate the interval of a periodic measurement.

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

[0863] Start time: used to indicate the start time of a measurement time.

[0864] End time: used to indicate the end time of a measurement time.

[0865] Applicable / valid time of a requested content: used to indicate a valid time and / or time interval of a requested content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0866] Start time: used to indicate a start time of the applicable / valid time.

[0867] End time: used to indicate an end time of the applicable / valid time.

[0868] Request prediction time interval: used to indicate a time and / or time interval for prediction. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0869] Prediction start time: used to indicate a start time of the prediction.

[0870] Prediction end time: used to indicate an end time of the prediction.

[0871] Applicable / valid time of a requested prediction content: used to indicate a time and / or time interval corresponding to a prediction content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0872] Start time: used to indicate a start time of the applicable / valid time.

[0873] End time: used to indicate an end time of the applicable / valid time.

[0874] Request information: used to indicate the request information for reporting the predicted beam information. It may include one or more of the following:

[0875] Number of cells: the number of cells corresponding to the predicted beam information requested to be reported.

[0876] Cell ID and / or ID list: the cells corresponding to the requested predicted beam information. For example, the cells corresponding to the predicted beam information requested to be reported should be one or more of the cell ID and / or ID list.

[0877] Number of nodes: the number of nodes corresponding to the predicted beam information requested to be reported.

[0878] Node ID and / or ID list: the nodes corresponding to the requested predicted beam information. For example, the nodes corresponding to the predicted beam information requested to be reported should be one or more of the node ID and / or ID list.

[0879] Number of beams: the number of beams corresponding to the predicted beam information requested to be reported. The beam may be an SSB beam or other beams.

[0880] Beam ID and / or ID list: the beams corresponding to the requested predicted beam information. For example, the beams corresponding to the predicted beam information requested to be reported should be one or more of the beam ID and / or ID list. The beam may be an SSB beam or other beams.

[0881] Number of slices: the number of slices corresponding to the predicted beam information requested to be reported.

[0882] Slice ID and / or ID list: the slices corresponding to the requested predicted beam information. For example, the slices corresponding to the predicted beam information requested to be reported should be one or more of the slice ID and / or ID list.

[0883] In some implementations, the fourteenth node may transmit a twentieth message containing a reporting response of the predicted beam information to the thirteenth node, so as to inform the thirteenth node whether the fourteenth node can measure and / or report and / or predict beam information, so that the thirteenth node can know whether the content requested to be reported can be received from the fourteenth node subsequently. In some implementations, for example, if the twentieth message received by the thirteenth node indicates that the fourteenth node can measure and / or report and / or predict beam information, the thirteenth node can subsequently receive the predicted beam information reported by the fourteenth node, for example, through a subsequent twenty-first message. In some other implementations, for example, the thirteenth node may also transmit a message for stoping (and / or cancelling) reporting to the fourteenth node based on the information indicated in the received twentieth message, for example, to stop (and / or cancel) reporting through the nineteenth message.

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

[0885] Transmitting node ID: used to identify the node that transmits the message.

[0886] Receiving node ID: used to identify the node that receives the message.

[0887] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the nineteenth message, in order for associating the reporting with the request and / or response.

[0888] Request ID: used to identify a request corresponding to the response. In some implementations, this ID may be consistent with the request ID in the nineteenth message, in order for associating the reporting with the request and / or response.

[0889] Acknowledge of a request for predicted beam information: used to indicate whether the predicted beam information can be measured and / or reported and / or predicted. The acknowledge of the request for predicted beam information may be a bit indicating whether the request can be measured and / or reported and / or predicted.

[0890] UE ID for which reporting can be performed: ID(s) of user(s) corresponding to predicted beam information that can be measured and / or reported. It may be an ID or an ID list.

[0891] Cell ID for which reporting can be performed: ID(s) of cell(s) corresponding to predicted beam information that can be measured and / or reported. It may be an ID or an ID list.

[0892] Beam ID for which reporting can be performed: ID(s) of beam(s) corresponding to predicted beam information that can be measured and / or reported. It may be an ID or an ID list.

[0893] Slice ID for which reporting can be performed: ID(s) of slice(s) corresponding to predicted beam information that can be measured and / or reported. It may be an ID or an ID list.

[0894] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0895] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0896] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the nineteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an 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 time available for reporting.

[0898] End time: used to indicate the end time of the time available for reporting.

[0899] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0900] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[0901] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the nineteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0902] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[0903] End time: used to indicate the end time of a measurement time when measurement can be performed.

[0904] Time available for prediction: used to indicate a time and / or time interval when prediction can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the nineteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0905] Prediction start time: used to indicate the start time when prediction can be performed.

[0906] Prediction end time: used to indicate the end time when prediction can be performed.

[0907] Applicable / valid time of corresponding prediction content that can be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that can be predicted. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the nineteenth message, or an event and / or condition that triggers reporting. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0908] Start time: used to indicate the start time of a valid time available for prediction.

[0909] End time: used to indicate the end time of a valid time available for prediction.

[0910] Corresponding information that can be reported and / or measured and / or predicted: used to indicate information corresponding to the beam information that can be reported and / or measured and / or predicted. It may include one or more of the following:

[0911] Number of slices: the number of slices corresponding to the beam information that can be reported and / or measured and / or predicted.

[0912] Slice ID and / or ID list: the scope of slices corresponding to the beam information that can be reported and / or measured and / or predicted For example, the slices corresponding to the beam information that can be reported and / or measured and / or predicted are one or more of the slice ID and / or ID list.

[0913] Number of cells: the number of cells corresponding to the beam information that can be reported and / or measured and / or predicted

[0914] Cell ID and / or ID list: the scope of cells corresponding to the beam information that can be reported and / or measured and / or predicted For example, the cells corresponding to the beam information that can be reported and / or measured and / or predicted are one or more of the cell ID and / or ID list.

[0915] Number of beams: the number of beams corresponding to the beam information that can be reported and / or measured and / or predicted.

[0916] Beam ID and / or ID list: the scope of beams corresponding to the beam information that can be reported and / or measured and / or predicted. For example, the beams corresponding to the beam information that can be reported and / or measured and / or predicted are one or more of the beam ID and / or ID list.

[0917] Number of nodes: the number of nodes corresponding to the beam information that can be reported and / or measured and / or predicted.

[0918] Node ID and / or ID list: the scope of nodes corresponding to the beam information that can be reported and / or measured and / or predicted. For example, the nodes corresponding to the beam information that can be reported and / or measured and / or predicted are one or more of the node ID and / or ID list.

[0919] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers measurement is met, the measurement and / or reporting can be performed.

[0920] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0921] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[0922] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0923] Start time: used to indicate the start time of the time unavailable for reporting.

[0924] End time: used to indicate the end time of the time unavailable for reporting.

[0925] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0926] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[0927] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[0929] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[0930] Time unavailable for prediction: used to indicate a time and / or time interval when prediction can not be performed. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a prediction start time and the last n bits represent a prediction end time. It may also be represented by separate fields, including one or more of the following:

[0931] Prediction start time: used to indicate the start time when prediction cannot be performed.

[0932] Prediction end time: used to indicate the end time when prediction cannot be performed.

[0933] Applicable / valid time of corresponding prediction content that cannot be predicted: used to indicate an applicable / valid time and / or time interval of a corresponding prediction content that cannot be predicted. The time may be a relative time or an absolute time. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc.If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0934] Start time: used to indicate the start time of a valid time unavailable prediction.

[0935] End time: used to indicate the end time of a valid time unavailable for prediction.

[0936] Corresponding information that cannot be reported and / or measured and / or predicted: used to indicate information corresponding to the beam information that cannot be reported and / or measured and / or predicted. It may include one or more of the following:

[0937] Number of slices: the number of slices corresponding to the beam information that cannot be reported and / or measured and / or predicted.

[0938] Slice ID and / or ID list: the scope of slices corresponding to the beam information that cannot be reported and / or measured and / or predicted. For example, the slices corresponding to the beam information that cannot be reported and / or measured and / or predicted are one or more of the slice ID and / or ID list.

[0939] Number of cells: the number of cells corresponding to the beam information that cannot be reported and / or measured and / or predicted.

[0940] Cell ID and / or ID list: the scope of cells corresponding to the beam information that cannot be reported and / or measured and / or predicted. For example, the cells corresponding to the beam information that cannot be reported and / or measured and / or predicted are one or more of the cell ID and / or ID list.

[0941] Number of beams: the number of beams corresponding to the beam information that cannot be reported and / or measured and / or predicted.

[0942] Beam ID and / or ID list: the scope of beams corresponding to the beam information that cannot be reported and / or measured and / or predicted. For example, the beams corresponding to the beam information that cannot be reported and / or measured and / or predicted are one or more of the beam ID and / or ID list.

[0943] Number of nodes: the number of nodes corresponding to the beam information that cannot be reported and / or measured and / or predicted.

[0944] Node ID and / or ID list: the scope of nodes corresponding to the beam information that cannot be reported and / or measured and / or predicted. For example, the nodes corresponding to the beam information that cannot be reported and / or measured and / or predicted are one or more of the node ID and / or ID list.

[0945] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers measurement is met, the measurement and / or reporting can be performed.

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

[0947] In some implementations, the fourteenth node may report a twenty-first message containing predicted beam information obtained and / or generated by the fourteenth node to the thirteenth node according to its own situation and / or according to the nineteenth message containing a request for reporting predicted beam information received from the thirteenth node. The beam information may be of the beam that the user is to access. The predicted beam information may be obtained by mathematical method calculation and / or artificial intelligence machine learning model. In some implementations, for example, the thirteenth node may transmit the predicted beam information to a handover target node in advance, and the target node may reserve resources of the predicted beam, thereby when a UE needs to access the beam, it is ensured that there are sufficient resources to guarantee the performance of the UE. In still other implementations, a gNB CU may transmit the predicted beam information to a gNB DU, and the gNB DU can reserve resources to ensure the performance of the UE.

[0948] In some implementations, the twenty-first message may include one or more of the following information and / or fields:

[0949] Transmitting node ID: used to identify the node that transmits the message.

[0950] Receiving node ID: used to identify the node that receives the message.

[0951] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement ID in the nineteenth message and / or the twentieth message, in order for associating the reporting with the request and / or response.

[0952] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the nineteenth message and / or the twentieth message, in order for associating the reporting with the request and / or response.

[0953] UE identification (ID): indicates the user corresponding to the reported predicted beam information. It may be a UE ID or a list of UE IDs.

[0954] Cell ID: indicates the cell corresponding to the reported predicted beam information. It may be a cell ID or a list of cell IDs.

[0955] Beam ID: indicates the beam corresponding to the reported predicted beam information. It may be a beam ID or a list of beam IDs.

[0956] Slice ID: indicates the slice corresponding to the reported predicted beam information. It may be a slice ID or a list of slice IDs.

[0957] Predicted beam information: indicates the reported predicted beam information. The 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.

[0958] Applicable / valid time corresponding to predicted beam information: used to indicate a valid time and / or time interval corresponding to predicted beam information. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the nineteenth message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0959] Start time: used to indicate a start time of the applicable / valid time.

[0960] End time: used to indicate an end time of the applicable / valid time.

[0961] Event and / or condition that triggered this reporting: indicates an event and / or condition that triggered this reporting.

[0962] Event and / or condition that triggered this measurement: indicates an event and / or condition that triggered this measurement.

[0963] Example 10

[0964] An aspect of the present disclosure proposes a method for supporting mobility management, which may include: a fifteenth node transmits a twenty-second message containing a reqeust for reporting actually accessed beam information to a sixteenth node, so as to request the sixteenth node to report the requested actually accessed beam information. In some implementations, for example, the fifteenth node can use the actually accessed beam information to evaluate whether the predicted beam information is appropriate. For example, if the actually accessed beam information is inconsistent with the predicted beam information, it means that the predicted beam information is inappropriate; and if the actually accessed beam information is consistent with the predicted beam information, it means that the predicted beam information is appropriate. In another implementation, for example, the fifteenth node can use the actually accessed beam information to support an artificial intelligence machine learning function. For example, the actually accessed beam information may be used as an input parameter to train an artificial intelligence machine learning model, which may be a model for predicting beam information or a model for generating a handover decision; or the actually accessed beam information may be used to evaluate an artificial intelligence machine learn model, for example, to evaluate whether a model can continue to be used, whether a model needs to be trained and / or adjusted, etc.

[0965] In some implementations, the twenty-second message may include one or more of the following information and / or fields:

[0966] Transmitting node ID: used to identify the node that transmits the message.

[0967] Receiving node ID: used to identify the node that receives the message.

[0968] Measurement and / or prediction ID: used to identify a measurement and / or prediction.

[0969] Request ID: used to identify a request.

[0970] UE identification (ID): indicates the user corresponding to the actually accessed beam information requested to be reported. It may be a UE ID or a list of UE IDs.

[0971] Cell ID: indicates the cell corresponding to the actually accessed beam information requested to be reported. It may be a cell ID or a list of cell IDs.

[0972] Beam ID: indicates the beam corresponding to the actually accessed beam information requested to be reported. It may be a beam ID or a list of beam IDs.

[0973] Slice ID: indicates the slice corresponding to the actually accessed beam information requested to be reported. It may be a slice ID or a list of slice IDs.

[0974] Identification of a request for reporting actually accessed beam information: which indicates a request for a message receiving node to report the actually accessed beam information.

[0975] Identification of a request for actually accessed beam information: indicates that the message is to request the reporting of actually accessed beam information. This field may be represented by a single bit. For example, when the bit is 1, it indicates that the actually accessed beam information is requested to be reported; and when the bit is 0, it indicates that the actually accessed beam information is not requested to be reported. Alternatively, when the bit is 0, it indicates that the actually accessed beam information is requested to be reported; and when the bit is 1, it indicates that the actually accessed beam information is requested to be reported.

[0976] Indication of a request for reporting whether the actually accessed beam is consistent with the received beam information: used to indicate a request for reporting information about whether the actually accessed beam is consistent with the received beam information.

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

[0978] Reporting registration request: used to indicate the type of a reporting request. For example, it may include start, end, add, update, modify, cancel, etc.

[0979] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0980] Event and / or condition that triggers reporting: when the event and / or condition that triggers reporting is met, reporting is required to be performed. The event and / or condition that triggers reporting includes one or more of the following:

[0981] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0982] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0983] The actually accessed beam is inconsistent with 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 that triggers reporting shall include one or more of the following configurations: event type and event.

[0984] Reporting periodicity: used to indicate the interval of a reporting. It may also be a time interval between two adjacent reportings. The time interval may be a maximum time interval or a minimum time interval. The reporting periodicity may also be the prediction time and / or measurement time of the reported information. In an implementation, for example, if there is no content in this field, a single reporting is indicated, and the reporting time of the single reporting is a measurement time and / or a reporting time. In some implementations, the reporting periodicity is used to indicate a time interval of a periodic reporting.

[0985] Reporting time of a requested content: used to indicate a time and / or time interval when the content is requested to be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[0986] Start time: used to indicate the start time of a reporting time.

[0987] End time: used to indicate the end time of a reporting time.

[0988] Reporting mode of a requested content: used to indicate a requested content reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[0989] Measurement mode of a requested content: used to indicate a requested content measurement mode. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[0990] Event and / or condition that triggers measurement: when the event and / or condition that triggers measurement is met, measurement is required to be performed. The event and / or condition that triggers measurement includes one or more of the following:

[0991] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0992] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0993] The actually accessed beam is inconsistent with received beam information. The received beam information may be generated and / or predicted beam information or other received beam information.Theeventand / orconditionthattriggersreportingshallincludeoneormoreofthefollowingconfigurations:eventtypeandevent.

[0994] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0995] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0996] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[0997] Measurement period: used to indicate an interval for measurement. It may also be a time interval between two adjacent measurements. The 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 an implementation, for example, if there is no content in this field, a single measurement is indicated, and the time of the single measurement is the measurement time and / or the reporting time. In some implementations, the measurement period is used to indicate a time interval of a periodic measurement.

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

[0999] Start time: used to indicate the start time of a measurement time.

[1000] End time: used to indicate the end time of a measurement time.

[1001] Applicable / valid time of a requested content: used to indicate a valid time and / or time interval of a requested content. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[1002] Start time: used to indicate a start time of the applicable / valid time.

[1003] End time: used to indicate an end time of the applicable / valid time.

[1004] Request information: used to indicate the request information for reporting the actually accessed beam information. It may include one or more of the following:

[1005] Number of cells: the number of cells corresponding to the actually accessed beam information requested to be reported.

[1006] Cell ID and / or ID list: the cells corresponding to the requested actually accessed beam information. For example, the cells corresponding to the actually accessed beam information requested to be reported should be one or more of the cell ID and / or ID list.

[1007] Number of nodes: the number of nodes corresponding to the actually accessed beam information requested to be reported.

[1008] Node ID and / or ID list: the nodes corresponding to the requested actually accessed beam information. For example, the nodes corresponding to the actually accessed beam information requested to be reported should be one or more of the node ID and / or ID list.

[1009] Number of beams: the number of beams corresponding to the actually accessed beam information requested to be reported. The beam may be an SSB beam or other beams.

[1010] Beam ID and / or ID list: the beams corresponding to the requested actually accessed beam information. For example, the beams corresponding to the actually accessed beam information requested to be reported should be one or more of the beam ID and / or ID list. The beam may be an SSB beam or other beams.

[1011] Number of slices: the number of slices corresponding to the actually accessed beam information requested to be reported.

[1012] Slice ID and / or ID list: the slices corresponding to the requested actually accessed beam information. For example, the slices corresponding to the actually accessed beam information requested to be reported should be one or more of the slice ID and / or ID list.

[1013] In some implementations, the sixteenth node may transmit a twenty-third message containing a reporting response of actually accessed beam information to the fifteenth node, so as to inform the fifteenth node whether the sixteenth node can report the actually accessed beam information, so that the fifteenth node can know whether the content requested to be reported can be received from the sixteenth node subsequently. In some implementations, for example, if the twenty-third message received by the fifteenth node indicates that the sixteenth node can report the actually accessed beam information, the fifteenth node can subsequently receive the actually accessed beam information reported by the sixteenth node, for example, through a twenty-fourth message. In some other implementations, for example, the fifteenth node may also transmit a message for stoping (and / or cancelling) reporting to the sixteenth node based on the information indicated in the received twenty-third message, for example, to stop (and / or cancel) reporting through the twenty-second message.

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

[1015] Transmitting node ID: used to identify the node that transmits the message.

[1016] Receiving node ID: used to identify the node that receives the message.

[1017] Measurement ID: used to identify this measurement. In some implementations, this ID may be consistent with the measurement ID in the twenty-second message, in order for associating the response with the request.

[1018] Request ID: used to identify a request corresponding to the response. In some implementations, this ID may be consistent with the request ID in the twenty-second message, in order for associating the response with the request.

[1019] Acknowledge of a request for actually accessed beam information: used to indicate whether the accessed beam information can be measured and / or reported. The acknowledge of a request for actually accessed beam information may be a bit indicating whether the request can be measured and / or reported.

[1020] UE ID for which reporting can be performed: ID(s) of user(s) corresponding to the actually accessed beam information that can be measured and / or reported. It may be an ID or an ID list.

[1021] Cell ID for which reporting can be performed: ID(s) of cell(s) corresponding to the actually accessed beam information that can be measured and / or reported. It may be an ID or an ID list.

[1022] Beam ID for which reporting can be performed: ID(s) of beam(s) corresponding to the actually accessed beam information that can be measured and / or reported. It may be an ID or an ID list.

[1023] Slice ID for which reporting can be performed: ID(s) of slice(s) corresponding to the actually accessed beam information that can be measured and / or reported. It may be an ID or an ID list.

[1024] Available reporting mode: used to indicate an available reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[1025] Available reporting periodicity: used to indicate an interval available for reporting. It may also be a time interval between two adjacent reportings that can be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[1026] Time available for reporting: indicates a time and / or time interval when a content can be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the twenty-second message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an 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 time available for reporting.

[1028] End time: used to indicate the end time of the time available for reporting.

[1029] Available measurement mode: used to indicate a mode available for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[1030] Measurement period avaliable for measurement: used to indicate a measurement period avaliable for measurement.

[1031] Available measurement time: used to indicate a measurement time and / or time interval when measurement can be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the twenty-second message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[1032] Start time: used to indicate the start time of a measurement time when measurement can be performed.

[1033] End time: used to indicate the end time of a measurement time when measurement can be performed.

[1034] Corresponding information that can be reported and / or measured: used to indicate information corresponding to the actually mearsured access beam information that can be reported and / or measured. It may include one or more of the following:

[1035] Number of slices: the number of slices corresponding to the actually accessed beam information that can be reported and / or measured.

[1036] Slice ID and / or ID list: the scope of slices corresponding to the actually accessed beam information that can be reported and / or measured. For example, the slices corresponding to the actually accessed beam information that can be reported and / or measured are one or more of the slice ID and / or ID list.

[1037] Number of cells: the number of cells corresponding to the actually accessed beam information that can be reported and / or measured.

[1038] Cell ID and / or ID list: the scope of cells corresponding to the actually accessed beam information that can be reported and / or measured. For example, the cells corresponding to the actually accessed beam information that can be reported and / or measured are one or more of the cell ID and / or ID list.

[1039] Number of beams: the number of beams corresponding to the actually accessed beam information that can be reported and / or measured.

[1040] Beam ID and / or ID list: the scope of beams corresponding to the actually accessed beam information that can be reported and / or measured. For example, the beams corresponding to the actually accessed beam information that can be reported and / or measured are one or more of the beam ID and / or ID list.

[1041] Number of nodes: the number of nodes corresponding to the actually accessed beam information that can be reported and / or measured.

[1042] Node ID and / or ID list: the scope of nodes corresponding to the actually accessed beam information that can be reported and / or measured. For example, the nodes corresponding to the actually accessed beam information that can be reported and / or measured are one or more of the node ID and / or ID list.

[1043] Trigger event and / or condition corresponding to a reporting and / or measurement that can be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that can be performed. When the event and / or condition that triggers reporting and / or measurement are met, reporting and / or measurement can be performed. The event and / or condition that triggers reporting includes one or more of the following:

[1044] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1045] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1046] The actually accessed beam is inconsistent with 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 that triggers reporting shall include one or more of the following configurations: event type and event.

[1047] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1048] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1049] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1050] Unavailable reporting mode: used to indicate an unavailable reporting mode. It may include single reporting, periodic reporting, on-demand reporting and event-triggered reporting, etc.

[1051] Unavailable reporting periodicity: used to indicate an interval unavailable for reporting. It may also be a time interval between two adjacent reportings that cannot be used for reporting. The time interval may be a maximum time interval or a minimum time interval. In some implementations, for example, the reporting periodicity may be a reporting interval of a periodic reporting mode.

[1052] Time unavailable for reporting: indicates a time and / or time interval when a content cannot be reported. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the twenty-second message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

[1053] Start time: used to indicate the start time of the time unavailable for reporting.

[1054] End time: used to indicate the end time of the time unavailable for reporting.

[1055] Unavailable measurement mode: used to indicate a mode unavailable for measurement. It may include single measurement, periodic measurement, on-demand measurement, event-triggered measurement, etc.

[1056] Measurement period unavaliable for measurement: used to indicate a measurement period unavaliable for measurement.

[1057] Unavailable measurement time: used to indicate a measurement time and / or time interval when measurement cannot be performed. The time may be a relative time or an absolute time. The time may also be a period of time or a time before or after an event. The event may be an event and / or condition that triggers measurement in the twenty-second message, or an event and / or condition that triggers reporting. The time interval may be expressed by a timer, a combination of a start time and an end time, and a combination of a start time and a time duration, etc. If it is a time interval, it may be represented by 2*n bits, for example, the first n bits represent a start time and the last n bits represent an end time. It may also be represented by separate fields, including one or more of the following:

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

[1059] End time: used to indicate the end time of a measurement time when measurement cannot be performed.

[1060] Corresponding information that cannot be reported and / or measured: used to indicate information corresponding to the actually accessed beam information that cannot be reported and / or measured. It may include one or more of the following:

[1061] Number of slices: the number of slices corresponding to the actually accessed beam information that cannot be reported and / or measured.

[1062] Slice ID and / or ID list: the scope of slices corresponding to the actually accessed beam information that cannot be reported and / or measured. For example, the slices corresponding to the actually accessed beam information that cannot be reported and / or measured are one or more of the slice ID and / or ID list.

[1063] Number of cells: the number of cells corresponding to the actually accessed beam information that cannot be reported and / or measured.

[1064] Cell ID and / or ID list: the scope of cells corresponding to the actually accessed beam information that cannot be reported and / or measured. For example, the cells corresponding to the actually accessed beam information that cannot be reported and / or measured are one or more of the cell ID and / or ID list.

[1065] Number of beams: the number of beams corresponding to the actually accessed beam information that cannot be reported and / or measured.

[1066] Beam ID and / or ID list: the scope of beams corresponding to the actually accessed beam information that cannot be reported and / or measured. For example, the beams corresponding to the actually accessed beam information that cannot be reported and / or measured are one or more of the beam ID and / or ID list.

[1067] Number of nodes: the number of nodes corresponding to the actually accessed beam information that cannot be reported and / or measured.

[1068] Node ID and / or ID list: the scope of nodes corresponding to the actually accessed beam information that cannot be reported and / or measured. For example, the nodes corresponding to the actually accessed beam information that cannot be reported and / or measured are one or more of the node ID and / or ID list.

[1069] Trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed: indicates a trigger event and / or condition corresponding to a reporting and / or measurement that cannot be performed. When the event and / or condition that triggers reporting and / or measurement are met, the reporting and / or measurement cannot be performed. The event and / or condition that triggers reporting includes one or more of the following:

[1070] UE accesses to a target cell. When the UE accesses to a target cell, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1071] A cell switch notification is received. When the message receiving node receives a cell switch notification message, reporting can be performed. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1072] The actually accessed beam is inconsistent with 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 that triggers reporting shall include one or more of the following configurations: event type and event.

[1073] UE accesses a target cell. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1074] UE receives a handover command and / or an LTM cell switch command. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

[1075] Handover occurs. The event and / or condition that triggers reporting shall include one or more of the following configurations: event type and event.

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

[1077] In some implementations, the sixteenth node may report a twenty-fourth message containing actually accessed beam information obtained by the sixteenth node to the fifteenth node according to its own situation and / or according to the twenty-second message containing a reqeust for reporting actually accessed beam information received from the fifteenth node. In some implementations, for example, the fifteenth node can use the actually accessed beam information to evaluate whether the predicted beam information is appropriate. For example, if the actually accessed beam information is inconsistent with the predicted beam information, it means that the predicted beam information is inappropriate; and if the actually accessed beam information is consistent with the predicted beam information, it means that the predicted beam information is appropriate. In another implementation, for example, the fifteenth node can use the actually accessed beam information to support an artificial intelligence machine learning function. For example, the actually accessed beam information may be used as an input parameter to train an artificial intelligence machine learning model, which may be a model for predicting beam information or a model for generating a handover decision; or the actually accessed beam information may be used to evaluate an artificial intelligence machine learn model, for example, to evaluate whether a model can continue to be used, whether a model needs to be trained and / or adjusted, etc.

[1078] In some implementations, the twenty-fourth message may include one or more of the following information and / or fields:

[1079] Transmitting node ID: used to identify the node that transmits the message.

[1080] Receiving node ID: used to identify the node that receives the message.

[1081] Measurement and / or prediction ID: used to identify a measurement and / or prediction. In some implementations, this ID may be consistent with the measurement and / or prediction ID in the twenty-second message and / or the twenty-third message, in order for associating the reporting with the request and / or response.

[1082] Request ID: used to identify a request corresponding to the reporting. In some implementations, this ID may be consistent with the request ID in the twenty-second message and / or the twenty-third message, in order for associating the reporting with the request and / or response.

[1083] UE identification (ID): indicates the user corresponding to the reported actually accessed beam information. It may be a UE ID or a list of UE IDs.

[1084] Cell ID: indicates the cell corresponding to the reported actually accessed beam information. It may be a cell ID or a list of cell IDs.

[1085] Beam ID: indicates the beam corresponding to the reported actually accessed beam information. It may be a beam ID or a list of beam IDs.

[1086] Slice ID: indicates the slice corresponding to the reported actually accessed beam information. It may be a slice ID or a list of slice IDs.

[1087] Actually accessed beam information: indicates the reported actually accessed beam information. The actually accessed 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.

[1088] Appli...

Claims

1.A method performed by a first node in a wireless communication system, the method comprising:receiving a first message including at least one of mobility information or an L3 measurement result related to a terminal, from a second node;determining a first timing advance (TA) value based on at least one of the mobility information, an L1 measurement result, or the L3 measurement result related to the terminal;transmitting a second message including the first TA value, wherein the first TA value is used for the terminal to access a target cell when performing handover, to the terminal; andreceiving a third message including a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate, from the second node.2.The method of claim 1, whereinthe second TA value is received by the second node from a target node to which the terminal is handed over.3.The method of claim 1, further comprising:receiving load-related information of a neighboring cell from the second node, wherein the neighboring cell includes a candidate target cell; andmaking a mobility decision based on the load-related information of the neighboring cell.4.The method of claim 3, wherein the load-related information of the neighboring cell includes at least one of the following:load information of the neighboring cell;information indicating a situation that load of the neighboring cell is too large; orinformation related to a load amount that the neighboring cell can receive.5.A method performed by a second node in a wireless communication system, comprising:transmitting a first message including at least one of mobility information or an L3 measurement result related to a terminal, to a first node, wherein at least one of the mobility information, the L3 measurement result, or an L1 measurement result related to the terminal is used for the first node to determine a first timing advance (TA) value; andtransmitting a third message including a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate, to the first node,wherein the first TA value is used for the terminal to access a target cell when performing handover.6.The method of claim 5, further comprising:receiving the second TA value from a target node to which the terminal is handed over.7.The method of claim 5, further comprising:transmitting, to the first node, at least one of a fourth message including load information of a neighboring cell, a fifth message including information indicating a situation that load of the neighboring cell is too large, or a sixth message including information of a load amount that the neighboring cell can receive, wherein the neighboring cell includes a candidate target cell; andwherein at least one of the load information of the neighboring cell, the information indicating a situation that load of the neighboring cell is too large, or the information of the load amount that the neighboring cell can receive is used for the first node to make a mobility decision.8.The method of claim 5, further comprising:transmitting a seventh message including information indicating activation or deactivation of a candidate target cell, to the first node,wherein the information indicating activation or deactivation of a candidate target cell is used for the first node to make a mobility decision.9.A first node device in a wireless communication system, comprising:a transceiver; anda processor coupled to the transceiver and configured to perform a method comprising:receiving a first message including at least one of mobility information or an L3 measurement result related to a terminal, from a second node;determining a first timing advance (TA) value based on at least one of the mobility information, an L1 measurement result, or the L3 measurement result related to the terminal;transmitting a second message including the first TA value, wherein the first TA value is used for the terminal to access a target cell when performing handover, to the terminal; andreceiving a third message including a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate, from the second node.10.The first node device of claim 9, whereinthe second TA value is received by the second node from a target node to which the terminal is handed over.11.The first node device of claim 9, themethod further comprising:receiving load-related information of aneighboring cell from the second node, wherein the neighboring cell includes acandidate target cell; andmaking a mobility decision based on theload-related information of the neighboring cell.12.The first node device of claim 11, wherein the load-related information of the neighboring cell includes at least one of the following:load information of the neighboring cell;information indicating a situation that load of the neighboring cell is too large; orinformation related to a load amount that the neighboring cell can receive.13.A second node device in a wireless communication system, comprising:a transceiver; anda processor coupled to the transceiver and configured to perform a method comprising:transmitting a first message including at least one of mobility information or an L3 measurement result related to a terminal, to a first node, wherein at least one of the mobility information, the L3 measurement result, or an L1 measurement result related to the terminal is used for the first node to determine a first timing advance (TA) value; andtransmitting a third message including a second TA value, wherein the second TA value is used for evaluating whether the first TA value is appropriate, to the first node,wherein the first TA value is used for the terminal to access a target cell when performing handover.14.The second node device of claim 13, the method further comprising:receiving the second TA value from a target node to which the terminal is handed over.15.The second node device of claim 13, the method further comprising:transmitting, to the first node, at least one of a fourth message including load information of a neighboring cell, a fifth message including information indicating a situation that load of the neighboring cell is too large, or a sixth message including information of a load amount that the neighboring cell can receive, wherein the neighboring cell includes a candidate target cell; andwherein at least one of the load information of the neighboring cell, the information indicating a situation that load of the neighboring cell is too large, or the information of the load amount that the neighboring cell can receive is used for the first node to make a mobility decision.

Images