Communication method, communication device, communication system, storage medium and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium and a program product. The method comprises: receiving first indication information sent by a network device, wherein the first indication information is used for indicating a changed transmission configuration indicator (TCI) state, and the changed TCI state is associated with a first cell in a first region; and on the basis of the first indication information, determining that a serving cell is to be changed from a second cell in the first region to the first cell, and communicating with the network device on the basis of the first cell. In the method of the present disclosure, a terminal learns of a changed TCI state by means of receiving first indication information, and determines the change of a serving cell in a first region on the basis of an association relationship between the TCI state and a first cell in the first region and on the basis of a beam management mode, such that service interruption caused by a cell handover process can be avoided, thereby improving the mobility robustness and the user experience.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] With the rapid development of mobile communication technology, future communication networks will have higher speeds, lower latency, and greater connectivity. In mobile communication technology, cell handover can occur as the terminal's location changes. Summary of the Invention

[0003] When a terminal performs a cell handover, a service interruption will occur.

[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0005] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0006] The network device receives first indication information, which is used to indicate the changed Transmission Configuration Indicator (TCI) state, wherein the changed TCI state is associated with the first cell in the first region.

[0007] Based on the first indication information, it is determined that the serving cell has been changed from the second cell in the first region to the first cell, and communication with the network device is based on the first cell.

[0008] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0009] Send a first indication message to the terminal. The first indication message is used to indicate the changed Transmission Configuration Indicator (TCI) status. The changed TCI status is associated with a first cell in a first region. The first indication message is used by the terminal to determine that the serving cell has changed from a second cell in the first region to the first cell, and to communicate with the network device based on the first cell.

[0010] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method described in the first aspect or the second aspect.

[0011] Fourthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0012] The terminal is configured to implement the method as described in the first aspect;

[0013] The network device is configured to implement the method as described in the second aspect.

[0014] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0015] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0016] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0017] In this embodiment of the disclosure, the terminal learns the changed TCI status by receiving the first indication information, and determines the change of the serving cell in the first area based on the association relationship between the TCI status and the first cell in the first area and the beam management method, thereby avoiding service interruption caused by cell handover process and improving mobile robustness and user experience. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0019] Figure 1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0020] Figure 1B is a schematic diagram of the cell change process provided according to an embodiment of the present disclosure;

[0021] Figure 2A is an exemplary interactive schematic diagram of a method provided according to an embodiment of the present disclosure;

[0022] Figures 2B to 2D are schematic diagrams of network deployment according to embodiments of the present disclosure;

[0023] Figure 2E is a schematic diagram of different TRPs in the same cloud device according to an embodiment of the present disclosure;

[0024] Figures 2F to 2H are schematic diagrams of network deployment according to embodiments of the present disclosure;

[0025] Figure 2I is a schematic diagram of cell distribution within an area according to an embodiment of the present disclosure;

[0026] Figures 3A to 3C are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0027] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure;

[0028] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure;

[0029] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0030] Figure 5B is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0031] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0032] In a first aspect, embodiments of this disclosure provide a communication method executed by a terminal, the method comprising:

[0033] The network device receives a first indication message, which is used to indicate the changed transmission configuration indication TCI status, wherein the changed TCI status is associated with the first cell in the first region.

[0034] Based on the first instruction information, it is determined that the serving cell is changed from the second cell in the first region to the first cell, and communication with network equipment is based on the first cell.

[0035] In the above embodiments, the terminal learns the changed TCI status by receiving the first indication information, and determines the change of the serving cell in the first area based on the association between the TCI status and the first cell in the first area and the beam management method, thereby avoiding service interruption caused by cell handover process and improving mobile robustness and user experience.

[0036] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0037] The network device receives first configuration information, which is used to configure at least one TCI state, wherein the at least one TCI state is associated with at least one cell in the first region.

[0038] In the above embodiments, the terminal can determine the cell associated with each TCI state based on the first configuration information sent by the network device, thereby facilitating the determination of the cell to be changed based on the TCI state when making subsequent cell changes, thus improving the efficiency of cell change.

[0039] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0040] Receive second configuration information sent by the network device. The second configuration information is used to configure the first area.

[0041] In the above embodiments, by configuring a first area, the terminal can change the serving cell based on beam management while moving within the first area, avoiding service interruption caused by cell handover and improving mobile robustness and user experience.

[0042] In conjunction with the embodiments of the first aspect, in some embodiments, the second configuration information includes a list of cells corresponding to the first region; the cell list includes at least one of the following:

[0043] Frequency list of the cell;

[0044] List of Physical Cell Identification (PCI) codes for each community.

[0045] In the above embodiments, by configuring the cell list corresponding to the first region, the cells contained in the first region are indicated or configured, so that the terminal can determine the relevant cells that can be changed using beam management, thereby improving the service interruption phenomenon.

[0046] In conjunction with the embodiments of the first aspect, in some embodiments, the first region is associated with a Cell Radio Network Temporary Identifier (C-RNTI).

[0047] In the above embodiments, the first area is associated with a C-RNTI, and each cell in the first area uses the same C-RNTI, which can ensure that the terminal can change the serving cell by means of beam management when moving in the first area.

[0048] In conjunction with the embodiments of the first aspect, in some embodiments, the bit length of C-RNTI is a first length or a second length, wherein the second length is greater than the first length.

[0049] In the above embodiments, the bit length of C-RNTI is either a first length or a second length, which improves the flexibility of C-RNTI allocation; extending the length of C-RNTI with the second length can also be applied to more scenarios, such as the scenario of a surge in devices in the Internet of Things.

[0050] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0051] Receive a second indication message sent by the network device, the second indication message being used to indicate one of the following:

[0052] The bit length of C-RNTI is either the first length or the second length;

[0053] The bit length of C-RNTI is the second length, where the device type of the terminal is an Internet of Things (IoT) device;

[0054] A second C-RNTI of reassigned length, wherein the terminal was initially assigned a C-RNTI of the first length.

[0055] In the above embodiments, C-RNTIs of different bit lengths can be allocated according to the actual situation of the terminal, which improves the flexibility of C-RNTI allocation and ensures that appropriate C-RNTIs are allocated to the terminal.

[0056] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0057] The system receives third configuration information sent by a network device. This third configuration information is used to configure cell configuration information corresponding to cells in the first area. The cell configuration information includes at least one of the following:

[0058] Community signage information;

[0059] Community public facilities information;

[0060] Community-specific configuration information;

[0061] Information used to indicate whether the cell configuration information is used for cell management or for the management of the first area.

[0062] In the above embodiments, the third configuration information enables the terminal to determine the configuration of each cell in the current first area, which is beneficial for the terminal to communicate based on the cell configuration and ensure communication performance.

[0063] In conjunction with the embodiments of the first aspect, in some embodiments, the cells in the first region satisfy at least one of the following:

[0064] They belong to the same distributed unit (DU);

[0065] Belongs to different DUs;

[0066] They belong to the same centralized unit (CU);

[0067] Belonging to different CUs;

[0068] They belong to the same cloud device.

[0069] In the above embodiments, the cells in the first region may belong to one of multiple units or to cloud devices. Cells in the first region under different architectures can effectively negotiate cell configurations to ensure uninterrupted service in the beam management method.

[0070] In conjunction with the embodiments of the first aspect, in some embodiments, when belonging to the same DU or the same cloud device, the cell configuration information corresponding to the first cell and the second cell is determined based on the network device; or,

[0071] When belonging to different DUs or different CUs, at least partially identical cell configuration information is determined based on the interaction between the first cell and the second cell.

[0072] In the above embodiments, the cell configuration information is determined in a suitable way according to the unit or cloud device to which the cell belongs, thereby improving the adaptability of the cell configuration information in the cell change scenario of this embodiment.

[0073] In conjunction with the embodiments of the first aspect, in some embodiments, the cells in the first region are co-frequency cells; or, the first region includes inter-frequency cells, wherein the inter-frequency cells satisfy at least one of the following:

[0074] The frequency of the inter-frequency cell is the same as that of any serving cell in the carrier aggregation (CA) configured for the terminal;

[0075] The inter-frequency cell is configured as the serving cell in the CA;

[0076] Each cell in a heterogeneous frequency cell system is configured with an associated list of cells.

[0077] In the above embodiments, the cell change method is applicable to both intra-frequency and inter-frequency scenarios, and can determine whether a cell is an intra-frequency cell or an inter-frequency cell based on the conditions met by the cell.

[0078] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0079] Receive fourth configuration information sent by the network device, the fourth configuration information including at least one of the following:

[0080] The TCI status list includes the TCI status associated with cells at the edge of the first region.

[0081] Parameters for measurement intervals.

[0082] In the above embodiments, the parameters of the TCI status list and measurement interval can be determined through the fourth configuration information, which facilitates the terminal to perform effective measurements on cells in the first area and improves communication performance.

[0083] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes the following:

[0084] The changed TCI status is in the TCI status list, and the terminal performs radio resource management (RRM) measurements;

[0085] The changed TCI status is in the TCI status list, and the measurement result of the second cell is less than the threshold. The terminal performs Radio Resource Management (RRM) measurement.

[0086] In the above embodiments, determining whether to perform RRM measurement based on whether the changed TCI state is in the TCI state list can avoid unnecessary measurements and reduce power consumption.

[0087] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0088] Measurements are performed on neighboring cells within the first area according to the measurement interval, wherein the neighboring cells satisfy at least one of the following:

[0089] The frequency differs from that of the service cell;

[0090] The active bandwidth part (BWP) of the serving cell does not include the frequency domain location of the second cell reference signal.

[0091] In the above embodiments, only neighboring cells within the first area need to be measured according to the measurement interval, without needing to measure other cells within the first area, which can avoid unnecessary measurements and reduce power consumption.

[0092] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0093] Receive a third indication message sent by a network device, the third indication message being used to indicate at least one of the following: key update; Media Access Control (MAC) reset; Packet Data Convergence Protocol (PDCP) reconstruction; Radio Link Control (RLC) reconstruction; Physical layer resource reconfiguration.

[0094] In the above embodiments, after a cell change, the terminal can perform key updates, MAC resets, PDCP reconstruction, RLC reconstruction, or physical layer resource reconfiguration based on the network device's failure status to ensure the communication performance after the change.

[0095] In conjunction with the embodiments of the first aspect, in some embodiments, each of the different first regions has a corresponding key, on a regional basis.

[0096] In the above embodiments, setting a corresponding key for each region avoids the use of the same key in different cells, reduces the risk of key leakage, and improves security.

[0097] In conjunction with the embodiments of the first aspect, in some embodiments, the first cell obtains the value of a state variable through the second cell, wherein the state variable includes at least one of the following:

[0098] RLC entity receive window status variables;

[0099] RLC entity send window status variables;

[0100] PDCP entity receive window state variables;

[0101] PDCP entity send window state variables;

[0102] MAC parameter information.

[0103] In the above embodiments, the second cell can update the values ​​of relevant state variables for the first cell, so that the first cell can communicate with the terminal based on the valid values ​​of the state variables, thereby improving communication performance.

[0104] Secondly, embodiments of this disclosure provide a communication method executed by a network device, the method comprising:

[0105] Send a first indication message to the terminal. The first indication message is used to indicate the changed transmission configuration indication TCI status. The changed TCI status is associated with the first cell in the first region. The first indication message is used by the terminal to determine that the serving cell has changed from the second cell in the first region to the first cell, and to communicate with the network device based on the first cell.

[0106] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0107] Send first configuration information to the terminal. The first configuration information is used to configure at least one TCI state, wherein the at least one TCI state is associated with at least one cell in the first region.

[0108] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0109] Send the second configuration information to the terminal. The second configuration information is used to configure the first area.

[0110] In conjunction with embodiments of the second aspect, in some embodiments, the second configuration information includes a list of cells corresponding to the first region; the cell list includes at least one of the following:

[0111] Frequency list of the cell;

[0112] List of Physical Cell Identifiers (PCIs) for the residential community.

[0113] In conjunction with embodiments of the second aspect, in some embodiments, the first region is associated with a cell radio network temporary identifier (C-RNTI).

[0114] In conjunction with the embodiments of the second aspect, in some embodiments, the bit length of C-RNTI is a first length or a second length, wherein the second length is greater than the first length.

[0115] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0116] Send a second indication message to the terminal, the second indication message being used to indicate one of the following:

[0117] The bit length of C-RNTI is either the first length or the second length;

[0118] The bit length of C-RNTI is the second length, where the device type of the terminal is an Internet of Things (IoT) device;

[0119] A second C-RNTI of reassigned length, wherein the terminal was initially assigned a C-RNTI of the first length.

[0120] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0121] Send third configuration information to the terminal. The third configuration information is used to configure the cell configuration information corresponding to the cell in the first area; wherein, the cell configuration information includes at least one of the following:

[0122] Community signage information;

[0123] Community public facilities information;

[0124] Community-specific configuration information;

[0125] Information used to indicate whether the cell configuration information is used for cell management or for the management of the first area.

[0126] In conjunction with the embodiments of the second aspect, in some embodiments, the cells in the first region satisfy at least one of the following:

[0127] They belong to the same distribution unit DU;

[0128] Belongs to different DUs;

[0129] Belonging to the same lumped unit CU;

[0130] They belong to different CUs;

[0131] They belong to the same cloud device.

[0132] In conjunction with the embodiments of the second aspect, in some embodiments, when belonging to the same DU or the same cloud device, the cell configuration information corresponding to the first cell and the second cell is determined based on the network device; or,

[0133] When belonging to different DUs or different CUs, at least partially identical cell configuration information is determined based on the interaction between the first cell and the second cell.

[0134] In conjunction with the embodiments of the second aspect, in some embodiments, the cells in the first region are co-frequency cells; or, the first region includes inter-frequency cells, wherein the inter-frequency cells satisfy at least one of the following:

[0135] The frequency of the inter-frequency cell is the same as that of any serving cell in the carrier aggregation CA configured for the terminal;

[0136] The inter-frequency cell is configured as a serving cell in the CA;

[0137] Each cell in a heterogeneous frequency cell system is configured with an associated list of cells.

[0138] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0139] Send fourth configuration information to the terminal, the fourth configuration information including at least one of the following:

[0140] The TCI status list includes the TCI status associated with cells at the edge of the first region.

[0141] Parameters for measurement intervals.

[0142] In conjunction with the embodiments of the second aspect, in some embodiments, the modified TCI state is located in the TCI state list, and the terminal is used to perform Radio Resource Management (RRM) measurements.

[0143] The changed TCI status is in the TCI status list, and the measurement result of the second cell is less than the threshold. The terminal is used to perform Radio Resource Management (RRM) measurements.

[0144] In conjunction with embodiments of the second aspect, in some embodiments, the measurement interval is used to perform measurements on neighboring cells within a first area, wherein the neighboring cells satisfy at least one of the following:

[0145] The frequency differs from that of the service cell;

[0146] The active bandwidth portion (BWP) of the serving cell does not include the frequency domain location of the second cell reference signal.

[0147] In conjunction with embodiments of the second aspect, in some embodiments, the method includes:

[0148] Send a third indication message to the terminal, the third indication message being used to indicate at least one of the following:

[0149] Key update;

[0150] Media access control MAC reset;

[0151] Packet Data Convergence Protocol (PDCP) reconstruction;

[0152] Radio Link Control (RLC) reconstruction;

[0153] Physical layer resource reallocation.

[0154] In conjunction with the embodiments of the second aspect, in some embodiments, each of the different first regions has a corresponding key, on a regional basis.

[0155] In conjunction with the embodiments of the second aspect, in some embodiments, the first cell obtains the values ​​of state variables through the second cell, wherein the state variables include at least one of the following:

[0156] RLC entity receive window status variables;

[0157] RLC entity send window status variables;

[0158] PDCP entity receive window state variables;

[0159] PDCP entity send window state variables;

[0160] MAC parameter information.

[0161] Thirdly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the method of the first aspect or the second aspect.

[0162] Fourthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0163] The terminal is configured to implement the method as described in the first aspect;

[0164] The network device is configured to implement the method described in the second aspect.

[0165] Fifthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0166] When the instruction is executed on the communication device, it causes the communication device to perform the method of the first aspect or the second aspect.

[0167] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, they implement the method as described in the first aspect or the second aspect.

[0168] In a seventh aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0169] Eighthly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0170] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

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

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

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

[0174] In the embodiments of this disclosure, "multiple" refers to two or more.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0193] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.

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

[0195] In some embodiments, network device 102 may include at least one of access network device and core network device.

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

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

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

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

[0200] In some embodiments, core network equipment includes network elements with specific functions, such as Access Management Function (AMF) and Service Management Function (SMF).

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

[0202] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

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

[0204] In some implementations, the signaling congestion and load issues arising from the introduction of Machine Type Communication (MTC) devices have been identified by SA (Standalone) 2. SA2 believes that these signaling congestion and load issues mainly exist in the following two scenarios:

[0205] Scenario 1: When an MTC application requires an MTC device to do one thing at a time;

[0206] Scenario 2: When a large number of MTCs are roaming users, the service network does not exist, and they reside on the local network, a large amount of signaling load is introduced.

[0207] In some implementations, SA1 proposes certain service requirements and application scenarios for MTC. To meet these MTC service requirements and improve the RAN's performance in supporting MTC, possible RAN-side enhancement technologies are studied. These include: resource allocation for a large number of MTC UEs, low mobility considerations, power-saving mechanisms, and how ultra-low service cycles and a large number of MTC UEs affect RAN-side performance.

[0208] In some implementations, based on Small Data and Device Triggering Enhancements (SDDTE) and UE Power Consumption Optimizations (UEPCOP), RAN-side enhancements mainly focus on improving signaling effectiveness and reducing UE power consumption.

[0209] In some implementations, because machine-type communication (primarily meter reading services, considering that meters are generally placed in poor coverage areas such as basements) involves periodically reporting data packets of relatively fixed size, and most MTC UEs are in a relatively fixed state, the processing complexity of the MTC UEs is considered to reduce these characteristics. At the same time, considering that some UEs may be in poor coverage environments, coverage enhancement is needed for these MTC UEs.

[0210] For example, for NR R17, the main scenarios and use cases are as follows:

[0211] 1. For industrial wireless sensors: Communication service availability is 99.99%, and end-to-end latency is less than 100 milliseconds. For all use cases, the reference bit rate is less than 2 Mbps (potentially asymmetric, e.g., high UL traffic), and the device is stationary; the battery should last for at least several years. For safety-related sensors, latency requirements are lower, with a latency of 5-10 milliseconds.

[0212] 2. For video surveillance: Economical video bitrates will be 2-4 Mbps, latency <500 milliseconds, and reliability 99%-99.9%. High-end video, such as agricultural video, requires 7.5-25 Mbps. It's important to note that the service model is dominated by uplink (UL) transmission.

[0213] 3. Wearables: The reference bit rate for smart wearable applications can be 5-50 Mbps in the downlink and 2-5 Mbps in the uplink. The peak bit rate of the device is even higher, up to 150 Mbps in the downlink and up to 50 Mbps in the uplink. The device's battery should last for several days (up to 1-2 weeks).

[0214] For example, the scenarios and use cases that can be considered for 6G Internet of Things (IoT) are shown in Table 1-1 below:

[0215] Table 1-1

[0216] In some implementations, 5G lightweight user terminal types or low-capability terminals (Redcap()) and normal commercial terminals have the same connected-state mobility, and MTC terminals and normal commercial terminals have the same connected-state mobility. In cellular-based Narrow Band Internet of Things (NB-IoT), weak mobility is supported, meaning it does not support changes, and cross-area mobility can be achieved based on the "Radio Link Failure (RLF) + Radio Resource Control (RRC) link reconstruction" method.

[0217] In some implementations, such as in NR, connected-state (RRC_CONNECTED) mobility is based on network device control and includes both cell-level and beam-level mobility. Cell-level mobility and beam-level mobility will be described below.

[0218] For cell-level mobility, RRC signaling is required. Figure 1B illustrates the cell handover process, which includes: the source gNB sending a handover request to the target gNB; when the target gNB grants admission control, it confirms the handover request to the source gNB; the source gNB then sends RRC reconfiguration signaling to the terminal; the UE performs the handover to the new cell based on the RRC reconfiguration signaling; and the handover continues until RRC reconfiguration is complete, at which point the terminal switches to the new cell.

[0219] For beam-level mobility, explicit RRC signaling is not required. Instead, it is triggered by Downlink Control Information (DCI) and the MAC Control Element (MAC CE), and can occur within a cell or between cells. When it occurs between cells, it is called inter-cell beam management (ICBM). For ICBM, a terminal can send and receive terminal-dedicated channels or signals through a TRP with a different PCI than the serving cell. However, for non-terminal-dedicated channels, signals can only be received from a TRP with the same PCI as the serving cell.

[0220] Optionally, in ICBM, the serving cell and neighboring cells must be under the same DU in the inter-cell beam management in R17, and the serving cell and neighboring cells must have the same frequency. It is also specified that the timing advance (TA) from the terminal to each cell is the same, and the time delay difference from each cell to the user is within one cyclic prefix range.

[0221] In some implementations, such as in 5G systems, network devices can provide terminals with one or more candidate configurations. One candidate configuration may include one or more "cells (or cell groups)". The network device can subsequently control the terminal to change between these candidate configurations via Layer 1 (L1) signaling (e.g., DCI) or L2 signaling (e.g., MAC CE); for example, changing the working cell (or cell group) from "cell (or cell group)-1" to "cell (or cell group)-2". This control signaling can be called "cell change control signaling". The above process can also be referred to as a network-triggered Layer 1 / L2-triggered Mobility (LTM) process.

[0222] In some implementations, LTM is illustrated below:

[0223] For version 18 (Rel-18), LTM refers to a process in which a network device triggers a PCell / PSCell cell switch via MAC CE based on L1 measurement results, which may be accompanied by a change in the Master Cell group (MCG) / Secondary Cell group (SCG).

[0224] In this process, the gNB receives an L1 measurement report from the terminal. Based on this report, the gNB changes the terminal's serving cell via a cell switch command issued by the MAC CE. The cell switch command indicates an LTM candidate cell configuration that the gNB has pre-provided to the terminal via RRC signaling. The terminal then accesses the target cell indicated in the received cell switch command. The LTM candidate cell configuration can only be added, modified, and released by network devices via RRC signaling. The LTM process can be used to reduce mobility latency.

[0225] For LTM, Rel-18 LTM supports subsequent LTM (subsequent LTM). Subsequent LTM means that the subsequent LTM cell handover process between candidate cells does not require network equipment to perform RRC reconfiguration. In other words, after performing mobility operations, the terminal will not delete the LTM configuration information on its own. The LTM configuration information can continue to be used even if RRC reconfiguration and updates are not performed, and can be used to trigger subsequent LTM.

[0226] In some implementations, Rel-18 only supports LTM between intra-DUs and inter-DUs (i.e., intra-CUs). However, Rel-19 will extend this to support LTM between inter-CUs or between different nodes or base stations (inter-nodes / gNBs). LTM supporting inter-CUs (inter-nodes / gNBs) based on SCG primary and secondary cell (PSCell) changes involves the participation of Mobile Nodes (MNs). MNs are responsible for coordinating the configuration between candidate PSCells of different CUs.

[0227] In the aforementioned implementations, both RRC-level mobility and LTM require cell handover, which will result in service interruption. ICBM does not replace handover; the handover process will still ultimately occur.

[0228] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the communication method of this embodiment includes:

[0229] In step S2101, network device 102 sends second configuration information to terminal 101.

[0230] In some embodiments, terminal 101 receives second configuration information.

[0231] In some embodiments, the second configuration information is used to configure the first region.

[0232] Optionally, the first region is used to define an area where cell changes can be performed based on beam management.

[0233] Optionally, the first area can be called an edge-less cell, in which handover between cells within the area can be achieved through beam management.

[0234] Optionally, the first area may include multiple cells, which may be configured with the same or similar characteristics.

[0235] For example, a first region is associated with a C-RNTI, and multiple cells within that first region have the same C-RNTI.

[0236] Optionally, the C-RNTI associated with the first region can be configured synchronously in the second configuration information.

[0237] In some embodiments, the second configuration information includes a list of cells corresponding to the first region.

[0238] Optionally, the list of cells includes at least one of the following:

[0239] A list of cell frequencies;

[0240] The PCI list for the community.

[0241] Optionally, the cell list includes a frequency list, with each frequency or frequency layer corresponding to one cell; or, the cell list includes a PCI list, with each PCI corresponding to one cell; or, the cell list includes a "frequency+PCI" list, with each combination of frequency and PCI corresponding to one cell.

[0242] Optionally, the frequency list of cells includes the frequency corresponding to each cell in the first region, and the PCI list of cells includes the PCI corresponding to each cell in the first region.

[0243] In some embodiments, the cells in the first region are co-frequency cells; or, the first region includes inter-frequency cells, wherein the inter-frequency cells satisfy at least one of the following: the inter-frequency cell has the same frequency as any serving cell in the carrier aggregation (CA) configured for the terminal; the inter-frequency cell is configured as a serving cell in the CA; and each cell in the inter-frequency cells is configured with an associated cell list.

[0244] Optionally, in a CA-based model, the frequency of the inter-frequency cell is the same as that of any serving cell in the CA configured for the terminal. For example, in a CA scenario where the serving cell includes serving cell1, serving cell2, and serving cell3, and the frequencies corresponding to serving cell1, serving cell2, and serving cell3 are f1, f2, and f3 respectively, then the frequency of the non-serving cell in the first area is one of f1, f2, and f3.

[0245] Optionally, based on the CA model, the inter-frequency cell is configured as the serving cell in the CA. Regardless of whether the frequencies of the cells in the first area meet the optimal band combination capability supported by the UE, the activated serving cell can meet the band combination capability supported by the UE.

[0246] Optionally, each cell in the inter-frequency cell network is configured with an associated cell list. Network device 102 configures at least one cell configuration for cells in the first area, each cell configuration being associated with a cell list, where each cell in the cell list belongs to a cell in the first area. Information regarding the cell configuration is provided in step S2103 below.

[0247] In step S2102, network device 102 sends second instruction information to terminal 101.

[0248] In some embodiments, terminal 101 receives second instruction information.

[0249] In some embodiments, the C-RNTI associated with the first region may have different bit lengths.

[0250] Optionally, the bit length of C-RNTI is a first length or a second length, wherein the second length is greater than the first length.

[0251] For example, the first length is 16 bits, and the second length is 24 bits.

[0252] In some embodiments, the second indication information is used to indicate the bit length of the C-RNTI.

[0253] In some embodiments, the second indication information is used to indicate one of the following:

[0254] The bit length of C-RNTI is either the first length or the second length;

[0255] The bit length of C-RNTI is the second length, where the device type of terminal 101 is IOT;

[0256] A second length of C-RNTI is reallocated, wherein terminal 101 is initially assigned a first length of C-RNTI.

[0257] The second length is greater than the first length. For example, the first length is 16 bits and the second length is 24 bits.

[0258] Optionally, when terminal 101 performs the random access procedure, the network device allocates the C-RNTI bit length to a first length or a second length in the Random Access Response (RAR), that is, it sends the second indication information through the RAR. In one example, as shown in the RAR diagram in Figure 2F, the C-RNTI bit length can be allocated in the sub-header of the RAR, or the C-RNTI bit length can be allocated inside the RAR.

[0259] Optionally, for IoT devices, when terminal 101 performs a random access procedure, terminal 101 can notify network device 102 that its device type is an IoT device via MSG1 (one or more preambles sent by the terminal based on the random access configuration and downlink measurements). Then, the network device allocates the second length of the C-RNTI in the RAR. Alternatively, network device 102 can also determine the second length of the C-RNTI to be configured based on the random access timing (RO) or the random access preamble.

[0260] Optionally, network device 102 initially allocates a C-RNTI of a first length to terminal 101, and then network device 102 may reallocate a C-RNTI of a second length to terminal 101 according to communication or scheduling requirements.

[0261] In step S2103, network device 102 sends third configuration information to terminal 101.

[0262] In some embodiments, terminal 101 receives third configuration information.

[0263] In some embodiments, the third configuration information is used to configure the cell configuration information corresponding to the cell in the first region.

[0264] In some embodiments, the cell configuration information includes at least one of the following:

[0265] Community identification information, such as a community identifier indicating a specific community in the first area;

[0266] Community public facilities information;

[0267] Community-specific configuration information;

[0268] Information used to indicate whether cell configuration information is used for cell management or for first area management; for example, this information may occupy 1 bit of indicator, and different bit values ​​indicate whether it is applied to cell management or for first area management.

[0269] Among them, the common configuration information of the cell can be the configuration information contained in sCellConfigCommon as defined in the protocol, and the cell-specific configuration information can be the configuration information contained in sCellConfigDedicated as defined in the protocol.

[0270] Optionally, network device 102 sends RRC dedicated signaling to terminal 101, the RRC dedicated signaling including third configuration information.

[0271] In some embodiments, the cells in the first region satisfy at least one of the following: belonging to the same DU; belonging to different DUs; belonging to the same CU; belonging to different CUs; ​​belonging to the same cloud device.

[0272] In one example, as shown in the network deployment diagram in Figure 2B, taking an architecture that includes two gNB-DUs, one gNB-CU-CP, and one gNB-CU-UP as an example, the gNB-DU and gNB-CU-CP need to communicate based on the F1-C interface, the gNB-DU and gNB-CU-UP need to communicate based on the F1-U interface, and the gNB-CU-CP and gNB-CU-UP need to communicate based on the E1 interface.

[0273] In some embodiments, when belonging to the same DU or the same cloud device, the cell configuration information corresponding to the first cell and the second cell is determined based on the network device; or, when belonging to different DUs or different CUs, at least partially identical cell configuration information is determined based on the interaction between the first cell and the second cell.

[0274] In the first example, the cells in the first region belong to the same DU, that is, the cells in the first region are intra-DUs, or intra-gNBs. In this example, network device 102 coordinates the allocation of radio resources for terminal 101 for each cell. The radio resource allocation includes the cell's common configuration information, cell-specific configuration information, and the bit length of the C-RNTI, etc. Among them, the cell configuration information coordinated by network device 102 for each cell is at least partially the same.

[0275] In the second example, the cells in the first area belong to different DUs, i.e., the cells in the first area are Inter-DUs or intra-CUs. In this case, the two gNB-DUs negotiate the radio resource allocation for each cell for terminal 101 based on the F1 interface. As shown in the network deployment diagram in Figure 2C, gNB-DU1 (corresponding to the second cell) and gNB-DU2 (corresponding to the first cell) belong to the same gNB-CU. gNB-DU1 requests a radio resource reserve request from gNB-DU2 in the first area through the gNB-CU. Two scenarios will occur: either gNB-DU2 responds to the request (radio resource reserve response), indicating a successful request, or gNB-DU2 responds to the request (radio resource reserve failure). In other words, in this example, gNB-DU1 and gNB-DU2 will coordinate cell configurations interactively to ensure that their cell configuration information is at least partially identical.

[0276] In the third example, the cells in the first area belong to different CUs, i.e., the cells in the first area are Inter-CUs, or inter-gNBs. In this example, the two gNB-DUs negotiate the allocation of radio resources for terminal 101 for each cell based on the F1 and E1 interfaces. As shown in the network deployment diagram in Figure 2D, gNB-DU1 (corresponding to the second cell) and gNB-DU2 (corresponding to the first cell) belong to different gNB-CUs. gNB-DU1 requests reserved resources from gNB-DU2 in the first area sequentially through gNB-CU1 and gNB-CU2. Then, one of two scenarios will occur: either gNB-DU2 responds to the reserved resource request, i.e., the reserved resource request is successful; or gNB-DU2 responds to the reserved resource request, i.e., the reserved resource request fails. In other words, in this example, gNB-DU1 and gNB-DU2 will coordinate cell configurations interactively to ensure that their cell configuration information is at least partially identical.

[0277] In the fourth example, the cells in the first region belong to the same cloud device. Optionally, the cells in the first region belong to different TRPs within the same cloud device. In this example, the different TRPs within the same cloud device are shown in Figure 2E, where each TRP corresponds to a cell in the first region. As can be seen from Figure 2E, the same Cloud End includes multiple TRPs, and the protocol stack included in the Cloud End can be any of the following:

[0278] The first type: Non-Access Stratum (NAS), RRC, PDCP, RLC.

[0279] The second type: NAS, RRC, PDCP, RLC, MAC.

[0280] The third type includes NAS, RRC, PDCP, RLC, MAC, and some physical layer functions, such as baseband processing functions.

[0281] In step S2104, network device 102 sends first configuration information to terminal 101.

[0282] In some embodiments, terminal 101 receives first configuration information.

[0283] In some embodiments, the first configuration information is used to configure at least one TCI state, wherein the at least one TCI state is associated with at least one cell in the first region.

[0284] Optionally, each TCI state in at least one TCI state is associated with a cell in the first region, or each TCI state is associated with a PCI, or each TCI state is associated with a frequency.

[0285] Optionally, the PCI and / or frequency associated with each TCI state can be configured in the first configuration information.

[0286] Optionally, the Information Element (IE) for configuring TCI status can be referenced in the following example:

[0287] In some embodiments, for the first cell, if the network device 102 does not send the configuration information of the first cell to the terminal 101, the configuration information of the first cell can be assumed to be the same as the configuration information of the second cell, or the same as the configuration information of the serving cell with the same frequency as the first cell.

[0288] Optionally, the first cell represents the target cell, i.e. the cell after the cell change.

[0289] Optionally, the second cell refers to the source cell, i.e., the serving cell before the cell change. It can also be called the current serving cell.

[0290] In step S2105, network device 102 sends fourth configuration information to terminal 101.

[0291] In some embodiments, the fourth configuration information includes at least one of the following:

[0292] The TCI status list includes the TCI status associated with cells at the edge of the first region.

[0293] Parameters for measurement intervals.

[0294] In one example, as shown in Figure 2I, the cells in the first region are distributed in gray, and the cells in white are the cells at the center of the first region.

[0295] In this example, terminal 101 can determine whether step S2107 needs to be executed based on the location of the movement.

[0296] In some embodiments, if terminal 101 moves between cells in the center of the first area, RRM measurement may not be performed to achieve terminal energy saving. If terminal 101 moves to a cell at the edge of the first area, it is necessary to further determine whether RRM measurement needs to be performed.

[0297] In step S2106, network device 102 sends first instruction information to terminal 101.

[0298] In some embodiments, terminal 101 receives first instruction information.

[0299] The first indication information is used to indicate the changed TCI status, wherein the changed TCI status is associated with the first cell in the first region. The changed TCI status can also be an active TCI status.

[0300] In some embodiments, network device 102 sends L1 signaling to terminal 101, the L1 signaling including first indication information. Optionally, the L1 signaling may be DCI.

[0301] In some embodiments, network device 102 sends L2 signaling to terminal 101, the L2 signaling including first indication information. Optionally, the L2 signaling may be MAC CE.

[0302] In step S2107, the terminal determines whether to perform the measurement based on the fourth configuration information.

[0303] In some embodiments, if the changed TCI status is in the TCI status list, the terminal 101 performs an RRM measurement.

[0304] In some embodiments, if the changed TCI status is in the TCI status list and the measurement result of the second cell is less than the threshold, then terminal 101 performs RRM measurement. In other cases, terminal 101 may not perform RRM measurement.

[0305] Optionally, the measurement result of the second cell can be the Reference Signal Received Power (RSRP).

[0306] In some embodiments, the terminal may perform measurements of neighboring cells in the first region according to the measurement interval, such as performing measurements of the first cell.

[0307] In some embodiments, a neighboring cell satisfies at least one of the following: it operates at a different frequency than the serving cell; and the serving cell's active BWP (Bandwidth Part) does not contain the frequency domain location of the second cell reference signal. The reference signal may include a Synchronization Signal Block (SSB) or a Downlink Channel State Information Reference Signal (CSI-RS).

[0308] In some embodiments, after obtaining the measurement results, the terminal can report the measurement results.

[0309] In step S2108, network device 102 sends third instruction information to terminal 101.

[0310] In some embodiments, the third indication information is used to indicate at least one of the following: key change; MAC reset; PDCP reconstruction; RLC reconstruction; physical layer resource reconfiguration. Of course, the third indication information may also include other information.

[0311] In some embodiments, each of the different first regions has a corresponding key, on a region-by-region basis.

[0312] Optionally, a key can be generated based on the identifier of the first region input, or based on the identifier of the first region configured in the network device 102.

[0313] In some embodiments, terminal 101 receives third indication information. During movement, the terminal performs key change, MAC reset, PDCP reconstruction, RLC reconstruction, physical layer resource reconfiguration, etc., based on network-side indications.

[0314] In step S2109, terminal 101 determines, according to the first instruction information, that the serving cell has changed from the second cell in the first region to the first cell, and communicates with network device 102 based on the first cell.

[0315] In some embodiments, after receiving the first indication information, the terminal 101 determines the first cell associated with the changed TCI state according to the changed TCI state indicated by the first indication information; the beam can be adjusted based on beam association, and the terminal can communicate with the network device 102 based on the first cell.

[0316] Optionally, terminal 101 performs a TCI state change, switching from the TCI state corresponding to the second cell to the TCI state corresponding to the first cell. Then, it communicates with network device 102 based on the first cell.

[0317] Optionally, network device 102 may include a target base station corresponding to the first cell and a source base station corresponding to the second cell.

[0318] In some embodiments, before the serving cell is changed to the first cell, the second cell needs to notify the first cell to activate reserved resources, or at least have some of the same cell configuration information.

[0319] [Corrected according to Rule 91, June 19, 2025] In one example, as shown in the network deployment diagram in Figure 2G, it can be seen from Figure 2G that the Source gNB-DU (second cell) and the Target gNB-DU (first cell) belong to the same gNB-CU. The Source gNB-DU requests reserved resources from the Target gNB-DU in the first area through the gNB-CU. Then, one of two situations will occur: one is that the Target gNB-DU responds to the reserved resource request, that is, the reserved resource request is successful; the other is that the Target gNB-DU responds to the reserved resource request, that is, the reserved resource request fails.

[0320] Optionally, the first cell and the second cell have at least some of the same cell configuration information based on interactive negotiation, so that after the terminal 101 changes the cell, the first cell can provide services to the terminal 101 according to the cell configuration information.

[0321] [Corrected according to Rule 91, June 19, 2025] In another example, as shown in the network deployment diagram in Figure 2H, it can be seen from Figure 2H that Source gNB-DU1 (second cell) and Target gNB-DU2 belong to different gNB-CUs. Source gNB-DU1 requests reserved resources from Target gNB-DU2 through Source gNB-CU and Target gNB-CU in sequence. Then, one of two situations will occur: one is that Target gNB-DU2 responds to the reserved resource request, that is, the reserved resource request is successful; the other is that Target gNB-DU2 responds to the reserved resource request, that is, the reserved resource request fails.

[0322] Optionally, the first cell and the second cell have at least some of the same cell configuration information based on interactive negotiation, so that after the terminal 101 changes the cell, the first cell can provide services to the terminal 101 according to the cell configuration information.

[0323] Optionally, the first cell can identify the reserved resources that need to be activated via C-RNTI.

[0324] In some embodiments, the first cell can obtain the values ​​of state variables from the second cell to provide services to the terminal. For example, after the network device 102 sends the first indication information, that is, after notifying the terminal 101 to perform a TCI state switch to the TCI state corresponding to the first cell, the source cell, i.e., the second cell, can notify the target cell, i.e., the first cell, of the relevant state variables.

[0325] The state variables include at least one of the following: RLC entity receive window state variable; RLC entity transmit window state variable; PDCP entity receive window state variable; PDCP entity transmit window state variable; MAC parameter information.

[0326] Optionally, the MAC parameter information includes the settings for Discontinuous Reception (DRX) parameters, Sounding Reference Signal (SRS) transmission parameters, Power Headroom Report (PHR) transmission parameters, and the settings for two variables related to Buffer Status Report (BSR) parameters.

[0327] Alternatively, the value of the state variable can be initialized to 0 based on the instruction of network device 102.

[0328] In one example, the first cell initializes its state variables based on the values ​​of the state variables notified by the second cell, as shown in Tables 2-1 to 2-3 below, and sets the receiver variables according to the sender variables:

[0329] Table 2-1

[0330] Table 2-2

[0331] Table 2-3

[0332] In some embodiments, the network side may instruct the terminal to perform the handover process based on RRC commands within the area, or implement the handover process based on the LTM mechanism.

[0333] In some embodiments, when the network detects that the target cell for handover is outside its area, the network can execute the handover process based on RRC commands or based on the LTM mechanism.

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

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

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

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

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

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

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

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

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

[0343] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

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

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

[0346] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0347] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0348] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0349] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2109. For example, steps S2106 and S2109 may be implemented as independent embodiments, but are not limited thereto.

[0350] In some embodiments, at least one of steps S2101, S2102, S2103, S2104, S2107, and S2108 may be optionally omitted or substituted in different embodiments.

[0351] In some embodiments, steps S2101, S2103, and S2104 can be executed synchronously or in an interchangeable order.

[0352] In some embodiments, the order of steps S2103 is for illustrative purposes only. For example, steps S2103 may be performed before steps S2102 or before steps S2104.

[0353] In some embodiments, steps S2101, S2103, S2104, and S2105 can be executed synchronously, such as by sending different configuration information through a single signaling signal.

[0354] In some embodiments, step S2102 can be executed synchronously with any of S2101, S2103, S2104, and S2105, such as sending second instruction information and configuration information via a signaling.

[0355] In some embodiments, steps S2107 and 2108 are optionally omitted or substituted in different embodiments.

[0356] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0357] Figure 3A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the communication method of this embodiment includes:

[0358] In step S3101, network device 102 sends first instruction information to terminal 101.

[0359] In some embodiments, the implementation of step S3101 can be referred to the implementation of step S2106 in FIG2A, and will not be repeated here.

[0360] In step S3102, the terminal 101 determines, according to the first instruction information, that the serving cell has been changed from the second cell in the first region to the first cell, and communicates with the network device based on the first cell.

[0361] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2109 in FIG2A, and will not be repeated here.

[0362] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0363] Figure 3B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the communication method of this embodiment includes:

[0364] In step S3201, network device 102 sends first configuration information to terminal 101.

[0365] In some embodiments, the implementation of step S3202 can be referred to the implementation of step S2104 in FIG2A, and will not be repeated here.

[0366] In step S3202, network device 102 sends first instruction information to terminal 101.

[0367] In some embodiments, the implementation of step S3202 can be referred to the implementation of step S2106 in FIG2A, and will not be repeated here.

[0368] In step S3203, terminal 101 determines, according to the first instruction information, that the serving cell has changed from the second cell in the first region to the first cell, and communicates with the network device based on the first cell.

[0369] In some embodiments, the implementation of step S3203 can be found in the implementation of step S2109 in FIG2A, and will not be repeated here.

[0370] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0371] Figure 3C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, the communication method of this embodiment includes:

[0372] In step S3301, network device 102 sends fourth configuration information to terminal 101.

[0373] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2105 in FIG2A, and will not be repeated here.

[0374] In step S3302, network device 102 sends first instruction information to terminal 101.

[0375] In some embodiments, the implementation of step S3302 can be referred to the implementation of step S2106 in FIG2A, and will not be repeated here.

[0376] In step S3303, terminal 101 determines, according to the first instruction information, that the serving cell has changed from the second cell in the first region to the first cell, and communicates with the network device based on the first cell.

[0377] In some embodiments, the implementation of step S3303 can be referred to the implementation of step S2109 in FIG2A, and will not be repeated here.

[0378] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0379] This disclosure provides a communication method that avoids service interruptions caused by changing cells across regions, thereby improving mobile robustness and user experience. To facilitate understanding of these embodiments, some specific examples are described below.

[0380] Example 1:

[0381] The network device is configured with at least one TCI state, and each TCI state is associated with a PCI and / or frequency. When the terminal moves within the first area, it performs cell changes based on commands from the network device, which are either L1 commands (e.g., DCI) or L2 commands (e.g., MAC CE). These commands change the serving cell by altering the TCI state.

[0382] Optionally, at least one TCI state configured by the network device corresponds to the first configuration information in the foregoing embodiments, and the command corresponds to the first instruction information in the foregoing embodiments.

[0383] Example 2:

[0384] Based on Example 1, the network device configures a first area via RRC dedicated signaling. Simultaneously, the C-RNTI that has already been configured or is currently configured together with the first area is associated with the first area. This means that the terminal uses the C-RNTI while moving within the first area. The first area can be represented by a cell list, such as a "frequency+PCI" list.

[0385] Optionally, the RRC dedicated signaling corresponds to the second configuration information in the aforementioned embodiments.

[0386] Example 3:

[0387] Based on Embodiments 1 and 2, the network device configures the configuration information of each cell in the first area through RRC dedicated signaling. The configuration information includes, but is not limited to: cell identification information of the area where the cell is located, used for cell management or area management, common configuration information of the cell (configuration information contained in sCellConfigCommon in the reference protocol), and cell-specific configuration information (configuration information contained in sCellConfigDedicated in the reference protocol).

[0388] Optionally, the configuration information for each cell corresponds to the third configuration information in the aforementioned embodiments.

[0389] Example 4:

[0390] Based on Examples 1 to 3, the C-RNTI can be a 16-bit C-RNTI or a longer C-RNTI, such as a 24-bit C-RNTI.

[0391] The first scenario: Determine whether a 16-bit C-RNTI or a 24-bit C-RNTI has been allocated based on network device indications.

[0392] Optionally, the terminal performs a random access procedure to allocate a C-RNTI in the RAR. The length of the C-RNTI is indicated in the RAR as either 16 bits or 24 bits, which can be indicated in the RAR sub-header or within the RAR itself, as shown in Figure 2F.

[0393] The second scenario: For IoT devices, a fixed 24-bit C-RNTI is allocated.

[0394] Optionally, if the IoT device can inform the network device that it is an IoT device via MSG1 during random access, the network device can allocate a 24-bit C-RNTI in the RAR. Alternatively, it can distinguish whether the terminal expects a 24-bit or 16-bit C-RNTI based on RO or preamble.

[0395] The third scenario: The terminal is initially assigned a 16-bit C-RNTI, and the network device can then be reconfigured to assign a 24-bit C-RNTI.

[0396] In this embodiment, variable-size C-RNTIs are supported.

[0397] Example 5:

[0398] Based on embodiments 1 to 4 above, as shown in Figure 2I, when the terminal is in the center of the first region, the terminal may not perform RRM measurement. RRM measurement may only be initiated when the terminal is at the edge of the first region, including the following two situations:

[0399] The first scenario: The network device is configured with a list of TCI states. When the active TCI state of the network device is a TCI state in the list of TCI states, RRM measurement is started; otherwise, RRM measurement is not started.

[0400] The second scenario: The network device is configured with a TCI state list. When the network device activates a TCI state that is in the TCI state list, and the RSRP of the second cell is less than the threshold configured on the network side, then RRM measurement is started; otherwise, RRM measurement is not started.

[0401] Optionally, the activated TCI state corresponds to the modified TCI state in the foregoing embodiments.

[0402] Optionally, this embodiment can achieve energy saving by skipping RRM measurements within the area 3), i.e., during movement within the edge-less cell.

[0403] Example 6:

[0404] Based on embodiments 1 to 5 above, when the terminal moves within the first area, the network device indicates the terminal's latest TCI state via L1 / L2 commands. The network device can also perform the handover process based on RRC commands or the LTM mechanism within the first area.

[0405] In some embodiments, when a network device detects that the target cell for handover is outside its area, the network device executes the handover process based on RRC commands or implements the handover process based on the LTM mechanism.

[0406] In some embodiments, during terminal movement, the terminal performs key change, MAC reset, PDCP reconstruction, RLC reconstruction, physical layer resource reconfiguration, etc., based on instructions from the network device.

[0407] In some embodiments, if the network device does not configure the configuration information of the cell where the target TCI state resides, the default configuration information is the same as the configuration of the currently serving cell. Alternatively, it may be the same as the configuration of a serving cell with the same frequency information among the currently serving cells.

[0408] Optionally, the target cell corresponds to the first cell in the foregoing embodiments, the region corresponds to the first region in the foregoing embodiments, the target TCI state corresponds to the modified TCI state in the foregoing embodiments, and the current serving cell corresponds to the second cell in the foregoing embodiments.

[0409] Example 7:

[0410] Based on the above embodiments 1 to 6, as shown in Figures 2B to 2E, the network deployment between cells in the first region may be intra-DU, or Inter-DU intra-CU or Inter-CU, or it may be “Cloud-end” + TRP network deployment.

[0411] The first scenario: intra-DU (intra-gNB)

[0412] Based on network devices, the system coordinates the allocation of radio resources for terminals in each cell. The resource allocation includes the cell's common configuration information (configuration information contained in sCellConfigCommon in the reference protocol), cell-specific configuration information (configuration information contained in sCellConfigDedicated in the reference protocol), C-RNTI, etc.

[0413] Second scenario: Inter-DU intra-CU

[0414] As shown in Figure 2C, the two DUs negotiate the allocation of radio resources for each terminal in each cell based on the F1 interface. For example, gNB-DU1, as the current serving cell, requests resources to be reserved by all cells in the aforementioned area.

[0415] The third scenario: Inter-CU (inter-gNB)

[0416] As shown in Figure 2D, the two DUs negotiate the allocation of radio resources for each terminal in each cell based on the F1 and E1 interfaces. For example, gNB-DU1 is the current serving cell and requests resources to be reserved by all cells in the above area.

[0417] The fourth scenario: Cloud-end + TRP

[0418] As shown in Figure 2E, in this architecture, the first region belongs to different TRPs within the same "Cloud-end". The protocol stack contained in the "Cloud-end" may be:

[0419] The first type: NAS, RRC, PDCP, RLC.

[0420] The second type: NAS, RRC, PDCP, RLC, MAC.

[0421] The third type includes NAS, RRC, PDCP, RLC, MAC, and some physical layer functions, such as baseband processing functions.

[0422] Example 8:

[0423] Based on embodiments 1 to 7 above, as shown in Figures 2G to 2H, before notifying the terminal to perform a TCI state change to the target cell's TCI state, the serving cell notifies the target cell to activate reserved resources. For example, the reserved resources to be activated are identified through C-RNTI.

[0424] In some embodiments, after the notifying terminal to perform a TCI state change to the target cell's TCI state, the serving cell notifies the target cell of the settings for the receive window state variables, transmit window state variables, and MAC-related parameters for each bearer of the network device, such as the DRX parameter setting, SRS transmission, PHR transmission, and the settings for two variables related to the BSR parameter. Alternatively, based on network device instructions, the state variables are initialized to 0.

[0425] Optionally, the target cell corresponds to the first cell in the foregoing embodiments, and the serving cell corresponds to the second cell in the foregoing embodiments.

[0426] It should be noted that the above embodiments 1 to 8 are applicable to both intra-frequency and inter-frequency scenarios. An inter-frequency scenario is one where the first region contains inter-frequency cells. Additionally, there are embodiments 9 to 11 for inter-frequency scenarios.

[0427] Example 9:

[0428] Based on the above embodiments, for different frequency scenarios, in order to support different frequency scenarios, the model can be divided into two types.

[0429] The first model:

[0430] Model 1.1: A CA-based model. In the first region, the frequency of a cell is at least the same as the frequency of the serving cell of another cell. For example, in a CA scenario, the serving cells are serving cell1, serving cell2, and serving cell3. Their corresponding frequency layers are f1, f2, and f3, respectively. The frequencies of cells within the first region, and those of non-serving cells, must be one of f1, f2, or f3.

[0431] Model 1.2: CA-based model. In the first area, all cells are configured as a serving cell in the CA scenario, regardless of whether the frequencies of these cells meet the band combination capability supported by the UE. However, the activated serving cell may not meet the band combination capability supported by the UE.

[0432] In Models 1.1 and 1.2 above, the configuration information of cells in the first region is the same as that of serving cells at the same frequency.

[0433] The second model:

[0434] The network device configures at least one cell configuration for cells within the first area. Each cell configuration is associated with a cell list, where each cell in the cell list belongs to a cell within the area. Cell configuration information includes common cell configuration information (configuration information contained in sCellConfigCommon in the reference protocol), cell-specific configuration information (configuration information contained in sCellConfigDedicated in the reference protocol), C-RNTI, etc. The terminal finds the cell configuration associated with the cell associated with the latest activated TCI state and determines the activated cell configuration.

[0435] Optionally, this embodiment supports edge-less cells with different frequencies and edge-less cells with the same frequency, and the process of configuring edge-less cells and activating reserved resources based on CA model and non-CA model.

[0436] Example 10:

[0437] The network side configures a measurement gap, which is used for measuring other cells in the first area. At this time, other cells are not the serving cells of the terminal, and / or are not on the same frequency as the serving cell, and / or the BWP activated by the serving cell does not include the SSB or CSI-RS frequency domain location of other cells.

[0438] Optionally, the measurement gap corresponds to the measurement interval in the foregoing embodiments, and other cells correspond to the neighboring cells in the foregoing embodiments.

[0439] Example 11:

[0440] The key is valid per area. To generate the key, you can enter the area ID or an ID configured on the network side.

[0441] Optionally, area id corresponds to the area identifier in the foregoing embodiments.

[0442] In some embodiments, the order of some or all of the embodiments from Embodiments 1 to 11 above is only illustrative and can be adjusted in actual implementation, such as allowing configuration-related information to be sent synchronously. One or more of Embodiments 1 to 11 above can be implemented in combination.

[0443] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

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

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

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

[0447] [Correction based on Rule 91, June 19, 2025] Figure 4A is a schematic diagram of a terminal according to an embodiment of this disclosure. Terminal 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, terminal 4100 may include at least one of: a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to receive first indication information sent by a network device, the first indication information indicating a changed Transmission Configuration Indicator (TCI) state, wherein the changed TCI state is associated with a first cell in a first region; the processing module 4102 is used to determine, based on the first indication information, that the serving cell has changed from a second cell in the first region to the first cell, and to communicate with the network device based on the first cell.

[0448] Optionally, the transceiver module 4101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be described in detail here. Optionally, the processing module 4102 is used to perform at least one of the other steps performed by the terminal in any of the above methods, which will not be described in detail here.

[0449] [Correction based on Rule 91, June 19, 2025] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send first indication information to a terminal, the first indication information indicating a changed Transmission Configuration Indicator (TCI) state, wherein the changed TCI state is associated with a first cell in a first region, and the first indication information is used by the terminal to determine that the serving cell has changed from a second cell in the first region to the first cell, and to communicate with the network device based on the first cell.

[0450] Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be described in detail here. Optionally, the processing module 4202 is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be described in detail here.

[0451] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0452] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0453] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

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

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

[0456] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

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

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

[0459] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, the schematic diagram of chip 5200 shown in Figure 5B can be referred to, but is not limited thereto.

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

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

[0462] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

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

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

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

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

[0467] The terminal learns the changed TCI status by receiving the first instruction information, and determines the change of the serving cell in the first area based on the association between the TCI status and the first cell in the first area and the beam management method. This can avoid service interruption caused by cell handover process and improve mobile robustness and user experience.

Claims

1. A communication method, executed by a terminal, the method comprising: The network device receives first indication information, which is used to indicate the changed Transmission Configuration Indicator (TCI) status, wherein the changed TCI status is associated with a first cell in a first region. Based on the first indication information, it is determined that the serving cell has been changed from the second cell in the first region to the first cell, and communication with the network device is based on the first cell.

2. The method as described in claim 1, wherein, The method further includes: The network device receives first configuration information, which is used to configure at least one TCI state, wherein the at least one TCI state is associated with at least one cell in the first region.

3. The method as described in claim 1 or 2, wherein, The method further includes: The system receives second configuration information sent by the network device, the second configuration information being used to configure the first area.

4. The method of claim 3, wherein, The second configuration information includes a list of cells corresponding to the first region; the cell list includes at least one of the following: Frequency list of the cell; List of Physical Cell Identifiers (PCIs) for the residential community.

5. The method according to any one of claims 1 to 4, wherein, The first region is associated with a cell wireless network temporary identifier (C-RNTI).

6. The method of claim 5, wherein, The bit length of the C-RNTI is either a first length or a second length, wherein the second length is greater than the first length.

7. The method of claim 5 or 6, wherein, The method further includes: Receive a second indication message sent by the network device, the second indication message being used to indicate one of the following: The bit length of the C-RNTI is either a first length or a second length; The bit length of the C-RNTI is the second length, wherein the device type of the terminal is an Internet of Things (IoT) device; The second length of the C-RNTI is reallocated, wherein the terminal was initially assigned the first length of the C-RNTI.

8. The method according to any one of claims 1 to 7, wherein, The method further includes: The network device receives third configuration information, which is used to configure cell configuration information corresponding to the cells in the first area; wherein the cell configuration information includes at least one of the following: Community signage information; Community public facilities information; Community-specific configuration information; Information used to indicate whether the cell configuration information is used for cell management or for the management of the first area.

9. The method according to any one of claims 1 to 8, wherein, The cells in the first region satisfy at least one of the following: They belong to the same distribution unit DU; Belongs to different DUs; Belonging to the same lumped unit CU; Belonging to different CUs; They belong to the same cloud device.

10. The method of claim 9, wherein, When belonging to the same DU or the same cloud device, the cell configuration information corresponding to the first cell and the second cell is determined based on the network device; or... When belonging to different DUs or different CUs, at least partially identical cell configuration information is determined based on the interaction between the first cell and the second cell.

11. The method according to any one of claims 1 to 10, wherein, The cells in the first region are co-frequency cells; or, the first region includes inter-frequency cells, wherein the inter-frequency cells satisfy at least one of the following: The frequency of the heterogeneous cell is the same as that of any serving cell in the carrier aggregation CA configured for the terminal; The inter-frequency cell is configured as a serving cell in the CA; Each cell in the heterogeneous frequency cell is configured with an associated cell list.

12. The method as claimed in any one of claims 1 to 11, wherein, The method further includes: The network device receives fourth configuration information, which includes at least one of the following: The TCI status list includes TCI statuses associated with cells at the edge of the first region; Parameters for measurement intervals.

13. The method of claim 12, wherein, The method also includes the following: The modified TCI status is located in the TCI status list, and the terminal performs Radio Resource Management (RRM) measurements. If the changed TCI status is in the TCI status list and the measurement result of the second cell is less than the threshold, the terminal performs Radio Resource Management (RRM) measurement.

14. The method of claim 12, wherein, The method further includes: Measurements are performed on neighboring cells within the first area according to the measurement interval, wherein the neighboring cells satisfy at least one of the following: The frequency is different from that of the serving cell; The active bandwidth portion (BWP) of the serving cell does not include the frequency domain location of the second cell reference signal.

15. The method as claimed in any one of claims 1 to 14, wherein, The method further includes: Receive third indication information sent by the network device, the third indication information being used to indicate at least one of the following: Key update; Media access control MAC reset; Packet Data Convergence Protocol (PDCP) reconstruction; Radio Link Control (RLC) reconstruction; Physical layer resource reallocation.

16. The method of claim 15, wherein, Each of the first regions has a corresponding key, with each region being a separate region.

17. The method as claimed in any one of claims 1 to 16, wherein, The first cell obtains the value of a state variable through the second cell, wherein the state variable includes at least one of the following: RLC entity receive window status variables; The RLC entity sends the window status variable; PDCP entity receive window state variables; The PDCP entity sends the window status variable; MAC parameter information.

18. A communication method performed by a network device, the method comprising: Send a first indication message to the terminal. The first indication message is used to indicate the changed Transmission Configuration Indicator (TCI) status. The changed TCI status is associated with a first cell in a first region. The first indication message is used by the terminal to determine that the serving cell has changed from a second cell in the first region to the first cell, and to communicate with the network device based on the first cell.

19. The method of claim 18, wherein, The method further includes: Send first configuration information to the terminal. The first configuration information is used to configure at least one TCI state, wherein the at least one TCI state is associated with at least one cell in the first region.

20. The method of claim 18 or 19, wherein, The method further includes: Send second configuration information to the terminal, the second configuration information being used to configure the first region.

21. The method of claim 20, wherein, The second configuration information includes a list of cells corresponding to the first region; the cell list includes at least one of the following: Frequency list of the cell; List of Physical Cell Identifiers (PCIs) for the residential community.

22. The method as claimed in any one of claims 18 to 21, wherein, The first region is associated with a cell wireless network temporary identifier (C-RNTI).

23. The method of claim 22, wherein, The bit length of the C-RNTI is either a first length or a second length, wherein the second length is greater than the first length.

24. The method of claim 22 or 23, wherein, The method further includes: Send a second indication message to the terminal, the second indication message being used to indicate one of the following: The bit length of the C-RNTI is either a first length or a second length; The bit length of the C-RNTI is the second length, wherein the device type of the terminal is an Internet of Things (IoT) device; The second length of the C-RNTI is reallocated, wherein the terminal was initially assigned the first length of the C-RNTI.

25. The method as claimed in any one of claims 18 to 24, wherein, The method further includes: Send third configuration information to the terminal, the third configuration information being used to configure cell configuration information corresponding to the cells in the first area; wherein, the cell configuration information includes at least one of the following: Community signage information; Community public facilities information; Community-specific configuration information; Information used to indicate whether the cell configuration information is used for cell management or for the management of the first area.

26. The method as claimed in any one of claims 18 to 25, wherein, The cells in the first region satisfy at least one of the following: They belong to the same distribution unit DU; Belongs to different DUs; Belonging to the same lumped unit CU; Belonging to different CUs; They belong to the same cloud device.

27. The method of claim 26, wherein, When belonging to the same DU or the same cloud device, the cell configuration information corresponding to the first cell and the second cell is determined based on the network device; or... When belonging to different DUs or different CUs, at least partially identical cell configuration information is determined based on the interaction between the first cell and the second cell.

28. The method as claimed in any one of claims 18 to 27, wherein, The cells in the first region are co-frequency cells; or, the first region includes inter-frequency cells, wherein the inter-frequency cells satisfy at least one of the following: The frequency of the heterogeneous cell is the same as that of any serving cell in the carrier aggregation CA configured for the terminal; The inter-frequency cell is configured as a serving cell in the CA; Each cell in the heterogeneous frequency cell is configured with an associated cell list.

29. The method as claimed in any one of claims 18 to 27, wherein, The method further includes: Send fourth configuration information to the terminal, the fourth configuration information including at least one of the following: The TCI status list includes TCI statuses associated with cells at the edge of the first region; Parameters for measurement intervals.

30. The method of claim 29, wherein, The modified TCI status is located in the TCI status list, and the terminal is used to perform Radio Resource Management (RRM) measurements. The modified TCI status is located in the TCI status list, and the measurement result of the second cell is less than the threshold. The terminal is used to perform Radio Resource Management (RRM) measurements.

31. The method of claim 29, wherein, The measurement interval is used to perform measurements on neighboring cells within the first area, wherein the neighboring cells satisfy at least one of the following: The frequency is different from that of the serving cell; The active bandwidth portion (BWP) of the serving cell does not include the frequency domain location of the second cell reference signal.

32. The method according to any one of claims 17 to 31, wherein, The method further includes: Send a third indication message to the terminal, the third indication message being used to indicate at least one of the following: Key update; Media access control MAC reset; Packet Data Convergence Protocol (PDCP) reconstruction; Radio Link Control (RLC) reconstruction; Physical layer resource reallocation.

33. The method of claim 32, wherein, Each of the first regions has a corresponding key, with each region being a separate region.

34. The method according to any one of claims 18 to 33, wherein, The first cell obtains the value of a state variable through the second cell, wherein the state variable includes at least one of the following: RLC entity receive window status variables; The RLC entity sends the window status variable; PDCP entity receive window state variables; The PDCP entity sends the window status variable; MAC parameter information.

35. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 17 or any one of claims 18 to 34.

36. A communication system comprising a terminal and network equipment, wherein, The terminal is configured to implement the method as described in any one of claims 1 to 17; The network device is configured to implement the method as described in any one of claims 18 to 34.

37. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 17 or any one of claims 18 to 34.

38. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 17 or any one of claims 18 to 34.

Images