Communication method and communication apparatus
Patent Information
- Application Number
- MYPI2025004986
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-02-16
- Filing Date
- 2024-02-05
- Publication Date
- 2024-08-16
AI Technical Summary
In the 5G network, when DU migrates and the MT does not migrate, how does the target host CU of the DU learn the downlink configuration information used for target F1 interface transmission, especially in the scenario where the DU and MT migrate to different target CUs? There are technologies that cannot effectively solve this problem.
By generating and sending information containing the identification information of the relay node, the third CU can request the second CU for downlink configuration information for F1 interface transmission, ensuring the establishment and configuration of the F1 interface. Specific steps include selecting an appropriate CU as the target host CU of the DU, ensuring the existence of an IP connection or Xn interface, receiving the identification information of the relay node, sending a request message to obtain the downlink configuration information, and performing cross-topology traffic migration when necessary.
It is realized that when DU migrates and MT does not migrate, the DU target host CU can obtain the required downlink configuration information, ensuring the correct establishment and transmission quality of the F1 interface, and solving the problem of difficulty in obtaining information in the existing technology.
Smart Images

Figure PI2025004986_DRAWING_001 
Figure PI2025004986_DRAWING_002 
Figure PI2025004986_DRAWING_003
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application with application number 202310153131.2 filed with the State Intellectual Property Office of China on February 16, 2023, and priority to the Chinese patent application with the invention name “Communication Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and in particular to a communication method and a communication device. Background Art
[0003] Compared to fourth-generation mobile communication systems, fifth-generation mobile communications (5G) imposes even more stringent requirements on various network performance indicators. These include a 1,000-fold capacity increase, wider coverage requirements, ultra-high reliability, and ultra-low latency. Given the abundance of high-frequency carrier frequencies, the use of high-frequency small cell networks is becoming increasingly popular in hotspots to meet 5G's ultra-high capacity requirements. High-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage, necessitating the dense deployment of large numbers of small cells. Providing fiber backhaul for these densely deployed small cells is, consequently, costly and difficult, necessitating economical and convenient backhaul solutions. Furthermore, to meet the need for wide coverage, fiber deployment is challenging and expensive in remote areas, necessitating the design of flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology offers a solution to both of these issues: it utilizes wireless transmission for both the access and backhaul links, reducing fiber deployment requirements.
[0004] In the IAB network, the relay node, or IAB-node, can provide wireless access services for user equipment (UE). The service data of the UE is transmitted by the IAB-node to the IAB host (IAB-donor) through a wireless backhaul link. The IAB-node includes a mobile terminal (MT) part and a distributed unit (DU) part. Among them, when the IAB-node faces its parent node, it can act as a terminal device, that is, the role of MT; when the IAB-node faces its child node (the child node may be another IAB-node, or UE), it is regarded as a network device, that is, the role of DU. The IAB-donor is an access network element with complete base station (such as gNB) functions, including a centralized unit (CU) and a distributed unit (DU). The IAB-donor is connected to the core network serving the UE (for example, connected to the 5G core network).
[0005] IAB node cross-CU migration can be implemented in two ways: full migration and partial migration. In a partial migration, the mobile operator (MT) of the migrating IAB node (i.e., the boundary node) undergoes cross-CU switching, but the boundary node's DU maintains an F1 connection with the source CU. In a full migration, the boundary node's DU must establish an F1 connection with the target host CU. The essential difference between full and partial migration lies in whether the DU migration is required (in reality, a new logical DU can be generated and then an F1 interface established with the target host CU, but from the macro perspective of the IAB node, it can often be described as "DU migration"). When the MT and DU have the same target host CU (i.e., the CU to which they are switched) (i.e., the MT also migrates before or after the DU migration, and the DU and MT migrate to the same target CU), the downlink configuration information used for F1 interface transmission is allocated by the target CU. The industry is currently researching solutions for DU migration without MT migration, i.e., solutions where the DU's target host CU (the CU to which the DU is migrating) is different from the CU to which the MT is connected. Therefore, it is necessary to study how the target host CU of the DU obtains the downlink configuration information for transmission on the target F1 interface (ie, the F1 interface between the target host CU and the DU) when the DU migrates but the MT does not migrate.
[0006] Summary of the Invention
[0007] The embodiments of the present application disclose a communication method and a communication device, which enable the target host CU of DU to obtain downlink configuration information for F1 interface transmission, thereby enabling the F1 interface to be established.
[0008] In a first aspect, an embodiment of the present application provides a communication method, the method comprising: generating first information, the first information being used to instruct a third CU to request downlink configuration information for F1 interface transmission from a second CU, the second CU having a radio resource control (RRC) connection with the MT of the relay node, or the second CU being the target CU to which the MT is about to switch, and the third CU being the target host CU of the DU of the relay node; and sending the first information to the third CU. The downlink configuration information for F1 interface transmission includes a differentiated services code point (DSCP) and / or a flow label for F1 interface transmission. The relay node may be an IAB node or other node having a DU part and an MT part. The target host CU of the DU of the relay node may be the CU to which the DU of the relay node is to be migrated. The executor of the method of the first aspect may be a first CU or a relay node, the first CU being the source host CU of the DU of the relay node, that is, there is an F1 interface between the DU of the relay node and the first CU. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information used for F1 interface transmission to be established between the third CU and the DU of the relay node.
[0009] In an embodiment of the present application, first information is sent to the third CU, where the first information is used to instruct the third CU to request downlink configuration information for F1 interface transmission from the second CU; so that the third CU obtains the downlink configuration information for F1 interface transmission, thereby enabling the F1 interface to be established.
[0010] In one possible implementation, the first information includes at least one of identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the mobile station in the second CU. The identification information of the second CU may include the gNB ID and / or Internet Protocol (IP) address of the second CU. The identification information of the DU of the relay node may include at least one of the following: the gNB-DU ID and / or IP address of the DU of the relay node, the BAP address of the relay node to which the MT belongs in the second CU, the IP address of the relay node to which the MT belongs used for F1 interface traffic transmission, the cell radio network temporary identifier (C-RNTI) and serving cell identifier of the MT. The identification information identifying the MT in the second CU may include the UE XnAP ID of the MT under the second CU. The DU of the relay node may be a new logical DU generated by the relay node, that is, a logical DU generated for DU migration. The first information may also include the UE XnAP ID of the MT under the first CU.
[0011] In this implementation, the first information is sent to the third CU, so that the third CU requests the second CU for downlink configuration information for F1 interface transmission according to the first information.
[0012] In a possible implementation manner, the first information is further used to indicate a binding relationship between the MT and the DU of the relay node.
[0013] In this implementation, the first information may enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0014] In a possible implementation, the first information is used to instruct the third CU to send a cross-topology traffic migration request to the second CU (for example, sending an IAB Transport Migration Management Request message to the second CU) to request the second CU for downlink configuration information for F1 interface transmission.
[0015] In one possible implementation, before sending the first information to the third CU, the method further includes: receiving second information from the relay node, where the second information includes identification information of a DU of the relay node. For example, the second information of a DU (not a generated logical DU) is received from the relay node. The second information may be carried in a gNB-DU Configuration Update message.
[0016] In this implementation, the second information is received from the relay node, and identification information of the DU of the relay node can be obtained so as to send the first information.
[0017] In one possible implementation, before sending the first information to the third CU, the method also includes: selecting the third CU as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU.
[0018] The F1 interface traffic between the third CU and the DU of the relay node needs to be transmitted through the topology under the second CU, wherein the transmission between the host DU of the second CU and the third CU is transmitted through the IP network. Therefore, it is necessary to ensure that the IP connection between the host DU of the second CU and the third CU exists (which can be called "IP reachability between the host DU of the second CU and the third CU"). It is generally believed that the IP reachability between the host DU of the second CU and the third CU (i.e., IP reachability) is equivalent to the IP reachability between the second CU and the third CU (because the host DU of the second CU and the second CU must be IP reachable). Therefore, when the first CU selects the target host CU of the DU, it needs to consider the IP reachability between the target host CU of the DU and the second CU. Alternatively, a more stringent judgment condition than IP reachability can be adopted: the existence or ability to establish an XN interface. In this implementation method, the third CU is selected as the target host CU of the DU of the relay node so that the F1 interface traffic between the DU of the relay node and the third CU established subsequently can be transmitted through the topology of the second CU.
[0019] In one possible implementation, the selecting of the third CU as the target host CU of the DU of the relay node includes: based on the network segment to which the IP address belongs, selecting the third CU that has an IP connection with the second CU as the target host CU of the DU of the relay node; or, selecting the third CU in the preconfigured target list as the target host CU of the DU of the relay node, where there is an IP connection, an Xn interface, or the ability to establish an Xn interface between the CU in the target list and the second CU.
[0020] In this implementation, a third CU that has an IP connection, an Xn interface, or can establish an Xn connection with the second CU is selected as the target host CU of the DU of the relay node.
[0021] In one possible implementation, the method further includes: receiving first reference information from the second CU via an XN interface, the first reference information being used to indicate that an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU; and determining, based on the first reference information, that an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU. For example, the first reference information includes multiple CUs (including the third CU) that have an IP connection, an Xn interface, or an Xn interface that can be established with the second CU.
[0022] In this implementation, it is determined based on the first reference information whether there is an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU, so as to select the third CU as the target host CU of the DU of the relay node.
[0023] In one possible implementation, the method further includes: receiving second reference information from the third CU via an XN interface, the second reference information being used to indicate that an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU; and determining, based on the second reference information, that an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU. For example, the second reference information includes multiple CUs (including the second CU) that have an IP connection, an Xn interface, or an Xn interface that can be established with the third CU.
[0024] In this implementation, it is determined based on the second reference information whether there is an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU, so as to select the third CU as the target host CU of the DU of the relay node.
[0025] In one possible implementation, the second information comes from the DU of the relay node, and the second information also includes identification information of the third CU. The identification information of the third CU includes the gNB ID and / or IP address of the third CU.
[0026] In this implementation, the second information further includes identification information of the third CU, so as to determine that the DU of the relay node establishes an F1 interface with the third CU.
[0027] In a possible implementation, the second information is used to instruct the first CU to trigger the third CU to request the second CU for downlink configuration information transmitted via the F1 interface, and the first CU is the source host CU of the DU of the relay node.
[0028] In this implementation, the second information is used to instruct the first CU to trigger the third CU to request the second CU for downlink configuration information transmitted via the F1 interface, so that the first CU promptly triggers the third CU to request the second CU for downlink configuration information transmitted via the F1 interface.
[0029] In one possible implementation, the second information is used to instruct the first CU to trigger the third CU to initiate a cross-topology process migration to the second CU. For example, the second information carries the first indication information, and the first indication information is used to instruct the first CU to trigger the third CU to initiate a cross-topology process migration to the second CU. For another example, the second information implicitly instructs the first CU to trigger the third CU to initiate a cross-topology process migration to the second CU. In other words, the second information has the function of implicit indication.
[0030] In this implementation, the second information is used to instruct the first CU to trigger the third CU to initiate cross-topology process migration to the second CU, and the first CU promptly triggers the third CU to initiate cross-topology process migration to the second CU.
[0031] In a possible implementation manner, the first information is further used to instruct the third CU to establish an F1 interface with the DU of the relay node.
[0032] In a possible implementation, the first information is further used to instruct the third CU to migrate the F1 interface traffic with the DU of the relay node to the second CU topology.
[0033] In a possible implementation, the sending the first information to the third CU includes: the DU of the relay node sends the first information to the third CU, where the first information is carried in an F1 setup request (F1 SETUP REQEUST) message.
[0034] In a possible implementation, the sending the first information to the third CU includes: the DU of the relay node sends the first information to the third CU, where the first information includes identification information identifying the MT in the second CU.
[0035] In the second aspect, an embodiment of the present application provides another communication method, which includes: receiving first information, wherein the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, and the second CU has an RRC connection with the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; sending third information to the second CU, wherein the third information is used to request downlink configuration information for F1 interface transmission. The executor of the method of the second aspect is the third CU. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission between the third CU to be established and the DU of the relay node.
[0036] In the embodiment of the present application, third information is sent to the second CU to request downlink configuration information for F1 interface transmission, so that the third CU establishes the F1 interface with the DU of the relay node.
[0037] In a possible implementation, the first information includes at least one of identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0038] In this implementation, based on the information included in the first information, it is possible to request the second CU for downlink configuration information for F1 interface transmission.
[0039] In a possible implementation, the first information is further used to indicate a binding relationship between the MT and the DU of the relay node. The identification information identifying the MT in the second CU includes a UE XnAP ID of the MT under the second CU.
[0040] In this implementation, the first information may enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0041] In a possible implementation, the first information is used to instruct the third CU to send a cross-topology traffic migration request to the second CU to request downlink configuration information for F1 interface transmission from the second CU.
[0042] In a possible implementation, the third information is further used to request a binding relationship between the MT and the DU of the relay node. The third information may include a UE XnAP ID of the MT under the third CU.
[0043] In this implementation, the third information is sent to the second CU, and the binding relationship between the MT and the DU of the relay node can also be obtained.
[0044] In a possible implementation manner, the first information comes from the DU of the relay node, and the first information is carried in an F1 setup request message (ie, an F1 SETUP REQUEST message).
[0045] In this implementation, the first information is carried in the F1 establishment request message, and there is no need to send additional information to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, which can save signaling overhead.
[0046] In one possible implementation, the first information comes from the DU of the relay node, and the first information includes identification information identifying the MT in the second CU; the method further includes: based on the identification information identifying the MT in the second CU, sending information for obtaining the binding relationship between the DU of the relay node and the MT to the second CU.
[0047] In this implementation, the information about the binding relationship between the DU and the MT of the relay node may be obtained by using the second CU to obtain the information about the binding relationship between the DU and the MT of the relay node.
[0048] In one possible implementation, the identification information of the MT includes at least one of the following: a backhaul adaptation protocol (BAP) address of the relay node to which the MT belongs in the second CU, an IP address of the relay node to which the MT belongs for F1 interface traffic transmission, and a C-RNTI and a serving cell identifier of the MT.
[0049] In a possible implementation, the method further includes: sending fourth information to the second CU, where the fourth information includes a correspondence between an IP address used for F1 interface transmission and a DSCP or flow label used for F1 interface transmission.
[0050] In this implementation, sending the fourth information to the second CU may enable the second CU to obtain the correspondence between the IP address used for F1 interface transmission and the DSCP or flow label used for F1 interface transmission.
[0051] In a possible implementation, the method further includes: receiving sixth information from the second CU, the sixth information including downlink configuration information for F1 interface transmission and identification information identifying the MT in the second CU, such as the UE XnAP ID of the MT under the second CU.
[0052] In a possible implementation manner, the first information is further used to instruct the third CU to establish an F1 interface with the DU of the relay node.
[0053] In a third aspect, an embodiment of the present application provides another communication method, which includes: receiving fifth information, the fifth information is used to instruct the second CU to send first information to the third CU, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, the second CU has an RRC connection with the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; sending the first information to the third CU. Alternatively, the fifth information is used to instruct the second CU to trigger the third CU to initiate cross-topology traffic migration to the second CU, and the first information is used to trigger the third CU to initiate cross-topology traffic migration to the second CU. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission between the third CU to be established and the DU of the relay node.
[0054] In the embodiment of the present application, the first information is sent to the third CU so that the third CU requests the second CU for downlink configuration information for F1 interface transmission.
[0055] In a possible implementation, the fifth information comes from the MT, and the fifth information includes identification information of the third CU and identification information of the DU of the relay node.
[0056] In this implementation, the fifth information comes from the MT, and the fifth information includes identification information of the third CU, so that the first information is sent to the third CU according to the fifth information.
[0057] In one possible implementation, the fifth information comes from the source host CU of the DU of the relay node, and the fifth information includes identification information of the third CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0058] In a possible implementation, the fifth information is further used to indicate to the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being executed, or the relay node and the third CU are about to establish an F1 interface).
[0059] In a possible implementation, the first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0060] In this implementation, the first information is sent to the third CU, so that the third CU requests the second CU for downlink configuration information for F1 interface transmission according to the first information.
[0061] In a possible implementation manner, the first information is used to indicate a binding relationship between the MT and the DU of the relay node.
[0062] In this implementation, the first information may enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0063] In a possible implementation manner, the first information is further used to instruct the third CU to establish an F1 interface with the DU of the relay node.
[0064] In one possible implementation, the method further includes: receiving ninth information, where the ninth information is used to indicate that DU migration of the relay node has been completed (or that an F1 interface between the DU of the relay node and the third CU has been established). The ninth information comes from the third CU or the relay node.
[0065] In a fourth aspect, an embodiment of the present application provides another communication method, which includes: generating fifth information, the fifth information being used to instruct (or trigger) the second CU to send first information to the third CU, the first information being used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, the second CU having an RRC connection with the MT of the relay node, or the second CU being the target CU to which the MT is about to switch, and the third CU being the target host CU of the DU of the relay node; and sending the fifth information to the second CU. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission between the third CU to be established and the DU of the relay node. The execution subject of the method of the fourth aspect may be the first CU or the relay node, the first CU being the source host CU of the DU of the relay node. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission between the third CU to be established and the DU of the relay node.
[0066] In the embodiment of the present application, the fifth information is sent to the second CU so that the second CU sends the first information to the third CU, so that the third CU can obtain downlink configuration information for F1 interface transmission.
[0067] In one possible implementation, the sending of the fifth information to the second CU includes: the source host CU of the DU of the relay node sends the fifth information to the second CU, and the fifth information includes the identification information of the third CU, the identification information of the DU of the relay node, and the identification information identifying the MT in the second CU.
[0068] In a possible implementation, before generating the fifth information, the method further includes: receiving seventh information of the DU from the relay node, where the seventh information includes identification information of the DU of the relay node.
[0069] In this implementation, the seventh information of the DU from the relay node is received, and the identification information of the DU of the relay node can be obtained.
[0070] In one possible implementation, before generating the fifth information, the method further includes: selecting the third CU as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU.
[0071] In one possible implementation, the selecting of the third CU as the target host CU of the DU of the relay node includes: based on the network segment to which the IP address belongs, selecting the third CU that has an IP connection with the second CU as the target host CU of the DU of the relay node; or, selecting the third CU in the preconfigured target list as the target host CU of the DU of the relay node, where there is an IP connection, an Xn interface, or the ability to establish an Xn interface between the CU in the target list and the second CU.
[0072] In this implementation, a third CU that has an IP connection, an Xn interface, or can establish an Xn connection with the second CU is selected as the target host CU of the DU of the relay node.
[0073] In a possible implementation, before sending the fifth information to the second CU, the method further includes: receiving eighth information of the DU from the relay node, where the eighth information is used to trigger the first CU to send the fifth information to the second CU.
[0074] In this implementation, the eighth information is received from the relay node, and the eighth information triggers the sending of the fifth information to the second CU.
[0075] In a possible implementation, the eighth information includes identification information of the second CU, identification information of the third CU, and identification information of the DU of the relay node.
[0076] In a possible implementation, the sending the fifth information to the second CU includes: the relay node sending the fifth information to the second CU, where the fifth information includes identification information of the third CU and identification information of the DU of the relay node.
[0077] In a fifth aspect, an embodiment of the present application provides another communication method, which includes: generating tenth information, the tenth information including identification information of the second CU, identification information of the DU of the relay node, identification information of the MT identifying the relay node in the second CU, and downlink configuration information for transmission of the F1 interface (not yet established) between the DU of the relay node and the third CU, the second CU and the MT have an RRC connection, and the third CU is the target host CU of the DU of the relay node; sending the tenth information to the third CU, the tenth information is used for the third CU to establish the F1 interface between the DU of the relay node. The executor of the method of the fifth aspect is the second CU.
[0078] In the embodiment of the present application, the tenth information is sent to the third CU so that the third CU establishes an F1 interface with the DU of the relay node.
[0079] In a possible implementation manner, the tenth information is further used to indicate a binding relationship between the MT and the DU of the relay node.
[0080] In one possible implementation, before sending the tenth information to the third CU, the method also includes: receiving eleventh information, wherein the eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the F1 interface (not completed establishment) between the DU of the relay node and the third CU to the third CU.
[0081] In this implementation, the eleventh information is received so that the tenth information is sent to the third CU according to the eleventh information.
[0082] In a possible implementation manner, the eleventh information comes from the MT, and the eleventh information includes identification information of the third CU and identification information of the DU of the relay node.
[0083] In a possible implementation, the eleventh information comes from the source host CU of the DU of the relay node, and the eleventh information includes identification information of the third CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0084] In a possible implementation, the eleventh information is also used to indicate to the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being executed, or the relay node and the third CU are about to establish an F1 interface).
[0085] In one possible implementation, the method further includes: receiving ninth information, where the ninth information is used to indicate that DU migration of the relay node has been completed (or that an F1 interface between the DU of the relay node and the third CU has been established). The ninth information comes from the third CU or the relay node.
[0086] In a sixth aspect, an embodiment of the present application provides another communication method, which includes: receiving tenth information, the tenth information including identification information of the second CU, identification information of the DU of the relay node, identification information of the MT identifying the relay node in the second CU, and at least one of the downlink configuration information for transmission of the F1 interface (not yet established) between the DU of the relay node and the third CU, wherein there is an RRC connection between the second CU and the MT, and the third CU is the target host CU of the DU of the relay node; based on the tenth information, establishing the F1 interface between the third CU and the DU of the relay node.
[0087] In an embodiment of the present application, based on the tenth information, an F1 interface is established between the third CU and the DU of the relay node. There is no need to send additional information to obtain downlink configuration information for F1 interface transmission between the DU of the relay node and the third CU, which can save signaling overhead.
[0088] In a possible implementation manner, the tenth information is further used to indicate a binding relationship between the MT and the DU of the relay node.
[0089] In the seventh aspect, an embodiment of the present application provides another communication method, which includes: generating eleventh information, wherein the eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the F1 interface (not completed establishment) between the DU of the relay node and the third CU to the third CU, and there is an RRC connection between the second CU and the MT, and the third CU is the target host CU of the DU of the relay node; sending the eleventh information to the second CU.
[0090] In the embodiment of the present application, the eleventh information is sent to the second CU so that the second CU sends downlink configuration information for transmission of the F1 interface (not yet established) between the DU of the relay node and the third CU to the third CU.
[0091] In a possible implementation, the sending the eleventh information to the second CU includes: the MT sending the eleventh information to the second CU, where the eleventh information includes identification information of the third CU and identification information of the DU of the relay node.
[0092] In one possible implementation, the sending of the eleventh information to the second CU includes: the source host CU of the DU of the relay node sends the eleventh information to the second CU, and the eleventh information includes the identification information of the third CU, the identification information of the DU of the relay node, and the identification information identifying the MT in the second CU.
[0093] In a possible implementation manner, the method further includes: receiving seventh information from the relay node, where the seventh information includes identification information of the DU of the relay node.
[0094] In a possible implementation, the method further includes: receiving twelfth information from the relay node, where the twelfth information is used to trigger the source host CU (ie, the first CU) of the DU of the relay node to send the eleventh information to the second CU.
[0095] In a possible implementation, the eleventh information is also used to indicate to the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being executed, or the relay node and the third CU are about to establish an F1 interface).
[0096] In a possible implementation, the eleventh information is further used to instruct the second CU to trigger the third CU to initiate cross-topology traffic migration.
[0097] In eighth aspect, an embodiment of the present application provides another communication method, which includes: generating first information; sending the first information to a third CU, wherein the first information is used to indicate the binding relationship between the DU of the relay node and the MT of the relay node, the third CU is the target host CU of the DU of the relay node, and there is an RRC connection between the MT and the second CU, and the second CU is different from the third CU.
[0098] In the embodiment of the present application, the first information is sent to the third CU so that the third CU can learn the binding relationship between the DU and the MT of the relay node.
[0099] In a possible implementation manner, the first information includes identification information of the DU of the relay node and identification information identifying the MT in the second CU.
[0100] In a possible implementation, the method further includes: receiving request information, where the request information is used to request a binding relationship between the MT and the DU of the relay node, and the request information includes identification information identifying the MT in the second CU.
[0101] In the ninth aspect, an embodiment of the present application provides another communication method, which includes: receiving first information, where the first information is used to indicate the binding relationship between the DU of the relay node and the MT of the relay node, the third CU is the target host CU of the DU of the relay node, and there is an RRC connection between the MT and the second CU, and the second CU is different from the third CU; based on the first information, determining the binding relationship between the DU and the MT of the relay node.
[0102] In the embodiment of the present application, the binding relationship between the DU and the MT of the relay node can be determined according to the first information.
[0103] In a possible implementation manner, the first information includes identification information of the DU of the relay node and identification information identifying the MT in the second CU.
[0104] In a possible implementation, the method further includes: sending request information, where the request information is used to request a binding relationship between the MT and the DU of the relay node, and the request information includes identification information identifying the MT in the second CU.
[0105] In the tenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the first aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the processing unit is used to generate first information, and the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, and the second CU has an RRC connection with the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; the transceiver unit is used to send the first information to the third CU.
[0106] In a possible implementation, the transceiver unit is further configured to receive second information from the relay node, where the second information includes identification information of the DU of the relay node.
[0107] In a possible implementation, the processing unit is further used to select the third CU as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU.
[0108] In one possible implementation, the processing unit is specifically used to select the third CU that has an IP connection with the second CU as the target host CU of the DU of the relay node based on the network segment to which the IP address belongs; or, select the third CU in the preconfigured target list as the target host CU of the DU of the relay node, where there is an IP connection, an Xn interface, or the ability to establish an Xn interface between the CU in the target list and the second CU.
[0109] In one possible implementation, the transceiver unit is further used to receive first reference information from the second CU through the XN interface, where the first reference information is used to indicate that an IP connection exists between the second CU and the third CU, an Xn interface exists, or an Xn interface can be established; the processing unit is further used to determine, based on the first reference information, that an IP connection exists between the second CU and the third CU, an Xn interface exists, or an Xn interface can be established.
[0110] In one possible implementation, the transceiver unit is further used to receive second reference information from the third CU through the XN interface, where the second reference information is used to indicate that an IP connection exists between the second CU and the third CU, an Xn interface exists, or an Xn interface can be established; the processing unit is further used to determine, based on the second reference information, that an IP connection exists between the second CU and the third CU, an Xn interface exists, or an Xn interface can be established.
[0111] Possible implementations of the communication method of the tenth aspect can refer to the various possible implementations of the first aspect.
[0112] For the technical effects brought about by various possible implementation methods of the tenth aspect, reference may be made to the introduction to the technical effects of the first aspect or various possible implementation methods of the first aspect.
[0113] In the eleventh aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the second aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the transceiver unit is used to receive first information, and the first information is used to instruct the third CU to request downlink configuration information for F1 interface transmission from the second CU, and the second CU has an RRC connection with the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; send third information to the second CU, and the third information is used to request downlink configuration information for F1 interface transmission.
[0114] In one possible implementation, the first information includes identification information identifying the MT in the second CU; the processing unit is further used to send information for obtaining the binding relationship between the DU of the relay node and the MT to the second CU based on the identification information identifying the MT in the second CU.
[0115] In a possible implementation, the transceiver unit is further configured to send fourth information to the second CU, where the fourth information includes a correspondence between an IP address used for F1 interface transmission and a DSCP or flow label used for F1 interface transmission.
[0116] In one possible implementation, the transceiver unit is further used to receive sixth information from the second CU, where the sixth information includes downlink configuration information for F1 interface transmission and identification information for identifying the MT in the second CU, such as the UE XnAP ID of the MT under the second CU.
[0117] Possible implementations of the communication method of the eleventh aspect may refer to various possible implementations of the second aspect.
[0118] For the technical effects brought about by various possible implementation methods of the eleventh aspect, reference may be made to the introduction to the technical effects of the second aspect or various possible implementation methods of the second aspect.
[0119] In a twelfth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the third aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the transceiver unit is used to receive fifth information, the fifth information is used to instruct the second CU to send first information to the third CU, the first information is used to instruct the third CU to request downlink configuration information for F1 interface transmission from the second CU, the second CU has an RRC connection with the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; and the first information is sent to the third CU.
[0120] In a possible implementation, the transceiver unit is further used to receive ninth information, where the ninth information is used to indicate that the DU migration of the relay node has been completed (or the F1 interface between the DU of the relay node and the third CU has been established).
[0121] Possible implementations of the communication method of the twelfth aspect can refer to the various possible implementations of the third aspect.
[0122] For the technical effects brought about by various possible implementation methods of the twelfth aspect, reference may be made to the introduction to the technical effects of the third aspect or various possible implementation methods of the third aspect.
[0123] In a thirteenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the fourth aspect above. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the processing unit is used to generate fifth information, and the fifth information is used to instruct (or trigger) the second CU to send first information to the third CU, and the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission. There is an RRC connection between the second CU and the MT of the relay node, or the second CU is the target CU to which the MT is about to switch, and the third CU is the target host CU of the DU of the relay node; the transceiver unit is used to send the fifth information to the second CU.
[0124] In a possible implementation, the transceiver unit is further configured to receive seventh information of the DU from the relay node, where the seventh information includes identification information of the DU of the relay node.
[0125] In a possible implementation, the processing unit is further used to select the third CU as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU.
[0126] In one possible implementation, the processing unit is specifically used to select the third CU that has an IP connection with the second CU as the target host CU of the DU of the relay node based on the network segment to which the IP address belongs; or, select the third CU in the preconfigured target list as the target host CU of the DU of the relay node, where there is an IP connection, an Xn interface, or the ability to establish an Xn interface between the CU in the target list and the second CU.
[0127] In a possible implementation, the transceiver unit is further configured to receive eighth information of the DU from the relay node, where the eighth information is used to trigger the first CU to send the fifth information to the second CU.
[0128] Possible implementations of the communication method of the thirteenth aspect can refer to the various possible implementations of the fourth aspect.
[0129] For the technical effects brought about by various possible implementation methods of the thirteenth aspect, reference may be made to the introduction to the technical effects of the fourth aspect or various possible implementation methods of the fourth aspect.
[0130] In a fourteenth aspect, an embodiment of the present application provides a communication device having the function of implementing the behavior in the embodiment of the method of the fifth aspect. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the processing unit is used to generate tenth information, the tenth information including at least one of the identification information of the second CU, the identification information of the DU of the relay node, the identification information of the MT identifying the relay node in the second CU, and the downlink configuration information for the transmission of the F1 interface (not completed) between the DU of the relay node and the third CU, the second CU has an RRC connection with the MT, and the third CU is the target host CU of the DU of the relay node; the transceiver unit is used to send the tenth information to the third CU, and the tenth information is used for the third CU to establish the F1 interface with the DU of the relay node.
[0131] In one possible implementation, the transceiver unit is further used to receive eleventh information, and the eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the F1 interface (not completed) between the DU of the relay node and the third CU to the third CU.
[0132] In a possible implementation, the transceiver unit is further used to receive ninth information, where the ninth information is used to indicate that the DU migration of the relay node has been completed (or the F1 interface between the DU of the relay node and the third CU has been established).
[0133] For possible implementations of the communication method of the fourteenth aspect, reference can be made to various possible implementations of the fifth aspect.
[0134] For the technical effects brought about by various possible implementation methods of the fourteenth aspect, reference may be made to the introduction to the technical effects of the fifth aspect or various possible implementation methods of the fifth aspect.
[0135] In a fifteenth aspect, an embodiment of the present application provides a communication device having the function of implementing the behavior in the embodiment of the method in the sixth aspect. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the transceiver unit is used to receive tenth information, the tenth information including identification information of the second CU, identification information of the DU of the relay node, identification information of the MT identifying the relay node in the second CU, and downlink configuration information for transmission of the F1 interface (not completed) between the DU of the relay node and the third CU, the second CU and the MT have an RRC connection, and the third CU is the target host CU of the DU of the relay node; the processing unit is used to establish the F1 interface between the third CU and the DU of the relay node based on the tenth information.
[0136] For possible implementations of the communication method of the fifteenth aspect, reference may be made to various possible implementations of the sixth aspect.
[0137] For the technical effects brought about by various possible implementation methods of the fifteenth aspect, reference may be made to the introduction to the technical effects of the sixth aspect or various possible implementation methods of the sixth aspect.
[0138] In a sixteenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the seventh aspect. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the processing unit is used to generate eleventh information, and the eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the F1 interface (not completed) between the DU of the relay node and the third CU to the third CU, the second CU has an RRC connection with the MT, and the third CU is the target host CU of the DU of the relay node; the transceiver unit is used to send the eleventh information to the second CU.
[0139] In a possible implementation, the transceiver unit is further configured to receive seventh information from the relay node, where the seventh information includes identification information of the DU of the relay node.
[0140] In a possible implementation, the transceiver unit is further used to receive twelfth information from the relay node, and the twelfth information is used to trigger the source host CU (i.e., the first CU) of the DU of the relay node to send the eleventh information to the second CU.
[0141] For possible implementations of the communication method of the sixteenth aspect, reference may be made to various possible implementations of the seventh aspect.
[0142] For the technical effects brought about by various possible implementation methods of the sixteenth aspect, reference may be made to the introduction to the technical effects of the seventh aspect or various possible implementation methods of the seventh aspect.
[0143] In the seventeenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method in the eighth aspect. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the processing unit is used to generate first information; the transceiver unit is used to send the first information to the third CU, and the first information is used to indicate the binding relationship between the DU of the relay node and the MT of the relay node, the third CU is the target host CU of the DU of the relay node, the MT has an RRC connection with the second CU, and the second CU is different from the third CU.
[0144] In a possible implementation, the transceiver unit is further configured to receive request information, where the request information is used to request a binding relationship between the MT and the DU of the relay node, and the request information includes identification information identifying the MT in the second CU.
[0145] For possible implementations of the communication method of the seventeenth aspect, reference may be made to various possible implementations of the eighth aspect.
[0146] For the technical effects brought about by various possible implementation methods of the seventeenth aspect, reference may be made to the introduction to the technical effects of the eighth aspect or various possible implementation methods of the eighth aspect.
[0147] In an eighteenth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the behavior in the embodiment of the method of the ninth aspect. The communication device can be a communication device, or a component of a communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can implement all or part of the functions of the communication device. The functions of the communication device can be implemented by hardware, or can be implemented by hardware executing corresponding software, and the hardware or software includes one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein: the transceiver unit is used to receive first information, and the first information is used to indicate the binding relationship between the DU of the relay node and the MT of the relay node, the third CU is the target host CU of the DU of the relay node, the MT has an RRC connection with the second CU, and the second CU is different from the third CU; the processing unit is used to determine the binding relationship between the DU of the relay node and the MT based on the first information.
[0148] In a possible implementation, the transceiver unit is further configured to send request information, where the request information is used to request a binding relationship between the MT and the DU of the relay node, and the request information includes identification information identifying the MT in the second CU.
[0149] For possible implementations of the communication method of the eighteenth aspect, reference may be made to various possible implementations of the ninth aspect.
[0150] For the technical effects brought about by various possible implementation methods of the eighteenth aspect, reference may be made to the introduction to the technical effects of the ninth aspect or various possible implementation methods of the ninth aspect.
[0151] In the nineteenth aspect, an embodiment of the present application provides another communication device, which includes a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the communication device executes the method shown in any one of the above-mentioned first to ninth aspects.
[0152] In the embodiment of the present application, during the execution of the above method, the process of sending information (or signals) in the above method can be understood as the process of outputting information based on the instructions of the processor. When outputting information, the processor outputs the information to the transceiver so that it can be transmitted by the transceiver. After being output by the processor, the information may also need to undergo other processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before being input into the processor.
[0153] For operations such as sending and / or receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual functions or internal logic in the relevant descriptions, they can be generally understood as instructions output based on the processor.
[0154] During implementation, the processor may be a processor specifically configured to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. For example, the processor may also be configured to execute a program stored in a memory. When the program is executed, the communication device performs the method described in the first aspect or any possible implementation of the first aspect.
[0155] In a possible implementation, the memory is located outside the communication device. In a possible implementation, the memory is located inside the communication device.
[0156] In a possible implementation, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
[0157] In a possible implementation, the communication device further includes a transceiver, and the transceiver is configured to receive signals or send signals.
[0158] In the twentieth aspect, the present application provides another communication device, which includes a processing circuit and an interface circuit, wherein the interface circuit is used to obtain data or output data; the processing circuit is used to execute the method shown in any one of the above-mentioned first to ninth aspects.
[0159] In the twenty-first aspect, the present application provides a computer-readable storage medium, which stores a computer program, and the computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of the above-mentioned aspects from the first aspect to the ninth aspect.
[0160] In aspect 22, the present application provides a computer program product, which includes a computer program, and the computer program includes program instructions, which, when executed, enable the computer to execute the method shown in any one of aspects 1 to 9 above.
[0161] In aspect 23, the present application provides a communication system, comprising the communication device described in the above-mentioned aspect 10 or any possible implementation of the aspect 10, and the communication device described in the above-mentioned aspect 11 or any possible implementation of the aspect 11.
[0162] In aspect 24, the present application provides a communication system, comprising the communication device described in the above-mentioned aspect 11 or any possible implementation of the aspect 11, the communication device described in the above-mentioned aspect 12 or any possible implementation of the aspect 12, and the communication device described in the above-mentioned aspect 13 or any possible implementation of the aspect 13.
[0163] In aspect 25, the present application provides a communication system, comprising the communication device described in aspect 14 or any possible implementation of aspect 14, the communication device described in aspect 15 or any possible implementation of aspect 15, and the communication device described in aspect 16 or any possible implementation of aspect 16.
[0164] In aspect 26, the present application provides a communication system, comprising the communication device described in aspect 17 or any possible implementation of aspect 17, and the communication device described in aspect 18 or any possible implementation of aspect 18.
[0165] In aspect 27, the present application provides a chip comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method as shown in any one of aspects 1 to 9 above. BRIEF DESCRIPTION OF THE DRAWINGS
[0166] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.
[0167] FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;
[0168] FIG2 shows an example of an IAB network including multiple UEs and multiple IAB nodes;
[0169] FIG3 is a schematic diagram of an IAB network architecture;
[0170] Figure 4 is a schematic diagram of a partial migration;
[0171] Figure 5 is a schematic diagram of a full migration;
[0172] Figure 6 shows an example of a continuous partial migration (without DU migration) scenario;
[0173] FIG7 is an example of a scenario of migrating DUs in a continuous partial migration according to an embodiment of the present application;
[0174] FIG8 is an example of a scenario in which DUs are migrated but MTs are not migrated, as provided in an embodiment of the present application;
[0175] FIG9 is an interactive flow chart of a communication method provided in an embodiment of the present application;
[0176] FIG10 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0177] FIG11 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0178] FIG12 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0179] FIG13 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0180] FIG14 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0181] FIG15 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0182] FIG16 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0183] FIG17A is another example of a scenario in which DUs migrate but MTs do not migrate, provided by an embodiment of the present application;
[0184] FIG17B is another example of a scenario in which DUs migrate but MTs do not migrate, provided by an embodiment of the present application;
[0185] FIG18 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0186] FIG19 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0187] FIG20 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0188] FIG21 is an interactive flow chart of another communication method provided in an embodiment of the present application;
[0189] FIG22 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application;
[0190] FIG23 is a schematic diagram of the structure of a network device 2300 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0191] The terms "first" and "second" in the specification, claims and drawings of the present application are only used to distinguish different objects, rather than to describe a specific order. It will be understood that the various digital numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and inherent logic. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.
[0192] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0193] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification of the present application and the appended claims, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include plural expressions, unless there is a clear contrary indication in the context. It should also be understood that the term "and / or" used in the present application refers to and includes any or all possible combinations of one or more listed items. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The term "multiple" used in the present application refers to two or more. In the textual description of the present application, the character " / " generally indicates that the objects associated before and after are in an "or" relationship. The term "at least one" used in the present application refers to one or more.
[0194] It is understood that in each embodiment of the present application, "A corresponds to B" means that there is a corresponding relationship between A and B, and B can be determined according to A. However, it should also be understood that determining (or generating) B according to (or based on) A does not mean that B is determined (or generated) only according to (or based on) A, and B can also be determined (or generated) according to (or based on) A and / or other information.
[0195] Figure 1 is a schematic diagram of the architecture of the communication system used in the embodiment of the present application. As shown in Figure 1, the communication system includes a core network device 110, a wireless access network device 120, a wireless backhaul device 130 and at least one terminal device (terminal device 140 and terminal device 150 are exemplarily described in Figure 1). The terminal device is connected to the wireless backhaul device wirelessly, and is connected to the wireless access network device through one or more wireless backhaul devices. In addition, some terminal devices can also be directly connected to the wireless access network device wirelessly). The wireless access network device is connected to the core network device wirelessly or wired. The core network device and the wireless access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the wireless access network device can be integrated into the same physical device, or the functions of some core network devices and some wireless access network devices can be integrated into one physical device. This application does not limit this. The terminal device can be fixed or movable. It should be understood that the mobile communication system shown in Figure 1 is merely a schematic diagram, and the communication system may also include other network devices, such as wireless relay devices or wireless backhaul devices, which are not shown in Figure 1. The embodiments of the present application do not limit the number of core network devices, wireless access network devices, wireless backhaul devices, and terminal devices included in the mobile communication system.
[0196] Among them, the wireless access network device is the access device that the terminal device uses to access the mobile communication system via wireless means. It can be a base station NodeB, an evolved base station eNodeB, a base station in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The embodiments of this application do not limit the specific technology and specific device form used by the wireless access network device. The terminal device may also be referred to as a terminal, UE, mobile station (MS), MT, etc.
[0197] The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a machine type communication (MTC) terminal, a wearable device, a vehicle-mounted terminal device, a drone, etc.
[0198] Among them, the wireless backhaul device can provide backhaul services for its child nodes. Specifically, it can be a relay node in the long term evolution (LTE) system, an IAB node in the 5G system, or other devices that can provide wireless relay functions. Wireless access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of wireless access network equipment and terminal equipment.
[0199] The wireless access network device and the terminal device, as well as the terminal device and the terminal device, can communicate through the licensed spectrum (licensed spectrum), can also communicate through the unlicensed spectrum (unlicensed spectrum), or can also communicate through the licensed spectrum and the unlicensed spectrum at the same time. The wireless access network device and the terminal device, as well as the terminal device and the terminal device, can communicate through the spectrum below 6 gigahertz (GHz), can also communicate through the spectrum above 6 GHz, and can also communicate using the spectrum below 6 GHz and the spectrum above 6 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between the wireless access network device and the terminal device.
[0200] The above-mentioned network elements can be network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on appropriate platforms. In addition, the embodiments of the present application can also be applied to other future-oriented communication technologies. The network architecture and service scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. It is known to those skilled in the art that with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in this application are also applicable to similar technical problems.
[0201] To facilitate understanding of the embodiments of the present application, the following is a brief description of the terms and technical features involved in the embodiments of the present application.
[0202] 1) IAB Network: Given the limited coverage of high-frequency bands, ensuring network coverage in remote areas is challenging and costly due to the difficulty of deploying fiber. This necessitates the design of flexible and convenient access and backhaul solutions. IAB technology emerged as a response to this challenge. Its access and backhaul links utilize wireless transmission, eliminating or reducing fiber deployment and lowering equipment costs.
[0203] In an IAB network, a relay node, also known as an IAB node (IAB-node), can provide wireless access services for UEs. The UE's service data is transmitted from the IAB-node to the IAB donor node (IAB-donor) via a wireless backhaul link. An IAB node can be referred to as a mIAB (mobile IAB) node. Hereinafter, mIAB refers to the mIAB node, mIAB-MT refers to the MT of the IAB node, and mIAB-DU refers to the DU of the IAB node. MT is the abbreviation for the MT of the IAB node, and DU is the abbreviation for the DU of the IAB node. An IAB node can establish a wireless backhaul link with one or more upper-level nodes and access the core network through the upper-level nodes. The upper-level node can control the relay node to certain extent (e.g., data scheduling, timing modulation, power control, etc.) through various signaling methods. In addition, the relay node can establish access links with one or more lower-level nodes and provide access services to one or more lower-level nodes. The upper-level node of a relay node can be a base station or another relay node. The lower-level node of a relay node can be a terminal or another relay node. In some cases, the upper-level node of an IAB node may also be referred to as its upstream node or parent node, and the lower-level node of the IAB node may also be referred to as its downstream node or child node.
[0204] Multi-hop networking may be used in the IAB network. Taking into account the need for service transmission reliability, the IAB node can support dual connectivity (DC) or multi-connectivity to cope with abnormal situations that may occur in the backhaul link (for example, interruption or blockage of the wireless link and load fluctuations, etc.) to improve the reliability of transmission. Therefore, the IAB network can support multi-hop and multi-connection networking, and there may be multiple routing paths between the terminal device and the host base station. Among them, on one path, there is a definite hierarchical relationship between the IAB nodes, and between the IAB nodes and the host base station serving the IAB nodes. Each IAB node regards the node that provides backhaul services to it as a parent node, and accordingly, each IAB node can be regarded as a child node of its parent node.
[0205] An IAB donor node (IAB-donor) can be an access network element with complete base station functionality, such as a donor base station (DgNB), or an access network element with a separate centralized unit (CU) and DU. The IAB donor node is connected to the core network element serving the terminal device (e.g., the 5G core network) and provides wireless backhaul functionality for the IAB node. For ease of presentation, the centralized unit of the IAB donor node is referred to as the donor CU or IAB-donor CU, and the distributed unit of the IAB donor node is referred to as the donor DU or IAB-donor DU. The donor CU may also be in a form with a separate control plane (CP) and user plane (UP). For example, the CU may consist of a CU-CP and one (or more) CU-UPs.
[0206] In the IAB network, one or more IAB-nodes may be included on a transmission path between the UE and the IAB-donor. Each IAB-node needs to maintain a wireless backhaul link to the parent node, and also needs to maintain a wireless link with the child node. If the child node of the IAB-node is a terminal device, there is a wireless access link between the IAB-node and the child node (i.e., the terminal device). If the child node of the IAB-node is another IAB-node, there is a wireless backhaul link between the IAB-node and the child node (i.e., the other IAB-node). Figure 2 shows an example of an IAB network including multiple UEs and multiple IAB nodes. Figure 2 takes an example including 2 UEs and 5 IAB nodes. Among them, the two UEs are UE1 and UE2, and the five IAB nodes are IAB node 1 to IAB node 5. It should be understood that the thick line in Figure 2 indicates the access link and the thin line indicates the backhaul link. Referring to Figure 2 , in the path "UE1 → IAB-node4 → IAB-node3 → IAB-node1 → IAB-donor," UE1 accesses IAB-node4 via a wireless access link, IAB-node4 connects to IAB-node3 via a wireless backhaul link, IAB-node3 connects to IAB-node1 via a wireless backhaul link, and IAB-node1 connects to the IAB-donor via a wireless backhaul link. It should be understood that the IAB networking scenario shown in Figure 2 is merely exemplary. There are many other possibilities in an IAB network that supports multi-hop and multi-connection networking, which are not listed here.
[0207] The IAB-node-DU (hereinafter simply referred to as mIAB-DU) is logically connected to the IAB-donor CU (hereinafter simply referred to as CU) through the F1 interface. Figure 3 is a schematic diagram of an IAB network architecture. The F1 connection in Figure 3 is not a physical direct connection, but a logical connection. In fact, the F1 connection between the mIAB-DU and the CU is physically realized through the NR Uu interface between the IAB-node MT and the parent node DU of each hop, but because the mIAB-DU can eventually communicate with the CU, it can be considered that there is a logical F1 interface. The F1 interface can also be called the F1* interface, and the embodiment of the present application does not limit the name of the interface. And in this article, the interface is called the F1 interface as an example. The IAB-donor CU is connected to the 5G core network (5G core network, 5GC / 5GCN) through the NG interface. There is an Xn-C interface between the IAB-donor CU and the gNodeB.
[0208] 2) Partial migration and full migration
[0209] In 3GPP Release 17 (Release-17), IAB node inter-CU migration is categorized into two implementation methods: full migration and partial migration. Full migration includes three implementation methods: gradual top-down, gradual bottom-up, and fully nested. In partial migration, the IAB node's transport unit switches across CUs, but the IAB node's data unit (DU) maintains an F1 connection with the source CU. In full migration, the IAB node's DU establishes an F1 connection with the candidate target CU. Rel-17 primarily targets IAB node migration for load balancing, so partial migration can be used. This method involves switching the transport unit (MT) to a different F1 interface transmission path, but does not change the F1 interface anchor point. Rel-18, on the other hand, primarily targets migration due to IAB node mobility. When an IAB node moves over a large area, maintaining an F1 connection with the source CU is inappropriate, and the F1 connection anchor point must be changed to the candidate target CU. Therefore, full migration is a mandatory feature of Rel-18 mobile IAB. The following briefly introduces the current status of the discussion on partial migration and full migration.
[0210] The IAB node that undergoes migration is called a boundary node. Figure 4 is a schematic diagram of a partial migration. Referring to Figure 4, IAB-node2 is a boundary node. Before IAB-node2 performs partial migration, there is an RRC connection between IAB-MT2 and CU1, and an F1 interface between IAB-DU2 and CU1. IAB-node2 communicates with IAB-donor through the source path (through IAB-node1 composed of IAB-MT1 and IAB-DU1), see the solid line with the arrow. During the partial migration of IAB-node2, IAB-MT2 undergoes cross-CU cell switching and establishes an RRC connection with CU2. However, in order to avoid or reduce the re-establishment process of introducing the F1 interface, IAB-DU2 still maintains the F1 interface with CU1 and does not establish an F1 interface with CU2. Therefore, the communication path between CU1 and IAB-DU2 becomes cross-topology: See the dashed arrow line. In Figure 4, CU1 and CU2 are referred to as the F1-terminating CU and non-F1-terminating CU, respectively. Note that data transmitted on this path does not pass through CU2; CU1 and Donor-DU2 communicate directly over the IP network. In partial migration, the core interaction signaling is the XN message between CU1 and CU2: the IAB TRANSPORT MANAGEMENT REQUEST / RESPONSE message. See TS 38.423 V17.2.0 Section 9.4.2 and Section 9.4.3. CU1 requests CU2 to help it establish cross-topology traffic transmission through the IAB TRANSPORT MANAGEMENT REQUEST message, which carries the traffic's IP address and quality of service (QoS) information. After CU2 establishes cross-topology traffic transmission, it returns the border node's mobile equipment's backhaul information (the topology within the dashed box below CU2) to CU1 through the IAB TRANSPORT MANAGEMENT RESPONSE message. Based on the border node's mobile equipment's backhaul information, CU1 configures cross-topology BAP rules for the border node through the F1AP. IAB TRANSPORT MANAGEMENT REQUEST / RESPONSE are UE-associated XN messages associated with the border node's mobile equipment. Therefore, both messages need to carry the border node's mobile equipment's UE XnAP ID under CU1 and the UE XnAP ID under CU2 to identify the MT.
[0211] Figure 5 is a schematic diagram of a full migration. Referring to Figure 5, IAB-node3 is a boundary node. In full migration, the F1 interface between IAB-DU3 and CU1 needs to be migrated to CU2. Since the protocol does not support the simultaneous existence of F1 interfaces between a DU and two CUs, the existing implementation scheme expands IAB-DU3 into two logical DUs, namely IAB-DU3a (which can be abbreviated as DU3a) and IAB-DU3b (i.e., the new logical DU). IAB-DU3a always maintains the F1 interface with CU1, while IAB-DU3b (which can be abbreviated as DU3b) is used to establish a new F1 interface with CU2. DU3a and DU3b can be regarded as two DUs, each with an F1 interface. The UE needs to make a switch from the cell under IAB-DU3a to the cell under IAB-DU3b. Among the three full migration implementation methods:
[0212] The first few steps of gradual top-down are similar to partial migration. First, according to the partial migration process, IAB-MT3 (abbreviated as MT3) is switched to establish the cross-topology F1-C and F1-U between DU3a and CU1. When CU2 helps to establish the cross-topology F1-C and F1-U between DU3a and CU1, it also establishes F1-C and F1-U between DU3b and CU2. Then, the UE is switched to DU3b. The UE can communicate directly with CU2 on the target path. The target path is
[0213] In the gradual bottom-up, first, by establishing the cross-topology F1-C and F1-U between DU3b and CU2, the UE can be switched to DU3b, and the control plane and user plane data transmission between DU3b and CU2 through topology 1 is established. After all UEs are successfully switched, a switching command is sent to MT3 or the switching command of MT3 is effective, and then F1-C / U is established on the target path, so that the UE traffic can be migrated to the target path. Topology 1 refers to Establishing control plane and user plane data transmission between DU3b and CU2 through topology 1 requires establishing backhaul link resources (BH RLC CH) on DU3b and donor-DU1, as well as on the intermediate hop nodes between the two (if any), and configuring the BAP layer so that corresponding resources are available on these relevant nodes for transmitting control plane and user plane data, and the BAP layer of each relevant node knows how to map data packets to resources.
[0214] The full nesting scenario is similar to the gradual bottom-up scenario. First, a cross-topology F1-C is established between DU3b and CU2. (Only the cross-topology F1-C is established to allow CU2 to switch the UE to DU3b when making a handover decision. However, the cross-topology F1-U is not established, and cross-topology data transmission is not performed.) This allows the UE to be allowed to switch to DU3b. After sending a handover command to all UEs, a handover command is immediately sent to MT3 or the handover command of MT3 is taken effect. Then, F1-C / U is directly established on the target path to enable the UE traffic to be migrated to the target path.
[0215] 3) DU migration in continuous partial migration
[0216] The essential difference between full migration and partial migration lies in whether a DU migration is required. (Actually, a new logical DU is generated and then an F1 interface is established with the target CU. However, from a macro perspective of the IAB node, this can often be referred to as "DU migration"). The Rel-18 mobile IAB project document lists full migration as a mandatory feature. However, this does not mean that a full migration is required for every IAB node migration. During discussions at previous Rel-18 meetings, the mainstream view was to use continuous partial migration as the baseline, performing DU migration only when necessary. Figure 6 illustrates an example of a continuous partial migration scenario (without DU migration). As shown in Figure 6, the mIAB (mobile IAB)-MT switches from the CU1 topology to the CU2 topology, and then from CU2 to the CU3 topology. The mIAB-DU maintains an F1 connection with CU1. According to the conclusions of the RAN3#117b e-meeting, the CU (i.e., CU1) serving as the F1 anchor point for the mIAB-DU determines whether a DU migration is required. Figure 7 is an example of a scenario of migrating DUs in a continuous partial migration provided in an embodiment of the present application. Figure 7 shows a situation where CU1 decides to perform DU migration when the mAB-MT migrates from the topology under CU2 to the topology under CU3. Similar to full migration, the mAB-node needs to generate a new logical DU (mIAB-DU2), establish an F1 interface with CU3, and then switch the UE from the cell under mAB-DU1 to the cell under mAB-DU2. In Figures 6 and 7, the mAB-MT is directly connected to the donor-DU, but this is only for illustration. The mAB-MT can also be connected to other fixed mAB-DUs and reach the donor-DU through multiple hops. This is not limited in the embodiments of the present application.
[0217] In the RAN3 meeting, many companies believed that the migration of mAB-MT (which can be referred to as MT) and mAB-DU (which can be referred to as DU) can be decoupled. Figure 8 is an example of a scenario in which DU migrates and MT does not migrate, provided in an embodiment of the present application. In Figure 8, DU2 represents a new logical DU generated by the mAB node, DU2 establishes an F1 interface with CU3 (that is, the DU of the mAB node migrates to CU3), and MT has an RRC connection with CU2. As shown in Figure 8, the DU of the mAB node migrates to CU3, the mAB-MT does not migrate, and the migration of DU does not depend on the migration of MT. The scenario in which MT migrates but DU does not migrate is partial migration. There is a lack of in-depth discussion in the standard about the scenario in which DU migrates but MT does not migrate. The reasons given by companies that support DU migration without relying on MT migration are mainly: due to mobility, MT may frequently change CUs (such as the CU of a pico-cell), while the anchor CU of DU should not be changed frequently. It is more inclined to access a CU with a larger control range rather than following the MT to select a CU of a small station. Therefore, DU migration can be decoupled from mobile equipment. For example, CU1 and CU3 are CUs of a macro base station, and CU2 is a CU of a small base station located at the intersection of the control ranges of CU1 and CU3. The mAB is moving from the control range of CU1 to the control range of CU3. When the mobile equipment is in CU2, CU1 considers that the DU needs to be migrated to CU3 first to prevent the mobile equipment from moving too far away from CU1 after further migration, which would increase transmission latency.
[0218] 4) Downlink configuration information for F1 interface transmission
[0219] The downlink configuration information used for F1 interface transmission may include: the DSCP / flow label required for the CU to transmit the downlink F1 interface message (F1 interface message from the CU to the DU). When the CU transmits the downlink F1 interface message, the CU needs to know what kind of DSCP / flow label to insert into the F1 interface message to ensure the quality of service (QoS) of the F1 interface message transmission. After receiving the F1 SETUP REQUEST message, the CU returns an F1 SETUP RESPONSE message to the mIAB-DU and inserts the DSCP / flow label into the IP header of the F1 SETUP RESPONSE message. And, in each subsequent F1 interface message interaction process, in the downlink direction, the CU will insert the DSCP / flow label into the IP header of the F1 interface message.
[0220] After a handshake of F1 SETUP REQUEST and F1 SETUP RESPONSE between the mAB-DU and the CU, the F1 interface is established and the CU can send F1 control messages to the mAB-DU. In the future, the CU can send more BAP configuration information to the mAB-DU through the F1 control message, instructing the IAB node to establish more backhaul links and backhaul radio link control channel (RLC channel) resources (initially there is only one default one, used to transmit the first F1 SETUP REQUEST), which will be used to transmit more other F1-C messages and F1-U user plane data.
[0221] Currently, we only consider the technical details for scenarios where the MT also migrates before or after the DU migration, and both the DU and the MT migrate to the same target CU. In this scenario, the downlink configuration information (such as DSCP / flow label) required for downlink F1 interface message transmission is allocated by the target CU.
[0222] Currently, the industry is studying solutions for DU migration but not MT migration, that is, solutions in which the target host CU of DU is different from the target host CU of MT. When DU migrates but MT does not migrate, as shown in the scenario of Figure 8, since the new F1 connection between mAB-DU2 and CU3 needs to pass through the topology under CU2, the downlink configuration information required for the downlink F1 interface message transmission should all be allocated by CU2. However, the existing DU migration solution does not take into account how CU3, which is the target host CU (also called the target F1 anchor CU, i.e., target F1-terminating CU), can obtain the downlink configuration information allocated by CU2 when MT does not migrate. Therefore, it is necessary to study how the target host CU of DU obtains the downlink configuration information for target F1 interface transmission when DU migrates but MT does not migrate.
[0223] The communication solution provided in the embodiment of the present application can solve the problem of how the target host CU of the DU obtains the downlink configuration information for transmission on the target F1 interface (i.e., the F1 interface between the target host CU and the DU) when the DU migrates but the MT does not. The communication solution provided in the embodiment of the present application is applicable to scenarios where the DU migrates but the MT does not migrate, as well as scenarios where the DU and MT migrate to different target CUs, such as the scenario shown in Figure 8.
[0224] The communication solution provided by the embodiments of the present application is described below with reference to the accompanying drawings.
[0225] FIG9 is an interactive flow chart of a communication method provided by an embodiment of the present application. As shown in FIG9 , the method includes:
[0226] 901. A first CU generates first information.
[0227] The above-mentioned first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission. Optionally, the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission between the above-mentioned third CU and the DU of the above-mentioned relay node to be established. The downlink configuration information for F1 interface transmission includes DSCP and / or flow label for F1 interface transmission. In this application, there is an RRC connection between the second CU and the MT of the relay node. Alternatively, the second CU is the target CU to which the MT is about to switch. The third CU is the target host CU of the DU of the relay node; the first CU is the source host CU of the DU of the relay node. In other words, there is an F1 interface between the DU of the relay node and the first CU.
[0228] In one possible implementation, the first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the mobile terminal in the second CU. The identification information of the second CU may include the gNB ID and IP address of the second CU. The identification information of the DU of the relay node may include at least one of the following: the gNB-DU ID and / or IP address of the DU of the relay node. The identification information identifying the mobile terminal in the second CU may include the UE XnAP ID of the mobile terminal under the second CU. The DU of the relay node may be a new logical DU generated by the relay node, i.e., a logical DU generated for DU migration. The first information may also include the UE XnAP ID of the mobile terminal under the first CU. In this implementation, the first information is sent to the third CU so that the third CU requests downlink configuration information for F1 interface transmission from the second CU based on the first information.
[0229] 902. The first CU sends first information to the third CU.
[0230] Correspondingly, the third CU receives the first information from the first CU. The first information may be carried in a new message, such as an IAB Transport Migration Procedure Request message. The name of the message carrying the first information is not limited.
[0231] In one possible implementation, the first information is further used to indicate a binding relationship between the MT (using the UE XnAP ID of the MT under the second CU) and the DU of the relay node (using the gNB-DU ID of the DU). In this implementation, the first information may also enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0232] In one possible implementation, the first information is used to instruct the third CU to send a cross-topology traffic migration request to the second CU (for example, sending an IAB Transport Migration Management Request message to the second CU) to request the second CU for downlink configuration information for F1 interface transmission.
[0233] In one possible implementation, the second CU is the target CU to which the MT is about to switch; the first information is further used to instruct the third CU to migrate F1 interface traffic with the DU of the relay node to the second CU topology. The first information is used to instruct the third CU to request downlink configuration information for F1 interface traffic migration from the second CU.
[0234] 903. The third CU sends third information to the second CU.
[0235] Correspondingly, the second CU receives the third information from the third CU.
[0236] The above-mentioned third information is used to request downlink configuration information for F1 interface transmission. Optionally, the third information is used to request downlink configuration information for F1 interface transmission between the third CU and the DU of the relay node. The third information may be carried in an inter-topology traffic migration request (IAB Transport Migration Management Request) message. An example of step 903 is: the third CU initiates an inter-topology traffic migration request to the second CU (such as: sending an IAB Transport Migration Management Request message to the second CU), and the IAB Transport Migration Management Request message is used to request downlink configuration information for F1 interface transmission between the third CU and the DU of the relay node.
[0237] 904. The second CU sends downlink configuration information for F1 interface transmission to the third CU.
[0238] Optionally, the second CU sends downlink configuration information for F1 interface transmission between the third CU and the DU of the relay node to the third CU. An example of step 904 is: the second CU replies to the third CU with a cross-topology traffic migration request response (e.g., sending an IAB Transport Migration Management Response message to the third CU), carrying the DSCP / flow label that the second CU wishes the third CU to insert into the IP header of the downlink F1 interface message (or F1 downlink data packet). Exemplarily, if the relay node's DU is identified by the DU's IP address in the first message, then in this step, the second CU replies to the third CU with the mapping relationship between the DU's IP address and the DSCP / flow label carried in the first message; if the relay node's DU is identified by the DU's gNB-DU ID in the first message, then in this step, the second CU replies to the third CU with the mapping relationship between the IP address it allocated for the DU and the DSCP / flow label.
[0239] In an embodiment of the present application, first information is sent to the third CU, where the first information is used to instruct the third CU to request downlink configuration information for F1 interface transmission from the second CU; so that the third CU obtains the downlink configuration information for F1 interface transmission, thereby enabling the F1 interface to be established.
[0240] Figure 10 is an interactive flow chart of another communication method provided by an embodiment of the present application. The method flow in Figure 10 is a possible implementation of the method described in Figure 9. In this implementation, the first CU selects the third CU as the target host CU of the DU of the relay node to ensure that the F1 interface traffic between the DU of the relay node and the third CU established subsequently can be transmitted through the topology of the second CU. In the drawings of the present application, CU1 represents the first CU, CU2 represents the second CU, CU2 represents the third CU, mAB-MT represents the MT of the relay node, mAB-DU1 represents the DU of the relay node, and mAB-DU2 represents the new logical DU generated by the relay node. As shown in Figure 10, the method includes:
[0241] 1001. The first CU selects the third CU as the target host CU of the DU of the relay node.
[0242] There is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU. The F1 interface traffic between the third CU and the DU of the relay node needs to be transmitted through the topology under the second CU, wherein the transmission between the host DU of the second CU and the third CU is transmitted through the IP network. Therefore, it is necessary to ensure that the IP connection between the host DU of the second CU and the third CU exists (which can be called "IP reachability between the host DU of the second CU and the third CU"). When the first CU selects the target host CU of the DU, it needs to consider the IP reachability between the target host CU of the DU and the second CU. Alternatively, a more stringent judgment condition than IP reachability can be adopted: the existence or ability to establish an XN interface.
[0243] One possible implementation of step 1001 is as follows: Based on the network segment to which the IP address belongs, the third CU that has an IP connection with the second CU is selected as the target host CU for the relay node's DU (i.e., the new logical DU). In this implementation, the third CU that has an IP connection, an Xn interface, or the ability to establish an Xn connection with the second CU is selected as the target host CU for the relay node's DU.
[0244] A possible implementation of step 1001 is as follows: selecting the third CU in a preconfigured target list as the target host CU for the DU of the relay node, where an IP connection, an Xn interface, or the ability to establish an Xn interface exists between the CU in the target list and the second CU. In this implementation, selecting the target host CU for the DU of the relay node from the target list ensures that an IP connection, an Xn interface, or the ability to establish an Xn connection exists between the target host CU selected for the DU of the relay node and the second CU.
[0245] In one possible implementation, before executing step 1001, the first CU performs the following operations: receiving first reference information from the second CU via an XN interface, the first reference information indicating that an IP connection, an Xn interface, or an ability to establish an Xn interface exists between the second CU and the third CU; and determining, based on the first reference information, that an IP connection, an Xn interface, or an ability to establish an Xn interface exists between the second CU and the third CU. For example, the first reference information includes multiple CUs (including the third CU) that have an IP connection, an Xn interface, or an ability to establish an Xn interface with the second CU. That is, the CUs (including the second CU) that have an XN interface with the first CU notify the first CU via the XN interface of all CUs that are IP-reachable or have an XN interface with them, and the first CU selects one of these CUs as the target host CU for the mAB-DU. Accordingly, the first CU also sends information about the CUs that have an XN interface or are IP-reachable to the CUs (including the second CU) that have an XN interface with them. Alternatively, the second reference information from the third CU is received through the XN interface, and the second reference information is used to indicate that there is an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU; based on the second reference information, it is determined that there is an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU. For example, the second reference information includes multiple CUs (including the second CU) that have an IP connection, an Xn interface, or an Xn interface can be established with the third CU. For example, the second reference information includes multiple CUs (including the second CU) that have an IP connection, an Xn interface, or an Xn interface can be established with the third CU. In this implementation, the first reference information from the second CU is received through the XN interface, and it can be learned that there is an IP connection, an Xn interface, or an Xn interface can be established between the second CU and the third CU.
[0246] 1002. The first CU sends message 1 to the DU of the relay node.
[0247] Accordingly, the relay node's DU receives Message 1 from the first CU. Message 1 may carry identification information of the third CU, such as the gNB ID of the third CU. Message 1 is used to trigger the relay node to initiate an F1 interface establishment request to the third CU via a new logical DU. Message 1 may be an F1 setup indication. Alternatively, Message 1 is used to trigger the relay node's DU to send its identification information to the first CU. Step 1002 is optional.
[0248] 1003. The DU of the relay node sends second information to the first CU.
[0249] Accordingly, the first CU receives the second information from the relay node's DU. The second information includes identification information of the relay node's DU, such as the gNB-DU ID of the relay node's DU. The second information may be carried in a gNB-DU Configuration Update message or other message. For example, after receiving Message 1, the relay node's DU sends the second information to the first CU. Alternatively, receipt of Message 1 by the relay node's DU triggers the relay node's DU to send the second information to the first CU. It is understood that after receiving Message 1, the relay node's DU can notify the first CU of the gNB-DU ID of DU2 (the relay node's new logical DU), enabling the first CU to subsequently notify the third CU of the gNB-DU ID of DU2.
[0250] 1004. The first CU sends first information to the third CU.
[0251] Correspondingly, the third CU receives the first information from the first CU. The first information is used to instruct the third CU to request the second CU for downlink configuration information for target F1 interface transmission. In this application, the target F1 interface refers to the F1 interface between the third CU to be established and the DU of the relay node. For example, the above-mentioned first information is used to instruct the above-mentioned third CU to send a cross-topology traffic migration request to the above-mentioned second CU (for example, sending an IAB Transport Migration Management Request message to the second CU) to request the above-mentioned second CU for downlink configuration information for target F1 interface transmission.
[0252] In one possible implementation, the first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU. The first information may also include the UE XnAP ID of the MT under the first CU. In this implementation, the first information is sent to the third CU so that the third CU requests downlink configuration information for target F1 interface transmission from the second CU based on the first information.
[0253] In a possible implementation, the first information is also used to indicate the binding relationship between the MT (UE XnAP ID identifier of the available MT under the second CU) and the DU of the relay node (gNB-DU ID identifier of the available DU).
[0254] 1005. The third CU sends third information to the second CU.
[0255] Correspondingly, the second CU receives the third information from the third CU. The third information is used to request downlink configuration information for target F1 interface transmission. Step 1005 can refer to step 903.
[0256] 1006. The second CU sends downlink configuration information for target F1 interface transmission to the third CU.
[0257] Step 1006 may refer to step 904 .
[0258] 1007. The DU of the relay node sends an F1 establishment request message to the third CU.
[0259] In some embodiments, after obtaining uplink configuration information for target F1 interface transmission, the DU of the relay node may send an F1 SETUP REQUEST message to the third CU.
[0260] 1008. The third CU sends an F1 establishment response message to the DU of the relay node.
[0261] After obtaining the downlink configuration information for the target F1 interface transmission and receiving the F1 SETUP REQUEST, the relay node sends an F1 setup response message to the DU of the relay node.
[0262] 1009. The third CU sends message 2 to the second CU.
[0263] Message 2 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1009 is optional. Message 2 may include: the UE XnAP ID of the mobile operator in the second CU, the UE XnAP ID of the mobile operator in the third CU, and the gNB-DU ID of mIAB-DU2.
[0264] 1009'. The MT sends message 3 to the second CU.
[0265] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1009' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. 1009 and step 1009' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 10 includes either step 1009 or step 1009', or does not include either step 1009 or step 1009'.
[0266] In this embodiment of the present application, the first CU selects the third CU as the target host CU for the relay node's DU to ensure that the F1 interface traffic subsequently established between the relay node's DU and the third CU can be transmitted through the second CU's topology. In addition, the first CU sends a first message to the third CU, which is used to instruct the third CU to request downlink configuration information for F1 interface transmission from the second CU; so that the third CU obtains the downlink configuration information for F1 interface transmission, thereby enabling the F1 interface to be established.
[0267] FIG11 is an interactive flow chart of another communication method provided by an embodiment of the present application. The method flow in FIG11 is a possible implementation of the method described in FIG9. In this implementation, the DU of the relay node sends a second message to the first CU, and the second message instructs the first CU to trigger the third CU to request the second CU for downlink configuration information transmitted by the F1 interface, so that the third CU can obtain the downlink configuration information for F1 interface transmission. As shown in FIG11, the method includes:
[0268] 1101. The DU of the relay node sends second information to the first CU.
[0269] Accordingly, the first CU receives second information from the relay node's DU. This second information includes identification information of the relay node's DU and identification information of the third CU, such as the third CU's gNB IB and / or IP address. The second information instructs the first CU to trigger the third CU to request downlink configuration information for target F1 interface transmission from the second CU. The second information may be carried in a gNB-DU Configuration Update message or other message.
[0270] In one possible implementation, before the relay node's DU sends the second information to the first CU, the relay node performs the following operations: based on pre-configured information for operations administration and maintenance (OAM), the relay node determines that a target F1 interface, i.e., an F1 interface between the relay node's DU and the third CU, needs to be established. After determining that the target F1 interface needs to be established, the relay node sends the second information to the first CU to establish the target F1 interface.
[0271] 1102. The first CU sends first information to the third CU.
[0272] Correspondingly, the third CU receives the first information from the first CU. The first information is used to instruct the third CU to request the second CU for downlink configuration information for target F1 interface transmission. For example, the above-mentioned first information is used to instruct the above-mentioned third CU to send a cross-topology traffic migration request to the above-mentioned second CU (for example, sending an IAB Transport Migration Management Request message to the second CU) to request the above-mentioned second CU for downlink configuration information for target F1 interface transmission. A possible implementation method of step 1103 is as follows: the first CU sends the first information to the third CU based on the second information. The operation of the first CU sending the first information to the third CU can be regarded as: the first CU triggers the third CU to request the second CU for the downlink configuration information for target F1 interface transmission.
[0273] In one possible implementation, the first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU. The first information may also include the UE XnAP ID of the MT under the first CU. In this implementation, the first information is sent to the third CU so that the third CU requests downlink configuration information for target F1 interface transmission from the second CU based on the first information.
[0274] In a possible implementation, the first information is also used to indicate the binding relationship between the MT (UE XnAP ID identifier of the available MT under the second CU) and the DU of the relay node (gNB-DU ID identifier of the available DU).
[0275] 1103. The third CU sends third information to the second CU.
[0276] Correspondingly, the second CU receives the third information from the third CU. The third information is used to request downlink configuration information for target F1 interface transmission. Step 1103 can refer to step 1005.
[0277] 1104. The second CU sends downlink configuration information for target F1 interface transmission to the third CU.
[0278] Step 1104 may refer to step 1006 .
[0279] 1105. The DU of the relay node sends an F1 establishment request message to the third CU.
[0280] Step 1105 may refer to step 1007 .
[0281] 1106. The third CU sends an F1 establishment response message to the DU of the relay node.
[0282] Step 1106 may refer to step 1008 .
[0283] 1107. The third CU sends message 2 to the second CU.
[0284] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mAB-DU2 and the third CU has been established). Step 1107 is optional. Message 2 may include: the UE XnAP ID of the mobile operator in the second CU, the UE XnAP ID of the mobile operator in the third CU, and the gNB-DU ID of mAB-DU2.
[0285] 1107'. The MT sends message 3 to the second CU.
[0286] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1107' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. Message 1107 and step 1107' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 11 includes either step 1107 or step 1107', or does not include either step 1107 or step 1107'.
[0287] In an embodiment of the present application, the DU of the relay node sends second information to the first CU, and the second information instructs the first CU to trigger the third CU to request the second CU for downlink configuration information transmitted by the F1 interface, so that the third CU can obtain the downlink configuration information for F1 interface transmission.
[0288] FIG12 is an interactive flow chart of another communication method provided by an embodiment of the present application. The method flow in FIG12 is a possible implementation of the method described in FIG9. In this implementation, the DU of the relay node sends a first message to the third CU, and the first message is used to instruct the third CU to request the second CU to transmit downlink configuration information for the target F1 interface, so that the third CU can obtain the downlink configuration information for the target F1 interface transmission. As shown in FIG12, the method includes:
[0289] 1201. The first CU sends message 1 to the DU of the relay node.
[0290] Correspondingly, the DU of the relay node receives the message 1 from the first CU. Step 1201 may refer to step 1002 .
[0291] 1201': The relay node determines that a target F1 interface needs to be established based on the OAM pre-configuration information.
[0292] It should be noted that steps 1201 and 1201' are two possible implementations. Both steps 1201 and 1201' can trigger the DU of the relay node to send the first information to the third CU, i.e., trigger the DU of the relay node to execute step 1201. The method flow in Figure 12 includes either step 1201 or step 1201', and the embodiments of the present application are not limited thereto.
[0293] 1202. The DU of the relay node sends first information to the third CU.
[0294] Accordingly, the third CU receives first information regarding a DU (logical DU) from the relay node. The first information is used to instruct the third CU to request the second CU for downlink configuration information for transmission on the target F1 interface. For example, the first information is used to instruct the third CU to send a cross-topology traffic migration request to the second CU to request the downlink configuration information for transmission on the target F1 interface. If the F1 interface between the third CU and the relay node's DU has not yet been established, the first information is carried in an F1 establishment request message, instructing the third CU to request the second CU for downlink configuration information for the newly established F1 interface. If the F1 interface between the third CU and the relay node's DU has already been established, the first information is carried in another F1 message (e.g., a GNB-DU CONFIGURATION UPDATE message), instructing the third CU to request the second CU for the downlink configuration information required to migrate the F1 interface to the second CU topology. The F1 establishment request message carries the gNB-DU ID and / or IP address of the relay node's DU, the gNB ID and / or IP address of the second CU, and identification information identifying the mobile equipment (MT) in the second CU. The identification information identifying the MT in the second CU includes at least one of the following: the BAP address of the relay node to which the MT belongs in the second CU, the IP address of the relay node used for F1 interface traffic transmission, and the C-RNTI and serving cell identifier of the MT. In this embodiment, the third CU has not obtained the MT's UE XnAP ID under the second CU from other CUs before step 1202. Therefore, the third CU cannot carry the MT's UE XnAP ID under the second CU when subsequently interacting with the second CU. Therefore, other forms of identification information are temporarily used in the first information to identify the MT. This identification needs to be recognizable by the second CU. In subsequent steps, the third CU will use this identification to find the second CU, and the second CU will then send the MT's UE XnAP ID under the second CU to the third CU. The C-RNTI is used to uniquely identify a UE within a cell. Therefore, the C-RNTI + serving cell ID can uniquely identify the MT under the second CU. Since the BAP address of the relay node to which the MT belongs in the second CU and the IP address of the relay node to which the MT belongs for F1 interface traffic transmission are both allocated by the second CU, these two items can also be used to identify the MT in the second CU.
[0295] 1203. The third CU sends third information to the second CU.
[0296] The third information is used to request downlink configuration information for target F1 interface transmission. The third information may include identification information identifying the MT in the second CU. The third information may be carried in an IAB Transport Migration Management Request message or other message.
[0297] In one possible implementation, the third information is further used to request a binding relationship between the MT and the DU of the relay node. The third information may include the UE XnAP ID of the MT under the third CU. In other words, the third information is used to request downlink configuration information for target F1 interface transmission and / or to request a binding relationship between the MT and the DU of the relay node. In this implementation, sending the third information to the second CU can also obtain the binding relationship between the MT and the DU of the relay node.
[0298] In one possible implementation, the first information includes identification information identifying the mobile terminal in the second CU. The third CU further performs the following operation: based on the identification information identifying the MT in the second CU, the third CU sends information for obtaining a binding relationship between the DU of the relay node and the MT to the second CU. After receiving this information, the second CU may inform the third CU of the binding relationship between the DU of the relay node and the MT. In this implementation, the information for obtaining a binding relationship between the DU of the relay node and the MT can be obtained by transmitting the information for obtaining a binding relationship between the DU of the relay node and the MT to the second CU.
[0299] In one possible implementation, the first information is carried in an F1 SETUP REQEUST message, and the F1 SETUP REQEUST message also includes a BAP address for target F1 interface transmission. When the BAP address (for target F1 interface transmission) carried in the F1 SETUP REQEUST message received by the third CU is not allocated by itself (for example, the identifier of the second CU that allocates the BAP address is also indicated in the F1 SETUP REQUEST message), the binding relationship between the mAB-DU and the mAB-MT will not be determined based on the BAP address. The third CU will initiate a request message (such as IAB Transport Migration Management Request) to the CU that allocates the BAP address (i.e., the second CU) to further obtain the binding relationship between the mAB-DU and the mAB-MT. In other words, only when the third CU learns that the BAP address carried in the received F1 SETUP REQEUST message is allocated by itself, will it determine the binding relationship based on the BAP address.
[0300] 1204. The second CU sends sixth information to the third CU.
[0301] The sixth information includes downlink configuration information for target F1 interface transmission and identification information for identifying the MT in the second CU, for example, the UE XnAP ID of the MT in the second CU.
[0302] In some possible embodiments, the second CU may send fourth information to the second CU, where the fourth information includes a correspondence between an IP address used for target F1 interface transmission and a DSCP or flow label used for target F1 interface transmission.
[0303] In this implementation, sending the fourth information to the second CU may enable the second CU to obtain the correspondence between the IP address used for F1 interface transmission and the DSCP or flow label used for F1 interface transmission.
[0304] 1205. The third CU sends an F1 establishment response message to the DU of the relay node.
[0305] Step 1205 may refer to step 1008 .
[0306] 1206. The third CU sends message 2 to the second CU.
[0307] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1206 is optional. Message 2 may include: the UE XnAP ID of the MT in the second CU, the UE XnAP ID of the MT in the third CU, and the gNB-DU ID of mIAB-DU2.
[0308] 1206'. The MT sends message 3 to the second CU.
[0309] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1206' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. Message 1206 and step 1206' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 12 may include either step 1206 or step 1206', or may not include either step 1206 or step 1206'.
[0310] In an embodiment of the present application, the DU of the relay node sends first information to the third CU, where the first information is used to instruct the third CU to request downlink configuration information for target F1 interface transmission from the second CU, so that the third CU can obtain the downlink configuration information for target F1 interface transmission.
[0311] FIG13 is an interactive flow chart of a communication method provided by an embodiment of the present application. In the interactive flow of FIG13 , the first CU instructs the second CU to send the first information to the third CU, rather than directly sending the first information to the third CU. As shown in FIG13 , the method includes:
[0312] 1301. The first CU selects the third CU as the target host CU of the DU of the relay node.
[0313] 1302. The first CU sends message 1 to the DU of the relay node.
[0314] Steps 1301 to 1302 may refer to steps 1001 to 1002 and will not be described in detail here.
[0315] 1303. The DU of the relay node sends seventh information to the first CU.
[0316] The seventh information includes identification information of the DU of the relay node.
[0317] 1301 ′: The relay node determines that a target F1 interface needs to be established based on the OAM pre-configuration information.
[0318] 1302'. The DU of the relay node sends eighth information to the first CU.
[0319] The eighth information is used to trigger the first CU to send the fifth information to the second CU. The fifth information is used to instruct (or trigger) the second CU to send the first information to the third CU, and the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission.
[0320] Steps 1301 to 1303 and steps 1301' to 1302' are two different implementations. It should be understood that the method flow in FIG13 includes steps 1301 to 1303, or includes 1301' to 1302', which is not limited in the embodiment of the present application.
[0321] 1304. The first CU sends fifth information to the second CU.
[0322] The fifth information is used to instruct (or trigger) the second CU to send the first information to the third CU. The first information is used to instruct the third CU to request the second CU for downlink configuration information for target F1 interface transmission. The fifth information may include identification information of the third CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0323] In one possible implementation, the fifth information is further used to indicate to the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being performed, or the relay node and the third CU are about to establish an F1 interface). After receiving the fifth information, the second CU does not migrate the MT of the relay node before the DU of the relay node completes the migration. In other words, the second CU will migrate the MT of the relay node only after the DU of the relay node completes the migration.
[0324] 1305. The second CU sends the first information to the third CU.
[0325] The first information may include at least one of identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0326] In a possible implementation, the first information is used to indicate the binding relationship between the MT and the DU of the relay node. In this implementation, the first information may enable the third CU to know the binding relationship between the MT and the DU of the relay node.
[0327] In one possible implementation, the second CU may further perform the following operation: receiving ninth information, where the ninth information is used to indicate that the DU migration of the relay node has been completed (or that the F1 interface between the DU of the relay node and the third CU has been established). The ninth information comes from the third CU or the relay node. The second CU cannot migrate the MT of the relay node before receiving the ninth information.
[0328] 1306. The third CU sends third information to the second CU.
[0329] Step 1306 may refer to step 903 .
[0330] 1307. The second CU sends downlink configuration information for target F1 interface transmission to the third CU.
[0331] 1308. The DU of the relay node sends an F1 establishment request message to the third CU.
[0332] 1309. The third CU sends an F1 establishment response message to the DU of the relay node.
[0333] 1310. The third CU sends message 2 to the second CU.
[0334] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1310 is optional. Message 2 may include: the UE XnAP ID of the mobile operator in the second CU, the UE XnAP ID of the mobile operator in the third CU, and the gNB-DU ID of mIAB-DU2.
[0335] 1310'. The MT sends message 3 to the second CU.
[0336] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1310' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. Message 1310 and step 1310' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 13 may include either step 1310 or step 1310', or may not include either step 1310 or step 1310'.
[0337] In this embodiment of the present application, the first CU sends the fifth information to the second CU, the second CU sends the first information to the third CU, and the third CU sends the third information to the second CU, so that the third CU can obtain downlink configuration information for target F1 interface transmission.
[0338] FIG14 is an interactive flow chart of another communication method provided by an embodiment of the present application. In the method flow in FIG14 , the first CU sends an eleventh message to the second CU, and the eleventh message is used to instruct the second CU to send downlink configuration information for transmission of the target F1 interface (not yet established) to the third CU. As shown in FIG14 , the method includes:
[0339] 1401. The first CU selects the third CU as the target host CU of the DU of the relay node.
[0340] 1402. The first CU sends message 1 to the DU of the relay node.
[0341] Steps 1401 to 1402 may refer to steps 1001 to 1002 and are not described again here.
[0342] 1403. The DU of the relay node sends seventh information to the first CU.
[0343] 1401': The relay node determines that a target F1 interface needs to be established based on the pre-configured information of the OAM.
[0344] 1402'. The DU of the relay node sends twelfth information to the first CU.
[0345] The twelfth information may include at least one of the identification information of the third CU, the identification information of the DU of the relay node, and the identification information of the second CU. The twelfth information is used to trigger the first CU to send the eleventh information to the second CU. The eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the target F1 interface (not completed) to the third CU.
[0346] Steps 1401 to 1403 and steps 1401' to 1402' are two different implementations. It should be understood that the method flow in FIG14 includes steps 1401 to 1403, or includes 1401' to 1402', which is not limited in the embodiment of the present application.
[0347] 1404. The first CU sends eleventh information to the second CU.
[0348] The eleventh information may include identification information of the third CU, identification information of the DU of the relay node, and identification information of the MT identifying the relay node in the second CU.
[0349] In a possible implementation, the eleventh information is also used to indicate the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being executed, or the relay node and the third CU are about to establish an F1 interface).
[0350] In a possible implementation, the eleventh information is further used to indicate the binding relationship between the MT and the DU of the relay node. In this implementation, the eleventh information may enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0351] 1405. The second CU sends tenth information to the third CU.
[0352] The tenth information includes at least one of identification information of the second CU, identification information of the DU of the relay node, identification information of the MT identifying the relay node in the second CU, and downlink configuration information for target F1 interface transmission.
[0353] 1406. The DU of the relay node sends an F1 establishment request message to the third CU.
[0354] 1407. The third CU sends an F1 establishment response message to the DU of the relay node.
[0355] 1408. The third CU sends message 2 to the second CU.
[0356] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1408 is optional. Message 2 may include: the UE XnAP ID of the MT in the second CU, the UE XnAP ID of the MT in the third CU, and the gNB-DU ID of mIAB-DU2.
[0357] 1408'. The MT sends message 3 to the second CU.
[0358] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1408' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. Message 1408 and step 1408' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 14 may include either step 1408 or step 1408', or may not include either step 1408 or step 1408'.
[0359] In the embodiment of the present application, the first CU sends the eleventh information to the second CU, and the second CU sends the tenth information to the third CU; the downlink configuration information for the target F1 interface transmission can be directly sent to the third CU, which can save signaling overhead.
[0360] FIG15 is an interactive flow chart of a communication method provided by an embodiment of the present application. In the interactive flow of FIG15 , the first CU instructs the second CU to send the first information to the third CU, rather than directly sending the first information to the third CU. As shown in FIG15 , the method includes:
[0361] 1501. The first CU selects the third CU as the target host CU of the DU of the relay node.
[0362] 1502. The first CU sends message 1 to the DU of the relay node.
[0363] Steps 1501 to 1502 may refer to steps 1001 to 1002 and will not be described in detail here. After the DU of the relay node receives the message 1, the relay node may determine that a target F1 interface needs to be established.
[0364] 1501': The relay node determines that a target F1 interface needs to be established based on the pre-configured information of the OAM.
[0365] Steps 1501 to 1502 and step 1501' are two different implementations. It should be understood that the method flow in FIG15 includes steps 1501 to 1502 or includes step 1501', which is not limited in the embodiment of the present application.
[0366] 1503. The MT of the relay node sends fifth information to the second CU.
[0367] The fifth information may include identification information of the third CU and identification information of the DU of the relay node. The fifth information is used to instruct (or trigger) the second CU to send the first information to the third CU. The first information is used to instruct the third CU to request the downlink configuration information for target F1 interface transmission from the above-mentioned second CU. Alternatively, the fifth information is used to instruct the second CU to trigger the third CU to initiate cross-topology traffic migration. The third CU initiating cross-topology traffic migration needs to request the downlink configuration information for target F1 interface transmission from the above-mentioned second CU.
[0368] In one possible implementation, the fifth information is also used to indicate to the second CU that the DU migration of the relay node is about to occur (or the DU migration of the relay node is being performed, or the relay node and the third CU are about to establish an F1 interface). After receiving the fifth information, the second CU does not migrate the MT of the relay node before the DU of the relay node completes the migration. In other words, the second CU will migrate the MT of the relay node only after the DU of the relay node completes the migration.
[0369] 1504. The second CU sends the first information to the third CU.
[0370] The first information may include identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
[0371] In a possible implementation, the first information is used to indicate the binding relationship between the MT and the DU of the relay node. In this implementation, the first information may enable the third CU to know the binding relationship between the MT and the DU of the relay node.
[0372] In one possible implementation, the second CU may further perform the following operation: receiving ninth information, where the ninth information is used to indicate that the DU migration of the relay node has been completed (or that the F1 interface between the DU of the relay node and the third CU has been established). The ninth information comes from the third CU or the relay node. The second CU cannot migrate the MT of the relay node before receiving the ninth information.
[0373] 1505. The third CU sends third information to the second CU.
[0374] Step 1505 may refer to step 903 .
[0375] 1506. The second CU sends downlink configuration information for target F1 interface transmission to the third CU.
[0376] 1507. The DU of the relay node sends an F1 establishment request message to the third CU.
[0377] 1508. The third CU sends an F1 establishment response message to the DU of the relay node.
[0378] 1509. The third CU sends message 2 to the second CU.
[0379] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1509 is optional. Message 2 may include: the UE XnAP ID of the mobile operator in the second CU, the UE XnAP ID of the mobile operator in the third CU, and the gNB-DU ID of mIAB-DU2.
[0380] 1509'. The MT sends message 3 to the second CU.
[0381] Message 3 is used to notify the second CU that DU migration is complete (or that the F1 interface between mIAB-DU2 and the third CU has been established). Step 1509' is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2. Message 1509 and step 1509' are two possible ways to notify the second CU that DU migration is complete. The method flow in Figure 15 may include either step 1509 or step 1509', or may not include either step 1509 or step 1509'.
[0382] In the embodiment of the present application, the MT of the relay node sends the fifth information to the second CU, the second CU sends the first information to the third CU, and the third CU sends the third information to the second CU, so that the third CU can obtain the downlink configuration information for the target F1 interface transmission.
[0383] FIG16 is an interactive flow chart of another communication method provided by an embodiment of the present application. In the method flow in FIG16 , the first CU sends an eleventh message to the second CU, and the eleventh message is used to instruct the second CU to send downlink configuration information for transmission of the target F1 interface (not yet established) to the third CU. As shown in FIG16 , the method includes:
[0384] 1601. The first CU selects the third CU as the target host CU of the DU of the relay node.
[0385] 1602. The first CU sends message 1 to the DU of the relay node.
[0386] Steps 1601 to 1602 may refer to steps 1001 to 1002 and will not be described in detail here. After the DU of the relay node receives the message 1, the relay node may determine that a target F1 interface needs to be established.
[0387] 1601': The relay node determines that a target F1 interface needs to be established based on the OAM pre-configuration information.
[0388] Steps 1601 to 1602 and step 1601' are two different implementations. It should be understood that the method flow in FIG16 includes steps 1601 to 1602 or includes step 1601', which is not limited in the embodiment of the present application.
[0389] 1603. The MT of the relay node sends eleventh information to the second CU.
[0390] The eleventh information is used to instruct the second CU to send downlink configuration information for transmission of the target F1 interface (not yet established) to the third CU. The eleventh information includes the identification information of the third CU and the identification information of the DU of the relay node.
[0391] In a possible implementation, the eleventh information is also used to indicate the second CU that DU migration of the relay node is about to occur (or DU migration of the relay node is being executed, or the relay node and the third CU are about to establish an F1 interface).
[0392] In a possible implementation, the eleventh information is used to indicate the binding relationship between the MT and the DU of the relay node. In this implementation, the eleventh information may enable the third CU to learn the binding relationship between the MT and the DU of the relay node.
[0393] 1604. The second CU sends tenth information to the third CU.
[0394] The tenth information includes at least one of the following: identification information of the second CU, identification information of the DU of the relay node, identification information identifying the MT of the relay node in the second CU, and downlink configuration information for target F1 interface transmission. In some embodiments, the tenth information also serves to inform the third CU of the binding relationship between the mAB-MT and the mAB-DU2. In other words, the tenth information is also used to indicate the binding relationship between the MT and the DU of the relay node.
[0395] 1605. The DU of the relay node sends an F1 establishment request message to the third CU.
[0396] 1606. The third CU sends an F1 establishment response message to the DU of the relay node.
[0397] In the embodiment of the present application, the MT of the relay node sends the eleventh information to the second CU, and the second CU sends the tenth information to the third CU; the downlink configuration information for the target F1 interface transmission can be directly sent to the third CU, which can save signaling overhead.
[0398] 1607. The third CU sends message 2 to the second CU.
[0399] Message 2 is used to inform the second CU that DU migration is complete (or that the F1 interface between mAB-DU2 and the third CU has been established). Step 1607 is optional. Message 2 may include: the UE XnAP ID of the MT in the second CU, the UE XnAP ID of the MT in the third CU, and the gNB-DU ID of mAB-DU2.
[0400] 1607'. The MT sends message 3 to the second CU.
[0401] Message 3 is used to inform the second CU that DU migration is complete (or the F1 interface between mIAB-DU2 and the third CU is established). Step 1607′ is optional. Optionally, Message 3 carries the gNB-DU ID of mIAB-DU2.
[0402] The aforementioned embodiments mainly analyze the scenario in which the first CU, the second CU, and the third CU are three different CUs, but the second CU and the third CU are the same CU, and the first CU and the second CU are the same CU, which are two special cases, corresponding to Figures 17A and 17B respectively. Figures 17A and 17B are examples of scenarios in which DU migrates and MT does not migrate provided in the embodiments of the present application. In the scenario shown in Figure 17A, the MT does not migrate and is always under the second CU, and the DU migrates from the first CU to the second CU. In the scenario shown in Figure 17A, the MT is always under the second CU, the DU migrates from the first CU to the second CU, and the downlink configuration information for target F1 interface transmission is allocated by the second CU. The second CU does not need to obtain the downlink configuration information for target F1 interface transmission from other CUs through interaction. In the scenario shown in Figure 17B, the MT does not migrate and is always under the second CU, and the DU migrates from the second CU to the third CU.
[0403] FIG18 is an interactive flow chart of another communication method provided in an embodiment of the present application. The communication method shown in FIG18 is applicable to the scenario shown in FIG17B. As shown in FIG18, the method may include:
[0404] 1801. The DU of the relay node sends second information to the second CU.
[0405] The second information can be carried in an existing gNB-DU configuration update message or a new message.
[0406] 1801′. The MT sends second information to the second CU.
[0407] The second information in step 1801 and step 1801' is the same. Step 1801 and step 1801' are two possible implementation methods, both of which enable the second CU to obtain the second information. The process of Figure 18 includes step 1801 or step 1801'. The second information may include identification information of the DU of the relay node. Optionally, the second information also includes identification information of the third CU. Before the DU or MT of the relay node sends the second information to the second CU, the relay node may perform the following operations: the DU of the relay node receives message 1 from the first CU; the relay node determines that a target F1 interface needs to be established based on message 1. Alternatively, before the DU or MT of the relay node sends the second information to the second CU, the relay node may perform the following operations: the relay node determines that a target F1 interface needs to be established based on the pre-configuration information of the OAM.
[0408] In one possible implementation, the second information is used to instruct (or trigger) the second CU to send the first information to the third CU. The first information is used to instruct the third CU to request the second CU for downlink configuration information for target F1 interface transmission. Alternatively, the first information is used to instruct the second CU to trigger the third CU to initiate cross-topology traffic migration. The third CU initiating cross-topology traffic migration needs to request the second CU for downlink configuration information for target F1 interface transmission.
[0409] In a possible implementation, the second information is used to instruct the second CU to send downlink configuration information for target F1 interface (uncompleted establishment) transmission to the third CU.
[0410] 1802. The second CU sends first information to the third CU.
[0411] When the second information is used to instruct (or trigger) the second CU to send the first information to the third CU, the method flow in FIG18 includes steps 1802 to 1804. Step 1802 can refer to step 1305.
[0412] 1803. The third CU sends third information to the second CU.
[0413] Step 1803 may refer to step 903 .
[0414] 1804. The second CU sends downlink configuration information for target F1 interface transmission to the third CU.
[0415] 1802′. The second CU sends tenth information to the third CU.
[0416] When the second information is used to instruct the second CU to send downlink configuration information for transmission over the target F1 interface (not yet established) to the third CU, the method flow in Figure 18 includes 1802'. The tenth information includes at least one of identification information of the second CU, identification information of the DU of the relay node, identification information of the MT identifying the relay node in the second CU, and downlink configuration information for transmission over the target F1 interface.
[0417] Steps 1802 to 1804 and step 1802' are two possible implementations for enabling the third CU to obtain downlink configuration information for target F1 interface transmission. It should be understood that the method flow in Figure 18 includes steps 1802 to 1804 or 1802', and this embodiment of the application does not limit this.
[0418] 1805. The DU of the relay node sends an F1 establishment request message to the third CU.
[0419] 1806. The third CU sends an F1 establishment response message to the DU of the relay node.
[0420] In the embodiment of the present application, the second CU sends the downlink configuration information or the tenth information for the target F1 interface transmission to the third CU, so that the third CU can obtain the downlink configuration information for the target F1 interface transmission.
[0421] The communication solution of the aforementioned embodiment enables the third CU to obtain downlink configuration information for target F1 interface transmission. The following describes a communication solution that enables the third CU to obtain the binding relationship between the DU of the relay node and the MT of the relay node.
[0422] FIG19 is a flow chart of another communication interaction method provided in an embodiment of the present application. As shown in FIG19 , the method includes:
[0423] 1901. A first CU generates first information.
[0424] The first information is used to indicate the binding relationship between the DU of the relay node and the mobile equipment of the relay node. The third CU is the target host CU of the DU of the relay node. The mobile equipment has an RRC connection with the second CU, and the second CU is different from the third CU. The first information may include identification information of the DU of the relay node and identification information identifying the mobile equipment in the second CU.
[0425] In some possible embodiments, before the first CU generates the first information, the process in FIG19 further includes steps 1001 to 1003 .
[0426] In some possible embodiments, before the first CU generates the first information, the process in FIG19 further includes step 1101 .
[0427] In some possible embodiments, the first CU in FIG19 is replaced by the second CU; before the second CU sends the first information, the process in FIG19 further includes steps 1301 to 1304.
[0428] In some possible embodiments, before the first CU generates the first information, the process in Figure 19 further includes steps 1401 to 1403. The twelfth information is used to trigger the first CU to send the first information to the second CU.
[0429] In some possible embodiments, the first CU in FIG19 is replaced by the second CU; before the second CU sends the first information, the process in FIG19 further includes steps 1501 to 1504.
[0430] In some possible embodiments, the first CU in FIG19 is replaced by the MT of the relay node; before the MT of the relay node sends the first information, the process in FIG19 further includes steps 1601 to 1602 or step 1601 ′.
[0431] 1902. The first CU sends first information to the third CU.
[0432] In one possible implementation, before sending the first information to the third CU, the first CU receives request information from the third CU. The request information is used to request a binding relationship between the mobile equipment (MT) and the DU of the relay node. The request information includes identification information identifying the MT in the second CU. Based on the request information, the first CU sends the first information to the third CU. In some possible embodiments, before receiving the request information from the third CU, the first CU sends an F1 setup request message to the third CU. The F1 setup request message may carry the gNB-DU ID and / or IP address of the DU of the relay node, the gNB ID and / or IP address of the second CU, and identification information identifying the MT in the second CU.
[0433] In one possible implementation, the first information is further used to instruct the third CU to request the second CU for downlink configuration information for target F1 interface transmission. For example, the first information is further used to instruct the third CU to initiate a cross-topology traffic migration request to the second CU to request the second CU for downlink configuration information for target F1 transmission.
[0434] 1903. The third CU determines the binding relationship between the DU and the MT of the relay node according to the first information.
[0435] In the embodiment of the present application, the binding relationship between the DU and the MT of the relay node can be determined according to the first information.
[0436] As the starting point of the downlink transmission BAP layer, the donor-DU requires downlink mapping (DL mapping). DL mapping involves obtaining the BAP routing ID and egress link information (including the next-hop BAP address and RLC CH ID) from the {destination IP address + DSCP / flow label} in the IP header. The details of DL mapping are as follows: the second CU configures the mapping of {destination IP address + DSCP / flow label} to {BAP routing ID + Next hop BAP Address + Next hop RLC CH ID} for donor-DU2. The second CU then sends the mapping of the destination IP address and DSCP / flow label to the third CU. When the third CU transmits downlink F1 data, it determines the corresponding DSCP / flow label based on the destination IP address. (The second CU may send a single IP address to the third CU, potentially mapping multiple DSCP / flow labels. Each mapping is sent to the third CU, which then determines which DSCP / flow label to use based on the IP address and its own QoS requirements.) The third CU then inserts both the IP address and DSCP / flow label into the IP header. When the downlink F1 data reaches donor-DU2, donor-DU2 opens the IP header, sees the determined {destination IP address + DSCP / flow label}, and then performs BAP layer processing according to the configured DL Mapping rules, wraps a BAP header outside the IP header (writes BAP routing ID), and sends it on the corresponding link (link) and RLC CH. CU can configure DL Mapping to donor-DU through UE CONTEXT SETUP REQUEST / UE CONTEXT MODIFICATION REQUEST / BAP MAPPING CONFIGURATION. In this application, donor-DU2 refers to the host DU managed by the second CU.
[0437] As can be seen from the above embodiments, a relatively large amount of interaction is performed in order for the third CU to obtain the DSCP / flow label for transmission on the target F1 interface. But in fact, the DSCP / flow label is used to finely manage the QoS requirements of the service. In the protocol, the DSCP / flow label is optional when the BAP layer of the donor-DU performs downlink mapping (DL Mapping). Although it is generally recommended to carry the DSCP / flow label in the IP header, the protocol does not require it to be carried. For user-plane data, the QoS types are relatively rich, and when doing DL Mapping for F1-U traffic, the necessity of carrying the DSCP / flow label is relatively large. However, for the F1-C on the control plane, the QoS requirements are relatively simple, and the necessity of carrying the DSCP / flow label is not as great as that of the F1-U. The communication solution provided below mainly solves the problem of how the donor-DU2 performs downlink mapping if the third CU does not obtain the DSCP / flow label when sending the first downlink F1 SETUP RESPONSE? In other words, before the third CU obtains the DSCP / flow label (for example, at the stage of sending F1-C, the DSCP / flow label may not be needed), how does donor-DU2 perform downlink mapping?
[0438] FIG20 is a flow chart of another communication interaction method provided by an embodiment of the present application. The communication solution shown in FIG20 can solve the problem of how donor-DU2 performs downlink mapping before the third CU obtains the DSCP / flow label. As shown in FIG20, the method includes:
[0439] 2001. The second CU sends first configuration information to the host DU managed by the second CU.
[0440] In Figure 20, donor-DU2 represents the donor DU managed by the second CU. For example, the second CU sends the first configuration information to the donor DU managed by the second CU in two ways other than the UE CONTEXT SETUP REQEUST. The first configuration information is used to inform the donor DU managed by the second CU to perform DL mapping based only on the IP address. The first configuration information does not include a DSCP / flow label.
[0441] 2002. The second CU receives second indication information.
[0442] The second indication information is used to instruct the second CU to send downlink configuration information for target F1 interface transmission to the third CU. For example, the second indication information is the third information or the eleventh information in the previous embodiment. Step 2002 is optional. The second CU receiving the second indication information is a possible implementation method for the second CU to know that the third CU is about to obtain or has obtained the correct DSCP / flow label. The second CU may also know that the third CU is about to obtain or has obtained the correct DSCP / flow label through other means.
[0443] 2002′. The third CU sends fourth information to the second CU.
[0444] The fourth information includes a correspondence between the IP address used for transmission on the target F1 interface and the DSCP or flow label used for transmission on the target F1 interface. This correspondence indicates the DSCP / flow label that the third CU wishes to insert for packets destined for each IP address. Step 2002' is optional. Step 2002' is one possible implementation method for the second CU to learn that the third CU is about to obtain or has obtained the correct DSCP / flow label.
[0445] 2003. The second CU sends first configuration update information to the host DU managed by the second CU.
[0446] The first configuration update information informs the host DU managed by the second CU to perform DL Mapping based on the IP address and DSCP / flow label. The first configuration update information includes the IP address and DSCP / flow label. When the second CU receives the second indication information or the fourth information, it determines that it is necessary to enable DL Mapping based on IP address + DSCP / flow label at this time, and DL Mapping can no longer be performed based on the IP address alone, then it initiates a DL Mapping configuration update to donor-DU2, that is, sends the first configuration update information to the host DU managed by the second CU. For example, the second CU can send the first configuration update information to the host DU managed by the second CU in two other ways besides UE CONTEXT SETUP REQEUST, because the initial context of the MT has been established. If the second CU receives the fourth information, the correspondence between the IP address and the DSCP / flow label in the first configuration update information adopts the one that the third CU wants to enter.
[0447] In an embodiment of the present application, before the third CU obtains the DSCP / flow label, the host DU managed by the second CU performs downlink mapping only based on the IP address; when the third CU is about to obtain or has obtained the correct DSCP / flow label, the host DU managed by the second CU performs DL Mapping based on the IP address and DSCP / flow label.
[0448] FIG21 is a flow chart of another communication interaction method provided by an embodiment of the present application. The communication solution shown in FIG21 can solve the problem of how donor-DU2 performs downlink mapping before the third CU obtains the DSCP / flow label. As shown in FIG21, the method includes:
[0449] 2101. The second CU sends second configuration information to the host DU managed by the second CU.
[0450] For example, the second CU can send the second configuration information to the host DU managed by the second CU in two other ways besides UE CONTEXT SETUP REQEUST, because the initial context of the MT has been established. The second configuration information includes an IP address, a DSCP / flow label and a third indication information. Optionally, the second configuration information includes a correspondence between the IP address and the DSCP / flow label. The third indication information is used to instruct donor-DU2 to ignore the DSCP / flow label value in the IP header of the F1 data packet sent by the third CU (if the third CU will insert an erroneous or random DSCP / flow label). The third indication information is also used to instruct the host DU managed by the second CU to perform DL Mapping according to the DSCP / flow label corresponding to the IP address in the second configuration information. If there are multiple DSCP / flow labels corresponding to the same IP address, donor-DU2 selects one of the DSCP / flow labels. Alternatively, the third indication information is also used to instruct donor-DU2 to perform DL mapping according to the DSCP / flow label corresponding to the IP address in the second configuration information, even though the IP header of the data packet sent by the third CU does not contain a DSCP / flow label value (if the third CU does not insert a DSCP / flow label). If there are multiple DSCP / flow labels corresponding to the same IP address, donor-DU2 selects one of the DSCP / flow labels.
[0451] 2102. The second CU receives second indication information.
[0452] Step 2102 may refer to step 2002 .
[0453] 2102'. The third CU sends fourth information to the second CU.
[0454] Step 2102' may refer to step 2002'.
[0455] 2103. The second CU sends second configuration update information to the host DU managed by the second CU.
[0456] The second configuration update information may include fourth indication information. The fourth indication information is used to inform donor-DU2 to cancel the operation of ignoring the DSCP / flow label value in the IP header of the F1 data packet described in step 2101 or to perform DL mapping according to the DSCP / flow label corresponding to the IP address configured in step 2101, that is, to resume normal DL mapping according to the DSCP / flow label in the IP header of the data packet sent by the third CU.
[0457] When the second CU receives the second indication information or the fourth information, it determines that DL Mapping based on IP address + DSCP / flow label needs to be enabled at this time, and DL Mapping based on IP address alone can no longer be performed, then it initiates a DL Mapping configuration update to donor-DU2, that is, sends the first configuration update information to the host DU managed by the second CU. For example, the second CU can send the first configuration update information to the host DU managed by the second CU in two ways other than UE CONTEXT SETUP REQEUST, because the initial context of the MT has been established.
[0458] This embodiment enables donor-DU2 to perform DL mapping only based on the IP address or the DSCP / flow label configured by the second CU when the third CU has not yet obtained the correct DSCP / flow label. When the third CU has obtained or is about to obtain the correct DSCP / flow label, donor-DU2 resumes DL mapping based on the DSCP / flow label in the IP header.
[0459] Figure 22 shows a possible exemplary block diagram of a communication device involved in an embodiment of the present application. As shown in Figure 22, the communication device 2200 may include: a processing unit 2201 and a transceiver unit 2202. The processing unit 2201 is used to control and manage the actions of the communication device 2200. The transceiver unit 2202 is used to support communication between the communication device 2200 and other devices. Optionally, the transceiver unit 2202 may include a receiving unit and / or a sending unit, which are used to perform receiving and sending operations respectively. Optionally, the communication device 2200 may also include a storage unit for storing program code and / or data of the communication device 2200. The above-mentioned transceiver unit may be referred to as an input / output unit, a communication unit, etc., and the above-mentioned transceiver unit may be a transceiver; the above-mentioned processing unit may be a processor. When the communication device is a module (such as a chip) in a communication device, the above-mentioned transceiver unit may be an input / output interface, an input / output circuit or an input / output pin, etc., and may also be referred to as an interface, a communication interface or an interface circuit, etc.; the above-mentioned processing unit may be a processor, a processing circuit or a logic circuit, etc. Specifically, the device may be the first CU, the second CU, the third CU, the IAB node, the mIAB-DU, the mIAB-MT, etc.
[0460] This application also provides a network device. As shown in Figure 23, a schematic diagram of the structure of a network device 2300 provided in an embodiment of this application is provided. For example, network device 2300 may include a first CU, a second CU, a third CU, and an IAB-DU, configured to perform the functions of the network device in the above-described method embodiment. It should be understood that the following is merely an example, and in future communication systems, network devices may have other forms and configurations.
[0461] For example, in a 5G communication system, the network device 2300 may include a CU, a DU, and an AAU. Compared to the network device in an LTE communication system, which consists of one or more radio frequency units, such as a remote radio unit (RRU) and one or more building base band units (BBU):
[0462] The non-real-time portion of the original BBU will be separated and redefined as a CU, responsible for handling non-real-time protocols and services. Some of the BBU's physical layer processing functions will be merged with the original RRU and passive antennas into the AAU. The remaining BBU functions will be redefined as a DU, responsible for handling physical layer protocols and real-time services. In short, the CU and DU are differentiated by the real-time nature of their processing, and the AAU is a combination of the RRU and antenna.
[0463] The CU, DU, and AAU can be deployed separately or together, resulting in a variety of network deployment configurations. One possible deployment configuration, shown in Figure 23, is consistent with traditional 4G network equipment, with the CU and DU deployed on shared hardware. It should be understood that Figure 23 is merely an example and does not limit the scope of protection of this application. For example, the deployment configuration may also include the DU being deployed in the BBU room, the CU being deployed centrally, or the DU being deployed centrally, with the CU being centralized at a higher level.
[0464] The AAU 2400 can implement transceiver functions corresponding to the transceiver unit 2202 in FIG. 22 . Optionally, the AAU 2400 can also be referred to as a transceiver, a transceiver circuit, or a transceiver, and can include at least one antenna 2401 and a radio frequency unit 2402. Optionally, the AAU 2400 can include a receiving unit and a transmitting unit. The receiving unit can correspond to a receiver (or receiver, receiving circuit), and the transmitting unit can correspond to a transmitter (or transmitter, transmitting circuit). The internal processing functions implemented by the CU and DU 2500 correspond to the functions of the processing unit 2201 in FIG. 22 . Optionally, the CU and DU 2500 can control network devices and can be referred to as controllers. The AAU, CU, and DU can be physically co-located or physically separated.
[0465] In addition, the network device is not limited to the form shown in Figure 23, but can also be in other forms: for example: including a BBU and an adaptive radio unit (ARU), or including a BBU and an AAU; it can also be customer premises equipment (CPE), or it can be in other forms, which is not limited in this application.
[0466] In one example, the CU and DU2500 may be composed of one or more boards, and the multiple boards may jointly support a wireless access network with a single access standard (such as an LTE network), or may respectively support wireless access networks with different access standards (such as an LTE network, a 5G network, a future network or other networks). The CU and DU2500 also include a memory 2501 and a processor 2502. The memory 2501 is used to store necessary instructions and data. The processor 2502 is used to control the network device to perform necessary actions, such as controlling the network device to execute the operation process of the network device in the above method embodiment. The memory 2501 and the processor 2502 may serve one or more boards. That is, a memory and a processor may be separately set on each board. Alternatively, multiple boards may share the same memory and processor. In addition, necessary circuits may be provided on each board.
[0467] It should be understood that the network device 2300 shown in Figure 23 is capable of implementing the network device functions involved in the method embodiments of Figures 9 to 16 and Figures 18 to 21. The operations and / or functions of the various units in the network device 2300 are respectively for implementing the corresponding processes performed by the network device in the method embodiments of the present application. In order to avoid or reduce repetition, detailed descriptions are appropriately omitted here. The structure of the network device illustrated in Figure 23 is only one possible form and should not constitute any limitation on the embodiments of the present application. The present application does not exclude the possibility of other forms of network device structures that may appear in the future.
[0468] The CU and DU 2500 can be used to perform the actions described in the previous method embodiments, which are implemented within the network device. The AAU 2400 can be used to perform the actions described in the previous method embodiments, where the network device sends or receives data to or from other devices. For details, please refer to the description in the previous method embodiments and will not be repeated here.
[0469] An embodiment of the present application also provides a communication system, which includes the above-mentioned first CU, the above-mentioned second CU, and the above-mentioned third CU.
[0470] An embodiment of the present application also provides a communication system, which includes the above-mentioned donor-CU2, the above-mentioned second CU, and the above-mentioned third CU.
[0471] An embodiment of the present application further provides a communication system, which includes the first CU, the second CU, the third CU, and the IAB node.
[0472] The present application also provides a chip, which includes: a communication interface and a processor; the communication interface is used for sending and receiving signals of the above-mentioned chip; the processor is used to execute computer program instructions so that the communication device including the above-mentioned chip executes the method in the above-mentioned embodiment.
[0473] Based on the above embodiments, embodiments of the present application further provide a readable storage medium storing instructions that, when executed, implement the method of any of the above embodiments. The readable storage medium may include a USB flash drive, a mobile hard drive, a read-only memory, a random access memory, a magnetic disk, or an optical disk, among other media capable of storing program code.
[0474] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program code.
[0475] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0476] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0477] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
Claims
1. A communication method, characterized in that: include: Generate first information, where the first information is used to instruct the third centralized unit CU to request the second CU for downlink configuration information for F1 interface transmission, where the second CU has a radio resource control RRC connection with the mobile terminal MT of the relay node, and the third CU is a target host CU of the distributed unit DU of the relay node; Send the first information to the third CU.
2. The method according to claim 1, characterized in that The first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
3. The method according to claim 1 or 2, characterized in that: Before sending the first information to the third CU, the method further includes: Second information is received from the relay node, where the second information includes identification information of the DU of the relay node.
4. The method according to any one of claims 1 to 3, characterized in that: Before sending the first information to the third CU, the method further includes: The third CU is selected as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the third CU and the second CU.
5. The method according to claim 4, characterized in that The selecting the third CU as the target host CU of the DU of the relay node includes: Based on the network segment to which the IP address belongs, selecting the third CU having an IP connection with the second CU as the target host CU of the DU of the relay node; Alternatively, the third CU in the preconfigured target list is selected as the target host CU of the DU of the relay node, and there is an IP connection, an Xn interface, or an Xn interface can be established between the CU in the target list and the second CU.
6. The method according to claim 3, characterized in that: The second information comes from the DU of the relay node, and the second information also includes identification information of the third CU.
7. The method according to claim 6, characterized in that The second information is used to instruct the first CU to trigger the third CU to request the second CU for downlink configuration information transmitted through the F1 interface, and the first CU is the source host CU of the DU of the relay node.
8. A communication method, characterized in that: include: Receive first information, where the first information is used to instruct a third centralized unit CU to request downlink configuration information for F1 interface transmission from a second CU, where a radio resource control RRC connection is established between the second CU and a mobile terminal MT of a relay node, and the third CU is a target host CU of a distributed unit DU of the relay node; Send third information to the second CU, where the third information is used to request downlink configuration information for F1 interface transmission.
9. The method according to claim 8, characterized in that The first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
10. The method according to claim 8 or 9, characterized in that: The third information is also used to request to obtain the binding relationship between the MT and the DU of the relay node.
11. The method according to any one of claims 8 to 10, characterized in that: The first information comes from the DU of the relay node, and the first information is carried in the F1 establishment request message.
12. The method according to claim 8 or 9, characterized in that: The first information comes from the DU of the relay node, and the first information includes identification information identifying the MT in the second CU; the method further includes: Based on the identification information identifying the MT in the second CU, information for acquiring a binding relationship between the DU of the relay node and the MT is sent to the second CU.
13. The method according to claim 12, characterized in that The identification information of the MT includes at least one of the following: a BAP address of the relay node to which the MT belongs in the second CU, an IP address of the relay node to which the MT belongs for F1 interface traffic transmission, a cell radio network temporary identifier C-RNTI of the MT, and a serving cell identifier.
14. The method according to any one of claims 8 to 13, characterized in that The method further comprises: Sending fourth information to the second CU, where the fourth information includes a correspondence between an IP address used for F1 interface transmission and a DSCP or a flow label used for F1 interface transmission.
15. A communication method, characterized in that: include: Receive fifth information, where the fifth information is used to instruct the second centralized unit CU to send first information to the third CU, where the first information is used to instruct the third CU to request the second CU for downlink configuration information for F1 interface transmission, where the second CU has a radio resource control RRC connection with the mobile terminal MT of the relay node, and the third CU is a target host CU of the distributed unit DU of the relay node; Send the first information to the third CU.
16. The method according to claim 15, characterized in that The fifth information comes from the MT, and the fifth information includes identification information of the third CU and identification information of the DU of the relay node.
17. The method according to claim 15, characterized in that The fifth information comes from the source host CU of the DU of the relay node, and the fifth information includes identification information of the third CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
18. The method according to any one of claims 15 to 17, characterized in that The first information includes identification information of the second CU, identification information of the DU of the relay node, and identification information identifying the MT in the second CU.
19. The method according to claim 18, characterized in that The first information is used to indicate a binding relationship between the MT and the DU of the relay node.
20. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 1 to 7.
21. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 8 to 14.
22. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 15 to 19.
23. A communication system, characterized in that: The communication system includes the communication device according to claim 20 and the communication device according to claim 21, or the communication system includes the communication device according to claim 21 and the communication device according to claim 22.
24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer is enabled to perform the method according to any one of claims 1 to 19.
25. A communication device, characterized in that: The device comprises a processor, the processor is coupled to a memory, the memory stores computer program instructions, and the processor is used to execute the computer program instructions so that the communication device performs the method according to any one of claims 1 to 19.
26. A computer program product, characterized in that The computer program product comprises a computer program, wherein the computer program comprises program instructions, and when the program instructions are executed, the computer is caused to perform the method according to any one of claims 1 to 19.
27. A communication method, characterized in that: include: Generate first information, where the first information is used to instruct a third centralized unit CU to send a cross-topology traffic migration request to a second CU, where a radio resource control RRC connection exists between the second CU and a mobile terminal MT of a relay node, and the third CU is a target host CU of a distributed unit DU of the relay node; Send the first information to the third CU.
28. The method according to claim 27, characterized in that The first information includes identification information of the second CU and a backhaul link adaptation layer protocol (BAP) address of the relay node to which the MT belongs in the second CU.
29. The method according to claim 28, characterized in that The identification information of the second CU includes the base station identifier gNB ID of the second CU.
30. The method according to any one of claims 27 to 29, characterized in that The first information is carried in an F1 establishment request message or a base station distributed unit configuration update GNB-DU CONFIGURATION UPDATE message.
31. A communication method, characterized in that: include: Receive first information, where the first information is used to instruct a third centralized unit CU to send a cross-topology traffic migration request to a second CU, where a radio resource control RRC connection is established between the second CU and a mobile terminal MT of a relay node, and the third CU is a target host CU of a distributed unit DU of the relay node; Send the cross-topology traffic migration request to the second CU.
32. The method according to claim 31, characterized in that The first information includes identification information of the second CU and a backhaul link adaptation layer protocol (BAP) address of the relay node to which the MT belongs in the second CU.
33. The method according to claim 32, characterized in that The identification information of the second CU includes the base station identifier gNB ID of the second CU.
34. The method according to any one of claims 31 to 33, characterized in that The first information is carried in an F1 establishment request message or a base station distributed unit configuration update GNB-DU CONFIGURATION UPDATE message.
35. The method according to any one of claims 31 to 34, characterized in that The sending the cross-topology traffic migration request to the second CU includes: Without obtaining the user equipment Xn interface protocol identifier UE XnAP ID of the MT under the second CU, the cross-topology traffic migration request carrying the BAP address of the relay node to which the MT belongs in the above-mentioned second CU is sent to the second CU.
36. A communication method, characterized in that: include: receiving an F1 setup request message, wherein the F1 setup request message includes a BAP address for target F1 interface transmission; In the case that the BAP address is self-assigned, the binding relationship between the mobile terminal MT of the relay node and the distributed unit DU of the relay node is determined based on the BAP address.
37. The method according to claim 36, characterized in that The BAP address is not allocated by itself means that the F1 establishment request message also indicates the identifier of the second CU that allocates the BAP address.
38. A communication method, characterized in that: include: Receive first information, where the first information is used to instruct a third centralized unit CU to send a cross-topology traffic migration request to a second CU, where a radio resource control RRC connection is established between the second CU and a mobile terminal MT of a relay node, where the third CU is a target host CU of a distributed unit DU of the relay node, and where the first information includes a BAP address of the relay node to which the MT belongs in the second CU; Information carrying the BAP address of the relay node to which the MT belongs in the second CU is sent to the second CU.
39. The method according to claim 38, characterized in that The sending, to the second CU, information carrying the BAP address of the relay node to which the MT belongs in the second CU includes: Send third information to the second CU, where the third information includes the BAP address, and the third information is carried in the cross-topology traffic migration request.
40. The method according to claim 38 or 39, characterized in that The sending, to the second CU, information carrying the BAP address of the relay node to which the MT belongs in the second CU includes: In the case where the user equipment Xn interface protocol identifier UE XnAP ID of the MT under the second CU is not obtained, information carrying the BAP address is sent to the second CU.
41. A communication method, characterized in that: include: Receiving information carrying a BAP address of a relay node to which a mobile terminal MT belongs in a second CU, wherein a radio resource control RRC connection exists between the second CU and the MT; Generate and send to the third CU a user equipment Xn interface protocol identifier UE XnAP ID of the MT under the second CU.
42. The method according to claim 41, characterized in that The BAP address information is carried in the cross-topology traffic migration request.
43. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 27 to 30.
44. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 31 to 35.
45. A communication device, characterized in that: Comprising modules or units for implementing the method of claim 36 or 37.
46. A communication device, characterized in that: The method comprises a module or a unit for implementing the method according to any one of claims 38 to 40.
47. A communication device, characterized in that: Comprising modules or units for implementing the method of claim 41 or 42.
48. A communication system, characterized in that: The communication system includes the communication device described in claim 43 and the communication device described in claim 44, or the communication system includes the communication device described in claim 46 and the communication device described in claim 47.
49. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed, the computer is enabled to perform the method according to any one of claims 27 to 42.
50. A communication device, characterized in that: The device comprises a processor, the processor is coupled to a memory, the memory stores computer program instructions, and the processor is used to execute the computer program instructions so that the communication device performs the method according to any one of claims 27 to 42.
51. A computer program product, characterized in that The computer program product comprises a computer program, wherein the computer program comprises program instructions, and when the program instructions are executed, the computer is caused to perform the method according to any one of claims 27 to 42.
