Communication method, communication device, and storage medium

Abstract

The present disclosure relates to the technical field of communication, and particularly relates to a communication method, a communication device and a storage medium, wherein the communication method comprises: receiving first information sent by a network device, wherein the first information is used for indicating to update a mobility-related configuration and is used for indicating a state of the updated mobility-related configuration. According to the present disclosure, in the case that the network device indicates to update the mobility-related configuration to the UE through the first information, the network device can also indicate the state of the updated mobility-related configuration through the first information, according to which, in the case that the UE determines to update the mobility-related configuration, the UE can also determine the state of the updated mobility-related configuration, so that the UE can reasonably perform subsequent operations based on the determined state.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to communication methods, communication devices, and storage media. Background Technology

[0002] Layer 1 and / or Layer 2 triggered mobility (L1 / L2 Triggered Mobility, LTM) can include two types: network-triggered LTM and conditional (C) LTM.

[0003] For example, network-triggered LTM refers to the process by which network devices, based on L1 or L3 measurement results, trigger a cell switch (PCell) and / or PSCell (primary / secondary cell) through the MAC CE (Media Access Control Element). This may be accompanied by changes in the MCG (Master Cell Group) and / or SCG (Secondary Cell Group).

[0004] CLTM refers to the process by which a UE triggers a PCell and / or PSCell cell switch based on L1 measurement and / or L3 measurement conditions configured by the network device. When the UE meets the CLTM conditions configured by the network device, the UE initiates the execution process of the PCell and / or PSCell cell switch. Summary of the Invention

[0005] Embodiments of this disclosure provide communication methods, communication devices, and storage media to address technical problems in the related art.

[0006] According to a first aspect of the present disclosure, a communication method is provided, executed by a user equipment (UE), the method comprising: receiving first information sent by a network device, wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

[0007] According to a second aspect of the present disclosure, a communication method is provided, performed by a network device, the method comprising: sending first information to a user equipment (UE), wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

[0008] According to a third aspect of the present disclosure, a communication method is proposed, comprising: a network device sending first information to a user equipment (UE); the UE determining, based on the first information, an update of mobility-related configuration and a state of the updated mobility-related configuration.

[0009] According to a fourth aspect of the present disclosure, a communication device is provided for performing the communication method described in any one of the first and second aspects.

[0010] According to a fifth aspect of the present disclosure, a communication system is provided, including a user equipment (UE) and a network device, wherein the UE is configured to implement the communication method described in the first aspect, and the network device is configured to implement the communication method described in the second aspect.

[0011] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform the communication method described in any one of the first and second aspects.

[0012] According to a seventh aspect of the present disclosure, a program product is provided that, when executed by a communication device, causes the communication device to perform the communication method described in any one of the first and second aspects.

[0013] According to embodiments of this disclosure, when the network device instructs the UE to update the mobility-related configuration via the first information, it can also instruct the status of the updated mobility-related configuration via the first information. Accordingly, when the UE determines that the mobility-related configuration has been updated, it can also determine the status of the updated mobility-related configuration so that the UE can reasonably perform subsequent operations based on the determined status. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0016] Figure 1B This is a schematic diagram illustrating the correlation between LTM measurement and reporting according to embodiments of this disclosure.

[0017] Figure 2 This is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0018] Figure 3 This is a schematic flowchart illustrating another communication method according to embodiments of the present disclosure.

[0019] Figure 4A This is a schematic block diagram of a communication device according to an embodiment of the present disclosure.

[0020] Figure 4B This is a schematic block diagram of a communication device according to an embodiment of the present disclosure.

[0021] Figure 5A This is a schematic diagram of the structure of the communication device proposed in the embodiments of this disclosure.

[0022] Figure 5B This is a schematic diagram of the chip structure proposed in the embodiments of this disclosure. Detailed Implementation

[0023] Embodiments of this disclosure provide communication methods, communication devices, and storage media.

[0024] In a first aspect, embodiments of this disclosure provide a communication method executed by a user equipment (UE), the method comprising: receiving first information sent by a network device, wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

[0025] In the above embodiments, when the network device instructs the UE to update the mobility-related configuration via the first information, it can also instruct the status of the updated mobility-related configuration via the first information. Therefore, when the UE determines that the mobility-related configuration has been updated, it can also determine the status of the updated mobility-related configuration, so that the UE can make a determination based on the determined status.

[0026] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0027] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0028] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0029] In the embodiments disclosed herein, "multiple" refers to two or more.

[0030] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0031] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0032] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0033] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0034] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0035] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0036] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0037] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0038] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0039] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0040] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0041] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0042] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0043] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0044] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0045] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0046] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0047] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0048] like Figure 1A As shown, the communication system 100 includes user equipment (e.g., terminal) 101 and network equipment 102, wherein the network equipment includes at least one of the following: access network equipment and core network equipment.

[0049] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0050] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0051] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0052] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0053] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0054] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0055] The following embodiments of this disclosure can be applied to Figure 1A The communication system 100 shown, or a part thereof, but not limited to it. Figure 1A The entities shown are illustrative; a communication system may include... Figure 1A All or part of the main body, or may include Figure 1A Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0056] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0057] In some embodiments, Layer 1 and / or Layer 2 triggered mobility (L1 / L2 Triggered Mobility, LTM) can include both network-triggered LTM and conditional LTM (CLTM).

[0058] For example, network-triggered LTM refers to the process by which a network device, based on L1 or L3 measurement results, triggers a cell switch in the PCell (primary cell) and / or PSCell (secondary cell) via network-side signaling (e.g., MAC CE (Media Access Control Control Element)). This may be accompanied by changes in the MCG (Master Cell Group) and / or SCG (Secondary Cell Group).

[0059] In a network-triggered LTM, you can change only PCell and / or MCG, or only PSCell and / or SCG, or you can change both PCell and / or MCG, as well as PSCell and / or SCG simultaneously.

[0060] It should be noted that triggering the above mobility process via MAC CE is only one example of this disclosure. The network side can also trigger the above mobility process via other signaling, such as RRC signaling, physical layer signaling, etc. This disclosure does not limit this.

[0061] In network-triggered LTM, the network device can provide the UE with one or more candidate configurations. For example, a candidate configuration can correspond to one or more cells (or cell groups).

[0062] For example, one candidate configuration corresponds to one candidate PCell (Primary Cell);

[0063] For example, a candidate configuration corresponds to a candidate MCG (primary cell group), wherein the MCG may include one PCell (primary cell) and / or one or more SCells (secondary cells);

[0064] For example, one candidate configuration corresponds to one or more candidate SCells;

[0065] For example, one candidate configuration corresponds to one candidate PSCell (Primary SCG Cell);

[0066] For example, a candidate configuration corresponds to a candidate SCG (Secondary Cell Group), wherein the SCG may include a PSCell and / or one or more SCells.

[0067] For example, the network device receives L1 measurement reports and / or L3 measurement reports sent by the UE. Based on the received measurement reports, the network device changes the UE's serving cell through a cell switch command issued by the MAC CE. The cell switch command indicates the LTM candidate configuration that the network device has provided to the UE in advance through RRC (Radio Resource Control) signaling.

[0068] The UE accesses the target cell indicated in the cell change command based on the received Cell switch command. Since the candidate configuration is provided to the UE in advance via RRC signaling, LTM helps reduce mobility latency.

[0069] For example, CLTM refers to the process by which a UE triggers a PCell and / or PSCell cell switch based on L1 measurement and / or L3 measurement conditions configured by the network device. When the UE meets the CLTM conditions configured by the network device, the UE initiates the execution process of the PCell and / or PSCell cell switch.

[0070] In some embodiments, for LTM (including network-triggered LTM and condition-triggered CLTM), LTM supports subsequent LTM, where subsequent LTM refers to LTM cell change between candidate cells that does not require network RRC reconfiguration. In other words, after the UE performs mobility operations, the UE will not delete the LTM configuration information on its own. The LTM configuration information in the UE can continue to be used to trigger subsequent LTM even if RRC reconfiguration and updates are not performed.

[0071] The following examples illustrate inter-node LTM within the AMF (Access and Mobility Management Function).

[0072] LTM is the process by which the gNB receives L1 or L3 measurement reports from the UE, and based on these reports, the gNB can change the UE's serving cell via a cell handover command signaled via the MAC CE. The cell handover command indicates the LTM candidate configuration previously prepared by the gNB and provided to the UE via RRC signaling. The UE then switches to the target configuration according to the cell handover command.

[0073] The cell handover command is carried in the MAC CE and contains the information required to perform an LTM cell handover.

[0074] The overall LTM process can include steps 1 through 22 as described below. Subsequent LTM operations are completed by repeating the early synchronization, LTM cell handover execution, and LTM cell switching completion steps, without needing to release, reconfigure, or add other LTM candidate configurations after each LTM cell handover. The general air interface procedure applies to SCG LTM. More details on SCG LTM can be found in relevant technologies and will not be elaborated here.

[0075] Step 1: The UE sends a MeasurementReport message (L3 measurement result) containing neighboring cell measurement values ​​to the source gNB.

[0076] Step 2: The source gNB determines the LTM configuration.

[0077] Step 3: The source gNB requests one or more candidate cells and / or one or more candidate gNBs belonging to the source gNB from the LTM.

[0078] For inter-gNB LTM, the source gNB initiates a handover request message containing a candidate cell ID for each candidate cell. For intra-gNB and inter-gNB LTM, the source gNB can request CSI (Channel State Information) resource configuration from the candidate cell or the gNB corresponding to the candidate cell.

[0079] Step 4: Admission control can be performed by the candidate cell or the gNB corresponding to the candidate cell.

[0080] Step 5: The candidate cell or the gNB corresponding to the candidate cell prepares the LTM configuration and provides it to the source gNB.

[0081] For inter-gNB LTM, the candidate gNB (which may be one or more) responds to the source gNB (with HO REQUESTACKNOWLEDGE, including the RRC configuration generated for the accepted candidate cell). For intra-gNB and inter-gNB LTM, the candidate may also include additional information related to CSI configuration and advance synchronization information.

[0082] Step 6: The source gNB sends an LTM configuration update message to the candidate gNB to update the LTM configuration of the candidate cell. The source gNB may include public CSI resource configuration.

[0083] Step 7: The candidate gNB sends an LTM configuration update confirmation message to the source gNB. The candidate gNB can also provide CSI report configuration.

[0084] Step 8: The source gNB sends an RRC reconfiguration message to the UE.

[0085] Step 9: The UE stores the LTM candidate configuration and sends an RRC reconfiguration complete message to the source gNB.

[0086] Step 9a: If advance data forwarding is applied, the source gNB sends an advance state transition message to the candidate gNB.

[0087] Steps 10 and 11: Early DL and UL synchronization with some LTM candidate cells can be performed.

[0088] For example, the source gNB can activate or deactivate the TCI (Transmission Configuration Indicator) status of the candidate LTM cell.

[0089] Depending on the network configuration, the UE can perform advance UL synchronization with LTM candidate cells by using UE-based TA (Timing Advance) measurements (if configured) and / or by sending a preamble to the candidate cells (triggered by the source gNB).

[0090] Through UL synchronization triggered by network devices, the UE receives a PDCCH (Physical Downlink Control Channel) command from the source cell to trigger CFRA (Contention-Free Random Access) for the candidate cell. The UE performs early TA acquisition by sending a preamble to the indicated candidate cell. To minimize data interruption on the source cell caused by CFRA to the indicated candidate cell, the UE does not receive a random access response from the network for TA value acquisition. The candidate gNB sends a TA information transfer message to the source gNB.

[0091] Step 12: The UE performs L1 measurements on the configured LTM candidate cells and sends an L1 measurement report to the source gNB if configured. L1 measurements should be performed whenever RRC reconfiguration (step 8) is applicable.

[0092] Step 13: The source gNB determines to initiate LTM. L3 measurements can also be used to determine this step.

[0093] Step 14: The source gNB decides to perform a cell handover to the target cell and sends an LTM cell handover command MAC CE that triggers the cell handover by including the target configuration ID, which indicates the index of the candidate configuration, one or more beams indicated by the TCI status, and the TA command for the target cell.

[0094] When the security context changes, the LTM cell handover command MAC CE also includes an NCC value. The UE hands over to the target cell and applies the candidate configuration indicated by the target configuration ID. When the security context changes again, the UE generates and applies a new security key based on the received NCC value.

[0095] Step 15: The source gNB sends a cell handover notification message to the target gNB to instruct it to initiate a cell handover command to the UE.

[0096] Step 16: If the UE does not have a valid TA for the target cell as specified in the relevant technology, the UE performs a random access procedure for the target cell.

[0097] Steps 17 and 18: The target gNB sends a handover success message to the source gNB, notifying the UE that it has successfully accessed the target cell. In return, the source gNB sends an SN STATUS TRANSFER message according to the principles described in the handover steps within the AMF and / or UPF (User Plane Function) in the relevant technologies.

[0098] Step 19: The UE completes the LTM cell handover process by sending an RRC reconfiguration complete message to the target cell. If the UE performed the RA procedure in step 16, the UE considers the LTM cell handover to be successfully completed when the random access procedure is successfully completed. For LTM without a RACH (Random Access Channel), the UE considers the LTM cell handover to be successfully completed when it determines that the network has successfully received its first UL data.

[0099] It should be noted that the execution order of steps 17 to 19 can be adjusted. For example, the target gNB can send a handover success message to the source gNB after receiving the RRC reconfiguration complete message.

[0100] Step 20: The new source gNB (i.e., the target gNB) sends an LTM configuration update message to the candidate gNB.

[0101] Step 21: The candidate gNB responds to the LTM configuration update confirmation message of the new source gNB.

[0102] Step 22: If no LTM candidate cell exists in the old source gNB, the new source gNB can send a UE context release message to notify the old source gNB to release the radio and control plane resources associated with the UE context. Any ongoing data forwarding can continue.

[0103] For subsequent LTM cell handover execution, steps 10-22 can be executed multiple times using the LTM candidate configuration provided in step 8.

[0104] The steps in the foregoing embodiments can be applied to the DU (Distributed Unit) LTM within gNB, the DU LTM between gNBs, and the CU (Centralized Unit) LTM between gNBs.

[0105] The following examples illustrate LTM measurement and reporting (also known as reporting).

[0106] Figure 1B This is a schematic diagram illustrating the correlation between LTM measurement and reporting according to embodiments of this disclosure.

[0107] like Figure 1B As shown, the LTM measurement and reporting configuration can specifically include LTM measurement resource configuration and LTM report configuration, and the LTM measurement resource configuration and LTM report configuration can be related.

[0108] In some embodiments, the LTM measurement and reporting configuration can be collectively referred to as LTM measurement configuration, which specifically may include LTM measurement resource configuration and LTM reporting configuration.

[0109] For example, LTM measurement configuration can refer to both LTM measurement resource configuration and LTM reporting configuration.

[0110] In addition, LTM measurement resource configuration can also be called measurement object configuration.

[0111] For example, LTM measurement resource configuration can be LTM-CSI-ResourceConfig. Depending on the measurement object, such as SSB (Synchronization Signal Block) or CSI-RS (Channel State Information Reference Signal), LTM-CSI-ResourceConfig can further include LTM-SSB-ResourceSet and LTM-NZP-CSI-RS-ResourceSet.

[0112] Among them, LTM-SSB-ResourceSet can include IEs (Information Elements) such as ltm-SSB-ResourceList and ltm-CandidateList; LTM-NZP-CSI-RS-ResourceSet can include IEs such as ltm-CSI-RS-ResourceList and ltm-CandidateList.

[0113] In some embodiments, the LTM-SSB-ResourceSet includes ltm-SSB-ResourceList and ltm-CandidateList, which respectively indicate the SSB index and LTM Candidate ID, used to indicate the index of the SSB corresponding to the Candidate Cell corresponding to the LTM Candidate ID. In other words, it indicates the SSB for which the UE measures this LTM Candidate Cell.

[0114] In some embodiments, the LTM-NZP-CSI-RS-ResourceSet includes ltm-CSI-RS-ResourceList and ltm-CandidateList, which respectively indicate the NZP-CSI-RS-ResourceId and LTMCandidate ID, used to indicate the NZP-CSI-RS-ResourceId corresponding to the Candidate Cell corresponding to the LTM Candidate ID. In other words, it indicates the NZP-CSI-RS-ResourceId of the LTM Candidate Cell measured by the UE.

[0115] For example, the LTM report configuration can be LTM-CSI-ReportConfig, which can be used to configure the corresponding configurations for different types of reporting, such as Periodic, semiPersistentOnPUSCH, semiPersistentOnPUCCH, and eventTriggered.

[0116] In some embodiments, an LTM report configuration can be associated with one or more LTM measurement resource configurations.

[0117] In some embodiments, an LTM measurement resource configuration can be associated with one or more different LTM reporting configurations.

[0118] In some embodiments, measurement reporting may include network-triggered measurement reporting and event-triggered measurement reporting.

[0119] In some embodiments, for network-triggered L1 measurement reporting, 3GPP has enhanced L1 measurement in R18 LTM, supporting both intra-frequency and inter-frequency L1 measurement. Currently, R18 only supports SSB-based L1-RSRP (Reference Signal Receiving Power) measurement.

[0120] L1 measurements support the reporting of semi-persistent and aperiodic data on PUSCH, as well as semi-persistent and periodic data on PUCCH.

[0121] Furthermore, in some embodiments, the relevant characteristics of the L1 measurement may also include the following aspects:

[0122] CSI-RS measurement, L1-SINR (Signal to Interference plus Noise Ratio) measurement, event-triggered L1 measurement reporting, and current L1 measurement enhancement.

[0123] For example, the LTM Cell Switch Command is generated by the S(source)-DU. In the LTM of the Intra-CU, the Source gNB-DU makes the Cell switch decision, and the S-DU makes the Cell Switch decision based on the L1 measurement results reported by the UE to determine the trigger for LTM access to the candidate target cell. Then the S-DU sends the Cell switch command to the UE.

[0124] In some embodiments, for event-based L1 measurement reporting, in order to reduce measurement reports and improve mobility robustness, Rel-19 supports event-triggered measurement reporting. Event-triggered measurement reporting can assist the NW side in selecting the target beam and / or cell to trigger early synchronization, or assist the network side in selecting the target cell and / or the corresponding beam when triggering LTM CellSwitch.

[0125] For example, a measurement report can be triggered when the measurement result of L1 meets the following event.

[0126] Event LTM2: The serving cell's beam becomes worse than the absolute threshold;

[0127] Event LTM3: The beam offset of the candidate cell is better than that of the serving cell;

[0128] Event LTM4: The candidate cell's beam becomes better than the absolute threshold;

[0129] Event LTM5: The serving cell's beam becomes worse than absolute threshold 1, while the candidate cell's beam becomes better than another absolute threshold 2.

[0130] For example, the serving cell's beam is the current beam, which is the beam indicated by the TCI state. The candidate cell's beam is any one or more beams configured in the candidate reference signal configuration (or measurement resource configuration).

[0131] For example, event-based L1 measurement reporting can be sent to the network via MAC CE messages.

[0132] For example, the configuration of measurement events is in the serving cell configuration, and the configuration of measurement events is associated with the configuration of measurement resources.

[0133] In some embodiments, the UE performs L1 measurement and reporting based on the LTM measurement and reporting configuration (also known as LTM measurement configuration) issued by the network side, and performs mobility based on one or more LTM candidates configured by the network side.

[0134] In some embodiments, the LTM measurement and reporting configuration can be collectively referred to as LTM measurement configuration, which specifically may include LTM measurement resource configuration and LTM reporting configuration.

[0135] The network side can update L1 measurement configurations and LTM candidates via RRC signaling, such as adding, modifying, and releasing these configurations. For example, LTM candidates can be added, modified, and released via ltm-CandidateToReleaseList-r18 and ltm-CandidateToAddModList-r18; L1 measurement resource configurations can be added, modified, and released via ltm-CSI-ResourceConfigToAddModList and ltm-CSI-ResourceConfigToReleaseList; and L1 measurement reporting configurations can be added, modified, and released via ltm-CSI-ReportConfigToAddModList and ltm-CSI-ReportConfigToReleaseList.

[0136] In some embodiments, considering the limited number of candidate configurations that a UE can simultaneously measure and decode, in non-DC (Dual Connection) scenarios, a UE can currently configure a maximum of 8 candidate cells simultaneously. Given the rapid mobility of the UE, candidate cells may change quickly, therefore the limitation of 8 candidate configurations is far from sufficient. If only 8 candidate configurations can be configured, the network side may need to frequently update the candidate configurations, resulting in significant air interface and signaling overhead on Xn. Therefore, the maximum number of configurable mobility configurations may be expanded in the future. Considering the limited measurement and decoding capabilities of the UE, it is necessary to limit the number of candidate cells that the UE can simultaneously measure.

[0137] Building on this, future mobility enhancements need to investigate configuration selection based on network-side signaling (e.g., MAC CE), using network-side signaling (e.g., MAC CE) to determine active candidate configurations and corresponding measurements.

[0138] For example, dynamic L1 measurement and reporting configuration changes. In the previously provided RRC configuration of UE L1 measurement and reporting LTM configuration, the necessary configurations and procedures for selecting configurations based on network-side signaling (e.g., MAC CE) are specified. It should be noted that this also applies to C-LTM.

[0139] In the future, MAC CE-based configuration selection will be used to implement Dynamic L1 measurement and reporting configuration change. Specific methods may include the following:

[0140] Option 1: Select (or activate / deactivate) the corresponding LTM candidate cell configuration via MAC CE, such as indicating the LTM candidate ID to activate or deactivate.

[0141] Option 2: Select (or activate / deactivate) the corresponding measurement configuration via MAC CE, such as measurement resource configuration and reporting configuration:

[0142] For example, the ltm-CSI-ResourceConfigId indicating activation or deactivation;

[0143] For example, the ltm-CSI-ReportConfigId indicates whether to activate or deactivate it.

[0144] Option 3: Select (or activate / deactivate) the corresponding measurement type via MAC CE, such as L1 measurement, L3 measurement, network-triggered L1 measurement, event-triggered L1 measurement, etc.

[0145] Based on the above analysis, on the one hand, to support dynamic L1 measurement and reporting configuration changes based on network-side signaling (e.g., MAC CE), activated or deactivated mobility configurations can be indicated via network-side signaling (e.g., MAC CE). These mobility configurations are pre-configured, for example, sent to the UE in advance via RRC signaling. Network devices can indicate the status of these pre-configured mobility configurations, such as activated or deactivated, via network-side signaling (e.g., MAC CE).

[0146] On the other hand, it is also necessary to support RRC signaling for updating these mobility configurations, such as adding, modifying, and releasing them. The problem then becomes how to determine the status of the updated mobility configuration.

[0147] Figure 2 This is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0148] In some embodiments, the communication method may be performed by the UE.

[0149] like Figure 2 As shown, the communication method may include the following steps:

[0150] In step S201, the UE receives the first information sent by the network device.

[0151] In some embodiments, the first information is used to indicate the update of mobility-related configurations and to indicate the status of the updated mobility-related configurations.

[0152] The status of the relevant configuration can be the initial state of the configuration information.

[0153] In some embodiments, updating mobility-related configurations may also be referred to as configuring mobility-related configurations, reconfiguring mobility-related configurations, adjusting mobility-related configurations, changing mobility-related configurations, etc. This disclosure does not limit the scope of the application.

[0154] Specifically, any information carrying mobility configuration related to the UE received from the network device falls within the scope of step S201.

[0155] In step S202, the UE determines the update of mobility-related configuration and the status of the updated mobility-related configuration based on the first information.

[0156] In some embodiments, updating mobility-related configurations includes at least one of the following:

[0157] Add mobility-related configurations;

[0158] Modify mobility-related configurations;

[0159] Release (or delete, remove, etc.) mobility-related configurations.

[0160] In some embodiments, the UE receives first information. For a certain mobility-related configuration #A in the first information, if the UE's current configuration already includes the mobility-related configuration #A, the UE can modify the mobility-related configuration #A in its current configuration according to the mobility-related configuration #A in the first information; otherwise (i.e., the current UE's configuration does not include the mobility-related configuration #A), the UE adds the mobility-related configuration #A.

[0161] In some embodiments, the state of the updated mobility-related configuration includes at least one of the following:

[0162] Activated;

[0163] Deactivate.

[0164] Activation can also be referred to as selection, being selected, or enabling, while deactivation can be referred to as not selected, not being selected, not enabling, disabling, or disabling.

[0165] According to embodiments of this disclosure, when the network device instructs the UE to update the mobility-related configuration via the first information, it can also instruct the status of the updated mobility-related configuration via the first information. Accordingly, when the UE determines that the mobility-related configuration has been updated, it can also determine the status of the updated mobility-related configuration so that the UE can reasonably perform subsequent operations based on the determined status.

[0166] In some embodiments, the mobility-related configuration includes at least one of the following:

[0167] Mobility configuration;

[0168] Mobility measurement resource allocation;

[0169] Mobility reporting configuration.

[0170] In some embodiments, mobility measurement resource configuration may also be referred to as mobility measurement object configuration, mobility measurement reference signal configuration, or any one or more of these.

[0171] In some embodiments, the mobility reporting configuration can also be a mobility measurement configuration.

[0172] In some embodiments, the mobility configuration includes at least one of the following:

[0173] L1-triggered mobility configuration;

[0174] L2-triggered mobility configuration;

[0175] L3-triggered mobility configuration;

[0176] Conditional Handover (CHO) configuration;

[0177] LTM configuration;

[0178] CLTM configuration.

[0179] The following embodiments mainly use mobility configuration including LTM configuration (or LTM candidate), such as LTM-Candidate, as an example to illustrate the technical solution of this disclosure.

[0180] For example, the measurement resource configuration in mobility-related configuration can be called mobility measurement resource configuration, such as LTM-CSI-ResourceConfig, and can be used to indicate the measurement resources of reference signals (such as CSI-RS, SSB, etc.).

[0181] For example, the reporting configuration (or uploading configuration) in mobility-related configurations can be called mobility reporting configuration, such as LTM-CSI-ReportConfig, which can indicate the resources used to send measurement results to network devices.

[0182] For example, the UE can obtain measurement results based on the measurement reference signal measured by the measurement resource, and then send the measurement results to the network device through the resource indicated by the report configuration. For example, the network device can determine whether to trigger the UE to perform mobility based on the mobility configuration based on the measurement results.

[0183] In some embodiments, when the mobility configuration includes LTM-Candidate, the first information may include IEs such as ltm-CandidateToAddModList-rx and ltm-CandidateToReleaseList-rx.

[0184] For example, ltm-CandidateToAddModList-rx is used to add and / or modify mobility configurations.

[0185] For example, ltm-CandidateToReleaseList-rx is used to release mobility configurations.

[0186] It should be noted that -rx in the preceding embodiments can refer to -r18, or include -r19, -r20, or other cases, and can also indicate the corresponding version for 6G. Furthermore, in some embodiments, the aforementioned IE can also be characterized by omitting the -rx field; this disclosure does not limit this.

[0187] In some embodiments, when the mobility measurement resource configuration includes LTM-CSI-ResourceConfig, the first information may include IEs such as ltm-CSI-ResourceConfigToAddModList and ltm-CSI-ResourceConfigToReleaseList.

[0188] For example, ltm-CSI-ResourceConfigToAddModList is used to add and / or modify mobility measurement resource configurations.

[0189] For example, ltm-CSI-ResourceConfigToReleaseList is used to release mobility measurement resource configurations.

[0190] In some embodiments, when the mobility reporting configuration includes LTM-CSI-ReportConfig, the first information may include IEs such as ltm-CSI-ReportConfigToAddModList and ltm-CSI-ReportConfigToReleaseList.

[0191] For example, ltm-CSI-ReportConfigToAddModList is used to add and / or modify mobility report configurations.

[0192] For example, ltm-CSI-ReportConfigToReleaseList is used to release mobility report configurations.

[0193] In some embodiments, the first information is carried in RRC signaling, or in a data packet. Of course, the first information is not limited to the above-described carrying methods and can also be carried in other ways, such as in a paging message.

[0194] In some embodiments, where the first information is carried in RRC signaling, the communication method further includes: notifying the lower layer of the status of the updated mobility-related configuration; and obtaining the status of the updated mobility-related configuration from the RRC layer through the lower layer.

[0195] For example, when the first information is carried in RRC signaling, the UE determines the update of mobility-related configuration and the status of the updated mobility-related configuration based on the first information.

[0196] Subsequent state-based operations are performed by lower layers, such as the MAC layer and PHY (physical) layer. Therefore, the lower layers can be notified of the updated mobility-related configuration status, or the lower layers can obtain the updated mobility-related configuration status from the RRC layer. This helps ensure that the lower layers are accurately aware of the updated mobility-related configuration status so that appropriate state-based operations can be performed subsequently.

[0197] In some embodiments, the RRC layer notifying the lower layer of the status of updated mobility-related configurations can be performed only when the update of mobility-related configurations is to add or modify mobility-related configurations, and not necessarily when other updates of mobility-related configurations (such as releasing mobility-related configurations).

[0198] In some embodiments, where the first information is carried in a data packet, the first information may be, for example, a MAC CE, and the data packet may be, for example, a MAC PDU (Protocol Data Unit). The MAC CE may indicate the status of an updated mobility-related configuration.

[0199] For example, in a separate architecture, the message corresponding to a data packet can be generated by the CU, while the MAC CE is generated by the DU. When the CU sends the message packet corresponding to the data packet to the DU, it can notify the DU of the updated mobility-related configuration status, or inform the DU to determine the updated mobility-related configuration status. The DU can then generate the MAC CE based on the updated mobility-related configuration status and send the MAC CE and the message corresponding to the data packet as a single data packet to the UE.

[0200] It should be noted that the function of the first information in indicating the update of mobility-related configuration can also be implemented based on MACCE, or based on other information in the data packet containing MAC CE. Alternatively, the function of the first information in indicating the update of mobility-related configuration can be implemented based on RRC signaling. That is, the first information can include two parts: one part is carried in RRC signaling to indicate the update of mobility-related configuration, and the other part is carried in the data packet to indicate the status of the updated mobility-related configuration.

[0201] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0202] When the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive.

[0203] When the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate whether the status of the added mobility-related configuration is active or deactivated.

[0204] When the first information is used to indicate the modification of mobility-related configuration, the first information is also used to indicate whether the modified mobility-related configuration is active or deactivated.

[0205] When the first information is used to indicate a modification to mobility-related configurations, the first information is also used to indicate that the state of the modified mobility-related configurations remains unchanged.

[0206] In some embodiments, when the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive; or, when the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are active.

[0207] In this embodiment, the first information does not necessarily need to carry special information to indicate the status of the updated mobility-related configuration. Instead, it can only carry information to indicate the release of the mobility-related configuration. When the UE determines that a certain mobility-related configuration is released based on the first information, it can also determine that the first information indicates that the status of the mobility-related configuration is deactivated. Therefore, it is beneficial to save the overhead of the first information.

[0208] In other words, when the UE receives the first information, which indicates the release of mobility-related configurations, the UE will deactivate the released mobility configurations. In this case, no default indication information is required, which is the default UE behavior specified by the protocol.

[0209] Taking the case where the first information is used to indicate the release of mobility-related configurations, and the first information is also used to indicate that the status of the released mobility-related configurations is deactivated as an example.

[0210] For example, mobility configurations include LTM-Candidate, and the first information can be released via the ltm-CandidateToReleaseList-rx instruction.

[0211] In this case, for each LTM-CandidateId in ltm-CandidateToReleaseList-rx, the UE can determine to delete the candidate configuration corresponding to the LTM-CandidateId.

[0212] In addition, since the first information is also used to indicate that the status of the released mobility configuration is deactivated, the UE can also determine that the status of the candidate configuration corresponding to LTM-CandidateId is deactivated and notify the lower layer that the candidate configuration corresponding to LTM-CandidateId is deactivated.

[0213] For example, mobility measurement resource configuration includes LTM-CSI-ResourceConfig, and the first information can be released by instructing ltm-CSI-ResourceConfigToReleaseList to release the mobility measurement configuration.

[0214] In this case, for each LTM-CSI-ResourceConfigId in ltm-CSI-ResourceConfigToReleaseList, the UE can determine to delete the measurement resource configuration corresponding to the LTM-CSI-ResourceConfigId.

[0215] In addition, since the first information is also used to indicate that the status of the released mobility measurement resource configuration is deactivated, the UE can also determine that the status of the measurement resource configuration corresponding to LTM-CSI-ResourceConfigId is deactivated and notify the lower layer that the measurement resource configuration corresponding to LTM-CSI-ResourceConfigId is deactivated.

[0216] For example, the mobility reporting configuration includes LTM-CSI-ReportConfig, and the first information can be released by the ltm-CSI-ResourceConfigToReleaseList instruction.

[0217] In this scenario, for each LTM-CSI-ReportConfigId in ltm-CSI-ReportConfigToReleaseList, the UE can determine whether to delete the report configuration corresponding to the LTM-CSI-ReportConfigId.

[0218] In addition, since the first information is also used to indicate that the status of the released mobility report configuration is deactivated, the UE can also determine that the status of the report configuration corresponding to LTM-CSI-ReportConfigId is deactivated and notify the lower layer that the report configuration corresponding to LTM-CSI-ReportConfigId is deactivated.

[0219] In some embodiments, when the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate that the status of the added mobility-related configuration is active; or, when the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate that the status of the added mobility-related configuration is deactivated.

[0220] In this embodiment, the first information does not necessarily need to carry special information to indicate the status of the updated mobility-related configuration. Instead, it can only carry information to indicate the addition of mobility-related configuration. When the UE determines to add a certain mobility-related configuration based on the first information, it can also determine that the first information indicates that the status of the mobility-related configuration is active, or determine that the first information indicates that the status of the mobility-related configuration is deactivated. This helps to save the overhead of the first information.

[0221] In other words, if the UE receives the first information, which indicates the addition of mobility-related configuration, then the UE either activates the added mobility configuration or deactivates it. In this case, a default indication is not required; this is the default UE behavior defined by the protocol.

[0222] It should be noted that adding and modifying mobility-related configurations can be done in a linked manner. For example, when adding a mobility-related configuration, if the identifier of the added configuration is the same as the identifier of an existing mobility-related configuration of the UE, the existing mobility-related configuration of the UE can be modified based on the added configuration; if the identifier of the added configuration is different from the identifier of an existing mobility-related configuration of the UE, the added configuration can be added to the UE's mobility-related configuration.

[0223] In some embodiments, the existing mobility-related configuration of the UE is the mobility-related configuration in the current UE configuration only when the first information is received, or before the first information is received.

[0224] Take mobility location in mobility-related configuration as an example.

[0225] For example, mobility configurations include LTM-Candidate, and the first information can be added via the ltm-CandidateToAddModList-rx instruction.

[0226] In this case, the UE can determine whether each LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration.

[0227] When a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration, the UE can update its existing candidate configuration based on the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx; when a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx does not exist in the UE's existing candidate configuration, the UE can add the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx to its candidate configuration and notify the lower layer whether the candidate configuration corresponding to the LTM-CandidateId is activated or deactivated.

[0228] Alternatively, if an LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration, the UE can modify its existing candidate configuration based on the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx, and notify the lower layer that the candidate configuration corresponding to the LTM-CandidateId is activated or deactivated; if an LTM-CandidateId in ltm-CandidateToReleaseList-rx does not exist in the UE's existing candidate configuration, the UE can add the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx to its candidate configuration, and notify the lower layer that the candidate configuration corresponding to the LTM-CandidateId is activated or deactivated.

[0229] In some embodiments, when the first information is used to indicate modification of mobility-related configuration, the first information is also used to indicate that the modified mobility-related configuration is in an active state; or, when the first information is used to indicate modification of mobility-related configuration, the first information is also used to indicate that the modified mobility-related configuration is inactive.

[0230] In this embodiment, the first information does not necessarily need to carry special information to indicate the status of the updated mobility-related configuration. Instead, it can only carry information to indicate the modification of the mobility-related configuration. When the UE determines to modify a certain mobility-related configuration based on the first information, it can also determine that the first information indicates that the status of the mobility-related configuration is active, or determine that the first information indicates that the status of the mobility-related configuration is deactivated. This helps to save the overhead of the first information.

[0231] In other words, if the UE receives the first information, which indicates that mobility-related configurations should be modified, then the UE either activates the modified mobility configuration or deactivates the modified mobility configuration. In this case, a default indication is not required; this is the default UE behavior defined by the protocol.

[0232] Take mobility location in mobility-related configuration as an example.

[0233] For example, mobility configurations include LTM-Candidate, and the first information can be added via the ltm-CandidateToAddModList-rx instruction.

[0234] In this case, the UE can determine whether each LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration.

[0235] When a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration, the UE can modify the UE's existing candidate configuration according to the candidate configuration corresponding to LTM-CandidateId in ltm-CandidateToReleaseList-rx, and notify the lower layer whether the candidate configuration corresponding to LTM-CandidateId is activated or deactivated.

[0236] If a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx does not exist in the UE's existing candidate configurations, the UE can add the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx to the UE's candidate configurations and notify the lower layer that the candidate configuration corresponding to the LTM-CandidateId is activated or deactivated.

[0237] In some embodiments, when the first information is used to indicate modification of mobility-related configuration, the first information is also used to indicate that the state of the modified mobility-related configuration remains unchanged (e.g., remains the same as before the modification); or, when the first information is used to indicate modification of mobility-related configuration, the first information is also used to indicate that the state of the modified mobility-related configuration remains unchanged (e.g., remains the same as before the modification).

[0238] In this embodiment, the first information does not necessarily need to carry special information to indicate the status of the updated mobility-related configuration. Instead, it can only carry information to indicate the modification of the mobility-related configuration. When the UE determines to modify a certain mobility-related configuration based on the first information, it can also determine that the first information indicates that the status of the mobility-related configuration remains unchanged. Therefore, it is beneficial to save the overhead of the first information.

[0239] In other words, if the UE receives the first information indicating a modification to mobility-related configuration, the UE determines that the state of the modified mobility configuration remains unchanged. For example, if the state was active before the modification, the UE determines that the state will remain active after the modification; if the state was deactivated before the modification, the UE determines that the state will remain deactivated after the modification. In this case, a default indication is not required; this is the default UE behavior defined by the protocol.

[0240] Take mobility location in mobility-related configuration as an example.

[0241] For example, mobility configurations include LTM-Candidate, and the first information can be added via the ltm-CandidateToAddModList-rx instruction.

[0242] In this case, the UE can determine whether each LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration.

[0243] When a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx exists in the UE's existing candidate configuration, the UE can modify the UE's existing candidate configuration according to the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx;

[0244] If a certain LTM-CandidateId in ltm-CandidateToReleaseList-rx does not exist in the UE's existing candidate configuration, the UE can add the candidate configuration corresponding to the LTM-CandidateId in ltm-CandidateToReleaseList-rx to the UE's candidate configuration and notify the lower layer that the candidate configuration corresponding to the LTM-CandidateId remains unchanged.

[0245] In some embodiments, the first information may include dedicated information specifically used to indicate the status of the updated mobility-related configuration. For example, the dedicated information may be referred to as sub-information, which is used to indicate the status of the updated mobility-related configuration.

[0246] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0247] If the field corresponding to the sub-information exists, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated;

[0248] If the field corresponding to the sub-information does not exist, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0249] When the value of the field corresponding to the sub-information is the first value, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0250] When the value of the field corresponding to the sub-information is the second value, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated.

[0251] In some embodiments, when the first information contains sub-information indicating the status of the updated mobility-related configuration, the UE may determine the status of the updated mobility-related configuration based on whether a field corresponding to the sub-information exists in the first information; or, the UE may determine the status of the updated mobility-related configuration based on the indication value of the field corresponding to the sub-information.

[0252] Taking the example of the UE determining the status of the updated mobility-related configuration based on whether the corresponding field of the sub-information exists in the first information.

[0253] For example, if the field corresponding to the sub-information does not exist in the first information, the UE determines that the updated mobility-related configuration is active; if the field corresponding to the sub-information exists in the first information, the UE determines that the updated mobility-related configuration is deactivated.

[0254] Alternatively, if the field corresponding to the sub-information does not exist in the first information, the UE determines that the status of the updated mobility-related configuration is deactivated; if the field corresponding to the sub-information exists in the first information, the UE determines that the status of the updated mobility-related configuration is activated.

[0255] Taking the example of the UE determining the status of the updated mobility-related configuration based on the indication value of the corresponding field of the sub-information.

[0256] For example, when the field corresponding to the sub-information indicates the first value, the UE determines that the updated mobility-related configuration is active; when the field corresponding to the sub-information indicates the second value, the UE determines that the updated mobility-related configuration is inactive.

[0257] For example, if the first value is 0, the second value can be 1, or if the first value is 1, the second value can be 0. Of course, the first and second values ​​are not limited to 0 and 1, and can include other values, which is not limited in this disclosure.

[0258] For example, if the first value is true, the second value can be false, or if the first value is false, the second value can be true.

[0259] For example, if the first value is activated, the second value can be deactivated, or if the first value is deactivated, the second value can be activated.

[0260] In some embodiments, when the first information is carried in RRC signaling, the sub-information in the first information may be located in the mobility-related configuration carried in the RRC signaling.

[0261] For example, when a network device instructs a UE to update its mobility-related configuration via RRC signaling, the sub-information in the first information may be located in the mobility-related configuration updated by the RRC signaling.

[0262] For example, if sub-information is used to indicate the status of mobility configuration, then the sub-information can be located in the updated mobility configuration, such as in the updated LTM-Candidate.

[0263] For example, if sub-information is used to indicate the status of mobility measurement resource configuration, then the sub-information can be located in the updated mobility measurement resource configuration, such as in the updated LTM-CSI-ResourceConfig.

[0264] For example, if sub-information is used to indicate the status of mobility reporting configuration, then the sub-information can be located in the updated mobility reporting configuration, such as in the updated LTM-CSI-ReportConfig.

[0265] For example, when a network device instructs a UE to update its mobility-related configuration via RRC signaling, the sub-information in the first information can be associated with the updated mobility-related configuration indicated by the RRC signaling.

[0266] For example, if sub-information is used to indicate the status of mobility configuration, then the sub-information can be associated with an updated mobility configuration, such as an updated LTM-Candidate.

[0267] For example, if sub-information is used to indicate the status of mobility measurement resource configuration, then the sub-information can be associated with an updated mobility measurement resource configuration, such as an updated LTM-CSI-ResourceConfig.

[0268] For example, if sub-information is used to indicate the status of mobility reporting configuration, then the sub-information can be associated with an updated mobility reporting configuration, such as an updated LTM-CSI-ReportConfig.

[0269] In some embodiments, the communication method further includes: switching from a first cell to a second cell; and determining the state of an updated mobility-related configuration based on first information received in the second cell.

[0270] For example, mobility-related configurations support subsequent mobility. In this case, the mobility-related configurations stored in the UE remain available after the UE performs mobility.

[0271] However, since the UE performs mobility operations, such as switching from the first cell to the second cell, and the state of mobility-related configurations can be different in different cells, the UE needs to redetermine the state of mobility-related configurations.

[0272] For example, for an updated mobility configuration, the UE needs to receive first information in the second cell after handover, and then determine the status of the updated mobility-related configuration based on the first information received in the second cell.

[0273] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S202. For example, step S201 may be implemented as a standalone embodiment, step S202 may be implemented as a standalone embodiment, and step S201+S202 may be implemented as a standalone embodiment, but is not limited thereto.

[0274] In some embodiments, steps S201 and S202 may be performed in an alternate order or simultaneously.

[0275] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0276] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0277] Figure 3 This is a schematic flowchart illustrating another communication method according to embodiments of the present disclosure.

[0278] For example, the cell where the UE is located before performing mobility is denoted as the first cell. In step S301, the UE can receive the first information sent by the first cell.

[0279] For example, the first information can be used to indicate the status of the updated mobility-related configuration in at least one cell (e.g., a candidate cell in an LTM scenario).

[0280] In some embodiments, the first information can be used to configure mobility.

[0281] Before performing mobility, the UE is in the first cell. In step S302, the updated mobility configuration in the first cell can be determined based on the first information. In step S303, the UE can perform mobility, for example, by handing over to a candidate cell, which can be called the second cell.

[0282] In some cases, the UE can trigger a handover to a second cell based on a mobility command sent by the network side.

[0283] In some cases, the UE can trigger a mobility procedure to hand over to a second cell based on conditions. When the UE meets the corresponding execution conditions, the UE performs the mobility procedure to hand over to the second cell.

[0284] After the UE performs mobility, it is in the second cell. Since the first information also indicates the status of the updated mobility configuration in the second cell, in step S304, the UE can determine the status of the updated mobility configuration in the second cell based on the first information.

[0285] For example, the first information can be sent to the UE by the network device corresponding to the first cell, such as gNB, or gNB-CU and / or gNB-DU under the separate architecture.

[0286] In some embodiments, this first information is included in the candidate configuration corresponding to the second cell.

[0287] For example, during the mobility preparation process, the network device corresponding to the first cell sends a mobility request to the network device corresponding to the second cell. The network device corresponding to the second cell generates a candidate configuration containing first information, which corresponds to the second cell. The network device corresponding to the second cell then sends this candidate configuration containing the first information to the network device corresponding to the first cell, which in turn sends it to the UE.

[0288] In other words, the first information, that is, the first information included in the candidate configuration corresponding to the second cell, is determined by the network device corresponding to the second cell. In some embodiments, the network device corresponding to the second cell may include any one or more of the following: target base station, candidate base station, target CU, candidate CU, target DU, and candidate DU.

[0289] For example, taking the mobility performed by the UE, including LTM, during the LTM configuration preparation phase, the candidate network device can determine (or predict) the state of the mobility configuration when the UE accesses the corresponding candidate cell. Then, it can carry the first information in the generated mobility-related configuration. When the UE performs mobility and applies the corresponding mobility-related configuration, it can determine the state of the mobility-related configuration based on the first information. For example, if the mobility-related configuration does not contain the first information, it can be determined that the mobility-related configuration is active. If the mobility-related configuration contains the first information, it can be determined that the mobility-related configuration is deactivated.

[0290] In some embodiments, a mobility-related configuration may carry first information to indicate the status of other mobility-related configurations.

[0291] Example 1:

[0292] Taking four mobility configurations as an example, namely LTM-CandidateId=1, LTM-CandidateId=2, LTM-CandidateId=3, and LTM-CandidateId=4. The information structure for LTM-CandidateId=1 can be shown in Table 1 below:

[0293] ltm-CandidateId=2 Contains first information ltm-CandidateId=3 Contains first information ltm-CandidateId=4

[0294] Table 1

[0295] When a UE performs mobility operations and switches to the cell corresponding to LTM-CandidateId=1, based on the information structure shown in Table 1, it can be determined that the two mobility configurations LTM-CandidateId=2 and LTM-CandidateId=3 contain the first information, so they can be determined to be deactivated. However, the mobility configuration LTM-CandidateId=4 does not contain the first information, so it can be determined to be activated. Therefore, the UE can perform mobility operations based on LTM-CandidateId=4.

[0296] Example 2:

[0297] Taking four mobility measurement resource configurations as an example, namely LTM-CSI-ResourceConfig=1, LTM-CSI-ResourceConfig=2, LTM-CSI-ResourceConfig=3, and LTM-CSI-ResourceConfig=4. For instance, these four mobility measurement resource configurations are located in LTM-Candidate with LTM-Candidate Id=1. The information structure of LTM-Candidate with LTM-Candidate Id=1 can be shown in Table 2 below:

[0298] ltm-CSI-ResourceConfigId=1 Contains first information ltm-CSI-ResourceConfigId=2 ltm-CSI-ResourceConfigId=3 Contains first information ltm-CSI-ResourceConfigId=4

[0299] Table 2

[0300] When a UE performs mobility and switches to the cell corresponding to LTM-CSI-ResourceConfig=1, based on the information structure shown in Table 2, it can be determined that the two mobility configurations LTM-CSI-ResourceConfigId=1 and LTM-CSI-ResourceConfigId=3 contain the first information, so they can be determined to be deactivated. However, the two mobility configurations LTM-CSI-ResourceConfigId=2 and LTM-CSI-ResourceConfigId=4 do not contain the first information, so they can be determined to be activated. Therefore, the UE can perform measurement operations based on LTM-CSI-ResourceConfigId=2 and LTM-CSI-ResourceConfigId=4.

[0301] The above embodiments mainly use mobility including LTM as an example to illustrate the technical solution of this disclosure. However, the mobility applicable to the embodiments of this disclosure is not limited to LTM, but may also include other mobility, such as L1 triggered mobility, L2 triggered mobility, L3 triggered mobility, CHO, etc.

[0302] For example, for L1-triggered mobility, the L1 measurement involved can also be called LTM measurement, beam measurement, MIMO (Multiple-Input Multiple-Output) measurement, CSI measurement, TCI state measurement, LTM L1 measurement, etc.

[0303] For example, for L3-triggered mobility, the L3 measurements involved can also be called RRM (Radio Resource Management) measurements, cell measurements, etc.

[0304] The communication method involved in the embodiments of this disclosure may include at least one of steps S301 to S304. For example, step S301 may be implemented as an independent embodiment, step S302 may be implemented as an independent embodiment, step S303 may be implemented as an independent embodiment, step S304 may be implemented as an independent embodiment, step S301+S302 may be implemented as an independent embodiment, and step S303+S304 may be implemented as an independent embodiment, but is not limited thereto.

[0305] In some embodiments, steps S301, S302, S303, and S304 may be performed in an interchangeable order or simultaneously.

[0306] In some embodiments, step S301 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0307] In some embodiments, step S302 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0308] In some embodiments, step S303 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0309] In some embodiments, step S304 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0310] In some embodiments, any one or more steps in steps S301 to S304 may be combined in any order as an independent embodiment, but are not limited thereto.

[0311] In some embodiments, see Figure 2 Other optional implementation methods described before or after the corresponding instruction manual.

[0312] The technical solutions of this disclosure will be illustrated by several further embodiments below.

[0313] In some embodiments, the UE receives RRC configuration information sent by the network side, which is used to update mobility-related configurations (e.g., measurement configuration and / or LTM candidate configurations). For the updated configuration, the UE needs to determine whether it is active or deactivated, and then perform measurement and / or LTM-triggered related operations based on this.

[0314] The network side carries indication information in the RRC configuration information, which is used to determine whether the updated configuration is active or deactivated.

[0315] To ensure configuration compatibility, if the RRC configuration contains the aforementioned indication information, the corresponding mobility-related configuration is deactivated; otherwise, it is activated.

[0316] For example, the IE in RRC signaling such as LTM-Candidate, LTM-CSI-ResourceConfig, and LTM-CSI-ReportConfig can contain indication information. When the UE receives the corresponding configuration, it determines that the current state is deactivated based on the indication information in the above configuration. Then the UE does not need to perform measurement and corresponding mobility operations on these configurations.

[0317] Since the indication information is carried in the RRC signaling, when the UE's RRC layer receives an update of at least one of LTM-Candidate, LTM-CSI-ResourceConfig, and LTM-CSI-ReportConfig, the RRC layer can notify the lower layer (e.g., MAC layer, physical layer) that the status of at least one of the corresponding LTM-Candidate, LTM-CSI-ResourceConfig, and LTM-CSI-ReportConfig is active or deactivated, and can also notify the lower layer that the corresponding configuration has been updated.

[0318] The above indication information determines the status (activated or deactivated) of newly added or modified configuration information. This can be used as the initial status, and the network side can still indicate the status of the configuration information via MAC CE later. If a MAC CE indicating the configuration information is received, the status indicated in the MAC CE shall prevail, and the indication information in the RRC configuration shall be ignored.

[0319] In some embodiments, the UE receives an RRC message sent by the network side. The RRC message includes first information, which is used to update a first configuration (e.g., mobility-related configuration). Updating the first configuration includes adding, modifying, or releasing one or more first configurations.

[0320] In some embodiments, the first configuration can be any one or more of LTM-Candidate, LTM measurement configuration, LTM measurement resource configuration (LTM-CSI-ResourceConfig), and LTM measurement reporting configuration (LTM-CSI-ReportConfig).

[0321] The corresponding first information can be ltm-CandidateToReleaseList-r18 and ltm-CandidateToAddModList-r18 to add, modify and release LTM candidates;

[0322] The ltm-CSI-ResourceConfigToAddModList and ltm-CSI-ResourceConfigToReleaseList are used to add, modify, and release LTM measurement resource configurations.

[0323] The ltm-CSI-ReportConfigToAddModList and ltm-CSI-ReportConfigToReleaseList are used to add, modify, and release LTM measurement reporting configurations.

[0324] In some embodiments, when the UE receives first information, the first information is used to release (or delete, remove, etc.) the first configuration, the UE releases the first configuration, and the state of the first configuration is deactivated.

[0325] For example, the first configuration is LTM candidate; LTM measurement resource configuration; LTM reporting configuration (where lowerLayer refers to the MAC layer and / or physical layer).

[0326] For example, the RRC layer notifies the MAC layer and / or the physical layer to deactivate the first configuration, as follows:

[0327] Example 1, the UE should:

[0328] 1> For each ltmCanditateId value contained in ltm CandidateToReleaseList in the current UE configuration:

[0329] 2> Delete the corresponding LTM candidate;

[0330] 2> Notify the lower-level LTM candidates that the LTM CandidateId has been deactivated.

[0331] Example 2, the UE should:

[0332] 1> For each ltm CSI ResourcesConfigId value included in ltm CSIResourceConfigToReleaseList, which is part of the current UE configuration:

[0333] 2> Notify the lower-level LTM CSIResourceConfig that it has been deactivated for LTM CSIResourceConfigId.

[0334] Example 3, the UE should:

[0335] 1> For each ltm CSI Report ConfigId value included in ltm CSI ReportConfigToReleaseList, which is part of the current UE configuration:

[0336] 2> Notify the lower-level LTM CSI ReportConfig that it has been deactivated for LTM CSI ReportConfigId.

[0337] In some embodiments, the MAC layer and / or the physical layer may obtain the latest configuration from the RRC layer, determine that the first configuration has been released, and thus determine that the corresponding configuration is deactivated.

[0338] In some embodiments, when the UE receives first information, which is used to add or modify a first configuration, the UE determines the state of the first configuration based on any one or more of the following methods:

[0339] Case 1: For the first added configuration, its initial state is either deactivated or activated by default; that is, when the UE receives the first information (or applies the first information to update the configuration), if the first configuration is the added configuration, then it is deactivated / activated.

[0340] Scenario 2: If the first configuration is modified, its status is deactivated or activated by default; that is, when the UE receives the first information (or applies the first information to update the configuration), if the first configuration is modified through this first information, it will be deactivated / activated.

[0341] Case 3: If the first configuration is modified, its state remains unchanged; that is, when the UE receives the first information (or applies the first information to update the configuration), if the first configuration is modified through this first information, it will still maintain its original state, that is, the state before the modification.

[0342] For scenario 3, the UE only needs to maintain the original state of the first configuration.

[0343] For scenarios 1 and 2, confirmation of configuration activation or deactivation can be determined at the RRC layer, and then the RRC layer notifies the lower layer, or the lower layer determines it based on changes in the configuration. In some embodiments, the lower layer can be the MAC layer (or MAC entity) and / or the physical layer (or physical layer entity).

[0344] For cases 1 and 3:

[0345] 1> For each ltm CanditateId value contained in ltm CandidateToAddModList:

[0346] 2> If the current UE configuration contains LTM candidates with an LTM CandidateId value:

[0347] 3> Reconfigure the corresponding LTM candidates based on the received LTM candidates;

[0348] 2> Otherwise:

[0349] 3> Add the received LTM candidate;

[0350] 3> Notify lower-level LTM candidates that they have been activated or deactivated for LTM CandidateId.

[0351] For cases 1 and 2:

[0352] 1> For each ltm CanditateId value contained in ltm CandidateToAddModList:

[0353] 2> If the current UE configuration contains LTM candidates with an LTM CandidateId value:

[0354] 3> Reconfigure the corresponding LTM candidates based on the received LTM candidates;

[0355] 2> Otherwise:

[0356] 3> Add the received LTM candidate;

[0357] 2> Notify lower-level LTM candidates that they have been activated or deactivated for LTM CandidateId.

[0358] Among them, "2>If the current UE configuration contains LTM candidates with LTM CandidateId values:" can indicate that the first configuration should be modified; "2>Otherwise:" indicates that the first configuration should be added.

[0359] In other words, when the UE receives the first information, if the current UE's configuration includes the first configuration A, then the first configuration A is modified; otherwise (i.e., the current UE's configuration does not include the first configuration A), then the first configuration A is added.

[0360] In some embodiments, for a modified first configuration and / or an added first configuration, the first configuration includes the indication information, which is used to indicate whether its state is active and / or deactivated.

[0361] In some embodiments, the first configuration is activated if it contains the indication information; otherwise, it is deactivated.

[0362] In some embodiments, the first configuration is deactivated if it contains the indication information; otherwise, it is activated.

[0363] In some embodiments, the first configuration is active if the value of the indication information in the first configuration is a first specific value (true, active, 1, etc.). It is deactivated if the value is a second specific value (false, deactivated, 0, etc.).

[0364] In some embodiments, the location of the indication information differs for different first configurations, specifically including one or more of the following:

[0365] The first configuration is an LTM candidate, and the indication information can be included in the corresponding LTM-Candidate, which is added and / or modified.

[0366] The first configuration is the LTM measurement resource configuration, and the indication information can be included in the corresponding LTM-CSI-ResourceConfig, which is added and / or modified.

[0367] The first configuration is the LTM reporting configuration, and the indication information can be included in the corresponding LTM-CSI-ReportConfig, which is added and / or modified.

[0368] In some embodiments, the confirmation of configuration activation or deactivation can be determined at the RRC layer, and then the RRC layer notifies the lower layer, or the lower layer determines it based on changes in the configuration. Specifically, the following scenarios can be considered:

[0369] The RRC layer can determine whether the first configuration is active or inactive based on the indication information, and then notify the lowerlayer MAC layer and / or physical layer.

[0370] The lowerlayer MAC / physical layer obtains the UE's current configuration from the RRC layer, determines whether the first configuration is newly added or modified, and determines whether the first configuration is active or deactivated based on the indication information;

[0371] If the RRC layer determines that the first configuration is newly added or has been modified, it notifies the lower layer MAC / physical layer to initiate a state update (state determination process) to determine whether the first configuration is active or deactivated based on the indication information.

[0372] In some embodiments, the network side carries a first MAC CE in the data packet that sends the first message. The first MAC CE indicates the status of the modified first configuration and / or the added first configuration. When the UE receives this data packet, it determines the status of the first configuration based on the first MAC CE.

[0373] Considering that the first message is generated by the CU and the first MAC CE is generated by the DU, the CU needs to inform the DU of the status of the first configuration when sending the first message (or the CU notifies the DU of the status of the first configuration). Based on this, the DU generates the first MAC CE and sends the first message and the first MAC CE to the UE through the same data packet. This data packet can refer to the same MACPDU.

[0374] In some embodiments, mobility configuration supports Subsequent Mobility, meaning that after mobility is performed, the previously configured mobility configuration and / or related measurement configuration can continue to be used. Therefore, after the UE performs mobility and applies the target cell configuration, the UE needs to redetermine the state of the previous mobility configuration because the serving cell has changed.

[0375] During the LTM configuration preparation phase, candidate base stations (e.g., candidate gNB-CU and / or candidate gNB-DU) determine the first configuration to be activated / deactivated when the UE accesses the corresponding candidate cell, and include indication information in the generated candidate configuration corresponding to the candidate cell. This indication information is used to activate and / or deactivate the first configuration when the UE switches to this candidate cell. When the UE performs an LTM Cell Switch, accesses the target cell (one of the candidate cells), and applies the candidate configuration corresponding to the target cell, the state of the first configuration is determined based on the indication information in the candidate configuration.

[0376] If the first configuration contains the indication information, then the first configuration is deactivated. If it does not contain it, then it is activated. For example, specific embodiments can be found in Tables 1 and 2, which will not be repeated here.

[0377] In some embodiments, mobility configuration can be configured in two parts. During the preparation process, the target base station only provides the necessary resources, such as Preamble and / or GBR (Guaranteed Bit Rate) resources for early uplink synchronization, and then the source base station sends the configuration corresponding to these necessary resources to the UE via RRC messages.

[0378] For example, GBR resources refer to Guaranteed Bit Rate resources, which include a set of network resources that are pre-allocated and locked to ensure that service data streams with GBR requirements can be continuously transmitted at the minimum guaranteed rate.

[0379] In some embodiments, the network side can provide the UE with more dynamic configurations through handover commands (such as LTM Cell Switch Command), such as configurations related to dynamic scheduling, which may include at least one of the following: C-RNTI (Cell Radio Network Temporary Identifier), SR (Scheduling Request), SRS (Sounding Reference Signal), and Preamble (e.g., for CFRA).

[0380] In some embodiments, the network side can provide the UE with more dynamic configurations through dynamic configuration signaling (e.g., MAC CE), such as configurations related to dynamic scheduling, which may include at least one of the following: C-RNTI, SR, SRS, Preamble (for CFRA).

[0381] It should be noted that:

[0382] The embodiments disclosed herein are also applicable to other mobility operations besides LTM, such as mobility triggered by other network sides.

[0383] In other words, LTM in the description can be replaced by the first mobility operation, which refers to the network side pre-configuring one or more candidate configurations and / or related measurements, synchronization configurations, etc. for the UE, and then the network side sends a message to trigger the handover, wherein the handover target configuration is one of the candidate configurations.

[0384] The first mobility operation can be L3 handover, LTM, etc., and this disclosure does not limit the name of the first mobility.

[0385] The measurements involved can be any one or more of L1 and L3 measurements (LTML1 measurement is mainly used as an example in this embodiment).

[0386] For example, L1 measurement can also be referred to as one or more of the following: LTM measurement, beam measurement, MIMO measurement, CSI measurement, TCI state measurement, LTM L1 measurement, etc.

[0387] For example, L3 measurement can also be referred to as one or more of the following: RRM measurement, cell measurement, etc.

[0388] In this disclosure, the states are described as activated and / or deactivated, or as configuration selected and / or not selected, configuration enabled and / or not enabled, etc. In this invention, activating and / or deactivating configurations can also be described as selecting and / or not selecting configurations, enabling / disabling configurations, etc. This disclosure does not limit the terminology used. Specifically, activated configuration information refers to any one or more operations, such as measurement and mobility, that the UE needs to perform based on the relevant configuration information. Deactivated configurations refer to configurations for which the UE does not need to perform any related operations, such as mobility operations, measurement, etc.

[0389] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0390] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.

[0391] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0392] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0393] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0394] In some embodiments, the terms “radio”, “wireless”, “radioaccess network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0395] In some embodiments, the terms "search space", "search spaceset", "search space configuration", "search spaceset configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0396] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0397] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0398] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0399] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0400] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0401] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0402] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0403] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0404] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0405] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0406] Corresponding to the embodiments of the communication methods described above, this disclosure also provides embodiments of communication devices.

[0407] Figure 4A This is a schematic block diagram illustrating a communication device according to embodiments of the present disclosure. For example, the communication device may be configured in and / or applied to a UE.

[0408] In some embodiments, the UE is configured to perform the method of any one of the optional embodiments of the first aspect.

[0409] like Figure 4A As shown, the communication device includes: a receiving module 301 and a processing module 302.

[0410] In some embodiments, the receiving module is configured to receive first information sent by a network device, wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

[0411] In some embodiments, updating mobility-related configurations includes at least one of the following: adding mobility-related configurations; modifying mobility-related configurations; or releasing mobility-related configurations.

[0412] In some embodiments, the state includes at least one of the following: activated; deactivated.

[0413] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0414] When the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive.

[0415] When the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate whether the status of the added mobility-related configuration is active or deactivated.

[0416] When the first information is used to indicate the modification of mobility-related configuration, the first information is also used to indicate whether the modified mobility-related configuration is active or deactivated.

[0417] When the first information is used to indicate a modification to mobility-related configurations, the first information is also used to indicate that the state of the modified mobility-related configurations remains unchanged.

[0418] In some embodiments, the first information includes sub-information that indicates the status of updated mobility-related configurations.

[0419] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0420] If the field corresponding to the sub-information exists, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated;

[0421] If the field corresponding to the sub-information does not exist, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0422] When the value of the field corresponding to the sub-information is the first value, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0423] When the value of the field corresponding to the sub-information is the second value, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated.

[0424] In some embodiments, the first information is carried in Radio Resource Control (RRC) signaling, or the first information is carried in a data packet.

[0425] In some embodiments, when the first information is carried in RRC signaling, the processing module is configured to at least one of the following: notify the lower layer of the status of the updated mobility-related configuration; or obtain the status of the updated mobility-related configuration from the RRC layer through the lower layer.

[0426] In some embodiments, the processing module is configured to switch from a first cell to a second cell and determine the state of the updated mobility-related configuration based on first information received in the second cell.

[0427] In some embodiments, the mobility-related configuration includes at least one of the following: mobility configuration; mobility measurement resource configuration; mobility reporting configuration.

[0428] In some embodiments, the mobility configuration includes at least one of the following: L1-triggered mobility configuration; L2-triggered mobility configuration; L3-triggered mobility configuration; conditional switching (CHO) configuration; layer 1 and / or layer 2-triggered mobility LTM configuration; and conditional LTM configuration.

[0429] Figure 4B This is a schematic block diagram illustrating a communication device according to embodiments of the present disclosure. For example, the communication device may be configured in and / or applied to a network device.

[0430] In some embodiments, the network device is configured to perform the method of any one of the optional embodiments of the first aspect.

[0431] like Figure 4B As shown, the communication device includes: a transmitting module 401.

[0432] In some embodiments, the sending module is configured to send first information to a user equipment (UE), wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

[0433] In some embodiments, updating mobility-related configurations includes at least one of the following: adding mobility-related configurations; modifying mobility-related configurations; or releasing mobility-related configurations.

[0434] In some embodiments, the state includes at least one of the following: activated; deactivated.

[0435] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0436] When the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive.

[0437] When the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate whether the status of the added mobility-related configuration is active or deactivated.

[0438] When the first information is used to indicate the modification of mobility-related configuration, the first information is also used to indicate whether the modified mobility-related configuration is active or deactivated.

[0439] When the first information is used to indicate a modification to mobility-related configurations, the first information is also used to indicate that the state of the modified mobility-related configurations remains unchanged.

[0440] In some embodiments, the first information includes sub-information that indicates the status of updated mobility-related configurations.

[0441] In some embodiments, the first information is used to indicate an update to mobility-related configuration, and to indicate the status of the updated mobility-related configuration, including at least one of the following:

[0442] If the field corresponding to the sub-information exists, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated;

[0443] If the field corresponding to the sub-information does not exist, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0444] When the value of the field corresponding to the sub-information is the first value, the first information is used to indicate that the status of the updated mobility-related configuration is active;

[0445] When the value of the field corresponding to the sub-information is the second value, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated.

[0446] In some embodiments, the first information is carried in Radio Resource Control (RRC) signaling, or the first information is carried in a data packet.

[0447] In some embodiments, the mobility-related configuration includes at least one of the following:

[0448] Mobility configuration;

[0449] Mobility measurement resource allocation;

[0450] Mobility reporting configuration.

[0451] In some embodiments, the mobility configuration includes at least one of the following: L1-triggered mobility configuration; L2-triggered mobility configuration; L3-triggered mobility configuration; conditional switching (CHO) configuration; layer 1 and / or layer 2-triggered mobility LTM configuration; and conditional LTM configuration.

[0452] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0453] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0454] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0455] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0456] Figure 5A This is a schematic diagram of the structure of the communication device 5100 proposed in this embodiment. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0457] like Figure 5AAs shown, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0458] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps (e.g., steps S201, S202, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 5101 performs at least one of other steps (e.g., steps S201, S202, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0459] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0460] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may vary. Figure 5A The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0461] Figure 5B This is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to... Figure 5B The diagram shown is a schematic representation of the structure of chip 5200, but it is not limited to this.

[0462] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0463] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0464] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S201, S202, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S201, S202, but not limited thereto).

[0465] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0466] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0467] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0468] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, Performed by a user equipment (UE), the method includes: The system receives first information sent by a network device, wherein the first information is used to indicate an update to mobility-related configuration and to indicate the status of the updated mobility-related configuration.

2. The method according to claim 1, characterized in that, Update mobility-related configurations, including at least one of the following: Add mobility-related configurations; Modify mobility-related configurations; Release mobility-related configurations.

3. The method according to claim 1 or 2, characterized in that, The state includes at least one of the following: activation; Go to activate.

4. The method according to any one of claims 1 to 3, characterized in that, The first information is used to indicate the updating of mobility-related configurations, and to indicate the status of the updated mobility-related configurations, including at least one of the following: When the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive. When the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate whether the status of the added mobility-related configuration is active or deactivated. When the first information is used to indicate the modification of mobility-related configuration, the first information is also used to indicate whether the modified mobility-related configuration is active or deactivated. When the first information is used to indicate a modification to mobility-related configurations, the first information is also used to indicate that the state of the modified mobility-related configurations remains unchanged.

5. The method according to any one of claims 1 to 3, characterized in that, The first information includes sub-information, which is used to indicate the status of updated mobility-related configurations.

6. The method according to any one of claims 1 to 5, characterized in that, The first information is used to indicate the updating of mobility-related configurations, and to indicate the status of the updated mobility-related configurations, including at least one of the following: If the field corresponding to the sub-information exists, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated; If the field corresponding to the sub-information does not exist, the first information is used to indicate that the status of the updated mobility-related configuration is active; When the value of the field corresponding to the sub-information is the first value, the first information is used to indicate that the status of the updated mobility-related configuration is active; When the value of the field corresponding to the sub-information is the second value, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated.

7. The method according to any one of claims 1 to 6, characterized in that, The first information is carried in Radio Resource Control (RRC) signaling, or the first information is carried in a data packet.

8. The method according to claim 7, characterized in that, When the first information is carried in RRC signaling, the method further includes at least one of the following: Notify the lower-level systems of the status of updated mobility-related configurations; The status of updated mobility-related configurations is obtained from the RRC layer at a lower level.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Switch from the first community to the second community; Based on the first information received in the second cell, the status of the updated mobility-related configuration is determined.

10. The method according to any one of claims 1 to 9, characterized in that, The mobility-related configurations include at least one of the following: Mobility configuration; Mobility measurement resource allocation; Mobility reporting configuration.

11. The method according to claim 10, characterized in that, The mobility configuration includes at least one of the following: L1-triggered mobility configuration; L2-triggered mobility configuration; L3-triggered mobility configuration; Conditional switching of CHO configuration; Mobility LTM configuration triggered by Layer 1 and / or Layer 2; Conditional LTM configuration.

12. A communication method, characterized in that, Performed by a network device, the method includes: Send first information to the user equipment (UE), wherein the first information is used to indicate an update of mobility-related configuration and to indicate the status of the updated mobility-related configuration.

13. The method according to claim 12, characterized in that, Update mobility-related configurations, including at least one of the following: Add mobility-related configurations; Modify mobility-related configurations; Release mobility-related configurations.

14. The method according to claim 12 or 13, characterized in that, The state includes at least one of the following: activation; Go to activate.

15. The method according to any one of claims 12 to 14, characterized in that, The first information is used to indicate the updating of mobility-related configurations, and to indicate the status of the updated mobility-related configurations, including at least one of the following: When the first information is used to indicate the release of mobility-related configurations, the first information is also used to indicate that the released mobility-related configurations are inactive. When the first information is used to indicate the addition of mobility-related configuration, the first information is also used to indicate whether the status of the added mobility-related configuration is active or deactivated. When the first information is used to indicate the modification of mobility-related configuration, the first information is also used to indicate whether the modified mobility-related configuration is active or deactivated. When the first information is used to indicate a modification to mobility-related configurations, the first information is also used to indicate that the state of the modified mobility-related configurations remains unchanged.

16. The method according to any one of claims 12 to 15, characterized in that, The first information includes sub-information, which is used to indicate the status of updated mobility-related configurations.

17. The method according to any one of claims 12 to 16, characterized in that, The first information is used to indicate the updating of mobility-related configurations, and to indicate the status of the updated mobility-related configurations, including at least one of the following: If the field corresponding to the sub-information exists, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated; If the field corresponding to the sub-information does not exist, the first information is used to indicate that the status of the updated mobility-related configuration is active; When the value of the field corresponding to the sub-information is the first value, the first information is used to indicate that the status of the updated mobility-related configuration is active; When the value of the field corresponding to the sub-information is the second value, the first information is used to indicate that the status of the updated mobility-related configuration is deactivated.

18. The method according to any one of claims 12 to 17, characterized in that, The first information is carried in Radio Resource Control (RRC) signaling, or the first information is carried in a data packet.

19. The method according to any one of claims 12 to 18, characterized in that, The mobility-related configurations include at least one of the following: Mobility configuration; Mobility measurement resource allocation; Mobility reporting configuration.

20. The method according to claim 19, characterized in that, The mobility configuration includes at least one of the following: L1-triggered mobility configuration; L2-triggered mobility configuration; L3-triggered mobility configuration; Conditional switching of CHO configuration; Mobility LTM configuration triggered by Layer 1 and / or Layer 2; Conditional LTM configuration.

21. A communication system, characterized in that, The device includes a terminal and an access network device, wherein the terminal is configured to implement the communication method according to any one of claims 1-11, and the access network device is configured to implement the communication method according to any one of claims 12-20.

22. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1 to 11 or 12-20.

23. A communication system, characterized in that, The device includes a user equipment (UE) and a network device, wherein the UE is configured to implement the communication method according to any one of claims 1 to 11, and the network device is configured to implement the communication method according to any one of claims 12 to 20.

24. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method according to any one of claims 1 to 20.

25. A program product, characterized in that, When the above-described program product is executed by a communication device, the communication device performs the communication method according to any one of claims 1 to 20.

Images