Node in wireless communication system, user equipment and method performed by same

Abstract

The invention provides a node in a wireless communication system, user equipment and a method performed by the same. The method executed by a first node in a wireless communication system provided by the present disclosure comprises: sending a fourth message to a second node, the fourth message comprising information related to resource reservation time in conditional switching; receiving a second message including a data transmission address of a candidate target cell from the second node; receiving a sixth message from the second node or a user equipment (UE), the sixth message comprising prediction information related to conditional switching; determining whether to carry out data transmission or not based on the prediction information related to the condition switching; and under the condition that data transmission is determined to be carried out, carrying out data transmission based on the data transmission address. According to the method disclosed by the invention, the continuity of services can be ensured in a switching scene.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more particularly, to a node, a user equipment and a method executed by the node in a wireless communication system. Background Art

[0002] In order to meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems."

[0003] Wireless communication is one of the most successful innovations in modern history. The number of subscribers to wireless communication services recently exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (e.g., tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and enterprises. In order to meet the high growth of mobile data services and support new applications and deployments, it is critical to improve the efficiency and coverage of the wireless interface.

[0004] During the switching process, the source node may send the user's relevant data to the target node before the user accesses the target node, so that the user can quickly obtain the relevant data after accessing the target node, thereby avoiding service interruption caused by the switching.

[0005] In the process of conditional secondary node modification and / or addition, the UE and candidate target secondary node may retain the configuration as the configuration for subsequent secondary node modification and / or addition. This process has at least one of the following problems:

[0006] 1. In this case, the candidate target auxiliary node needs to reserve resources for a long time. Due to the limited nature of resources, long-term resource reservation may cause other users to suffer performance damage due to resource shortage.

[0007] 2. After the user switches to a target secondary node, when the user changes the secondary node subsequently, the target secondary node cannot forward data to other target secondary nodes, thereby failing to ensure business continuity.

[0008] 3. Because the configuration can be retained for a long time, as the user moves, there is no need to forward data to each alternative target node, resulting in a waste of data transmission.

[0009] How to select the target node for data forwarding and when to trigger data forwarding have a great impact on improving the effectiveness of data forwarding. Summary of the invention

[0010] An embodiment of the present disclosure provides a method performed by a first node in a wireless communication system, comprising: sending a fourth message to a second node, wherein the fourth message includes information related to a resource reservation time in a conditional switching; receiving a second message including a data transmission address of a candidate target cell from the second node; receiving a sixth message from the second node or a user equipment UE, wherein the sixth message includes prediction information related to the conditional switching; determining whether to perform data transmission based on the prediction information related to the conditional switching; and in the case of determining to perform data transmission, performing data transmission based on the data transmission address.

[0011] An embodiment of the present disclosure provides a method performed by a second node in a wireless communication system, comprising: receiving a fourth message from a first node, wherein the fourth message includes information related to a resource reservation time in a conditional switching; sending a second message including a data transmission address of a candidate target cell to the first node; and sending a sixth message to the first node, wherein the sixth message includes prediction information related to the conditional switching; wherein the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission; and wherein, in the case of determining to perform data transmission, the first node performs data transmission based on the data transmission address.

[0012] An embodiment of the present disclosure provides a method executed by a user equipment UE in a wireless communication system, comprising: receiving a fourth message from a second node, wherein the fourth message includes an RRC container, and the RRC container includes information related to resource reservation time in conditional switching; and sending a sixth message to the second node or the first node, wherein the sixth message includes prediction information related to the conditional switching, and the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission.

[0013] An embodiment of the present disclosure provides a first node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the first node in the wireless communication system according to an embodiment of the present disclosure.

[0014] An embodiment of the present disclosure provides a second node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the second node in the wireless communication system according to an embodiment of the present disclosure.

[0015] An embodiment of the present disclosure provides a user equipment UE in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the user equipment UE in the wireless communication system according to an embodiment of the present disclosure.

[0016] An embodiment of the present disclosure provides a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, are used to implement a method performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to an embodiment of the present disclosure.

[0017] The method provided by the present disclosure and executed by the first node and / or the second node and / or the user equipment in the wireless communication system can ensure the continuity of the service by exchanging the conditional switching related information between the nodes. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0019] Figure 1 is an exemplary system architecture 100 of System Architecture Evolution (SAE);

[0020] Figure 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

[0021] Figures 3A-3L Schematic diagrams of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure are respectively shown;

[0022] Figures 4A-4K Schematic diagrams of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure are respectively shown;

[0023] Figure 5A-5G Schematic diagrams of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure are respectively shown;

[0024] Figure 6 A flowchart of a method performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0025] Figure 7 A flowchart of a method performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0026] Figure 8 A flow chart of a method performed by a user equipment in a wireless communication system according to an embodiment of the present disclosure is shown;

[0027] Fig. 9 A schematic diagram of a first node according to an embodiment of the present disclosure is shown;

[0028] Fig.10 A schematic diagram of a second node according to an embodiment of the present disclosure is shown;

[0029] Fig.11 A schematic diagram of a user equipment according to an embodiment of the present disclosure is shown; and

[0030] Figures 11A-11B Schematic diagrams of one aspect of a node execution method according to an embodiment of the present disclosure are respectively shown. DETAILED DESCRIPTION

[0031] The following description with reference to the accompanying drawings is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to facilitate understanding but should be considered as exemplary only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

[0032] The terms and expressions used in the following specification and claims are not limited to their dictionary meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, 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 purposes only and not for the purpose of limiting the present disclosure as defined in the appended claims and their equivalents.

[0033] It should 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.

[0034] The term "include" or "may include" refers to the presence of the corresponding disclosed functions, operations or components that can be used in various embodiments of the present disclosure, rather than limiting the presence of one or more additional functions, operations or features. In addition, the term "include" or "have" may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

[0035] The term "or" used in various embodiments of the present disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.

[0036] Unless defined differently, all terms (including technical terms or scientific terms) used in the present disclosure have the same meanings as understood by those skilled in the art described in the present disclosure. Common terms as defined in dictionaries are interpreted as having meanings consistent with the context in the relevant technical field, and should not be interpreted ideally or overly formally unless clearly defined in the present disclosure.

[0037] An embodiment of the present disclosure provides a method performed by a first node in a wireless communication system, comprising: sending a fourth message to a second node, wherein the fourth message includes information related to a resource reservation time in a conditional switching; receiving a second message including a data transmission address of a candidate target cell from the second node; receiving a sixth message from the second node or a user equipment UE, wherein the sixth message includes prediction information related to the conditional switching; determining whether to perform data transmission based on the prediction information related to the conditional switching; and in the case of determining to perform data transmission, performing data transmission based on the data transmission address.

[0038] According to an embodiment of the present disclosure, before receiving a second message including a data transmission address of a candidate target cell from the second node, a radio resource control RRC reconfiguration complete message is sent by the UE to the second node.

[0039] According to an embodiment of the present disclosure, the information related to the resource reservation time in the conditional switching is used by the second node to determine whether to use the first node as a candidate target node.

[0040] According to an embodiment of the present disclosure, the method further includes: sending a first message including a request for a data transmission address to the second node, wherein the second message is sent from the second node based on the first message.

[0041] According to an embodiment of the present disclosure, the method also includes: receiving a third message from the second node, wherein the third message includes information related to the user equipment UE in the conditional switching and / or information related to the resource reservation request in the conditional switching, and wherein the fourth message is sent to the second node based on the third message.

[0042] According to an embodiment of the present disclosure, the method further includes: sending a fifth message to the second node, wherein the fifth message includes a request for reporting prediction information related to conditional switching, and wherein the sixth message is sent from the second node based on the fifth message.

[0043] According to an embodiment of the present disclosure, the data transmission includes one or more of normal data transmission and data forwarding, wherein the data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

[0044] According to an embodiment of the present disclosure, the second message includes one or more of the following: an identifier of the UE performing conditional switching, a request index corresponding to the second message, an accepted quality of service QoS flow identifier, a transmission address, a data transmission direction corresponding to the transmission address, information on whether data transmission is triggered, an identifier for triggering data transmission, an event for triggering data transmission, a cell identifier corresponding to the transmission address, a node identifier corresponding to the transmission address, a slice identifier corresponding to the transmission address, a protocol data unit PDU session identifier corresponding to the transmission address, a wireless bearer identifier corresponding to the transmission address, a quality of service QoS flow identifier corresponding to the transmission address, and information that can be used for data transmission.

[0045] According to an embodiment of the present disclosure, the first message includes one or more of the following: an identifier of the UE performing conditional switching, a request index, an identifier for requesting address reporting, a direction of data transmission, a cell identifier corresponding to the requested transmission address, a node identifier corresponding to the requested transmission address, a slice identifier corresponding to the requested transmission address, a protocol data unit PDU session identifier corresponding to the requested transmission address, a wireless bearer identifier corresponding to the requested transmission address, a quality of service QoS flow identifier corresponding to the requested transmission address, and requested information for data transmission.

[0046] According to an embodiment of the present disclosure, the fourth message includes one or more of the following: a cell identifier corresponding to the information related to the resource reservation time in the conditional switching, a node identifier corresponding to the information related to the resource reservation time in the conditional switching, a slice identifier corresponding to the information related to the resource reservation time in the conditional switching, a UE identifier performing conditional switching corresponding to the information related to the resource reservation time in the conditional switching, the maximum resource reservation time, the minimum resource reservation time, the resource reservation time interval, and the applicable time corresponding to the switching configuration.

[0047] According to an embodiment of the present disclosure, the third message includes one or more of the following: a cell identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a node identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a slice identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a UE identifier for conditional switching corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, an expected maximum arrival probability of the UE, a time corresponding to the expected maximum arrival probability of the UE, an expected minimum arrival probability of the UE, a time corresponding to the expected minimum arrival probability of the UE, an expected arrival time of the UE, an expected arrival probability of the UE, a time corresponding to the expected arrival probability of the UE, a request for maximum resource reservation time, a request for minimum resource reservation time, a request for resource reservation time interval, a request for resource reservation time, an indication of whether setting the resource reservation time is allowed, and prediction credibility.

[0048] According to an embodiment of the present disclosure, the sixth message includes one or more of the following: a request identifier corresponding to the sixth message, a sending node identifier, a receiving node identifier, a user identifier corresponding to the reported information, measured and / or predicted content, reported content, an event triggering the report, the applicable time corresponding to the measured content, and the applicable time corresponding to the reported content.

[0049] According to an embodiment of the present disclosure, the fifth message includes one or more of the following: a request identifier, a sending node identifier, a receiving node identifier, a UE identifier corresponding to the requested information, a reporting mode, a reporting time, a reporting period, a reporting trigger event, a measurement and / or prediction mode, a measurement and / or prediction time, a measurement and / or prediction period, requested measurement and / or prediction content, requested reporting content, the applicable time corresponding to the requested reporting content, the requested prediction time, the requested reporting credibility requirement, and the prediction credibility.

[0050] An embodiment of the present disclosure provides a method performed by a second node in a wireless communication system, comprising: receiving a fourth message from a first node, wherein the fourth message includes information related to a resource reservation time in a conditional switching; sending a second message including a data transmission address of a candidate target cell to the first node; and sending a sixth message to the first node, wherein the sixth message includes prediction information related to the conditional switching; wherein the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission; and wherein, in the case of determining to perform data transmission, the first node performs data transmission based on the data transmission address.

[0051] According to an embodiment of the present disclosure, before sending a second message including a data transmission address of a candidate target cell to the first node, the method further includes: receiving a radio resource control RRC reconfiguration complete message from a user equipment UE.

[0052] According to an embodiment of the present disclosure, the method further includes: determining whether to use the first node as a candidate target node based on information related to the resource reservation time in the conditional switching.

[0053] According to an embodiment of the present disclosure, the method further includes: receiving a first message including a request for a data transmission address from the first node, wherein the second message is sent to the first node based on the first message.

[0054] According to an embodiment of the present disclosure, the method also includes: sending a third message to the first node, wherein the third message includes information related to the user equipment UE in the conditional switching and / or information related to the resource reservation request in the conditional switching, and wherein the fourth message is sent from the first node based on the third message.

[0055] According to an embodiment of the present disclosure, the method further includes: receiving a fifth message from the first node, wherein the fifth message includes a request for reporting prediction information related to conditional switching, and wherein the sixth message is sent to the first node based on the fifth message.

[0056] According to an embodiment of the present disclosure, the data transmission includes one or more of normal data transmission and data forwarding, wherein the data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

[0057] According to an embodiment of the present disclosure, the second message includes one or more of the following: an identifier of the UE performing conditional switching, a request index corresponding to the second message, an accepted quality of service QoS flow identifier, a transmission address, a data transmission direction corresponding to the transmission address, information on whether data transmission is triggered, an identifier for triggering data transmission, an event for triggering data transmission, a cell identifier corresponding to the transmission address, a node identifier corresponding to the transmission address, a slice identifier corresponding to the transmission address, a protocol data unit PDU session identifier corresponding to the transmission address, a wireless bearer identifier corresponding to the transmission address, a quality of service QoS flow identifier corresponding to the transmission address, and information that can be used for data transmission.

[0058] According to an embodiment of the present disclosure, the first message includes one or more of the following: an identifier of the UE performing conditional switching, a request index, an identifier for requesting address reporting, a direction of data transmission, a cell identifier corresponding to the requested transmission address, a node identifier corresponding to the requested transmission address, a slice identifier corresponding to the requested transmission address, a protocol data unit PDU session identifier corresponding to the requested transmission address, a wireless bearer identifier corresponding to the requested transmission address, a quality of service QoS flow identifier corresponding to the requested transmission address, and requested information for data transmission.

[0059] According to an embodiment of the present disclosure, the fourth message includes one or more of the following: a cell identifier corresponding to the information related to the resource reservation time in the conditional switching, a node identifier corresponding to the information related to the resource reservation time in the conditional switching, a slice identifier corresponding to the information related to the resource reservation time in the conditional switching, a UE identifier performing conditional switching corresponding to the information related to the resource reservation time in the conditional switching, the maximum resource reservation time, the minimum resource reservation time, the resource reservation time interval, and the applicable time corresponding to the switching configuration.

[0060] According to an embodiment of the present disclosure, the third message includes one or more of the following: a cell identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a node identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a slice identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a UE identifier for conditional switching corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, an expected maximum arrival probability of the UE, a time corresponding to the expected maximum arrival probability of the UE, an expected minimum arrival probability of the UE, a time corresponding to the expected minimum arrival probability of the UE, an expected arrival time of the UE, an expected arrival probability of the UE, a time corresponding to the expected arrival probability of the UE, a request for maximum resource reservation time, a request for minimum resource reservation time, a request for resource reservation time interval, a request for resource reservation time, an indication of whether setting the resource reservation time is allowed, and prediction credibility.

[0061] According to an embodiment of the present disclosure, the sixth message includes one or more of the following: a request identifier corresponding to the sixth message, a sending node identifier, a receiving node identifier, a user identifier corresponding to the reported information, measured and / or predicted content, reported content, an event triggering the report, the applicable time corresponding to the measured content, and the applicable time corresponding to the reported content.

[0062] According to an embodiment of the present disclosure, the fifth message includes one or more of the following: a request identifier, a sending node identifier, a receiving node identifier, a UE identifier corresponding to the requested information, a reporting mode, a reporting time, a reporting period, a reporting trigger event, a measurement and / or prediction mode, a measurement and / or prediction time, a measurement and / or prediction period, requested measurement and / or prediction content, requested reporting content, the applicable time corresponding to the requested reporting content, the requested prediction time, the requested reporting credibility requirement, and the prediction credibility.

[0063] An embodiment of the present disclosure provides a method executed by a user equipment UE in a wireless communication system, comprising: receiving a fourth message from a second node, wherein the fourth message includes an RRC container, and the RRC container includes information related to resource reservation time in conditional switching; and sending a sixth message to the second node or the first node, wherein the sixth message includes prediction information related to the conditional switching, and the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission.

[0064] According to an embodiment of the present disclosure, the method further includes: based on the information related to the resource reservation time in the conditional switching, detecting whether the operation event is satisfied.

[0065] An embodiment of the present disclosure provides a first node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the first node in the wireless communication system according to an embodiment of the present disclosure.

[0066] An embodiment of the present disclosure provides a second node device in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the second node in the wireless communication system according to an embodiment of the present disclosure.

[0067] An embodiment of the present disclosure provides a user equipment UE in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the user equipment UE in the wireless communication system according to an embodiment of the present disclosure.

[0068] An embodiment of the present disclosure provides a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, are used to implement a method performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to an embodiment of the present disclosure.

[0069] The method provided by the present disclosure and executed by the first node and / or the second node and / or the user equipment in the wireless communication system can ensure the continuity of the service by exchanging the conditional switching related information between the nodes.

[0070] The accompanying drawings discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0071] Figure 1 It is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides a wireless network interface for the UE to access. The Mobility Management Entity (MME) 103 is responsible for managing the mobility context, session context and security information of the UE. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, and the packet data context of the user equipment.

[0072] Figure 2 is 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.

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

[0074] The entities and / or nodes described in the present disclosure may include: gNB, gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), gNB-CU-Control Plane (gNB CU-CP)), gNB-CU-User Plane (gNB CU-UP)), en-gNB, eNB, ng-eNB, UE, Access and Mobility Management Function (Access and Mobility Management Function (AMF)), Session Management Function (Session Management Function (SMF)), Mobility Management Entity (Mobility Management Entity (MME)) and other network entities or network logical units.

[0075] The signal strength and / or signal quality described in the present disclosure may be a received signal strength indicator (RSSI), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a signal to interference plus noise ratio (SINR), etc.

[0076] The handover described in the present disclosure may include any situation where a user access node and / or a cell changes, for example, may include one or more of the following: handover, secondary node addition, secondary node change, primary node change, etc.

[0077] The data transmission described in the present disclosure may include (normal) data transmission (Data Transmission), data forwarding (Data Forwarding), etc. Wherein data forwarding includes early data forwarding (Early Data Forwarding), late data forwarding (Late Data Forwarding), (normal) data forwarding, data transmission replicated by the Packet Data Convergence Protocol layer (PDCP), etc.

[0078] The data transmission described in the present disclosure may be from one node to another, from an old node to a new node, from a source node to a target node, from a primary node to a secondary node, from a source primary node to a target secondary node, from an old secondary node to a new secondary node, from a source secondary node to a new secondary node, from an old primary node to a new primary node, from a source primary node to a target primary node, from a secondary node to a primary node, etc.

[0079] In the present disclosure, the node may refer to a node or a cell managed by a node. For example, the target node may refer to a target node or a target cell.

[0080] In the present disclosure, the cell may refer to a cell or a node where a cell is located.

[0081] In the present disclosure, a source node may refer to a source node, a source auxiliary node, a source main node, or any other source node in a switch.

[0082] In the present disclosure, a target node may also refer to a candidate target secondary node.

[0083] In the present disclosure, a target node may refer to a target node, a target secondary node, a target primary node, a candidate target node, a candidate target secondary node, a candidate target primary node, or any other target node in a switch.

[0084] In the present disclosure, an operation event and an operation condition may refer to each other.

[0085] The method provided by the present disclosure and performed by the first node and / or the second node and / or the user equipment in the wireless communication system may also be referred to as a method for supporting mobility management.

[0086] Example 1

[0087] In some embodiments, the present disclosure proposes a method for supporting mobility management, which may include: a first node sends a first message including a request for a data transmission address to a second node, so that the second node sends the relevant data transmission address to the first node, and after the first node obtains the address for the data transmission, the data is sent according to the obtained address and / or the address stored by itself, or the first node stores the address after obtaining the address, does not trigger data transmission, and provides reference information for subsequent data transmission. In some embodiments, for example, after the first node obtains the address for data transmission (for example, data forwarding), before the user accesses the target node and / or cell, the first node performs data forwarding to send the relevant data to the relevant target node and / or cell, so as to ensure that the UE can quickly receive the relevant data after the switch, so as to ensure the service continuity of the UE.

[0088] In some embodiments, the first message may be or may be carried by one or more of the following messages: Xn's Xn-U address indication (XN-U ADDRESS INDICATION) message or an early state transfer (EARLY STATUSTRANSFER) message or a handover success (HANDOVER SUCCESS) message or an addition request acknowledgement (S-NODEADDITION REQUEST ACKNOWLEDGE) message or a secondary node modification request acknowledgement (S-NODE MODIFICATIONREQUEST ACKNOWLEDGE) message, or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container.

[0089] In some implementations, the first message may include one or more of the following fields or related information:

[0090] UE identity: used to identify the UE that performs (conditional) switching. It may include one or more of the following: a user identity assigned by the new node, a user identity assigned by the old node, a user identity assigned by the source node, a user identity assigned by the auxiliary node, a user identity assigned by the primary node, a user identity assigned by the auxiliary node, a user identity assigned by the first message sending node, a user identity assigned by the first message receiving node, etc. The identity may be one identity, multiple identities, or an identity list.

[0091] ●Request index: used to identify the request.

[0092] ● Flag for requesting address reporting: used to indicate whether to request reporting of address information. The flag can be represented by a single bit. For example, when the bit is 1, it indicates requesting reporting of address information, and when the bit is 0, it indicates not requesting reporting of address information. Alternatively, when the field appears, it indicates requesting reporting of address information, and when the field does not appear, it indicates not requesting reporting of address information.

[0093] ●Data transmission direction: used to indicate the data transmission direction corresponding to the requested address. The direction includes one or more of the following: uplink, downlink, uplink or downlink, uplink and downlink.

[0094] ●Cell ID: The cell ID corresponding to the requested transmission address is used to indicate which cell and / or cells the requested address is for. The ID can be one ID, multiple IDs, or an ID list.

[0095] ●Node ID: The node ID corresponding to the requested transmission address is used to identify which node and / or nodes the requested address is for. The ID can be one ID, multiple IDs, or an ID list.

[0096] ● Slice ID: The slice ID corresponding to the requested transmission address is used to identify which slice and / or which slices the requested address is for. The ID can be one ID, multiple IDs, or an ID list.

[0097] ● Protocol Data Unit (PDU) session identifier: The protocol data unit PDU session identifier corresponding to the requested transmission address is used to identify which and / or which PDU sessions the requested address is for. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0098] ● Radio bearer identifier: The radio bearer identifier corresponding to the requested transport address is used to identify which and / or which radio bearers the requested address is for. The identifier can be one identifier, multiple identifiers, or an identifier list. The radio bearer can be a data radio bearer (DRB), a signaling radio bearer (SRB), etc.

[0099] ●Quality of Service (QoS) Flow Identifier: The QoS flow identifier corresponding to the requested transport address is used to identify which QoS flow and / or flows the requested address is for. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0100] ● Information requested for data transfer: may include one or more of the following:

[0101] ○QoS flow identifier: an identifier used to identify the requested QoS flow for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0102] ○ Radio bearer identifier: an identifier used to identify the radio bearer requested for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list. The radio bearer can be a data radio bearer (DRB) or a signaling radio bearer (SRB).

[0103] ○PDU session: an identifier for identifying the requested PDU session for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0104] ○Cell ID: an ID used to identify the cell for which data transmission is requested. The ID can be one ID, multiple IDs, or an ID list.

[0105] ○Node ID: an ID used to identify the node for the requested data transmission. The ID can be one ID, multiple IDs, or an ID list.

[0106] ○ Slice ID: an ID used to identify the slice for the requested data transmission. The ID can be one ID, multiple IDs, or an ID list.

[0107] In some embodiments, the second node may send a second message containing a data transmission address (e.g., a data transmission address of a candidate target cell) to the first node according to its own situation and / or after receiving a first message containing a data transmission address request. After receiving the address, the first node may perform relevant data transmission, such as (normal) data transmission (Data Transmission), data forwarding (Data Forwarding), etc. Wherein data forwarding includes early data forwarding (Early Data Forwarding), late data forwarding (Late Data Forwarding), (normal) data forwarding, etc. After receiving the address, the first node may also forward it to other nodes for other nodes to perform relevant data transmission, wherein the other nodes may be any nodes other than the second node. In some embodiments, for example, after the first node obtains the address for data transmission (e.g., data forwarding), before the user accesses the target node and / or cell, the first node performs data forwarding to send relevant data to the relevant target node and / or cell to ensure that the UE can quickly receive relevant data after switching to ensure service continuity of the UE.

[0108] In some embodiments, the second message may be or may be carried by one or more of the following messages: an Xn-U address indication (XN-U ADDRESS INDICATION) message of Xn, an EARLY STATUS TRANSFER message, or another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container.

[0109] In some implementations, the second message may include one or more of the following fields or related information:

[0110] UE identity: used to identify the UE that performs (conditional) switching. It may include one or more of the following: a user identity assigned by the new node, a user identity assigned by the old node, a user identity assigned by the source node, a user identity assigned by the auxiliary node, a user identity assigned by the primary node, a user identity assigned by the auxiliary node, a user identity assigned by the first message sending node, a user identity assigned by the first message receiving node, etc. The identity may be one identity, multiple identities, or an identity list.

[0111] ● The request index corresponding to the report: used to identify the request index corresponding to the report. It can also be called the request index corresponding to the second message. The request index can be used to inform the receiving node of the message which request the reported content is for.

[0112] ● Accepted QoS flow identifier: an identifier used to identify the QoS flow accepted for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0113] ●Transmission address: The address may be transport layer information, and may include one or more of the following: transport layer address, tunnel endpoint identifier (TEID), QoS mapping relationship, etc. The QoS mapping relationship may include one or more of the following: flow label, differentiated services code point, etc. The address may be for one or more of uplink transmission, downlink transmission, uplink transmission or downlink transmission, uplink transmission and downlink transmission.

[0114] ●The transmission direction corresponding to the transmission address: the direction includes one or more of the following: uplink, downlink, uplink or downlink, uplink and downlink.

[0115] ● Information on whether to trigger data transmission: This may include one or more of the following:

[0116] ○ An identifier for retaining address information but not performing data transmission: used to inform the node and / or other nodes that receive the message to retain the address information but not trigger data transmission.

[0117] ○ An identifier for triggering data transmission: used to indicate that the message can trigger the receiving node of the message and / or other nodes to perform data transmission.

[0118] ○ Events triggering data transmission: When the events triggering data transmission are met, data transmission can be triggered. This information can avoid unnecessary data transmission, such as premature data transmission, late data transmission, unnecessary data transmission, etc. For example, it effectively prevents unnecessary data transmission when a user accesses a cell for a short time and / or the user does not access a cell for a long time. It can include one of the following events or a combination of multiple events (for example, it can be that multiple events need to be met at the same time, or it can be that at least one of the multiple events is met) and the corresponding information in the event:

[0119] ■Event 1: When the time when the user accesses the cell meets a certain predetermined time, for example, greater than and / or equal to and / or less than a threshold time, data transmission can be triggered. The event needs to include event type, event content, information related to the predetermined time, etc. The information related to the predetermined time can be a threshold time or a timer. For example, when the user accesses the cell, a timer is started, and data transmission can be triggered when the timer times out, or data transmission can be triggered within the timer time.

[0120] ■Event 2: A predetermined time has passed after the address information is received. For example, the timing may be started after the address is received, and data transmission may be triggered when the counted time is greater than and / or equal to and / or less than a threshold time. The event needs to include the event type, event content, information related to the predetermined time, etc. The information related to the predetermined time may be a threshold time or a timer. For example, when the address information is received, the timer is started, and when the timer times out, data transmission may be triggered, or data transmission may be triggered within the timer time.

[0121] ■Event three: User access to the cell can trigger data transmission.

[0122] ■Event 4: Receiving address information can trigger data transmission.

[0123] ■Event 5: When the signal quality measured by the user and / or the node meets certain conditions, data transmission can be triggered. For example, when the signal quality is greater than and / or equal to and / or less than a threshold value (or when the signal quality is in a certain interval) and / or the event that meets the conditions is greater than and / or equal to and / or less than a threshold time, data transmission can be triggered. The event needs to include event type, event content, condition-related information, etc. The condition-related information can be a signal quality threshold value, a threshold time when the signal quality meets the conditions, etc.

[0124] ■Event 6: When the user's trajectory is within a certain range and / or when the user's trajectory is outside a certain range, data transmission can be triggered. The event needs to include event type, event content, range-related information, etc. The range can be a certain geographical area, one or more cells, the coverage range of one or more nodes, or one or more beam coverage ranges. Range-related information may include one or more of the following: geographical coordinates corresponding to the geographical area, cell identifiers and / or identifier lists, node identifiers and / or identifier lists, beam identifiers and / or identifier lists.

[0125] ■Event seven: When the user needs to be switched, data transmission can be triggered.

[0126] ■Event 8: When a node decides to switch to energy-saving mode, data transmission can be triggered. For example, when a node is about to enter energy-saving mode, data transmission can be triggered.

[0127] ■Event 9: When the current time from the time the node plans to enter the energy-saving mode meets certain predetermined time information, for example, greater than and / or equal to and / or less than a certain time threshold, data transmission can be triggered. This event needs to include event type, event content, information related to the scheduled time, etc. The information related to the scheduled time can be a threshold time or a timer. For example, when the current time from the time the node plans to enter the energy-saving mode is less than a certain time threshold, data transmission can be triggered.

[0128] ■ Event 10: When receiving information that the target node of data transmission is about to switch to energy-saving mode, data transmission can be triggered. For example, when receiving information that the target node of data transmission is about to switch from energy-saving mode to non-energy-saving mode, data transmission can be triggered.

[0129] ●Cell ID: The cell ID corresponding to the transmission address is used to indicate which cell and / or cells the reported address is for. The ID can be one ID, multiple IDs, or an ID list.

[0130] ●Node ID: The node ID corresponding to the transmission address is used to identify which node and / or nodes the reported address is for. The ID can be one ID, multiple IDs, or an ID list.

[0131] ● Slice ID: The slice ID corresponding to the transmission address is used to identify which slice and / or which slices the reported address is for. The ID can be one ID, multiple IDs, or an ID list.

[0132] ● Protocol Data Unit (PDU) session identifier: The protocol data unit PDU session identifier corresponding to the transmission address is used to identify which and / or which PDU sessions the reported address is for. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0133] ● Radio bearer identifier: The radio bearer identifier corresponding to the transmission address is used to identify which radio bearer and / or radio bearers the reported address is for. The identifier can be one identifier, multiple identifiers, or an identifier list. The radio bearer can be a data radio bearer (DRB) or a signaling radio bearer (SRB).

[0134] ●Quality of Service (QoS) Flow Identifier: The QoS flow identifier corresponding to the transmission address is used to identify which QoS flow and / or flows the reported address is for. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0135] ● Information that can be used for data transmission: may include one or more of the following:

[0136] ○ QoS flow identifier: an identifier used to identify the (accepted) QoS flow that can be used for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0137] ○ Radio bearer identifier: an identifier used to identify the (accepted) radio bearer that can be used for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list. The radio bearer can be a data radio bearer (DRB) or a signaling radio bearer (SRB).

[0138] ○PDU session: an identifier used to identify the (accepted) PDU session that can be used for data transmission. The identifier can be one identifier, multiple identifiers, or an identifier list.

[0139] ○ Cell ID: an ID used to identify a cell that can perform data transmission (accepted). The ID can be one ID, multiple IDs, or an ID list.

[0140] ○ Node ID: an ID used to identify a node that can perform data transmission (accepted). The ID can be one ID, multiple IDs, or an ID list.

[0141] ○ Slice ID: an ID used to identify the (accepted) slice that can perform data transmission. The ID can be one ID, multiple IDs, or an ID list.

[0142] ○Transmission address: used to identify address information that can be used for data transmission. The address can be transport layer information, and can include one or more of the following: transport layer address, tunnel endpoint identifier (TEID), QoS mapping relationship, etc. The QoS mapping relationship can include one or more of the following: flow label (FlowLabel), differentiated services code point (Differentiated Services Code Point), etc. The address can be for one or more of uplink transmission, downlink transmission, uplink transmission or downlink transmission, uplink transmission and downlink transmission.

[0143] In some embodiments, the first node may be a target node in a handover, and the second node may be a source node in a handover; or the first node may be a source node in a handover, and the second node may be a source node in a handover; or the first node is a secondary node in a dual connection, and the second node is a primary node in a dual connection; or the first node is a primary node in a dual connection, and the second node is a secondary node in a dual connection; or the first node is a secondary node newly accessed by the UE, and the second node is a secondary node accessed by the original UE; or the first node is a secondary node accessed by the source UE, and the second node is a secondary node newly accessed by the UE; or the first node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP, and the second node may be a UE; or the first node may be a UE, and the second node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP; or the first node may be a source node in a handover, and the second node may be a user in a handover; or the first node may be a user in a handover, and the second node may be a source node in a handover; or the first node may be a target node in a handover, and the second node may be a user in a handover; or the first node may be a user in a handover, and the second node may be a target node in a handover.

[0144] The fields and / or information included in the first message may be information of data transmission or information of second (Secondary) data transmission.

[0145] The fields and / or information included in the second message may be information of data transmission or information of second (Secondary) data transmission.

[0146] Example 2

[0147] In some embodiments, the present disclosure proposes a method for supporting mobility management, which may include: a third node sends a third message containing information related to a user equipment UE in conditional switching and / or information related to a resource reservation request in conditional switching to a fourth node, so as to provide reference information for the fourth node when performing resource reservation and / or resource allocation. After receiving the third message, the fourth node may also forward the information to other nodes to provide reference information for other nodes when performing resource reservation and / or resource allocation. In some embodiments, in the case of conditional switching, the configuration may continue to be retained as a configuration for subsequent conditional switching after the conditional switching, and the target node may reserve and / or release the resources prepared for the conditional switching as appropriate after obtaining the information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in the conditional switching. For example, when the user's estimated arrival time is a certain moment, the target node may not need to reserve resources for conditional switching before the estimated arrival time, and / or start reserving resources at a certain moment before the estimated arrival time, and / or reserve resources at the estimated arrival time, and / or use the reserved resources for other users if other users need the resources before the estimated arrival time.

[0148] In some embodiments, the third message may be or may be carried by one or more of the following messages: it may be a handover request (HANDOVER REQUEST) message of X2 or Xn, or a get UE context response (RETRIEVE UECONTEXT RESPONSE) message, or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; it may also be a second eNB addition request (SENB ADDITION REQUEST) message or a second gNB addition request (SGNBADDITION REQUEST) message of X2; it may also be a secondary node addition request (S-NODE ADDITION REQUEST) message or a secondary node addition request confirmation (S-NODE ADDITION REQUEST ACKNOWLEDGE) message or a secondary node modification required (S-NODE MODIFICATION REQUIRED) message or a secondary node change confirmation (S-NODE MODIFICATIONCONFIRM) message or a secondary node change required (S-NODE CHANGE REQUIRED) message or a secondary node change confirmation (S-NODE CHANGE It may also be a UE CONTEXT SETUP REQUEST message or a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION REQUEST message or a UE CONTEXT MODIFICATION RESPONSE message of F1; it may also be another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container.

[0149] In some implementations, the third message may include one or more of the following fields or related information:

[0150] ● The cell identity corresponding to the following information: Or it is called the cell identity corresponding to the third message, or the cell identity corresponding to the information related to the user equipment UE in the conditional handover and / or the information related to the resource reservation request in the conditional handover.

[0151] ●Node identifier corresponding to the following information. Or it is called the node identifier corresponding to the third message, or the node identifier corresponding to the information related to the user equipment UE in the conditional switching and / or the information related to the resource reservation request in the conditional switching. It may include one or more of the following: the user identifier assigned by the new node, the user identifier assigned by the old node, the user identifier assigned by the source node, the user identifier assigned by the auxiliary node, the user identifier assigned by the main node, the user identifier assigned by the auxiliary node, the user identifier assigned by the first message sending node, the user identifier assigned by the first message receiving node, etc. The identifier can be one identifier, multiple identifiers, or a list of identifiers.

[0152] ●The slice identifier corresponding to the following information: Or it is called the slice identifier corresponding to the third message, or the slice identifier corresponding to the information related to the user equipment UE in the conditional switching and / or the information related to the resource reservation request in the conditional switching.

[0153] ● The user identity of the handover corresponding to the following information. Or it is called the user identity of the (conditional) handover corresponding to the third message, or the UE identity of the conditional handover corresponding to the information related to the user equipment UE in the conditional handover and / or the information related to the resource reservation request in the conditional handover.

[0154] ● Expected maximum arrival probability: indicates the maximum probability of a user arriving at a cell and / or node. The arrival probability can be the expected maximum arrival probability for a period of time in the future or the expected maximum arrival probability at the current moment.

[0155] ●The time corresponding to the estimated maximum arrival probability: indicates the time information corresponding to the maximum probability of a user arriving at a cell and / or node.

[0156] ● Expected minimum arrival probability: indicates the minimum probability of a user arriving at a cell and / or node. The arrival probability can be the expected minimum arrival probability for a period of time in the future or the expected minimum arrival probability at the current moment.

[0157] ●The time corresponding to the estimated minimum arrival probability: indicates the time information corresponding to the minimum probability of a user arriving at a cell and / or node.

[0158] ● Estimated time of arrival: indicates the time it takes for a user to arrive at a cell and / or node.

[0159] ● Expected arrival probability: indicates the arrival probability of a user arriving at a cell and / or node. In some implementations, it can be one or more expected arrival probabilities or a list. The arrival probability can be the expected arrival probability for a period of time in the future or the expected arrival probability at the current moment.

[0160] ● Time corresponding to the expected arrival probability: indicates the time information corresponding to the probability of the user arriving at a cell and / or node. In some implementations, it can be one or more times corresponding to the expected arrival probability, or it can be a list.

[0161] ● Requested maximum resource reservation time: indicates the maximum resource reservation time for requesting the target node to reserve resources. This information mainly provides reference information for the receiving node of the message to make resource reservations, so as to improve resource utilization and avoid performance damage to other users due to long-term resource reservations. In some embodiments, for example, the receiving node of the message can reserve resources based on the information. For example, resource reservation is performed only within the requested maximum resource reservation time; resource reservation is not performed outside of this time. In other embodiments, for example, the receiving node of the message can set the resource reservation time based on the information, and resource reservation is performed only within the resource reservation time, and the resource reservation time can be sent to the sending node of the third message via a fourth message.

[0162] ● Requested minimum resource reservation time: indicates the minimum resource reservation time for requesting the target node to reserve resources. This information mainly provides reference information for the receiving node of the message to make resource reservations, so as to improve resource utilization and avoid performance damage to other users due to long-term resource reservations. In some embodiments, for example, the receiving node of the message can reserve resources based on the information. For example, resource reservation is performed only within the requested minimum resource reservation time; resource reservation is not performed outside of this time. In other embodiments, for example, the receiving node of the message can set the resource reservation time based on the information (in some embodiments, for example, the set resource reservation time should include the requested minimum resource reservation time), and resource reservation is performed only within the resource reservation time, and the resource reservation time can be sent to the sending node of the third message via a fourth message.

[0163] ● Request resource reservation time interval: indicates the time interval for requesting the target node to reserve resources. This information mainly provides reference information for the receiving node of the message to make resource reservations, so as to improve resource utilization and avoid performance damage to other users due to long-term resource reservations. In some embodiments, for example, the receiving node of the message can reserve resources based on the information. For example, resource reservation is performed only within the requested resource reservation time interval; resource reservation is not performed outside of this time. In other embodiments, for example, the receiving node of the message can set the resource reservation time based on the information (in some embodiments, for example, the set resource reservation time should include the requested resource reservation time interval), and resource reservation is performed only within the resource reservation time, and the resource reservation time can be sent to the sending node of the third message via a fourth message.

[0164] ● Requested resource reservation time: indicates the time for requesting the target node to reserve resources. This information mainly provides reference information for the receiving node of the message to make resource reservations, so as to improve resource utilization and avoid performance damage to other users due to long-term resource reservations. In some embodiments, for example, the receiving node of the message can reserve resources based on the information. For example, resource reservation is performed only within the requested resource reservation time; resource reservation is not performed outside of this time. In other embodiments, for example, the receiving node of the message can set the resource reservation time based on the information (in some embodiments, for example, the set resource reservation time should include the requested resource reservation time), and resource reservation is performed only within the resource reservation time, and the resource reservation time can be sent to the sending node of the third message via a fourth message.

[0165] ●Indication of whether setting the resource reservation time is allowed: an indication of whether the target node is allowed to set the resource reservation time. If the indication indicates that setting the resource reservation time is allowed, the target node can set the resource reservation time. In one embodiment, for example, the resource reservation time set by the target node can be sent via a fourth message. If the indication indicates that setting the resource reservation time is not allowed, the target node cannot set the resource reservation time. In some embodiments, the target node needs to reserve resources from the time it receives a handover request for the user until the user accesses the target node and / or the target node receives a handover cancellation message and / or a message that the user accesses other target nodes.

[0166] ● Confidence: Used to indicate the confidence / accuracy of a forecast and / or prediction.

[0167] In some embodiments, the fourth node may send a fourth message containing information related to resource reservation (time) in conditional switching to the third node according to its own situation and / or receiving a third message containing information related to user equipment UE in conditional switching and / or information related to resource reservation request in conditional switching, so that the third node can confirm the time that the fourth node and / or target node (the target node can be other nodes except the third node and the fourth node) will reserve resources for the UE for the switching, and the third node can select the target node and / or configure the UE and / or perform cell selection based on the information. For example, when the resource reservation time set by the node is too short, the source node may not select the node as the target node and / or cell.

[0168] In some embodiments, the fourth message may be or may be carried by one or more of the following messages: it may be a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message or a UE context request (RETRIEVE UE CONTEXT REQUEST) message or a handover success (HANDOVER SUCCESS) message of X2 or Xn; it may also be a second eNB addition request confirmation (SENB ADDITION REQUEST ACKNOWLEDGE) message or a second gNB addition request confirmation (SGNB ADDITION REQUEST ACKNOWLEDGE) message of X2; it may also be a secondary node addition request confirmation (S-NODE ADDITION REQUEST ACKNOWLEDGE) message of Xn; it may also be a user context establishment request (UECONTEXT SETUP REQUEST) message or a user context establishment response (UE CONTEXT SETUP RESPONSE) message or a user context modification request (UE CONTEXT MODIFICATION REQUEST) message or a user context modification response (UE CONTEXT MODIFICATION REQUEST) message of F1. RESPONSE) message; it may also be another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container.

[0169] In some implementations, the fourth message may include one or more of the following fields or related information:

[0170] ●The cell identifier corresponding to the following information may also be referred to as the cell identifier corresponding to the fourth message, or the cell identifier corresponding to the information related to resource reservation (time) in conditional switching.

[0171] ●The node identifier corresponding to the following information may also be referred to as the node identifier corresponding to the fourth message, or the node identifier corresponding to the information related to resource reservation (time) in conditional switching.

[0172] ●The slice identifier corresponding to the following information may also be called the slice identifier corresponding to the fourth message, or the slice identifier corresponding to the information related to resource reservation (time) in conditional switching.

[0173] ●The user identifier for switching corresponding to the following information may also be referred to as the user identifier for conditional switching corresponding to the third message, or the UE identifier for conditional switching corresponding to the information related to resource reservation (time) in the conditional switching. . It may include one or more of the following: a user identifier assigned by the new node, a user identifier assigned by the old node, a user identifier assigned by the source node, a user identifier assigned by the auxiliary node, a user identifier assigned by the primary node, a user identifier assigned by the auxiliary node, a user identifier assigned by the first message sending node, a user identifier assigned by the first message receiving node, etc. The identifier may be one identifier, multiple identifiers, or an identifier list.

[0174] ●Maximum resource reservation time: indicates the maximum time the target node can reserve resources.

[0175] ● Resource reservation time: indicates the time during which the target node can reserve resources. In some embodiments, the target node reserves resources for the conditional switching only within this time, and cannot ensure resource reservation for the conditional switching outside this time interval. In other embodiments, if the source node and / or the master node informs the target node through a third message that it is allowed to set the resource reservation time, the target node (which can be a target master node or a target auxiliary node) can set the resource reservation time and send it to the source node through this field and the fourth message. In some further embodiments, if the source node and / or the master node informs the target node through a third message about the requested resource reservation time, the target node resets the resource reservation time according to its own situation, and the reset resource reservation time is sent to the source node through this field and the fourth message.

[0176] ● Time information corresponding to the handover configuration: indicates the applicable time of the handover configuration. In some implementations, the handover configuration is valid only during the applicable time, and is invalid outside the applicable time. In one implementation process, after receiving the information, the source node sends a handover command to the user only during the applicable time. In another implementation process, after receiving the information, the user performs the handover process only during the applicable time, for example, checks whether the configured conditional handover operation conditions are met, and / or accesses the target cell within the applicable time.

[0177] In some embodiments, the third node may be a target node in the handover, and the fourth node may be a source node in the handover; or the third node may be a source node in the handover, and the fourth node may be a source node in the handover; or the third node is a secondary node in the dual connection, and the fourth node is a primary node in the dual connection; or the third node is a primary node in the dual connection, and the fourth node is a secondary node in the dual connection; or the third node is a secondary node newly accessed by the UE, and the fourth node is a secondary node accessed by the original UE; or the third node is a secondary node accessed by the source UE, and the fourth node is a secondary node newly accessed by the UE; or the third node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP, and the fourth node may be a UE; or the third node may be a UE, and the fourth node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP; or the third node may be a source node in the handover, and the fourth node may be a user in the handover; or the third node is a user in the handover, and the fourth node may be a source node in the handover; or the third node may be a target node in the handover, and the fourth node may be a user in the handover; or the third node may be a user in the handover, and the fourth node may be a target node in the handover.

[0178] Example 3

[0179] In some embodiments, the present disclosure proposes a method for supporting mobility management, which may include: a fifth node sends a fifth message containing a request for reporting prediction information related to conditional switching to a sixth node, so that the sixth node reports the prediction result related to the conditional switching, so that the fifth node can make relevant decisions and / or perform subsequent configuration and / or behavior of conditional switching, for example, triggering early data forwarding, etc. The fifth node may also forward it to other nodes for other nodes to make relevant switching decisions. In this scheme, subsequent actions can be performed according to the predicted user information, and unnecessary subsequent actions and / or data transmission waste can be avoided. In some embodiments, for example, when it is predicted that the UE will not meet the running event in a short time, the target node can use the reserved resources for other users to improve resource utilization and avoid unnecessary resource reservation. In other embodiments, for example, the node can reserve resources when it is predicted that the UE will meet the running event. In some other embodiments, for example, when the node predicts that the UE will meet the switching condition, the node can forward the candidate target node early to avoid invalid data transmission, etc. For example, only the cell corresponding to the switching condition that will be met can be forwarded early, and no data transmission can be performed on other candidate target cells.

[0180] In some implementations, the fifth message may be or may be carried by one or more of the following messages: may be a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message of Xn; may also be a handover command (HANDOVER COMMAND) message or a handover request confirmation (HANDOVER REQUEST ACKNOWLEDGE) message of NG; may be an RRC reconfiguration (RRCReconfiguration) message or an RRC reconstruction (RRCReestablishment) message or an RRC establishment (RRCSetup) message or an RRC release (RRCRelease) message of Radio Resource Control (RRC); may be an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XN SETUP RESPONSE) message of Xn; may also be an eNB configuration update (ENB CONFIGURATION UPDATE) message or an eNB configuration update confirmation (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or an EN-DC configuration update (EN-DC REQUEST) message of X2. It may be an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message of Xn; it may be a RESET REQUEST message of X2 or Xn; it may be a MOBILITY CHANGE REQUEST message of X2;It may also be the F1 setup request (F1SETUP REQUEST) message or the F1 setup response (F1SETUP REQUEST) message or the GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or the GNB-DU configuration update confirmation (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or the GNB-CU configuration update (GNB-CUCONFIGURATION UPDATE) message or the GNB-CU configuration update confirmation (GNB-CU CONFIGURATION UPDATEACKNOWLEDGE) message or the GNB-DU resource coordination request (GNB-DU RESOURCE COORDINATION REQUEST) message or the GNB-DU resource coordination response (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be the GNB-CU-UP E1 setup request (GNB-CU-UP E1 SETUP REQUEST) message or the GNB-CU-UP E1 setup response (GNB-CU-UP E1 SETUP The gNB-CU-CP CONFIGURATION UPDATE message or the gNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message may be a GNB-CU-CP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-CP E1 SETUP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-CP CONFIGURATION UPDATE message or a gNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message; it may also be a RESOURCE STATUS REQUEST message of X2, Xn, F1 or E1, or an EN-DC RESOURCE STATUS REQUEST message of X2. REQUEST) message; it may also be an NG uplink RAN ​​configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, a downlink RAN ​​configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message;It may also be a HANDOVER REQUEST ACKNOWLEDGE message or a RETRIEVE UE CONTEXTREQUEST message or a HANDOVER SUCCESS message of X2 or Xn; it may also be a SENB ADDITION REQUEST ACKNOWLEDGE message or a SGNB ADDITIONREQUEST ACKNOWLEDGE message of X2; it may also be an S-NODE ADDITIONREQUEST ACKNOWLEDGE message of Xn; it may also be another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container. ;

[0181] In some implementations, the fifth message may include one or more of the following fields or related information:

[0182] ●Request ID: used to identify the request.

[0183] ●Sending node ID: the node ID that sends the fifth message.

[0184] ●Receiving node identifier: the node identifier that receives the fifth message.

[0185] ●The user ID corresponding to the requested information.

[0186] ●Reporting mode: can include single reporting, on-demand reporting, periodic reporting, etc.

[0187] ●Reporting time: used to indicate the reporting time.

[0188] ●Reporting cycle: used to indicate the reporting cycle in case of periodic reporting.

[0189] ● Report triggering event: used to indicate the event that triggers the report. This event may include:

[0190] ○ The predicted time to meet the operational event is less than and / or equal to a threshold value

[0191] ○ Predict the time to meet the operation event within a certain time interval

[0192] ○ The predicted time to meet the operational event is greater than and / or equal to a threshold value

[0193] ●Measurement and / or prediction mode: can include single measurement and / or prediction, on-demand

[0194] Measurement and / or prediction, periodic measurement and / or prediction, etc.

[0195] ●Measurement and / or prediction time: used to indicate the measurement and / or prediction time.

[0196] ● Measurement and / or prediction period: used to indicate the time period of measurement and / or prediction. The period may be the time period for performing periodic measurement and / or prediction in the case of periodic reporting and / or periodic measurement and / or prediction.

[0197] ● Request measurement and / or prediction content: Parameters requested for measurement and / or prediction. This may include one or more of the following:

[0198] ○The cell ID corresponding to the expected operation event

[0199] ○Estimated time to meet the operation event

[0200] ○Expected operational events to be met

[0201] ○Estimated arrival time

[0202] ○ Applicable time: The estimated and / or predicted time when the results will be applicable.

[0203] ○ Confidence: The confidence level of the predicted and / or forecasted results.

[0204] ● Request report content: Parameters requested to be reported. This may include one or more of the following:

[0205] ○The cell ID corresponding to the expected operation event

[0206] ○Estimated time to meet the operation event

[0207] ○Expected operational events to be met

[0208] ○Estimated arrival time

[0209] ○ Applicable time: The estimated and / or predicted time when the results will be applicable.

[0210] ○ Confidence: The confidence level of the predicted and / or forecasted results.

[0211] ●Applicable time corresponding to the requested reporting content: indicates the time when the requested reporting content is applicable.

[0212] ●Requested prediction time: indicates the time requested for prediction.

[0213] ● Request to report credibility requirement: used to indicate the accuracy requirement of the prediction. In some embodiments, when the credibility and / or accuracy of the prediction result meets the requirement, the prediction result can be reported.

[0214] ● Confidence: Used to indicate the confidence / accuracy of a forecast and / or prediction.

[0215] In some embodiments, the sixth node may send a sixth message containing conditional switching related prediction information to the fifth node according to its own situation and / or according to the fifth message containing conditional switching related prediction information reporting request received, so that the fifth node can obtain the relevant prediction results about the conditional switching, and the fifth node can make switching related decisions according to the message, for example, reserving resources, releasing resources, deciding whether to perform early data forwarding, deciding when to perform early data forwarding, performing early data forwarding, etc. In some embodiments, for example, when it is predicted that the UE will not meet the operation event in a short time, the target node can use the reserved resources for other users to improve resource utilization and avoid unnecessary resource reservation. In other embodiments, for example, the node can reserve resources when it is predicted that the UE will meet the operation event. In some other embodiments, for example, when the node predicts that the UE will meet the switching condition, the node performs early data forwarding on the candidate target node, does not transmit data to other candidate target nodes, avoids invalid data transmission, etc.

[0216] In some embodiments, the sixth message may be or may be carried by one or more of the following messages: RRC setup completion (RRCSetupComplete), RRC recovery completion (RRCResumeComplete), RRC reconfiguration completion (RRCReconfigurationComplete), RRC reconstruction completion (RRCReestablishmentComplete), user measurement available (UE-MeasurementsAvailable) of RRC; it may also be a handover request (HANDOVER REQUEST) message or a get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message of X2 or Xn; it may also be a second eNB addition request (SENB ADDITIONREQUEST) message or a second gNB addition request (SGNB ADDITION REQUEST) message of X2; it may also be a secondary node addition request (S-NODE ADDITION REQUEST) message or a secondary node addition request confirmation (S-NODE ADDITIONREQUEST) message of Xn. ACKNOWLEDGE) message or S-NODE MODIFICATION REQUIRED message or S-NODE MODIFICATION CONFIRM message or S-NODE CHANGEREQUIRED message or S-NODE CHANGE CONFIRM message or S-NODE MODIFICATION REQUEST message or S-NODE MODIFICATION REQUEST ACKNOWLEDGE message of F1; it may also be a UE CONTEXT SETUP REQUEST message or UE CONTEXT SETUP RESPONSE message or UE CONTEXT MODIFICATION REQUEST message or UE CONTEXT MODIFICATION RESPONSE message of F1. RESPONSE) message; it may also be another and / or newly defined RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container.

[0217] In some implementations, the sixth message may include one or more of the following fields or related information:

[0218] ●The request identifier corresponding to the report: used to indicate the request identifier corresponding to the report, or it can be called the request identifier corresponding to the sixth message.

[0219] ●Sending node ID: the node ID that sends the sixth message.

[0220] ●Receiving node identifier: the node identifier that receives the sixth message.

[0221] ●The user ID corresponding to the reported information.

[0222] ●Measured and / or predicted content: Parameters measured and / or predicted. This may include one or more of the following:

[0223] ○The cell ID corresponding to the expected operation event

[0224] ○Estimated time to meet the operation event

[0225] ○Expected operational events to be met

[0226] ○Estimated arrival time

[0227] ○ Applicable time: The estimated and / or predicted time when the results will be applicable.

[0228] ○ Confidence: The confidence level of the predicted and / or forecasted results.

[0229] ● Report content: Reported parameters. It can include one or more of the following:

[0230] ○The cell ID corresponding to the expected operation event

[0231] ○Estimated time to meet the operation event

[0232] ○Expected operational events to be met

[0233] ○Estimated arrival time

[0234] ○ Applicable time: The estimated and / or predicted time when the results will be applicable.

[0235] ○ Confidence: The confidence level of the predicted and / or forecasted results.

[0236] ●The event that triggered the report: used to indicate the event that triggered the report.

[0237] ● Applicable time corresponding to the measurement content: indicates the applicable time information corresponding to the measurement content. The measurement content is only valid within the applicable time. This information can inform the receiving node of the valid time of the information to avoid the receiving node from using the information incorrectly and / or avoid the receiving node from using the information at an invalid time.

[0238] ● Applicable time corresponding to the reported content: indicates the applicable time information corresponding to the reported content. The reported content is only valid within the applicable time. This information can inform the receiving node of the valid time of the information to avoid the receiving node from using the information incorrectly and / or avoid the receiving node from using the information at an invalid time.

[0239] In some embodiments, the fifth node may be a target node in the handover, and the sixth node may be a source node in the handover; or the fifth node may be a source node in the handover, and the sixth node may be a source node in the handover; or the fifth node is a secondary node in the dual connection, and the sixth node is a primary node in the dual connection; or the fifth node is a primary node in the dual connection, and the sixth node is a secondary node in the dual connection; or the fifth node is a secondary node newly accessed by the UE, and the sixth node is a secondary node accessed by the original UE; or the fifth node is a secondary node accessed by the source UE, and the sixth node is a secondary node newly accessed by the UE; or the fifth node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP, and the sixth node may be a UE; or the fifth node may be a UE, and the sixth node may be a gNB or a gNB DU or a gNB CU or a gNB CUUP; or the fifth node may be a source node in the handover, and the sixth node may be a user in the handover; or the fifth node is a user in the handover, and the sixth node may be a source node in the handover; or the fifth node may be a target node in the handover, and the sixth node may be a user in the handover; or the fifth node may be a user in the handover, and the sixth node may be a target node in the handover. The fifth node may be a source secondary node and / or a target secondary node, and the sixth node may be a UE. In some further embodiments, the fifth node may be a source primary node and / or a target primary node, and the sixth node may be a UE.

[0240] In some implementations, the information interaction between the user and the node can be transparently transmitted through another node by means of an RRC container. For example, a message sent by the UE to the primary node can be sent to the primary node by carrying the message in an RRC container through a secondary node, or a message sent by the UE to the secondary node can be sent to the secondary node by carrying the message in an RRC container through a primary node, or a message sent by the UE to the target node can be sent to the target node by carrying the message in an RRC container from the source node.

[0241] In the present disclosure, user may be referred to as user equipment, UE, etc.

[0242] In this disclosure, forecast and prediction may refer to each other.

[0243] In this disclosure, credibility and accuracy may refer to each other.

[0244] In the present disclosure, switching-related decisions and / or switching decisions may include one or more of the following: whether to trigger switching, selection of target cells and / or nodes, selection of switching time, whether to add auxiliary nodes, whether to change auxiliary nodes, reserve resources, release resources, decide whether to perform early data forwarding, decide when to perform early data forwarding, perform early data forwarding, whether to perform data transmission, etc.

[0245] In the present disclosure, time may be represented by one or more of the following: timestamp, time point, time interval, timer, time period, time length, time cycle, time interval, etc. The time length may be the time length from a certain time point, and the time point may be the current moment. The time may be a relative time or an absolute time. In some embodiments, the time period may be represented by a separate field, for example, a combination of a start time and an end time, or a combination of a start time and a time period.

[0246] Exemplary embodiments of the present disclosure are further described below in conjunction with the accompanying drawings.

[0247] The text and drawings are provided as examples only to help understand the present disclosure. They should not be interpreted as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art based on what is disclosed herein that the embodiments and examples shown may be changed without departing from the scope of the present disclosure.

[0248] Figure 3A A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3AThe process of exchanging data transmission address information between two nodes is shown, so that the first node can obtain relevant information of the data transmission address, and the first node can transmit data to the relevant node according to the obtained address information. In some embodiments, for example, the first node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the second node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the first node can be an AMF or an SMF or an MME, and the second node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the first node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node can be an AMF or an SMF or an MME. In some other embodiments, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the first node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the second node may be a primary node in a dual connection. In some other embodiments, for example, the first node may be a primary node in a dual connection, and the second node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the first node may be a source node in a handover, and the second node may be a target node and / or a candidate target node in a handover.

[0249] Step 301A: The second node sends the data transmission address related information to the first node. The data transmission address related information may be the aforementioned second message.

[0250] Step 302A: The first node forwards the received data transmission address related information to other nodes, and / or performs data transmission to related nodes based on the received data transmission address.

[0251] Figure 3B A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3BThe process of exchanging data transmission address information between two nodes is shown, so that the first node can obtain relevant information of the data transmission address, and the first node can transmit data to the relevant node according to the obtained address information. In some embodiments, for example, the first node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the second node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the first node can be an AMF or an SMF or an MME, and the second node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the first node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node can be an AMF or an SMF or an MME. In some other embodiments, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the first node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the second node may be a primary node in a dual connection. In some other embodiments, for example, the first node may be a primary node in a dual connection, and the second node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the first node may be a source node in a handover, and the second node may be a target node and / or a candidate target node in a handover.

[0252] Step 301B: The first node sends a data transmission address request to the second node to request the second node to feed back the relevant data transmission address to the first node. The data transmission address request may be the aforementioned first message.

[0253] Step 302B: The second node sends the data transmission address related information to the first node. The data transmission address related information may be the aforementioned second message.

[0254] Step 303B: the first node forwards the received data transmission address related information to other nodes, and / or performs data transmission to related nodes based on the received data transmission address.

[0255] Figure 3CA schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3C The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown, so that the candidate target secondary node can obtain the data transmission address, so that after the UE accesses a candidate target secondary node, the candidate target secondary node can perform data transmission for subsequent switching.

[0256] Step 301C: The primary node sends a secondary node adding request to the candidate target secondary node (eg, T-SN1 and / or other candidate T-SNs).

[0257] Step 302C: The candidate target secondary node sends a secondary node adding request confirmation to the primary node.

[0258] Step 303C: the master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0259] Step 304C: The UE sends an RRC reconfiguration completion message to the master node.

[0260] Step 305C.a: The primary node sends an Xn-U address indication message to the source secondary node.

[0261] In some embodiments, the UE may be single-connected and only connected to a single node (for example, the MN in the figure), and there is no S-SN in the process. In this case, the above steps 301C to 304C are a secondary node adding process, not a secondary node changing process, and step 305C.a is replaced by the following step 305C.b.

[0262] Step 305C.b: The master node sends a data transmission address to all candidate target secondary nodes so that the candidate target secondary nodes can obtain the address for data transmission. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the above-mentioned second message. In some embodiments, the message can be carried by the Xn-U address indication message. In some embodiments, after receiving the message, the candidate target secondary node saves the address to prepare for subsequent data transmission without triggering actual data transmission. The actual data transmission is triggered by the subsequent step 310C.

[0263] Step 306C: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0264] Step 307C: The primary node and the source secondary node perform a secondary node release and / or modification process. If the source secondary node continues to be the target secondary node for subsequent conditional switching, the secondary node modification process is performed. If the source secondary node is not the target secondary node for subsequent conditional switching, the secondary node release process is performed. If the source secondary node is one of the target secondary nodes, this step is omitted.

[0265] Step 308C: The UE performs a random access procedure with T-SN1.

[0266] Step 309C: Perform other processes for changing and / or adding secondary nodes.

[0267] Step 310C: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0268] Step 311C: If step 310C is to decide to perform early data forwarding, the access secondary node of the UE (eg, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0269] Step 312C: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0270] Step 313C: Perform other processes for auxiliary node change and / or addition.

[0271] Figure 3D A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3D The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the access secondary node can request the master node to send a data transmission address so that the access secondary node can obtain the data transmission address, and the access secondary node can perform data transmission for subsequent switching.

[0272] Step 301D: The primary node sends a secondary node adding request to the candidate target secondary node.

[0273] Step 302D: The candidate target secondary node sends a secondary node adding request confirmation to the primary node.

[0274] Step 303D: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0275] Step 304D: The UE sends an RRC reconfiguration completion message to the master node.

[0276] Step 305D: The primary node sends an Xn-U address indication message to the source secondary node.

[0277] In some implementations, the UE may be single-connected and only connected to a single node (for example, the MN in the figure), and there is no S-SN in the process. In this case, the above steps 301D to 304D are a secondary node adding process, not a secondary node changing process, and there is no step 305D.

[0278] Step 306D: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0279] Step 307D.a: The master node sends a data transmission address request to the source slave node to request the source slave node to send its data transmission address to the master node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by a slave node modification request message.

[0280] Step 307D.b: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0281] If the source auxiliary node continues to be the target auxiliary node for subsequent conditional switching, step 307D performs the auxiliary node modification process. If the source auxiliary node is not the target auxiliary node for subsequent conditional switching, step 307D performs the auxiliary node release process, and there is no need to request and report the data transmission address. If the source auxiliary node is one of the target auxiliary nodes, step 307D is omitted.

[0282] Step 308D: The UE performs a random access procedure with T-SN1.

[0283] Step 309D: Perform other processes for changing and / or adding auxiliary nodes.

[0284] Step 310D.a: The access secondary node of the UE (for example, T-SN1 in this example) sends a data transmission address request to the primary node to request the primary node to send a data transmission address to the access secondary node to prepare for subsequent data transmission and / or switching. The data transmission address request may be the aforementioned first message.

[0285] Step 310D.b: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address, which can be used for subsequent data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message.

[0286] Step 311D: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0287] Step 312D: If step 310D is to decide to perform early data forwarding, the access secondary node of the UE (eg, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0288] Step 313D: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0289] Step 314D: Perform other processes for secondary node change and / or addition.

[0290] Figure 3E A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3E The process of exchanging data transmission address information between the master node (MN), the source secondary node (S-SN) and the candidate target secondary node (T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the master node sends the transmission address to the access secondary node, and the access secondary node can perform data transmission for subsequent switching.

[0291] Step 301E: The primary node sends a secondary node adding request to the candidate target secondary node.

[0292] Step 302E: The candidate target secondary node sends a secondary node adding request confirmation to the primary node.

[0293] Step 303E: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0294] Step 304E: The UE sends an RRC reconfiguration completion message to the master node.

[0295] Step 305E: The primary node sends an Xn-U address indication message to the source secondary node.

[0296] In some implementations, the UE may be single-connected and only connected to a single node (for example, the MN in the figure), and there is no S-SN in the process. In this case, the above steps 301E to 304E are a secondary node adding process, not a secondary node changing process, and there is no step 305E.

[0297] Step 306E: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0298] Step 307E.a: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0299] Step 307E.b: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0300] If the source auxiliary node continues to be the target auxiliary node for subsequent conditional switching, step 307E performs the auxiliary node modification process. If the source auxiliary node is not the target auxiliary node for subsequent conditional switching, step 307E performs the auxiliary node release process, and there is no need to request and report the data transmission address. If the source auxiliary node is one of the target auxiliary nodes, there is no step 307E.

[0301] Step 308E: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address, which can be used for subsequent data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message. This step can be performed before, at the same time, or after step 309E and step 310E.

[0302] Step 309E: The UE performs a random access procedure with T-SN1.

[0303] Step 310E: Perform other processes for secondary node change and / or addition.

[0304] Step 311E: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0305] Step 312E: If step 311E is to decide to perform early data forwarding, the access secondary node of the UE (eg, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0306] Step 313E: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0307] Step 314E: Perform other processes for secondary node change and / or addition.

[0308] Figure 3F A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3F The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown, so that the candidate target secondary node can obtain the data transmission address, so that after the UE accesses a candidate target secondary node, the candidate target secondary node can perform data transmission for subsequent switching.

[0309] Step 301F: The primary node sends a secondary node adding request to the candidate target secondary node.

[0310] Step 302F: The candidate target secondary node sends a secondary node adding request confirmation to the primary node.

[0311] Step 303F: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0312] Step 304F: The UE sends an RRC reconfiguration completion message to the master node.

[0313] Step 305F.a: The primary node sends an Xn-U address indication message to the source secondary node.

[0314] In some embodiments, the UE may be single-connected and only connected to a single node (for example, the MN in the figure), and there is no S-SN in the process. In this case, the above steps 301F to 304F are a secondary node adding process, not a secondary node changing process, and step 305F.a is replaced by the following step 305F.b.

[0315] Step 305F.b: The master node sends a data transmission address to all candidate target secondary nodes so that the candidate target secondary nodes can obtain the address for data transmission. The data transmission address can be the second message mentioned above. In some embodiments, the message can be carried by the Xn-U address indication message. In some embodiments, after receiving the message, the candidate target secondary node saves the address for subsequent data transmission in preparation, and does not trigger actual data transmission. The actual data transmission is triggered by subsequent steps 310F and 311F.

[0316] Step 306F: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0317] Step 307F.a: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0318] Step 307F.b: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the data transmission address of all candidate target slave nodes. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0319] If the source auxiliary node continues to be the target auxiliary node for subsequent conditional switching, step 307F performs the auxiliary node modification process. If the source auxiliary node is not the target auxiliary node for subsequent conditional switching, step 307F performs the auxiliary node release process, and there is no need to request and report the data transmission address. If the source auxiliary node is one of the target auxiliary nodes, step 307F is omitted.

[0320] Step 308F: The UE performs a random access procedure with T-SN1.

[0321] Step 309F: Perform other processes for auxiliary node change and / or addition.

[0322] Step 310F: The primary node determines whether to perform early data forwarding. In some implementations, the primary node may determine whether to perform early data forwarding based on one or more of a UE measurement report, a candidate target secondary node, an operation event, and the like.

[0323] Step 311F: If step 310F is to decide to perform early data forwarding, the master node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), which can be used for early data forwarding. The data transmission address can be one or more of the following: the data transmission address of all candidate target secondary nodes, the data transmission address containing only the source secondary node, the identifier that triggers data transmission, and the event that triggers data transmission. The data transmission address can be the aforementioned second message.

[0324] Step 312F: The access secondary node of the UE (for example, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0325] Step 313F: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0326] Step 314F: Perform other processes for secondary node change and / or addition.

[0327] Figure 3G A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3G The process of exchanging data transmission address information between the master node (MN), the source secondary node (S-SN) and the candidate target secondary node (T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the master node sends the transmission address to the access secondary node, and the access secondary node can perform data transmission for subsequent switching.

[0328] Step 301G: The primary node sends a secondary node adding request to the candidate target secondary node.

[0329] Step 302G: The candidate target secondary node sends a secondary node adding request confirmation to the primary node.

[0330] Step 303G: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0331] Step 304G: The UE sends an RRC reconfiguration completion message to the master node.

[0332] Step 305G: The primary node sends an Xn-U address indication message to the source secondary node.

[0333] In some embodiments, the UE may be single-connected and only connected to a single node (for example, the MN in the figure), and there is no S-SN in the process. In this case, the above steps 301G to 304G are a secondary node adding process, not a secondary node changing process, and there is no step 305G.

[0334] Step 306G: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0335] Step 307G.a: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0336] Step 307G.b: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0337] If the source auxiliary node continues to be the target auxiliary node for subsequent conditional switching, step 307G performs the auxiliary node modification process. If the source auxiliary node is not the target auxiliary node for subsequent conditional switching, step 307G performs the auxiliary node release process, and there is no need to request and report the data transmission address. If the source auxiliary node is one of the target auxiliary nodes, step 307G is omitted.

[0338] Step 308G: The UE performs a random access process with T-SN1.

[0339] Step 309G: Perform other processes for changing and / or adding secondary nodes.

[0340] Step 310G: The primary node determines whether to perform early data forwarding. In some implementations, the primary node may determine whether to perform early data forwarding based on one or more of a UE measurement report, a candidate target secondary node, an operation event, and the like.

[0341] Step 311G: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address and / or trigger data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message.

[0342] Step 312G: The access secondary node of the UE (for example, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0343] Step 313G: When the configured operation events are met, the UE sends an RRC reconfiguration complete message.

[0344] Step 314G: Perform other processes for secondary node change and / or addition.

[0345] Figure 3H A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3H The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown, so that the candidate target secondary node can obtain the data transmission address, so that after the UE accesses a candidate target secondary node, the candidate target secondary node can perform data transmission for subsequent switching.

[0346] Step 301H: The source secondary node sends a secondary node change required message to the primary node.

[0347] Step 302H: The primary node sends a secondary node adding request message to the candidate target secondary node.

[0348] Step 303H: The candidate target secondary node sends a secondary node adding request confirmation message to the primary node.

[0349] Step 304H: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by a secondary node modification request message.

[0350] Step 305H: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0351] Step 306H: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0352] Step 307H: The UE sends an RRC reconfiguration completion message to the master node.

[0353] Step 308H: The primary node sends a secondary node change confirmation message to the source secondary node.

[0354] Step 309H: The master node sends a data transmission address to all candidate target secondary nodes so that the candidate target secondary nodes can obtain the address for data transmission. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the above-mentioned second message. In some embodiments, the message can be carried by the Xn-U address indication message. In some embodiments, after receiving the message, the candidate target secondary node saves the address to prepare for subsequent data transmission without triggering actual data transmission. The actual data transmission is triggered by the subsequent step 313H.

[0355] Step 310H: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0356] Step 311H: UE performs a random access process with T-SN1.

[0357] Step 312H: Perform other processes for auxiliary node change and / or addition.

[0358] Step 313H: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0359] Step 314H: If step 314H is to decide to perform early data forwarding, the access secondary node of the UE (eg, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0360] Step 315H: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0361] Step 316H: Perform other processes for auxiliary node change and / or addition.

[0362] Fig. 3I A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Fig. 3I The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the access secondary node can request the master node to send a data transmission address so that the access secondary node can obtain the data transmission address, and the access secondary node can perform data transmission for subsequent switching.

[0363] Step 301I: The source secondary node sends a secondary node change required message to the primary node.

[0364] Step 302I: the primary node sends a secondary node adding request message to the candidate target secondary node.

[0365] Step 303I: the candidate target secondary node sends a secondary node adding request confirmation message to the primary node.

[0366] Step 304I: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0367] Step 305I: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0368] Step 306I: the master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0369] Step 307I: The UE sends an RRC reconfiguration completion message to the master node.

[0370] Step 308I: The primary node sends a secondary node change confirmation message to the source secondary node.

[0371] Step 309I: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0372] Step 310I: The UE performs a random access procedure with T-SN1.

[0373] Step 311I: Perform other processes for changing and / or adding auxiliary nodes.

[0374] Step 312I.a: The access secondary node of the UE (for example, T-SN1 in this example) sends a data transmission address request to the primary node to request the primary node to send a data transmission address to the access secondary node to prepare for subsequent data transmission and / or switching. The data transmission address request may be the aforementioned first message.

[0375] Step 312I.b: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address, which can be used for subsequent data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message.

[0376] Step 313I: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0377] Step 314I: If step 310D is to decide to perform early data forwarding, the access secondary node of the UE (eg, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0378] Step 314I: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0379] Step 316I: Perform other processes for secondary node change and / or addition.

[0380] Figure 3JA schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3J The process of exchanging data transmission address information between the master node (MN), the source secondary node (S-SN) and the candidate target secondary node (T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the master node sends the transmission address to the access secondary node, and the access secondary node can perform data transmission for subsequent switching.

[0381] Step 301J: The source secondary node sends a secondary node change required message to the primary node.

[0382] Step 302J: The primary node sends a secondary node adding request message to the candidate target secondary node.

[0383] Step 303J: The candidate target secondary node sends a secondary node adding request confirmation message to the primary node.

[0384] Step 304J: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0385] Step 305J: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0386] Step 306J: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0387] Step 307J: The UE sends an RRC reconfiguration completion message to the master node.

[0388] Step 308J: The primary node sends a secondary node change confirmation message to the source secondary node.

[0389] Step 309J: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0390] Step 310J: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0391] Step 311J: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address, which can be used for subsequent data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message. This step can be performed before, at the same time, or after step 311J and step 312J.

[0392] Step 311J: UE performs a random access process with T-SN1.

[0393] Step 312J: Perform other processes for auxiliary node changes and / or additions.

[0394] Step 313J: The access secondary node of the UE (e.g., T-SN1 in this example) determines whether early data forwarding should be performed. In some embodiments, the access secondary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, etc.

[0395] Step 314J: If step 313J is to decide to perform early data forwarding, the access secondary node of the UE (for example, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0396] Step 315J: When the configured operation events are met, the UE sends an RRC reconfiguration complete message.

[0397] Step 316J: Perform other processes for auxiliary node changes and / or additions.

[0398] Figure 3K A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3K The process of exchanging data transmission address information between the master node (Master Node, MN), the source secondary node (Source Secondary Node, S-SN) and the candidate target secondary node (Target Secondary Node, T-SN) is shown, so that the candidate target secondary node can obtain the data transmission address, so that after the UE accesses a candidate target secondary node, the candidate target secondary node can perform data transmission for subsequent switching.

[0399] Step 301K: The source slave node sends a slave node change required message to the master node.

[0400] Step 302K: The primary node sends a secondary node adding request message to the candidate target secondary node.

[0401] Step 303K: The candidate target secondary node sends a secondary node adding request confirmation message to the primary node.

[0402] Step 304K: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0403] Step 305K: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0404] Step 306K: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0405] Step 307K: The UE sends an RRC reconfiguration completion message to the master node.

[0406] Step 308K: The primary node sends a secondary node change confirmation message to the source secondary node.

[0407] Step 309K: The master node sends a data transmission address to all candidate target secondary nodes so that the candidate target secondary nodes can obtain the address for data transmission. The data transmission address can be the second message mentioned above. In some embodiments, the message can be carried by the Xn-U address indication message. In some embodiments, after receiving the message, the candidate target secondary node saves the address to prepare for subsequent data transmission without triggering actual data transmission. The actual data transmission is triggered by subsequent steps 313K and 314K.

[0408] Step 310K: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0409] Step 311K: UE performs a random access process with T-SN1.

[0410] Step 312K: Perform other processes for auxiliary node changes and / or additions.

[0411] Step 313K: The primary node determines whether early data forwarding should be performed. In some implementations, the primary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, and the like.

[0412] Step 314K: If step 310F is to decide to perform early data forwarding, the master node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), which can be used for early data forwarding. The data transmission address can be one or more of the following: the data transmission address of all candidate target secondary nodes, the data transmission address containing only the source secondary node, the identifier that triggers data transmission, and the event that triggers data transmission. The data transmission address can be the aforementioned second message.

[0413] Step 315K: The access secondary node of the UE (for example, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0414] Step 316K: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0415] Step 317K: Perform other processes for auxiliary node changes and / or additions.

[0416] Figure 3L A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 3L The process of exchanging data transmission address information between the master node (MN), the source secondary node (S-SN) and the candidate target secondary node (T-SN) is shown. After the UE accesses one of the target secondary nodes (T-SN1 is used as an example in this example), the master node sends the transmission address to the access secondary node, and the access secondary node can perform data transmission for subsequent switching.

[0417] Step 301L: The source secondary node sends a secondary node change required message to the primary node.

[0418] Step 302L: The primary node sends a secondary node adding request message to the candidate target secondary node.

[0419] Step 303L: The candidate target secondary node sends a secondary node adding request confirmation message to the primary node.

[0420] Step 304L: The primary node sends a data transmission address request to the source secondary node to request the source secondary node to send its data transmission address to the primary node. The data transmission address request may be the aforementioned first message. In some implementations, the message may be carried by the secondary node modification request message.

[0421] Step 305L: The source slave node sends a data transmission address to the master node, so that the master node can obtain the data transmission address of the source slave node, which can be forwarded by the master node to other target slave nodes to prepare for subsequent data transmission and switching. The data transmission address can be the aforementioned second message. In some embodiments, the message can be carried by the slave node modification request confirmation message.

[0422] Step 306L: The master node sends an RRC reconfiguration message to the UE, including the operation events of the addition and / or change of the secondary node conditions, the configuration of the target cell, etc.

[0423] Step 307L: The UE sends an RRC reconfiguration completion message to the master node.

[0424] Step 308L: The primary node sends a secondary node change confirmation message to the source secondary node.

[0425] Step 309L: When the configured operation event is met, the UE sends an RRC reconfiguration complete message. In this example, it is taken that the UE meets the operation conditions of switching and / or adding T-SN1.

[0426] Step 310L: The UE performs a random access procedure with T-SN1.

[0427] Step 311L: Perform other processes for secondary node change and / or addition.

[0428] Step 312L: The primary node determines whether to perform early data forwarding. In some implementations, the primary node may determine whether to perform early data forwarding based on one or more of the UE's measurement report, candidate target secondary nodes, operating events, and the like.

[0429] Step 313L: The primary node sends a data transmission address to the access secondary node of the UE (for example, T-SN1 in this example), so that the access secondary node of the UE (for example, T-SN1 in this example) can obtain the data transmission address and / or trigger data transmission, for example, early data forwarding, etc. The data transmission address can be the data transmission address of all candidate target secondary nodes. The data transmission address can be the aforementioned second message.

[0430] Step 314L: The access secondary node of the UE (for example, T-SN1 in this example) performs early data forwarding to other candidate target secondary nodes.

[0431] Step 315L: When the configured operation event is met, the UE sends an RRC reconfiguration complete message.

[0432] Step 316L: Perform other processes for secondary node change and / or addition.

[0433] Figure 4A A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4A The process of exchanging information related to resource reservation in conditional handover between two nodes (hereinafter, also referred to as relevant information of resource reservation for conditional handover) is shown, so that the third node can obtain relevant information of resource reservation for conditional handover of the fourth node and / or other nodes, and the third node can configure conditional handover according to the information, and / or cancel conditional handover, and / or forward it to other nodes, etc. In some embodiments, for example, the third node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the third node can be an AMF or an SMF or an MME, and the fourth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be an AMF or an SMF or an MME. In some other embodiments, for example, the third node may be a UE, and the fourth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the fourth node may be a primary node in a dual connection. In some other embodiments, for example, the third node may be a primary node in a dual connection, and the fourth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the third node may be a source node in a handover, and the fourth node may be a target node and / or a candidate target node in a handover.

[0434] Step 401A: The fourth node sends information related to resource reservation (time) in the conditional switching to the third node. The information related to resource reservation (time) in the conditional switching may be the aforementioned fourth message. In one implementation process, the target node only reserves resources within the resource reservation time, and the remaining time of the resource can be used for other users to improve resource utilization. For example, it can avoid the situation where the resource reservation time is too long due to the conditional switching and other users lack resources.

[0435] Step 402A: The third node makes a switching decision and / or configures and / or performs a switching behavior based on the received resource reservation related information, and may also forward the received resource reservation related information to other nodes for other nodes to make switching decisions and / or configure and / or perform switching behaviors. In some embodiments, the user can detect whether the operation event is satisfied based on the resource reservation related information. In some embodiments, for example, the user can only switch to the target node when the operation event is satisfied within the resource reservation time. In other embodiments, for example, the source node determines whether the resource reservation time of the target node is suitable, and the judgment can be made based on the user's measurement report, movement trajectory, movement speed, etc. If the source node determines that the resource reservation time of the target node is suitable, the subsequent switching process is performed. If the source node determines that the resource reservation time of the target node is not suitable, the switch is canceled.

[0436] Figure 4B A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4BThe process of exchanging information related to resource reservation in conditional handover between two nodes is shown, so that the third node can obtain relevant information about resource reservation of the fourth node and / or other nodes for conditional handover, and the third node can configure conditional handover according to the information, and / or cancel conditional handover, and / or forward it to other nodes, etc. In some embodiments, for example, the third node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the third node can be an AMF or an SMF or an MME, and the fourth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be an AMF or an SMF or an MME. In some other embodiments, for example, the third node may be a UE, and the fourth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the fourth node may be a primary node in a dual connection. In some other embodiments, for example, the third node may be a primary node in a dual connection, and the fourth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the third node may be a source node in a handover, and the fourth node may be a target node and / or a candidate target node in a handover.

[0437] Step 401B: The third node sends the information of the user and / or resource reservation request in the conditional switching (i.e., information related to the user equipment UE in the conditional switching and / or information related to the resource reservation request in the conditional switching) to the fourth node. The information of the user and / or resource reservation request in the conditional switching may be the aforementioned third message. In one implementation process, the source node may determine the probability and / or time of the user arriving at the target cell and / or node based on the user's measurement report, motion trajectory, motion speed, etc. The source node sends the information to the target node, and the target node may use the information to formulate a resource reservation strategy, for example, to reserve resources when the user is about to arrive at the target cell and / or node to improve resource utilization, for example, to avoid resource waste caused by long-term resource reservation due to the user not arriving at the target cell and / or node for a long time. In other embodiments, the source node may set whether to allow the target node to set the resource reservation time. If allowed, the target node may formulate the information and / or send it to the source node and / or to the user through subsequent processes.

[0438] Step 402B: The fourth node sends information related to the resource reservation (time) in the conditional switching to the third node. The information related to the resource reservation (time) in the conditional switching may be the aforementioned fourth message. In one implementation process, the target node reserves resources only within the resource reservation time, and the remaining time, the resources may be used for other users to improve resource utilization. For example, it is possible to avoid the situation where the resource reservation time is too long due to the conditional switching and other users lack resources. In some embodiments, the fourth node may independently decide whether to set the resource reservation related information based on its own situation. In other embodiments, if the resource reservation time is allowed to be set in step 410B, the fourth node may set the resource reservation time and / or send the resource reservation time to the third node through this step.

[0439] Step 403B: The third node makes a switching decision and / or configures and / or performs a switching behavior based on the received resource reservation related information, and may also forward the received resource reservation related information to other nodes for the other nodes to make a switching decision and / or configure and / or perform a switching behavior. In some embodiments, for example, a user can only switch to a target node when an operation event is satisfied within the resource reservation time. In other embodiments, for example, the source node determines whether the resource reservation time of the target node is suitable, and the judgment may be made based on the user's measurement report, motion trajectory, motion speed, etc. If the source node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed. If the source node determines that the resource reservation time of the target node is not suitable, the switch is canceled.

[0440] Figure 4CA schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4C The process of interactively exchanging information related to resource reservation in conditional switching between a source master node and a target slave node is shown, so that the source master node can obtain relevant information about resource reservation of the target slave node for conditional switching. The source master node can configure conditional switching based on the information, and / or cancel conditional switching, and / or forward it to the user, etc.

[0441] Step 401C: the source master node and / or the source master node CU sends a secondary node adding request to the target secondary node and / or the target secondary node CU.

[0442] Step 402C: The target secondary node CU sends a UE context establishment request to the target secondary node DU.

[0443] Step 403C: The target auxiliary node DU makes a resource reservation decision for conditional switching, and sends the resource reservation information in the conditional switching to the target auxiliary node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In some embodiments, the message may be carried by a user context establishment response message. In one implementation process, the target auxiliary node only reserves resources within the resource reservation time, and the remaining time of the resources can be used for other users to improve resource utilization. For example, it can avoid the situation where the resource reservation time is too long due to conditional switching and other users lack resources.

[0444] Step 404C: The target auxiliary node and / or the target auxiliary node CU sends the resource reservation information in the conditional switching to the source main node and / or the source main node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node addition request confirmation message. In some embodiments, for example, the source main node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source main node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user. If the source main node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0445] Step 405C: The source master node and / or the source master node CU sends the resource reservation information in the conditional switching to the UE. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In this document, the fourth message may also include an RRC container, and the RRC container may include the resource reservation information in the conditional switching (or referred to as information related to the resource reservation time in the conditional switching). In some embodiments, for example, the UE may only switch to the target secondary node when the operation event is satisfied within the resource reservation time.

[0446] Step 406C: The UE sends an RRC reconfiguration completion message to the source master node.

[0447] Step 407C: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0448] Figure 4D A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4D The process of interactively exchanging information related to resource reservation in conditional switching between a source master node and a target slave node is shown, so that the source master node can obtain relevant information about resource reservation of the target slave node for conditional switching. The source master node can configure conditional switching based on the information, and / or cancel conditional switching, and / or forward it to the user, etc.

[0449] Step 401D: The source master node and / or the source master node CU sends the information of the user and / or the request for resource reservation in the conditional switching to the target auxiliary node and / or the target auxiliary node CU. The information of the user and / or the request for resource reservation in the conditional switching may be the aforementioned third message. In some embodiments, the message may be carried by the auxiliary node addition request message. In one implementation process, the source master node may judge the probability and / or time of the user arriving at the target cell and / or node based on the user's measurement report, motion trajectory, motion speed, etc., and the source master node sends the information to the target auxiliary node. The target auxiliary node may use the information to formulate a resource reservation strategy, for example, to reserve resources when the user is about to arrive at the target cell and / or node to improve resource utilization, for example, to avoid resource waste caused by long-term resource reservation due to the user not arriving at the target cell and / or node for a long time. In other embodiments, the source master node may set whether to allow the auxiliary node to set the resource reservation time. If allowed, the target auxiliary node may formulate the information and / or send it to the source master node and / or to the user through subsequent processes.

[0450] Step 402D: The target secondary node CU sends the information of the user and / or resource reservation request in the conditional handover to the target secondary node DU. The information of the user and / or resource reservation request in the conditional handover may be the aforementioned third message. In some implementations, the message may be carried by the UE context establishment request.

[0451] Step 403D: The target auxiliary node DU makes a resource reservation decision for conditional switching, and sends the resource reservation information in the conditional switching to the target auxiliary node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In some embodiments, the message may be carried by a user context establishment response message. In one implementation process, the target auxiliary node reserves resources only within the resource reservation time, and the remaining time of the resources can be used for other users to improve resource utilization. For example, it can avoid the situation where the resource reservation time is too long due to conditional switching and other users lack resources.

[0452] Step 404D: The target auxiliary node and / or the target auxiliary node CU sends the resource reservation information in the conditional switching to the source main node and / or the source main node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node addition request confirmation message. In some embodiments, for example, the source main node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source main node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user. If the source main node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0453] Step 405D: The source master node and / or the source master node CU sends the conditional switching resource reservation information to the UE. The conditional switching resource reservation information may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In some implementations, for example, the UE may only switch to the target secondary node when the operation event is satisfied within the resource reservation time.

[0454] Step 406D: The UE sends an RRC reconfiguration completion message to the source master node.

[0455] Step 407D: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0456] Figure 4E A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4E The process of interactively exchanging information related to resource reservation in conditional switching between a source master node and a target slave node is shown, so that the source master node can obtain relevant information about resource reservation of the target slave node for conditional switching. The source master node can configure conditional switching based on the information, and / or cancel conditional switching, and / or forward it to the user, etc.

[0457] Step 401E: The source master node and / or the source master node CU sends a secondary node adding request to the target secondary node and / or the target secondary node CU.

[0458] Step 402E: The target secondary node CU sets the resource reservation information in the conditional handover and sends the information to the target secondary node DU. The resource reservation information in the conditional handover may be the aforementioned fourth message. In some implementations, the message may be carried by the UE context establishment request message.

[0459] Step 403E: The target auxiliary node DU, based on the conditional handover resource reservation information set by the CU in step 402E, modifies and / or accepts and / or rejects the conditional handover resource reservation information according to its own situation, or sets the conditional handover resource reservation information of the DU itself. The DU sends the conditional handover resource reservation information setting and / or decision to the target auxiliary node CU. The conditional handover resource reservation information may be the aforementioned fourth message. In some implementations, the message may be carried by the UE context establishment response message.

[0460] Step 404E: The target auxiliary node and / or the target auxiliary node CU sends the resource reservation information in the conditional switching to the source main node and / or the source main node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node addition request confirmation message. In some embodiments, for example, the source main node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source main node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user. If the source main node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0461] Step 405E: The source master node and / or the source master node CU sends the conditional switching resource reservation information to the UE. The conditional switching resource reservation information may be the aforementioned fourth message. In one implementation, the message may be carried by an RRC reconfiguration message. In some implementations, for example, the UE may only switch to the target secondary node when the operation event is satisfied within the resource reservation time.

[0462] Step 406E: The UE sends an RRC reconfiguration completion message to the source master node.

[0463] Step 407E: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0464] Figure 4F A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4FThe process of interactively exchanging information related to resource reservation in conditional switching between a source master node and a target slave node is shown, so that the source master node can obtain relevant information about resource reservation of the target slave node for conditional switching. The source master node can configure conditional switching based on the information, and / or cancel conditional switching, and / or forward it to the user, etc.

[0465] Step 401F: The source master node and / or the source master node CU sends a secondary node adding request message to the target secondary node and / or the target secondary node CU.

[0466] Step 402F: The target secondary node CU sends a UE context establishment request message to the target secondary node DU.

[0467] Step 403F: The target secondary node DU sends a UE context establishment response message to the target secondary node CU.

[0468] Step 404F: The target auxiliary node CU sets the resource reservation information in the conditional switching, and the target auxiliary node and / or the target auxiliary node CU sends the resource reservation information in the conditional switching to the source main node and / or the source main node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node addition request confirmation message. In some embodiments, for example, the source main node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source main node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user. If the source main node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0469] Step 405F: The source master node and / or the source master node CU sends the conditional switching resource reservation information to the UE. The conditional switching resource reservation information may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In some implementations, for example, the UE may only switch to the target secondary node when the operation event is satisfied within the resource reservation time.

[0470] Step 406F: The UE sends an RRC reconfiguration completion message to the source master node.

[0471] Step 407F: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0472] Figure 4G A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4GThe process of interactively exchanging information related to resource reservation in conditional switching between a source master node and a target slave node is shown, so that the source master node can obtain relevant information about resource reservation of the target slave node for conditional switching. The source master node can configure conditional switching based on the information, and / or cancel conditional switching, and / or forward it to the user, etc.

[0473] Step 401G: The source master node and / or the source master node CU sends a secondary node adding request message to the target secondary node and / or the target secondary node CU.

[0474] Step 402G: The target secondary node CU sends a UE context establishment request message to the target secondary node DU.

[0475] Step 403G: The target secondary node DU sends a UE context establishment response message to the target secondary node CU.

[0476] Step 404G: The target auxiliary node CU sets the resource reservation information in the conditional switching, and the target auxiliary node and / or the target auxiliary node CU sends the resource reservation information in the conditional switching to the source main node and / or the source main node CU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node addition request confirmation message. In some embodiments, for example, the source main node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source main node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user. If the source main node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0477] Step 405G: The target secondary node CU sends the resource reservation information in the conditional switching to the target secondary node DU. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the UE context modification request message. In one implementation process, for example, the target secondary node DU may reserve resources according to the received resource reservation information.

[0478] Step 406G: The target secondary node DU sends a UE context establishment response message to the target secondary node CU.

[0479] Step 407G: The source master node and / or the source master node CU sends the conditional switching resource reservation information to the UE. The conditional switching resource reservation information may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In some implementations, for example, the UE may only switch to the target secondary node when the operation event is satisfied within the resource reservation time.

[0480] Step 408G: The UE sends an RRC reconfiguration completion message to the source master node.

[0481] Step 409G: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0482] Step 405G and step 406G may be performed before, simultaneously with, and / or after step 407G. After the target auxiliary node CU sets the resource reservation information in the conditional switching, step 405G may also be performed before and / or simultaneously with step 404G, and the target auxiliary node CU first notifies the target auxiliary node DU and then notifies the source main node, or the target auxiliary node CU notifies the target auxiliary node DU and the source main node at the same time.

[0483] Figure 4H A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4H The information of users and / or requested resource reservation in the interactive conditional switching between the source main node, the source auxiliary node and the target auxiliary node is shown. The target auxiliary node can make a switching decision according to the information of the conditional switching and / or requested resource reservation, for example, whether to receive the switching request and / or auxiliary node adding request, resource reservation information in the conditional switching, etc.

[0484] Step 401H: The source master node sends the information of the user and / or resource reservation request in the conditional handover to the target slave node. The information of the user and / or resource reservation request in the conditional handover may be the aforementioned third message. In some embodiments, the message may be carried by the slave node add request message. The target slave node may make a handover decision according to the information of the conditional handover and / or resource reservation request, for example, whether to receive the handover request and / or slave node add request, resource reservation information in the conditional handover, etc.

[0485] Step 402H: The target secondary node sends a secondary node adding request confirmation message to the source primary node.

[0486] Step 403H: The source master node may formulate the resource reservation information in the conditional switching according to the user and / or requested resource reservation information in the conditional switching. The source master node sends the resource reservation information in the conditional switching to the UE. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In some embodiments, for example, the UE may only switch to the target secondary node when the operation event is met within the resource reservation time. In some embodiments, the formulated resource reservation information in the conditional switching may be consistent with the requested resource reservation information.

[0487] Step 404H: The UE sends an RRC reconfiguration completion message to the source master node.

[0488] Step 405H: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0489] Fig. 4I A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Fig. 4I The resource reservation information in the interactive conditional switching between the source master node, the source slave node and the target slave node is shown. The target slave node can formulate the resource reservation information in the conditional switching according to its own situation and send it to the source master node and then to the user.

[0490] Step 401I: The source primary node sends a secondary node adding request message to the target secondary node.

[0491] Step 402I: The target auxiliary node sets the resource reservation information in the conditional switching, and the target auxiliary node sends the resource reservation information in the conditional switching to the source master node. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by the auxiliary node adding a request confirmation message. In some embodiments, for example, the source master node determines whether the resource reservation time of the target auxiliary node is suitable, and the judgment may be based on the user's measurement report, movement trajectory, movement speed, etc. If the source master node determines that the resource reservation time of the target node is suitable, a subsequent switching process is performed, for example, the information is sent to the user, and if the source master node determines that the resource reservation time of the target node is not suitable, the switching is canceled.

[0492] Step 403I: The source master node sends the conditional handover resource reservation information to the UE. The conditional handover resource reservation information may be the aforementioned fourth message. In one implementation, the message may be carried by an RRC reconfiguration message. In some implementations, for example, the UE may only handover to the target secondary node when an operation event is satisfied within the resource reservation time.

[0493] Step 404I: The UE sends an RRC reconfiguration completion message to the source master node.

[0494] Step 405I: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0495] Figure 4J A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4J The information of users and / or requested resource reservation in the interactive conditional switching between the source main node, the source auxiliary node and the target auxiliary node is shown. The target auxiliary node can make a switching decision according to the information of the conditional switching and / or requested resource reservation, for example, whether to receive the switching request and / or auxiliary node adding request, resource reservation information in the conditional switching, etc.

[0496] Step 401J: The source secondary node sends the information of the user and / or resource reservation request in the conditional switching to the source primary node. The information of the user and / or resource reservation request in the conditional switching may be the aforementioned third message. In some implementations, the message may be carried by the secondary node change need message.

[0497] Step 402J: The source master node sends the information of the user and / or the resource reservation request in the conditional handover to the target slave node. The information of the user and / or the resource reservation request in the conditional handover may be the aforementioned third message. In some embodiments, the message may be carried by the slave node add request message. The target slave node may make a handover decision according to the information of the resource reservation request in the conditional handover, for example, whether to receive the handover request and / or the slave node add request, the resource reservation information in the conditional handover, etc.

[0498] Step 403J: The target secondary node sends a secondary node adding request confirmation message to the source primary node.

[0499] Step 404J: The source primary node sends a secondary node change confirmation message to the source secondary node.

[0500] Step 405J: The source master node may formulate the resource reservation information in the conditional switching according to the user and / or requested resource reservation information in the conditional switching. The source master node sends the resource reservation information in the conditional switching to the UE. The resource reservation information in the conditional switching may be the aforementioned fourth message. In one implementation process, the message may be carried by an RRC reconfiguration message. In some embodiments, for example, the UE may only switch to the target secondary node when an operating event is satisfied within the resource reservation time. In some embodiments, the formulated resource reservation information in the conditional switching may be consistent with the requested resource reservation information.

[0501] Step 406J: The UE sends an RRC reconfiguration completion message to the source master node.

[0502] Step 407J: The UE performs subsequent handover procedures such as random access with the target secondary node.

[0503] Figure 4K A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 4KThe process of exchanging information related to resource reservation in conditional handover between two nodes is shown, so that the fourth node obtains information related to user-related information and / or requesting resource reservation in conditional handover from the third node, and the fourth node can receive and / or reject the conditional handover request based on the information, and can also make a resource reservation decision based on the information. In some embodiments, for example, the third node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the fourth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the third node can be an AMF or an SMF or an MME, and the fourth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the fourth node may be an AMF or an SMF or an MME. In some other embodiments, for example, the third node may be a UE, and the fourth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the third node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the fourth node may be a primary node in a dual connection. In some other embodiments, for example, the third node may be a primary node in a dual connection, and the fourth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the third node may be a source node in a handover, and the fourth node may be a target node and / or a candidate target node in a handover.

[0504] Step 401K: The third node sends the information of the user and / or resource reservation requested in the conditional switching to the fourth node. The information of the user and / or resource reservation requested in the conditional switching may be the aforementioned third message. In one implementation process, the source node may judge the probability and / or time of the user arriving at the target cell and / or node based on the user's measurement report, motion trajectory, motion speed, etc. The source node sends the information to the target node, and the target node may use the information to formulate a resource reservation strategy, for example, to reserve resources when the user is about to arrive at the target cell and / or node to improve resource utilization, for example, to avoid waste of resources caused by long-term resource reservation due to the user not arriving at the target cell and / or node for a long time.

[0505] Step 402K: The fourth node decides to accept and / or reject the conditional handover request based on the received user-related information and / or the related information of requesting resource reservation and resource reservation. The fourth node sends a conditional handover response to the third node.

[0506] Step 403K: The fourth node makes a resource reservation decision based on the received information about the user in the conditional handover and / or the information about the request for resource reservation. For example, resource reservation is performed when the user is about to arrive at the target cell and / or node to improve resource utilization, for example, to avoid resource waste caused by long-term resource reservation due to the user not arriving at the target cell and / or node for a long time.

[0507] Step 404K: The third node makes a switching decision and / or configures and / or performs a switching action and / or forwards it to other nodes, etc.

[0508] Figure 5A A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5AThe process of exchanging conditional handover related prediction information between two nodes is shown, so that the fifth node can obtain the prediction results related to conditional handover of the fourth node and / or other nodes, and the fifth information can set the handover related decision and / or forward it to other nodes, etc. In some embodiments, for example, the fifth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the sixth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the fifth node can be an AMF or an SMF or an MME, and the sixth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the fifth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node can be an AMF or an SMF or an MME. In some other embodiments, for example, the sixth node may be a UE, and the fifth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the fifth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the sixth node may be a primary node in a dual connection. In some other embodiments, for example, the fifth node may be a primary node in a dual connection, and the sixth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the fifth node may be a source node in a handover, and the sixth node may be a target node and / or a candidate target node in a handover. In some other embodiments, the fifth node may be a target node and / or a candidate target node in a handover, and the sixth node may be a source node in a handover. In some other embodiments, the fifth node may be a source secondary node and / or a target secondary node, and the sixth node may be a UE. In some further embodiments, the fifth node may be a source master node and / or a target master node, and the sixth node may be a UE.

[0509] Step 501A: The sixth node sends conditional switching related prediction information to the fifth node. The conditional switching related prediction information may be the aforementioned sixth message.

[0510] Step 502A: The fifth node makes a switching-related decision based on the received conditional switching-related prediction information, and / or forwards it to other nodes for other nodes to make switching-related decisions, etc. In some embodiments, the information can be used to determine whether to trigger early data forwarding. If the decision is to trigger, the fifth node can forward data to the target node. If the decision is to trigger but there is no relevant transmission address, the fifth node (for example, it can be a secondary node) can use the first message to request the data transmission address from the primary node and / or other nodes; if the decision is to trigger but there is no relevant transmission address, the fifth node (for example, it can be the primary node) can also use the second message to inform the secondary node of the data transmission address of the secondary node and / or trigger the secondary node to forward data to other target secondary nodes. In other embodiments, the information can be used to make decisions related to resource reservation, such as resource reservation time, etc. For example, the fifth node (which can be the source node) can make information about user and / or resource reservation requested in conditional switching, and send the formulated information about user and / or resource reservation requested in conditional switching to the target node, and refer to the relevant content of Figure 4 later; or the fifth node (which can be the target node) can make resource reservation information in conditional switching, and refer to the relevant content of Figure 4 later. This figure can be combined with other embodiments in the present disclosure.

[0511] Figure 5B A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5BThe process of exchanging conditional handover related prediction information between two nodes is shown, so that the fifth node can obtain the prediction results related to conditional handover of the fourth node and / or other nodes, and the fifth information can set the handover related decision and / or forward it to other nodes, etc. In some embodiments, for example, the fifth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the sixth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In other embodiments, for example, the fifth node can be an AMF or an SMF or an MME, and the sixth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In still other embodiments, for example, the fifth node can be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the sixth node can be an AMF or an SMF or an MME. In some other embodiments, for example, the sixth node may be a UE, and the fifth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the fifth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection, and the sixth node may be a primary node in a dual connection. In some other embodiments, for example, the fifth node may be a primary node in a dual connection, and the sixth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in a dual connection. In some other embodiments, the fifth node may be a source node in a handover, and the sixth node may be a target node and / or a candidate target node in a handover. In some other embodiments, the fifth node may be a target node and / or a candidate target node in a handover, and the sixth node may be a source node in a handover. In some other embodiments, the fifth node may be a source secondary node and / or a target secondary node, and the sixth node may be a UE. In some further embodiments, the fifth node may be a source master node and / or a target master node, and the sixth node may be a UE.

[0512] Step 501B: The fifth node sends a conditional handover related prediction information reporting request to the sixth node, requesting the sixth node to send conditional handover related prediction information to the fifth node. The conditional handover related prediction information reporting request may be the aforementioned fifth message.

[0513] Step 502B: The sixth node sends conditional switching related prediction information to the fifth node. The conditional switching related prediction information may be the aforementioned sixth message.

[0514] Step 503B: The fifth node makes a switching-related decision based on the received conditional switching-related prediction information, and / or forwards it to other nodes for other nodes to make switching-related decisions, etc. In some embodiments, this information can be used to determine whether to trigger early data forwarding. If the decision is to trigger, the fifth node can forward data to the target node. If the decision is to trigger but there is no relevant transmission address, the fifth node (for example, it can be a secondary node) can use the first message to request the data transmission address from the primary node and / or other nodes; if the decision is to trigger but there is no relevant transmission address, the fifth node (for example, it can be the primary node) can also use the second message to inform the secondary node of the data transmission address of the secondary node and / or trigger the secondary node to forward data to other target secondary nodes. In other embodiments, the information can be used to make decisions related to resource reservation, such as resource reservation time, etc. For example, the fifth node (which can be the source node) can make information about user and / or resource reservation requested in conditional switching, and send the formulated information about user and / or resource reservation requested in conditional switching to the target node, and refer to the relevant content of Figure 4 later; or the fifth node (which can be the target node) can make resource reservation information in conditional switching, and refer to the relevant content of Figure 4 later. This figure can be combined with other embodiments in the present disclosure.

[0515] Figure 5C A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5C The prediction information related to the switching of interaction conditions between the UE, the source master node, the source slave node, and the target slave node is shown. After receiving the information, the source slave node is used to decide whether to trigger early data forwarding, so that the source slave node can trigger early data forwarding at an appropriate time, and / or select appropriate cells and / or nodes for data forwarding, so as to avoid triggering early data forwarding too early and / or too late, and / or avoid unnecessary data forwarding, etc.

[0516] Step 500C: Conditional secondary node change process.

[0517] Step 501C: The UE sends conditional handover related prediction information to the source master node. The conditional handover related prediction information may be the aforementioned sixth message.

[0518] Step 502C: The source master node sends the conditional switching related prediction information to the source slave node. The conditional switching related prediction information may be the aforementioned sixth message. In an implementation process, the message may be carried by the slave node modification request message.

[0519] Step 503C: The source secondary node sends a secondary node modification request confirmation message to the source primary node.

[0520] Step 504C: The source secondary node may decide whether to trigger early data forwarding and / or a target node for early data forwarding based on the collected conditional switching related prediction information.

[0521] Step 505C: If step 504C determines to perform early data forwarding, the source secondary node performs data forwarding to all and / or selected target secondary nodes.

[0522] Figure 5D A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5D The prediction information related to the switching of interaction conditions between the UE, the source master node, the source slave node, and the target slave node is shown. After receiving the information, the source slave node is used to decide whether to trigger early data forwarding, so that the source slave node can trigger early data forwarding at an appropriate time, and / or select appropriate cells and / or nodes for data forwarding, so as to avoid triggering early data forwarding too early and / or too late, and / or avoid unnecessary data forwarding, etc.

[0523] Step 500D: Conditional auxiliary node change process.

[0524] Step 501D: The UE sends the conditional switching related prediction information to the source auxiliary node. The conditional switching related prediction information may be the aforementioned sixth message. The message may be sent directly by the UE to the source auxiliary node, or the UE may use the RRC container to carry the sixth message and send it to the source auxiliary node through forwarding of the source primary node, that is, the user sends it to the source primary node, and the source primary node forwards it to the source auxiliary node.

[0525] Step 502D: The source secondary node may decide whether to trigger early data forwarding and / or the target node for early data forwarding based on the collected conditional switching related prediction information.

[0526] Step 503D: If step 502D determines to perform early data forwarding, the source slave node forwards data to all and / or selected target slave nodes.

[0527] Figure 5E A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5D The prediction information related to the switching of interaction conditions between the UE, the source master node, and the target slave node is shown. After receiving the information, the source master node is used to decide whether to trigger early data forwarding, so that the source master node can trigger early data forwarding at an appropriate time, and / or select appropriate cells and / or nodes for data forwarding, so as to avoid triggering early data forwarding too early and / or too late, and / or avoid unnecessary data forwarding, etc.

[0528] Step 500E: Conditional secondary node change and / or addition process.

[0529] Step 501E: The UE sends the conditional handover related prediction information to the source master node. The conditional handover related prediction information may be the aforementioned sixth message.

[0530] Step 502E: The source master node may decide whether to trigger early data forwarding and / or the target node for early data forwarding based on the collected conditional switching related prediction information.

[0531] Step 503E: If step 502E determines to perform early data forwarding, the source master node forwards data to all and / or selected target slave nodes.

[0532] Fig. 5F A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Fig. 5F The prediction information related to the switching of interaction conditions between the UE, the source node, and the target node is shown. After receiving the information, the source node is used to decide whether to trigger early data forwarding, so that the source node can trigger early data forwarding at an appropriate time, and / or select appropriate cells and / or nodes for data forwarding, so as to avoid triggering early data forwarding too early and / or too late, and / or avoid unnecessary data forwarding, etc.

[0533] Step 500F: Conditional switching process.

[0534] Step 501F: The UE sends the conditional handover related prediction information to the source node. The conditional handover related prediction information may be the aforementioned sixth message.

[0535] Step 502F: The source node may decide whether to trigger early data forwarding and / or the target node for early data forwarding based on the collected conditional switching related prediction information.

[0536] Step 503F: If step 502F determines to perform early data forwarding, the source node forwards data to all and / or selected target nodes.

[0537] Figure 5G A schematic diagram of one aspect of a method for supporting mobility management according to an embodiment of the present disclosure is shown. Specifically, Figure 5G The prediction information related to the switching of interaction conditions between the UE, the source master node, the source slave node, and the target slave node is shown. After receiving the information, the source master node is used to decide whether to trigger early data forwarding, so that the source slave node can trigger early data forwarding at an appropriate time, and / or select appropriate cells and / or nodes for data forwarding, so as to avoid triggering early data forwarding too early and / or too late, and / or avoid unnecessary data forwarding, etc.

[0538] Step 500G: Conditional secondary node change process.

[0539] Step 501G: The UE sends conditional handover related prediction information to the source master node. The conditional handover related prediction information may be the aforementioned sixth message.

[0540] Step 502G: The source master node decides whether to trigger early data forwarding and which cells to select for early data forwarding.

[0541] Step 503G: The source master node sends a data transmission address to the source secondary node. The source master node may send the selected cell for early data forwarding and / or the corresponding data transmission address to the source secondary node. In one implementation, the data transmission address may be the aforementioned second message.

[0542] Step 504G: The source secondary node forwards data to the target secondary node.

[0543] Fig.11A A schematic diagram of one aspect of a node execution method according to an embodiment of the present disclosure is shown. Specifically, Fig.11AThe process of exchanging Hybrid Automatic RepeatreQuest (HARQ) transmission related parameters between two nodes is shown, so that the seventh node can obtain the relevant parameters of HARQ transmission of the eighth node and / or other nodes, and the seventh node can use the parameters to evaluate the quality of wireless resources. In one embodiment, the seventh node can make relevant decisions based on the HARQ transmission related parameters, such as selecting a transmission path and / or formulating a resource allocation strategy, for example, selecting a relevant path in the Packet Data Convergence Protocol (PDCP) replication. In some embodiments, for example, the seventh node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the eighth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the seventh node may be an AMF or an SMF or an MME, and the eighth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In some further embodiments, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be an AMF or an SMF or an MME. In some further embodiments, for example, the seventh node may be a node hosting a PDCP entity, and the eighth node may be a node interacting with a node hosting a PDCP entity. The node interacting with a node hosting a PDCP entity may also be referred to as a corresponding node. In some further embodiments, for example, the seventh node may be a node interacting with a node hosting a PDCP entity, and the eighth node may be a node hosting a PDCP entity. In some other embodiments, for example, the seventh node may be a UE, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the seventh node may be a secondary node and / or a target secondary node and / or a candidate target secondary node (CandidateTarget Secondary Node) in a dual connection, and the eighth node may be a primary node in a dual connection.In some other embodiments, for example, the seventh node may be a master node in a dual connection, and the eighth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node in the dual connection. In some other embodiments, the seventh node may be a source node in a handover, and the eighth node may be a target node and / or a candidate target node in a handover. In some other embodiments, the seventh node may be a target node and / or a candidate target node in a handover, and the eighth node may be a source node in a handover. In some other embodiments, the seventh node may be a source secondary node and / or a target secondary node, and the eighth node may be a UE. In some other embodiments, the seventh node may be a source master node and / or a target master node, and the eighth node may be a UE.

[0544] Step 1101A: The eighth node sends HARQ transmission related parameters to the seventh node. The HARQ transmission related parameters may include one or more of the following: the number of HARQ transmissions, the number of HARQ transmissions within a certain period of time, the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, the (average) number of HARQ retransmissions for transmitting a certain amount of data, the average number of retransmissions, the average number of transmissions, the event that triggers the report, and indication information of the above parameters, etc. Among them, the average number of retransmissions may be the average number of retransmissions required for the transmission of one or more data packets. The average number of transmissions may be the average number of transmissions required for the transmission of one or more data packets, and the transmission includes the first transmission and retransmissions. Among them, the indication information of the existence of the above-mentioned parameters may include one or more of the following: indication information of the existence of the number of HARQ transmissions, indication information of the existence of the number of HARQ transmissions within a certain period of time, indication information of the (average) number of HARQ transmissions for transmitting a certain amount of data, indication information of the (average) number of HARQ failures that occur when transmitting a certain amount of data, indication information of the (average) number of HARQ retransmissions that occur when transmitting a certain amount of data, indication information of the average number of retransmissions, indication information of the average number of transmissions, etc.

[0545] The event triggering the report may include one or more of the following: the number of HARQ failures reaches a predetermined threshold, the number of HARQ retransmissions reaches a predetermined threshold, the HARQ failure rate reaches a predetermined threshold, the HARQ retransmission rate reaches a predetermined threshold, and the HARQ parameter reaches a predetermined threshold. The HARQ parameter may include one or more of the following: the number of HARQ transmissions, the number of HARQ transmissions within a certain period of time, the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, the (average) number of HARQ retransmissions for transmitting a certain amount of data, the average number of retransmissions, and the average number of transmissions.

[0546] The HARQ transmission related parameters may be carried by a downlink data transmission status (DL DATA DELIVERY STATUS) information frame, an assistance information data (ASSISTANCE INFORMATION DATA) information frame, a downlink user data (DL USERDATA) information frame, or a new information frame; or may be carried by an assistance information type (Assistance Information Type) in the assistance information data; the indication information of the existence of the HARQ transmission related parameters may be carried by the number of octets for RadioQuality Assistance Information Field (Number of octets for RadioQuality Assistance Information Field) in the assistance information data. The HARQ transmission related parameters may also be carried by an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container and / or Medium Access Control Control Element (MAC CE).

[0547] The seventh node may evaluate the radio resource status and / or the radio transmission status according to the HARQ transmission related parameters.

[0548] Step 1102A: The seventh node makes relevant decisions and / or forwards them to other nodes. The relevant decisions may include one or more of the following: selecting a transmission path, a resource allocation strategy, selecting a relevant path in PDCP duplication, etc.

[0549] Fig. 11B A schematic diagram of one aspect of a node execution method according to an embodiment of the present disclosure is shown. Specifically, Fig. 11BThe process of exchanging Hybrid Automatic RepeatreQuest (HARQ) transmission related parameters between two nodes is shown, so that the seventh node can obtain the relevant parameters of HARQ transmission of the eighth node and / or other nodes, and the seventh node can use the parameters to evaluate the quality of wireless resources. In one embodiment, the seventh node can make relevant decisions based on the HARQ transmission related parameters, such as selecting a transmission path and / or formulating a resource allocation strategy, for example, selecting a relevant path in the Packet Data Convergence Protocol (PDCP) replication. In some embodiments, for example, the seventh node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the eighth node can be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the seventh node may be an AMF or an SMF or an MME, and the eighth node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In some further embodiments, for example, the seventh node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the eighth node may be an AMF or an SMF or an MME. In some further embodiments, for example, the seventh node may be a node having a PDCP entity, and the eighth node may be a node interacting with a node having a PDCP entity. In some further embodiments, for example, the seventh node may be a node interacting with a node having a PDCP entity, and the eighth node may be a node having a PDCP entity. In some further embodiments, for example, the seventh node may be a UE, and the eighth node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In some other embodiments, for example, the seventh node may be a secondary node and / or a target secondary node and / or a candidate target secondary node (Candidate TargetSecondary Node) in the dual connection, and the eighth node may be a primary node in the dual connection. In some other embodiments, for example, the seventh node may be a primary node in the dual connection, and the eighth node may be a secondary node and / or a target secondary node and / or a candidate target secondary node (Candidate Target Secondary Node) in the dual connection. In some other embodiments, the seventh node may be a source node in a handover, and the eighth node may be a target node and / or a candidate target node in a handover.In some other embodiments, the seventh node may be a target node and / or a candidate target node in the handover, and the eighth node may be a source node in the handover. In some other embodiments, the seventh node may be a source auxiliary node and / or a target auxiliary node, and the eighth node may be a UE. In some other embodiments, the seventh node may be a source master node and / or a target master node, and the eighth node may be a UE.

[0550] Step 1101B: The seventh node sends a request for HARQ transmission related parameters to the eighth node. The HARQ transmission related parameters may include one or more of the following: the number of HARQ transmissions, the number of HARQ transmissions within a certain period of time, the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, the (average) number of HARQ retransmissions for transmitting a certain amount of data, the average number of retransmissions, the average number of transmissions, and indication information of the existence of the above parameters. The average number of retransmissions may be the average number of retransmissions required for the transmission of one or more data packets. The average number of transmissions may be the average number of transmissions required for the transmission of one or more data packets, and the transmission includes the first transmission and retransmissions. Among them, the indication information of the existence of the above-mentioned parameters may include one or more of the following: indication information of the existence of the number of HARQ transmissions, indication information of the existence of the number of HARQ transmissions within a certain period of time, indication information of the (average) number of HARQ transmissions for transmitting a certain amount of data, indication information of the (average) number of HARQ failures that occur when transmitting a certain amount of data, indication information of the (average) number of HARQ retransmissions that occur when transmitting a certain amount of data, indication information of the average number of retransmissions, indication information of the average number of transmissions, etc.

[0551] The HARQ transmission related parameter request may include one or more of the following:

[0552] -HARQ transmission related parameter request indication: When the eighth node receives the request indication, it needs to report the HARQ related parameters.

[0553] - Polling of HARQ transmission related parameters: After receiving the polling, the eighth node needs to report HARQ related parameters.

[0554] -Parameters requested to be reported: may include one or more of the following: number of HARQ transmissions, number of HARQ transmissions within a certain period of time, (average) number of HARQ transmissions for transmitting a certain amount of data, (average) number of HARQ failures for transmitting a certain amount of data, (average) number of HARQ retransmissions for transmitting a certain amount of data, average number of retransmissions, average number of transmissions, indication information of the existence of the above parameters, etc. Among them, the indication information of the existence of the above parameters may include one or more of the following: indication information of the existence of the number of HARQ transmissions, indication information of the existence of the number of HARQ transmissions within a certain period of time, indication information of the existence of the (average) number of HARQ transmissions for transmitting a certain amount of data, indication information of the existence of the (average) number of HARQ failures for transmitting a certain amount of data, indication information of the existence of the (average) number of HARQ retransmissions for transmitting a certain amount of data, indication information of the existence of the average number of retransmissions, indication information of the existence of the average number of transmissions, etc.

[0555] -HARQ parameter measurement time: used to identify the time for statistics and / or measurement of HARQ parameters.

[0556] -HARQ parameter reporting time: used to identify the reporting time of the HARQ parameters.

[0557] -Data volume corresponding to HARQ parameter measurement: used to identify the data volume corresponding to the statistics and / or measurement of HARQ parameters. For example, when the requested parameter is the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, and the (average) number of HARQ retransmissions for transmitting a certain amount of data, the data volume indicates a certain amount of data among the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, and the (average) number of HARQ retransmissions for transmitting a certain amount of data.

[0558] - Reporting mode: can include single reporting, on-demand reporting, periodic reporting, event-triggered reporting, etc.

[0559] -Reporting period: used to indicate the reporting period of periodic reporting.

[0560] -Measurement cycle

[0561] - Events that trigger reporting: may include one or more of:

[0562] ○ The number of HARQ failures reaches a predetermined threshold: the event needs to indicate the predetermined threshold.

[0563] ○ The number of HARQ retransmissions reaches a predetermined threshold: the event needs to indicate the predetermined threshold.

[0564] ○ The HARQ failure rate reaches a predetermined threshold: the event needs to indicate the predetermined threshold.

[0565] ○ The HARQ retransmission rate reaches a predetermined threshold: the event needs to indicate the predetermined threshold.

[0566] ○HARQ parameter reaches a predetermined threshold: the event needs to indicate the predetermined threshold. The HARQ parameter may include one or more of the following: number of HARQ transmissions, number of HARQ transmissions within a certain period of time, (average) number of HARQ transmissions for transmitting a certain amount of data, (average) number of HARQ failures for transmitting a certain amount of data, (average) number of HARQ retransmissions for transmitting a certain amount of data, average number of retransmissions, average number of transmissions.

[0567] The HARQ transmission related parameter request may be carried by a downlink data transmission status (DL DATA DELIVERYSTATUS) information frame, an auxiliary information data (ASSISTANCE INFORMATION DATA) information frame, a downlink user data (DLUSER DATA) information frame, or a new information frame. The HARQ transmission related parameter request may also be carried by an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or an RRC container and / or a medium access control control element (Medium Access Control Control Element, MAC CE). The eighth node may measure and / or collect and / or report the HARQ transmission related parameters according to the received HARQ transmission related parameter request.

[0568] Step 1102B: The eighth node sends HARQ transmission related parameters to the seventh node. The HARQ transmission related parameters may include one or more of the following: the number of HARQ transmissions, the number of HARQ transmissions within a certain period of time, the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, the (average) number of HARQ retransmissions for transmitting a certain amount of data, the average number of retransmissions, the average number of transmissions, the event that triggers the report, and indication information of the above parameters, etc. Among them, the average number of retransmissions may be the average number of retransmissions required for the transmission of one or more data packets. The average number of transmissions may be the average number of transmissions required for the transmission of one or more data packets, and the transmission includes the first transmission and retransmissions. Among them, the indication information of the existence of the above-mentioned parameters may include one or more of the following: indication information of the existence of the number of HARQ transmissions, indication information of the existence of the number of HARQ transmissions within a certain period of time, indication information of the (average) number of HARQ transmissions for transmitting a certain amount of data, indication information of the (average) number of HARQ failures that occur when transmitting a certain amount of data, indication information of the (average) number of HARQ retransmissions that occur when transmitting a certain amount of data, indication information of the average number of retransmissions, indication information of the average number of transmissions, etc.

[0569] The event triggering the report may include one or more of the following: the number of HARQ failures reaches a predetermined threshold, the number of HARQ retransmissions reaches a predetermined threshold, the HARQ failure rate reaches a predetermined threshold, the HARQ retransmission rate reaches a predetermined threshold, and the HARQ parameter reaches a predetermined threshold. The HARQ parameter may include one or more of the following: the number of HARQ transmissions, the number of HARQ transmissions within a certain period of time, the (average) number of HARQ transmissions for transmitting a certain amount of data, the (average) number of HARQ failures for transmitting a certain amount of data, the (average) number of HARQ retransmissions for transmitting a certain amount of data, the average number of retransmissions, and the average number of transmissions.

[0570] The HARQ transmission related parameters may be carried by a downlink data transmission status (DL DATA DELIVERY STATUS) information frame, an assistance information data (ASSISTANCE INFORMATION DATA) information frame, a downlink user data (DL USERDATA) information frame, or a new information frame; or may be carried by an assistance information type (Assistance Information Type) in the assistance information data; the indication information of the existence of the HARQ transmission related parameters may be carried by the number of octets for RadioQuality Assistance Information Field (Number of octets for RadioQuality Assistance Information Field) in the assistance information data. The HARQ transmission related parameters may also be carried by an RRC and / or Xn and / or X2 and / or F1 and / or E1 and / or NG message and / or RRC container and / or Medium Access Control Control Element (MAC CE).

[0571] The seventh node may evaluate the radio resource status and / or the radio transmission status according to the HARQ transmission related parameters.

[0572] Step 1103B: The seventh node makes relevant decisions and / or forwards them to other nodes. The relevant decisions may include one or more of the following: selecting a transmission path, a resource allocation strategy, selecting a relevant path in PDCP duplication, etc.

[0573] In the present disclosure, a node interacting with a node hosting a PDCP entity (A node interacting with the node hosting PDCP entity) may also be referred to as a corresponding node (Cooresponding node).

[0574] In the above examples, the source master node and the target secondary node are used as examples, but the content of the present disclosure is not limited to the example content. For example, the source master node may also be the source node in the switch, and the target secondary node may also be the secondary node in the switch. In this case, in the above examples, the secondary node add request message should be replaced with a switch request message, and the secondary node add request confirmation message should be replaced with a switch request confirmation message.

[0575] It should be understood that, depending on the application scenario, the various exemplary aspects, methods, steps, processes, etc. shown in the above-mentioned drawings can be combined and implemented in any manner, and this document does not limit this.

[0576] Next, Figure 6A flowchart of a method 600 performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0577] like Figure 6 As shown, according to an embodiment of the present disclosure, a method 600 executed by a first node in a wireless communication system may include: in step S601, sending a fourth message to a second node, wherein the fourth message includes information related to a resource reservation time in a conditional switching; in step S602, receiving a second message including a data transmission address of a candidate target cell from the second node; in step S603, receiving a sixth message from the second node or a user equipment UE, wherein the sixth message includes prediction information related to the conditional switching; in step S604, determining whether to perform data transmission based on the prediction information related to the conditional switching; and in step S605, when it is determined that data transmission is to be performed, performing data transmission based on the data transmission address.

[0578] According to an embodiment of the present disclosure, before receiving a second message including a data transmission address of a candidate target cell from the second node, a radio resource control RRC reconfiguration complete message is sent by the UE to the second node.

[0579] According to an embodiment of the present disclosure, the information related to the resource reservation time in the conditional switching is used by the second node to determine whether to use the first node as a candidate target node.

[0580] According to an embodiment of the present disclosure, the method 600 may further include: sending a first message including a request for a data transmission address to the second node, wherein the second message is sent from the second node based on the first message.

[0581] According to an embodiment of the present disclosure, method 600 may further include: receiving a third message from the second node, wherein the third message includes information related to the user equipment UE in the conditional switching and / or information related to the resource reservation request in the conditional switching, and wherein the fourth message is sent to the second node based on the third message.

[0582] According to an embodiment of the present disclosure, method 600 may further include: sending a fifth message to the second node, wherein the fifth message includes a request for reporting prediction information related to conditional switching, and wherein the sixth message is sent from the second node based on the fifth message.

[0583] According to an embodiment of the present disclosure, the data transmission includes one or more of normal data transmission and data forwarding, wherein the data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

[0584] According to an embodiment of the present disclosure, the second message includes one or more of the following: an identifier of the UE performing conditional switching, a request index corresponding to the second message, an accepted quality of service QoS flow identifier, a transmission address, a data transmission direction corresponding to the transmission address, information on whether data transmission is triggered, an identifier for triggering data transmission, an event for triggering data transmission, a cell identifier corresponding to the transmission address, a node identifier corresponding to the transmission address, a slice identifier corresponding to the transmission address, a protocol data unit PDU session identifier corresponding to the transmission address, a wireless bearer identifier corresponding to the transmission address, a quality of service QoS flow identifier corresponding to the transmission address, and information that can be used for data transmission.

[0585] According to an embodiment of the present disclosure, the first message includes one or more of the following: an identifier of the UE performing conditional switching, a request index, an identifier for requesting address reporting, a direction of data transmission, a cell identifier corresponding to the requested transmission address, a node identifier corresponding to the requested transmission address, a slice identifier corresponding to the requested transmission address, a protocol data unit PDU session identifier corresponding to the requested transmission address, a wireless bearer identifier corresponding to the requested transmission address, a quality of service QoS flow identifier corresponding to the requested transmission address, and requested information for data transmission.

[0586] According to an embodiment of the present disclosure, the fourth message includes one or more of the following: a cell identifier corresponding to the information related to the resource reservation time in the conditional switching, a node identifier corresponding to the information related to the resource reservation time in the conditional switching, a slice identifier corresponding to the information related to the resource reservation time in the conditional switching, a UE identifier performing conditional switching corresponding to the information related to the resource reservation time in the conditional switching, the maximum resource reservation time, the minimum resource reservation time, the resource reservation time interval, and the applicable time corresponding to the switching configuration.

[0587] According to an embodiment of the present disclosure, the third message includes one or more of the following: a cell identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a node identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a slice identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a UE identifier for conditional switching corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, an expected maximum arrival probability of the UE, a time corresponding to the expected maximum arrival probability of the UE, an expected minimum arrival probability of the UE, a time corresponding to the expected minimum arrival probability of the UE, an expected arrival time of the UE, an expected arrival probability of the UE, a time corresponding to the expected arrival probability of the UE, a request for maximum resource reservation time, a request for minimum resource reservation time, a request for resource reservation time interval, a request for resource reservation time, an indication of whether setting the resource reservation time is allowed, and prediction credibility.

[0588] According to an embodiment of the present disclosure, the sixth message includes one or more of the following: a request identifier corresponding to the sixth message, a sending node identifier, a receiving node identifier, a user identifier corresponding to the reported information, measured and / or predicted content, reported content, an event triggering the report, the applicable time corresponding to the measured content, and the applicable time corresponding to the reported content.

[0589] According to an embodiment of the present disclosure, the fifth message includes one or more of the following: a request identifier, a sending node identifier, a receiving node identifier, a UE identifier corresponding to the requested information, a reporting mode, a reporting time, a reporting period, a reporting trigger event, a measurement and / or prediction mode, a measurement and / or prediction time, a measurement and / or prediction period, requested measurement and / or prediction content, requested reporting content, the applicable time corresponding to the requested reporting content, the requested prediction time, the requested reporting credibility requirement, and the prediction credibility.

[0590] Figure 7 A flowchart of a method 700 performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0591] like Figure 7As shown, the method 700 performed by the second node in the wireless communication system according to the embodiment of the present disclosure may include: in step S701, receiving a fourth message from the first node, wherein the fourth message includes information related to the resource reservation time in the conditional switching; in step S702, sending a second message including a data transmission address of a candidate target cell to the first node; and in step S703, sending a sixth message to the first node, wherein the sixth message includes prediction information related to the conditional switching. In some embodiments, the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission. In some embodiments, in the case of determining to perform data transmission, the first node performs data transmission based on the data transmission address.

[0592] According to an embodiment of the present disclosure, before sending the second message including the data transmission address of the candidate target cell to the first node, the method 700 may further include: receiving a radio resource control RRC reconfiguration complete message from a user equipment UE.

[0593] According to an embodiment of the present disclosure, the method 700 may further include: determining whether to use the first node as a candidate target node based on information related to the resource reservation time in the conditional switching.

[0594] According to an embodiment of the present disclosure, the method 700 may further include: receiving a first message including a request for a data transmission address from the first node, wherein the second message is sent to the first node based on the first message.

[0595] According to an embodiment of the present disclosure, method 700 may further include: sending a third message to the first node, wherein the third message includes information related to the user equipment UE in the conditional switching and / or information related to the resource reservation request in the conditional switching, and wherein the fourth message is sent from the first node based on the third message.

[0596] According to an embodiment of the present disclosure, method 700 may further include: receiving a fifth message from the first node, wherein the fifth message includes a request for reporting prediction information related to conditional switching, and wherein the sixth message is sent to the first node based on the fifth message.

[0597] According to an embodiment of the present disclosure, the data transmission includes one or more of normal data transmission and data forwarding, wherein the data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

[0598] According to an embodiment of the present disclosure, the second message includes one or more of the following: an identifier of the UE performing conditional switching, a request index corresponding to the second message, an accepted quality of service QoS flow identifier, a transmission address, a data transmission direction corresponding to the transmission address, information on whether data transmission is triggered, an identifier for triggering data transmission, an event for triggering data transmission, a cell identifier corresponding to the transmission address, a node identifier corresponding to the transmission address, a slice identifier corresponding to the transmission address, a protocol data unit PDU session identifier corresponding to the transmission address, a wireless bearer identifier corresponding to the transmission address, a quality of service QoS flow identifier corresponding to the transmission address, and information that can be used for data transmission.

[0599] According to an embodiment of the present disclosure, the first message includes one or more of the following: an identifier of the UE performing conditional switching, a request index, an identifier for requesting address reporting, a direction of data transmission, a cell identifier corresponding to the requested transmission address, a node identifier corresponding to the requested transmission address, a slice identifier corresponding to the requested transmission address, a protocol data unit PDU session identifier corresponding to the requested transmission address, a wireless bearer identifier corresponding to the requested transmission address, a quality of service QoS flow identifier corresponding to the requested transmission address, and requested information for data transmission.

[0600] According to an embodiment of the present disclosure, the fourth message includes one or more of the following: a cell identifier corresponding to the information related to the resource reservation time in the conditional switching, a node identifier corresponding to the information related to the resource reservation time in the conditional switching, a slice identifier corresponding to the information related to the resource reservation time in the conditional switching, a UE identifier performing conditional switching corresponding to the information related to the resource reservation time in the conditional switching, the maximum resource reservation time, the minimum resource reservation time, the resource reservation time interval, and the applicable time corresponding to the switching configuration.

[0601] According to an embodiment of the present disclosure, the third message includes one or more of the following: a cell identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a node identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a slice identifier corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, a UE identifier for conditional switching corresponding to information related to the user equipment UE in conditional switching and / or information related to the resource reservation request in conditional switching, an expected maximum arrival probability of the UE, a time corresponding to the expected maximum arrival probability of the UE, an expected minimum arrival probability of the UE, a time corresponding to the expected minimum arrival probability of the UE, an expected arrival time of the UE, an expected arrival probability of the UE, a time corresponding to the expected arrival probability of the UE, a request for maximum resource reservation time, a request for minimum resource reservation time, a request for resource reservation time interval, a request for resource reservation time, an indication of whether setting the resource reservation time is allowed, and prediction credibility.

[0602] According to an embodiment of the present disclosure, the sixth message includes one or more of the following: a request identifier corresponding to the sixth message, a sending node identifier, a receiving node identifier, a user identifier corresponding to the reported information, measured and / or predicted content, reported content, an event triggering the report, the applicable time corresponding to the measured content, and the applicable time corresponding to the reported content.

[0603] According to an embodiment of the present disclosure, the fifth message includes one or more of the following: a request identifier, a sending node identifier, a receiving node identifier, a UE identifier corresponding to the requested information, a reporting mode, a reporting time, a reporting period, a reporting trigger event, a measurement and / or prediction mode, a measurement and / or prediction time, a measurement and / or prediction period, requested measurement and / or prediction content, requested reporting content, the applicable time corresponding to the requested reporting content, the requested prediction time, the requested reporting credibility requirement, and the prediction credibility.

[0604] Figure 8 A flowchart of a method 800 executed by a user equipment in a wireless communication system according to an embodiment of the present disclosure is shown.

[0605] like Figure 8As shown, according to an embodiment of the present disclosure, method 800 performed by a user equipment in a wireless communication system may include: in step S801, receiving a fourth message from a second node, wherein the fourth message includes an RRC container, and the RRC container includes information related to the resource reservation time in the conditional switching; and in step S802, sending a sixth message to the second node or the first node, wherein the sixth message includes prediction information related to the conditional switching, and the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission.

[0606] According to an embodiment of the present disclosure, the method 800 may further include: based on the information related to the resource reservation time in the conditional switching, detecting whether the operation event is satisfied.

[0607] It should be understood that methods 600, 700, 800, etc. according to the embodiments of the present disclosure may also include any steps described in combination with various examples, aspects, drawings, etc. of the present disclosure.

[0608] Next, Fig. 9 A schematic diagram of a first node 900 according to an embodiment of the present disclosure is shown.

[0609] like Figure 8 As shown, the first node (or first node device) 800 according to an embodiment of the present disclosure may include a transceiver 910 and a processor 920. The transceiver 910 may be configured to send and receive signals. The processor 920 may be coupled to the transceiver 910 and may be configured to (e.g., control the transceiver 910) execute the method performed by the first node according to an embodiment of the present disclosure.

[0610] Fig.10 A schematic diagram of a second node 1000 according to an embodiment of the present disclosure is shown.

[0611] like Fig.10 As shown, the second node (or second node device) 1000 according to an embodiment of the present disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to send and receive signals. The processor 1020 may be coupled to the transceiver 1010 and may be configured to (e.g., control the transceiver 1010) execute the method performed by the second node according to an embodiment of the present disclosure. The processor may also be referred to as a controller.

[0612] Fig.11 A schematic diagram of a user equipment 1100 according to an embodiment of the present disclosure is shown.

[0613] like Fig.11As shown, the user equipment 1100 according to an embodiment of the present disclosure may include a transceiver 1110 and a processor 1120. The transceiver 1110 may be configured to send and receive signals. The processor 1120 may be coupled to the transceiver 1110 and may be configured to (e.g., control the transceiver 1110) execute the method performed by the user equipment according to an embodiment of the present disclosure. In the present disclosure, the processor may also be referred to as a controller.

[0614] The embodiments of the present disclosure further provide a computer-readable medium on which computer-readable instructions are stored. When the instructions are executed by a processor, they can be used to implement any method according to the embodiments of the present disclosure.

[0615] Various embodiments of the present disclosure may be implemented as computer-readable codes embodied on a computer-readable recording medium from a specific perspective. A computer-readable recording medium is any data storage device that can store data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), and the like. Computer-readable recording media may be distributed via a computer system connected via a network, and therefore computer-readable codes may be stored and executed in a distributed manner. Moreover, the functional programs, codes, and code segments for implementing the various embodiments of the present disclosure may be easily interpreted by a technician in the field of the embodiments of the present disclosure.

[0616] It will be understood that the embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. Software may be stored as program instructions or computer-readable codes executable on a processor on a non-transient computer-readable medium. Examples of non-transient computer-readable recording media include magnetic storage media (e.g., ROM, floppy disk, hard disk, etc.) and optical recording media (e.g., CD-ROM, digital video disk (DVD), etc.). Non-transient computer-readable recording media may also be distributed on network-coupled computer systems so that computer-readable codes are stored and executed in a distributed manner. The medium may be read by a computer, stored in a memory, and executed by a processor. Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transient computer-readable recording medium suitable for storing (multiple) programs with instructions for implementing embodiments of the present disclosure. The present disclosure may be implemented by a program having a code for specifically implementing the apparatus and method described in the claims, the program being stored in a machine (or computer) readable storage medium. The program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the present disclosure suitably includes its equivalents.

[0617] The above description is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can make various changes or substitutions within the technical scope disclosed in the present disclosure, and these changes or substitutions should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method performed by a first node in a wireless communication system, comprising: Sending a fourth message to the second node, wherein the fourth message includes information related to the resource reservation time in the conditional switching; receiving from the second node a second message including a data transmission address of a candidate target cell; receiving a sixth message from the second node or user equipment UE, wherein the sixth message includes prediction information related to conditional switching; Determining whether to perform data transmission based on the prediction information related to the conditional switching; and When it is determined to perform data transmission, data transmission is performed based on the data transmission address.

2. The method according to claim 1, wherein: Before receiving a second message including a data transmission address of a candidate target cell from the second node, a radio resource control RRC reconfiguration complete message is sent by the UE to the second node.

3. The method according to claim 1, wherein: The information related to the resource reservation time in the conditional switching is used by the second node to determine whether to use the first node as a candidate target node.

4. The method according to claim 1, further comprising: sending a first message including a request for a data transmission address to the second node, The second message is sent from the second node based on the first message.

5. The method according to claim 1, further comprising: receiving a third message from the second node, wherein the third message includes information related to a user equipment UE in conditional handover and / or information related to a resource reservation request in conditional handover, The fourth message is sent to the second node based on the third message.

6. The method according to claim 1, further comprising: sending a fifth message to the second node, wherein the fifth message includes a request for reporting prediction information related to the conditional switching, The sixth message is sent from the second node based on the fifth message.

7. The method according to claim 1, wherein: The data transmission includes one or more of normal data transmission and data forwarding, The data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

8. A method performed by a second node in a wireless communication system, comprising: receiving a fourth message from the first node, wherein the fourth message includes information related to a resource reservation time in a conditional handover; sending a second message including a data transmission address of a candidate target cell to the first node; and Sending a sixth message to the first node, wherein the sixth message includes prediction information related to conditional switching; The prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission; and Wherein, when it is determined to perform data transmission, the first node performs data transmission based on the data transmission address.

9. The method according to claim 8, before sending a second message including a data transmission address of a candidate target cell to the first node, further comprising: A radio resource control (RRC) reconfiguration complete message is received from a user equipment (UE).

10. The method according to claim 8, further comprising: Whether to use the first node as a candidate target node is determined based on information related to the resource reservation time in the conditional switching.

11. The method according to claim 8, further comprising: receiving from said first node a first message comprising a request for a data transmission address, The second message is sent to the first node based on the first message.

12. The method according to claim 8, further comprising: sending a third message to the first node, wherein the third message includes information related to a user equipment UE in conditional switching and / or information related to a resource reservation request in conditional switching, The fourth message is sent from the first node based on the third message.

13. The method according to claim 8, further comprising: receiving a fifth message from the first node, wherein the fifth message includes a request for reporting prediction information related to conditional switching, The sixth message is sent to the first node based on the fifth message.

14. The method according to claim 8, wherein: The data transmission includes one or more of normal data transmission and data forwarding, The data forwarding includes one or more of early data forwarding, late data forwarding and normal data forwarding.

15. A method performed by a user equipment UE in a wireless communication system, comprising: receiving a fourth message from the second node, wherein the fourth message includes an RRC container, and the RRC container includes information related to a resource reservation time in a conditional handover; and A sixth message is sent to the second node or the first node, wherein the sixth message includes prediction information related to the conditional switching, and the prediction information related to the conditional switching is used by the first node to determine whether to perform data transmission.

16. The method according to claim 15, further comprising: Based on the information related to the resource reservation time in the conditional switching, it is detected whether the operation event is satisfied.

17. A node device in a wireless communication system, comprising: Transceiver; as well as A processor is coupled to the transceiver and is configured to execute the method as claimed in any one of claims 1-7 or 8-14.

18. A user equipment in a wireless communication system, comprising: Transceiver; as well as A processor is coupled to the transceiver and configured to execute the method according to any one of claims 15-16.

19. A computer-readable medium having computer-readable instructions stored thereon, wherein the instructions, when executed by a processor, implement the method according to any one of claims 1-7 or 8-14 or 15-16.

Images