Migration determination methods, apparatus and storage medium
By passing relevant information between IAB nodes, allowing the first node to decide whether to trigger IAB-DU migration, solving the problems of migration conflicts and waste of signaling resources in the prior art, and improving the availability of mobile IAB nodes.
Patent Information
- Application Number
- PCT/CN2023/121242
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-25
- Publication Date
- 2025-04-03
AI Technical Summary
The prior art is difficult to effectively manage the migration of distribution units (IAB-DUs) in integrated access and backhaul (IAB) nodes, resulting in migration conflicts and waste of signaling resources, affecting the availability of mobile IAB nodes as wireless relays.
By passing the associated information between IAB nodes, the first node is allowed to decide whether to trigger the migration of the IAB-DU based on the received information, avoiding multiple nodes from triggering the migration at the same time, thereby improving the reliability and efficiency of the migration.
It effectively avoids conflicts during the IAB nodes when performing DU migration, saves signaling resources of relay equipment, and improves the availability of IAB nodes, especially mobile IAB nodes, as wireless relays.
Smart Images

Figure CN2023121242_03042025_PF_FP_ABST
Abstract
Description
Method and device for determining migration, storage medium Technical Field
[0001] The present disclosure relates to the field of communications, and in particular to a method and device for determining migration, and a storage medium. Background Art
[0002] Integrated access and backhaul (IAB) supports millimeter wave base stations for wireless access and backhaul, effectively reducing the need for additional fiber deployment when deploying dense networks and enabling wireless relay in the Next Generation Radio Access Network (NG-RAN).
[0003] Summary of the Invention
[0004] To improve the availability of IAB nodes, especially mobile IAB nodes, embodiments of the present disclosure provide a method and apparatus for determining migration, and a storage medium.
[0005] According to a first aspect of an embodiment of the present disclosure, a method for determining migration is provided. The method is performed by a first node and includes:
[0006] receiving first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU);
[0007] Based on the first information, it is determined whether to trigger DU migration.
[0008] According to a second aspect of an embodiment of the present disclosure, a method for determining migration is provided. The method is performed by a second node and includes:
[0009] First information is sent to a first node, where the first information is information associated with integrated access and backhaul distributed unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
[0010] According to a third aspect of an embodiment of the present disclosure, there is provided a first node, including:
[0011] a transceiver module configured to receive first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU);
[0012] The processing module is configured to determine whether to trigger DU migration based on the first information.
[0013] According to a fourth aspect of an embodiment of the present disclosure, a second node is provided, including:
[0014] The transceiver module is configured to send first information to the first node, where the first information is information associated with the integrated access and backhaul distribution unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
[0015] According to a fifth aspect of an embodiment of the present disclosure, there is provided a first node, including:
[0016] one or more processors;
[0017] The first node is used to execute the method for determining migration as described in any one of the first aspects.
[0018] According to a sixth aspect of an embodiment of the present disclosure, a second node is provided, including:
[0019] one or more processors;
[0020] The terminal is used to execute the method for determining migration as described in any one of the second aspects.
[0021] According to a seventh aspect of an embodiment of the present disclosure, there is provided a communication system, including:
[0022] A first node, the terminal is used to execute the method for determining migration according to any one of the first aspects;
[0023] The second node is used to execute the method for determining migration as described in any one of the second aspects.
[0024] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method for determining migration as described in any one of the first aspect or the second aspect.
[0025] In an embodiment of the present disclosure, the first node can determine whether to trigger DU migration of the IAB node based on the first information sent by the second node, thereby avoiding DU migration conflicts, saving relay device signaling resources, improving the reliability of the IAB node in performing DU migration, and improving the availability of the IAB node, especially the mobile IAB (mobile IAB) node, as a wireless relay.
[0026] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0028] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0029] FIG1B is an exemplary schematic diagram of the NG-RAN architecture provided according to an embodiment of the present disclosure.
[0030] FIG1C is an exemplary schematic diagram of a connection scenario before performing MT migration according to an embodiment of the present disclosure.
[0031] FIG1D is an exemplary schematic diagram of a connection scenario after MT migration is performed according to an embodiment of the present disclosure.
[0032] FIG. 1E is an exemplary schematic diagram of a connection scenario before and after MT migration according to an embodiment of the present disclosure.
[0033] FIG1F is a schematic diagram illustrating an exemplary process of triggering MT migration according to an embodiment of the present disclosure.
[0034] FIG1G is a schematic diagram illustrating an exemplary process of triggering an F1 connection according to an embodiment of the present disclosure.
[0035] FIG1H is a schematic diagram illustrating an exemplary process of notifying the result of establishing an F1 connection according to an embodiment of the present disclosure.
[0036] FIG2A is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0037] FIG2B is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0038] FIG3A is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0039] FIG3B is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0040] FIG3C is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0041] FIG3D is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0042] FIG4A is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0043] FIG4B is an exemplary interactive diagram of a method for determining migration provided according to an embodiment of the present disclosure.
[0044] FIG5A is an exemplary interactive diagram of an apparatus for determining migration according to an embodiment of the present disclosure.
[0045] FIG5B is an exemplary interactive diagram of an apparatus for determining migration according to an embodiment of the present disclosure.
[0046] FIG6A is a schematic diagram of an exemplary interaction of a communication device according to an embodiment of the present disclosure.
[0047] FIG6B is an exemplary interaction diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0048] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.
[0049] The embodiments of the present disclosure provide a method and device for determining migration, and a storage medium.
[0050] In a first aspect, an embodiment of the present disclosure provides a method for determining migration, the method being performed by a first node and comprising:
[0051] receiving first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU);
[0052] Based on the first information, it is determined whether to trigger DU migration.
[0053] In the above embodiment, the first node can determine whether to trigger DU migration based on first information sent by the second node, where the first information is information related to integrated access and backhaul distribution unit (IAB)-DU migration. This can avoid conflicts caused by multiple nodes simultaneously triggering the IAB node to execute DU migration, thereby improving the reliability of the IAB node in executing DU migration.
[0054] With reference to some embodiments of the first aspect, in some embodiments, receiving the first information sent by the second node includes:
[0055] Receive a first message sent by the second node; wherein the first message is an F1 interface application protocol F1AP message, and the first message includes the first information.
[0056] In the above embodiment, the first node may receive the first message sent by the second node, and the first message may be an F1AP message carrying the first information. Implementation is simple and availability is high.
[0057] In combination with some embodiments of the first aspect, in some embodiments, the first information includes DU migration information.
[0058] In the above embodiment, the first information may include DU migration information, so that the first node determines whether to trigger DU migration based on the DU migration information, thereby improving the reliability of the IAB node in performing DU migration.
[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the DU migration information includes at least one of the following:
[0060] Preconfiguration information;
[0061] Migration request information, where the migration request information is used to request the first node to trigger the DU migration.
[0062] In the above embodiment, the first node may determine whether to trigger DU migration based on pre-configuration information and / or migration request information, thereby improving the reliability of the IAB node in performing DU migration.
[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the pre-configuration information includes at least one of the following:
[0064] Base station identification information of one or more first candidate target IAB-donor-CUs of a centralized unit of an integrated access and backhaul host node, where the first candidate target IAB-donor-CUs are preconfigured candidate target IAB-donor-CUs;
[0065] IAB node identification information;
[0066] First migration time information, where the first migration time information is used to indicate pre-configured time information for migration to the corresponding first candidate target IAB-donor-CU.
[0067] In the above embodiment, the pre-configuration information may include but is not limited to the above information. The first node may determine whether to trigger DU migration based on the pre-configuration information, and determine the target IAB-donor-CU to be migrated to, thereby improving the reliability of DU migration.
[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the migration request information includes at least one of the following:
[0069] Base station identification information of one or more second candidate target IAB-donor-CUs, where the second candidate target IAB-donor-CUs are the candidate target IAB-donor-CUs to which the second node requests migration;
[0070] IAB node identification information;
[0071] Second migration time information, where the second migration time information is used to indicate time information for migrating to the corresponding second candidate target IAB-donor-CU.
[0072] In the above embodiment, the migration request information may include but is not limited to the above information. The first node may determine whether to trigger DU migration and determine the target IAB-donor-CU to be migrated to based on the migration request information, thereby improving the reliability of DU migration.
[0073] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to trigger DU migration based on the first information includes:
[0074] Determining, based on the DU migration information, to trigger the DU migration;
[0075] The method further comprises:
[0076] Based on the DU migration information and / or network load information, a target IAB-donor-CU to which the IAB-DU is to be migrated is determined.
[0077] In the above embodiment, when the first node determines to trigger DU migration based on DU migration information, it can determine the target IAB-donor-CU to which the IAB-DU is to be migrated based on the DU migration information and / or network load information. This improves the availability of IAB nodes, especially mobile IAB nodes, as wireless relays.
[0078] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0079] A second message is sent to the second node, where the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0080] In the above embodiment, the first node may send the second message to the second node, thereby triggering the IAB-DU to establish an F1 connection with the target IAB-donor-CU, thereby further improving the reliability of DU migration.
[0081] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to trigger DU migration based on the DU migration information includes:
[0082] Based on the DU migration information, it is determined not to trigger the DU migration.
[0083] In the above embodiment, the first node may also determine not to trigger DU migration based on the DU migration information, thereby avoiding conflicts with DU migrations triggered by other nodes and improving the reliability and availability of DU migration.
[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the first node is an integrated access and backhaul host IAB-donor node, and the second node is an IAB node; or,
[0085] The first node is an integrated access and backhaul host centralized unit IAB-donor-CU, and the second node is the IAB-DU; or
[0086] The first node is an F1-terminating-IAB-donor-CU, and the second node is the IAB-DU; or, the first node is a source F1-terminating-IAB-donor-CU, and the second node is a source IAB-DU; or,
[0087] The first node is a centralized unit gNB-CU of the base station, and the second node is a distributed unit gNB-DU of the base station.
[0088] In the above embodiment, the first node and the second node may correspond to the above nodes respectively, thereby improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0089] In combination with some embodiments of the first aspect, in some embodiments, the first information includes result indication information, and the result indication information is used to indicate the F1 connection establishment result.
[0090] In the above embodiment, the first information may include result indication information, and the result indication information is used to indicate the F1 connection establishment result. The first node can determine whether to trigger DU migration based on the F1 connection establishment result, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0091] In conjunction with some embodiments of the first aspect, in some embodiments, the result indication information is used to indicate:
[0092] The result of the third node establishing the F1 connection with the fourth node.
[0093] In the above embodiment, the result indication information can be used to indicate the result of the F1 connection established between the third node and the fourth node. After the third node and the fourth node establish the F1 connection, the first node can trigger DU migration to migrate the IAB-DU to a more appropriate target IAB-donor-CU, thereby improving the reliability of the IAB node performing DU migration.
[0094] In combination with some embodiments of the first aspect, in some embodiments, the fourth node is a node determined by the second node based on the migration configuration information and / or the second message of the operation, management and maintenance OAM device, and the result indication information is used to instruct the third node to establish an F1 connection with the fourth node, and the second message is sent by the first node to the second node; wherein the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0095] In the above embodiment, the fourth node can be determined by the second node, and the second node can send result indication information to the first node via a second message. The first node can then determine, based on the second message, whether the third node should establish an F1 connection with the fourth node. This allows the first node to determine whether to trigger DU migration, thereby increasing availability.
[0096] In conjunction with some embodiments of the first aspect, in some embodiments, the result indication information includes at least one of the following:
[0097] identification information of the fourth node;
[0098] The triggering node indication information is the node that triggers the third node to establish the F1 connection with the fourth node.
[0099] In the above embodiment, the result indication information may include the above information so that the first node can identify the fourth node and the triggering node that triggers the third node to establish the F1 connection with the fourth node, thereby avoiding DU migration conflicts and improving the reliability of DU migration.
[0100] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to trigger DU migration based on the first information includes:
[0101] Based on the result indication information, it is determined to trigger establishment of a new F1 connection.
[0102] In the above embodiment, the first node can trigger a new F1 connection based on the result indication information and determine that there is a more suitable target node (a node different from the third node), so that the fourth node can perform DU migration and migrate to a more suitable target node, with high availability.
[0103] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether to trigger DU migration based on the first information includes:
[0104] Based on the result indication information, it is determined not to trigger establishment of a new F1 connection.
[0105] In the above embodiment, the first node may not trigger a new F1 connection based on the result indication information in order to avoid resource waste caused by frequent triggering of DU migration, thereby achieving high availability.
[0106] In conjunction with some embodiments of the first aspect, in some embodiments, the first node and the fourth node are IAB-donor nodes, and the second node and the third node are IAB nodes; or,
[0107] The first node and the fourth node are IAB-donor-CUs, and the second node and the third node are IAB-DUs; or,
[0108] The first node and the fourth node are F1-terminating-IAB-donor-CU, and the second node and the third node are the IAB-DU; or,
[0109] The first node is a source F1-terminating-IAB-donor-CU, the fourth node is a target F1-terminating-IAB-donor-CU, the second node is a source IAB-DU, and the third node is a target IAB-DU; or,
[0110] The first node and the fourth node are gNB-CUs, and the second node and the third node are gNB-DUs.
[0111] In the above embodiment, the first node, the second node, the third node and the fourth node may correspond to the above nodes respectively, thereby improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0112] In a second aspect, an embodiment of the present disclosure provides a method for determining migration, the method being performed by a second node and comprising:
[0113] First information is sent to a first node, where the first information is information associated with integrated access and backhaul distributed unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
[0114] With reference to some embodiments of the second aspect, in some embodiments, sending the first information to the first node includes:
[0115] Send a first message to the first node; wherein the first message is an F1 interface application protocol F1AP message, and the first message includes the first information.
[0116] In combination with some embodiments of the second aspect, in some embodiments, the first information includes DU migration information.
[0117] In conjunction with some embodiments of the second aspect, in some embodiments, the DU migration information includes at least one of the following:
[0118] Preconfiguration information;
[0119] Migration request information, where the migration request information is used to request the first node to trigger DU migration.
[0120] In conjunction with some embodiments of the second aspect, in some embodiments, the pre-configuration information includes at least one of the following:
[0121] Base station identification information of one or more first candidate target IAB-donor-CUs of a centralized unit of an integrated access and backhaul host node, where the first candidate target IAB-donor-CUs are preconfigured candidate target IAB-donor-CUs;
[0122] IAB node identification information;
[0123] First migration time information, where the first migration time information is used to indicate pre-configured time information for migration to the corresponding first candidate target IAB-donor-CU.
[0124] In conjunction with some embodiments of the second aspect, in some embodiments, the migration request information includes at least one of the following:
[0125] Base station identification information of one or more second candidate target IAB-donor-CUs, where the second candidate target IAB-donor-CUs are the candidate target IAB-donor-CUs to which the second node requests migration;
[0126] IAB node identification information;
[0127] Second migration time information, where the second migration time information is used to indicate time information for migrating to the corresponding second candidate target IAB-donor-CU.
[0128] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0129] A second message sent by the first node is received, where the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with a target IAB-donor-CU.
[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the first node is an integrated access and backhaul host IAB-donor node, and the second node is an IAB node; or,
[0131] The first node is an integrated access and backhaul host centralized unit IAB-donor-CU, and the second node is the IAB-DU; or
[0132] The first node is an F1-terminating-IAB-donor-CU, and the second node is the IAB-DU; or, the first node is a source F1-terminating-IAB-donor-CU, and the second node is a source IAB-DU; or,
[0133] The first node is a centralized unit gNB-CU of the base station, and the second node is a distributed unit gNB-DU of the base station.
[0134] In combination with some embodiments of the second aspect, in some embodiments, the first information includes result indication information, and the result indication information is used to indicate the F1 connection establishment result.
[0135] In conjunction with some embodiments of the second aspect, in some embodiments, the result indication information is used to indicate:
[0136] The result of the third node establishing the F1 connection with the fourth node.
[0137] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0138] Determining a fourth node based on migration configuration information of an operations, administration, and maintenance (OAM) device and / or a second message, where the second message is sent by the first node to the second node; wherein the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU;
[0139] Determine that the result indication information is used to instruct the third node to establish an F1 connection with the fourth node.
[0140] In conjunction with some embodiments of the second aspect, in some embodiments, the result indication information includes at least one of the following:
[0141] identification information of the fourth node;
[0142] The triggering node indication information is the node that triggers the third node to establish the F1 connection with the fourth node.
[0143] In conjunction with some embodiments of the second aspect, in some embodiments, the first node and the fourth node are IAB-donor nodes, and the second node and the third node are IAB nodes; or,
[0144] The first node and the fourth node are IAB-donor-CUs, and the second node and the third node are IAB-DUs; or,
[0145] The first node and the fourth node are F1-terminating-IAB-donor-CU, and the second node and the third node are the IAB-DU; or,
[0146] The first node is a source F1-terminating-IAB-donor-CU, the fourth node is a target F1-terminating-IAB-donor-CU, the second node is a source IAB-DU, and the third node is a target IAB-DU; or,
[0147] The first node and the fourth node are gNB-CUs, and the second node and the third node are gNB-DUs.
[0148] In a third aspect, an embodiment of the present disclosure provides a first node, including:
[0149] a transceiver module configured to receive first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU);
[0150] The processing module is configured to determine whether to trigger DU migration based on the first information.
[0151] In a fourth aspect, an embodiment of the present disclosure provides a second node, including:
[0152] The transceiver module is configured to send first information to the first node, where the first information is information associated with the integrated access and backhaul distribution unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
[0153] In a fifth aspect, an embodiment of the present disclosure provides a first node, including:
[0154] one or more processors;
[0155] The first node is used to execute the method for determining migration as described in any one of the first aspects.
[0156] In a sixth aspect, an embodiment of the present disclosure provides a second node, including:
[0157] one or more processors;
[0158] The terminal is configured to execute any one of the migration determination methods described by the second node.
[0159] In a seventh aspect, an embodiment of the present disclosure provides a communication system, including:
[0160] A first node, the terminal is used to execute the method for determining migration according to any one of the first aspects;
[0161] The second node is used to execute the method for determining migration as described in any one of the second aspects.
[0162] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the method for determining migration as described in any one of the first aspect or the second aspect.
[0163] It is understandable that the above-mentioned relay device, access network node, first node, second node, core network node, communication system, storage medium, program product, and computer program are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.
[0164] The present disclosure provides a method, device, and storage medium for determining migration. In some embodiments, the terms "determining migration" and "authorization method," "authorization processing method," and "communication method" are interchangeable. The terms "device for determining migration" and "authorization method device," "authorization device," and "communication device" are interchangeable. The terms "system for determining migration" and "communication system" are interchangeable.
[0165] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0166] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.
[0167] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.
[0168] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.
[0169] In the embodiments of the present disclosure, “plurality” refers to two or more.
[0170] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.
[0171] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.
[0172] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.
[0173] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.
[0174] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0175] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.
[0176] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.
[0177] In some embodiments, "network" can be interpreted as devices included in the network, such as relay devices, access network nodes, core network nodes, etc.
[0178] In some embodiments, a "repeater device" may also be referred to as a relay node, and an "access network device (AN device)" may also be referred to as a "radio access network device (RAN device)", a "base station (BS)", a "radio base station", or a "fixed station". In some embodiments, the term "node" may also be understood as an "access point", a "transmission point (TP)", a "reception point (RP)", a "transmission and / or reception point (TRP)", a "panel", an "antenna panel", an "antenna array", a "cell", a "macro cell", a "small cell", a "femto cell", a "pico cell", a "sector", a "cell group", a "serving cell", a "carrier", a "component carrier", a "bandwidth part (BWP)", or the like.
[0179] In some embodiments, the "relay device" is an IAB-node, a mobile IAB-node, a VMR (vehicle-mounted relays), or an MBSR (Mobile Base Station Relay).
[0180] In some embodiments, the "terminal portion of the relay device" is an IAB-MT.
[0181] In some embodiments, the "terminal part of the relay device" is an IAB-MT in an IAB AB-node or a mobile IAB-MT in a mobile IAB-node.
[0182] In some embodiments, the "access network portion of the relay device" is an IAB-DU.
[0183] In some embodiments, the "terminal part of the relay device" is an IAB-DU in an IAB-node or a mobile IAB-DU in a mobile IAB-node.
[0184] In the embodiment of the present disclosure, the IAB may be replaced by a VMR or an MBSR.
[0185] 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.
[0186] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.
[0187] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
[0188] In some embodiments, data, information, etc. may be obtained with the user's consent.
[0189] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.
[0190] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.
[0191] As shown in FIG1A , a communication system 100 includes a relay node 101 , an access network node 102 , and a core network node 103 .
[0192] In some embodiments, relay node 101, also known as an IAB-node, supports wireless access and backhaul over New Radio (NR). The network-side NR backhaul termination node is called an IAB-donor node, which is a gNB with IAB functionality. Backhaul can be performed over a single hop or multiple hops.
[0193] In some embodiments, the access network node 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network node may include an integrated access backhaul base station (IAB-donor), an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.
[0194] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between access network nodes or within access network nodes involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.
[0195] In some embodiments, the access network node can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network node, with some of the functions of the protocol layer centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer distributed in the DU, which is centrally controlled by the CU, but is not limited to this.
[0196] In some embodiments, the core network node 103 may be a device including multiple network elements, or may be multiple devices or device groups, each including all or part of multiple network elements. The network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).
[0197] In some embodiments, the core network node 103 may include multiple network elements, such as an access and mobility management function (AMF), a user plane function (UPF), etc.
[0198] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).
[0199] In some embodiments, in the NG-RAN architecture, such as that shown in Figure 1B , an access network node may be provided as an IAB-donor. The IAB-donor may include an IAB-donor-CU and one or more IAB-donor-DUs. When the gNB-CU control plane (gNB-CU-CP) and gNB-CU user plane (gNB-CU-UP) are separated, the IAB-donor node may include an IAB-donor-CU-CP, multiple IAB-donor-CU-UPs, and multiple IAB-donor-DUs. The IAB-node can connect to an upstream IAB node (IAB-node) or IAB-donor-DU via a subset of terminal device functionality of the fifth-generation mobile communication radio (NR Uu) interface (referred to as the IAB-MT functionality in the IAB-node). The IAB-node provides wireless backhaul to downstream IAB nodes and terminal devices via network functionality of the NR Uu interface (referred to as the IAB-DU functionality in the IAB-node).
[0200] The control plane (F1-C) traffic of the F1 interface between the IAB-node and the IAB-donor-CU is backhauled via the IAB-donor-DU and an optional intermediate IAB-node. The F1-U traffic between the IAB-node and the IAB-donor-CU is backhauled via the IAB-donor-DU and an optional intermediate IAB-node.
[0201] In the Release 18 (R18) IAB research project, the mobile IAB scenario is supported. The mobile IAB research work focuses on the scenario where the vehicle-mounted mobile IAB node provides 5G coverage / capability enhancement for the vehicle-mounted and / or surrounding terminals.
[0202] The IAB-donor to which an IAB-node is connected may change as the IAB-node moves, necessitating an IAB-node migration. Migrations can be categorized as partial migrations, which include but are not limited to migrating only the IAB-MT, and full migrations, which include migrating both the IAB-MT and IAB-DU to the same IAB-donor.
[0203] Partial migration may mean that only the IAB-MT on the IAB-node migrates (also called switching) to a new IAB-donor, while the IAB-DU on the IAB-node still maintains a connection with the original IAB-donor (the connection needs to pass through the IAB-donor-DU of the IAB-MT, that is, the corresponding transmission path needs to be established under the IAB-donor of the IAB-MT), and the UE context on the IAB-DU is also stored on the original IAB-donor.
[0204] For example, as shown in Figures 1C and 1D, Figure 1C shows a Uu connection established between IAB-MT and IAB-donor-CU1, and an F1 connection established between IAB-DU1 and IAB-donor-CU1, before partial migration. Figure 1D shows a Uu connection established between IAB-MT and IAB-donor-CU2, after IAB-MT migration, while IAB-DU1 and IAB-donor-CU1 maintain an F1 connection.
[0205] In the embodiments of the present disclosure, the migration of IAB-DUs can be performed independently of the IAB-MT. That is, only the IAB-DUs on the IAB-node are migrated to a new IAB-donor. For example, the IAB-node in the present disclosure may refer to a mobile IAB-node.
[0206] IAB-DU can perform migration independently. When performing DU migration, all terminals served by the IAB-DU need to migrate from one IAB-donor to another IAB-donor. However, the IAB-DU needs to disconnect the F1 connection with the source IAB-donor-CU and then establish a new F1 connection with the target IAB-donor-CU. This will cause the terminal connection to be interrupted and the terminal needs to re-establish the connection.
[0207] To avoid interruption of terminal services, as shown in Figure 1E , a new logical DU can be established on the IAB-node. This logical DU is connected to the target IAB-donor-CU of the IAB-DU, which is IAB-donor-CU2 in Figure 1E , thereby enabling terminal migration. From the terminal's perspective, the handover is from a logical cell of IAB-DU1 to a logical cell of IAB-DU2. This reuses the legacy handover process and reduces service interruption.
[0208] In some embodiments, the present disclosure further provides a schematic diagram for triggering DU migration, such as shown in FIG1F . DU migration can be triggered by a source donor-CU, such as in step 1a of FIG1F , or by an operations, administration, and maintenance (OAM) device connected to the IAB-MT, such as in step 1b of FIG1F . Triggering DU migration includes, but is not limited to, sending the gNB ID (gNB ID) of the target donor-CU and the terminal ID corresponding to the IAB-MT to the IAB-node, so that the IAB-DU2 establishes an F1 connection with the target donor-CU, such as in step 2 of FIG1F .
[0209] The RRC-terminating donor-CU is the donor-CU of the IAB-MT, and the F1-terminating donor-CU is the donor-CU of the IAB-DU. After IAB-DU2 establishes an F1 connection with the target donor-CU, IAB-DU1 notifies the source donor-CU of the establishment result.
[0210] In some embodiments, the purpose of the Mobile IAB F1 Setup Trigger procedure is to trigger the establishment of an F1 interface between a target logical gNB-DU and a target F1-terminating donor-CU. The target logical gNB-DU is co-located with the gNB-DU that receives the trigger message. Based on the trigger message, the target logical gNB-DU establishes an F1 interface toward the target F1-terminating donor-CU to support Mobile IAB-DU migration. This procedure uses non-terminal-related signaling.
[0211] For example, as shown in Figure 1G , the gNB-CU initiates this process by sending a Mobile Integrated Access and Backhaul F1 Setup Trigger (MIAB F1SETUP TRIGGERING) message to the gNB-DU. The gNB-DU initiates Transport Network Layer (TNL) connection establishment and F1 connection establishment to the target F1-terminating donor-CU indicated by the target gNB ID included in the MIAB F1setup TRIGGERING message.
[0212] If the MIAB F1 SETUP TRIGGERING message contains the target gNB Internet Protocol (IP) address information element (IE), the gNB-DU shall store this IP address and use it for establishing the Stream Control Transmission Protocol (SCTP) association and for establishing the F1 interface towards the target F1-terminating donor-CU.
[0213] If the MIAB F1 SETUP TRIGGERING message contains the Target Security Gateway (SeGW) IP Address IE, the gNB-DU shall store this IP address and use it for establishing a secure connection to protect the F1 interface towards the target F1-terminating donor-CU.
[0214] In some embodiments, the purpose of the Mobile IAB F1 Establishment Result Notification procedure is to report the result of the F1 interface establishment between the target logical gNB-DU and the target F1-terminating donor-CU. The target logical gNB-DU is co-located with the gNB-DU that sent the Notification message and can be used to establish another F1 interface to support Mobile IAB-DU migration. This procedure uses non-termination-related signaling.
[0215] For example, as shown in Figure 1H , the gNB-DU initiates this procedure by sending a MIAB F1 SETUP OUTCOME NOTIFICATION message to the gNB-CU. After the target logical gNB-DU co-located with the gNB-DU has performed the F1 setup procedure with the target F1-terminating donor-CU, the gNB-DU sends the MIAB F1 SETUP OUTCOME NOTIFICATION message to the gNB-CU to report the F1 setup result to the target F1-terminating donor-CU.
[0216] If the activated cell mapping list is included in the MIAB F1 SETUP OUTCOME NOTIFICATION message, the gNB-CU shall take the activated cell mapping list into account when further performing handover of the terminal connection from this gNB-DU to its co-located target logical gNB-DU, if cell mapping lists are supported.
[0217] In some embodiments, both the OAM and the source donor-CU can trigger DU migration. If the OAM and the source donor-CU choose to migrate an IAB-DU to different target IAB-donor-CUs, a DU migration conflict may occur. To avoid DU migration conflicts, the present disclosure provides a method, apparatus, and storage medium for determining migration, which effectively avoid DU migration conflicts, improve the reliability of IAB nodes executing DU migration, and enhance the availability of IAB nodes, particularly mobile IAB nodes, as wireless relays.
[0218] FIG2A is an interactive diagram illustrating a method for determining migration according to an embodiment of the present disclosure. As shown in FIG2A , an embodiment of the present disclosure relates to a method for determining migration, the method comprising:
[0219] Step S2101: The second node sends first information to the first node.
[0220] In some embodiments, the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU).
[0221] In some embodiments, the first information is used by the first node to determine whether to trigger DU migration.
[0222] In some embodiments, the first node may be an IAB-donor node and the second node may be an IAB node.
[0223] In the embodiment of the present disclosure, the involved IAB node may be a mobile IAB node. Due to the mobility of the mobile IAB node, partial migration, such as MT migration or DU migration, or full migration may be performed.
[0224] Of course, the IAB nodes in the present disclosure are not limited to mobile IAB nodes, and solutions for performing DU migration by other types of IAB nodes should also fall within the protection scope of the present disclosure.
[0225] For example, the IAB node sends the first information to the IAB-donor node, and the IAB-donor node determines whether to trigger DU migration based on the first information, specifically, whether to trigger DU migration of the IAB node.
[0226] In some embodiments, the first node may be an IAB-donor-CU and the second node may be an IAB-DU.
[0227] For example, the IAB-DU sends the first information to the IAB-donor-CU, and the IAB-donor-CU determines whether to trigger DU migration based on the first information, specifically, whether to trigger the IAB-DU to perform DU migration.
[0228] In some embodiments, the first node may be an F1-terminating-IAB-donor-CU, and the second node may be an IAB-DU.
[0229] For example, the IAB-DU sends the first information to the F1-terminating-IAB-donor-CU, and the F1-terminating-IAB-donor-CU determines whether to trigger DU migration based on the first information, specifically whether to trigger the IAB-DU to perform DU migration.
[0230] In some embodiments, the IAB-DU performing DU migration includes the target IAB-DU on the IAB-node establishing an F1 connection with the target IAB-donor-CU.
[0231] In some embodiments, the first node may be a centralized unit gNB-CU of the base station, and the second node may be a distributed unit gNB-DU of the base station.
[0232] For example, the gNB-DU sends the first information to the gNB-CU, and the gNB-CU determines whether to trigger DU migration based on the first information, specifically whether to trigger the gNB-DU to perform DU migration.
[0233] The above description is merely an example, and other combinations of the first node and the second node should also fall within the scope of protection of the present disclosure.
[0234] In some embodiments, the second node may send a first message to the first node, carrying the first information.
[0235] In an example, the first message may be an F1 interface application protocol (F1 Application Protocol, F1AP) message.
[0236] Exemplarily, the first message may reuse an existing F1AP message in the protocol. The second node sends the existing F1AP message to the first node, where the message carries the first information.
[0237] Exemplarily, the first message may be a new F1AP message provided by the protocol, which is used to send the first information.
[0238] In some embodiments, the first information may include DU migration information.
[0239] In some embodiments, the DU migration information may include pre-configuration information. The pre-configuration information may be DU migration related information pre-configured by the OAM. The OAM may send the pre-configuration information to the second node via the core network. The second node then sends the pre-configuration information to the first node via the first message.
[0240] Exemplarily, the pre-configuration information may include, but is not limited to, at least one of the following:
[0241] Base station identification information of one or more first candidate target integrated access and backhaul donor node centralized units (target IAB-donor-CU);
[0242] IAB node identification information;
[0243] First migration time information.
[0244] Among them, the base station identification information of the first candidate target IAB-donor-CU can be the gNB ID information of the first candidate target IAB-donor-CU.
[0245] The number of the first candidate target IAB-donor-CU may be one or more, and the pre-configuration information may include base station identification information of each candidate first candidate target IAB-donor-CU.
[0246] The first candidate target IAB-donor-CU is a pre-configured candidate target IAB-donor-CU. For example, the first candidate target IAB-donor-CU may be a pre-configured candidate target IAB-donor-CU by OAM.
[0247] The identification information of the IAB node may include, but is not limited to: terminal identification information of the IAB-MT and / or a Backhaul Adaptation Protocol (BAP) address. The present disclosure does not limit the identification information of the IAB node.
[0248] The first migration time information may be used to indicate pre-configured time information for migration to the corresponding first candidate target IAB-donor-CU.
[0249] In an embodiment of the present disclosure, the first migration time information can be used to indicate a preconfigured time point for migration to the corresponding first candidate target IAB-donor-CU, including but not limited to absolute time, such as Universal Time Coordinated (UTC), or relative time, such as a time offset value (offset) relative to the current time point.
[0250] Alternatively, the first migration time information may be used to indicate a preconfigured time period for migrating to the corresponding first candidate target IAB-donor-CU.
[0251] The present disclosure does not limit the content of the first migration time information.
[0252] Exemplarily, the OAM may pre-configure first migration time information to migrate to each first candidate target IAB-donor-CU, and send the information to the second node through the core network. After receiving the information, the second node may send the information to the first node through a first message.
[0253] In some embodiments, the DU migration information may include migration request information.
[0254] In one example, the migration request information is used to request the first node to trigger the DU migration.
[0255] In one example, the migration request information may include, but is not limited to, at least one of the following:
[0256] Base station identification information of one or more second candidate target IAB-donor-CUs;
[0257] IAB node identification information;
[0258] Second migration time information.
[0259] Among them, the base station identification information of the second candidate target IAB-donor-CU can be the gNB ID information of the second candidate target IAB-donor-CU.
[0260] The number of the second candidate target IAB-donor-CU may be one or more, and the migration request information may include base station identification information of each candidate second candidate target IAB-donor-CU.
[0261] The second candidate target IAB-donor-CU is the candidate target IAB-donor-CU to which the second node requests migration.
[0262] Exemplarily, when requesting the first node to trigger DU migration, the second node can determine one or more second candidate target IAB-donor-CUs in real time, and send the base station identification information of each second candidate target IAB-donor-CU to the first node through a first message.
[0263] The terminal identification information and / or BAP address of the IAB-MT is not limited in the present disclosure to the identification information of the IAB node.
[0264] The second migration time information may be used to indicate time information for requesting migration to the corresponding second candidate target IAB-donor-CU.
[0265] In an embodiment of the present disclosure, the second migration time information can be used to indicate the time point for requesting migration to the corresponding second candidate target IAB-donor-CU, including but not limited to absolute time, such as UTC, or relative time, such as a time offset value relative to the current time point.
[0266] Alternatively, the second migration time information may be used to indicate a preconfigured time period for migrating to the corresponding second candidate target IAB-donor-CU.
[0267] The present disclosure does not limit the content of the second migration time information.
[0268] In some embodiments, the DU migration information may include pre-configuration information and migration request information. The information content included in the pre-configuration information and migration request information has been introduced in the above embodiments and will not be repeated here.
[0269] Step S2102: The first node determines whether to trigger DU migration based on the first information.
[0270] In some embodiments, the first information includes DU migration information, and the DU migration information includes pre-configuration information. After receiving the pre-configuration information, the first node can determine to trigger DU migration based on its own decision based on the pre-configuration information.
[0271] Alternatively, the first node, as the final decision node for determining the target IAB-donor-CU, may determine to trigger DU migration based on pre-configured information.
[0272] For example, the OAM sends the pre-configuration information to the second node through the core network, and the second node forwards it to the first node. The first node may determine to trigger DU migration.
[0273] In some embodiments, the first information includes DU migration information, which includes trigger request information. After receiving the trigger request information, the first node may determine that the second node requests the first node to trigger DU migration. The first node may determine to trigger DU migration based on the trigger request information and according to its own decision.
[0274] Alternatively, the first node, as the final decision node for determining the target IAB-donor-CU, may determine to trigger DU migration based on the trigger request information.
[0275] For example, regardless of whether the second node receives the preconfiguration information, it may send the trigger request information to the first node based on its own mobility or other conditions. The first node may determine to trigger DU migration. In some embodiments, the first node may determine, based on the DU migration information, that another node has triggered DU migration. To avoid wasting signaling resources and avoiding DU migration conflicts, the first node may determine not to trigger the DU migration.
[0276] Alternatively, the first node may determine, based on the DU migration information, that the timing and / or conditions for triggering DU migration are not met, and the first node may determine not to trigger DU migration.
[0277] Exemplarily, the first node determines, based on pre-configuration information, that other nodes, such as OAM, trigger DU migration, and the first node may determine not to trigger DU migration.
[0278] Exemplarily, the first node may determine not to trigger DU migration based on the migration request information. In some embodiments, the first node may determine whether to trigger the DU migration based on pre-configuration information and the migration request information.
[0279] Exemplarily, the first node may determine to trigger the DU migration based on the pre-configuration information and the migration request information.
[0280] Exemplarily, the first node may determine not to trigger the DU migration based on the pre-configuration information and the migration request information.
[0281] Exemplarily, when the first node receives the pre-configuration information and the migration request information, and there is a common candidate target IAB-donor-CU, it determines to trigger the DU migration.
[0282] Exemplarily, when the first node receives the pre-configuration information and the migration request information and there is no common candidate target IAB-donor-CU, it determines not to trigger the DU migration.
[0283] In some embodiments, determining to trigger DU migration includes but is not limited to at least one of the following:
[0284] Determine the target IAB-donor-CU based on its own strategy (e.g., network load information).
[0285] Determine a final target IAB-donor-CU from the candidate target IAB-donor-CUs received from the second node and its own policy;
[0286] Instructs the IAB-DU to establish an F1 connection between the target DU and the finally determined target IAB-donor-CU.
[0287] In some embodiments, determining not to trigger DU migration includes but is not limited to at least one of the following:
[0288] After determining a target IAB-donor-CU according to its own policy, the target IAB-donor-CU is the same as the candidate target IAB-donor-CU received from the second node, and deciding not to instruct the target DU to establish an F1 connection with the determined target IAB-donor-CU to the IAB-DU;
[0289] After determining a target IAB-donor-CU according to its own policy, the target IAB-donor-CU is different from the candidate target IAB-donor-CU received from the second node, and deciding not to instruct the target DU to establish an F1 connection with the determined target IAB-donor-CU to the IAB-DU;
[0290] After receiving the candidate target IAB-donor-CU from the second node, it is determined that the candidate target IAB-donor-CU received by the candidate second node can be used as the final target IAB-donor-CU, and it is decided not to instruct the target DU to establish an F1 connection with the candidate target IAB-donor-CU to the IAB-DU.
[0291] The above description is merely an exemplary description, and any solution in which the first node determines whether to trigger DU migration based on the first information should fall within the scope of protection of the present disclosure.
[0292] Step S2103: The first node determines a target IAB-donor-CU to which the IAB-DU is to be migrated based on the DU migration information and / or network load information.
[0293] In some embodiments, when the first node determines to trigger DU migration, it may determine a target IAB-donor-CU to which the IAB-DU is to be migrated based on the DU migration information and / or network load information.
[0294] Exemplarily, after the first node determines to trigger DU migration, it may determine a target IAB-donor-CU to which the IAB-DU is to be migrated based on the DU migration information and / or network load information.
[0295] The network load information may be the network load information of the first candidate target IAB-donor-CU and / or the second candidate target IAB-donor-CU, or the network load information of the third candidate target IAB-donor-CU. This disclosure does not limit the candidate target IAB-donor-CU corresponding to the network load information.
[0296] Among them, the first candidate target IAB-donor-CU is a preconfigured candidate target IAB-donor-CU, the second candidate target IAB-donor-CU is the candidate target IAB-donor-CU to which the second node requests to migrate, and the third candidate target IAB-donor-CU can be the candidate target IAB-donor-CU determined by the first node based on its own decision.
[0297] For example, the first node may select one from the first candidate target IAB-donor-CU as the target IAB-donor-CU based on the pre-configuration information.
[0298] For another example, the first node may select, based on the pre-configured information, from the first candidate target IAB-donor-CUs, the one whose migration time indicated by the first migration time information is closest to the current time point as the target IAB-donor-CU.
[0299] For another example, the first node may select, based on the network load information of the third candidate target IAB-donor-CU, the one with the smallest network load from the third candidate target IAB-donor-CUs as the target IAB-donor-CU.
[0300] For another example, the first node can select, based on the pre-configuration information and the network load information of the first candidate target IAB-donor-CU, one from the first candidate target IAB-donor-CU whose migration time indicated by the first migration time information is closest to the current time point and whose network load is less than the threshold as the target IAB-donor-CU.
[0301] For another example, the first node selects one from the second candidate target IAB-donor-CU and / or the third candidate target IAB-donor-CU as the target IAB-donor-CU based on the trigger request information.
[0302] For another example, the first node selects the one with the smallest network load from the second candidate target IAB-donor-CUs as the target IAB-donor-CU based on the trigger request information and the network load information of the second candidate target IAB-donor-CU.
[0303] The above description is merely an example. All solutions in which the first node determines to trigger DU migration and further determines the target IAB-donor-CU to which the IAB-DU is to be migrated should fall within the scope of protection of the present disclosure.
[0304] Step S2104: The first node sends a second message to the second node.
[0305] In some embodiments, when the first node determines to trigger DU migration based on the first information, it may send a second message to the second node.
[0306] In some embodiments, the second message may be an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0307] In an example, the second message may be a MIAB F1 SETUP TRIGGERING message, and the second message may carry base station identification information of the target IAB-donor-CU.
[0308] The target IAB-donor-CU is a target IAB-donor-CU determined by the first node based on pre-configuration information and / or migration request information.
[0309] Exemplarily, the target IAB-donor-CU may be one of the first candidate target IAB-donor-CUs included in the pre-configuration information, or may be one of the second candidate target IAB-donor-CUs included in the migration request information, or may be one of the common candidate target IAB-donor-CUs included in the pre-configuration information and the migration request information, or may be one of the third candidate target IAB-donor-CUs determined by the first node based on its own decision. This disclosure is not limited to this.
[0310] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.
[0311] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.
[0312] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.
[0313] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, steps S2101 to S2102 can be implemented as independent embodiments, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, steps S2102 to S2104 can be implemented as an independent embodiment, and steps S2101 to S2104 can be implemented as independent embodiments, but are not limited thereto.
[0314] In some embodiments, step S2103 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S2103 may not be performed.
[0315] In some embodiments, step S2104 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S2104 may not be performed.
[0316] In some embodiments, steps S2101 to S2104 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0317] In the above embodiment, the first node can determine whether to trigger DU migration of the IAB node based on the first information sent by the second node, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0318] FIG2B is an interactive diagram illustrating a method for determining migration according to an embodiment of the present disclosure. As shown in FIG2B , an embodiment of the present disclosure relates to a method for determining migration, the method comprising:
[0319] Step S2201: The second node determines a fourth node based on the migration configuration information of the OAM device and / or the second message.
[0320] In some embodiments, the second node may serve as the final decision node for determining the target IAB-donor-CU. Accordingly, the second node may determine the fourth node. The fourth node here may be understood as the target node to be migrated to, as determined by the second node, when performing DU migration.
[0321] In some embodiments, the migration configuration information may include pre-configuration information.
[0322] Exemplarily, the OAM may send the pre-configuration information to the second node through the core network, and the second node determines whether to trigger DU migration based on the pre-configuration information, that is, to establish an F1 connection between the IAB-DU and the target IAB-donor-CU.
[0323] In some embodiments, the migration configuration information may include other information associated with the migration configured by the OAM or core network node. The migration here may be a partial migration or a full migration, which is not limited in this disclosure.
[0324] In some embodiments, the second message may be sent by the first node to the second node, wherein the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0325] In some embodiments, the second node determines the fourth node based on migration configuration information of the OAM device.
[0326] In some embodiments, the second node may determine the fourth node based on a second message sent by the first node to the second node.
[0327] In some embodiments, the second node simultaneously receives the migration configuration information from the OAM and the second message from the first node. The second node, as the final decision node, can jointly determine the fourth node based on the migration configuration information and the second message.
[0328] The combination of the second node and the fourth node will be introduced in subsequent steps and will not be introduced here.
[0329] Step S2202: The second node sends first information to the first node.
[0330] In some embodiments, the first information may include result indication information, where the result indication information is used to indicate the result of the F1 connection establishment.
[0331] In some embodiments, the second node determines a fourth node, and the determination result indication information is used to instruct the third node to establish an F1 connection with the fourth node.
[0332] In some embodiments, the second node may indicate the result of establishing the F1 connection between the third node and the fourth node through result indication information, wherein the result includes but is not limited to successful establishment of the F1 connection.
[0333] In some embodiments, the result indication information may include, but is not limited to, at least one of the following:
[0334] identification information of the fourth node;
[0335] The triggering node indication information is the node that triggers the third node to establish the F1 connection with the fourth node.
[0336] The triggering node may be an OAM or other node, and the other node may be an IAB-donor node, which is not limited in the present disclosure.
[0337] In some embodiments, the second node may send a first message to the first node. The first message may be an F1AP message carrying first information, that is, carrying result indication information.
[0338] In some embodiments, the first message may be a MIAB F1 SETUP OUTCOME NOTIFICATION message.
[0339] In some embodiments, the first node and the fourth node are IAB-donor nodes, and the second node and the third node are IAB nodes.
[0340] In the embodiment of the present disclosure, the involved IAB node may be a mobile IAB node. Due to the mobility of the mobile IAB node, partial migration, such as MT migration or DU migration, or full migration may be performed.
[0341] Of course, the IAB nodes in the present disclosure are not limited to mobile IAB nodes, and solutions for performing DU migration by other types of IAB nodes should also fall within the protection scope of the present disclosure.
[0342] Exemplarily, the first node is IAB-node #1, the fourth node is IAB-donor node #2, the second node is IAB node #1, and the third node is IAB node #2.
[0343] Accordingly, the second node IAB node #1 determines the fourth node IAB-donor node #2, and the determination result indication information is used to instruct the third node IAB node #2 and the fourth node IAB-donor node #2 to establish an F1 connection. The second node IAB node #1 sends result indication information to the first node IAB-node node #1, indicating the result of the F1 connection establishment between the third node IAB node #2 and the fourth node IAB-donor node #2.
[0344] In some embodiments, the first node and the fourth node are F1-terminating-IAB-donor-CUs, and the second node and the third node are the IAB-DUs.
[0345] Exemplarily, the first node is F1-terminating-IAB-donor-CU#1, the fourth node is F1-terminating-IAB-donor-CU#2, the second node is IAB-DU#1, and the third node is IAB-DU#2.
[0346] Accordingly, the second node IAB-DU#1 determines the fourth node F1-terminating-IAB-donor-CU#2, and the determination result indication information is used to instruct the third node IAB-DU#2 and the fourth node F1-terminating-IAB-donor-CU#2 to establish an F1 connection. The second node IAB-DU#1 sends result indication information to the first node F1-terminating-IAB-donor-CU#1#1, indicating the result of the F1 connection establishment between the third node IAB-DU#2 and the fourth node F1-terminating-IAB-donor-CU#2.
[0347] In some embodiments, the first node is a source F1-terminating-IAB-donor-CU, the fourth node is a target F1-terminating-IAB-donor-CU, the second node is a source IAB-DU, and the third node is a target IAB-DU.
[0348] Exemplarily, the source IAB-DU may determine a fourth node, namely, a target F1-terminating-IAB-donor-CU. Furthermore, the source IAB-DU may determine result indication information for instructing the target IAB-DU to establish an F1 connection with the target F1-terminating-IAB-donor-CU. The source IAB-DU may send result indication information to the source F1-terminating-IAB-donor-CU, indicating the result of establishing the F1 connection between the target IAB-DU and the target F1-terminating-IAB-donor-CU.
[0349] In some embodiments, the first node and the fourth node are gNB-CUs, and the second node and the third node are gNB-DUs.
[0350] For example, the first node is gNB-CU#1, the fourth node is gNB-CU#2, the second node is gNB-DU#1, and the third node is gNB-DU#2.
[0351] Accordingly, the second gNB-DU#1 determines the fourth gNB-CU#2 and uses the determination result indication information to instruct the third gNB-DU#2 and the fourth gNB-CU#2 to establish an F1 connection. The second gNB-DU#1 sends a result indication information to the first gNB-CU#1, indicating the result of establishing the F1 connection between the third gNB-DU#2 and the fourth gNB-CU#2.
[0352] Step S2203: The first node determines whether to trigger DU migration based on the first information.
[0353] In some embodiments, the first node may determine, based on the result indication information, that the triggering node has already triggered DU migration, and thus determine that the first node will no longer trigger the establishment of a new F1 connection, that is, will no longer trigger DU migration.
[0354] In some embodiments, the first node may determine to trigger establishment of a new F1 connection when it determines, based on the result indication information, that the F1 connection between the third node and the fourth node should be terminated.
[0355] Exemplarily, considering the mobility of the mAB node, the first node may determine to trigger establishment of a new F1 connection when determining that the fourth node has changed.
[0356] Exemplarily, the first node may determine to trigger establishment of a new F1 connection when it is determined that the fourth node selected by the second node is not suitable for this DU migration.
[0357] For example, the first node reselects a target IAB-donor-CU and instructs the target IAB-DU to establish an F1 connection with the target IAB-donor-CU. Step S2204: The first node sends a second message to the second node.
[0358] In some embodiments, when the first node determines to trigger establishment of a new F1 connection based on the first information, the first node may send a second message to the second node.
[0359] In some embodiments, the second message may be an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0360] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2204. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, steps S2201 to S2202 can be implemented as independent embodiments, step S2203 can be implemented as an independent embodiment, step S2204 can be implemented as an independent embodiment, steps S2202 to S2204 can be implemented as an independent embodiment, and steps S2201 to S2204 can be implemented as independent embodiments, but are not limited thereto.
[0361] In some embodiments, step S2204 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger a new F1 connection based on the first information, step S2204 may not be performed.
[0362] In some embodiments, steps S2201 to S2204 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0363] In some embodiments, steps S2201 to S2204 may be combined with steps S2101 to S2104 or implemented independently, and this disclosure does not limit this.
[0364] In the above embodiment, the second node can send the first information to the first node after determining the fourth node and establishing an F1 connection between the third node and the fourth node. The first node determines whether to trigger the DU migration of the IAB node based on the first information sent by the second node, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0365] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to an information processing method, which is executed by a first node and includes:
[0366] Step S3101, obtain first information.
[0367] In some embodiments, the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU).
[0368] In some embodiments, the first information is used by the first node to determine whether to trigger DU migration.
[0369] In some embodiments, the first information may include DU migration information.
[0370] In some embodiments, the DU migration information may include pre-configuration information and / or migration request information.
[0371] In some embodiments, the first node may obtain the first information from the second node, but is not limited thereto. The first node may also receive the first information sent by other entities.
[0372] In some embodiments, the first node obtains the first information determined according to a predefined rule.
[0373] In some embodiments, the first node performs processing to obtain the first information.
[0374] In some embodiments, step S3101 is omitted, the first node autonomously implements the function indicated by the first information, or the first node obtains the first information based on predefined rules or protocol agreements, or the above functions are default or default.
[0375] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0376] Step S3102: Determine whether to trigger DU migration.
[0377] In some embodiments, the first node may determine whether to trigger DU migration based on the first information.
[0378] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0379] Step S3103: Determine the target IAB-donor-CU.
[0380] In some embodiments, the first node may determine, based on the first information, a target IAB-donor-CU when triggering DU migration.
[0381] In some embodiments, the optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0382] Step S3104, sending a second message.
[0383] In some embodiments, the first node may send a second message when determining to trigger DU migration based on the first information.
[0384] In some embodiments, the second node receives the second message.
[0385] In some embodiments, the second message may be an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0386] In some embodiments, the optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0387] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step S3101 can be implemented as an independent embodiment, step S3102 can be implemented as an independent embodiment, steps S3101 to S3102 can be implemented as independent embodiments, step S3103 can be implemented as an independent embodiment, step S3104 can be implemented as an independent embodiment, steps S3102 to S3104 can be implemented as an independent embodiment, and steps S3101 to S3104 can be implemented as independent embodiments, but are not limited thereto.
[0388] In some embodiments, step S3103 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S3103 may not be performed.
[0389] In some embodiments, step S3104 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S3104 may not be performed.
[0390] In some embodiments, steps S3101 to S3104 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0391] In the above embodiment, the first node can determine whether to trigger DU migration of the IAB node based on the first information sent by the second node, and when determining to trigger DU migration, determine the target IAB-donor-CU, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0392] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to an information processing method, which is executed by a first node and includes:
[0393] Step S3201, obtain first information.
[0394] In some embodiments, the first information is information associated with migration of an integrated access and backhaul distribution unit (IAB-DU).
[0395] In some embodiments, the first information is used by the first node to determine whether to trigger DU migration.
[0396] In some embodiments, the first information may include result indication information, where the result indication information is used to indicate the result of the F1 connection establishment.
[0397] In some embodiments, the first node may obtain the first information from the second node, but is not limited thereto. The first node may also receive the first information sent by other entities.
[0398] In some embodiments, the first node obtains the first information determined according to a predefined rule.
[0399] In some embodiments, the first node performs processing to obtain the first information.
[0400] In some embodiments, step S3201 is omitted, the first node autonomously implements the function indicated by the first information, or the first node obtains the first information based on predefined rules or protocol agreements, or the above functions are default or default.
[0401] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2202 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0402] Step S3202: Determine whether to trigger DU migration.
[0403] In some embodiments, the first node may determine whether to trigger DU migration based on the result indication information.
[0404] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2203 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0405] Step S3203, sending a second message.
[0406] In some embodiments, the first node may send a second message when determining to trigger DU migration based on the first information.
[0407] In some embodiments, the second node receives the second message.
[0408] In some embodiments, the second message may be an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
[0409] In some embodiments, the optional implementation of step S3203 can refer to the optional implementation of step S2204 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0410] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, and step S3203 may be implemented as an independent embodiment. Steps S3201 to S3203 may be implemented as independent embodiments, but are not limited thereto.
[0411] In some embodiments, step S3203 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger a new F1 connection based on the first information, step S3203 may not be performed.
[0412] In some embodiments, steps S3201 to S3203 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0413] In the above embodiment, the first node can determine whether to trigger DU migration of the IAB node based on the result indication information sent by the second node, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0414] FIG3C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to an information processing method, which is executed by the second node, and the method includes:
[0415] Step S3301, sending the first information.
[0416] In some embodiments, the second node may send the first information to the first node.
[0417] In some embodiments, the first node receives first information.
[0418] In some embodiments, the first information is used by the first node to determine whether to trigger DU migration.
[0419] In some embodiments, the first information may include DU migration information.
[0420] In some embodiments, the DU migration information may include pre-configuration information and / or migration request information.
[0421] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0422] Step S3302, obtain the second message.
[0423] In some embodiments, the second node may obtain the second message from the first node, but is not limited thereto. The second node may also receive the second message sent by other entities.
[0424] In some embodiments, the second node obtains the second message determined according to a predefined rule.
[0425] In some embodiments, the second node performs processing to obtain the second message.
[0426] In some embodiments, step S3302 is omitted, the second node autonomously implements the function indicated by the second message, or the second node obtains the second message based on predefined rules or protocol agreements, or the above functions are default or default.
[0427] In some embodiments, the optional implementation of step S3302 can refer to the optional implementation of step S2104 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
[0428] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3301 and S3302. For example, step S3301 may be implemented as an independent embodiment, step S3302 may be implemented as an independent embodiment, and steps S3301 to S3302 may be implemented as independent embodiments, but are not limited thereto.
[0429] In some embodiments, step S3302 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S3302 may not be performed.
[0430] In some embodiments, steps S3301 to S3302 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0431] In the above embodiment, the second node can send the first information to the first node, so that the first node determines whether to trigger the DU migration of the IAB node based on the first information. The second node can determine the target IAB-donor-CU based on the second message sent by the first node, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0432] FIG3D is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to an information processing method, which is executed by the second node, and the method includes:
[0433] Step S3401, determine the fourth node.
[0434] In some embodiments, the second node may serve as the final decision node for determining the target IAB-donor-CU. Accordingly, the second node may determine the fourth node. The fourth node here may be understood as the target node to be migrated to, as determined by the second node, when performing DU migration.
[0435] In some embodiments, the optional implementation of step S3401 can refer to the optional implementation of step S2201 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0436] Step S3402, sending the first information.
[0437] In some embodiments, the second node may send the first information to the first node.
[0438] In some embodiments, the first node receives first information.
[0439] In some embodiments, the first information is used by the first node to determine whether to trigger DU migration.
[0440] In some embodiments, the first information may include result indication information.
[0441] In some embodiments, the optional implementation of step S3402 can refer to the optional implementation of step S2202 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0442] Step S3403, obtain the second message.
[0443] In some embodiments, the second node may obtain the second message from the first node, but is not limited thereto. The second node may also receive the second message sent by other entities.
[0444] In some embodiments, the second node obtains the second message determined according to a predefined rule.
[0445] In some embodiments, the second node performs processing to obtain the second message.
[0446] In some embodiments, step S3403 is omitted, the second node autonomously implements the function indicated by the second message, or the second node obtains the second message based on predefined rules or protocol agreements, or the above functions are default or default.
[0447] In some embodiments, the optional implementation of step S3403 can refer to the optional implementation of step S2204 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0448] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step S3401 can be implemented as an independent embodiment, step S3402 can be implemented as an independent embodiment, step S3403 can be implemented as an independent embodiment, steps S3401 to S3402 can be implemented as an independent embodiment, and steps S3401 to S3403 can be implemented as independent embodiments, but are not limited thereto.
[0449] In some embodiments, step S3403 is an optional step and may be omitted or replaced in different embodiments. For example, if the first node determines not to trigger DU migration based on the first information, step S3403 may not be performed.
[0450] In some embodiments, steps S3401 to S3403 are optional steps, and one or more of these steps may be omitted or replaced in different embodiments.
[0451] In the above embodiment, the second node can determine the fourth node and send first information to the first node, where the first information is result indication information. The first node determines whether to trigger DU migration based on the first information, thereby improving the reliability of the IAB node in performing DU migration and improving the availability of the IAB node, especially the mobile IAB node, as a wireless relay.
[0452] The above method is further illustrated below with examples:
[0453] In the embodiments of the present disclosure, any of the following methods may be used to avoid DU migration conflicts:
[0454] Method 1: OAM sends the pre-configured target donor-CU information, i.e., pre-configuration information, to IAB-MT in advance. Then IAB-DU1 notifies the source donor-CU of the pre-configured target donor-CU, avoiding the source donor-CU sending an additional DU migration trigger to IAB-DU.
[0455] In method 2, the source donor-CU performs the final decision. If there is a target donor-CU selected by the OAM, the decision needs to be made by the source donor-CU. That is, IAB-DU1 sends the target donor-CU information received from the OAM (including migration request information or pre-configuration information) to the source donor-CU. The source donor-CU determines whether to trigger DU migration based on the request information, or selects the target donor-CU to trigger DU migration based on the pre-configuration information.
[0456] Method 3: The IAB-node performs the final decision. If the IAB-node receives target donor-CU information from OAM or source donor-CU at the same time, the IAB-node determines the final selected target donor-CU based on the implementation. Optionally, the IAB-DU1 indicates the selection result in the outcome information.
[0457] In an embodiment of the present disclosure, a method for determining migration is provided, including:
[0458] Solution 1, corresponding to the above methods 1 and 2:
[0459] First, the first node receives DU migration information from the second node through a first message, and the first node determines whether to trigger DU migration according to the DU migration information.
[0460] Secondly, the DU migration information includes at least one of the following information:
[0461] - Pre-configuration information;
[0462] - Migration request information.
[0463] Again, the pre-configuration information includes at least one of the following:
[0464] gNB IDs of one or more first candidate target donor-CUs;
[0465] Preconfigured first migration time information;
[0466] IAB node identification information.
[0467] Again, the migration request information includes at least one of the following:
[0468] gNB IDs of one or more second candidate target donor-CUs;
[0469] Second migration time information for executing the migration;
[0470] IAB node identification information.
[0471] Based on the above, the first node determines whether to trigger DU migration according to the DU migration information, including:
[0472] According to the DU migration information, the first node determines the target donor-CU and triggers DU migration, that is, sends a second message to the second node; or
[0473] According to the DU migration information, it is determined not to trigger DU migration, that is, not to send the second message to the second node.
[0474] The second message is used to trigger the establishment of an F1 connection between the target IAB-DU (ie, IAB-DU2) and the target IAB-donor-CU.
[0475] Based on the above, possible combinations of the first and second nodes are:
[0476] The first node is IAB-donor, and the second node is IAB-node;
[0477] The first node is IAB-donor-CU, and the second node is IAB-DU;
[0478] The first node is F1-terminating-IAB-donor-CU, and the second node is IAB-DU;
[0479] The first node is source F1-terminating-IAB-donor-CU, and the second node is source IAB-DU;
[0480] The first node is the gNB-CU and the second node is the gNB-DU.
[0481] Option 2, corresponding to method 3 above:
[0482] First, the first node receives result indication information from the second node through a first message, and the first node determines whether to trigger DU migration according to the result indication information.
[0483] Secondly, the result indication information is sent after the third node establishes the F1 connection with the third fourth node.
[0484] Again, the result indication information includes at least one of the following information:
[0485] Identification information of the fourth node, used to indicate the fourth node, for example, the gNB ID of the Target donor-CU;
[0486] Identification information of a triggering node, where the triggering node is the node that triggers the third node to establish a connection with the fourth node, for example, an OAM or IAB-donor.
[0487] Based on the above, the first node determines whether to trigger DU migration according to the result indication information, including:
[0488] The first node determines not to trigger DU migration based on the result indication information, that is, does not send a second message to the second node. The second message is used to trigger the establishment of an F1 connection between the target IAB-DU (i.e., IAB-DU2) and the target IAB-donor-CU; or
[0489] The first node determines to trigger DU migration according to the result indication information, that is, sends a second message to the second node.
[0490] Based on the above, the possible combinations of the first node, the second node, the third node, and the fourth node are:
[0491] The first and fourth nodes are IAB-donors, and the second and third nodes are IAB-nodes;
[0492] The first and fourth nodes are IAB-donor-CU, and the second and third nodes are IAB-DU;
[0493] The first and fourth nodes are F1-terminating-IAB-donor-CU, and the second and third nodes are IAB-DU;
[0494] The first node is the source F1-terminating-IAB-donor-CU, the fourth node is the target F1-terminating-IAB-donor-CU, the second node is the source IAB-DU, and the third node is the target IAB-DU;
[0495] The first and fourth nodes are gNB-CUs, and the second and third nodes are gNB-DUs.
[0496] In Example 1 (corresponding to Method 1 and Method 2), as shown in FIG4A , the following steps are omitted except for the contents not related to the invention:
[0497] Step S4100: The IAB-MT receives pre-configuration information from the OAM.
[0498] In step S4101, the gNB-DU (i.e., IAB-DU1) sends a first message to the gNB-CU (i.e., F1-terminating IAB-donor-CU).
[0499] Among them, the gNB-DU can correspond to the above-mentioned second node, and the gNB-CU can correspond to the above-mentioned first node.
[0500] Among them, the first message is an F1AP message.
[0501] The first message includes DU migration information.
[0502] The DU migration information includes at least one of the following information:
[0503] (Corresponding to method 1) pre-configured information, including one or more pre-configured base station identification information of the first candidate target donor-CU, and / or first migration time information, and / or identification information of the IAB node;
[0504] (Corresponding to method 2) The migration request information includes base station identification information of one or more second candidate target donor-CUs requested for migration, and / or second migration time information, and / or identification information of the IAB node.
[0505] The gNB-CU performs at least one of the following operations based on the DU relocation information:
[0506] (Solution 1) The Mobile 1AB F1 Setup Triggering message is not sent to the gNB-DU to avoid simultaneous occurrence of DU migration triggered by OAM.
[0507] (Method 2) A second message is sent to the gNB-DU (the second message is an F1AP message, e.g., a Mobile 1AB F1Setup Triggering message), and the target gNB ID included in the message is the target donor-CU indicated in the DU migration configuration information (i.e., step S4102 in Figure 4A).
[0508] In the above embodiment, conflicts between DU migration triggered by the source donor-CU and DU migration triggered by OAM can be avoided, and the most appropriate target donor-CU can be determined based on the OAM configuration and network load, thereby ensuring the service experience of users accessing through the IAB-node.
[0509] Example 2 (Method 3), as shown in FIG4B , the following steps are omitted for irrelevant content of the invention:
[0510] In step S4201, the gNB-DU sends a first message to the gNB-CU.
[0511] Among them, the gNB-DU can correspond to the above-mentioned second node, and the gNB-CU can correspond to the above-mentioned first node.
[0512] The first message is an F1AP message, for example, a MIAB F1 SETUP OUTCOME NOTIFICATION message.
[0513] The first message includes result indication information, and the result indication information includes at least one of the following information:
[0514] Identification information of the fourth node, such as the gNB ID of the Target donor-CU;
[0515] Identification information of the triggering node, for example, the triggering node is OAM.
[0516] The gNB-CU (source F1-terminating donor-CU) may determine whether to trigger DU migration based on the result indication information.
[0517] For example, if it is determined that OAM has triggered DU migration, the gNB-CU will not trigger DU migration.
[0518] In the above embodiment, the final target IAB-donor-CU is determined by the IAB-node, which can avoid triggering conflicts and unnecessary signaling overhead.
[0519] In some embodiments, the above method may include the method described in the embodiments of the above communication system, the first node side, the second node side, etc., which will not be repeated here.
[0520] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.
[0521] The present disclosure also provides an apparatus for implementing any of the above methods. For example, a device is provided that includes units or modules for implementing each step performed by a relay device in any of the above methods. For another example, another device is provided that includes units or modules for implementing each step performed by a first node or a second node (e.g., an access network node, a relay device, etc.) in any of the above methods.
[0522] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.
[0523] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.
[0524] FIG5A is a schematic diagram of the structure of a first node proposed in an embodiment of the present disclosure. As shown in FIG5A , the first node 5100 may include: a transceiver module 5101 and a processing module 5102 .
[0525] In some embodiments, the transceiver module 5101 is configured to receive first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit IAB-DU.
[0526] Optionally, the above-mentioned transceiver module 5101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 5100 in any of the above methods (for example, step S2101, step S2104, step S2202, step S2204, but not limited to these), which will not be repeated here.
[0527] In some embodiments, the processing module 5102 is configured to determine whether to trigger DU migration based on the first information.
[0528] Optionally, the processing module 5102 is configured to execute at least one of the other steps (such as step S2102, step S2103, step S2203, but not limited thereto) performed by the first node 5100 in any of the above methods, which are not repeated here.
[0529] FIG5B is a schematic diagram of the structure of a second node proposed in an embodiment of the present disclosure. As shown in FIG5B , the second node 5200 may include: a transceiver module 5201 .
[0530] In some embodiments, the transceiver module 5201 is configured to send first information to the first node, where the first information is information associated with the integrated access and backhaul distribution unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
[0531] Optionally, the above-mentioned transceiver module 5201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second node 5200 in any of the above methods (for example, step S2101, step S2104, step S2202, step S2204, but not limited to these), which will not be repeated here.
[0532] In some embodiments, the second node further includes a processing module 5202 (not shown in FIG. 5B ).
[0533] Optionally, the processing module 5102 is configured to execute at least one of the other steps (such as step S2201, but not limited thereto) executed by the second node 5200 in any of the above methods, which will not be described in detail here.
[0534] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.
[0535] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.
[0536] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., a core network node, an access network node, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a core network node in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.
[0537] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, relay devices, DUs or CUs of relay devices, etc.), execute programs, and process program data. The communication device 6100 is used to perform any of the above methods.
[0538] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may be located outside the communication device 6100.
[0539] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceiver 6103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2104, step S2202, and step S2204, but not limited thereto), and the processor 6101 performs at least one of the other steps (for example, step S2102, step S2103, step S2201, and step S2203, but not limited thereto).
[0540] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.
[0541] In some embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102. The interface circuit 6104 may be configured to receive signals from the memory 6102 or other devices, and may be configured to send signals to the memory 6102 or other devices. For example, the interface circuit 6104 may read instructions stored in the memory 6102 and send the instructions to the processor 6101.
[0542] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component 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, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
[0543] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. For the case where the chip 6200 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.
[0544] The chip 6200 includes one or more processors 6201 , and the chip 6200 is configured to execute any of the above methods.
[0545] In some embodiments, the chip 6200 further includes one or more interface circuits 6202. Optionally, the interface circuit 6202 is connected to the memory 6203. The interface circuit 6202 can be used to receive signals from the memory 6203 or other devices, and can be used to send signals to the memory 6203 or other devices. For example, the interface circuit 6202 can read instructions stored in the memory 6203 and send the instructions to the processor 6201.
[0546] In some embodiments, the interface circuit 6202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2104, step S2202, step S2204, but not limited to these), and the processor 6201 executes at least one of the other steps (for example, step S2102, step S2103, step S2201, step S2203, but not limited to these).
[0547] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.
[0548] In some embodiments, the chip 6200 further includes one or more memories 6203 for storing instructions. Alternatively, all or part of the memories 6203 may be located outside the chip 6200.
[0549] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.
[0550] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0551] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.
[0552] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.
[0553] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A method for determining migration, characterized in that The method is performed by a first node and includes: receiving first information sent by the second node, where the first information is information associated with migration of an integrated access and backhaul distribution unit IAB-DU; Based on the first information, it is determined whether to trigger DU migration.
2. The method according to claim 1, characterized in that The receiving first information sent by the second node includes: Receive a first message sent by the second node; wherein the first message is an F1 interface application protocol F1AP message, and the first message includes the first information.
3. The method according to claim 1 or 2, characterized in that: The first information includes DU migration information.
4. The method according to claim 3, characterized in that The DU migration information includes at least one of the following: Pre-configuration information; Migration request information, where the migration request information is used to request the first node to trigger the DU migration.
5. The method according to claim 4, characterized in that The pre-configuration information includes at least one of the following: Base station identification information of one or more first candidate target integrated access and backhaul host node centralized unit target IAB-donor-CU, wherein the first candidate target IAB-donor-CU is a pre-configured candidate target IAB-donor-CU; IAB node identification information; The first migration time information is used to indicate the pre-configured time information of migration to the corresponding first candidate target IAB-donor-CU.
6. The method according to claim 4, characterized in that The migration request information includes at least one of the following: base station identification information of one or more second candidate target IAB-donor-CUs, where the second candidate target IAB-donor-CU is the candidate target IAB-donor-CU to which the second node requests migration; IAB node identification information; Second migration time information, where the second migration time information is used to indicate time information for migrating to the corresponding second candidate target IAB-donor-CU.
7. The method according to any one of claims 3 to 6, characterized in that: The determining, based on the first information, whether to trigger DU migration includes: Based on the DU migration information, determining to trigger the DU migration; The method further comprises: Based on the DU migration information and / or the network load information, a target IAB-donor-CU to which the IAB-DU is to be migrated is determined.
8. The method according to claim 7, characterized in that The method further comprises: A second message is sent to the second node, where the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
9. The method according to any one of claims 3 to 6, characterized in that: The determining whether to trigger DU migration based on the DU migration information includes: Based on the DU migration information, it is determined not to trigger the DU migration.
10. The method according to any one of claims 3 to 9, characterized in that: The first node is an integrated access and backhaul host IAB-donor node, and the second node is an IAB node; or, The first node is an integrated access and backhaul host centralized unit IAB-donor-CU, and the second node is the IAB-DU; or, The first node is a F1-terminating-IAB-donor-CU, and the second node is the IAB-DU; or The first node is a source F1-terminating-IAB-donor-CU, and the second node is a source IAB-DU; or, The first node is a centralized unit gNB-CU of the base station, and the second node is a distributed unit gNB-DU of the base station.
11. The method according to claim 1 or 2, characterized in that: The first information includes result indication information, and the result indication information is used to indicate the F1 connection establishment result.
12. The method according to claim 11, characterized in that The result indication information is used to indicate: The result of the third node establishing the F1 connection with the fourth node.
13. The method according to claim 11 or 12, characterized in that: The fourth node is a node determined by the second node according to the migration configuration information of the operation management and maintenance OAM device and / or the second message, and the result indication information is used to instruct the third node to establish an F1 connection with the fourth node, and the second message is sent by the first node to the second node; wherein the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU.
14. The method according to any one of claims 11 to 13, characterized in that: The result indication information includes at least one of the following: identification information of the fourth node; The triggering node indication information is the node that triggers the third node to establish the F1 connection with the fourth node.
15. The method according to any one of claims 11 to 14, characterized in that: The determining, based on the first information, whether to trigger DU migration includes: Based on the result indication information, it is determined to trigger establishment of a new F1 connection.
16. The method according to any one of claims 11 to 14, characterized in that: The determining, based on the first information, whether to trigger DU migration includes: Based on the result indication information, it is determined not to trigger establishment of a new F1 connection.
17. The method according to any one of claims 11 to 16, characterized in that: The first node and the fourth node are IAB-donor nodes, and the second node and the third node are IAB nodes; or, The first node and the fourth node are IAB-donor-CU, and the second node and the third node are the IAB-DU; or, The first node and the fourth node are F1-terminating-IAB-donor-CU, and the second node and the third node are the IAB-DU; or, The first node is a source F1-terminating-IAB-donor-CU, the fourth node is a target F1-terminating-IAB-donor-CU, the second node is a source IAB-DU, and the third node is a target IAB-DU; or, The first node and the fourth node are gNB-CU, and the second node and the third node are gNB-DU.
18. A method for determining migration, characterized in that The method is performed by the second node, comprising: First information is sent to a first node, where the first information is information associated with integrated access and backhaul distribution unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
19. The method according to claim 18, characterized in that The sending the first information to the first node includes: Send a first message to the first node; wherein the first message is an F1 interface application protocol F1AP message, and the first message includes the first information.
20. The method according to claim 18 or 19, characterized in that The first information includes DU migration information.
21. The method according to claim 20, characterized in that The DU migration information includes at least one of the following: Pre-configuration information; Migration request information, where the migration request information is used to request the first node to trigger DU migration.
22. The method according to claim 21, characterized in that The pre-configuration information includes at least one of the following: Base station identification information of one or more first candidate target integrated access and backhaul host node centralized unit target IAB-donor-CU, wherein the first candidate target IAB-donor-CU is a pre-configured candidate target IAB-donor-CU; IAB node identification information; The first migration time information is used to indicate the pre-configured time information of migration to the corresponding first candidate target IAB-donor-CU.
23. The method according to claim 21, characterized in that The migration request information includes at least one of the following: base station identification information of one or more second candidate target IAB-donor-CUs, where the second candidate target IAB-donor-CU is the candidate target IAB-donor-CU to which the second node requests migration; IAB node identification information; Second migration time information, where the second migration time information is used to indicate time information for migrating to the corresponding second candidate target IAB-donor-CU.
24. The method according to any one of claims 20 to 23, characterized in that: The method further comprises: A second message sent by the first node is received, where the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with a target IAB-donor-CU.
25. The method according to any one of claims 20 to 24, characterized in that: The first node is an integrated access and backhaul host IAB-donor node, and the second node is an IAB node; or, The first node is an integrated access and backhaul host centralized unit IAB-donor-CU, and the second node is the IAB-DU; or, The first node is a centralized unit F1-terminating-IAB-donor-CU of an F1 terminating integrated access and backhaul host, and the second node is the IAB-DU; or, the first node is a source F1-terminating-IAB-donor-CU, and the second node is a source IAB-DU; or, The first node is a centralized unit gNB-CU of the base station, and the second node is a distributed unit gNB-DU of the base station.
26. The method according to claim 18 or 19, characterized in that The first information includes result indication information, and the result indication information is used to indicate the F1 connection establishment result.
27. The method according to claim 26, characterized in that The result indication information is used to indicate: The result of the third node establishing the F1 connection with the fourth node.
28. The method according to claim 26 or 27, characterized in that The method further comprises: Determine a fourth node based on the migration configuration information and / or the second message of the operation management and maintenance OAM device, wherein the second message is sent by the first node to the second node; wherein the second message is an F1AP message, and the second message is used to trigger the IAB-DU to establish an F1 connection with the target IAB-donor-CU; Determine that the result indication information is used to instruct the third node to establish an F1 connection with the fourth node.
29. The method according to any one of claims 26 to 28, characterized in that: The result indication information includes at least one of the following: identification information of the fourth node; The triggering node indication information is the node that triggers the third node to establish the F1 connection with the fourth node.
30. The method according to any one of claims 26 to 29, characterized in that: The first node and the fourth node are IAB-donor nodes, and the second node and the third node are IAB nodes; or, The first node and the fourth node are IAB-donor-CU, and the second node and the third node are the IAB-DU; or, The first node and the fourth node are F1-terminating-IAB-donor-CU, and the second node and the third node are the IAB-DU; or, The first node is a source F1-terminating-IAB-donor-CU, the fourth node is a target F1-terminating-IAB-donor-CU, the second node is a source IAB-DU, and the third node is a target IAB-DU; or, The first node and the fourth node are gNB-CU, and the second node and the third node are gNB-DU.
31. A first node, characterized in that: include: A transceiver module is configured to receive first information sent by a second node, wherein the first information is information associated with migration of an integrated access and backhaul distribution unit IAB-DU; The processing module is configured to determine whether to trigger DU migration based on the first information.
32. A second node, characterized in that: include: The transceiver module is configured to send first information to the first node, where the first information is information associated with the integrated access and backhaul distribution unit IAB-DU migration, and the first information is used by the first node to determine whether to trigger DU migration.
33. A first node, characterized in that: include: one or more processors; The first node is used to execute the method for determining migration according to any one of claims 1-17.
34. A second node, characterized in that: include: one or more processors; The second node is used to execute the method for determining migration according to any one of claims 18 to 30.
35. A communication system, characterized in that: include: A first node, wherein the first node is used to perform the method for determining migration according to any one of claims 1 to 17; A second node, wherein the second node is used to execute the method for determining migration according to any one of claims 18 to 30.
36. A storage medium storing instructions, characterized in that: When the instructions are executed on a communication device, the communication device executes the method for determining migration according to any one of claims 1-17 or 18-30.
Citation Information
Patent Citations
Node in communication system and a method thereof
CN114071599A
Method and apparatus for updating IAB-node configuration information during inter-anchor migration
CN115244978A
Node in wireless communication system and method performed by same
CN115278813A
Migration of an integrated access and backhaul node
US20220086718A1