Communication method, terminal, network device and storage medium

Abstract

The invention relates to a communication method, a terminal, network equipment and a storage medium. The method comprises the following steps: receiving first information sent by first network equipment; under the condition that the first condition is met, receiving second information sent by second network equipment; wherein the first network equipment comprises a low-frequency cell, and the second network equipment comprises a high-frequency cell. In the method disclosed by the invention, communication can be performed based on the first network equipment and the second network equipment, so that low-frequency resources and high-frequency resources can be reasonably utilized.

Description

Communication methods, terminals, network devices and storage media Technical Field

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

[0002] With the advancement of communication technology, the power consumption of network equipment continues to increase. 5G base stations have high bit rates and high speeds, and the power consumption of a single base station is several times that of a 4G base station. The energy consumption of base stations brings huge network operation and maintenance costs to operators.

[0003] Summary of the Invention

[0004] The methods for utilizing high-frequency or low-frequency spectrum resources in relevant base stations need to be improved.

[0005] This disclosure provides a communication method, terminal, device, and storage medium.

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

[0007] Receive the first information sent by the first network device;

[0008] If the first condition is met, receive the second information sent by the second network device;

[0009] The first network device includes a low-frequency cell, and the second network device includes a high-frequency cell.

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

[0011] Sending first information to the terminal, wherein, when a first condition is met, a second network device is used to send second information, wherein the first network device includes a low-frequency cell and the second network device includes a high-frequency cell.

[0012] Thirdly, embodiments of this disclosure provide a communication method executed by a second network device, the method comprising:

[0013] When the first condition is met, the second information is sent to the terminal, wherein the first network device is used to send the first information, and the first network device includes a low-frequency cell, and the second network device includes a high-frequency cell.

[0014] Fourthly, embodiments of this disclosure provide a communication system, including: a terminal, a first network device, and a second network device;

[0015] The terminal is used to execute the method described in the first aspect;

[0016] The first network device is used to perform the method described in the second aspect;

[0017] The second network device is used to perform the method described in the third aspect.

[0018] Fifthly, embodiments of this disclosure provide a terminal, including:

[0019] The transceiver module is configured to receive first information sent by a first network device; and to receive second information sent by a second network device when a first condition is met, wherein the first network device includes a low-frequency cell and the second network device includes a high-frequency cell.

[0020] Sixthly, embodiments of this disclosure provide a network device, including:

[0021] The transceiver module is used to send first information to the terminal or send second information to the terminal when a first condition is met. When the first condition is met, a second network device is used to send the second information. The network device includes a low-frequency cell or a high-frequency cell.

[0022] In a seventh aspect, embodiments of this disclosure provide a communication device, including:

[0023] One or more processors;

[0024] The communication device is configured to implement the method described in the first aspect, or the second aspect, or the third aspect.

[0025] Eighthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

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

[0027] Ninthly, embodiments of this disclosure provide a program product, wherein,

[0028] When the program product is executed by a communication device, the communication device performs the method as described in the first aspect, or the second aspect, or the third aspect.

[0029] In this embodiment of the disclosure, communication can be based on the first network device and the second network device, which facilitates the rational use of low-frequency and high-frequency resources. Attached Figure Description

[0030] 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.

[0031] Figures 1a and 1b are exemplary schematic diagrams of the architecture of a communication system provided according to embodiments of the present disclosure;

[0032] Figures 2a to 2f are exemplary interactive schematic diagrams of a method provided according to an embodiment of the present disclosure;

[0033] Figures 3a to 3e are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0034] Figures 4a and 4b are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0035] Figure 5 is an exemplary flowchart of a method provided according to an embodiment of the present disclosure;

[0036] Figure 6a is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0037] Figure 6b is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0038] Figure 7a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0039] Figure 7b is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0040] This disclosure provides a communication method, terminal, device, and storage medium.

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

[0042] Receive the first information sent by the first network device;

[0043] If the first condition is met, receive the second information sent by the second network device;

[0044] The first network device includes a low-frequency cell, and the second network device includes a high-frequency cell.

[0045] In the above embodiments, communication can be based on the first network device and the second network device, which facilitates the rational use of low-frequency resources and saves energy, or uses high-frequency resources to improve the user experience.

[0046] In conjunction with the embodiments of the first aspect, in some embodiments, the configuration information of the first network device and the second network device are different; the configuration information includes at least one of the following:

[0047] Does it support sending public signals?

[0048] Does it support sending system broadcast messages?

[0049] Does it support paging?

[0050] Does it support the initial RACH access process?

[0051] In conjunction with the embodiments of the first aspect, in some embodiments, the first information is one of the following:

[0052] RRC signaling;

[0053] Information used for neighborhood search.

[0054] In conjunction with the embodiments of the first aspect, in some embodiments, the first information includes at least one of the following:

[0055] Low-frequency list;

[0056] The list of high-frequency frequencies configured for the first network device;

[0057] Synchronization Signal Block (SSB);

[0058] System Information (SI).

[0059] In conjunction with the embodiments of the first aspect, in some embodiments, the second information is information used for cell search.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes: sending request information to a second network device, the request information being used to request second information.

[0061] In conjunction with the embodiments of the first aspect, in some embodiments, the first condition includes at least one of the following:

[0062] There are no low-frequency cells available for residential use;

[0063] The measurement result for the high-frequency cell is greater than or equal to the threshold configured by the first network device.

[0064] In conjunction with the embodiments of the first aspect, in some embodiments, the second information includes at least one of the following:

[0065] SSB;

[0066] System Information Block SIB1;

[0067] The terminal is in the Radio Resource Control (RRC) idle state.

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

[0069] When the second condition is met, high-frequency cells are not searched or selected.

[0070] In conjunction with the embodiments of the first aspect, in some embodiments, the second condition includes at least one of the following:

[0071] High-frequency cells do not allow camping;

[0072] The high-frequency cell does not belong to the cell corresponding to the frequency list configured in the first network device;

[0073] The SSB transmitted by the high-frequency cell is not on the synchronization grid;

[0074] The MIB in the SSB sent by the high-frequency cell indicates that the high-frequency cell is in a prohibited access state.

[0075] In conjunction with the embodiments of the first aspect, in some embodiments, the request information is sent on the sub-band full-duplex SBFD time-domain resource.

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

[0077] Based on frequency priority and / or frequency band combination BC capability, select or reselect the cell to stay in.

[0078] In conjunction with the embodiments of the first aspect, in some embodiments, the frequency priority of a low-frequency cell is higher than the frequency priority of a high-frequency cell; or, a cell with a higher frequency priority is determined based on at least one of the frequency priority, the frequency range FR priority, and the sub-priority of a configured or defined frequency priority.

[0079] In conjunction with the embodiments of the first aspect, in some embodiments, the frequency priority satisfies at least one of the following:

[0080] Configuring or defining frequency layers on a frequency basis, with different frequency priorities corresponding to different frequency layers;

[0081] The frequency layers in different frequency bands are configured or defined in units of frequency bands, and the frequency priorities are different.

[0082] Frequency layers are configured or defined in units of frequency layers (FRs), and the frequency priorities in different FRs are different.

[0083] In conjunction with the embodiments of the first aspect, in some embodiments, the stationed cell belongs to a cell in the BC supported by the terminal.

[0084] In conjunction with the embodiments of the first aspect, in some embodiments, the first information is a paging message, wherein the first network device and the second network device located in the same geographical area have the same Tracking Area Code (TAC); or,

[0085] The first condition is that the first network device and the second network device, which are located in the same geographical area, have different TACs. The first information is the paging message sent by the first network device, and the second information is the paging message sent by the second network device.

[0086] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes: performing a re-registration process when selecting or reselecting to a high-frequency cell;

[0087] Send a first instruction message to the first network device. The first instruction message is used to instruct the terminal to camp on a high-frequency cell.

[0088] In conjunction with the embodiments of the first aspect, in some embodiments, the TAC includes an indicator bit, which is used to indicate that the network device corresponding to the TAC is a first network device or the indicator bit is used to indicate that the network device corresponding to the TAC is a second network device.

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

[0090] Send a first measurement report to the first network device. The first measurement report includes measurement results of the frequency layer of the control plane.

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

[0092] Switch to low-frequency cell;

[0093] New high-frequency cells;

[0094] Maintain existing high-frequency cells;

[0095] Release existing high-frequency cells.

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

[0097] Receive beam indication information sent by the first network device or the second network device.

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

[0099] When a terminal in an RRC inactive state is camped on a high-frequency cell, it requests the RRC recovery process.

[0100] Enter RRC connected state or RRC idle state according to the instructions of the first network device.

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

[0102] A second measurement report is sent to the first network device. The second measurement report is used to indicate the type of cell being measured and is also used by the first network device to update the Automatic Neighbor Relationship (ANR).

[0103] In conjunction with the embodiments of the first aspect, in some embodiments, the cell type includes at least one of the following:

[0104] Coverage rate of the community;

[0105] Capacity-type residential communities;

[0106] Control plane area;

[0107] User-facing community;

[0108] Whether it is a high-frequency cell that supports being dynamically turned on or off;

[0109] Among them, low-frequency cells are coverage cells or control area cells.

[0110] In conjunction with the embodiments of the first aspect, in some embodiments, the identifier length for the first network device is shorter than the identifier length for the second network device.

[0111] In conjunction with the embodiments of the first aspect, in some embodiments, the first information or the second information includes third indication information, which is used to indicate the identification length of the first network device or the identification length of the second network device.

[0112] In conjunction with the embodiments of the first aspect, in some embodiments, the context of the terminal is stored in the first network device.

[0113] In conjunction with the embodiments of the first aspect, in some embodiments, the control plane of the terminal is located in a low-frequency network, and the user plane of the terminal is located in a high-frequency network.

[0114] In conjunction with the embodiments of the first aspect, in some embodiments, the low-frequency cell is used for the control plane; and / or

[0115] The high-frequency cell is used for the user plane.

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

[0117] Sending first information to the terminal, wherein, when a first condition is met, a second network device is used to send second information, wherein the first network device includes a low-frequency cell and the second network device includes a high-frequency cell.

[0118] In conjunction with the embodiments of the second aspect, in some embodiments, the configuration information of the first network device and the second network device are different; the configuration information includes at least one of the following:

[0119] Does it support sending public signals?

[0120] Does it support sending system broadcast messages?

[0121] Does it support paging?

[0122] Does it support the initial RACH access process?

[0123] In conjunction with the embodiments of the second aspect, in some embodiments, the first information is one of the following:

[0124] RRC signaling;

[0125] Information used for neighborhood search.

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

[0127] Low-frequency list;

[0128] The list of high-frequency frequencies configured for the first network device;

[0129] Synchronization Signal Block (SSB);

[0130] System Information (SI).

[0131] In conjunction with the embodiments of the second aspect, in some embodiments, the frequency priority of low-frequency cells is higher than the frequency priority of high-frequency cells; or,

[0132] A cell with high frequency priority is determined based on at least one of the following: frequency priority, frequency range (FR) priority, or sub-priority of the configured or defined frequency priority.

[0133] In conjunction with the embodiments of the second aspect, in some embodiments, the frequency priority satisfies at least one of the following:

[0134] Configuring or defining frequency layers on a frequency basis, with different frequency priorities corresponding to different frequency layers;

[0135] The frequency layers in different frequency bands are configured or defined in units of frequency bands, and the frequency priorities are different.

[0136] Frequency layers are configured or defined in units of frequency layers (FRs), and the frequency priorities in different FRs are different.

[0137] In conjunction with embodiments of the second aspect, in some embodiments, sending at least one piece of information to the terminal includes:

[0138] The first information is a paging message, wherein the first network device and the second network device located in the same geographical area have the same tracking area code (TAC), or the first condition is that the first network device and the second network device located in the same geographical area have different TACs, wherein at least one information includes a paging message.

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

[0140] The receiving terminal sends a first indication message, which is used to indicate that the terminal is camped on a high-frequency cell.

[0141] In conjunction with the embodiments of the second aspect, in some embodiments, the TAC includes an indicator bit, which is used to indicate that the network device corresponding to the TAC is a first network device or the indicator bit is used to indicate that the network device corresponding to the TAC is a second network device.

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

[0143] The receiving terminal sends a first measurement report, which includes measurement results of the frequency layer of the control plane.

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

[0145] Switch to low-frequency cell;

[0146] New high-frequency cells;

[0147] Maintain existing high-frequency cells;

[0148] Release existing high-frequency cells.

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

[0150] Send beam indication information to the terminal.

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

[0152] The receiving terminal sends a second measurement report, which is used to indicate the type of cell being measured and is also used by the first network device to update the Automatic Neighbor Relationship (ANR).

[0153] In conjunction with the embodiments of the second aspect, in some embodiments, the cell type includes at least one of the following:

[0154] Coverage rate of the community;

[0155] Capacity-type residential communities;

[0156] Control plane area;

[0157] User-facing community;

[0158] Whether it is a high-frequency cell that supports being dynamically turned on or off;

[0159] Among them, low-frequency cells are coverage cells or control area cells.

[0160] In conjunction with the embodiments of the second aspect, in some embodiments, the identifier length for the first network device is shorter than the identifier length for the second network device.

[0161] In conjunction with the embodiments of the second aspect, in some embodiments, the first information includes third indication information, which is used to indicate the identifier length of the first network device or the identifier length of the second network device.

[0162] In conjunction with embodiments of the second aspect, in some embodiments, the first network device stores the context of the terminal.

[0163] In conjunction with the embodiments of the second aspect, in some embodiments, the control plane of the terminal is located in a low-frequency network, and the user plane of the terminal is located in a high-frequency network.

[0164] In conjunction with embodiments of the second aspect, in some embodiments, the low-frequency cell is used for the control plane; and / or

[0165] The high-frequency cell is used for the user plane.

[0166] Thirdly, embodiments of this disclosure provide a communication method executed by a second network device, the method comprising:

[0167] When the first condition is met, the second information is sent to the terminal, wherein the first network device is used to send the first information, and the first network device includes a low-frequency cell, and the second network device includes a high-frequency cell.

[0168] In conjunction with the embodiments of the third aspect, in some embodiments, the configuration information of the first network device and the second network device are different; the configuration information includes at least one of the following:

[0169] Does it support sending public signals?

[0170] Does it support sending system broadcast messages?

[0171] Does it support paging?

[0172] Does it support the initial RACH access process?

[0173] In conjunction with the embodiments of the third aspect, in some embodiments, the second information includes information for cell search, and the method further includes: receiving request information sent by a terminal, the request information being used to request the second information.

[0174] In conjunction with embodiments of the third aspect, in some embodiments, the first condition includes at least one of the following:

[0175] There are no low-frequency cells available for residential use;

[0176] The measurement result for the high-frequency cell is greater than or equal to the threshold configured by the first network device.

[0177] In conjunction with embodiments of the third aspect, in some embodiments, the second information includes at least one of the following:

[0178] SSB;

[0179] System Information Block SIB1;

[0180] The terminal is in the Radio Resource Control (RRC) idle state.

[0181] In conjunction with the embodiments of the third aspect, in some embodiments, the frequency priority of low-frequency cells is higher than the frequency priority of high-frequency cells; or,

[0182] A cell with high frequency priority is determined based on at least one of the following: frequency priority, frequency range (FR) priority, or sub-priority of the configured or defined frequency priority.

[0183] In conjunction with embodiments of the third aspect, in some embodiments, the frequency priority satisfies at least one of the following:

[0184] Configuring or defining frequency layers on a frequency basis, with different frequency priorities corresponding to different frequency layers;

[0185] The frequency layers in different frequency bands are configured or defined in units of frequency bands, and the frequency priorities are different.

[0186] Frequency layers are configured or defined in units of frequency layers (FRs), and the frequency priorities in different FRs are different.

[0187] In conjunction with embodiments of the third aspect, in some embodiments, the second information includes a paging message, wherein the first condition is that a first network device and a second network device located in the same geographical area have different TACs, and wherein at least one piece of information includes a paging message.

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

[0189] Send beam indication information to the terminal.

[0190] In conjunction with the embodiments of the third aspect, in some embodiments, the identifier length for the first network device is shorter than the identifier length for the second network device.

[0191] In conjunction with embodiments of the third aspect, in some embodiments, the second information includes third indication information, which is used to indicate the identifier length of the first network device or the identifier length of the second network device.

[0192] In conjunction with the embodiments of the third aspect, in some embodiments, the control plane of the terminal is located in a low-frequency network, and the user plane of the terminal is located in a high-frequency network.

[0193] In conjunction with embodiments of the third aspect, in some embodiments, the low-frequency cell is used for the control plane; and / or

[0194] The high-frequency cell is used for the user plane.

[0195] Fourthly, embodiments of this disclosure provide a communication system, including: a terminal, a first network device, and a second network device;

[0196] The terminal is used to execute the method of the first aspect;

[0197] The first network device is used to perform the method of the second aspect;

[0198] The second network device is used to execute the method of the third aspect.

[0199] Fifthly, embodiments of this disclosure provide a terminal, including:

[0200] The transceiver module is configured to receive first information sent by a first network device; and to receive second information sent by a second network device when a first condition is met, wherein the first network device includes a low-frequency cell and the second network device includes a high-frequency cell.

[0201] Sixthly, embodiments of this disclosure provide a network device, including:

[0202] The transceiver module is used to send first information to the terminal or send second information to the terminal when a first condition is met. When the first condition is met, a second network device is used to send the second information. The network device includes a low-frequency cell or a high-frequency cell.

[0203] In a seventh aspect, embodiments of this disclosure provide a communication device, including:

[0204] One or more processors;

[0205] The communication equipment is configured to implement the method of the first aspect, or the second aspect, or the third aspect.

[0206] Eighthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0207] 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, or the third aspect.

[0208] Ninthly, embodiments of this disclosure provide a program product, wherein,

[0209] When the program product is executed by a communication device, it causes the communication device to perform the method of the first aspect, or the second aspect, or the third aspect.

[0210] In a tenth 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.

[0211] Eleventhly, 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.

[0212] It is understood that the aforementioned terminals, network 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.

[0213] 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.

[0214] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0215] 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.

[0216] 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.

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

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

[0219] 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 B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0220] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); 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, C, etc.

[0221] 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.

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

[0223] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0224] 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”.

[0225] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0226] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0227] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "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," or "bandwidth part (BWP)."

[0228] In some embodiments, "terminal" or "terminal device" may be referred to as "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," "client," etc.

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

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

[0231] 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.

[0232] Figure 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure, and Figure 1b is a schematic diagram of a scenario of a communication system according to an embodiment of the present disclosure.

[0233] As shown in Figure 1a, the communication system 100 includes a terminal 101, a first network device 102, and a second network device 103. The communication system 100 of this embodiment is a high-low frequency hybrid networking system, wherein the first network device 102 and the second network device 103 can be connected via an Xn interface.

[0234] In some embodiments, the first network device 102 uses low-frequency spectrum resources, such as those between 30 and 300 kHz. Low-frequency signals have long transmission distances and strong penetration, but spectrum resources are limited.

[0235] In some embodiments, the second network device 103 uses high-frequency spectrum resources, such as those above 300 kHz. High-frequency signals have high path loss and short transmission distances compared to low-frequency signals, but they have abundant spectrum resources and can transmit a large amount of information.

[0236] In some embodiments, the first network device 102 includes one or more low-frequency cells, which may also be referred to as low-frequency sites or low-frequency carriers. The second network device 103 includes one or more high-frequency cells, which may also be referred to as high-frequency sites or high-frequency carriers. In this communication system, the high- and low-frequency cells are located at different sites. The connection between the first network device 102 and the second network device 103 can be an ideal backhaul connection or a non-ideal backhaul connection.

[0237] In some embodiments, the first network device 102 has a Radio Resource Control (RRC) entity and an RRC state machine. The second network device 103 may have an RRC entity but no RRC state machine. The RRC entity on the second network device 103 is only used for encapsulating RRC configuration parameters and does not have RRC signaling. For example, the second network device 103 sends configuration parameters to the first network device 102 through the Xn interface. The first network device 102 generates RRC signaling through the RRC entity and sends the generated RRC signaling to the terminal 101, thereby realizing the configuration and management of the second network device 103 site. The implementation of the first network device 102 can refer to the Master Node (MN) in the Dual Connectivity (MR-DC) technology of 5G Multi-RAT systems, and the implementation of the second network device 103 can refer to the Secondary Cell Group (SCG) in MR-DC. The RRC entity on the SCG side can be used to generate SCG RRC signaling and RRC configuration parameters. Alternatively, the implementation of the second network device 102 can refer to the LTE DC node.

[0238] In some embodiments, each low-frequency cell in the first network device 102 is a normal cell that supports information exchange during communication, such as supporting the transmission of Synchronization Signal Block (SSB), supporting the broadcast of System Information (SI), supporting paging, and supporting the Random Access Channel (RACH) process.

[0239] In some embodiments, the high-frequency cells in the second network device 103 are subject to certain limitations in information exchange. For example, the high-frequency cells or high-frequency sites in the second network device 103 may be deployed in any of the following ways:

[0240] Method 1: No public signals, including SSB, are transmitted. This may include:

[0241] Method 1.1: This method does not transmit public signals, including SSBs, and does not support broadcast system information, paging, or the initial access RACH procedure. In this method, terminal 101 can access the network via the low-frequency carrier of the first network device 102. The system can configure the high-frequency carrier of the second network device 103 to provide data transmission services using the low-frequency carrier of the first network device 102. Blind addition is possible in the configuration; the high-frequency carrier is activated by per-UE signal measurement before being used for data transmission. Furthermore, terminal 101 can obtain synchronization and perform measurements via the SSB of the low-frequency cell.

[0242] Method 1.2: No public signals, including SSBs, are transmitted; broadcast system information and paging are not supported, but the RACH procedure is supported. System broadcast information is configured on the high-frequency carrier of the second network device 103 via the low-frequency carrier of the first network device 102. Terminal 101 can initiate an initial access procedure to the high-frequency carrier of the second network device 103. Furthermore, synchronization and measurements can be obtained via the low-frequency cell SSB.

[0243] Operating mode 2: Supports sending a common signal (SSB). This may include:

[0244] Sub-mode 2.1: Only the common signal SSB is transmitted on the synchronization raster; system broadcast information, paging, and the initial access RACH procedure are not supported. The SSB can be used to synchronize and search for the high-frequency carrier of the second network device 103.

[0245] Sub-mode 2.2: Only transmits the common signal SSB on the asynchronous grid; does not support system broadcast information, paging, or the initial access RACH procedure, etc.

[0246] Sub-mode 2.3: Only transmits the common signal SSB on the synchronization grid; does not support system broadcast information or paging, but supports the initial access RACH procedure, etc. System broadcast information on the high-frequency carrier can be configured via the low-frequency carrier, and terminal 101 can initiate the initial access procedure to the high-frequency carrier.

[0247] Sub-mode 2.4: Only transmits the common signal SSB on the asynchronous grid; does not support system broadcast information or paging, but supports the initial access RACH procedure, etc. By configuring the system broadcast information of the high-frequency carrier through the low-frequency carrier, terminal 101 can initiate the initial access procedure to the high-frequency carrier.

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

[0249] In some embodiments, the first network device 102 or the second network device 103 may be an access network device that satisfies the embodiments described in this disclosure, and both may be connected to a core network device. Alternatively, the first network device 102 may include at least one of an access network device and a core network device.

[0250] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless 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 wireless fidelity (WiFi) system.

[0251] 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.

[0252] 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 protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0253] In some embodiments, a core network device can be a single device comprising one or more network elements, or it can be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC). Alternatively, a core network device refers to a network element with a specific function, such as an Access Management Function (AMF) or a Service Management Function (SMF).

[0254] 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 provided 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 provided in this disclosure are also applicable to similar technical problems.

[0255] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1a or FIG1b, or to a part thereof, but are not limited thereto.

[0256] The entities shown in Figure 1a or Figure 1b are illustrative. The communication system may include all or part of the entities in Figure 1a or Figure 1b, or other entities other than those in Figure 1a or Figure 1b. The number and form of each entity are arbitrary. The connection relationship between the entities is illustrative. The entities may not be connected or may be connected. The connection can be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

[0257] 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), 6G, 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 processing 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).

[0258] In relevant mobile communication networks, traffic distribution varies with time of day; for example, traffic is lower at night, higher during the day, and significantly lower at midnight. In addition to this main distribution characteristic, there are also a certain probability of isolated incidents, such as a single user's network usage scenario. From the user's perspective, simply shutting down a cell is not ideal for standalone deployments and can lead to coverage gaps.

[0259] In some scenarios, there are surges in capacity demand triggered by events, such as concerts and other large-scale user gatherings. In these situations, rapid network deployment and application are crucial. Traditional network-side deployment methods are clearly insufficient, while pre-built base stations would result in network "empty" operation. Unlike Wireless Fidelity (Wi-Fi) LANs, cellular network deployment requires configuring various neighbor cell relationships or optimizing parameters. It has not yet achieved a plug-and-play approach similar to Wi-Fi, where it can be turned on when needed and off when not to conserve energy. Rapidly establishing networks and minimizing the impact on existing networks, especially user mobility, is of significant research value.

[0260] For users moving in idle states, multiple layers of coverage are not necessary; basic coverage is sufficient. Multi-layered coverage, deployed in small cells, is primarily to meet the throughput requirements of connected states.

[0261] Furthermore, 5G has very little spectrum below 6GHz, making the application of spectrum above 6GHz necessary. In 6G deployment, the spectrum used for 6G is mostly high-frequency, even higher than that used for 5G. As mentioned earlier, high-frequency bands have limited coverage, high signal loss, and rapid fading, but abundant spectrum resources and the ability to transmit large amounts of information. Low-frequency signals travel further and have stronger penetration, but spectrum resources are limited. Future service volumes will continue to increase, demanding higher cell capacity. Simultaneously, with the development of mobile communication technology, the requirements for communication connection quality and service continuity will also become increasingly stringent.

[0262] In NR, the spectrum is characterized by high frequency and wide range. However, there are also cells refarmed from LTE spectrum for NR. Therefore, in NR cell deployment, high-frequency cells and low-frequency cells have equal priority in cell search or reselection. Thus, the shutdown and activation of NR cells, or their deployment, is not a plug-and-play process, and network deployment can be time-consuming before they are truly operational. NR's network energy-saving goals propose energy-saving solutions such as reducing SSB-less cells, on-demand SSB or SIB1 requests, cell DTX / DRX / switching off, and power / spatial adaptation. These energy-saving solutions are not backward compatible and cannot well adapt to service demands, especially network demands caused by unforeseen events.

[0263] Based on the above description, the available low-frequency spectrum for future 6G will be limited and become a valuable resource, while high-frequency spectrum will be relatively abundant. This disclosure embodiment considers simultaneously utilizing both low-frequency and high-frequency resources in the network to provide users with a high-performance user experience. The communication system based on a hybrid high-low frequency network provided in this disclosure embodiment is used to improve network performance while considering inherent environmental considerations. Network energy saving is achieved by shutting down cells for services or entering an energy-saving state. How to implement the hybrid high-low frequency network is detailed in the following embodiment description.

[0264] Figure 2a is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2a, this disclosure relates to a communication method, which includes:

[0265] In step S2101, the first network device 102 sends the first information to the terminal 101.

[0266] In some embodiments, the first network device 102 includes at least one low-frequency cell (e.g., between 30 and 300 kHz) for the control plane (CP). The low-frequency cell may also be referred to as a low-frequency site, low-frequency carrier, or low-frequency layer. Optionally, the first network device 102 can be used for the control plane, such as transmitting control information. For example, the first information is RRC signaling, and the first network device 102 can send RRC signaling to the terminal 101. For example, the second network device 102 can be used to generate RRC parameters and send the corresponding RRC signaling to the terminal 101 through the first network device 102.

[0267] In some embodiments, the configuration information of the first network device and the second network device are different; the configuration information includes at least one of the following:

[0268] Does it support sending public signals?

[0269] Does it support sending system broadcast messages?

[0270] Does it support paging?

[0271] Does it support the initial RACH access process?

[0272] This embodiment can be found in the description of the foregoing embodiments or the following embodiments, and will not be repeated here.

[0273] Optionally, the control plane of the terminal is located in a low-frequency network, and the user plane of the terminal is located in a high-frequency network.

[0274] Optionally, low-frequency cells are used for the control plane; and / or, high-frequency cells are used for the user plane.

[0275] In some embodiments, the first information may be system information for cell search, for example, the first network device 102 transmits the first information via system broadcast. In some embodiments, the first information includes at least one of the following:

[0276] Low-frequency list;

[0277] The list of high-frequency frequencies configured in the first network device 102;

[0278] Synchronization Signal Block (SSB);

[0279] System Information (SI).

[0280] Optionally, the low-frequency list may correspond to at least one low-frequency cell, for example, it may include low-frequency cells with inter-frequency bands. In one example, the first information includes the low-frequency list, and during cell search, terminal 101 may prioritize searching for low-frequency cells based on the low-frequency list. Alternatively, during cell reselection, terminal 101 may prioritize searching for low-frequency cells based on the low-frequency list.

[0281] Optionally, the high-frequency list may correspond to at least one high-frequency cell. In one example, the first information includes a low-frequency list and a high-frequency list. During the cell search process, the terminal 101 may prioritize searching low-frequency cells, and then search for or reselect high-frequency cells based on the high-frequency list when certain conditions are met.

[0282] Optionally, the SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The PSS and SSS can be used by terminal 101 to obtain time synchronization and cell information during cell search; the PBCH can be used to obtain system information. The SI may include system information such as SIB1. The first information may also include reference signals, etc.

[0283] In some embodiments, the low-frequency list can be broadcast by the first network device 102 through the cell system, and the terminal 101 can store it based on historical information received from the cell system broadcast. Alternatively, the first network device 102 may not send the low-frequency list, and the low-frequency list may be written into the terminal 101 during the product implementation process of the terminal.

[0284] In some embodiments, during this step, terminal 101 may be in an RRC idle state. Terminal 101 receives first information sent by the first network device 103 and can perform cell search for low-frequency cells based on the first information. For example, during the cell search process, terminal 101 receives PSS and SSS to obtain synchronization and cell information; it receives PBCH to obtain system information. Then it continuously receives SIB1 until sufficient system information is obtained to complete the cell search process.

[0285] In step S2102, the second network device 103 sends the second information to the terminal 101.

[0286] In some embodiments, the second network device 103 includes at least one high-frequency cell for the user plane (UP). The high-frequency cell may also be referred to as a high-frequency site, a high-frequency carrier, or a high-frequency layer, etc.

[0287] In some embodiments, the second information may be information sent by the second network device 103 for cell search.

[0288] In some embodiments, terminal 101 may receive second information.

[0289] In some embodiments, this step can be performed when a first condition is met, such as when the second network device 103 sends the second information when the first condition is met. For example, the second network device 103 sends the second information when the first condition is met, and / or the terminal 101 receives the second information when the first condition is met.

[0290] In some embodiments, the first condition includes at least one of the following:

[0291] There are no low-frequency cells available for residential use;

[0292] The measurement result for the high-frequency cell is greater than or equal to the threshold configured in the first network device 102.

[0293] Optionally, there may be no low-frequency cell available for camping, for example, if terminal 101 cannot find a suitable low-frequency cell during the cell search process based on step S2101. That is, cell search for high-frequency cells is initiated only if no suitable low-frequency cell can be found.

[0294] Alternatively, the first network device 102 may be configured with a quality threshold, such as a Reference Signal Received Power (RSRP) threshold. When the measurement results of a high-frequency cell meet the RSRP threshold, the terminal 101 may determine to start cell search for the high-frequency site.

[0295] In some embodiments, the first network device 102 can configure a frequency list of high-frequency sites, such as configuring a high-frequency frequency list through the aforementioned first information, and the terminal 101 can perform high-frequency cell search based on the high-frequency frequency list.

[0296] In some embodiments, the second network device 103, i.e., the high-frequency site, can operate in an on-demand SSB or SIB1 (SIB1) mode, and can send cell search, cell selection, or cell reselection information according to the request of the terminal 101.

[0297] For example, before step S2102, the following steps may be included: terminal 101 sends request information to second network device 103, the request information being used to request second information.

[0298] Optionally, the second information includes at least one of the following:

[0299] SSB;

[0300] System Information Block 1 (SIB1);

[0301] Optionally, when the second network device 103 is in on-demand SSB / SIB1 mode, high-frequency cells can be camped based on the request of terminal 101 with a very low probability. That is, the cell search or camping of the second network device 103 can be understood as a fallback working mode, camping when there are no suitable low-frequency cells.

[0302] In some embodiments, terminal 101 may be in an RRC idle state, and when no suitable low-frequency cell is found, it performs a cell search for a high-frequency cell based on the second information from the second network device 103. The cell search process can still refer to the relevant protocols or the previous example.

[0303] Step S2103: Terminal 101 selects the cell to be camped.

[0304] In some embodiments, the terminal 101 can perform cell search for low-frequency cells based on the first information, and can determine whether the searched cells are suitable for camping, and select a suitable low-frequency cell to camp on, such as selecting a low-frequency cell that meets the S criterion.

[0305] In some embodiments, when the first condition is met, such as when no suitable low-frequency cell can be found, the terminal 101 can perform a cell search for high-frequency cells based on the second information, and select a suitable high-frequency cell in an emergency.

[0306] In some embodiments, the terminal 101 performs cell search on low-frequency and high-frequency cells and can select the cell to camp on based on different principles. For example, the cell to camp on is selected based on frequency priority, where the frequency priority of low-frequency cells is higher than that of high-frequency cells in this embodiment.

[0307] In some embodiments, if terminal 101 in the RRC idle state finds a suitable cell through cell search, it can send a request to establish an RRC connection and initiate a random access (RACH) procedure to camp on the suitable cell.

[0308] 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", and "field" can be used interchangeably.

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

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

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

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

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

[0314] 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.

[0315] 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.

[0316] 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 after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0317] The method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2103.

[0318] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2a.

[0319] In this embodiment, based on the characteristics of a small number of low-frequency sites and a large number of high-frequency sites, the first network device 102 and the second network device 103 can be used together for joint deployment of high-low frequency hybrid networking. The number of the first network device 102 can be one or at least two, and the number of the second network device 103 can be one or at least two. This embodiment does not limit the number of such devices. During the cell search process, the terminal 101 can preferentially camp on low-frequency cells to effectively achieve energy saving in high-frequency cells.

[0320] Figure 2b is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2b, this embodiment of the disclosure relates to a communication method, which includes:

[0321] In step S2201, the first network device 102 sends the first information to the terminal 101.

[0322] In some embodiments, the first information may include information for cell reselection. For example, the first information may include reference signals related to measurements of the current cell. It may also include neighbor cell configuration information.

[0323] In some embodiments, the terminal 101 may be camped on a certain cell, such as a low-frequency cell.

[0324] In some embodiments, terminal 101 may receive the first information and perform measurements of the cell to monitor the signal quality of the cell.

[0325] In some embodiments, when the neighbor cell measurement conditions are met, the terminal 101 may perform neighbor cell measurement based on the neighbor cell configuration information to monitor the signal quality of the neighbor cell.

[0326] In step S2202, the second network device 103 sends the second information to the terminal 101.

[0327] In some embodiments, the second network device 103 may send second information when a first condition is met. In this embodiment, the second information may be related to a cell reselection scenario, or it may be related to measurements configured for high-frequency cell reselection by the first network device 102.

[0328] In some embodiments, the second information may include information for cell reselection, for example, the second information may include reference signals related to high-frequency cell measurements.

[0329] In some embodiments, the neighbor cell configuration information may include high-frequency cells.

[0330] In some embodiments, terminal 101 may, based on the configuration of first network device 102, receive second information sent by second network device 103 when measurement conditions are met, and perform high-frequency cell measurement.

[0331] In step S2203, terminal 101 performs cell reselection based on frequency priority.

[0332] In some embodiments, terminal 101 may perform cell reselection based on information sent by first network device 102 and / or second network device 103.

[0333] Optionally, during the cell reselection process, the terminal 101 can perform measurements on its own cell or neighboring cells based on the frequency priority of the cells, such as measuring cells with high frequency priority.

[0334] Optionally, for multiple cells that meet the reselection criteria, terminal 101 can also select the optimal cell based on frequency priority. For example, terminal 101 can perform cell reselection according to a priority strategy.

[0335] In some embodiments, step S2203 may include the following steps: terminal 101 selects a cell to stay in cell reselection based on frequency priority and / or band combination (BC) capability.

[0336] In one embodiment, during cell selection or reselection, the high-frequency cell is visible to the terminal 101 in the RRC idle state. For example, referring to the description of step S2102, "visible" means that the second network device 103 can send an SSB or send an SSB based on the request information of the terminal 101; "visible" can also mean that the second network device 103 can send an SIB1 or send an SIB1 based on the request information of the terminal 101.

[0337] In one example, the frequency priority of a low-frequency cell is higher than that of a high-frequency cell. In this example, during cell reselection, terminal 101 can preferentially camp on a low-frequency cell, thereby maximizing the network energy-saving gains of the high-frequency site / cell.

[0338] In this example, frequency priority can be configured in different ways or with different granularities. The frequency priority must satisfy at least one of the following:

[0339] Configured or defined on a per-frequency basis, with different frequency layers having different frequency priorities;

[0340] Configured or defined per band, with different frequency priorities corresponding to frequency layers in different bands;

[0341] Frequency layers are configured or defined per FR, and the frequency priorities in different FRs are different.

[0342] Optionally, when configuring the granularity as per FR, the priorities of FR1 and FR2 can be set to different values. Furthermore, each FR can be divided into frequency layers, or if a FR is not divided into frequency layers, the priorities of all frequency layers within that FR are the same. For example, if there is no further division of frequency layers within FR1, the per-frequency priorities within FR1 are the same. As another example, if FR1 is 1 (1 indicates high priority) and FR2 is 2 (2 indicates relatively low priority), then the priorities of all frequency layers within FR1 are definitely higher than the priorities of all frequency layers within FR2.

[0343] In another example, a cell with a higher frequency priority is determined based on at least one of the frequency priority, the frequency range (FR) priority, or the sub-priority of a configured or defined frequency priority.

[0344] In this example, the granularity of frequency priority configuration can still refer to the previous example.

[0345] In this example, for cells with high frequency priority, the frequency priority can be determined based on both per-band or per-FR priority and frequency layer priority. If the frequency layer priority is within FR1 or FR2, the final frequency priority needs to take into account the FR priority.

[0346] For example, frequency priority = per frequency priority + FR priority * N, where N is the total number of frequency priorities.

[0347] Alternatively, combining the number or classification of frequency priorities in related technologies, a new priority level can be configured, such as denoted as subsubpriority. The value of subsubpriority can be ENUMERATED{oDot2,oDot4,oDot6,oDot8}. A comparison of frequency priorities is jointly determined by the per-frequency priorities in related technologies, the subpriorities in related technologies, and the subsubpriority in this embodiment. If the per-frequency priorities are the same, the frequency priority is determined according to the subpriority; if the subpriorities are the same, the frequency priority is determined according to the subsubpriority.

[0348] In another embodiment, during cell selection or reselection, high-frequency cells are invisible to terminal 101 in the RRC idle state. In this embodiment, terminal 101 in the RRC idle state can see the low-frequency layer but cannot see the high-frequency layer.

[0349] In this embodiment, the method may include step S2204:

[0350] In step S2204, when the second condition is met, terminal 101 does not search for or select a high-frequency cell.

[0351] The second condition is used to indicate that the high-frequency cell or high-frequency layer is not visible to the idle terminal 101.

[0352] Optionally, the second condition includes at least one of the following:

[0353] High-frequency cells cannot be camped. When high-frequency cells cannot be camped, they do not send SSBs, and there is no system broadcast or paging or any other control plane information in the high-frequency cells.

[0354] High-frequency cells do not belong to the frequency list configured by the first network device 102; this list can refer to the configuration in the first information, for example, the high-frequency layer will not be configured in the high-frequency frequency list for cell reselection broadcast by the low-frequency cell system. In this method, high-frequency cells can send SSB, but do not send SIB1, and terminal 101 can request SIB1.

[0355] The SSB transmitted by the high-frequency cell is not on the synchronization grid.

[0356] The MIB in the SSB sent by the high-frequency cell indicates that the high-frequency cell is in a barred state.

[0357] In this embodiment, the terminal 101 may not measure the high-frequency cell during the cell reselection process in order to maintain the energy efficiency of the high-frequency cell.

[0358] In some embodiments, in conjunction with the description of the aforementioned step S2203 embodiment, the terminal 101 may also prioritize low-frequency cells based on frequency priority during the cell reselection process.

[0359] For example, in this embodiment, if a suitable low-frequency cell cannot be found based on frequency priority or R criterion, and cell reselection is initiated, for example, if no suitable cell is found for more than 10 seconds, then terminal 101 can start searching for high-frequency cells.

[0360] Optionally, terminal 101 can enable the search for high-frequency cells, which can be based on terminal capabilities or on the high-frequency list broadcast by the first network device 102 system.

[0361] Optionally, the high-frequency cell can be a cell that supports on-demand SIB1 to maximize energy savings for high-frequency network equipment.

[0362] In one example, referring to the description of step S2102, terminal 101 can request SIB1 based on request information. In this example, terminal 101 can send an uplink signal to transmit request information based on uplink (UL) resources pre-allocated on the downlink (DL) spectrum, and request SIB1 based on this uplink signal. The UL resources pre-allocated on the DL spectrum are sub-band full-duplex (SBFD) time-domain resources. In this example, the request information is sent on sub-band full-duplex (SBFD) time-domain resources.

[0363] In some embodiments, in conjunction with the description of the foregoing embodiments, the terminal 101 may perform cell reselection based on frequency priority and / or BC capability during the cell reselection process.

[0364] In this embodiment, the first information sent by the first network device 102 may not include a high-frequency frequency list. For example, the cell reselection frequency list configured in the system broadcast message for low-frequency cells may not include the frequency configuration of high-frequency cells or sites. However, the configuration information corresponding to the low-frequency frequency list in the first information may include a high-frequency layer list that overlaps with the low-frequency frequency layer, which is used to assist the terminal 101 in performing cell selection and reselection.

[0365] In one example, terminal 101 selects or reselects a cell that belongs to the BC (Band Combination) supported by terminal 101. In this example, terminal 101 determines the target cell as the reselection target cell based on its supported high-frequency capabilities and the BC capabilities between it and low-frequency bands. Only after terminal 101 enters the RRC connected state (RRC_CONNECTED) can it obtain data transmission services based on its supported high-frequency band capabilities and the BC capabilities between it and low-frequency bands. For example, low-frequency frequency 1 has a higher priority, and low-frequency frequency 2 has a lower priority than low-frequency frequency 1; terminal 101 cannot support the BC combination corresponding to low-frequency frequency 1 or the BC combination supported by the network, but can support the BC combination corresponding to low-frequency frequency 2. Therefore, terminal 101 can consider the low-frequency cell corresponding to low-frequency frequency 2 as a cell with higher frequency priority, and will select the cell or frequency layer corresponding to low-frequency frequency 2 during the cell selection or reselection process.

[0366] It is worth emphasizing that, unlike the low-frequency priority approach in the embodiments of this disclosure, in relevant 5G technologies, low-frequency cells and high-frequency cells have equal priority. Terminals can choose to camp on either a low-frequency or high-frequency cell through cell search. During cell reselection, the decision to reselect to a high-frequency or low-frequency cell can also be based on existing frequency priority and cell channel measurement quality. For terminals in the RRC_CONNECTED state, the target cell for handover can be determined by reporting the terminal's cell signal measurement quality.

[0367] The method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204.

[0368] In some embodiments, other alternative implementations may be described before or after the specification corresponding to Figure 2b.

[0369] Figure 2c is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2c, this embodiment of the disclosure relates to a communication method, which includes:

[0370] In step S2301, the first network device 102 sends the first information to the terminal 101.

[0371] In some embodiments, the first information includes information for mobility management.

[0372] Optionally, the mobility of terminal 101 in this embodiment may include control plane (CP) mobility or user plane (UP) mobility. CP mobility includes handover scenarios, RRC resume scenarios, etc.

[0373] In some embodiments, the first information may include measurement configuration information configured on the network side, such as the measurement object and measurement reporting configuration. For example, if terminal 101 is camped on a low-frequency cell, the first network device 102 may send measurement configuration information to terminal 101.

[0374] Optionally, the measurement objects include the low-frequency layer (or low-frequency cell) and the high-frequency layer (or high-frequency cell).

[0375] In some embodiments, terminal 101 receives the first information and may perform measurements based on network configuration.

[0376] Optionally, terminal 101 may obtain a first measurement report based on the measurement.

[0377] In step S2302, terminal 101 sends a first measurement report to first network device 102.

[0378] In some embodiments, the first network device 102 receives the first measurement report.

[0379] Optionally, the first measurement report can be based on the measurement reporting configuration configured in the network. For example, the measurement reporting configuration can adopt A-series events, B-series events, or periodic measurement reporting in related technologies.

[0380] In some embodiments, taking the configuration of CP mobility by the first network device 102 as an example, the first measurement report includes measurement results of the frequency layer of the control plane CP, for example, measurement results of low-frequency cells.

[0381] In some embodiments, the network side, such as the first network device 102, performs corresponding scheduling based on the first measurement report reported by the terminal 101, such as the frequency layer measurement result of the CP, such as executing step S2303.

[0382] In step S2303, the first network device 102 sends the second instruction information to the terminal 101.

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

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

[0385] Switch to low-frequency cell;

[0386] Add a new high-frequency cell (or add a high-frequency cell);

[0387] Maintain existing high-frequency cells;

[0388] Release existing high-frequency cells.

[0389] Optionally, the first network device 102 can trigger the terminal 101 to switch to other low-frequency cells based on the frequency layer measurement results of the CP reported by the terminal 101 through the second indication information.

[0390] Optionally, during the handover process, the first network device 102 can also manage high-frequency cells. For example, during the handover process, it can directly configure a new high-frequency cell, maintain the previous high-frequency cell, or release the previous high-frequency cell through the second instruction information.

[0391] Optionally, when adding a new high-frequency cell, the method may further include step S2304:

[0392] In step S2304, the first network device 102 sends the measurement results of the high-frequency cell to the second network device 103.

[0393] In some embodiments, the first network device 102 can configure the measurement objects of high-frequency cells and receive the measurement results reported by the terminal 101. After receiving the high-frequency measurement results reported by the terminal 101, the first network device 102 can send the measurement results corresponding to the high-frequency cells to the second network device 103 when adding new high-frequency cells.

[0394] In some embodiments, the second network device 103 can receive the measurement results of the aforementioned high-frequency cell and can select beam information, such as the beam index of the Physical Downlink Control Channel (PDCCH) and / or the beam index set of the Physical Downlink Shared Channel (PDSCH). Optionally, the second network device 103 can send beam indication information to the terminal 101, or send beam indication information to the terminal 101 through the first network device 102.

[0395] In step S2305, the first network device 102 sends beam indication information to the terminal 101.

[0396] In some embodiments, beam indication information includes the PDCCH Transmission Configuration Indicator state (TCI state) for initial activation, and / or PDSCH TCI states, etc.

[0397] In some embodiments, the first network device 102 may receive beam indication information sent by the second network device 103 and may send the beam indication information to the terminal 101.

[0398] In some embodiments, terminal 101 receives beam indication information.

[0399] In some embodiments, beam indication information may be sent to terminal 101 by a first network device 102 or a second network device 103.

[0400] In some embodiments, when adding a high-frequency cell, the first network device 102 sends the PDCCH TCI state, PDSCH TCI states, etc. to the terminal 101 for initial activation.

[0401] The method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2305.

[0402] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG2c.

[0403] Figure 2d is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2d, this embodiment of the disclosure relates to a communication method, which includes:

[0404] In step S2401, terminal 101 sends an RRC recovery request to the second network device 103.

[0405] In some embodiments, terminal 101 in the RRC inactive state (RRC_INACTIVE) may perform this step.

[0406] In some embodiments, if a low-frequency coverage vulnerability exists, and terminal 101 is camped on a high-frequency site or high-frequency cell, terminal 101 may be triggered to initiate an RRC Resume process.

[0407] In some embodiments, terminal 101 may use RRC Resume Request information to indicate the addressing of first network device 102 or low-frequency cell.

[0408] In some embodiments, the second network device 103 receives the request and can perform an RRC Resume through the first network device 102.

[0409] In some embodiments, the terminal context is always stored in the first network device 102.

[0410] In some embodiments, the first network device 102 requests the second network device 103 to establish a control plane connection.

[0411] In some embodiments, the first network device 102 may establish a control plane connection to a high-frequency cell at a serving site, such as the high-frequency cell at the serving site being the high-frequency cell where the terminal 101 is camped.

[0412] In some embodiments, the first network device 102 may forward RRC signaling to the second network device 103.

[0413] In some embodiments, the second network device 103 can send RRC configuration parameters to the first network device 102, and the first network device 102 can generate RRC signaling.

[0414] In step S2402, the second network device 103 sends the control signaling corresponding to the RRC recovery request to the first network device 102.

[0415] In some embodiments, the control signaling may refer to RRC recovery request information, or parameters related to RRC recovery obtained based on the request information.

[0416] In some embodiments, the first network device 102 receives the control signaling.

[0417] In some embodiments, the first network device 102 may determine the corresponding Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) based on the RRC message of the control signaling.

[0418] In step S2403, the first network device 102 sends a PDCP PDU to the second network device 103.

[0419] In some embodiments, the second network device 103 may receive the PDU.

[0420] In step S2404, the second network device 103 sends a PDCP PDU to the terminal 101.

[0421] In some embodiments, the first information includes PDCP PDU, meaning that the second network device 103 sends the first information to the terminal 101 in this step. In some embodiments, for the RRC Resume scenario, when the network side, such as the first network device 102, releases the terminal 101 to RRC_INACTIVE, it configures the Radio Access Network (RAN) to the area range corresponding to the low-frequency site. When the terminal 101 initiates the RRC Resume procedure, it also addresses the low-frequency cell to obtain the UE Access Stratum (AS) context.

[0422] Optionally, the context of terminal 101 is stored in the first network device 102.

[0423] In some embodiments, after terminal 101 initiates RRC Resume, the network side can keep the UE in the RRC_CONNECTED state or allow the UE to enter the RRC_IDLE state.

[0424] In some embodiments, if terminal 101 has no service at this time, the first network device 102, i.e., the low-frequency site, is still responsible for releasing terminal 101 to the RRC_INACTIVE state and configuring the RRC_INACTIVE configuration information. That is, the AS context of terminal 101 is always stored on the low-frequency site.

[0425] In some embodiments, if there is a possibility that terminal 101 may switch to a high-frequency site in the future, for example, if there is no low-frequency site coverage, terminal 101 is not allowed to enter the RRC_INACTIVE state.

[0426] The method involved in the embodiments of this disclosure may include at least one of steps S2401 to S2404.

[0427] In some embodiments, other alternative implementations may be described before or after the specification corresponding to Figure 2d.

[0428] Figure 2e is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2e, this embodiment of the disclosure relates to a communication method, which includes:

[0429] Step S2501: The first network device 102 sends the first information to the terminal 101.

[0430] In some embodiments, terminal 101 receives the first information.

[0431] In some embodiments, the first information may be the first information from other embodiments. Alternatively, in this embodiment, the first information may include paging information.

[0432] In some embodiments, the first network device 102 can initiate paging within the coverage area of ​​a low-frequency cell. It is worth noting that in related technologies, paging messages are sent from a pre-registered list (TAlist) configured on the network side when the terminal registers.

[0433] In some embodiments, to ensure that terminal 101 can receive paging information, i.e., paging messages are reachable for terminal 101, in scenarios where low-frequency coverage has vulnerabilities and terminal 101 may be camped on a high-frequency cell, the following can be satisfied: the first network device 102 and the second network device 103 located in the same geographical area have the same Tracking Area Code (TAC), i.e., the first condition is not satisfied at this time. The first condition is that the first network device 102 and the second network device 103 located in the same geographical area have different TACs.

[0434] In some embodiments, if the first condition is met, i.e., the first network device 102 and the second network device 103 located in the same geographical area have different TACs, in a scenario where there are gaps in low-frequency coverage and the terminal 101 may be camped in a high-frequency cell, in order to ensure that the paging message is reachable for the terminal 101, the method may include step S2501 and / or the following step S2502:

[0435] In step S2502, the second network device 102 sends the second information to the terminal 101.

[0436] In some embodiments, terminal 101 receives the second information.

[0437] In some embodiments, the second information may be the same as that in other embodiments. Alternatively, in this embodiment, the second information may include paging information.

[0438] In some embodiments, when a dual-layer TAC deployment is configured in the same geographical area, i.e., the first network device 102 and the second network device 103 located in the same geographical area have different TACs, the execution of step S2201 or step S2202 can be determined based on the TAC, i.e., based on whether the TAC corresponds to a high-frequency cell or a low-frequency cell, when paging is triggered on the network side, the corresponding first network device 102 and / or second network device 103 initiates paging.

[0439] In this embodiment, during network deployment, high-frequency cells and low-frequency cells are also two independent network layers.

[0440] Optionally, the TAC includes an indicator bit, which is used to indicate that the network device corresponding to the TAC is a first network device 102 or to indicate that the network device corresponding to the TAC is a second network device 103. This indicator bit can occupy 1 bit.

[0441] For example, in NR, the TAC is 24 bits (TrackingAreaCode::=BIT STRING(SIZE(24))). In this embodiment or in future 6G, the TAC can be 25 bits, where the newly added high-order bits or low-order bits can be used as indicator bits to indicate whether the TAC is a TAC of a high-frequency cell or a TAC of a low-frequency cell. If the TAC is a TAC of a high-frequency cell, step S2202 can be executed, or steps S2201 and S2202 can be executed; if the TAC is a TAC of a low-frequency cell, step S2201 can be executed.

[0442] In step S2503, terminal 101 performs a re-registration process.

[0443] In some embodiments, the default terminal 101 preferentially camps on a low-frequency cell, while camping on a high-frequency cell is a temporary network camping mode.

[0444] In one example, step S2503 is executed when selecting or reselecting a high-frequency cell. In this example, when terminal 101 performs cell selection or reselection on a low-frequency cell, if it reselects or selects a high-frequency cell, terminal 101 is triggered to perform a re-registration process. Terminal 101 may also execute step S2504.

[0445] In another example, step S2503 is executed when selecting or reselecting a low-frequency cell. If terminal 101 reselects from a high-frequency cell or selects a low-frequency cell, terminal 101 can also re-initiate the registration process.

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

[0447] In some embodiments, the first indication information is used to indicate that the terminal 101 is camped on a high-frequency cell. The terminal 101 may perform a re-registration process when selecting or reselecting to a high-frequency cell, and may indicate to the network side through the first indication information that the terminal 101 is currently camped on a high-frequency cell.

[0448] The method involved in the embodiments of this disclosure may include at least one of steps S2501 to S2504.

[0449] In some embodiments, at least one of steps S2502 to S2504 is optional and can be replaced by one or more steps in different embodiments.

[0450] In some embodiments, the method may also be combined with any of the embodiments shown in Figures 2a to 2d.

[0451] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2e.

[0452] In this embodiment of the disclosure, in the joint deployment of high- and low-frequency hybrid networking, the same TAC can be configured for low-frequency sites and high-frequency sites in the same geographical area, or a two-layer TAC can be deployed for low-frequency sites and high-frequency sites in the same geographical area, thereby performing a reasonable paging process based on TAC, effectively achieving energy saving in high-frequency cells while improving user experience.

[0453] Figure 2f is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 2f, this embodiment of the disclosure relates to a method for communication, the method including:

[0454] Step S2601: The first network device 102 sends the first information to the terminal 101.

[0455] In some embodiments, the first information can be used by terminal 101 to measure, and the measurement result is used by the first network device to update the Automatic Neighbor Relation (ANR).

[0456] In some embodiments, the first information may also refer to the description in Figures 2a to 2e.

[0457] In some embodiments, terminal 101 may receive the first information and perform measurements to obtain a second measurement report.

[0458] In step S2602, the second network device 103 sends the second information to the terminal 101.

[0459] In some embodiments, the second network device 103 may perform this step when a first condition is met, which may be based on the configuration or requirements of the first network device 102 requiring the transmission of second information.

[0460] In some embodiments, the second information can be used by terminal 101 to measure, and the measurement result is used by the first network device to update ANR.

[0461] In some embodiments, the second information may also refer to the description in Figures 2a to 2e.

[0462] In some embodiments, terminal 101 may receive the second information and perform measurements to obtain a second measurement report.

[0463] In step S2603, terminal 101 sends a second measurement report to first network device 102.

[0464] In some embodiments, the first network device 102 receives the second measurement report.

[0465] In some embodiments, the second measurement report is used to indicate the type of cell being measured and is also used by the first network device to update the Automatic Neighbor Relation (ANR).

[0466] In some embodiments, in conjunction with the description of the foregoing embodiments, the first network device 102 is used for the control plane and the second network device 103 is used for the user plane. In this embodiment, the control plane and user plane can be separated in a high-low frequency hybrid network. The control plane of a terminal 101 is located on the low-frequency network and the user plane is located on the high-frequency network.

[0467] In some embodiments, the first network device 102 can perform control based on a second measurement report. For example, when the terminal 101 moves within a small area, the first network device 102 can perform operations such as adding or deleting serving high-frequency cells. High-frequency networks can achieve "plug and play," dynamically shutting down cells without affecting coverage, thus achieving network energy saving.

[0468] In some embodiments, the first network device 102 can be responsible for control plane connectivity, enabling control plane handover between low-frequency cells. Between the first network device 102 and the second network device 103, the first network device 102 can be responsible for adding and deleting high-frequency cells.

[0469] In some embodiments, the neighbor cell relationships on the network side may include the following first layer, or the following two layers:

[0470] First layer: Neighbor relationships between low-frequency cells or low-frequency sites.

[0471] The second layer: the neighboring cell relationships between low-frequency cells and high-frequency cells;

[0472] In this network deployment scenario, a low-frequency cell can have two types of neighboring cells: cells with continuous CP (Content Delivery System) and cells that handle load balancing. A high-frequency cell can have one type of neighboring cell, the master neighboring cell, which manages the high-frequency cell. The high-frequency cell can be freely shut down without affecting the mobility of RRC_CONNECTED, RRC_IDLE, or INACTIVE terminals 101.

[0473] In some embodiments, high-frequency cells may include two types: one is a cell that supports plug-and-play; the other is a cell that does not support plug-and-play. For cells that do not support plug-and-play, the same applies as regular cells, i.e., the terminal can reselect or switch to cell 101.

[0474] In some embodiments, the second measurement report, i.e., the ANR measurement report, may indicate the cell type, which includes at least one of the following:

[0475] Coverage rate of the community;

[0476] Capacity-type residential communities;

[0477] Control plane area;

[0478] User-facing community;

[0479] Whether it is a high-frequency cell that supports being dynamically turned on or off;

[0480] Among them, low-frequency cells are coverage cells or control plane cells, while high-frequency cells are capacity cells or user plane cells.

[0481] For example, the second measurement report can indicate whether a cell is a coverage cell or a capacity cell, a control plane cell or a user plane cell, or whether it supports plug-and-play type cells. For example, cell types can be: user plane cell (CP only), control plane cell (UP only), or control plane cell and user plane cell (CP and UP).

[0482] In some embodiments, the second measurement report may carry an indication via SSB or via content-reduced SIB1 (assuming the high-frequency cell can transmit a portion of content-reduced SIB1).

[0483] In some embodiments, due to the separate processing of CP and UP, or the hierarchical processing of CP cells and UP cells, the coding of a cell or site can also be based on a hierarchical mechanism. For example, the identifier ID of a high-frequency cell and the identifier ID of a low-frequency cell belong to different ID spaces, and the ID sizes can also be different.

[0484] In one example, the identifier length used for the first network device 102 is shorter than the identifier length used for the second network device 103. For example, with more high-frequency cells, the ID length of high-frequency cells can be longer. With fewer low-frequency cells, more users can be maintained, and the IDs of low-frequency cells can be shorter.

[0485] For example, the ID of the first network device 102 can occupy 24 bits, of which 20 bits are the terminal identifier or UE identifier, and 4 bits are the low-frequency cell truncation ID. These 4 bits can uniquely identify a low-frequency cell or site within a certain range (e.g., RNA). For low-frequency cells, a short 24-bit inactive Radio Network Temporary Identifier (I-RNTI) can be allocated; for high-frequency cells, a long 40-bit I-RNTI can be allocated.

[0486] Optionally, the ID of a low-frequency cell or site can be bound to a band or FR, thus making the low-frequency cell unique under a band or FR.

[0487] In this example, the first information in step S2601 may further include: third indication information, which indicates the identifier length of the first network device 102 or the identifier length of the second network device. For example, the first network device 102 may broadcast an indication of whether the corresponding base station ID is a long size or a short size. Alternatively, the third indication information may be sent through the second information.

[0488] In some embodiments, the identification-related implementation can also be applied to any of the embodiments shown in Figures 2a to 2e. The following are several examples describing the application scenarios of cell ID:

[0489] In the first example, during the RRC resume procedure, the I-RNTI carried in the RRC Resume Request message reported by terminal 101 is a short-size format, such as 24 bits or 32 bits, used to indicate that the target base station is a low-frequency site or corresponding low-frequency cell. Alternatively, the RRC Resume Request message can carry an explicit indication indicating that a low-frequency site is being addressed. If terminal 101 is camped on a high-frequency site and initiates an RRC Resume, the low-frequency site can still restore the connection of terminal 101. In accordance with the description of the foregoing embodiments, the context of terminal 101 is always preserved on the low-frequency site.

[0490] In this example, a low-frequency station can request a high-frequency station serving as a service station to establish a control plane connection. The high-frequency station forwards RRC signaling to the low-frequency station for transmission and reception. Upon receiving control signaling, the high-frequency station forwards it to the low-frequency station. For example, this could involve the Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) used for forwarding RRC signaling between the low-frequency and high-frequency stations. If terminal 101 has no service at this time, the low-frequency station can release terminal 101 to the RRC_INACTIVE state and configure the RRC_INACTIVE configuration information. The context of terminal 101 is always stored on the low-frequency station.

[0491] If there is a possibility that terminal 101 will switch to a high-frequency site, for example, when there is no low-frequency site coverage, terminal 101 is not allowed to enter the RRC_INACTIVE state.

[0492] In the second example, during the handover process, the measurement results reported by terminal 101 include the Physical Cell Identification (PCI) and frequency of the target cell. The sites interact with each other's site configurations. Based on the interacted site configurations, PCI, and frequency, the source cell can determine whether the target base station is a low-frequency or high-frequency site, or whether the target cell uses a short-size or long-size site ID; alternatively, the site configuration may carry an explicit indication of whether the target cell is a low-frequency or high-frequency site. Then, the source cell addresses the target site and initiates the handover process.

[0493] In this example, if there is no low-frequency site coverage but a high-frequency site does, the low-frequency site requests a control plane connection from a high-frequency site serving the site. The low-frequency site forwards RRC signaling to the high-frequency site for transmission and reception. Upon receiving the control signaling, the high-frequency site forwards it to the low-frequency site. For example, the low-frequency and high-frequency sites forward PDCP PDUs of RRC signaling. If terminal 101 has no service at this time, the low-frequency site is still responsible for releasing terminal 101 to the RRC_INACTIVE state and configuring the RRC_INACTIVE configuration information; the AS context of terminal 101 is always stored on the low-frequency site.

[0494] In the third example, for adding a high-frequency site addressing, the measurement results reported by terminal 101 include the target cell's PCI and frequency. The sites interact with each other's site configurations. Based on the interacted site configurations, PCI, and frequency, the current site knows whether the target base station is a low-frequency site or a high-frequency site; or whether the target cell uses a short-size site ID or a long-size site ID; or the site configuration carries a display indication indicating whether it is a low-frequency site or a high-frequency site; then it addresses the target site and initiates the high-frequency site addition process.

[0495] In the fourth example, for addressing between high-frequency sites, when high-frequency sites need to establish a connection to transfer data, the high-frequency site can address the target site and establish a connection based on the length of the site ID.

[0496] The method involved in the embodiments of this disclosure may include at least one of steps S2601 to S2603.

[0497] In some embodiments, at least one of steps S2601 and S2603 is optional and can be replaced by one or more steps in different embodiments.

[0498] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG2f.

[0499] In this embodiment of the disclosure, in a high-low frequency hybrid network, to meet the needs of user mobility and throughput, low-frequency cells (coverage-related) and high-frequency cells (capacity-related) can be jointly deployed. Furthermore, the control plane and user plane are separated. Based on a dynamic and random distribution of traffic, high-frequency cells in this embodiment are primarily responsible for capacity enhancement and can dynamically activate capacity-type cells. Simultaneously, when traffic is low, certain high-frequency cells can be dynamically shut down or put into hibernation to achieve network energy saving, enabling rapid network construction and use, and allowing for convenient shutdown of network energy-saving measures—achieving plug-and-play and on-demand network functionality. In this embodiment, terminal context can be effectively managed within the network, supporting efficient mobility and improving user performance and experience.

[0500] Figure 3a is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3a, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method comprising:

[0501] Step S3101: Receive the first information.

[0502] In some embodiments, the implementation of step S3101 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0503] Step S3102: Receive the second information when the conditions are met.

[0504] In some embodiments, the implementation of step S3102 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0505] Step S3103: Select the community to stay in.

[0506] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2103 in FIG2a, and will not be repeated here.

[0507] Step S3104: Cell reselection based on frequency priority.

[0508] In some embodiments, the implementation of step S3104 can refer to the implementation of step S2203 in FIG2b, and will not be repeated here.

[0509] The method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3104.

[0510] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3a.

[0511] Figure 3b is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3b, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0512] Step S3201: Receive the first information.

[0513] In some embodiments, the implementation of step S3201 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0514] Step S3202: Receive the second information when the first condition is met.

[0515] In some embodiments, the implementation of step S3202 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0516] Step S3203: Send the first measurement report.

[0517] In some embodiments, the implementation of step S3203 can refer to the implementation of step S2302 in FIG2c, and will not be repeated here.

[0518] Step S3204: Receive the second instruction information.

[0519] In some embodiments, the implementation of step S3204 can refer to the implementation of step S2303 in FIG2c, and will not be repeated here.

[0520] Step S3205: Receive beam indication information.

[0521] In some embodiments, the implementation of step S3204 can refer to the implementation of step S2305 in FIG2c, and will not be repeated here.

[0522] The method involved in the embodiments of this disclosure may include at least one of steps S3201 to S3205.

[0523] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3b.

[0524] Figure 3c is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3c, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0525] Step S3301: Receive first information and / or second information.

[0526] In some embodiments, the implementation of step S3301 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0527] Step S3302: Perform the re-registration process.

[0528] In some embodiments, the implementation of step S3302 can refer to the implementation of step S2503 in FIG2e, and will not be repeated here.

[0529] Step S3303: Send the first instruction information.

[0530] In some embodiments, the implementation of step S3303 can refer to the implementation of step S2504 in FIG2e, and will not be repeated here.

[0531] The method involved in the embodiments of this disclosure may include at least one of steps S3301 to S3303.

[0532] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG3c.

[0533] Figure 3d is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3d, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0534] Step S3401: Receive the first information.

[0535] In some embodiments, the implementation of step S3401 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0536] Step S3402: Send the second measurement report.

[0537] In some embodiments, the implementation of step S3402 can refer to the implementation of step S2603 in FIG2f, and will not be repeated here.

[0538] The method involved in the embodiments of this disclosure may include at least one of steps S3401 to S3402.

[0539] In some embodiments, other alternative implementations may be described before or after the specification corresponding to Figure 3d.

[0540] Figure 3e is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 3e, this embodiment of the disclosure relates to a communication method executed by a terminal 101, the method including:

[0541] Step S3501: Receive the first information.

[0542] In some embodiments, the implementation of step S3501 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0543] Step S3502: Receive the second information when the conditions are met.

[0544] In some embodiments, the implementation of step S3502 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0545] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3e.

[0546] Figure 4a is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4a, this embodiment of the disclosure relates to a communication method executed by a first network device 102, the method comprising:

[0547] Step S4101: Send the first message.

[0548] In some embodiments, the implementation of step S4101 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0549] Step S4102: Receive the first measurement report.

[0550] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2302 in FIG2c, and will not be repeated here.

[0551] Step S4103: Send the second instruction information.

[0552] In some embodiments, the implementation of step S4103 can refer to the implementation of step S2303 in FIG2c, and will not be repeated here.

[0553] The methods involved in the embodiments of this disclosure may include at least one of steps S4101 to S4103, and can be referred to the implementation method on the terminal side.

[0554] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4a.

[0555] Figure 4b is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 4b, this embodiment of the disclosure relates to a communication method executed by a first network device 102, the method comprising:

[0556] Step S4201: Send the first message.

[0557] In some embodiments, the implementation of step S4201 can refer to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0558] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4b.

[0559] Figure 5 is a flowchart illustrating a communication method according to an embodiment of this disclosure. As shown in Figure 5, this embodiment of the disclosure relates to a communication method executed by a second network device 103, the method including:

[0560] Step S5101: Send the second message.

[0561] In some embodiments, the implementation of step S5101 can be referred to the relevant implementations in Figures 2a to 2f, which will not be repeated here.

[0562] In some embodiments, other optional implementations described before or after the specification corresponding to Figure 5 may be referred to.

[0563] This disclosure proposes a method for simultaneously utilizing low-frequency and high-frequency resources to provide a high-performance user experience for the user system, which is applicable to the native green requirements of future 6G networks. It may include the process of a terminal performing cell search and cell reselection in a high-low frequency hybrid network, camping on low-frequency cells as much as possible to maximize the network energy-saving gains of high-frequency cells. Simultaneously, for terminals in RRC connection state in future 6G networks, this method simultaneously utilizes low-frequency and high-frequency resources to provide a high-performance user experience, such as methods for handling control plane mobility in high-low frequency hybrid networks, and node addressing during mobility. To facilitate understanding of this disclosure, some embodiments are listed below:

[0564] Example 1: System

[0565] Referring to the high- and low-frequency hybrid networking system shown in Figure 1b, high- and low-frequency cells are located at different sites, and they can be ideally backhauled or non-ideally backhauled.

[0566] In 5G MR-DC, the SCG side has an RRC entity, but no RRC state machine. The RRC entity can be used to generate SCG RRC signaling and RRC configuration parameters. The MN side has both an RRC entity and an RRC state machine.

[0567] In the high-low frequency hybrid network of this embodiment, the high-frequency site side can have an RRC entity, similar to SCG, but this RRC entity is only used for RRC configuration parameter encapsulation and does not have RRC signaling. Alternatively, it can be similar to LTE DC, without an RRC entity. The high-frequency site sends the configuration parameters to the low-frequency site through the Xn interface, and the low-frequency site generates RRC signaling through the RRC entity and sends it to the UE to achieve configuration and management below the high-frequency site.

[0568] The relationship between high-frequency and low-frequency cells and how they cooperate to provide high-performance services to the UE. First, a low-frequency site is a normal cell, supporting SSB, system broadcast information, paging, and the initial access RACH procedure, etc. The deployment for high-frequency sites / cells can be as follows:

[0569] Method 1.1: No public signals, including SSBs, are transmitted. System broadcast information, paging, and the initial access RACH procedure are not supported. The UE accesses the network via a low-frequency carrier and configures a high-frequency carrier for data transmission services. Blind addition is possible in the configuration, which activates the per-UE signal measurement of the high-frequency carrier before data transmission. Furthermore, synchronization and measurements can be obtained through the low-frequency cell SSB.

[0570] Method 1.2: No common signals, including SSB, are transmitted. System broadcast information and paging are not supported, but the Initial Access RACH procedure is supported. By configuring the system broadcast information of the high-frequency carrier through the low-frequency carrier, the UE can initiate the initial access procedure to the high-frequency carrier. Furthermore, synchronization and measurements can be obtained through the low-frequency cell SSB.

[0571] Mode 2.1: Only the Common Signal (SSB) is transmitted, and it is transmitted on the synchronization grid. System broadcast messages, paging, and initial access RACH procedures are not supported. The SSB can be used for synchronization and searching for high-frequency carriers.

[0572] Option 2.2: Only the Common Signal (SSB) is transmitted, and it is transmitted on an asynchronous grid. System broadcast messages, paging, and initial access RACH procedures are not supported.

[0573] Method 2.3: Only the Common Signal (SSB) is transmitted, and it is transmitted on the synchronization grid. System broadcast information and paging are not supported, but the Initial Access RACH procedure is supported. By configuring the system broadcast information of the high-frequency carrier through the low-frequency carrier, the UE can initiate the initial access procedure to the high-frequency carrier.

[0574] Option 2.4: Only the Common Signals Subsequent Broadcast (SSB) is transmitted, and it is transmitted on an asynchronous grid. System broadcast information and paging are not supported, but the Initial Access RACH procedure is supported. By configuring the system broadcast information of the high-frequency carrier using the low-frequency carrier, the UE can initiate the initial access procedure to the high-frequency carrier.

[0575] Example 2: Cell Search

[0576] This embodiment illustrates cell search in a high- and low-frequency hybrid network.

[0577] When a terminal searches for a cell, it prioritizes searching for low-frequency cells. The inter-frequency cells broadcast in the system broadcast for cell reselection are also low-frequency cells (used at the CP frequency layer). High-frequency cell searching is only initiated if no suitable low-frequency cell can be found. Alternatively, cell searching at high-frequency sites can be determined based on configuration thresholds on the low-frequency site, such as the RSRP threshold. A frequency list for high-frequency sites can also be configured on the low-frequency site. For example, if a high-frequency site cell normally operates in on-demand SIB1 mode and requires a very small UE request for camping, it could be a fallback operating mode.

[0578] The low-frequency list for cell search mentioned above can be written to the terminal by the UE during implementation, or stored as historical information received through cell system broadcast.

[0579] Example 3: Cell Selection and Reselection

[0580] This embodiment includes setting and determining the frequency priority of high- and low-frequency hybrid networking, a method for confirming the target cell for cell reselection, and a method for limiting the activation of high-frequency search.

[0581] During the cell selection / reselection process, there are several ways to handle high-frequency cells.

[0582] Method 1:

[0583] For idle UEs, high-frequency sites are visible. "Visible" means that the high-frequency cell sends an SSB, or can send an SSB or SIB1 upon request.

[0584] For example, during network deployment, low-frequency sites have high frequency priority, while high-frequency layers have low priority. This ensures that UEs camp on low-frequency sites / cells as much as possible, maximizing the network energy-saving gains of high-frequency sites / cells.

[0585] Optionally, the current granularity of frequency layer priority configuration is per frequency. In the future, the granularity of 6G frequency layer priority configuration can be per band or per FR, meaning that the priority of FR1 and the priority of FR2 can be set to different values. If there is no further division of frequency layers within FR1, the per frequency priority within FR1 is the same. If FR1 is 1 (high priority) and FR2 is 2 (relatively low priority), then the priority of the frequency layers within FR1 is definitely higher than the priorities of each frequency layer within FR2. Alternatively, the determination of frequency layer priority is based on the priority of fer band or per FR, and is jointly determined by the frequency layer priority. That is, the frequency layer priority is within FR1 or FR2, and the final frequency layer priority needs to take into account the priority of FR. For example, frequency layer priority = per frequency priority + FR priority * N, where N is the total number of frequency layer priorities. Alternatively, a subsubpriority can be configured on top of the existing frequency priority. For example, the value could be ENUMERATED{oDot2,oDot4,oDot6,oDot8}. The priority of a frequency layer is determined by the frequency priority, subpriority, and subsubpriority together. If the frequency priorities are the same, the subpriority is considered; if the subpriorities are the same, the subsubpriority is considered.

[0586] Option 2:

[0587] The UE can only see the low-frequency layer, while the high-frequency layer is invisible to idle users. "Invisibility" can manifest as follows: (1) High-frequency cells cannot camp, do not send SSBs, and do not have any control plane information such as system broadcasts and paging. (2) The high-frequency layer is not configured in the frequency list for cell reselection broadcast by the low-frequency cell system. High-frequency cells send SSBs but do not send SIB1, but the UE can request SIB1. (3) The SSBs sent by high-frequency cells are not on the synchronization grid. (4) High-frequency cells send SSBs, but the MIB indicates that the cell is barred.

[0588] If, based on frequency priority, the R criterion fails to find a suitable cell to initiate cell reselection (e.g., no suitable cell is found for more than 10 seconds), the terminal can initiate a search for high-frequency sites. This can be done based on UE capabilities or on a list of high-frequency sites broadcast by the system. In this case, the high-frequency site cell can be one that supports on-demand SIB1, aiming to maximize network energy efficiency. Since there is no prior information, an uplink signal can be sent on pre-allocated UL resources (SBFD resources) on the DL spectrum to request SIB1.

[0589] The final cell reselection frequency list configured in the system broadcast message for low-frequency sites does not include the frequency configuration of high-frequency sites. However, the configuration information of the low-frequency layer also includes a list of high-frequency layers that overlap with the low-frequency layer, used to assist the UE in performing cell selection and reselection. For example, the UE determines the target cell as the reselection target cell based on the supported high-frequency capabilities and the band combination capabilities with the low-frequency layer. Thus, after the UE enters the RRC_CONNECTED state, it can obtain data transmission services based on the supported high-frequency band capabilities and the band combination capabilities with the low-frequency layer. For example, even if the current low-frequency frequency has a high priority, if the network-supported band combination or any low-frequency and high-frequency band combination is not supported by the UE, the UE will not consider that frequency to have a high priority and will select the next lowest priority frequency layer if the band combination supported by that next lowest priority frequency layer is supported by the UE.

[0590] Example 4: paging

[0591] The current paging message is sent from the TA list configured on the network side during UE registration. In the high-low frequency hybrid network of this embodiment, the network side needs to initiate paging within the range of low-frequency sites. To ensure the paging message is reachable from the terminal, then (only when the UE might be camped on a high-frequency site, such as in scenarios with low-frequency coverage vulnerabilities):

[0592] Option 1:

[0593] Low-frequency and high-frequency sites can be configured with the same TAC within the same geographical area. When a UE performs cell reselection on a low-frequency site, if it reselects or selects a cell on a high-frequency site, the UE is triggered to perform a re-registration process, and the network side is instructed to keep the terminal camped on the high-frequency site. It can be understood that camping on a low-frequency site is the default, while camping on a high-frequency site is a temporary network camping method. If the UE reselects a cell from a high-frequency site or selects a cell on a low-frequency site, it also needs to re-initiate the registration process.

[0594] Option 2:

[0595] High-frequency and low-frequency sites are configured with different TACs in the same geographical area. That is, a two-layer TAC deployment is configured in the same geographical area. For example, the TAC is currently 24 bits in NR (TrackingAreaCode::=BIT STRING(SIZE(24))), and in the future 6G, the TAC can be 25 bits, where the high-order bits indicate whether the TAC is a high-frequency site TAC or a low-frequency site TAC. That is, when deploying the network, there are two independent network layers between high-frequency and low-frequency sites. Based on whether the TAC indicates a high-frequency or low-frequency site, when paging is triggered on the network side, paging is initiated at the base station of the high-frequency site and / or the low-frequency site.

[0596] Example 5: Hierarchical Management of High and Low Frequency Site IDs

[0597] This embodiment includes a hierarchical management method for high and low frequency sites in a high-low frequency hybrid network.

[0598] Because of the separate processing of CP (Content Provider) and UP (Upload Provider) sites, site encoding can also be hierarchical. That is, high-frequency site IDs and low-frequency site IDs belong to different ID spaces and can have different sizes. For example, if there are more high-frequency sites, their IDs can be longer. If there are fewer low-frequency sites and more users are being served, their site IDs can be shorter. Furthermore, the cell can broadcast instructions indicating whether the base station ID is long or short.

[0599] For example, 24 bits represent the 20-bit UE identifier, and 4 bits represent the low-frequency site truncated ID. Within a certain range (e.g., RNA), this ID can uniquely identify a low-frequency site. If it's a low-frequency site, a short 24-bit I-RNTI is assigned; if it's a high-frequency site, a long 40-bit I-RNTI is assigned. Furthermore, the low-frequency site ID can also be bound to a band or FR (Frequency Reference Registry), ensuring uniqueness for low-frequency sites within a single band or FR.

[0600] Examples of scenarios using site IDs are as follows:

[0601] Example 1: During the RRC resume process, the I-RNTI carried in the RRC Resume Request message reported by the UE is a short size, such as 24 bits or 32 bits, indicating that the target base station is a low-frequency site. Alternatively, the RRC Resume Request message may carry an explicit indication indicating that a low-frequency site is being addressed. This also solves the MSG3size problem. If the UE is currently camped on a high-frequency site, when initiating an RRC Resume, the low-frequency site can still restore the UE's connection, but the UE's context remains on the low-frequency site. At this time, the low-frequency site requests a control plane connection from a high-frequency site serving the UE, and the low-frequency site forwards RRC signaling to the high-frequency site for transmission and reception. The high-frequency site, upon receiving the control signaling, forwards it to the low-frequency site. For example, this involves forwarding PDCP PDUs of RRC signaling between the low-frequency and high-frequency sites. If the UE has no service at this time, the low-frequency site is still responsible for releasing the UE to the RRC_INACTIVE state and configuring the RRC_INACTIVE configuration information. In other words, the UE's AS context is always stored on the low-frequency site.

[0602] If there is a possibility that the UE will switch to a high-frequency site in the future, for example, if there is no low-frequency site coverage, the UE is not allowed to enter the RRC_INACTIVE state.

[0603] Example 2: During the handover process, the measurement results reported by the terminal include the target cell's PCI and frequency. Sites exchange site configurations. Based on these configurations, along with the PCI and frequency, the source cell knows whether the target base station is a low-frequency or high-frequency site, or whether it uses a short-size or long-size site ID. It then addresses the target site and initiates the handover process. Alternatively, the site configuration may include a display indicator indicating whether it is a low-frequency or high-frequency site.

[0604] If there is no low-frequency site coverage but a high-frequency site does, the low-frequency site requests a control plane connection from a high-frequency site serving the site. The low-frequency site forwards RRC signaling to the high-frequency site for transmission and reception. The high-frequency site, upon receiving the control signaling, forwards it to the low-frequency site. This could be a PDCP PDU forwarding RRC signaling between the low-frequency and high-frequency sites. If the UE has no service at this time, the low-frequency site is responsible for releasing the UE to the RRC_INACTIVE state and configuring the RRC_INACTIVE configuration information. In other words, the UE's AS context is always stored on the low-frequency site.

[0605] Example 3: Adding high-frequency site addressing. The measurement results reported by the terminal include the target cell's PCI and frequency. Sites interact with each other based on site configurations. According to the interacting site configurations, as well as the PCI and frequency, the current site knows whether the target base station is a low-frequency or high-frequency site, or whether the target cell uses a short-size or long-size site ID. Then, it addresses the target site and initiates the high-frequency site addition process. Alternatively, the site configuration can carry a display indicator to indicate whether it is a low-frequency or high-frequency site.

[0606] Example 4: Addressing between high-frequency sites. When high-frequency sites need to establish a connection to transfer data, the high-frequency site can address the target site based on the length of the site ID and establish a connection.

[0607] Example 6: CP Mobility

[0608] This embodiment includes a beam method for rapidly activating high-frequency sites during CP mobility in a high- and low-frequency hybrid network.

[0609] In a hybrid high- and low-frequency network, the network side will configure measurement objects, including both low-frequency and high-frequency layers. Measurement reporting configuration can also utilize A-series and B-series events, as well as periodic measurement reporting, as described in relevant technologies.

[0610] In this network deployment scenario, terminal mobility is divided into two types: CP mobility and UP mobility.

[0611] For CP mobility, this includes handover scenarios, RRC resume scenarios, etc.

[0612] In handover scenarios, the network triggers a handover to other low-frequency sites based on the frequency layer measurement results of the CP reported by the UE. During this handover process, a new high-frequency site can be configured directly, the previous high-frequency site can be maintained, or the previous high-frequency site can be released. When adding a new high-frequency site, the low-frequency site can send the measurement results of the high-frequency site to the high-frequency site. The high-frequency site can select the beam index of the PDCCH and / or the beam index set of the PDSCH. These results are then sent to the UE for initial activation of the PDCCH TCI state and PDSCH TCI states when the high-frequency site is added.

[0613] In the RRC Resume scenario, when the network releases the UE to RRC_INACTIVE, the RNA is configured to the area range corresponding to the low-frequency site. When the UE initiates the RRC Resume procedure, it will also address the low-frequency site to obtain the UE AS context. If a low-frequency coverage vulnerability exists and the terminal is camped on a high-frequency site, the UE will be triggered to initiate the RRC Resume procedure. The network can then either keep the UE in the RRC_CONNECTED state or allow the UE to enter the RRC_IDLE state.

[0614] Example 7: ANR

[0615] This embodiment includes hierarchical management of ANR in a high- and low-frequency hybrid network.

[0616] For hybrid high- and low-frequency networks, the control plane and user plane are separated. Specifically, a terminal's control plane resides on the low-frequency network, while its user plane resides on the high-frequency network. When a user moves within a small area, operations such as adding or deleting services between high-frequency networks are performed. The high-frequency network can achieve "plug-and-play" functionality, dynamically shutting down cells without affecting coverage, thus achieving network energy savings.

[0617] Therefore, for low-frequency cells or sites responsible for control plane connections, the handover of control plane functions is handled by the low-frequency site, while for high-frequency sites, the low-frequency site is responsible for adding and deleting high-frequency sites. Thus, the neighbor cell relationship on the network side can be divided into two levels, or rather, only a first level:

[0618] First layer: Neighboring relationships between low-frequency sites

[0619] Second layer: Neighborhood relationships between low-frequency and high-frequency stations;

[0620] Therefore, a low-frequency cell can have two types of neighbor cells: one is a CP (Continuous Content Provider) cell, and the other is a load-sharing cell. A high-frequency cell, on the other hand, has only one type of neighbor cell, which is the master neighbor cell, responsible for managing the high-frequency site.

[0621] In this network-side deployment scenario, high-frequency site cells can be freely shut down without affecting the mobility of RRC_CONNECTED, RRC_IDLE / INACTIVE UEs.

[0622] For high-frequency cells, there can be two types: cells that support plug-and-play and cells that do not. Cells that do not support plug-and-play function like traditional cells, meaning they can support cell reselection and handover. Therefore, in ANR measurement reports, the cell type can be indicated, such as coverage-type, capacity-type, control plane, or user plane, or whether plug-and-play is supported. For example, cell types could be: CP only, UP only, or CP and UP. The cell type can be indicated or reduced in the SIB1 (assuming high-frequency cells can send a partially reduced SIB1) carried in the SSB.

[0623] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided 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.

[0624] 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.

[0625] 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).

[0626] Figure 6a is a schematic diagram of the structure of a terminal according to an embodiment of this disclosure. As shown in Figure 6a, the terminal 6100 may include at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the transceiver module 6101 is used to receive first information sent by a first network device; and is also used to receive second information sent by a second network device when a first condition is met, wherein the first network device includes a low-frequency cell and the second network device includes a high-frequency cell.

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

[0628] Figure 6b is a schematic diagram of the structure of a network device according to an embodiment of this disclosure. As shown in Figure 6b, the network device 6200 may include at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the network device is a first network device 102, and the transceiver module 6201 is used to send first information to a terminal, wherein the network device includes a low-frequency cell;

[0629] The network device is a second network device 103. The transceiver module 6201 is used to send second information to the terminal when the first condition is met. The network device includes a high-frequency cell.

[0630] 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.

[0631] 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. Optionally, the processing module may be interchangeable with a processor.

[0632] Figure 7a is a schematic diagram of the structure of the communication device 7100 proposed in an embodiment of this disclosure. The communication device 7100 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 7100 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.

[0633] As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can 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 7100 can be used to execute any of the above methods. Optionally, one or more processors 7101 can be used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

[0634] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 7101 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, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0635] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Optionally, all or part of the memories 7103 may be located outside the communication device 7100. In optional embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memories 7103 and can be used to receive data from the memories 7103 or other devices, and to send data to the memories 7103 or other devices. For example, the interface circuits 7104 can read data stored in the memories 7103 and send the data to the processor 7101.

[0636] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. 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 and programs; (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.; (7) others, etc.

[0637] Figure 7b is a schematic diagram of the structure of the chip 7200 proposed in an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7b, but it is not limited thereto.

[0638] Chip 7200 includes one or more processors 7201. Chip 7200 is used to perform any of the above methods.

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

[0640] In some embodiments, the interface circuit 7202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 7202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 7202 performs data interaction between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps.

[0641] 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.

[0642] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 7100, cause the communication device 7100 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.

[0643] This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0644] 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

[0645] It can communicate with the first network device and the second network device, which facilitates the rational use of low-frequency and high-frequency resources.

Claims

1. A method of communication performed by a terminal, the method comprising: receiving first information transmitted by a first network device; receiving second information transmitted by a second network device, in a case that a first condition is met; wherein the first network device comprises a low frequency cell, and the second network device comprises a high frequency cell; and wherein configuration information of the first network device is different from that of the second network device, and the configuration information comprises at least one of: whether to support transmitting a common signal; whether to support transmitting system broadcast information; whether to support paging; whether to support an initial access RACH procedure; and wherein the first information is one of: RRC signaling; and information for cell search; and wherein the first information comprises at least one of: a low frequency frequency list; a high frequency frequency list configured by the first network device; a synchronization signal block, SSB; and system information, SI. 2.The method of claim 1, wherein the second information is information for cell search. 3.The method of claim 1, further comprising: transmitting, to the second network device, request information for requesting the second information. 4.The method of claim 1, wherein the first condition comprises at least one of: absence of the low frequency cell for camping; and a measurement result of the high frequency cell being greater than or equal to a threshold configured by the first network device.

2. The method of claim 1, wherein, 5.The method of claim 1, wherein the second information comprises at least one of: an SSB; and a system information block, SIB1. 6.The method of claim 1, wherein the terminal is in a radio resource control, RRC, idle state. 7.The method of claim 1, further comprising: not searching for or not selecting the high frequency cell, in a case that a second condition is met. 8.The method of claim 7, wherein the second condition comprises at least one of: the high frequency cell being not campable; the high frequency cell not belonging to a cell corresponding to a frequency list configured by the first network device; an SSB transmitted by the high frequency cell not being on a synchronization raster; and a MIB in the SSB transmitted by the high frequency cell indicating that the high frequency cell is in a barred access state. 9.The method of claim 1, wherein: the request information is transmitted on sub-band full duplex, SBFD, time domain resources.

3. The method of claim 1, wherein, 10.The method of claim 1, further comprising: selecting or reselecting a camped cell according to a frequency priority and / or a band combination, BC, capability. 11.The method of claim 10, wherein: a frequency priority of the low frequency cell is higher than a frequency priority of the high frequency cell; or the cell with the higher frequency priority is determined according to at least one of: a priority of a frequency; a priority of a frequency range, FR; a configured or defined sub-level priority of the priority of the frequency. 12.The method of claim 10, wherein the frequency priority satisfies at least one of: being configured or defined in a frequency unit, and frequency priorities of frequency layers in different frequencies being different; being configured or defined in a band unit, and frequency priorities of frequency layers in different bands being different; or being configured or defined in an FR unit, and frequency priorities of frequency layers in different FRs being different.

4. The method of claim 3, wherein, 13.The method of claim 10, wherein: the camped cell belongs to cells in a BC supported by the terminal. 14.The method of claim 1, wherein: the first information is a paging message, and the first network device and the second network device located in a same geographical area have a same tracking area code, TAC. 15.The method of claim 1, wherein: the first information is a paging message, and the first network device and the second network device located in a same geographical area have a same tracking area code, TAC. ​ ​ 5. The method of claim 3, wherein, ​ 6. The method of claim 5, wherein, ​ ​ 7. The method of claim 5, wherein, ​ ​ ​ 8. The method of claim 5 or 6, wherein, ​ ​ ​ ​ 9. The method of claim 8, wherein, ​ ​ 10. The method of claim 9, wherein, ​ ​ ​ ​ ​ ​ ​ 12. The method of any one of claims 1 to 11, wherein, ​ ​ ​ ​ ​ 14. The method of claim 12, wherein, ​ ​ ​ ​ ​ ​ ​ ​ The first condition is that the first network device and the second network device located in the same geographical area have different TACs, the first information is a paging message sent by the first network device, and the second information is a paging message sent by the second network device.

17. The method of claim 16, wherein, The method further includes: performing a re-registration procedure when selecting or reselecting the high-frequency cell; sending first indication information to the first network device, the first indication information being used to indicate that the terminal camps on the high-frequency cell.

18. The method of claim 16, wherein The TAC includes an indication bit, which is used to indicate that the network device corresponding to the TAC is a first network device or the indication bit is used to indicate that the network device corresponding to the TAC is a second network device.

19. The method of any one of claims 1 to 18, wherein, The method further includes: sending a first measurement report to the first network device, the first measurement report including measurement results of a frequency layer of a control plane; receiving second indication information sent by the first network device, the second indication information being used to indicate at least one of the following: switching to a low-frequency cell; adding a high-frequency cell; maintaining an existing high-frequency cell; releasing an existing high-frequency cell.

20. The method of claim 19, wherein, The method further includes: receiving beam indication information sent by the first network device or the second network device.

21. The method of claim 19, wherein, The method further includes: when the terminal in an RRC inactive state camps on the high-frequency cell, requesting an RRC resume procedure.

22. The method of any one of claims 1 to 21, wherein, The method further includes: sending a second measurement report to the first network device, the second measurement report being used to indicate the type of a measured cell and also being used for the first network device to update automatic neighbor relation (ANR).

23. The method of claim 22, wherein, The type of the cell includes at least one of the following: a coverage cell; a capacity cell; a control plane cell; a user plane cell; whether it is a high-frequency cell that supports being dynamically turned on or off; The low-frequency cell is a coverage cell or a control plane cell.

24. The method of any of claims 1-23, wherein The length of the identifier for the first network device is less than the length of the identifier for the second network device.

25. The method of claim 24, wherein The first information includes third indication information, the third indication information being used to indicate the length of the identifier of the first network device; and / or The second information includes third indication information, the third indication information being used to indicate the length of the identifier of the second network device.

26. The method of any of claims 1-25, wherein The context of the terminal is stored in the first network device.

27. The method of any of claims 1-26, wherein The control plane of the terminal is located in a low-frequency network, and the user plane of the terminal is located in a high-frequency network.

28. The method of any of claims 1-27, wherein The low-frequency cell is used for a control plane; and / or The high-frequency cell is used for a user plane.

29. A communication method, performed by a first network device, the method comprising: The first information is sent to a terminal, wherein the second network device is configured to send the second information when a first condition is met, wherein the first network device comprises a low-frequency cell, and the second network device comprises a high-frequency cell.

30. The method of claim 29, wherein, The configuration information of the first network device is different from that of the second network device, and the configuration information comprises at least one of the following: Whether to support sending a common signal; Whether to support sending system broadcast information; Whether to support paging; Whether to support an initial access RACH procedure.

31. The method of claim 29, wherein, The first information comprises at least one of the following: RRC signaling; Information for cell search.

32. The method of claim 31, wherein, The first information comprises at least one of the following: A low-frequency frequency list; A high-frequency frequency list configured by the first network device; A synchronization signal block SSB; System information SI.

33. The method of any one of claims 29 to 32, wherein The frequency priority of the low-frequency cell is higher than that of the high-frequency cell; or The cell with the high frequency priority is determined according to at least one of the following: priority of a frequency, priority of a frequency range FR, and sub-priority of a configured or defined frequency priority.

34. The method of claim 33, wherein, The frequency priority satisfies at least one of the following: Configured or defined by frequency, and different frequency layers in different frequencies correspond to different frequency priorities; Configured or defined by frequency band, and different frequency layers in different frequency bands correspond to different frequency priorities; Configured or defined by FR, and different frequency layers in different FRs correspond to different frequency priorities.

35. The method of any one of claims 29 to 34, wherein The first information is a paging message, wherein the first network device and the second network device located in the same geographical area have the same tracking area code TAC, or the first condition is that the first network device and the second network device located in the same geographical area have different TACs.

36. The method of claim 35, wherein, The method further comprises: Receiving first indication information sent by the terminal, wherein the first indication information is used to indicate that the terminal camps on the high-frequency cell.

37. The method of claim 35, wherein The TAC comprises an indication bit, wherein the indication bit is used to indicate that the network device corresponding to the TAC is the first network device or the indication bit is used to indicate that the network device corresponding to the TAC is the second network device.

38. The method of any one of claims 29 to 37, wherein, The method further comprises: Receiving a first measurement report sent by the terminal, wherein the first measurement report comprises a measurement result of a frequency layer of a control plane; Sending second indication information to the terminal, wherein the second indication information is used to indicate at least one of the following: Switching to a low-frequency cell; Adding a high-frequency cell; Maintaining an existing high-frequency cell; Releasing an existing high-frequency cell.

39. The method of claim 38, wherein, The method further comprises: Sending beam indication information to the terminal.

40. The method of any one of claims 29 to 39, wherein, The method further comprises: Receiving a second measurement report sent by the terminal, wherein the second measurement report is used to indicate a type of a measured cell, and is further used for the first network device to update an automatic neighbor relation ANR.

41. The method of claim 40, wherein, The type of the cell comprises at least one of the following: A coverage cell; A capacity cell; A control plane cell; A user plane cell; Whether it is a high-frequency cell that is dynamically opened or closed. The low-frequency cell is a coverage cell or a control plane cell.

42. The method of any of claims 29-41, wherein, an identifier length for the first network device is less than an identifier length for the second network device.

43. The method of claim 42, wherein, the first information comprises third indication information, the third indication information being used to indicate the identifier length for the first network device or the identifier length for the second network device.

44. The method of any of claims 29-43, wherein, a context of the terminal is stored in the first network device.

45. The method of any of claims 29-44, wherein, a control plane of the terminal is located in a low-frequency network, and a user plane of the terminal is located in a high-frequency network.

46. The method of any of claims 29-45, wherein, the low-frequency cell is used for a control plane; and / or the high-frequency cell is used for a user plane.

47. A communication method performed by a second network device, the method comprising: sending, to a terminal, second information when a first condition is met, wherein a first network device is used to send first information, wherein the first network device comprises a low-frequency cell, and the second network device comprises a high-frequency cell.

48. The method of claim 47, wherein, configuration information of the first network device is different from configuration information of the second network device; the configuration information comprises at least one of the following: whether to support sending a common signal; whether to support sending system broadcast information; whether to support paging; whether to support an initial access RACH procedure.

49. The method of claim 47, wherein, the second information comprises information used for cell search, and the method further comprises: receiving request information sent by the terminal, the request information being used to request the second information.

50. The method of claim 47, wherein, the first condition comprises at least one of the following: there is no low-frequency cell for camping; a measurement result of the high-frequency cell is greater than or equal to a threshold configured by the first network device.

51. The method of claim 49 or 50, wherein, the second information comprises at least one of the following: an SSB; a system information block SIB1; wherein the terminal is in a radio resource control RRC idle state.

52. The method of any of claims 47-51, wherein, a frequency priority of the low-frequency cell is higher than a frequency priority of the high-frequency cell; or the cell with the high frequency priority is determined according to at least one of the following: a priority of a frequency, a priority of a frequency range FR, a configured or defined sub-priority of a frequency priority.

53. The method of claim 52, wherein, the frequency priority satisfies at least one of the following: configured or defined in a frequency unit, frequency priorities of frequency layers corresponding to different frequencies are different; configured or defined in a frequency band unit, frequency priorities of frequency layers corresponding to different frequency bands are different; configured or defined in an FR unit, frequency priorities of frequency layers corresponding to different FRs are different.

54. The method of any of claims 47-53, wherein, the second information comprises a paging message, and the first condition is that the first network device and the second network device located in a same geographical area have different TACs.

55. The method of any one of claims 47 to 53, wherein, the method further comprises: sending, to the terminal, beam indication information. 56.The method of any of claims 47-53, wherein, an identifier length for the first network device is smaller than an identifier length for the second network device. 57.The method of claim 56, wherein, the second information comprises third indication information, the third indication information being used to indicate the identifier length for the first network device or the identifier length for the second network device. 58.The method of any of claims 47-57, wherein, a control plane of the terminal is located in a low frequency network, and a user plane of the terminal is located in a high frequency network. 59.The method of any of claims 47-58, wherein, the low frequency cell is used for the control plane; and / or the high frequency cell is used for the user plane.

60. A communication system comprising: a terminal, a first network device, a second network device; the terminal is configured to perform the method of any of claims 1-28; the first network device is configured to perform the method of any of claims 29-46; the second network device is configured to perform the method of any of claims 47-58. 61.A terminal comprising: a transceiver configured to receive first information transmitted by a first network device; and further configured to receive second information transmitted by a second network device in a case where a first condition is met, wherein the first network device comprises a low frequency cell, and the second network device comprises a high frequency cell. 62.A network device comprising: a transceiver configured to transmit first information to a terminal or transmit second information to the terminal in a case where a first condition is met, wherein the network device comprises a low frequency cell or a high frequency cell. 63.A communication device comprising: one or more processors; wherein the communication device is configured to implement the method of any of claims 1-28, or any of claims 29-46, or any of claims 47-58. 64.A storage medium having stored instructions, wherein, when the instructions are run on a communication device, the communication device is caused to perform the method of any of claims 1-28, or any of claims 29-46, or any of claims 47-58. 65.A program product, wherein, when the program product is executed by a communication device, the communication device is caused to perform the method of any of claims 1-28, or any of claims 29-46, or any of claims 47-58.

Images