Mobility management method and apparatus, device and storage medium

Abstract

The present application relates to the technical field of communications, and discloses a mobility management method and apparatus, a device, and a storage medium. The method comprises: sending and / or receiving mobility management-related signaling, the mobility management-related signaling including signaling for one or more group-based devices. Mobility management can be performed on one or more devices on the basis of a group, thereby facilitating ensuring the continuity of overall network services.

Description

Mobility management methods, devices, equipment and storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a mobility management method, apparatus, device, and storage medium. Background Technology

[0002] In related technologies, interactions related to connected mobility management typically occur between terminal devices and network devices.

[0003] In a subnetwork-based system, terminal devices, group header devices, and macro nodes need to interact with each other regarding connected mobility management. Ensuring the continuity of overall network services remains a challenge.

[0004] Summary of the Invention

[0005] This application provides a mobility management method, apparatus, device, and storage medium. The technical solution is as follows:

[0006] According to one aspect of the embodiments of this application, a mobility management method is provided, the method being executed by a first terminal device, the method comprising:

[0007] Sending and / or receiving mobility management-related signaling, including signaling for one or more devices based on a group.

[0008] According to another aspect of the embodiments of this application, a mobility management method is provided, the method being performed by a source group head device, the method comprising:

[0009] Sending and / or receiving mobility management-related signaling, including signaling for one or more devices based on a group.

[0010] According to another aspect of the embodiments of this application, a mobility management method is provided, the method being executed by a source / macro node device, the method comprising:

[0011] Sending and / or receiving mobility management-related signaling, including signaling for one or more devices based on a group.

[0012] According to another aspect of the embodiments of this application, a mobility management method is provided, the method being performed by a target group head device, the method comprising:

[0013] Sending and / or receiving mobility management-related signaling, including signaling for one or more devices based on a group.

[0014] According to another aspect of the embodiments of this application, a mobility management method is provided, the method being executed by a target macro node device, the method comprising:

[0015] Sending and / or receiving mobility management-related signaling, including signaling for one or more devices based on a group.

[0016] According to another aspect of the embodiments of this application, a mobility management device is provided, the device comprising:

[0017] A transceiver module is used to send and / or receive mobility management-related signaling, including signaling for one or more devices based on a group.

[0018] According to another aspect of the embodiments of this application, a mobility management device is provided, the device comprising:

[0019] A transceiver module is used to send and / or receive mobility management-related signaling, including signaling for one or more devices based on a group.

[0020] According to another aspect of the embodiments of this application, a mobility management device is provided, the device comprising:

[0021] A transceiver module is used to send and / or receive mobility management-related signaling, including signaling for one or more devices based on a group.

[0022] According to another aspect of the embodiments of this application, a mobility management device is provided, the device comprising:

[0023] A transceiver module is used to send and / or receive mobility management-related signaling, including signaling for one or more devices based on a group.

[0024] According to another aspect of the embodiments of this application, a mobility management device is provided, the device comprising:

[0025] A transceiver module is used to send and / or receive mobility management-related signaling, including signaling for one or more devices based on a group.

[0026] According to another aspect of the embodiments of this application, a communication device is provided, the communication device comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor;

[0027] The processor is configured to load and execute executable instructions to implement mobility management methods as described above.

[0028] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, which stores a computer program that is loaded and executed by a processor to implement the mobility management methods as described in the various aspects above.

[0029] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium; a processor reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the mobility management methods as described in the various aspects above.

[0030] The technical solutions provided in this application embodiment may include the following beneficial effects:

[0031] In the case of both macro-domain networks and micro-domain networks, the first terminal device can perform group-based mobility management based on the received mobility management-related signaling. This reduces the need for multiple transmissions or receptions of the same type of signaling for different devices within the same group when there are interactions between the terminal device, the group head device, and the macro node device that need to perform connection-mode mobility management-related interactions. Attached Figure Description

[0032] Figure 1 shows a schematic diagram of a communication system provided in an embodiment of this application;

[0033] Figure 2 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0034] Figure 3 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0035] Figure 4 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0036] Figure 5 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0037] Figure 6 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0038] Figure 7 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0039] Figure 8 shows a schematic diagram of a mobility management method provided in an embodiment of this application;

[0040] Figure 9 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0041] Figure 10 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0042] Figure 11 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0043] Figure 12 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0044] Figure 13 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0045] Figure 14 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0046] Figure 15 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0047] Figure 16 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0048] Figure 17 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0049] Figure 18 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0050] Figure 19 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0051] Figure 20 shows a flowchart of a mobility management method provided in an embodiment of this application;

[0052] Figure 21 shows a structural block diagram of a movable device provided in an embodiment of this application;

[0053] Figure 22 shows a structural block diagram of a source header device provided in an embodiment of this application;

[0054] Figure 23 shows a structural block diagram of a source group external device provided in an embodiment of this application;

[0055] Figure 24 shows a structural block diagram of a target assembly head device provided in an embodiment of this application;

[0056] Figure 25 shows a structural block diagram of a target group external device provided in an embodiment of this application;

[0057] Figure 26 shows a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims. All other embodiments obtained by those skilled in the art with respect to the embodiments of this application without inventive effort are within the scope of protection of this application.

[0059] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items. It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word “if,” as used herein, can be interpreted as “when,” “in response to a determination,” or “when…”.

[0060] First, the relevant technologies involved in the embodiments of this application will be introduced:

[0061] • Radio Resource Management (RRM) Measurement:

[0062] For connected user equipment (UE), the basic measurement configuration of the 5th Generation (5G) system inherits the framework of the Long Term Evolution (LTE) system, including the following parts:

[0063] 1. Measurement Object: This identifies the frequency point information where the UE performs the measurement. Regarding the measurement reference signal, the New Radio (NR) system supports the measurement of two types of reference signals: Synchronization Signal and PBCH Block (SSB) and Channel State Information-Reference Signal (CSI-RS). For SSB measurement, the frequency point information is the SSB frequency point associated with the measurement object. Since the 5G system supports transmission with multiple different subcarrier spacings, the measurement object needs to indicate the relevant SSB subcarrier spacing. For the measurement configuration of the SSB reference signal, the measurement object also needs to indicate the SSB measurement time window information, i.e., the SSB Measurement Timing Configuration (SMTC) information. The network can further instruct the UE on which SSBs to measure within the SMTC. For the measurement configuration of the CSI-RS reference signal, the measurement object includes the configuration of CSI-RS resources. To enable the UE to derive cell measurement results from beam measurement results, the measurement object is also configured with beam measurement result filtering thresholds based on SSB and CSI-RS, as well as the maximum number of beams allowed for linear averaging calculation. For Layer 3 (L3) filtering of beam measurement results and cell measurement results, the measurement object also indicates specific filtering coefficients according to different measurement reference signals.

[0064] 2. Reporting Configuration: This mainly includes configuration information such as reporting criteria, reference signal type, and reporting format. NR supports periodic reporting, event-triggered reporting, Cell Global Identity (CGI) reporting for Automatic Neighbor Relation (ANR) purposes, and System Frame Number and Frame Timing Difference (SFTD) reporting for time difference measurement. For periodic and event-triggered reporting, the reporting configuration specifies the reference signal type, measurement reporting amount, whether to report beam measurement results, and the maximum number of beams that can be reported. For event-triggered reporting, the reporting configuration specifies a measurement trigger amount for each event, selecting one from Reference Signal Received Power (RSRP), Reference Signal Receiving Quality (RSRQ), and Signal to Interference plus Noise Ratio (SINR). Currently, the 5G system inherits 6 intra-system measurement events (i.e., events A1 to A6) and 2 inter-system measurement events (i.e., events B1 and B2) from the LTE system.

[0065] 3. Measurement Identifier: The NR system associates measurement identifiers with measurement objects and reporting configurations. This association method is flexible, allowing for any combination of measurement objects and reporting configurations; that is, one measurement object can be associated with multiple reporting configurations, and one reporting configuration can be associated with multiple measurement objects. The measurement identifier is carried in the measurement report for reference by the network side.

[0066] 4. Measurement Configuration: A set of measurement filtering configuration information is defined for measurement event assessment, reporting, and periodic reporting. Each measurement configuration includes beam measurement configuration and cell measurement configuration, and two sets of filtering configuration information are defined for SSB and CSI-RS respectively. Each set of filtering configuration information further defines three sets of filtering coefficients for RSRP, RSRQ, and SINR respectively. The L3 filtering coefficient used in the measurement object corresponds to a measurement configuration here, indicated by the index in the measurement configuration sequence.

[0067] 5. Measurement Interval: For connected NR UEs, a measurement interval needs to be configured on the network side when performing inter-frequency or inter-system measurements. Within the measurement interval, the UE stops all services and measurements of serving cells. For intra-frequency measurements, the UE may also require a measurement interval, such as when the currently active (Bandwidth Part, BWP) does not cover the SSB frequency to be measured. In terms of configuration, NR supports two measurement interval methods: measurement intervals based on the UE and measurement intervals based on the frequency range (FR).

[0068] • Measurement execution and measurement reporting:

[0069] To meet the power-saving requirements of UEs, the network can include an s-measure (RSRP value) parameter in the measurement configuration. The UE compares the RSRP measurement value of the primary cell (PCell) with the s-measure parameter to control whether the UE performs measurements on non-serving cells. Specifically, the network configures only one s-measure parameter. Since NR supports both SSB and CSI-RS measurements, the network indicates whether the threshold value is for SSB-RSRP or CSI-RSRP values. One s-measure parameter controls the initiation of measurements for all neighboring cells.

[0070] The measurement reporting process in the NR system is largely the same as that in the LTE system, except that NR adds the reporting of SINR measurement results and beam measurement results. When reporting beam measurement results, the UE also reports the beam index as an identifier.

[0071] • Connected mobility management:

[0072] Mobility management of connected UEs is mainly achieved through the network-controlled handover process, which includes three stages: handover preparation, handover execution, and handover completion.

[0073] During the handover preparation phase, after receiving the measurement report sent by the UE, the source base station will make a handover decision and initiate a handover request to the target base station. If the target cell accepts the request, it will send a handover response message to the source base station through the inter-base station interface. This message contains the configuration information of the target cell, i.e., the handover command.

[0074] During the handover execution phase, the source base station sends a handover command to the UE. Upon receiving the handover command, the UE disconnects from the source cell, begins establishing downlink synchronization with the target cell, and then initiates a random access procedure to the target cell using the random access resources configured in the handover command. Upon completion of the random access procedure, the UE reports a handover completion message. During the UE's access to the target cell, the source base station forwards data packets from the User Plane Function (UPF) to the target base station and sends the uplink and downlink data packet transmission and reception status information from the source cell before forwarding to the target base station.

[0075] During the handover completion phase, the target base station sends a path transition request to the Access and Mobility Management Function (AMF), requesting the AMF to switch the data packet transmission path from the UPF to the access network to the target base station. Once the AMF responds to the request, it indicates that the path transition was successful, and the target base station can instruct the source base station to release the UE's context information. At this point, the UE's connection has been switched to the target cell.

[0076] • Conditional Handover (CHO):

[0077] Unlike traditional base station-triggered immediate handover, Conditional Handover (CHO) pre-configures the handover command content for the target cell to the UE when the source cell link quality is good, and simultaneously configures a handover execution condition associated with this handover command content. When the configured handover execution condition is met, the UE can spontaneously initiate handover access to the target cell that meets the condition based on the configuration in the handover command. Since the UE no longer triggers measurement reporting when the handover condition is met, and the UE has already obtained the configuration in the handover command in advance, the previously mentioned problems of measurement reporting and incorrect reception of handover commands are solved. The conditional handover process is also divided into three stages.

[0078] During the handover preparation phase, after receiving the measurement report sent by the UE, the source base station decides to initiate the conditional handover preparation process and sends a handover request message to the target base station. Once the target base station accepts the handover request, it will respond with a set of target cell configurations and send them to the source base station. When forwarding the target cell configurations, the source base station will also configure a set of handover execution conditions for the UE.

[0079] In detail, the conditional handover configuration consists of two parts: target cell configuration and handover execution condition configuration. The target cell configuration is the handover command responded to by the target base station. The source base station must forward this command to the UE completely and transparently, without allowing any modification to its content—a principle consistent with traditional handover. Similar to traditional handover, the handover command can be configured fully or incrementally. When using incremental configuration, the latest UE configuration from the source cell will serve as the reference configuration for the incremental configuration.

[0080] Handover execution condition configuration is primarily used by the UE to assess when to trigger a handover. In discussions of conditional handover configuration, the 3rd Generation Partnership Project (3GPP) adopted the principle of maximizing the reuse of RRM measurement configurations and decided to introduce measurement reporting events, widely used in traditional handover, into the handover execution condition configuration, mainly targeting events A3 and A5. The difference is that when event A3 or A5 in the handover execution condition configuration is triggered, the terminal will no longer report measurements but will instead perform a handover access operation. To achieve this distinction, in the Radio Resource Control (RRC) signaling design, the standard discussion decided to redefine events A3 and A5 to a new conditional trigger configuration branch in the reporting configuration. This way, handover execution conditions can be configured to the UE in the form of measurement identifiers, without interfering with measurement configurations related to measurement reporting. During the discussions, some network equipment manufacturers suggested that, in order to minimize deviations from the traditional handover decision-making network implementation, the handover execution conditions configured for the terminal need to consider multiple factors, such as multiple reference signals (SSB or CSI-RS), multiple measurements (RSRP, RSRQ, and SINR), and multiple measurement events. Conversely, terminal manufacturers preferred that the configuration of handover execution conditions be as simple as possible for easy implementation by the UE. Ultimately, through discussions and integration at the standards meeting, the following consensus was reached regarding the configuration of handover execution conditions:

[0081] • A maximum of two measurement markers;

[0082] • A maximum of one reference signal (SSB or CSI-RS);

[0083] • A maximum of two measurements (two of RSRP, RSRQ, and SINR);

[0084] • A maximum of two measurement events.

[0085] Since the handover configuration is sent to the UE in advance, and because the direction of terminal movement is somewhat unpredictable, the source base station cannot accurately know which candidate cell the UE will ultimately initiate handover access to. Therefore, in actual network deployment, the source base station will send handover requests to multiple target base stations and forward the handover commands from multiple target base stations to the UE, while configuring the corresponding handover execution conditions. In other words, the terminal typically receives a set of handover configurations related to a set of candidate cells.

[0086] During the handover execution phase, the UE continuously evaluates whether the measurement results of the candidate cell meet the handover execution conditions. Once the conditions are met, the UE immediately terminates the connection with the source cell, establishes synchronization with the new cell, initiates a random access procedure, and reports a handover completion message to the target base station upon completion of the random access procedure.

[0087] As mentioned earlier, since the direction of terminal movement is unpredictable, the network typically configures a set of conditional handover configurations for target cells, which provides the terminal with significant flexibility in selecting the target cell for handover. The terminal is only allowed to select a target cell once. If access to that target cell fails, the terminal triggers a connection re-establishment process. Furthermore, NR has introduced enhancements to connection re-establishment. Specifically, during connection re-establishment, if the cell selected by the terminal is a CHO candidate cell, the terminal can directly perform handover access based on the conditional handover configuration of that cell; otherwise, the terminal performs the traditional connection re-establishment process. Additionally, if multiple target cells simultaneously meet the conditions, NR does not specify how the terminal should select one.

[0088] • Sub-Network:

[0089] The "IMT-2030+ Vision and Requirements White Paper" mentions potential application scenarios for 6th Generation (6G) such as immersive experiences, digital twins, and intelligent interaction. Simultaneously, based on traditional performance indicators, it proposes extreme performance requirements such as ultra-high speed, ultra-high transmission reliability, ultra-low latency, ultra-dense connections, and ultra-low power consumption. However, simultaneously supporting these extreme performance requirements across the entire network would significantly increase network load and 6G operating costs, making it impractical. Considering that these specific application scenarios are typically deployed in smaller areas and have strong local data service attributes, deploying and providing localized, high-performance data service support within a small area is an important direction for meeting 6G scenario requirements. Wide-area micro-domain convergence and sub-network wireless access network concepts such as sub-networks have been successively proposed by the industry in the 6G era. One approach is to aggregate terminal data within microdomains, introducing a cluster head node for each microdomain. Microdomain terminals can then interact with the wide area network (WAN) or other microdomain terminals via the cluster head node, significantly reducing the load and maintenance costs of the macrodomain network and improving spectrum resource utilization. In some embodiments, the macrodomain network may also be referred to as a macro network or a wide area network.

[0090] Microdomain terminal services can be divided into two types: local services within the microdomain, which are services whose generation, transmission, and processing are all confined to the microdomain itself; and non-local services, which are services generated within the microdomain but processed outside the microdomain, or services generated outside the microdomain but targeted at a specific node within the microdomain. These types of services typically have medium latency requirements in the millisecond range or are latency-insensitive services, and can ultimately be processed via a wide area network (WAN).

[0091] Micro-domain local service transmission includes data transmission between micro-domain terminals and micro-domain cluster head nodes, as well as optional data transmission between micro-domain terminals. Compared with traditional WAN transmission, micro-domain local service data has a shorter transmission path, making it easier to achieve extreme performance requirements such as ultra-low latency and ultra-high reliability. In a WAN-micro-domain converged networking architecture, signaling connections between micro-domain cluster head nodes and the WAN access network and WAN core network are required.

[0092] In addition to supporting local service transmission within the microdomain, it is also necessary to support non-local service transmission between microdomain terminals and the macrodomain network. This will fully utilize WAN cloud computing resources, balance the load between the microdomain and macrodomain networks, and more effectively and flexibly handle various services from microdomain terminals. Furthermore, non-local microdomain services also include inter-microdomain service transmission, such as information transmission between terminals in one microdomain and terminals in another, or information transmission between two microdomain cluster head nodes. For non-local microdomain services, relay mode can be used to forward them to the macrodomain network through the microdomain cluster head node.

[0093] In some embodiments, a microdomain may also be referred to as a private domain, a subnet, or a subnetwork. A cluster head may also be referred to as a group head, a cluster head node, or a group head node.

[0094] Figure 1 illustrates a schematic diagram of a communication system provided in an exemplary embodiment of this application. The communication system 100 includes a macro-domain communication system 101 and at least one micro-domain communication system. The macro-domain communication system 101 includes a macro node device 110 and at least one macro-domain terminal device 120.

[0095] In this embodiment, at least one micro-domain communication system includes micro-domain communication system 102 and micro-domain communication system 103. Micro-domain communication system 102 includes a micro-domain group leader device 131 and at least one micro-domain terminal device 141. Micro-domain communication system 103 includes a micro-domain group leader device 132 and at least one micro-domain terminal device 142. It should be understood that the micro-domain group leader device 131 and micro-domain group leader device 132 can be terminal devices or macro node devices. Micro-domain terminal devices can also be referred to as group member devices. In this embodiment, an example is provided where the entire communication system 100 includes macro node devices, terminal devices, group leader devices, and group member devices.

[0096] The macro-domain terminal device 120 or micro-domain terminal device 140 in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus. This terminal includes, but is not limited to: handheld devices, wearable devices, in-vehicle devices, and IoT devices, such as: mobile phones, tablets, e-readers, laptops, desktop computers, televisions, game consoles, mobile internet devices (MID), augmented reality (AR) terminals, virtual reality (VR) terminals, mixed reality (MR) terminals, wearable devices, controllers, electronic tags, controllers, wireless terminals in industrial control, self-driving, remote medical, smart grid, transportation safety, smart city, smart home, remote medical surgery, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, and wireless local loops. Loop (WLL) stations, personal digital assistants (PDAs), set-top boxes (STBs), customer premises equipment (CPEs), etc.

[0097] The macro node device 110 or micro domain group head device 130 in this application embodiment provides wireless communication functions, including but not limited to: Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B, or Home Node B, HNB), Baseband Unit (BBU), Access Point (AP), Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP), or Transmission and Reception Point (TRP) in a Wireless Fidelity (Wi-Fi) system, etc., and can also provide next-generation Node B (Next Generation Node) functions in 5G mobile communication systems. B, gNB) or transmission point (TRP or TP), or, in a 5G system, one or a group of antenna panels (including multiple antenna panels) of a base station, or, network nodes constituting a gNB or transmission point, such as baseband unit (BBU) or distributed unit (DU), or base stations in Beyond Fifth Generation (B5G) mobile communication systems or 6th Generation (6G) mobile communication systems, or core network (CN), fronthaul, backhaul, radio access network (RAN), network slicing, etc., or serving cell, primary cell (PCell), primary secondary cell (PSCell), special cell (SpCell), secondary cell (SCell), neighboring cell, etc. of terminal equipment.

[0098] In some embodiments, macro node devices and macro domain terminal devices can communicate one-to-one, one-to-many, or many-to-one. Each macro node device communicates with each macro domain terminal device via some kind of air interface technology.

[0099] In some embodiments, the microdomain header device and the microdomain terminal device can communicate one-to-one, one-to-many, or many-to-one. Each microdomain header device communicates with each microdomain terminal device through some kind of air interface technology.

[0100] In some embodiments, macro node devices and micro domain group head devices can communicate one-to-one, one-to-many, or many-to-one. Each macro node device communicates with each micro domain group head device via some kind of air interface technology.

[0101] It should be understood that in the description of the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between them, or a relationship of instruction and being instructed, configuration and being configured, etc. In the embodiments of this application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0102] In some embodiments, this application provides a mobility management method capable of enabling micro-domain terminal devices to switch from a source micro-domain to a target micro-domain, or micro-domain terminal devices to a target macro-domain, or macro-domain terminal devices to a target micro-domain, or macro-domain terminal devices to a target macro-domain. In some embodiments, the micro-domain network may also be referred to as a micro-network or a private network.

[0103] In some embodiments, the micro-domain terminal device switching from the source micro-domain to the target micro-domain can also be understood as the micro-domain terminal device switching from the source micro-domain network to the target micro-domain network, or the micro-domain terminal device switching from the source micro-domain node to the target micro-domain node, or the micro-domain terminal device switching from the source macro-domain node to the target macro-domain node.

[0104] In some embodiments, the switching of a micro-domain terminal device from a source micro-domain to a target macro-domain can also be understood as the switching of a micro-domain terminal device from a source micro-domain network to a target macro-domain network, or the switching of a micro-domain terminal device from a source micro-domain node to a target macro-domain node, or the switching of a micro-domain terminal device from a source macro-domain node to a target macro-domain node.

[0105] In some embodiments, the macro domain terminal device switching from the source macro domain to the target micro domain can also be understood as the macro domain terminal device switching from the source macro domain network to the target micro domain network, or the macro domain terminal device switching from the source macro domain node to the target micro domain node, or the macro domain terminal device switching from the source macro domain node to the target macro domain node.

[0106] In some embodiments, the macro domain terminal device switching from the source macro domain to the target macro domain can also be understood as the macro domain terminal device switching from the source macro domain network to the target macro domain network, or the macro domain terminal device switching from the source macro domain node to the target macro domain node.

[0107] In some embodiments, the source microdomain and the target microdomain correspond to the same macrodomain network. For example, as shown in FIG2, the microdomain terminal device 141 switches from microdomain network 1 to microdomain network 2. Here, microdomain network 1 is the source microdomain, microdomain network 2 is the target microdomain, microdomain network 1 corresponds to macrodomain network 1, and microdomain network 2 also corresponds to macrodomain network 1.

[0108] In some embodiments, the source microdomain and the target microdomain correspond to different macrodomain networks. For example, as shown in FIG3, the microdomain terminal device 141 switches from microdomain network 1 to microdomain network 3. Here, microdomain network 1 is the source microdomain, microdomain network 3 is the target microdomain, microdomain network 1 corresponds to macrodomain network 1, and microdomain network 3 corresponds to macrodomain network 2. Macrodomain network 1 and macrodomain network 2 are different.

[0109] In some embodiments, the macro domain network corresponding to the source micro domain is the same as the target macro domain. For example, as shown in FIG4, the micro domain terminal device 141 switches from micro domain network 1 to macro domain network 1. Here, micro domain network 1 is the source micro domain, macro domain network 1 is the target macro domain, and micro domain network 1 also corresponds to macro domain network 1.

[0110] In some embodiments, the macro domain network corresponding to the source micro domain is different from the target macro domain. For example, as shown in FIG5, the micro domain terminal device 141 switches from micro domain network 1 to macro domain network 2. Here, micro domain network 1 is the source micro domain, macro domain network 2 is the target macro domain, micro domain network 1 corresponds to macro domain network 1, and macro domain network 1 and macro domain network 2 are different.

[0111] In some embodiments, the source macro domain and the target micro domain correspond to the same macro domain network. For example, as shown in FIG6, the macro domain terminal device 121 switches from macro domain network 1 to micro domain network 1. Here, macro domain network 1 is the source macro domain, micro domain network 1 is the target micro domain, and micro domain network 1 also corresponds to macro domain network 1.

[0112] In some embodiments, the source macro domain and the target micro domain correspond to different macro domain networks. For example, as shown in FIG7, the macro domain terminal device 121 switches from macro domain network 2 to micro domain network 1. Here, macro domain network 2 is the source macro domain, micro domain network 1 is the target micro domain, micro domain network 1 corresponds to macro domain network 1, and macro domain network 1 and macro domain network 2 are different.

[0113] In some embodiments, the source macro domain and the target macro domain are different. For example, as shown in FIG8, macro domain terminal device 121 switches from macro domain network 2 to macro domain network 1. Macro domain network 1 and macro domain network 2 are different.

[0114] This application provides a mobility management method, including the following implementation scenarios:

[0115] Implementation Scenario 1: The RRC connection anchor point is on the group head device, switching from the source microdomain to the target microdomain;

[0116] Implementation Scenario 2: The RRC connection anchor point is on the group head device, switching from the source micro domain to the target macro domain;

[0117] Implementation Scenario 3: The RRC connection anchor point is on the group head device, switching from the source macro domain to the target micro domain;

[0118] Implementation Scenario 4: Switching from the source macro domain to the target macro domain;

[0119] Implementation Scenario 5: The RRC connection anchor point is on the macro node device, switching from the source macro domain to the target micro domain;

[0120] Implementation Scenario 6: The RRC connection anchor point is on the macro node device, switching from the source micro domain to the target macro domain;

[0121] Implementation Scenario 7: RRC connection anchor point is on macro node device, switching from source micro domain to target micro domain;

[0122] For implementation scenario one:

[0123] Figure 9 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more member devices, a source group head device, and a target group head device to enable one or more member devices to switch from a source microdomain to a target microdomain. The method includes:

[0124] Operation 1: The source group head device sends a measurement configuration message to one or more member devices;

[0125] In some embodiments, the source group head device is a device that manages one or more member devices in a source microdomain. Optionally, both the source group head device and the member devices are terminal devices. Optionally, the source group head device is a network device, and the member devices are terminal devices.

[0126] In this embodiment, the source group head device can be understood as a source microdomain macro node device within the source microdomain. The group member device can be understood as a source microdomain terminal device within the source microdomain.

[0127] In some embodiments, a measurement configuration message is used to indicate the measurement configuration of one or more member devices. Optionally, the measurement configuration includes at least one of a measurement identifier, a reference signal, a measurement quantity, and a measurement event. The measurement configuration indicated by the measurement configuration message is configured for all or some of the member devices in the source microdomain. For example, assuming that the source microdomain includes member device 1 and member device 2, the measurement configuration message sent by the source group head device may be for both member device 1 and member device 2, or it may be for only member device 1 or member device 2.

[0128] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a private measurement configuration. The common measurement configuration is broadcast to multiple member devices via a system message, while the private measurement configuration is sent individually to each member device via terminal-specific signaling. Optionally, the private measurement configuration is sent via RRC private signaling or a MAC control element (MAC CE).

[0129] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple member devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0130] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single member device, used to indicate the measurement configuration used by the single member device within the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to member device 1, used to indicate that the measurement configuration of member device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to member device 2, used to indicate that the measurement configuration of member device 2 is measurement configuration 2 and measurement configuration 3.

[0131] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple member devices, and a dedicated measurement configuration includes a dedicated portion of the measurement configuration of a single member device. For example, the common measurement configuration includes a measurement configuration 2 shared by member device 1 and member device 2. The dedicated measurement configuration includes a measurement configuration 1 dedicated to member device 1 and a measurement configuration 3 dedicated to member device 2.

[0132] When there are enough common measurement configurations for multiple member devices, indicating the complete set of measurement configurations for multiple member devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both member device 1 and member device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configuration.

[0133] Operation 2: One or more member devices receive measurement configuration messages sent by the source group head device;

[0134] In some embodiments, one or more member devices receive a measurement configuration from a measurement configuration message sent by a source group head device, and perform measurements based on the corresponding measurement configuration to generate measurement results. These measurement results are obtained based on the measurement configuration.

[0135] Operation 3: One or more member devices report measurement results to the source group head device;

[0136] In some embodiments, one or more member devices report measurement results to the source group head device based on the reporting configuration. Optionally, the measurement results include at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate micro-domain network.

[0137] In some embodiments, each member device reports measurement results to the source group head device based on its reporting configuration. For example, assuming the group includes member device 1 and member device 2, the measurement results include measurement result 1 reported by member device 1 to the source group head device based on its reporting configuration, and measurement result 2 reported by member device 2 to the source group head device based on its reporting configuration. There is a one-to-one correspondence between the member devices and the measurement results.

[0138] Operation 4: The source group head device receives measurement results reported by one or more member devices;

[0139] In some embodiments, the source group head device receives measurement results reported by one or more member devices and determines a target microdomain from at least one candidate microdomain network based on the measurement results. The target microdomain is the microdomain network to which one or more member devices will switch.

[0140] In some embodiments, the source microdomain and the target microdomain correspond to the same macrodomain network. Alternatively, the source microdomain and the target microdomain correspond to different macrodomain networks.

[0141] Operation 5: The source group head device sends the first handover request to the target group head device;

[0142] In some embodiments, when the source group head device determines the target microdomain, the source group head device sends a first handover request to the target group head device.

[0143] In some embodiments, the target group head device is a device that manages one or more member devices in a target microdomain. Optionally, the target group head device is an end device. Optionally, the target group head device is a network device.

[0144] In some embodiments, the first handover request is used to request the handover of one or more member devices from the source microdomain to the target microdomain.

[0145] In some embodiments, the first handover request is sent via a direct connection interface between the source group head device and the target group head device, or forwarded via a macro node device. For example, the first handover request is sent to the source macro node device in the form of an RRC message by the source group head device, then sent to the target macro node device by the source macro node device, and finally sent to the target group head device in the form of an RRC message by the target macro node device.

[0146] In some embodiments, the first switching request carries identifiers of one or more member devices. These identifiers help identify the member device requiring switching when multiple member devices are included. For example, suppose the source microdomain includes member device 1, member device 2, and member device 3. If the first switching request carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 need to be switched, while member device 3 does not need to be switched.

[0147] Operation 6: The target group head device receives the first handover request sent by the source group head device;

[0148] In some embodiments, the target group head device receives a first handover request sent by the source group head device, and performs access control on one or more group member devices based on the first handover request.

[0149] Operation 7: The target group head device sends a first handover request confirmation to the source group head device;

[0150] In some embodiments, the target group head device sends a first handover request confirmation to the source group head device based on the received first handover request. The first handover request confirmation is a handover request confirmation for one or more member devices.

[0151] In some embodiments, the first handover request confirmation is sent via a direct connection interface between the source group head device and the target group head device, or forwarded via a macro node device. For example, the first handover request confirmation is sent by the source group head device to the source macro node device in the form of an RRC message, then sent by the source macro node device to the target macro node device, and finally sent by the target macro node device to the target group head device in the form of an RRC message.

[0152] In some embodiments, the first handover request confirmation carries the identifiers of one or more member devices. This identifier helps identify member devices that can perform the handover when multiple member devices are included. For example, suppose the first handover request requests a handover of member device 1, member device 2, and member device 3. If the first handover request confirmation carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 can perform the handover, while member device 3 cannot perform the handover.

[0153] Operation 8: The source group head device receives confirmation of the first handover request sent by the target group head device;

[0154] In some embodiments, the source group head device receives a first handover request confirmation sent by the target group head device, and sends a handover command to one or more group member devices based on the first handover request confirmation.

[0155] Operation 9: The source group head device sends a switchover command to one or more group member devices;

[0156] In some embodiments, the switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0157] In some embodiments, the source group head device sends a handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes the information required for the handover.

[0158] In some embodiments, the handover command is a common handover command, which is broadcast to multiple member devices in system messages. When the handover command is directed at multiple member devices simultaneously, broadcasting the handover command to multiple member devices in system messages helps to save signaling overhead.

[0159] In some embodiments, the handover command is a dedicated handover command, which is sent individually to each member device via dedicated RRC signaling.

[0160] Operation 10: One or more member devices receive a switching command sent by the source group head device;

[0161] In some embodiments, one or more member devices receive a handover command and determine, based on the handover command, whether to switch the RRC connection to the target group head device. If it is determined that the RRC connection to the target group head device should be switched, the following operations continue.

[0162] In some embodiments, each member device receives its corresponding handover command and determines whether to switch the RRC connection to the target group head device based on the corresponding handover command. For example, assuming member device 1 receives a handover command, member device 1 determines whether to switch the RRC connection to the target group head device based on the received handover command.

[0163] Operation 11: One or more member devices switch their RRC connection to the target group head device;

[0164] In some embodiments, one or more member devices switch the RRC connection from the source group head device to the target group head device according to a received switching command.

[0165] In some embodiments, each member device switches its RRC connection to the target group head device. For example, assuming that member device 1, member device 2, and member device 3 all receive a switching command, then member device 1, member device 2, and member device 3 respectively switch their RRC connections to the target group head device.

[0166] Operation 12: One or more member devices send a handover completion message to the target group head device;

[0167] In some embodiments, after one or more member devices complete the RRC connection handover, a handover completion message is sent to the target group head device. The handover completion message indicates that the RRC connection of one or more member devices has been switched to the target group head device.

[0168] In some embodiments, each member device sends a handover completion message to the target group head device. For example, suppose member device 1, member device 2, and member device 3 each switch their RRC connection to the target group head device. Then, member device 1, member device 2, and member device 3 each send handover completion message 1, handover completion message 2, and handover completion message 3 to the target group head device.

[0169] Operation 13: The target group head device receives a handover completion message from one or more group member devices.

[0170] In some embodiments, when the target group head device receives a handover completion message from one or more member devices, it indicates that one or more member devices have successfully established an RRC connection with the target group head device. At this point, one or more member devices have successfully handed over from the source microdomain to the target microdomain.

[0171] In some embodiments, the target group head device receives handover completion messages from all member devices that have switched their RRC connections from the source group head device to the target group head device. For example, assuming member device 1, member device 2, and member device 3 have switched their RRC connections to the target group head device, the handover completion messages received by the target group head device include handover completion message 1 sent by member device 1, handover completion message 2 sent by member device 2, and handover completion message 3 sent by member device 3.

[0172] In summary, the method provided in this embodiment enables member devices to switch from a source microdomain to a target microdomain based on the group when the RRC connection anchor point of one or more member devices is located on the group head device. Furthermore, the group head device can directly manage the mobility of member devices without the involvement of macro node devices, which helps reduce the complexity of successful switching of member devices from the source microdomain to the target microdomain.

[0173] For implementation scenario two:

[0174] Figure 10 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. This method is jointly executed by one or more member devices, a source group head device, and a target macro node device to enable one or more member devices to switch from a source microdomain to a target macrodomain.

[0175] The method includes:

[0176] Operation 21: The source group head device sends a measurement configuration message to one or more member devices;

[0177] In some embodiments, the source group head device is a device that manages one or more member devices in a source microdomain. Optionally, both the source group head device and the member devices are terminal devices. Optionally, the source group head device is a network device, and the member devices are terminal devices.

[0178] In this embodiment, the source group head device can be understood as a source microdomain macro node device within the source microdomain. The group member device can be understood as a source microdomain terminal device within the source microdomain.

[0179] In some embodiments, a measurement configuration message is used to indicate the measurement configuration of one or more member devices. Optionally, the measurement configuration includes at least one of a measurement identifier, a reference signal, a measurement quantity, and a measurement event. The measurement configuration indicated by the measurement configuration message is configured for all or some of the member devices in the source microdomain. For example, assuming that the source microdomain includes member device 1 and member device 2, the measurement configuration message sent by the source group head device may be for both member device 1 and member device 2, or it may be for only member device 1 or member device 2.

[0180] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a private measurement configuration. The common measurement configuration is broadcast to multiple member devices via a system message, while the private measurement configuration is sent individually to each member device via terminal-specific signaling. Optionally, the private measurement configuration is sent via RRC private signaling or a MAC control element (MAC CE).

[0181] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple member devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0182] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single member device, used to indicate the measurement configuration used by the single member device within the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to member device 1, used to indicate that the measurement configuration of member device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to member device 2, used to indicate that the measurement configuration of member device 2 is measurement configuration 2 and measurement configuration 3.

[0183] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple member devices, and a dedicated measurement configuration includes a dedicated portion of the measurement configuration of a single member device. For example, the common measurement configuration includes a measurement configuration 2 shared by member device 1 and member device 2. The dedicated measurement configuration includes a measurement configuration 1 dedicated to member device 1 and a measurement configuration 3 dedicated to member device 2.

[0184] When there are enough common measurement configurations for multiple member devices, indicating the complete set of measurement configurations for multiple member devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both member device 1 and member device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configuration.

[0185] Operation 22: One or more member devices receive a measurement configuration message sent by the source group head device;

[0186] In some embodiments, one or more member devices receive a measurement configuration from a measurement configuration message sent by a source group head device, and perform measurements based on the corresponding measurement configuration to generate measurement results. These measurement results are obtained based on the measurement configuration.

[0187] Operation 23: One or more member devices report measurement results to the source group head device;

[0188] In some embodiments, one or more member devices report measurement results to the source group head device based on the reporting configuration. Optionally, the measurement results include at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate macro domain network.

[0189] In some embodiments, each member device reports measurement results to the source group head device based on its reporting configuration. For example, assuming the group includes member device 1 and member device 2, the measurement results include measurement result 1 reported by member device 1 to the source group head device based on its reporting configuration, and measurement result 2 reported by member device 2 to the source group head device based on its reporting configuration. There is a one-to-one correspondence between the member devices and the measurement results.

[0190] Operation 24: The source group head device receives measurement results reported by one or more member devices;

[0191] In some embodiments, the source group head device receives measurement results reported by one or more group member devices and determines a target macro domain from at least one candidate macro domain network based on the measurement results. The target macro domain is the macro domain network to which one or more group member devices will switch.

[0192] In some embodiments, the macro domain network corresponding to the source micro domain is the same as the target macro domain. Alternatively, the macro domain network corresponding to the source micro domain is different from the target macro domain.

[0193] Operation 25: The source group head device sends a second handover request to the target macro node device;

[0194] In some embodiments, if the source group head device determines the target macro domain, the source group head device sends a second handover request to the target macro node device.

[0195] In some embodiments, the target macro node device can be understood as the target macro domain device in the target macro domain.

[0196] In some embodiments, the second switching request is used to request the switching of one or more member devices from the source microdomain to the target macrodomain.

[0197] In some embodiments, the second handover request is sent via an RRC message.

[0198] In some embodiments, the second handover request carries identifiers of one or more member devices. These identifiers help identify the member device requiring a handover when multiple member devices are included. For example, suppose the source microdomain includes member device 1, member device 2, and member device 3. If the second handover request carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 need to be switched, while member device 3 does not need to be switched.

[0199] Operation 26: The target macro node device receives the second handover request sent by the source group head device;

[0200] In some embodiments, the target macro node device receives a second handover request sent by the source group head device, and performs access control on one or more group member devices based on the second handover request.

[0201] Operation 27: The target macro node device sends a second handover request confirmation to the source group head device;

[0202] In some embodiments, the target macro node device sends a second handover request confirmation to the source group head device based on the received second handover request. The second handover request confirmation is a handover request confirmation for one or more group member devices.

[0203] In some embodiments, the second handover request confirmation is sent via an RRC message.

[0204] In some embodiments, the second handover request confirmation carries the identifiers of one or more member devices. This identifier helps identify member devices that can perform the handover when multiple member devices are included. For example, suppose the second handover request requests a handover of member device 1, member device 2, and member device 3. If the second handover request confirmation carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 can perform the handover, while member device 3 cannot perform the handover.

[0205] Operation 28: The source group head device receives confirmation of the second handover request sent by the target macro node device;

[0206] In some embodiments, the source group head device receives a second handover request confirmation from the target macro node device, and sends a handover command to one or more group member devices based on the second handover request confirmation.

[0207] Operation 29: The source group head device sends a switchover command to one or more group member devices;

[0208] In some embodiments, the switching command is used to trigger one or more member devices to switch from the source microdomain to the target macrodomain.

[0209] In some embodiments, the source group head device sends a handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes the information required for the handover.

[0210] In some embodiments, the handover command is a common handover command, which is broadcast to multiple member devices in system messages. When the handover command is directed at multiple member devices simultaneously, broadcasting the handover command to multiple member devices in system messages helps to save signaling overhead.

[0211] In some embodiments, the handover command is a dedicated handover command, which is sent individually to each member device via dedicated RRC signaling.

[0212] Operation 30: One or more member devices receive a switching command sent by the source group head device;

[0213] In some embodiments, one or more member devices receive a handover command and determine, based on the handover command, whether to switch the RRC connection to the target macro node device. If it is determined that the RRC connection to the target macro node device should be switched, the following operations continue.

[0214] In some embodiments, each member device receives its corresponding handover command and determines whether to switch its RRC connection to the target macro node device based on the corresponding handover command. For example, assuming member device 1 receives a handover command, member device 1 determines whether to switch its RRC connection to the target macro node device based on the received handover command.

[0215] Operation 31: One or more member devices switch their RRC connection to the target macro node device;

[0216] In some embodiments, one or more member devices switch the RRC connection from the source group head device to the target macro node device according to a received switching command.

[0217] In some embodiments, each member device switches its RRC connection to the target macro node device. For example, assuming that member device 1, member device 2, and member device 3 all receive a switching command, then member device 1, member device 2, and member device 3 respectively switch their RRC connections to the target macro node device.

[0218] Operation 32: One or more member devices send a handover completion message to the target macro node device;

[0219] In some embodiments, after one or more member devices complete the RRC connection handover, a handover completion message is sent to the target macro node device. The handover completion message indicates that the RRC connection of one or more member devices has been switched to the target macro node device.

[0220] In some embodiments, each member device sends a handover completion message to the target macro node device. For example, suppose member device 1, member device 2, and member device 3 each switch their RRC connection to the target macro node device. Then, member device 1, member device 2, and member device 3 each send handover completion message 1, handover completion message 2, and handover completion message 3 to the target macro node device.

[0221] Operation 33: The target macro node device receives a handover completion message from one or more member devices.

[0222] In some embodiments, when the target macro node device receives a handover completion message from one or more member devices, it indicates that one or more member devices have successfully established an RRC connection with the target macro node device. At this point, one or more member devices have successfully handed over from the source micro domain to the target macro domain.

[0223] In some embodiments, the target macro node device receives handover completion messages from all member devices that have switched their RRC connections from the source group head device to the target macro node device. For example, assuming member device 1, member device 2, and member device 3 have switched their RRC connections to the target macro node device, the handover completion messages received by the target macro node device include handover completion message 1 sent by member device 1, handover completion message 2 sent by member device 2, and handover completion message 3 sent by member device 3.

[0224] In summary, the method provided in this embodiment enables member devices to switch from the source microdomain to the target macrodomain based on the group when the RRC connection anchor point of one or more member devices is located on the group head device. Furthermore, the source group head device can directly manage the mobility of member devices without the involvement of the source macro node device, which helps reduce the complexity of successful switching of member devices from the source microdomain to the target macrodomain.

[0225] For implementation scenario three:

[0226] Figure 11 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more terminal devices, a source macro node device, and a target group head device to enable one or more terminal devices to switch from a source macro domain to a target micro domain. The method includes:

[0227] Operation 41: The source macro node device sends a measurement configuration message to one or more terminal devices;

[0228] In this embodiment, the source macro node device can be understood as a source macro domain device within a source macro domain. The terminal device can be understood as a source macro domain terminal device within a source macro domain.

[0229] In some embodiments, a measurement configuration message is used to indicate the measurement configuration of one or more terminal devices. Optionally, the measurement configuration includes at least one of a measurement identifier, a reference signal, a measurement quantity, and a measurement event. The measurement configuration indicated by the measurement configuration message is configured for all or some of the terminal devices in the source macro domain. For example, assuming that the source macro domain includes terminal device 1 and terminal device 2, the measurement configuration message sent by the source macro node device may be for both terminal device 1 and terminal device 2, or it may be for only terminal device 1 or terminal device 2.

[0230] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in terminal-specific signaling. Optionally, the dedicated measurement configuration is sent via RRC dedicated signaling or a MAC control element (MAC CE).

[0231] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple terminal devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0232] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration adopted by the single terminal device in the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to terminal device 1, used to indicate that the measurement configuration of terminal device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to terminal device 2, used to indicate that the measurement configuration of terminal device 2 is measurement configuration 2 and measurement configuration 3.

[0233] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device. For example, the common measurement configuration includes a measurement configuration 2 shared by terminal device 1 and terminal device 2. The dedicated measurement configuration includes a measurement configuration 1 proprietary to terminal device 1 and a measurement configuration 3 proprietary to terminal device 2.

[0234] When there are enough common measurement configurations for multiple terminal devices, indicating the complete set of measurement configurations for multiple terminal devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both terminal device 1 and terminal device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configurations.

[0235] Operation 42: One or more terminal devices receive measurement configuration messages sent by the source macro node device;

[0236] In some embodiments, one or more terminal devices receive a measurement configuration from a measurement configuration message sent by a source macro node device, and perform measurements based on the corresponding measurement configuration to generate measurement results. These measurement results are obtained based on the measurement configuration.

[0237] Operation 43: One or more terminal devices report measurement results to the source macro node device;

[0238] In some embodiments, one or more terminal devices report measurement results to the source macro node device based on the reporting configuration. Optionally, the measurement results include at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate micro-domain network.

[0239] In some embodiments, each terminal device reports measurement results to the source macro node device based on its reporting configuration. For example, assuming terminal device 1 and terminal device 2 are included, the measurement results include measurement result 1 reported by terminal device 1 to the source macro node device based on its reporting configuration, and measurement result 2 reported by terminal device 2 to the source macro node device based on its reporting configuration. There is a one-to-one correspondence between the terminal devices and the measurement results.

[0240] Operation 44: The source macro node device receives measurement results reported by one or more terminal devices;

[0241] In some embodiments, the source macro node device receives measurement results reported by one or more terminal devices and determines a target microdomain from at least one candidate microdomain network based on the measurement results. The target microdomain is the microdomain network to which one or more terminal devices will switch.

[0242] In some embodiments, the macrodomain networks corresponding to the source macrodomain and the target microdomain are the same. Alternatively, the macrodomain networks corresponding to the source macrodomain and the target microdomain are different.

[0243] Operation 45: The source macro node device sends a third handover request to the target group head device;

[0244] In some embodiments, when the source macro node device determines the target micro domain, the source macro node device sends a third handover request to the target group head device.

[0245] In some embodiments, the target group head device is a device that manages one or more member devices in a target microdomain. Optionally, the target group head device is an end device. Optionally, the target group head device is a network device.

[0246] In some embodiments, the third switching request is used to request the switching of one or more terminal devices from the source macro domain to the target micro domain.

[0247] In some embodiments, the third handover request is sent via an RRC message.

[0248] In some embodiments, the third handover request carries the identifiers of one or more terminal devices. This identifier helps identify the terminal device requiring a handover when multiple terminal devices are included. For example, suppose the source macrodomain includes terminal device 1, terminal device 2, and terminal device 3. If the third handover request carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal device 1 and terminal device 2 need to be switched, while terminal device 3 does not need to be switched.

[0249] Operation 46: The target group head device receives the third handover request sent by the source macro node device;

[0250] In some embodiments, the target group head device receives a third handover request sent by the source macro node device, and performs access control on one or more terminal devices based on the third handover request.

[0251] Operation 47: The target group head device sends a third handover request confirmation to the source macro node device;

[0252] In some embodiments, the target group head device sends a third handover request confirmation to the source macro node device based on the received third handover request. The third handover request confirmation is a handover request confirmation for one or more terminal devices.

[0253] In some embodiments, the third handover request confirmation is sent via an RRC message.

[0254] In some embodiments, the third handover request confirmation carries the identifiers of one or more terminal devices. This identifier helps identify the terminal devices that can perform the handover when multiple terminal devices are included. For example, suppose the third handover request requests a handover of terminal devices 1, 2, and 3. If the third handover request confirmation carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal devices 1 and 2 can perform the handover, while terminal device 3 cannot.

[0255] Operation 48: The source macro node device receives confirmation of the third handover request sent by the target group head device;

[0256] In some embodiments, the source macro node device receives a third handover request confirmation sent by the target group head device, and sends a handover command to one or more terminal devices based on the third handover request confirmation.

[0257] Operation 49: The source macro node device sends a handover command to one or more terminal devices;

[0258] In some embodiments, the switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain.

[0259] In some embodiments, the source macro node device sends a handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes the information required for the handover.

[0260] In some embodiments, the handover command is a common handover command, which is broadcast to multiple terminal devices in system messages. When the handover command is directed to multiple terminal devices simultaneously, broadcasting the handover command to multiple terminal devices in system messages helps to save signaling overhead.

[0261] In some embodiments, the handover command is a dedicated handover command, which is sent individually to each terminal device via dedicated RRC signaling.

[0262] Operation 50: One or more terminal devices receive a handover command sent by the source macro node device;

[0263] In some embodiments, one or more terminal devices receive a handover command and determine, based on the handover command, whether to switch the RRC connection to the target group head device. If it is determined that the RRC connection to the target group head device should be switched, the following operations continue to be performed.

[0264] In some embodiments, each terminal device receives its corresponding handover command and determines whether to switch the RRC connection to the target group head device based on the corresponding handover command. For example, assuming terminal device 1 receives a handover command, terminal device 1 determines whether to switch the RRC connection to the target group head device based on the received handover command.

[0265] Operation 51: One or more terminal devices switch their RRC connection to the target group head device;

[0266] In some embodiments, one or more terminal devices switch the RRC connection from the source macro node device to the target group head device according to the received switching command.

[0267] In some embodiments, each terminal device switches its RRC connection to the target group head device. For example, assuming that terminal device 1, terminal device 2, and terminal device 3 all receive a switching command, then terminal device 1, terminal device 2, and terminal device 3 respectively switch their RRC connections to the target group head device.

[0268] Operation 52: One or more terminal devices send a handover completion message to the target group head device;

[0269] In some embodiments, after one or more terminal devices complete the RRC connection handover, a handover completion message is sent to the target group head device. The handover completion message is used to indicate that the RRC connection of one or more terminal devices has been switched to the target group head device.

[0270] In some embodiments, each terminal device sends a handover completion message to the target group head device. For example, suppose terminal device 1, terminal device 2, and terminal device 3 respectively switch their RRC connections to the target group head device. Then, terminal device 1, terminal device 2, and terminal device 3 respectively send handover completion message 1, handover completion message 2, and handover completion message 3 to the target group head device.

[0271] Operation 53: The target group head device receives a handover completion message from one or more terminal devices.

[0272] In some embodiments, when the target group head device receives a handover completion message from one or more terminal devices, it indicates that one or more terminal devices have successfully established an RRC connection with the target group head device. At this point, one or more terminal devices have successfully handover from the source macro domain to the target micro domain.

[0273] In some embodiments, the target group head device receives handover completion messages from all terminal devices that have switched their RRC connections from the source macro node device to the target group head device. For example, assuming terminal device 1, terminal device 2, and terminal device 3 have switched their RRC connections to the target group head device, the handover completion messages received by the target group head device include handover completion message 1 sent by terminal device 1, handover completion message 2 sent by terminal device 2, and handover completion message 3 sent by terminal device 3.

[0274] In summary, the method provided in this embodiment enables terminal devices to switch from a source macro domain to a target micro domain based on a group. Furthermore, the target group head device can directly manage the mobility of the terminal device without the involvement of the target macro node device, which helps reduce the complexity of successfully switching the terminal device from the source macro domain to the target micro domain.

[0275] For implementation scenario four:

[0276] Figure 12 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more terminal devices, a source macro node device, and a target macro node device to enable one or more terminal devices to switch from a source macro domain to a target macro domain. The method includes:

[0277] Operation 61: The source macro node device sends a measurement configuration message to one or more terminal devices;

[0278] In this embodiment, the source macro node device can be understood as a source macro domain device within a source macro domain. The terminal device can be understood as a source macro domain terminal device within a source macro domain.

[0279] In some embodiments, a measurement configuration message is used to indicate the measurement configuration of one or more terminal devices. Optionally, the measurement configuration includes at least one of a measurement identifier, a reference signal, a measurement quantity, and a measurement event. The measurement configuration indicated by the measurement configuration message is configured for all or some of the terminal devices in the source macro domain. For example, assuming that the source macro domain includes terminal device 1 and terminal device 2, the measurement configuration message sent by the source macro node device may be for both terminal device 1 and terminal device 2, or it may be for only terminal device 1 or terminal device 2.

[0280] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in terminal-specific signaling. Optionally, the dedicated measurement configuration is sent via RRC dedicated signaling or a MAC control element (MAC CE).

[0281] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple terminal devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0282] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration adopted by the single terminal device in the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to terminal device 1, used to indicate that the measurement configuration of terminal device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to terminal device 2, used to indicate that the measurement configuration of terminal device 2 is measurement configuration 2 and measurement configuration 3.

[0283] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device. For example, the common measurement configuration includes a measurement configuration 2 shared by terminal device 1 and terminal device 2. The dedicated measurement configuration includes a measurement configuration 1 proprietary to terminal device 1 and a measurement configuration 3 proprietary to terminal device 2.

[0284] When there are enough common measurement configurations for multiple terminal devices, indicating the complete set of measurement configurations for multiple terminal devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both terminal device 1 and terminal device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configurations.

[0285] Operation 62: One or more terminal devices receive measurement configuration messages sent by the source macro node device;

[0286] In some embodiments, one or more terminal devices receive a measurement configuration from a measurement configuration message sent by a source macro node device, and perform measurements based on the corresponding measurement configuration to generate measurement results. These measurement results are obtained based on the measurement configuration.

[0287] Operation 63: One or more terminal devices report measurement results to the source macro node device;

[0288] In some embodiments, one or more terminal devices report measurement results to the source macro node device based on the reporting configuration. Optionally, the measurement results include at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate macro domain network.

[0289] In some embodiments, each terminal device reports measurement results to the source macro node device based on its reporting configuration. For example, assuming terminal device 1 and terminal device 2 are included, the measurement results include measurement result 1 reported by terminal device 1 to the source macro node device based on its reporting configuration, and measurement result 2 reported by terminal device 2 to the source macro node device based on its reporting configuration. There is a one-to-one correspondence between the terminal devices and the measurement results.

[0290] Operation 64: The source macro node device receives measurement results reported by one or more terminal devices;

[0291] In some embodiments, the source macro node device receives measurement results reported by one or more terminal devices and determines a target macro domain from at least one candidate macro domain network based on the measurement results. The target macro domain is the macro domain network to which one or more terminal devices will switch.

[0292] In some embodiments, the source macrodomain and the target macrodomain are different.

[0293] Operation 65: The source macro node device sends a fourth handover request to the target macro node device;

[0294] In some embodiments, when the source macro node device determines the target macro domain, the source macro node device sends a fourth handover request to the target macro node device.

[0295] In some embodiments, the target macro node device can be understood as the target macro domain device in the target macro domain.

[0296] In some embodiments, the fourth handover request is used to request the handover of one or more terminal devices from the source macro domain to the target macro domain.

[0297] In some embodiments, the fourth switching request is sent via a direct connection interface between macro node devices.

[0298] In some embodiments, the fourth handover request carries the identifiers of one or more terminal devices. This identifier helps identify the terminal device requiring a handover when multiple terminal devices are included. For example, suppose the source macrodomain includes terminal device 1, terminal device 2, and terminal device 3. If the fourth handover request carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal device 1 and terminal device 2 need to be switched, while terminal device 3 does not need to be switched.

[0299] Operation 66: The target macro node device receives the fourth handover request sent by the source macro node device;

[0300] In some embodiments, the target macro node device receives a fourth handover request sent by the source macro node device, and performs access control on one or more terminal devices based on the fourth handover request.

[0301] Operation 67: The target macro node device sends a fourth handover request confirmation to the source macro node device;

[0302] In some embodiments, the target macro node device sends a fourth handover request confirmation to the source macro node device based on the received fourth handover request. The fourth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0303] In some embodiments, the fourth handover request confirmation is sent via a direct connection interface between macro node devices.

[0304] In some embodiments, the fourth handover request confirmation carries the identifiers of one or more terminal devices. This identifier helps identify the terminal devices that can perform the handover when multiple terminal devices are included. For example, suppose the fourth handover request requests a handover of terminal devices 1, 2, and 3. If the fourth handover request confirmation carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal devices 1 and 2 can perform the handover, while terminal device 3 cannot.

[0305] Operation 68: The source macro node device receives confirmation of the fourth handover request sent by the target macro node device;

[0306] In some embodiments, the source macro node device receives a fourth handover request confirmation from the target macro node device, and sends a handover command to one or more terminal devices based on the fourth handover request confirmation.

[0307] Operation 69: The source macro node device sends a handover command to one or more terminal devices;

[0308] In some embodiments, the switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain.

[0309] In some embodiments, the source macro node device sends a handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes the information required for the handover.

[0310] In some embodiments, the handover command is a common handover command, which is broadcast to multiple terminal devices in system messages. When the handover command is directed to multiple terminal devices simultaneously, broadcasting the handover command to multiple terminal devices in system messages helps to save signaling overhead.

[0311] In some embodiments, the handover command is a dedicated handover command, which is sent individually to each terminal device via dedicated RRC signaling.

[0312] Operation 70: One or more terminal devices receive a handover command sent by the source macro node device;

[0313] In some embodiments, one or more terminal devices receive a handover command and determine, based on the handover command, whether to switch the RRC connection to the target macro node device. If it is determined that the RRC connection to the target macro node device should be switched, the following operations continue to be performed.

[0314] In some embodiments, each terminal device receives its corresponding handover command and determines whether to switch the RRC connection to the target macro node device based on the corresponding handover command. For example, assuming terminal device 1 receives a handover command, terminal device 1 determines whether to switch the RRC connection to the target macro node device based on the received handover command.

[0315] Operation 71: One or more terminal devices switch their RRC connection to the target macro node device;

[0316] In some embodiments, one or more terminal devices switch the RRC connection from the source macro node device to the target macro node device according to the received switching command.

[0317] In some embodiments, each terminal device switches its RRC connection to the target macro node device. For example, assuming that terminal device 1, terminal device 2, and terminal device 3 all receive a switching command, then terminal device 1, terminal device 2, and terminal device 3 respectively switch their RRC connections to the target macro node device.

[0318] Operation 72: One or more terminal devices send a handover completion message to the target macro node device;

[0319] In some embodiments, after one or more terminal devices complete the RRC connection handover, a handover completion message is sent to the target macro node device. The handover completion message indicates that the RRC connection of one or more terminal devices has been switched to the target macro node device.

[0320] In some embodiments, each terminal device sends a handover completion message to the target macro node device. For example, suppose terminal device 1, terminal device 2, and terminal device 3 respectively switch their RRC connections to the target macro node device. Then, terminal device 1, terminal device 2, and terminal device 3 respectively send handover completion message 1, handover completion message 2, and handover completion message 3 to the target macro node device.

[0321] Operation 73: The target macro node device receives a handover completion message from one or more terminal devices.

[0322] In some embodiments, when the target macro node device receives a handover completion message from one or more terminal devices, it indicates that one or more terminal devices have successfully established an RRC connection with the target macro node device. At this point, one or more terminal devices have successfully handover from the source macro domain to the target macro domain.

[0323] In some embodiments, the target group head device receives handover completion messages from all terminal devices that have switched their RRC connections from the source macro node device to the target macro node device. For example, assuming terminal device 1, terminal device 2, and terminal device 3 have switched their RRC connections to the target macro node device, the handover completion messages received by the target macro node device include handover completion message 1 sent by terminal device 1, handover completion message 2 sent by terminal device 2, and handover completion message 3 sent by terminal device 3.

[0324] In summary, the method provided in this embodiment enables the terminal device to switch from the source macro domain to the target macro domain based on the group.

[0325] For implementation scenario five:

[0326] Figure 13 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more terminal devices, a source macro node device, a target group head device, and a target macro node device to enable one or more terminal devices to switch from a source macro domain to a target micro domain. The method includes:

[0327] Operation 81: The source macro node device sends a measurement configuration message to one or more terminal devices;

[0328] In this embodiment, the source macro node device can be understood as a source macro domain device within a source macro domain. The terminal device can be understood as a source macro domain terminal device within a source macro domain.

[0329] In some embodiments, a measurement configuration message is used to indicate the measurement configuration of one or more terminal devices. Optionally, the measurement configuration includes at least one of a measurement identifier, a reference signal, a measurement quantity, and a measurement event. The measurement configuration indicated by the measurement configuration message is configured for all or some of the terminal devices in the source macro domain. For example, assuming that the source macro domain includes terminal device 1 and terminal device 2, the measurement configuration message sent by the source macro node device may be for both terminal device 1 and terminal device 2, or it may be for only terminal device 1 or terminal device 2.

[0330] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in terminal-specific signaling. Optionally, the dedicated measurement configuration is sent via RRC dedicated signaling or a MAC control element (MAC CE).

[0331] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple terminal devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0332] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration adopted by the single terminal device in the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to terminal device 1, used to indicate that the measurement configuration of terminal device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to terminal device 2, used to indicate that the measurement configuration of terminal device 2 is measurement configuration 2 and measurement configuration 3.

[0333] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device. For example, the common measurement configuration includes a measurement configuration 2 shared by terminal device 1 and terminal device 2. The dedicated measurement configuration includes a measurement configuration 1 proprietary to terminal device 1 and a measurement configuration 3 proprietary to terminal device 2.

[0334] When there are enough common measurement configurations for multiple terminal devices, indicating the complete set of measurement configurations for multiple terminal devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both terminal device 1 and terminal device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configurations.

[0335] Operation 82: One or more terminal devices receive measurement configuration messages sent by the source macro node device;

[0336] In some embodiments, one or more terminal devices receive a measurement configuration from a measurement configuration message sent by a source macro node device, and perform measurements based on the corresponding measurement configuration to generate measurement results. These measurement results are obtained based on the measurement configuration.

[0337] Operation 83: One or more terminal devices report measurement results to the source macro node device;

[0338] In some embodiments, one or more terminal devices report measurement results to the source macro node device based on the reporting configuration. Optionally, the measurement results include at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate micro-domain network.

[0339] In some embodiments, each terminal device reports measurement results to the source macro node device based on its reporting configuration. For example, assuming terminal device 1 and terminal device 2 are included, the measurement results include measurement result 1 reported by terminal device 1 to the source macro node device based on its reporting configuration, and measurement result 2 reported by terminal device 2 to the source macro node device based on its reporting configuration. There is a one-to-one correspondence between the terminal devices and the measurement results.

[0340] Operation 84: The source macro node device receives measurement results reported by one or more terminal devices;

[0341] In some embodiments, the source macro node device receives measurement results reported by one or more terminal devices and determines a target microdomain from at least one candidate microdomain network based on the measurement results. The target microdomain is the microdomain network to which one or more terminal devices will switch.

[0342] In some embodiments, the macrodomain networks corresponding to the source macrodomain and the target microdomain are the same. Alternatively, the macrodomain networks corresponding to the source macrodomain and the target microdomain are different.

[0343] Operation 85: The source macro node device sends a fifth handover request to the target macro node device;

[0344] In some embodiments, when the source macro node device determines the target micro domain, the source macro node device sends a fifth handover request to the target macro node device.

[0345] In some embodiments, the fifth handover request is used to request the handover of one or more terminal devices from the source macro domain to the target micro domain.

[0346] In some embodiments, the fifth switching request is sent via a direct connection interface between macro node devices.

[0347] In some embodiments, the fifth handover request carries the identifiers of one or more terminal devices. This identifier helps identify the terminal device requiring a handover when multiple terminal devices are included. For example, suppose the source macrodomain includes terminal device 1, terminal device 2, and terminal device 3. If the fifth handover request carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal device 1 and terminal device 2 need to be switched, while terminal device 3 does not need to be switched.

[0348] Operation 86: The target macro node device receives the fifth handover request sent by the source macro node device;

[0349] In some embodiments, the target macro node device receives a fifth handover request sent by the source macro node device, and performs access control on one or more terminal devices based on the fifth handover request.

[0350] Operation 87: The target macro node device sends a fifth handover request confirmation to the source macro node device;

[0351] In some embodiments, the target macro node device sends a fifth handover request confirmation to the source macro node device based on the received fifth handover request. The fifth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0352] In some embodiments, the fifth handover request confirmation is sent via a direct connection interface between macro node devices.

[0353] In some embodiments, the fifth handover request confirmation carries the identifiers of one or more terminal devices. This identifier helps identify the terminal devices that can perform the handover when multiple terminal devices are included. For example, suppose the fifth handover request requests a handover of terminal devices 1, 2, and 3. If the fifth handover request confirmation carries identifier 1 for terminal device 1 and identifier 2 for terminal device 2, it indicates that terminal devices 1 and 2 can perform the handover, while terminal device 3 cannot.

[0354] Operation 88: The source macro node device receives confirmation of the fifth handover request sent by the target macro node device;

[0355] In some embodiments, the source macro node device receives a fifth handover request confirmation from the target macro node device, and sends a handover command to one or more terminal devices based on the fifth handover request confirmation.

[0356] Operation 89: The source macro node device sends a handover command to one or more terminal devices;

[0357] In some embodiments, the switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain.

[0358] In some embodiments, the source macro node device sends a handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes the information required for the handover.

[0359] In some embodiments, the handover command is a common handover command, which is broadcast to multiple terminal devices in system messages. When the handover command is directed to multiple terminal devices simultaneously, broadcasting the handover command to multiple terminal devices in system messages helps to save signaling overhead.

[0360] In some embodiments, the handover command is a dedicated handover command, which is sent individually to each terminal device via dedicated RRC signaling.

[0361] Operation 90: One or more terminal devices receive a handover command sent by the source macro node device;

[0362] In some embodiments, one or more terminal devices receive a handover command and determine, based on the handover command, whether to switch the RRC connection to the target macro node device. If it is determined that the RRC connection to the target macro node device should be switched, the following operations continue to be performed.

[0363] In some embodiments, each terminal device receives its corresponding handover command and determines whether to switch the RRC connection to the target group head device based on the corresponding handover command. For example, assuming terminal device 1 receives a handover command, terminal device 1 determines whether to switch the RRC connection to the target macro node device based on the received handover command.

[0364] Operation 91: One or more terminal devices switch their RRC connection to the target macro node device;

[0365] In some embodiments, one or more terminal devices switch the RRC connection from the source macro node device to the target macro node device according to the received switching command.

[0366] In some embodiments, each terminal device switches its RRC connection to the target macro node device. For example, assuming that terminal device 1, terminal device 2, and terminal device 3 all receive a switching command, then terminal device 1, terminal device 2, and terminal device 3 respectively switch their RRC connections to the target macro node device.

[0367] Operation 92: One or more terminal devices send a second handover completion message to the target group head device;

[0368] In some embodiments, after one or more terminal devices complete an RRC connection handover, a second handover completion message is sent to the target group head device. The second handover completion message indicates that the RRC connection of one or more terminal devices has been switched to the target macro node device.

[0369] In some embodiments, the target group head device is a device that manages one or more member devices in a target microdomain. Optionally, the target group head device is an end device. Optionally, the target group head device is a network device.

[0370] Operation 93: The target group head device receives a second handover completion message sent by one or more terminal devices;

[0371] In some embodiments, when the target group head device receives a second handover completion message from one or more terminal devices, it indicates that one or more terminal devices have successfully established an RRC connection with the target macro node device.

[0372] Operation 94: The target group head device sends the first handover completion message to the target macro node device;

[0373] In some embodiments, the target group head device aggregates the second handover completion messages sent by one or more terminal devices to obtain a first handover completion message. Alternatively, the first handover completion message may be understood as including one or more second handover completion messages corresponding to one or more terminal devices.

[0374] Operation 95: The target macro node device receives the first handover completion message sent by the target group head device.

[0375] In some embodiments, when the target macro node device receives a first handover completion message, it indicates that one or more terminal devices have successfully established an RRC connection with the target macro node device. At this point, one or more terminal devices have successfully switched from the source macro domain to the target micro domain.

[0376] In summary, the method provided in this embodiment has the RRC connection anchor point of the terminal device on the macro node device, which means that the mobility management of the terminal device requires the participation of the macro node device. By summarizing one or more second handover completion messages into a first handover completion message through the target group head device, the mobility management pressure of the macro node device is shared by the group head device, which is conducive to improving the overall network mobility management efficiency.

[0377] For implementation scenario six:

[0378] Figure 14 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more member devices, a source group head device, a source macro node device, and a target macro node device to enable one or more member devices to switch from a source micro domain to a target macro domain. The method includes:

[0379] Operation 201: The source macro node device sends the first measurement configuration message to the source group head device;

[0380] In some embodiments, the source group head device is a device that manages one or more member devices in a source microdomain. Optionally, both the source group head device and the member devices are terminal devices. Optionally, the source group head device is a network device, and the member devices are terminal devices.

[0381] In this embodiment, the source macro node device can be understood as a source macro domain device within a source macro domain. The source macro domain is the macro domain network corresponding to the source micro domain. The source group head device can be understood as a source micro domain macro node device within a source micro domain.

[0382] In some embodiments, the first measurement configuration message is used to indicate the measurement configuration of the source group head device. And / or, the first measurement configuration message is used to indicate the measurement configuration of one or more group member devices. That is, the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0383] In some embodiments, if the first measurement configuration message is for a source group head device, the following operation is not performed. The source group head device is equivalent to the terminal device in the embodiments shown in FIG11 or FIG12 above, and can switch from the source macro domain to the target micro domain or from the source macro domain to the target macro domain. Further details are omitted here.

[0384] In this embodiment of the application, an example is given where the first measurement configuration message is for all or some of the group member devices.

[0385] In some embodiments, the first measurement configuration message carries an identifier for one or more member devices. This identifier helps distinguish between multiple member devices in the case of multiple member devices.

[0386] Operation 202: The source group head device receives the first measurement configuration message sent by the source group head device;

[0387] In some embodiments, the source group head device generates a second measurement configuration message based on the received first measurement configuration message.

[0388] Operation 203: The source group head device sends a second measurement configuration message to one or more group member devices;

[0389] In this embodiment of the application, the member device can be understood as the source microdomain terminal device in the source microdomain.

[0390] In some embodiments, the second measurement configuration message is used to indicate the measurement configuration of one or more member devices. The measurement configuration indicated by the second measurement configuration message is configured for all or some of the member devices in the source microdomain. For example, assuming that the source microdomain includes member device 1 and member device 2, the second measurement configuration message sent by the source group head device may be for both member device 1 and member device 2, or it may be for only member device 1 or member device 2.

[0391] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a private measurement configuration. The common measurement configuration is broadcast to multiple member devices via a system message, while the private measurement configuration is sent individually to each member device via terminal-specific signaling. Optionally, the private measurement configuration is sent via RRC private signaling or a MAC control element (MAC CE).

[0392] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple member devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0393] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single member device, used to indicate the measurement configuration used by the single member device within the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to member device 1, used to indicate that the measurement configuration of member device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to member device 2, used to indicate that the measurement configuration of member device 2 is measurement configuration 2 and measurement configuration 3.

[0394] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple member devices, and a dedicated measurement configuration includes a dedicated portion of the measurement configuration of a single member device. For example, the common measurement configuration includes a measurement configuration 2 shared by member device 1 and member device 2. The dedicated measurement configuration includes a measurement configuration 1 dedicated to member device 1 and a measurement configuration 3 dedicated to member device 2.

[0395] When there are enough common measurement configurations for multiple member devices, indicating the complete set of measurement configurations for multiple member devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both member device 1 and member device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configuration.

[0396] Operation 204: One or more member devices receive a second measurement configuration message sent by the source group head device;

[0397] In some embodiments, one or more member devices receive a measurement configuration from a second measurement configuration message sent by a source group head device, and perform measurements based on the corresponding measurement configuration to generate a second measurement result. This second measurement result is obtained based on the measurement configuration.

[0398] Operation 205: One or more member devices report a second measurement result to the source group head device;

[0399] In some embodiments, one or more member devices report a second measurement result to the source group head device based on a reporting configuration. Optionally, the second measurement result includes at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate macro domain network.

[0400] Operation 206: The source group head device receives the second measurement result reported by one or more member devices;

[0401] In some embodiments, the source group head device receives a second measurement result reported by one or more group member devices, and the source group head device generates a first measurement result based on the received second measurement result.

[0402] Operation 207: The source group head device sends the first measurement result to the source macro node device;

[0403] In some embodiments, the first measurement result includes the second measurement result of all or some of the group member devices. And / or, the first measurement result includes the third measurement result of the source group head device.

[0404] In some embodiments, the first measurement result further includes an identifier corresponding to each second measurement result, and / or an identifier corresponding to each third measurement result.

[0405] Operation 208: The source macro node device receives the first measurement result sent by the source group head device;

[0406] In some embodiments, the source macro node device determines a target macro domain from at least one candidate macro domain network based on the first measurement result. The target macro domain is the macro domain network to which one or more member devices will switch.

[0407] In some embodiments, the macro domain network corresponding to the source micro domain is the same as the target macro domain. Alternatively, the macro domain network corresponding to the source micro domain is different from the target macro domain.

[0408] Operation 209: The source macro node device sends a sixth handover request to the target macro node device;

[0409] In some embodiments, if the source macro node device determines the target macro domain, the source macro node device sends a sixth handover request to the target macro node device.

[0410] In some embodiments, the target macro node device can be understood as the target macro domain device in the target macro domain.

[0411] In some embodiments, the sixth handover request is used to request the handover of one or more member devices from the source microdomain to the target macrodomain.

[0412] In some embodiments, the sixth switching request is sent via a direct connection interface between macro node devices.

[0413] In some embodiments, the sixth handover request carries identifiers of one or more member devices. This identifier helps identify the member device requiring a handover when multiple member devices are included. For example, suppose the source microdomain includes member device 1, member device 2, and member device 3. If the sixth handover request carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 need to be switched, while member device 3 does not need to be switched.

[0414] Operation 210: The target macro node device receives the sixth handover request sent by the source macro node device;

[0415] In some embodiments, the target macro node device receives a sixth handover request sent by the source macro node device, and performs access control on one or more member devices based on the sixth handover request.

[0416] Operation 211: The target macro node device sends a sixth handover request confirmation to the source macro node device;

[0417] In some embodiments, the target macro node device sends a sixth handover request acknowledgment to the source macro node device based on the received sixth handover request. The sixth handover request acknowledgment is a handover request acknowledgment for one or more member devices.

[0418] In some embodiments, the sixth handover request confirmation is sent via a direct connection interface between macro node devices.

[0419] In some embodiments, the sixth handover request confirmation carries the identifiers of one or more member devices. This identifier helps identify member devices that can perform the handover when multiple member devices are included. For example, suppose the sixth handover request requests a handover of member device 1, member device 2, and member device 3. If the sixth handover request confirmation carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 can perform the handover, while member device 3 cannot perform the handover.

[0420] Operation 212: The source macro node device receives confirmation of the sixth handover request sent by the target macro node device;

[0421] In some embodiments, the source macro node device receives a sixth handover request confirmation from the target macro node device and sends a first handover command to the source group head device based on the sixth handover request confirmation.

[0422] Operation 213: The source macro node device sends the first switching command to the source group head device;

[0423] In some embodiments, when a first switching command is used to trigger a switching of the source group head device, the first switching command carries the identifier of the source group head device.

[0424] In some embodiments, when a first switching command is used to trigger a switching of one or more member devices, the first switching command carries the identifiers of one or more member devices.

[0425] That is, the first switching command carries the identifiers of the active group head device and / or one or more group member devices to indicate the device that needs to perform the switching.

[0426] Operation 214: The source group head device receives the first handover command sent by the source macro node device;

[0427] In some embodiments, when the first switching command is used to trigger the source group head device to switch, the source group head device is equivalent to the terminal device in the embodiments shown in FIG11 or FIG12 above, and can realize switching from the source macro domain to the target micro domain or from the source macro domain to the target macro domain. Further details will not be elaborated here.

[0428] In this embodiment, an example is given where a first switching command is used to trigger a switching of one or more member devices. The first switching command is used to generate a second switching command, which is a switching command for one or more member devices.

[0429] Operation 215: The source group head device sends a second handover command to one or more group member devices;

[0430] In some embodiments, the second switching command is used to trigger one or more member devices to switch from the source microdomain to the target macrodomain.

[0431] In some embodiments, the source group head device sends a second handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes information required for the handover.

[0432] In some embodiments, the second handover command is a common second handover command, which is broadcast to multiple member devices in a system message. When the second handover command is directed to multiple member devices simultaneously, broadcasting the second handover command to multiple member devices in a system message helps to save signaling overhead.

[0433] In some embodiments, the second handover command is a dedicated second handover command, which is sent individually to each member device via dedicated RRC signaling.

[0434] Operation 216: One or more member devices receive a second handover command sent by the source group head device;

[0435] In some embodiments, one or more member devices receive a second handover command and determine, based on the second handover command, whether to switch the RRC connection to the target macro node device. If it is determined that the RRC connection to the target macro node device should be switched, the following operations continue to be performed.

[0436] Operation 217: One or more member devices switch their RRC connection to the target macro node device;

[0437] In some embodiments, one or more member devices switch the RRC connection from the source group head device to the target macro node device according to the received second handover command.

[0438] Operation 218: One or more member devices send a handover completion message to the target macro node device;

[0439] In some embodiments, after one or more member devices complete the RRC connection handover, a handover completion message is sent to the target macro node device. The handover completion message indicates that the RRC connection of one or more member devices has been switched to the target macro node device.

[0440] Operation 219: The target macro node device receives a handover completion message from one or more member devices.

[0441] In some embodiments, when the target macro node device receives a handover completion message from one or more member devices, it indicates that one or more member devices have successfully established an RRC connection with the target macro node device. At this point, one or more member devices have successfully handed over from the source micro domain to the target macro domain.

[0442] In summary, the method provided in this embodiment, where the RRC connection anchor point of the terminal device is on the macro node device, means that the mobility management of the terminal device requires the participation of the macro node device. By sending a first measurement configuration message from the source macro node device to the source group head device, enabling the source group head device to further generate a second measurement configuration message, and by sending a first handover command from the source macro node device to the source group head device, enabling the source group head device to further generate a second handover command, the mobility management burden on the macro node device can be shared by the group head device, which is beneficial to improving the overall mobility management efficiency of the network.

[0443] For implementation scenario seven:

[0444] Figure 15 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is jointly executed by one or more member devices, a source group head device, a source macro node device, a target group head device, and a target macro node device, for enabling one or more member devices to switch from a source microdomain to a target microdomain. The method includes:

[0445] Operation 221: The source macro node device sends the first measurement configuration message to the source group head device;

[0446] In some embodiments, the source group head device is a device that manages one or more member devices in a source microdomain. Optionally, both the source group head device and the member devices are terminal devices. Optionally, the source group head device is a network device, and the member devices are terminal devices.

[0447] In this embodiment, the source macro node device can be understood as a source macro domain device within a source macro domain. The source macro domain is the macro domain network corresponding to the source micro domain. The source group head device can be understood as a source micro domain macro node device within a source micro domain.

[0448] In some embodiments, the first measurement configuration message is used to indicate the measurement configuration of the source group head device. And / or, the first measurement configuration message is used to indicate the measurement configuration of one or more group member devices. That is, the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0449] In some embodiments, if the first measurement configuration message is for a source group head device, the following operation is not performed. The source group head device is equivalent to the terminal device in the embodiments shown in FIG11 or FIG12 above, and can switch from the source macro domain to the target micro domain or vice versa. Further details are omitted here.

[0450] In this embodiment of the application, an example is given where the first measurement configuration message is for all or some of the group member devices.

[0451] In some embodiments, the first measurement configuration message carries an identifier for one or more member devices. This identifier helps distinguish between multiple member devices in the case of multiple member devices.

[0452] Operation 222: The source group head device receives the first measurement configuration message sent by the source group head device;

[0453] In some embodiments, the source group head device generates a second measurement configuration message based on the received first measurement configuration message.

[0454] Operation 223: The source group head device sends a second measurement configuration message to one or more group member devices;

[0455] In this embodiment of the application, the member device can be understood as the source microdomain terminal device in the source microdomain.

[0456] In some embodiments, the second measurement configuration message is used to indicate the measurement configuration of one or more member devices. The measurement configuration indicated by the second measurement configuration message is configured for all or some of the member devices in the source microdomain. For example, assuming that the source microdomain includes member device 1 and member device 2, the second measurement configuration message sent by the source group head device may be for both member device 1 and member device 2, or it may be for only member device 1 or member device 2.

[0457] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a private measurement configuration. The common measurement configuration is broadcast to multiple member devices via a system message, while the private measurement configuration is sent individually to each member device via terminal-specific signaling. Optionally, the private measurement configuration is sent via RRC private signaling or a MAC control element (MAC CE).

[0458] In some embodiments, the common measurement configuration includes the complete set of measurement configurations for multiple member devices, each measurement configuration having its own measurement identifier. For example, suppose the common measurement configuration includes measurement configuration 1, measurement configuration 2, and measurement configuration 3. Measurement configuration 1 corresponds to measurement identifier 1, measurement configuration 2 corresponds to measurement identifier 2, and measurement configuration 3 corresponds to measurement identifier 3.

[0459] In some embodiments, a dedicated measurement configuration includes a measurement identifier corresponding to a single member device, used to indicate the measurement configuration used by the single member device within the complete set of measurement configurations. For example, the dedicated measurement configuration includes measurement identifier 1 and measurement identifier 2 corresponding to member device 1, used to indicate that the measurement configuration of member device 1 is measurement configuration 1 and measurement configuration 2. The dedicated measurement configuration also includes measurement identifier 2 and measurement identifier 3 corresponding to member device 2, used to indicate that the measurement configuration of member device 2 is measurement configuration 2 and measurement configuration 3.

[0460] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple member devices, and a dedicated measurement configuration includes a dedicated portion of the measurement configuration of a single member device. For example, the common measurement configuration includes a measurement configuration 2 shared by member device 1 and member device 2. The dedicated measurement configuration includes a measurement configuration 1 dedicated to member device 1 and a measurement configuration 3 dedicated to member device 2.

[0461] When there are enough common measurement configurations for multiple member devices, indicating the complete set of measurement configurations for multiple member devices, as well as the corresponding measurement identifiers, through common measurement configurations can help save signaling overhead. For example, when both member device 1 and member device 2 correspond to measurement configuration 2, measurement configuration 2 can be configured only once through common measurement configuration.

[0462] Operation 224: One or more member devices receive a second measurement configuration message sent by the source group head device;

[0463] In some embodiments, one or more member devices receive a measurement configuration from a second measurement configuration message sent by a source group head device, and perform measurements based on the corresponding measurement configuration to generate a second measurement result. This second measurement result is obtained based on the measurement configuration.

[0464] Operation 225: One or more member devices report a second measurement result to the source group head device;

[0465] In some embodiments, one or more member devices report a second measurement result to the source group head device based on a reporting configuration. Optionally, the second measurement result includes at least one of RSRP, RSRQ, and SINR corresponding to at least one candidate macro domain network.

[0466] Operation 226: The source group head device receives the second measurement result reported by one or more member devices;

[0467] In some embodiments, the source group head device receives a second measurement result reported by one or more group member devices, and the source group head device generates a first measurement result based on the received second measurement result.

[0468] Operation 227: The source group head device sends the first measurement result to the source macro node device;

[0469] In some embodiments, the first measurement result includes the second measurement result of all or some of the group member devices. And / or, the first measurement result includes the third measurement result of the source group head device.

[0470] In some embodiments, the first measurement result further includes an identifier corresponding to each second measurement result, and / or an identifier corresponding to each third measurement result.

[0471] Operation 228: The source macro node device receives the first measurement result sent by the source group head device;

[0472] In some embodiments, the source macro node device determines the target micro domain from at least one candidate macro domain network based on the first measurement result. The target micro domain is the macro domain network to which one or more member devices will switch.

[0473] In some embodiments, the macro-domain network corresponding to the source micro-domain is the same as the target micro-domain. Alternatively, the macro-domain network corresponding to the source micro-domain is different from the target micro-domain.

[0474] Operation 229: The source macro node device sends a seventh handover request to the target macro node device;

[0475] In some embodiments, when the source macro node device determines the target micro domain, the source macro node device sends a seventh handover request to the target macro node device.

[0476] In some embodiments, the seventh handover request is used to request the handover of one or more member devices from the source microdomain to the target microdomain.

[0477] In some embodiments, the seventh switching request is sent via a direct connection interface between macro node devices.

[0478] In some embodiments, the seventh handover request carries identifiers of one or more member devices. These identifiers help identify the member device requiring a handover when multiple member devices are included. For example, suppose the source microdomain includes member device 1, member device 2, and member device 3. If the seventh handover request carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 need to be switched, while member device 3 does not need to be switched.

[0479] Operation 230: The target macro node device receives the seventh handover request sent by the source macro node device;

[0480] In some embodiments, the target macro node device receives a seventh handover request sent by the source macro node device, and performs access control on one or more member devices based on the seventh handover request.

[0481] Operation 231: The target macro node device sends a seventh handover request confirmation to the source macro node device;

[0482] In some embodiments, the target macro node device sends a seventh handover request acknowledgment to the source macro node device based on the received seventh handover request. The seventh handover request acknowledgment is a handover request acknowledgment for one or more member devices.

[0483] In some embodiments, the seventh handover request confirmation is sent via a direct connection interface between macro node devices.

[0484] In some embodiments, the seventh handover request confirmation carries the identifiers of one or more member devices. This identifier helps identify member devices that can perform the handover when multiple member devices are included. For example, suppose the seventh handover request requests a handover of member device 1, member device 2, and member device 3. If the seventh handover request confirmation carries identifier 1 for member device 1 and identifier 2 for member device 2, it indicates that member device 1 and member device 2 can perform the handover, while member device 3 cannot perform the handover.

[0485] Operation 232: The source macro node device receives confirmation of the seventh handover request sent by the target macro node device;

[0486] In some embodiments, the source macro node device receives a seventh handover request confirmation from the target macro node device and sends a first handover command to the source group head device based on the seventh handover request confirmation.

[0487] Operation 233: The source macro node device sends the first switching command to the source group head device;

[0488] In some embodiments, when a first switching command is used to trigger a switching of the source group head device, the first switching command carries the identifier of the source group head device.

[0489] In some embodiments, when a first switching command is used to trigger a switching of one or more member devices, the first switching command carries the identifiers of one or more member devices.

[0490] That is, the first switching command carries the identifiers of the active group head device and / or one or more group member devices to indicate the device that needs to perform the switching.

[0491] Operation 234: The source group head device receives the first handover command sent by the source macro node device;

[0492] In some embodiments, when the first switching command is used to trigger the source group head device to switch, the source group head device is equivalent to the terminal device in the embodiments shown in FIG11 or FIG12 above, and can realize switching from the source macro domain to the target micro domain or from the source macro domain to the target micro domain. Further details will not be elaborated here.

[0493] In this embodiment, an example is given where a first switching command is used to trigger a switching of one or more member devices. The first switching command is used to generate a second switching command, which is a switching command for one or more member devices.

[0494] Operation 235: The source group head device sends a second handover command to one or more group member devices;

[0495] In some embodiments, the second switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0496] In some embodiments, the source group head device sends a second handover command via an RRC Reconfiguration message. The RRC Reconfiguration message includes information required for the handover.

[0497] In some embodiments, the second handover command is a common second handover command, which is broadcast to multiple member devices in a system message. When the second handover command is directed to multiple member devices simultaneously, broadcasting the second handover command to multiple member devices in a system message helps to save signaling overhead.

[0498] In some embodiments, the second handover command is a dedicated second handover command, which is sent individually to each member device via dedicated RRC signaling.

[0499] Operation 236: One or more member devices receive a second handover command sent by the source group head device;

[0500] In some embodiments, one or more member devices receive a second handover command and determine, based on the second handover command, whether to switch the RRC connection to the target macro node device. If it is determined that the RRC connection to the target macro node device should be switched, the following operations continue to be performed.

[0501] Operation 237: One or more member devices switch RRC connection to the target macro node device;

[0502] In some embodiments, one or more member devices switch the RRC connection from the source group head device to the target macro node device according to the received second handover command.

[0503] Operation 238: One or more member devices send a second handover completion message to the target group head device;

[0504] In some embodiments, after one or more member devices complete the RRC connection handover, a second handover completion message is sent to the target macro node device. The second handover completion message is used to indicate that the RRC connection of one or more member devices has been switched to the target macro node device.

[0505] Operation 239: The target group head device receives a second handover completion message from one or more group member devices;

[0506] In some embodiments, when the target group head device receives a second handover completion message from one or more terminal devices, it indicates that one or more group member devices have successfully established an RRC connection with the target macro node device.

[0507] Operation 240: The target group head device sends the first handover completion message to the target macro node device;

[0508] In some embodiments, the target group head device aggregates the second handover completion messages sent by one or more group member devices to obtain a first handover completion message. Alternatively, the first handover completion message can be understood as including one or more second handover completion messages corresponding to one or more group member devices.

[0509] Operation 241: The target macro node device receives the first handover completion message sent by the target group head device.

[0510] In some embodiments, when the target macro node device receives a first handover completion message, it indicates that one or more member devices have successfully established an RRC connection with the target macro node device. At this point, one or more member devices have successfully handed over from the source microdomain to the target microdomain.

[0511] In summary, the method provided in this embodiment, where the RRC connection anchor point of the terminal device is on the macro node device, means that the mobility management of the terminal device requires the participation of the macro node device. By sending a first measurement configuration message from the source macro node device to the source group head device, enabling the source group head device to further generate a second measurement configuration message; by sending a first handover command from the source macro node device to the source group head device, enabling the source group head device to further generate a second handover command; and by summarizing one or more second handover completion messages into a first handover completion message through the target group head device, the mobility management burden on the macro node device can be partially relieved by the group head device, which is beneficial to improving the overall network mobility management efficiency.

[0512] Figure 16 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is performed by a first terminal device. The method includes:

[0513] Operation 320: The first terminal device sends and / or receives signaling related to mobility management.

[0514] In some embodiments, signaling associated with mobility management includes signaling for one or more devices based on a group. In embodiments of this application, mobility management includes at least one of: switching from a source microdomain to a target microdomain, switching from a source microdomain to a target macrodomain, switching from a source macrodomain to a target microdomain, and switching from a source macrodomain to a target macrodomain.

[0515] In some embodiments, signaling related to mobility management includes at least one of the following:

[0516] The switching command sent by the source group head device;

[0517] Switch the RRC connection to the target group head device;

[0518] A handover completion message sent to the target group head device;

[0519] Measurement configuration messages sent by the source group head device;

[0520] Measurement results reported to the source group head device;

[0521] The switching command sent by the source macro node device;

[0522] Switch the RRC connection to the target macro node device;

[0523] A handover completion message sent to the target macro node device;

[0524] The second handover completion message is sent to the target group head device;

[0525] Measurement configuration messages sent by the source macro node device;

[0526] The measurement results reported to the source macro node device;

[0527] The second switching command sent by the source group head device;

[0528] The second measurement configuration message sent by the source group head device;

[0529] The second measurement result reported to the source group head device.

[0530] Example 1: Switching from the source microdomain to the target microdomain;

[0531] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0532] Operation 1-1: Receive the switching command sent by the source group head device. The switching command is used to trigger one or more group member devices to switch from the source microdomain to the target microdomain. The one or more group member devices include the first terminal device.

[0533] For details on the specific implementation method, please refer to Operation 10 above.

[0534] Operation 1-2: Switch the RRC connection to the target group head device according to the switching command, and send a switching completion message to the target group head device.

[0535] For detailed implementation methods, please refer to Operations 11 and 12 above.

[0536] Example 2: Switching from the source micro-domain to the target macro-domain;

[0537] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0538] Operations 1-3: Receive the switching command sent by the source group head device. The switching command is used to trigger one or more group member devices to switch from the source micro domain to the target macro domain. The one or more group member devices include the first terminal device.

[0539] For detailed implementation methods, please refer to operation 30 above.

[0540] Operations 1-4: Switch the RRC connection to the target macro node device according to the switching command, and send a switching completion message to the target macro node device.

[0541] For detailed implementation methods, please refer to operations 31 and 32 above.

[0542] In a further embodiment based on the above-described Embodiment 1 or Embodiment 2, the method further includes:

[0543] Operation 2-1: Receive the measurement configuration message sent by the source group head device; and report the measurement results to the source group head device.

[0544] The measurement configuration message indicates that the measurement configuration is configured for all or some of the group member devices in the source micro-domain, and the measurement result is obtained based on the measurement configuration.

[0545] For detailed implementation methods, please refer to operations 2 and 3 above. Alternatively, for detailed implementation methods, please refer to operations 22 and 23 above.

[0546] Example 3: Switching from the source macro domain to the target micro domain;

[0547] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0548] Operations 1-5: Receive the switching command sent by the source macro node device. The switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain. The one or more terminal devices include the first terminal device.

[0549] For detailed implementation methods, please refer to operation 50 above.

[0550] Operations 1-6: Switch the RRC connection to the target group head device according to the switching command, and send a switching completion message to the target group head device.

[0551] For detailed implementation methods, please refer to operations 51 and 52 above.

[0552] Example 4: Switching from the source macro domain to the target macro domain;

[0553] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0554] Operations 1-7: Receive the handover command sent by the source macro node device. The handover command is used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain. The one or more terminal devices include the first terminal device.

[0555] For detailed implementation methods, please refer to operation 70 above.

[0556] Operations 1-8: Switch the RRC connection to the target macro node device according to the switching command, and send a switching completion message to the target macro node device.

[0557] For detailed implementation methods, please refer to operations 71 and 72 above.

[0558] Example 5: Switching from the source macro domain to the target micro domain;

[0559] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0560] Operations 1-9: Receive the switching command sent by the source macro node device. The switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain. The one or more terminal devices include the first terminal device.

[0561] For detailed implementation methods, please refer to operation 90 above.

[0562] Operations 1-10: Switch the RRC connection to the target macro node device according to the switching command, and send a second switching completion message to the target group head device.

[0563] The second handover completion message is used to be aggregated into the first handover completion message by the target group head device and then sent to the target macro node device.

[0564] For detailed implementation methods, please refer to operations 91 and 92 above.

[0565] In a further embodiment based on Embodiment 3, Embodiment 4, or Embodiment 5 described above, the method further includes:

[0566] Operation 3-1: Receive the measurement configuration message sent by the source macro node device and report the measurement results to the source macro node device.

[0567] The measurement configuration message indicates that the measurement configuration is configured for all or part of the terminal devices in the source macro domain, and the measurement result is obtained based on the measurement configuration.

[0568] For detailed implementation methods, please refer to operations 42 and 23 above. Alternatively, for detailed implementation methods, please refer to operations 62 and 63 above. Alternatively, for detailed implementation methods, please refer to operations 82 and 83 above.

[0569] Example 6: Switching from the source micro-domain to the target macro-domain;

[0570] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0571] Operation 1-11: Receive the second switching command sent by the source group head device. The second switching command is used to trigger one or more group member devices to switch from the source micro domain to the target macro domain. The one or more group member devices include the first terminal device.

[0572] For details on the specific implementation method, please refer to operation 216 above.

[0573] Operations 1-12: Switch the RRC connection to the target macro node device according to the second switching command, and send a switching completion message to the target macro node device.

[0574] The second switching command is generated based on the first switching command, which is sent by the source macro node device to the source group head device.

[0575] For detailed implementation methods, please refer to operations 217 and 218 above.

[0576] Example 7: Switching from the source microdomain to the target microdomain;

[0577] In some embodiments, the above operation 320 can be replaced by the following sub-operations:

[0578] Operation 1-13: Receive the second switching command sent by the source group head device. The second switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain. The one or more member devices include the first terminal device.

[0579] For detailed implementation methods, please refer to operation 236 above.

[0580] Operations 1-14: Switch the RRC connection to the target macro node device according to the second handover command, and send the second handover completion message to the target group head device.

[0581] The second handover command is generated based on the first handover command, which is sent from the source macro node device to the source group head device. The second handover completion message is used by the target group head device to summarize the second handover completion message into the first handover completion message and then send it to the target macro node device.

[0582] For detailed implementation methods, please refer to operations 237 and 238 above.

[0583] In a further embodiment based on Embodiment Six or Embodiment Seven above, the method further includes:

[0584] Operation 4-1: Receive the second measurement configuration message sent by the source group head device; and report the second measurement result to the source group head device, the second measurement result being obtained based on the measurement configuration indicated by the second measurement configuration message.

[0585] The measurement configuration indicated by the second measurement configuration message is configured for all or some of the group member devices. The second measurement configuration message is generated based on the first measurement configuration message. The first measurement configuration message is sent by the source macro node device to the source group head device. The measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0586] For detailed implementation methods, please refer to operations 204 and 205 above. Alternatively, for detailed implementation methods, please refer to operations 224 and 225 above.

[0587] Figure 17 shows a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is performed by a source group head device. The method includes:

[0588] Operation 620: The source group head device sends and / or receives signaling related to mobility management.

[0589] In some embodiments, signaling associated with mobility management includes signaling for one or more devices based on a group. In embodiments of this application, mobility management includes at least one of: switching from a source microdomain to a target microdomain, and switching from a source microdomain to a target macrodomain.

[0590] In some embodiments, signaling related to mobility management includes at least one of the following:

[0591] The first handover request sent to the target group head device;

[0592] Confirmation of the first handover request sent by the target group head device;

[0593] A handover command sent to one or more member devices;

[0594] The second handover request sent to the target macro node device;

[0595] Confirmation of the second handover request sent by the target macro node device;

[0596] Measurement configuration messages sent to all or some of the group members' devices;

[0597] Measurement results reported by all or some of the team members' equipment;

[0598] Example 1: Switching from the source microdomain to the target microdomain;

[0599] In some embodiments, the above operation 620 can be replaced by the following sub-operation:

[0600] Operation 6-1: Send a first handover request to the target group head device. The first handover request is used to request the handover of one or more group member devices from the source microdomain to the target microdomain.

[0601] For detailed implementation methods, please refer to step 5 above.

[0602] Operation 6-2: Receive the first handover request confirmation sent by the target group head device. The first handover request confirmation is for the handover request confirmation of one or more group member devices.

[0603] For detailed implementation methods, please refer to step 8 above.

[0604] Operation 6-3: Send a switching command to one or more member devices. The switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0605] For detailed implementation methods, please refer to operation 9 above.

[0606] Example 2: Switching from the source micro-domain to the target macro-domain;

[0607] In some embodiments, the above operation 620 can be replaced by the following sub-operation:

[0608] Operation 6-4: Send a second handover request to the target macro node device. The second handover request is used to request the handover of one or more member devices from the source micro domain to the target macro domain.

[0609] For detailed implementation methods, please refer to operation 25 above.

[0610] Operation 6-5: Receive the second handover request confirmation sent by the target macro node device. The second handover request confirmation is for the handover request confirmation of one or more member devices.

[0611] For detailed implementation methods, please refer to operation 28 above.

[0612] Operation 6-6: Send a switching command to one or more member devices. The switching command is used to trigger one or more member devices to switch from the source micro domain to the target macro domain.

[0613] For detailed implementation methods, please refer to operation 29 above.

[0614] In a further embodiment based on the above-described Embodiment 1 or Embodiment 2, the method further includes:

[0615] Operation 7-1: Send measurement configuration messages to all or some of the team members' devices; and receive measurement results reported by all or some of the team members' devices.

[0616] The measurement results are obtained based on the measurement configuration indicated by the measurement configuration message.

[0617] For detailed implementation methods, please refer to operations 1 and 4 above. Alternatively, for detailed implementation methods, please refer to operations 24 and 25 above.

[0618] Example 3: Switching from the source micro-domain to the target macro-domain;

[0619] In some embodiments, the above operation 620 can be replaced by the following sub-operation:

[0620] Operation 6-7: Receive the first switching command sent by the source macro node device. The first switching command is used to trigger the source group head device and / or one or more group member devices to switch from the source micro domain to the target macro domain.

[0621] For details on the specific implementation method, please refer to operation 214 above.

[0622] Operation 6-8-1: If the first switching command triggers a source group head device switch, then switch the RRC connection to the target macro node device according to the first switching command;

[0623] Operation 6-8-2: If the first switching command triggers a switching of one or more member devices, then a second switching command is sent to one or more member devices. The second switching command is used to trigger one or more member devices to switch from the source micro domain to the target macro domain.

[0624] For details on the specific implementation method, please refer to operation 215 above.

[0625] Example 4: Switching from the source microdomain to the target microdomain;

[0626] In some embodiments, the above operation 620 can be replaced by the following sub-operation:

[0627] Operation 6-9: Receive the first switching command sent by the source macro node device. The first switching command is used to trigger the source group head device and / or one or more group member devices to switch from the source micro domain to the target micro domain.

[0628] For detailed implementation methods, please refer to operation 234 above.

[0629] Operation 6-10-1: If the first switching command triggers a source group head device switch, then switch the RRC connection to the target macro node device according to the first switching command;

[0630] Operation 6-10-2: If the first switching command triggers a switching of one or more member devices, then a second switching command is sent to one or more member devices. The second switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0631] For details on the specific implementation method, please refer to operation 235 above.

[0632] In a further embodiment based on Embodiment 3 or Embodiment 4 above, the method further includes:

[0633] Operation 8-1: Receive the first measurement configuration message sent by the source macro node device;

[0634] For detailed implementation methods, please refer to operation 202 above. Or, for detailed implementation methods, please refer to operation 222 above.

[0635] Operation 8-2: Send a second measurement configuration message to all or some of the team member devices. The second measurement configuration message is generated based on the first measurement configuration message.

[0636] For detailed implementation methods, please refer to operation 203 above. Or, for detailed implementation methods, please refer to operation 223 above.

[0637] Operation 8-3: Receive the second measurement results of all or part of the group members' devices. The second measurement results are obtained based on the measurement configuration indicated by the second measurement configuration message.

[0638] For detailed implementation methods, please refer to operation 206 above. Or, for detailed implementation methods, please refer to operation 226 above.

[0639] Operation 8-4: Report the first measurement result to the source macro node device. The first measurement result includes the second measurement results of all or some of the group member devices, and / or the third measurement result of the source group head device.

[0640] The first measurement configuration message indicates that the measurement configuration is configured for the source group head device and / or all or some of the group member devices, while the second measurement configuration message indicates that the measurement configuration is configured for all or some of the group member devices.

[0641] For detailed implementation methods, please refer to operation 207 above. Or, for detailed implementation methods, please refer to operation 227 above.

[0642] Figure 18 shows a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is performed by a source macro node device. The method includes:

[0643] Operation 920: The source macro node device sends and / or receives signaling related to mobility management.

[0644] In some embodiments, signaling associated with mobility management includes signaling for one or more devices based on a group. In embodiments of this application, mobility management includes at least one of: switching from a source macro domain to a target micro domain, switching from a source macro domain to a target macro domain, switching from a source micro domain to a target micro domain, and switching from a source micro domain to a target macro domain.

[0645] In some embodiments, signaling related to mobility management includes at least one of the following:

[0646] A third handover request sent to the target group head device;

[0647] Confirmation of the third handover request sent by the target group head device;

[0648] A switching command sent to one or more terminal devices;

[0649] The fourth handover request sent to the target macro node device;

[0650] Confirmation of the fourth handover request sent by the target macro node device;

[0651] The fifth handover request sent to the target macro node device;

[0652] Confirmation of the fifth handover request sent by the target macro node device;

[0653] Measurement configuration messages sent to all or some of the terminal devices;

[0654] Measurement results reported by all or some of the terminal devices;

[0655] The sixth handover request sent to the target macro node device;

[0656] Confirmation of the sixth handover request sent by the target macro node device;

[0657] The first switching command sent to the source group head device;

[0658] The seventh handover request sent to the target macro node device;

[0659] Confirmation of the seventh handover request sent by the target macro node device;

[0660] The first measurement configuration message sent to the source group head device;

[0661] The first measurement result sent by the source head device.

[0662] Example 1: Switching from the source macro domain to the target micro domain;

[0663] In some embodiments, the above operation 920 can be replaced by the following sub-operation:

[0664] Operation 9-1: Send a third handover request to the target group head device. The third handover request is used to request the handover of one or more terminal devices from the source macro domain to the target micro domain.

[0665] For detailed implementation methods, please refer to operation 45 above.

[0666] Operation 9-2: Receive the third handover request confirmation sent by the target group head device. The third handover request confirmation is a handover request confirmation for one or more terminal devices.

[0667] For detailed implementation methods, please refer to operation 48 above.

[0668] Operation 9-3: Send a switching command to one or more terminal devices. The switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain.

[0669] For detailed implementation methods, please refer to operation 49 above.

[0670] Example 2: Switching from the source macro domain to the target macro domain;

[0671] In some embodiments, the above operation 920 can be replaced by the following sub-operation:

[0672] Operation 9-4: Send a fourth handover request to the target macro node device. The fourth handover request is used to request the handover of one or more terminal devices from the source macro domain to the target macro domain.

[0673] For detailed implementation methods, please refer to operation 65 above.

[0674] Operation 9-5: Receive the fourth handover request confirmation sent by the target macro node device. The fourth handover request confirmation is for the handover request confirmation of one or more terminal devices.

[0675] For detailed implementation methods, please refer to operation 68 above.

[0676] Operation 9-6: Send a handover command to one or more terminal devices. The handover command is used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain.

[0677] For detailed implementation methods, please refer to operation 69 above.

[0678] Example 3: Switching from the source macro domain to the target micro domain;

[0679] In some embodiments, the above operation 920 can be replaced by the following sub-operation:

[0680] Operation 9-7: Send the fifth handover request to the target macro node device. The fifth handover request is used to request that one or more terminal devices be switched from the source macro domain to the target micro domain.

[0681] For detailed implementation methods, please refer to operation 85 above.

[0682] Operation 9-8: Receive the fifth handover request confirmation sent by the target macro node device. The fifth handover request confirmation is for the handover request confirmation of one or more terminal devices.

[0683] For detailed implementation methods, please refer to operation 88 above.

[0684] Operation 9-9: Send a handover command to one or more terminal devices. The handover command is used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain.

[0685] For detailed implementation methods, please refer to operation 89 above.

[0686] In a further embodiment based on the above-described Embodiment 1, Embodiment 2, or Embodiment 3, the method further includes:

[0687] Operation 10-1: Send measurement configuration messages to all or some terminal devices; and receive measurement results reported by all or some terminal devices.

[0688] The measurement results are obtained based on the measurement configuration indicated by the measurement configuration message.

[0689] For detailed implementation methods, please refer to operations 41 and 44 above. Alternatively, for detailed implementation methods, please refer to operations 61 and 64 above. Alternatively, for detailed implementation methods, please refer to operations 81 and 84 above.

[0690] Example 4: Switching from the source micro-domain to the target macro-domain;

[0691] In some embodiments, the above operation 920 can be replaced by the following sub-operation:

[0692] Operations 9-10: Send a sixth handover request to the target macro node device. The sixth handover request is used to request the source group head device and / or one or more group member devices to be switched from the source micro domain to the target macro domain.

[0693] For detailed implementation methods, please refer to operation 209 above.

[0694] Operation 9-11: Receive the sixth handover request confirmation sent by the target macro node device. The sixth handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0695] For details on the specific implementation method, please refer to operation 212 above.

[0696] Operation 9-12: Send a first switching command to the source group head device. The first switching command is used to trigger the source group head device and / or one or more group member devices to switch from the source micro domain to the target macro domain.

[0697] For details on the specific implementation method, please refer to operation 213 above.

[0698] Example 5: Switching from the source microdomain to the target microdomain;

[0699] In some embodiments, the above operation 920 can be replaced by the following sub-operation:

[0700] Operation 9-13: Send a seventh handover request to the target macro node device. The seventh handover request is used to request the source group head device and / or one or more group member devices to be switched from the source microdomain to the target microdomain.

[0701] For details on the specific implementation method, please refer to operation 229 above.

[0702] Operation 9-14: Receive the seventh handover request confirmation sent by the target macro node device. The seventh handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0703] For details on the specific implementation method, please refer to operation 232 above.

[0704] Operation 9-15: Send a first switching command to the source group head device. The first switching command is used to trigger the source group head device and / or one or more member devices to switch from the source microdomain to the target microdomain.

[0705] For detailed implementation methods, please refer to operation 233 above.

[0706] In a further embodiment based on Embodiment 4 or Embodiment 5 above, the method further includes:

[0707] Operation 11-1: Send a first measurement configuration message to the source group head device. The measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0708] Operation 11-2: Receive the first measurement result sent by the source group head device, the first measurement result including the second measurement results of all or part of the group member devices, and / or the third measurement result of the source group head device.

[0709] The second measurement result is obtained based on the measurement configuration indicated by the second measurement configuration message, which is generated based on the first measurement configuration message. The measurement configuration indicated by the second measurement configuration message is configured for all or some of the group members' devices.

[0710] For detailed implementation methods, please refer to operations 201 and 208 above. Alternatively, for detailed implementation methods, please refer to operations 221 and 228 above.

[0711] Figure 19 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is performed by a target group head device. The method includes:

[0712] Operation 1220: The target group head device sends and / or receives signaling related to mobility management.

[0713] In some embodiments, signaling associated with mobility management includes signaling for one or more devices based on a group. In embodiments of this application, mobility management includes at least one of: switching from a source microdomain to a target microdomain and switching from a source macrodomain to a target microdomain.

[0714] In some embodiments, signaling related to mobility management includes at least one of the following:

[0715] The first handover request sent by the source group head device;

[0716] Confirmation of the first handover request sent to the source group head device;

[0717] A handover completion message sent by one or more member devices;

[0718] The third handover request sent by the source macro node device;

[0719] Confirmation of the third handover request sent to the source macro node device;

[0720] A second handover completion message for one or more member devices;

[0721] The first handover completion message is sent to the target macro node device.

[0722] Example 1: Switching from the source microdomain to the target microdomain;

[0723] In some embodiments, the above operation 1220 can be replaced by the following sub-operations:

[0724] Operation 12-1: Receive the first handover request sent by the source group head device. The first handover request is used to request the handover of one or more member devices from the source microdomain to the target microdomain.

[0725] For detailed implementation methods, please refer to operation 6 above.

[0726] Operation 12-2: Send the first handover request confirmation to the source group head device. The first handover request confirmation is a handover request confirmation for one or more group member devices.

[0727] For detailed implementation methods, please refer to Operation 7 above.

[0728] Operation 12-3: After establishing an RRC connection with one or more member devices, receive a handover completion message from one or more member devices.

[0729] For details on the specific implementation method, please refer to operation 13 above.

[0730] Example 2: Switching from the source macro domain to the target micro domain;

[0731] In some embodiments, the above operation 1220 can be replaced by the following sub-operations:

[0732] Operation 12-4: Receive the third handover request sent by the source macro node device. The third handover request is used to request the handover of one or more terminal devices from the source macro domain to the target micro domain.

[0733] For detailed implementation methods, please refer to operation 46 above.

[0734] Operation 12-5: Send a third handover request confirmation to the source macro node device. The third handover request confirmation is a handover request confirmation for one or more terminal devices.

[0735] For detailed implementation methods, please refer to operation 47 above.

[0736] Operation 12-6: After establishing an RRC connection with one or more terminal devices, receive a handover completion message from one or more terminal devices.

[0737] For detailed implementation methods, please refer to operation 53 above.

[0738] Example 3: Switching from source microdomain to target microdomain / Switching from source macrodomain to target microdomain;

[0739] In some embodiments, the above operation 1220 can be replaced by the following sub-operations:

[0740] Operation 12-7: Receive the second handover completion message from one or more member devices;

[0741] Operation 12-8: Based on the second handover completion messages from one or more member devices, generate the first handover completion message;

[0742] Operation 12-9: Send the first handover completion message to the target macro node device.

[0743] For detailed implementation methods, please refer to operations 93 and 94 above. Alternatively, for detailed implementation methods, please refer to operations 239 and 240 above.

[0744] Figure 20 illustrates a flowchart of a mobility management method provided in an exemplary embodiment of this application. The method is executed by a target macro node device. The method includes:

[0745] Operation 1320: The target macro node device sends and / or receives signaling related to mobility management.

[0746] In some embodiments, signaling associated with mobility management includes signaling for one or more devices based on a group. In embodiments of this application, mobility management includes at least one of: switching from a source microdomain to a target macrodomain, switching from a source microdomain to a target microdomain, switching from a source macrodomain to a target microdomain, and switching from a source macrodomain to a target macrodomain.

[0747] In some embodiments, signaling related to mobility management includes at least one of the following:

[0748] The second handover request sent by the source group head device;

[0749] Confirmation of the second handover request sent to the source group head device;

[0750] A handover completion message sent by one or more terminal devices;

[0751] The fourth handover request sent by the source macro node device;

[0752] Confirmation of the fourth handover request sent to the source macro node device;

[0753] The fifth handover request sent by the source macro node device;

[0754] Confirmation of the fifth handover request sent to the source macro node device;

[0755] The first handover completion message sent by the target group head device;

[0756] The sixth handover request sent by the source macro node device;

[0757] Confirmation of the sixth handover request sent to the source macro node device;

[0758] The seventh handover request sent by the source macro node device;

[0759] Confirmation of the seventh handover request sent to the source macro node device.

[0760] Example 1: Switching from the source micro-domain network to the target macro-domain;

[0761] In some embodiments, the above operation 1320 can be replaced by the following sub-operations:

[0762] Operation 13-1: Receive the second handover request sent by the source group head device. The second handover request is used to request the handover of one or more terminal devices from the source microdomain to the target macrodomain.

[0763] For detailed implementation methods, please refer to operation 26 above.

[0764] Operation 13-2: Send a second handover request confirmation to the source group head device. The second handover request confirmation is a handover request confirmation for one or more terminal devices.

[0765] For detailed implementation methods, please refer to operation 27 above.

[0766] Operation 13-3: After establishing a connection with one or more terminal devices, receive a handover completion message from one or more terminal devices.

[0767] For detailed implementation methods, please refer to operation 33 above.

[0768] Example 2: Switching from the source macro domain to the target macro domain;

[0769] In some embodiments, the above operation 1320 can be replaced by the following sub-operations:

[0770] Operation 13-4: Receive the fourth handover request sent by the source macro node device. The fourth handover request is used to request the handover of one or more terminal devices from the source macro domain to the target macro domain.

[0771] For detailed implementation methods, please refer to operation 66 above.

[0772] Operation 13-5: Send the fourth handover request confirmation to the source macro node device. The fourth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0773] For detailed implementation methods, please refer to operation 67 above.

[0774] Operation 13-6: After establishing a connection with one or more terminal devices, receive a handover completion message from one or more terminal devices.

[0775] For details on the specific implementation method, please refer to operation 73 above.

[0776] Example 3: Switching from the source macro domain to the target micro domain;

[0777] In some embodiments, the above operation 1320 can be replaced by the following sub-operations:

[0778] Operation 13-7: Receive the fifth handover request sent by the source macro node device. The fifth handover request is used to request the handover of one or more terminal devices from the source macro domain to the target micro domain.

[0779] For detailed implementation methods, please refer to operation 86 above.

[0780] Operation 13-8: Send the fifth handover request confirmation to the source macro node device. The fifth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0781] For detailed implementation methods, please refer to operation 87 above.

[0782] Operation 13-9: Receive the first handover completion message sent by the target group head device. The first handover completion message is generated based on the summary of the second handover completion messages of one or more terminal devices.

[0783] For detailed implementation methods, please refer to operation 95 above.

[0784] Example 4: Switching from the source micro-domain to the target macro-domain;

[0785] In some embodiments, the above operation 1320 can be replaced by the following sub-operations:

[0786] Operation 13-10: Receive the sixth handover request sent by the source macro node device. The sixth handover request is used to request the source group head device and / or one or more group member devices to switch from the source micro domain to the target macro domain.

[0787] For details on the specific implementation method, please refer to operation 210 above.

[0788] Operation 13-11: Send the sixth handover request confirmation to the source macro node device. The sixth handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0789] For details on the specific implementation method, please refer to operation 211 above.

[0790] Operation 13-12: After establishing a connection with one or more member devices, receive a handover completion message from one or more member devices.

[0791] For details on the specific implementation method, please refer to operation 219 above.

[0792] Example 5: Switching from the source microdomain to the target microdomain;

[0793] In some embodiments, the above operation 1320 can be replaced by the following sub-operations:

[0794] Operation 13-13: Receive the seventh handover request sent by the source macro node device. The seventh handover request is used to request the source group head device and / or one or more group member devices to be switched from the source micro domain to the target micro domain.

[0795] For details on the specific implementation method, please refer to operation 230 above.

[0796] Operations 13-14: Send the seventh handover request confirmation to the source macro node device. The seventh handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0797] For details on the specific implementation method, please refer to operation 231 above.

[0798] Operations 13-15: Receive the first handover completion message sent by the target group head device. The first handover completion message is generated by summarizing the second handover completion messages of one or more group member devices.

[0799] For details on the specific implementation method, please refer to operation 241 above.

[0800] It should be noted that the timing of the above operations is not limited in the embodiments of this application.

[0801] Figure 21 shows a structural block diagram of a movable device provided in an exemplary embodiment of this application. The movable device is a mobile device located in a macro-domain network or a micro-domain network. The device includes:

[0802] Transceiver module 2110 is used to send and / or receive mobility management related signaling, including signaling for one or more devices based on a group.

[0803] In some embodiments, mobility management includes at least one of: switching from a source microdomain to a target microdomain, switching from a source microdomain to a target macrodomain, switching from a source macrodomain to a target microdomain, and switching from a source macrodomain to a target macrodomain.

[0804] The transceiver module 2110 is also used to receive a switching command sent by the source group head device. The switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain. The one or more member devices include the first terminal device.

[0805] The transceiver module 2110 is also used to switch the RRC connection to the target group head device according to the switching command, and to send a switching completion message to the target group head device.

[0806] The transceiver module 2110 is also used to receive a switching command sent by the source group head device. The switching command is used to trigger one or more group member devices to switch from the source micro domain to the target macro domain. The one or more group member devices include the first terminal device.

[0807] The transceiver module 2110 is also used to switch the RRC connection to the device outside the target group according to the switching command, and to send a switching completion message to the device outside the target group.

[0808] The transceiver module 2110 is also used to receive a switching command sent by a device outside the source group. The switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain. The one or more terminal devices include the first terminal device.

[0809] The transceiver module 2110 is also used to switch the RRC connection to the target group head device according to the switching command, and to send a switching completion message to the target group head device.

[0810] The transceiver module 2110 is also used to receive a handover command sent by a device outside the source group. The handover command is used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain. The one or more terminal devices include the first terminal device.

[0811] The transceiver module 2110 is also used to switch the RRC connection to the device outside the target group according to the switching command, and to send a switching completion message to the device outside the target group.

[0812] The transceiver module 2110 is also used to receive a switching command sent by a device outside the source group. The switching command is used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain. The one or more terminal devices include the first terminal device.

[0813] The transceiver module 2110 is also used to switch the RRC connection to the device outside the target group according to the switching command, and to send a second switching completion message to the target group head device.

[0814] The second handover completion message is used to be aggregated into the first handover completion message by the target group head device and then sent to the target group external device.

[0815] In some embodiments, the handover command is a common handover command, which is sent in a system message to multiple terminal devices in a broadcast manner; or, the handover command is a dedicated handover command, which is sent individually to each terminal device through dedicated RRC signaling.

[0816] The transceiver module 2110 is also used to receive a second switching command sent by the source group head device. The second switching command is used to trigger one or more group member devices to switch from the source micro domain to the target macro domain. The one or more group member devices include the first terminal device.

[0817] The transceiver module 2110 is also used to switch the RRC connection to the device outside the target group according to the second switching command, and to send a switching completion message to the device outside the target group.

[0818] The second switching command is generated based on the first switching command, which is sent from the external source group device to the source group head device.

[0819] The transceiver module 2110 is also used to receive a second switching command sent by the source group head device. The second switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain. The one or more member devices include the first terminal device.

[0820] The transceiver module 2110 is also used to switch the RRC connection to the device outside the target group according to the second switching command, and to send the second switching completion message to the target group head device.

[0821] The second handover command is generated based on the first handover command, which is sent from the source group external device to the source group head device. The second handover completion message is used to be summarized by the target group head device into the first handover completion message and then sent to the target group external device.

[0822] In some embodiments, the second handover command is a common handover command, which is sent to multiple terminal devices in a system message via broadcast; or, the second handover command is a dedicated handover command, which is sent to the terminal devices via dedicated RRC signaling.

[0823] In some embodiments, the first switching command carries the identifiers of the active group head device and / or one or more group member devices to indicate the device that needs to perform the switching.

[0824] The transceiver module 2110 is also used to receive measurement configuration messages sent by the source group head device and to report measurement results to the source group head device. The measurement configuration message indicates that the measurement configuration is configured for all or some of the member devices in the source microdomain, and the measurement results are obtained based on the measurement configuration.

[0825] The transceiver module 2110 is also used to receive measurement configuration messages sent by devices outside the source group and report measurement results to those devices. The measurement configuration message indicates a measurement configuration specific to all or some of the terminal devices in the source macro domain, and the measurement results are obtained based on this configuration.

[0826] The transceiver module 2110 is further configured to receive a second measurement configuration message sent by the source group head device; and to report a second measurement result to the source group head device, wherein the second measurement result is obtained based on the measurement configuration indicated by the second measurement configuration message. The measurement configuration indicated by the second measurement configuration message is configured for all or some of the group member devices; the second measurement configuration message is generated based on a first measurement configuration message; the first measurement configuration message is sent by a source group external device to the source group head device; and the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0827] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in a terminal-specific signaling.

[0828] In some embodiments, a common measurement configuration includes a complete set of measurement configurations for a plurality of terminal devices, each measurement configuration having its own measurement identifier; a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration used by the single terminal device in the complete set of measurement configurations.

[0829] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device.

[0830] Figure 22 shows a structural block diagram of a source group header device provided in an exemplary embodiment of this application. The source group header device is a means for managing one or more member devices in a source microdomain. The device includes:

[0831] Transceiver module 2210 is used to send and / or receive mobility management related signaling, including signaling for one or more devices based on a group.

[0832] In some embodiments, mobility management includes at least one of: switching from a source microdomain to a target microdomain and switching from a source microdomain to a target macrodomain.

[0833] The transceiver module 2210 is also used to send a first handover request to the target group head device, the first handover request being used to request the handover of one or more group member devices from the source microdomain to the target microdomain.

[0834] The transceiver module 2210 is also used to receive a first handover request confirmation sent by the target group head device, wherein the first handover request confirmation is a handover request confirmation for one or more group member devices.

[0835] The transceiver module 2210 is also used to send a switching command to one or more member devices, the switching command being used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0836] The transceiver module 2210 is also used to send a second handover request to a device outside the target group. The second handover request is used to request that one or more member devices be switched from the source micro domain to the target macro domain.

[0837] The transceiver module 2210 is also used to receive a second handover request confirmation sent by a device outside the target group. The second handover request confirmation is a handover request confirmation for one or more member devices.

[0838] The transceiver module 2210 is also used to send a switching command to one or more member devices, the switching command being used to trigger one or more member devices to switch from the source micro domain to the target macro domain.

[0839] In some embodiments, the handover command is a public handover command, which is sent in a system message to multiple member devices in a broadcast manner; or, the handover command is a private handover command, which is sent through private RRC signaling.

[0840] The transceiver module 2210 is also used to receive a first switching command sent by a device outside the source group. The first switching command is used to trigger the source group head device and / or one or more member devices to switch from the source micro domain to the target macro domain.

[0841] The transceiver module 2210 is also used to switch the RRC connection to the target group external device according to the first switching command if the first switching command triggers the source group head device switching.

[0842] The transceiver module 2210 is also configured to send a second switching command to one or more member devices if the first switching command triggers a switching of one or more member devices. The second switching command is used to trigger one or more member devices to switch from the source micro domain to the target macro domain.

[0843] The transceiver module 2210 is also used to receive a first switching command sent by a device outside the source group. The first switching command is used to trigger the source group head device and / or one or more member devices to switch from the source microdomain to the target microdomain.

[0844] The transceiver module 2210 is also used to switch the RRC connection to the target group external device according to the first switching command if the first switching command triggers the source group head device switching.

[0845] The transceiver module 2210 is also configured to send a second switching command to one or more member devices if the first switching command triggers a switching of one or more member devices. The second switching command is used to trigger one or more member devices to switch from the source microdomain to the target microdomain.

[0846] In some embodiments, the second handover command is a common handover command, which is sent in a system message to multiple member devices in a broadcast manner; or, the second handover command is a dedicated handover command, which is sent through dedicated RRC signaling.

[0847] In some embodiments, the first handover request and the first handover request confirmation are sent via a direct connection interface between the source group head device and the target group head device, or forwarded via an external device; and / or, the first handover request and the first handover request confirmation carry the identifiers of one or more group member devices.

[0848] In some embodiments, the second handover request and the second handover request confirmation are sent via an RRC message; and / or, the second handover request and the second handover request confirmation carry the identifiers of one or more member devices.

[0849] In some embodiments, the first switching command carries the identifiers of the active group head device and / or one or more group member devices to indicate the device that needs to perform the switching.

[0850] The transceiver module 2210 is also used to send measurement configuration messages to all or some of the member devices; and to receive measurement results reported by all or some of the member devices. The measurement results are obtained based on the measurement configuration indicated by the measurement configuration message.

[0851] The transceiver module 2210 is also used to receive the first measurement configuration message sent by the external device of the source group.

[0852] The transceiver module 2210 is also used to send a second measurement configuration message to all or some of the group member devices, the second measurement configuration message being generated based on the first measurement configuration message.

[0853] The transceiver module 2210 is also used to receive the second measurement results of all or part of the group member devices, the second measurement results being obtained based on the measurement configuration indicated by the second measurement configuration message.

[0854] The transceiver module 2210 is also used to report a first measurement result to a device outside the source group, the first measurement result including the second measurement results of all or some of the group member devices, and / or the third measurement result of the source group head device.

[0855] The first measurement configuration message indicates that the measurement configuration is configured for the source group head device and / or all or some of the group member devices, while the second measurement configuration message indicates that the measurement configuration is configured for all or some of the group member devices.

[0856] In some embodiments, the first measurement result further includes an identifier corresponding to each second or third measurement result.

[0857] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in a terminal-specific signaling.

[0858] In some embodiments, a common measurement configuration includes a complete set of measurement configurations for a plurality of terminal devices, each measurement configuration having its own measurement identifier; a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration used by the single terminal device in the complete set of measurement configurations.

[0859] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device.

[0860] Figure 23 shows a structural block diagram of a source group external device provided in an exemplary embodiment of this application. The source group external device is a device in the source macrodomain that establishes a communication connection with the source group head device. The device includes:

[0861] Transceiver module 2310 is used to send and / or receive mobility management related signaling, including signaling for one or more devices based on a group.

[0862] In some embodiments, mobility management includes at least one of: switching from a source macro domain to a target micro domain, switching from a source macro domain to a target macro domain, switching from a source micro domain to a target micro domain, and switching from a source micro domain to a target macro domain.

[0863] The transceiver module 2310 is also used to send a third handover request to the target group head device, the third handover request being used to request the handover of one or more terminal devices from the source macro domain to the target micro domain.

[0864] The transceiver module 2310 is also used to receive a third handover request confirmation sent by the target group head device. The third handover request confirmation is a handover request confirmation for one or more terminal devices.

[0865] The transceiver module 2310 is also used to send a switching command to one or more terminal devices, the switching command being used to trigger one or more terminal devices to switch from the source macro domain to the target micro domain.

[0866] The transceiver module 2310 is also used to send a fourth handover request to a device outside the target group. The fourth handover request is used to request that one or more terminal devices be switched from the source macro domain to the target macro domain.

[0867] The transceiver module 2310 is also used to receive a fourth handover request confirmation sent by a device outside the target group. The fourth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0868] The transceiver module 2310 is also used to send a handover command to one or more terminal devices, the handover command being used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain.

[0869] The transceiver module 2310 is also used to send a fifth handover request to a device outside the target group. The fifth handover request is used to request that one or more terminal devices be switched from the source macro domain to the target micro domain.

[0870] The transceiver module 2310 is also used to receive a fifth handover request confirmation sent by a device outside the target group. The fifth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0871] The transceiver module 2310 is also used to send a handover command to one or more terminal devices, the handover command being used to trigger one or more terminal devices to switch from the source macro domain to the target macro domain.

[0872] In some embodiments, the handover command is a common handover command, which is broadcast to multiple terminal devices in a system message; or, the handover command is a dedicated handover command, which is sent via dedicated RRC signaling.

[0873] The transceiver module 2310 is also used to send a sixth handover request to a device outside the target group. The sixth handover request is used to request the source group head device and / or one or more group member devices to switch from the source micro domain to the target macro domain.

[0874] The transceiver module 2310 is also used to receive a sixth handover request confirmation sent by a device outside the target group. The sixth handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0875] The transceiver module 2310 is also used to send a first switching command to the source group head device, the first switching command being used to trigger the source group head device and / or one or more group member devices to switch from the source micro domain to the target macro domain.

[0876] The transceiver module 2310 is also used to send a seventh handover request to a device outside the target group. The seventh handover request is used to request the source group head device and / or one or more group member devices to switch from the source microdomain to the target microdomain.

[0877] The transceiver module 2310 is also used to receive a seventh handover request confirmation sent by a device outside the target group. The seventh handover request confirmation is a handover request confirmation for the source group head device and / or one or more group member devices.

[0878] The transceiver module 2310 is also used to send a first switching command to the source group head device, the first switching command being used to trigger the source group head device and / or one or more group member devices to switch from the source microdomain to the target microdomain.

[0879] In some embodiments, the first handover command is a common handover command, which is sent in a system message to multiple member devices in a broadcast manner; or, the first handover command is a dedicated handover command, which is sent through dedicated RRC signaling.

[0880] In some embodiments, the third handover request and the third handover request confirmation are sent via RRC messages; and / or, the third handover request and the third handover request confirmation carry the identifiers of one or more terminal devices.

[0881] In some embodiments, the fourth handover request and the fourth handover request confirmation are sent via a direct connection interface between external devices; and / or, the fourth handover request and the fourth handover request confirmation carry the identifiers of one or more terminal devices.

[0882] In some embodiments, the fifth handover request and the fifth handover request confirmation are sent via a direct connection interface between external devices; and / or, the fifth handover request and the fifth handover request confirmation carry the identifiers of one or more terminal devices.

[0883] In some embodiments, the sixth handover request and the sixth handover request confirmation are sent via a direct connection interface between external devices; and / or, the sixth handover request and the sixth handover request confirmation carry the identifiers of an active group head device and / or one or more group member devices.

[0884] In some embodiments, the seventh handover request and the seventh handover request acknowledgment are sent via a direct connection interface between external devices; and / or, the seventh handover request and the seventh handover request acknowledgment carry the identifiers of an active group head device and / or one or more group member devices.

[0885] The transceiver module 2310 is also used to send measurement configuration messages to all or some of the terminal devices; and to receive measurement results reported by all or some of the terminal devices. The measurement results are obtained based on the measurement configuration indicated by the measurement configuration message.

[0886] The transceiver module 2310 is also used to send a first measurement configuration message to the source group head device, wherein the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or some of the group member devices.

[0887] The transceiver module 2310 is also used to receive a first measurement result sent by the source group head device, the first measurement result including the second measurement results of all or some of the group member devices, and / or the third measurement result of the source group head device.

[0888] The second measurement result is obtained based on the measurement configuration indicated by the second measurement configuration message, which is generated based on the first measurement configuration message. The measurement configuration indicated by the second measurement configuration message is configured for all or some of the group members' devices.

[0889] In some embodiments, the first measurement result further includes an identifier corresponding to each second or third measurement result.

[0890] In some embodiments, the measurement configuration includes at least one of a common measurement configuration and a dedicated measurement configuration. The common measurement configuration is broadcast to multiple terminal devices in a system message, while the dedicated measurement configuration is sent individually to each terminal device in a terminal-specific signaling.

[0891] In some embodiments, a common measurement configuration includes a complete set of measurement configurations for a plurality of terminal devices, each measurement configuration having its own measurement identifier; a dedicated measurement configuration includes a measurement identifier corresponding to a single terminal device, used to indicate the measurement configuration used by the single terminal device in the complete set of measurement configurations.

[0892] In some embodiments, a common measurement configuration includes a common portion of the measurement configurations of multiple terminal devices, and a dedicated measurement configuration includes a proprietary portion of the measurement configuration of a single terminal device.

[0893] Figure 24 shows a structural block diagram of a target group head device provided in an exemplary embodiment of this application. The target group head device is a means for managing one or more member devices in a target microdomain. The device includes:

[0894] Transceiver module 2410 is used to send and / or receive mobility management related signaling, including signaling for one or more devices based on a group.

[0895] In some embodiments, mobility management includes at least one of: switching from a source microdomain to a target microdomain and switching from a source macrodomain to a target microdomain.

[0896] The transceiver module 2410 is also used to receive a first handover request sent by the source group head device, the first handover request being used to request the handover of one or more member devices from the source microdomain to the target microdomain.

[0897] The transceiver module 2410 is also used to send a first handover request confirmation to the source group head device, the first handover request confirmation being a handover request confirmation for one or more group member devices.

[0898] The transceiver module 2410 is also used to receive a handover completion message sent by one or more member devices after establishing an RRC connection with one or more member devices.

[0899] The transceiver module 2410 is also used to receive a third handover request sent by a device outside the source group. The third handover request is used to request that one or more terminal devices be switched from the source macro domain to the target micro domain.

[0900] The transceiver module 2410 is also used to send a third handover request confirmation to a device outside the source group. The third handover request confirmation is a handover request confirmation for one or more terminal devices.

[0901] The transceiver module 2410 is also used to receive a handover completion message sent by one or more terminal devices after establishing an RRC connection with one or more terminal devices.

[0902] In some embodiments, the first handover request and the first handover request confirmation are sent via a direct connection interface between the source group head device and the target group head device, or forwarded via an external device; and / or, the first handover request and the first handover request confirmation carry the identifiers of one or more group member devices.

[0903] In some embodiments, the third handover request and the third handover request confirmation are sent via RRC messages; and / or, the third handover request and the third handover request confirmation carry the UE ID of one or more terminal devices.

[0904] The transceiver module 2410 is also used to receive a second handover completion message from one or more member devices.

[0905] The transceiver module 2410 is also used to aggregate and generate a first handover completion message based on the second handover completion messages of one or more member devices.

[0906] The transceiver module 2410 is also used to send a first handover completion message to a device outside the target group.

[0907] Figure 25 shows a structural block diagram of a target group external device provided in an exemplary embodiment of this application. The target group external device is a device in the target macrodomain that establishes a communication connection with the target group head device. The device includes:

[0908] Transceiver module 2510 is used to send and / or receive mobility management related signaling, including signaling for one or more devices based on a group.

[0909] In some embodiments, mobility management includes at least one of: switching from a source microdomain to a target macrodomain, switching from a source microdomain to a target microdomain, switching from a source macrodomain to a target microdomain, and switching from a source macrodomain to a target macrodomain.

[0910] The transceiver module 2510 is also used to receive a second handover request sent by the source group head device, the second handover request being used to request the handover of one or more terminal devices from the source microdomain to the target macrodomain.

[0911] The transceiver module 2510 is also used to send a second handover request confirmation to the source group head device, the second handover request confirmation being a handover request confirmation for one or more terminal devices.

[0912] The transceiver module 2510 is also used to receive a handover completion message sent by one or more terminal devices after establishing a connection with one or more terminal devices.

[0913] The transceiver module 2510 is also used to receive a fourth handover request sent by a device outside the source group. The fourth handover request is used to request that one or more terminal devices be switched from the source macro domain to the target macro domain.

[0914] The transceiver module 2510 is also used to send a fourth handover request confirmation to a device outside the source group. The fourth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0915] The transceiver module 2510 is also used to receive a handover completion message sent by one or more terminal devices after establishing a connection with one or more terminal devices.

[0916] The transceiver module 2510 is also used to receive a fifth handover request sent by a device outside the source group. The fifth handover request is used to request that one or more terminal devices be switched from the source macro domain to the target micro domain.

[0917] The transceiver module 2510 is also used to send a fifth handover request confirmation to a device outside the source group. The fifth handover request confirmation is a handover request confirmation for one or more terminal devices.

[0918] The transceiver module 2510 is also used to receive a first handover completion message sent by the target group head device, which is generated by summarizing second handover completion messages from one or more terminal devices.

[0919] The transceiver module 2510 is also used to receive a sixth handover request sent by a device outside the source group. The sixth handover request is used to request the source group head device and / or one or more member devices to switch from the source micro domain to the target macro domain.

[0920] The transceiver module 2510 is also used to send a sixth handover request confirmation to a device outside the source group. The sixth handover request confirmation is a handover request confirmation for the source group head device and / or one or more member devices.

[0921] The transceiver module 2510 is also used to receive a handover completion message sent by one or more member devices after establishing a connection with one or more member devices.

[0922] The transceiver module 2510 is also used to receive a seventh handover request sent by a device outside the source group. The seventh handover request is used to request the source group head device and / or one or more member devices to switch from the source microdomain to the target microdomain.

[0923] The transceiver module 2510 is also used to send a seventh handover request confirmation to a device outside the source group. The seventh handover request confirmation is a handover request confirmation for the source group head device and / or one or more member devices.

[0924] The transceiver module 2510 is also used to receive a first handover completion message sent by the target group head device, which is generated by summarizing second handover completion messages from one or more group member devices.

[0925] In some embodiments, the second handover request and the second handover request confirmation are sent via an RRC message; and / or, the second handover request and the second handover request confirmation carry the identifiers of one or more member devices.

[0926] In some embodiments, the fourth handover request and the fourth handover request confirmation are sent via a direct connection interface between external devices; and / or, the fourth handover request and the fourth handover request confirmation carry the identifiers of one or more terminal devices.

[0927] In some embodiments, the fifth handover request and the fifth handover request confirmation are sent via a direct connection interface between external devices; and / or, the fifth handover request and the fifth handover request confirmation carry the identifiers of one or more terminal devices.

[0928] In some embodiments, the sixth handover request and the sixth handover request confirmation are sent via a direct connection interface between external devices; and / or, the sixth handover request and the sixth handover request confirmation carry the identifiers of an active group head device and / or one or more group member devices.

[0929] In some embodiments, the seventh handover request and the seventh handover request acknowledgment are sent via a direct connection interface between external devices; and / or, the seventh handover request and the seventh handover request acknowledgment carry the identifiers of an active group head device and / or one or more group member devices.

[0930] It should be noted that the above embodiments of the device are only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above. For example, the transceiver module can be divided into a receiving module and a sending module, with the receiving module performing the receiving operation and the sending module performing the sending operation.

[0931] Figure 26 shows a schematic diagram of the structure of a communication device provided in one embodiment of this application. The communication device may include: a processor 2601, a receiver 2602, a transmitter 2603, a memory 2604, and a bus 2605.

[0932] The processor 2601 includes one or more processing cores, and the processor 2601 executes various functional applications and information processing by running software programs and modules.

[0933] The receiver 2602 and the transmitter 2603 can be implemented as a transceiver 2606, which can be a communication chip.

[0934] The memory 2604 is connected to the processor 2601 via a bus 2605. The memory 2604 can be used to store computer programs, and the processor 2601 can be used to execute the computer programs to implement the various operations performed by the terminal device or network device in the above method embodiments.

[0935] Furthermore, the memory 2604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0936] This application also provides a computer-readable storage medium storing a computer program that is used by the processor of a terminal device or network device to implement the various operations in the mobility management method described above. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0937] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip is running on a terminal device or network device, it is used to implement the various operations in the above-described mobility management method.

[0938] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of a terminal device or network device reads and executes the computer instructions from the computer-readable storage medium to implement the various operations in the mobility management method described above.

[0939] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0940] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

A mobility management method characterized by comprising: The method is performed by a first terminal device, and the method comprises: sending and / or receiving signaling related to mobility management, the signaling related to mobility management comprising signaling for one or more devices based on a group. The method according to claim 1, characterized in that, The mobility management comprises at least one of: switching from a source micro-domain to a target micro-domain, switching from the source micro-domain to a target macro-domain, switching from a source macro-domain to the target micro-domain. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management comprises: receiving a handover command sent by a source group head device, the handover command being used to trigger the one or more group member devices to switch from the source micro-domain to the target micro-domain, the one or more group member devices comprising the first terminal device; switching the RRC connection to a target group head device according to the handover command, and sending a handover complete message to the target group head device. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management comprises: receiving a handover command sent by a source group head device, the handover command being used to trigger the one or more group member devices to switch from the source micro-domain to the target macro-domain, the one or more group member devices comprising the first terminal device; switching the RRC connection to a target macro node device according to the handover command, and sending a handover complete message to the target macro node device. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management comprises: receiving a handover command sent by a source macro node device, the handover command being used to trigger the one or more terminal devices to switch from the source macro-domain to the target micro-domain, the one or more terminal devices comprising the first terminal device; switching the RRC connection to a target group head device according to the handover command, and sending a handover complete message to the target group head device. The method according to claim 2, characterized in that The mobility management further comprises switching from the source macro-domain to the target macro-domain; The sending and / or receiving signaling related to mobility management comprises: receiving a handover command sent by a source macro node device, the handover command being used to trigger the one or more terminal devices to switch from the source macro-domain to the target macro-domain, the one or more terminal devices comprising the first terminal device; switching the RRC connection to a target macro node device according to the handover command, and sending a handover complete message to the target macro node device. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management comprises: receiving a handover command sent by a source macro node device, the handover command being used to trigger the one or more terminal devices to switch from the source macro-domain to the target micro-domain, the one or more terminal devices comprising the first terminal device; switching the RRC connection to a target macro node device according to the handover command, and sending a second handover complete message to a target group head device; wherein the second handover complete message is used to be aggregated by the target group head device into a first handover complete message and then sent to the target macro node device. The method according to any one of claims 3 to 7, characterized in that, The switching command is a common switching command, which is sent in a system message in a broadcast form for multiple terminal devices; or The switching command is a dedicated switching command, which is sent separately for each terminal device through dedicated RRC signaling. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management includes: receiving a second switching command sent by a source group head device, the second switching command being used to trigger one or more group member devices to switch from the source micro domain to the target micro domain, the one or more group member devices including the first terminal device; switching the RRC connection to the target macro node device according to the second switching command, and sending a switching completion message to the target macro node device; The second switching command is generated based on a first switching command, which is sent by a source macro node device to the source group head device. The method according to claim 2, characterized in that The sending and / or receiving signaling related to mobility management includes: receiving a second switching command sent by a source group head device, the second switching command being used to trigger one or more group member devices to switch from the source micro domain to the target micro domain, the one or more group member devices including the first terminal device; switching the RRC connection to the target macro node device according to the second switching command, and sending a second switching completion message to the target group head device; The second switching command is generated based on a first switching command, which is sent by a source macro node device to the source group head device, and the second switching completion message is used to be aggregated by the target group head device into a first switching completion message and then sent to the target macro node device. According to the method of claim 9 or 10, The second switching command is a common switching command, which is sent in a system message in a broadcast form for multiple terminal devices; or The second switching command is a dedicated switching command, which is sent to the terminal device through dedicated RRC signaling. The method according to claim 9 or 10, characterized in that The first switching command carries the identity of the source group head device and / or the one or more group member devices, which is used to indicate the devices that need to perform switching. The method according to claim 3 or 4, characterized in that The method further includes: receiving a measurement configuration message sent by the source group head device; and reporting a measurement result to the source group head device; The measurement configuration indicated by the measurement configuration message is configured for all or part of the group member devices in the source micro domain, and the measurement result is measured based on the measurement configuration. The method according to claims 5 to 7, characterized in that The method further includes: receiving a measurement configuration message sent by the source macro node device, and reporting the measurement result to the source macro node device; The measurement configuration indicated by the measurement configuration message is configured for all or part of the terminal devices in the source macro domain, and the measurement result is measured based on the measurement configuration. The method according to claim 9 or 10, characterized in that The method further includes: receiving a second measurement configuration message sent by the source group head device; and reporting a second measurement result to the source group head device, the second measurement result being measured based on the measurement configuration indicated by the second measurement configuration message; The second measurement configuration message is generated based on a first measurement configuration message, the first measurement configuration message is sent by a source macro node device to the source group head device, and the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or all or part of the group member devices. The method according to any one of claims 13 to 15, characterized in that The measurement configuration comprises at least one of a common measurement configuration and a dedicated measurement configuration, the common measurement configuration is sent in a system message by broadcasting for a plurality of terminal devices, and the dedicated measurement configuration is sent in terminal-specific signaling for each terminal device. The method of claim 16, wherein The common measurement configuration comprises a complete set of measurement configurations of the plurality of terminal devices, each measurement configuration has a respective measurement identifier; and the dedicated measurement configuration comprises a measurement identifier corresponding to a single terminal device, used to indicate a measurement configuration adopted by the single terminal device in the complete set of measurement configurations. The method of claim 16, wherein The common measurement configuration comprises a common part of the measurement configurations of the plurality of terminal devices, and the dedicated measurement configuration comprises a dedicated part of the measurement configuration of the single terminal device. A mobility management method characterized by comprising: The method is performed by a source group head device, and the method comprises: sending and / or receiving mobility management related signaling, the mobility management related signaling comprising signaling for one or more group-based devices. According to the method of claim 19, wherein The mobility management comprises at least one of switching from a source micro domain to a target micro domain, and switching from the source micro domain to a target macro domain. The method of claim 20, wherein The sending and / or receiving mobility management related signaling comprises: sending a first handover request to a target group head device, the first handover request being used to request switching of one or more group member devices from the source micro domain to the target micro domain; receiving a first handover request acknowledgement sent by the target group head device, the first handover request acknowledgement being a handover request acknowledgement for the one or more group member devices; sending a handover command to the one or more group member devices, the handover command being used to trigger the one or more group member devices to switch from the source micro domain to the target micro domain. The method of claim 20, wherein The sending and / or receiving mobility management related signaling comprises: sending a second handover request to a target macro node device, the second handover request being used to request switching of one or more group member devices from the source micro domain to the target macro domain; receiving a second handover request acknowledgement sent by the target macro node device, the second handover request acknowledgement being a handover request acknowledgement for the one or more group member devices; sending a handover command to the one or more group member devices, the handover command being used to trigger the one or more group member devices to switch from the source micro domain to the target macro domain. According to the method of claim 21 or 22, wherein The handover command is a common handover command, which is sent in a system message by broadcasting for a plurality of group member devices; or The handover command is a dedicated handover command, which is sent by dedicated RRC signaling. The method of claim 20, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a first handover command sent by a source macro node device, the first handover command being used to trigger the source group head device and / or one or more group member devices to handover from the source micro domain to the target micro domain; if the first handover command triggers the source group head device to handover, switching RRC connection to the target macro node device according to the first handover command; if the first handover command triggers the one or more group member devices to handover, sending a second handover command to the one or more group member devices, the second handover command being used to trigger the one or more group member devices to handover from the source micro domain to the target micro domain. The sending and / or receiving signaling related to mobility management comprises: The method of claim 20, wherein receiving a first handover command sent by a source macro node device, the first handover command being used to trigger the source group head device and / or one or more group member devices to handover from the source micro domain to the target micro domain; if the first handover command triggers the source group head device to handover, switching RRC connection to the target macro node device according to the first handover command; if the first handover command triggers the one or more group member devices to handover, sending a second handover command to the one or more group member devices, the second handover command being used to trigger the one or more group member devices to handover from the source micro domain to the target micro domain. The method according to claim 24 or 25, wherein: the second handover command is a common handover command, which is sent in a system message in a broadcast form for multiple group member devices; or the second handover command is a dedicated handover command, which is sent through dedicated RRC signaling. The first handover request and the first handover request acknowledgement are sent through a direct interface between the source group head device and the target group head device, or are forwarded by a macro node device; and / or The method of claim 21, wherein The first handover request and the first handover request acknowledgement carry the identity of the one or more group member devices. The second handover request and the second handover request acknowledgement are sent through RRC messages; and / or The method of claim 22, wherein The second handover request and the second handover request acknowledgement carry the identity of the one or more group member devices. The method according to claim 24 or 25, wherein: The first handover command carries the identity of the source group head device and / or the one or more group member devices, which is used to indicate the device that needs to perform handover. The method further comprises: The method according to claim 21 or 22, characterized in that sending a measurement configuration message to all or part of the group member devices; and receiving measurement results reported by the all or part of the group member devices; wherein the measurement results are obtained based on the measurement configuration indicated by the measurement configuration message. The method further comprises: The method according to claim 24 or 25, characterized in that receiving a first measurement configuration message sent by the source macro node device; sending a second measurement configuration message to all or part of the group member devices, the second measurement configuration message being generated based on the first measurement configuration message; ​ receiving second measurement results of the all or part of the member devices, the second measurement results being measured based on the measurement configuration indicated by the second measurement configuration message; reporting first measurement results to the source macro node device, the first measurement results comprising the second measurement results of the all or part of the member devices, and / or the third measurement results of the source group head device; wherein the measurement configuration indicated by the first measurement configuration message is configured for the source group head device and / or the all or part of the member devices, and the measurement configuration indicated by the second measurement configuration message is configured for the all or part of the member devices. The method of claim 31, wherein The first measurement results further comprise an identifier corresponding to each of the second measurement results or the third measurement results. The method according to any one of claims 30 to 32, characterized in that The measurement configuration comprises at least one of a common measurement configuration and a dedicated measurement configuration, the common measurement configuration being sent in a system message by broadcasting for a plurality of terminal devices, and the dedicated measurement configuration being sent in terminal-specific signaling for each terminal device. The method of claim 33, wherein The common measurement configuration comprises a full set of measurement configurations of the plurality of terminal devices, each measurement configuration having a respective measurement identifier; and the dedicated measurement configuration comprises a measurement identifier corresponding to a single terminal device, used to indicate a measurement configuration adopted by the single terminal device in the full set of measurement configurations. The method of claim 33, wherein The common measurement configuration comprises a common part of measurement configurations of the plurality of terminal devices, and the dedicated measurement configuration comprises a dedicated part of measurement configurations of the single terminal device. A mobility management method, characterized by, The method is performed by a source macro node device, and the method comprises: sending and / or receiving mobility management related signaling, the mobility management related signaling comprising signaling for one or more devices based on a group. The method of claim 36, wherein The mobility management comprises at least one of: handover from a source macro domain to a target micro domain, handover from a source micro domain to the target micro domain, and handover from the source micro domain to the target macro domain. The method of claim 37, wherein The sending and / or receiving mobility management related signaling comprises: sending a third handover request to a target group head device, the third handover request being used to request handover of one or more terminal devices from the source macro domain to the target micro domain; receiving a third handover request acknowledgement sent by the target group head device, the third handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; sending a handover command to the one or more terminal devices, the handover command being used to trigger the one or more terminal devices to handover from the source macro domain to the target micro domain. The method of claim 37, wherein The mobility management further comprises handover from the source macro domain to a target macro domain. The sending and / or receiving mobility management related signaling comprises: sending a fourth handover request to a target macro node device, the fourth handover request being used to request handover of one or more terminal devices from the source macro domain to the target macro domain; receiving a fourth handover request acknowledgement sent by the target macro node device, the fourth handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; sending a handover command to the one or more terminal devices, the handover command being used to trigger the one or more terminal devices to handover from the source macro domain to the target micro domain. The method of claim 37, wherein The sending and / or receiving of the signaling related to mobility management comprises: sending a fifth handover request to a target macro node device, the fifth handover request being used to request handover of one or more terminal devices from the source macro domain to the target micro domain; receiving a fifth handover request acknowledgement sent by the target macro node device, the fifth handover request acknowledgement being an acknowledgement of the handover request for the one or more terminal devices; sending a handover command to the one or more terminal devices, the handover command being used to trigger the one or more terminal devices to handover from the source macro domain to the target micro domain. The method according to any one of claims 38 to 40, wherein: the handover command is a common handover command, the common handover command being sent in a system message in a broadcast form for a plurality of terminal devices; or the handover command is a dedicated handover command, the dedicated handover command being sent through dedicated RRC signaling. The method of claim 37, wherein The sending and / or receiving of the signaling related to mobility management comprises: sending a sixth handover request to a target macro node device, the sixth handover request being used to request handover of the source group header device and / or one or more group member devices from the source micro domain to the target macro domain; receiving a sixth handover request acknowledgement sent by the target macro node device, the sixth handover request acknowledgement being an acknowledgement of the handover request for the source group header device and / or one or more group member devices; sending a first handover command to the source group header device, the first handover command being used to trigger the source group header device and / or one or more group member devices to handover from the source micro domain to the target macro domain. The method of claim 37, wherein The sending and / or receiving of the signaling related to mobility management comprises: sending a seventh handover request to a target macro node device, the seventh handover request being used to request handover of the source group header device and / or one or more group member devices from the source micro domain to the target micro domain; receiving a seventh handover request acknowledgement sent by the target macro node device, the seventh handover request acknowledgement being an acknowledgement of the handover request for the source group header device and / or one or more group member devices; sending a first handover command to the source group header device, the first handover command being used to trigger the source group header device and / or one or more group member devices to handover from the source micro domain to the target micro domain. The method according to claim 42 or 43, wherein: the first handover command is a common handover command, the common handover command being sent in a system message in a broadcast form for a plurality of group member devices; or the first handover command is a dedicated handover command, the dedicated handover command being sent through dedicated RRC signaling. The method of claim 38, wherein The third handover request and the third handover request acknowledgement are sent through RRC messages; and / or The third handover request and the third handover request acknowledgement carry an identity of the one or more terminal devices. The method of claim 39, wherein The fourth handover request and the fourth handover request acknowledgement are sent through an interface between macro node devices; and / or, The fourth handover request and the fourth handover request acknowledgement carry the identity of the one or more terminal devices. The method of claim 40, wherein The fifth handover request and the fifth handover request acknowledgement are sent through a direct interface between macro node devices; and / or, The fifth handover request and the fifth handover request acknowledgement carry the identity of the one or more terminal devices. The method of claim 42, wherein The sixth handover request and the sixth handover request acknowledgement are sent through a direct interface between macro node devices; and / or, The sixth handover request and the sixth handover request acknowledgement carry the identity of the source group head device and / or one or more group member devices. The method of claim 43, wherein The seventh handover request and the seventh handover request acknowledgement are sent through a direct interface between macro node devices; and / or, The seventh handover request and the seventh handover request acknowledgement carry the identity of the source group head device and / or one or more group member devices. The method according to any one of claims 38 to 40, characterized in that The method further comprises: sending a measurement configuration message to all or part of the terminal devices; and receiving measurement results reported by the all or part of the terminal devices; The measurement results are obtained based on measurement configurations indicated by the measurement configuration message. The method according to claim 42 or 43, characterized in that The method further comprises: sending a first measurement configuration message to the source group head device, the measurement configuration indicated by the first measurement configuration message being configured for the source group head device and / or all or part of the group member devices; receiving a first measurement result sent by the source group head device, the first measurement result comprising a second measurement result of all or part of the group member devices, and / or a third measurement result of the source group head device; The second measurement result is obtained based on a measurement configuration indicated by a second measurement configuration message, the second measurement configuration message being generated based on the first measurement configuration message, the measurement configuration indicated by the second measurement configuration message being configured for all or part of the group member devices. The method of claim 51, wherein The first measurement result further comprises an identity corresponding to each of the second measurement result or the third measurement result. The method according to any one of claims 50 to 52, characterized in that The measurement configuration comprises at least one of a common measurement configuration and a dedicated measurement configuration, the common measurement configuration being sent in a system message through a broadcast mode for a plurality of terminal devices, and the dedicated measurement configuration being sent in terminal-specific signaling for each terminal device. The method of claim 53, wherein The common measurement configuration comprises a full set of measurement configurations of the plurality of terminal devices, each measurement configuration having a respective measurement identity; and the dedicated measurement configuration comprises a measurement identity corresponding to a single terminal device, used to indicate a measurement configuration adopted by the single terminal device in the full set of measurement configurations. The method of claim 53, wherein The common measurement configuration comprises a common part of measurement configurations of the plurality of terminal devices, and the dedicated measurement configuration comprises a dedicated part of measurement configurations of a single terminal device. A mobility management method, characterized by, The method is performed by a target group head device, and the method comprises: sending and / or receiving mobility management related signaling, the mobility management related signaling comprising signaling for one or more devices based on a group. The method of claim 56, wherein, The mobility management comprises at least one of: switching from a source micro-domain to a target micro-domain, switching from a source macro-domain to the target micro-domain. The method of claim 57, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a first handover request sent by a source group header device, the first handover request being used to request switching one or more group member devices from the source micro-domain to the target micro-domain; sending a first handover request acknowledgement to the source group header device, the first handover request acknowledgement being a handover request acknowledgement for the one or more group member devices; after establishing an RRC connection with the one or more group member devices, receiving a handover completion message sent by the one or more group member devices. The method of claim 57, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a third handover request sent by a source macro node device, the third handover request being used to request switching one or more terminal devices from the source macro-domain to the target micro-domain; sending a third handover request acknowledgement to the source macro node device, the third handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; after establishing an RRC connection with the one or more terminal devices, receiving a handover completion message sent by the one or more terminal devices. The method of claim 58, wherein The first handover request and the first handover request acknowledgement are sent through a direct interface between the source group header device and the target group header device, or forwarded by a macro node device; and / or, The first handover request and the first handover request acknowledgement carry an identity of the one or more group member devices. The method of claim 59, wherein The third handover request and the third handover request acknowledgement are sent through an RRC message; and / or, The third handover request and the third handover request acknowledgement carry a UE ID of the one or more terminal devices. The method of claim 57, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a second handover completion message of the one or more group member devices; based on the second handover completion message of the one or more group member devices, generating a first handover completion message by aggregation; sending the first handover completion message to a target macro node device. A mobility management method characterized by comprising: The method is performed by a target macro node device, and the method comprises: sending and / or receiving signaling related to mobility management, the signaling related to mobility management comprising signaling for one or more group-based devices. According to the method of claim 63, wherein The mobility management comprises at least one of: switching from a source micro-domain to a target macro-domain, switching from the source micro-domain to a target micro-domain, switching from a source macro-domain to the target micro-domain. The method of claim 64, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a second handover request sent by a source group header device, the second handover request being used to request switching one or more terminal devices from the source micro-domain to the target macro-domain; sending a second handover request acknowledgement to the source group header device, the second handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; after establishing a connection with the one or more terminal devices, receiving a handover completion message sent by the one or more terminal devices. The method of claim 64, wherein The mobility management further comprises switching from the source macro domain to the target macro domain; The sending and / or receiving signaling related to mobility management comprises: receiving a fourth handover request sent by the source macro node device, the fourth handover request being used for requesting to switch one or more terminal devices from the source macro domain to the target macro domain; sending a fourth handover request acknowledgement to the source macro node device, the fourth handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; after connection with the one or more terminal devices is established, receiving a handover completion message sent by the one or more terminal devices. The method of claim 64, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a fifth handover request sent by the source macro node device, the fifth handover request being used for requesting to switch one or more terminal devices from the source macro domain to the target micro domain; sending a fifth handover request acknowledgement to the source macro node device, the fifth handover request acknowledgement being a handover request acknowledgement for the one or more terminal devices; receiving a first handover completion message sent by the target group header device, the first handover completion message being generated based on a summary of second handover completion messages of the one or more terminal devices. The method of claim 64, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a sixth handover request sent by the source macro node device, the sixth handover request being used for requesting to switch a source group header device and / or one or more group member devices from the source micro domain to the target macro domain; sending a sixth handover request acknowledgement to the source macro node device, the sixth handover request acknowledgement being a handover request acknowledgement for the source group header device and / or one or more group member devices; after connection with the one or more group member devices is established, receiving a handover completion message sent by the one or more group member devices. The method of claim 64, wherein The sending and / or receiving signaling related to mobility management comprises: receiving a seventh handover request sent by the source macro node device, the seventh handover request being used for requesting to switch a source group header device and / or one or more group member devices from the source micro domain to the target micro domain; sending a seventh handover request acknowledgement to the source macro node device, the seventh handover request acknowledgement being a handover request acknowledgement for the source group header device and / or one or more group member devices; receiving a first handover completion message sent by the target group header device, the first handover completion message being generated based on a summary of second handover completion messages of the one or more group member devices. The method of claim 65, wherein The second handover request and the second handover request acknowledgement are sent through RRC messages; and / or, The second handover request and the second handover request acknowledgement carry the identity of the one or more group member devices. The method of claim 66, wherein The fourth handover request and the fourth handover request acknowledgement are sent through a direct connection interface between macro node devices; and / or, The fourth handover request and the fourth handover request acknowledgement carry the identity of the one or more terminal devices. The method of claim 67, wherein The fifth handover request and the fifth handover request acknowledgement are sent through a direct connection interface between macro node devices; and / or, The fifth handover request and the fifth handover request acknowledgement carry the identity of the one or more terminal devices. The method of claim 68, wherein The sixth handover request and the sixth handover request acknowledgement are sent through a direct interface between macro node devices; and / or, The sixth handover request and the sixth handover request acknowledgement carry the identity of the source group head device and / or one or more group member devices. The method of claim 69, wherein The seventh handover request and the seventh handover request acknowledgement are sent through a direct interface between macro node devices; and / or, The seventh handover request and the seventh handover request acknowledgement carry the identity of the source group head device and / or one or more group member devices. A movable device, characterized by The mobile device is a mobility device located in a macro domain network or a micro domain network, the device comprising: a transceiver module for sending and / or receiving mobility management related signaling, the mobility management related signaling including signaling for one or more group based devices. A source group header device characterized by The source group head device is a device in a source micro domain for managing one or more group member devices, the device comprising: a transceiver module for sending and / or receiving mobility management related signaling, the mobility management related signaling including signaling for one or more group based devices. A source group external device characterized by The source macro node device is a device in a source macro domain that has a communication connection established with the source group head device, the device comprising: a transceiver module for sending and / or receiving mobility management related signaling, the mobility management related signaling including signaling for one or more group based devices. A destination group header device characterized by The target group head device is a device in a target micro domain for managing one or more group member devices, the device comprising: a transceiver module for sending and / or receiving mobility management related signaling, the mobility management related signaling including signaling for one or more group based devices. A target group-out device, characterized in that The target out-of-group device is a device in a target macro domain that has a communication connection established with the target group head device, the device comprising: a transceiver module for sending and / or receiving mobility management related signaling, the mobility management related signaling including signaling for one or more group based devices. A communication device characterized by comprising: The communication device comprises: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the mobility management method according to any one of claims 1 to 74. A computer-readable storage medium, characterized by, The computer readable storage medium stores a computer program, which is loaded and executed by the processor to implement the mobility management method according to any one of claims 1 to 74. A computer program product, characterized in that The computer program product comprises computer instructions stored in a computer readable storage medium, the processor obtaining the computer instructions from the computer readable storage medium, so that the processor is loaded and executed to implement the mobility management method according to any one of claims 1 to 74.

Images